Open WadeBarnes opened 1 year ago
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 https://github.com/bcgov/aries-vcr/issues/751 which was causing credential processing (posting) errors.
Email sent to Registries to ask them to look into the issue.
Based on feedback from BC Registries PA0000002
has all it's dates set to 0001-01-01
which cause the error we're seeing. It's a little strange though, that the code is flagging the records for FM0794306
and not PA0000002
with the error.
We are waiting for a response from BC Registries as to why all the dates are set to 0001-01-01
on PA0000002
.
@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?
Checked-in with @amanji, this is still an issue. We might want to deal with it as part of the rewrite in #334
Pipeline Logs:
Pipeline Status Records:
cc @esune, @amanji, @ianco