Swift 6 concurrency check not complaining about Objc block property

Description
I work on an ObjC framework which contains an Option class with a beforeSend property block callback like so (names changed for simplicity):
typedef Event *_Nullable (^ BeforeSendCallback)(Event *_Nonnull event);

@interface Option
@property (nonatomic, copy) BeforeSendCallback beforeSend;
//... More properties
@end

The beforeSend callback can be called from any thread, and when we do call it from a thread other than the one the user used to create the option object, the app crashes with EXC_BREAKPOINT, if the user didn't mark the closure with @Sendable.
I would think that the compiler should complain about this in Swift 6 mode. Am I missing something?
Reproduction
This crashes in runtime when beforeSend is used in a background thread:
MySDK.start { option in
 option.beforeSend = { event in
     //process event
     return event
  }
}

This does not crashes in runtime:
MySDK.start { option in
 option.beforeSend = { @Sendable event in
     //process event
     return event
  }
}

Expected behavior
I would expected the compiler to complain about the missing @Sendable in the closure or any other error.
Environment
swift-driver version: 1.115 Apple Swift version 6.0.2 (swiftlang-<IP_ADDRESS>.2 clang-16<IP_ADDRESS>)
Target: arm64-apple-macosx15.0
Additional information
No response

i'm not entirely sure what the expected behavior is in this case, but you may find this section of the Swift 6 migration guide of interest. in particular, there are some annotations that can be applied to objc code to communicate the intended swift concurrency behaviors of an API.


improve two-level-select enormously with defining join-field as top-level and prevent changing value of thar  toplevel

Is your feature request related to a problem? Please describe.
Case of Orders for a certain Category and then adding Orderlines where you can only add IItems from that same Category as set in the Order. So the Order shouls set  the top-level field of the two-levl-select in the linked Orderlines.
And users should not be able to change to top-level of the two-level-select.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

I think this can be done using an form action. I used it and it works well. There is a help menu on the Edit view that describes how to create a form action.
From the release of 0.9.0
It is now also possible to use an action inside a form to change the field contents. This is done by returning set_fields from an action. You can use this to fill in a selected template or to set calculated (but editable) values

hello @cfredericksen,
Thanks for helping me with this.
I have added a form action on my edit view to prefill a Select fieldtype for ordered_item but alas with no the result I hoped for.

It shows all the Items in my table instead of test-texts vCPU02 and vCPU03. So I guess I am making some mistake here. Can you give a clue?
tia
Folkert

Here is my example, hopefully this will help.
I have a "New Job" Edit View.
In this Edit View, I have a 2 Fields with a select view.
When a user selects "Client", it will limit the list for possible jobs.
To do that that:
I add code, see below, to the Where box in the field of a select view (if you click the ? next to Where, it will show the possible choices)
client == $client

Keep in mind, I have two tables connected via keys that make the lookup possible.
Also, often times when I am having trouble its bc I structured my table relationship incorrectly.


Run Chrome in headless mode

Though it is not difficult to define something like HeadlessChromeFactory, it would be nice if there is an out-of-the-box support of headless mode.

Hi @hirofumi,
Thank you so much for this. ChromeFactory and ChromeInfo now both accept a ChromeOptions parameters, and it is now possible to set headless to true.
Best.

I'm glad to hear that. Thank you for letting me know!

And thanks so much for your review!


Make expr non-Optional in irast.Set

The bulk of the work to make this happen was done in #6938
(introducing TypeRoot) and #7090 (moving Pointer into expr).
The final pieces are making EmptySet an Expr instead of a Set subclass
and getting rid of the cases where we "clear" expressions out of a
Set.
The biggest benefit here is that the meaning of a Set is much clearer
now, but there are some nice direct benefits too.
This lets have fully table dispatched set compilation in several places
now.
_get_set_rvar, which was 155 lines long in 2.x, is now finally completely
gone!
_compile_set_in_singleton_mode is also gone, replaced with simply
compiling the set's expression.
Typechecker error messages involving SetE are also much nicer now.

Depends on https://github.com/edgedb/edgedb/pull/7114


Bug fixes for resource names

PTAL

They are being tested by the change in library.proto to use a qualified and unqualified ResouceSet name. The GapicCodeGeneratorAnnotationsTest wouldn't pass with the changes in library.proto, and after half-way tweaking it would read Book as a messageType containing a resourceSet and use the containing ResourceSet within Book.


[python] Clarify test_update_dataframe.py and _arrow_types.py

Issue and/or context: Pre-PR to facilitate #2518
Changes: Just renames and comments -- zero functional changes
Notes for Reviewer:

Thanks for all the many improvements via #2529 @ryan-williams ! :)


Text labels not supported on Opera Mini

I'm drawing a simple chart with no text labels at all, and I'm still getting errors when using it on Opera Mini since its trying to call measureText.
Supposedly the error comes from this line:
// around line 1535
var firstWidth = this.ctx.measureText(this.xLabels[0]).width,

We need a test case for this. Opera is now based on Blink which supports measureText


Blur relates from frame modifier. Some values cause entire view to disappear

We have gradient view in the project example. If I change only one line of code to make it rect not the square, the view completely disappears:
var gradient: some View {
        LinearGradient(colors: [Color("Color 1"), Color("Color 2"), Color("Color 3")], startPoint: .top, endPoint: .bottom)
            //.aspectRatio(1.0, contentMode: .fit)
            .frame(width: 256, height: 482) <<--- 482 cause view to disappear, while 481 still works fine
            .clipShape(.rect(cornerRadius: 57/2))
            .padding(32)
            .background(Color("Black"))
            .glur(offset: 0.3, interpolation: 0.5, radius: 32.0)
    }

Hey there, @denandreychuk!
This issue is concerning, and seems to be a limitation with how Apple is interfacing SwiftUI with Metal. Apparently, it fails to convert a view into a texture to be used in Metal when either dimension go past 545 points. In the case above, 482 plus 64 points of padding equals 546 which causes a texture conversion error to trigger.
This limit seems to be weirdly low — on Mac, for example, I was able to run the code with no issues. I'll file a radar on it through Feedback Assistant and see how it goes.

I've looked deeper into this and the issue apparently is exclusive to apps running on the iOS simulator. I submitted an issue on feedback assistant (FB13604685) with these specific details — let's see if it gets fixed!
As it's not an urgent issue that directly impacts the quality of the codebase, I'll close this for now and add a disclaimer in the README.

Oh, I see! Thanks for looking into this, @joogps!


Can't assert Rails.logger call when migrating from Rails 4 to Rails 5

Rails <IP_ADDRESS>
rspec-rails 3.5.2
rspec-mocks 3.5.0
Ruby 2.3.1
I am currently migrating our test suite to Rails 5 and am almost done except for two more failing specs. The current spec works on Rails 4 but fails with Rails 5:
it 'logs the sending of the mail' do
  expect(Rails.logger).to receive(:info).with("Mail sent to #{email} of #{owner_name}")
  post :create, params: valid_params
end

Rails 5 throws the following error:
[ActiveJob] [ActionMailer::DeliveryJob] [3f947144-d89b-494c-83d5-ece711d18f04] Could not log "perform_start.active_job" event. RSpec::Mocks::MockExpectationError: #<ActiveSupport::Logger:0x007fbf30fc3090 @progname=nil, @level=0, @default_formatter=#<Logger::Formatter:0x007fbf30fc2ff0 @datetime_format=nil>, @formatter=#<ActiveSupport::Logger::SimpleFormatter:0x007fbf2fdcb068 @datetime_format=nil, @thread_key="activesupport_tagged_logging_tags:70229559236660">, @logdev=#<Logger::LogDevice:0x007fbf30fc2e38 @shift_size=nil, @shift_age=nil, @filename=nil, @dev=#<File:/Users/user/Development/Redacted/log/test.log>, @mon_owner=nil, @mon_count=0, @mon_mutex=#<Thread::Mutex:0x007fbf30fc2cd0>>, @local_levels=#<Concurrent::Map:0x007fbf30fc2b90 entries=0 default_proc=nil>> received :info with unexpected arguments
  expected: ("Mail sent to<EMAIL_ADDRESS>of Hardy-Döring")
       got: (nil)

It logs correctly when I comment out the expect() line. But that renders the spec useless.
This is the strack trace I got:
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-support-3.5.0/lib/rspec/support.rb:87:in `block in <module:Support>'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-support-3.5.0/lib/rspec/support.rb:96:in `notify_failure'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-mocks-3.5.0/lib/rspec/mocks/error_generator.rb:327:in `notify'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-mocks-3.5.0/lib/rspec/mocks/error_generator.rb:311:in `__raise'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-mocks-3.5.0/lib/rspec/mocks/error_generator.rb:55:in `raise_unexpected_message_args_error'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-mocks-3.5.0/lib/rspec/mocks/message_expectation.rb:501:in `raise_unexpected_message_args_error'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-mocks-3.5.0/lib/rspec/mocks/proxy.rb:187:in `message_received'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-mocks-3.5.0/lib/rspec/mocks/proxy.rb:326:in `message_received'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-mocks-3.5.0/lib/rspec/mocks/method_double.rb:77:in `proxy_method_invoked'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-mocks-3.5.0/lib/rspec/mocks/verifying_proxy.rb:156:in `proxy_method_invoked'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-mocks-3.5.0/lib/rspec/mocks/method_double.rb:64:in `block (2 levels) in define_proxy_method'
2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/log_subscriber.rb:93:in `info'
2.3.1/lib/ruby/gems/2.3.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/log_subscriber.rb:18:in `process_action'
2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/subscriber.rb:95:in `finish'
2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/log_subscriber.rb:83:in `finish'
2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/fanout.rb:102:in `finish'
2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/fanout.rb:46:in `block in finish'
2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/fanout.rb:46:in `each'
2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/fanout.rb:46:in `finish'
2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:42:in `finish_with_state'
2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:27:in `ensure in instrument'
2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:27:in `instrument'
2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `instrument'
2.3.1/lib/ruby/gems/2.3.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
2.3.1/lib/ruby/gems/2.3.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/params_wrapper.rb:248:in `process_action'
2.3.1/lib/ruby/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
2.3.1/lib/ruby/gems/2.3.0/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:126:in `process'
2.3.1/lib/ruby/gems/2.3.0/gems/actionview-<IP_ADDRESS>/lib/action_view/rendering.rb:30:in `process'
2.3.1/lib/ruby/gems/2.3.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:190:in `dispatch'
2.3.1/lib/ruby/gems/2.3.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/test_case.rb:532:in `process'
2.3.1/lib/ruby/gems/2.3.0/gems/rails-controller-testing-1.0.1/lib/rails/controller/testing/template_assertions.rb:61:in `process'
2.3.1/lib/ruby/gems/2.3.0/gems/devise-4.2.0/lib/devise/test/controller_helpers.rb:33:in `block in process'
2.3.1/lib/ruby/gems/2.3.0/gems/devise-4.2.0/lib/devise/test/controller_helpers.rb:100:in `catch'
2.3.1/lib/ruby/gems/2.3.0/gems/devise-4.2.0/lib/devise/test/controller_helpers.rb:100:in `_catch_warden'
2.3.1/lib/ruby/gems/2.3.0/gems/devise-4.2.0/lib/devise/test/controller_helpers.rb:33:in `process'
2.3.1/lib/ruby/gems/2.3.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/test_case.rb:629:in `process_with_kwargs'
2.3.1/lib/ruby/gems/2.3.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/test_case.rb:389:in `post'
2.3.1/lib/ruby/gems/2.3.0/gems/rails-controller-testing-1.0.1/lib/rails/controller/testing/integration.rb:12:in `block (2 levels) in <module:Integration>'
/Users/user/Development/Redacted/spec/controllers/test_accounts_controller_spec.rb:184:in `block (4 levels) in <top (required)>'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example.rb:254:in `instance_exec'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example.rb:254:in `block in run'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example.rb:496:in `block in with_around_and_singleton_context_hooks'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example.rb:453:in `block in with_around_example_hooks'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/hooks.rb:464:in `block in run'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/hooks.rb:604:in `block in run_around_example_hooks_for'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example.rb:338:in `call'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-rails-3.5.2/lib/rspec/rails/example/controller_example_group.rb:191:in `block (2 levels) in <module:ControllerExampleGroup>'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example.rb:443:in `instance_exec'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example.rb:443:in `instance_exec'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/hooks.rb:375:in `execute_with'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/hooks.rb:606:in `block (2 levels) in run_around_example_hooks_for'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example.rb:338:in `call'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-rails-3.5.2/lib/rspec/rails/adapters.rb:127:in `block (2 levels) in <module:MinitestLifecycleAdapter>'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example.rb:443:in `instance_exec'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example.rb:443:in `instance_exec'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/hooks.rb:375:in `execute_with'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/hooks.rb:606:in `block (2 levels) in run_around_example_hooks_for'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example.rb:338:in `call'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/hooks.rb:607:in `run_around_example_hooks_for'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/hooks.rb:464:in `run'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example.rb:453:in `with_around_example_hooks'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example.rb:496:in `with_around_and_singleton_context_hooks'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example.rb:251:in `run'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example_group.rb:627:in `block in run_examples'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example_group.rb:623:in `map'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example_group.rb:623:in `run_examples'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example_group.rb:589:in `run'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example_group.rb:590:in `block in run'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example_group.rb:590:in `map'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example_group.rb:590:in `run'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example_group.rb:590:in `block in run'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example_group.rb:590:in `map'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/example_group.rb:590:in `run'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/runner.rb:113:in `block (3 levels) in run_specs'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/runner.rb:113:in `map'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/runner.rb:113:in `block (2 levels) in run_specs'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/configuration.rb:1835:in `with_suite_hooks'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/runner.rb:112:in `block in run_specs'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/reporter.rb:77:in `report'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/runner.rb:111:in `run_specs'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/runner.rb:87:in `run'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/runner.rb:71:in `run'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/lib/rspec/core/runner.rb:45:in `invoke'
2.3.1/lib/ruby/gems/2.3.0/gems/rspec-core-3.5.4/exe/rspec:4:in `<top (required)>'
2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:287:in `load'
2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:287:in `block in load'
2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:259:in `load_dependency'
2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:287:in `load'
2.3.1/lib/ruby/gems/2.3.0/gems/spring-commands-rspec-1.0.4/lib/spring/commands/rspec.rb:18:in `call'
2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
-e:1:in `<main>'

I'm however not sure if it's rspec-mocks' fault or if something changed in Rails 5. I could however not find anything in the Rails 5 change logs about changes related to ActionMailer or ActionSupport::Logger.

Thats a funny error, is your mail being sent asynchronously? It looks like the expectation is failing because the mail hasn't been sent, when is causing the job to fail in the background picking up the spec.

Yep, I send it using .perform_later with ActiveJob and sucker_punch as an adapter.
And yeah, I also think that because it doesn't catch the log entry, then fails to send the mail altogether. At least once it didn't get nil but Started processing using MailsController.... So it might be the part about it being asynchronous.
But according to this entry in the README of sucker_punch it should be synchronous during the test.

Try adding an allow(Rails.logger).to receive(:info) before the expect

That works, thanks! But... why? :D

But... why?

You've set a specific expectation, but doing something different, this is the expected behaviour of RSpec. You need to tell it you also don't care about other calls to that method, which is what the allow statement is doing.
Why does it work on Rails 4? Probably because before Rails wasn't also using the logger to tell you stuff about active job, probably :)

I see, thank you for the explanation.

My mistake MyJob.new(argument1, argument2).perform_later
The right way MyJob.perform_later(argument1, argument2)


Enable OSX builds

let's try this again. We had seg-faults in #10 but maybe things have changed...
addresses #9

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Stuck due to https://github.com/UCL/STIR/issues/531.

trying again with #33


tint and alpha corners are incorrect

It appears that tintTopRight, tintTopLeft, etc. and alphaTopRight.. etc are not pointing at the correct corners visually.

I've got a live example here:
https://jsfiddle.net/02sdm0tc/5/

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch and will be part of the next release. If you get time to build and test it for yourself we would appreciate that.

built and tested, works as expected.  👍


small optimizations for XQUIC

Hello everyone. Here I have prepared a small request containing some optimizations for the xquic implementation, which, it seems to me, have a right to exist. I will be glad to receive feedback.

Best regards, Pavel

Hello !
I tried to correct all the comments, please look at it in your free time


fixing hook failure behaviour, solves #534

wip

@dasilvacontin Why is this a PR if it's a WIP? :smile:

Never mind, I guess I got too excited or something. :sweat_smile:

i'm fine with it, just put wip in the title or something and make it clear that it's not ready to go. it's a good way to get feedback before wasting a bunch of time on something that's not gonna get in.

@travisjeffery that was my initial intention, to show I'm actively working on it and maybe get some comments, but I'm still trying to figure out stuff.


⚠ Bofrost.de has degraded performance

In 17f6554, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1067 ms

Resolved: Bofrost.de performance has improved in ea4dff2 after 6 minutes.


Removing not necessary public imports

:tophat: What? Why?
Moving to .m file QuartzCore and runtime imports.
:ghost: GIF

:+1:

lol, let's import QuartzCore in the whole app xD

:+1:


added route for updating users and test to reflect changes

hey @pollygee I saw this up on github and I figured I'd contribute since I haven't written any ruby in a while. Just implemented a rails method for updating a users password in the database, nothing huge. Made for this ticket: https://github.com/rubyforgood/pantry_scheduler/issues/100

👍 🎈 🎆 Thanks @deathtenk that's awesome.  Feel free to help anytime we've still got a ways to go so we can def use the help!

I'll add you to the repo too so you can branch instead of fork.


Reduce amount of unneeded copying in ipset code.

Fixes issue #811.

No changelog updates, because there is already a changelog update saying "improve ipset performance".

One minor nitpick.  Otherwise LGTM.  Please merge when ready.

I have picked both those nits, and shall now merge.


feature: add wayland support

This resolves #51
I'm not sure if I should also update the Cargo.lock in the repo, but I guess it's ok not to do it.
Btw: Isn't the standard way of doing things in rust not shipping the Cargo.lock with library crates anyways?

Thanks for the PR.
I'm not entirely sure about the lockfile. The lock file is for the workspace and not the individual crates, which are published separately, so it shouldn't affect consumers from crates.io? I'm not sure what's a downside to having a lock file on the workspace as a whole.

@darthdeus
I think there is no real downside to this. People working on the repo with different feature flags (x11/wayland) are probably just gonna overwrite the Cargo.lock back and forth.
But since you're probably also working on unpublished executable crates in that workspace it's just fine :+1:


Add getDimensions to device and use it in gallery grid

closes #345

Integrated, thanks.
I think we should replace this workaround (async device dimensions) completely with our custom native module. I hope that we can measure the true screen dimensions in native code without problems...


Drag'n'drop support

It would be helpful if certain tasks in the explorer panel could be made also using d'n'd instead of just traditional dialogs.
We would like to support the following tasks:

[ ] replace catalogs by dragging a catalog onto another
[ ] move a catalog from one connection to another by dragging a catalog onto another connection - essentially backing up the catalog in source connection and importing the catalog to the target connection

Cc @novoj

Dragging the "backup file" from listing to connection could restore the catalog from particular backup.

Dragging backup file from computer to backup listing could open "Restored catalog from file" with the dropped file.


Ollie: Watch nafig.nafig(?:@spam.ru)?

Ollie requests the watch of the watch_keyword nafig\.nafig(?:@spam\.ru)?. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

nafig\.nafig(?:@spam\.ru)? has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Spevacus in Charcoal HQ


Add an XLA utility function HasOverlappinWindow.

This is a split from PR: https://github.com/tensorflow/tensorflow/pull/32251

Fixed the comments.

@nouiz Could you please address Ubuntu Sanity errors? Thanks!

I tried to fit it, but I don't understand why it do not like it.


Update Useful_links.md

added Development tools that help developer code easy

Before committing, please cross check whether someone has created a category for supposed tool or not. In your case, I can see JSON category and you have committed links in "Development Tools". So please move them to JSON category and request a PR again.

No his commit absolutely correct, it should go under "development tools" category only.

Ok. My bad. :)

Thank you @milaptank for sharing a list of awesome development tools!


Cleanup selection interface

Codecov Report

Merging #99 into master will decrease coverage by <.01%.
The diff coverage is 100%.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bf13b1b...d9f6225. Read the comment docs.


Using pypy3 for f6 instead of python.

https://github.com/foreshadow/atom-python-run/issues/22
I tried to comment on this thread but its closed and that's only thread I got while searching for pypy. There isn't much about pypy in google either.
I tried pypy3 {file} and pypy3.exe {file} but pypy3 uses python and pypy3.exe just closes the terminal. I'm on windows and environment variables are set up and pypy3 is working via cmd properly.

If you checked the option Pause, this package will first call python as a terminal wrapper, then your pypy3 is called by that python.
Uncheck that Pause and only pypy3 will run.

I unchecked pause but still the cmd window keeps closing. Can you please tell me exactly what I have to write in the command for f6 so that pypy3 is used.

pypy3 {file} as long as pypy3 is in your environment variable PATH.
So in this way pypy3 is called and it exits immediately (did you add a input() at the end of your code to prevent it from closing?)
Also, you may check ~/.atom/packages/atom-python-run/cp.log for more details, it was generated when you checked the option Pause before.

I wrote pypy3 {file} and pypy3 is in my environment variable Path.
And I have written an interactive script so there are a few input() statements in the code. But still the cmd window says python.exe at top. In cp.log I found the address path has 2 slashes \ after each drive or folder like F:\abc\adf...

I looked into this package's source code, which was updated by another collaborator who had deleted his github account. For the current version, no matter whether you check Pause or not, this pakage always call python to run a wrapper first, then your command pypy3 will be called by that.
Therefore, showing a python.exe is a default manner, and the double slashes is also too.
Show me all content of cp.log.

https://www.dropbox.com/s/2frocftvt9scryk/cp.log?dl=0
Here is the link for cp.log file


Add pghydro (+ misc. extension desc. updates)

Add pghydro Dockerfile and Trunk.toml

The files come pre-compiled, so no Makefile
Similar to PostGIS, pghydro has other extensions bundled in the main GitHub repository (https://github.com/pghydro/pghydro)
The other extensions depend on pghydro, and using Trunk ci workflow, the extension would build correctly, even with the output: Using extension_name: pghydro. However, installing consistently threw the following error:

Failed to fetch Trunk archive from v1 API: Found no Trunk project with name pghydro
error: Request to registry failed: No extension with the given name was found

Therefore, this PR serves to publish only pghydro to Trunk, and not its companion extensions, by including the following in the Trunk.toml file:

    cd pghydro
    set -x
    mv pghydro* /usr/share/postgresql/15/extension
    """

Closing


HDDS-11278. Move code out of Hadoop util package

What changes were proposed in this pull request?
Ozone should not add code in Hadoop packages unless necessary for extending/using non-public classes.  Using org.apache.hadoop.test and org.apache.hadoop.util can be avoided in most cases.
https://issues.apache.org/jira/browse/HDDS-11278
How was this patch tested?
CI:
https://github.com/adoroszlai/ozone/actions/runs/10235856341

Thanks @hemantk-12, @tanvipenumudy for the review.


Consider running tests under "Strict" mode instead of wrapping everything in IssuesNoWarning

Very cool repo!
I see many of your tests are wrapping everything in IssuesNoWarning. However, you may be able to ensure all tests run without warning without needing to do this by using the "Strict" option for running tests, which adds a FailOnWarning plugin to the test runner. These effectively ensures that any warning that is issued causes a test failure (other than ones being directly tested using IssuesWarings/verifyWarning and warnings you have suppressed using SuppressedWarningsFixture)
Hope that helps!

Thank you for the kind words!
We are currently working on expanding and porting the test suite to a recent redesign so this is extremely timely advice which I'll be applying.
@nurkanovic This will be included in the test updates in PR #75

Once again thank you for the advice @acampbel . This is resolved in #134


[Feature Request] Download as Ogg rather than MP3

What is the purpose of your issue?

[ ] Bug
[x] Feature Request
[ ] Question
[ ] Other

Description
spotify is native ogg, can we download as ogg so there is no chance of any quality loss

Well it will be a nope as this is not downloading any songs from Spotify itself it is downloading from YouTube so there will always be quality loss due to the way it is encoded.
If you want to get better quality music use a different program or service for your music needs I personally use this just for quickness and replace all the songs that get downloaded with better quality ones when I have time to replace them.


Connecting Applications with Services

Hello,
on the site I read
You should now be able to curl the nginx Service on <CLUSTER-IP>:<PORT> from any node in your cluster.
After following the instructions I can curl my nginx service only on that nodes where a pod is running. On the others I got
curl: (7) Failed to connect to <IP_ADDRESS> port 80: No route to host
Is that intentionally or am I missing something?
Also the DNS part does not work at all for me. After following the instructions according to the page, I only get
Server:    <IP_ADDRESS>
Address 1: <IP_ADDRESS>

nslookup: can't resolve 'my-nginx'

Since this takes that long I assume it's a timeout error.
I'm using kubernetes 1.24 on Debian Bullseye with cri-dockerd installed as mentioned on https://github.com/Mirantis/cri-dockerd
Marco

@marco74  could you  provide the task reference you are facing issue on?

Actually I do not understand your question. I already wrote that I followed the instructions on
I followed every single step on https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/
The first problem I see is that two pods have the same IP. With that they wont be able to cummunicate with each other, so what am I missing to not get the same IP on both pods (on different nodes):
marco@kn1:~/kubernetes/test1$ kubectl apply -f ./run-my-nginx.yaml
deployment.apps/my-nginx created
marco@kn1:~/kubernetes/test1$ kubectl get pods -l run=my-nginx -o wide
NAME                       READY   STATUS              RESTARTS   AGE   IP       NODE   NOMINATED NODE   READINESS GATES
my-nginx-df7bbf6f5-lsp2v   0/1     ContainerCreating   0          8s    <none>   kn6    <none>           <none>
my-nginx-df7bbf6f5-zkhvp   0/1     ContainerCreating   0          8s    <none>   kn3    <none>           <none>
marco@kn1:~/kubernetes/test1$ kubectl get pods -l run=my-nginx -o wide
NAME                       READY   STATUS    RESTARTS   AGE   IP           NODE   NOMINATED NODE   READINESS GATES
my-nginx-df7bbf6f5-lsp2v   1/1     Running   0          52s   <IP_ADDRESS>   kn6    <none>           <none>
my-nginx-df7bbf6f5-zkhvp   1/1     Running   0          52s   <IP_ADDRESS>   kn3    <none>           <none>
marco@kn1:~/kubernetes/test1$ kubectl get pods -l run=my-nginx -o yaml | grep podIP
    podIP: <IP_ADDRESS>
    podIPs:
    podIP: <IP_ADDRESS>
    podIPs:

@marco74 Could you please share which cni plugin you are using ?  i have checked in my env , pod's are getting different IP's .
kubectl get pods -l run=my-nginx -o wide
NAME                        READY   STATUS    RESTARTS   AGE   IP               NODE
my-nginx-5b56ccd65f-9b55t   1/1     Running   0          70s   <IP_ADDRESS>   workernode1
my-nginx-5b56ccd65f-x9rnz   1/1     Running   0          70s   <IP_ADDRESS>   workernode1

@Kartik494 Thank you for your answer. Different IPs must be necessary, otherwise one pod could not connect to the other because routing won't work, when the same subnets are used. Could you please drop me a thorough instruction set how to set up a cluster, starting right after OS-setup, then I could compare to find the mistake.
Usually I startup with a fresh installed Debian Bullseye on a Virtual-Box machine that's installed by a remastered netinst-image already including Docker installation.
common instruction set (for master and worker):
## install cri-dockerd
sudo apt-get -y install golang
# From: https://github.com/Mirantis/cri-dockerd
git clone https://github.com/Mirantis/cri-dockerd.git
cd cri-dockerd/
mkdir bin
cd src/
go get
go build -o ../bin/cri-dockerd
cd ..
sudo mkdir -p /usr/local/bin
sudo install -o root -g root -m 0755 bin/cri-dockerd /usr/local/bin/cri-dockerd
sudo cp -a packaging/systemd/* /etc/systemd/system
sudo sed -i -e 's,/usr/bin/cri-dockerd,/usr/local/bin/cri-dockerd,' /etc/systemd/system/cri-docker.service
cd ..

sudo systemctl daemon-reload
sudo systemctl enable cri-docker.service
sudo systemctl enable --now cri-docker.socket

## install kubernetes
sudo curl -fsSLo /usr/share/keyrings/kubernetes-archive-keyring.gpg https://packages.cloud.google.com/apt/doc/apt-key.gpg
echo "deb [signed-by=/usr/share/keyrings/kubernetes-archive-keyring.gpg] https://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee /etc/apt/sources.list.d/kubernetes.list
sudo apt-get update
sudo apt-get install -y kubelet kubeadm kubectl
sudo apt-mark hold kubelet kubeadm kubectl

sudo kubeadm --cri-socket unix:///run/cri-dockerd.sock config images pull

then on master
I initialize with:
sudo kubeadm --cri-socket unix:///run/cri-dockerd.sock init

## configure in personal directory
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

Then I either do
kubectl apply -f https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/kube-flannel.yml

or
kubectl create -f https://projectcalico.docs.tigera.io/manifests/tigera-operator.yaml

on the worker node I run the commend that the master shows me when I hit
echo "sudo `kubeadm token create --print-join-command --ttl 30m` --cri-socket=unix:///run/cri-dockerd.sock"

back on the master I can see all my workers
marco@kn1:~$ kubectl get nodes
NAME   STATUS   ROLES           AGE   VERSION
kn1    Ready    control-plane   94s   v1.24.0
kn2    Ready    <none>          30s   v1.24.0
kn3    Ready    <none>          25s   v1.24.0
kn4    Ready    <none>          21s   v1.24.0
kn5    Ready    <none>          15s   v1.24.0
kn6    Ready    <none>          11s   v1.24.0

Then I continue with https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/
marco@kn1:~$ vim run-my-nginx.yaml
marco@kn1:~$ kubectl apply -f ./run-my-nginx.yaml
kubectl get pods -l run=my-nginx -o wide
deployment.apps/my-nginx created
NAME                       READY   STATUS    RESTARTS   AGE   IP       NODE   NOMINATED NODE   READINESS GATES
my-nginx-df7bbf6f5-bxh54   0/1     Pending   0          0s    <none>   kn4    <none>           <none>
my-nginx-df7bbf6f5-rvlnd   0/1     Pending   0          0s    <none>   kn5    <none>           <none>
marco@kn1:~$ kubectl get pods -l run=my-nginx -o wide
NAME                       READY   STATUS    RESTARTS   AGE   IP           NODE   NOMINATED NODE   READINESS GATES
my-nginx-df7bbf6f5-bxh54   1/1     Running   0          46s   <IP_ADDRESS>   kn4    <none>           <none>
my-nginx-df7bbf6f5-rvlnd   1/1     Running   0          46s   <IP_ADDRESS>   kn5    <none>           <none>

Hi @marco74 ,
If you choose the service type: ClusterIP then you can curl the nginx service from any pods (curl pkg should be installed on that pod's image or later on, you can install it by its package manager) on that XYZ node in your cluster.
Suppose pod-1 is deployed on worker-01 node and pod-2 is deployed on worker-02 node
then you can Curl to that nginx service on its <CLUSTER-IP>:<PORT> from inside pod (pod-1 or pod-2).
Simply run the command: kubectl exec -it pod-1 -- bash
then do curl <CLUSTER-IP>:<PORT>
If you want to curl from the node then change service type: ClusterIP to NodePort.
Reference link - https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
Regards,

@Tej-Singh-Rana: Thank you for that hint! I can test this tomorrow. Just to give quicker replies (and hopefully answers): Isn't that considered as alpha in 1.24? So I'm wondering, why https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/ is not just working as expected. This also does not answer the question why two pods get the same IP. As far as I know networking, networking cannot work properly, when two participants have the same IP.
Regards,

After tests with Ubuntu 20.04 and 22.04 I found out following. Kubernetes stops supporting newer distributions including Ubuntu 22.04 and Debian 11 with Version 1.21. Since that version kube-system pods get restarted constantly:
marco@kn3:~$ cat /etc/debian_version
11.3
marco@kn3:~$ dpkg -l kubectl kubeadm kubelet
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-=====================================
ii  kubeadm        1.21.13-00   amd64        Kubernetes Cluster Bootstrapping Tool
ii  kubectl        1.21.13-00   amd64        Kubernetes Command Line Tool
ii  kubelet        1.21.13-00   amd64        Kubernetes Node Agent
marco@kn3:~$ kubectl get pods --all-namespaces
NAMESPACE     NAME                          READY   STATUS    RESTARTS   AGE
kube-system   coredns-558bd4d5db-dqb6t      0/1     Pending   0          57m
kube-system   coredns-558bd4d5db-p65tb      0/1     Pending   0          56m
kube-system   etcd-kn3                      1/1     Running   15         57m
kube-system   kube-apiserver-kn3            1/1     Running   13         57m
kube-system   kube-controller-manager-kn3   1/1     Running   13         57m
kube-system   kube-proxy-76dvp              1/1     Running   14         57m
kube-system   kube-scheduler-kn3            1/1     Running   12         57m

I assume that it's not intended to restart pods that often. Just as a comparision tha same with version 1.20 on the same OS (different VM):
11.3
marco@kn2:~$ dpkg -l kubectl kubeadm kubelet
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-=====================================
ii  kubeadm        1.20.15-00   amd64        Kubernetes Cluster Bootstrapping Tool
ii  kubectl        1.20.15-00   amd64        Kubernetes Command Line Tool
ii  kubelet        1.20.15-00   amd64        Kubernetes Node Agent
marco@kn2:~$ kubectl get pods --all-namespaces
NAMESPACE     NAME                          READY   STATUS    RESTARTS   AGE
kube-system   coredns-74ff55c5b-tbjxw       0/1     Pending   0          11h
kube-system   coredns-74ff55c5b-xb4ws       0/1     Pending   0          11h
kube-system   etcd-kn2                      1/1     Running   3          11h
kube-system   kube-apiserver-kn2            1/1     Running   2          11h
kube-system   kube-controller-manager-kn2   1/1     Running   2          11h
kube-system   kube-proxy-l8rwl              1/1     Running   2          11h
kube-system   kube-scheduler-kn2            1/1     Running   2          11h

The only difference in setting up the stack was
sudo apt-get -y install kubelet=1.21.13-00 kubectl=1.21.13-00 kubeadm=1.21.13-00

vs.
sudo apt-get -y install kubelet=1.20.15-00 kubeadm=1.20.15-00 kubectl=1.20.15-00

So, what prevents newer kubernetes versions from working cleanly on the latest distributions Debian 11 and Ubuntu 22.04? Does anybody know how to get kubernetes working on those distributions as well?

After having a look at https://github.com/kubernetes/kubernetes/issues/105762 I found a solution, that solves the restart problem on Debian 11. I do not use Ubuntu, therefore feel free to also test it on Ubuntu 22.04.
With the hint I updated /etc/containerd/config.toml:
version = 2

[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
  runtime_type = "io.containerd.runc.v2"

  [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
    SystemdCgroup = true

With this I got the stack running without restarts, also the network initialization works very smooth. My suggestion for the kubernetes documentation team. could you please add the two lines

version = 2
`runtime_type = "io.containerd.runc.v2"

at https://kubernetes.io/docs/setup/production-environment/container-runtimes/#containerd ? I was not able to get the stack running without those two lines.
For all those who are interested in how I finally setup a cluster with Debian 11 and kubernetes 1.24:
sudo apt-get -y update
sudo apt-get -y install ca-certificates curl gnupg lsb-release

#from:
# * https://gist.github.com/dbathgate/737e8d800decde9adbf8a0130870bcc4
# * https://github.com/flannel-io/flannel
sudo mkdir -p /opt/bin/
sudo curl --location https://github.com/flannel-io/flannel/releases/download/v0.18.0/flanneld-amd64 -o /opt/bin/flanneld
sudo chmod +x /opt/bin/flanneld #/usr/local/bin/flanneld

curl -fsSL https://download.docker.com/linux/debian/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg
echo   "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/debian \
  $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt-get -y update

sudo apt-get -y install containerd.io
sudo sed -i "s/^\(disabled_plugins\s*=\)/# \1/" /etc/containerd/config.toml
cat <<EOF | sudo tee -a /etc/containerd/config.toml
### from https://github.com/kubernetes/kubernetes/issues/105762
version = 2

[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
  runtime_type = "io.containerd.runc.v2"

  [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
    SystemdCgroup = true

EOF
sudo systemctl restart containerd

## Prerequisites for kubernetes, according to:
##   https://kubernetes.io/docs/setup/production-environment/container-runtimes/
cat <<EOF | sudo tee /etc/modules-load.d/k8s.conf
overlay
br_netfilter
EOF

sudo modprobe overlay
sudo modprobe br_netfilter

# sysctl params required by setup, params persist across reboots
cat <<EOF | sudo tee /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-iptables  = 1
net.bridge.bridge-nf-call-ip6tables = 1
net.ipv4.ip_forward                 = 1
EOF

# Apply sysctl params without reboot
sudo sysctl --system

## install kubernetes
sudo curl -fsSLo /usr/share/keyrings/kubernetes-archive-keyring.gpg https://packages.cloud.google.com/apt/doc/apt-key.gpg
echo "deb [signed-by=/usr/share/keyrings/kubernetes-archive-keyring.gpg] https://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee /etc/apt/sources.list.d/kubernetes.list
sudo apt-get update
sudo apt-get install -y kubelet kubeadm kubectl

sudo kubeadm config images pull

sudo kubeadm --pod-network-cidr=<IP_ADDRESS>/16 init

mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

kubectl apply -f https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/kube-flannel.yml

kubectl get pods -n kube-system -o wide

Regards,

@marco74 as of now, is there a task page that needs fixing? If so, what's the task page and what in that page isn't right?

@sftim Thank you for asking, just looked up:
https://kubernetes.io/docs/setup/production-environment/container-runtimes/#containerd describes how to setup containerd for Kubernetes.
When reading containerd's documentation for configuration (https://github.com/containerd/cri/blob/master/docs/config.md) they write about version = 2. This was added with commit e2550f6285638aaf591d40927c319a301b697d5f on Jul, 24 2019 (https://github.com/containerd/cri/commit/e2550f6285638aaf591d40927c319a301b697d5f), not fully 3 years ago. runtime_type = "io.containerd.runc.v2" is mentioned in the same documentation since https://github.com/containerd/cri/commit/aaddaa27320bfe89959d838205a7117af825361e, on Dec, 16 2019. This was about 2.5 years ago.
Debian 11 released about 10 months ago. It works quite stable but I could not get Kubernetes running without those two settings. I also tried omitting one of the two lines – both are needed. I tested without using those two lines on Ubuntu 22.04 and could not get it running either. I did not test on Ubuntu 22.04, but I am pretty sure that this will work with those two lines.
It would be great, if somebody could explain me why version 2 is necessary, currently I do not know it. At the moment I only know that it helps. As you can read in this thread, I read about this on another thread, After I looked why the system-containers are restarting continuously.
Therefore I would really appreciate if this block:
[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
  ...
  [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
    SystemdCgroup = true

could be adapted to this:
version = 2

[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
  runtime_type = "io.containerd.runc.v2"

  [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
    SystemdCgroup = true

Could you, or probably somebody else do that?
Marco

For an analogy, think about the Linux kernel and userland tools.
If you want to do something that involves setting up Linux networking then you need to know about the kernel, and maybe also iproute2 and other tools.
Each component there has documentation that goes so far but ultimately those docs often do stop at a point.
Because there's so much that touches Kubernetes but isn't actually Kubernetes, as a project we adopted an official policy on this. If in the future we find we have a much bigger amount of volunteered / contributed time going into docs, we're open to revising that policy. Right now, we want to make sure we're fair to all the different 3rd party tools out there and try to limit how much detail we go into
You are welcome to identify a page such as https://kubernetes.io/docs/setup/production-environment/container-runtimes/ and highlight a specific section that's wrong - no problem at all with that - or misleading. You can also propose improvements.
This issue isn't, right now actionable enough. Imagine that a new docs contributor comes along and reads the issue description

Hello,
on the site I read You should now be able to curl the nginx Service on <CLUSTER-IP>:<PORT> from any node in your cluster.
After following the instructions I can curl my nginx service only on that nodes where a pod is running. On the others I got curl: (7) Failed to connect to <IP_ADDRESS> port 80: No route to host Is that intentionally or am I missing something?
Also the DNS part does not work at all for me. After following the instructions according to the page, I only get
Server:    <IP_ADDRESS>
Address 1: <IP_ADDRESS>

nslookup: can't resolve 'my-nginx'

Since this takes that long I assume it's a timeout error.
I'm using kubernetes 1.24 on Debian Bullseye with cri-dockerd installed as mentioned on https://github.com/Mirantis/cri-dockerd
Marco

Can they use that information to work out what web page to fix and get an insight into how they might? I'm worried they can't.
We do, as a project, want to make it easier for folks to use kubeadm and to troubleshoot what happens when it goes wrong. However, this is a bit like the Linux kernel project offering only so much troubleshooting for someone whose Linux computer doesn't boot. At some point, an end user may be better off finding a packaged distribution (the likes of EKD-D, OKD, or RKE) and referring to the more opinionated docs for that specific combination of components. In the Linux computing world that might be Alpine, Debian, Fedora, Rocky, Ubuntu. You get the picture I hope.
I think the next steps here could be one of:

Treat this issue as having been mainly a support request along with some feedback, and close it.
You, @marco74, open a new issue that does aim to be more actionable for someone who tries to work on it.
File a feature request issue based on an identified need. For example:

add a guide on getting a cluster up and running that is more opinionated than the existing docs and also has more hand-holding than Kubernetes the hard way
improve the docs for troubleshooting new clusters
improve the docs for troubleshooting issues relating to container runtime configuration
add more links to container runtime projects' docs on troubleshooting
your own idea here!

Which of those do you like best @marco74 ?

container runtime projects' docs also does not have that good documentation

I agree. I believe that the right way to address the shortcomings you've seen working out how to build a cluster is to fix that.
In the Kubernetes project we don't really have capacity to document Kubernetes itself as well as we'd like. As a project, we don't have much capacity to go and improve those other products' docs - however, that is what needs to happen somehow.

GitHub issues are the right place to report that the documentation is wrong, or to suggest improvements. The original report here was actually not really in the right place, because you framed it as a support request. I'm afraid that GitHub is the wrong place to request help with Kubernetes, and this holds even if you felt that you wanted support because the docs fell short of expectations.
We have a guide to communicating on GitHub. I hope I'm following the spirit of that guide, and I encourage everyone to. You're welcome to create more issues @marco74; I especially recommend that you read and follow the advice in Creating an issue.
Maybe reporting an actionable issue doesn't match what you were looking for. If you'd like to have more of a discussion around how we document Kubernetes and help new folks get started, GitHub isn't the right place for that; maybe try Discuss Kubernetes?

/remove-lifecycle stale


Ignores draft option

While releasing, using this config block immediately creates a public release instead of a release draft
    - name: Tauri Build
      uses: tauri-apps/tauri-action@v0
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
      with:
        # NOTE: "__VERSION__" automatically replaced
        tagName: v__VERSION__
        releaseName: v__VERSION__
        body: "See the assets to download this version and install."
        prerelease: false
        draft: true

Also, it seems like the body is ignored too.
This is what a release looks like upon completion:

The correct options for this are releaseDraft and releaseBody. The README used to show an out-of-date example.


Fix scenarios in User and RecoveryForm

Lost default scenario

+1
I think it should be merged

Thank you!


[SPARK-18659] [SQL] Incorrect behaviors in overwrite table for datasource tables

What changes were proposed in this pull request?
Two bugs are addressed here

INSERT OVERWRITE TABLE sometime crashed when catalog partition management was enabled. This was because when dropping partitions after an overwrite operation, the Hive client will attempt to delete the partition files. If the entire partition directory was dropped, this would fail. The PR fixes this by adding a flag to control whether the Hive client should attempt to delete files.
The static partition spec for OVERWRITE TABLE was not correctly resolved to the case-sensitive original partition names. This resulted in the entire table being overwritten if you did not correctly capitalize your partition names.

cc @yhuai @cloud-fan
How was this patch tested?
Unit tests. Surprisingly, the existing overwrite table tests did not catch these edge cases.

Test build #69432 has started for PR 16088 at commit 4b6a4ee.

Test build #69432 has finished for PR 16088 at commit 4b6a4ee.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69432/
Test PASSed.

Merged build finished. Test PASSed.

Test build #69504 has started for PR 16088 at commit f4356f0.

Test build #69504 has finished for PR 16088 at commit f4356f0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69504/
Test PASSed.

Merged build finished. Test PASSed.

Test build #69532 has started for PR 16088 at commit b79cef4.

LGTM pending jenkins

Test build #69537 has started for PR 16088 at commit a9f9710.

Test build #69532 has finished for PR 16088 at commit b79cef4.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69532/
Test FAILed.

retest this please

Test build #69543 has started for PR 16088 at commit a9f9710.

Test build #69537 has finished for PR 16088 at commit a9f9710.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69537/
Test PASSed.

Test build #69543 has finished for PR 16088 at commit a9f9710.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69543/
Test PASSed.

thanks, merging to master/2.1!


[User Story AB#891328] Separate entt assert for constexpr functions (defaults to same)

So that we can define a separate constexpr assert handler vs regular.
Unfortunately we can't use std::is_constant_evaluated (c++20, also doesn't work with the static), the only solution other than splitting the assert is c++23's consteval and that isn't happening so here we are!
Discussion:
https://mojangab.slack.com/archives/C17SFESBC/p1665698125018929
Summary / TLDR:
Want to define a static bool inside our assert handler, but that breaks all constexpr usages of the assert. Plan is to define a constexpr friendly one and the new non constexpr friendly one (using the static, that lets you ignore the assert via dialog).
To do so requires us to use a separate assert for these cases (such as these ones here in entt, which actually were the only cases in the codebase where the assert was used in a constexpr function).

Codecov Report

Merging #8 (053acb3) into master (9ac5f6d) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master        #8   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          139       139
  Lines        20906     20906
=========================================
  Hits         20906     20906

Impacted Files
Coverage Δ

src/entt/core/memory.hpp
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

You should directly reach out to @skypjack  about this. So far we have been at parity with the entt main repo. I’d like to keep it that way. But I also feel these could just be static asserts.

I guess this sort of is directly reaching out to him.

Yeah, please, don't merge this PR here.
We're keeping this repo in sync with skypjack/entt and we would have to port, sync and update everything anyway.
I strongly suggest to open the PR to the main repo. We can bring it into Minecraft for you if you like.
This significantly simplifies our work.
Moreover, we've a pretty large change here on branch experimental (which is the upcoming master in the main repo).
Merging this PR would create us quite a lot of issues at the moment. Please, kindly hold on until the tests are over and master is updated. 🙏
Note: I started the tests right away after a merge from main but they already passed once two days ago (then I had some problems somewhere else and the PR is now too old with its 3 days 😅). I'll probably merge it before you get up. 👍

As for the PR, I don't fully get what problem it tries to solve. 🤔
I see that the ENTT_ASSERT in a constexpr function turns it into a non-constexpr one (in debug only though).
However, consider that for example fast_mod is used more often than not in non-constexpr contexts. Therefore, treating the assert as if the function was constexpr no matter what isn't likely the right approach.

By the way, don't get me wrong. I'm definitely not opposed to merging it in the main repo if it helps.
Just please follow the same process we go through all the times. It would help a lot. Thanks! 👍

I went on and turned the offending functions into non-constexpr ones since the constexpr-ness isn't really required here.
If it works for you, we can bring this upstream in Minecraft early next week, immediately after the PR we've already on the fly. Just let me know.

I went even more on 😅 and added an ENTT_ASSERT_CONSTEXPR variable as you suggested (used in the subsequent commits, tested and documented already).
If you agree, I can port these changes to Minecraft immediately after the PR we've already on the fly. Let me know. 👍

Hey, thank you @skypjack! That commit solves my issue, I think that would be great to port to the Minecraft fork.


Contributor name not showing when 'logged in'

Describe the bug
In the Explorer, I log in (I've tried<EMAIL_ADDRESS>and<EMAIL_ADDRESS>- at least one of these has permissions) and get the password right. But the Explorer reloads still saying 'log in' and not showing the contributor names.
is it possible to restore this function?
Screenshot showing Search page after login.

As discussed outside of this issue, I'm closing this as we're directing efforts here towards planning & making a new (and hopefully better) version of the explorer.
Will make a new github issue to track this :)


K8 Tweaks

Nodes tables

Convert Capacity Memory value to human readable short string

Node Metrics - Legend/Series label

Shows duplicates due to labels missing container details. Also results in 13 shown in legend vs 30 shown in 'hover over' window. Think the conclusion was to show metrics per container and confirm legend area scrolls correctly

Filter out Container POD everywhere except for the 'Network IO' chart (any others?)
Summary cards showing total CPU time in seconds need to round up to hours, days, etc. Moment should be able to do this using their Durations object
Namespace--> applications table needs to show additional version column
Docs needed to describe different methods to connect to K8 endpoint
Upstream but fix here to prove out... void space is shown on pages where there are no tabs (pods-->metrics)
Upstream but mostly visible here.... Handle pagination from different api's rather than using cf params

I've renamed version -> App Version. There is no separate label for Chart Version, rather its integrated into the Chart Name


Update uob_utils.py

Removed the debug for adding arbitrary number of days for testing purposes.

Some bug fixes...


Facebook SDK Integration Issue in React Native App for iOS 14+

🐛 Bug Report

To Reproduce

Expected Behavior

Code Example

Environment

Facebook SDK Integration Issue in React Native App for iOS 14+
I'm experiencing an issue with Facebook SDK integration in my React Native app. The SDK is working correctly on Android and iOS versions below 14, but it's not functioning properly on iOS 14 and above. Here's what I've implemented so far:
AppDelegate.mm
#import <React/RCTBundleURLProvider.h>
#import <AuthenticationServices/AuthenticationServices.h>
#import <SafariServices/SafariServices.h>
#import <FBSDKCoreKit/FBSDKCoreKit-Swift.h>
#import <FBAEMKit/FBAEMKit-Swift.h>
#import <React/RCTLinkingManager.h>
#import <AppTrackingTransparency/AppTrackingTransparency.h>
#import <AdSupport/AdSupport.h>

// In didFinishLaunchingWithOptions:
[[FBSDKApplicationDelegate sharedInstance] application:application
                       didFinishLaunchingWithOptions:launchOptions];

if (@available(iOS 14, *)) {
  [ATTrackingManager requestTrackingAuthorizationWithCompletionHandler:^(ATTrackingManagerAuthorizationStatus status) {
    // Handle tracking authorization status if needed
  }];
}

return [super application:application didFinishLaunchingWithOptions:launchOptions];

// OpenURL method
- (BOOL)application:(UIApplication *)application
   openURL:(NSURL *)url
   options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options
{
  [FBAEMReporter configureWithNetworker:nil appID:@"YOUR_APP_ID" reporter:nil];
  [FBAEMReporter enable];
  [FBAEMReporter handle:url];

  return [RCTLinkingManager application:application openURL:url options:options];
}

Podfile
pod 'FBSDKCoreKit', '~> 17.0.0'
pod 'FBSDKLoginKit', '~> 17.0.0'
pod 'FBSDKShareKit', '~> 17.0.0'

Info.plist
I've added the necessary Facebook-related keys and values to my Info.plist file, including:

FacebookAdvertiserIDCollectionEnabled
FacebookAppID
FacebookAutoLogAppEventsEnabled
FacebookClientToken
FacebookDisplayName
LSApplicationQueriesSchemes (for Facebook-related URL schemes)
NSUserTrackingUsageDescription

React Native Package
I'm using react-native-fbsdk-next version 13.0.0 in my project.
Despite these implementations, the Facebook SDK is not working on iOS 14 and above. What could be the issue, and how can I resolve it?

Same issue here and how to resolve it? Any solution for this issue?

Now facebook needs upgrade SDK version iOS v17.0.3

@qsales2022 Have you resolved it ? If yes, could you please let me know how did you do it ?

I believe these are different issues.
Original poster says it simply isn't working. I can't reproduce that. It works fine for me from the example app here on iOS 14+ and in my work app. So I'm going to close the issue as I cannot reproduce.
Other posters have hijacked the thread to say they want the ios SDK updated. That's been done in other pull requests


Allow custom role rights, set env, update output

use new output system
allow customization of the user rights
export PGDATABASE and PGPASSWORD env vars

fixes #6
fixes #7

@ikalnytskyi This PR fixes a warning about a deprecated command too. See:

Isn't it interesting merge it asap? Or, if you want, I can fix just part related with the warning.
Thanks. Have a nice day.

@rcmuniz1994 I have since released an updated version that has postgis focus - https://github.com/actions-marketplace-validations/nyurik_action-setup-postgis -- but obviously many people only need postgres itself, not postgis.

Hey @nyurik,
Thanks for the patch and sorry for ignoring it for so long.

use new output system

Can you please submit it as a separate PR? If inconvenient, I can do it on your behalf. I just want to track separate changes separately, preserving rationale in commits description.

export PGDATABASE and PGPASSWORD env vars

Can you please explain why do we need this? Users are advised to use connection-uri instead of relying on environment variables.

allow customization of the user right

The trick you're doing is a little bit low-level. Can you please explain to me what is your use case and what are you trying to achieve? I'd expect createuser invoked by this action to be an implementation detail, and all non-standard users be crafted by action users via createuser manual invocation.

I think raised concerns are addressed in @v4, so I'm closing this patch. Please feel free to re-submit with improvements you're still missing or file a ticket in the issue tracker.

@ikalnytskyi thanks for an in-depth reply!  I somehow missed, and only now got back to reviewing all this. Thanks for your dedication!


Lib Switcher

Uses the work here https://github.com/pmndrs/website/pull/12 from @emmelleppi and cleans up all the conflicts and fixes the names and links

LGTM!


GET fails on ESP8266 in YY_MODE_PEER_CLIENT mode

GET fails on ESP8266 in YY_MODE_PEER_CLIENT mode. Can be demonstrated by the /yoyo/peers endpoint - doesn't connect with the gateway to get the list of peers.
handleRequest: /yoyo/peers
Mode: STA
PHY mode: N
Channel: 1
AP id: 0
Status: 5
Auto connect: 1
BSSID set: 1
GET http://<IP_ADDRESS>/yoyo/peers
[HTTP-Client][begin] url: http://<IP_ADDRESS>/yoyo/peers
[HTTP-Client][begin] host: <IP_ADDRESS> port: 80 url: /yoyo/peers
[HTTP-Client][sendRequest] type: 'GET' redirCount: 0
[hostByName] Host: <IP_ADDRESS> is a IP!
[HTTP-Client] failed connect to <IP_ADDRESS>:80
[HTTP-Client][returnError] error(-1): connection failed
[HTTP-Client][end] tcp is closed

In fact this bug is more general - ESP8266s in any mode don't successfully connect to other devices on their peer network. This is from a POST initiated in YY_MODE_PEER_SERVER mode >
[HTTP-Client] failed connect to <IP_ADDRESS>:80
[HTTP-Client][returnError] error(-1): connection failed
[HTTP-Client][end] tcp is closed
[HTTP-Client][end] tcp is closed
And yet sending this same POST via Postman from a laptop on that same network works.

In fact this bug is more general - ESP8266s in any mode don't successfully connect to other devices on their peer network. This is from a POST initiated in YY_MODE_PEER_SERVER mode >
[HTTP-Client] failed connect to <IP_ADDRESS>:80
[HTTP-Client][returnError] error(-1): connection failed
[HTTP-Client][end] tcp is closed
[HTTP-Client][end] tcp is closed
And yet sending this same POST via Postman from a laptop on that same network works.

This all works on the ESP32 and if an ESP8266 joins the peer network as YY_MODE_PEER_CLIENT, then that works too - getting peers as per the first report. Which implies the problem is the ESP8266 as YY_MODE_PEER_SERVER.

This all works on the ESP32 and if an ESP8266 joins the peer network as YY_MODE_PEER_CLIENT, then that works too - getting peers as per the first report. Which implies the problem is the ESP8266 as YY_MODE_PEER_SERVER.

It seems that this problem was caused because the request was being made before the AsyncWebHandler handleBody() had completed. #f576e3d fixes this by maintaining a broadcast message list that is processed after handleBody() has completed.

It seems that this problem was caused because the request was being made before the AsyncWebHandler handleBody() had completed. #f576e3d fixes this by maintaining a broadcast message list that is processed after handleBody() has completed.


Add RenameOrg endpoint for Org Admin API

Adds RenameOrg and RenameOrgByName functions for the Github Enterprise Organization Admin API. Addresses #1479.

I'm not sure why either. I think it was late and wanted CI test results before looking over it again today.

Thank you, @wesleimp!
Merging.


Bug: 2 "alias" related issues

For example, when node [[App]] has an alias "app":
Case 1: With Dendron enabled, I created a new node [[app.Chrome]], the Matrix view will show the parent as "app", but clicking it will lead to creating a new empty node [[app]], instead of the existing node [[App]].
Case 2: When I created a node [[app1]] and add this in frontmatter: "up: [[App]]". and then create a node [[app2]] with "up: [[app]]" (lowercase, which is the alias). But in app1's matrix view, I can't see "app2" as its sibling. Same thing happens in app2's matrix view.

Hey, thanks for the issue. I think in both cases, this isn't the "expected" behaviour, but I also don't think it's wrong. Aliases are different from the file path - they have to be specified differently [[path|alias]]. If Obsidian is treating [[app]] as distinct from [[App]], I don't think Breadcrumbs should not do that.
Having said this, Breadcrumbs V4 works differently under the hood, so this issue might be resolved anyway. But I'm going to close this out as not planned.


[ExpressionLanguage] Add function service

Symfony version(s) affected
7.0.7
Description
I have an error :
The function "service" does not exist around position 1 for expression `service('App\Service\Generator').generate('songs_by_artist_' ~ entity.getId())`.

How to reproduce
I have the following entity:
<?php

namespace App\Entity;

use App\Repository\BookRepository;
use Doctrine\ORM\Mapping as ORM;
use Symfony\UX\Turbo\Attribute\Broadcast;

#[ORM\Entity(repositoryClass: BookRepository::class)]
#[Broadcast(topics: ["@=service('App\\Service\\Generator').generate('songs_by_artist_' ~ entity.getId())", 'books'], template: 'broadcast/Book.stream.html.twig', private: true)]
class Book
{
    #[ORM\Id]
    #[ORM\GeneratedValue]
    #[ORM\Column]
    private ?int $id = null;

    #[ORM\Column(length: 255)]
    private ?string $title = null;

    public function getId(): ?int
    {
        return $this->id;
    }

    public function getTitle(): ?string
    {
        return $this->title;
    }

    public function setTitle(string $title): static
    {
        $this->title = $title;

        return $this;
    }
}

But when I create a Book entity, I get the following error:
The function "service" does not exist around position 1 for expression `service('App\Service\Generator').generate('songs_by_artist_' ~ entity.getId())`.

In my case, $this->functions is enum and constant :  https://github.com/symfony/symfony/blob/7.1/src/Symfony/Component/ExpressionLanguage/Parser.php#L242
Possible Solution
No response
Additional Context
No response

This has never been possible as i see it .. I believe expression language is used there to compose topic names based on the enttity props.
Or am i missing something ?

Yes but I saw in the documentation below that it was possible to use the service function in expression languages: https://symfony.com/doc/current/service_container/expression_language.html

... in the service container:)

Yes, but the ExpressionLanguage used in the service container's configuration is configured to access the Symfony Container (or at least something to fetch services from), which was never the case here with Symfony\UX\Turbo\Attribute\Broadcast attribute.

So, won't fix?

Maybe we can find another alternative, instead of passing the whole container, we can inject a service that could be configured under broadcard.topic_generator (or smth like that)?

So, won't fix?

Maybe let's use another word than  fix ... as this is a request for a feature (that has never existed in the first place, right ? 😅)
Could you give you the final usage you're looking after, so maybe we can suggest other ways to achieve it ?

Maybe we can find another alternative, instead of passing the whole container, we can inject a service that could be configured under broadcard.topic_generator (or smth like that)?

Yes, why not :).

Maybe let's use another word than fix ... as this is a request for a feature (that has never existed in the first place, right ? 😅)

Yes, it's true, you're right, sorry 😄.

Could you give you the final usage you're looking after, so maybe we can suggest other ways to achieve it ?

Currently, when I put:

it becomes:
<div id="book_7" data-controller="symfony--ux-turbo--mercure-turbo-stream" data-symfony--ux-turbo--mercure-turbo-stream-topic-value="book_detail_7" data-symfony--ux-turbo--mercure-turbo-stream-hub-value="http://<IP_ADDRESS>:56215/.well-known/mercure">

With a generator, this will hash/encode the data-symfony--ux-turbo--mercure-turbo-stream-topic-value. It will then be more secure.
This line

will then become:
<div id="book_7" data-controller="symfony--ux-turbo--mercure-turbo-stream" data-symfony--ux-turbo--mercure-turbo-stream-topic-value="AiLvziwlkB5M9UpYKRyiHvDs/BK7t4T6B7CR48ropyA=" data-symfony--ux-turbo--mercure-turbo-stream-hub-value="http://<IP_ADDRESS>:56215/.well-known/mercure">

I like the idea, should it be something to add here or in the Mercure bundle ?

You might as well do it directly in MercureBundle. But is there a downside?

Not resolved.

I still doubt this repo is the best place to implement this feature.


Update repositories.json

Added my repository at bottom

Getting an issue when I refresh HPM.  Any suggestions on how I can fix this?
[cid:5a297051-77fc-41fe-a11b-5725ab1f771b]

From: dcmeglio @.>
Sent: Saturday, July 31, 2021 5:00 PM
To: dcmeglio/hubitat-packagerepositories @.>
Cc: Scott Barton @.>; Author @.>
Subject: Re: [dcmeglio/hubitat-packagerepositories] Update repositories.json (#106)
Merged #106https://github.com/dcmeglio/hubitat-packagerepositories/pull/106 into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dcmeglio/hubitat-packagerepositories/pull/106#event-5094711860, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADWNN5J7FFISIBWRO24WD6LT2RP6DANCNFSM5BHS6PLA.
[https://ipmcdn.avast.com/images/icons/icon-envelope-tick-green-avg-v1.png]http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail     Virus-free. www.avg.comhttp://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail

Also getting this error.
[cid:1dd3558d-ae23-47ab-bf45-c2847d354308]

From: Scott Barton @.>
Sent: Monday, August 2, 2021 2:24 PM
To: dcmeglio/hubitat-packagerepositories @.>; dcmeglio/hubitat-packagerepositories @.***>
Subject: Re: [dcmeglio/hubitat-packagerepositories] Update repositories.json (#106)
Getting an issue when I refresh HPM.  Any suggestions on how I can fix this?
[cid:5a297051-77fc-41fe-a11b-5725ab1f771b]

From: dcmeglio @.>
Sent: Saturday, July 31, 2021 5:00 PM
To: dcmeglio/hubitat-packagerepositories @.>
Cc: Scott Barton @.>; Author @.>
Subject: Re: [dcmeglio/hubitat-packagerepositories] Update repositories.json (#106)
Merged #106https://github.com/dcmeglio/hubitat-packagerepositories/pull/106 into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dcmeglio/hubitat-packagerepositories/pull/106#event-5094711860, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADWNN5J7FFISIBWRO24WD6LT2RP6DANCNFSM5BHS6PLA.
[https://ipmcdn.avast.com/images/icons/icon-envelope-tick-green-avg-v1.png]http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail     Virus-free. www.avg.comhttp://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail

Unfortunately those images aren’t appearing.


Issue 60 stack structure

Pull request checklist

[x] All tests pass. Demo project builds and runs.
[x] I have resolved any merge conflicts.
[x] I have followed the coding style, and reviewed the contributing guidelines.

This fixes issue #60
What's in this pull request?

change stack structure so that both background and main contexts are connected to the persistent store coordinator
sync mechanism between contexts now use mergeChangesFromContextDidSaveNotification(_:)

What's not in this pull request?

child contexts creation with background context as parent.
childContext use the main context as parent. This may not be something we want with this new structure (at least not all the time).
some of the tests may be simplified or changed to reflect the new stack structure and update mechanism.

Whoa @Liquidsoul ! This is awesome! 👍 😄 Great work.
Only one small comment to address, then I'll merge. Thanks so much for working on this!
I'll be releasing this with 4.0.0 soon.

What's not in this pull request?

child contexts creation with background context as parent. childContext use the main context as parent. This may not be something we want with this new structure (at least not all the time).

Yep, agreed. I created #73 to follow up here. 😄

some of the tests may be simplified or changed to reflect the new stack structure and update mechanism.

I think what you've done with the tests is great! 👍 Is there something specific you think we should change?

Thanks @jessesquires ! 😊
I've amended my last commit to change the documentation and rebased the branch.

I think what you've done with the tests is great! 👍 Is there something specific you think we should change?

I was wondering if the sibling context updates checks in SaveTests.swift could be removed.
We test that saving the background and the main context will merge the changes into the other, it may not be necessary to do this kind of check in all the tests.
Maybe this could reduce the size of some of those tests without reducing the coverage.

@Liquidsoul ahhh, I see. I actually like this. Feels very thorough. 😄


New Scheduler with CouchDB backend

Environment details:

Local ansible deployment
Ubuntu 20.04, Docker 20.10.12

Steps to reproduce the issue:

Follow Ansible deployment instructions for new Scheduler
Modify them to deploy with couchdb backend and not Elastic Search
Will hit error at the following command: ansible-playbook -i environments/$ENVIRONMENT openwhisk.yml -e db_activation_backend=CouchDB

Provide the expected results and outputs:
I'd expected it to deploy correctly.
Provide the actual results and outputs:
The scheduler will fail to deploy. The error ansible gives is:
fatal: [scheduler0]: FAILED! => {"attempts": 12, "changed": false, "elapsed": 0, "msg": "Status code was -1 and not [200]: Request failed: <urlopen error [Errno 111] Connection refused>", "redirected": false, "status": -1, "url": "http://<IP_ADDRESS>:14001/ping"}

Status code was -1 and not [200]: Request failed: <urlopen error [Errno
111] Connection refused>

This isn't very helpful, I don't think, but the scheduler logs are more informative:
[2022-04-25T18:10:32.291Z] [INFO] [#tid_sid_unknown] [WatcherService] watch endpoint: WatchEndpoint(whisk/instance/scheduler0/lease,7802908987417965063,false,lease-service,Set(DeleteEvent))
Exception in thread "main" java.lang.ExceptionInInitializerError
        at java.base/java.lang.J9VMInternals.ensureError(J9VMInternals.java:186)
        at java.base/java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:175)
        at org.apache.openwhisk.core.scheduler.queue.ElasticSearchDurationCheckerProvider$.instance(ElasticSearchDurationChecker.scala:121)
        at org.apache.openwhisk.core.scheduler.queue.ElasticSearchDurationCheckerProvider$.instance(ElasticSearchDurationChecker.scala:112)
        at org.apache.openwhisk.core.scheduler.Scheduler.<init>(Scheduler.scala:91)
        at org.apache.openwhisk.core.scheduler.Scheduler$.main(Scheduler.scala:339)
        at org.apache.openwhisk.core.scheduler.Scheduler.main(Scheduler.scala)
Caused by: pureconfig.error.ConfigReaderException: Cannot convert configuration to a org.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStoreConfig. Failures are:
  at 'whisk':
    - Key not found: 'activation-store'.

        at pureconfig.package$.getResultOrThrow(package.scala:139)
        at pureconfig.package$.loadConfigOrThrow(package.scala:161)
        at org.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore$.<init>(ElasticSearchActivationStore.scala:420)
        at org.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore$.<clinit>(ElasticSearchActivationStore.scala)
        ... 5 more

It appears the scheduler is looking for ElasticSearch backend, and not CouchDB.
I'm hoping to learn if the scheduler can function with CouchDB as an activation store or not.
Additional information you deem important:

Ansible scheduler documentation says it's recommended to use ElasticSearch at the activation store but does not say it's required.

In the configuration instructions, I replaced the ElasticSearchDurationCheckerProvider with NoopDurationCheckerProvider, because this seemed a reasonable thing to do to try to fix the issue above.
However, the error remained the same even after that change.

I'm in the process of setting up the new scheduler and haven't had any issue with the components at least talking to one another. I'm using the NoopDurationCheckerProvider since we don't use elastic search. You should be able to use the new scheduler with activations in couchdb. What is the new error and what does your config look like for both the duration checker and configuring the activation store?

Thank you for your response @bdoyle0182! I refreshed my environment and it appears that something just hadn't updated after I'd changed to the NoopDurationCheckerProvider. So I suppose I'd already fixed my own issue.
I've updated the directions in PR I just made to describe the above.


Trimming Badge Selection

Leading off of #386, we're going to do a review of the badges supported in the repo.
1. Open-Source Software
2. Freeware
3. hot
4. Recommend
5. Must Have
6. App Store
7. Star Rating

I propose we trim this to:
1. Open-Source
2. Freeware
3. App Store
4. Recommended

to kill some of the redundancy and clean it all up a bit.

@alichtman good!

About "Recommended":
There are awesome lists that don't have this badge because they are awesome lists and don't have "not recommeded" apps. All apps in the lists are unique or already too good to be judged. If some app is better by all means than another app in the list then the second app just should not be on the list. If there are no alternatives to the app it's automatically the recommended app of its kind. Plus this approach will allow avoiding holy wars like Sublime Text vs Atom, Postman vs Insomnia, Safari vs Chrome ... Some of them are especially tough if we consider the diverse audience of the list (even if we simplify the situation and imagine that there only two "types" of readers Designers and Devs ).
And another issue who (and how) is going to determine if an app is "Recommended" (again taking into account that the list is a collaborative project) ?

You're right, in my opinion.


Add an API to observer for querying deleted sites

If a site is deleted. Observer will return 404. Add an ability to observer that allows users to query for deleted sites and still get relevant data.

How will you get hostnames/stamp etc for deleted sites from DB. is there a way?
If its not possible, then an alternative way at applens is to take subId, resource group and hostname as input for deleted sites and directly query API as kusto will have data


feat(protocol-designer, app, api): step grouping foundation

addresses AUTH-573
Overview
co-authored by @jbleon95
This is the foundation for Step grouping in the system. Step grouping is part of the PD redesign follow-up (originally it was part of the PD redesign but got descoped a few days ago. it IS still part of the redesign plans but will be in a follow up): https://opentrons.atlassian.net/wiki/spaces/RPDO/pages/4331339778/WIP+Step+Grouping+Architecture+Proposal+for+JSON+protocols+only
The way step grouping works is the user in PD adds the step to a group and that information gets parsed into commandAnnotations in the schema as part of a secondOrderCommand.
When uploading the protocol to the app, the commandAnnotations is part of the CompletedProtocolAnalysis which is displayed in the Timeline tab in ProtocolDetails - only on the desktop app. Note that the Timeline tab is only visible if you have the Protocol timeline feature flag turned on.
NOTE: the following video is from old PD navigation and components and can't be tested anymore. Since the redesign is soon to be released and the old components are getting deleted here, the usage of the old components has been deleted in lieu of adding the actions/selectors created in this pr to the new designs.
https://github.com/user-attachments/assets/1642d2f9-c518-49da-b453-fcf480573d8a
Test Plan

examine the attached protocol, look specifically at "commandAnnotations" key. See that there is are 2 second order commands.

commandAnnotationsTest.json

upload the protocol to the app. make sure the Protocol timeline ff is turned on and go to the "timeline" tab in protocol details. You should see the group displayed.

Changelog

create a bunch of redux actions in PD
add 2 new keys to RootState in PD (unsavedGroup, stepGroups)
extend AnnotatedSteps in the app to display the steps in the group
@jbleon95 added api and robot-server support for commandAnnotations to show up in the CompletedProtocolAnalysis

Review requests

Risk assessment
low, behind ff in app and in PD

This PR was initially created before the PD redesign work started. the PD UI components that were previously used are soon to be deprecated and deleted since the PD redesign wrote completely new UI components.
This is the followup ticket to utilize the new redux actions and selectors that were created in this PR: https://opentrons.atlassian.net/browse/AUTH-1112


PR Fix, SE to Chat SE, using CS Chat

I liked the previous sound options, would those be available again sometime? :)


fix: add focus styles fallback for IE11

Alaska Airlines Pull Request
IE 11 was not rendering focus styles on the input options when tabbing. This fallback achieves a similar effect, but is not a perfect replica (see image below). Focus styles should not change in browsers that support focus-within.

Type of change:
Please delete options that are not relevant.

[x] Revision of an existing capability

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Orion Design System Team

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: geoffrey1218:x: ecommerceUXdesignYou have signed the CLA already but the status is still pending? Let us recheck it.

:tada: This PR is included in version 1.1.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[hotfix][e2e] Fix pipeline e2e test cases failures

This PR fixes pipeline e2e test case failures.

Allowing YAML parser to accept duplicate keys to avoid conflicts between flink-conf.yaml and FLINK_PROPERTIES env
Adds missing mysql-driver.jar excluded from fat jar

@lvyanquan PTAL

LGTM. Wait for CI pass.


Update sbt, sbt-dependency-tree, ... to 1.10.5

About this PR
📦 Updates

org.scala-sbt:sbt
org.scala-sbt:sbt-dependency-tree
org.scala-sbt:scripted-plugin

from 1.9.9 to 1.10.5
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #769.


Migrate redundant water property functions to utils implementation

Some redundant implementations were overlooked in https://github.com/NREL/GEOPHIRES-X/pull/96
https://github.com/NREL/GEOPHIRES-X/blob/bf1ad58196f4217c5405941e75d09d2e17bd5a64/src/geophires_x/Reservoir.py#L13-L57
https://github.com/NREL/GEOPHIRES-X/blob/bf1ad58196f4217c5405941e75d09d2e17bd5a64/src/geophires_x/WellBores.py#L13-L29

Note: this is nontrivial, as existing testcases including example1_addons request water properties at temperatures that are outside of IAPWS bounds


Matured project to include capitalization (much like a fine wine).

It's smrt.

I'm sorry, this change would break backwards compatibility.

I don’t know how I didn’t see that before! I have so much to learn

On Jun 3, 2017, at 9:09 AM, qntm<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
I'm sorry, this change would break backwards compatibility.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/qntm/abcdefghijklmnopqrstuvwxyz/pull/1#issuecomment-305974131, or mute the thread https://github.com/notifications/unsubscribe-auth/AMTaHBYek0Rj-1P1xaWT6aVTvTAOYV-sks5sAVsKgaJpZM4Nu82l.


New Claim is not present in the App Metadata XML document

Hi,
I have tried to add another claim as:
surname2           user.givenname
but when i look into the App Metadata XML file the new claim is not present. Why?
thanks

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0800632e-a9b3-5f96-f290-207c7ef6be88
Version Independent ID: eaa3c7a0-76d5-433f-9ac3-bc72638c0ff3
Content: Tutorial: Azure Active Directory single sign-on (SSO) integration with Azure AD SAML Toolkit
Content Source: articles/active-directory/saas-apps/saml-toolkit-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@smoms Although you customize the claims for the applications, Azure AD will not add these custom claims in the Federation Metadata XML file. But when you do the SSO then they will appear correctly in the token.

#please-close


support REGEXP,RLIKE expr

Related datafuselabs/databend#3071, datafuselabs/databend#3050
sqlparser-rs did not support 'REGEXP,RLIKE'. In order to support 'REGEXP,RLIKE' expr in databend that we must support 'REGEXP,RLIKE'  in sqlparser-rs first.

@sundy-li  @PsiACE  PTAL.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

60 of 60 (100.0%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.08%) to 89.874%

Files with Coverage Reduction
New Missed Lines
%

src/parser.rs
1
84.34%

Totals

Change from base Build<PHONE_NUMBER>:
0.08%

Covered Lines:
6701

Relevant Lines:
7456

💛  - Coveralls

LGTM, yet lint is not happy.

LGTM, yet lint is not happy.

Fixed

Thanks for the contribution.


Configure kubelet Shutdown Grace Period

What this PR does / why we need it
This PR configures both the shutdownGracePeriod and shutdownGracePeriodCriticalPods. The grace period is set to 5 minutes while the critical pods grace period is set to 1 minute. This means that kubelet will start terminating critical pods (pods with Priority class set to system-cluster-critical or system-node-critical) in the last 1 minute of the shutdownGracePeriod. This is important since our CNI (cilium) is a critical pod that needs to terminated last.
This feature is implemented using systemd Inhibitor Locs. The maximum inhibit delay is controlled by the InhibitDelayMaxSec in logind. On our AWS nodes the default is set to 30 seconds, so we need to override it. This is why the /lib/systemd/logind.conf.d/zzz-kubelet-graceful-shutdown.conf is mounted in the nodes (the zzz prefix is so it always lands as the last evaluated file).
Checklist

[x] Update changelog in CHANGELOG.md.

References

Graceful Node Shutdown docs
Graceful Node Shutdown Proposal docs (there's some more info on how it works in here)
logind.conf docs
systemd inhibit docs

Trigger e2e tests

/test create
/test upgrade
/run cluster-test-suites

/test all

/test create
/test upgrade

/test create
/test upgrade


Build Failed

Hello How to get an error report when my build fail?

Post the full output of the build log somewhere and link it here.

log.txt

this is my log file

Error: Error validating package name. Package name must look like: com.company.Name

That's the app id in your cordova/config.xml file. Look for (<widget id="..."). This id must be a valid Java package name and it must have a period in its name. The current version of the CLI ensures this pattern.

Error: Error validating package name. Package name must look like: com.company.Name

The id attribute in the root widget tag of cordova/config.xml needs to be in reverse-domain notation, like org.example.myapp

after the compilation i install the apk and i see this

Why i'm still into a tabris container and not directly into my app?

Because you built a debug version of your app.  This contains all of your Cordova plugins plus the source code from your repo at the time you built it. If you need to make changes to your source code you can do so on your development machine and load them via the URL tab.
Once you perform a Release build you will no longer have any of the developer tools and your app will launch straightaway.

ok thank you


stdin example

Doing a go build on stdin.go in the examples folder and then a ./stdin causes the program to hang on  MAC El Capitan 10.11.6.

It hangs because it's waiting for stdin data. Try something like this:
$ cat /bin/ls | go run _examples/stdin.go

That worked, I figured it was waiting for keyboard stdin.