Urgh. Bot now failing at a stage that it’s never failed before. I don’t think I changed anything that could have affected that… And worst…in the four times I’ve tried running this, I’ve gotten 2 different errors. One the first two times, which is made up of a bunch of JSON-esque stuff, and the second 2 times it’s a more traditional stack trace…for a library that isn’t being used until long after the line that it failed on.
Oh, well. I figured out that the problem was not where I thought it was. Guess I needed better logging. The problem is, in fact, in an area that I’ve changed recently.
I know how to fix it in the short term…but the problem was caused by something I put in place because that was the proposed solution to how to get it running under Docker. So now I have to go back to the drawing board on that one…
Urgh. Bot now failing at a stage that it’s never failed before. I don’t think I changed anything that could have affected that… And worst…in the four times I’ve tried running this, I’ve gotten 2 different errors. One the first two times, which is made up of a bunch of JSON-esque stuff, and the second 2 times it’s a more traditional stack trace…for a library that isn’t being used until long after the line that it failed on.
Oh, well. I figured out that the problem was not where I thought it was. Guess I needed better logging. The problem is, in fact, in an area that I’ve changed recently.
I was just about to ask what happened. Glad you got it sorted 👍
I know how to fix it in the short term…but the problem was caused by something I put in place because that was the proposed solution to how to get it running under Docker. So now I have to go back to the drawing board on that one…