I have been working successfully with uploading gen~ patches via the Mod watcher until today 
The watcher returns “Upload failed” and the max console returns
modduo.support: error returned from server 500 (phase Uploading…)
I have tried with multiple gen~ patches including the demo’s.
How can it work one day and not the next? Could it be something on my end?
error 500 means server error, something on our side.
@acunha has been doing some updates to the cloud to improve stability, seems you sadly run into a regression there.
Hi @Kevin I just fixed an issue regarding the maxgen pipeline. Please try again and let me know how it goes.
@acunha Tried again without success - although different error message this time
modduo.support: error returned from server 504 (phase Uploading…)
Hi @acunha, tried again today to upload (the gen~ dattorro reverb example patch) and received the following message
modduo.support: error returned from server 504 (phase Uploading…)
Btw I updated to the new Dwarf OS v1.12
Any thoughts?
@falkTX @acunha the Mod watcher still isn’t working for me can either of you comment on what’s happening with this?
modduo.support: error returned from server 504 (phase Uploading…)
Is there something I need to do to flag this as an issue? If so can you let me know who I need to contact?
My M1 Mac Mini had been spitting out errors using the MODwatcher regarding missing libzstd.1.dylib files in various places. After installing the Zstd library with Brew, that problem seems to be solved. The Mac Mini can finally see the Duo X using MODwatcher. So, I tried again. However, the following error message cropped up:
“modduo.support: error returned from server 504 (phase Uploading…)”
To be thorough, just tried the install on my Intel based MacBook Pro, and it gave the same error. In both cases, I was trying to install the Simple Vibrato as a test. Also checked the Duo X and it didn’t show up there.
So, one problem seems to be solved (Yay!).
At the very least, this problem doesn’t seem to have anything to do with which chip architecture is being used to run MaxMSP. Don’t know if this helps, but I thought I’d pass it on. I’ll keep my eye out for an update. Thanks for your time.
Lloyd
PS All of the relevant software and operating systems have been updated to the latest versions.
This seems to be a new thing that happened super recently. I already talked with @acunha about this, but he didn’t manage to figure out quickly from where the issue is coming and why it started to happen. So he will need a couple of weeks to look at this.
@lgdyson3 @jon Thanks for taking the time to reply.
So the issue seems to be uploading to the cycling 74 server?
Being so heavily dependent on everything working smoothly on my end, the Mod Device end and Cycling 74’s end simultaneously makes me feel a bit nervous about the stability of the system.
It would be great if I could run the custom MOD cloud build system on my own computer, is this a notion that is outside the realm of possibility I wonder?
I will maybe try the manual upload of gen~ patches described here when I get a chance
https://wiki.moddevices.com/wiki/Max_gen~
If anyone has any experience of doing this I’d love to hear how you got on…
for local builds.
I tried directly with the mod_build.sh and got this output:
Please type your plugin name, then press enter to confirm
TestExport
Submitting process...
Got release process 62a08e6d7be9543eb3e43883.
Uploading buildroot package...Traceback (most recent call last):
File "/Users/thomas/Downloads/max-gen-deploy/resources/publish.py", line 54, in <module>
checksum = json.loads(urlopen(release_process['source-href'], data).read().decode())
File "/opt/homebrew/Cellar/python@3.10/3.10.4/Frameworks/Python.framework/Versions/3.10/lib/python3.10/urllib/request.py", line 216, in urlopen
return opener.open(url, data, timeout)
File "/opt/homebrew/Cellar/python@3.10/3.10.4/Frameworks/Python.framework/Versions/3.10/lib/python3.10/urllib/request.py", line 525, in open
response = meth(req, response)
File "/opt/homebrew/Cellar/python@3.10/3.10.4/Frameworks/Python.framework/Versions/3.10/lib/python3.10/urllib/request.py", line 634, in http_response
response = self.parent.error(
File "/opt/homebrew/Cellar/python@3.10/3.10.4/Frameworks/Python.framework/Versions/3.10/lib/python3.10/urllib/request.py", line 563, in error
return self._call_chain(*args)
File "/opt/homebrew/Cellar/python@3.10/3.10.4/Frameworks/Python.framework/Versions/3.10/lib/python3.10/urllib/request.py", line 496, in _call_chain
result = func(*args)
File "/opt/homebrew/Cellar/python@3.10/3.10.4/Frameworks/Python.framework/Versions/3.10/lib/python3.10/urllib/request.py", line 643, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 504: Gateway Time-out
I’m not exactly sure how this system works, so I can’t really answer you on that, sorry 
This URL is broken
https://pipeline.dev.moddevices.com/maxgen/bundle/
Any update on this? “Couple of weeks” is a quite unacceptable support time for a important feature for some of us…
The problem has been fixed. Let me know if things are working.
Everytime I fixed something turns out some other thing was broken… Software is strange because if you leave it alone it actually gets old 
