Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug] 4 issues are generated instead of 2 issues #32

Closed
sinsukehlab opened this issue Mar 23, 2023 · 20 comments
Closed

[Bug] 4 issues are generated instead of 2 issues #32

sinsukehlab opened this issue Mar 23, 2023 · 20 comments
Labels
bug Something isn't working engineering

Comments

@sinsukehlab
Copy link
Contributor

Describe the bug
This course is expected to generate two issues, but it actually generates four issues (duplicate of duplicates).
See: https://github.com/sinsukehlab/connect-the-dots-check/actions/runs/4427726352/jobs/7765772081

To Reproduce
Steps to reproduce the behavior:

  1. Start course
  2. Click on the Actions tab
  3. See error

Expected behavior
This course is expected to automatically generate just two issues.

Screenshots
If applicable, add screenshots to help explain your problem.

Device information

  • Type: Desktop PC
  • OS: Windows 11
  • Browser: Chrome
  • Version: 111

Additional context
Add any other context about the problem here.
@sinsukehlab sinsukehlab added the bug Something isn't working label Mar 23, 2023
@sinsukehlab
Copy link
Contributor Author

The Step 0 workflow runs two times with one error and one success. Both runs create two issues.

@Tracy-Hamner
Copy link

Duplicate of #2

1 similar comment
@Devaaaaaaaaaaaa
Copy link

Duplicate of #2

@sinsukehlab sinsukehlab mentioned this issue May 29, 2023
Merged
@AMT3E
Copy link

AMT3E commented Jun 1, 2023

4d4be9b

@nikand19

This comment was marked as spam.

Sign in to view
@rukhjam
Copy link

rukhjam commented Jun 9, 2023

Duplicate of #2

2 similar comments
@PlayersSlayer96
Copy link

Duplicate of #2

@kolin1979
Copy link

Duplicate of #2

@Scullen0814
Copy link

@cmwilson21 #44

/**

Details

``

**

@CCSO3-Shawn
Copy link

Duplicate of #2

1 similar comment
@kakrakak
Copy link

Duplicate of #2

@ismaeel771
Copy link

9f4f80a

@ShomaVGujjar
Copy link

Duplicate of #2

This was referenced Jul 24, 2023
Closed
Closed
@ShomaVGujjar
Copy link

#23

@JANNUSATISHKUMAR
Copy link

9f4f80a

@dipaklean
Copy link

Duplicate of #2

@pandi1424gl
Copy link

ff885ef

@pandi1424gl
Copy link

#2 f885ef

@sinsukehlab
Copy link
Contributor Author

The recent update #39 has resolved this issue somehow.

@Gabor12321
Copy link

Duplicate of #2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working engineering
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests