Process completed with exit code 1.

Unable to process file command 'env' successfully.

Invalid value. Matching delimiter not found 'EOF'

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-is-contract.md | 19 | EOFv1 as scoped in [EIP-7692](./eip-7692.md) removes code introspection capabilities from the EVM, including the `EXTCODESIZE` instruction. This makes it hard for ERC-721 and ERC-1155 standard contracts to be implemented, as they rely on discovering whether a token's `safeTransfer` call target was an EOA or a smart contract: | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+` = help: see https://ethereum.github.io/eipw/markdown-link-first/

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-is-contract.md | 19 | EOFv1 as scoped in [EIP-7692](./eip-7692.md) removes code introspection capabilities from the EVM, including the `EXTCODESIZE` instruction. This makes it hard for ERC-721 and ERC-1155 standard contracts to be implemented, as they rely on discovering whether a token's `safeTransfer` call target was an EOA or a smart contract: | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-is-contract.md | 24 | `IS_CONTRACT` is aimed to fill this gap and bring back the possibility to easily implement ERC-721 and ERC-1155 standard contracts in EOF. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-is-contract.md | 24 | `IS_CONTRACT` is aimed to fill this gap and bring back the possibility to easily implement ERC-721 and ERC-1155 standard contracts in EOF. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-is-contract.md | 58 | There have been other solutions proposed to alleviate the problems related to lack of code introspection required for ERC-721 and ERC-1155 standards: | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-is-contract.md | 58 | There have been other solutions proposed to alleviate the problems related to lack of code introspection required for ERC-721 and ERC-1155 standards: | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-is-contract.md | 74 | Removing code introspection is one of the tenets of EOF and `IS_CONTRACT` would be an exception from the principle. Without `IS_CONTRACT`, ERC-721 and ERC-1155 standard implementations have to resort to either: | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-is-contract.md | 74 | Removing code introspection is one of the tenets of EOF and `IS_CONTRACT` would be an exception from the principle. Without `IS_CONTRACT`, ERC-721 and ERC-1155 standard implementations have to resort to either: | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-is-contract.md | 78 | 3. Updating the standards to not rely on code introspection (`safeTransfer` safe guards) patterns, also unlikely to happen as ERC-721 and ERC-1155 are Final and adopted in practice. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-is-contract.md | 78 | 3. Updating the standards to not rely on code introspection (`safeTransfer` safe guards) patterns, also unlikely to happen as ERC-721 and ERC-1155 are Final and adopted in practice. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

Canceling since a higher priority waiting request for 'Continuous Integration-8838' exists

The operation was canceled.

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@65d862660abb392b8c4a3d1195a2108db131dd05. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/