Skip to content

Conversation

@janjakubnanista
Copy link
Collaborator

@janjakubnanista janjakubnanista commented Jun 10, 2025

Description

Very plug-here-plumb-there PoC of integration of the launch scheduler with the existing code.

Due to how we pass the arguments around, the L1 setup has been split into several atomic pieces that come together under the l1 name.

If used like this, this PR reveals the need for:

  • Dependency aggregator helpers - something that will just gather dependency outputs under a struct
  • Logging helpers - something that will wrap a particular item with before/after logs

Of course, the IDs should not be hardcoded all over the place, and the main.star should not be doing low-level work like this. But remember, PoC.

@janjakubnanista janjakubnanista changed the title Jan/needs and gets wip: Use schedule to launch L1 related services and tasks Jun 10, 2025
@janjakubnanista janjakubnanista changed the base branch from main to jan/needs June 10, 2025 03:15
@janjakubnanista janjakubnanista changed the title wip: Use schedule to launch L1 related services and tasks chore: Use schedule to launch L1 related services and tasks Jun 10, 2025
@janjakubnanista janjakubnanista force-pushed the jan/needs-and-gets branch 5 times, most recently from c8794e5 to d6475dd Compare June 10, 2025 18:31
@emhane emhane added the A-l1 Area: Layer 1 label Aug 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-l1 Area: Layer 1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants