PMXBOT Log file Viewer

Help | Karma | Search:

#mongodb logs for Saturday the 16th of January, 2016

(Back to #mongodb overview) (Back to channel listing) (Animate logs)
[00:30:29] <morf> hi guys
[00:30:53] <morf> any tip for mongodb client ui ... something simple, basically just something that can render collections to tables
[00:30:56] <morf> platform linux
[00:31:02] <morf> no web scripts
[00:37:11] <Boomtime> https://www.mongodb.com/products/compass
[00:38:52] <Boomtime> @morf: although ->"render collections to tables" -> you know that's impossible right? documents are schemaless by default - the only table column that is assured to exist is _id, every other column might be unique per document
[00:39:52] <morf> Boomtime: well i'm not storing random data they are pretty much the same like in traditional sql dbs
[00:43:25] <shlant> hi all. can I safely ignore "The server certificate does not match the host name x" messages if I have —sslAllowInvalidHostnames set for my replica?
[00:48:04] <morf> shlant: that's for you to decide, if you know the certificate is valid and right, just for different hostname, you can imho safely ignore it
[00:48:23] <Boomtime> @morf: unfortunately, any tool which assumes your condition, wouldn't work in the general case
[00:48:35] <Boomtime> with that said, you will find some suggestions around
[00:49:11] <Boomtime> have you looked through this list? -> https://docs.mongodb.org/ecosystem/tools/administration-interfaces/#data-viewers
[00:50:15] <Boomtime> @shlant: that message is effectively telling you a man-in-the-middle attack might be going on - you are explicitly telling it you don't care - do you care?
[00:51:23] <Boomtime> crypto on the wire is not entirely useless anyway, since it will certainly stop eavedroppers and capturing after-the-fact, but your configuration won't stop more sophisticated attacks like man-in-the-middle
[00:52:16] <Boomtime> the trouble is, if you sufficiently trust your network enough to believe man-in-the-middle is not possible, then why are you using SSL?
[00:52:19] <shlant> morf: that's what I thought. As long as it's not rejecting connnections or something because of it
[00:54:13] <morf> Boomtime: yeah i get it ... i just want something that doesn't exist yet again :)
[00:56:23] <Boomtime> right, then you're all good, the options you chose reduce what would be an error, to a warning, and the connection is accepted (with regrets)
[02:51:11] <shlant> Boomtime: that's a good question. It's partly because the related app is being used to advertise the importance of privacy and partly because setting up ssl using existing certs isn't a big deal, but setting up a whole certificate issuing service will be a PITA
[03:38:15] <Boomtime> @shlant: yep, i understand - so long as you are aware of the shortfalls in security you can work towards improving it
[03:42:23] <shlant> Boomtime: for sure. Thanks for looking out :)
[11:00:19] <ondreian> anyone ever came across an error like this: MongoError: BSONObj size: -1859549040 (0x90882991) is invalid. Size must be between 0 and 16793600(16MB) First element: ?`@: ?type=-124
[15:14:13] <metame> ondreian: not sure what your query looks like that's causing the error but this might help: http://stackoverflow.com/questions/22213777/exception-bsonobj-size-286331154-0xeeeeeeee-is-invalid-size-must-be-betwee
[15:49:44] <glowdemon1> I'm trying out something like Twitter and I need to store statuses. Whenever I place a status on a webpage, it needs to show the status and the number of the status. The number needs to be an incremented ID to keep count of statuses. How would I accomplish this?
[15:50:11] <glowdemon1> Because I've read that incremented IDs are a no-go in Mongo, perhaps there are other alternatives.
[15:56:06] <metame> glowdemon1: instead of overriding the _id you can just add another field like status_id to your doc
[16:02:24] <metame> glowdemon1: to implement it with consistency you can follow the docs: https://docs.mongodb.org/manual/tutorial/create-an-auto-incrementing-field/
[16:03:42] <metame> glowdemon1: really depends on scale but using an auto-increment pattern with something as (potentially) numerous as statuses may hurt perf
[17:39:46] <diegoaguilar> Hello where can I get a compiled linux version of mongosniff
[17:56:54] <diegoaguilar> Hello, can someone please give an eye to this
[17:56:54] <diegoaguilar> http://stackoverflow.com/questions/34830136/why-would-a-mongoose-query-return-no-results-while-it-does-at-mongo-cli
[18:31:01] <majora> I'm having a bit of a problem using mongoose in node trying to get it to populate an array of Schema Objects
[18:33:07] <majora> here is the code I'm using <http://pastie.org/10692085>
[18:40:32] <majora> oh, I fixed it
[18:44:28] <Desetude> Hey all
[18:44:43] <Desetude> Anyone here able to help with the Java Driver's decoding?
[19:29:12] <cheeser> doh! just missed her.
[20:15:57] <StephenLynx> if my index is {a:1} and I have a sort {a:1,b:1} will the index be used to help the sorting?
[21:06:30] <benoitc> hi
[21:06:51] <benoitc> is there any doc about the storage engine api ?
[21:06:57] <benoitc> I can't find it right now
[21:07:38] <ChALkeR> StephenLynx: Hi again. So, what made you think that I'm using mongoose yesterday?
[21:07:55] <ChALkeR> > <StephenLynx> ChALkeR you should stop using mongoose./
[21:07:58] <ChALkeR> I don't.
[21:08:51] <StephenLynx> <ChALkeR> Anyone using mongoose here? You should update.
[21:09:20] <ChALkeR> StephenLynx: Yes. They should update.
[21:09:36] <StephenLynx> update implies update mongoose version, not stop using it.
[21:09:36] <ChALkeR> What made you think that _I_ am using it?
[21:09:54] <StephenLynx> because I assumed you learned of some issue on some version.
[21:10:09] <ChALkeR> You said to me that I should stop using it.
[21:10:23] <StephenLynx> why would you care about versions of it if you doesn`t use it?
[21:10:41] <ChALkeR> bc i found a bug in it
[21:10:46] <StephenLynx> so you use it?
[21:10:49] <ChALkeR> No.
[21:10:54] <ChALkeR> What makes you think so?
[21:10:58] <StephenLynx> so you just woke up
[21:11:02] <StephenLynx> and decided to look for a bug
[21:11:07] <StephenLynx> on a thing you doesn`t use?
[21:11:31] <ChALkeR> I have current versions of all the npm packages downloaded.
[21:11:47] <ChALkeR> (well, a bit out of date actually, but still)
[21:12:02] <StephenLynx> you have all npm packages downloaded? the whole database?
[21:12:18] <ChALkeR> Only the latest versions.
[21:12:23] <StephenLynx> of all packages?
[21:12:26] <ChALkeR> Yes.
[21:12:28] <ChALkeR> Why shouldn't I?
[21:12:35] <StephenLynx> even the dumb wrappers?
[21:12:39] <StephenLynx> for useless crap?
[21:12:50] <ChALkeR> e.g.?
[21:13:04] <StephenLynx> you got over 100k packages from npm installed?
[21:13:15] <StephenLynx> and you keep checking for new versions of ALL of them?
[21:13:16] <ChALkeR> Downloaded and unpacked (except one).
[21:13:22] <ChALkeR> Not installed.
[21:13:51] <StephenLynx> but you got one hundred thousand packages downloaded and you watch for new versions on them?
[21:13:53] <ChALkeR> I do not run that in real-time, so my versions are a bit out of date.
[21:13:57] <ChALkeR> Yes.
[21:14:00] <ChALkeR> Why shouldn't I?
[21:14:04] <StephenLynx> jesus christ
[21:14:26] <StephenLynx> for the same reason you don`t buy one item from the super market of every product they have
[21:15:26] <ChALkeR> I don't get the metaphor.
[21:17:30] <ChALkeR> StephenLynx: Btw, this is the bug that I'm talking about: https://github.com/Automattic/mongoose/issues/3764
[21:25:50] <StephenLynx> lol mongoose
[21:30:18] <ChALkeR> check out the poc: https://github.com/Automattic/mongoose/issues/3764#issuecomment-172078278
[21:30:36] <StephenLynx> >Ahem. Just what? I reported this privately for a reason.
[21:30:38] <StephenLynx> so you don`t use it
[21:30:39] <ChALkeR> so, everyone using mongoose should update
[21:30:43] <StephenLynx> but you keep checking for bugs
[21:30:48] <StephenLynx> on 100k npm modules?
[21:31:02] <StephenLynx> everyone using mongoose should stop using mongoose.
[21:31:13] <ChALkeR> No, i report only a few of those.
[21:31:25] <StephenLynx> but you keep checking all those modules for bugs?
[21:31:26] <ChALkeR> But when I see an issue, why not report it?
[21:31:35] <StephenLynx> even on modules you don`t use?
[21:31:36] <ChALkeR> especially if the package is widely used
[21:31:47] <StephenLynx> so you would bug check PHP all day long?
[21:31:55] <ChALkeR> why?
[21:31:58] <StephenLynx> I am pretty sure it is also widely used.
[21:32:35] <ChALkeR> if I would somehow find a bug in php that is worth my time, I will report it
[21:32:44] <ChALkeR> Why not?
[21:32:54] <StephenLynx> how would you find a bug on something you don`t use?
[21:33:21] <ChALkeR> I was searching for inaccurate Buffer usage in npm modules.
[21:35:10] <ChALkeR> I think that Node.js Buffer API should be changed, and did a quick research on what different people do with it.
[21:35:15] <ChALkeR> I am using Node.js.
[21:35:31] <ChALkeR> StephenLynx: Does that make sense to you?
[22:15:05] <atomicb0mb> How can I query only documents where they key "foo" exists?
[22:16:52] <atomicb0mb> hello ?!
[22:16:54] <atomicb0mb> nobody knows that?
[22:25:58] <cheeser> $exists