Skip to content

Fix some small problems #3878

New issue

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

Merged
merged 3 commits into from
May 20, 2024
Merged

Conversation

jberthold
Copy link
Member

  • --interim-simplification problem: When maxDepth < forceFallback , the proxy was considering a genuine DepthBound result as an artefact caused by the interim simplification, and would try to continue execution.
  • The cabal.project file was set up to never profile any booster or kore-rpc-types code
  • When given a path to a non-existing file as input, RpcClient reported a server connection error and retried (the criterion for recognising connection errors was to general).

@jberthold jberthold self-assigned this May 20, 2024
(Just forceDepth, _) -> Just forceDepth
(_, Just maxDepth) -> Just $ maxDepth - currentDepth
_ -> Nothing
(bResult, bTime) <- Stats.timed $ booster (Execute r{maxDepth = mbDepthLimit})
case bResult of
Right (Execute boosterResult)
-- the execution reached the depth bound due to a forced Kore simplification
| boosterResult.reason == DepthBound && isJust cfg.forceFallback -> do
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Once cDepth was reaching maxDepth (see above, when maxDepth < forceDepth) we were starting to make requests with max-depth: 0 and looping.

@jberthold jberthold marked this pull request as ready for review May 20, 2024 06:46
Copy link
Contributor

@geo2a geo2a left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@rv-jenkins rv-jenkins merged commit 31bf501 into master May 20, 2024
7 checks passed
@rv-jenkins rv-jenkins deleted the HOTFIX-interim-glitch+client-error-no-file branch May 20, 2024 08:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants