-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Merge develop
into breaking
#12202
Merge develop
into breaking
#12202
Conversation
…ully qualified library name
- SemanticTests accepts fully qualified library name and also unqualifed library name when the library is defined in the same file for convenience. - commandline tests are added! Signed-off-by: soroosh-sdi <soroosh.sardari@gmail.com>
Remove linking to unqualified library name
Template code for disallowing options in input modes that do not support them (handles `--error-recovery`)
[Docs] Fix formatting of the "security fixes" link on the main page
Fix typo in ir-breaking-changes.rst
Fix typo compiler->constructor.
Co-authored-by: shikharvashistha <shikharvashistha@yandex.com> Co-authored-by: cameel <kamil.sliwak@codepoets.it>
[CI] Store yul-phaser as an artifact
[CI] Run hardhat tests as a PR check
…command [CI] Reusable command for gitter notifications
Added different colors for warning & error
Do not use named function labels if function names are not unique.
Assert and stack traces for Bash scripts
…dition Add missing condition to `gitter_notify` command
…arding-fqln Clarify that `linkersymbol()` accepts but does not require a fully qualified library name
[SMTChecker] Report contract invariants
[trivial] Sort bugfixes in changelog
This is to avoid a assert from failing for forward declared user defined value types.
And added a proper error message when constant types containing (nested) mapping types are used.
Oh! The use-after-free is in develop?? I'll fix it right away. |
CI seems to be failing for the same reason as the last time (#11840 (comment)). Last time I reported it to CircleCI and this is how I described the situation (after some back and forth to provide more details):
The main part of the response I got was this:
I haven't heard anything on the issue since then. Apparently the bug is still present. If my assessment is correct then a workaround is to simply merge something into |
Fix is here: #12203 |
Yeah. It's not the first time this happens - some jobs that run outside of PRs have no notifications so we usually don't notice. I have a PR that adds notifications to them: #12174. |
Moved storage size assert to TypeChecker from DeclarationTypeChecker
Fix wrong path to isoltest in docs
Fix use-after-free bug.
Looks like EDIT: Ah, wait. That's on develop. The job will run on |
The Hardhat test finally ran on The workflow as a whole did not pass though. There's some unrelated breakage. |
I just got a notification from CircleCI that the issue from #12202 (comment) has been fixed. So, hopefully, no more |
The main reason for updating the branch is that I want to see if the
t_ems_ext_hardhat
job added in #12165 will pass onbreaking
too.