I'm confused

does original project permissions allow you to edit my fork permissions? lel

no idea

no problem, just surprising

@snowmonster has joined the channel

@Fireduck I just realized. windows uses leading /forward slash for arguments.

You can set paths with \\ I believe in windows

Also note, windows `start` command allows `start /NODE <NUMA NODE>`

*https://github.com/snowblossomcoin/snowblossom/compare/2069236abe7d...44bdca894b83* https://github.com/snowblossomcoin/snowblossom/commit/44bdca894b8359b9c5d95c9a3a60704c35c97cec - batch windows line endings, send prompt batch file

*https://github.com/snowblossomcoin/snowblossom/compare/44bdca894b83...4cbb43bb02f0* https://github.com/snowblossomcoin/snowblossom/commit/4cbb43bb02f059f17828d5b2840ee5356d0834d6 - need that

apparently git won't allow you to commit empty folders

Put an erotic readme in

*https://github.com/snowblossomcoin/snowblossom/compare/4cbb43bb02f0...15ecd8a545ea* https://github.com/snowblossomcoin/snowblossom/commit/15ecd8a545ea0a53d3a71eff49d7a01d422351d1 - batch windows line endings, send prompt batch file

Squashed my 3 commits to 1

git doesn't understand folders

*https://github.com/snowblossomcoin/snowblossom/compare/15ecd8a545ea...59be32909327* https://github.com/snowblossomcoin/snowblossom/commit/59be32909327de1b9382f0c3e5652c6389d719ef - batch windows line endings, send prompt batch file

Miner should exit on java heap exception while reading in precache. A retry is unlikely to help.

[snowblossomcoin/snowblossom] Issue opened by tster123

People complain it is too noisy

Then they want to know what snowfield we are on

well, yup

@Fireduck, is this expected: INFO snowblossom.miner.PoolMiner$MinerThread submitWork Work submit: error_message: "snowblossom.lib.ValidationException: POW Pass index does not match 3701091392 660822336 4294967296"

No that is bad

Something ignoring the return false on readword?

Probably my fault

well, that is with my change too...

but submitWork does ignore it...

it should never be false there though

should add an assertion or warning there maybe

yeah

if it were false, the buffer wouldn't be filled and I'd expect strange errors

which is what happens

oh, looks like I have a bug maybe

heh

when falling back to disk, I was passing in current depth 0, and I need to pass in current depth Globals.POW_LOOK_PASSES

*https://github.com/snowblossomcoin/snowblossom/compare/59be32909327...af78f4111cf5* https://github.com/snowblossomcoin/snowblossom/commit/af78f4111cf5767fd644ed9969f549df85d117a9 - Adding clueless seed hosts

*https://github.com/snowblossomcoin/snowblossom/compare/af78f4111cf5...13714b261d6b* https://github.com/snowblossomcoin/snowblossom/commit/13714b261d6b63dd19901020b4f0abbd43922dae - Nonsense wallet test

*https://github.com/snowblossomcoin/snowblossom/compare/13714b261d6b...6d760348ff0c* https://github.com/snowblossomcoin/snowblossom/commit/6d760348ff0cfc370cebf6398780badf7d365f5e - Release 1.0.8

*https://github.com/snowblossomcoin/snowblossom/compare/6d760348ff0c...7c780c258cc0* https://github.com/snowblossomcoin/snowblossom/commit/7c780c258cc0fe9926a8ffb57aed25b731cae8ff - dev

[snowblossomcoin/snowblossom] Release - Release 1.1.0

should have handed that off to QA first

@Clueless can you test your scripts and make sure they work as expected?

I'll run through the basics on windows

*https://github.com/snowblossomcoin/snowblossom/compare/7c780c258cc0...6f0f1a24a51e* https://github.com/snowblossomcoin/snowblossom/commit/6f0f1a24a51ef97836472c118fb055175dc73e8b - dos style returns, use 'wallet' rather than 'wallets'

the install a node script seems to work great on debian

@Fireduck the build.sh script replaces all the new lines iwth carriage returns for windows.

in the building deploy temporary directory

also, I thought I already fixed `wallet` ?

not in pool_miner.conf

I thought..

maybe I didn't push it. -_-;

it happens

if you stop working on master and do four eyes principled pull requests, i could be interested in rigging up qa automation

QA is my thing and build automation as well

We have decent unit test framework. Needs more tests of course.

I don't imagine that we will ever be at the point of testing that the sample configs are all correct in an automated fashion.

And some of our unit tests are full integration tests that start up nodes and miners.

Not really unit tests but we run them with junit

the integration tests are easy to turn into quick and dirty smoke tests

Smoke test is load/performance test, right?

no, just a basic ’will it start up and not immediately misbehave’

stuff like ’mine one share on a testnet pool and quit’

