rabbitmq-server: 4.0.2 → 4.0.4

ChangeLog for 4.0.3
ChangeLog for 4.0.4

Also:

The package uses the latest supported Erlang version (Erlang 27)

The package is moved to by-name

Built on platform(s)

[X] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[X] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage

[X] Tested basic functionality of all binary files (usually in ./result/bin/)

25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 358653

x86_64-linux

:white_check_mark: 3 packages built:

rabbitmq-server
rabbitmq-server.doc
rabbitmq-server.man

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 358653

aarch64-linux

:white_check_mark: 3 packages built:

rabbitmq-server
rabbitmq-server.doc
rabbitmq-server.man

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4894

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 358653

x86_64-linux

:white_check_mark: 3 packages built:

rabbitmq-server
rabbitmq-server.doc
rabbitmq-server.man

aarch64-linux

:white_check_mark: 3 packages built:

rabbitmq-server
rabbitmq-server.doc
rabbitmq-server.man

x86_64-darwin

:white_check_mark: 3 packages built:

rabbitmq-server
rabbitmq-server.doc
rabbitmq-server.man

aarch64-darwin

:white_check_mark: 3 packages built:

rabbitmq-server
rabbitmq-server.doc
rabbitmq-server.man


Support for specifying runtimeClassName in model resource

Not sure sure if i'm doing something wrong or theres an easier workaround for this.
I'm using the nvidia gpu operator in a very vanilla config.
This results in the generation of several runtimeClass resources.
In this configuration, where one component of the nvidia gpu operator is handling the driver instead of me manually installing the driver on the host, it seems that pods which want to have access to the GPU require runtimeClassName: nvidia to be in the pod spec.
I'm not sure if I'm missing it or not but I dont see a way to specify runtimeClassName in the CRD for a model.  Thanks for all the hard work!  I'd really like to use your project!

Hi, thanks for the issue. And thanks for the in-detailed statement.
Indeed, after a brief read through documentations, I found runtimeClass requires extra parameters with no workaround (retricted by immutable of Pods, too, so no directly modifications are allowed.)
I will add one for you ASAP today. Stay tuned.


cirq.measure_pauli_string rejects negated pauli strings

import cirq
cirq.measure_single_paulistring(-cirq.Y(cirq.LineQubit(0))*cirq.Y(cirq.LineQubit(1)), key='1')

This should be fairly straightforward to fix.  We raise an error if the pauli string is does not have a coefficient of 1 here - https://github.com/quantumlib/Cirq/blob/9a1609ce8800ed1aa82bbf6261f5f7b8a41b81cf/cirq-core/cirq/ops/measure_util.py#L55
However, the underlying PauliMeasurementGate does support DensePauliStrings with coefficient +1 and -1. So, instead of passing pauli_observable.values() to construct the PauliMeasurementGate, we can just pass pauli_observable.dense(pauli_observable.keys()) and then remove the check for coefficient being exactly +1.
https://github.com/quantumlib/Cirq/blob/9a1609ce8800ed1aa82bbf6261f5f7b8a41b81cf/cirq-core/cirq/ops/measure_util.py#L60

I can take this issue.


[bug] Undefined "data" field on StreamingV2GetRulesResult

The "data" field on StreamingV2GetRulesResult isn't defined as optional, however, if you have no rules set (therefore no rules returned in response) then the data field is undefined. Not sure if the type definition is wrong or if an empty array should be returned when there's no rules.

Hi,
Many endpoints behave like this.
I've noticed this after first release of the lib (because Twitter do not document it).
Making data property optional is a major breaking change and can be painful in 95% of use-cases, so it's untouched for now.

Appreciate the explanation. I'll just make sure to always check the data property to see if it's undefined


Jelly file association disappeared

Version report

What Operating System are you using (both controller, and any agents involved in the problem)?

MacOS
Reproduction steps

Update to latest intellij from a previous version
Update stapler plugin to latest version (2.0.2)
Open a jelly file

Results
Expected result:
Syntax highlighting
Actual result:
Rendered as a text file
Work around
I was able to add an association myself via editor settings:
Editor => File types => Jelly
Add *.jelly
cc @duemir

Same as #58. I thought I fixed it :( Some kind of edge case, probably. It still uses deprecated API after all.

Will see what happens when I upgrade my other machine, been holding off though as I had a couple of other unrelated issues with the upgrade too

In #71 I have reverted the workaround that I did to "fix" #58. We should be back to old behaviour. 2021.2 no association between *.jelly and XML file type. 2021.1 and 2021.3 and newer should have it.
If you have manually added *.jelly to XML file type, it will override whatever plugin declares as far as I understand.


Invalid Character

Hey all,
I tried making an app with a dash in the name time-clock and didn't realize the dash was killing newclear for a while. The error on rake newclear looked like this:
KC:time-clock$ rake newclear
================================================================================
A new version of RubyMotion is available. Run `sudo motion update' to upgrade.
================================================================================

Cleaning Project...
fatal: Not a git repository (or any of the parent directories): .git
    Delete ./build
    Delete /Users/KC/Library/RubyMotion/build

Bundling...

Setting up gradle automation dependencies...
fatal: Not a git repository (or any of the parent directories): .git
 [warning] To avoid issues you should install `Extras/Android Support Repository`. Open the gui to install it : /Users/KC/.rubymotion-android/sdk/tools/android
 [warning] To avoid issues you should install `Extras/Google Repository`. Open the gui to install it : /Users/KC/.rubymotion-android/sdk/tools/android
Building project...
for device
================================================================================
A new version of RubyMotion is available. Run `sudo motion update' to upgrade.
================================================================================

fatal: Not a git repository (or any of the parent directories): .git
    Create ./build/Development-16/AndroidManifest.xml
    (skipping file '.gitkeep' due to ANDROID_AAPT_IGNORE pattern '.*')
    (skipping file '.gitkeep' due to ANDROID_AAPT_IGNORE pattern '.*')
