Code push soon

[mark]

I'm going to be doing a code push shortly as soon as I'm happy with the positioning of my ducks. (I don't need them to all have the same Y coordinates, but they should at least be near each other.)

This is a smaller push than most, there isn't a ton of stuff that's changed. There are a few major changes to how the importer works though, which is my area of most concern and where I'll be spending a lot of time watching.

As always, please comment and let me know if there are any issues. Thank you!

Update: Code pushed. There was some temporary slowness, our load balancer (Perlbal) got into a weird state where it was using 100% CPU. I restarted it and things returned to normal.

Update #2: There was an issue affecting status messages for community imports. This should be fixed now.

Comments

[blnktfrt]

Thanks for keeping us in the loop.

[shibes]

Thanks Mark :) Sounds good and thanks for letting us know ♥

[paian]

Thank you!

[turlough]

Good luck!!

[fannyfae]

Thank you, Mark! You guys are the best! :)

[radiophile]

Hmm, could one of the "major changes" be community imports...? :D *fingers crossed*

Thanks for the heads up!

[denise]

IT COULD BE

*shifty eyes*

[sergal]

Thanks guys! <3 Here's hoping it's all going to go through as smoothly as possible!

[autumnus]

good luck!

[glazedmacguffin]

I have a question about the potential for community imports.

Will they come through a lot like the comments do, with links to the original journals, or with a community name/icon? I don't see this as a problem at all because I'm delighted with the potential to back things up and glad for all the hard work you're doing. I'm just curious.

[denise]

They'll be imported the same way that comments are, as having been posted by the identity account of the original poster (so they can still log in and manage them with their LJ credentials).

[arliss]

I've not said before, but I just want to add my voice to the chorus of "thankyouthankyouthankyou" for being wonderful and responsive and proactive and all wonderful things. You and all the DW crew are appreciated more than you can possibly ever know.

[musyc]

♥♥♥♥♥

In the time it took between "see code push post on mobile device" and "get back inside to laptop, refresh reading page", the push went through. FAST! EFFICIENT! INFORMATIVE!

It's like a geekcoding superhero convention around here sometimes.

[cypher]

It's like a geekcoding superhero convention around here sometimes.

So much this. ^^

[fulminata]

Getting "Duplicate entry '613635-lj_verify-3' for key 1" error.

Information is accurate & I'm the only maintainer in the community.

[mark]

It looks like it has since gone through?

[kj_svala]

Thank you for the info!

[greyduck]

I'm at the point now where I've so many ducks I can't get them all in a row.

What I'm curious to try, however, is getting my ducks in a column...

[delight]

You're an exemplary duck manager, not having too high expectations for wild birds.

[mark]

I have a five week old baby at home. My expectations for most creatures at this point are:

a) Can you take in sustenance when it is put in your mouth?
b) Can you excrete the waste products when you're done?

If yes to both, then congratulations! You meet my standards.

[skorupi]

That just makes me squeal a little. ♥ Thanks for keeping us on the up-and-up!

[darjeeling]

Your code pushing skills are just ducky! :D

yes you may shoot me for that pun

This is AWESOME!!!

[ttmods]

Hiya Mark,

I set up the import for SWS, if you can delete/stop on your end if it's too load heavy, that's fine, just as long as I get an email failure notification :)

Also? The two TINY comms that I mod seem to be coming over just fine! **Does happy dance**

**Note: These were processed through my Seed account, if you need to know that specific account I can PM you :)

Re: This is AWESOME!!!

[mark]

Nope! I only need to know if there's a problem. Yeah, definitely look over the small comms you did and see how they look. Let me know of any problems.

We have a limit in right now that will bail if someone tries to import more than 100k comments. SWS will fail once it gets to the comment import -- but that's OK. You can go back later and re-schedule the comment import and they'll come over just fine.

[ex_tigre909]

Thank you for all your hard work!

[articletwelve]

I'm getting an error on importing comments on one community that has about 1,100, and another whose entries made it halfway before failing. Didn't get an error message on the entries, but I got two of these in my inbox:

"Failure running job: Undefined subroutine &LWP::Debug::debug called at /usr/share/perl5/LWPx/ParanoidAgent.pm line 377.

This was failure #4."

(I got two notifs, both said #4.)

Edit: Tried both the comments & entries again and got the same error for both, so I'll let them sit before retrying.

[denise]

In my experience that usually means LJ is freaking out and returning an error instead of the proper data feed that the importer uses, but I can't be 100% sure...

[green_knight]

100% CPU? I've had Firefox eating 190% of mine. Mind you, my computer thought it had 180GB of virtual memory the other day, which - on a 60GB hard drive - is quite an achievement. Maybe that's what's meant by 'cloud computing'?

Thanks for keeping us updated.

[azurelunatic]

The cloud is a magical place full of fairy dust and pixies.

[intermezzo]

You guys are amazing! ♥♥♥♥♥♥♥♥♥♥

[soc_puppet]

You can't see me (at least, I think you can't), but I'm totally dancing in my chair right now.

[denise]

Don't tell anybody, but I totally did too.

[kareila]

Will you update the hg tags as soon as the dust has settled?

[mark]

Yes, thank you for reminding me!

[ninetydegrees]

I don't know if this is normal considering traffic/load circumstances but the site is back to being pretty slow for me. Not as much as it was right after the push but really quite slow as compared to other sites/usual loading time. Just mentioning in case there's something else going on.

[mark]

Resolved! See http://dw-maintenance.dreamwidth.org/42076.html.