Skip to content

docs: update instructions #1976

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

ArturWieczorek
Copy link
Contributor

@ArturWieczorek ArturWieczorek commented May 12, 2025

secp256k1 = { url = "github:bitcoin-core/secp256k1?ref=v0.3.2"; flake = false; };

which has different revison: https://github.com/bitcoin-core/secp256k1/releases/tag/v0.3.2

secp256k1$ git co v0.3.2
HEAD is now at acf5c55 Merge bitcoin-core/secp256k1#1312: release: Prepare for 0.3.2

secp256k1$ git last
commit acf5c55ae6a94e5ca847e07def40427547876101 (HEAD, tag: v0.3.2)
Merge: 3e3d125 d490ca2
Author: Tim Ruffing <[email protected]>
Date:   Sat May 13 19:38:26 2023 +0200

    Merge bitcoin-core/secp256k1#1312: release: Prepare for 0.3.2
  • Remove not existing anymore environments: sanchonet, private
  • Fix typos, wrong anchors
  • Update ghc to 9.6.7 and cabal to 3.10.2.0 - the same versions as in official node instruction

@ArturWieczorek ArturWieczorek requested a review from a team as a code owner May 12, 2025 17:42
Cmdv
Cmdv previously approved these changes May 12, 2025
@ArturWieczorek ArturWieczorek force-pushed the artur/update-building-doc branch 3 times, most recently from bba92af to 48905d8 Compare May 13, 2025 16:35
@ArturWieczorek ArturWieczorek changed the title docs: update builiding and running instruction docs: update instructions May 13, 2025
@ArturWieczorek ArturWieczorek marked this pull request as draft May 13, 2025 16:37
@ArturWieczorek ArturWieczorek force-pushed the artur/update-building-doc branch 2 times, most recently from 6e6ad89 to 96c1787 Compare May 13, 2025 17:03
@ArturWieczorek ArturWieczorek marked this pull request as ready for review May 13, 2025 20:52
ghcup install cabal 3.10.1.0
ghcup set ghc 8.10.7
ghcup set cabal 3.10.1.0
ghcup install ghc 9.6.7
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Is this OK for cardano-db-sync ? Those are the versions that were recently added in official cardano-node build instruction --> https://developers.cardano.org/docs/get-started/cardano-node/installing-cardano-node/#building-via-cabal

@ArturWieczorek ArturWieczorek requested review from sgillespie and Cmdv May 13, 2025 20:56
@ArturWieczorek ArturWieczorek force-pushed the artur/update-building-doc branch from 96c1787 to f3802ba Compare May 14, 2025 12:55
@@ -12,7 +12,6 @@
- `--fix-only`: Runs only the db-sync fix procedure for the wrong datum, redeemer_data, and plutus script bytes and exits.
- `--disable-cache`: Disables the db-sync caches. Reduces memory usage but it takes longer to sync.
- `--rollback-to-slot SLOTNO`: Force a rollback to the specified slot, if the given slot doesn't exist it will use the next greater slot.
- `--disable-in-out`: Disables the `tx_in` and `tx_out` table.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This one has no effect anymore. When using --disable-epoch --disable-in-out it will result in:

preprod_13.6.0.5=# select count(*) from epoch;
 count 
-------
     0
(1 row)


preprod_13.6.0.5=# select count(*) from tx_in;
  count  
---------
 1211557
(1 row)

preprod_13.6.0.5=# select count(*) from tx_out;
  count  
---------
 1686855
(1 row)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Does it mean that things related to pHasInOut and enpHasInOut:

should be removed from code ?

@@ -12,7 +12,6 @@
- `--fix-only`: Runs only the db-sync fix procedure for the wrong datum, redeemer_data, and plutus script bytes and exits.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Can we delete --skip-fix and --fix-only as well ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants