Closed rndquu closed 7 months ago
Hi @rndquu Can I work on this issue?
- /start: Assign the origin sender to the issue automatically.
- /stop: Unassign the origin sender from the issue automatically.
- /help: List all available commands.
- /autopay: Toggle automatic payment for the completion of the current issue.
- /query: Comments the users multiplier and address
- /multiplier: Set the bounty payout multiplier for a specific contributor, and provide the reason for why.
example usage: "/wallet @user 0.5 'Multiplier reason'"
- /allow: Set access control. (Admin Only)
- /wallet: <WALLET_ADDRESS | ENS_NAME>: Register the hunter's wallet address.
ex1: /wallet 0x0000000000000000000000000000000000000000
ex2: /wallet vitalik.eth
@devilkiller-ag
Hi @rndquu Can I work on this issue?
Hey, sure
How does devpool bounties sync all bounties, when does it know to run
@rndquu
How does devpool bounties sync all bounties, when does it know to run
This github workflow syncs bounties (i.e. github issues) every 15 minutes
/start
/assign
ill just make the pr first i guess
/stop
! No assignees found for issue
/start
Warning! | This task was created over 184 days ago. Please confirm that this issue specification is accurate before starting. |
Deadline | Mon, Mar 4, 4:25 PM UTC |
Registered Wallet | 0xAe5D1F192013db889b1e2115A370aB133f359765 |
/wallet 0x0000...0000
if you want to update your registered payment wallet address.+ Evaluating results. Please wait...
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 1 | 0.8 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
ill just make the pr first i guess... | 0.8 | 0.33 | 0.8 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Specification | 1 | 31.8 |
Issue | Comment | 2 | 3.8 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
Check the [list](https://github.com/ubiquity/devpool-directory/i... | 31.8a: count: 2 score: "2" words: 2 li: count: 3 score: "3" words: 81 code: count: 3 score: "3" words: 3 | 1 | 31.8 |
> Hi @rndquu Can I work on this issue? Hey, sure... | 0.4 | 0.1 | 0.4 |
> How does devpool bounties sync all bounties, when does it know... | 3.4a: count: 1 score: "1" words: 1 | 0.59 | 3.4 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 2 | 1.4 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
How does devpool bounties sync all bounties, when does it know t... | 1.3 | 0.81 | 1.3 |
@rndquu ... | 0.1 | 0.47 | 0.1 |
This isn't working @rndquu @Keyrxng
This is currently assigned:
https://github.com/ubiquity/card-issuance/issues/26
Public and private issues are affected.
This isn't working @rndquu @Keyrxng
This is currently assigned:
Public and private issues are affected.
https://github.com/ubiquity/devpool-directory-private doesn't have the latest code from https://github.com/ubiquity/devpool-directory
https://github.com/ubiquity/devpool-directory-private should have been forked from https://github.com/ubiquity/devpool-directory, @devpanther could you fix it?
Oh @rndquu, I've forgotten but something did not work when we forked.
Oh yeah, we can't private a fork of a public repo
I don't have access to privates anymore
Oh @rndquu, I've forgotten but something did not work when we forked.
Oh yeah, we can't private a fork of a public repo
I don't have access to privates anymore
https://github.com/ubiquity/work.ubq.fi/issues/2#issuecomment-2015254588
You need write access to https://github.com/ubiquity/devpool-directory-private, right?
I don't have access to privates anymore
https://github.com/ubiquity/work.ubq.fi/issues/2#issuecomment-2015254588
You need write access to https://github.com/ubiquity/devpool-directory-private, right?
Yes
I don't have access to privates anymore
ubiquity/work.ubq.fi#2 (comment) You need write access to https://github.com/ubiquity/devpool-directory-private, right?
Yes
Sent invite with write access to https://github.com/ubiquity/devpool-directory-private
This needs to be addressed in time for the conference. @Keyrxng can you handle this?
Otherwise @ubiquity/software-development any takers?
what is the fuzz with this task, why it was reopened, it had 2 linked PRs assuming solving this issue?
if bounty is unavailable (i.e. assigned to some bounty hunter) and exists in the list with the state open then close such bounty
This is not implemented correctly. I receive frequent complaints from new would-be candidates that its tedious to go through the devpool.directory and constantly have to sift through already assigned tasks.
This is especially relevant as we are hiring a team of developer relations managers to find devs at the upcoming conference this week, with their first point of entry being the devpool.directory
if bounty is unavailable (i.e. assigned to some bounty hunter) and exists in the list with the state open then close such bounty
This is not implemented correctly. I receive frequent complaints from new would-be candidates that its tedious to go through the devpool.directory and constantly have to sift through already assigned tasks.
This is especially relevant as we are hiring a team of developer relations managers to find devs at the upcoming conference this week, with their first point of entry being the devpool.directory
The is implemented correctly. As you already mentioned you see already assigned issues only from private repos.
TLDR;
The is implemented correctly. As you already mentioned you see already assigned issues only from private repos.
No my comment asserts that public and private repos are affected. Besides, I just checked again and the first task from a public repos is assigned.
My current open PR against the devpool is the logic which ran to produce this result. However, the original issue was resolved according to the spec here and that was just to remove the unavailable
bounties from the devpool repo was it not? The work UI interfacing was not part of this bounty
However, the original issue was resolved according to the spec here and that was just to remove the
unavailable
bounties from the devpool repo was it not?
You're right. I read the following as "closing" the issue which means that it would not render in the work.ubq.fi UI
if bounty is unavailable (i.e. assigned to some bounty hunter) and exists in the list with the state open then close such bounty
With an emphasis on
then close such bounty
So we need to file a new issue and get a new pull request to actually close them?
+ Evaluating results. Please wait...
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 5 | 21.2 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
This isn't working @rndquu @Keyrxng This is currently assigned... | 2.4 | 0.16 | 2.4 |
This needs to be addressed in time for the conference. @Keyrxng ... | 2.1 | 0.56 | 2.1 |
> if bounty is unavailable (i.e. assigned to some bounty hunter)... | 8.5a: count: 2 score: "2" words: 4 | 0.61 | 8.5 |
> The is implemented correctly. As you already mentioned you see... | 2.6 | 0.585 | 2.6 |
> However, the original issue was resolved according to the spec... | 5.6code: count: 1 score: "1" words: 1 | 0.45 | 5.6 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 1 | 2 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
what is the fuzz with this task, why it was reopened, it had 2 l... | 2 | 0.47 | 2 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 3 | 3.4 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
Oh @rndquu, I've forgotten but something did not work when we fo... | 2.5 | 0.16 | 2.5 |
I don't have access to privates anymore ... | 0.8 | 0.27 | 0.8 |
> > I don't have access to privates anymore > > https://github.... | 0.1 | 0.3 | 0.1 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 1 | 0.8 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
ill just make the pr first i guess... | 0.8 | 0.23 | 0.8 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 2 | 10.3 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
# Open in UBQ devpool: ![empty_string_unassigned](https://git... | 3.7h1: count: 4 score: "1" words: 24 | 0.5 | 3.7 |
- https://github.com/ubiquity/devpool-directory/pull/1145 My ... | 6.6li: count: 1 score: "0.25" words: 8 code: count: 1 score: "0.25" words: 1 | 0.595 | 6.6 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Specification | 1 | 31.8 |
Issue | Comment | 7 | 40.8 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
Check the [list](https://github.com/ubiquity/devpool-directory/i... | 31.8a: count: 2 score: "2" words: 2 li: count: 3 score: "3" words: 81 code: count: 3 score: "3" words: 3 | 1 | 31.8 |
> Hi @rndquu Can I work on this issue? Hey, sure... | 0.4 | 0.13 | 0.4 |
> How does devpool bounties sync all bounties, when does it know... | 3.4a: count: 1 score: "1" words: 1 | 0.24 | 3.4 |
> This isn't working @rndquu @Keyrxng > > This is currently a... | 9.6a: count: 1 score: "1" words: 4 | 0.19 | 9.6 |
> Oh @rndquu, I've forgotten but something did not work when we ... | 4.4 | 0.4 | 4.4 |
> I don't have access to privates anymore https://github.com/... | 4.8 | 0.56 | 4.8 |
> > > I don't have access to privates anymore > > > > > > [... | 3.6a: count: 1 score: "1" words: 6 | 0.44 | 3.6 |
> > if bounty is unavailable (i.e. assigned to some bounty hunte... | 14.6a: count: 4 score: "4" words: 6 li: count: 2 score: "2" words: 39 | 0.51 | 14.6 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 2 | 1.4 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
How does devpool bounties sync all bounties, when does it know t... | 1.3 | 0.08 | 1.3 |
@rndquu ... | 0.1 | 0.37 | 0.1 |
However, the original issue was resolved according to the spec here and that was just to remove the
unavailable
bounties from the devpool repo was it not?You're right. I read the following as "closing" the issue which means that it would not render in the work.ubq.fi UI
if bounty is unavailable (i.e. assigned to some bounty hunter) and exists in the list with the state open then close such bounty
With an emphasis on
then close such bounty
So we need to file a new issue and get a new pull request to actually close them?
Sorry confused that PR with the decimals one but once the next action run happens im certain that decimals will be closed,
Although the QA I presented and if you check the devpool, it states this issue is closed and you have just left a comment on the PR associated with it
FYI current issue (hiding unavailable bounties) works as expected in https://github.com/ubiquity/devpool-directory/pull/1145
FYI current issue (hiding unavailable bounties) works as expected in https://github.com/ubiquity/devpool-directory/pull/1145
I see, thanks for highlighting this.
The proper form of delivery would require cherry picking changes and associating them with a task to be eligible for the reward.
Hiding the unavailable
bounties was implemented correctly when rndquu closed this as completed. I just deleted all issues and then checked-out from the merge commit with the only change being commenting out the twitter stuff and no unavailable
labels or assigned issues exist in my devpool
Check the list of all available partners' bounties.
When a bounty (i.e. issue) has the
Unavailable
label it means that the bounty is already assigned to some bounty hunter. We should hide such bounties from the list.What should be done:
open
then close such bountyclosed
then reopen such bounty