sasjs submitted job did not show up in SAS EVM
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- cli
Research direction
No file, test, command, or reproduction details are provided. Start by tracing the CLI's sasjs job-submission entry point and determine how submitted jobs are expected to appear in SAS EVM. Done means a submitted job is visible in SAS EVM, with a regression test or reproduction documented if the project supports one.
Written by the indexing model from the issue text.
Description
sasjs submitted job did not show up in SAS EVM
- Dominant language
- TypeScript
- Stars
- 40
- Forks
- 6
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sasjs/cli
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
refactoring
-
refactoring
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
adapter refactoring
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·