api_version with both header and parameter versioning strategies

My routes file looks like this, with identical controllers under each api_version
scope path: :api, as :api, module: :api do
  api_version module: "v1",
    header: { name: 'version', value: '1' },
    parameter: { name: 'v', value: '1' } do
      scope controller: :some do
        get 'index'
      end
      # additional controllers...
    end
  end

  api_version module: "v0",
    header: { name: 'version', value: '0' },
    parameter: { name: 'v', value: '0' } do
      scope controller: :some do
        get 'index'
      end
      # additional controllers with same names as in v1...
    end
  end
end

My api controllers have this structure in the app:
app/controllers/api/v0/some_controller.rb
app/controllers/api/v1/some_controller.rb
With this setup, an api consumer hitting any endpoint and passing ?v=0 to try to hit the v0 controller is instead routed to the v1 controller with the same name. The resolution to be able to hit v0 endpoints was to remove the header option from v1, leaving:
api_version module "v1",
    parameter: { name: 'v', value: '1' } do
    # some routez

I would like to be able to have a v1 api consumer use a header as well, is there an alternate syntax that will allow this?

@jessicb can you show me what those two controllers look like (not the whole file, but just the module and class declaration)?

Sure! They are identical:
class Api::V0::BaseController < ActionController::Base
class Api::V1::BaseController < ActionController::Base

@jessicb and what versions of Rails and versionist are you using?

I'm on rails 5.1.6 and versionist 1.5.0.

@jessicb let me replicate this setup locally and see what's going on. Stay tuned......

@jessicb Hmmm, are you sure you copied those routes correctly? I copied the above routes verbatim, and I'm getting a syntax error:
> ruby -v
ruby 2.2.5p319 (2016-04-26 revision 54774) [x86_64-darwin15]

> rails -v
Rails 5.1.6

> cat config/routes.rb
Rails.application.routes.draw do
  # issue #88

  scope path: :api, as :api, module: :api do
    api_version module: "v1",
      header: { name: 'version', value: '1' },
      parameter: { name: 'v', value: '1' } do
        scope controller: :some do
          get 'index'
        end
        # additional controllers...
      end
    end

    api_version module: "v0",
      header: { name: 'version', value: '0' },
      parameter: { name: 'v', value: '0' } do
        scope controller: :some do
          get 'index'
        end
        # additional controllers with same names as in v1...
      end
    end
  end
end

bundle exec rake routes
rake aborted!
SyntaxError: /Users/bploetz/workspace/versionist-test-rails51/config/routes.rb:4: syntax error, unexpected tSYMBEG, expecting keyword_do or '{' or '('
  scope path: :api, as :api, module: :api do
                        ^
/Users/bploetz/workspace/versionist-test-rails51/config/routes.rb:23: syntax error, unexpected keyword_end, expecting end-of-input
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/activesupport-5.1.6/lib/active_support/dependencies.rb:286:in `load'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/activesupport-5.1.6/lib/active_support/dependencies.rb:286:in `block in load'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/activesupport-5.1.6/lib/active_support/dependencies.rb:258:in `load_dependency'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/activesupport-5.1.6/lib/active_support/dependencies.rb:286:in `load'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application/routes_reloader.rb:55:in `block in load_paths'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application/routes_reloader.rb:55:in `each'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application/routes_reloader.rb:55:in `load_paths'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application/routes_reloader.rb:18:in `reload!'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application/routes_reloader.rb:41:in `block in updater'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/activesupport-5.1.6/lib/active_support/file_update_checker.rb:81:in `call'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/activesupport-5.1.6/lib/active_support/file_update_checker.rb:81:in `execute'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application/routes_reloader.rb:42:in `updater'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application/routes_reloader.rb:31:in `execute_if_updated'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application/finisher.rb:128:in `block in <module:Finisher>'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/initializable.rb:30:in `instance_exec'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/initializable.rb:30:in `run'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/initializable.rb:59:in `block in run_initializers'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/initializable.rb:58:in `run_initializers'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application.rb:353:in `initialize!'
/Users/bploetz/workspace/versionist-test-rails51/config/environment.rb:5:in `<top (required)>'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application.rb:329:in `require'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application.rb:329:in `require_environment!'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application.rb:445:in `block in run_tasks_blocks'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/rake-12.3.2/exe/rake:27:in `<top (required)>'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/bin/ruby_executable_hooks:15:in `eval'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/bin/ruby_executable_hooks:15:in `<main>'
Tasks: TOP => routes => environment
(See full trace by running task with --trace)

Let me know......

Sorry, that should be as: :api

@jessicb made that change, still no bueno:
cat config/routes.rb
Rails.application.routes.draw do
  # issue #88

  scope path: :api, as: :api, module: :api do
    api_version module: "v1",
      header: { name: 'version', value: '1' },
      parameter: { name: 'v', value: '1' } do
        scope controller: :some do
          get 'index'
        end
        # additional controllers...
      end
    end

    api_version module: "v0",
      header: { name: 'version', value: '0' },
      parameter: { name: 'v', value: '0' } do
        scope controller: :some do
          get 'index'
        end
        # additional controllers with same names as in v1...
      end
    end
  end
end

bundle exec rake routes
rake aborted!
SyntaxError: /Users/bploetz/workspace/versionist-test-rails51/config/routes.rb:24: syntax error, unexpected keyword_end, expecting end-of-input
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/activesupport-5.1.6/lib/active_support/dependencies.rb:286:in `load'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/activesupport-5.1.6/lib/active_support/dependencies.rb:286:in `block in load'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/activesupport-5.1.6/lib/active_support/dependencies.rb:258:in `load_dependency'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/activesupport-5.1.6/lib/active_support/dependencies.rb:286:in `load'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application/routes_reloader.rb:55:in `block in load_paths'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application/routes_reloader.rb:55:in `each'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application/routes_reloader.rb:55:in `load_paths'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application/routes_reloader.rb:18:in `reload!'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application/routes_reloader.rb:41:in `block in updater'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/activesupport-5.1.6/lib/active_support/file_update_checker.rb:81:in `call'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/activesupport-5.1.6/lib/active_support/file_update_checker.rb:81:in `execute'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application/routes_reloader.rb:42:in `updater'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application/routes_reloader.rb:31:in `execute_if_updated'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application/finisher.rb:128:in `block in <module:Finisher>'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/initializable.rb:30:in `instance_exec'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/initializable.rb:30:in `run'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/initializable.rb:59:in `block in run_initializers'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/initializable.rb:58:in `run_initializers'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application.rb:353:in `initialize!'
/Users/bploetz/workspace/versionist-test-rails51/config/environment.rb:5:in `<top (required)>'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application.rb:329:in `require'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application.rb:329:in `require_environment!'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/railties-5.1.6/lib/rails/application.rb:445:in `block in run_tasks_blocks'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/gems/rake-12.3.2/exe/rake:27:in `<top (required)>'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/bin/ruby_executable_hooks:15:in `eval'
/Users/bploetz/.rvm/gems/ruby-2.2.5@versionist-test-rails51/bin/ruby_executable_hooks:15:in `<main>'
Tasks: TOP => routes => environment
(See full trace by running task with --trace)

Apologies for the extra end there, this should work:
Rails.application.routes.draw do
  scope path: :api, as: :api, module: :api do
    api_version module: "v1",
      header: { name: 'version', value: '1' },
      parameter: { name: 'v', value: '1' } do
        scope controller: :base do
          get 'index'
        end
      end

    api_version module: "v0",
      header: { name: 'version', value: '0' },
      parameter: { name: 'v', value: '0' } do
      scope controller: :base do
        get 'index'
      end
    end
  end
end

@jessicb better!  And just to confirm, you said above that
app/controllers/api/v0/some_controller.rb
contains
class Api::V0::BaseController < ActionController::Base
But that can't be right (rails complains about this). Can you show me what your base controller looks like for v0, and what some_controller.rb looks like as well?

Sorry! I'm providing skeletal examples here, because the actual files are large...
These controllers should contain the class definition provided above.
app/controllers/api/v0/base_controller.rb
app/controllers/api/v1/base_controller.rb
Then the some_controller files should contain:
class Api::V0::SomeController < Api::V0::BaseController
  def index
  end
end

class Api::V1::SomeController < Api::V1::BaseController
  def index
  end
end

This gives me a bundle exec rake routes:
           Prefix Verb URI Pattern          Controller#Action
        api_index GET  /api/index(.:format) api/v1/some#index
                  GET  /api/index(.:format) api/v1/some#index
                  GET  /api/index(.:format) api/v0/some#index
                  GET  /api/index(.:format) api/v0/some#index

@jessicb no worries, it's just important that I'm comparing apples to apples when trying to reproduce this issue. :) Stay tuned......

@jessicb this bit:
scope controller: :base do
  get 'index'
end

What exactly is that doing, or what are you trying to have that do? I've never seen scope: :controller before. And what's weird is if I don't have an index action in class Api::V1::BaseController rails complains.
Started GET "/api/index" for <IP_ADDRESS> at 2019-05-03 16:23:14 -0400

AbstractController::ActionNotFound (The action 'index' could not be found for Api::V1::BaseController):

Try this instead of scope controller: :base do.
scope controller: :some, as: :some, path: :some do
And then the endpoints would be /api/some/index?v=0 vs /api/some/index?v=1.

@jessicb Ok, I did something similar (not exactly) and I can reproduce the bug. Stay tuned........

@jessicb I'm still trying to find the bug that's causing this, but in the mean time I've found that, at least for me locally, if I change the order of the api_version blocks in the routes.rb file so that 0 comes first and then 1, everything works as expected. So you can give that a try and see if it works for you too.
Still working on it though.....

@jessicb ok, figured it out. So it turns out that it's not the order of api_version blocks in routes.rb that was the culprit, it's actually that it was picking up your header v1 strategy all the time. Why?
The way the header strategy works is that it looks for a header on the request with the name you've configured in your header strategy, grabs that header's value, and sees if the configured header value matches the header's value on the request. If not, it moves on to the other configured versioning strategies looking for a match.
You unfortunately chose "version" as your header name. Rack comes with a bunch of built in headers, one of which is "HTTP_VERSION" (note: the HTTP_ prefix is added by rack for all incoming request headers). For example:
["HTTP_VERSION", "HTTP/1.1"]

That HTTP_ prefix is removed by Rails and the uppercased/underscored string is returned to it's normal version before being stored as the key for the header in the ActionDispatch::Http::Headers object (see the comment at the top of https://api.rubyonrails.org/classes/ActionDispatch/Http/Headers.html for an example).  So the "HTTP_VERSION" header just becomes "version", which is the versioning header you configured in api_version. And since HTTP headers can contain multiple values and quality qualifiers, versionist doesn't look for an exact match of the header value, just that your configured header value is within the header value string. See this issue for the gory details as to why. So in this case, your configured header version of "1" is found within "HTTP/1.1." and thus the false positive match.
Ugh.
I've pushed up a change which will raise an exception if you choose "version" for your header name, as this clashes with the builtin HTTP_VERSION header as noted above. So you will need to choose a different header name (API-VERSION, X-VERSION, etc) to use for your header versioning strategy configuration. Once I changed the header name in my example app, everything worked as expected.
If you could update your Gemfile to point at this change
gem 'versionist', :git => 'https://github.com/bploetz/versionist.git', :branch => 'fix/issue_88'

And then run bundle update versionist, you should see it complain about your routes configuration on startup. Change your header name to something other than "version" and you should be good to go.
I will merge this to master and release a new version of versionist with this change when you confirm this works for you.
Any questions let me know.

@bploetz Thanks for digging into this, it's an interesting bug. I'm surprised that no one else has run into this using version as a header name...
I will test and report back, thanks again.

@jessicb yeah I had the same reaction: how has no one run into this already?! :)

@bploetz This is looking good after further testing!

@jessicb great, thanks for testing. Will release a new version with this change.

versionist 2.0.0 has been released with this change.
https://rubygems.org/gems/versionist


Dispatcher book example backwards?

The book has this example of creating a dispatcher here:
    let mut dispatcher = DispatcherBuilder::new()
        .add(HelloWorld, "hello_world", &[])
        .add(UpdatePos, "update_pos", &["hello_world"])
        .build();

I believe this results in HelloWorld running before UpdatePos.  The call to dispatcher.dispatch results in displaying the original positions without velocity applied.  If you add a second call to dispatcher.dispatch you see the positions with
velocity applied once.  Is this what was intended?
    let mut dispatcher = DispatcherBuilder::new()
        .add(UpdatePos, "update_pos", &[])
        .add(HelloWorld, "hello_world", &["update_pos"])
        .build();

Yeah, the intention wasn't to show the updated positions but just how to build the system graph. If you think it's too confusing, feel free to create a PR.

Closing due to inactivity.


feat(Routes): add nitro sticker pack fetching by ID

Please describe the changes this PR makes and why it should be merged:
Reference Discord API Docs PRs or commits:

https://github.com/discord/discord-api-docs/pull/4193

Apparently Discord doesn't want this route to be used. (Source)


Is it possible to calculate the used stack by every function call tree?

Now Ghidra can show function call graph, can it show how much
stack every function use and the max stack size of any function
call tree?

Ghidra does not have this capability.


fix(ci): Handle cases when job does not have a finished date

What does this PR do?
Handle a specific case to prevent script failure when job has no finished_date

Motivation
Prevent job failure

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

n end date?

@KSerrania it's skipped jobs that have no finished_at date.
On the case of this pipeline the following required jobs are skipped
new-e2e-agent-platform-install-script-suse-a7-x86_64
new-e2e-agent-platform-install-script-ubuntu-a7-x86_64
new-e2e-agent-platform-install-script-debian-iot-agent-a7-x86_64
new-e2e-agent-platform-install-script-debian-a7-x86_64
deploy_suse_rpm_testing_x64-a7
deploy_deb_testing-a7_x64

because of the failures on package_build step.
We might maybe ignore the statistics in such case, if all the required jobs are not launched

/merge


Feat: Schema overriding hook for OpenApiConfig [POC]

Adds a hook which allows overriding OpenAPI schema definitions.
This is useful for two scenarios:

Override the schema description of a generic class with specific type parameter, as the annotated Schema description might not be specific enough.
Example: TypeKeyNameVerboseDto<CountryCode>
Clone a schema, overriding its name and description, to use it for some specific field.
This is due to OpenAPI limitations which don't allow to specify a field description for complex singular objects, see https://github.com/springdoc/springdoc-openapi/issues/1178 .
Example: legalAddress in LegalEntityPartnerCreateRequest etc.

This is just a proof-of-concept how it could be done. I don't know if it's worth it considering the effort, especially in the second case.
Proof of concept for https://github.com/eclipse-tractusx/bpdm/issues/409
https://github.com/eclipse-tractusx/bpdm/pull/398 must be merged first

The ADR links to this PR saying "The potential workarounds are implemented as proof-of-concept in ...".
I don't know if the PR is still readable after closing it?

The ADR links to this PR saying "The potential workarounds are implemented as proof-of-concept in ...". I don't know if the PR is still readable after closing it?

No worries, the closed pull request is still readable and can be reopened as well. I will close it for now. If we feel we need to open it, we can do so at a later time.


build fixes

closes gh-1994

All good for me. Just wait for CI

I could not build this patch with flow disabled:
./build/stage/lib/common/sol-types.o: In function sol_drange_mod': sol-types.c:(.text.sol_drange_mod+0x48): undefined reference to fmod'
./build/stage/shared/sol-util.o: In function sol_util_double_equal': sol-util.c:(.text.sol_util_double_equal+0x8d): undefined reference to fmin'
collect2: error: ld returned 1 exit status
tools/build/Makefile.rules:394: recipe for target 'build/soletta_sysroot/usr/lib/libsoletta.so' failed
make: *** [build/soletta_sysroot/usr/lib/libsoletta.so] Error 1
Please, look at https://github.com/solettaproject/soletta/pull/1996/commits/64ac7ea3f07d3a26a3d264869f28dc376ba64cc9 (rogue commit to fix build that I've written when testing IPM, I wasn't aware of https://github.com/solettaproject/soletta/issues/1994)

@edersondisouza make clean/git clean?

On 09-05-2016 15:58, Gustavo Sverzut Barbieri wrote:

@edersondisouza https://github.com/edersondisouza make clean/git clean?

I'm always using make distclean, not better.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/solettaproject/soletta/pull/1997#issuecomment-217956529

fine, I wasn't able to reproduce this issue with the ldflag, but I'm cherry-picking your commit and let's see if it's ok now. Waiting for CI to run all tests...

On 09-05-2016 16:20, Bruno Dilly wrote:

fine, I wasn't able to reproduce this issue with the ldflag, but I'm
cherry-picking your commit and let's see if it's ok now. Waiting for CI
to run all tests...

Worked here, tks! But weird that you couldn't reproduce it...

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/solettaproject/soletta/pull/1997#issuecomment-217962338


How many GPU memory did you use?

Hi, I used a Titan XP to train or test your code, but I meet the error of 'cuda out of memory', so how can I use multi-gpu to train your code or how can I switch the dataset to MSVD?

what batch size did you set?

what's the batch size you set?

I just use the command you provided.

It's strange. I trained the model using a 16g GPU.

Oh, maybe the needed gpu memory is more than the Titan xp which only has 12G
---Original---
From<EMAIL_ADDRESS>Date: Mon, Nov 23, 2020 18:28 PM
To<EMAIL_ADDRESS>Cc: "涂云斌"<1515503470<EMAIL_ADDRESS>Subject: Re: [SydCaption/SAAT] How many GPU memory did you use? (#25)
It's strange. I trained the model using a 16g GPU.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

You can try to slightly reduce the batch size to 56 or 48, though I remember it wasn't that much.

OK, thank you!
---Original---
From<EMAIL_ADDRESS>Date: Mon, Nov 23, 2020 19:19 PM
To<EMAIL_ADDRESS>Cc: "涂云斌"<1515503470<EMAIL_ADDRESS>Subject: Re: [SydCaption/SAAT] How many GPU memory did you use? (#25)
You can try to slightly reduce the batch size to 56 or 48, though I remember it wasn't that much.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


install_script fails on macOS Mojave 10.14.3

Was trying to run install_script on macOS Mojave and came across the linking error.
[ 50%] Linking CXX shared library libproducer.dylib
Undefined symbols for architecture x86_64:
  "_CRYPTO_THREADID_set_callback", referenced from:
      OpenSSLThreadCallbacks::registerThreadingCallbacks() in OpenSSLThreadCallbacks.cpp.o
  "_CRYPTO_THREADID_set_numeric", referenced from:
      OpenSSLThreadCallbacks::openSSLThreadIdCallback(crypto_threadid_st*) in OpenSSLThreadCallbacks.cpp.o
  "_CRYPTO_num_locks", referenced from:
      OpenSSLThreadCallbacks::initOpenSSLMutexes() in OpenSSLThreadCallbacks.cpp.o
  "_CRYPTO_set_dynlock_create_callback", referenced from:
      OpenSSLThreadCallbacks::registerThreadingCallbacks() in OpenSSLThreadCallbacks.cpp.o
  "_CRYPTO_set_dynlock_destroy_callback", referenced from:
      OpenSSLThreadCallbacks::registerThreadingCallbacks() in OpenSSLThreadCallbacks.cpp.o
  "_CRYPTO_set_dynlock_lock_callback", referenced from:
      OpenSSLThreadCallbacks::registerThreadingCallbacks() in OpenSSLThreadCallbacks.cpp.o
  "_CRYPTO_set_locking_callback", referenced from:
      OpenSSLThreadCallbacks::registerThreadingCallbacks() in OpenSSLThreadCallbacks.cpp.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [libproducer.dylib] Error 1
make[1]: *** [CMakeFiles/producer.dir/all] Error 2
make: *** [all] Error 2

So far I tried deleting downloads, CmakeCache.txt, CMakeFiles before running the install script but same error.

I got the latest release 1.7.9 and was able to compile successfully. Closing this issue.


Adding ability to open bookmark in splits

For bookmarked files, it works the same as executing the shortcut on a file node.
However, it's different for bookmarked directories. Currently, it selects the directory in the tree if the node is visible. Otherwise nothing happens. What should be the best behaviour?

activate the bookmarked directory?
or output a message and leave the cursor on the bookmark?
call s:echo("cannot open bookmarked directory in a split")

Preference?

Hey, I wont be pulling this as I have made some pretty big refactors over the last few days that implement this feature as a side effect.
The diff stat is pretty large, so I was testing it at home for a couple of days before pushing.
git diff --stat 3620029ae0c82d4ad83f2ddfe26e55235c975933..HEAD
plugin/NERD_tree.vim |  541 ++++++++++++++++++++++++++------------------------
1 files changed, 284 insertions(+), 257 deletions(-)

FYI, bookmarked files AND dirs can now be opened in splits/vsplits/new tabs and in the previous window. Also, this sort of hack call s:openVSplit(s:TreeFileNode.New(a:bm.path)) has finally been removed from the code :)
Ironically, I started doing this refactor in response to #35


install: Update Fedora instructions

kata packages are already present on Fedora 31+. Knowing that, there's
no reason to use the packages provided by OpenSUSE.
Signed-off-by: Fabiano Fidêncio<EMAIL_ADDRESS>

Shall I create an issue to link in the patch?

@fidencio yes, and include fixes #xxx in your commit message

Details on how we "execute" documents (purely for interests sake):

https://github.com/kata-containers/documentation/blob/master/Documentation-Requirements.md#code-blocks
https://github.com/kata-containers/tests/tree/master/cmd/kata-manager
https://github.com/kata-containers/tests/blob/master/.ci/kata-doc-to-script.sh

Okay, based on @crobinso's explanation and the @jodh-intel's review, I've updated the patch.

Thanks @fidencio. We do still need to understand the situation regarding the kata kernel and image though. How are users expected to obtain these assets on F31+?

Doh! Looks like I didn't get a mail about the latest update there. I'd like to test this tomorrow before acking, but thanks for updating!

@jodh-intel I had tried kata on fedora 31 the other day, and it does not work out of the box.
First, I realised selinux needed to be disabled. We need to brainstorm what needs to be done on Kata side to add this support.
Fedora 31 also ships with cgroupsv2 support. We are currently working on adding that.
So, one needs to explicitly fallback to cgroupsv1 for Kata.
Booting from rootfs fails as kernel lacks NVDIMM support.  So today just initrd works.
Complete list of bugs, some of them non-blocking:
https://apps.fedoraproject.org/packages/kata-runtime/bugs

Yes I should have mentioned, the 'out of the box' piece has some problems. What we have been telling people is:
# onetime setup per host boot
sudo mkdir -p /run/cgroupv1; sudo mount -t cgroup -o cpu,cpuacct cgroup /run/cgroupv1/

# Run a sample container
sudo podman run --security-opt label=disable --runtime=/usr/bin/kata-runtime --rm -it alpine sh

First part will set up enough of cgroupv1 to make kata happy (last I checked). You can also boot the host with systemd.unified_cgroup_hierarchy=0
The podman --security-opt label=disable removes the need to fully disable selinux.
podman also provides a helpful --runtime option that saves having to make system defaults changes.
FWIW on Fedora docker does not get a lot of love
The nvdimm/image boot issue is known, due to the driver not being built into the kernel. Unfortunately we are at an impasse on that one at the moment: https://bugzilla.redhat.com/show_bug.cgi?id=1750581

@crobinso Thanks, passing --security-opt label=disable works too. I had tried with disabling selinux on a system level earlier. With the above steps you mentioned I got kata working with podman.
We should add the above steps to the documentation in this PR.
Since cgroupsv2 is the default, docker does not work either out of box on fedora31. The only way I got it working is by passing  systemd.unified_cgroup_hierarchy=0 on the kernel command line and rebooting. @crobinso Is that the recommended way to go about for enabling docker ?
Lastly, I noticed that the configuration.toml file for kata exists under /usr/share/kata-containers/defaults/configuration.toml in fedora31 instead of /usr/share/defaults/kata-containers/configuration.toml. Was there any particular reason for picking the former.
This needs a mention in our docs as well.

On 19 Dec 2019, at 02:15, Archana Shinde<EMAIL_ADDRESS>wrote:
@crobinso Thanks, passing --security-opt label=disable works too. I had tried with disabling selinux on a system level earlier. With the above steps you mentioned I got kata working with podman.
We should add the above steps to the documentation in this PR.
Since cgroupsv2 is the default, docker does not work either out of box on fedora31. The only way I got it working is by passing systemd.unified_cgroup_hierarchy=0 on the kernel command line and rebooting. @crobinso Is that the recommended way to go about for enabling docker ?

I have other issues with docker so I have

Lastly, I noticed that the configuration.toml file for kata exists under /usr/share/kata-containers/defaults/configuration.toml in fedora31 instead of /usr/share/defaults/kata-containers/configuration.toml. Was there any particular reason for picking the former.

Not many packages seem to put things directly in /usr/share/defaults on Fedora. Any reason why it matters for Kata (besides instructions)?

This needs a mention in our docs as well.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Adding dnm label whilst we work through these issues...

@jodh-intel @fidencio what is the status of this instructions? should we add the specification that to run docker with fedora 31 we need cgroupsv1?

imho our install docs / scripts cannot reasonably modify the way a users entire system boots and operates just to accommodate Docker.
Working on that not unreasonable assumption, I think the best we can do is to ensure the install docs detect cgroups v2 and error with a helpful message that:

Explains the cgroups v1/v2 issue.
States that installing (docker) on distro versions using cgroups v2 (such as F31) require manual intervention.
Listing what intervention is required along with pros / cons.

In fact, I think this topic should be discussed by the @kata-containers/architecture-committee.

/test

/test

/test

Oh, this one was superseded by https://github.com/kata-containers/documentation/pull/711.  Good to know! :-)
Thanks a lot for the reviews, I'm closing this one.


Fix Chart automation release-2.1

https://github.com/open-cluster-management/backlog/issues/9784

This will need to wait because CICD has said to not add anything to the 2.1.x stream until 2.1.5 has shipped

/hold


Fixing flaky tests

Codecov Report

Merging #85 (dc3dd3d) into main (7c2bd92) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##               main      #85   +/-   ##
=========================================
  Coverage     83.37%   83.38%
  Complexity      146      146
=========================================
  Files            39       39
  Lines          1666     1667    +1
  Branches        264      264
=========================================
+ Hits           1389     1390    +1
  Misses          172      172
  Partials        105      105

Impacted Files
Coverage Δ

...adata/parser/step/kamelet/KameletParseCatalog.java
100.00% <ø> (ø)

...o/backend/metadata/parser/ClusterParseCatalog.java
90.32% <100.00%> (ø)

Continue to review full report at Codecov.

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


Fix wrong env key in build time configuration docs

Env-Key definition should be constantly either customEnv or customKey - I went for customKey.

Thank you! 🙏


tz-<IP_ADDRESS> test suite failure

Citing from http://hydra.cryp.to/build/1733581/nixlog/1/raw:
Preprocessing test suite 'th-test' for tz-<IP_ADDRESS>...
[1 of 1] Compiling Main             ( tests/testTH.hs, dist/build/th-test/th-test-tmp/Main.dyn_o )

tests/testTH.hs:10:16:
    Exception when trying to run compile-time code:
      /usr/share/zoneinfo/Europe/Budapest: openBinaryFile: does not exist (No such file or directory)
    Code: includeSystemTZ "Europe/Budapest"
    In the splice: $(includeSystemTZ "Europe/Budapest")

Apparently, the test suite uses hard-coded system paths that don't exist (on NixOS).
Cc: @klao

@peti Does NixOS put tzdata information in some other path? At least on ubuntu that file is provided by e.g. http://packages.ubuntu.com/xenial/tzdata and I'm unaware how to have different system zoneinfo (compare to locale information in /usr/share/locale ?)

Does NixOS put tzdata information in some other path?

Yes, it does. The directory /usr does not exist on NixOS.

@peti Is the TZDIR environment variable set at the point where the tests are run? My package tries to use it, and only falls back to /usr/share/zoneinfo if it's not set...
Or what is the proper way to figuring out where to look for system time zone files under NixOS?

$TZDIR is not set by default, but I can make it available. Let me check ...

With $TZDIR available, the test suite succeeds, indeed. Thank you very much for the quick response!

Great, thank you too for taking care of all of our stuff on NixOS!


字体颜色配比不合理，导致部分颜色观察不是很清晰

[Enter feedback here]

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

ID: 583ae3e7-5915-f22b-e54c-6c100cf2a7da
Version Independent ID: 95f2549e-29f9-e31a-b4d0-432b971643ff
Content: Tutorial: Create a web API with ASP.NET Core
Content Source: aspnetcore/tutorials/first-web-api.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

The font color ratio is unreasonable, resulting in some colors that are not very clear

Moved to https://github.com/MicrosoftDocs/feedback/issues/3206


macOS launchd agent associated_bundle_identifiers should be Array instead of Hash

Description
The current launchd.rb resource is requiring a hash and creating a launchagent incorrectly. The result should produce an array of bundle identifiers instead of a hash: https://github.com/chef/chef/commit/703953c7e6db6c57a230741cd960b1b914420300
Chef Version
Chef Infra Client: 18.1.0
Platform Version
macOS 13.2
Replication Case
## default.rb
...
    'launchagent' => {
      'associated_bundle_identifiers' => {
        'AKey' => 'com.github.bundle.identifier'
      },
...

Results in a file like:
/Library/LaunchAgents/com.github.bundle.identifier
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>AssociatedBundleIdentifiers</key>
	<dict>
		<key>AKey</key>
		<string>com.github.bundle.identifier</string>
	</dict>
	<key>Label</key>
	<string>com.github.bundle.identifier</string>
	<key>LimitLoadToSessionType</key>
...
..
.

when the chef code should be:
##default.rb
...
    'launchagent' => {
      'associated_bundle_identifiers' => [
        'com.github.bundle.identifier'
      ],
...

and the resulting file should look like:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>AssociatedBundleIdentifiers</key>
	<array>
		<string>com.github.bundle.identifier</string>
	</array>
	<key>Label</key>
	<string>com.github.bundle.identifier</string>

Attempting to create an array results in a failed chef run because a Hash is required.
[2023-01-05T12:42:31-05:00] FATAL: Chef::Exceptions::ValidationFailed: cpe_launchd[Managing all of launchd] (cpe_launchd::default line 15) had an error: Chef::Exceptions::ValidationFailed: Property associated_bundle_identifiers must be one of: Hash!  You passed ["com.github.bundle.identifier"].

#13477

PR #13937 follow-up fix, subsequent tag v18.3.8, stable release v18.4.2


Nodejs 20 support

Hello, are you planning support for node 20? I privately uploaded the version locally and apparently I didn't see any errors. The only point was the restriction in package.json

@operacional6
Hello!
Yes, we would like to do an upgrade soon.
I have not had much time to maintain it lately.


jellyfin-ffmpeg: fix libaribcaption inconsistency

ffmpeg_6-full checks enabling libaribcaption against a version value of 6.1 sourced from a different scope than the derivation version of 6.0.1 used in the overrideAttrs section.
Fixes https://github.com/NixOS/nixpkgs/issues/280645
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

@anund there's also a patch in ffmpeg's code at line 352 that makes the same check. It needs to be fixed in order to build properly on darwin.

This is also being discussed here: https://github.com/NixOS/nixpkgs/pull/280784

I'd rather work around a bug in the "upstream" package rather than the "downstream" one.
https://github.com/NixOS/nixpkgs/pull/280784


Extra items for sets and dictionaries of the same size

Comparing Set([1, 2]) and Set([1, 3]) result in
Missing: 2

This is a partial information, because there is 3 which balances the count but is totally unexpected.
This change makes the result to be:
Missing: 2
Extra: 3

Comparing dictionaries : ["1": "1", "2": "2"] and ["1": "1", "3": "3"]
Before:
Key 2:
|	Received: nil
|	Expected: Optional("2")

After:
Missing key pairs:
|	2: Optional("2")

Extra key pairs:
|	3: Optional("3")

Fixed and squashed.

Fixed and squashed.

Since it doesn't block merge I prefer staying as close as possible to the original Difference code.

Since it doesn't block merge I prefer staying as close as possible to the original Difference code.

Most of the violations are for long lines, and in some cases you wrote if () { ... } while in swift you don't have to use () in the if. That's all.
Please address these issues.
It's bad style and adds noise when CRing.

Most of the violations are for long lines, and in some cases you wrote if () { ... } while in swift you don't have to use () in the if. That's all.
Please address these issues.
It's bad style and adds noise when CRing.

I see

I see


ditaval not coloring anymore in 2.0.1 but colored nicely in 1.x

I just migrated from DITA-OT 1.x to 2.0.1 and noticed that the same, unchanged project does not apply colors anymore provided by ditaval:
<val>
	<prop att="audience" val="developer" action="flag" backcolor="blue" />
	<prop att="audience" val="service" action="flag" backcolor="orange" />
	<prop att="audience" val="admin" action="flag" backcolor="yellow"/>
</val>

What happens is that the text in fact is still included, but not colored at all, it still has transparent / white background.
As I do not assume that the ditaval syntax has changed significantly, I assume this is a bug.

Which transtype?

pdf

I can provide a closed-source ("confidential" DITA content) project reproducing the problem if you like, so you can reproduce rather simple. Just send me your e-Mail address and I will provide a download link for it.

Please create a small test set of dummy information as a Gist to reproduce this issue instead.

Cannot reproduce anymore. I assume it was a side effect of #1294 or at least might have a related cause. I suggest to close #1293 to see if it will happen again after #1294 is fixed.


[SPARK-17242][Document]Update links of external dstream projects

What changes were proposed in this pull request?
Updated links of external dstream projects.
How was this patch tested?
Just document changes.

Test build #64434 has started for PR 14814 at commit 17bb37e.

/cc @rxin

Test build #64434 has finished for PR 14814 at commit 17bb37e.

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/64434/
Test PASSed.

Test build #64444 has started for PR 14814 at commit 46bf9ab.

Test build #64444 has finished for PR 14814 at commit 46bf9ab.

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/64444/
Test PASSed.

Merging in master/2.0.


[project monitoring v2] editing prometheus rule throws an error when saved

Setup

Rancher version:
Browser type & version:

Describe the bug
Attempted to edit prometheus rule, error 'name' contains an invalid character
To Reproduce

click monitoring > alerting > advanced > prometheus rules
select a rule that includes a '.' and edit config
modify a value
click save

Result
"Name" contains an invalid character: . (the dot is included in the name of the selected prom rule)
impl.js:182 CreateEditView mixin failed to save:  Array(1)
Expected Result
rule saved
Screenshots

Need to determine if the . is a known Grafana issue or not since we'd need to work around that.

The error message itself is either originating from a specific rule in the model (see code snippet from model below paragraph) so it seems like the error message should be preventing the user from saving. I think @aiyengar2 had mentioned that these prometheus rules were automatically created and therefore bypassed validation rules on the backend but that would indicate that these rules shouldn't be available to edit.
      {
        nullable:       false,
        path:           'metadata.name',
        required:       true,
        translationKey: 'generic.name',
        type:           'dnsLabel',
      }

The warning message This PrometheusRule is managed by the Helm app rancher-monitoring; changes made here will likely be overwritten the next time Helm runs. seems to indicate that we shouldn't be letting the user perform this edit to begin with. That warning seems to be keyed off of the following code in the resourceDetail masthead:
managedWarning() {
      const { value } = this;
      const labels = value?.metadata?.labels || {};

      const managedBy = labels[KUBERNETES.MANAGED_BY] || '';
      const appName = labels[KUBERNETES.MANAGED_NAME] || labels[KUBERNETES.INSTANCE] || '';

      return {
        show:    this.mode === _EDIT && !!managedBy,
        type:    value?.kind || '',
        hasName: appName ? 'yes' : 'no',
        appName,
        managedBy,
      };
    },

I can probably bake some additional logic into the model to remove the "edit config" and "edit yaml" options from the action menu if that's the route we need to go or I can remove the customValidationRule from the model which we'd probably want to think critically about since this rule was specifically created in this pull request: https://github.com/rancher/dashboard/pull/1685 for this issue: https://github.com/rancher/dashboard/issues/811

This is odd. We've documented that users are supposed to be able to edit PrometheusRules. https://rancher.com/docs/rancher/v2.6/en/monitoring-alerting/configuration/advanced/prometheusrules/ It's the Prometheus resource that you're not supposed to touch because it's managed, not PrometheusRules.
It looks like the "managed by" label is being incorrectly added to the metadata of the PrometheusRule. I think.

This runs into a grey zone whereby we should guide the users to not modify certain rule names since they're internal but they could based on what's doable via kubectl.
Overall, this is a DNS validation rule tied to . but since this is a Prometheus rule. Prometheus has its own validation mechanism that we could leverage so that we can look at this down the road.

@aiyengar2 How does the resource get created with a . in it? How is that a valid k8s resource name?
For now, we can detect an invalid name and prevent editing and show a banner at the top saying that the resource can not be edited.

Validator in place and working. Just need to disable entire form and provide banner when "." in the name field.


Typescript language service suddenly dies

Issue Type: Bug
Typescript language service suddenly dies
VS Code version: Code 1.66.2 (dfd34e8260c270da74b5c2d86d61aee4b6d56977, 2022-04-11T07:49:20.994Z)
OS version: Darwin x64 18.7.0
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8279U CPU @ 2.40GHz (8 x 2400)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
6, 4, 3

Memory (System)
8.00GB (0.05GB free)

Process Argv
--crash-reporter-id 58879c26-1b7f-45d1-a0bd-d3b792894300

Screen Reader
no

VM
0%

Extensions (48)

Extension
Author (truncated)
Version

rainbow-brackets
2gu
0.0.6

better-comments
aar
3.0.0

scss-lint
ada
0.1.10

vscode-css-formatter
aes
1.0.2

vscode-django
bat
1.10.0

simple-react-snippets
bur
1.2.6

npm-intellisense
chr
1.4.1

bracket-pair-colorizer-2
Coe
0.2.4

python-environment-manager
don
1.0.4

python-extension-pack
don
1.7.0

es7-react-js-snippets
dsz
4.4.3

vscode-html-css
ecm
1.11.0

Solidity
Ele
0.0.58

vscode-great-icons
emm
2.1.86

auto-close-tag
for
0.5.14

auto-rename-tag
for
0.1.10

sass-lint
gle
1.0.7

solidity
Jua
0.0.139

vsc-python-indent
Kev
1.15.0

MagicPython
mag
1.1.0

code-beautifier
mic
2.3.3

vscode-scss
mrm
0.10.0

vscode-docker
ms-
1.22.0

csharp
ms-
1.24.4

vscode-kubernetes-tools
ms-
1.3.7

python
ms-
2022.4.1

vscode-pylance
ms-
2022.4.2

remote-containers
ms-
0.231.6

vscode-typescript-tslint-plugin
ms-
1.3.4

language-liquid
nei
0.1.1

autodocstring
njp
0.6.1

prisma
Pri
3.12.0

typescript-hero
rbb
3.0.0

vscode-yaml
red
1.6.0

format-html-in-php
rif
1.7.0

markdown-preview-enhanced
shd
0.6.2

autoimport
ste
1.5.4

vscode-stylelint
sty
1.2.2

open-in-browser
tec
2.0.0

vscode-helm
tec
0.4.0

stylelint
thi
0.51.0

python
tht
0.2.3

helm-intellisense
Tim
0.14.2

vscodeintellicode
Vis
1.2.20

jinja
who
0.0.8

change-case
wma
1.0.0

markdown-all-in-one
yzh
3.4.3

html-css-class-completion
Zig
1.20.0

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonvspyt551:30345470
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
cppdebugcf:30475217

+1

+1

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

Yes after i had this error, disabled all extensions, besides the Typescript language service, and had the same problem. It was about a NextJS+Typescript+React code base with a lot of dependencies though. It occured on a large file i had to refactor (~1200 lines, multiple components in one tsx)
Don't know about latest version, i will install tomorrow and will try to verify it again.

If you see this in VS Code insiders, please share a project that demonstrates the issue so we can investigate

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Changes to repo-header-download-drop

Changed the repo-header-download-drop url input to behave slightly different. When clicking on the url input it now selects the whole url and you can copy it manually too. (When using a Flash Blocker for example.). Also I have replaced the Red Circle cursor (due to the default disabled class) with the default one. The behavior is now the same as on github.com.
Before:

After:

Looks good! Thanks!


Carry -- Update to Joyent Install Doc #11687

I'm gong to pick this up after the release...also...I'm not sure how this fits with the recent commentary coming in on Joyent installation.

I guess checking in with @shykes is in order!

@thaJeztah should this be closed?

Pretty sure we do, the joyent.md file doesn't exists anymore :sweat_smile:


Add directoryConfig to globalData

The directory config is not available to immediately invoked plugins (like vite), so previously we were passing directories explicitly. Additionally, the publicDir was not available in the global data at all, so the iiifConfig was previously parsing the vite options to get it.
Changes:

Provide inputDir outputDir and publicDir to globalData plugin and add them to globalData under directoryConfig key
Decouple iiifConfig from vite plugin

@mphstudios that property is not available to the plugins that we invoke without using addPlugin (for example, the vite plugin)


Allow multiple stories being generated during interactive learning

Rasa Core version:
0.11.6
Python version:
Python 2.7.15
Operating system (windows, osx, ...):
osx
Issue:
Starting up the interactive learning session takes quite a while. So it would be nice to add multiple stories in one session. Right now you can use /restart to start over, but you lose your progress by doing so. Maybe there could be a /new to start a new conversation / story.

in the master version of core, if you do /restart it will start over, but it will still export all your conversations once you tell it to export :) could you try installing the master version?

@akelad : I just upgrade to 0.12 (master branch), but I still see the same behavior. After doing /restart it asks you to confirm that the intent is restart, the action is restart and then it clears the history. If you then have another conversation and then /stop and export, the stories.md only contains the last conversation.

Ok, I just found the solution. Instead of restarting with /restart which clears the history, you should /stop and then select "Start fresh". Then you keep all the stories.
Thanks, that's great!

@tmbo is that correct behaviour with /restart?

I guess we should properly handle /restart and do the same as we do with the Start fresh menu item

cool, will create a new issue


Add golangci-lint

@fkondej I am bumping this as I am preparing a PR (#262) that fixes the offences raised by golangci-lint.
Do you think it's possible to have this working on jenkins instead of github ?

After discussing with @jeremyletang, having it on github for now is ok.


feat: Add support to mark features pending. Update fcs.unloadApp invocation

:tada: This PR is included in version 1.3.0-dev.13 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


⚠ Secret Website 2 has degraded performance

In 6834b9e, Secret Website 2 ($SECRET_WEBSITE_2) experienced degraded performance:

HTTP code: 200
Response time: 4386 ms

Resolved: Secret Website 2 performance has improved in 78584d0.


Implement a function to check if the DB is initialised with the proper seed data.

Implement a function to check if the DB is initialized with the proper seed data

Check if the tables in the DB have seed data related to the erc20gateway contract.

Verification of Gateway Address is sufficient enough to check if the DB is initialised with the proper seed data.


Add hCard support to the contributors page.

I don't see the value in adding this. The contributors list has a link to any domain, which could link off to something which offers the hcard.

Hcard get picked up by search etc
On Thu, 17 Sep 2015 21:19 Matthew Gaunt<EMAIL_ADDRESS>wrote:

I don't see the value in adding this. The contributors list has a link to
any domain, which could link off to something which offers the hcard.
—
Reply to this email directly or view it on GitHub
https://github.com/google/WebFundamentals/issues/675#issuecomment-141215937
.

Paul did this as part of the focus week.


Simplify to using one Json serializer in Java samples

We are currently using Jackson in output binding samples and GSON in trigger samples.
### Tasks
- [x] Update GitHub samples
- [x] Update MSDocs
- [x] Update Maven templates

PR to update MSDocs: https://github.com/MicrosoftDocs/azure-docs-pr/pull/261588


[B] - Score set issue with greenhouse

After purchasing two greenhouses, and losing, you reset, and it stays at 101M

This issue needs to be verified, however, this should be fixed

this issue has been fixed in the latest preview build


i.MX EPIT Timer Driver

This adds EPIT driver and enables it on M4 core of i.MX 6SoloX SoC and on UDOO Neo Full board.
The driver conforms to the new counter API (#8340, #8331) and should be merged into topic-counters branch.

Codecov Report

Merging #11441 into topic-counters will increase coverage by <.01%.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##           topic-counters   #11441      +/-   ##
==================================================
+ Coverage           48.37%   48.37%   +<.01%
==================================================
  Files                 265      265
  Lines               42188    42192       +4
  Branches            10137    10137
==================================================
+ Hits                20408    20412       +4
  Misses              17703    17703
  Partials             4077     4077

Impacted Files
Coverage Δ

kernel/mem_slab.c
100% <0%> (ø)
:arrow_up:

kernel/thread.c
94.9% <0%> (+0.09%)
:arrow_up:

Continue to review full report at Codecov.

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

Can you also add counter to the list of supported features in the board yaml and doc, and update tests/drivers/counter/counter_basic_api to run on this board?

@MaureenHelm @nordic-krch I've added two commits for the tests, one fixes the compilation errors existing on the topic-counter branch at the moment and the other adds support for the UDOO Neo board.
Note that the EPIT timer has just one compare register. As this is used to fire the wrap callback, there are zero channels available. I had to modify the test to look at the number of available channels first and skip some tests if needed.
How about the functionality when only one compare register is available? We have some options:

The EPIT implementation could stay as it is now - no channel alarms, wrap callback available.
Return error if counter_set_wrap() is called with non-null callback. Support one channel alarm.
After initialisation of the driver, counter_get_num_of_channels() would return 1. If counter_set_wrap()
is called with non-null callback, counter_get_num_of_channels() would return 0 and it will not be allowed to set a channel alarm. If counter_set_wrap() is called with null callback, counter_get_num_of_channels() would still return 1 and allow to set one channel alarm. But I think the counter_get_num_of_channels() is meant to be consistent and always number the same number of channels, although it is not stated in the API documentation explicitly.

@stanislav-poboril could you rebase?
regarding the approach when only one channel is available. There are 2 scenarios that can be covered with that:

periodic alarm
single-shot alarm.

For periodic alarm you need set_wrap to indicate that counter must be reset on wrap. For single shot you can use set_alarm or alternatively use set_wrap and disable counter in the callback to ensure single-shot functionality. Imo, to keep it simple i would stick with set_wrap only. The cost is that user must call counter_disable to avoid getting periodic callback.


type-o

fixing a typo

This has been fixed in latest code https://github.com/apache/mesos/blob/1.1.x/include/mesos/zookeeper/zookeeper.hpp#L44 We should close this pr.


Thanks for fixing this very important issue.


clean clients should not have persistent subscription records.

If the current client is a clean session, a subscription should not be stored in persistence as it is not a persistent session.

Can you add a unit test?

@sundryp thanks for a patch, that's why redis and other persistences are growing so big

This would need a unit test.

@mcollina, now I'm trying to test this, but I cannot find the issue, subscriptions for clean clients must be cleared somewhere else.


Improving performance of the SDK

Background:
We are bridge-ing many devices (80, 100, 150+) via our Matter bridge device based on bridge-app example and using commit e2b9cadff4f15ac8fb3fa7c2144a945f229a6549 (May 30th 2023). A controller (eg. Apple Home and Google Home) is making an incredible amount of attribute reads and it seems that the responses are not received fast enough for the controller to work correctly (the controller chokes and can’t be used).
Question:
Let’s say that there are no hardware limitations and that our application specific response is instant. Can the Matter SDK be somehow configured to use more resources to improve performance?
We have been playing around with different settings in src/lib/core/CHIPConfig.h, src/system/SystemConfig.h and src/include/platform/CHIPDeviceConfig.h but with no success. Any tips would be much appreciated.

Have you tried reducing the log level?
E.g. errors only: chip::Logging::SetLogFilter(chip::Logging::LogCategory::kLogCategory_Error);

@svigelj Apple Home will generally do one read at a time, so you should not have problems servicing that on your end....
If you have situations where Apple Home is mis-behaving filing a feedback ticket with logs might be useful.  Please let me know the ticket id so I can follow up on it.
Feedback assistant ticket:

File a feedback assistant ticket.
https://developer.apple.com/bug-reporting/#feedback-assistant
Click on the link below using your account:
https://feedbackassistant.apple.com/new-form-response
Choose iOS/iPadOS to file an issue
Choose the area as Home App and fill in the details of the type of issue and the description

Technical Information
Please provide the following
a) Sysdiagnose logs for iPhone / iPad with the timestamp / timeframe of the issue
b) Sysdiagnose logs for all the Home Hubs (HomePod mini / HomePod / Apple TV) with the timestamp / timeframe of the issue
c) Accessory logs with the timestamp / timeframe of the issue
d) mDNS network logs with timestamp / timeframe of the issue
e) Video or screenshot describing the issue (optional but beneficial)
Please make sure you download and install the profiles for iOS and tvOS as provided here. The instructions are also in these links.
iOS:

https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=ios&name=homekit
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=ios&name=network
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=ios&name=mdns

tvOS:

https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=tvos&name=homekit
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=tvos&name=network
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=tvos&name=mdns
For installation instructions, refer to https://developer.apple.com/bug-reporting/profiles-and-logs.
Note: Once you have the profile on the iPhone, it will ask you if you want to install it on other devices. Follow the prompts to install on the HomePod, Apple TV, etc., where you have the described issue and reproduce it.

@ste-ca yes, we have reduced the log level as well - which didn't help.
@bzbarsky-apple On our end we service all the requests without errors, the problem might be that Apple Home is expecting to go through all the reads in a shorter time than it does (it is making thousands of reads, especially for Reachable attribute). We will follow up with the feedback ticket as you have suggested shortly. Thanks!

@bzbarsky-apple the feedback ticket ID is FB12268741. We have included a detailed overview of the issue and how to reproduce it. Thank you for helping out on this issue :+1: .

@svigelj Thank you!  Sorry for the slow response, but at this point we will hopefully have someone looking into this and figure out what's going on here.

Closing this as this is being handled through feedback assistant.


Task 561 - 564: Wiki auto and winograd dataset

@SavanDoshi, Wondering if you can help review these tasks?

readme.md : should be in the format of  Name | Summary | Category.
you need to update the readme according to it. ex: task562_pronoun_finder | find the pronoun in the sentence | Pronoun Finder

Check grammar for definitions and explanations for every task.
There are many asci characters in the file. Use this command to generate json "json.dumps(your_json_string, indent=4, ensure_ascii=False))"
in the explanations whenever you are referring to a particular word from the input sentence. put that word in the quote. ex:  in the first negative example "There is no his in the sentence" -> "There is no "his" in the sentence".
change the explanations according to the above method.

task561:

Category should be "Summarization"  instead of "Title Generation".
Try to write definition clearly. ex: instead of using the word "passage" use "sentence" as there are no passage examples.

task562:

Category should be "Answer Generation".
write a clear and proper definition as if you are explaining to another person.

task563:

Category should be "Answer Generation".
explain the definition clearly like, what is quote in the sentence.

task564:

Category should be "Answer Generation".

So do I create another pull request ? @SavanDoshi

So do I create another pull request ? @SavanDoshi

No, update the files in this PR.

ohkay.. I will do that today.

@SavanDoshi, check and let me know if you are happy with the changes or have any other feedback?

@swarooprm looks good to me.

Your HW2 is complete now.
Would you like to submit the same tasks to our big project repo https://github.com/allenai/natural-instructions-expansion/pulls? You just need to fork that repo, rename tasks starting from the latest number in the repo and create PR there. This way, you can be part of our research on "learning from instructions instead of learning from examples (conventional machine learning)". This is purely optional and your HW2 grade does not depend on this @khushal1996

Hi @swarooprm Yeah sure. I have submitted the tasks to the repo you mentioned.


Incorporate WM and PVEc into model, as per C++ aslrest

I've copied the C++ pretty closely, the following things could do with looking at (most are marked with FIXMEs):

hardcoded constants, eg WM ATT = ATT + 0.3, fcalibwm, pcwm etc.
the mean on the fwm posterior is 0.5, because the ftiss mean is 1.5, so that seemed to make sense
posterior initialisation for tissue flow is different under PVEc than the original C++ code, because we don't do an initialisation CBF run first. Instead I've done a simple linear equation based on a 3:1 ratio (we could set that ratio as a model option perhaps?) I did try an approach similar to the original code but it didn't give very good performance.
redundancy of model options: pvcorr, incpve, incwm, inferwm
parameter names (eg why fwm instead of ftisswm)

Regarding the FIXME, I would set the default on --pc to None but describe the rules in the option help description. Then in init, apply the default rule when self.pc is None.
Agreed that --incpve is pointless - can just remove this. I'm not clear that --pvcorr is that useful either but happy to leave it as a compatibility shorthand for --incwm --inferwm.

Regarding the FIXME, I would set the default on --pc to None but describe the rules in the option help description. Then in init, apply the default rule when self.pc is None.
Agreed that --incpve is pointless - can just remove this. I'm not clear that --pvcorr is that useful either but happy to leave it as a compatibility shorthand for --incwm --inferwm.

Also looks like the _get_data internal method in the data model probably needs to be renamed if it's going to be used by models - will have a little think about this as the possibly cleaner alternative would be to allow a model option to have an image type which handles this stuff transparently.

Also looks like the _get_data internal method in the data model probably needs to be renamed if it's going to be used by models - will have a little think about this as the possibly cleaner alternative would be to allow a model option to have an image type which handles this stuff transparently.

--pc defaults: fixed as you suggest
--incpve removed
model._get_data(): will leave this to you to rename in a later commit?

--pc defaults: fixed as you suggest
--incpve removed
model._get_data(): will leave this to you to rename in a later commit?

Yes, let's leave the _get_data for now - not sure the best solution for this and what's there is harmless enough

Yes, let's leave the _get_data for now - not sure the best solution for this and what's there is harmless enough


Document building an ephemeral VM for local molecule testing

Update the testing roles documentation with complete steps to build a new CentOS9 stream VM which can run local molecule tests as resquired by the edpm_libvirt and edpm_nova roles.

rdo-check
im  going to quickly follow this in a clean vm but overall it looks fine to me

recheck


drive can't pull files, needs update

The version of the drive package in nixpkgs is affected by [an
issue] drive issue that prevents it from pulling (downloading)
files from Google Drive; this issue should be fixed if the package is
updated to version 0.3.8 or newer (the current version being <IP_ADDRESS>).
(I would update it myself, but I lack sufficient familiarity with Go
and go2nix.)

If the following works for you, can open it as a pull request:
https://gist.github.com/anonymous/c76c620c789b099f06b60108232b3676

@Mic92: That seems to work, thanks! Did you mean that you or I would
file the PR?

@8573 you can.

I've filed the PR.

Merged.


Unresponsive bubble-temperature-container (Daikin Skyport)

Describe the bug
When in auto HVAC Mode, the .bubble-temperature-container is present but uncontrollable.
To Reproduce
Steps to reproduce the behavior:

Add a Daikin Skyport (in my case, an Amana Smart Thermostat) integration & thermostat
Add a climate card for the above
Configuration:

type: custom:bubble-card
card_type: climate
entity: climate.amana
sub_button:
  - name: HVAC modes menu
    select_attribute: hvac_modes
    state_background: false
    show_arrow: false
icon: mdi:home-thermometer-outline
card_layout: large

Attempt to change temperature on first temperature control (.bubble-temperature-container)
See error

Expected behavior
.bubble-temperature-container should not show, or should adjust temperature somehow.
Screenshots
Included in To Reproduce
YAML
type: custom:bubble-card
card_type: climate
entity: climate.amana
sub_button:
  - name: HVAC modes menu
    select_attribute: hvac_modes
    state_background: false
    show_arrow: false
icon: mdi:home-thermometer-outline
card_layout: large

Informations (please complete the following information):

OS: Linux, macOS 15.1, Windows 11
Browser/App: brave, chrome
Bubble Card version: v2.3.0-beta.5
Home Assistant version: 2024.11.1

Additional context
Workaround for hiding temperature control in auto mode:
styles: |-
  .bubble-temperature-container {
    display: ${ hass.states['climate.amana'].state === 'auto' ? 'none' : 'inherit'  };
  }

nevermind, not needed on beta.6


understanding connection process

Hi, I'm working on SIM800L with arduino UNO and testing MQTT example. I just want to understand how connection to the server is managed. I've enabled debug mode and looking at serial monitor I saw
AT+CIPSTART=0,"TCP","test.mosquitto.org",1883
OK
0, CONNECT OK
AT+CIPSEND=0,27
>MQTTGsmClientTest
DATA ACCEPT:0,27
AT+CIPRXGET=4,0
+CIPRXGET: 4,0,0
OK
AT+CIPSTATUS=0

And after that a lot of
AT+CIPRXGET=4,0
+CIPRXGET: 4,0,0
OK
AT+CIPSTATUS=0

What is the purpose of that CIPRXGET and CIPSTATUS?
Finally after some of those messages I see:
AT+CIPSTATUS=0
+CIPSTATUS: 0,0,"TCP","<IP_ADDRESS>","1883","CONNECTED"
OK
+CIPRXGET: 1,0
AT+CIPRXGET=4,0
+CIPRXGET: 4,0,4
OK
AT+CIPRXGET=2,0,4
+CIPRXGET: 2,0,4,0

OK
success

So, that last CIPRXGET is the one that receive CONNACK packet. But what is the purpose of previous commands?

I can't help you with all of the CIP commands. They are coming from whatever network client you are using underneath PubSubClient.


[Bug]: Bundle name overlaps with bundle ID

What happened?

What operating system are you seeing the problem on?
Mac OS
What browsers are you seeing the problem on?
Firefox
What wallet extension are you using?
Metamask
Rules

[X] I agree to follow this project's rules

Paid

new layout


Features :  add Save Project in Project menu

Problem Description
Missing features in Project Menus:
Save Project does the following :
Saved the position in tab of opened files.
Saved the current working directory.
Saved the layout.
 It allows to open a project with correct setting/opened files and work straight.

Sometimes, we can have 2 projects into a same directory, how to manage it ?
(opened files are different).

Best is to save Project configuration into a single zip file on disk, make fully flexible.

What steps reproduce the problem?
What is the expected output? What do you see instead?
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version:
Python version:
Qt version:
PyQt version:
Operating System name/version:

Dependencies

PASTE DEPENDENCIES HERE

Good suggestions! Unfortunately we'll have to leave for a future major release (probably Spyder 5, maybe 6) because right now we're really swamped.
Thanks for understanding!


Add files via upload

Adds badge text-based feedback indicating invalid |accept-language| strings, a single |accept-language|  substring, multiple valid |accept-language| substrings, and all |accept-language| having |;q=0|.
Not sure if "q=0" is the best feedback. It could be "!language" or something along those lines.

Woohoo! This seems to work really well. The use of emoji to indicate errors is super clever.
I think we can determine the highest qvalue language more concisely via map/reduce. I believe this does the same thing, given a valid input string:
  let best = (input) => {
    return input.split(',')
                .map(token => token.trim().split(';q='))
                .map(([lang, qval]) => [lang, qval ? parseFloat(qval) : 1])
                .reduce(([bestLang, bestQval], [lang, qval]) => {
                  if (qval > bestQval) {
                    return [lang, qval];
                  } else if (qval === bestQval) {
                    return ['mul', bestQval]
                  } else {
                    return [bestLang, bestQval];
                  }
                }, ['', -1]);
  }

For example:
> best('en, de')
[ 'mul', 1 ]
> best('en, de;q=0.5')
[ 'en', 1 ]
> best('en;q=0.1, de;q=0.5')
[ 'de', 0.5 ]

Does that function look right to you?

@callahad I've never used the map method, reduce method, or destructured arrays, so I find this code is somewhat confusing. That said, on researching those things and in testing the shown code, your code does appear to generally return the correct best array on invocation.
The code is incomplete though since it doesn't evaluate the validity of the string. One can't accurately determine the bestQval value without first examining whether the input is valid. Perhaps the omission was intentional though. I guess it gives a useful value for the invalid case involving an empty string, at least; the bestQval of 1 can simply be discarded.
It also doesn't handle a bestQval value of 0. For example, (input = 'en;q=0') is explicitly disallowing English without otherwise expressing a preference for a language, so this case requires special handling since en is not the best language. In those cases, it seems that the label should be an empty string, !en or !mul, or some placeholder value like q=0 or 🛇.
This code, based on yours, seems to handle the missing cases:
let valid = /^[a-z]{1,8}(?:-[a-z]{1,8})?(?:;q=(?:0(?:\.\d{0,3})?|1(?:\.0{0,3})?))?(?:, *[a-z]{1,8}(?:-[a-z]{1,8})?(?:;q=(?:0(?:\.\d{0,3})?|1(?:\.0{0,3})?))?)*$/i;
let best = input => {
  return valid.test(input) ? (() => {
    let output = input.split(',')
      .map(token => token.trim().split(';q='))
      .map(([lang, qval]) => [lang, qval ? parseFloat(qval) : 1])
      .reduce(([bestLang, bestQval], [lang, qval]) => {
        return qval > bestQval ? [lang, qval] : qval === bestQval ? ['mul', bestQval] : [bestLang, bestQval];
      }, ['', -1])
    return output[1] ? output[0] : '🛇\ufe0f';
  })() : !input ? '' : '⚠\ufe0f';
};

(There's no emoji for 🛇 on Windows. This just future-proofs the character.)

It seems that my regex is actually inaccurate. Apparently RFC2616 is superseded by RFC7231, which allows both numbers (in addition to letters) after the language-range's hyphen-minus character and optional whitespace (spaces and tabs) around the ;q= semicolon.
Still can't figure out what the formal rules are for whitespace around commas.

So RFC3282 specifies a ridiculously permissive model that allows CFWS (comments and "folding whitespace") around the ;, q, and =; after token-separating commas; and around the entire accept-language header value. See https://tools.ietf.org/html/rfc3282#section-3 and https://tools.ietf.org/html/rfc2822#section-3.2.3.
I have no idea how to implement comment detection since I can't understand what the spec means when it defines quoted-pair.
The next best solution seems to be (A) to prohibit entry of anything other than [\t ,\-\.0-9;=A-Za-z] since there's no "folding" without being able to enter CRLF pairs and no comments without being able to enter parentheses or (B) to treat potentially valid values as errors. Continuing to allow (B) would continue to allow people to use this extension to test invalid accept-language headers at the expense of incorrectly flagging valid, "exotic" header values as errors in the UI.
Using \[\t ]\g.replace('') before processing should allow split(';q=') while also allowing one to drop calls to trim().
/^[\t ]*[a-z]{1,8}(?:-[0-9a-z]{1,8})?(?:[\t ]*;[\t ]*q[\t ]*=[\t ]*(?:0(?:\.\d{0,3})?|1(?:\.0{0,3})?))?(?:,[\t ]*[a-z]{1,8}(?:-[a-z0-9]{1,8})?(?:[\t ]*;[\t ]*[\t ]*q[\t ]*=[\t ]*(?:0(?:\.\d{0,3})?|1(?:\.0{0,3})?))?)*[\t ]*$/i handles the case of optional whitespace and adds support for numbers in the language strings.


Reverse engineering the REST API auth token format

It has come to my attention that the REST API authentication token is actually base64 encoded data.
When a token expires, Pandora sends the following message back, implying that the token stores some sort of state.
ListenerState in auth token does not match state in radio db
It's possible that this token may include useful information like when the token will expire. I intend to look into this further, and I'll document any findings here before collating anything meaningful into a page in a PR.
An example (expired) authentication token:
BIQ3pFmHssCsDO8nEYuyojSfYKUus0LpEOsueZ3Zk0vQtUNfywnxI4cA==

04 84 37 a4 59 87 b2 c0 ac 0c ef 27 11 8b b2 a2
34 9f 60 a5 2e b3 42 e9 10 eb 2e 79 9d d9 93 4b
d0 b5 43 5f cb 09 f1 23 87 00

Could it simply be base-64 encoded binary data that they associate with account data in their database?  I would think the token expiration is not included within the token itself, but rather they likely use the token as a UUID to lookup a record on their end.

Could it simply be base-64 encoded binary data that they associate with account data in their database?

Possibly, but the expired error message references a ListenerState in the authentication token.
Here are six more tokens, retrieved in quick succession:
VIG280FHDA0eGu2afiWsF1K1b/N36CkLH6lf9WCTNo/9zdDHokkLK7mQ==
VIojC6zfuZse46P1c765ADK3K0HGRSkGTliS1BR7haa7q2zyifhCC9mQ==
VIirUwvxHipElkKksjrxnwVKBXgmvu2hA2wWegdHLsDzw8AI3vvWw7pA==
VITXTCn1yy656XXzprlDSUMK67sJkvVQxv9DMED8if33TT+7b0dAtR/A==
VIX7sGpTWj+WTKMmq38tG5FdAxqoGRd+FiN7gC2GiML8zJnNGHxDPRuA==
VIirUwvxHipElkKksjrxnwVMbTTMLo7krVxz7Ljdj1Ak41MyEkZbOAsg==
54 81 b6 f3 41 47 0c 0d 1e 1a ed 9a 7e 25 ac 17 52 b5 6f f3 77 e8 29 0b 1f a9 5f f5 60 93 36 8f fd cd d0 c7 a2 49 0b 2b b9 90

54 8a 23 0b ac df b9 9b 1e e3 a3 f5 73 be b9 00 32 b7 2b 41 c6 45 29 06 4e 58 92 d4 14 7b 85 a6 bb ab 6c f2 89 f8 42 0b d9 90

54 88 ab 53 0b f1 1e 2a 44 96 42 a4 b2 3a f1 9f 05 4a 05 78 26 be ed a1 03 6c 16 7a 07 47 2e c0 f3 c3 c0 08 de fb d6 c3 ba 40

54 84 d7 4c 29 f5 cb 2e b9 e9 75 f3 a6 b9 43 49 43 0a eb bb 09 92 f5 50 c6 ff 43 30 40 fc 89 fd f7 4d 3f bb 6f 47 40 b5 1f c0

54 85 fb b0 6a 53 5a 3f 96 4c a3 26 ab 7f 2d 1b 91 5d 03 1a a8 19 17 7e 16 23 7b 80 2d 86 88 c2 fc cc 99 cd 18 7c 43 3d 1b 80

54 88 ab 53 0b f1 1e 2a 44 96 42 a4 b2 3a f1 9f 05 4c 6d 34 cc 2e 8e e4 ad 5c 73 ec b8 dd 8f 50 24 e3 53 32 12 46 5b 38 0b 20

Interesting. Have you considered fuzzing individual bytes until the ListenerState error displays? Also, I would imagine either some sort of session identifier or account identifier is included in the token, unless they are in fact using the token as a UUID that they look up on the backend. Perhaps hybrid, as I'm sure you were using the same user account in your collection of these auth tokens.

Interesting. Have you considered fuzzing individual bytes until the ListenerState error displays?

I haven't tried all that thoroughly, but I did try changing random bytes in different areas. Only the very last nibble seems to be able to be changed without invalidating the token.


[BUG] Unable to build anymore on any machine

Describe the bug
The build no longer works on any machine, including Windows, Linux and Docker
To Reproduce
git clone the repo, follow the build instructions with yarn install and yarn build. Error as follows:

flowise-ui:build: $ craco build
flowise-ui:build: Creating an optimized production build...
flowise-ui:build: Failed to compile.
flowise-ui:build:
flowise-ui:build: Module parse failed: Unexpected token (143:13)
flowise-ui:build: File was processed with these loaders:
flowise-ui:build:  * ../../node_modules/babel-loader/lib/index.js
flowise-ui:build:  * ../../node_modules/source-map-loader/dist/cjs.js
flowise-ui:build: You may need an additional loader to handle the result of these loaders.
flowise-ui:build: |     // return some(), else if(), (x*sum(1, 2))
flowise-ui:build: |     variants: [{
flowise-ui:build: >       begin: /=/,
flowise-ui:build: |       end: /;/
flowise-ui:build: |     }, {
flowise-ui:build:
flowise-ui:build:
flowise-ui:build: error Command failed with exit code 1.
flowise-ui:build: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
flowise-ui:build: ERROR: command finished with error: command (E:\git\UpdatedFlowise\packages\ui) yarn run build exited (1)

Expected behavior
Builds.

getting similar issue with my builds :(

Mine is on render and am having the same issue, I tried restoring from a snapshot, but it is just looping starting and failing.
==> Running 'yarn start'
Oct 27 08:02:33 AM  yarn run v1.22.5
Oct 27 08:02:34 AM  $ run-script-os
Oct 27 08:02:34 AM  $ cd packages/server/bin && ./run start
Oct 27 08:02:37 AM  (node:104) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
Oct 27 08:02:37 AM  (Use node --trace-deprecation ... to show where the warning was created)
Oct 27 08:02:37 AM  (node:104) [ERR_DLOPEN_FAILED] Error Plugin: flowise: The module '/opt/render/project/src/node_modules/canvas/build/Release/canvas.node'
Oct 27 08:02:37 AM  was compiled against a different Node.js version using
Oct 27 08:02:37 AM  NODE_MODULE_VERSION 115. This version of Node.js requires
Oct 27 08:02:37 AM  NODE_MODULE_VERSION 120. Please try re-compiling or re-installing
Oct 27 08:02:37 AM  the module (for instance, using npm rebuild or npm install).
Oct 27 08:02:37 AM  module<EMAIL_ADDRESS>Oct 27 08:02:37 AM  task: toCached
Oct 27 08:02:37 AM  plugin: flowise
Oct 27 08:02:37 AM  root: /opt/render/project/src/packages/server
Oct 27 08:02:37 AM  See more details with DEBUG=*
Oct 27 08:02:37 AM   ›   Error: command start not found
Oct 27 08:02:37 AM  error Command failed with exit code 2.
Oct 27 08:02:37 AM  info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Oct 27 08:02:37 AM  error Command failed with exit code 2.
Oct 27 08:02:37 AM  info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Okay this appears fixed this morning with a fresh install. Only 1135 remains.


Fix installing Wine Development and staging builds on Debian Buster

libfaudio0 dependency is the missing for Wine staging and Wine development.
This dependency is not directly available in the official WineHQ Ubuntu and Debian 10 repository because it's not part of the Wine project. It is mentioned (along with a link to a forum post) at the top of the WineHQ Ubuntu and Debian installation pages that users need to download and install this package separately, but many users ignore it / don't read that part. On the other hand, those upgrading from older Wine builds / those that already have the WineHQ repository added never get to the official WineHQ installation page, so they won't notice this very important detail.
It's worth noting that the missing libfaudio0 dependency has been added to the Debian bullseye / sid and the upcoming Ubuntu 19.10 release, so this is only an issue for older releases.

We're moving back to debian stretch because of #506.
Superseded by #512


docs: Replace outdated web framework recommendation

The trunkrs.dev site currently recommends Seed as one of the “most popular [Rust web frameworks] today”, but Seed appears to no longer be actively developed or maintained.
This change keeps Yew as a suggested framework, adds ~Dioxus~ Leptos, and also links to an actively-maintained list of Rust libraries for building web pages.

@ctron PTAL – I have swapped Dioxus for Leptos, and Yew is now listed first.

I agree that it might make sense to update this

The Trunk project homepage currently recommends a library whose own readme has described it as “not maintained at the moment” for the past year, and whose website hasn’t been updated with a new release since 2020.
Please permit me to be so bold as to suggest … it does make sense to update this, and I would urge the Trunk maintainers to do so. I believe it would benefit our community, and people new to web development in Rust in particular. Thank you. 🙏🏻

Please permit me to be so bold as to suggest … it does make sense to update this, and I would urge the Trunk maintainers to do so. I believe it would benefit our community, and people new to web development in Rust in particular. Thank you. 🙏🏻

I think I said that indeed makes sense. It least that was my intention. My only remark was the choice of tools to highlight. I think that's fixed, so I don't see any reason not to merge this.

@ctron I'm familiar with Dioxus but not "Doxius". Is this just a typo? (If not, I wonder if they changed names at some point.)

Typo


refactor: pool's Deposit, Withdraw and Swap forms

Closing this PR, too many changes and comments.


How to use model to generate trajectories

I've trained a model with the given dataset, and saved the model to /Result folder, which is a .pt file. Then I want to use the model
to generate new trajectories. Which function should I use?

If you are referring to TrajGAIL, there's a function called unroll_trajectory in the main file


How to change currency in this program.

It's not possible, yet, but I'll add this as a feature request. The bot doesn't do any currency calculations, though, so it's only for displaying data and won't make a difference in numbers.


Show warning in case of sample ID duplicates in sample type Excel file

When the user uploads a sample type list Excel file, each sample ID should be present only once.
Implement a check for this, and show a warning in case of duplicate sample IDs.
Now when a sample ID is present multiple times, that sample is also shown multiple times in the normalized data when it should not be.

The same check should be implemented for the metadata.

Also good to check that there are no missing sample IDs in the sample type list (something like this is already implemented for the metadata file).


Fix "go get" command for installation

With updates to the go CLI, the required target has changed. This commit modifies the command to be the one that works now.
Fixes: https://github.com/spf13/cobra/issues/2057

Hello, is there anything we can do to help this get merged?

@spf13 It's worth to merge it cause I ran into this problem and spent some time to figure out that the link is not correct


[RabbitMQ] Monitor troubleshooting

📑 I have found these related issues/pull requests
No
🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
When i add RabbitMQ node (With rabbitmq_management enabled) into Kuma, kuma return 406 in results
Node appear Offline.

👟 Reproduction steps
Add RabbitMQ node HTTP (If rabbitmq-plugins enable rabbitmq_management work)
Wait for results
👀 Expected behavior
Node appear Online and working
😓 Actual Behavior
Node appear Offline
🐻 Uptime-Kuma Version
2.0.0-beta.0
💻 Operating System and Arch
Ubuntu 22.04 LTS
🌐 Browser
Opera
🖥 Deployment Environment

Runtime: Docker 27.2.1, build 9e34c9b
Database: sqlite/embedded
Filesystem used to store the database on:
number of monitors: 62

📝 Relevant log output
uptime-kuma-1  | 2024-11-07T08:21:31+01:00 [MONITOR] WARN: Monitor #71 'RabbitMQ ACC': Failing: Request failed with status code 406 | Interval: 60 seconds | Type: rabbitmq | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:21:36+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:22:06+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:22:31+01:00 [MONITOR] WARN: Monitor #71 'RabbitMQ ACC': Failing: Request failed with status code 406 | Interval: 60 seconds | Type: rabbitmq | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:22:36+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:23:06+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:25:31+01:00 [MONITOR] WARN: Monitor #71 'RabbitMQ ACC': Failing: Request failed with status code 406 | Interval: 60 seconds | Type: rabbitmq | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:25:36+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:26:06+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:26:31+01:00 [MONITOR] WARN: Monitor #71 'RabbitMQ ACC': Failing: Request failed with status code 406 | Interval: 60 seconds | Type: rabbitmq | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:26:36+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:27:06+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:29:31+01:00 [MONITOR] WARN: Monitor #71 'RabbitMQ ACC': Failing: Request failed with status code 406 | Interval: 60 seconds | Type: rabbitmq | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:29:36+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:30:06+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:30:31+01:00 [MONITOR] WARN: Monitor #71 'RabbitMQ ACC': Failing: Request failed with status code 406 | Interval: 60 seconds | Type: rabbitmq | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:30:36+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0
uptime-kuma-1  | 2024-11-07T08:31:06+01:00 [MONITOR] WARN: Monitor #1 'FD-WebTools': Failing: Child inaccessible | Interval: 30 seconds | Type: group | Down Count: 0 | Resend Interval: 0

cc: @Suven-p

@FlashModz Which version of rabbitmq are you using?

@FlashModz Which version of rabbitmq are you using?

Hi,
It's the 3.8.14, Erlang 23.2.3.

@FlashModz Could you also include the response from rabbitmq health check endpoint?
Preferably from inside kuma container
curl -v "http://$rmqHost:$rmqPort/api/health/checks/alarms"  -H "Authorization:Basic $(echo -n $rmqUser:$rmqPass | base64)"


cannot work with core.cache

puget.print/pprint failes when tried to print core.cache object.
It because you cannot sort Cache type.
You can reproduce with below.
(require '[leiningen.exec :refer [deps])
(deps '[[org.clojure/core.cache "0.6.4"]
        [mvxcvi/puget "0.8.1"]])
(require '[clojure.core.cache :as cache])
(require '[puget.printer :as puget])
(def c (cache/ttl-cache-factory {:a 1}))
(prn c)
(puget/cprint c)

Hmm, I'll take a look. As a workaround, you could use the :escape-types option to avoid pretty-printing these.

With 0.9.0 you can specify a custom print handler for core.cache objects to get around this behavior.


added recommendation page

It shows unsolved public path's activities.
route -/homev3

Coincidentally I have made some GUI style changes (minor ones) as well! Later I will try combine our changes to your homev3 and make another PR.


2.b.i Requirements Changes

Altered the Requirements to include new requirements for assessment 2 and removed unnecessary ones from the table.

Changes on Requirements Table: [Used the walkthrough inspection methhod]

Added the new requirements for assessment 2 and split them according to the tables created by team 3 following the same ID format team 3 had set and set them to the correct user requirements
Changed the priority on any pre-existent requirements that didn’t have to be implemented until assessment 2
[Still needs justification]

Taking over to review and write a brief explanation justifying the changes made.

11/03/22 - 10:55
All the various changes (and lack of) have been documented and are beginning to be written up in full.

Taking over to review and feedback.
(16/04/22)

Review complete.

More requirements could be added as we go along, therefore the issue will remain open.
FR_GAME_DIFFICULTY and FR_SAVE_POINT still need justifying in the "write up" document

As a side note might be useful to split the Power-Ups requirement (UR_POWER_UPS) into the individual 5 components requested by the new brief.
(16/04/22)

22/04/22 - 10:30
Full write up completed, with the rest of the functional requirements being added and the lack of changes to NFRs being added too.

22/04/22 - 10:40
File reviewed and moved to the "Reviewer approved" column.


Sign in to LUIS portal doesn't get me the Welcome page

Following the steps of "Sign in to LUIS portal and begin authoring", it doesn't present the welcome page for me to choose the type of LUIS authoring key as shown in the screenshot. Any place/step I need to check to get it work?

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

ID: 407d2781-1fe1-38a6-dc18-37d4e37d651c
Version Independent ID: 919a2206-13f9-4f51-2e4f-45fe062d7d43
Content: How to use authoring and runtime keys - LUIS - Azure Cognitive Services
Content Source: articles/cognitive-services/LUIS/luis-how-to-azure-subscription.md
Service: cognitive-services
Sub-service: language-understanding
GitHub Login: @diberry
Microsoft Alias: diberry

@joyceywho The documentation and release of the LUIS portal are out of sink due. The portal will work as documented in the next day or two. Until then, you won't need to create a LUIS authoring resource.

@joyceywho I have tried the steps in the tutorial now and the welcome screen is shown as mentioned in the documentation.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag @RohitMungi-MSFT in your reply. We will gladly continue the discussion and we will reopen the issue.


relax length constraints

Current coverage is 88.69% (diff: 100%)

Merging #4698 into master will increase coverage by <.01%

@@             master      #4698   diff @@
==========================================
  Files           121        121
  Lines         73841      73850     +9
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          65491      65500     +9
  Misses         8350       8350
  Partials          0          0

Powered by Codecov. Last update 04b45d1...a92618b

LGTM

Auto-merge toggled on

Thanks!


Exception in the constructor runing on the device, but it works correctly in the emulator.

Exception in the constructor runing  on the device, but it works correctly in the emulator.
// Ex: Exception has been thrown by the target of an invocation
ZXingBarcodeImageView barcode = new ZXingBarcodeImageView
                {
                    HorizontalOptions = LayoutOptions.FillAndExpand,
                    VerticalOptions = LayoutOptions.FillAndExpand,
                };
// Ex: Exception of type 'System.Collection.Generic.KeyNotFoundException' was thrown.
ZXingScannerPage scanPage = new ZXingScannerPage();

But... on emulator works...

Thanks for reporting this issue!  Unforunately it took me way too long to respond 😭.  Sorry, I apologize!  Recently the source code for this project was completely refactored to modernize it.  Many PR's were included in this effort, and many bugs were hopefully fixed.  Please try out the latest 3.x series of NuGet packages (currently in prerelease).  To try and make the project more maintainable in my spare time going forward, I've decided to close all existing issues to start with a clean slate.  If you're still experiencing this issue on the newest version, please open a new issue with as much detail as possible.  Thank you for your patience and understanding!  Happy scanning!