Skip to content

Coop Bounty - 1 Start Work Missing #1678

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.

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

Closed
PixelantDesign opened this issue Jul 10, 2018 · 10 comments
Closed

Coop Bounty - 1 Start Work Missing #1678

PixelantDesign opened this issue Jul 10, 2018 · 10 comments

Comments

@PixelantDesign
Copy link
Contributor

from Tim Vanmourik

https://github.com/TimVanMourik/GiraffeTools/issues/72

A coop bounty, and two applications. However, the second one (@Thoughtscript) doesn't show up in the list, and the first one twice.

image 10

@PixelantDesign PixelantDesign added the bug This is something that isn't working as intended. label Jul 10, 2018
@owocki
Copy link
Contributor

owocki commented Jul 10, 2018

@pinkiebell is this something we missed in the last PR?

happy to tip out something extra if you can find a fix

@pinkiebell
Copy link
Contributor

@owocki I will take a look

@pinkiebell
Copy link
Contributor

@owocki can you trigger create_activity_records? Thanks

@pinkiebell
Copy link
Contributor

My guess: User's network connection was reset/other error after clicking on start work - modal dialog.
After that we update the ui and display a green success banner instead of an error.

@owocki
Copy link
Contributor

owocki commented Jul 10, 2018

the application to start work went through, but not the Activity object.. so I dont think it was a network issue

@pinkiebell
Copy link
Contributor

pinkiebell commented Jul 10, 2018

@owocki

Hmm. Then the user should be in 'bounty.interested' ? (looking at create_new_interest_helper)

https://gitcoin.co/actions/api/v0.1/bounties/?github_url=https://github.com/TimVanMourik/GiraffeTools/issues/72&network=mainnet&standard_bounties_id=724

@pinkiebell
Copy link
Contributor

pinkiebell commented Jul 10, 2018

Ohh wait. Maybe the second application @TimVanMourik means is a duplicate email from the first applicant?

Edit:
Btw, bounty's activity data is consistent with slackbot messages.

@TimVanMourik
Copy link

Hi @pinkiebell, sorry, my bug report wasn’t very elaborate. The timeline of the problem was this:

  1. @Weezyana07 applied, I received an email and I approved him
  2. @Thoughtscript applied (“@TimVanMourik - Signed up! Thanks!”). I did not receive any email. I checked out the page and saw screenshot above: a duplicate of @Weezyana07, although I could not approve him.
  3. You, @pinkiebell, applied as a test, I did receive the email and the gitcoin message was updated accordingly. I did not check out the bounty page to see if I could confirm you before you removed your application.

@pinkiebell
Copy link
Contributor

@TimVanMourik

Thanks! 'Weezyana07 Applied' & 'Worker Weezyana07, Approved' are two different events, so that is fine.

That means @Thoughtscript has not applied or he tried and had a network error and got no error message; which means he just has to hit 'Start Work' again ;).

I think the issue is closed then? @owocki

@TimVanMourik
Copy link

Ahhh, I was under the impression it was a ‘worker list’ instead of an ‘action list’! That in combination with @Thoughtscript not appearing lead me to this bug report. Problem resolved then! Thanks @pinkiebell

@thelostone-mc thelostone-mc removed the bug This is something that isn't working as intended. label Jul 19, 2018
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

No branches or pull requests

5 participants