We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
the client calls the submit2 function even though the submit 1 function call for the same epoch has received no data
ftso-v2-songbird-client | [11-15|10:48:30.001] INFO protocol/submitter.go:161 Submitter submit1 did not get any data, skipping submission ftso-v2-songbird-client | [11-15|10:48:50.001] INFO protocol/submitter.go:150 Submitter submit2 running for epoch 813753 [2024-11-15 10:48:45 +0000 UTC, 2024-11-15 10:50:15 +0000 UTC] ftso-v2-songbird-client | [11-15|10:48:50.001] INFO protocol/protocol_utils.go:55 Calling protocol client API: http://data-provider:3500/submit2/813752/0xxxxxxxxxxxx ftso-v2-songbird-client | [11-15|10:48:54.158] INFO protocol/submitter.go:79 Submitter submit2 successfully sent tx_
I think it causes a panlization in the rewards' calculation.
Makes it sense to perform the submit 2 function only if submit1 is enabled and has received data for the same epoch ?
Davide
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
the client calls the submit2 function even though the submit 1 function call for the same epoch has received no data
ftso-v2-songbird-client | [11-15|10:48:30.001] INFO protocol/submitter.go:161 Submitter submit1 did not get any data, skipping submission
ftso-v2-songbird-client | [11-15|10:48:50.001] INFO protocol/submitter.go:150 Submitter submit2 running for epoch 813753 [2024-11-15 10:48:45 +0000 UTC, 2024-11-15 10:50:15 +0000 UTC]
ftso-v2-songbird-client | [11-15|10:48:50.001] INFO protocol/protocol_utils.go:55 Calling protocol client API: http://data-provider:3500/submit2/813752/0xxxxxxxxxxxx
ftso-v2-songbird-client | [11-15|10:48:54.158] INFO protocol/submitter.go:79 Submitter submit2 successfully sent tx_
I think it causes a panlization in the rewards' calculation.
Makes it sense to perform the submit 2 function only if submit1 is enabled and has received data for the same epoch ?
Davide
The text was updated successfully, but these errors were encountered: