kenneho.net

When running JUnit tests on a legacy code base at work I got the familiar “Argument(s) are different! [….] Actual invocation has different arguments” notice from Mockito. I ran the tests from the command line, but as I could see no difference between the expected and actual output I re-ran the tests inside IntelliJ to investigate further, resulting in this: Notice the trailing newline in the actual request made. From the reported error above it wasn’t straight forward figuring out…

Read More Read More

I recently got this error in Camel during unit testing: In case others come across the same issue, I thought I’d do a quick write-up on what the solution in my specific scenario was. Consider these production code extracts: The unit test: When running the unit test, I got the error referenced in the title: To get the test to work, just a very small adjustment to the production code was required: I’m running Camel 3.18.1.

In my BlitzJS project (which in turn utilizes NextJS), I ran into this error: Error: require() of ES Module /home/me/project/node_modules/three/examples/jsm/controls/DragControls.js from /home/me/project/node_modules/3d-force-graph/dist/3d-force-graph.common.js not supported. Instead change the require of DragControls.js in /home/me/project/node_modules/3d-force-graph/dist/3d-force-graph.common.js to a dynamic import() which is available in all CommonJS modules. The code causing the error was this: A quick refactor (for refernece including some additional code) resolved the issue:

I recently needed to convert a bunch of .msg files to PDF. I didn’t want to install any additional 3rd party software other than the Python libraries I needed. As the code would run on Windows servers, I though I’d utilize the excellen win32com Python package, and use only native Windows applications for performing the actual converting. I didn’t find a way to convert .msg to PDF in one, so I solved it by first using Outlook to convert the…

Read More Read More

Note to self: Here’s a super simple starting point for setting up a Flask application that supports both API and CLI interaction. To run it, run this command: To “map” the CLI to a custom app name, add a setup.py file with contents like this: Restart the Flask app. Now, uses can interact with the CLI like this: