18558: Rubee Coinmaster

[RSS Bot]

Rubee Coinmaster

by darzil on 2018-04-10 15:34:41

M /src/data/items.txt (view) (diff)
M /src/net/sourceforge/kolmafia/CoinmasterRegistry.java (view) (diff)
M /src/net/sourceforge/kolmafia/RequestLogger.java (view) (diff)
M /src/net/sourceforge/kolmafia/objectpool/ItemPool.java (view) (diff)
M /src/net/sourceforge/kolmafia/request/NPCPurchaseRequest.java (view) (diff)
A /src/net/sourceforge/kolmafia/request/RubeeRequest.java (view)
M /src/net/sourceforge/kolmafia/swingui/CoinmastersFrame.java (view) (diff)

[Veracity]

Sure wish sourceforge would fetch 18556, 18557, and 18559 for me; "svn update" says I am up-to-date at 18555.

[Veracity]

Somebody else's bug report to sourceforge:

"My subversion repos are completely broken now. Worked with it 6 hours ago, now svn access is completely unusable:

Updating one repo gives "At revision 2577" although I checked in revision 2578 yesterday and the web frontend acknowledges that there is a revision 2578. But when browsing rev 2578 of my "glvertex" repo I get "Oh snap! We can't process this request."

Updating another repo just yields "svn: E160006: No such revision 544" although the repo "ofxworkbench" is already at revision 551.

What is going on with sourceforge??? Before the move of the new server backend sourceforge was slow but usable, after the move it was slower and now it is unusable!"

Yup. Looking at the svn checkins on this forum, for the newest 3, it gives that "oh, snap" message.

Sourceforge's response:

"Hello,

Our DevOps team found and discovered the issue.

They asked that you please re-push the lost revisions.
Sincerely,

SourceForge Support"

[Veracity]

There are quite a few people saying that it looks like their project was restored from a few days ago.

How are you supposed to "re-push the lost revisions"?

[AlbinoRhino]

Huh. Tortoise updated me to 18558 earlier today. Now when I click it it says "No such revision 18558". (Even though I already have that revision and in fact just finished playing my turns with a build from it.) Maybe sourceforge broke something in the past several hours?

[Veracity]

I believe it. I opened a trouble ticket.

[Darzil]

Interesting, I could see the ticket earlier, but now it needs a login and even if I do I have no access.

Hopefully means someone has taken ownership of the issue, as it no longer appears in Open Issues, though it also doesn't yet work.

[Veracity]

"Hello,

Our DevOps team discovered and fixed the issue.

They ask that you please re-push the lost revisions.

Sincerely,

SourceForge Support"

[Veracity]

Pain in the rear, I know, but Darzil - could you please resubmit your work?
I am eager to try it out.

Thanks.

[Darzil]

Just rebuilding my directories, then I'll diff them and transfer over, as just submit doesn't work, nor does revert or anything else.