Closed brianamarie closed 3 years ago
In case anyone is curious and would like to help troubleshoot, we will likely go through the course using a tool called smee.io to trace the signals sending webhooks (from GitHub) that the bot is listening to (Learning Lab). We'll especially look for any unexpected behavior around the steps where the course is freezing.
So I just started this tonight and am stuck at the same place. I am not sure why, but my node-forge
version expected by selfsigned
started as 0.8.2
, but then whenever i merge branches (e.g. [1], [2]), i have to resolve a conflict of bumping it to 0.9.0
. Probably this merge is failing, but I'm unsure how to proceed /-: I have tried merging master to staging-test
, sresolving the conflict, and pushing back to staging-test
, but that was not sufficient for the lab(?) to proceed.
omg, i was trying to fix it by updating the package versions in package* on master prior to doing the rest of the lab... i deleted my first attempt 🤦♂️ breaking all the links above 🤦♂️
Thank you for your work on this, @hcientist! Out of curiosity, did you have smee.io enabled while you were testing? I wonder if that would give us any more insight 🤔
Unfortunately not. I can try to make time some time this week.
aight so lemme figure out smee
@hcientist It may not be helpful, but at about minute 40 of this youtube video, I walk through configuring smee.io in a Learning Lab course for debugging.
https://youtu.be/nQ5oh9Et1As?t=2321 😃 here we go
What happens if I paste this smee log?
delete less than a minute ago
push less than a minute ago
check_suite 1 minute ago
check_run 1 minute ago
pull_request 1 minute ago
label 1 minute ago
check_run 2 minutes ago
pull_request 2 minutes ago
push 2 minutes ago
pull_request_review 2 minutes ago
pull_request 6 minutes ago
issue_comment 6 minutes ago
pull_request 6 minutes ago
push 6 minutes ago
push 11 minutes ago
delete 11 minutes ago
issue_comment 11 minutes ago
pull_request 11 minutes ago
push 11 minutes ago
pull_request 11 minutes ago
check_suite 12 minutes ago
check_run 12 minutes ago
check_run 12 minutes ago
check_run 12 minutes ago
check_run 12 minutes ago
check_run 13 minutes ago
check_run 13 minutes ago
check_run 13 minutes ago
check_run 13 minutes ago
check_run 13 minutes ago
check_run 13 minutes ago
pull_request 13 minutes ago
push 13 minutes ago
check_suite 17 minutes ago
check_run 17 minutes ago
check_run 17 minutes ago
check_run 17 minutes ago
check_run 17 minutes ago
check_run 17 minutes ago
check_run 18 minutes ago
check_run 18 minutes ago
check_run 18 minutes ago
check_run 18 minutes ago
check_run 18 minutes ago
issue_comment 18 minutes ago
check_run 18 minutes ago
pull_request 18 minutes ago
push 18 minutes ago
check_suite 31 minutes ago
check_run 31 minutes ago
check_suite 31 minutes ago
check_run 31 minutes ago
check_run 31 minutes ago
check_run 31 minutes ago
check_run 31 minutes ago
check_run 31 minutes ago
check_run 32 minutes ago
check_run 32 minutes ago
check_run 32 minutes ago
check_run 32 minutes ago
check_run 32 minutes ago
check_run 32 minutes ago
check_run 32 minutes ago
check_run 33 minutes ago
check_run 33 minutes ago
check_run 33 minutes ago
check_run 33 minutes ago
check_run 33 minutes ago
issue_comment 33 minutes ago
check_run 33 minutes ago
check_suite 33 minutes ago
pull_request 33 minutes ago
push 33 minutes ago
check_run 34 minutes ago
issue_comment 34 minutes ago
check_suite 34 minutes ago
pull_request 34 minutes ago
push 34 minutes ago
ping about 1 hour ago
I'm not entirely sure what this tells me ¯\(ツ)/¯ Still stopped at same step
A bug has been reported in Halp and in the Community forum, stating that the course is blocked after step 6/7.
Examples:
It appears the user approves the PR, the bot merges, but then the course freezes.
One user also reported a merge conflict in this PR, but that doesn't seem consistent across all bugs.
cc @ps-programs @mattdavis0351 👀