Robert Chisholm

API appears to be back up, but now it's throwing an exception I've not seen it produce before. ``` namePairs[showName].update(); File "C:\Program Files\Anaconda3\lib\site-packages\pytvdbapi\api.py", line 212, in update self._populate_data() File "C:\Program...

Thanks, I'm glad this is something you've thought about. > a) Implement a more efficient method for identifying header dependencies. This was my initial thought, but as I thought about...

@benbarsdell > It doesn't ship a compiled binary, it just ships all of the source and headers along with (e.g., embedded in) the application. The offline preprocessing step just does...

So I started looking at this again today. I can't make much sense of #82, but from leo's other sources it appears they're using Jitify differently to us (we construct...

This is somewhat less important with recent Jitify compile speed improvements. Agent function compilation is now down to around 1 second per agent function (down from 7+s).

> so we can just rely on 11.2 +'s stability promises This seems like the best plan, assuming you're not aware of any HPC with only super old CUDA available.

Your choice tbh, you manage it. 11.2+ only feels simpler.

> i.e. visual studio 2019 issue? I have that on my home desktop, can try fighting it at some point. Or we just sack off VS2019, given it doesnt built...

> Fixes https://github.com/NVIDIA/jitify/issues/90 #90 refers to Jitify1. I take it this is in response to the performance regression between CUDA 12.1 and 12.2 (in a test case I've been investigating...

> This is actually not in response to that issue; I only just became aware of it and do not know the root cause (possibly some header hierarchy changed and...