hi there, folks:
I'd really like to release 0.7.0 but I would like it to be at least a
little bit tested before I do so. Could those of you with CVS trees check
everything out and see if it performs as advertised? Deeper bugs than
that will have to wait for the next release, but I'd at least like to know
if it works for someone other than me.
______ __ __ _____ _ _
| ____ | \_/ |_____] |_____|
|_____| |_____ | | | |
@ t w i s t e d m a t r i x . c o m
Are there any major disadvantages of using pymongo with callInThread
instead of txmongo? I'd like to take advantage of some newer features in
pymongo (unfortunately not available in txmongo) and it's certainly easier
to maintain feature parity using callInThread.
Is anyone using the silverberg CQL (Cassandra) library for Twisted in
production? Just curious what people's experience with it is, since it
appears to be the most recently updated Twisted/CQL project.
I have a twisted TCP server to listens to client, processes requests, do
mysql database operations if needed (using adbapi Connection pool) and
return the result. Before deploying this in production, I want to know
right way to configure the server.
Since twisted is single threaded, how can I leverage multiple cores of my
production machine (which has 6 cores and 16 GB RAM) ?
One approach that I thought of was to start multiple instances of twisted
server on different ports. This would help in using the other cores as
well. What do you guys suggest ?
As commented by @glyph
Since we've added the buildbot link to trac pages, force-builds.py is
basically obsolete. I think we should just scrub all mentions of it,
and probably delete it.
I have created a ticket to remove it and clean documentation:
Is there anyone else still using this tool?
Should we keep it and rather than removing it, improve its documentation?
To help with the review process I would like to ask permissions for
triggering buildbot builds.
Is there a wiki page describing what are the steps required for a regular
contributor to get permissions to run buildbot tests and get write access
to the repo?
In the same time, maybe we can write a few words about the steps required
for a new contributor to become a full reviewer. Ex.
1. Contribute a few patches (ex 10) and learn the basic review process.
Observe how reviewers respond to your patch.
2. Start doing review as junior reviewer, without merging. Once you are ok
with the patch, invite another core developer to take a final view and
merge the patch
3. Once you have reviewed a few patches without errors (ex 10) you can ask
for full review permission or a core developer will let you know that you
can merge the patch without asking someone else.
This can be part of the current review process page:
What do you think?
Is not much, but should provide some guidance and hope!
Are you guys aware of anything which solves the same kind of problem as
t.s.pb but in js? I asked about this on the js stack exchange chat room and
the general response was that there's isn't anything. I figured y'all might