The xyOps Roadmap

[jhuckaby]

I just published the xyOps roadmap:

https://github.com/pixlcore/xyops/wiki/Roadmap

What do you think? Anything missing you want to see added?

Let me know!

[talder]

Nice comprehensive list!

Maybe this is not the place to discuss this, but momentarily I'm missing some file monitoring integration on the satellite side. I have a dozen of servers/computers where files are dumped generated by medical devices. The files have to be processed ASAP, so if I could have a satellite on them with active file monitoring, i could trigger a workflow/event. The user will have to do some manual configuration on the satellite side to specify the folders to monitor for changes. Now the initiation to look for file changes has to come from the conductor/scheduler itself.

Kind regards,

Tim

[jhuckaby]

What a great feature! And this is the perfect place to drop it. Let me put some thought to how that could work. I have a few ideas...

[cju-mt]

talder, I currently do something similar. I use Salt beacons to accomplish this. I moved over from the Cronicle where I had been using Salt to fill in the gaps, using Cronicle as primarily a scheduler. Salt is super reliable.

[jhuckaby]

I'm working on this ASAP. First adding a feature request by @cju-mt (#158), then will add this one right away.

[jhuckaby]

@talder All done! Your feature request has been fully implemented in xyOps v1.0.10. I wrote up a whole Wiki about it:

https://github.com/pixlcore/xyops/wiki/Remote-File-Processor

[talder]

Wow! Thx! Will test this out this weekend.

[cju-mt]

Feature Suggestion: Native File Transfer Integration for Jobs

Background

The xyOps API already contains the basics needed for satellite file transfer — run_event
supports file injection via input.files, and upload_job_file allows a running job to push
files back to the conductor. These mechanisms are functional but require hand-rolling API calls
and custom error handling. There is no native GUI surface, no in-script trigger mechanism, and
no way to make transfer behavior part of the job definition itself.

Workflows already treat files as first-class data in several meaningful ways — the Split
controller can distribute one file per sub-job, the Join controller concatenates files from
upstream jobs, and input.files flows automatically between connected nodes. This suggestion
builds naturally on those foundations rather than introducing a foreign concept.

This suggestion proposes promoting file transfer to a first-class feature with both GUI
configuration and in-script command support.

---

Core Concepts

Push Files

Deliver one or more files from the conductor to the satellite — either automatically at job
start or triggered explicitly from within the script at any point during execution. Should
support individual files, glob patterns, and directories.

Pull / Return Files

Retrieve one or more files from the satellite back to the conductor — either at job completion
or triggered programmatically mid-script. This is particularly relevant for jobs that must wait
for an external process to produce output before returning results. Should support individual
files, glob patterns, and directories.

Wait For Files

A blocking in-script command that suspends execution until an expected file arrives at a
specified path. Once the file arrives, execution resumes automatically. This is conceptually
a condition-based counterpart to the existing Wait controller, which pauses on duration —
wait_for_files would pause on presence. The timeout parameter controls how long to wait
— on expiry, behavior should be governed by the transfer flags described below rather than
always being a hard failure.

---

In-Script Trigger Commands

The key capability being requested is the ability to trigger file operations from within the
script itself using recognized keywords or structured output — similar to how xyOps already
parses JSON output to capture job data. This allows the script to determine when a transfer
happens based on runtime logic, rather than being limited to fixed job lifecycle points.

Conceptual syntax:

##xyops:push_files source="C:\output\*.csv" destination="/data/reports/"
##xyops:pull_files source="/data/input/config.json" destination="C:\jobs\input\"
##xyops:wait_for_files path="C:\jobs\input\config.json" timeout=300

All transfer operations should produce visible output in the job log — bytes transferred,
files skipped, and success or failure — so the job log tells the complete story without
needing to look elsewhere.

---

Transfer Behavior Flags

Each transfer operation should support a set of behavioral options configurable both in the
job UI and as inline switches on the in-script trigger commands. UI-level flags would
apply as defaults for the entire job, while inline switches would allow individual transfer
commands within the same script to override those defaults as needed.

Conceptual inline syntax:

##xyops:push_files source="C:\output\*.csv" destination="/data/reports/" required_for_success
##xyops:pull_files source="/data/input/config.json" destination="C:\jobs\input\" only_if_newer
##xyops:wait_for_files path="C:\jobs\input\config.json" timeout=300 fail_silently

