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
The production parser is down for BD (at least until #7746), but there was no github issue for it opened saying the production parser is down as I expected.
Doing poetry run test-parser BD production leads to the following error, and BD data seems to have been estimated since 15th November. Why didn't we have an issue opened about it? I guess it can be because its failing to open new issues, but perhaps succeeding to comment on the PR as I've seen it active commenting previously.
BTW I think I might have figured out the issue here, it seems to think that estimated data also comes from the parsers, basically it's checking the output of our data instead of the inputs.
The production parser is down for BD (at least until #7746), but there was no github issue for it opened saying the production parser is down as I expected.
Doing
poetry run test-parser BD production
leads to the following error, and BD data seems to have been estimated since 15th November. Why didn't we have an issue opened about it? I guess it can be because its failing to open new issues, but perhaps succeeding to comment on the PR as I've seen it active commenting previously.The text was updated successfully, but these errors were encountered: