Rootul P

master has a branch protection rule that prevents me from deleting it

I deleted branches that haven't been touched in over 6 months: https://github.com/celestiaorg/celestia-core/branches We're down to 10 branches. Tagging @evan-forbes if you have admin rights to delete the `master` branch.

If it's strictly for reference purposes, are you open to renaming `master` to `deprecated-master` in order to avoid confusion like https://github.com/celestiaorg/celestia-core/pull/795#pullrequestreview-1030657928

Safe to close this issue in favor of https://github.com/celestiaorg/celestia-core/issues/839 ?

Closing in favor of https://github.com/celestiaorg/celestia-core/issues/839 and https://github.com/celestiaorg/celestia-app/issues/659

Notes from synchronous discussion: - We likely don't want to switch to leopard and instead want to switch to an implementation in klauspost (https://github.com/klauspost ?) @musalbas to add link to...

After reading the linked comments, I still don't understand the motivation behind this issue. @Wondertan does celestia-node want to use the share splitting code with a requirement that prevents it...

I observed this error in a clone of https://github.com/b9lab/ida-exercise-week-2-student-repo No errors observed here: ``` git fsck --no-dangling --full Checking object directories: 100% (256/256), done. Checking objects: 100% (1018/1018), done. ```

Closing in favor of https://github.com/celestiaorg/celestia-core/issues/839 and https://github.com/celestiaorg/celestia-app/issues/659? Please re-open if this needs further attention.

You're right! I can reproduce this on Firefox but can't reproduce on Chrome / Brave.