Collectible Card Game Headquarters

Tentative target release date: Friday July 26.

My wife is having her foot surgery on the 18th and this might make it difficult for me to keep up the same pace over the next several weeks.

Tried to do a snapshot build and deploy this morning several times and they ended with a build failure. It looks like there may be a problem at cardforge. I can not predict if this will also affect tomorrow's beta release.
 

Code: Select all

[INFO] --- maven-install-plugin:2.4:install (default-install) @ forge ---
[INFO] Installing /Users/chrish/Workspace_SVN/ForgeSVN/target/forge-1.4.4-SNAPSHOT.jar to /Users/chrish/.m2/repository/forge/forge/1.4.4-SNAPSHOT/forge-1.4.4-SNAPSHOT.jar
[INFO] Installing /Users/chrish/Workspace_SVN/ForgeSVN/pom.xml to /Users/chrish/.m2/repository/forge/forge/1.4.4-SNAPSHOT/forge-1.4.4-SNAPSHOT.pom
[INFO] Installing /Users/chrish/Workspace_SVN/ForgeSVN/target/forge-1.4.4-SNAPSHOT.tar.bz2 to /Users/chrish/.m2/repository/forge/forge/1.4.4-SNAPSHOT/forge-1.4.4-SNAPSHOT.tar.bz2
[INFO]
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ forge ---
Downloading: ftp.cardforge.org/snapshots/forge/forge/1.4.4-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata forge:forge:1.4.4-SNAPSHOT/maven-metadata.xml from/to cardforge-snapshot-repo (ftp.cardforge.org/snapshots): Error transferring file via FTP
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11:16.908s
[INFO] Finished at: Thu Jul 25 10:58:02 EDT 2013
[INFO] Final Memory: 78M/591M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project forge: Failed to retrieve remote metadata forge:forge:1.4.4-SNAPSHOT/maven-metadata.xml: Could not transfer metadata forge:forge:1.4.4-SNAPSHOT/maven-metadata.xml from/to cardforge-snapshot-repo (ftp.cardforge.org/snapshots): Error transferring file via FTP: Operation timed out -> [Help 1]
[ERROR]

Tried to do a snapshot build and deploy just to see if the problem that was noticed yesterday was temporary. Go another build failure. I think that we might have a similar problem with the beta, but I am not sure.

Code: Select all

[INFO] --- maven-install-plugin:2.4:install (default-install) @ forge ---
[INFO] Installing /Users/chrish/Workspace_SVN/ForgeSVN/target/forge-1.4.4-SNAPSHOT.jar to /Users/chrish/.m2/repository/forge/forge/1.4.4-SNAPSHOT/forge-1.4.4-SNAPSHOT.jar
[INFO] Installing /Users/chrish/Workspace_SVN/ForgeSVN/pom.xml to /Users/chrish/.m2/repository/forge/forge/1.4.4-SNAPSHOT/forge-1.4.4-SNAPSHOT.pom
[INFO] Installing /Users/chrish/Workspace_SVN/ForgeSVN/target/forge-1.4.4-SNAPSHOT.tar.bz2 to /Users/chrish/.m2/repository/forge/forge/1.4.4-SNAPSHOT/forge-1.4.4-SNAPSHOT.tar.bz2
[INFO]
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ forge ---
Downloading: ftp.cardforge.org/snapshots/forge/forge/1.4.4-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata forge:forge:1.4.4-SNAPSHOT/maven-metadata.xml from/to cardforge-snapshot-repo (ftp.cardforge.org/snapshots): Error transferring file via FTP
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10:01.935s
[INFO] Finished at: Fri Jul 26 08:19:34 EDT 2013
[INFO] Final Memory: 78M/592M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project forge: Failed to retrieve remote metadata forge:forge:1.4.4-SNAPSHOT/maven-metadata.xml: Could not transfer metadata forge:forge:1.4.4-SNAPSHOT/maven-metadata.xml from/to cardforge-snapshot-repo (ftp.cardforge.org/snapshots): Error transferring file via FTP: Operation timed out -> [Help 1]
[ERROR]

Chris H. wrote:(ftp.cardforge.org/snapshots): Error transferring file via FTP: Operation timed out -> [Help 1]
[ERROR] [/code]

Maybe the ftp has filled up? Do we keep old snapshots that aren't releases? Maybe we should start cleaning any snapshots older than say.. 3 releases out?

We do keep all of the old snapshot builds. I sent off a pm to Rob.

I've been noticing that FTP access to the site has been flakey the past few days. I can login to FTP, but can't get a directory listing. I can login to the control panel, use their File Manager applet, and the rest of cardforge looks fine. I don't think it's an issue with how much data is stored.

I did delete a bunch of snapshots and releases from last year. I know some people may want older revisions, but how old is too old?

Looking into things, I'm seeing we're allegedly maxing the bandwidth.. not sure how. Temporarily, I renamed the fpics and releases folders to see if it's real traffic.

Update: It really seems to be related to picture requests. I know someone removed the delay between picture requests, but I think it is necessary. Either that, or some other devs need to step up with a mirror(s) to split the requests.

What about hosting the Forge LQ set and non-set downloads here at slightlymagic? Is that a possibility?

Thank you for the info Rob.

The user data including the pics were separated from the forge folder some time ago. This should have stopped people from re-downloading all of the pics with each update.

Has Forge become extremely popular recently or is some other site or project linking to cardforge for our pics rather than hosting their own copy?

Well there's definitely been a lot of new users posting bugs to the forums, so word has definitely been spreading. But leeching is a possibility too.

I tried to trace the four IP's I saw hammering away last night... One of them downloaded the main release first on July 9, then all the pics, then the release again last night, and all the pics. All the traffic has Java 1.7.xx as the http client, so it's likely Forge itself, not leeching..

It seems legit(ish) compared to how the site's been running for a while now... the delay was removed at least a few months ago right? I don't think the traffic is directly related, rather something is wrong with the hosting server. Just the same, I need to request that the delay be put back for this next release.

BTW, overall traffic has doubled since January, according to the webstats I was looking at while diagnosing the issue.

I've submitted a support request with the provider. I hope they overlook the questionable content and traffic, considering their fine-print-limited "unlimited storage and bandwidth".

If anyone wants to help with additional hosting, either themselves, or pitch-in through paypal, PM me. I have cardforge.org and cardforge.net, no reason .net can't live elsewhere.

I suspect that the delay was removed as part of the separate user data project but I could be wrong. Re-adding this delay sounds like a good idea.

I can hold off of any additional releases until someone re-adds the delay.

Would it be worth it to then remove all of the older releases from cardforge that did not contain the delay?

Chris H. wrote:I suspect that the delay was removed as part of the separate user data project but I could be wrong. Re-adding this delay sounds like a good idea.

I can hold off of any additional releases until someone re-adds the delay.

Would it be worth it to then remove all of the older releases from cardforge that did not contain the delay?

I don't believe that's when it was removed, I think Max just got rid of it one day, and I told him that Rob asked that to be in there specifically.

I don't think we should break historical archiving due to this however.

Do you know the subversion revision where the delay was removed?

Cheers,
Steve

I see it in r20423. Looks like he lowered the delay from .25 sec - .5 sec to .05 sec - .1 sec. It must have been removed sometime after that.

friarsol wrote:I see it in r20423. Looks like he lowered the delay from .25 sec - .5 sec to .05 sec - .1 sec. It must have been removed sometime after that.

Thanks. Does this look like the relevant segment of code?

Code: Select all

// GuiDownloader.java

            // throttle to reduce load on the server
            try {
                Thread.sleep(r.nextInt(50) + 50);
            } catch (final InterruptedException e) {
                Log.error("GuiDownloader", "Sleep Error", e);
            }


This is actually the current setting.

The previous settings were -

Code: Select all

r17149 Thread.sleep(r.nextInt(250) + 250);  // random delay between 0.25 sec and 0.5 sec
r11372 Thread.sleep(r.nextInt(750) + 420);  // random delay between 0.42 sec to 1.17 sec


This would obviously be simple enough to update but it would be useful to know why it was reduced in case there might be a lurking gotcha.

Cheers,
Steve