Verify Keenetic Manager on Flathub

The instructions can be found here:
https://docs.flathub.org/docs/for-app-authors/verification

Done. Soon should update in flathub page
Thx for the highlight


Refactor commands that expect HTTP 200 calls with undefined results

Some time ago I ran into a few planner commands that check if the API responses are undefined:
return request
      .get(requestOptions)
      .then((response: any) => {
        const etag: string | undefined = response<EMAIL_ADDRESS>: undefined;

        if (!etag) {
          return Promise.reject(`Error fetching task details`);
        }

        return Promise.resolve(etag);
      });

This is accompanied by a test in the testfile:
it('fails validation when task details endpoint fails', (done) => {
    sinonUtil.restore(request.get);

    sinon.stub(request, 'get').callsFake((opts) => {
      if (opts.url === `https://graph.microsoft.com/v1.0/planner/tasks/Z-RLQGfppU6H3663DBzfs5gAMD3o/details`) {
        return Promise.resolve(undefined);
      }

      return Promise.reject('Invalid request');
    });

   // etc
});

I wonder if there is some specific reason why this coded this way. If an endpoint fails, it probably does not return HTTP 200, and henceforth this checks and testcases are superfluous and can be removed.
The places where I noticed this are:

task add
task reference add
task reference remove
task set

and also in serviceannouncement health get.
I'd think we should refactor this, or it should be clearly stated in a comment that this behavior was observed.

@Jwaegebaert, @milanholemans: Do you by any chance have ideas about this? I think you worked on some of these commands.

I think you're right. Either the API call succeeds and you get an etag back. Or the task doesn't exist and the request util throws an error. I can't think of a way to get a HTTP success message without an etag value.
So I think this can be removed indeed.

this method is repeated in several places.

That's possible yes, but I think it's only a few places, as some other places require a specific extra property, using $select.

If it's not needed, let's clean it up. Good catch 👍


cel_matcher: matching on xds route metadata

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/assign @kyessenov


WIP: Add support for second zone

Work in progress - do not merge yet

Replaced by https://github.com/kongo09/hass-onkyo-ng/pull/6


Saving msoffice files failes

When saving a ms office 365 file (Word, Excel) the provided memfs crashes immediatly.
So far I could target the error in  in
winstuff.py
def evolve
The return value of lib.FspSetSecurityDescriptor is not checked there.
Changing the method to:
def evolve(self, security_information, modification_descriptor):
    psd = ffi.new("SECURITY_DESCRIPTOR**")
    if NTSTATUS.STATUS_SUCCESS == lib.FspSetSecurityDescriptor(
        self.handle, security_information, modification_descriptor, psd):
        handle = psd[0]
        size = lib.GetSecurityDescriptorLength(handle)
        return type(self)(handle, size)
    else:
        raise RuntimeError(
            f"Cannot create new security descriptor"
            f"{cook_ntstatus(lib.GetLastError())}"
        )

solves the problem, but I'm not quiet sure if this is enough so far.

Hi @robert-boulanger and thanks a lot for the report,
I'll investigate this issue and let you know what I find.

Sadly I haven't been able to reproduce your issue on my windows machine. However, the fix you suggest makes sense and I'll create a dedicated PR.
Do you have a log you could share with the RuntimeError you added? I'd like to see the stack strace for this issue.

This issue appeared on a Win10 Enterprise. Maybe Word behaves different on Prof or Home Editions.
It appeared when editing the word file and closing the application (without saving before)
Then a dialog pops up asking whether to save or not. There I pressed save.
winfspy_word_save_crash.txt

And here the log with the provided fix
(BTW: A Added a BEG line to the wrapper which gets printed before the function is executed)
winfspy_word_save_fixed.txt

Thanks for the logs, I have been able to reproduce the issue.
I'm working on a fix at the moment.

Fixed in PR #26, released in version 0.8.0
Thanks again!


feat!(static-analysis): refactoring semgrep action path

Description: This PR introduces the updated action path for Semgrep, moving from static-analysis/semgrep to static-analysis in preparation for the @v3 release.
BREAKING CHANGE:
The action path has been updated, requiring repositories to update their workflows:

From: open-turo/actions-security/static-analysis/semgrep@v2
To: open-turo/actions-security/static-analysis@v3

Renovate Bot will create pull requests for repositories referencing @v2 to help with the transition.

Cleanup:
This is no longer required. Closing the PR.


Only run integration tests when arrow changes

Which issue does this PR close?
re https://github.com/apache/arrow-rs/issues/2149
Rationale for this change
These actions test the integration of the arrow crate, yet they run on all PRs (including parquet changes and now also object_store changes) and they take significant time (32 minutes), often the longest test in the suite
What changes are included in this PR?

Only run this integration if files in arrow or .github change
Rename test to be more specific

Are there any user-facing changes?
no
Testing:

Positive (a change to .github, in this PR): https://github.com/apache/arrow-rs/runs/7483623018?check_suite_focus=true
Postive (a change to arrow): I need to merge this PR to test
Negative(a change to parquet): I need to merge this PR to test

cc @viirya  and @tustvold

Codecov Report

Merging #2152 (9235baf) into master (19a7189) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2152   +/-   ##
=======================================
  Coverage   82.86%   82.86%
=======================================
  Files         237      237
  Lines       61296    61296
=======================================
+ Hits        50792    50793    +1
+ Misses      10504    10503    -1

Impacted Files
Coverage Δ

...row/src/array/builder/string_dictionary_builder.rs
90.64% <0.00%> (-0.72%)
:arrow_down:

parquet_derive/src/parquet_field.rs
65.98% <0.00%> (+0.22%)
:arrow_up:

arrow/src/datatypes/datatype.rs
63.00% <0.00%> (+0.31%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us.


Fix path to boxes.rsi for foam dart ammo box

About the PR

Should fix #15168.
I used webedit and didn't test it, but in my defence it's one character and I can't make it worse.
This is my most sinful PR ever.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

no cl no fun

lmao


[Feat] Adding Contributer list in the Teams page

Description
I would like to add the contributer list in the teams section.
It shows how much work was doing while building this website hence increases its value.
Thank you.
Screenshots
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I'm a GSSoC'24-Extd contributor
[X] I'm a Hacktoberfest'24 contributor
[X] I am willing to work on this issue (optional)

Hello @Jay-1409, this is a very good feature, but according to our website, it will not look good. Try to find any other bugs or features, which I am happy to assign to you. Thank you!

Please don't forget to give our repository a star and let me know once you've done it.


Do not display email address in user display

Thanks to COVID-19, people often share screens with others.
This commit removes the screen display of email addresses on user display,
even to those authorized to see it. Instead, it just shows "Send email"
as the text. We continue to support a mailto: hyperlink.
No functionality is lost, this commit just reduces the risk of
unintentional disclosure via screen sharing.
Those who are authorized to see the email addresses can still
hover to see it, or click on the link to send an email, or
right-click to copy the email address.
We also still display the email address if a user is editing their
entry. But editing is a much rarer event, and we have to display
the email address then (so users can confirm it and/or edit it
to the correct value).
Signed-off-by: David A. Wheeler<EMAIL_ADDRESS>

This provides a modest increase in privacy with no real downside, and there have been no objections, so I'm merging t.


Feature/create agnostic services

The main idea of this PR is to start taking out logics from React to agnostic services that could be used regarding of the framework in use.
In this PR I have created three services:

crossmintModalService. This replaces the existing hook useCrossmintModal.
crossmintPayButtonService. This would take care of all the logics that happen on the CrossmintPayButton view.
crossmintStatusService. It would take care of the logics regarding fetching the status and handling the button status view.

This was actually pretty straight forward since our components are not really too heavy on reactivity, so it is fairly easy to take the logics out.
I would like to get an initial feedback on this approach, and if I get the green light Ill move all the logics into common services and start creating Vue, Angular and Svelte wrappers this weekend.

Thank you!

Tests are failing because now its depending on the base package... Will see how to fix later

I don't think that the hooks should go inside the base package?
If u checkout the example this repo is based on, they have separate folders for react, and base is a general package containing only non-framework specific types and functions.

There are no hooks inside the base package.
Maybe I should change the way the services are used. Instead of:
const { connect } = useCrossmintModalService();
Im changing it for:
crossmintModalService.connect();
So its clear that there is no reactivity in the base logics, just pure typescript.

There are no hooks inside the base package.
Maybe I should change the way the services are used. Instead of:
const { connect } = useCrossmintModalService();
Im changing it for:
const { connect } = crossmintModalService();
So its clear that there is no reactivity in the base logics, just pure typescript. Reactivity should be handled at the component level.
Im using functions to encapsulate information instead of classes (as in the example you provided). Do classes make more sense to you?
@mPaella

Functions are good. Only other thing I can see is possibly the useCrossmintStatus hook should go inside the base package as well? wdyt?

cc @angel-paella
@mPaella could you please test locally to ensure that everything is working correctly.
For the tests to work, we would need to publish the new base package. Locally, they work.
Thanks!

LGTM. We should also add the tsup build to the base package, then deploy both.


[FR] Table

Great work. Really like it. 👍
Would it be possible to integrate a flexible table solution like http://tabulator.info/?

Thanks for the feedback! Yes, I need to add a decent table. You can also do it using the custom widget. I need to look into how to do it in a component-friendly manner so one can define the cells as components or something like that. Trying to get away from injecting raw HTML everywhere...

NB: I'd appreciate if you could use the forum for non-issues, thanks!


Bug: Auto Generate does not work properly.

I have the feeling that the oauth client credentials cache does not renew expired keys.
I have the problem almost every month that I get the response Invalid OAuth token from the Twitch API.
Unfortunately I could not look at it. Workaround was: Change cache key.

After some research I came across the following:

The API limits the number of active access tokens associated with a given refresh token. The limit is 50 token per client/user (that is, a user can only have 50 tokens live at a time per client ID).

Maybe my app generated too many tokens and after some time Twitch invalidated the cached token. So the token is probably invalid in the cache and will not be deleted for further requests. All subsequent requests will be rejected with an 'Invalid OAuth token'.
Source: https://dev.twitch.tv/docs/authentication#:~:text=The API limits the number,a time per client ID).

I also encountered this issue. In response, I've added some changes to clear the cached API client credentials if the API response indicates that the given OAuth token is invalid

Fied in v4.0.0

Fied in v4.0.0


Wrong video record orientation.

Whenever I record and upload a video, my record has different orientation (upside down)
I checked the local file under file system and saw that the orientation is wrong. Here is the screenshot.

@3akat Anything new?

Hi @objectorientedperson,
Unfortunately was unable to reproduce on any of my devices, will try to fix blindly.

@objectorientedperson can you please try version a420c47417?

@3akat Just wanted to let you know that I had checked all of our channels and no one else was reporting such issues. LG is one of the common marks of devices that tests are done on as well so it is possible that there was something specific happening.
I suggest closing it by the end of the week as solved. @objectorientedperson please let us know before in case you are still experiencing any similar experience as your original report.

Hi, @Bane-D I was about to create an issue and I found this. I'm facing this exact same issue. And the thing is that I can reproduce it constantly without a hitch.
Can we reopen it to discuss more?

@sagrawal31 done! Please add more info if you have something :)

