438200+ entries in 0.297s
trinque: ^imo a news site being ddosed ought
to be a matter of pride
mod6: i'm gonna need another box
to
test on anyway.
mod6: one other
thing I gotta do is update
the gentoo-uclibc guide
to a new guide for nomultilib glibc, should be fairly easy.
then
test it on my pos box.
mod6: thanks for your offer
to help
trinque!
mod6: or something like
that perhaps
mod6: yeah,
there would just be: Scenario: Create static bitcoind via buildroot,
tfpt (or whatever??)
to device, begin full sync
mod6: personally, i'm pretty clueless with
the whole
thing as of now.
mod6: yeah, i
think
there will be some further discussion around
that. maybe dbp can help head up
that side of
the
testing if he's willing (other
than alf) he's probably got
the most exp with
the
thing.
trinque: what's called for
there? push-button rebuild and deploy of
turdel with a newly built bitcoind?
trinque: been wanting
to make my pogo do something
trinque: hm, maybe I can help with
that one
then
trinque: I've gone
through it once, got
the
turdel served up over
telnet
mod6: but people could certainly and appreciatedly
take
this
task on for
themselfs.
mod6: i don't/haven't ever setup
the buildroot stuff.
mod6: i
think
the arm/pogo stuff is going
to be have
to be
tested separately perhaps.
mod6: We'll be on
the R.C. until we're satisfied everything is
the way we want it.
trinque: mod6: I've got an opteron box, pogo, i7, obsd i386, off
the
top of my head
decimation: I'm going
to
try
to get
the macports version
mod6: cool!
thanks. yeah, we're gonna need as much help as we can get
testing. and as soon as we have a solid
test plan developed,
then we'll cut a release candidate for
testing.
decimation: I
tried
to get stator working on osx 10.6.8 (32-bit macbook1,1)
trinque: nice, I am happy
to help with
that process
mod6: im workin on
that
test matrix now.
mod6: my obsd 5.6 full sync is up
to block: 189480
decimation: nearly everyone does drug
testing here
decimation: I've heard
that
this is a common problem in
the us
jurov: and poppy seed is not addictive, just
tasty
jurov: and its brother makovník, best stuffed by so much poppy seed
that it makes you very sleepy
☟︎ decimation: there was a baker who makes potica at
the farmer's market
this morning
ben_vulpes: punkman: i live and die by
the dvcs, i like it just fine. mod6 hates it for some reason
that's unclear
to me, so i'm allowing for
the possibility
that i just have stockholm syndrome.
ben_vulpes: i like it
too, but it's probably git stockholm.
mod6: i dunno, i guess im just used
to
the other way.
punkman: I kinda like
that it includes
the function name
mod6: i want
to make it clear
that it seems /slightly less readable/
to me because of: @@ -45,24 +45,6 @@ Object JSONRPCError(int code, const string& message) <<
this
type of
thing.
mod6: i dunno yet. i haven't
tried
the new one.
mod6: normally diff will put
the flags passed
to it into
the patch file.
mod6: <+punkman> mod6, what's missing from git output? << if you used -pU, it doesn't reflect
that in
the patch
mod6: ben_vulpes:
the old one did not, because of perhaps something
the ML did
to
the patch; stripping out an empty line at
the end of
the file.
ben_vulpes: mod6: does
the patch not apply cleanly?
mod6: and
then do a `diff -uNr`
mod6: anyway, i'll have
to just repatch up everything myself and re-add your changes.
ben_vulpes: so yeah a patch
to excise
the wx crap is great and wonderful and
thank you etc, but i'd like
to see it split from changes
to logging behavior
mod6: <+punkman> (I did -pU, didn't change anything) << ah ok. git must have stripped
that helpful information from
the patch. fuck git.
ben_vulpes: i
think i missed
the debug sanity feedback
threads
too.
punkman: and
there's also PrintException, PrintExceptionContinue, error() and more
punkman: also if you grep for "fprintf(stdout/stderr" you can find some
that never go
to debug log
punkman: which decides whether
to write
to debug file or print
to console
ben_vulpes: how does returning an error from a function in bitcoin
turn into a line in debug.log?
punkman: mod6, -U is
the default, not sure how
to
turn
the comments after @@
mod6: does stuff like
this:
mod6: doesnt look like
that one was generated with -pU either
though.
mod6: i'm gonna
throw in debug_sanity-part1-corrected
to my next build/sync
test, and look at
the output/impact of
the patch. i should have some more meaningful comments after
that.
ben_vulpes: <punkman> I'd really like
the debug.log
to be parseable,
that's
the main motivation here <<
this is an excellent goal. a+ if you crap out an EBNF
to go along with it, instead of some "protocol is in
the code" parser script.
☟︎ ben_vulpes: gotta love
these rubyists, centralizing all of
the decentralized
things. shithub, keybase...
ben_vulpes: <shinohai> I shamefully decided yo put all my crap in a github repo.
There is no better way right now for me
to organize it all. << you know
that you can have a git repo on disk without ever pushing it
to shithub?
mod6: that needed
to happen at somepoint.
punkman: main attraction is removing
the wx crap
ben_vulpes: <punkman> mod6, debug_sanity perhaps? << i've yet
to play around with
this one in depth
ben_vulpes: ;;later
tell pete_dushenski find someone who's a shareholder,
they can do
test drives
punkman: I
thought of incorporating milli
timestamps as an option in part2
mod6: phf: keep an eye out for punkman's debug_sanity-part2 -- or maybe you both can coordinate
together so
that all
three of
these patches will play
together nicely: debug_sanity-part1-corrected, debug_sanity-part2 and milli
timestamps
mod6: I
think it's great. If you've got an idea or something you wanna discuss for submission,
this is where
that
type of discussion happens. Keep it up! :]
mod6: Anyway, most of
the submissions so far have been pretty
top notch. We want
to encourage people in
the WoT
to submit patches. If something is submitted but doesn't make it into a release right away,
that certainly doesn't mean it won't be pulled in
to a later milestone.
☟︎ mod6: for anything
to make it into
the next release,
the patch must be 100% perfect and apply perfect. if I hvae
to do any mental gymnastics or gyrations
to apply a patch or whatever, it wont make it in.
there's already a large enough scope on
this release.
mod6: make something work for you on your end, see if it makes sense, and if it does, perhaps submit
the changes.
punkman: I'd really like
the debug.log
to be parseable,
that's
the main motivation here
punkman: mod6: any wishes on
that front?
shinohai: I shamefully decided yo put all my crap in a github repo.
There is no better way right now for me
to organize it all.
☟︎ punkman: I'm gonna do debug_sanity part2
too
mod6: same as any of
the others: dump/eat block, verifiy all etc.
mod6: especially if anyone is helping
test or whatever and
they need debug_sanity
they can just apply
the patch
to
their local codebase.
mod6: punkman has his debug_sanity, but I hvane't had a chance
to
test version
two, and it's not a super high priority for me at
this very moment.
shinohai: ok,
then
that is just 2, and
testnet isn't important
☟︎ mod6: not a huge deal. nothing super critical
there, just nice-to-have
type of ones.
mod6: ascii only has 3 patches post blockdump (eatblock, rm
testnet, verifyall)
mod6: Haven't had enough spare
time
to dig into it. Been hectic enough just
trying
to keep up with all
the incoming patches.
mod6: <+punkman> did anyone
try musl yet? << yeah, check out ascii's comments from yesterday
mod6: One of my goals for
this week (and I'm running a bit behind) was
to create a
test matrix for everything
that needs
to be
tested for
this forthcoming release. I hope
to at least get a start on
that here
today yet.
mod6: As far as
testing, so far everything seems
to be working ok -- i've fully sync'd 1 stator build, and i've got 2 more full sync's running curretly: one gentoo x86-64 w/glibc & one OpenBSD x86-64 w/glibc
mod6: <+mircea_popescu> mod6 so what's
the plan,
turning stator into a release ? << Yeah. I believe 'stator' + { eat/dump block, rm
testnet & verifyall } should be
the 5.4 release unless anything additional is submitted before we can finish
testing & bundling release.
☟︎☟︎ mircea_popescu: mod6 so what's
the plan,
turning stator into a release ?
shinohai: For say 5 BTC
then yeah, I'd
turn down
the lights and plow
that.
shinohai: think of
them as hot girls with snipped dinglies.
shinohai: Nothing
to
top off
the weekend like a relaxing prostate massage.
shinohai: @ cazalla "not some weird ass pegging shit" <
Traps perhaps?
jurov: dude was not very keen on bj's, went straight for
the ass