Open plebhash opened 5 months ago
we've been having CI issues with sv2-ffi
recently
https://github.com/stratum-mining/stratum/pull/1170 as an unsuccessful attempt to solve them
I feel we should disable CI for sv2-ffi
crate until 100% coverage over protocols
is achieved
for now, we're not aware of anyone consuming these, so the maintenance burden seems unjustified
which is the error?
ion sv2-ffi we have tests and header checks. I don't thing we should disable them
which is the error?
sv2.h
hashes are not matching, but that only happens on Github Actions
https://github.com/stratum-mining/stratum/actions/runs/10990732245/job/30511588545
@jbesraa and I tried reproducing locally on multiple setups without success
sorry a typo I meant "in"
ion sv2-ffi we have tests and header checks. I don't thing we should disable them
the idea here is to disable .github/workflows/sv2-header-check.yaml
we can still leave scripts/{build_header,sv2-header-check}.sh
for future reference
why? what error do you have? that script is very important
why? what error do you have? that script is very important
https://github.com/stratum-mining/stratum/issues/919#issuecomment-2371645443
CI problems discussed above were solved via https://github.com/stratum-mining/stratum/pull/1172
hiding the discussion to avoid confusion
the core goal of this issue remains: expand FFI functionality to all protocols
crates
As discussed here, for historical reasons, the FFIs were started with the intention to be imported into Bitcoin Core (TP).
So FFI functionality is currently limited to:
protocols/v2/codec-sv2
protocols/v2/const-sv2
protocols/v2/binary-sv2
protocols/v2/subprotocols/common-messages
protocols/v2/subprotocols/template-distribution-sv2
In order to allow firmware integrations (e.g.: https://github.com/skot/ESP-Miner/issues/168), this functionality needs to be expanded with:
protocols/v2/framing-sv2
protocols/v2/noise-sv2
protocols/v2/subprotocols/job-declaration
protocols/v2/subprotocols/mining