Flag	Description
Required for job success	If the transfer fails, the job is marked failed regardless of script exit code
Required for job to continue	Execution halts until the transfer completes; failure aborts the job
Transfer only if newer	Skips the transfer if the destination file is equal to or newer than the source
Fail silently	Logs the failure but allows the job to continue; useful for optional output collection

---

Workflow Integration

Native file transfer would compose naturally with several existing workflow features:

Multiplex controller — a push operation combined with a Multiplex node would become a
single-step "distribute this file to all target satellites" mechanism, with stagger support
already built in to avoid thundering herds.

Decision controller — if push and pull operations emitted a success/fail result into job
output data, a Decision node could branch the workflow based on transfer outcome, integrating
cleanly with existing conditional logic.

Split and Join controllers — the Split controller already distributes one file per sub-job;
native push/pull would let those distributed files be delivered to and retrieved from satellites
as part of the same workflow without custom API calls in every script.

---

Bucket Integration

Since buckets already exist and files staged via Fetch Bucket land in the job's temp directory,
it would be natural for push and pull operations to optionally reference a bucket as a source
or destination — keeping the entire workflow inside the platform without requiring external
storage references.

---

Summary

Many automation jobs aren't simple linear operations. A job may need to deliver a config file,
execute a process, wait for that process to produce output, retrieve the result, and only then
report success. In-script transfer triggers and a wait_for_files command would make that kind
of workflow fully expressible within a single job definition without custom API plumbing in
every script — and with native workflow support, those same patterns scale naturally across
many satellites at once.

Thanks for listening!

Oh.... One more thing... I love xyOps :)

[cju-mt]

Absolutely. Thanks From: Nick Dollimount ***@***.***> Sent: Tuesday, February 24, 2026 12:05 PM To: pixlcore/xyops ***@***.***> Cc: cju-mt ***@***.***>; Mention ***@***.***> Subject: Re: [pixlcore/xyops] The xyOps Roadmap (Discussion #153) Hi @cju-mt<https://github.com/cju-mt> ! Can you add this to the Issues tab as a new feature request to be properly tracked? - Reply to this email directly, view it on GitHub<#153 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC2ANZ3CEX5HX22HIW3GCLT4NSOE3AVCNFSM6AAAAACV3PNUYWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKOJRGQ2DCMY>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[undefined-moe]

Wonder if there would be a way to sync workflows from / to a git repository (for version control needs / easy rollbacks)

[jhuckaby]

That's on the roadmap! Coming in v1.1!

https://github.com/pixlcore/xyops/wiki/Roadmap#v11

• Remote filesystem sync with Git integration
  • Sync xyOps entities to and from filesystem formats suitable for Git workflows.
  • Add safe push/pull modes plus optional entity locking to reduce configuration drift.

[undefined-moe]

Sorry for duplicates but thanks for the quick reply!

Also this state: active column seems not very useful for active tasks list. maybe replace with time elapsed? (I'm currently having issues that causes the workflow to stuck forever in finishing state and i'll put details in a issue later)

[undefined-moe]

And it would be great if we can have a "Skipped" state instad of merging them to "Aborted"
Or maybe simply adding a option to silent crons aborted due to rate limits (those never executed)

e.g. having a cron task that runs every minute, sets max parallel to 1, and the job runs for 2 minutes, skipping one execution, currently it adds a aborted task to Errors page

[undefined-moe]

Proposal: Environments

Currently to deliver workflow required workflow scripts, there are two common ways:

1. use tools like npx to dynamically download them
   -> This requires probing registry and set packages up on every execution (and likely unzipping packages every time)
2. manually sync scripts used, or a git repo to every running worker, at the same location, then use cd /path/to/dir or ln -s /path/to/dir $PWD/work to get those scripts
   -> You'll have to manually upgrade/pull on each machine once you have changes to the environment
3. use xyops bucket (really?)

What I'm expecting:

Once a workflow job is triggered:

1. Check if there's existing environment setup on target machine (yes: goto step 5)
2. Download required environments at /opt/xyops/satellite/envs/[name-version]
3. Set them up (if setup script exists), and record env vars
4. Mark environment as ready
5. Update envLastUseTime (for garbage collection)
6. Load saved env vars from setup step, for application packages, add them to path (npm: read "bin" from package.json, add to $PATH, pypi: add dir to $PYTHONPATH, ...)
7. Execute workflow job

The whole structure might look like this:

environments:
  my-git-env:
    type: git
    remote: git@github.com:pixlcore/xyops
    defaultVersion: xxx
    setup: |
      eval "$(direnv export bash)"
      yarn install
      yarn build
      export APPLICATION_BUNDLE=xxx
      # [environment variables freeze here]
  esbuild-npm-env:
    type: npm
    package: esbuild
    defaultVersion: xxx
    registry?: https://registry.npmjs.com
  numpy-python-env:
    type: pypi
    package: numpy
    defaultVersion: xxx
    registry?: https://pypi.org/simple/

secret-vaults:
  some-secret:
    in-environments?:
    - esbuild-npm-env # use in workflow jobs that runs in that env
  ssh-private-key:
    setup-environments?:
    - my-git-env # use when setting up the environment

workflows:
  jobs:
    some-shell-job:
      environment?: 'my-git-env@commit-hash/tag' # used in `git checkout`, empty string for default version
      runs: |
        # no more setups
        yarn run test
    some-npm-job:
      environment?: 'esbuild-npm-env@version'
      runs: |
        esbuild --version

Open for comments and suggestions.

[jhuckaby]

use tools like npx to dynamically download them

This requires probing registry and set packages up on every execution (and likely unzipping packages every time)

This is not true, and not how npx works. It only downloads and unzips once, then it saves everything, including all expanded dependencies, on local disk (typically in ~/.npm/_npx). This local copy is then reused for repeated runs on the same server. uvx for python works the same way, as does go run for golang, as does docker run for Docker images.

This is exactly why I chose this system for the Plugin Marketplace. It allows you to publish a Plugin by shipping only a single command, and the runtime only needs to download it once -- on the first job run (on each server).

Note: There is a small nuance, as these tools do sometimes hit the network to update their registry metadata, but they never delete or reinstall locally stored packages.

[undefined-moe]

It only downloads and unzips once

seems yarn dlx does this every time (especially for package that marks preferUnplugged), npm wins this

---

Yes there's a cache under ~/.npm , but at least on my machine, it's not sometimes, it's every startup, and that's the issue --
It connects to registry.npmjs.org even if I locked the version number and just set them up, creating a ~0.5s extra startup delay.

 ⚡ { nodejs esbuild } Workspace  ~  strace -f -e trace=connect npx esbuild --version 2>&1
strace: Process 3726673 attached
strace: Process 3726674 attached
strace: Process 3726675 attached
strace: Process 3726676 attached
strace: Process 3726677 attached
strace: Process 3726678 attached
strace: Process 3726679 attached
strace: Process 3726680 attached
strace: Process 3726681 attached
strace: Process 3726682 attached
strace: Process 3726683 attached
[pid 3726683] +++ exited with 0 +++
⠙[pid 3726681] connect(28, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
[pid 3726681] connect(27, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
[pid 3726681] connect(27, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("114.114.114.114")}, 16) = 0
⠹[pid 3726681] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.10.34")}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.11.34")}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.8.34")}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.3.34")}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.5.34")}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.7.34")}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.6.34")}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.0.34")}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.1.34")}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.2.34")}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.4.34")}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.9.34")}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:322", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:922", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:222", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:122", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:522", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:b22", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:422", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:622", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:22", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:a22", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:822", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726681] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726681] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:722", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726672] connect(27, {sa_family=AF_INET6, sin6_port=htons(443), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:322", &sin6_addr), sin6_scope_id=0}, 28) = -1 EINPROGRESS (Operation now in progress)
[pid 3726672] connect(27, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("104.16.10.34")}, 16) = -1 EINPROGRESS (Operation now in progress)
Need to install the following packages:
esbuild@0.27.3
Ok to proceed? (y) y

⠇strace: Process 3726699 attached
⠏strace: Process 3726700 attached
strace: Process 3726701 attached
strace: Process 3726702 attached
strace: Process 3726703 attached
strace: Process 3726704 attached
strace: Process 3726705 attached
strace: Process 3726706 attached
⠋strace: Process 3726707 attached
[pid 3726706] +++ exited with 0 +++
strace: Process 3726708 attached
strace: Process 3726709 attached
strace: Process 3726710 attached
[pid 3726707] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3726707, si_uid=0} ---
strace: Process 3726711 attached
[pid 3726711] +++ exited with 0 +++
[pid 3726710] +++ exited with 0 +++
[pid 3726709] +++ exited with 0 +++
[pid 3726708] +++ exited with 0 +++
[pid 3726707] +++ exited with 0 +++
[pid 3726699] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3726707, si_uid=0, si_status=0, si_utime=0, si_stime=0} ---
[pid 3726703] +++ exited with 0 +++
[pid 3726701] +++ exited with 0 +++
[pid 3726702] +++ exited with 0 +++
[pid 3726704] +++ exited with 0 +++
[pid 3726700] +++ exited with 0 +++
[pid 3726705] +++ exited with 0 +++
[pid 3726699] +++ exited with 0 +++
[pid 3726672] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3726699, si_uid=0, si_status=0, si_utime=4 /* 0.04 s */, si_stime=4 /* 0.04 s */} ---
strace: Process 3726712 attached
strace: Process 3726713 attached
strace: Process 3726714 attached
strace: Process 3726715 attached
strace: Process 3726716 attached
0.27.3
[pid 3726716] +++ exited with 0 +++
[pid 3726715] +++ exited with 0 +++
[pid 3726714] +++ exited with 0 +++
[pid 3726713] +++ exited with 0 +++
[pid 3726712] +++ exited with 0 +++
[pid 3726672] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3726712, si_uid=0, si_status=0, si_utime=0, si_stime=1 /* 0.01 s */} ---
[pid 3726681] +++ exited with 0 +++
[pid 3726682] +++ exited with 0 +++
[pid 3726679] +++ exited with 0 +++
[pid 3726680] +++ exited with 0 +++
[pid 3726677] +++ exited with 0 +++
[pid 3726674] +++ exited with 0 +++
[pid 3726676] +++ exited with 0 +++
[pid 3726675] +++ exited with 0 +++
[pid 3726673] +++ exited with 0 +++
[pid 3726678] +++ exited with 0 +++
+++ exited with 0 +++
 ⚡ { nodejs esbuild } Workspace  ~  strace -f -e trace=connect npx esbuild --version 2>&1
