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
We're using Inertia (via Nova) behind a load balancer.
Each server builds its own assets. The compilations and hashes are deterministic, but the files are sometimes listed in a different order in the manifest.json file from one server to the next. Because Inertia uses an md5 hash of the manifest.json file as for its version check, this results in frequent false positive version mismatches.
Would it be possible to use something less error-prone for the versioning check? The most error-proof option would be to parse and sort the json, but that could add excess overhead to each request. Is there a way to access the hash of the last git commit?
As is, Nova is almost unusable for us because of all the full page reloads when Inertia responds to a request with a 409 error.
The text was updated successfully, but these errors were encountered:
We're using Inertia (via Nova) behind a load balancer.
Each server builds its own assets. The compilations and hashes are deterministic, but the files are sometimes listed in a different order in the manifest.json file from one server to the next. Because Inertia uses an md5 hash of the manifest.json file as for its version check, this results in frequent false positive version mismatches.
Would it be possible to use something less error-prone for the versioning check? The most error-proof option would be to parse and sort the json, but that could add excess overhead to each request. Is there a way to access the hash of the last git commit?
As is, Nova is almost unusable for us because of all the full page reloads when Inertia responds to a request with a 409 error.
The text was updated successfully, but these errors were encountered: