Skip to content

Conversation

@joel-wong-aws
Copy link
Contributor

What was the problem/requirement? (What/Why)

As I was debugging an issue with starting an adaptor, I got the error message

2024/12/16 21:45:13-06:00 INFO: Initializing backend process...
2024/12/16 21:45:13-06:00 ERROR: Failed to initialize backend process: [WinError 193] %1 is not a valid Win32 application
2024/12/16 21:45:13-06:00 ERROR: Entrypoint failed: [WinError 193] %1 is not a valid Win32 application
2024/12/16 21:45:13-06:00 Process pid 3584 exited with code: 1 (unsigned) / 0x1 (hex)

It's difficult to understand what went wrong here because the error message does not contain the command that was attempted to be run.

What was the solution? (How)

Increased log level from debug to info when printing out the arrgs that are about to be run before this command.

What is the impact of this change?

This will make it easier to debug issues when adaptors fail to start.

How was this change tested?

Added a unit test for the logs being printed at INFO level, it passed.

  • Have you run the unit tests?
    Yes

Was this change documented?

No, N/A

Is this a breaking change?

No

Does this change impact security?

No


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@joel-wong-aws joel-wong-aws requested a review from a team as a code owner December 18, 2024 21:54
@sonarqubecloud
Copy link

@joel-wong-aws joel-wong-aws enabled auto-merge (squash) January 31, 2025 02:33
@sonarqubecloud
Copy link

@joel-wong-aws joel-wong-aws merged commit 712e570 into OpenJobDescription:mainline Jan 31, 2025
19 checks passed
jblagden pushed a commit to jblagden/openjd-adaptor-runtime-for-python that referenced this pull request Aug 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants