Inconsistent Webserver Validation Results#57
Open
austinmatherne-wk wants to merge 1 commit into
Open
Conversation
DisclosureSystem.select() clears mappedPaths on each request, so the __xule_resources_dir__ mapping registered once in init() was lost after the first request. Move the registration outside the once-only guard so it re-registers on every call, with a duplicate check for idempotency.
Contributor
|
We couldn't include this change in the final version of release 26.1 but we will add to a future release. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi @freddym56,
We received a support email regarding inconsistent EDGAR validation results from the webserver. The issue is that
mappedPathsis reset on each request, so the__xule_resources_dir__mapping registered once ininit()is lost after the first request. This can be avoided by moving the registration outside the once-only guard so it re-registers on every call, with a duplicate check for idempotency.The issue can be replicated by running:
first-request.json
second-request.json