You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to bring to your attention a compatibility issue that arises when using django-healthcheck in conjunction with django-storages version 1.14.4.
Description
After upgrading django-storages from 1.14.3 to 1.14.4, django-healthcheck tests that involve file existence checks started failing. The tests report that files cannot be found even though they were saved successfully. This seems to be due to a change in the behavior of the exists() method in django-storages as described in this issue.
Steps to Reproduce
Use django-healthcheck to run tests involving file storage.
Upgrade django-storages from 1.14.3 to 1.14.4.
Run the tests again and observe the failures indicating missing files.
Expected Behavior
Tests should pass as they did with django-storages 1.14.3, with the exists() method correctly identifying saved files.
Actual Behavior
Tests fail, reporting that files cannot be found immediately after they are saved.
Temporary Solution
Downgrading django-storages to 1.14.3 resolves the issue, but this is not a long-term solution due to the security patches included in 1.14.4.
The text was updated successfully, but these errors were encountered:
Hi,
I wanted to bring to your attention a compatibility issue that arises when using
django-healthcheck
in conjunction withdjango-storages
version 1.14.4.Description
After upgrading
django-storages
from 1.14.3 to 1.14.4,django-healthcheck
tests that involve file existence checks started failing. The tests report that files cannot be found even though they were saved successfully. This seems to be due to a change in the behavior of theexists()
method indjango-storages
as described in this issue.Steps to Reproduce
django-healthcheck
to run tests involving file storage.django-storages
from 1.14.3 to 1.14.4.Expected Behavior
Tests should pass as they did with
django-storages
1.14.3, with theexists()
method correctly identifying saved files.Actual Behavior
Tests fail, reporting that files cannot be found immediately after they are saved.
Temporary Solution
Downgrading
django-storages
to 1.14.3 resolves the issue, but this is not a long-term solution due to the security patches included in 1.14.4.The text was updated successfully, but these errors were encountered: