0pdd
0pdd copied to clipboard
show total repositories count
Let's render this total repo counter on the front page. We will have to go through all S3 objects in the bucket and count them. Will take a lot of time, so let's invent some caching mechanism. Maybe, let's use stateful.co counter and increment it every time we create a new S3 object, which we've never seen before.
Job #30 is now in scope, role is DEV
The job #30 assigned to @silasreinagel/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this
@silasreinagel/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.
@yegor256 I'm pretty stuck on this issue, but I'm not sure what ticket to open. What I would normally do is connect to PROD S3 and develop until the counter integration is correct, but I don't have PROD credentials, and the integration is impossible without knowing exactly what and how the data is stored.
I wanted to try to integrate with Stateful, but it's broken, and I opened two bugs.
I would add just a counter to the page, but it feels degenerate to do that if it will only show 0 repositories for now.
What would you suggest? What ticket should I open?
@SilasReinagel what's missing in the project now?
The user @silasreinagel/z resigned from #30, please stop working. Reason for job resignation: It is older than 10 days, see §8
I should have rejected this ticket. This ticket is presently in a unimplementable state dor anyone who doesn't have access to the S3 instance.
The job #30 assigned to @dmydlarz/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this
The job #30 assigned to @danielpalafox/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be a monetary reward for this job
@danielpalafox/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.
The job #30 assigned to @shelvacu/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be a monetary reward for this job
@shelvacu/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.
The user @shelvacu/z resigned from #30, please stop working. Reason for job resignation: It is older than 10 days, see §8
The job #30 assigned to @golyalpha/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be a monetary reward for this job
@yegor256 I'd like to reiterate on @SilasReinagel's comment about the (testing) S3 instance access. Shall I open an issue about that?
@golyalpha I don't think we need any test access to S3 for testing. Let's just fake the connection with a mock object.
@golyalpha/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.
@0crat resign
@0crat resign (here)
@golyalpha The user @golyalpha/z resigned from #30, please stop working. Reason for job resignation: Order was cancelled
The job #30 assigned to @snugghash/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be a monetary reward for this job
@snugghash/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.
@0crat resign