Skip to content
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

report error when cast bigint to datetime #12064

Closed
wants to merge 1 commit into from

bvt case

8a1f385
Select commit
Loading
Failed to load commit list.
Closed

report error when cast bigint to datetime #12064

bvt case
8a1f385
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Oct 11, 2023 in 1s

9 potential rules

Rule: Automatic merge on approval (queue)

  • #approved-reviews-by>=1
  • any of: [:twisted_rightwards_arrows: queue conditions]
    • all of: [:pushpin: queue conditions of queue default]
      • #approved-reviews-by>=1 [🛡 GitHub branch protection]
      • branch-protection-review-decision=APPROVED [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-neutral=multi cn e2e bvt test docker compose(PUSH)
        • check-skipped=multi cn e2e bvt test docker compose(PUSH)
        • check-success=multi cn e2e bvt test docker compose(PUSH)
      • any of: [🛡 GitHub branch protection]
        • check-neutral=multi cn e2e bvt test docker compose(PESSIMISTIC)
        • check-skipped=multi cn e2e bvt test docker compose(PESSIMISTIC)
        • check-success=multi cn e2e bvt test docker compose(PESSIMISTIC)
      • any of: [🛡 GitHub branch protection]
        • check-neutral=e2e BVT Test on Linux/x64(LAUNCH)
        • check-skipped=e2e BVT Test on Linux/x64(LAUNCH)
        • check-success=e2e BVT Test on Linux/x64(LAUNCH)
      • any of: [🛡 GitHub branch protection]
        • check-neutral=Multi-CN e2e BVT Test on Linux/x64(LAUNCH, PROXY)
        • check-skipped=Multi-CN e2e BVT Test on Linux/x64(LAUNCH, PROXY)
        • check-success=Multi-CN e2e BVT Test on Linux/x64(LAUNCH, PROXY)
      • any of: [🛡 GitHub branch protection]
        • check-neutral=e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC)
        • check-skipped=e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC)
        • check-success=e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC)
      • any of: [🛡 GitHub branch protection]
        • check-neutral=Compatibility Test on Linux/x64(LAUNCH)
        • check-skipped=Compatibility Test on Linux/x64(LAUNCH)
        • check-success=Compatibility Test on Linux/x64(LAUNCH)
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
      • #review-threads-unresolved=0 [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success=SCA Test on Ubuntu/x86
        • check-neutral=SCA Test on Ubuntu/x86
        • check-skipped=SCA Test on Ubuntu/x86
      • any of: [🛡 GitHub branch protection]
        • check-success=UT Test on Ubuntu/x86
        • check-neutral=UT Test on Ubuntu/x86
        • check-skipped=UT Test on Ubuntu/x86
  • #changes-requested-reviews-by<=0
  • -draft [:pushpin: queue requirement]
  • -label=do-not-merge/wip
  • -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]

Rule: Auto update branch (update)

  • -closed [:pushpin: update requirement]
  • created-at>=00:10 ago
  • #commits-behind>0 [:pushpin: update requirement]

Rule: label for Bug (label)

  • body~=(?im)- \[x\] BUG

Rule: label for Feature (label)

  • body~=(?im)- \[x\] Feature

Rule: label for Improvement (label)

  • body~=(?im)- \[x\] Improvement

Rule: label for Documentation (label)

  • body~=(?im)- \[x\] Documentation

Rule: label for Test and CI (label)

  • body~=(?im)- \[x\] Test and CI

Rule: label for Code Refactoring (label)

  • body~=(?im)- \[x\] Code Refactoring

Rule: label for API-change (label)

  • body~=(?im)- \[x\] API-change

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com