Skip to content

Update ERC-165: Clarify misleading usage of pure attribute #2118

Update ERC-165: Clarify misleading usage of pure attribute

Update ERC-165: Clarify misleading usage of pure attribute #2118

Triggered via pull request February 28, 2024 13:13
Status Cancelled
Total duration 1m 7s
Artifacts 1

ci.yml

on: pull_request
Save PR Number
3s
Save PR Number
HTMLProofer
57s
HTMLProofer
Link Check
19s
Link Check
CodeSpell
14s
CodeSpell
EIP Walidator
9s
EIP Walidator
Markdown Linter
4s
Markdown Linter
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 5 warnings
Markdown Linter
Process completed with exit code 1.
Markdown Linter
Unable to process file command 'env' successfully.
Markdown Linter
Invalid value. Matching delimiter not found 'EOF'
the first match of the given pattern must be a link: ERCS/erc-165.md#L22
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 22 | 3. How to detect if a contract implements ERC-165 | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+` = help: see https://ethereum.github.io/eipw/markdown-link-first/
the first match of the given pattern must be a link: ERCS/erc-165.md#L57
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 57 | A contract that is compliant with ERC-165 shall implement the following interface (referred as `ERC165.sol`): | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
the first match of the given pattern must be a link: ERCS/erc-165.md#L86
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 86 | ### How to Detect if a Contract Implements ERC-165 | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
the first match of the given pattern must be a link: ERCS/erc-165.md#L89
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 89 | 2. If the call fails or return false, the destination contract does not implement ERC-165. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
the first match of the given pattern must be a link: ERCS/erc-165.md#L91
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 91 | 4. If the second call fails or returns true, the destination contract does not implement ERC-165. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
the first match of the given pattern must be a link: ERCS/erc-165.md#L92
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 92 | 5. Otherwise it implements ERC-165. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
the first match of the given pattern must be a link: ERCS/erc-165.md#L96
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 96 | 1. If you are not sure if the contract implements ERC-165, use the above procedure to confirm. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
the first match of the given pattern must be a link: ERCS/erc-165.md#L97
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 97 | 2. If it does not implement ERC-165, then you will have to see what methods it uses the old-fashioned way. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
the first match of the given pattern must be a link: ERCS/erc-165.md#L98
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 98 | 3. If it implements ERC-165 then just call `supportsInterface(interfaceID)` to determine if it implements an interface you can use. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
the first match of the given pattern must be a link: ERCS/erc-165.md#L106
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 106 | The mechanism described above (with `0xffffffff`) should work with most of the contracts previous to this standard to determine that they do not implement ERC-165. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
HTMLProofer
Canceling since a higher priority waiting request for 'Continuous Integration-283' exists
HTMLProofer
The operation was canceled.
Save PR Number
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/upload-artifact@65d862660abb392b8c4a3d1195a2108db131dd05. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Markdown Linter
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
EIP Walidator
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
CodeSpell
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Link Check
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Artifacts

Produced during runtime
Name Size
pr_number Expired
86 Bytes