-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
event_by_corp_filing errors processing records from LEAR #323
Comments
This is a problem with 2 records? Are the rest processing OK? Any other information beyond the logs to provide, @WadeBarnes ? BC Registries has in the past used a date of 0 to trigger magic handling, so my guess is this is an instance of that. @thorwolpert — could you please raise a flag with other BC Registries folks about this? I don’t know/can’t find the GitHub ID of folks like Dwayne and David Roberts. |
Yes, just an issue with the two records. All others are fine. No additional information yet. I have not looked at the data or associated code yet. |
OK — I think the next step is to have BC Reg look at this entity (it’s one sole prop) on their side and see what is magic about it. Their registration is in OrgBook BC — https://orgbook.gov.bc.ca/entity/FM0794306 I don’t see any new records associated with the entity, which is what is implied with these process failures. |
BTW, this issue is unrelated to bcgov/aries-vcr#751 which was causing credential processing (posting) errors. |
Email sent to Registries to ask them to look into the issue. |
Code that is failing: von-bc-registries-agent/data-pipeline/bcreg/bcreg_lear.py Lines 85 to 94 in ee1aa1e
|
Based on feedback from BC Registries We are waiting for a response from BC Registries as to why all the dates are set to |
@WadeBarnes @swcurran any updates on this? Can we close the issue if the problem is with the data, or do we still have something we need to be looking into? |
I forwarded you some additional information. Some decisions need to be made as to how we handle these situations. It looks like the BC Reg code may handle these issues, but the LEAR code does not contain the same logic. |
@esune, have we looked into fixing this issue yet? |
I believe this was being tackled by @amanji together with the other fixes to the pipeline - see https://app.zenhub.com/workspaces/bcgov-ditp-products-team-63c987121278d5001ecb177b/issues/zh/41 I believe the changes have been merged and are waiting for validation and promotion. |
@amanji, is there a PR associated to this ticket? |
Pipeline Logs:
Pipeline Status Records:
cc @esune, @amanji, @ianco
The text was updated successfully, but these errors were encountered: