Need to exempt NBs that download data from automated runs

[mnwhite]

Two of the notebooks here download data from FRED and do stuff with it. When FRED is down or unavailable, DemARK's automated tests fail due to an http non-response. There are two potential solutions:

1. Exempt those two notebooks from the workflow

2. Store the downloaded data as a file in DemARK, and have a commented out cell indicating how it was originally produced.

[llorracc]

“as a in DemARK” as a “file” in DemARK? I Think our convention in Denmark is that everything is supposed to be a self-contained notebook. Can the data be stored inside the notebook? Sent from Gmail Mobile

…

On Mon, Feb 16, 2026 at 09:43 Matthew N. White ***@***.***> wrote: *mnwhite* created an issue (econ-ark/DemARK#241) <#241> Two of the notebooks here download data from FRED and do stuff with it. When FRED is down or unavailable, DemARK's automated tests fail due to an http non-response. There are two potential solutions: 1. Exempt those two notebooks from the workflow 2. Store the downloaded data as a in DemARK, and have a commented out cell indicating how it was originally produced. — Reply to this email directly, view it on GitHub <#241>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKCK7ZWRIT6MRDXAVYDG734MHJP5AVCNFSM6AAAAACVJMFGR2VHI2DSMVQWIX3LMV43ASLTON2WKOZTHE2DQMJQGQYDQNQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mnwhite]

Yes, I edited the issue a few seconds after posting to add the word "file".

We could have the data right in the notebook, but it would have to appear as a mass of numbers. Off the top of my head, I don't actually know how much data those two NBs are using.

I think it might be best to just exempt them from the auto-runs.

[llorracc]

Is there some diagnostic for the particular problem (sounds like maybe Fred downtime or something?) that the notebook encounters? If so then perhaps our test for that notebook should pass if that particular problem is occurring so it will not break in the future when the same thing happens, but then we would catch other breaking changes?

[mnwhite]

I think the only way to do that would be to have a try/except block, where the except would fill in dummy data that allows the notebook to run, but would produce nonsense results.

…

On Tue, Feb 17, 2026 at 2:44 PM Christopher Llorracc Carroll < ***@***.***> wrote: *llorracc* left a comment (econ-ark/DemARK#241) <#241 (comment)> Is there some diagnostic for the particular problem (sounds like maybe Fred downtime or something?) that the notebook encounters? If so then perhaps our test for that notebook should pass if that particular problem is occurring so it will not break in the future when the same thing happens, but then we would catch other breaking changes? — Reply to this email directly, view it on GitHub <#241 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADKRAFNCLEQPKOUNPBH5TQ34MNVQXAVCNFSM6AAAAACVJMFGR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSMJWG42DAOBWHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[llorracc]

Couldn't the execution of the notebook just terminate with a message saying "couldn't access Fred right now" or whatever, but exit with code 0?

[mnwhite]

Yes, that would work.

…

On Tue, Feb 17, 2026 at 2:55 PM Christopher Llorracc Carroll < ***@***.***> wrote: *llorracc* left a comment (econ-ark/DemARK#241) <#241 (comment)> Couldn't the execution of the notebook just terminate with a message saying "couldn't access Fred right now" or whatever, but exit with code 0? — Reply to this email directly, view it on GitHub <#241 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADKRAFOQWPQEAQE2ZMGKGGD4MNWZTAVCNFSM6AAAAACVJMFGR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSMJWG44DEMZZGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>