Brent Swisher

Release v2.0.1 looks to have landed a fix for this as well, this PR can likely be closed now.

@rictic just a heads up I am pretty sure release v2.0.1 fixed this issue and it and #175 can both be closed now.

@shoupeva-ithaka - can you look this over and see if there is still work needed for this issue, and if so provide a status update on what is needed, and...

I think the difference between when it happens and when not is when there are releases for pharos-site as as well pharos itself, is that right?

I threw some time at this today. I didn't get far, but I don't know when I will get back to it so recording my findings here if it's useful...

@michael-iden Wondering what the status of this is, I see it has been open a few months. Is there work needed here? Should it be closed as no longer needed?

@michael-iden No worries at all, appreciate the work in this, just trying to do a little GitHub cleanup where I can! 😄