Refused to display in a frame because it set 'X-Frame-Options' to 'deny'

Library

[ ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[x]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Framework

[x] Angular
[ ] React
[ ] Other

Description
We have integrated Azure AD B2C with Angular application using MSAL, now we are running into an issue, whenever token expiring and trying to renew, we are facing this issue Refused to display in a frame because it set 'X-Frame-Options' to 'deny' in chrome browser
Error Message
Refused to display in a frame because it set 'X-Frame-Options' to 'deny'
MSAL Configuration
const msalConfig: Configuration = {
  auth: {
    clientId: `XXX-Client-ID-XXX`,
    authority: `XXX-Authority-XXX`,
    validateAuthority: false,
    redirectUri: `http://localhost:4200`,
  },
  cache: {
    cacheLocation: 'localStorage', // This configures where your cache will be stored
    storeAuthStateInCookie: isIE,
  },
  system: {
    loadFrameTimeout: 30000
  }
};
@NgModule({
imports: [
MsalModule.forRoot(msalConfig, {
      popUp: isIE,
      consentScopes: [
        'openid',
      ],
      unprotectedResources: [],
      protectedResourceMap: [
        [environment.API, environment.SCOPES]
      ],
      extraQueryParameters: {}
    }),
],
providers: [
    MsalService,
    {
      provide: HTTP_INTERCEPTORS,
      useClass: MsalInterceptor,
      multi: true
    }
]
})

// There is no separate login redirect page, all the routes are protected with MsalGuard

Reproduction steps
In our application azure configuration, accessToken lifetime is set to 60 minutes, once accessToken expires when we are trying to request an authorized API endpoint, the browser screen becomes blank and in the console, we could see the Refused to display in a frame because it set 'X-Frame-Options' to 'deny'.
Expected behavior
Token renewed and application behaves normally
Identity Provider

[ ] Azure AD
[x] Azure B2C Basic Policy
[ ] Azure B2C Custom Policy
[ ] ADFS
[ ] Other

Browsers/Environment

[x] Chrome
[ ] Firefox
[x] Edge
[ ] Safari
[ ] IE
[ ] Other (Please add browser name here)

Regression

[ ] Did this behavior work before?
Version:

Security

[x] Is this issue security related?

Source

[ ] Internal (Microsoft)
[ ] Customer request

@navinna Please see the docs on this error here

@tnorling
In order to give a smooth user experience, we couldn't display the popup to renew the token, also we don't want to redirect the user to get the token, is there any other option to achieve this?

@navinna What did you determine was the cause of this error in your scenario? Was it multiple accounts signed in?

@tnorling
No, there is only one account signed in, I couldn't confirm the cause of this issue in my application.
After reading the doc you mentioned above, I came to know this is the expected behavior. Here my concern is I cannot use the acquireTokenPopup(), can we restrict the redirection when using acquireTokenRedirect to get the new token?

@navinna What happens when you open the link from the error in a new tab? This is expected behavior in some, but not all, scenarios.

@tnorling I don't understand, may I know what is your recommendation, here is my problem

accessToken lifetime is set to 60 minutes, once accessToken expires, when we are trying to request an authorized API endpoint, we could see X-Frames-Options to deny.
after a min or two I could see in the console, token renewal operation failed due to timeout .

in this scenario I am not using acquireTokenSilent() to renew the token.

in this scenario I am not using acquireTokenSilent() to renew the token.

@navinna how are you getting the access token?
Please open the link from the X-Frame options deny error in a new tab and observe what is happening. If it shows an error or is expecting any sort of interaction that is why this error is being thrown.
You can also try upgrading to msal-angular v2 where we do not expect this error to occur as frequently

in this scenario I am not using acquireTokenSilent() to renew the token.

@navinna how are you getting the access token?
Please open the link from the X-Frame options deny error in a new tab and observe what is happening. If it shows an error or is expecting any sort of interaction that is why this error is being thrown.
You can also try upgrading to msal-angular v2 where we do not expect this error to occur as frequently

@tnorling
We cannot use v2 since it's under development and not ready for production.
I opened the error in the new tab and I could see the same error in the console, but I would like to know is there any solution or workaround for this issue.

@navinna X-Frame-Options Deny means that the service does not allow the page to be rendered in an iframe. There are many reasons why this would not be allowed and the solution depends on your particular scenario. When you open the error url in a new tab you should see the page that was trying to be rendered in the hidden iframe. Can you clarify do you see a login page or your app when you open the url?


Add OpenLyrics context menu options to foobar's "View" menu

Hi @jacquesh,
this feature request is referred to my last reply from here: https://github.com/jacquesh/foo_openlyrics/issues/177.
Can you please add your OpenLyrics context menu options:

to foobar's "View" menu:

As you know. when holding Shift key + clicking on foobar's "View" menu the advanced options will be shown.
Also can you please add two additional options "Next lyrics" which will cycle to the next lyrics source and automatically display
the new lyrics and add the option "Save lyrics to tags", which will write the lyrics to the %lyrics% metadata field.
I have my own lyrics context menu in my theme with some ESLyric context menu options:

When I have these context menu options, I can call them like this:
fb.RunMainMenuCommand('View/ESLyric/Panels/Lyric information');
In your case it would be:
fb.RunMainMenuCommand('View/OpenLyrics/Search for lyrics');
fb.RunMainMenuCommand('View/OpenLyrics/Save lyrics');
fb.RunMainMenuCommand('View/OpenLyrics/About lyrics');
etc... you get the picture...
This should be quick and easy to implement, can you add it in your next version?
Thanks!
-TT

As you know. when holding Shift key + clicking on foobar's "View" menu the advanced options will be shown.

I actually didn't know this. That's interesting. Do you know what the distinction is between regular and "advanced" menu items? How do I specify that something only shows up in the advanced menu? I'm guessing I specify flag_defaulthidden from menu.h's mainmenu_commands?
You also have a few other requests in here:

"Next lyrics" which will cycle to the next lyrics source and automatically display the new lyrics

This isn't really a thing, but it's been asked for before. The closest issue I can find is #211 so I'd say we should track it there

"Save lyrics to tags", which will write the lyrics to the %lyrics% metadata field.

This looks somewhat like #352. I seem to recall somebody else was asking recently to allow saving to tags when the lyric is loaded from files (or something to that effect) but I can't find the issue now =/

When I have these context menu options, I can call them like this:

You can already do this for the examples given though, right? The items registered with the context menu are at least available for setting hotkeys. Are they also available via whatever API you're using there (since it clearly isn't the C++ SDK)?

As you know. when holding Shift key + clicking on foobar's "View" menu the advanced options will be shown.

I actually didn't know this. That's interesting. Do you know what the distinction is between regular and "advanced" menu items? How do I specify that something only shows up in the advanced menu? I'm guessing I specify flag_defaulthidden from menu.h's mainmenu_commands?

No idea, I am not a foobar component developer nor have knowledge about C++, only HTML, CSS and JavaScript...
When holding Shift key + clicking on foobar's menu "File", "View" and "Playback", you will get extra hidden menu items
of foobar and user-components. @TheQwertiest and @marc2k3 would definitely know about this. Can you please
share your knowledge @marc2k3? Thanks.

You can already do this for the examples given though, right? The items registered with the context menu are at least available for setting hotkeys. Are they also available via whatever API you're using there (since it clearly isn't the C++ SDK)?

I am using @TheQwertiest Spider Monkey Panel component which is an interface between foobar and JavaScript.
There is also the predecessor of SMP -> JScript Panel 3 ( which is actively maintained by @marc2k3 ).
Both have the method fb.RunMainMenuCommand which just executes available main menu items:
https://theqwertiest.github.io/foo_spider_monkey_panel/assets/generated_files/docs/html/fb.html#.RunMainMenuCommand
https://jscript-panel.github.io/docs/namespaces/fb/#fbrunmainmenucommandcommand
So I need these in the foobar "View" menu to be able to execute them.
-TT


use generic package name

We should remove the env-linter from the scope @namics and use a generic name. (e.g. envlinter, environment-linter, ...)

I like the name envlinter

That would be great, of course.
And all the criteria for unpublishing should be met. (https://docs.npmjs.com/policies/unpublish#packages-published-more-than-72-hours-ago)

This is complete so feel free to snatch it up before someone else does.

Cool. Thank you very much @seanperkins
Re-publishing works at the earliest 24h after unpublishing. Will try it tomorrow.

published to npm as version 0.5.1 https://www.npmjs.com/package/env-linter
thank you again


Creating a waypoint with the same name as a workload results in the waypoint (silently) not being created

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
k create ns test1
k apply -f samples/httpbin/httpbin.yaml -n test1
istioctl x waypoint apply -n test1 --name httpbin --enroll-namespace

->
waypoint test1/httpbin applied
namespace test1 labeled with "istio.io/use-waypoint: httpbin"

k get pods -n test1 ->
NAME                       READY   STATUS    RESTARTS   AGE   IP           NODE                    NOMINATED NODE   READINESS GATES
httpbin-648f469544-7sfds   1/1     Running   0          9m    <IP_ADDRESS>   istio-testing-worker2   <none>           <none>

k get gateways -n test1
NAME      CLASS            ADDRESS   PROGRAMMED   AGE
httpbin   istio-waypoint             False        35s

Version
1.22

Additional Information
Refusing to create with a name collision is fine, but the fact that it doesn't tell me that there's a problem and seems happy is probably not.

controller does write the programmed false status condition

adding --wait flag the the waypoint apply results in a basic timeout. one point of improvement could be the check gtw status when it times out and print the conditions

@bleggett
The only way that a warning seems plausible is to mirror what the controller checks for currently, but there is risk of deviation overtime. Then we're in a situation of having to update istioctl to match the gateway deployment(?) controller whenever that changes. That seems less than ideal.
If the controller does write the programmed false status condition as @ilrudie pointed out, do we need to do more work/checking in istioctl?

If the controller does write the programmed false status condition as @ilrudie pointed out, do we need to do more work/checking in istioctl?

Maybe not, but it's not great UX - I did something reasonable, you let me do it with no negative feedback, and there's (some other) command I need to check to actually know that it didn't take for whatever reason.
(maybe just putting
waypoint test1/httpbin applied
namespace test1 labeled with "istio.io/use-waypoint: httpbin"
monitor status of waypoint deployment with `k get gateways -n test1`

in waypoint apply's output would be enough of a breadcrumb)

Yeah we need to train people to check status on Gateways, and this is part of that industry-wide transition. Adding a monitor should improve the UX though, so +1 to that idea

@bleggett, would you say that being able to return the failure message IF you use the wait flag is not good enough?
IMO waypoint apply is OK to be transactionally similar to kubectl apply.

If the controller does write the programmed false status condition as @ilrudie pointed out, do we need to do more work/checking in istioctl?

Maybe not, but it's not great UX - I did something reasonable, you let me do it with no negative feedback, and there's (some other) command I need to check to actually know that it didn't take for whatever reason, and until/unless I do that the policy I think will be applied is not being applied.
(maybe just putting
waypoint test1/httpbin applied
namespace test1 labeled with "istio.io/use-waypoint: httpbin"
monitor status of waypoint deployment with `k get gateways -n test1`

in waypoint apply's output would be enough of a breadcrumb)

@howardjohn brought up some good points as to why this might not be as helpful as we'd think:
https://github.com/istio/istio/pull/51394

Does not seem very helpful for a newer users. It will return istio gateways, not k8s ones, in some cases I think as a first issue. It also doesn't tell users what do look for. It also is hard to monitor because its a one-shot command

@bleggett ^

If I'm saying "it would be good to have a way to check that the waypoint is working and to point people at how they can do this" and we are saying "well, the tool for that isn't useful or reliable for that" I think we still have a UX problem, if I understand it correctly.
What do we expect people to do here? Always use --wait? What do they do if they don't?

I think a waypoint status makes more sense then expecting istioctl to analyze whether or not the waypoint is valid statically. waiting works because we can check on the status that the waypoint controllers write and report it back if it fails or return happily if it succeeds but we don't need to figure out everything the controllers are doing. In that line of thinking having an istioctl command that gets your waypoint status seems more reasonable.

Aight renamed.
"k get gateways -n test1 doesn't do the job, so we need an istioctl command" seems reasonable to me.

@bleggett
So safe to say should we scrap this one  and show status to the user instead?


Children/subfolders is empty but hasChildren is true

Describe the bug
$folder->getChildren()->total() is 0
Used config
See code to reproduce (maybe I'm doing something wrong?)
Code to Reproduce
The troubling code section which produces the reported bug.
$cm = new ClientManager([
    'accounts' => [
        'myaccount' => [
            'host'       => 'myhost.com',
            'port'       => 993,
            'protocol'   => 'imap',
            'encryption' => 'ssl',
            'username'   => 'myusername',
            'password'   => 'mypassword',
        ]
    ]
]);

$client = $cm->account('myaccount');
$folder = $client->getFolder('TestFolder');
var_dump($folder->hasChildren()); // bool(true)
var_dump($folder->getChildren()->total()); // int(0) <-- bug?

Expected behavior
In my case I expect var_dump($folder->getChildren()->total()); to be int(1)
Desktop / Server (please complete the following information):

OS: Linux Server Debian
PHP: 8.2.10 (fpm)
Provider: Gmail / Mailcow

Hello again,
After looking into the source code, I realize why the expected results is "wrong",
The $client->getFolder(...) method calls getFolders(false, ...)
so I managed to make a "workaround" to get what I need like this:
$folders = $client->getFolders(true, 'TestFolder');
$folder  = $folders->first();
var_dump($folder->getChildren()->all());

Resulting in:
array(1) {
  [0]=>
  object(Webklex\PHPIMAP\Folder)#860 (12) {
  ...

But although I now managed to get a list of subfolders and var_dump($folder->getChildren()); gives me this:
object(Webklex\PHPIMAP\Support\FolderCollection)#918 (3) {
  ["items":protected]=>
  array(1) {
    [0]=>
    object(Webklex\PHPIMAP\Folder)#919 (12) {

The var_dump($folder->getChildren()->total()); still gives me:
int(0)


copy button

oh what! does the copy/paste work just out of the box with this Lexical feature to save to HTML?


[bug?] Can't specify drop_last argument in  Datasets.dataloaders()

In 35_tutorial.wikitext.ipynb, I call dsets.dataloaders(bs=bs, seq_len=seq_len,drop_last=True), and get
TypeError: type object got multiple values for keyword argument 'drop_last'
This is because  in fastai2/data/core.py
class FilteredBase:
....
    def dataloaders(self, bs=64, val_bs=None, shuffle_train=True, n=None, path='.', dl_type=None, dl_kwargs=None, device=None,
                  **kwargs):
....
        dl = dl_type(self.subset(0), bs=bs, shuffle=shuffle_train, drop_last=shuffle_train, n=n, device=device,
                     **merge(kwargs, dl_kwargs[0]))

drop_last has already been specified as shuffle_train. I can't get the reason that whether to shuffle the trainset relates to whether to drop the last batch, so I guess it is a bug.

You can pass it now, but note that it doesn't really change the existing behavior: shuffle_train with set it to True and the validation dataloader will always set it to False.

Is there a reason that we can't drop the last batch of validataion dataset ?
When I set seq_len=200, I get last batch of shape (batch_size, 133) which breaks my model.
And my model is kind of like this, so it is hard to adapt to batch with different sequence length.
class ExperimentTextModel(...):
  def __init__(...):
    ...
    self.norm = nn.BatchNorm1d(config.sequence_length)
    ...

Or can I get (bs, 200) for the last batch which bs is smaller than batch_size I specified?


freing _frame too early (writeMultipleCoils sets wrong values)

In this function for example _frame is freed and after that frame[6+i] is read. But frame actually points to _frame:
void Modbus::writeMultipleCoils(byte* frame,word startreg, word numoutputs, byte bytecount)
See code changes below:

Original code:
//Clean frame buffer
free(_frame);
_len = 5;
_frame = (byte *) malloc(_len);
if (!_frame) {
this->exceptionResponse(MB_FC_WRITE_COILS, MB_EX_SLAVE_FAILURE);
return;
}
_frame[0] = MB_FC_WRITE_COILS;
_frame[1] = startreg >> 8;
_frame[2] = startreg & 0x00FF;
_frame[3] = numoutputs >> 8;
_frame[4] = numoutputs & 0x00FF;
byte bitn = 0;
word totoutputs = numoutputs;
word i;
while (numoutputs--) {
    i = (totoutputs - numoutputs) / 8;
    this->Coil(startreg, bitRead(frame[6+i], bitn));
    //increment the bit index
    bitn++;
    if (bitn == 8) bitn = 0;
    //increment the register
    startreg++;
}

Changed code:
byte bitn = 0;
word totoutputs = numoutputs;
word i;
word tempNumoutputs = numoutputs;
word tempStartreg = startreg;
while (tempNumoutputs) {
    i = (totoutputs - tempNumoutputs) / 8;
    this->Coil(tempStartreg, bitRead(frame[6+i], bitn));
    //increment the bit index
    bitn++;
    if (bitn == 8) bitn = 0;
    //increment the register
    tempStartreg++;
	tempNumoutputs--;
}

//Clean frame buffer
**free(_frame);**
_len = 5;
_frame = (byte *) malloc(_len);
if (!_frame) {
    this->exceptionResponse(MB_FC_WRITE_COILS, MB_EX_SLAVE_FAILURE);
    return;
}

_frame[0] = MB_FC_WRITE_COILS;
_frame[1] = startreg >> 8;
_frame[2] = startreg & 0x00FF;
_frame[3] = numoutputs >> 8;
_frame[4] = numoutputs & 0x00FF;

See issue https://github.com/andresarmento/modbus-arduino/issues/35 as well.

You are right, this is a severe issue if your system (e.g. esp32) is capable of running multiple processes and uses dynamic memory more than a small embedded with no other processes running. That may be the reason why not all users do have reported problems. I have got the same problems with this issue and needed to change the code. But your way to change it is in my eyes not the best way to correct this issue. By placing the whole response section behind the register writing processes (btw. this issue is also present to write multiple coils) you are not acting according to Modbus error compliance: When the malloc() function in allocating the frame for the answer does give an error back you will answer the function call from the Modbus master with an error code although you have changed the registers successfully according to the write function call. To avoid this scenario there is no other way than using a second frame buffer for input. So I defined an "_iframe" in Modbus.h:
 protected:         byte *_frame; 		byte *_iframe;         byte  _len;         byte  _reply;         void receivePDU(byte* frame);
Then I'm using this frame for the receivePDU() function in "ModbusIP.cpp":
`            if (_MBAP[2] !=0 || _MBAP[3] !=0) return;   //Not a MODBUSIP packet
if (_len > MODBUSIP_MAXFRAME) return;      //Length is over MODBUSIP_MAXFRAME
        _iframe = (byte*) malloc(_len);
        i = 0;
        while (client.available()){
            _iframe[i] = client.read();
            i++;
            if (i==_len) break;
        }

        this->receivePDU(_iframe);
		free(_iframe);
        if (_reply != MB_REPLY_OFF) {

`
With this construction, you are freeing the _iframe at the right point: after finishing the call to receivePDU(). This means you need to remove all the early free(_frame) lines in Modbus.ccp and leave just the single one at the end of "void ModbusIP::task()" after sending the response in ModbusCPP. Please search for all of the "free(_frame)" in Modbus.cpp and comment them ALL! In my eyes, Modbus.cpp should not deal with freeing the output frame buffer but the piece of software which is sending (ModbusIP.cpp).
I know that this way of solving the problem does require additional dynamic buffer memory. But to me, it seems to be the only clear and compliant way of solving the issue.


JavaDocs for UpdateTurnList Inaccurate

Bug Report
The JavaDocs for a softbutton array inside of UpdateTurnList reference a max value of 4, however the mobile api has a max value of 1.  When time permits the documentation should be updated as error can be seen in guides.
Snippet below:
    /**
     * Sets the SoftButtons
     *
     * @param softButtons
     *            a List<SoftButton> value
     *

     *            Notes:

     *

     *
If omitted on supported displays, the alert will not have any SoftButton

     *
ArrayMin: 0

     *
ArrayMax: 4

     *

     * @since SmartDeviceLink 2.0
     */

    public void setSoftButtons(List<SoftButton> softButtons){
        setParameters(KEY_SOFT_BUTTONS, softButtons);
    }

JavaDocs:
https://github.com/smartdevicelink/sdl_android/blob/master/sdl_android/src/main/java/com/smartdevicelink/proxy/rpc/UpdateTurnList.java#L88
Mobile API:
https://github.com/smartdevicelink/sdl_core/blob/master/src/components/interfaces/MOBILE_API.xml#L5841
Reproduction Steps
Review JavaDocs for UpdateTurnList and compare to mobile api
Expected Behavior
Accurate JavaDocs
Observed Behavior
Incorrect JavaDocs

Confirmed the RPC spec defines it as the same : https://github.com/smartdevicelink/rpc_spec/blob/master/MOBILE_API.xml#L5841
Very strange definition for a param, an array with max value 1. However, issue is valid; I will get it fixed for this RC.
Just an FYI, the RPC spec reference should be used over the Core MOBILE_API.xml as the "source of truth".

Will be fixed with commit: https://github.com/smartdevicelink/sdl_android/pull/1015/commits/730ae6c8538c33bea4aa718a1e16244f398b899b


Custom ipfs gateway and JSON Metadata missing

Hello @juliancwirko and thanks a lot for this awesome tool.
I created my first test collection under this address.
My images and metadata are here.
Hence I used Qmd4Y4DtWRVSKzMDtPxPgGGpfeQ8bJKYR1pgxxVzBU5S8h as my ipfs base path when I set up the contract.
However, when having minted an NFT, not gateway.pinata.cloud is taken, but ipfs.io. One can see this here.
Besides, also when looking at the mint, the 1.json file is not listed as asset, but instead the image (1.png) is listed twice.
Appreciate your help and thanks!

Regarding the ipfs, I found a solution by just uploading directly to ipfs.
Here is an updated example, and when clicking the ipfs link, one can see that the image is now there!
The only thing that still doesn't seem to work is, that the metadata JSON file is linked as asset.
As an example, ElrondApes has the JSON file linked under assets, while in my case we again have 2 assets, but both point to the image

Can it be that the metadata problem is because according to the docs, the metadata field should have the syntax: metadata:ipfsCID/fileName.json;tags:tag1,tag2,tag3, while in your contract the tags come before the metadata-statement?
So in your contract the syntax is: tags:tag1,tag2,tag3;metadata:ipfsCID/fileName.json, which is opposite to the docs

Elven tools smart contract doesn't add the json files to the assets/uris (at least not yet). The place for the metadata json file is in the NFT's attributes. It is base64 encoded there. The json in the assets is something custom to the marketplace. I have some more about it here: https://github.com/juliancwirko/elven-nft-minter-sc/issues/3
Regarding IPFS, what is essential is only the CID and elven tools smart contract ads the ipfs:// schema and additionally, the https://ipfs.io.ipfs/ gateway, which is the most popular, probably even not needed. You can use any ipfs gateway. This doesn't;t matter. What matters is your base CID. Check the: https://ipfs.github.io/public-gateway-checker/ there is a lot of them.

@juliancwirko so if I understood it correct, there is no need for a dedicated metadata file, because the metadata is already stored along with the NFT.
That leaves the question open for me, how can one query this metadata?

@juliancwirko Thank you so much.
I inserted my token identifier on the link you provided, got bWV0YWRhdGE6UW1WRHlKWHRGQlZYZW9iQ3p6dWRpNEFuS0tRUXJaVThzY29zalcyU0hHeTdnbi8yLmpzb24= as attribute, which base64-decoded gave me QmVDyJXtFBVXeobCzzudi4AnKKQQrZU8scosjW2SHGy7gn/2.json, the ipfs-link to my metadata.
In your second paragraph you were basically saying that in the next time, they will replace the base64-encoded path to my metadata with the actual metadata itself?

Yes, this is how it should work, but I checked it some time ago. There is quite a lot going on in the API service repository. I will add a to-do item to double-check it again to ensure that the metadata is created and other stuff, like media links, populated based on the nft's assets/uris. Some time ago, it was there immediately after nft creation, but they've added performance optimizations.

Thank you so much for all your help 🎉😄


Blockstack has a dependency that causes a vulnerability?

                       === npm audit security report ===

# Run  npm install<EMAIL_ADDRESS>to resolve 1 vulnerability
SEMVER WARNING: Recommended action is a potentially breaking change

  High            Regular Expression Denial of Service

  Package         minimatch

  Dependency of   blockstack

  Path            blockstack > hasprop > tape > glob > minimatch

  More info       https://nodesecurity.io/advisories/118

Any ideas?

This should be fixed in the 18.0.0 release.


Fix report scheduler timer_types

To reproduce the problem:

With non-English locale set, go to Cloud Intel -> Reports -> Schedules
Click 'Add a new schedule' in toolbar button
Change the schedule frequency to something else (Daily, Hourly, ...)

The timer_types submitted with the form must not be translated, otherwise the form submission
would fail for non-English locales:
HTTP parse error, malformed request (): #<Puma::HttpParserError:
Invalid HTTP format, parsing fails.>
...

The problem also shows in darga.


Add unit tests

We need to add unit tests to each and every thing that we have not yet.
Has been reported here https://github.com/surajssd/kapp/issues/24

IMO this is a practice that we should follow, and we're following right now. Let's continue that, and closing this since this is more of a meta/tracking issue.


MariaDB libs broken

[harsh@phoenix vcpkg]$ ./vcpkg install libmariadb
The following packages will be built and installed:
libmariadb[core]:x64-linux
Starting package 1/1: libmariadb:x64-linux
Building package libmariadb[core]:x64-linux...
-- Using cached /home/harsh/vcpkg/downloads/MariaDB-mariadb-connector-c-v3.0.2.tar.gz
-- Using source at /home/harsh/vcpkg/buildtrees/libmariadb/src/v3.0.2-283e8b69ee
-- Configuring x64-linux-dbg
-- Configuring x64-linux-rel
-- Building x64-linux-dbg
-- Building x64-linux-rel
CMake Error at ports/libmariadb/portfile.cmake:31 (file):
file RENAME failed to rename
/home/harsh/vcpkg/packages/libmariadb_x64-linux/lib/mariadb/mariadbclient.lib

to
/home/harsh/vcpkg/packages/libmariadb_x64-linux/lib/mariadbclient.lib

because: No such file or directory
Call Stack (most recent call first):
scripts/ports.cmake:71 (include)
Error: Building package libmariadb:x64-linux failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: libmariadb:x64-linux
Vcpkg version: 0.0.113-unknownhash

Running inside a docker image hived off from centos/devtoolset-7-toolchain-centos7:latest

*.lib = windows
ls /home/harsh/vcpkg/packages/libmariadb_x64-linux/lib

Duplicate of https://github.com/Microsoft/vcpkg/issues/3624

Thank you for posting this issue! it's a same issue with  https://github.com/Microsoft/vcpkg/issues/3624, so close it.


Can we pass url parameters for dashboards

I want to pass the parameters from the user to dashboard. According to the user inputs i want to visualize dashboard. Can you suggest how to do that.

I have the similar question, I could not find a clear and easy way to programmatically generate an iframe from the superset, or at least there is no such tutorials yet. We could either hack the iframe by passing parameters or hack the source code to provide our own api?

If my understanding is correct, you can do that via Flask RESTAPI
https://flask-appbuilder.readthedocs.io/en/latest/quickhowto.html#rest-api

@graceguo-supercat @williaster ^

@mistercrunch I want to trigger the query with the dashboard ui parameters. then want to visualize that query results.

Hi @Geetha-LMI for url parameters for dashboard, can you elaborate a little bit, what's input and expected results? What kind of customization you are looking for dashboard?

@Geetha-LMI Superset dashboard is a set of charts, in which each chart is a sql lab query. Dashboard can organize charts nicely (defined in position_json), add default filters, inline filters and immunes, add auto refresh (and other dashboard metadata). Do you want to create related charts by API, then add them into dashboard?

@graceguo-supercat  I want to pass the parameters to the sql lab query from the ui

Flow like: dashboard url parameters -> map to chart parameters -> generate sql lab query -> rendered in chart in dashboard?

@graceguo-supercat Yes

Hi..Was this functionality ever implemented in superset?

You might find the article Apache Superset — Use URL to filter dashboards useful.


No completions in REPL window when ES6 Mode is on

Using latest build from master (VS2015 U2, 6/11/2016)
Expected
REPL Window shows completions after . or Ctrl-Space
Actual
No completions are available

Duplicate of #916


Async: NLog is swallowing log messages, even with overflowAction="Block"

Hi, I opened this ticket with NLog-Project, but was not sure if the mis-configuration (or bug) was with NLog itself or with NLog.Extensions.AzureBlobStorage:
https://github.com/NLog/NLog/issues/4107
Does the extension swallow log messages even when overflowAction="Block"? Apologies if I am mis-configuring but I've read and tried everything that I can.
And please take no offense at "slow" - I mean slow as in over the network as opposed to local storage.
Colin

Because the AzureBlobStorage supports batching and retry, then it actually contains its own internal-queue. So no need to make use of the AsyncWrapper (Actually it will just introduce an overhead).
By default then its own internal-queue has overflowAction="Discard". As you can see from the documentation:
https://github.com/JDetmar/NLog.Extensions.AzureStorage/blob/master/src/NLog.Extensions.AzureBlobStorage/README.md
Maybe try this instead:
<nlog>

<extensions>
    <add assembly="NLog.Extensions.AzureBlobStorage" />
</extensions>

<variable name="commonLayout" value="${longdate:universalTime=True}|${pad:${uppercase:${level}}:padding=5:fixedLength=True}|${logger}|${machinename}|${appdomain}|[${threadname}(${threadid})] ${onexception:${newline}EXCEPTION\:${exception:format=tostring,Data:maxInnerExceptionLevel=10}}" />

<targets>
      <target xsi:type="AzureBlobStorage"
              name="AzureBlobStorage"
              overflowAction="Block"
              layout="${commonLayout}"
              connectionString="DefaultEndpointsProtocol=https;AccountName=blueduckops;AccountKey=(redacted);EndpointSuffix=core.windows.net"
              container="bkg-logs"
              blobName="${machinename}/${logger}/${date:universalTime=true:format=yyyy-MM-dd}/${date:universalTime=true:format=hh}.log" />
</targets>

<rules>
    <!-- These are very noisy and have been disabled with no writeTo -->
    <logger name="*" minlevel="Info" writeTo="AzureBlobStorage" />
</rules>

</nlog>

Thank you very much for explaining why I ran into the issues I did. This solved my problem!

Yes it is a new thing that the new NLog-targets that performs async network-writing includes their own internal AsyncWrapper-queue (Allowing them to better throttle and retry).
Happy that your issue was resolved.

@ColinNg If you have any advice out tuning the BatchSize and BlobName to handle the limit of 50.000 appends. Then please tell, then we can update the documentation for others to read.


[gdal] Update to 3.10.0

All features are tested successfully in the following triplet:
x86-windows
x64-windows
x64-windows-static


Error

Description
What steps will reproduce the problem?

What is the expected output? What do you see instead?
Please provide any additional information below
File "/Users/psotresc/anaconda3/lib/python3.6/site-packages/spyder/utils/introspection/plugin_client.py", line 158, in _on_finished
File "/Users/psotresc/anaconda3/lib/python3.6/site-packages/spyder/utils/introspection/plugin_client.py", line 104, in run
OSError: Could not start <spyder.utils.introspection.plugin_client.PluginClient object at 0x181964da68>
Traceback (most recent call last):
File "/Users/psotresc/anaconda3/lib/python3.6/site-packages/spyder/utils/introspection/plugin_client.py", line 158, in _on_finished
File "/Users/psotresc/anaconda3/lib/python3.6/site-packages/spyder/utils/introspection/plugin_client.py", line 104, in run
OSError: Could not start <spyder.utils.introspection.plugin_client.PluginClient object at 0x181964d678>
Version and main components

Spyder Version: 3.2.6
Python Version: 3.6.3
Qt Versions: 5.6.2, PyQt5 5.6 on Darwin

Dependencies
pyflakes >=0.6.0 :  1.6.0 (OK)
pycodestyle >=2.3:  2.3.1 (OK)
pygments >=2.0   :  2.2.0 (OK)
pandas >=0.13.1  :  0.22.0 (OK)
numpy >=1.7      :  1.13.3 (OK)
sphinx >=0.6.6   :  1.6.3 (OK)
rope >=0.9.4     :  0.10.5 (OK)
jedi >=0.9.0     :  0.10.2 (OK)
psutil >=0.3     :  5.4.0 (OK)
nbconvert >=4.0  :  5.3.1 (OK)
sympy >=0.7.3    :  1.1.1 (OK)
cython >=0.21    :  0.26.1 (OK)
qtconsole >=4.2.0:  4.3.1 (OK)
IPython >=4.0    :  6.1.0 (OK)
pylint >=0.25    :  1.7.4 (OK)

Please describe step by step how you got this error so we can reproduce it in our side. If you fail to do that, we'll close this issue in a week from now.
Also, please follow our
https://github.com/spyder-ide/spyder/wiki/Troubleshooting-Guide-and-FAQ
to see if it can solve your problem.

Closed due to lack of response. If you can provide more information, please re-open and do so. Thanks.


wget error from tutorial

I was starting to install higlass and tried to follow the instructions here to download a sample dataset
https://docs.higlass.io/tutorial.html#prerequisites
Alas, this yields a 403 error:
'''
$ wget https://data.4dnucleome.org/files-processed/4DNFI2A4OBS9/@@download/4DNFI2A4OBS9.mcool -O sample.mcool
</files-processed/4DNFI2A4OBS9/@@download/4DNFI2A4OBS9.mcool -O sample.mcool
--2021-11-01 23:09:55--  https://data.4dnucleome.org/files-processed/4DNFI2A4OBS9/@@download/4DNFI2A4OBS9.mcool
Resolving data.4dnucleome.org (data.4dnucleome.org)... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to data.4dnucleome.org (data.4dnucleome.org)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2021-11-01 23:09:56 ERROR 403: Forbidden.
'''

Oh, lovely. Here's another one you can use:
https://pkerp.s3.amazonaws.com/public/dixon2012-h1hesc-hindiii-allreps-filtered.1000kb.multires.cool
I'll fix the docs right now. Thanks for the heads up!

Just updated the docs.


add company name to import

the extension allows to extract title. any way to add current company name as well?

Hello awayand,
Thanks for using the extension and for the feedback.
It would be possible yes. I keep it in mind for next time I work on the extension.
Best,
Flo

Hi @awayand , following @varya pull request, I've pushed a new version that store company name from detail profile page. The new version is 1.0.3 and has been summited to Google Chrome store.
Best,
Florian

lovely, thanks a lot, @floriandiud and @varya


ci: use snapd from edge channel

Now that this PR: https://github.com/snapcore/snapd/pull/12061 is landed, snapd should permit the agent to read the kernel config from /boot/config*.
Marking as "Draft" for now until snapd releases properly.

Just waiting for the edge build to land for snapd and this should go green :crossed_fingers:

:tada: it worked!
The version of snapd currently is use in the CI pipeline is in edge and won't be on mainstream Ubuntu boxes for a couple of weeks. @kakkoyun up to you if you want to merge this now? I'm happy either way. I can keep this in draft until the release of snapd, or we can go for it.


pretty_music21

A preliminary pretty_midi-like read-only interface to music21.  Can be used to convert musicXML files into NoteSequence proto.

I signed it!

LGTM


Remove meta-title from MetaTags

Remove meta_title from meta tag collection in default installation and make it configurable.

Hello @salmantzo Whats the problem we are trying to solve with this? Also there are a few programming issues in the MR I've marked those

closing as not active


Resolve code scanning bug reports

Results from Sonatype Lift:
S1002
Fix rate: > 90%
should omit comparison to bool constant, can be simplified to requeue

 controllers/egeriaplatform_controller.go 130
 Staticcheck
Show Details
S1002
Fix rate: > 90%
should omit comparison to bool constant, can be simplified to requeue

 controllers/egeriaplatform_controller.go 121
 Staticcheck
Show Details
S1002
Fix rate: > 90%
should omit comparison to bool constant, can be simplified to requeue

 controllers/egeriaplatform_controller.go 88
 Staticcheck
Show Details
SA4006
Fix rate: > 90%
this value of requeue is never used

 controllers/egeriaplatform_controller.go 136
 Staticcheck
Show Details
G104
Fix rate: > 50%
Errors unhandled.

 controllers/egeriaplatform_controller.go 378
 GoSec
Show Details
G104
Fix rate: > 50%
Errors unhandled.

 controllers/egeriaplatform_controller.go 407
 GoSec
Show Details
ST1008
error should be returned as the last argument

 controllers/egeriaplatform_controller.go 278
 Staticcheck
Show Details
ST1008
error should be returned as the last argument

 controllers/egeriaplatform_controller.go 255
 Staticcheck
Show Details
ST1008
error should be returned as the last argument

 controllers/egeriaplatform_controller.go 243
 Staticcheck
Show Details
ST1008
error should be returned as the last argument

 controllers/egeriaplatform_controller.go 178
 Staticcheck
Show Details

See https://lift.sonatype.com/results/github.com/odpi/egeria-k8s-operator

All lift errors were recently fixed


Smallest Common Multiple

Challenge Name
Smallest Common Multiple
Issue Description
// noprotect -- >> Only with that line is working...
Browser Information

Browser Name, Version:
Operating System:
Mobile, Desktop, or Tablet:

Your Code
// noprotect

function smallestCommons(arr) {

  var tableTwoDimension = [] ;

  var minNum = Math.min(arr[0],arr[1]);
  var maxNum = Math.max(arr[0],arr[1]);

  var isLooping = true;
  var pos = maxNum;

  while(isLooping){

    var isWorking = false;

    for(var i=minNum;i<=maxNum;i++){

       if(pos%i === 0)
         isWorking = true;
        else {
          isWorking = false;
          break;
        }
    }

   if(isWorking)
    break;
    else pos++;

  }

  return pos;

}
smallestCommons([23,18]);

Screenshot

@CostasDev I'm not sure this is a bug. I'd consider it more of a feature of the code editor. It does its best to prevent infinite loops by preventing the callstack from being overloaded. I think since it notifies you of how to override it, it's fine as-is.

hi @dhcodes  but the question is correct only if i add the first line, otherwise is incorrect

@CostasDev I don't think it's incorrect without that line; it's just that the tests don't run without that line to protect users from a possible infinite loop browser crash if they didn't break the while loop eventually.

@CostasDev @dhcodes IIRC the loop-protect library has always been cautious about while loops.
As @dhcodes says, it's not that there is an issue with your code, or with the challenge, it's more to do with a cautious approach towards protecting you and your browser from infinite loops.
This is something that the developers of loop-protect recognised and have added the ability to disable loop protection with // no-protect, all be it at your own risk.

ok thank you very much guys for your response !!

Closing this for now. @CostasDev please reopen if you have more to discuss.


Add caching mechanism to model_eval and batch_eval

See if this fixes the issue where the tutorial gets slightly slower each epoch

As far as I can tell, there's not actually anything to cache in batch_eval.
model_eval builds the accuracy graph, but batch_eval uses a predefined graph. batch_eval_multi_worker builds the graph on several GPUs, but batch_eval doesn't build anything, it just uses a graph the user already built with their own GPU assignments.

I confirmed that this causes the tutorial slowdown. The fix drops the time per epoch of the tutorial on one GTX from 5.1 sec on epoch 10 to 4.75 sec, and there's no upward trend in time per epoch anymore.


StyleBoxTexture be always expanded to a texture size

Godot version
9937915ad77059b63582ffd4e324afb26f467b76
System information
Windows 11
Issue description
Even if I decrease a Sub-region property to 0, 0 it is expanded to a full size at runtime:

It should take the parent container size into account, but instead it expanded independently, which broke the UI used that style box.
It's broken after https://github.com/godotengine/godot/pull/71686 cc @YuriSizov
Steps to reproduce
Try to use StyleBoxTexture
Minimal reproduction project
TestSBTexture.zip

Thanks for reproducing this. My UI is quite broken in Beta 14/15 and this seems to be the cause.

Thanks for reproducing this. My UI is quite broken in Beta 14/15 and this seems to be the cause.

The cause for this is not in Beta 14, only Beta 15 has the relevant changes.

I've encountered an issue in beta 15 with ProgressBar controls using StyleBoxTexture for the bar fill that no longer size the bar correctly for low values but become correct as the bar is close to full. I'm guessing this bug is the cause, preventing the bars from being scaled smaller than the original texture size for the stylebox texture?

The PR wrongly assumed that get_center_size() had anything to do with stylebox's minimum size and the changes forced it as minimum size everywhere (including Controls that never cared about texture's size, like Button or PanelContainer, which explains all issues...).

 Why shouldn't all controls respect the region of the texture, if that's how the stylebox was set up? The problem was that controls that tried to respect the center bit ended up ignoring the min size. So it wasn't working correctly for them, not really.

We could add ignore_texture_size property to StyleBoxTexture, to allow shrinking past the texture's size.

Honestly, I can't find the reason for the existing logic. It tracks back to the pre-open-source days, and might be just a mistake or a carry-over from some old Juan's system. I think your initial hunch to remove the logic was correct, @Chaosus. Let me see if this breaks anything, and I'll make a PR that completely removes the override. If some stylebox doesn't look correctly after that change, it simply needs to adjust its margins to the expected value.
What could make sense to account for in the min size, is borders of the 9-patch mode. But that would be a completely new behavior, unrelated to any previously established or current logic.

Removing the min size override logic fixes your issue though.

My custom_min_size of all controls setted to zero or what you mean?

@YuriSizov So I've setted the sub-region property to zero in the inspector, and after the editor restarted - it's reverted to texture size - do you think it's OK?

The region is used to define which part of the texture to use, same thing as using an AtlasTexture. If you set it to zero then it doesn't make any sense, because that means you don't want any part of the texture to appear on the screen. That's what KoBeWi wanted to make implicitly okay with his PR. Either way, that's unrelated to the issue here. I've made my PR now.


ROS2 Foxy Docker Pointcloud Display Black

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues.
[X] This issue is not a question, feature request, or anything other than a bug report directly related to this project.

Description
When starting the Zed Mini camera from within Docker the published pointcloud returns a black image when visualized. Running ros2 topic hz /zedm/zed_node/point_cloud/cloud_registered shows that data is being sent:
root@3c1f21d12482:/app# ros2 topic hz /zedm/zed_node/point_cloud/cloud_registered
average rate: 10.002
	min: 0.094s max: 0.105s std dev: 0.00344s window: 11
average rate: 9.990
	min: 0.092s max: 0.109s std dev: 0.00372s window: 21
average rate: 9.987
	min: 0.092s max: 0.109s std dev: 0.00347s window: 31
average rate: 9.989
	min: 0.092s max: 0.109s std dev: 0.00343s window: 42
average rate: 10.002
	min: 0.092s max: 0.109s std dev: 0.00347s window: 53

and other topics, such as zedm/zed_node/rgb_raw/image_raw_color, work as intended. Setting QoS on my (python) subscriber, as mentioned here, in the following way
from rclpy.qos import QoSProfile, QoSReliabilityPolicy, QoSHistoryPolicy, DurabilityPolicy

self.qos_profile = QoSProfile(
    history=QoSHistoryPolicy.RMW_QOS_POLICY_HISTORY_KEEP_LAST,
    depth=1,
    reliability=QoSReliabilityPolicy.RMW_QOS_POLICY_RELIABILITY_RELIABLE,
    durability=DurabilityPolicy.RMW_QOS_POLICY_DURABILITY_VOLATILE
)

self.pcd_subscriber = self.create_subscription(
    PointCloud2,
    'zedm/zed_node/point_cloud/cloud_registered',
    self.listener_callback,
    self.qos_profile
)

does not help. Installing version v3.0.0 of the image_transport package via:
git clone https://github.com/ros-perception/image_common.git --branch 3.0.0 --single-branch

also didn't fix this and I have tried different lighting and distance settings.
My issue seems related to this discussion, which appears to be stale and I have not been able to find a solution. Any help would be greatly appreciated.
Steps to Reproduce

Build ROS2 Foxy Docker
Start Docker which will start the camera via ros2 launch zed_wrapper zedm.launch.py
Subscribe to /zedm/zed_node/point_cloud/cloud_registered
Visualize the PointCloud2 data (I use open3d)

Expected Result
Pointcloud being visualised correctly.
Actual Result
Black image with following data preview when inspecting topic:
root@7c0d23a6a14d:/app# ros2 topic echo /zedm/zed_node/point_cloud/cloud_registered
header:
  stamp:
    sec:<PHONE_NUMBER>
    nanosec: 560916346
  frame_id: zedm_left_camera_frame
height: 720
width: 1280
fields:
- name: x
  offset: 0
  datatype: 7
  count: 1
- name: y
  offset: 4
  datatype: 7
  count: 1
- name: z
  offset: 8
  datatype: 7
  count: 1
- name: rgb
  offset: 12
  datatype: 7
  count: 1
is_bigendian: false
point_step: 16
row_step: 20480
data:
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- 255
- 255
- 255
- 127
- '...'
is_dense: false
---

ZED Camera model
ZED Mini
Environment
OS: Ubuntu 20.04
GPU: NVIDIA GeForce RTX 3090 Ti
_Docker ARGs_
UBUNTU_RELEASE_YEAR=20
ZED_SDK_MAJOR=3
ZED_SDK_MINOR=8
CUDA_MAJOR=11
CUDA_MINOR=4
ROS_DISTRO=foxy

Anything else?
I'm using a slightly modified Docker script, as the original one did not work and I'm passing the GPU via Docker Compose.

    cd ~/ros2_ws
else
    mkdir -p ~/ros2_ws/src
    cd ~/ros2_ws/src/
    git clone https://github.com/ros-perception/image_common.git --branch 3.0.0 --single-branch
    git clone --recursive https://github.com/stereolabs/zed-ros2-wrapper.git
    cd ~/ros2_ws
    rosdep init
    rosdep update
    rosdep install --from-paths src --ignore-src -r -y
    colcon build --symlink-install --cmake-args=-DCMAKE_BUILD_TYPE=Release
fi

source install/local_setup.bash

ros2 launch zed_wrapper zedm.launch.py

@nfs-chris We provided Dockerfile files in the new docker folder, can you try the release version (you can adapt it to Foxy and Ubuntu 20 if you need).

Thank you for the docker files @Myzhar. Unfortunately, it seems the GPU is not picked up correctly:
[ZED][INFO] Logging level INFO
[zed_wrapper-2] in void sl::Mat::alloc(size_t, size_t, sl::MAT_TYPE, sl::MEM) : Err [804]: forward compatibility was attempted on non supported HW.
[zed_wrapper-2] No NVIDIA graphics card detected. Install an NVIDIA GPU, CUDA and restart your computer after completing installation.
[zed_wrapper-2] [WARN] [1675671033.258160341] [zedm.zed_node]: Error opening camera: NO GPU DETECTED

As other containers which are running on the same machine do detect the GPU, despite using the same parameters, there still seems to be an issue with how the image is built. I will investigate further and try out different parameters.

Are you using the correct commands to start the container?
The host device must have a CUDA capable NVIDIA GPU, NVIDIA docker support must be correctly installed and finally the correct commands must be used to start the container.
More info: https://www.stereolabs.com/docs/docker/

I am using docker compose up zedm with the following docker-compose.yml:
zedm:
  build:
    context: .
    dockerfile: zed_mini.Dockerfile
  devices:
    - /dev/bus/usb:/dev/bus/usb
    - /dev/dri:/dev/dri
    - /dev/nvidia0:/dev/nvidia0
    - /dev/nvidiactl:/dev/nvidiactl
    - /dev/nvidia-uvm:/dev/nvidia-uvm
  privileged: true
  volumes:
    - /dev/shm:/dev/shm
    - /tmp/.X11-unix:/tmp/.X11-unix
    - /usr/lib/nvidia-470:/usr/lib/nvidia-470
  environment:
    - DISPLAY=$DISPLAY
  deploy:
    resources:
      reservations:
        devices:
          - driver: nvidia
             count: 1
             capabilities: [gpu]

To check if the GPU is available I run nvidia-smi before running the ros2 command to start the zed mini:
echo "Starting Zed Mini..."
# setup ros2 environment
source "/opt/ros/$ROS_DISTRO/setup.bash" --
source "/root/ros2_ws/install/local_setup.bash" --

# Welcome information
echo "ZED ROS2 Docker Image"
echo "---------------------"
echo 'ROS distro: ' $ROS_DISTRO
echo 'DDS middleware: ' $RMW_IMPLEMENTATION
echo "---"
echo 'Available ZED packages:'
ros2 pkg list | grep zed
echo "---------------------"

nvidia-smi
ros2 launch zed_wrapper zedm.launch.py

which gives the expected output:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.161.03   Driver Version: 470.161.03   CUDA Version: 11.7     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:01:00.0  On |                  Off |
|  0%   32C    P8    19W / 450W |    384MiB / 24253MiB |      8%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
+-----------------------------------------------------------------------------+

but then crashes with the previously mentioned error about no GPU being detected.

Hello,
you  may miss a few things in his compose file
services:
  your_awesome_service:
    runtime: nvidia
    environment:
      - NVIDIA_DRIVER_CAPABILITIES=all
    privileged: true

Can you try these ?

Hi, I am following the official docs which can be found here, setting the runtime and driver capabilities accordingly (and this works for other setups I use). privileged: true is also set, as you can see from my previous post.

Can you update your nvidia driver ? it's quite old, maybe it's getting compatibility issues.
515 version (sudo apt install nvidia-driver-515) would do the trick.


lug, mirror-intel: add GitHub release support

https://github.com/tuna/issues/issues/1087
https://github.com/tuna/issues/issues/1113
https://github.com/tuna/issues/issues/1060

https://github.com/tuna/issues/issues/1087
https://github.com/tuna/issues/issues/1113
https://github.com/tuna/issues/issues/1060


Adds kubectl logo to repository

Adds kubectl logo images in three sizes (full, medium, and small)
The full size is 3182x3200
The medium size is 300x300
The small size is 200x200
Includes the medium logo into the README.md

/assign

/lgtm
/approve


Website title become URL in Chrome for iOS

When I click any link at website, the title become URL:

Hi there,
This is still happening in the latest (and many previous builds) when going from the page to any subsequent pages in a tab. It only seems to happen on iPad (mine is a retina Mini 2 on iOS8).
Any ideas?


This makes the links stick to the word beforehand, we should probably revert that:

          This makes the links stick to the word beforehand, we should probably revert that:

Originally posted by @chingucoding in https://github.com/microsoft/WinUI-Gallery/pull/1294#discussion_r1222735405

Thank you for mentioning this again, gladly before merging the PR that was fixed and the issue is not present on the main branch.


Application Suspend and Resume Events Callback

When an application moves to the background, it is often appropriate for it to stop updating.  I'm currently using the window focus callback function for this purpose as a workaround since I have only single window, but a callback to indicate when the application moves to the foreground or the background would be better solution.

Application focus doesn't exist on all platforms. You can track whether any of your windows currently has focus by saving the last state passed to the window focus callback, as defocus events are always sent before focus events.

Thank you for letting me know.  I was surprised that this wasn't already included in GLFW since GLFW seems so well designed, so this clarifies it.  Is this also the reason that joystick events are not included, because they are not supported on all platforms?

Joystick events exist on all platforms but not all their APIs.

I see.
Have you considered simulating joystick events?  When a joystick is first connected, you could poll the joystick's state initially and send axis moved events for each non-zero axis value and joystick button down events for each button that's pressed.  Later, when the user calls glfwPollEvents (I'm not clear on the timing issues involved with glfwWaitEvents), you could poll the joystick's state again and send events for each joystick value that has changed.  It may not be as accurate as receiving actual events from the OS, but it still should be the equivalent of what people are doing now.
This would also probably be an easy way to do a proof of concept for joystick event callbacks.  And it might also be an easy way to do a first release of joystick event functionality.  You could then add OS-based support for platforms with APIs that do support joystick events, and continue to use the event simulation on platforms where the APIs don't support joystick events.


Consider using crates.io/crates/xrl?

Hey Raph,
I've been working on xrl  trying to get it ready to start working on my front end over the next couple of months, but i'd like to see Xrl used by as many front ends as possible, at least the one's written in rust. I found in my early experience's with Xi writing the Update logic to be a bit tedious and error prone. Xrl handle's all of that logic(or it will after my PR is accepted) just requiring the user to pass a 'Update' to there line cache and Xrl handle's it appropriately. Multiple front ends using xrl would reduce duplication of work throughout the Xi community.
It is already in use by little-dude/xi-tui and i plan on having my front end bytebuddha/Zen running by the end of this year(cant work on it until then, I've got a busy couple of months ), so i'm looking for smaller project's in the Xi ecosystem to work on in my free time.
I chose to try and convert xi-win first because:
- It is small
- Not much development going on at the moment
- It's written in rust
- As far as i know Xrl has never been tested on any OS other than Linux and i would prefer to get testing on both Mac & Windows.
So with that in mind a have a few question's:

What do you think of using Xrl as a common library for xi front ends
- If not why?
Is xi-win in to early a stage to switch to using xrl?
Have you ever thought about a seperate(or internal in the xi repo?) library to handle all of xi-core front end protocol? (from a front ends point of view)
- If you have could you share your thoughts on it?

Thank you so much for creating Xi, I've found it to be the perfect project to play with in my free time and has taught me alot!

@bytebuddha Development has been picking up a little, and I expect to be contributing rather regularly to xi-win from now on. If you'd like to join us @ zulip, you're more than welcome to. :) There's a budding community there, with representatives from several front-ends.

@LiHRaM I signed up, Thanks!


Invalid regex clears the screen

Bug Description
When an invalid regex is entered such as "*" without quotes, everything (plots and top bar) disappears.
Reproduction Steps
Enter steps to reproduce the behavior:

Display an environment with plots
Type "*" into filter box without quotes.
Only a blue screen remains.
Refresh, the window is still blank.
Clear cookies.
Window is visible again.

Client logs:
react-dom.min.js?v=950495cc51ccb90612cf0fe0bb44f8f3:162 SyntaxError: Invalid regular expression: /*/: Nothing to repeat
at String.match ()
at main.js?v=3261b9e7369b15bddd67dcef356a4655:35
at Array.map ()
at t.value (main.js?v=3261b9e7369b15bddd67dcef356a4655:35)
at h (react-dom.min.js?v=950495cc51ccb90612cf0fe0bb44f8f3:130)
at beginWork (react-dom.min.js?v=950495cc51ccb90612cf0fe0bb44f8f3:134)
at d (react-dom.min.js?v=950495cc51ccb90612cf0fe0bb44f8f3:158)
at f (react-dom.min.js?v=950495cc51ccb90612cf0fe0bb44f8f3:159)
at g (react-dom.min.js?v=950495cc51ccb90612cf0fe0bb44f8f3:159)
at t (react-dom.min.js?v=950495cc51ccb90612cf0fe0bb44f8f3:167)
I don't know if regex is handled in the server or the client so I can't make a suggestion to fix. Any ideas?

Ah thanks for the flag - this bug happens in the JS in two locations:
https://github.com/facebookresearch/visdom/blob/master/js/main.js#L1150
https://github.com/facebookresearch/visdom/blob/master/js/main.js#L539
Before checking filter, we should be ensuring that filter is valid


Extract parquet statistics from Interval columns

Is your feature request related to a problem or challenge?
Part of https://github.com/apache/datafusion/issues/10453, where we are filling out support for extracting statistics for all data types from parquet files
At the moment, even if statistics are extracted for a different type (like Int32) the PruningPredicate will attempt to cast these values to the correct type:
https://github.com/apache/datafusion/blob/acd7106fa40fad58f50ae06227971c51073d8f48/datafusion/core/src/physical_optimizer/pruning.rs#L909-L911
However, in order to be efficient and ensure the cast kernel doesn't add anything incorrectly, we should be extracting the parquet statistics as the correct Array type directly. It turns out we do not do this yet for several types and those types do not have good (or any) test coverage. We almost missed this in https://github.com/apache/datafusion/pull/10711 in @xinlifoobar
Thus, we need to add support and tests for other types
Describe the solution you'd like

Add a new test to arrow_stastics.rs (run this with cargo test --test parquet_exec) with the relevant type
Potentially add a new case to the match here https://github.com/apache/datafusion/blob/acd7106fa40fad58f50ae06227971c51073d8f48/datafusion/core/src/datasource/physical_plan/parquet/statistics.rs#L61-L182  to get the correct types

Here are some example PRs:

https://github.com/apache/datafusion/pull/10729
https://github.com/apache/datafusion/pull/10593

Describe alternatives you've considered
No response
Additional context
No response

take

...while looking into this I noticed, that there are no statistics written for an Interval, which is also described here.
@alamb I guess we can't extract any statistics here? And writing any tests that check we have no statistics written, does not seem to be very helpful?

@alamb I guess we can't extract any statistics here? And writing any tests that check we have no statistics written, does not seem to be very helpful?

I actually think these would be helpful then as soon as there are statistics we can hook them up to the tests. If you had time to write the tests that would be great. We can then perhaps file a ticket in parquet-rs for supporting writing statistics to interval types.

I did some digging in order to find out why / or where the writing of those statistics is not supported (yet).
Since I'm not familiar with the parquet impl, here are my findings, which might be useful in a follow-up ticket in arrow-rs.

When trying to fn write_slice() the min, max values are never updated due to a filter-condition; that checks if the type is INTERVAL
In order to support updating the min max values, we need to handle the comparison of INTERVAL here

I think this should be possible, or put differently, I don't see the reason yet, why this is not supported?
Somethin similar (comparing FixedLenByteArrays) is already done for DECIMAL here?
Perhaps, you have some more information on this @alamb - otherwise this might be enough information to file a ticket in arrow-rs?


documentation docker-compose pull: does it pull incremental or everything?

File: compose/reference/pull.md, CC @gbarr01
I just searched on the web for docker-compose pull, because I wanted to figure out, if the command downloads only updated data, or every time everything from scratch. https://docs.docker.com/compose/reference/pull/ was the first result, but I did not find enough information to confirm my assumptions about the command. Would it be possible to add a bit more details?
Does the command download all data from scratch, or only missing / updated data?

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!


feat(rust): implement wire protocol codec for ockam messages

rebased and merged https://github.com/ockam-network/ockam/commit/127a595a3d98e62901c69859b1a5299fad8a45b8

#276 251


Could not autowire. No beans of 'IncidentApi' type found.

When using Spring rest client api when inject IncidentApi there is error :

and Spring boot is unable to boot
I am currently using 7.20.4 version and Spring boot 3.1.7

The same problem on Spring Boot 3.2.4. Does it work on Spring Boot 3 then? Indeed, I do not see the required annotations on the ProcessDefinitionApi class, for example. It seems that defining a @Configuration with corresponding bean factory methods solves this particular issue.

Does this work with 7.20.5?
If not, I will have to dig deeper as the artefacts should contain the spring boot 3 style autoconfiguration.imports

It's simply missing in CamundaApi.
One workaround is to add it manually in class annotated with Configuration:
@Bean     public IncidentApi incidentApi() {         return new IncidentApi(apiClient);     }


Update rstudio.rb

Can you please update the commit message from the default GH one to mention the app being updated and the version. i.e
"Rstudio 0.99.447"

done

Thanks :+1:


azure.servicebus.aio.ServiceBusClient hangs when sending too many batches concurrently

Package Name: azure-servicebus - azure.servicebus.aio.ServiceBusClient
Package Version: 7.2.0
Operating System: MacOS
Python Version: 3.8

Describe the bug
When sending many batches concurrently in an asyncio.gather, the async ServiceBus client seems to hang.
To Reproduce
Steps to reproduce the behavior:
Create many full batches of messages:
# Create a lot of messages to send
to_send = [
    azure.servicebus.ServiceBusMessage(
        json.dumps({"some_fake_message": i})
    )
    for i in range(200_000)
]

# Create a bunch of full batches out of those messages (my ServiceBus batch size limit is 262,144 bytes)
batches = []
batch = await sender.create_message_batch()
for i in to_send:
    try:
        batch.add_message(i)
    except Exception as e:
        # Can't actually find this exception in the SDK - hacky workaround to catch the right error
        if type(e).__qualname__ != "MessageSizeExceededError":
            raise
        batches.append(batch)
        batch = await sender.create_message_batch()

# Catch the last batch at the end
if len(batch):
    batches.append(batch)

Then, send the batches concurrently and it should hang:
await asyncio.gather(*[sender.send_messages(batch) for batch in batches])

Sending the batches in series succeeds for me, taking around 320 seconds:
for batch in batches:
    await sender.send_messages(batch)

Expected behavior
Sending batches concurrently should work without hanging, and ideally the concurrency should give some performance benefit over sending in series due to the improved use of CPU while waiting on network IO.

hey @michaelcredera , thanks for the reaching out and sharing the code with me.
I'll try to reproduce it locally.
I also feel it's is related to the issue here: https://github.com/Azure/azure-sdk-for-python/issues/14903 -- The service has restriction on the amount of messages in a batch which is being accepted.

The code above fills the batch until the max size is reached - so maybe this is a bug in that API?

I tried to reproduce the issue using the code you provided. I did hit issue, while it's not the program hanging but an error is raised, and after I turned on the logging via, I find that it's the service being throttled.
INFO:uamqp.c_uamqp:b'<- [DISPOSITION]* {true,3,NULL,true,* {* {com.microsoft:server-busy,The request was terminated because the namespace t1sbtest is being throttled. Error code : 50009. Please wait 2 seconds and try again. To know more visit https://aka.ms/sbResourceMgrExceptions

I think we're hitting the quotas defined by the service, could you check if it's the same issue happening in your case?
You could turn on the logging via:
import logging
logging.basicConfig(level=logging.INFO)
client = ServiceBusClient(..., logging_enable=True)

(and after digging a while, I think it's not related to the message amount issue I previously referenced, apologize for misleading you)

Mine hangs still, but logs a different error:
import asyncio

import azure.servicebus.aio
import azure.servicebus.exceptions

to_send = [
    azure.servicebus.ServiceBusMessage(
        json.dumps({"some_fake_message": i})
    )
    for i in range(200_000)
]
logging.basicConfig(level=logging.INFO)
logging.getLogger("uamqp").setLevel(logging.DEBUG)

conn = ""
queue_name = ""
client = azure.servicebus.aio.ServiceBusClient.from_connection_string(conn, logging_enable=True)
sender = client.get_queue_sender(queue_name)

# Create a bunch of full batches out of those messages (my ServiceBus batch size limit is 262,144 bytes)
batches = []
batch = await sender.create_message_batch()
for i in to_send:
    try:
        batch.add_message(i)
    except Exception as e:
        # Can't actually find this exception in the SDK - hacky workaround to catch the right error
        if type(e).__qualname__ != "MessageSizeExceededError":
            raise
        batches.append(batch)
        batch = await sender.create_message_batch()
        batch.add_message(i)

# Catch the last batch at the end
if len(batch):
    batches.append(batch)
await asyncio.gather(*[sender.send_messages(batch) for batch in batches])

Logs:
ConnectionClose('ErrorCodes.UnknownError: Connection in an unexpected error state.')
... (repeated)
ConnectionClose('ErrorCodes.UnknownError: Connection in an unexpected error state.')

Queue stats:

Hi @michaelcredera, thank you very much for your patience on this! I was finally able to reproduce the ErrorCodes.UnknownError after creating a servicebus namespace and queue with your configurations.  Error code : 50009. Please
wait 2 seconds and try again. To know more visit https://aka.ms/sbResourceMgrExceptions TrackingId:f91a540c000004810050cce2611beb63_G0_B6, SystemTracker:swathip-test-servicebus:Queue:servicebus-test-queue, Timestamp:2021-08-17T17:02:44,NULL}},NULL}'
INFO:uamqp.c_uamqp:b'-> [TRANSFER]* {2,72,<48 00 00 00>,2147563264,false,true}'
INFO:uamqp.c_uamqp:b'-> [TRANSFER]* {2,72,<48 00 00 00>,2147563264,false,true}'
INFO:uamqp.c_uamqp:b'-> [TRANSFER]* {2,72,<48 00 00 00>,2147563264,false,true}'
INFO:uamqp.c_uamqp:b'-> [TRANSFER]* {2,72,<48 00 00 00>,2147563264,false,true}'
INFO:uamqp.c_uamqp:b'-> [TRANSFER]* {2,72,<48 00 00 00>,2147563264,false,true}'
INFO:uamqp.c_uamqp:b'-> [TRANSFER]* {2,72,<48 00 00 00>,2147563264,false,true}'
INFO:uamqp.c_uamqp:b'-> [TRANSFER]* {2,72,<48 00 00 00>,2147563264,false,true}'
INFO:uamqp.c_uamqp:b'-> [TRANSFER]* {2,72,<48 00 00 00>,2147563264,false,true}'
INFO:uamqp.c_uamqp:b'-> [TRANSFER]* {2,72,<48 00 00 00>,2147563264,false,true}'
INFO:uamqp.c_uamqp:b'-> [TRANSFER]* {2,72,<48 00 00 00>,2147563264,false,true}'
INFO:uamqp.c_uamqp:b'-> [TRANSFER]* {2,72,<48 00 00 00>,2147563264,false,true}'
INFO:uamqp.c_uamqp:b'-> [TRANSFER]* {2,72,<48 00 00 00>,2147563264,false,true}'
INFO:uamqp.c_uamqp:b'-> [TRANSFER]* {2,72,<48 00 00 00>,2147563264,false,true}'
INFO:uamqp.c_uamqp:b'-> [TRANSFER]* {2,72,<48 00 00 00>,2147563264,false,false}'
INFO:uamqp.async_ops.client_async:Client told to backoff - sleeping for 4 seconds
INFO:uamqp.c_uamqp:b'<- [DISPOSITION]* {true,56,NULL,true,* {* {amqp:internal-error,The service was unable to process the request; please retry the operation. For more information on exception types and proper
exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 Reference:62c5190f-6fc9-4d92-8b8f-537ce7d138c2, TrackingId:f91a540c000004810050cce2611beb63_G0_B6, SystemTracker:swathip-test-servicebus:Queue:servicebus-test-queue, Timestamp:2021-08-17T17:02:44,NULL}},NULL}'
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.InternalServerError: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 Reference:62c5190f-6fc9-4d92-8b8f-537ce7d138c2, TrackingId:f91a540c000004810050cce2611beb63_G0_B6, SystemTracker:swathip-test-servicebus:Queue:servicebus-test-queue, Timestamp:2021-08-17T17:02:44')
INFO:uamqp.c_uamqp:b'<- [DISPOSITION]* {true,55,NULL,true,* {* {com.microsoft:server-busy,The request was terminated because the namespace swathip-test-servicebus is being throttled. Error code : 50009. Please
wait 2 seconds and try again. To know more visit https://aka.ms/sbResourceMgrExceptions TrackingId:f91a540c000004810050cce2611beb63_G0_B6, SystemTracker:swathip-test-servicebus:Queue:servicebus-test-queue, Timestamp:2021-08-17T17:02:44,NULL}},NULL}'
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageException('com.microsoft:server-busy: The request was terminated because the namespace swathip-test-servicebus is being throttled. Error code
: 50009. Please wait 2 seconds and try again. To know more visit https://aka.ms/sbResourceMgrExceptions TrackingId:f91a540c000004810050cce2611beb63_G0_B6, SystemTracker:swathip-test-servicebus:Queue:servicebus-test-queue, Timestamp:2021-08-17T17:02:44')
INFO:uamqp.c_uamqp:b'<- [DISPOSITION]* {true,58,NULL,true,* {* {amqp:internal-error,The service was unable to process the request; please retry the operation. For more information on exception types and proper
exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 Reference:ff0b02ae-0a36-4806-b69e-bc3729e3b3ec, TrackingId:f91a540c000004810050cce2611beb63_G0_B6, SystemTracker:swathip-test-servicebus:Queue:servicebus-test-queue, Timestamp:2021-08-17T17:02:45,NULL}},NULL}'
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.InternalServerError: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 Reference:ff0b02ae-0a36-4806-b69e-bc3729e3b3ec, TrackingId:f91a540c000004810050cce2611beb63_G0_B6, SystemTracker:swathip-test-servicebus:Queue:servicebus-test-queue, Timestamp:2021-08-17T17:02:45')
INFO:uamqp.c_uamqp:b'<- [DISPOSITION]* {true,57,NULL,true,* {* {com.microsoft:server-busy,The request was terminated because the namespace swathip-test-servicebus is being throttled. Error code : 50009. Please
wait 2 seconds and try again. To know more visit https://aka.ms/sbResourceMgrExceptions TrackingId:f91a540c000004810050cce2611beb63_G0_B6, SystemTracker:swathip-test-servicebus:Queue:servicebus-test-queue, Timestamp:2021-08-17T17:02:45,NULL}},NULL}'
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageException('com.microsoft:server-busy: The request was terminated because the namespace swathip-test-servicebus is being throttled. Error code
: 50009. Please wait 2 seconds and try again. To know more visit https://aka.ms/sbResourceMgrExceptions TrackingId:f91a540c000004810050cce2611beb63_G0_B6, SystemTracker:swathip-test-servicebus:Queue:servicebus-test-queue, Timestamp:2021-08-17T17:02:45')
INFO:uamqp.c_uamqp:b'<- [DISPOSITION]* {true,59,NULL,true,* {* {com.microsoft:server-busy,The request was terminated because the namespace swathip-test-servicebus is being throttled. Error code : 50009. Please
wait 2 seconds and try again. To know more visit https://aka.ms/sbResourceMgrExceptions TrackingId:f91a540c000004810050cce2611beb63_G0_B6, SystemTracker:swathip-test-servicebus:Queue:servicebus-test-queue, Timestamp:2021-08-17T17:02:47,NULL}},NULL}'
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageException('com.microsoft:server-busy: The request was terminated because the namespace swathip-test-servicebus is being throttled. Error code
: 50009. Please wait 2 seconds and try again. To know more visit https://aka.ms/sbResourceMgrExceptions TrackingId:f91a540c000004810050cce2611beb63_G0_B6, SystemTracker:swathip-test-servicebus:Queue:servicebus-test-queue, Timestamp:2021-08-17T17:02:47')
INFO:azure.servicebus.aio._base_handler_async:AMQP error occurred: (ClientMessageError('ErrorCodes.InternalServerError: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 Reference:62c5190f-6fc9-4d92-8b8f-537ce7d138c2, TrackingId:f91a540c000004810050cce2611beb63_G0_B6, SystemTracker:swathip-test-servicebus:Queue:servicebus-test-queue, Timestamp:2021-08-17T17:02:44')), condition: (<ErrorCodes.InternalServerError: b'amqp:internal-error'>), description: (b'The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 Reference:62c5190f-6fc9-4d92-8b8f-537ce7d138c2, TrackingId:f91a540c000004810050cce2611beb63_G0_B6, SystemTracker:swathip-test-servicebus:Queue:servicebus-test-queue, Timestamp:2021-08-17T17:02:44').
INFO:uamqp.sender:Message sender b'sender-link-ccbfe44b-07df-404f-80d3-1608f1b33813' state changed from <MessageSenderState.Open: 3> to <MessageSenderState.Closing: 4> on connection: b'SBSender-dca3eb48-5404-4117-bc08-dd45fb12eaf3'
INFO:uamqp.c_uamqp:b'-> [DETACH]* {2,true}'
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.UnknownError')
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.UnknownError')
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.UnknownError')
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.UnknownError')
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.UnknownError')
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.UnknownError')
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.UnknownError')
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.UnknownError')
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.UnknownError')
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.UnknownError')
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.UnknownError')
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.UnknownError')
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.UnknownError')
INFO:uamqp.async_ops.client_async:Client told to backoff - sleeping for 4 seconds
INFO:uamqp.async_ops.client_async:Client told to backoff - sleeping for 4 seconds
INFO:uamqp.async_ops.client_async:Client told to backoff - sleeping for 4 seconds
INFO:uamqp.async_ops.client_async:Client told to backoff - sleeping for 4 seconds
INFO:uamqp.async_ops.client_async:Client told to backoff - sleeping for 4 seconds
INFO:uamqp.async_ops.client_async:Client told to backoff - sleeping for 4 seconds
INFO:uamqp.async_ops.client_async:Client told to backoff - sleeping for 4 seconds
INFO:uamqp.async_ops.client_async:Client told to backoff - sleeping for 4 seconds
INFO:uamqp.async_ops.client_async:Client told to backoff - sleeping for 4 seconds
INFO:uamqp.async_ops.client_async:Client told to backoff - sleeping for 4 seconds
INFO:uamqp.async_ops.client_async:Client told to backoff - sleeping for 4 seconds
INFO:uamqp.async_ops.client_async:Client told to backoff - sleeping for 4 seconds
INFO:uamqp.sender:Message sender b'sender-link-5d85f436-bfb6-4be0-940d-72a72f945ec6' state changed from <MessageSenderState.Idle: 1> to <MessageSenderState.Opening: 2> on connection: b'SBSender-dca3eb48-5404-4117-bc08-dd45fb12eaf3'
INFO:uamqp.c_uamqp:b'-> [ATTACH]* {sender-link-5d85f436-bfb6-4be0-940d-72a72f945ec6,3,false,0,1,* {SBSender-dca3eb48-5404-4117-bc08-dd45fb12eaf3},* {amqps://swathip-test-servicebus.servicebus.windows.net/servicebus-test-queue},NULL,NULL,0,1048576}'
INFO:uamqp.async_ops.client_async:CBS session pending b'SBSender-dca3eb48-5404-4117-bc08-dd45fb12eaf3'.
INFO:uamqp.async_ops.client_async:Closing exclusive connection b'SBSender-dca3eb48-5404-4117-bc08-dd45fb12eaf3'.
INFO:azure.servicebus.aio._base_handler_async:AMQP error occurred: (ClientMessageError('ErrorCodes.UnknownError')), condition: (<ErrorCodes.UnknownError: b'amqp:unknown-error'>), description: (None).
INFO:uamqp.sender:Message sender b'sender-link-5d85f436-bfb6-4be0-940d-72a72f945ec6' state changed from <MessageSenderState.Opening: 2> to <MessageSenderState.Closing: 4> on connection: b'SBSender-dca3eb48-5404-4117-bc08-dd45fb12eaf3'
INFO:uamqp.c_uamqp:b'-> [DETACH]* {3,true}'
INFO:uamqp.sender:Message sender b'sender-link-5d85f436-bfb6-4be0-940d-72a72f945ec6' state changed from <MessageSenderState.Closing: 4> to <MessageSenderState.Idle: 1> on connection: b'SBSender-dca3eb48-5404-4117-bc08-dd45fb12eaf3'
Traceback (most recent call last):
  File "c:\users\swathip\documents\forks\azure-sdk-for-python\sdk\servicebus\azure-servicebus\azure\servicebus\aio\_base_handler_async.py",
line 246, in _do_retryable_operation
    return await operation(**kwargs)
  File "c:\users\swathip\documents\forks\azure-sdk-for-python\sdk\servicebus\azure-servicebus\azure\servicebus\aio\_servicebus_sender_async.py", line 198, in _send
    await self._handler.send_message_async(message.message)
  File "C:\Users\swathip\Documents\env39\lib\site-packages\uamqp\async_ops\client_async.py", line 651, in send_message_async
    raise errors.ClientMessageError(exception, info=details)
uamqp.errors.ClientMessageError: ErrorCodes.UnknownError

Ultimately, it looks like this final error that is being raised is the UnknownError that you encountered, along with the Connection being closed. However, in my log, it shows that the original reason for this error seems to be that the service is being throttled with the following error, as was mentioned previously by @yunhaoling:
Error: MessageException('com.microsoft:server-busy: The request was terminated because the namespace swathip-test-servicebus is being throttled. Error code
: 50009. Please wait 2 seconds and try again...)

Would you be able to copy and paste a larger snippet of your error logging? This would help us determine whether the service is being throttled and whether that is the original error that leads to the UnknownError in your case as well.
I modified your code a little bit:
import os
import asyncio
import json
import logging
from azure.servicebus import ServiceBusMessage
from azure.servicebus.aio import ServiceBusClient

logging.basicConfig(level=logging.INFO)
#logging.getLogger("uamqp").setLevel(logging.DEBUG)
CONNECTION_STR = os.environ['SERVICE_BUS_CONNECTION_STR']
QUEUE_NAME = os.environ["SERVICE_BUS_QUEUE_NAME"]

async def main():
   servicebus_client = ServiceBusClient.from_connection_string(conn_str=CONNECTION_STR, logging_enable=True)

   async with servicebus_client:
       sender = servicebus_client.get_queue_sender(queue_name=QUEUE_NAME)
       # Create a lot of messages to send
       to_send = [
           ServiceBusMessage(
               json.dumps({"some_fake_message": i})
           )
           for i in range(200_000)
       ]

       # Create a bunch of full batches out of those messages (my ServiceBus batch size limit is 262,144 bytes)
       batches = []
       batch = await sender.create_message_batch()
       for i in to_send:
           try:
               batch.add_message(i)
           except Exception as e:
                # Can't actually find this exception in the SDK - hacky workaround to catch the right error
               if type(e).__qualname__ != "MessageSizeExceededError":
                   raise
               batches.append(batch)
               batch = await sender.create_message_batch()

       # Catch the last batch at the end
       if len(batch):
           batches.append(batch)

       await asyncio.gather(*[sender.send_messages(batch) for batch in batches])

   print("Send message is done.")

loop = asyncio.get_event_loop()
loop.run_until_complete(main())

(If throttling is the reason for you as well, it seems like our error messages do not provide adequate information - I apologize for that! We will update our exception handling to provide more details ASAP!)

Hey @swathipil, nice find! I'll try with your code and see if I can get the same error message.

The below snippet shows my logs with your script - My reading of this log is that connections get throttled until something (race condition?) causes the client to reach an inconsistent state in its error handling. The 500/internal server errors are interesting mixed in with the throttling errors. It's also interesting that the coroutines are all competing with each other.
One thought in addition to a logging change - maybe this is something that could be helped with a semaphore based on the throttling threshold so that the client doesn't unintentionally spam the server? I'm not sure if this would be easy to implement, because the size of the semaphore would need to be determined by the throttling limit of the server, and the send_messages method would need to be able to take up a certain amount of the semaphore depending on the batch size. It could also impact performance for some applications to add in the overhead of locking / releasing every time we send a message.
class ThrottlingSemaphore(asyncio.Semaphore):
    async def acquire(self, count: int = 1):
        # Silly, surely a more performant way to implement this if it's not in a library already...
        for _ in range(count):
            await super().acquire()
    async def release(self, count: int = 1):
        for _ in range(count):
            await super().release()

class ServiceBusSender:
    async def _open(self):
        ...
        max_size = ... # Something based on the server throttling limit?
        self._throttling_semaphore = ThrottlingSemaphore(max_size)

    async def send_messages(self, message: Union[...]):
        to_lock = # Something to get the semaphore batch size based on the message size?
        try:
            await self._throttling_semaphore.acquire(to_lock)
            ...
        finally:
            await self._throttling_semaphore.release(to_lock)

Anyways, I really appreciate you both looking into this!
INFO:azure.servicebus.aio._base_handler_async:AMQP error occurred: (ClientMessageError('com.microsoft:server-busy: The request was terminated because the namespace dev-atticus is being throttled. Error code : 50009. Please wait 2 seconds and try again. To know more visit https://aka.ms/sbResourceMgrExceptions TrackingId:bb9c89d9000005b90157140661264e50_G52_B8, SystemTracker:dev-atticus:Queue:test-scrapeerror, Timestamp:2021-08-25T14:07:21')), condition: (b'com.microsoft:server-busy'), description: (b'The request was terminated because the namespace dev-atticus is being throttled. Error code : 50009. Please wait 2 seconds and try again. To know more visit https://aka.ms/sbResourceMgrExceptions TrackingId:bb9c89d9000005b90157140661264e50_G52_B8, SystemTracker:dev-atticus:Queue:test-scrapeerror, Timestamp:2021-08-25T14:07:21').
INFO:uamqp.c_uamqp:b'<- [DISPOSITION]* {true,193,NULL,true,* {},NULL}'
INFO:uamqp.c_uamqp:b'<- [DISPOSITION]* {true,194,NULL,true,* {* {com.microsoft:server-busy,The request was terminated because the namespace dev-atticus is being throttled. Error code : 50009. Please wait 2 seconds and try again. To know more visit https://aka.ms/sbResourceMgrExceptions TrackingId:bb9c89d9000005b90157140661264e50_G52_B8, SystemTracker:dev-atticus:Queue:test-scrapeerror, Timestamp:2021-08-25T14:07:24,NULL}},NULL}'
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageException('com.microsoft:server-busy: The request was terminated because the namespace dev-atticus is being throttled. Error code : 50009. Please wait 2 seconds and try again. To know more visit https://aka.ms/sbResourceMgrExceptions TrackingId:bb9c89d9000005b90157140661264e50_G52_B8, SystemTracker:dev-atticus:Queue:test-scrapeerror, Timestamp:2021-08-25T14:07:24')
INFO:uamqp.c_uamqp:b'-> [TRANSFER]* {2,239,<EF 00 00 00>,2147563264,false,true}'
INFO:uamqp.c_uamqp:b'-> [TRANSFER]* {2,239,<EF 00 00 00>,2147563264,false,false}'
[repeated]
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.InternalServerError: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 Reference:52ee3166-2bd8-4c22-9210-293328dba9c3, TrackingId:bb9c89d9000005b90157140661264e50_G52_B8, SystemTracker:dev-atticus:Queue:test-scrapeerror, Timestamp:2021-08-25T14:07:25')
INFO:azure.servicebus.aio._base_handler_async:AMQP error occurred: (ClientMessageError('ErrorCodes.InternalServerError: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 Reference:52ee3166-2bd8-4c22-9210-293328dba9c3, TrackingId:bb9c89d9000005b90157140661264e50_G52_B8, SystemTracker:dev-atticus:Queue:test-scrapeerror, Timestamp:2021-08-25T14:07:25')), condition: (<ErrorCodes.InternalServerError: b'amqp:internal-error'>), description: (b'The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 Reference:52ee3166-2bd8-4c22-9210-293328dba9c3, TrackingId:bb9c89d9000005b90157140661264e50_G52_B8, SystemTracker:dev-atticus:Queue:test-scrapeerror, Timestamp:2021-08-25T14:07:25').
INFO:uamqp.sender:Message sender b'sender-link-b8d400f9-a237-4a1d-812b-233e8708f8db' state changed from <MessageSenderState.Open: 3> to <MessageSenderState.Closing: 4> on connection: b'SBSender-0452459c-427d-481c-9c65-46bae864afd1'
INFO:uamqp.c_uamqp:b'-> [DETACH]* {2,true}'
INFO:uamqp.client:Message error, 3 retries exhausted. Error: MessageSendFailed('ErrorCodes.UnknownError')
[repeated]
INFO:uamqp.sender:Message sender b'sender-link-b94978d7-3570-4605-a478-84d5c25b0f47' state changed from <MessageSenderState.Idle: 1> to <MessageSenderState.Opening: 2> on connection: b'SBSender-0452459c-427d-481c-9c65-46bae864afd1'
INFO:uamqp.c_uamqp:b'-> [ATTACH]* {sender-link-b94978d7-3570-4605-a478-84d5c25b0f47,3,false,0,1,* {SBSender-0452459c-427d-481c-9c65-46bae864afd1},* {amqps://dev-atticus.servicebus.windows.net/test-scrapeerror},NULL,NULL,0,1048576}'
INFO:azure.servicebus.aio._base_handler_async:AMQP error occurred: (ClientMessageError('ErrorCodes.UnknownError')), condition: (<ErrorCodes.UnknownError: b'amqp:unknown-error'>), description: (None).
INFO:uamqp.sender:Message sender b'sender-link-b94978d7-3570-4605-a478-84d5c25b0f47' state changed from <MessageSenderState.Opening: 2> to <MessageSenderState.Closing: 4> on connection: b'SBSender-0452459c-427d-481c-9c65-46bae864afd1'
INFO:uamqp.c_uamqp:b'-> [DETACH]* {3,true}'
INFO:uamqp.sender:Message sender b'sender-link-b94978d7-3570-4605-a478-84d5c25b0f47' state changed from <MessageSenderState.Closing: 4> to <MessageSenderState.Idle: 1> on connection: b'SBSender-0452459c-427d-481c-9c65-46bae864afd1'
INFO:uamqp.c_uamqp:b'Bad parameters: message_sender=0x0, message=0x7fb2fed4cc00, on_message_send_complete=0x101728a80, callback_context=0x1248d8cd0, timeout=0' (b'/Users/runner/work/1/s/src/vendor/azure-uamqp-c/src/message_sender.c':b'messagesender_send_async':1011)
INFO:uamqp.c_uamqp:Send operation result is NULL
INFO:uamqp.async_ops.client_async:Message not sent, raising RuntimeError.
INFO:azure.servicebus.aio._base_handler_async:AMQP error occurred: (ClientMessageError('ErrorCodes.UnknownError')), condition: (<ErrorCodes.UnknownError: b'amqp:unknown-error'>), description: (None).
INFO:azure.servicebus.aio._base_handler_async:AMQP error occurred: (ClientMessageError('ErrorCodes.UnknownError')), condition: (<ErrorCodes.UnknownError: b'amqp:unknown-error'>), description: (None).
INFO:uamqp.client:Message error, 3 retries exhausted. Error: ClientMessageError("ErrorCodes.ClientError: 'NoneType' object has no attribute 'send_async'")
INFO:uamqp.client:Message error, 3 retries exhausted. Error: ClientMessageError("ErrorCodes.ClientError: 'NoneType' object has no attribute 'send_async'")
INFO:uamqp.client:Message error, 3 retries exhausted. Error: ClientMessageError("ErrorCodes.ClientError: 'NoneType' object has no attribute 'send_async'")
INFO:uamqp.client:Message error, 3 retries exhausted. Error: ClientMessageError("ErrorCodes.ClientError: 'NoneType' object has no attribute 'send_async'")
INFO:azure.servicebus.aio._base_handler_async:AMQP error occurred: (ClientMessageError('ErrorCodes.UnknownError')), condition: (<ErrorCodes.UnknownError: b'amqp:unknown-error'>), description: (None).
INFO:azure.servicebus.aio._base_handler_async:AMQP error occurred: (ClientMessageError('ErrorCodes.UnknownError')), condition: (<ErrorCodes.UnknownError: b'amqp:unknown-error'>), description: (None).
INFO:azure.servicebus.aio._base_handler_async:AMQP error occurred: (ClientMessageError('ErrorCodes.UnknownError')), condition: (<ErrorCodes.UnknownError: b'amqp:unknown-error'>), description: (None).
INFO:azure.servicebus.aio._base_handler_async:AMQP error occurred: (ClientMessageError('ErrorCodes.UnknownError')), condition: (<ErrorCodes.UnknownError: b'amqp:unknown-error'>), description: (None).
INFO:azure.servicebus.aio._base_handler_async:AMQP error occurred: (ClientMessageError('ErrorCodes.InternalServerError: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 Reference:52ee3166-2bd8-4c22-9210-293328dba9c3, TrackingId:bb9c89d9000005b90157140661264e50_G52_B8, SystemTracker:dev-atticus:Queue:test-scrapeerror, Timestamp:2021-08-25T14:07:25')), condition: (<ErrorCodes.InternalServerError: b'amqp:internal-error'>), description: (b'The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 Reference:52ee3166-2bd8-4c22-9210-293328dba9c3, TrackingId:bb9c89d9000005b90157140661264e50_G52_B8, SystemTracker:dev-atticus:Queue:test-scrapeerror, Timestamp:2021-08-25T14:07:25').
INFO:azure.servicebus.aio._base_handler_async:AMQP error occurred: (ClientMessageError('ErrorCodes.UnknownError')), condition: (<ErrorCodes.UnknownError: b'amqp:unknown-error'>), description: (None).
[repeated]
INFO:uamqp.async_ops.client_async:CBS session pending b'SBSender-0452459c-427d-481c-9c65-46bae864afd1'.
INFO:uamqp.async_ops.client_async:Closing exclusive connection b'SBSender-0452459c-427d-481c-9c65-46bae864afd1'.
Traceback (most recent call last):
  File "/Users/michael.mehrtens/dev/azure-sdk-for-python/sdk/servicebus/azure-servicebus/azure/servicebus/aio/_base_handler_async.py", line 246, in _do_retryable_operation
    return await operation(**kwargs)
  File "/Users/michael.mehrtens/dev/azure-sdk-for-python/sdk/servicebus/azure-servicebus/azure/servicebus/aio/_servicebus_sender_async.py", line 198, in _send
    await self._handler.send_message_async(message.message)
  File "/Users/michael.mehrtens/envs/default/lib/python3.8/site-packages/uamqp/async_ops/client_async.py", line 651, in send_message_async
    raise errors.ClientMessageError(exception, info=details)
uamqp.errors.ClientMessageError: ErrorCodes.UnknownError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "scripts/large_batch.py", line 53, in <module>
    loop.run_until_complete(main())
  File "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "scripts/large_batch.py", line 47, in main
    await asyncio.gather(*[sender.send_messages(batch) for batch in batches])
  File "/Users/michael.mehrtens/dev/azure-sdk-for-python/sdk/servicebus/azure-servicebus/azure/servicebus/aio/_servicebus_sender_async.py", line 358, in send_messages
    await self._do_retryable_operation(
  File "/Users/michael.mehrtens/dev/azure-sdk-for-python/sdk/servicebus/azure-servicebus/azure/servicebus/aio/_base_handler_async.py", line 250, in _do_retryable_operation
    last_exception = await self._handle_exception(exception)
  File "/Users/michael.mehrtens/dev/azure-sdk-for-python/sdk/servicebus/azure-servicebus/azure/servicebus/aio/_base_handler_async.py", line 198, in _handle_exception
    raise error
azure.servicebus.exceptions.ServiceBusError: Service Bus has encountered an error. Error condition: ErrorCodes.UnknownError.
Error in sys.excepthook:

Original exception was:

@michaelcredera - Thanks for your thoughts + snippets on this! When I get a chance, I plan on doing some more investigation on the race condition and semaphores to see whether this is feasible (Issue #20523). In the meantime, can we close this issue? (It looks like you might already have a solution of iterating through the batches. However, I want to make sure we prioritize this issue if it is blocking you.)
Thanks!