We use cookies and similar tools to enhance your experience, provide our services, deliver relevant advertising, and make improvements. Approved third parties also use these tools to help us deliver advertising and provide certain site features.
Customize cookie preferences
We use cookies and similar tools (collectively, "cookies") for the following purposes.
Essential
Essential cookies are necessary to provide our site and services and cannot be deactivated. They are usually set in response to your actions on the site, such as setting your privacy preferences, signing in, or filling in forms.
Performance
Performance cookies provide anonymous statistics about how customers navigate our site so we can improve site experience and performance. Approved third parties may perform analytics on our behalf, but they cannot use the data for their own purposes.
Allowed
Functional
Functional cookies help us provide useful site features, remember your preferences, and display relevant content. Approved third parties may set these cookies to provide certain site features. If you do not allow these cookies, then some or all of these services may not function properly.
Allowed
Advertising
Advertising cookies may be set through our site by us or our advertising partners and help us deliver relevant marketing content. If you do not allow these cookies, you will experience less relevant advertising.
Allowed
Blocking some types of cookies may impact your experience of our sites. You may review and change your choices at any time by clicking Cookie preferences in the footer of this site. We and selected third-parties use cookies or similar technologies as specified in the AWS Cookie Notice.
I want to see what the logs would look like if my Python code contains error so I removed a few quotation marks from my script. It should had caused errors, however the log still printed out normally for quite a while before it actually stopped working.
Is there a way to force them to pick up the new code right away?
Do we have access to the dev ticket?
What is the ETA?
Do we have a way to force the slave to reload the event plugins? Restart the slave, restart the machine�
Is there a place where we can see the last time it updated the events?
Yeah, restarting the Slave (easy if you have remote administration enabled) is the way to go here.
The developer tickets arenât publicly available but you can always ask us to poke on them.
If youâre developing scripts and need to restart often, running a Slave on your workstation or a test machine is the best way to iterate quickly on changes. Additionally, having a local Repository you can develop on as a staging area is quite nice and what we all do over here. @mois.moshev has had some good luck using this workflow.
It usually says in the applications log if verbose logging is enabled. I went digging to find an example, but came up empty handed. Itâs something like âreloading X because it has changed on diskâ where X is an event.
The log message saying that an event plugin is being reloaded as its changed on disk appears in your âConsoleâ panel in DL monitor if you have Verbose Logging enabled in Repo Options.
Developers/Scripters in DL should always have the âConsoleâ & âBackground Opsâ panels docked in their Monitor UI as power tools. HINT: you could saved a monitor layout either locally or share globally in your pipeline to âswitchâ into dev mode.
I too would be interested in more details about this.
Currently I am setting up a Linux worker, from my Windows machine. The local Windows worker always reloads its plugins when restarted, but this doesnât seem to happen reliably on Linux.
Perhaps this changed with sandboxing? From what I gather, event plugins run in their own sandbox process, and it is unclear how to manage that.