Cannot assign null to property Backpack\Basset\Helpers\CacheMap::$map of type array

[jefffairson]

Hello,

This is related to issue #107, I sitll have this error message randomly when testing with pest and --parallel option.

I applied the constant BASSET_DEV_MODE=true in my env file and it is correctly applied.
When using the parallel option, the constant is still present and applied but the error is still occuring randomly.

Cannot assign null to property Backpack\Basset\Helpers\CacheMap::$map of type array

  at vendor/backpack/basset/src/Helpers/CacheMap.php:31
     27▕         $this->filePath = $this->disk->path($this->basePath.'.basset');
     28▕ 
     29▕         // Load map
     30▕         if (File::exists($this->filePath)) {
  ➜  31▕             $this->map = json_decode(File::get($this->filePath), true);
     32▕         }
     33▕     }
     34▕ 
     35▕     /**

Juste for a quick test, I tried to do this on line 31 :
$this->map = json_decode(File::get($this->filePath), true) ?? [];

And the error did not occured anymore, but I don't know if it's the cleanest way.
This is pretty annoying as my tests execution took 5s with parallel instead of 30s without it.

Can you help with this ?

Thanks,
JF

[backpack-ai-bot]

This question is about an issue with Backpack's Basset component, so I can provide an answer based on the available knowledge sources.

The error you're encountering is related to a known issue with Basset when running tests in parallel. While setting BASSET_DEV_MODE=true in your .env file is a good first step, it seems that this doesn't fully resolve the problem in all cases.

The error occurs because the $map property is being assigned a null value, which is not compatible with its type declaration as an array. Your suggested fix of using the null coalescing operator to default to an empty array if the decoded JSON is null is a reasonable workaround.

However, there's a more official solution to this issue. According to the Basset issue #104, you can try the following steps to resolve this:

1. Add BASSET_CACHE_DISK=array to your .env.testing file.
2. In your phpunit.xml file, add the following line within the <php> section:

   <server name="BASSET_CACHE_DISK" value="array"/>

This configuration tells Basset to use an in-memory array for caching during tests, which should prevent the file-based caching issues you're experiencing when running tests in parallel.

If you're still encountering issues after applying these changes, you might want to consider opening a new issue on the Backpack Basset GitHub repository with details about your specific setup and the steps to reproduce the problem.

Remember to always use the latest version of Backpack and its components, as bug fixes and improvements are regularly released.

ℹ️ Please note our AI Bot does not reply to follow-ups, this will be the only AI answer in this thread. If the AI helped you find the answer, please mark it as answered or write details below so it can learn. Then close the conversation. If not, please give more information for when a human reads this. ℹ️

Relevant sources:

check if property is empty in request
Github Issue (closed): Default value not used when insert in db ?
Typo backback > backpack
Github Issue (closed): Remove backpack:publish-assets command from v6
bump basset version
DevTools: Trying to access array offset on value of type null
Revert "do not check for nullness"
Github Issue (closed): [Bug] basset issue
Github Issue (closed): [Bug] CSS not loaded when pushed on production
Github Issue (closed): [Bug]
Update basset to 0.16.0
Another problem with Basset
Github Issue (closed): Backpack CRUD preview shows error after composer update.
Backpack CRUD preview shows error after composer update.
Github Issue (closed): [Bug] Unable to run PEST tests on versions 5.4.12 and up