bug: Meltano Upgrade on Windows stops with error "is not a valid Win32 application"
See original GitHub issueMeltano Version
2.3.0
Python Version
3.9
Bug scope
CLI (options, error messages, logging, etc.)
Operating System
Windows Server 2022 Standard
Description
I have noticed on Windows if the file(symbolic link) .meltano/run/bin
is present in your project when you run the upgrade via meltano upgrade
or the melatno ui
“Upgrade Button” you will get the following WinError
.
[WinError 193] %1 is not a valid Win32 application
if you remove the file and run meltano upgrade
the upgrade will complete. I am not sure what the long term ramification of deleting the file is.
Code
No response
Issue Analytics
- State:
- Created a year ago
- Comments:17 (12 by maintainers)
Top Results From Across the Web
error: update.exe is not a valid Win32 application
Hi,. This error can be caused if the below conditions are true: a. The path of a service's executable file contains spaces.
Read more >Fix: Not a Valid Win32 Application Error in Windows 10/11
Method 2: Try downloading the file from another source It may happen that the setup file is corrupt or an incomplete setup. Just...
Read more >How to fix a not a valid Win32 application error - Javatpoint
Sometimes or on rare occasions, Windows may report a bug as "not a valid Win32 application. This message, not a valid Win32 application,...
Read more >Methods to Resolve Not a Valid Win32 Application Error [2022]
Learn more about the biggest issue that the windows OS users face: Not a Valid Win32 Application Error. Get to know the reasons...
Read more >How to Fix "not a valid Win32 application" with (Simple Steps)
dll File. Shell32.dll is a critical system file in the Windows which is used by the OS whenever you run any executable file....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Admittedly I’m not very familiar for the context of why symlinks are created here and if there are other use cases where this is needed. However, it seems some of the context was from the days when Meltano was expecting users to manually create a virtualenv for Meltano, which may or may not be ‘activated’ at the time of invoking other processes. If Meltano is installed with
pipx
, as we currently recommend, then themeltano
shim should already be on thePATH
and I don’t know if we still need the symlinks.I don’t want to block a valid fix but I’ve opened a related item here for longer-term discussion on this topic:
The above proposes we pass a modified
PATH
or a customMELTANO_PATH
to processes that may need to invoke Meltano directly.@visch , @tayloramurphy , @aaronsteers , I was wondering does Windows even need a
.\.meltano\run\bin
file? Currently one is not created and everyone is running on pretty well. I made the assumption I was missing something vital but maybe runningmeltano init
andmeltano install
viapoetry shell
was adding something Windows users do not need. I guess I am also curious as to what purpose the.\.meltano\run\bin
symbolic link serves.