./build/Development-16/AndroidManifest.xml:2: Tag <manifest> attribute package has invalid character '-'.
rake aborted!
Command failed with status (1): ["/Users/KC/.rubymotion-android/sdk/build-t...]
/Library/RubyMotion/lib/motion/project/template/android.rb:188:in `block in <top (required)>'
/Library/RubyMotion/lib/motion/project/template/android.rb:755:in `block (2 levels) in <top (required)>'
/Library/RubyMotion/lib/motion/project/template/android.rb:755:in `each'
/Library/RubyMotion/lib/motion/project/template/android.rb:755:in `block in <top (required)>'
/Users/KC/.rvm/gems/ruby-2.1.2/bin/ruby_executable_hooks:15:in `eval'
/Users/KC/.rvm/gems/ruby-2.1.2/bin/ruby_executable_hooks:15:in `<main>'
Tasks: TOP => build
(See full trace by running task with --trace)

I can see it now, but I first updated ruby motion, then I thought it might be the fatal thing about it not being a git repository because of the warnings:
[warning] To avoid issues you should install `Extras/Android Support Repository`. Open the gui to install it : /Users/KC/.rubymotion-android/sdk/tools/android
[warning] To avoid issues you should install `Extras/Google Repository`. Open the gui to install it : /Users/KC/.rubymotion-android/sdk/tools/android

After installing those I was still getting fatal not a git repo . . . so I created one and then I get
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:

so I add all and commit it and finally I get
KC:time-clock$ rake newclear

Cleaning Project...
    Delete ./build
    Delete /Users/KC/Library/RubyMotion/build
    Delete vendor/Gradle

Bundling...

Setting up gradle automation dependencies...
Building project...
for device
    Create ./build/Development-16/AndroidManifest.xml
    (skipping file '.gitkeep' due to ANDROID_AAPT_IGNORE pattern '.*')
    (skipping file '.gitkeep' due to ANDROID_AAPT_IGNORE pattern '.*')
./build/Development-16/AndroidManifest.xml:2: Tag <manifest> attribute package has invalid character '-'.
rake aborted!
Command failed with status (1): ["/Users/KC/.rubymotion-android/sdk/build-t...]
/Library/RubyMotion/lib/motion/project/template/android.rb:188:in `block in <top (required)>'
/Library/RubyMotion/lib/motion/project/template/android.rb:758:in `block (2 levels) in <top (required)>'
/Library/RubyMotion/lib/motion/project/template/android.rb:758:in `each'
/Library/RubyMotion/lib/motion/project/template/android.rb:758:in `block in <top (required)>'
/Users/KC/.rvm/gems/ruby-2.1.2/bin/ruby_executable_hooks:15:in `eval'
/Users/KC/.rvm/gems/ruby-2.1.2/bin/ruby_executable_hooks:15:in `<main>'
Tasks: TOP => build
(See full trace by running task with --trace)

And this one tipped me off that the line before rake aborted! is the issue :blush:
I'm telling you all this so that:

I can request some kind of error checking / fixing like bluepotion create time-clock  renames the app to time_clock or something like that.

I can demonstrate the way my brain approached the stack trace in case it's useful in designing the error process.

Thanks for the great gem!
-KC

Oi!  That's a crazy one! Good find.


Updating the Gaming on Google Cloud gHack to use Space Agon

Changes to the Cloud Gaming gHack, updating the readme, challenges, and solutions guide. The hack will now have participants deploying Space Agon with Agones and setting up Open Match.
Github Pages: https://thelancelord.github.io/cloud-hackathons/hacks/gaming-on-gcp/

@gfilicetti @meken

Changes should all be made, ready for another round of checks!


Removal of issue label not reflected in webhook POST data

Gitea version (or commit ref):

1.8.3

Operating system:

Alpine linux  v3.10 hardened

Database

[x] MySQL (mariadb actually)

Can you reproduce the bug at https://try.gitea.io:

[x] Yes (https://try.gitea.io/testLabels/testLabels/issues/1)

How to reproduce
Step 1 Add label to issue
result: Webhook posts the issue data, including the right label information (the recently added label)
Step 2: Remove that same label (BUG)
result: Webhook posts the issue data, but this still includes the recently removed label! I'm expecting the webhook to remove the removed label from it's post data (issue.label).
Step 3: generate another webhook (like adding a comment)
result: The webhook provides the right label data again. So the label removed in step2 is not included in  issue.labels

It looks like Gitea is sending it's webhook POST before it has actually updated the values internally. Because of this, te Gitea webhook is sending out-of-date information. A simple workaround is to request the labels when receiving the label_updated action, but that kind of defeats the purpose.
EDIT: this link actually shows the requests Gitea sent. Nice!

@dodedodo I want to know more detail about this issue and the repository on try site has been deleted.

Which gitea version were you using?
Which type webhook did you tested?

I posted a similar issue (#7838). I think there are some cases for webhooks that the code write the new data to database, but the data served to the webhook is the old data. It could be solved by either writing the data to the structure as well before handling the webhook, or to reload the data from the database.

@davidsvantesson With the recent code refactoring that @lunny has been doing, I think this particular scenario should have been eliminated because one of the things he did was to move the webhook call outside of the model transaction. Unless of course some webhooks still require refactoring. All of this has been done in the 1.11 branch, however.

@guillep2k I have not worked on webhooks lately, might be that many update issues are solved.

Hi all,
This should be fixed in 1.13.
https://github.com/go-gitea/gitea/pull/13007
KR
Alex


PR: Enable remote debugging automatically upon launch of the application

I've had issues recently where I wanted debugging enabled upon launch of the application.  This patch does just that.
From AppDelegate.m, the end developer can change one boolean on the RootView initialization.
  RCTRootView *rootView = [[RCTRootView alloc] initWithBundleURL:jsCodeLocation
                                                withDebugEnabled:NO  // YES to enable debugging upon app launch
                                                      moduleName:@"UIExplorerApp"
                                                   launchOptions:launchOptions];

This Boolean cascades the RootView into the Bridge instantiation,
- (instancetype)initWithBundleURL:(NSURL *)bundleURL
                  withDebugEnabled:(BOOL)debugEnabled
                       moduleName:(NSString *)moduleName
                    launchOptions:(NSDictionary *)launchOptions
{
  RCTBridge *bridge = [[RCTBridge alloc] initWithBundlePath:bundleURL.absoluteString
                                           withDebugEnabled:debugEnabled
                                             moduleProvider:nil
                                              launchOptions:launchOptions];
  return [self initWithBridge:bridge
                   moduleName:moduleName];
}

where if YES, the executor class is configured  as
self.executorClass = NSClassFromString(@"RCTWebSocketExecutor");
- (instancetype)initWithBundlePath:(NSString *)bundlePath
                  withDebugEnabled:(BOOL)debugEnabled
                    moduleProvider:(RCTBridgeModuleProviderBlock)block
                     launchOptions:(NSDictionary *)launchOptions
{
  if ((self = [super init])) {
    _bundlePath = bundlePath;
    _moduleProvider = block;
    _launchOptions = launchOptions;
#if DEBUG
    if (debugEnabled == YES) {
      self.executorClass = NSClassFromString(@"RCTWebSocketExecutor");
    }
#endif
    [self setUp];
    [self bindKeys];
  }

  return self;
}

For anyone at FB looking at this, what could I have done differently not to break the TravisCI build?
The log states:
"No output has been received in the last ... minutes, this potentially indicates a stalled build or something wrong with the build itself.
"```

What is the use-case for this? Make it easier to develop apps? If so, I'd suggest making "is debugger enabled" a setting that survives app restarts.

I submitted #652 a couple days ago which lets you specify the primary executor. So one thing you could do is create a bridge that defaults to the WebSocketExecutor:
[[RCTBridge alloc] initWithBundlePath:bundlePath
                   moduleProvider:block
                    launchOptions:launchOptions
                    executorBlock:^{
                 Class executorClass = NSClassFromString(@"RCTWebSocketExecutor");
                 if (!executorClass) {
                   RCTLogError(@"WebSocket debugger is not available. Did you forget to include RCTWebSocketExecutor?");
                   executorClass = [RCTContextExecutor class];
                 }
                 return [[executorClass alloc] init];
               }
               debugExecutorBlock:nil];

One thing that's nice about this approach is you can configure the WebSocketExecutor to support using the Chrome debugger while running the app on your phone.

@frantic , the use case is simple.
1 Run my app
2 Enable debug (key strokes, clicks, etc)
3 Critical condition hit, App shits the bed
This PR simply pulls step 2 out of the loop, which is really 2 steps.
Think about what life would be like if you were a web developer that had to reopen dev tools upon every page refresh.  This PR is synonymous to keeping the web debug tools open & on the ready on every page refresh.
@ide,
This PR, in contrast to what you've posted, is end-developer friendly. It's configured so that developers can change a simple boolean without having to know what a WebSocketExecutor is =).   They can also do it from a higher-level of exposure (AppDelegate.m) instead of diving into the core React framework.

@jaygarcia - how about the suggestion I made with remembering the last executor? I think this would be even more friendly and you don't have to remember to change your code before shipping to the appstore

@frantic, that is probably the best idea/pattern, but we'd still need the #if DEBUG/#endif around it.  That way when it is shipped to the app store, and the developer forgets to turn it off, it will never be enabled.
Want me to push that into the Info.plist? That's a trivial action. =)

@frantic gentle nudge. =)

I imagine that this code is very outdated, given lots of changes since this PR nearly two weeks ago.  I remain interested in making this happen, even if it requires refactoring on my part.  =)

One major change that landed recently is that the executor and debug mode, etc. are all controlled via the bridge now, rather than the root view.
We're going to be doing some more refactoring of this soon, so I'd probably hold off on trying to update this for now.
As @frantic suggests, the eventual solution will probably be for the app to simply remember it's last state, so if you set debug mode in the dev menu and then do a cold start, it should still be in debug mode.

As @frantic suggests, the eventual solution will probably be for the app to simply remember it's last state, so if you set debug mode in the dev menu and then do a cold start, it should still be in debug mode.

It looks like you folks got around to doing this, works great, so I will close this


Update issue query

The current issue query can fail under certain circumstances. The backend team recommends updating it to:
query issueByNumber($owner: String!, $repo: String!, $number: Float!) {
  Issue(state: closed, number: $number, filter: {repo: {name: $repo, owner: $owner}}) {
    number
    title
    labels {
      name
    }
    repo {
      url
      owner
      name
      org {
        provider {
          url
          apiUrl
        }
      }
    }
    closedBy {
      login
      name
      emails {
        address
      }
    }
  }
}

The filter argument is new, so the schema needs updating in atomist-skills/skill and then that updated here.

Schema update in @atomist/skill: https://github.com/atomist-skills/skill/pull/202

Schema update in @atomist/skill: https://github.com/atomist-skills/skill/pull/202


Release Tag?

There's no release tag(s) for this library, so the only thing you can do in Composer is have an open-ended dependency or specify an exact commit...
https://packagist.org/packages/adobe-marketing-cloud/marketing-cloud-php-sdk
Could you add release tags? Preferablly compatible with Semver?
http://semver.org
Thanks!

We've tagged the updated version as well as the legacy version. Please use 2.0.2 for the latest release. Thanks for the feedback!