archive snowblossom slack dev
prev 2018-06-13 next
2018-06-13 00:20:04
GitHub
[snowblossomcoin/snowblossom] Issue closed by cluelessperson
2018-06-13 01:38:28
Fireduck
SIP2 - My cat is pretty and smells nice
2018-06-13 02:01:50
Clueless
`vote_yes=1,2`
2018-06-13 02:48:05
Fireduck
@Clueless I think I'll have MrPlow output a status report every few minutes.
2018-06-13 02:48:31
Fireduck
It'll have miner rates 1min, 5min, 1hr
2018-06-13 02:48:40
Fireduck
Pool rates Etc
2018-06-13 02:48:45
Clueless
That'd be great. For now I'm just regexing the log and reporting values.
2018-06-13 02:48:57
Fireduck
Yeah, that is suck
2018-06-13 02:49:03
Clueless
If you could also report a total number of connected miners that'd be cool too.
2018-06-13 02:49:28
Clueless
because I was just about to count up the unique addresses from the log
2018-06-13 02:49:38
Fireduck
sure
2018-06-13 02:50:45
Clueless
@Fireduck Let me number this properly. These are what I think we care about. 1. Total Rate. 2. Rate per miners/address 3. Number of addresses/miners 4. Announce when block is won
2018-06-13 02:50:55
Fireduck
roger
2018-06-13 02:50:57
Clueless
If those are logged, I think it'd be perfect. :D
2018-06-13 02:51:27
Clueless
I have the webpage on a simple cronjob that updates the index.html with latest hash rate. I can have output the winners
2018-06-13 03:10:17
Fireduck
rate reporting added to duckutil
2018-06-13 03:10:24
Fireduck
now I need to get this baby to sleep
2018-06-13 03:39:37
GitHub
[snowblossomcoin/snowblossom] Issue opened by tster123
2018-06-13 05:38:39
Tyler Boone
?
2018-06-13 05:38:43
Clueless
ah, I'm wrong
2018-06-13 05:38:55
Clueless
it's just a proof check fail
2018-06-13 05:39:04
Clueless
I thought it was the thing blocking
2018-06-13 06:03:49
GitHub
memfield_precache_gb=X this will move exactly X GB of the memfield into memory while using the rest from disk
2018-06-13 06:04:09
GitHub
[snowblossomcoin/snowblossom] #75 hybrid memfield
2018-06-13 06:57:35
Rotonen
@Fireduck if mrplow could flush a status.txt (or xml or json) periodically, that’d be neat
2018-06-13 09:24:27
Rotonen
a thought: voting blank?
2018-06-13 09:24:51
Rotonen
distinct from not voting
2018-06-13 13:46:43
Clueless
@Rotonen What is voting blank?
2018-06-13 17:18:16
Fireduck
@Clueless run that code with report_path set to something
2018-06-13 17:18:23
Fireduck
and it will make you a sweet hash rate report
2018-06-13 17:18:58
Fireduck
$ cat pool_report.txt Total: 1-min: 69.9K/s, 5-min: 14.0K/s, hour: 1.2K/s snowtest:emcpfwr7m5u6zmg3n4wmnz3lf4lz9h5ecarth54a 1-min: 69.9K/s, 5-min: 14.0K/s, hour: 1.2K/s
2018-06-13 18:57:00
Rotonen
@Fireduck very nice - for when are you planning next release?
2018-06-13 20:07:04
Fireduck
don't have a specific plan
2018-06-13 20:07:27
Fireduck
most of the code changes have been to peer service which I imagine people are running from master branch
2018-06-13 20:40:43
Clueless
is there a method to tally votes yet by explorer yet?
2018-06-13 20:40:50
Clueless
will setup his own explorer
2018-06-13 20:44:56
Tyler Boone
I started looking at that last night
2018-06-13 20:45:26
Tyler Boone
ended up spending 2 hours figuring out why my local shackleton was throwing away every other request
2018-06-13 21:44:43
GitHub
If the binary name matches a directory name (case-insenstive) there is a build error: * * * protolib/protolib.pb_java.jar protolib/protolib.pb.descriptor_set * * * INFO: Analysed 9 targets (0 packages loaded). INFO: Found 9 targets... ERROR: /Users/jgleason/t/snowblossom.git/BUILD:38:1: Creating runfiles tree bazel-out/darwin-fastbuild/bin/Shackleton.runfiles failed (Exit 1) _bin/build-runfiles (args bazel-out/darwin-fastbuild/bin/Shackleton.runfiles_manifest bazel-out/darwin-fastbuild/bin/Shackleton.runfiles): mkdir '*main*/shackleton': File exists [17] INFO: Elapsed time: 0.568s, Critical Path: 0.36s INFO: 1 process, worker. FAILED: Build did NOT complete successfully A work around of changing: java_binary( name = "Shackleton", to java_binary( name = "ShackletonS", Made the build succeed. So something about a directory shackleton already existing. Not sure if that is because of the class of that name or the source directory or what. Not sure what to do about it either. Maybe if we make the binary ShackletonExplorer.
2018-06-13 22:14:48
Rotonen
i’ll need to bother figuring out flushing stats to a nicer looking site with a static site generator eventually, but gonna roll with actual releases - i might be old fashioned
2018-06-13 22:25:16
Tyler Boone
I think we should make a handful of minor improvements and then roll out a simple quality of life update
2018-06-13 22:38:58
Rotonen
sounds fair
2018-06-13 22:39:51
Rotonen
less repetitive logging would be one of those for me
2018-06-13 23:11:06
Clueless
@Fireduck @Tyler Boone Do you think it would be good to setup an automatic release schedule?
2018-06-13 23:11:31
Clueless
Create a policy that it doesn't go into the release unless it's dire or has a week of testing?
2018-06-13 23:12:07
Clueless
I can setup test machines to build nightly to test changes. We monitor them for errors in logs, block height, etc.
2018-06-13 23:12:32
Clueless
and I can setup a test-production, one that immediately builds new releases and runs them
2018-06-13 23:12:34
Clueless
same purpose
2018-06-13 23:12:48
Rotonen
@Clueless as far as i can see it's 2 devs, a few enthusiasts - no need for red tape
2018-06-13 23:13:10
Clueless
agreed.
2018-06-13 23:13:13
Rotonen
building systems is enjoyable, but not the purpose itself
2018-06-13 23:13:31
Rotonen
wrong hammer, and with enjoyable hammers everything looks like a nail, etc.
2018-06-13 23:14:06
Clueless
@Rotonen Another thought is that I can setup a node that automatically rebuilds **every commit* so we can more readily test changes.
2018-06-13 23:14:23
Rotonen
rather set up integration testing via travis
2018-06-13 23:16:47
Rotonen
i suppose step 1 would be 'will it still build', namely i still cannot build shackleton
2018-06-13 23:17:46
Rotonen
also the build is a bit noisy on a modern clang on macos, but nothing critical in the way of warnings, but i could look at rigging scan-build for the c++ bits
2018-06-13 23:18:09
Clueless
no idea what you're saying.
2018-06-13 23:18:36
Clueless
I'd just automate away building constantly, and if it errors, alerts us so we can check the log and fix it
2018-06-13 23:18:57
Fireduck
There is an issue for Shackleton. Case sensitive issue
2018-06-13 23:19:00
Rotonen
yeah, just use travis and/or appveyor for stuff like that, straight up github integrations and free for open source
2018-06-13 23:19:06
Fireduck
Opened today
2018-06-13 23:19:30
Rotonen
https://clang-analyzer.llvm.org/scan-build.html <- also scan-build is just about my all-time favourite toy, so i'll try jamming that about anywhere i touch
2018-06-13 23:21:46
Tyler Boone
IMO, automatic builds and releases are time savers, but setting them up is work
2018-06-13 23:23:02
Rotonen
a simple build + smoke test via travis should not be that hard to pull off
2018-06-13 23:23:19
Rotonen
elegance can follow over time
2018-06-13 23:23:43
Clueless
@Fireduck The reporting is niceeee.
2018-06-13 23:24:06
Fireduck
We have some solid integration tests already
2018-06-13 23:24:07
Clueless
@Rotonen I'll look into travis. :I I'm not averse, just ignorant.
2018-06-13 23:24:14
Fireduck
Just need more of then
2018-06-13 23:24:18
Fireduck
Them
2018-06-13 23:24:32
Rotonen
@Fireduck how do you run the tests?
2018-06-13 23:24:49
Tyler Boone
bazel test //...
2018-06-13 23:24:57
Rotonen
thank you
2018-06-13 23:25:57
Rotonen
and that seems to build :all as well, so i cannot run those, as shackleton craps up, but that'll eventually settle
2018-06-13 23:26:02
Rotonen
but neat
2018-06-13 23:26:39
Tyler Boone
shackleton is broked?
2018-06-13 23:26:59
Rotonen
@Fireduck hinted it'd be some case sensitivity issue and that'd make sense as i'm on APFS
2018-06-13 23:27:00
Fireduck
Read the issue
2018-06-13 23:27:04
Tyler Boone
but yeah, test obviously requires build :wink:
2018-06-13 23:27:07
Rotonen
and some devs are on NTFS
2018-06-13 23:27:18
Tyler Boone
whoops
2018-06-13 23:28:34
Rotonen
earlier there was also a classic git defaults vs. line endings issue
2018-06-13 23:32:45
Rotonen
trying to figure out bazel: is there an easy way to build all the deploy targets at once, like some built-in meta tag, or would that have to be defined in the BUILD file?
2018-06-13 23:33:15
Fireduck
Not sure
2018-06-13 23:39:10
Clueless
@Rotonen Can you confirm discord user: Rotonen#7301 is you?
2018-06-13 23:39:40
Rotonen
@Clueless yeah, why?
2018-06-13 23:42:10
Clueless
@Rotonen figured I'd make you mod.
2018-06-13 23:42:39
Rotonen
so long as you do not expect me to actually put forth any moderation effort
2018-06-13 23:43:14
Clueless
No expectation. Just seem reasonable and not powermad
2018-06-13 23:44:29
Clueless
@Fireduck Perhaps a nonsense question. Would it ever be possible to point snowblossom processing at research data? curious (and maybe dumb)
2018-06-13 23:45:01
Rotonen
boinc already exists and they're good at that
2018-06-13 23:46:10
Clueless
My thinking is that then the data fields are self-generating, have no limit, it would shut idiots up about power usage, and it would buy us "helping mankind" votes.
2018-06-13 23:49:23
Fireduck
Snowblossom would not be useful for anything
2018-06-13 23:55:26
Clueless
I figured it was probably a stupid premise