2023-08-21 10:26:43 +00:00
|
|
|
import ../../conf
|
|
|
|
when codex_enable_proof_failures:
|
|
|
|
import std/strutils
|
|
|
|
import pkg/stint
|
|
|
|
import pkg/ethers
|
|
|
|
import pkg/ethers/testing
|
|
|
|
|
|
|
|
import ../../contracts/requests
|
feat: create logging proxy (#663)
* implement a logging proxy
The logging proxy:
- prevents the need to import chronicles (as well as export except toJson),
- prevents the need to override `writeValue` or use or import nim-json-seralization elsewhere in the codebase, allowing for sole use of utils/json for de/serialization,
- and handles json formatting correctly in chronicles json sinks
* Rename logging -> logutils to avoid ambiguity with common names
* clean up
* add setProperty for JsonRecord, remove nim-json-serialization conflict
* Allow specifying textlines and json format separately
Not specifying a LogFormat will apply the formatting to both textlines and json sinks.
Specifying a LogFormat will apply the formatting to only that sink.
* remove unneeded usages of std/json
We only need to import utils/json instead of std/json
* move serialization from rest/json to utils/json so it can be shared
* fix NoColors ambiguity
Was causing unit tests to fail on Windows.
* Remove nre usage to fix Windows error
Windows was erroring with `could not load: pcre64.dll`. Instead of fixing that error, remove the pcre usage :)
* Add logutils module doc
* Shorten logutils.formatIt for `NBytes`
Both json and textlines formatIt were not needed, and could be combined into one formatIt
* remove debug integration test config
debug output and logformat of json for integration test logs
* Use ## module doc to support docgen
* bump nim-poseidon2 to export fromBytes
Before the changes in this branch, fromBytes was likely being resolved by nim-stew, or other dependency. With the changes in this branch, that dependency was removed and fromBytes could no longer be resolved. By exporting fromBytes from nim-poseidon, the correct resolution is now happening.
* fixes to get compiling after rebasing master
* Add support for Result types being logged using formatIt
2024-01-23 07:35:03 +00:00
|
|
|
import ../../logutils
|
2023-08-21 10:26:43 +00:00
|
|
|
import ../../market
|
|
|
|
import ../salescontext
|
|
|
|
import ./proving
|
|
|
|
|
|
|
|
logScope:
|
|
|
|
topics = "marketplace sales simulated-proving"
|
|
|
|
|
|
|
|
type
|
|
|
|
SaleProvingSimulated* = ref object of SaleProving
|
|
|
|
failEveryNProofs*: int
|
|
|
|
proofCount: int
|
|
|
|
|
|
|
|
proc onSubmitProofError(error: ref CatchableError, period: UInt256, slotId: SlotId) =
|
feat: create logging proxy (#663)
* implement a logging proxy
The logging proxy:
- prevents the need to import chronicles (as well as export except toJson),
- prevents the need to override `writeValue` or use or import nim-json-seralization elsewhere in the codebase, allowing for sole use of utils/json for de/serialization,
- and handles json formatting correctly in chronicles json sinks
* Rename logging -> logutils to avoid ambiguity with common names
* clean up
* add setProperty for JsonRecord, remove nim-json-serialization conflict
* Allow specifying textlines and json format separately
Not specifying a LogFormat will apply the formatting to both textlines and json sinks.
Specifying a LogFormat will apply the formatting to only that sink.
* remove unneeded usages of std/json
We only need to import utils/json instead of std/json
* move serialization from rest/json to utils/json so it can be shared
* fix NoColors ambiguity
Was causing unit tests to fail on Windows.
* Remove nre usage to fix Windows error
Windows was erroring with `could not load: pcre64.dll`. Instead of fixing that error, remove the pcre usage :)
* Add logutils module doc
* Shorten logutils.formatIt for `NBytes`
Both json and textlines formatIt were not needed, and could be combined into one formatIt
* remove debug integration test config
debug output and logformat of json for integration test logs
* Use ## module doc to support docgen
* bump nim-poseidon2 to export fromBytes
Before the changes in this branch, fromBytes was likely being resolved by nim-stew, or other dependency. With the changes in this branch, that dependency was removed and fromBytes could no longer be resolved. By exporting fromBytes from nim-poseidon, the correct resolution is now happening.
* fixes to get compiling after rebasing master
* Add support for Result types being logged using formatIt
2024-01-23 07:35:03 +00:00
|
|
|
error "Submitting invalid proof failed", period = period, slotId, msg = error.msg
|
2023-08-21 10:26:43 +00:00
|
|
|
|
2023-12-11 10:29:15 +00:00
|
|
|
method prove*(state: SaleProvingSimulated, slot: Slot, challenge: ProofChallenge, onProve: OnProve, market: Market, currentPeriod: Period) {.async.} =
|
2023-08-21 10:26:43 +00:00
|
|
|
trace "Processing proving in simulated mode"
|
|
|
|
state.proofCount += 1
|
|
|
|
if state.failEveryNProofs > 0 and
|
|
|
|
state.proofCount mod state.failEveryNProofs == 0:
|
|
|
|
state.proofCount = 0
|
|
|
|
|
|
|
|
try:
|
|
|
|
warn "Submitting INVALID proof", period = currentPeriod, slotId = slot.id
|
2024-02-07 06:50:35 +00:00
|
|
|
await market.submitProof(slot.id, Groth16Proof.default)
|
2023-08-21 10:26:43 +00:00
|
|
|
except ProviderError as e:
|
|
|
|
if not e.revertReason.contains("Invalid proof"):
|
|
|
|
onSubmitProofError(e, currentPeriod, slot.id)
|
|
|
|
except CatchableError as e:
|
|
|
|
onSubmitProofError(e, currentPeriod, slot.id)
|
|
|
|
else:
|
2023-12-11 10:29:15 +00:00
|
|
|
await procCall SaleProving(state).prove(slot, challenge, onProve, market, currentPeriod)
|