-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
Nightly Build Failure 2024-03-05 #3441
Comments
I looked at the code and found that the error occurs here: if not os.path.exists(filedir):
os.makedirs(filedir) Which sort of seems like there is some sort of race condition going on where someone makes the dir between when the code checks for the dir and when it decides to make the dir. I'm confused because this happens before we split off into multiple workers. There's some concurrency stuff in the Arelle lib but it looks mostly UI-related? But maybe there's some weird code path in there that I don't understand. |
@bendnorman you had to do some fiddling to get the nightly build re-running last time, right? What was the fiddling? |
Yes! I manually kicked off the GitHub action for tag of the previous nightly build. |
Re-running fixed this. 🤷 |
I'm suspicious that this error may be related to the error we're getting in the FERC XBRL archivers: catalyst-cooperative/pudl-archiver#285 It's complaining about the same file early on https://www.xbrl.org/2003/xbrl-linkbase-2003-12-31.xsd |
And I guess this never comes up when running the ETL locally because this file has looong since been cached in my personal local arelle cache. |
I tried removing the cache directory entirely in my local setup and re-running the FERC to SQLite extraction, and it doesn't seem to care at all. It's not even repopulating the cached files |
Overview
Something funny seems to have happened with
arelle
's local cache...Next steps
What next steps do we need to do to understand or remediate the issue?
main
?Looks like we have an arelle change - we can try to see if 2.23.13 breaks locally too. And we can try to see if there are relevant code changes between those patch versions.
UPDATE 10:34 ET: 2.23.13 did not break the following ferc_to_sqlite run:
And the code changes between 2.23.10 and 2.23.13 didn't turn up anything suspicious.
Verify that everything is fixed!
Once you've applied any necessary fixes, make sure that the nightly build outputs are all in their right places.
Tasks
Relevant logs
link to build logs from internal distribution bucket
The text was updated successfully, but these errors were encountered: