Refreshing the Stache causes throws an "Call to a member function collection() on null" error.

[dev-jenny]

Hi, as the title suggests - this happens both on the backend cache utility and when I call the Stache::refresh() method. Any idea what might cause it? I'm deleting entries programmatically and need to refresh the stache afterwards to avoid the Call to a member function selectedQueryColumns() on null issue.

Stacktrace:

[2021-10-12 10:46:12] local.ERROR: Call to a member function collection() on null {"userId":"da866361-ae6c-4e5a-997a-c2e28d448640","exception":"[object] (Error(code: 0): Call to a member function collection() on null at /home/vagrant/site1/vendor/statamic/cms/src/Structures/CollectionTree.php:48)
[stacktrace]
#0 /home/vagrant/site1/vendor/statamic/cms/src/Structures/CollectionTree.php(31): Statamic\\Structures\\CollectionTree->collection()
#1 /home/vagrant/site1/vendor/statamic/cms/src/Stache/Indexes/Value.php(34): Statamic\\Structures\\CollectionTree->path()
#2 /home/vagrant/site1/vendor/statamic/cms/src/Stache/Indexes/Value.php(12): Statamic\\Stache\\Indexes\\Value->getItemValue()
#3 [internal function]: Statamic\\Stache\\Indexes\\Value->Statamic\\Stache\\Indexes\\{closure}()
#4 /home/vagrant/site1/vendor/laravel/framework/src/Illuminate/Collections/Collection.php(642): array_map()
#5 /home/vagrant/site1/vendor/statamic/cms/src/Stache/Indexes/Value.php(13): Illuminate\\Support\\Collection->map()
#6 /home/vagrant/site1/vendor/statamic/cms/src/Stache/Indexes/Index.php(90): Statamic\\Stache\\Indexes\\Value->getItems()
#7 /home/vagrant/site1/vendor/laravel/framework/src/Illuminate/Collections/HigherOrderCollectionProxy.php(60): Statamic\\Stache\\Indexes\\Index->update()
#8 /home/vagrant/site1/vendor/laravel/framework/src/Illuminate/Collections/Traits/EnumeratesValues.php(234): Illuminate\\Support\\HigherOrderCollectionProxy->Illuminate\\Support\\{closure}()
#9 /home/vagrant/site1/vendor/laravel/framework/src/Illuminate/Collections/HigherOrderCollectionProxy.php(61): Illuminate\\Support\\Collection->each()
#10 /home/vagrant/site1/vendor/statamic/cms/src/Stache/Stores/Store.php(422): Illuminate\\Support\\HigherOrderCollectionProxy->__call()
#11 /home/vagrant/site1/vendor/laravel/framework/src/Illuminate/Collections/HigherOrderCollectionProxy.php(60): Statamic\\Stache\\Stores\\Store->warm()
#12 /home/vagrant/site1/vendor/laravel/framework/src/Illuminate/Collections/Traits/EnumeratesValues.php(234): Illuminate\\Support\\HigherOrderCollectionProxy->Illuminate\\Support\\{closure}()
#13 /home/vagrant/site1/vendor/laravel/framework/src/Illuminate/Collections/HigherOrderCollectionProxy.php(61): Illuminate\\Support\\Collection->each()
#14 /home/vagrant/site1/vendor/statamic/cms/src/Stache/Stache.php(109): Illuminate\\Support\\HigherOrderCollectionProxy->__call()
#15 /home/vagrant/site1/vendor/statamic/cms/src/Stache/Stache.php(98): Statamic\\Stache\\Stache->warm()
#16 /home/vagrant/site1/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(261): Statamic\\Stache\\Stache->refresh()
#17 /home/vagrant/site1/vendor/statamic/cms/src/Http/Controllers/CP/Utilities/CacheController.php(91): Illuminate\\Support\\Facades\\Facade::__callStatic()
#18 /home/vagrant/site1/vendor/statamic/cms/src/Http/Controllers/CP/Utilities/CacheController.php(76): Statamic\\Http\\Controllers\\CP\\Utilities\\CacheController->clearStacheCache()
#19 /home/vagrant/site1/vendor/laravel/framework/src/Illuminate/Routing/Controller.php(54): Statamic\\Http\\Controllers\\CP\\Utilities\\CacheController->clear()
#20 /home/vagrant/site1/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(45): Illuminate\\Routing...
"} 

[jasonvarga]

How are you creating the entries?

[dev-jenny]

They are coming from an API that I check every minute for changes:

$entry = Entry::find($id);

if ( $entry ) {
    $entry->merge($data);
} else {
    $entry = Entry::make()
    ->id($id)
    ->collection('jobs')
    ->blueprint('jobs')
    ->locale('nl')
    ->published(true)
    ->slug($slug)
    ->data($data)
    ->set('updated_at', now()->timestamp);
}
$entry->save();

Now if an entry is no longer in the API it gets deleted:

$jobs = Entry::query()
    ->where('collection', 'jobs')
    ->get();
$somethingGotDeleted = false;
foreach ($jobs as $job) {
    $id = $job->job_id;
    if (!in_array($id, $existingJobIdsFromAPI)) {
        if (Entry::find($id)) {
            $somethingGotDeleted = true;
            Entry::find($id)->delete();
        }
    }
}

I think the cache issue has nothing to do with this since it was happening before I've been using the API. Though I think the code above is more connected to the Call to a member function selectedQueryColumns() on null I linked to. And that's why I want to make the stache refresh work properly without the exception (which works by the way, it just throws the collection() on null exception).

[jasonvarga]

If you're using queues, then there's an issue opened for that. #2993

[dev-jenny]

Hi, no not using that. For now basically I just want to use Stache::refresh(); without it throwing an exception and it will solve my Call to a member function selectedQueryColumns() on null issue as well.

[dev-jenny]

Just found a fix for this. It is basically the same as issue #3478. The solution is to delete misconfigured .yaml files on the content/trees/ directory.