ThomasCarter0973 · 9 May 2025, 15:19 UTC
Record the loaded module path and interpreter on each machine, then inspect the callable signature from those loaded copies. That should show whether the same script is reaching different interfaces before any controller communication occurs.
22 pointsDifferent copies indeed. Old machine loads from the job folder, new machine from its environment. Thanks, that saved more random reinstalling
6 pointsCompare the argument names accepted by those copies. Also establish the source and version of the working folder before deciding whether reproducing that environment or adapting the script is the appropriate change.
11 pointsDoes the shortcut use the same environment as your terminal? We have seen that difference in another laptop discussion, and it can make a repaired terminal test irrelevant to how operators launch the job.
23 pointsShortcut and terminal both use the same one here. The old folder accepts the argument, installed copy doesn't. Can't find a version label on the old folder yet
17 pointsLook for the original supplied archive or the handover message that accompanied it. A known working folder is worth preserving, but it should not become an unexplained dependency in the next handover.
8 pointsOur controller guide came in an email attachment with the revision in the filename, while the extracted folder just said SDK. Do you still have the delivery email?
21 pointsPurchasing has the original attachments. Looking there now
10 pointsDon't edit the argument out just to make the error go away. Find which interface you meant to use first.
16 pointsFound the archive. Supplier identified it against our controller setup in the same email. The files match the working job copy
19 pointsGlad purchasing kept it. Are you keeping that source message with the rebuilt setup notes?
10 pointsI would first reproduce the documented working environment for the existing read-only check, while preserving the current failed environment for comparison. Migrating to another SDK version can then be assessed separately if needed.
9 pointsDoing that. Notes now identify the archive and import path, plus the interpreter. No script edits so far
3 pointsGet someone else to follow the notes. You already know where all the hidden bits live.
14 pointsAnd use the normal launch shortcut for the final check. That was my concern earlier, even though the environments currently match.
17 pointsColleague rebuilt it from the notes and got past the argument check through the shortcut. Controller check is booked for the test slot
6 pointsRecord the read-only response shape as well as success, so you verify that the existing parser receives the interface it was written for.
17 pointsWas the original archive still available from the supplier too, or only in purchasing's mailbox?
19 pointsMake sure your team has its own approved copy either way. Email search is a rotten recovery tool at midnight.
14 pointsRead-only check passed, response handled correctly. Supplier confirmed the archive, and we've kept an approved local copy with the setup notes. That was a lot of fuss for code that hadn't changed
19 pointsThis discussion is closed to new replies after six months without activity. Last activity: .