strace: Process 3726747 attached
strace: Process 3726748 attached
strace: Process 3726749 attached
strace: Process 3726750 attached
strace: Process 3726751 attached
strace: Process 3726752 attached
strace: Process 3726753 attached
strace: Process 3726754 attached
strace: Process 3726755 attached
strace: Process 3726756 attached
strace: Process 3726757 attached
[pid 3726757] +++ exited with 0 +++
⠙[pid 3726755] connect(28, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
[pid 3726755] connect(27, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
[pid 3726755] connect(27, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("114.114.114.114")}, 16) = 0
⠹[pid 3726755] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.11.34")}, 16) = 0
[pid 3726755] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726755] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.8.34")}, 16) = 0
[pid 3726755] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726755] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.3.34")}, 16) = 0
[pid 3726755] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:922", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726755] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726755] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:222", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726755] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726755] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:122", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726746] connect(27, {sa_family=AF_INET6, sin6_port=htons(443), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:922", &sin6_addr), sin6_scope_id=0}, 28) = -1 EINPROGRESS (Operation now in progress)
[pid 3726746] connect(27, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("104.16.11.34")}, 16) = -1 EINPROGRESS (Operation now in progress)
strace: Process 3726761 attached
strace: Process 3726762 attached
strace: Process 3726763 attached
[pid 3726761] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3726761, si_uid=0} ---
strace: Process 3726764 attached
[pid 3726761] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3726761, si_uid=0} ---
strace: Process 3726765 attached
0.27.3
[pid 3726765] +++ exited with 0 +++
[pid 3726764] +++ exited with 0 +++
[pid 3726763] +++ exited with 0 +++
[pid 3726762] +++ exited with 0 +++
[pid 3726761] +++ exited with 0 +++
[pid 3726746] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3726761, si_uid=0, si_status=0, si_utime=0, si_stime=0} ---
[pid 3726755] +++ exited with 0 +++
[pid 3726756] +++ exited with 0 +++
[pid 3726754] +++ exited with 0 +++
[pid 3726753] +++ exited with 0 +++
[pid 3726751] +++ exited with 0 +++
[pid 3726750] +++ exited with 0 +++
[pid 3726749] +++ exited with 0 +++
[pid 3726748] +++ exited with 0 +++
[pid 3726747] +++ exited with 0 +++
[pid 3726752] +++ exited with 0 +++
+++ exited with 0 +++
 ⚡ { nodejs esbuild } Workspace  ~  strace -f -e trace=connect npx esbuild@0.27.3 --version 2>&1
