Cache getting incorrectly accessed/read

Open
#15 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
api, backend

Research direction

Start by inspecting cms/jrbit/class/crisp/api/Flagsmith.php at line 53 and reproduce the restart scenario described for PHP CMS usage in Docker on tag 2.1.1. Compare behavior with an empty cache folder and after manually deleting it, then trace why cachedCall is null. Done means the client works after container restart without manual cache-folder removal.

Written by the indexing model from the issue text.

Description

bug

I am accessing flagsmith in a docker container via a PHP CMS and everytime after restarting I have to manually clear the cache folder (removing the cache folder via the entrypoint doesnt work aswell) due to an error that the cachedCall is null.

https://sentry.internal.jrbit.de/share/issue/4bf1cd4ca04b4cbcaca8541a37709f9e/

The cache folder is empty and after deleting it it works.

https://github.com/JRB-IT/crispcms/blob/68e313aedf9c30aa996ae10fead621acab24fe5b/cms/jrbit/class/crisp/api/Flagsmith.php#L53

Any clue on what the issue is an how to hotfix it? Running on Tag 2.1.1

Dominant language
PHP
Stars
18
Forks
13
Avg merge
28m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Flagsmith/flagsmith-php-client

All issues in Flagsmith/flagsmith-php-client

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.