[Converge] mdb_v8 Related Commits

[jasnell]

There are several mdb_v8 Related Commits

• 878c40e1b3762a5f3ed48094f954fbee705f69ff mdb_v8: fix symbols not loaded properly - nodejs/node-v0.x-archive@878c40e
• ebfa7e350aed8f61b68a290be2e8fefca9db939e mdb_v8: add tests for ::findjsobjects -k KIND - nodejs/node-v0.x-archive@ebfa7e3
• 4312f8d760bdf574b5a461e426331f0b4d298f18 mdb_v8: update for v0.12 - nodejs/node-v0.x-archive@4312f8d

[bnoordhuis]

Looks alright to me but the V8 changes in the last commit should be upstreamed first.

[Fishrock123]

Some extra discussion / context between myself and @misterdjules on irc about mdb: http://logs.libuv.org/io.js/2015-05-22#17:49:38.409

[misterdjules]

FWIW, here's the issue that was used to track upstreaming the V8 changes in the last commit: nodejs/node-v0.x-archive#9147.

[Fishrock123]

@misterdjules was that ever upstreamed in the end?

[misterdjules]

@Fishrock123 It hasn't been upstreamed yet.

[jasnell]

@misterdjules ... is there a timeline for getting those upstreamed?

[misterdjules]

@jasnell There is no timeline. If it needs to be done quickly, please bump the priority in nodejs/node-v0.x-archive#9147.

[Fishrock123]

Please bump it. I think this is a converge blocker.

[Fishrock123]

Can we expedite this a bit? Is there anyone else who is familiar with mdb other than @misterdjules?

cc @nodejs/tsc If theres a point we'll fall behind for a converged release I think this is it.

[rvagg]

/cc @jclulow @davepacheco - halp? As @Fishrock123 points out above, this is a convergence blocker, can we have some Joyent eyes here?

[Fishrock123]

Also maybe cc @Raynos because I know he uses mdb a lot with node.

[misterdjules]

I can work on upstreaming the V8 changes soon, but not today.

Also, what is blocking exactly?

[Fishrock123]

@misterdjules two things:

1. Any changes to v8 in io.js/converged must be upstreamed prior to floating them. (General policy)
2. Someone with knowledge of it has to actually update the biding for io.js/converged, I think?