I then tried to re-track it but got some sort of error, though the command seemed to still proceed:
(esgdownload) ker:/net2/ker/UDA_downloads/esgf/log> esgpull track 11586f
/net2/ker/anaconda3/envs/esgdownload/lib/python3.12/site-packages/esgpull/database.py:143: SAWarning: Object of type <Query> not in session, add operation along 'File.queries' won't proceed (This warning originated from the Session 'autoflush' process, which was invoked automatically in response to a user-initiated operation.)
result = self.session.merge(item)
π <11586f> is now tracked.
(esgdownload) ker:/net2/ker/UDA_downloads/esgf/log> esgpull show
(esgdownload) ker:/net2/ker/UDA_downloads/esgf/log>
As seen above, when running esgpull show a third time, the query has been inadvertently deleted. I'm presuming this is not intended behavior and the query should simply be put back into a "tracked" state.
A query which was previously tracked:
Afterwards, I decided to untrack it:
I then tried to re-track it but got some sort of error, though the command seemed to still proceed:
As seen above, when running
esgpull show
a third time, the query has been inadvertently deleted. I'm presuming this is not intended behavior and the query should simply be put back into a "tracked" state.