strace: Process 3726803 attached
strace: Process 3726804 attached
strace: Process 3726805 attached
strace: Process 3726806 attached
strace: Process 3726807 attached
strace: Process 3726808 attached
strace: Process 3726809 attached
strace: Process 3726810 attached
strace: Process 3726811 attached
strace: Process 3726812 attached
strace: Process 3726813 attached
[pid 3726813] +++ exited with 0 +++
⠙[pid 3726811] connect(28, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
[pid 3726811] connect(27, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
[pid 3726811] connect(27, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("114.114.114.114")}, 16) = 0
⠹[pid 3726811] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.8.34")}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.3.34")}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.5.34")}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.7.34")}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.6.34")}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.0.34")}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.1.34")}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.2.34")}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.4.34")}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.9.34")}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.10.34")}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.11.34")}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:222", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:122", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:522", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:b22", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:422", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:622", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:22", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:a22", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:822", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:722", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:322", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726811] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726811] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:922", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726802] connect(27, {sa_family=AF_INET6, sin6_port=htons(443), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:222", &sin6_addr), sin6_scope_id=0}, 28) = -1 EINPROGRESS (Operation now in progress)
[pid 3726802] connect(27, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("104.16.8.34")}, 16) = -1 EINPROGRESS (Operation now in progress)
Need to install the following packages:
esbuild@0.27.3
Ok to proceed? (y) y

⠇strace: Process 3726834 attached
⠏strace: Process 3726835 attached
strace: Process 3726836 attached
strace: Process 3726837 attached
strace: Process 3726838 attached
strace: Process 3726839 attached
strace: Process 3726840 attached
strace: Process 3726841 attached
strace: Process 3726842 attached
[pid 3726841] +++ exited with 0 +++
⠋strace: Process 3726843 attached
strace: Process 3726844 attached
[pid 3726842] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3726842, si_uid=0} ---
strace: Process 3726845 attached
strace: Process 3726846 attached
[pid 3726846] +++ exited with 0 +++
[pid 3726845] +++ exited with 0 +++
[pid 3726844] +++ exited with 0 +++
[pid 3726843] +++ exited with 0 +++
[pid 3726842] +++ exited with 0 +++
[pid 3726834] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3726842, si_uid=0, si_status=0, si_utime=0, si_stime=0} ---
[pid 3726839] +++ exited with 0 +++
[pid 3726837] +++ exited with 0 +++
[pid 3726838] +++ exited with 0 +++
[pid 3726836] +++ exited with 0 +++
[pid 3726835] +++ exited with 0 +++
[pid 3726840] +++ exited with 0 +++
[pid 3726834] +++ exited with 0 +++
[pid 3726802] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3726834, si_uid=0, si_status=0, si_utime=5 /* 0.05 s */, si_stime=2 /* 0.02 s */} ---
strace: Process 3726847 attached
strace: Process 3726848 attached
strace: Process 3726849 attached
[pid 3726847] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3726847, si_uid=0} ---
strace: Process 3726850 attached
[pid 3726847] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3726847, si_uid=0} ---
strace: Process 3726851 attached
0.27.3
[pid 3726848] ???( <unfinished ...>
[pid 3726851] +++ exited with 0 +++
[pid 3726850] +++ exited with 0 +++
[pid 3726849] +++ exited with 0 +++
[pid 3726848] +++ exited with 0 +++
[pid 3726847] +++ exited with 0 +++
[pid 3726802] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3726847, si_uid=0, si_status=0, si_utime=0, si_stime=1 /* 0.01 s */} ---
[pid 3726811] +++ exited with 0 +++
[pid 3726812] +++ exited with 0 +++
[pid 3726810] +++ exited with 0 +++
[pid 3726809] +++ exited with 0 +++
[pid 3726807] +++ exited with 0 +++
[pid 3726806] +++ exited with 0 +++
[pid 3726805] +++ exited with 0 +++
[pid 3726804] +++ exited with 0 +++
[pid 3726803] +++ exited with 0 +++
[pid 3726808] +++ exited with 0 +++
+++ exited with 0 +++
 ⚡ { nodejs esbuild } Workspace  ~  strace -f -e trace=connect npx esbuild@0.27.3 --version 2>&1
