Skip to content

[3/N] Add back skyrl-train and skyrl-tx code#1140

Merged
erictang000 merged 1 commit intoNovaSky-AI:mainfrom
erictang000:add_tx_and_train
Feb 16, 2026
Merged

[3/N] Add back skyrl-train and skyrl-tx code#1140
erictang000 merged 1 commit intoNovaSky-AI:mainfrom
erictang000:add_tx_and_train

Conversation

@erictang000
Copy link
Collaborator

@erictang000 erictang000 commented Feb 16, 2026

Add back skyrl-train and skyrl-tx code for now while we ensure the migration to skyrl is smooth.

See #1138, #1139 for context.


Open with Devin

@erictang000 erictang000 merged commit 6b89b92 into NovaSky-AI:main Feb 16, 2026
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request re-introduces a significant amount of code for skyrl-train and skyrl-tx, including extensive documentation, examples, and CI configurations. The overall structure is well-organized. My review focuses on ensuring security best practices and script correctness. I've identified a potential security vulnerability regarding the handling of environment files containing secrets and a bug in one of the example run scripts. Please see the detailed comments for suggestions.

.pytest_cache/
build/
dist/
*.egg-info/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

To prevent accidental leakage of secrets, it's a good practice to ignore environment files that are meant to hold sensitive information. Files like .env.llm_judge and .env.miniswe contain placeholders for secrets or sensitive URLs and should not be tracked by git. Users can then create local copies from example files.

I recommend adding a rule to ignore all .env files, while keeping .env.example files. This can be done by renaming the secret-containing files to have a .example suffix and adding a rule like the following to your .gitignore.

*.egg-info/

# Ignore environment files that may contain secrets
.env*
!*.env.example

# bash examples/mini_swe_agent/run_mini_swe_30B.sh

# ensure that all worker nodes can access this data directory
DATA_DIR="$DATA/data/swe_gym_subset"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The environment variable $DATA is used here but it's not defined within the script. This will likely cause the script to fail if $DATA is not set in the user's environment. Other scripts in this PR use $HOME as a default. To make the script more robust and self-contained, you should either define $DATA or use a more standard variable like $HOME.

Suggested change
DATA_DIR="$DATA/data/swe_gym_subset"
DATA_DIR="$HOME/data/swe_gym_subset"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant