[Fixed] Non_blocking error

[anthonys]

Continuing the discussion from Anvil Extras 2.5:

For some reason, non_blocking is failing to import after this push.

No change in the code base. Has anyone else experienced this?

[demapped]

Yep. I started getting the same error about an hour ago, with no changes to my code.

[demapped]

I found that changing the version from “Published” to “v2.5.2” fixed the problem for me.

[wim.vandebrug]

Suddenly when running my app I got this error:
ModuleNotFoundError: No module named ‘anvil_extras.non_blocking’

whereas Yesterday everything worked fine. And I did not change anything in the code.
And the anvil_extras package is added:

When I define the version of anvil_extras explicitly to v2.5.2 it works fine.
What am I missing here?

[hugetim]

My guess is that the anvil_extras Published branch (in the Anvil cloud repo, which is not directly visible from GitHub for anvil_extras) inadvertently got set to one of the other fix patches @stucork pushed 5 hours ago, one that was pre-non_blocking: v2.3.1 or v2.2.4, that is.

The context:

[FIXED] Apps Unusable - has there been any updates?

Yes, you should bump the version to get the fix. Assuming you’re getting the same deserialization error from anvil_extras.storage Anvil-extras was using a type check rather than an isinstance check when deserializing objects from indexed-db. The return type from javascript changed and this led to the errors Edit: We’ve pushed the fix to 2.4.1 as a patch on 2.4.x This way you don’t need to bump the minor version

General PSA: If you have Anvil apps in production, it’s a good idea to set the notification level of the Bug Reports section this forum to “Normal” or higher so you at least see them in your feed when coming to the forum to report something, because otherwise I think it defaults to Muted:

[stucork]

That should now be fixed, apologies for the inconvenience. The Production version should be back to normal