Fix undeclared statusCode variable

[NameFILIP]

statusCode on the line 173 is an undeclared variable. It crashes the node server.

[jeking3]

Could you please amend your commit message to begin with the Jira ticket ID, for example:

THRIFT-3926: fix undeclared statusCode variable
Client: nodejs

[jeking3]

I used the github squash and merge tool to fix the commit message to conform to project requirements. Thanks.

[NameFILIP]

Thank you @jeking3!

[NameFILIP]

How often do you guys publish new versions? Is there a chance to have it in the npm sometimes soon?

[jeking3]

Language-specific distribution is spotty. For example I do perl cpan updates myself. It looks like we regularly publish; I'm not sure when we're going to start the 0.12.0 release cycle but I know we want more frequent releases than we've done in the past.

[NameFILIP]

Any updates on the 0.12.0 release? We'd like to move away from referencing a specific commit to using an official version. Anything I can help with?

[jeking3]

@NameFILIP looks like we dropped the ball this year again, but thank you for being persistent here, because it's needed.

@jfarrell we need a long term solution to getting multiple releases out the door yearly. We should be able to release quarterly with automation or at least twice yearly even with a manual process. cc: @jensg - I think this can be done entirely through CI automation by leveraging a branch with a release/ prefix which kicks off different jobs, including automation of the build numbers across all the languages package descriptions, and eventually a job that can build and publish to package managers automatically.

With @allengeorge working on exorcising the build demons in cl and d so that our CI build can be more stable (I'm regularly re-kicking individual jobs to work around known issues), I can work on release automation. I'll look through the backlog to see if there is an entry for this, and if not I will add it.

[lxe]

Thanks for the follow up @allengeorge! Do the language framework releases have to be atomic? For example node patches can go out and get published to npm at a much more frequent cadence when such patch releases are necessary.

[vicapow]

Hello. Also running into this in an issue of ours. Any chance we could get a new release kicked off?

All the best,
Victor

[jeking3]

@lxe to date the project has only made monolithic releases. I understand the importance of having language-specific patches however, and after the 0.12.0 release we'll look into doing that.