This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/cargo/master/arrow-31.0.0
in repository https://gitbox.apache.org/repos/asf/arrow-ballista.git
discard ef7b38a3 Update arrow requirement from 28.0.0 to 31.0.0
add 18e2cc88 Fix Cargo.toml format issue (#616)
add cbad55d7 Refactor executor main (#614)
add b1713967 Refactor scheduler main (#615)
add 8e2c5514 Update arrow requirement from 28.0.0 to 31.0.0
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (ef7b38a3)
\
N -- N -- N refs/heads/dependabot/cargo/master/arrow-31.0.0 (8e2c5514)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
ballista/client/Cargo.toml | 2 +-
ballista/core/Cargo.toml | 2 +-
ballista/executor/Cargo.toml | 5 +-
ballista/executor/src/bin/main.rs | 83 +++++++++++++
.../executor/src/{main.rs => executor_process.rs} | 128 +++++++++------------
ballista/executor/src/lib.rs | 1 +
ballista/scheduler/Cargo.toml | 4 +
ballista/scheduler/src/{ => bin}/main.rs | 111 +-----------------
ballista/scheduler/src/lib.rs | 1 +
ballista/scheduler/src/scheduler_process.rs | 122 ++++++++++++++++++++
10 files changed, 277 insertions(+), 182 deletions(-)
create mode 100644 ballista/executor/src/bin/main.rs
rename ballista/executor/src/{main.rs => executor_process.rs} (87%)
rename ballista/scheduler/src/{ => bin}/main.rs (60%)
create mode 100644 ballista/scheduler/src/scheduler_process.rs