Pablo Galindo Salgado
Pablo Galindo Salgado
> @DinoV @colesbury I haven't paid attention to FT when I updated the draft implementation so please take a special look at that In particular `./python -m test test_import.test_lazy_imports -v`...
Thanks for the detailed bug report! I tried to reproduce this issue with some basic tests using large allocation files, but I wasn’t able to hit the same error condition....
My hypothesis as this time is that something is corrupting the files. This can be us somehow racing to write (unlikely but possible) or something in your file system. We...
My hypothesis as this time is that something is corrupting the files. This can be us somehow racing to write (unlikely but possible) or something in your file system. We...
The other option that I can think of is that you compile memray in the place you are using to read the file with some special debug changes to understand...
> Are output files good to parse at any point in time, or would the server have to be stopped for all related processes to finish writing? I just pulled...
> Not sure if this is the best place to discuss the name, but I'm not sure if "tracing" is the best new name for cProfile. > > First of...
CC @AA-Turner @hugovk @StanFromIreland
> I propose the name `profiling.boring` for cProfile. 
> In this case, would a (hypothetical) future stdlib tracing implementation be considered for the `profiling` package/namespace? Yes, I don't think is unreasonable > What about a similar but more...