Like we have been discussing over the email 😄we have written a Cordova plugin https://github.com/wizpanda/cordova-plugin-ziggeo and is stabilizing it.
In the start, I was thinking that this issue of wrong orientation (180 degrees rotated) is because of some misconfiguration in the Cordova plugin code. But later I figured out that, it is only happening when we are explicitly setting the facing to front camera through the following code:
builder.facing(CameraView.FACING_FRONT);

When this flag is not set (i.e. back camera is being used), this issue is not happening. (I have not tried by manually switch the camera).

This can be easily reproduced by setting the line builder.facing(CameraView.FACING_FRONT) in this demo app only.

https://stackoverflow.com/questions/29609838/nullpointerexception-from-mediaplayer-onpause-looses-reference this helps?

will check everything, thanks!

Any solution/workaround for this to fix?

Sorry to rush because our app is recording only with the front camera only as it is an assessment test app.

Please take a look at 0.82.4

That's so fast 😄 This issue is actually fixed now. Thank you for the quick resolution. Please close this issue again.
By the way, what was the problem? Why using front camera was recording in reverse orientation?

Great to hear that!
The problem is that camera orientation value is different from screen orientation. For example if screen orientation is 0 recorder should be configured with 90. And the case was that for the from camera it should be 270 instead of 90.
In short - wrong calculation.

Thank you for the explanation @3akat


Create FUNDING.yml

github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]

Please help us further enhance the collaboration on this project,


Cloudflare & up to date IP ranges

Description: If you are behind Cloudflare service, you may have already applied a solution in order to get visitor's real IP.
However, these IP ranges can be changed at anytime, in case CF decides so (blacklisting purposes etc).
Workaround: Instead of creating a static config file that is included in nginx's config, I suggest the following way, which will be updating itself based on a cronjob.
Commands:
cd /root/
wget https://gist.github.com/irazasyed/fc73419d0d92f607c495/raw/2d2495c69eef44eaad50a9fa6ff821e6ae007d74/cf-ip-ranges-updater.sh
chmod +x cf-ip-ranges-updater.sh
./cf-ip-ranges-updater.sh

Finally, include your new config file in server block of nginx:
include /etc/nginx/cloudflare-ips.conf;
And add a cronjob so cf-ipranges-updater.sh will be executed regularly:
50 0 * * * /root/cf-ip-ranges-updater.sh

Isn't it easier to create  a cloudflare.conf file in /etc/nginx/conf.d/ to not have to include it manually in nginx configuration.
There is also a similar script for ufw : https://github.com/Paul-Reed/cloudflare-ufw/
Because with fail2ban, or a rate limiter on nginx, it happen to ban some cloudflare IPs

Closing this as it's a duplicate of https://github.com/EasyEngine/easyengine/issues/646


libc: Implement ftw and nftw function

Summary
see the reference here:
https://pubs.opengroup.org/onlinepubs/009695399/basedefs/ftw.h.html
Impact
New function
Testing

@yamt and @patacongo since my team membrer also need ftw/nftw function, I provide an implementation, please review it.

@yamt and @patacongo all issue is addressed, please take a look.

@yamt, please merge this patch if you don't have more concern.


Exploration into Anserini + NN integration via ONNX

Soon we'll have a demo of running a NN on the JVM via ONNX:
https://github.com/castorini/ONNX-demo/
Let's do some exploration of Anserini+NN integration to see how the pieces might begin to fit together? A simple demo might be to do a search, and classify sentences from the retrieved documents into positive and negative.

You may want to consider using the JavaCPP Preset for ONNX

Today's FB Horizon announcement features ONNX prominently: https://code.fb.com/ml-applications/horizon/

@lintool For the integration, would we want to use the JavaCCP Preset mentioned about or use Scala code (following Heli's example) and call that from Java?

No idea... try both and compare and contrast?

Some more detail to aid in your decision-making:
The JavaCPP Preset for ONNX contains everything that you get from an implementation generated from ONNX Protobuf definitions, including the ability to load a model. You also get the ability to "polish" and convert the version of a model (in this now merged PR ) as well as access to the operator schemas, the ONNX IR, ONNX-ML (Classical Machine Learning extension), ONNXIFI and more.
The JavaCPP Preset offers an API that is as close as possible to the ONNX C++ API in Java. This means it does not include a backend capable of actually running inference on the model.
In contrast, my project ONNX-Scala (which uses the JavaCPP Preset under the hood) aims to provide a typeful, idiomatic and purely functional Scala API to ONNX. ONNX-Scala makes full use of (sometimes bleeding-edge) language features where appropriate, while targeting 2 current and 2 in-development versions of Scala for the JVM, as well as Scala Native and Scala.js.
ONNX-Scala provides a clean separation between API, program definition, and backend implementation.
Currently there is no backend available for ONNX-Scala either, but the plan is to have several backend implementations available. The first cut of the first one should be ready in the near future.
Lantern is the top candidate right now, although I have partially-baked MXNet backend that could be revived as well.
I am also working on a JavaCPP Preset for ngraph , which should provide us with an ONNX backend in Java (also a candidate for a backend in ONNX-Scala).
Phew; hope it helps.

@EmergentOrder cool, thanks for the detailed rundown!

@EmergentOrder Thanks for the info!

Hey @EmergentOrder I recently checked out your LinkedIn profile - it says you're a freelance developer... if you're interested in doing some work for us, let's chat. If interested, ping me directly on email?

No plans in the near future to work on this, closing for now.


Documentation unclear

The documentation is uncler for me: What does this function do?:

isvalid.validate.query(schema)

Validates the req.query of your express or connect application - aka. the query string.
I agree the documentation should clarify.


Fix Broken links

links to eosio documentation are broken
https://guide.eoscostarica.io/docs/eos-learn/accounts-and-permissions/

The link used in https://github.com/eoscostarica/guide.eoscostarica.io/pull/376 is not the latest, please use the latest link.
Change https://developers.eos.io/manuals/eosjs/v21.0/how-to-guides/how-to-create-an-account to https://developers.eos.io/manuals/eosjs/latest/how-to-guides/how-to-create-an-account


Run the vagrant provisioning script as unprivileged user

In it's current state on the develop branch, the vagrant script is run as root. That means everything that is downloaded in the script will be owned by root.
It seems okay now, but when I was trying it out a while back, I was having trouble with something (linking or something?) because it had to be run by root to have access, whereas I was logged in as the vagrant user.
It seems like it would be nicer if everything was installed as an unprivileged user.

Fixed in PR #173


Class 'App\Providers\GenericAdapter' not found

Hi there,
I follow the documentation and I use the package version 1.0.0-alpha.3
but when I make a api request this error

{
    "message": "Class 'App\\Providers\\GenericAdapter' not found",
    "status_code": 500
}

also I want to ask if the package is ready to use in a production app?

Hi. That's just an example in the documentation, the generic adapter doesn't actually exist. You can read all about adapters here:
http://laravel-json-api.readthedocs.io/en/latest/basics/adapters/
We're using this package in three production apps.


merge package from arlac77/npm-package-template

package.json

chore(devDependencies): update documentation:^6.3.3 from template
chore(devDependencies): add rollup-plugin-commonjs:^9.1.3 from template
chore(devDependencies): add rollup-plugin-node-resolve:^3.3.0 from template
chore(devDependencies): add rollup-plugin-babel:^3.0.4 from template
chore(devDependencies): add rollup-plugin-json:^3.0.0 from template
chore(devDependencies): add rollup-plugin-executable:^1.2.0 from template
chore(devDependencies): add babel-preset-env:^1.6.1 from template
docs(package): remove keyword null

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


General Discussion

How do you think, what schema this GraphQL Sandbox should have? Containing data model for a todo app similar to Wunderlist (user, todo list, todo item etc.), or an event planning app (events, attendees, speakers, etc.), something else? Ideally, it should contain all the GraphQL built-in types: Scalars (Int, Float, String, Boolean, ID), Objects, Interfaces, Unions, Enums, Input Objects, Lists and Non-Null.

Don't think this should be tied to a single schema. A Blog example or a TodoMVC implementation are quite simple and well known, so allow developers to learn/compare on familiar examples.
A more complex example would also be useful to showcase all features of each implementation.

Hi guys,
I thought it would be useful to have a checklist of things that we ideally should cover for the schema that we eventually decide to go with.
Let me know what you guys think!
Cheers!

Schema checklist
Schema

[ ] Query
[ ] Mutation
[ ] Subscription

Definitions

[ ] GraphQLScalarType
[ ] GraphQLObjectType
[ ] GraphQLInterfaceType
[ ] GraphQLUnionType
[ ] GraphQLEnumType
[ ] GraphQLInputObjectType
[ ] GraphQLList
[ ] GraphQLNonNull

Scalars

[ ] GraphQLInt
[ ] GraphQLFloat
[ ] GraphQLString
[ ] GraphQLBoolean
[ ] GraphQLID

Misc (Some of these may overlap with the above, but I thought it would be good to be explicit)

[ ] Object implementing one or more Interfaces
[ ] Union of one or more Objects
[ ] Enum
[ ] Input Object type
[ ] Custom scalar
[ ] Input with one argument
[ ] Input with default value
[ ] Input with multiple arguments
[ ] Input with multiple arguments & multiple default values
[ ] Self-referential Object (e.g. type User has a field friends that returns a list of User type)

Type Markers (optional? not sure how practical it is)

[ ] Nullable type (default)
[ ] Non-null type: String!
[ ] List type: [String]
[ ] List of non-null types: [String!]
[ ] Non-null list type: [String]!
[ ] Non-null list of non-null types: [String!]!

Reference
http://graphql.org/docs/api-reference-type-system/


Failed to install devchat on Win11

Describe the bug
Failed to install devchat on Win11

cmd_2023-07-08_14.10.13_1_pip_errors.log
fail.log
157.0ms (setup:799): 2023-07-08 16:43:27
157.0ms (setup:800): C:\Users\zhaoqiong\AppData\Roaming\Python\Python310\site-packages\pipx_main_.py environment
157.0ms (setup:801): pipx version is 1.2.0
157.0ms (setup:802): Default python interpreter is 'D:\soft\python\python.exe'
157.0ms (cli:874): pipx finished.
To Reproduce
Steps to reproduce the behavior:

sign in https://www.devchat.ai/  and click "this link"
Click on "Install" ,
Install by default according to prompts

Expected behavior
Successfully installed and can be used normally
Desktop (please complete the following information):

OS: [windows11]
Browser [chrome]
Version [v0.1.14]

Additional context
Add any other context about the problem here.

It seems the problem is pipx is using a different python interpreter (which is C:\Users\zhaoqiong.local\pipx\venvs\devchat\Scripts\python.exe) than what is used by your cmd.
Could you rerun python -m pipx ensurepath in myenv and then try pipx install devchat again?
BTW, why do you issue those commands instead of letting DevChat run the automatic installation process? Does it work? If not, maybe consider uninstalling DevChat and reinstalling it. Our script should be able to handle most issues.

Pipx will use an internal Python interpreter, which is C: Users [...] . Local pipx venvs devchat Scripts Python. exe. All modules installed by pipx will be bound to this interpreter. But when you install pipx and then install devchat through pipx, it will install a Python interpreter with pip module.
In the error log, it is displayed that the pip module does not exist, so some errors occurred during the pipx installation process or devchat installation, and the pip module was not downloaded correctly.
It is recommended to uninstall pipx first, and then manually execute the following command:
Python - m pipx uninstall devchat
Python - m pip install -- user pipx
Python - m pipx securepath
Python - m pipx install devchat -- force


how make custom page for Route::resource

Hi,
how make custom page for Route::resource if record not found?
Laravel 6.1

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

yes .. but not fixed problem


too many volumes returned

I'm using the Virtualbox storage driver, when I run multiple machines, it creates multiple virtualbox disks. It looks like RexRay picks up any virtualbox disk. If I inspect the 'packer-ubuntu-14.04-disk1.vmdk' volume through Docker I get this error: VolumeDriver.Get: {"Error":"too many volumes returned"}. Which is because there are two volumes with the same name.
> docker volume ls

local               32a94cff881e8545d4c1a60d659b4b785dce6afcc5cc30058b57e211c36c7809
rexray              packer-ubuntu-14.04-disk1.vmdk
rexray              packer-ubuntu-14.04-disk1.vmdk

> rexray volume

- name: packer-ubuntu-14.04-disk1.vmdk
  volumeid: 3bbdd001-211f-4800-a82e-73173ee95607
  availabilityzone: ""
  status: /Users/raymond/VirtualBox VMs/vagrant_master-0_1459937297096_17980/packer-ubuntu-14.04-disk1.vmdk
  volumetype: ""
  iops: 0
  size: "39"
  networkname: ""
  attachments:
  - volumeid: 3bbdd001-211f-4800-a82e-73173ee95607
    instanceid: c68a2419-62c0-4c29-b124-2d3c62a6705b
    devicename: /dev/sda3
    status: /Users/raymond/VirtualBox VMs/vagrant_master-0_1459937297096_17980/packer-ubuntu-14.04-disk1.vmdk
- name: packer-ubuntu-14.04-disk1.vmdk
  volumeid: 85564279-8145-4450-9db1-2a1e0bfa0015
  availabilityzone: ""
  status: /Users/raymond/VirtualBox VMs/vagrant_node-0_1459941887608_83510/packer-ubuntu-14.04-disk1.vmdk
  volumetype: ""
  iops: 0
  size: "39"
  networkname: ""
  attachments:
  - volumeid: 85564279-8145-4450-9db1-2a1e0bfa0015
    instanceid: eb671b09-aa38-4824-bf93-d94693a6a471
    devicename: ""
    status: /Users/raymond/VirtualBox VMs/vagrant_node-0_1459941887608_83510/packer-ubuntu-14.04-disk1.vmdk

Is it possible for rexray to ignore these volumes?

Hi @adaptivdesign,
For a workaround, can you create the disks manually to avoid the duplication of names? Using the VirtualBox storage manager this should be possible.
In the meantime I am working on a patch...

Hi @adaptivdesign,
Here's a binary I built for Darwin (OS X) with the patch described in PR #352. To use the patched binary, please edit your REX-Ray config.yml and create a root config key named docker: if it does not exist, and then add the following child key so that the end-result looks like this (the example does not take into account existing keys you may have):
docker:
  useFirstVolume: true

@adaptivdesign I am not sure if I'm a fan of solving for this problem. Since there is no way to determine which volume to which the query refers (if multiple with same name), it doesn't seem to make sense that we would enable any type of operation in this case.
To me the real solve has to do with ensuring a globally unique identifier accommodates volumes in Docker.
Can you describe more about what you're trying to achieve with accessing the specific OS volume? An alternative would also be to manipulate the name of the volume through the vbox cli.

@clintonskitson no no I completely agree with you. I don't expect anything else then the current behaviour. If 2 or more volumes exist and I want to inspect one, I totally understand an error occurs. The problem is, that I'm using the Docker API and it simply lists all volumes, which in turn will be inspected by my code.
Mayby the problem isn't clear I did not add these 2 volumes. On a fresh install in a virtualbox vm, when I list the docker volumes, or by calling rexray volumes, I already see these 2 volumes (depending on the amount of machines I'm running they will increase). To me it looks like they are picked up by the rexray driver automatically.

So I get what is happening, but I am unsure as to why you would want to use
the base OS virtual disks with rexray. As far as listing the volumes is it
causing a problem seeing the volumes in the list of all volumes?
A filter could possibly be introduced in the VirtualBox driver but it
doesn't seem necessary unless it is causing functionality problems.
On Wednesday, April 6, 2016, Raymond Reggers<EMAIL_ADDRESS>wrote:

I'm using the Virtualbox storage driver, when I run multiple machines, it
creates multiple virtualbox disks. It looks like RexRay picks up any
virtualbox disk. If I inspect the 'packer-ubuntu-14.04-disk1.vmdk' volume
through Docker I get this error: VolumeDriver.Get: {"Error":"too many
volumes returned"}. Which is because there are two volumes with the same
name.
'''
docker volume ls
local 32a94cff881e8545d4c1a60d659b4b785dce6afcc5cc30058b57e211c36c7809
rexray packer-ubuntu-14.04-disk1.vmdk
rexray packer-ubuntu-14.04-disk1.vmdk
'''
'''
rexray volume

name: packer-ubuntu-14.04-disk1.vmdk volumeid:
3bbdd001-211f-4800-a82e-73173ee95607 availabilityzone: "" status:
/Users/raymond/VirtualBox
VMs/vagrant_master-0_1459937297096_17980/packer-ubuntu-14.04-disk1.vmdk
volumetype: "" iops: 0 size: "39" networkname: "" attachments:

volumeid: 3bbdd001-211f-4800-a82e-73173ee95607 instanceid:
c68a2419-62c0-4c29-b124-2d3c62a6705b devicename: /dev/sda3 status:
/Users/raymond/VirtualBox
VMs/vagrant_master-0_1459937297096_17980/packer-ubuntu-14.04-disk1.vmdk

name: packer-ubuntu-14.04-disk1.vmdk volumeid:
85564279-8145-4450-9db1-2a1e0bfa0015 availabilityzone: "" status:
/Users/raymond/VirtualBox
VMs/vagrant_node-0_1459941887608_83510/packer-ubuntu-14.04-disk1.vmdk
volumetype: "" iops: 0 size: "39" networkname: "" attachments:

volumeid: 85564279-8145-4450-9db1-2a1e0bfa0015 instanceid:
eb671b09-aa38-4824-bf93-d94693a6a471 devicename: "" status:
/Users/raymond/VirtualBox
VMs/vagrant_node-0_1459941887608_83510/packer-ubuntu-14.04-disk1.vmdk '''

Is it possible for rexray to ignore these volumes?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/emccode/rexray/issues/351

Hi Guys,
To be clear, you can totally control the disks virtual box creates. You may have to create them manually or rename them, but even though you didn't name them, you can control the situation pre or post.
Regarding the "fix", I agree it's not ideal. I was simply trying to create a workaround for @adaptivdesign in order for him to continue testing REX-Ray. But you're absolutely correct @clintonskitson, volume names should be unique as far as Docker is concerned.
However.
(you knew it was coming)
Volume names do NOT have to be unique as far as many storage platforms are concerned (virtual box included). In fact, Virtualbox uses UUIDs as its disk (or volume to us) ID.
Would there be an issue with us simply returning the volume ID to docker instead of the name? Sure, the user would have to keep track of that and it's more difficult to do for them, but that may be required for driver-specific cases such as Virtualbox where the volume name is not unique.

Me neither, I don't want to use the base os virtual disks. It's just that they are already there listed as a volume (I didn't add them as a docker volume). This causes problems

Thank you @akutz. No no I will definitely keep using RexRay, i prefer it very much above Flocker or anything else. To me this seems like a problem with the Virtualbox Driver and the vboxwebsrv.

Hi @clintonskitson,
Would a possible fix for this be to include a virtualbox driver option that allows you to toggle between the Disk name and ID as the value returned to Docker as the "name".

The issue of having everything that a storage platforms has be advertised
to docker is something we are addressing separately. We believe that
optionally you should be able to decide which volumes get advertised to
which container run times or clusters.
@akutz Knew you would get there =) The problem is that docker only returns
name through the API today, and yes we could manipulate the field and use
it in whatever way we want.
But if someone creates a volume via docker then you would assume the name
returned from ls would be there volume name and not the ID.
IMO for Docker, a uniqueness param as part of the API is needed to really
properly address the notion of multiple volumes w same name.
On Thursday, April 7, 2016, Raymond Reggers<EMAIL_ADDRESS>wrote:

Me neither, I don't want to use the base os virtual disks. It's just that
they are already there listed as a volume (I didn't add them as a docker
volume). This causes problems
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/emccode/rexray/issues/351#issuecomment-207064809

I have an idea. So the virtualbox driver works by creating a virtual disk. Why don't we make the driver ALWAYS prefix disks it creates with something like libstorage- so that when it comes time to list available disks we know which ones are there specifically for purposes of REX-Ray and libStorage? We can simply remove the prefix before sending it back to Docker and always add the prefix when Docker wants to inspect a disk.

I am assuming you are referring to the Dublin branch where we implemented
this at a higher level. Yeah it would be useful for rexray to be able to
configure a prefix as part of the module config that specifies which
prefixes are valid to return and create with.
On Thursday, April 7, 2016, Schley Andrew Kutz<EMAIL_ADDRESS>wrote:

I have an idea. So the virtualbox driver works by creating a virtual disk.
Why don't we make the driver ALWAYS prefix disks it creates with something
like libstorage- so that when it comes time to list available disks we
know which ones are there specifically for purposes of REX-Ray and
libStorage? We can simply remove the prefix before sending it back to
Docker and always add the prefix when Docker wants to inspect a disk.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/emccode/rexray/issues/351#issuecomment-207066634

Hi @clintonskitson,
I could have meant that, but in this case I simply meant specifically for this driver.

Don't want to interrupt you guys, but it seems my case seems to behave different than intended. I ran https://github.com/jonasrosland/vagrant-rexray . If i run "rexray volume" it outputs all vbox disks on my host machine, if I run "docker volume ls" it shows no single rexray volume (expected behaviour).
I will try to narrow down the problem. If it persists, I'll make a vagrant box to replicate the issue. Ok?

@adaptivdesign What you are seeing is likely due to the Docker version. In Docker 1.10, the docker volume ls functionality was changed to display all volumes from the storage platform. Previous to that Docker would only return volumes that Docker had previously made contact with. This was done because the source of truth for volumes was taking place in two separate locations and changes to the storage platform would cause Docker to malfunction when trying to use the same volume name again.

@akutz It could be driver level implementation but then if something at a global level was implemented, it might conflict or be confusing when individual drivers were also mutating the volume names.
I believe the only volume name manipulation in the drivers today is in ScaleIO where we shrink to 31 chars.

@clintonskitson Thank you a lot, that clears everything up!


vSphere Cloud Provider code refactoring - Datacenter

This PR tracks the work for vSphere Cloud Provider code refactoring for Datacenter object. Datacenter object includes all the functions required for the management of datacenter objects like VM, Datastore, Folder etc. Some functions are listed below:

GetDatacenter
GetVMByUUID
GetVMByPath
GetDatastoreByPath
GetDatastoreByName
GetFolderByPath
GetVMMoList
GetDatastoreMoList

It also includes functional testing for this datacenter object.

This PR is out for review on 06/09 and merged by 06/12. PR - https://github.com/vmware/kubernetes/pull/154.
This PR is fully tested and successfully merged.

This PR is a part of main PR - https://github.com/vmware/kubernetes/issues/134


Redirect in middleware when locale is missing from url

Describe the bug
Hi, not a real bug report, but more of a question if I'm misunderstanding a feature or I've found a bug. In my understanding, if I configure localeSubpaths: 'all' the locale should always be present in the URL. I visit for https://www.google.be/hello it should make sure this is rewritten to https://www.google.be/en/hello. This currently kinda works but seems to be handled on the client side and not on the server in the middleware.
Occurs in next-i18next version
0.45.0
Expected behaviour
I would expect the middleware to detect that the current request url is missing the locale and redirect the entire request via a 302 redirect.
I've tracked the issue down to the lng-path-detector.js file which seems to be not setting the correct config.correctedUrl.
I think the issue is in this section: https://github.com/keustma/next-i18next/blob/master/src/utils/lng-path-detector.js#L35
The if statement is entered, the allLanguages.forEach does not set the correct url. Before leaving the if statement, I added a part to the if-statement which seems to fix the issue.
if (!languageChanged && languageNeedsSubpath && !req.url.startsWith("/".concat(language, "/"))) {
      allLanguages.forEach(function (lng) {
        if (req.url.startsWith("/".concat(lng, "/"))) {
          config.correctedUrl = req.url.replace("/".concat(lng, "/"), '/');
          languageChanged = true;
        }
      });

      if(!languageChanged) {
        config.correctedUrl = '/' + language + req.url;
      }
}

Yes, that's correct. The middleware should redirect with a 302 via this util. If you've found a situation where that does not happen, please provide a reproducible example. Thanks!
cc @capellini

Hi,
a minimal reproduction case can be found here https://github.com/keustma/next-i18next-redirect-repro, when running npm run dev I expect a GET to http://localhost:3000 to receive a status 302 FOUND status and a redirect to http://localhost:3000/en/. But this is not happening.

Your linked repository doesn't have an _app.tsx.

I added the _app.tsx file.

Yes, and it's redirecting to /en/.

Ah, got it. Yes, also disabling JavaScript will reproduce this bug.

After taking a deeper look, the lng-path-detector util appears to be poorly written and bug-prone.

@keustma This should be fixed by #404. Can you review and/or test?

@isaachinman Please let me know how I may assist.

Hey @capellini - as this is a bug, it would be great to have test coverage to prevent regressions. Might make sense to have an e2e test covering this and do network interception via Puppeteer.

it would be great to have test coverage to prevent regressions. Might make sense to have an e2e test covering this and do network interception via Puppeteer.

:+1: I'll see if i can come up with some tests to prevent regressions.


Grammar: 'using () {}' vs 'try () {}'

Although there is a separate syntax discussion ongoing in #11, I'd like to have a separate discussion on the merits of aligning somewhat with Java's try-with-resources syntax:
// declaration head
try (const a = …) {
}

// expression head
try (expr) {
}

Note that Java also allows you to couple try-with-resources with additional optional catch and finally clauses:
try (const a = …) {
}
catch (ex) {
  // 'a' is already disposed and out of scope
}
finally {
  // 'a' is already disposed and out of scope
}

Which would be semantically equivalent to:
try {
  try (const a = …) {
  }
}
catch (ex) {
  // 'a' is already disposed and out of scope
}
finally {
  // 'a' is already disposed and out of scope
}

The choice here is similar to the match vs case decision for pattern matching. I think we should decide in general whether we are OK with adding this type of contextual keyword going forward, which involves more complex cover grammars similar to those added for async arrow functions. Cc @bakkot @waldemarhorwat

Aside any grammar issues, I believe that adding new reserved keywords to a language should be done carefully.
For example, while adding async/await makes sense, since it's a change of paradigm, this proposal is only a glorified syntactic sugar. While I believe it has its value, I don't find it worthy of a new token in the language.
Also, this may not be a strong argument, but given Brendan Eich clear inspiration on Java for creating Javascript, sticking with the known try-with-resources Java pattern is better than introducing using.

Switched to try in #26.


Add Non-Capacity Var Nodes to Dispatch or Case

Pull Request Description
What issue does this change request address?
Closes #62
What are the significant changes in functionality due to this change request?
Add optional dispatch_var node to either the Component node or a more generalized dispatch_var in Case node.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass.
[ ] 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large tes.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added, the the analytic documentation must be updated/added.
[ ] 9. If any test used as a basis for documentation examples have been changed, the associated documentation must be reviewed and assured the text matches the example.

Closing because #138 is the actual PR for this change.


Integration with Subscriptions package not working

The integration with the subscription package does not seem to be working. A payment is created but the redirect to make the payment never takes place. I am using Laravel 11. Please help, I am stuck now.

hi @ejjaquet can you share the Provider you add for the support subscription?


Starter template doesn't start in iOS

I tried the tailwind template and launched yarn native and then opened the simulator with i.
I get this error:
CommandError: No development build (com.solito.nativewind) for this project is installed. Please make and install a development build on the device first.
Learn more: https://docs.expo.dev/development/build/

yarn native is no longer the right command; try yarn ios (yarn expo run:ios)

yarn native  should work, you just need to create a dev client first. or you can remove —dev-client from the native command to use expo go, but i recommend the dev client instead by running yarn ios first

I figured I had to go into cd apps/expo to be ablel to run yarn ios. I was using the yarn native command in the root folder.

Yeah I should make this more clear now that SDK 49 is in the starters. I'm thinking we remove --dev-client from the yarn native script in the root.

Try to change root package.json to
  "scripts": {
    "android": "cd apps/expo && npx expo run:android",
    "ios": "cd apps/expo && npx expo run:ios",
    "web": "cd apps/next && yarn next"
  },

and use Simpulator with iOS 17. It works for me.

Hey guys, I pushed a fix for the newest starters. They now use Expo Go by default. Expo is very confusing with this workflow tbh, I wish it were more clear.
Option 1: If you're on an existing starter, just remove --dev-client from the start script in apps/expo. This lets you use Expo Go. Unlikely workflow to stick with.
Option 2: If you want to use a dev client (recommended), first run expo run:ios or expo run:android in apps/expo, and then run yarn native.


Integer node names break parsing of the node

When we have a node with just an integer node name, this breaks node parsing. I am not sure whether this is strictly in the spec of devicetree, but Zephyr seems to build fine with it so it might be nice to support it.
Here is an example ZMK build: https://github.com/rael-dev/zmk-config-corne/actions/runs/12188804747/job/34002649093#step:13:1472

Hmm. That might conflict with the integer token. I'll have to check whether the parser/tokenizer is able to know which tokens are possible in each context and select the correct thing. Alternatively, I might be able to make the node name node allow either a node name token or an integer token.


Possible to skip unloadable resource?

Some webpages show well in browser, but uncapturable with screenshot-stream. I saw same errors on both that some resources cannot be loaded.
Wondering if there is way to make screenshot-stream as tough as browser.

We're switching to Headless Chrome https://github.com/kevva/screenshot-stream/pull/46.

Thanks.


[Rust] Fixes issue with CPP enums

Fixes issue reported by user here.
Bindgen generates differing types on windows vs other platforms for CPP enums.

cc @nhynes.


remove-bqtable cmdlet & tests

Remove-BqTable cmdlet + integration tests.
(also changed over a few Gcbq*'s to Bq*'s that I missed in the previous commit)

PTAL.  All changes should have been addressed.

Refactored that method and addressed the other changes.  It looks much cleaner now.


Cannot import Textractor, No module named 'txtai.pipeline'

I get an error
"ModuleNotFoundError: No module named 'txtai.pipeline'"
when importing from txtai.pipeline import Textractor from this example
https://colab.research.google.com/github/neuml/txtai/blob/master/examples/10_Extract_text_from_documents.ipynb

Can you get the latest copy of the notebook and try again? There was a NLTK issue today that likely caused this.
https://github.com/neuml/txtai/issues/760

hi there david, really love this extractor and it worked perfectly yesterday.
today it seems there is an issue with this  "import ImportError: Textractor pipeline is not available "
error message: ------------------------------------------------------------------------------------------
/usr/local/lib/python3.10/dist-packages/txtai/pipeline/data/textractor.py in init(self, sentences, lines, paragraphs, minlength, join, tika, sections, headers)
30
31     def init(self, sentences=False, lines=False, paragraphs=False, minlength=None, join=False, tika=True, sections=False, headers=None):
---> 32         if not TIKA:
33             raise ImportError('Textractor pipeline is not available - install "pipeline" extra to enable')
34
ImportError: Textractor pipeline is not available - install "pipeline" extra to enable

hi there, given your suggestion, i applied a previous version of nltk and it worked
!pip install nltk==3.8.0
import nltk
nltk.download('punkt')

Glad to hear it!


Mock values unable to be parsed by dbt

When parsing the cosmos DAG in CI/CD, I am running into issues with dbt.
Runtime Error
  Credentials in profile "default", target "prod" invalid: 'mock_value' is not valid under any of the given schemas

I am using the following profile mapping.
GoogleCloudServiceAccountDictProfileMapping
The mock profile it creates:
 default:
    outputs:
        prod:
            dataset: mock_value
            keyfile_json: mock_value
            method: service-account-json
            project: project
            threads: 1
            type: bigquery
    target: prod

The key keyfile_json: mock_value in the above yaml is not accepted by DBT
For the mock we can simply remove the field.
Reproduce
Take above mock profile and put it in a profiles.yml
run dbt ls
or
from pathlib import Path

from cosmos import DbtDag, ProfileConfig, ProjectConfig
from cosmos.profiles import GoogleCloudServiceAccountDictProfileMapping
from pendulum import datetime

CURRENT_DIR = Path(__file__).resolve().parent

profile_config = ProfileConfig(
    profile_name="profile",
    target_name="target",
    profile_mapping=GoogleCloudServiceAccountDictProfileMapping(
        conn_id="conn", profile_args={}
    ),
)
my_cosmos_dag = DbtDag(
    dag_id="dag",
    start_date=datetime(2023, 1, 1),
    schedule_interval="@daily",
    project_config=ProjectConfig(
        dbt_project_path=CURRENT_DIR,
    ),
    profile_config=profile_config,
    catchup=False,
)

Running with dbt=1.5.6
Comos 1.1.2

@joppevos This was released as part of 1.2:

https://pypi.org/project/astronomer-cosmos/1.2.0/
https://github.com/astronomer/astronomer-cosmos/releases/tag/astronomer-cosmos-v1.2.0


operator can't pull from private gitlab registry

Bug Report
What did you do?
I"m trying to get OLM/Openshift to work with a private gitlab registry for pulling operator images.  For this, I created
a ServiceAccount, and patched it with a docker registry pull secret that works with the gitlab instance. Then I proceed
to install the operator using OLM functionality.
What did you expect to see?
I expected that a ServiceAccount that is created manually would be honored by OLM during the installation and that the
ServiceAccount would retain its imagePullSecrets.
What did you see instead? Under which circumstances?
After I approve the InstallPlan, OLM appears to be removing the ServiceAccount that I created manually, and then creates a new ServiceAccount with
the same name, but leaves out the applied (via patch) imagePullSecrets.  This causes the operator pod to not be able
to pull the gitlab registry images.
Environment

operator-lifecycle-manager version:

name: OPERATOR_NAME
value: olm-operator
name: RELEASE_VERSION
value: 4.11.1
image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:71e485ca85f437eab29e7442aba98f9b40209e187e09cc16b02a90ce2ea47a69

Kubernetes version information:

Client Version: 4.11.2
Kustomize Version: v4.5.4
Server Version: 4.11.1
Kubernetes Version: v1.24.0+4f0dd4d

Kubernetes cluster kind:

openshift 4.11.1
Possible Solution
I would have thought that OLM would detect that the ServiceAccount was already created, then perform a merge/patch on it instead of deleting the ServiceAccount and recreating it (from the CSV spec).  I don't see a way in the CSV to tell OLM to add the imagePullSecret to the ServiceAccount that it recreates either.  I need a way to retain or specify the imagePullSecrets for OLM to use when running the operator.
Additional context
I currently get around this problem by re-patching the ServiceAccount after OLM recreates it, then killing the operator pod, then it can pull from gitlab.  I also tried to set the imagePullSecret via the CSV but that also doesn't appear to work, instead OLM creates an imagePullSecret with a generated name.

@sqqqrly

ping


fix(switch): focus access

Switch
#32
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Only
[ ] Refactor

Description, Motivation and Context
Switches weren't accessible by focus, so I change a little bit the CSS to be able to do it. However, the focus continues not to show anything by design. We should find a way to show the focus stage in a visible way without breaking the system design
Screenshots - Animations

Thank you @DaniAcu!


fix: multi-scf support yunti tag issue fix

修复multi-scf组件apigw绑定云梯标签不生效问题

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Modify Pipeline UI test in Smoke to use pip_index_url (making it compatible with disconnected clusters)

Implements RHOAIENG-3473:

Modifies Pipelines UI test in Smoke to use pip_index_url and pip_trusted_host. The values should be available in the global variables PIP_INDEX_URL and PIP_TRUSTED_HOST (for connected and disconnected clusters).
The test will:

Create a custom ConfigMap in the data science project containing the values for pip_index_url and pip_trusted_host
Run iris_pipeline_pip_index_url_compiled.yaml  sample file, which reads the ConfigMap (using kfp-kubernetes, new dependency) and injects the values as env vars in the pipeline tasks.
Note:  I had to manually modify iris_pipeline_pip_index_url_compiled.yaml in order to use PIP_TRUSTED_HOST, as currently the kfp 2.7.0 is using pip_index_url for both values

Tested successfully in disconnect/job/psi/job/rhods-smoke/10/console

Adding label do-not-merge until PIP_INDEX_URL and PIP_TRUSTED_HOST are configured in Jenkins


Set runtime_type into pipeline based on selected tile

The changes relative to #2258 will require that a new runtime_type field be added into the pipeline (as a sibling to runtime).  This type should equate to the string-ized name of the RuntimeProcessorType enumeration (e.g., KUBEFLOW_PIPELINES) - updated here.
The runtime field will continue to reflect the processor name or its corresponding schema (as the two must match).  Today, there is no distraction between runtime name and type.

This will be addressed in #2263.


No backend with an available connection slot that can reach address

System Health details
System Information

version
core-2023.5.4

installation_type
Home Assistant Container

dev
false

hassio
false

docker
true

user
root

virtualenv
false

python_version
3.10.11

os_name
Linux

os_version
6.1.21-v8+

arch
aarch64

timezone
Europe/Amsterdam

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
5000

Installed Version
1.30.1

Stage
running

Available Repositories
1286

Downloaded Repositories
10

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Dashboards

dashboards
1

resources
3

views
1

mode
storage

Recorder

oldest_recorder_run
21 May 2023 at 03:27

current_recorder_run
30 May 2023 at 20:04

estimated_db_size
109.45 MiB

database_engine
sqlite

database_version
3.40.1

Spotify

api_endpoint_reachable
ok

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
Cannot pair Nuki Smart Lock 3.0 using Raspberry Pi 4B with buit-in Bluetooth.
Reproduction steps
No Nuki device is automatically discovered.
I then tried adding the integration manually and filled out the device name and address. This takes me to the followup screen and after putting the Nuki in pairing mode and selecting 'Pair device automatically' I get an error.
 Please report issue to the custom integration author for hass_nuki_bt using this method at custom_components/hass_nuki_bt/config_flow.py, line 151: ret = await device.pair()
2023-05-31 15:27:07.162 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 235, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 146, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 180, in post
    return await super().post(request, flow_id)
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 72, in wrapper
    result = await method(view, request, data, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 110, in post
    result = await self._flow_mgr.async_configure(flow_id, data)
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 267, in async_configure
    result = await self._async_handle_step(
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 367, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
  File "/config/custom_components/hass_nuki_bt/config_flow.py", line 151, in async_step_pair
    ret = await device.pair()
  File "/usr/local/lib/python3.10/site-packages/pyNukiBT/nuki.py", line 502, in pair
    await self.connect() # connect so we can identify the device type and update self._const accordingly
  File "/usr/local/lib/python3.10/site-packages/pyNukiBT/nuki.py", line 386, in connect
    await self._client.connect()
  File "/usr/src/homeassistant/homeassistant/components/bluetooth/wrappers.py", line 253, in connect
    wrapped_backend = self._async_get_best_available_backend_and_device(manager)
  File "/usr/src/homeassistant/homeassistant/components/bluetooth/wrappers.py", line 355, in _async_get_best_available_backend_and_device
    raise BleakError(
bleak.exc.BleakError: No backend with an available connection slot that can reach address XX:XX:XX:XX:XX:XX was found

Diagnostics dump
No response

So after setting up an ESP32 as a Bluetooth proxy the Nuki is detected, but when configuring automatically the wizard finishes, but it says 'Failed to setup' on the integrations page.
Logs:
2023-06-08 20:50:03.499 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Apartment door for hass_nuki_bt

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
    result = await component.async_setup_entry(hass, self)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hass_nuki_bt/__init__.py", line 79, in async_setup_entry
    if not await coordinator.async_wait_ready():
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hass_nuki_bt/coordinator.py", line 148, in async_wait_ready
    await self._async_update()
  File "/config/custom_components/hass_nuki_bt/coordinator.py", line 108, in _async_update
    await self.device.update_state()
  File "/usr/local/lib/python3.11/site-packages/pyNukiBT/nuki.py", line 424, in update_state
    self._const.NukiCommand.REQUEST_DATA,
    ^^^^^^^^^^^
AttributeError: 'NukiDevice' object has no attribute '_const'

Any ideas @ronengr ?

Regarding the first issue, it seems there is no BT controller available to HA that is in range of the Nuki.
I see that adding a BT Proxy fixed this :-)
Regarding the 2nd issue, this is strange.
what version of hass_nuki_bt are you using?

Regarding the first issue, it seems there is no BT controller available to HA that is in range of the Nuki.
I see that adding a BT Proxy fixed this :-)
Regarding the 2nd issue, this is strange.
what version of hass_nuki_bt are you using?

I assumed having a Bluetooth enabled Raspberry Pi was enough, but apparently not.
I've tried everything that came to mind including your suggestion using version 0.0.5, but no luck. In the end I switched to https://github.com/technyon/nuki_hub.

Maybe there was something wrong with my Bluetooth config. I'd rather not touch it now that it's working so I won't be able to give you more help with debugging.
If I'm the only one facing this problem it was likely me. I think there's definitely a case for not using an ESP so I hope your project will be successful!
Feel free to close this issue.

I am getting this error in conjunction with this warning:
2023-11-25 13:18:36.015 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hass_nuki_bt' attempted to call BleakClient with an address instead of a BLEDevice at custom_components/hass_nuki_bt/config_flow.py, line 151: ret = await device.pair(), please create a bug report at https://github.com/ronengr/hass_nuki_bt/issues

I'm also on a Pi 4B with builtin bluetooth. My Nuki lock is version 1.0. hass_nuki_bt version is 0.0.7.

Same error here with NUKI 3 (not pro) and a raspberry pi located quite close to the NUKI.
First time it did work but calling the service failed. After removing the integration and trying to pair again it immediately  showed "ERROR" and the logs show:
File "/usr/local/lib/python3.11/site-packages/habluetooth/wrappers.py", line 379, in _async_get_best_available_backend_and_device raise BleakError( bleak.exc.BleakError: No backend with an available connection slot that can reach address 54:D2:72:5C:13:64 was found

@maryum375
if you are getting this error from bleak it means the computer cannot find a way to communicate with the Nuki BT device.
either there is an issue with the BT adapter or there are interference or some other issues causing the connection issue.
you can try moving the RPI closer or try adding an antenna to the RPI, or maybe use a BT proxy.
Unfortunately, if bleak (the underlying BT package for HA) cannot establish a connection to the device, there is nothing i can do


Improve compatibility between Drain Cleaner and other tools

Some tools have compatibility issues with Drain Cleaner because when the Pod Disruption Budget is set to maxUnavailable: 0, they take it as that these Pods cannot be evicted and the node cannot be drained (scaled-down, ...). That does not apply to the Strimzi Pods when Drain Cleaner is used. But I guess it is a fair assumption.
This PR changes how the Drain Cleaner works to try to address it. The old behavior is the following:

PDB is set to maxUnavailable: 0
Drain Cleaner gets the eviction request through the webhook, annotates the pod and approves the eviction request
Kubernetes get the eviction request for execution but do not evict the Pod because of the Pod Disruption Budget.

So we rely on the PDB to not have the Pod evicted. The new behavior does not rely on the Pod Disruption Budget anymore:

PDB can be set to maxUnavailable: 1 (but 0 would work as well from Drain Cleaner perspective)
Drain Cleaner gets the eviction request through the webhook, annotates the pod and denies the eviction request
Kubernetes never get the eviction request for execution and the PDB is ignored

This change has some negative side effects:

While it might improve how Drain Cleaner works with some tools, we do not know what other tools will it break. The denied Eviction request from the webhook is a different error from the eviction failing due to PDB. And for example kubectl drain fails when it sees it rather than retrying. So any tooling expecting the PDB error and retrying for that would likely fail with the new error.
When Drain Cleaner is installed in the Kube cluster, the Pod Disruption Budget is ignored during evictions (i.e. if the user sets it to 0, 1 or 2, it will work the same). Today, when you use Drain Cleaner and set the PDB to 1, it essentially bypasses the Drain Cleaner. I'm not sure I see this as a major issue, but it is a difference in behavior.

I believe the improved compatibility is worth it. But this PR keeps the original mode as an alternative so that affected users can switch back to it.

But this PR keeps the original mode as an alternative so that affected users can switch back to it.

Thank you for keeping this as an option 🙂👍
For what it's worth in our use case we use the cluster-autoscaler, and in order to force it to consider our kafka broker pods as evictable (but in a controlled manner), we add the annotation cluster-autoscaler.kubernetes.io/safe-to-evict=true. This overrides the logic that considers that pods with PDBs set at maxUnavailable: 0 are unsafe to evict.
The cluster-autoscaler then attempts the drain,  the drain cleaner adds the annotation, and the operator controls the moves 😌
We prefer to use this and keep relying on having PDB set at maxUnavailable: 0 in order to keep the strimzi operator in control in case the drain-cleaner is unavailable for any reason (to safeguard partition availability), and the autoscaler is effectively allowed to make progress on its drain after strimzi is done moving the pods. 🙂
I am adding this here just as a FYI for anyone to consider, but if this is out of line please let me know 🗒

This overrides the logic that considers that pods with PDBs set at maxUnavailable: 0 are unsafe to evict

If you opened up the PDB fully or set a maxUnavailable to 1 here would you see tangibly different behavior? I would think that if you are saying that pods are safe-to-evict then you are effectively either saying that CAS can roll multiple nodes at once or a single node at a time? How does this start to differ if you don't have to set this annotation and you just open the PDBs?

@hileef I did not try cluster-autoscaler. But I think it should work with the new way without needing the additional annotation. That said, there is no plan to remove the old mode from the Drain Cleaner. So if it works better for you, it is fine and you should be able to keep using it.

@jonathan-innis I will try to describe my understanding here, please let me know if this makes senses and/or is clear enough 🙏  📖

if we "open" the PDBs ( let's say to any value of maxUnavailable >= 1 )
then with the old behaviour, evictions will pass through and actually cause broker pods to be deleted by the kubernetes control plane, without it being under the strimzi operator's control ⚠
with the new behaviour from this PR, if the drain cleaner is up, then it will always refuse evictions, and its manual-roll annotation will causes strimzi operator to roll the broker pods in a controlled manner ✅
but, if the drain-cleaner is unavailable for any reason (which is a small, but non-zero risk), then the kubernetes control plane could proceed with broker pod deletions ⚠ (unless this line is changed)
The cluster-autoscaler safe-to-evict annotation's presence or absence does not matter in these cases above.

If we have "closed" PDBs ( maxUnavailable = 0 )
Generally any evictions are guaranteed to be blocked, irrespective of the health of the drain-cleaner.
This means that at no point will the kubernetes control plane proceed to delete a kafka broker pod from an eviction request.
This is true with both the old and new behaviour.
If the drain-cleaner is unavailable, the cluster remains stable ( no node/pod movements ). 🆗
If the drain-cleaner is running then the manual rolling annotations will be set, and the strimzi operator will be able to roll the broker pods in a controlled manner ( e.g. taking into account replication lag status of partitions and overall kafka cluster health ). ✅
The cluster-autoscaler annotation's presence in this case allows us to tell it to try to make eviction attempts anyways, where it normally wouldn't, as it includes calculations to ignore nodes that host pods subject to zero acceptable disruptions by default. So, without an annotation, the cluster-autoscaler will not attempt evictions, even though we would like it to, but in a controlled-by-strimzi manner.

overall, the differences are

we want to err on the side of the strimzi operator being in control ( rather than the kubernetes control plane )
we want to err on the side of blocking rather than allowing node drains in failure cases
we want the auto-scaler to be able to do its thing, but without impacting kafka availability
therefore : we are likely to maintain "closed" PDBs for now.

We understand that the new behaviour from this PR allows other autoscalers to consider nodes hosting kafka pods as drainable (via open PDBs), whereas we use a cluster-autoscaler specific annotation for this today (with closed PDBs).
I simply wanted to highlight that auto-scaling ( 💸 )  with closed PDBs is possible when using the CAS. 🙂
The new behaviour from this PR doesn't prevent us from continuing with closed PDBs, but additionally we like to see the eviction requests go all the way through to the PDB refusal as we have some monitoring queries that assume that behaviour, so we are happy to carry on with that 😌
@jonathan-innis I hope that makes it a little bit clearer 😅
please do let me know if you think I am making a mistake or am missing something 🙏

no plan to remove the old mode from the Drain Cleaner.
So if it works better for you, it is fine and you should be able to keep using it.

@scholzj that sounds perfect for us, thanks a lot 👍

@strimzi/maintainers Please think about this PR so that we can decide it on the next community call on Thursday.

/azp run build

/azp run drain-cleaner

@ppatierno @im-konge Please have a look at this, it should be now ready for review.


Improve input component

@Stefanwullems I generally like the idea of merging TextInput and NumericInput into a single component. @Michiel87 also had some thoughts about this. Let's wait for his input.


add missing variable sshd_config_path

Closes #29

Hi @felixb,
is this project still alive?
Can some one review my MRs?
I've tried to contact the arillso group by e-mail<EMAIL_ADDRESS>but the mail was rejected by the remote server 😢
Regards,
Frank


Fix missing spanish translation

Here is the translated text that I skipped.
Glad that now we have tests :).

@stsewd THANK YOU! :100:
Thanks to tests that we can found syntax errors in cson.


musig-spec: add Session Context to simplify sign/verify/sigagg

ACK 5576a9efcbb24871c88b24cf3b9afabd43bb489f

Closing this because discussions on #167 also affect commits in this PR, so better to focus on #167.


why there is no zero(attn) before compute<EMAIL_ADDRESS>in h100 example?

https://github.com/HazyResearch/ThunderKittens/blob/eab8f21c1addbc52bd013339023f4afa01a5bc57/examples/attn/h100/h100_fwd.cu#L106
Is it bug?

Hi @xiayuqing0622,
Thanks for your question. So, the clarification here is that mm_ABt is different from mma_ABt - specifically, the former essentially resets the values in att_block, while the latter accumulates onto the values in att_block (mma = accumulate, mm = reset).

Hi @xiayuqing0622,
Thanks for your question. So, the clarification here is that mm_ABt is different from mma_ABt - specifically, the former resets the values in att_block, while the latter accumulates onto the values in att_block
(mma = accumulate and mm = reset, which is identical to if att_block was zeroed before).

o i see, thank you. :)


Materials are rendering black if there are no lights in the scene (Intel driver bug)

Godot version:3.1

OS/device including version:Windows 7 64 bit
Intel g41 express chipset
Open Gl 2.1

Issue description: I used GLES2 renderer. Adding  a mesh instance gives a completely black cube. Adding materials has no effect. The sky is rendering as it should. Using mesa3d as a open GL 3.1 fixes this problem. Otherwise it occurs on every project

Steps to reproduce: Add a cube in Godot 3.1 on intel g41 express on GLES2 project
Minimal reproduction project:

Well, Godot prints some information to stdout, which you can get on windows by running it from the command line, or from the console window which opens alongside Godot (in debug builds).

Here is the log
https://drive.google.com/file/d/1z8KfR_Wu7dqddRKIxIMUoh05Cp2Slssi/view?usp=drivesdk

I just wanted to point out that this issue has NOT been fixed in Godot 3.1 beta 4

It turned out that I just needed to add a light to the scene. Though when I ran the same project on Mesa with a opengl 3.3 'emulated' environment, I found that a mesh with no materials was rendering blue without any material or light.
It is still a issue, but a minor one now.
GLES3-no lights give blue mesh
GLES2-no lights give black mesh

Is this still reproducible in 3.1 beta 8 or later?
Also make sure to have the default_env.tres defined as default environment in your project settings, otherwise it's normal that there is no default lighting. If it's defined and it still doesn't work, it might be that the settings used in default_env.tres don't work for your GPU, you could try to edit them to see what happens.

Using beta 8 here, and its still not fixed

With that said, g41 chipset is quite old,2008 I think, and I dont think any serious(or even hobbyist) would be using it. Only I am stuck with it. :)

Still present in latest Calinou builds

Is this present in 3.1.2 or 3.2 beta x?

@clayjohn
3.2 beta 3
No lights in any of these
Default Environment

No Environment(red material applied)

No Environment No material

A custom environment with no changes to default values(red material)

A custom environment with no changes to default values(red material)+ directional light

No light; Red Material; Custom Env; Ambient light set to white

Do remember that my hardware is ancient.

Can anyone still reproduce this bug in Godot 3.2.3 or any later release?

I seem to remember a similar bug being closed as fixed after the batching changes?

I seem to remember a similar bug being closed as fixed after the batching changes?

Yes, that was https://github.com/godotengine/godot/issues/30330.

@KoBeWi I am extremely sorry, but I have sold off that PC. So I can't check.

Closing then. If someone can still reproduce, comment.

I have the same issue

I'm In Godot 3.3.3
I have a Intel i3 550
Window 10 64 bit
Also with the GLES2 render

Does it happen in Godot 3.4?

Yep

Still getting the same issue on Godot v3.4.stable.mono.official.206ba70f4
Windows 10 64 Bit
Intel HD Graphics 2000
GLES 2

What does fix is to use a mesa 3d .dll file in the same directory of the godot executable, this way Godot will be forced to render in the CPU instead of the GPU using mesa drivers.

I tested this on an old CPU with intel HD Graphics:
Ubuntu 20.04 LTS:
Godot worked will without any problem with meshes or performance on both GLES2 and GLES3
Windows 10 Pro 64-bit:
Meshes are completely black,
Then I tried to force render on the CPU by using this .dll file
At first it seems good but I noticed that the imported materials are completely black.
Testing device:

CPU: Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz
GPU: (built-in) Intel® HD Graphics for Previous Generation Intel® Processors
RAM: 2×Samsung 2GB DDR3 SDRAM Memory 240pin PC3-10600U 1333MHz (2×2GB DDR3)
OS: Windows 10 Pro 64-bit + Ubuntu 20.04 LTS

Screenshots (using .dll file):
GLES2:

FPS: (170 - 180)
Left: raw mesh instance
Center: mesh instance with spatial material (no imports)
Right: mesh instance with spatial material (imported texture)

GLES3:

FPS: (31 - 34)
Left: raw mesh instance
Center: mesh instance with spatial material (no imports)
Right: mesh instance with spatial material (imported texture)

https://i.imgur.com/I95crK7.gif - Windows 10 Intel HD Graphics 620 on Godot 3.4.5
Just wanted to show this issue still exists, it only happens without a directional light OR if you have a meshinstance with a spatialmaterial and another without in the same area. No problem in GLES2 or with directional light visible.
The flickering speed is not consistent, some camera positions it doesn't flicker at all. Some directions it flickers even faster.
Btw I'm having the exact same problems from https://github.com/godotengine/godot/issues/30330 which was closed. Either something broke it since then or it was never really fixed. I'm using roughly default settings on a new project.
OP seems to having a separate problem from me and all the other people hijacking this issue though, to be clear. But maybe the problem is related?

https://i.imgur.com/I95crK7.gif - Windows 10 Intel HD Graphics 620 على Godot 3.4.5
أردت فقط أن أوضح أن هذه المشكلة لا تزال موجودة، فهي تحدث فقط بدون ضوء اتجاهي أو إذا كان لديك مثيل شبكي يحتوي على مادة مكانية وآخر بدونه في نفس المنطقة. لا توجد مشكلة في GLES2 أو مع رؤية الضوء الاتجاهي.
سرعة الوميض ليست متسقة، وفي بعض أوضاع الكاميرا لا تومض على الإطلاق. تومض في بعض الاتجاهات بشكل أسرع.
راجع للشغل أواجه نفس المشاكل بالضبط من رقم 30330 الذي تم إغلاقه. إما أن شيئًا ما قد كسره منذ ذلك الحين أو لم يتم إصلاحه أبدًا. أنا أستخدم الإعدادات الافتراضية تقريبًا في مشروع جديد.
يبدو أن OP يواجه مشكلة منفصلة عني وعن جميع الأشخاص الآخرين الذين يختطفون هذه المشكلة، لكي نكون واضحين. ولكن ربما تكون ا

@clayjohn 3.2 بيتا 3
لا أضواء في أي من هذه
البيئة الافتراضية
لا توجد بيئة (تم تطبيق المادة الحمراء)
لا توجد بيئة لا توجد مادة
بيئة مخصصة بدون تغييرات على القيم الافتراضية (المادة الحمراء)
بيئة مخصصة بدون تغييرات على القيم الافتراضية (المادة الحمراء) + ضوء الاتجاه

ERROR

FIX

FIX

This doesn't actually fix the issue, merely sidestep it. Using a fixed ambient light color is different from using the sky as a source of ambient light color.

As you said, it's just avoiding the problem, but at least it works if you intend to work on your project on another computer temporarily, and if you want to export your project, just fill the world environment settings in another computer and paste them inside your project, or move your entire project to export it from another computer.
Perhaps the problem is due to the incompatibility of Godot 3.5 with the motherboard or processor, because I did not encounter the problem in Godot 4 or another device.
This is a partial solution for those who have not found a solution and do not want to spend their brains trying to find a solution
And sorry for talking so much