Chris Chatelain

"finally" is not the word I'd use, it's been mentioned in detail multiple times by multiple people, you only needed to actually look. I am not the ticket author, but I was able to find the code that was mentioned in the very first message in a few seconds of looking at your code. All of the information was there. Even if you'd searched the most recent version of your code for mesact, you would have found it! It would have been faster than all of the exchanges denying the code existed. This is a very...

you seem to be trying very hard not to do your own due dilligence. I showed you the exact version of your code, and his license is right at the root of his project and has been there since December of 2022. https://github.com/jethornton/mesact/blob/master/LICENSE Also, are you suggesting that emitting a stacktrace to your users asking them to submit a github issue with your software at the mesact github repo is a reasonable thing? Look at the screenshot I posted, that's YOUR 1.5.0 version, and it...

I have no skin in the game other than curiosity, but I took a look. https://pasteboard.co/i2dOL3jZDbFC.png This is from ggieger.py version 1.5.0. It shows your excepthook is telling your users upon exception to file an issue at the mesaact github project, which is not associated with giegerlog. While it is trivial code that could easily have been come up with in isolation, the fact that it tells your users to file an issue at a github project that is not yours is an error that should be fixed. I...

I have no skin in the game other than curiosity, but I took a look. https://photos.google.com/u/0/photo/AF1QipPMbMUTnJeJmDNqvAsagnoRhQh0P7Dax0l-e5Od This is from ggieger.py version 1.5.0. It shows your excepthook is telling your users upon exception to file an issue at the mesaact github project, which is not associated with giegerlog. While it is trivial code that could easily have been come up with in isolation, the fact that it tells your users to file an issue at a github project that is not...

I have no skin in the game other than curiosity, but I took a look. https://photos.google.com/u/0/photo/AF1QipPMbMUTnJeJmDNqvAsagnoRhQh0P7Dax0l-e5Od This is from ggieger.py version 1.5.0. It shows your excepthook is telling your users upon exception to file an issue at the mesaact github project, which is not associated with giegerlog. While it is trivial code that could easily have been come up with in isolation, the fact that it tells your users to file an issue at a github project that is not...

I have no skin in the game other than curiosity, but I took a look. https://photos.fife.usercontent.google.com/pw/AP1GczOp2zSDG7PikF5VhV0AmKsBkksIGy3fVt6Win7inyKTBGCmJVcsaOFw_A=w944-h593-s-no?authuser=0 This is from ggieger.py version 1.5.0. It shows your excepthook is telling your users upon exception to file an issue at the mesaact github project, which is not associated with giegerlog. While it is trivial code that could easily have been come up with in isolation, the fact that it tells your users...

I have no skin in the game other than curiosity, but I took a look. https://photos.fife.usercontent.google.com/pw/AP1GczOp2zSDG7PikF5VhV0AmKsBkksIGy3fVt6Win7inyKTBGCmJVcsaOFw_A=w944-h593-s-no?authuser=0 This is from ggieger.py version 1.5.0. It shows your excepthook is telling your users upon exception to file an issue at the mesaact github project, which is not associated with giegerlog. While it is trivial code that could easily have been come up with in isolation, the fact that it tells your users...

I have no skin in the game other than curiosity, but I took a look. This is from ggieger.py version 1.5.0. It shows your excepthook is telling your users upon exception to file an issue at the mesaact github project, which is not associated with giegerlog. While it is trivial code that could easily have been come up with in isolation, the fact that it tells your users to file an issue at a github project that is not yours is an error that should be fixed. I suggest you remove any references to mesact,...