https://en.wikipedia.org/wiki/Smoke_testing_(software) In computer programming and software testing, smoke testing (also confidence testing, sanity testing, build verification test (BVT) and build acceptance test) is preliminary testing to reveal simple failures severe enough to (for example) reject a prospective software release. Smoke tests are a subset of test cases that cover the most important functionality of a component or system, used to aid assessment if main functions of the software appear to work correctly. When used to determine if a computer program should be subjected to further, more fine-grained testing, a smoke test may be called an intake test. Alternately, it is a set of tests run on each new build of a product to verify that the build is testable before the build is released into the hands of the test team. In the DevOps paradigm, use of a BVT step is one hallmark of the continuous integration maturity stage. For example, a smoke test may address basic questions like "does the program run?", "does the user interface open?", or "does clicking the main button do anything?" The process of smoke testing aims to determine whether the application is so badly broken as to make further immediate testing unnecessary. As the book Lessons Learned in Software Testing puts it, "smoke tests broadly cover product features in a limited time ... if key features don't work or if key bugs haven't yet been fixed, your team won't waste further time installing or testing". Smoke tests frequently run quickly, giving benefits of faster feedback, rather than running more extensive test suites, which would naturally take much longer. Smoke testing performed on a particular build is also known as a build verification test. A daily build and smoke test is among industry best practices. Smoke testing is also done by testers before accepting a build for further testing. Microsoft claims that after code reviews, "smoke testing is the most cost-effective method for identifying and fixing defects in software". One can perform smoke tests either manually or using an automated tool. In the case of automated tools, the process that generates the build will often initiate the testing. Smoke tests can be broadly categorized as functional tests or as unit tests. Functional tests exercise the complete program with various inputs. Unit tests exercise individual functions, subroutines, or object methods. Functional tests may comprise a scripted series of program inputs, possibly even with an automated mechanism for controlling mouse movements. Unit tests can be implemented either as separate functions within the code itself, or else as a driver layer that links to the code without altering the code being tested.

Ah, my integration tests do that

I might be using wrong terminology

terminology is house and scope specific anyway

i’m not assuming strangers mostly ever fully understand each other

smoke tests come from mechanical and electrical engineering, turn it on and see if it runs just fine or if the smoke escapes

there is actually this jokey belief that most devices actually run and operate on the smoke, as they usually immediately stop functioning if you let the smoke out

a pratchettian twist on the cargo cult idea, i suppose

Yeah, the magic smoke

I've let the magic smoke out a few times

@Rotonen @Fireduck I philosophically sit in my head arguing with myself, how can I REALLY explain something to someone so they understand

and usually it just comes to, you can communicate concepts, but you can't be certain they see the same colors as you perceive them and feel the same way

goes nuts

I had an older version of snowblossom compiled and installed from source and tried to install `sample1-install-node-systemd-service-latest-release.sh` via `https://github.com/snowblossomcoin/snowblossom/blob/master/example/scripts/sample1-install-node-systemd-service-latest-release.sh after extracting the zip file in /var/snowblossom the script fails - most likely in line 32:"ln -sf "$snowblossom_home/systemd/snowblossom-node.service" /etc/systemd/system/" Here's the output: ``` replace snowblossom-1.1.0/configs/client.conf? [y]es, [n]o, [A]ll, [N]one, [r]ename: n replace snowblossom-1.1.0/configs/pool-miner.conf? [y]es, [n]o, [A]ll, [N]one, [r]ename: n replace snowblossom-1.1.0/configs/logging.properties? [y]es, [n]o, [A]ll, [N]one, [r]ename: n replace snowblossom-1.1.0/configs/miner.conf? [y]es, [n]o, [A]ll, [N]one, [r]ename: n replace snowblossom-1.1.0/configs/node.conf? [y]es, [n]o, [A]ll, [N]one, [r]ename: n creating: snowblossom-1.1.0/wallet/ inflating: snowblossom-1.1.0/wallet/readme.txt inflating: snowblossom-1.1.0/node.sh creating: snowblossom-1.1.0/snow/ inflating: snowblossom-1.1.0/snow/readme.txt inflating: snowblossom-1.1.0/send.bat inflating: snowblossom-1.1.0/pool-miner.sh inflating: snowblossom-1.1.0/SnowBlossomMiner_deploy.jar Failed to execute operation: Too many levels of symbolic links ``` copying the service definition files from `systemd/` and then starting manually still seems to work.

checking

*https://github.com/snowblossomcoin/snowblossom/compare/6f0f1a24a51e...3de50ce42dfe* https://github.com/snowblossomcoin/snowblossom/commit/3de50ce42dfea9d5abdaa72777611cddd1c2d038 - Rename Shackleton binary to ShackletonExplorer

[snowblossomcoin/snowblossom] Issue closed by fireduck64

*https://github.com/snowblossomcoin/snowblossom/compare/3de50ce42dfe...90ac3d59cdc4* https://github.com/snowblossomcoin/snowblossom/commit/90ac3d59cdc42b51cd4bf3b769376302c04e4b66 - fixes #57

[snowblossomcoin/snowblossom] Issue closed by fireduck64

*https://github.com/snowblossomcoin/snowblossom/compare/90ac3d59cdc4...5633725d52f6* https://github.com/snowblossomcoin/snowblossom/commit/5633725d52f62246cab6234b6a42cee615ec4382 - balm. fixes #83

[snowblossomcoin/snowblossom] Issue closed by fireduck64

*https://github.com/snowblossomcoin/snowblossom/compare/5633725d52f6...797b5003ff7b* https://github.com/snowblossomcoin/snowblossom/commit/797b5003ff7b440bd4ff651a5e08acb2b10e7410 - oops, missed register

[snowblossomcoin/snowblossom] Issue closed by fireduck64

My DNS is taking forever to sync for my seeds. Ughhh

dynamic dns to update those hostnames or what?

@Tyler Boone does setting the log levels per component work?

for console output

or log file

I've only played with it a little