strace: Process 3726875 attached
strace: Process 3726876 attached
strace: Process 3726877 attached
strace: Process 3726878 attached
strace: Process 3726879 attached
strace: Process 3726880 attached
strace: Process 3726881 attached
strace: Process 3726882 attached
strace: Process 3726883 attached
strace: Process 3726884 attached
strace: Process 3726885 attached
[pid 3726885] +++ exited with 0 +++
⠙[pid 3726883] connect(28, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
[pid 3726883] connect(27, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory)
[pid 3726883] connect(27, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("114.114.114.114")}, 16) = 0
⠹[pid 3726883] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.3.34")}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.5.34")}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.7.34")}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.6.34")}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.0.34")}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.1.34")}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.2.34")}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.4.34")}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.9.34")}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.10.34")}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.11.34")}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("104.16.8.34")}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:122", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:522", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:b22", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:422", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:622", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:22", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:a22", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:822", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:722", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:322", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:922", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726883] connect(27, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid 3726883] connect(27, {sa_family=AF_INET6, sin6_port=htons(0), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:222", &sin6_addr), sin6_scope_id=0}, 28) = 0
[pid 3726874] connect(27, {sa_family=AF_INET6, sin6_port=htons(443), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2606:4700::6810:122", &sin6_addr), sin6_scope_id=0}, 28) = -1 EINPROGRESS (Operation now in progress)
[pid 3726874] connect(27, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("104.16.3.34")}, 16) = -1 EINPROGRESS (Operation now in progress)
strace: Process 3726889 attached
strace: Process 3726890 attached
strace: Process 3726891 attached
strace: Process 3726892 attached
[pid 3726889] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3726889, si_uid=0} ---
strace: Process 3726893 attached
strace: Process 3726894 attached
0.27.3
[pid 3726894] +++ exited with 0 +++
[pid 3726893] +++ exited with 0 +++
[pid 3726892] +++ exited with 0 +++
[pid 3726891] +++ exited with 0 +++
[pid 3726890] +++ exited with 0 +++
[pid 3726889] +++ exited with 0 +++
[pid 3726874] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3726889, si_uid=0, si_status=0, si_utime=0, si_stime=1 /* 0.01 s */} ---
[pid 3726884] +++ exited with 0 +++
[pid 3726883] +++ exited with 0 +++
[pid 3726881] +++ exited with 0 +++
[pid 3726882] +++ exited with 0 +++
[pid 3726878] +++ exited with 0 +++
[pid 3726879] +++ exited with 0 +++
[pid 3726876] +++ exited with 0 +++
[pid 3726877] +++ exited with 0 +++
[pid 3726875] +++ exited with 0 +++
[pid 3726880] +++ exited with 0 +++
+++ exited with 0 +++
 ⚡ { nodejs esbuild } Workspace  ~  strace -f -e trace=connect esbuild --version 2>&1
strace: Process 3726962 attached
strace: Process 3726963 attached
strace: Process 3726964 attached
strace: Process 3726965 attached
[pid 3726963] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3726961, si_uid=0} ---
strace: Process 3726966 attached
strace: Process 3726967 attached
0.25.5
[pid 3726967] +++ exited with 0 +++
[pid 3726966] +++ exited with 0 +++
[pid 3726965] +++ exited with 0 +++
[pid 3726964] +++ exited with 0 +++
[pid 3726963] +++ exited with 0 +++
[pid 3726962] +++ exited with 0 +++
+++ exited with 0 +++
 ⚡ { nodejs esbuild } Workspace  ~  time npx esbuild --version
0.27.3
npx esbuild --version  0.54s user 0.05s system 45% cpu 1.311 total
 ⚡ { nodejs esbuild } Workspace  ~  time esbuild --version
0.25.5
esbuild --version  0.00s user 0.01s system 85% cpu 0.006 total 
⚡ { nodejs esbuild } Workspace  ~  npx --version
10.9.4
 ⚡ { nodejs esbuild } Workspace  ~  node --version
v22.21.1

