Skip to content

build(deps): bump YamlDotNet from 3.3.0 to 5.0.0 in /clang-tools-extra/clang-tidy-vs/ClangTidy#1

Open
dependabot[bot] wants to merge 1 commit intointersec/9.xfrom
dependabot/nuget/clang-tools-extra/clang-tidy-vs/ClangTidy/YamlDotNet-5.0.0
Open

build(deps): bump YamlDotNet from 3.3.0 to 5.0.0 in /clang-tools-extra/clang-tidy-vs/ClangTidy#1
dependabot[bot] wants to merge 1 commit intointersec/9.xfrom
dependabot/nuget/clang-tools-extra/clang-tidy-vs/ClangTidy/YamlDotNet-5.0.0

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github May 19, 2020

Bumps YamlDotNet from 3.3.0 to 5.0.0.

Release notes

Sourced from YamlDotNet's releases.

Security issues and dropping legacy behaviors

/!\ This release fixes a security issue. It is strongly recommended to upgrade, mainly if you are parsing documents from sources that you do not trust.

Many thanks to Kurt Boberg, from the DocuSign Application Security Team, who identified this issue and provided feedback on mitigation strategies.

  • Remove the legacy backwards-compatibe syntax that enabled to create Serializer and Deserializer directly then changing their configutation.
    In most cases, the calls to the constructors should be replaced by instantiations of SerializerBuilder and DeserializerBuilder. These can be configured at will, then used to create instances of (De)serializer. It is still possible to use the default constructors, if no configuration is needed.

  • Drop support for specifying arbitrary type names in tags.
    Support for automatically resolving a fully qualified type name from a tag has been discontinued. That feature was poorly designed and not standard.
    During deserialization, each tag mapping must be explicitly registered. During serialization, when using the EnsureRoundtrip method, it is necessary to register tag mappings for each type that will require a tag, that is, any type that is used as the value of a property with a different declared type.

  • Fix bug where deserialized values were not being converted to the destination type.

    var sut = new DeserializerBuilder()
        .WithTagMapping("!dbl", typeof(DoublyConverted))
        .Build();
    // The scalar "hello" will first be converted to DoublyConverted
    // then that value will be converted to int.
    var result = sut.Deserialize<int>("!dbl hello");
    Assert.Equal(5, result);

Add support for (de)serialization of System.Type

No release notes provided.

Cleanup the project

  • Refactored the project and solution so that they load and build cleanly in VS2017.
  • Reviewed the target platforms.
    • The currently supported platforms are now:
      • .NET Framework 4.5
      • .NET Framework 3.5
      • .NET Framework 2.0 (experimental)
      • .NET Standard 1.3
      • Unity Subset v3.5
    • The following platforms are no longer supported:
      • Profile259 (please upgrade to netstandard)
... (truncated)
Changelog

Sourced from YamlDotNet's changelog.

Release notes

Release 8.1.1

Bug fixes

  • Improve compliance with the official YAML test suite: #467, #469 and #475.

  • Make YamlMemberAttribute.DefaultValuesHandling actually usable. Fixes #466.

  • Actually inherit YamlIgnore attributes: #481.

New features

  • Add LowerCaseNamingConvention: #477.

Previous releases

... (truncated)
Commits
  • e024a32 Prepare release 5.0.0
  • 0ce8ac1 Drop support for specifying arbitrary type names in tags
  • c8df563 Remove legacy backwards compatibility
  • f96b7cc Ensure that tagged values are properly converted to the destination type
  • 8f20a18 Prepare release 4.3.2
  • 857192d Fix bug whe TypeConverter was being ignored on all platforms
  • 145477a Remove serialization support from exceptions
  • 113261c Add quick build task
  • 837f61a Pin Cake version
  • 667778b Merge pull request #313 from thoughtcroft/patch-1
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [YamlDotNet](https://github.com/aaubry/YamlDotNet) from 3.3.0 to 5.0.0.
- [Release notes](https://github.com/aaubry/YamlDotNet/releases)
- [Changelog](https://github.com/aaubry/YamlDotNet/blob/master/RELEASE_NOTES.md)
- [Commits](aaubry/YamlDotNet@v3.3.0...v5.0.0)

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label May 19, 2020
IntersecBot pushed a commit that referenced this pull request Oct 11, 2021
For some reasons, on centos-7 with LLVM_LINK_LLVM_DYLIB=ON, there is a
segfault when on `suffix.str()` when `suffix` is a Twine variable in
RewriteBlocksAction::CreateASTConsumer():

  #0 0x00007fbb9f506054 PrintStackTraceSignalHandler(void*) (/srv/tools/clang_9.x/bin/../lib/libLLVM-9.so+0x6a6054)
  #1 0x00007fbb9f503d5e llvm::sys::RunSignalHandlers() (/srv/tools/clang_9.x/bin/../lib/libLLVM-9.so+0x6a3d5e)
  #2 0x00007fbb9f506308 SignalHandler(int) (/srv/tools/clang_9.x/bin/../lib/libLLVM-9.so+0x6a6308)
  #3 0x00007fbba23185d0 __restore_rt (/lib64/libpthread.so.0+0xf5d0)
  #4 0x00007fbb9e3c976f __memcpy_ssse3_back /usr/src/debug////////glibc-2.17-c758a686/string/../sysdeps/x86_64/multiarch/memcpy-ssse3-bac
 k.S:1628:0
  #5 0x00007fbb9f4e68c9 llvm::raw_svector_ostream::write_impl(char const*, unsigned long) (/srv/tools/clang_9.x/bin/../lib/libLLVM-9.so+0
 x6868c9)
  #6 0x00007fbb9f4e50f1 llvm::raw_ostream::write(char const*, unsigned long) (/srv/tools/clang_9.x/bin/../lib/libLLVM-9.so+0x6850f1)
  #7 0x00007fbb9f4c10c3 llvm::Twine::printOneChild(llvm::raw_ostream&, llvm::Twine::Child, llvm::Twine::NodeKind) const (/srv/tools/clang
 _9.x/bin/../lib/libLLVM-9.so+0x6610c3)
  #8 0x00007fbb9f4c0d94 llvm::Twine::str() const (/srv/tools/clang_9.x/bin/../lib/libLLVM-9.so+0x660d94)
  #9 0x0000000000dab4f5 clang::RewriteBlocksAction::CreateASTConsumer(clang::CompilerInstance&, llvm::StringRef) (/srv/tools/clang_9.x/bi
 n/clang+0xdab4f5)
 #10 0x0000000000b839f2 clang::FrontendAction::CreateWrappedASTConsumer(clang::CompilerInstance&, llvm::StringRef) (/srv/tools/clang_9.x/
 bin/clang+0xb839f2)
 #11 0x0000000000b86816 clang::FrontendAction::BeginSourceFile(clang::CompilerInstance&, clang::FrontendInputFile const&) (/srv/tools/cla
 ng_9.x/bin/clang+0xb86816)
 #12 0x0000000000b26bb5 clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) (/srv/tools/clang_9.x/bin/clang+0xb26bb5)
 #13 0x0000000000c2b4d8 clang::ExecuteCompilerInvocation(clang::CompilerInstance*) (/srv/tools/clang_9.x/bin/clang+0xc2b4d8)
 #14 0x000000000060de69 cc1_main(llvm::ArrayRef<char const*>, char const*, void*) (/srv/tools/clang_9.x/bin/clang+0x60de69)
 #15 0x000000000060b680 main (/srv/tools/clang_9.x/bin/clang+0x60b680)
 #16 0x00007fbb9e2963d5 __libc_start_main /usr/src/debug/glibc-2.17-c758

The solution is to use a std::string instead for `suffix`.
IntersecBot pushed a commit that referenced this pull request Oct 12, 2021
For some reasons, on centos-7 with LLVM_LINK_LLVM_DYLIB=ON, there is a
segfault when on `suffix.str()` when `suffix` is a Twine variable in
RewriteBlocksAction::CreateASTConsumer():

  #0 0x00007fbb9f506054 PrintStackTraceSignalHandler(void*) (/srv/tools/clang_9.x/bin/../lib/libLLVM-9.so+0x6a6054)
  #1 0x00007fbb9f503d5e llvm::sys::RunSignalHandlers() (/srv/tools/clang_9.x/bin/../lib/libLLVM-9.so+0x6a3d5e)
  #2 0x00007fbb9f506308 SignalHandler(int) (/srv/tools/clang_9.x/bin/../lib/libLLVM-9.so+0x6a6308)
  #3 0x00007fbba23185d0 __restore_rt (/lib64/libpthread.so.0+0xf5d0)
  #4 0x00007fbb9e3c976f __memcpy_ssse3_back /usr/src/debug////////glibc-2.17-c758a686/string/../sysdeps/x86_64/multiarch/memcpy-ssse3-bac
 k.S:1628:0
  #5 0x00007fbb9f4e68c9 llvm::raw_svector_ostream::write_impl(char const*, unsigned long) (/srv/tools/clang_9.x/bin/../lib/libLLVM-9.so+0
 x6868c9)
  #6 0x00007fbb9f4e50f1 llvm::raw_ostream::write(char const*, unsigned long) (/srv/tools/clang_9.x/bin/../lib/libLLVM-9.so+0x6850f1)
  #7 0x00007fbb9f4c10c3 llvm::Twine::printOneChild(llvm::raw_ostream&, llvm::Twine::Child, llvm::Twine::NodeKind) const (/srv/tools/clang
 _9.x/bin/../lib/libLLVM-9.so+0x6610c3)
  #8 0x00007fbb9f4c0d94 llvm::Twine::str() const (/srv/tools/clang_9.x/bin/../lib/libLLVM-9.so+0x660d94)
  #9 0x0000000000dab4f5 clang::RewriteBlocksAction::CreateASTConsumer(clang::CompilerInstance&, llvm::StringRef) (/srv/tools/clang_9.x/bi
 n/clang+0xdab4f5)
 #10 0x0000000000b839f2 clang::FrontendAction::CreateWrappedASTConsumer(clang::CompilerInstance&, llvm::StringRef) (/srv/tools/clang_9.x/
 bin/clang+0xb839f2)
 #11 0x0000000000b86816 clang::FrontendAction::BeginSourceFile(clang::CompilerInstance&, clang::FrontendInputFile const&) (/srv/tools/cla
 ng_9.x/bin/clang+0xb86816)
 #12 0x0000000000b26bb5 clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) (/srv/tools/clang_9.x/bin/clang+0xb26bb5)
 #13 0x0000000000c2b4d8 clang::ExecuteCompilerInvocation(clang::CompilerInstance*) (/srv/tools/clang_9.x/bin/clang+0xc2b4d8)
 #14 0x000000000060de69 cc1_main(llvm::ArrayRef<char const*>, char const*, void*) (/srv/tools/clang_9.x/bin/clang+0x60de69)
 #15 0x000000000060b680 main (/srv/tools/clang_9.x/bin/clang+0x60b680)
 #16 0x00007fbb9e2963d5 __libc_start_main /usr/src/debug/glibc-2.17-c758

The solution is to use a std::string instead for `suffix`.

(cherry picked from commit 2254f23)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants