Update failure and error:
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
Research direction
Start by retrieving and reviewing the event-log report linked in the issue, then reproduce the failure while updating SEToolbox. Trace the update path from the point where the error occurs and confirm that the update completes without the reported failure.
Written by the indexing model from the issue text.
Description
Went to update SETOOLBOX and it throwed an error at me XD
https://ufile.io/g4sym is the file report from event log...
- Dominant language
- C#
- Stars
- 156
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 midspace/SEToolbox
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
1.202.120.1 Error Open
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
Crash on Replace Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in midspace/SEToolbox
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·