Honestly 0.5s isn't unaffordable for me, but things can go worse: if under poor network condition to registry mirror during job startup, npx stuck there for minutes (try set https_proxy to something like http://localhost:12345 to observe) until it finally realizes "oh we should use a local cache instead".

[jhuckaby]

I'm sorry about NPX adding 0.5 seconds. That is unfortunate, but there is very little I can do about it in the short term.

I will look at introducing a new way of publishing Marketplace Plugins in the future, but it won't be until xyOps v2 or v3, as that is a very large redesign.

I just want to point out that this only affects Marketplace Plugins that are shipped via NPX or related tools. You can always write your own Plugins that invoke Node.js or similar runtime instantly, with no network delay.

[ovizii]

I read this on your roadmap:

e Web Hook From Template

One-click templates for Slack, Discord, Pushover, ntfy, and generic bearer-token APIs.

You can consider adding apprise-api to the mix. For now, I handcrafted a webhook which leads to my apprise, but I think this would be a good addition as it would add hundreds of target services. Some apps I self-host have this already baked in, so there's not even a needs to have a separate apprise-API instance of my own running.

[rasalter]

Thank you for a great scheduler. Wonderful. Really looking forward to the expanded CLI interface. We're planning to install and purchase support. I hate to ask, but is there an estimate for when it will be available? Thanks.

v1.1
Full remote CLI for xyOps
API-driven CLI for remote operations (e.g. xy events list, xy events run e12345, xy events run e12345 --follow).
Secure auth model using scoped API keys and session profiles.

[jhuckaby]

100% 😃 The CLI will support almost all of the API endpoints. Creating events is an absolute must! 👍🏻

[rasalter]

How is this coming along? I've seen great things in the release notes, but this is the thing we are looking forward to.

[jhuckaby]

Hi there @rasalter! Oh dang, I am so sorry, I said "end of July at the very latest" up above. Huge apologies for the delay, and the accidental lie. I am constantly working on the CLI, even this very evening as we speak, but I keep getting distracted with fixing bugs and (really good) feature requests from users 😝

Here are a few screenshots of the CLI (work in progress, final results may vary):

Dashboard:

---

Event List:

As you can see, it honors your custom category colors! 😃

---

Event Details:

---

Live job tracking, with progress bar and time remaining:

---

I'm especially proud of my animated progress bars, which admittedly I coded many years ago now:

---

The CLI is really fun and easy to use, and exposes the ENTIRE xyOps API, so you can create, edit, view and delete events, run jobs, upload files, manage tickets, track live jobs with progress, everything.

I'm using my own CLI toolkit called pixl-cli to render the tables, lists, progress bars and dash units.

I think it's about 75% complete at this point, if I could make an estimate. I believe version 1.0 of the CLI should be out in about 2 weeks, so let me just say "end of August" to be safe.

Sorry about my previous July estimate -- I was assuming I could spend the entire month on it, but that didn't happen.

I'm a solo-founder trying to do "everything", so I keep getting pulled away from this project. But I am committed to finishing it ASAP!

(Also, I refuse to cheat and use AI)

Back to coding!

[rasalter]

Great! Thanks. Looking forward to using it. Our team has been CLI based for years for managing our whole system, from database, detached tasks, and batch jobs, monitoring executing, held, and scheduled jobs with one command each of those three jobs statuses. Then if a job issues an alert e-mail, we can go to the application logs directory and search for the logs for that job for a piece of information from the e-mail alert or list the logs and find the right one based on the time of the e-mail alert and start the investigation. With one command we can see the creation and last modified time of the logs for a job to when and how long the job has been taking and see the size of the log files to see if anything is unusual. Then view the log file to see what happened and when. All from the command line. We can make a job scheduled for a later time run now, change when it will run, switch which queue it is going to run on when its queue gets backed up, delete the job, or put it on hold. We can see a full status of a job to see the queue, the user it is to run as, the script it is to run, where the log file will be, and the parameters that will be passed to the script(job). We can status each or all of the queues, stop or start them individually or all at once. This is very handy when we are starting the system back up from an outage, planned or unplanned. Being able to do the same with xyops will make it an easy transition. Thank you for all the hard work. :)

[jhuckaby]

Wow, that's a LONG list of requirements. I may not be able to hit all of those for v1, but I'll do my very best, and I will definitely be iterating on it over time.