SSL_get_ciphers() after SSL_CTX_set_cipher_list() returns ciphers that shouldn't be enabled.

The Cisco AnyConnect protocol relies on "resuming" sessions which didn't previously exist, so we have to generate the SSL_SESSION manually. The master secret and session ID — and the ciphersuite — are exchanged in advance in a separate TCP channel along with authentication and IP configuration etc.
In order to find the right SSL_CIPHER I have always just used SSL_CTX_set_cipher_list() with the specific single ciphersuite that is to be used, then SSL_get_ciphers() returns a list containing precisely that one:
http://git.infradead.org/users/dwmw2/openconnect.git/blob/v8.00:/openssl-dtls.c#l425
Recent test builds with OpenSSL HEAD have stopped this working. I end up with unrelated ciphersuites in the list, which don't match the one I asked for.
I see this with DTLS, so I'm not sure the TLSv1.3 ciphersuite changes as discussed in https://github.com/openssl/openssl/issues/7196 should make any difference?
For example when setting just AES128-GCM-SHA256 with SSL_CTX_set_cipher_suites() (and I tried doing it with SSL_set_cipher_suites() too for good measure), I get the following four results from SSL_get_ciphers():
Cipher #0: TLS_AES_256_GCM_SHA384  TLSv1.3 Kx=any      Au=any  Enc=AESGCM(256) Mac=AEAD
Cipher #1: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3 Kx=any      Au=any  Enc=CHACHA20/POLY1305(256) Mac=AEAD
Cipher #2: TLS_AES_128_GCM_SHA256  TLSv1.3 Kx=any      Au=any  Enc=AESGCM(128) Mac=AEAD
Cipher #3: AES128-GCM-SHA256       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(128) Mac=AEAD

I am, of course, perfectly happy to be told that I'm Doing It Wrong™, as long as your instructions for doing it right do not include going back a decade or more in a time machine and telling Cisco to use PSK for this instead of abusing session resume.
For versions of OpenSSL prior to 1.1, I actually did need the SSL_CIPHER as we created the SSL_SESSION directly. For modern versions I only need the value of SSL_CIPHER_get_id() corresponding to the cipher, because I create the ASN.1 and then use d2i_SSL_SESSION().
I'd really like to avoid having to make my own lookup table though. Is there a simple method I can use to go from, e.g, "AES128-GCM-SHA256" → 0x009c other than trying to set the ciphersuite and then trusting that SSL_get_ciphers() will return only the one I wanted?

Marking as inactive, to be closed at the end of 3.4 dev barring further input


AttributeError: 'Source' object has no attribute 'compilation_database'

[deoplete] Traceback (most recent call last):
[deoplete]   File "/home/milan/.vim/bundle/deoplete.nvim/rplugin/python3/deoplete/deoplete.py", line 57, in completion_begin
[deoplete]     complete_position, candidates = self.gather_candidates(context)
[deoplete]   File "/home/milan/.vim/bundle/deoplete.nvim/rplugin/python3/deoplete/deoplete.py", line 93, in gather_candidates
[deoplete]     results = self.gather_results(context)
[deoplete]   File "/home/milan/.vim/bundle/deoplete.nvim/rplugin/python3/deoplete/deoplete.py", line 168, in gather_results
[deoplete]     context['candidates'] = source.gather_candidates(context)
[deoplete]   File "/home/milan/.vim/bundle/deoplete-clang/rplugin/python3/deoplete/sources/deoplete_clang.py", line 38, in gather_candidates
[deoplete]     if self.compilation_database:
[deoplete] AttributeError: 'Source' object has no attribute 'compilation_database'
[deoplete] An error has occurred. Please execute :messages command.

Please upload minimal init.vim less than 50 lines and reproduce ways from neovim starting.

@tex @Shougo Maybe this problem caused by this https://github.com/zchee/deoplete-clang/issues/11.


Application crashes after authentication using latest master

Running commit a9242c21b3c9e2a28753e1dc9ef835d4c5720e70, the application crashes upon logging in:

I would suggest having either feature branches or functional tags allowing people to know what to checkout locally when testing.

@hickscorp at this point I'm just committing directly to master because I'm just trying to get it working. But yes. When it reaches a point at which people can successfully use the app, then yeah semantic versioning and feature branches will become a thing!
If you'd like to help out on some development, my discord is warpig#9483. Let's chat.

Deployed a fix for this.


[Bug] issue with updates

Overview

Insomnia Version:  5.1.1 (<IP_ADDRESS>1)
Operating System:  OS X 10.11.6
Summary:  App always show notification about update on startup

How To Reproduce

Launch Insomnia
After some time app will show notification: 'Insomnia Update Ready. Relaunch the app for it to take effect'
Relaunch Insomnia
I'm again see the message from step 2 on each launch

Hi @vavgustov,
I'm not sure how much help I can provide, as Insomnia uses Squirrel (build into Electron) to manage auto-updates. It's possible that something like something like strict file permissions or a non-standard installation could cause it to fail. Was 5.1.1 the first version of the app that you installed? Did you install it via the DMG download on the website?
Since you are seeing the update notification, it means that Squirrel has at least downloaded the latest update (currently 5.2.0) and thinks that it has installed it correctly. I'm not sure, but it looks like Squirrel downloads updates to /Applications/Insomnia.app/Contents/Frameworks/Squirrel.framework/Versions.

Let me know if any of that helps.

I installed DMG from website.
5.1.1 wasn't first version. First version was 5.0.20 or 5.1.0 and updates are worked ok.
My terminal output similar to yours except my dates are May 29 and May 30 (seems these dates related to v5.1.1 release date).
I'm think if it's related to Squirrel I'll keep this app version for some time and may be it will start work with next updates. Otherwise I'll reinstall DMG.
Thanks!


SRSDeploymentKit-<IP_ADDRESS> should be updated

SRSDeploymentKit-<IP_ADDRESS>.msi should be updated, it only supports Windows Version 10.0.18362.418 which is Windows 10 1903 with end of life december 8th 2020. Furthermore it's not available to download in the Volume Licensing Service Center.
This is relevant for:
https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/blob/live/Teams/rooms/console.md
and
https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/blob/live/Teams/rooms/rooms-scale.md
Both use the Same SRSDeploymentKit.

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


GUVNOR-2562: Guided Decision Table Editor: Clicking on GridLayer when editing cell does not update View

See https://issues.jboss.org/browse/GUVNOR-2562

+1


Toyota Tss2 Blindspot signals

Adding these signals are easy, they are on the can bus.

LGTM, @pd0wm can we write instructions for regenerating the process replay?

check out branch
run selfdrive/test/process_replay/update_refs.py
push updated ref_commit

I can add this to the process replay readme if you want

Unfortunately it's a little annoying on github to checkout someones branch in such a way that you can push to it.
@arne182 Can you change selfdrive/test/process_replay/ref_commit to
63ee3eaab23b45821a3a04888ae7506ec27dedb3 then the tests should pass

@quillford the problem then is to have an environment where it can run. I usually use termux on android to say update the generator of the opendbc things but for this command to work you need to have a whole bunch of things installed first. The last time I tried it on the eon it was also missing at least one dependancy.


Question?

Support for Fabric or Forge servers?

I will look into fabric server support ...

the dynmap plugin interface for non paper plattforms is very different so I can not port it easily.

Damn, Thanks for looking into it so quickly lmao


Add Python 3.11 to the testing

thanks, but there's already a 311 test

There is?!?  https://github.com/MarcoGorelli/cython-lint/actions/runs/3393345107

yup https://github.com/MarcoGorelli/cython-lint/actions/runs/3393345105/jobs/5640572484

I see...  Thx.


Vagrant's nginx.conf would benefit from sendfile off

If you're developing locally in Vagrant using Nginx, you'll want to set sendfile off; in nginx.conf. If @xyu can give me a suggestion on how to script that into the Vagrant provisioning I'll be glad to do a pull request.
Without sendfile off; Nginx doesn't seem to consistently read the source file in the root directory making development problematic when frequent changes are made.

Thanks for the PR closing this issue.


Automated cherry pick of #11825

Cherry pick of #11825 on release-7.7.
/cc  @harshilsharma63
NONE

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.

Trying to auto merge this PR.

Pull Request successfully merged
SHA: 11c7870908e27bfc2c1057d7f74fb85bbe3dd6e5


bump version in package.json to v2.16.7

release version v2.16.7

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


feat(claudeup): upgrade claude to use 2.1

Fixes #139

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

Hi @oconpa, thanks ! I just edited your comment to add a link to the related ticket in the backlog.
One thing missing is the update of the context window size in the lambda function (https://github.com/awslabs/generative-ai-cdk-constructs/blob/main/lambda/aws-qa-appsync-opensearch/question_answering/src/llms/text_generation_llm_selector.py#L92C5-L92C5) to 200k

Hi @oconpa , I see you fixed the token limit issue, thanks ! Were you able to test it by any chance ? So we can close this PR

Hi @oconpa , I see you fixed the token limit issue, thanks ! Were you able to test it by any chance ? So we can close this PR

Can we merge this PR first (https://github.com/awslabs/generative-ai-cdk-constructs/pull/198#issuecomment-1906735746), then this one?

Hi @oconpa , I see you fixed the token limit issue, thanks ! Were you able to test it by any chance ? So we can close this PR

Can we merge this PR first (#205), then this one?

Done, thanks for your contribution ! :)

Tested


Corrected translation for Portuguese Brazil

I saw a lot of words in Portuguese from Portugal inside the Portuguese Brazil translation and corrected that. I attached the zip file with the new pt-BR.js. This could help other Brazilian users from your software.
pt-BR.js.zip

I have updated your corrections, thank for your contribution.


Feedback on improving order of sections in Documentation on using DevHome for DevBox management

Moved from issue : https://github.com/microsoft/devhome/issues/3928
Documentation Link:
https://learn.microsoft.com/en-us/azure/dev-box/how-to-use-dev-home-customize-dev-box#:~:text=or Update.-,Sign in to Dev Home,-Dev Home allows
Actual Behavior:
Now the order of the article content is:

Install or update Dev Home
Sign in to Dev Home
Add extensions

If users try to sign in to Dev Home after downloading the application without any other operations, they cannot find the button to add their Microsoft (Azure) accounts in "Settings" - "Accounts" - "Add account" page. Only after adding (enabling) the Dev Home Azure extension can they find the add Azure account button.

Expected Behavior:
The correct order of the article content should be:

Install or update Dev Home
Add extensions
Sign in to Dev Home

I also filed feedback from the doc, so please go ahead and duplicate this out if that is being tracked separately.

@ezekielalexthomas
It looks like your issue is resolved since you closed this thread.
If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


Add note about automatic input expansion

As discussed in https://github.com/tensorflow/tensorflow/issues/42046 this documents the fact that TensorFlow automatically expands inputs to at least 2D when calling functions on Keras models (this actually happens in model.train_step, model.test_step, and model.predict_step, but I suspect those are used less frequently than model.fit(), etc).
This should hopefully reduce confusion between
outputs = model(inputs)  # allows 1D inputs
and
outputs = model.predict(inputs)  # will automatically expand 1D inputs to 2D

Thanks for the PR! We're actually in the process of removing this behavior right now. It will be gone in TF 2.7.


Model accuracy drops after a few epoch when training with custom dataset !

Hi @plemeri
Thank you for your work.
I tried training the swin b model from scratch with my custom dataset which is having 420000 images of humans , products , cars . etc (210000 * 2 Horizontal Flip ) , after a few epoch of training it starts giving weird output and the accuracy drops and the output from the model becomes very poor.
I had changed the batch size to 8 in order to train the model little quicker but the results started to get very horrible after a few epochs. Can you please tell me why this is occurring ?
Please see the attached input and output images for a better understanding of the problem.
image-compare.pdf
Thanks :)

Hello @ds-jpg
First of all, by just seeing the results cannot tell the problem exactly.
But I think the issue came from the training and inference image size difference.
I recommend using another configuration which we used for real-world scenario with composite datasets.
Plus_Ultra.yaml
Thank you.


lower/remove "object has been modified" type log messages from the OLM operators

Bug Report

What did you do?
A clear and concise description of the steps you took (or insert a code snippet).
Currently OLM emits a lot of unnecessary cache miss logs at the error level in the style of
error="Operation cannot be fulfilled on catalogsources.operators.coreos.com \"operatorhubio-catalog\": the object has been modified; please apply your changes to the latest version and try again" id=OTXzH source=operatorhubio-catalog

which confuses admins and others looking at the OLM logs. It also greatly increases the volume of OLM logs which then affects  clients of OLM logs such as log aggregation/exporter tools. It's worth investigating whether there is a way to remove or tone down these logs in a way that does not change the sync behavior of OLM.
Environment

operator-lifecycle-manager version:

Kubernetes version information:

Kubernetes cluster kind:

Possible Solution

Additional context
Add any other context about the problem here.

One possible solution lowering logs from the informer could be passing a different instance of the logger than the one that OLM generates on startup and fine-tuning it

Initial solution is to lower the log-level of this particular error in the queueinformer underlying this particular operator's queue.
May be a symptom of underlying controller problems.
Possible solution is generate a metric based on when this modified error occurs and then diagnose based on the number of occurrences.

@exdx Should this be closed now that https://github.com/operator-framework/operator-lifecycle-manager/pull/2631 has been merged for a while now?

This code may allow us to identify whenever an update fails due to a conflict.


unnecessary async key word

https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/3844c9eedb7f07e6fc927d1039af9a8f54366cad/samples/react-sample-app/src/AuthProvider.js#L29
await isn't being used in this code block, I don't think async is necessary here.

While it is true that async is required to use await, it also inherently makes the function return a promise. In this case, the function already explicitly returns a promise, so you're right, its technically not needed, but I just added it for consistency with the other functions in the file that return a promise.
Appreciate the feedback, we're always looking to improve our samples and make them clearer, so I'll keep this in mind as we make further improvements.


Make facebook::react::Instance methods overridable

Summary:
Public methods of class facebook::react::Instance that interface with NativeNoJsBridge become virtual, making the class mockable
Currently, custom types (i.e. deriving facebook::xplat::module::CxxModule or facebook::react::JSExcecutor) that need to interact with the facebook::react::Instance can't be fully unit tested without bootstrapping a full ReactNative app.
This change aims to make some of the class's public methods virtual so mock implementations of facebook::react::Instance can be written and any interaction with this class can be simulated in isolation, which will allow for complete and lightweight unit tests, increasing code coverage.
Changelog:
[General] [Changed] - Allow facebook::react::Instance to be extended for broader JSExecutor and Module unit testing / mocking.
Test Plan:

Build
Run unit and integration tests.

I am sorry, but, IMHO, a particular approach to testability is not a good reason to make methods virtual.

I am sorry, but, IMHO, a particular approach to testability is not a good reason to make methods virtual.

@shergin What is the drawback of making these methods virtual?
Testability helps writing better modules, and, to my knowledge, there is no noticeable risk or performance implication.
Can you share your concerns?

The performance implications are real (virtual methods are being called using dynamic dispatch (vtable) whereas normal ones are just direct calls; calling virtual functions cannot be inlined) but, besides that, the question is more about using idiomatic C++.
In C++, if a method is marked virtual, it gives a strong signal to a reader that the method is being called on a pointer to a base class, that the method is being called from a parent class in order to delegate the execution to a super class, and/or that the method is part of some interface (abstract class). All that begs questions like "why is this done this way?", "what was the intent?", "what am I missing reading this?". In short, making a method virtual is a very important design decision.
And usually the testability is not a good answer to that because we usually want to test everything, and that implies that we should add virtual to everything?.. If we do so, that will not be real C++ anymore.
I think we should consider another approach to mocking (e.g. replacing real classes with mocks using build tools).

And usually the testability is not a good answer to that because we usually want to test everything, and that implies that we should add virtual to everything?.. If we do so, that will not be real C++ anymore.

For this purposes, struct interfaces are used.
I'd argue it would be better to have a supertype of Instance,s say, IInstance.
I do wonder if the vtable performance impact is relevant for this case, but haven't tried any measurements.

Using virtual methods to mock for unit-testability is fairly common, but I understand the concern about performance impacts as well.
Using virtual methods does not automatically mean an indirect call via viable ends up in the generated code. Both LLVM and GCC can both devirtualize these calls when they have visibility of the concrete type being passed into other parts of the program via function/method/ctor arguments.
Can you show a man objdump of the dispatches to these now-virtual  methods to see if if the compiler has correctly applied this optimization? If it has, then that should allay Valentin’s concerns. FWIW, when I was tuning folly and C++ RN on my last project, I found that LLVM correctly devirtualized but I was using Link Time Optimization and Whole Program Optimization, so YMMV when using the BUCK build and whatever compiler version is included in the NDKs.

I am way more concerned about the readability and simplicity of the code than actual runtime performance in this particular case (which will probably be good even if the calls are not devirtualized because it's not a hot path).
The framework has many places where virtualization is not allowed because of actual performance overhead though. To test those places we need to figure out something different anyway. That's why I lean towards compile-time approaches.
If we believe that using virtual dispatch is the right approach here, we should start from designing meaningful interfaces to which Instance would conform (improving code to make it testable). I mean, now it's 11 methods, even if we will introduce Interface interface, ConcreteInterface implementation and MockInterface mock, It's hard to believe that it's a path to the right direction (towards achieving confidence in the code) because we are increasing complexity which is already pretty high.


Can't change language with physical keyboard

Hi, I'm using physical keyboard with my android tablet and I can't change language when using hackers keyboard, while with default samsung keyboard I can do it with shift+space.
Is there anything I can do about it?

Sliding finger on spacebar should do it.

I mean... physical keyboard... like... connected with bluetooth.


Stacked planes with 3D world generated Marching Cubes

When switching the world generation type to 3D in my marching cubes world the outcome are multiple layers of a 2D-generated landscape (see attachment). What am I missing here?

My bad: AChunkBase::GenerateHeightMap() called GenerateHeightMap2D(ActorLocation); instead of GenerateHeightMap3D(ActorLocation);
copy and waste.


Add documentation link to README

Add link to documentation at https://jni.github.io/affinder/
The gh-pages docs don't pop up for me in a google search for affinder, whereas the github repo is easy to find.
This makes it too easy to assume that there are no docs, which is a shame given all the hard work James put into PR https://github.com/jni/affinder/pull/53

Blech, sorry I missed this originally @GenevieveBuckley, such an easy PR to merge! 😅 🙏 Thank you!


[CT-1281] [Bug] column names are not escaped in tests even if quoted in schema.yml

Is this a new bug in dbt-snowflake?

[X] I believe this is a new bug in dbt-snowflake
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Similar to https://github.com/dbt-msft/dbt-sqlserver/issues/121 - I wrote a test with a column with a space in its name "Has logged in in the last 30 days", and tested it for not_null, the generated test does not quote the name of the column and fails in Snowflake.
I tried to change the yml name to be double (and eventually single) quoted and ran it again with the same behavior.
Expected Behavior
I would expect the column name to be double quoted in snowflake to allow arbitrary identifiers.
Steps To Reproduce

Create a model (I used a view but it probably doesn't matter) and create a new column with a space in its name.  select null as "this column has a space in its name"
Test the column is not_null in your schema.yml
The test fails as it writes out the test like the following:

select this column has a space in its name
from database.schema.☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺
where this column has a space in its name is null

Relevant log output
Actual error from a relevant log

[0m22:47:14.961278 [debug] [Thread-1  ]: Database Error in test not_null_* (models\stack_overflow\schema.yml)
  001003 (42000): SQL compilation error:
  syntax error line 12 at position 17 unexpected '1'.
  syntax error line 14 at position 10 unexpected 'asked'.
  compiled SQL at target\run\core_metrics\models\stack_overflow\schema.yml\not_null_*_15a5ebc1410cad026adc07cb5988bff7.sql

Environment
- OS: Windows 10 Enterprise 64-bit (10.0, Build 19044) (19041.vb_release.191206-1406)
- Python: Python 3.8.10
- dbt-core: 1.2.1
- dbt-snowflake: 1.2.0

Additional Context
No response

So after finding https://docs.getdbt.com/reference/resource-properties/quote I am closing this as I have a workaround but it still seems weird that identifier doesn't quote identifiers when running these tests.

@sta-ck Just to clarify — you were able to get this working when you set:
version: 2
models:
  - name: model_name
    columns:
      - name: 'Has logged in in the last 30 days'
        quote: true
        tests:
          - not_null

But it was not working when you added the quotes within the yaml (including the awkward double-quoting shown below)?
version: 2
models:
  - name: model_name
    columns:
      - name: '"Has logged in in the last 30 days"'
        tests:
          - not_null


Add cbtis278.edu.mx

URL: https://www.cbtis278.edu.mx/
IT related course offer: https://www.cbtis278.edu.mx/ofimatica-2/
Proof of ownership: https://www.cbtis278.edu.mx/mensaje-director/

@julianparra1 Pull request merged. Thank you.


[BUG] The value of print() in UDF apps doesn't show up in logs even when show_log=True

As titled. Need investigation.

It is invalid? Or?


test: use installed cypress version in yarn pnp example

This PR removes the use of yarn dlx from

.github/workflows/example-yarn-modern-pnp.yml
README > Yarn Plug'n'Play

and changes running Cypress from
command: yarn dlx cypress run to
command: yarn cypress run.
Issue
yarn dlx cypress run causes the latest version of Cypress to be used, with no regard of the version coming from package.json. This should not be the default way of demonstrating github-action with Yarn Plug'n'Play. The Cypress test should run using the exact version installed by yarn install.
The problem can be seen in job<PHONE_NUMBER> from PR https://github.com/cypress-io/github-action/pull/904 which reverts the example to installing Cypress 12.9.0. Despite this, the example actually runs with Cypress 12.11.0.
Verification
Install an older version of Cypress e.g. with yarn install<EMAIL_ADDRESS>-D -E, run the workflow .github/workflows/example-yarn-modern-pnp.yml and check that the Cypress test runs with the older, selected version.

A successful run is recorded in job<PHONE_NUMBER>.

@MikeMcC399 I should have looked more into npx, I thought it was acting the same as yarn dlx and installing a new package every time. So by using yarn dlx in my PR I assumed I would actually keep it consistent with how the action worked by default, but now I'm seeing that isn't the case. 🤦♂
Good catch!

@PilotConway
Many thanks for your confirmation! I'm still ramping up on Yarn Plug'n'Play so I didn't catch this issue until after your PR was merged.
npx will only install a package if one isn't already available. It will use the version defined in local dependencies if possible.

@marktnoonan
Could we get this merged?
It would avoid Yarn Plug'n'Play users copying an incorrect example from https://github.com/cypress-io/github-action/commit/73fc04a0729a5f83d5619c2f53d35f92fb352089 which might trip them up as new versions of Cypress are released and they have chosen to remain with an earlier version. Without this PR the action will always run with the latest version of Cypress when Yarn Modern (version 2 and later) is configured with the default setting of pnp.
After the PR is merged, the action uses the version of Cypress taken from package.json => yarn.lock and does not force the use of cypress@latest.

Hi @nagash77
Can this PR be moved along? It was approved 2 weeks ago by @AtofStryker. A second approval is missing.


chore: changing default values for policy-cidr-match-mode

Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[ ] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[ ] Provide a title or release-note blurb suitable for the release notes.
[ ] Are you a user of Cilium? Please add yourself to the Users doc
[ ] Thanks for contributing!

This PR changes the default value of policy-cidr-match-mode to nodes while installation.
Since this has unwanted consequences on existing installations, the changed is being supported by upgradeCompatibility flag.
The intended behaviour of this change is

for all new installations policy-cidr-match-mode is set to nodes by default
for upgrades if no upgradeCompatibility is set or if upgradeCompatibility >= 1.17 then policy-cidr-match-mode is set to nodes.
for upgrades if upgradeCompatibility < 1.17 then the policy-cidr-match-mode remains unchanged.
docs can be found here

Fixes: #31961
Changed default values for policy-cidr-match-mode to nodes

Local tests

When upgradeCompatibility  is not provided then policy-cidr-match-mode is set to nodes as defined in values.yaml.

helm template test-release --debug  ./install/kubernetes/cilium \
  --namespace kube-system | grep 'policy-cidr-match-mode'
install.go:222: [debug] Original chart version: ""
install.go:239: [debug] CHART PATH: /Users/anuragdubey/Documents/GitHub/cilium/install/kubernetes/cilium

# of policy-cidr-match-mode is changed to the one defined in values.yaml
  policy-cidr-match-mode: "nodes"

When upgradeCompatibility  is provided as 1.17 then policy-cidr-match-mode is set to nodes as defined in values.yaml.

helm template test-release --debug  ./install/kubernetes/cilium \
  --set upgradeCompatibility=1.17 \
  --namespace kube-system | grep 'policy-cidr-match-mode'
install.go:222: [debug] Original chart version: ""
install.go:239: [debug] CHART PATH: /Users/anuragdubey/Documents/GitHub/cilium/install/kubernetes/cilium

# of policy-cidr-match-mode is changed to the one defined in values.yaml
  policy-cidr-match-mode: "nodes"

When upgradeCompatibility  is provided as 1.18 then policy-cidr-match-mode is set to nodes as defined in values.yaml.

helm template test-release --debug  ./install/kubernetes/cilium \
  --set upgradeCompatibility=1.18 \
  --namespace kube-system | grep 'policy-cidr-match-mode'
install.go:222: [debug] Original chart version: ""
install.go:239: [debug] CHART PATH: /Users/anuragdubey/Documents/GitHub/cilium/install/kubernetes/cilium

# of policy-cidr-match-mode is changed to the one defined in values.yaml
  policy-cidr-match-mode: "nodes"

When upgradeCompatibility  is provided as 1.16 then policy-cidr-match-mode is not set and hence remains unchanged.

helm template test-release --debug  ./install/kubernetes/cilium \
--set upgradeCompatibility=1.16 \
--namespace kube-system | grep 'policy-cidr-match-mode'
install.go:222: [debug] Original chart version: ""
install.go:239: [debug] CHART PATH: /Users/anuragdubey/Documents/GitHub/cilium/install/kubernetes/cilium

# of policy-cidr-match-mode is changed to the one defined in values.yaml

/test

/test

Let's get someone from the @cilium/sig-policy team to chime in here, as this is a pretty significant change

@Anurag252 Could you provide some context as for the motivation for this change?

I had a bit more of a think about this, and I'm concerned about accidentally exploding policy map sizes in the case of remote-node and cluster entity selectors.
I have a plan to prevent this by using partial wildcarding, but it probably won't happen until v1.18.
So, I'm sorry, @Anurag252, but we're not quite ready for this. This is a solid PR, but some dependencies aren't there yet. I'll be closing this for now. I really appreciate your willingness to jump in :-).


MIC-000: Fix not-authorised typo

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.94%. Comparing base (4e526ec) to head (112056d).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #344      +/-   ##
==========================================
+ Coverage   90.86%   90.94%   +0.07%
==========================================
  Files         349      349
  Lines        5322     5322
  Branches      769      769
==========================================
+ Hits         4836     4840       +4
+ Misses        471      467       -4
  Partials       15       15

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add Limelight USB Drivers

New CSA here (new to FRC as well) Great tool BTW!
It would be useful to include the USB Driver Tool on this page: here
And maybe a link too to the "How to" for Limelight:  link
And maybe throw the Limelight files all in a folder too?

Ideally we try to avoid manually packaging anything, and only take direct downloads from the manufacturer.
Reasons mostly surround efficiency and update speed.

Sorry. I accidentally copied and pasted the same website link to both of my links above.
Here is the page from the Limelight, https://limelightvision.io/pages/downloads see USB Drivers, which redirects to here https://github.com/raspberrypi/usbboot/raw/master/win32/rpiboot_setup.exe
Perhaps that redirect is the basis of your comment, "avoid manually packaging anything"?
But without that driver your out of luck till you can find some useable internet.

I was more referring to the comment below.

And maybe throw the Limelight files all in a folder too?

The driver files would be a good addition - feel free to make a PR - the CSV format should be pretty self explanatory.


Support nullable ListFields with django-rest-framework

As mentioned in https://github.com/wharton/drf-excel/issues/61 it doesn't work when a ListField has a null value in it.
This should fix that 🥳

@Rmvandiepen Hey, I very much appreciate the PR! I'm hoping to take some time at DjangoCon US this week during sprints to catch up on merges.  I'm pretty sure we still need to merge this one to cover all edge cases, but wanted to run it by both of you since you encountered and fixed the edge case from yesterday. Thoughts?

same, looks good!

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.

Please upload report for BASE (main@339e088). Learn more about missing BASE report.

Files with missing lines
Patch %
Lines

drf_excel/fields.py
50.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #78   +/-   ##
=======================================
  Coverage        ?   92.59%
=======================================
  Files           ?        4
  Lines           ?      351
  Branches        ?        0
=======================================
  Hits            ?      325
  Misses          ?       26
  Partials        ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Thanks a lot for your contribution and your patience 🎉


Minor updates,mostly for large datasets

Changes include:

Added filtered candidate  extraction (only extract candidate from documents that pass through a filter)
Added options for safer (but slower) candidate extraction and adding into the db
Added support for different optimizer in the config
Added option to run corpus extraction in batches (Only in single-threaded mode)
Added support for LR schedule
Added support for model selection based on F-beta score

@stephenbach here we have a major PR being opened against the master branch. I would not recommend merging it before #923, since it could cause conflicts and we really want new work being tested against the new installation framework.
What is the timeline for the merging of the 0.7.0-alpha branch?

Rebased on v0.7 in #937


top-level syntax

Current surface is almost the core term, for example, we can have let x : a = t; u directly. But in the top-level this setup is inconvenience, user will not want only single expression there in a file! Thus, the redesign is required, current plan is there will have three top-level form

let x : a = t;
postulate x : t
inductive type (notice the -> is not allowed till #29 done)data Nat
| zero : Nat
| suc : Nat -> Nat

and don't allow other forms in top-level!
Tasks

[ ] top-level let
[ ] top-level postulate
[ ] inductive type
[ ] module information (with export list)module Core (Nat)

Does the idea like following work?
data Raw
    = RSrcPos Position Raw
    | RVar Name               -- x
    | RLam Name Raw           -- λ x . t
    | RApp Raw Raw            -- t u
    | RU                      -- U
    | RPi Name RTy RTy        -- (x : a) → b
    | RTopLevel TopLevelRaw

data TopLevelRaw
    = RLet Name RTy Raw Raw   -- let x : a = t; u
    | RPostulate Name RTy Raw -- posulate x : a; u
    -- inductive type
    -- data Nat
    -- | zero : Nat
    -- | suc : Nat -> Nat
    -- ; u
    | RData Name (List (Name, RTy)) Raw

data ModuleInfoRaw = ....

data ModuleRaw = ModuleRaw ModuleInfoRaw TopLevelRaw

or you want to make it a more flattened structure?
data Raw
    = RSrcPos Position Raw
    | RVar Name               -- x
    | RLam Name Raw           -- λ x . t
    | RApp Raw Raw            -- t u
    | RU                      -- U
    | RPi Name RTy RTy        -- (x : a) → b
    | RTopLevel TopLevelRaw

data TopLevelRaw
    = RLet Name RTy Raw   -- let x : a = t
    | RPostulate Name RTy -- posulate x : a
    -- inductive type
    -- data Nat
    -- | zero : Nat
    -- | suc : Nat -> Nat
    | RData Name (List (Name, RTy))

data ModuleInfoRaw = ....

data ModuleRaw = ModuleRaw ModuleInfoRaw (List TopLevelRaw)

The second one, and Raw will not need RTopLevel, it's lower expression. On the another hand, Raw need another RLet Name RTy Raw Raw, for let x : a = t in u
You can write TLet as following to avoid conflict I guess
data TopLevelRaw
    = TLet Name RTy Raw   -- let x : a = t
    | TPostulate Name RTy -- posulate x : a
    -- inductive type
    -- data Nat
    -- | zero : Nat
    -- | suc : Nat -> Nat
    | TData Name (List (Name, RTy))


refactor: make setup script able to update an existing installation

I think this PR needs renaming and a description what it actually does: complete rewrite, change in ui functionality, ability to be rerun, what else.
Then it would really great if some people who have been using it could give it a spin or two.


only send common device values in fhir bundle

BACKEND PULL REQUEST
Related Issue

part of #5822

Changes Proposed

Only pick common values for equipment_uid and testkit_name
Correct the service request to use test_order_loinc and completed status in bulk uploader fhir

Testing

How should reviewers verify this PR?

It kind of feels like these changes should have broken an existing unit test... Sonar is happy with the coverage, but maybe it would be worthwhile to test this new behavior more explicitly?

We also have the story that Mike is working on to improve testing coverage for the fhir work fwiw.


recv_deadline with past instant is ambiguous

Hello,
Thanks for your work on this crate.
I find recv_deadline on a channel a bit ambiguous when we pass an Instant that is in the past. This behavior isn't documented and, in my first intuition was: it will not even try to recv as the deadline is already pass. After a test it shows me that even if the deadline is in the past but there is already a message in the channel he will be received.
Do you think the behavior should change or is it possible to document it ?

"deadline" relates to whether or not to wait for a message for how long, and I think it is reasonable to receive it if the message is immediately available.
I think it is reasonable to document the behavior.


Add test - confirm summary is blank when editing a case

Right now, I am seeing on production, the previous summary lingering.

This is a problem only when editing from the admin panel.  So I will table the issue for now as a known, low priority issue.

So you need to be an admin editing an article to see the previous summary? How is this different from expectations?

Anyone can see the previous summary by looking at the history page.  The previous summary should really not show in the edit form for anyone, but at this point since it's just us two, I think the risk of someone forgetting to update the summary and using the old one is limited.


operator cockroachdb (6.0.0)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible

/merge possible

/merge possible

@chrisseto @udnay @dmesser this PR has been waiting for approval for a while. Can we merge it?

@mporrato Since all the tests check out I think this would be up to @udnay and @himanshu-cockroach. Remember that you can add yourself to the maintainer list of this operator like described in the docs so no authorization is needed from the maintainers.

/merge possible


Fav Icon color alert status

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
UI Feature
🔖 Feature description
I have many browser tabs open during the day. One of those is uptime kuma, I was thinking how nice it would be to look up at the tab with favicon and if any service was down it would turn red instead of green.
Once all the services are up again turn back to green. Just a quick visual to know all it ok or not. I find myself actually opening the browser page just to take a look and then moving on to something else.
I have no clue how this could be done just tossing a feature idea out there. If this has been brought up already sorry. Thank you!
✔ Solution
Once a service ( any service out of all that are enabled ) goes down the favicon turns RED, maybe even start blicking. Once all is resumed and back to normal it goes back to solid green.
❓ Alternatives
page refreshes from noticing a service is down and another H1 name is displayed. Instead of "Uptime Kuma" it could say "Uptime Kuma Down" or "Downtime Kuma"
If possible have a enable / disable button for this feature in settings.
📝 Additional Context
No response

Can confirm it is working in latest versions (1.14.0+)


[Bug]: SLC ProductionDateTime is not consistently accurate enough for reporting purposes

Checked for duplicates
Yes - I've already checked
Describe the bug
Generating accountability reports show that retrieval time for SLC products is inaccurate. This inaccuracy comes from the metadata in CMR. We should use ProviderDates Insert timestamps for reporting purposes for SLC and other products.
What did you expect?
I expected retrieval time for SLC to be some time after sensor time.
Reproducible steps
1.ingest SLC
2. generate a retrieval time report in bach-ui
3. observe retrieval times and public available date times.

Environment
- INT

Store both ProviderDate: Insert and productionDateTime.


b_thread deepcopy bug fix and external event support

Hi @adielashrov. please review this pull request. it contains a fix for the thread deepcopy issue and external events support. We still need to figure out how external event support acts in rich events protocol.
In any case, let me know what you think (don't merge the pull request yet)


services.node-red.withNpmAndGcc does not work as expected, project support

Describe the bug
Even with withNpmAndGcc I was not able to install node-red-contrib-modbus via the palette manager. Result was:
13 Jan 04:53:24 - [info] Modul wird installiert: node-red-contrib-modbus, Version: 5.27.2
13 Jan 04:53:35 - [warn] Installation des Moduls node-red-contrib-modbus ist fehlgeschlagen:
13 Jan 04:53:35 - [warn] ------------------------------------------
13 Jan 04:53:35 - [warn] npm WARN config production Use `--omit=dev` instead.
npm WARN deprecated<EMAIL_ADDRESS>The library contains critical security issues and should not be used for production! The maintenance of the project has been discontinued. Consider migrating your code to isolated-vm.
npm ERR! code ENOENT
npm ERR! syscall spawn sh
npm ERR! path /persist/node-red/node_modules/serialport/node_modules/@serialport/bindings-cpp
npm ERR! errno -2
npm ERR! enoent spawn sh ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in: /persist/node-red/.npm/_logs/2024-01-13T03_53_25_156Z-debug-0.log
13 Jan 04:53:35 - [warn] ------------------------------------------
Error: Installation fehlgeschlagen
    at /nix/store/3bn3fgd1yqwf4rnpff6f0b954vlfxrra-node-red-3.1.0/lib/node_modules/node-red/node_modules/@node-red/registry/lib/installer.js:285:25
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
13 Jan 04:53:35 - [error] Error: Installation fehlgeschlagen

Steps To Reproduce
Steps to reproduce the behavior:

Setup node-red service with withNpmAndGcc enabled
Open web interface, palette manager, install node-red-contrib-modbus

Running nixpkgs-23.11, tried with nodejs_18 and nodejs_20.
Expected behavior
Clean install of the module. The palette manager works fine as is for node-red-dashboard, for example.
Additional context
I was able to solve it with an override:
    (final: prev:
    {
      node-red = prev.nodePackages.node-red.overrideAttrs (oldAttrs: {
        nativeBuildInputs = oldAttrs.nativeBuildInputs or [] ++ [ prev.makeWrapper ];
        postInstall = oldAttrs.postInstall or "" + ''
          mkdir -p $out/bin
          wrapProgram $out/bin/node-red \
            --prefix PATH : "${prev.lib.makeBinPath [
              # module installation
              final.nodejs
              final.nodePackages.npm
              final.bash
              final.gcc
              # projects
              final.git
              final.openssl
              final.openssh ]}"
        '';
      });
    })

I would rename withNpmAndGcc to withBuildEnv (and have it include nodejs and bash) and add an additional option withProjects to provide deps for the new NodeRED project manager – but my Nix fu is reaching its limits here, to implement this cleanly.
Notify maintainers
@pbsds @emilylange @chewblacka @h7x4
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.71, NixOS, 23.11 (Tapir), 23.11.20240108.6723fa4`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Add a :+1: reaction to issues you find important.

I think none of the mentioned contributors are familiar with the package. Via #116578: @MatthewCroughan @nixinator

The correct approach is packaging the nodes purely with dream2nix or node2nix, then symlinking that pure, derivation based node_modules folder into the path for node-red. Anything else is just bound to run into dependency issues. You can't just give NPM everything it could possibly want or need at runtime.
I'm doing something like that here https://github.com/nix-how/ming
Firstly, I'm reproducing a node using dream2nix:
https://github.com/nix-how/ming/blob/0a91236e7c90dfdd8b306f41b9db89d01fb343c0/flake.nix#L34-L40
Then I symlink the resulting node_modules folder into the node-red path
https://github.com/nix-how/ming/blob/0a91236e7c90dfdd8b306f41b9db89d01fb343c0/vm.nix#L90-L92

I should also note that nodes are just NPM packages that can be packaged as part of nodePackages in Nixpkgs, and if they were this would mean you could easily include them in a list.
So if you can put https://flows.nodered.org/node/node-red-contrib-modbus into nodePackages I can make a module option for node-red that looks like
{
  services.node-red = {
    enable = true;
    nodes = [  nodePackages.node-red-contrib-modbus ];
  };
}

I prefer the dream2nix approach described above though, so I don't think I'll spend any time on this since what I've described above is easy to implement in your own system.  Maintaining the node-red nodes as part of nodePackages in Nixpkgs will likely be a maintenance burden compared to calling a single dream2nix function in your own system flake.

Surely it's preferable to have the modules available as proper Nix packages. OTOH, I see bash and node as pretty reasonable components of a node build environment – and they are installed anyway, so it's just a few more links.
What do you think about the project support? Those deps stem from NodeRED itself.

It's more complicated to let NPM manage the packages than to just use Nix. Just make a derivation for the package and then pass it in.

Ok, I think the nodes option would be a good idea. Still, how would you deal with the project feature and its deps?

Still, how would you deal with the project feature and its deps?

Oh yeah, I played with that a bit hoping it would be good, but I found that it was poorly implemented and you're better off making a systemd service that does a git commit and push on the service outside of node-red. I find that node-red is really good on its own, with the core nodes, and a few manually packaged nodes.
Giving node-red access to NPM means you can try to install any unreproducible node, and potentially break your installation.
Giving node-red access to git and ssh-keygen results in key management issues that are complex to solve with nix/jq/systemd since it doesn't give you methods of providing the keys and tries to do everything itself. The git interface is not complete or worth using IMO.
If you want to do these things, all you have to do is add do the path like you've already suggested in the original post, and this overriding/overlay ability via the Nix expression language is what Nix is good at.
An easier way than patching the PATH of the package, for your own configuration is like this:
{ pkgs, ... }:
{
  systemd.services.node-red.path = with pkgs; [ git ssh-keygen ];
}

Adding these deps to the path in Nixpkgs just means we have more untested/untestable features that people might make issues about. And I know from experience with node-red that these features aren't that great.

You could also make it an argument on the node-red package, that would make the most sense. Then you could have:
{
  services.node-red.package = (node-red.override { withProjectsFeature = true; });
}

Oh yeah, I played with that a bit hoping it would be good, but I found that it was poorly implemented and you're better off making a systemd service that does a git commit and push on the service outside of node-red. I find that node-red is really good on its own, with the core nodes, and a few manually packaged nodes.
Giving node-red access to NPM means you can try to install any unreproducible node, and potentially break your installation. Giving node-red access to git and ssh-keygen results in key management issues that are complex to solve with nix/jq/systemd since it doesn't give you methods of providing the keys and tries to do everything itself. The git interface is not complete or worth using IMO.

I agree, “projects” is basically still beta. I'm pretty new to Nix (and NodeRED) and I like to keep my little unreproducible, mutable corners – especially for exploring a technology and various modules in this case. It's just not much fun to poke around declarations for half an hour for a quick test. On a production system it's different, of course, but I feel it's nice to keep both ways open (for Nix in general).
Closing this issue now, thank you for your helpful input!
P.S.: Still I think

I would rename withNpmAndGcc to withBuildEnv (and have it include nodejs and bash)

would be a good idea.  😌

@MatthewCroughan
dream2nix does not seem to work for me, there's basically no documentation and the community/devs are not able or willing to help on the Matrix chat or GitHub issues. I made an attempt, but I suspect I'm pretty much on a wrong path there.
I had more success with buildNpmPackage and then using your systemd.tmpfiles hack to inject that into node-red. But I couldn't figure out so far how to bundle more than one package this way. (Which appears to be easier with dream2nix.) Adding it to the node-red overlay with buildInputs = oldAttrs.buildInputs or [] ++ [ node-red-contrib-home-assistant-websocket ]; did not make any difference – which makes sense, since it's required during runtime. That's where your earlier suggestion would fit in, I assume.

Package example using buildNpmPackage
{ lib, buildNpmPackage, fetchFromGitHub }:

buildNpmPackage rec {
  pname = "node-red-contrib-home-assistant-websocket";
  version = "0.59.0";

  src = fetchFromGitHub {
    owner = "zachowj";
    repo = pname;
    rev = "v${version}";
    hash = "sha256-BvptqazEfcRm5sdQrWNX46AfhLhPwAHC05fCHEOp9Xk=";
  };

  npmDepsHash = "sha256-ShWmaBrZWruDiILaH2AGxtcuP2F9Sw8LXnHW31lnJVk=";

  # The prepack script runs the build script, which we'd rather do in the build phase.
  npmPackFlags = [ "--ignore-scripts" ];

  meta = with lib; {
    description = "Node-RED integration with Home Assistant";
    license = licenses.mit;
  };
}

In your example it appears you created a separate flake (and repo) that also contains the node package sources. What I'm after is a way to pull in a number of packages via GitHub from my main NixOS configuration.
Would be great if you could shed some more light, this is slightly frustrating...

I also stumbled upon the problem of not being able to install nodes from the palette manager.
The description of the option ´services.node-red.withNpmAndGcc´  says:
Give Node-RED access to NPM and GCC at runtime, so ‘Nodes’ can be downloaded and managed imperatively via the ‘Palette Manager’.

Even. If this is not the correct declarative way, I would expect it to work.
A way to declare the usage of arbitrary 3rd party nodes in a declarative way would be the best solution though.
As a NixOS beginner, I did not understand the solution from @MatthewCroughan using dream2nix. Is there a comprehensive example somewhere?
This blocks moving my smarthome server to NixOS.

I think the example I provided is comprehensive. You have to learn Nix.

Ok. I ltried and learned and got it to work with several Node-Red modules separately. But when I'm trying to use multiple nodes at once, I fail at linking both to the module path.
Coming from your example:
  systemd.tmpfiles.rules = [
    "L+ ${config.services.node-red.userDir}/node_modules 0755 ${config.services.node-red.user} ${config.services.node-red.group} - ${node-red-dashboard}/lib/node_modules"
  ];

I wanted it to link to the subfolders like that:
  systemd.tmpfiles.rules = [
    "L+ ${config.services.node-red.userDir}/node_modules/node-red-dashboard 0755 ${config.services.node-red.user} ${config.services.node-red.group} - ${node-red-dashboard}/lib/node_modules/node-red-dashboard"
  ];

Which results in
Detected unsafe path transition /var/lib/node-red/node_modules (owned by node-red) → / (owned by root) during canonicalization of var/lib/node-red/node_modules.

So either my thought of linking is wrong here, or I need to change the owner of the module in the store somehow...
I'm aware, that this is not strictly related to this issue,  but it can help to work around the problem and use Node-Red modules declaratively.


gam info domain - KeyError: u'language'

Full steps to reproduce the issue:

gam info domain

Actual outcome (what errors or bad behavior do you see instead?):
Traceback (most recent call last):

File "/Users/jan/R-D/gam/src/gam.py", line 13170, in
sys.exit(ProcessGAMCommand(sys.argv))
File "/Users/jan/R-D/gam/src/gam.py", line 12575, in ProcessGAMCommand
doGetDomainInfo()
File "/Users/jan/R-D/gam/src/gam.py", line 1722, in doGetDomainInfo
doGetCustomerInfo()
File "/Users/jan/R-D/gam/src/gam.py", line 1752, in doGetCustomerInfo
print u'Default Language: %s' % customer_info[u'language']
KeyError: u'language'

I checked the response for this client from the API. It is actually not returning any language-key, so I suppose it should default to 'en' as stated in the overview.

What do you see if you go to admin.google.com > Company profile > Profile ?
Jay


Disallow \8 and \9 escape sequences in string literals (no-nonoctal-decimal-escape)

https://eslint.org/docs/rules/no-nonoctal-decimal-escape
Although not being specified in the language until ECMAScript 2021, \8 and \9 escape sequences in string literals were allowed in most JavaScript engines, and treated as "useless" escapes:
"\8" === "8"; // true
"\9" === "9"; // true

Since ECMAScript 2021, these escape sequences are specified as non-octal decimal escape sequences, retaining the same behavior.
Nevertheless, the ECMAScript specification treats \8 and \9 in string literals as a legacy feature. This syntax is optional if the ECMAScript host is not a web browser. Browsers still have to support it, but only in non-strict mode.
Regardless of your targeted environment, these escape sequences shouldn't be used when writing new code.
Rule Details
This rule disallows \8 and \9 escape sequences in string literals.
Examples of incorrect code for this rule:
/*eslint no-nonoctal-decimal-escape: "error"*/

"\8";

"\9";

var foo = "w\8less";

var bar = "December 1\9";

var baz = "Don't use \8 and \9 escapes.";

var quux = "\0\8";

Examples of correct code for this rule:
/*eslint no-nonoctal-decimal-escape: "error"*/

"8";

"9";

var foo = "w8less";

var bar = "December 19";

var baz = "Don't use \\8 and \\9 escapes.";

var quux = "\0\u0038";

I can't imagine there being any ecosystem impact from this – accepted for standard 17.


Pass on QueryString from Upstream to Downstream

Expected Behavior / New Feature
I want to forward the queryString parameters passed on the original request to the downstream.
Actual Behavior / Motivation for New Feature
When using the following configuration:
{
     "DownstreamPathTemplate": "/{url}",
     "DownstreamScheme": "http",
     "UpstreamPathTemplate": "/messaging/{url}",
     "UpstreamHttpMethod": [ "Get" ],
     "DownstreamHostAndPorts": [
       {
         "Host": "localhost",
         "Port": 5001
       }
     ]
   }

I want to pass on optional queryStrings as well.
So when navigating to:
http://localhost:6992/messaging/api/v1/messages?contractId=86
I want it to be passed on like:
http://localhost:5001/api/v1/messages?contractId=86
But for this scenario as well:
http://localhost:6992/messaging/api/v1/messages
I want it to be passed on like:
http://localhost:5001/api/v1/messages
Specifications

Version: 12.0.1
Platform: win, net462
Subsystem:

Isn't this already working? https://ocelot.readthedocs.io/en/latest/features/routing.html#routing

Hi @stephanonline !
The Routing feature was implemented long years ago. So, Placeholders work fine.

{
     "DownstreamPathTemplate": "/{url}",
     "UpstreamPathTemplate": "/messaging/{url}",
}

Your route is absolutely valid, because This will forward any path + query string combinations to the downstream service after the path
Are you still with Ocelot?

Not an issue! Question has been answered.


NPE in getAccountInfo() if result is nil

If a non-compliant RPC server returns result: null for getAccountInfo(), the client will panic with null pointer deref (line 127 on out.Value because out is nil).
https://github.com/gagliardetto/solana-go/blob/dd0af958252d8cdd28db04a39fc67103223946cc/rpc/getAccountInfo.go#L123-L127
Ideally the RPC client would never panic under any circumstances

How about
if out == nil || out.Value == nil {

but in that case, can we be sure that out == nil means not found ?

imo, out == nil violates the spec, so it's best to error here. Maybe we could wrap CallForInto to return an error if out == nil after unmarshaling.

In some cases, result == nil follows the spec (e.g. getBlock: https://github.com/solana-labs/solana/blob/master/docs/src/developing/clients/jsonrpc-api.md#getblock )

if out == nil {
   return errors.New("got null response")
}


Packages missing when trying to bootup flask application

What happened?
I am trying to switch from a classic Dockerfile to paketo buildpacks.
Before I had a Dockerfile in which I call pipenv install --deploy --system to install all packages and the container image was functional.
After creating the image with Paketo it fails to start because there are missing required packages. At the beginning the dependency Unleash failed while importing six. Then I removed Unleash for testing purposes and it failed when trying to import certifi (see below).
Does it have something to do, that the buildpack does not use the --system flag? Or is some path set wrong so it can't find the system packages?
Build Configuration

What platform (pack, kpack, tekton buildpacks plugin, etc.) are you  using? Please include a version.
pack

What buildpacks are you using? Please include versions.

===> DETECTING
7 of 10 buildpacks participating
paketo-buildpacks/ca-certificates 2.4.2
paketo-buildpacks/cpython         0.7.3
paketo-buildpacks/pip             0.7.0
paketo-buildpacks/pipenv          0.2.1
paketo-buildpacks/pipenv-install  0.2.3
paketo-buildpacks/python-start    0.7.0
paketo-buildpacks/procfile        4.4.1

What builder are you using? If custom, can you provide the output from pack  inspect-builder <builder>?
paketobuildpacks/builder:base

Can you provide a sample app or relevant configuration (buildpack.yml,  nginx.conf, etc.)?

[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]
flask = "*"
flask-dance = "*"
pyopenssl = "*"
flask-wtf = "*"
python-gitlab = "*"
python-slugify = "*"
gunicorn = "*"
requests = "*"
unleashclient = "*"
cachetools = "*"

[dev-packages]
unittest-xml-reporting = "*"
coverage = "*"

[requires]
python_version = "3.9"

[$] docker run --interactive --tty --env PORT=8080 --publish 8080:8080 my-app-paketo
[2021-12-14 12:36:48 +0000] [1] [INFO] Starting gunicorn 20.1.0
[2021-12-14 12:36:48 +0000] [1] [INFO] Listening at: http://<IP_ADDRESS>:8080 (1)
[2021-12-14 12:36:48 +0000] [1] [INFO] Using worker: sync
[2021-12-14 12:36:48 +0000] [18] [INFO] Booting worker with pid: 18
[2021-12-14 12:36:48 +0000] [18] [ERROR] Exception in worker process
Traceback (most recent call last):
  File "/layers/paketo-buildpacks_pipenv-install/packages/workspace-dqq3IVyd/lib/python3.9/site-packages/gunicorn/arbiter.py", line 589, in spawn_worker
    worker.init_process()
  File "/layers/paketo-buildpacks_pipenv-install/packages/workspace-dqq3IVyd/lib/python3.9/site-packages/gunicorn/workers/base.py", line 134, in init_process
    self.load_wsgi()
  File "/layers/paketo-buildpacks_pipenv-install/packages/workspace-dqq3IVyd/lib/python3.9/site-packages/gunicorn/workers/base.py", line 146, in load_wsgi
    self.wsgi = self.app.wsgi()
  File "/layers/paketo-buildpacks_pipenv-install/packages/workspace-dqq3IVyd/lib/python3.9/site-packages/gunicorn/app/base.py", line 67, in wsgi
    self.callable = self.load()
  File "/layers/paketo-buildpacks_pipenv-install/packages/workspace-dqq3IVyd/lib/python3.9/site-packages/gunicorn/app/wsgiapp.py", line 58, in load
    return self.load_wsgiapp()
  File "/layers/paketo-buildpacks_pipenv-install/packages/workspace-dqq3IVyd/lib/python3.9/site-packages/gunicorn/app/wsgiapp.py", line 48, in load_wsgiapp
    return util.import_app(self.app_uri)
  File "/layers/paketo-buildpacks_pipenv-install/packages/workspace-dqq3IVyd/lib/python3.9/site-packages/gunicorn/util.py", line 359, in import_app
    mod = importlib.import_module(module)
  File "/layers/paketo-buildpacks_cpython/cpython/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 850, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/workspace/app.py", line 7, in <module>
    from flask_dance.contrib.gitlab import make_gitlab_blueprint, gitlab as gl_oauth
  File "/layers/paketo-buildpacks_pipenv-install/packages/workspace-dqq3IVyd/lib/python3.9/site-packages/flask_dance/__init__.py", line 1, in <module>
    from .consumer import OAuth1ConsumerBlueprint, OAuth2ConsumerBlueprint
  File "/layers/paketo-buildpacks_pipenv-install/packages/workspace-dqq3IVyd/lib/python3.9/site-packages/flask_dance/consumer/__init__.py", line 1, in <module>
    from .oauth1 import OAuth1ConsumerBlueprint
  File "/layers/paketo-buildpacks_pipenv-install/packages/workspace-dqq3IVyd/lib/python3.9/site-packages/flask_dance/consumer/oauth1.py", line 5, in <module>
    from requests_oauthlib.oauth1_session import TokenRequestDenied, TokenMissing
  File "/layers/paketo-buildpacks_pipenv-install/packages/workspace-dqq3IVyd/lib/python3.9/site-packages/requests_oauthlib/__init__.py", line 3, in <module>
    from .oauth1_auth import OAuth1
  File "/layers/paketo-buildpacks_pipenv-install/packages/workspace-dqq3IVyd/lib/python3.9/site-packages/requests_oauthlib/oauth1_auth.py", line 9, in <module>
    from requests.compat import is_py3
  File "/layers/paketo-buildpacks_pipenv-install/packages/workspace-dqq3IVyd/lib/python3.9/site-packages/requests/__init__.py", line 133, in <module>
    from . import utils
  File "/layers/paketo-buildpacks_pipenv-install/packages/workspace-dqq3IVyd/lib/python3.9/site-packages/requests/utils.py", line 26, in <module>
    from . import certs
  File "/layers/paketo-buildpacks_pipenv-install/packages/workspace-dqq3IVyd/lib/python3.9/site-packages/requests/certs.py", line 15, in <module>
    from certifi import where
ModuleNotFoundError: No module named 'certifi'
[2021-12-14 12:36:48 +0000] [18] [INFO] Worker exiting (pid: 18)
[2021-12-14 12:36:48 +0000] [1] [INFO] Shutting down: Master
[2021-12-14 12:36:48 +0000] [1] [INFO] Reason: Worker failed to boot.

It seems like this could be caused by an issue similar to what we saw over in the pip-install: https://github.com/paketo-buildpacks/pip-install/pull/58


Make hotkey-tabbing to Plots pane also focus on it [Feature request]

If I do Ctrl + W after switching to Plots pane with hotkeys, it closes the IPython console instead. It also ignores arrow keys, so I can't up and down to change plots. I still need to manually click somewhere in the Plots pane for these things to work.
I switch between Plots and IPython fairly often with hotkeys, it'd be nice if focus was switched also.

Hi @OverLordGoldDragon thank you for the feedback! I think a similar request but related with the Help pane was being discussed over https://github.com/spyder-ide/spyder/issues/22189. Most probably going with the flexible option mentioned at https://github.com/spyder-ide/spyder/issues/22189#issuecomment-2248269160 should help with this one too :+1:


Fix Pytest profile failed with "local variable 'case' referenced before assignment"

When the CLI working with pytest-launchable, the Pytest profile on the CLI failed with the message "local variable 'case' referenced before assignment". So, I add a few lines to define the variables at the top of the function.

Oh, man… 🤦♂
launchable/test_runners/pytest.py:96: error: Variable annotation syntax is only supported in Python 3.6 and greater
Found 1 error in 1 file (errors prevented further checking)

Is it difficult to add test codes to confirm fixing it?


Issue#793: iDRAC telemetry acquisition

Fixes #793
Description of the Solution
Executing telemetry.yml will fetch iDRAC IP from AWX and filter iDRACs with datacenter license having firmware version>4.0 and initiate telemetry collection for the same.
If new iDRAC node is added on AWX, user can execute telemetry/add_idrac_node.yml which will start telemetry acquisition process for all newly added nodes.
Suggested Reviewers
@sujit-jadhav

@all-contributors please add @sakshiarora13 for bug


[CI] Make *nix unit test fail if C++ extension is not available

I am trying to fix the issue C++ extension availability when building/installing torchaudio from source. See https://github.com/pytorch/audio/pull/842 for the detail.
Currently our test suites automatically/silently skip tests on C++ extension if it is not available.
This is nice in local env, but in CI these tests should be enforced and reported as failure if C++ extension is not available.
This PR adds switch for making tests fail if C++ extension is not available.
This should make https://github.com/pytorch/audio/pull/845 fail so that we can debug what is wrong with the current setup.

Example of failure on CI
https://app.circleci.com/pipelines/github/pytorch/audio/3049/workflows/5b3042b8-eb77-414c-9e1e-b89e8faf6704/jobs/84548

thanks!


Having to choose between methods for retrieving a Topic or Subscription is confusing

In #393, @jeffmendoza wrote:

This library allows a lot of flexibility

I share that impression, and in particular I was confused by the presence of two methods for retrieving topics and two for retrieving subscriptions:

Project#get_topic
Project#topic

and

Project#get_subscription
Project#subscription

The method names do little to suggest a distinction, so I looked at the docs, which state:

The difference between this method and Project#get_topic is that this method does not make an API call to Pub/Sub to verify the topic exists.

To me the behavior of "avoiding the API call to verify the Topic exists" feels like it should be an option to Project#get_topic, not a separate method.
Digging into the code, however, I found a rather involved mechanism for lazy loading. In the case of Topic, does this mechanism serve any goal other than just letting the user publish a message without needlessly retrieving a topic? If not, it seems to me that much internal complexity (and potential user confusion about state) could be avoided with a method that simply accepts the topic name and message:
pubsub = gcloud.pubsub
msg = pubsub.publish  "existing-topic", "This is the first API call to Pub/Sub."

In my opinion, this simple design makes it very clear that the Topic is not being retrieved, and that "this method does not make an API call to Pub/Sub to verify the topic exists."
Clearly there could be more to this lazy loading than I was able to find on my own, so please inform me!

Much of the "lazy object" is specific to optimizing the publish use case. Performance it increased because gcloud is able to publish a message on a topic without first making the API call to retrieve the topic.
gcloud.pubsub.topic("my-topic").publish("my message") # 1 API call made

During initial development I proposed what you are proposing, a publish method at a higher level, but this was rejected at the time.
gcloud.pubsub.publish("my-topic", "my message") # 1 API call made

I find the second example less confusing. I think it would help with conceptual overhead the current design has as it doesn't introduce an additional state to the topic objects.

@stephenplusplus @tmatsuo Thoughts on the ^ proposed solution?

I like the simple solution of having
gcloud.pubsub.publish("my-topic", "my message") # 1 API call made

The question here is what is the purpose of having topic object at all? Is it really useful?

Topic is still useful for listing the subscriptions that are tracking a topic, as well as managing the IAM policy and testing the IAM permissions.

The REST representation of Topic is its name and nothing more. So if you know the name, apparently there's no sense in loading it, other than to verify existence.

I've been moving some things around in #402, and right now the difference between #topic and #get_topic, and between #subscription and #get_subscription has been removed. The methods are now the same (one is an alias of the other) and always return a looked up record. Also, Project#publish and Project#subscribe have been added to perform the single API action with optional autocreate.
We may decide to allow these methods to skip lookup and return a "lazy" object in the future, but that will be implemented as a new optional parameter to those methods instead of maintaining two different methods. One reason for this is because gcloud offers many ways to pull messages from a Subscription, and so having a way to skip lookup would be useful in those cases. Or to get/set the IAM policy without also performing the initial lookup, which would be useful for checking permissions on a topic/subscription before attempting to exercise the permissions by retrieving the resource.


Pattern: CTA section visual design & design specs provided by Reboot designers

Notes

The Reboot team is responsible for creating the visual designs and design specs for most of the patterns included in the Solutions page.  This issue is to track the transition of the Reboot design work to the DDS design & engineering team members.

Additional Information

Visual Designs & Design Specs Box folder link

Acceptance Criteria

[x] Visual designs and specs received from Reboot designers
[x]  A pdf file is created and placed in the Box folder with the updated Sketch file
[x] Meetings conducted with DDS team members to review the designs

Visual designs and design specs provided here:
https://ibm.ent.box.com/folder/109648616047
Includes sketch file and pdf

Pattern walk through meeting chaired by Alain on April 13.

@RobertaJHahn we had to update this pattern due to ontology changes so the specs also needed updating. The sketch and PDF for visual designs and specs are now updated in this folder:
https://ibm.ent.box.com/folder/109648616047


Merge branch 'main' of https://github.com/arduino/library-registry

add irm-mini-arduino library

fixed

fixed @ArduinoBot


Add CI to check for formatting issues on PRs

Closed by #29

Closed by https://github.com/WLAN-Pi/wlanpi-core/pull/29


Small: convergence_criteria for ValueFunc (etc) classes

The ValueFunc, MargValueFunc, etc classes should have a convergence_criteria attribute, so that (say) 'vFunc' can be added as a convergence criterion in the consumption-saving model. This might be all that's necessary to do the 1D transformations item on the Issues page (and add missing derivative methods, maybe).

Fixed in new commit to comments-and-cleanup.


User selection is invisible!

Hello!
With bootScore 5.1.2,2 and WP 6.0.2 when a user selects something, the selection is invisible. This only seems to occur with bootScore, and I cannot reproduce on bootstrap itself.
Example: https://www.androidacy.com

Hello,
where can something be selected on your page? There are a lot of components but I do not see a selection?

Text is being selected (you can select and try to drag and it will show it's being selected) but it's not being colored as the variables are wrong:
::selection {
    color: var(--bs-white);
    background-color: var(--bs-primary);
}

and checking you theme the variable --bs-primary doesn't exist and is replaced by --primary instead.

Yes, thats why the default Bootstrap var(--bs-primary) variables do not work in your case. You must remove bs- prefix like in example above.

--bs- is the default Bootstrap prefix https://getbootstrap.com/docs/5.2/customize/css-variables/#root-variables

This is not a break. bootScore uses default Bootstrap variables for additional CSS https://github.com/bootscore/bootscore/blob/main/scss/bootscore/_colors.scss. If you change prefix, of course they won't work.

This is not a break. bootScore uses default Bootstrap variables for additional CSS https://github.com/bootscore/bootscore/blob/main/scss/bootscore/_colors.scss. If you change prefix, of course they won't work.
This is your color :root, no --bs there:

Not sure this would work, but shouldn't we use something like then?
::selection {
  color: var(--#{$prefix}white);
  background-color: var(--#{$prefix}primary);
}

Not sure this would work, but shouldn't we use something like then?

Works ;-) Somebody want to create a PR?

Do we then want to continue using css variables, or do we want to use the scss variables? So instead use $primary to get that color.

I was looking through the codebase for more examples of using CSS variables and haven't found any (at least not in the bootscore folder) so SCSS variables would be best IMO

This one uses color variables as well https://github.com/bootscore/bootscore/blob/main/scss/bootscore_woocommerce/_wc_colors.scss


fix sale icon in customer wishlist page for RTL

Bug report
Title
fix sale icon in customer wishlist page for RTL
Issue Description
fix sale icon in customer wishlist page for RTL
Preconditions
1. framework Version- master

Steps to reproduce
1. step1- change store view to RTL
2. step2- add the sales product to the wishlist

Expected result
sale icon should place on the product's right end
Actual result

working on it

fixed in master https://prnt.sc/v3xquf


Initial work to get pip working on Mono

There's also PipeStream in PythonFile.TryGetFileHandle. Since they're no longer PipeStreams you may need to add a check.


Add AMQ Online 1.1

@ctron Thank you for this PR!
This operator is distinct from the amq-streams operator, correct?

Yes, it is however related to the EnMasse operator from PR #234

@ctron Red Hat operators are no longer being accepted to this repository. There is a separate pipeline for submitting these types of operators.
Closing this PR due to it being obsolete

@ctron Red Hat operators are no longer being accepted to this repository. There is a separate pipeline for submitting these types of operators.

Where would I find information about this "pipeline"?


Smoke test periodically fails

💡 Summary
The smoke test periodically fails on first run.  If you re-run it passes.  It appears to be unsuccessful in downloading an update for the web driver for Selenium.
Motivation and context
A more robust implementation will free developers from tracking intermittent failures.
This would be useful because developer time is important.
Implementation notes
Please provide details for implementation, such as:
Check status of download if possible.
Check integrity of zip file if possible
Re-try on failure
Report failure concisely.
Acceptance criteria
How do we know when this work is done?

[ ] Smoke test is successful NOTE: Issue is intermittent so will need to be monitored.

Closed with PR #728


[Feature Request] Add built-in categories for mounts, toys, and bags.

Currently, the "mounts" and "toys" category does not seem to exist, and toys get bundled into "Consumables", when they deserve their own category.

Bags also get bundled with a "BoE" category even if they're not bound.

It would be nice to have these categories built-in to the addon.

This is available if you turn on the Subtype category option.


I think there are some defects

First of all, I English level is not very good, please forgive me!In the process I use the moquette, I think I found several problems.
In the org.eclipse.moquette.spi.impl.ProtocolProcessor class, there is a sentence:
If (m_clientIDs.get (clientId) = = null) {
Throw new RuntimeException (String.format ("Can't find a ConnectionDescriptor for client <%s> in cache <%s>", clientId, m_clientIDs));
}
This will cause the publisher obstruction.
Also, When broker announced the news to client, if client is persistent, suddenly closed the connection or throws an exception, this time is no receipt to broker has been receiving complete. Broker will never again release relevant information to the client.

Please, could you provide an unit test or an algorithm that manifest the problem. That exception is safe checkpoint, if the clientID is not present in the cache, it means that something bad happened, so in which case do you exposed this behaviour?

'could you provide an unit test or an algorithm that manifest the problem': because involve interaction with the client, so it is not easy to provide.
'if the clientID is not present in the cache, it means that something bad happened': clientID is not in the cache, that the subscriber has appeared problem (possibly subscribers process is active kill). This time should be stored subscriber message, but should not throw an exception blocked the publisher, Is it right??

My second question may not be described clearly. When the subscriber and publisher Qos is 2, and the news is persistent. The first step, the broker process is started, the publisher process starts and released ten messages. The second step, the subscriber process start and begin to receive messages (debug mode). When the receiving end fifth messages, forced the closure of the subscriber process. The third step, the subscriber process to restart and restart the receive message. This time has not received any news. That is to say, broker lost five messages behind the.

To test similar conditions, I usually write a groovy script that acts as a client launched against a fresh start of the broker.

Not reproducible


UIAPPS-78 Bring in apps code

N.B. Do not merge until we know we can rename the repos.
Jira Issue: https://datadoghq.atlassian.net/browse/UIAPPS-78
What it does
We pull all of the code from the current apps repo at https://github.com/DataDog/apps/commit/8c5e57b77a7ca2375ef3d003baabc151b73754a8 into this repo. This lets us keep the history (with the same exact commits and SHAs!) while moving more stuff to this repo.
The diff is pretty big because it's pulling in all 135 commits from the apps repo. The only actual new stuff that's not in either the apps repo or this repo is this commit: https://github.com/DataDog/ui-extensions-sdk/pull/61/commits/e67dfee554381b82a7ca58f9b93c36cf6380895e.
TODO

[ ] Make sure we can rename the apps repo and the ui-extensions-sdk repo before merging this. The only reason I say that is that it'll minimize the amount of time these two repos need to coordinate commits. The alternative being that we'd have to merge in new commits from the apps repo if something gets in in-between merging this and renaming. That sounds more painful than just dealing with it in this PR (or trashing this PR and making a new one from scratch).

Thanks for the review!
Looks like a few more commits were added to the apps repo. I'll try to pull those into this PR and merge it. If it's too hard, I'm just going to open a new PR with similar changes.


Adding support for custom gallery properties.

Support a generic dictionary of following kind in the JSON manifest (vss-extension.json)
"galleryProperties": [{
"key": "value"
}]
which tfx-cli can interpret and convert to following in the VSIX manifest

Run sanity tests.

@kesane-msft,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@kesane-msft, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot


Suggestion: Add warning about possible anti-cheat issues in the coming soon MP anti-cheat update

My suggested text:

Warning: This modification may be detected as a cheating tool and/or considered an "unfair advantage" (due to the increased field of view) by the new Ace Combat 7 anti-cheating measure going live at the end of August.

The developers have stated that anti-cheat measures won't affect single player mods so we highly recommend not playing online with it installed until we have more information.

You can find more details at: https://service-en.bandainamcoent.eu/app/detail/a_id/4820/m/ACE COMBAT 7: SKIES UNKNOWN/t/Anti-Cheat FAQ/p/7312

I've opened a ticket with Namco to see if they know whether or not the anticheat system will flag this mod.
In the meantime, I will add this warning to the script and have the user indicate their acceptance before continuing. I may also write a "disable" script to remove the mod so that people can still play online with relative ease.
When the anticheat launches, if Namco hasn't responded, then I'll try to play online myself with the mod in place and see what happens. Nothing ventured, nothing gained. :)

a84f381ea32c2eafbc1812190fd4b8f47206f91d
Warning added. Leaving this issue open so I can investigate the anticheat when it goes live.

Seems like it's ok to use!

Sweet! Thank you!


Set up Kibana

Get Kibana up and running on the Kubernetes cluster for log viewing

Set up with fluentbit, still need to configure dashboards and searches in Kibana


Add NWB export for ephys_acute (acute probe insertion) module

Resolved with https://github.com/datajoint/element-array-ephys/pull/36 merged

Unlinking the issue since we decided to make #44 work with the ephys_no_curation module.


Specify dart line length in lsp configurations

Hello, this is not an issue rather a question to find a solution
from what i understand, the lsp server uses dart format for formatting, is there a way to override the default 80 character line length? i am using neovim with dartls configuration for nvim-lspconfig.
Thank you!

As long as your client allows you to specify the config, you can use dart.lineLength to control the line length for formatting.
In VS Code, you'd do this by adding the following to your user/workspace settings:
"dart.lineLength": 120,

The LSP server sends the client a request for the "dart" configuration and then reads the "lineLength" setting. I'm not familiar with nvim-lspconfig so I can't advise how you'd do this specifically. If it doesn't seem to work, please post back with a log of the LSP traffic (if you can't capture this from your client, you can pass --instrumentation-log-file=/foo/bar.txt when starting the LSP server).
(I'll close this in the meantime since I think it answers the question, but we can re-open if if not).


Issues of Radical Pre-train

You have done a great job, when I run the pre-training script while doing Radical Pre-train it shows the following error: main_radical.py: error: unrecognized arguments: --use_radical, why is this happening and what should I do to fix it

Thank you for your comment. I've just addressed the issue caused by the Detectron2 parser. However, the pre-training dataset has not been released due to its large size (~ several TB). We are actively exploring solutions and will keep you updated. Thank you for your interest in our paper.


Create LICENSE

Hello! Please I want to get a license for Novosibirsk Airport (UNNT). How do I do this?

Hi. How do you mean?

We want to draw an APP in Novosibirsk on SimAware (UNNT)

Budget?
Get Outlook for iOShttps://aka.ms/o0ukef

From: ikv20009 @.>
Sent: Saturday, September 10, 2022 1:07:19 PM
To: arvinjarvin/SimAware @.>
Cc: abdoa018.319 @.>; State change @.>
Subject: Re: [arvinjarvin/SimAware] Create LICENSE (#1)
We want to draw an APP in Novosibirsk on SimAware (UNNT)
—
Reply to this email directly, view it on GitHubhttps://github.com/arvinjarvin/SimAware/pull/1#issuecomment-1242715402, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AN43FI5MET3IXKPA6FGC2X3V5R2XPANCNFSM4UMTY53Q.
You are receiving this because you modified the open/close state.Message ID: @.***>

What should I do now?


Display commit status based on current branch

Current implementation only fetches /commits endpoint https://github.com/sindresorhus/refined-github/blob/master/source/features/add-ci-link.js#L13. The problem was that it only display main branch (usually master) commit status. When I change the branch, the commit status still points to master branch
We can improve this further (I think) by requesting specific commit by passing long commit hash

We can get the value via href attribute with .commit-tease-sha as selector
Is this something that useful to be added? Or people prefer main branch commit status more? I can help implementing this if this was useful

Go ahead!

I think this is happening natively in GitHub now :)
We can close this issue.


x/tools/gopls: doesn't handle replace directive

go version go1.15 windows/amd64
Version: 1.48.0 (user setup)
Commit: db40434f562994116e5b21c24015a2e40b2504e6
Date: 2020-08-13T07:50:42.600Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19041
Go extension 0.16.1
gopls version
golang.org/x/tools/gopls 0.4.4
<EMAIL_ADDRESS>h1:8djGYsaZ0ByP0vaXg4T+mnyfDcHpWKSZ+tpQSGv9ahk=

I have a project with sub-module. The main repo contains api folder, so the main go.mod contain replace directive like:
replace {repo-url}/api => ./api

And I can not understand several things how to make extension to work as expected:

If I do not fix the api version manually, the go-command makes it version v0.0.0-00010101000000-000000000000, after go mod tidy. But vscode-go despite of replace and "special" module version value, opens old api-version references (ctrl+click) from global pkg/mod/ folder. Restarting the language server does not help to force using local api-folder.

If I run go get -u in module context to update api to latest available version (v0.2.0-pre in my case) then the go.mod file is properly modified. BUT vscode-go continue to use old module version which is not required and is not exists in go.mod. Restarting the gopls, reloading vscode does not help - an older version of api-module is opened by ctrl+click on api-references.

What do I need to do to force extension work in this simple case? Who of them the vscode-go OR the gopls is ignoring the replace-directive?

Can you please provide the gopls logs when you encounter this issue? Instructions on how to capture the logs are here. We are still working out some issues with replace directives in gopls, but this case should work.

@stamblerre I can not post logs of my private project. But I have completed some investigation for this issue. Primary, I have a big workspace for over 10 repos. Some of them is not yet updated to the latest dependencies versions and gopls logs contains errors just the same as go mod tidy output if I run the command inside repos. But the repo from which this issue is appeared was updated. I can suppose gopls collects or caches results for another workspace-entry-points and does not work "from scratch" for every workspace dir or may it lost the context or stops to respond and then wakes up ... But I'm not able to explain why the next experiment was successfull. I created temporary workspace for a single repo. And vscode started to work fine. But... Now it always opens local module from replace-directive and doesn't react at changes of the module version in go.mod. I am confused because the gopls works more or less fine only for simple workspaces.

gopls currently requires that each workspace folder be in a single module. If you're opening a directory that contains multiple modules, you will see strange results like those you're describing. Instead, you can use the Add Folder to Workspace option in VS Code to add new folders that each are in a single module.

@heschik I know. In my case, I worked only on "main" module inside the multi-module repo. The code of sub-module was updated before by adding it folder as workspace root. After updating was done the sub-module root was removed from workspace.

OK. In that case I'm not sure what the problem is, and without logs it's going to be difficult to investigate any further. If you can put together a reproducer we'll be happy to take a look.

Closing as this is in the WaitingForInfo state and gopls/v0.5.0 will be released soon. Please open a new issue if you still have this issue with gopls/v0.5.0-pre3 (GO111MODULE=on go get<EMAIL_ADDRESS>