Verified Commit df2e82c0 authored by Konstantin Ivanov's avatar Konstantin Ivanov
Browse files

[#465] Fix links in markdown docs

Problem: some links are broken.

Recently xrefcheck gained a feature to ignore some links, with it we can
finally make xrefcheck pass.

Solution:

* Mark that link to "New issue" page as ignored, since it requires
  authentication and returns a weird 503 error code for unauthorized
  agent.
* Remove the link to an MR about gas limit bump in `nomadic-labs/tezos`
  repo, since I failed to find this MR in their new `metastatedev/tezos`
  repo.
* Correct other links.
parent 2cb32dde
Pipeline #286210927 passed with stages
in 21 minutes and 41 seconds
......@@ -8,7 +8,7 @@ SPDX-License-Identifier: LicenseRef-MIT-TQ
## Reporting Issues
Please [open an issue](https://gitlab.com/morley-framework/morley/-/issues/new)
Please <!-- xrefcheck: ignore link --> [open an issue](https://gitlab.com/morley-framework/morley/-/issues/new)
if you find a bug or have a feature request.
Before submitting a bug report or feature request, check to make sure it hasn't already been submitted.
......
......@@ -16,7 +16,7 @@ These contracts are occasionally updated in the [tezos repository][tz:contracts]
Here are some things you should keep in mind:
1. Update the link to the contracts in this file.
2. Do not accidentally add the `legacy` folder because it was removed as stated above.
3. Carefully check the [Contracts.hs](/code/cleveland/morley-test/Test/Util/Contracts.hs) module:
3. Carefully check the [Contracts.hs](/code/cleveland/test-common/Test/Util/Contracts.hs) module:
+ `wellTypedContractDirs` lists all folders with well-typed contracts, you may need to add new folders there.
+ We have to distinguish ill-typed and unparseable contracts, and our parser is not the same as in Tezos, so there is an ill-typed example contract that is not parseable by our code.
It's handled in that module.
......
......@@ -355,7 +355,8 @@ You *should* avoid overly general signatures for functions that are actually
used with only one type for each parameter. If you need the polymorhic version
(i.e. if you are instantiating it more than once or if you are writing a
library), you *may* use GHC's [`SPECIALIZE`
pragma](https://downloads.haskell.org/~ghc/latest/docs/html/users_guide/glasgow_exts.html#specialize-pragma).
pragma](https://downloads.haskell.org/~ghc/latest/docs/html/users_guide/exts/rewrite_rules.html#specialisation).
You *should* omit parentheses if you have only one constraint.
......
......@@ -19,7 +19,7 @@ transaction, an integer has been added to the storage and ten characters have
been appended to an existing string in the storage, then ꜩ 18 will be withdrawn
from the contract’s balance and destroyed.
I could not find any confirmation that this is true. Note that generally the [whitepaper](https://tezos.com/static/white_paper-2dc8c02267a8fb86bd67a108199441bf.pdf) is **outdated and must be ignored.** See protocol descriptions in the [whitedoc](https://tezos.gitlab.io/mainnet/index.html) instead.
I could not find any confirmation that this is true. Note that generally the [whitepaper](https://tezos.com/assets/files/whitepaper-d0cd272790ed3ba5951b30d019db2013.pdf) is **outdated and must be ignored.** See protocol descriptions in the [whitedoc](https://tezos.gitlab.io/mainnet/index.html) instead.
The whitepaper also says that contracts must have positive balance to _exist,_ which is also [not true](https://tezos.stackexchange.com/questions/886/what-are-the-new-rules-for-when-a-kt1-gets-destroyed-or-when-burn-cap-must) — contracts may have zero balance and it is perfectly fine.
......
......@@ -102,7 +102,7 @@ Usually, by typechecking in the context of Tezos people mean _parsing_ (includin
# Contents list lifecycle
In Tezos, a manager (an entity who initiates the state change) signs a "contents list" — a list of operations she wants to perform.
There is a hard limit for each operation from the content list. [In Carthage](https://gitlab.com/nomadic-labs/tezos/-/merge_requests/117/diffs), each operation can consume no more than `1_040_000` gas, _including_ the internal operations that may be emitted. The whole contents list has no defined upper limit but since all the transactions from it must belong to the same _block,_ the block gas limit applies. In Carthage, the block gas limit is `10_400_000` gas.
There is a hard limit for each operation from the content list. Starting from Carthage, each operation can consume no more than `1_040_000` gas, _including_ the internal operations that may be emitted. The whole contents list has no defined upper limit but since all the transactions from it must belong to the same _block,_ the block gas limit applies. In Carthage, the block gas limit is `10_400_000` gas.
Each operation in the list is one of the following:
1. Reveal
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment