Ambiguous error when uploading ES modules without the entitlement

🐛 Bug report

Describe the bug
When running wrangler dev or wrangler publish, it throws 403 Forbidden error.
Reproduce the bug
A list of steps to reproduce the bug.

Clone https://github.com/cloudflare/modules-rollup-esm (official example)
Install dependencies, modify package.json name, add account_id to wrangler.toml.
Run wrangler dev
See error:

$> wrangler dev
...
src/index.mjs → dist/index.mjs...
created dist/index.mjs in 223ms
Error: HTTP status client error (403 Forbidden) for url (https://api.cloudflare.com/client/v4/accounts/<account-id>/workers/scripts/custom-build-test/edge-preview)

$> wrangler publish
...
src/index.mjs → dist/index.mjs...
created dist/index.mjs in 214ms
✨  Build completed successfully!
Error: Something went wrong! Status: 403 Forbidden, Details {
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 10015,
      "message": "workers.api.error.not_entitled"
    }
  ],
  "messages": []
}

Expected behavior
Should build and deploy, but it fails in the deploy.
Environment and versions
Fill out the following information about your environment.

operating system: MacOS Catalina 10.15.7
output of wrangler -V: wrangler 1.16.0
output of node -v: v14.16.1
content of wrangler.toml:

It's literally like the example (hiding account id here):
name = "custom-build-test"
# type = "javascript" is required to use the `[build]` section
type = "javascript"
account_id = "<account_id>"
workers_dev = true
route = ""
zone_id = ""

[build]
command = "npm run build"
upload.format = "modules"
upload.main = "./index.mjs"

Thanks for reporting this. To get around this, you should signup your account for the Durable Objects open beta. Go to the Workers section of the dashboard, and you'll see a tab for "Durable Objects"
Soon, we will remove this restriction, but before then we should clarify the error message. So I'll keep this open

@Electroid related question, it says Durable Objects is only available while you are on the Workers Bundled plan. and, even though I'm on paid plan, I'm basically making open source and I assume most people don't have a paid account.
Will the custom builds (without DO) be available with free plans after the restriction you mention is removed?

@Electroid related question, it says Durable Objects is only available while you are on the Workers Bundled plan. and, even though I'm on paid plan, I'm basically making open source and I assume most people don't have a paid account.
Will the custom builds (without DO) be available with free plans after the restriction you mention is removed?

@frandiox If I understand correctly: you enabled Unbound, but when you try to sign up for Durable Objects it won't let you with that error?

@Electroid Ah no, I haven't enabled Unbound. I'm in a workers bundled plan (the one that is $5/mo) and that seems to be working well after enabling Durable Objects.
The message I wrote in my previous post is not an error, but a warning when enabling DO in the dashboard. Basically my question is, will the "custom builds" feature be available only for paid plans, or also for free plans? Thanks!

Custom builds are available for all plans, free and paid. :) It's only ES modules, that for now, you'll need to be in the Durable Objects beta. Soon, that will no longer be a requirement.


Support for prismatic joint

Hi,
I'm wondering if joint of type "prismatic", defined as "a sliding joint that slides along the axis, and has a limited range specified by the upper and lower limits" are supported. I don't find on the code any behavior attached to that join, although I see it's used on the Panda and Fetch robot models: https://github.com/facebookresearch/differentiable-robot-model/search?q=prismatic
Cheers,
Marcelo

Hi,
I am also wondering the same i.e if the current robot model supports prismatic joints? Also, is it possible to use it for floating base systems?
Best,
Mohak


Update README.md for the proof test

This project is no longer active. I suggest using TFJS instead.


Import the Ebnf code

I have written most of the code in another project that sparked this one.

Migrated from BitBucket.


add minimum supported version to Travis

So I know a lot of people use the nightly and a lot of people always run the latest stable rust. But there's some of us out there that will get stuck on a stable release for a few months due complexities in build environments, breakages moving forward, etc.
For all my crates I try to include the following in .travis-ci.yml so that there's a minimum supported version:
rust:
- nightly
- beta
- stable
- 1.4.0

Its fine to raise that level up as needed but its helpful to ensure that a "stable" series (e.g. 0.6.x) remains compatible with the same version of Rust or if it needs to be bumped up people can understand how they need to update.

Seems like the latest supported version is the 1.8. However, it uses a feature from the latest stable. https://travis-ci.org/brson/error-chain/jobs/180998245#L286-L306. The modification in lib.rs is easy, the one in error_chain.rs less easy.

Thank you. No matter the version its a welcome addition for me.


[RFR] Feature/deep linking accordions

@Koded - I am intensely aware that the Toggle component is getting a little bit FATTY - for actual production I would bring the functionality and pass it down through props or rather have it in the container.


UTF8/Unicode issue with < Delphi 2009

Bugreport: Wrong function definition leads to a loss of widestring information.
function Get: string;overload;
begin
    ...
    Result := UTF8Decode(...);
end;

UTF8Decode returns a widestring, function returns a string. All non charset-character-information is lost. This error occurs on following functions:
function Get: string;overload;
function Post(Content: TStream): string;overload;
function Post(Content: string): string;overload;
function Put(Content: TStream): string;overload;
function Put(Content: string): string;overload;
function Patch(Content: TStream): string;overload;
function Patch(Content: string): string;overload;

I've temporarily changed the return type from string to widestring to solve this issue.

Thanks for the report.
String means different things between different versions of Delphi, so, is a mess.
I am not so sure that the widestring is the right type here (for all delphi versions). Maybe is better to use compiler directives in this case.
What do you think?

Yes I think so, too.
I think that type string became a unicode string type by default since Delphi 2009. If you can confirm this I could add compiler directives.
option 1:
function TResource.Get: {$IFDEF DELPHI_2009_UP}string{$ELSE}Widestring{$ENDIF};
begin
  Result := FRestClient.DoRequest(METHOD_GET, Self);
end;

option 2:
{$IFDEF DELPHI_2009_UP}
function TResource.Get: String
{$ELSE}
function TResource.Get: Widestring
{$ENDIF};
begin
  Result := FRestClient.DoRequest(METHOD_GET, Self);
end;

option 3:
{$IFDEF DELPHI_2009_UP}function TResource.Get: String{$ELSE}function TResource.Get: Widestring{$ENDIF};
begin
  Result := FRestClient.DoRequest(METHOD_GET, Self);
end;

1.) Should I sent you a pull request?
2.) Which option do you prefer?

I'm not sure about that, but I guess that string is a widestring type in some 2009+ versions of delphi, and it is UnicodeString in the latest versions.  But it doesn't matter. Your solution will solve the problem anyway.

I prefer the first option, less code duplication. I hope we have more opinions from the other members. :)

Absolutely. You can write a test for this problem?

Why not define the string type using defines and use it the need of defines inside the class. This way you can use it for all other routines to!!!
type
{$IFDEF DELPHI_2009_UP}
RestString = String
{$ELSE}
RestString = WideString
{$ENDIF}

TResource = class(...)
...
  function Get: RestString;
...
end;

function TResource.Get: RestString
begin
  Result := FRestClient.DoRequest(METHOD_GET, Self);
end;

much better @ronaldhoek :+1:

@ronaldhoek: very nice solution!
@RobertoSchneiders: I'll do it in the way @ronaldhoek suggested. You'll hearing from me soon.

@ronaldhoek  :+1:
SuperObject use the way below, then don't depend of a specific compiler directive or be aware at which delphi version includes unicode support.
{$if (sizeof(Char) = 1)}
  RestString = WideString;
{$else}
  RestString = string;
{$ifend}

Ah, sorry about that - it was just a copy-paste from some unit I knew it was in...
BTW: starting with the unicode versions of Delphi, the define 'UICODE' was introduces.
So you can also use {$IFDEF UNICODE} instead off {$if (sizeof(Char) = 1)}

Looks better use  {$IFDEF UNICODE}


Docs - clarify the terms for client-gateway-backend TLS hops (use edge/backend rather than downstream/upstream)

Followup to https://github.com/kubernetes-sigs/gateway-api/pull/2547#pullrequestreview-1706707215 and https://github.com/kubernetes-sigs/gateway-api/pull/2493#discussion_r1373724118

Wrong repo.


K8SPXC-473: change current stored version

Make current version as stored version in crd.yaml

PXC operator docker - perconalab/percona-xtradb-cluster-operator:PR-609-f77af89b

Test name
Status

recreate
passed

storage
passed

big-data
passed

haproxy
passed

scaling
passed

init-deploy
passed

self-healing
passed

scaling-proxysql
passed

upgrade
passed

restore-to-encrypted-cluster
passed

limits
passed

self-healing-advanced
passed

upgrade-consistency
passed

monitoring
passed

security-context
passed

operator-self-healing
passed

demand-backup
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

scheduled-backup
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

demand-backup-encrypted-with-tls
passed

tls-issue-cert-manager-ref
passed


Improve JSON processing in CLI by allowing file input

Reported by @nauerz-ibm
Also, users found an error passing data FROM a JS action INTO a Swift action. JSON that is perfectly valid was failing when passed from a Swift action into a JSON action. The JSON contained a single quote within a double quote, and once the single quote was removed, then it worked as expected.

For example:

This failed (part of a larger JSON array):

{rating:"3.5",name:”Bally's Las Vegas",lat:"36.113579",city:"Las Vegas",lon:"-115.172792",price:"117"}

Changing to this succeeded:

{rating:"3.5",name:”Ballys Las Vegas",lat:"36.113579",city:"Las Vegas",lon:"-115.172792",price:"117"}

The only difference is the removal of a single quote from Bally's in the name field, which worked without issue.

Why is this a CLI issue?

Because it's a problem an user hit using the CLI
After reading closely I think this one it's an user error of not escaping the single quote in shell or cmd
I think there nothing the CLI can do to fix it but we can discuss here how to improve it
Brainstorm:
Passing JSON in terminal for simple things works fine but for complex strings it's not that good, what I did in another project I did a CLI was to have a flag in the CLI   to pass a JSON file containing the a json object with the information that the user would pass in terminal instead so you can pass the params as args or as a file input

I would generalize this issue then to have better support for sending JSON - eg you cannot now send a top level json as in wsk action invoke /whisk.system/samples/greeting '{"name":"..."}'.

Yep I agree more generic way to send json in CLI I just need help from someone deciphering original bug report 😬

This has bugged me for a while too. I'll take a stab at it.

@psuter go ahead and do it on go-CLI branch take a look at WIP PR

Postponed in light of the Go CLI progress.

@csantanapr, looks like there are two different issues here. One is adding JSON file input support. The other is passing JSON to the CLI. Both the provided JSON strings are invalid as there are not quotes around the key values. The single quote bug is fixed in the Go CLI. I will ignore the invalid JSON pieces here, and use the issue to track the file input enhancements.

@csantanapr, here's what I had in mind for the new flags.
filename points to a file containing JSON content.
wsk action create actionName artifactName -pf keyName filename
wsk action create actionName artifactName -paramFile keyName filename
wsk action create actionName artifactName -af keyName filename
wsk action create actionName artifactName -annotationFile keyName filename

@dubeejw yes that was the agreement to use this issue to track enhancement to the Go CLI to allow user to pass JSON data by file.
I think starting with parameters and annotations would be a good start.
I was thinking on having it more generic and simpler one file for all parameters, one file for all annotations, not one file per parameter or annotation.
For example:
wsk action create actionName artifactName -pf filename
wsk action create actionName artifactName -paramfile filename
filename =
{
   "param1":"param1_value",
   "param2":"param2_value"
}

Params, and annotations take two values. One is a name, and the other is a value. Where the value can be JSON. This is why I recommend the second argument be a file name. Existing commands look like the following:
wsk action create actionName artifactName -param paramName "{\"key\": \"value\"}"

Yes I'm aware how it works today, that's why I want JSON file not work in the same and work in a better way.
Wow that sounded like a riddle 😄

 -p, --param KEY VALUE        default action parameter values in KEY VALUE format (default [])

@dubeejw Now I'm confuse, the CLI usage says that its --param key value not -param paramName "{"key": "value"}"

Anyway have a JSON with the keys and the values is what I'm proposing. And we can still keep composition if you think is something we can do also like
wsk action invoke -pf fileparamset1.json -p anotherp pvalue -pf fileparamset2.json
I say for first stab MVP to support a simple use case first.

The key is just a name for that parameter, it isn't JSON.

If we want to provide the ability to create parameters and annotations via wsk action create actionName artifactName -pf params.json -af annots.json we will need to update the database schema.

as a transition step, the CLI could remap the JSON to the required schema. These two features can be added separately.

Not sure that parsing the user provided JSON the way we need it for the key/value fields will be possible in Go since it is a strongly-typed language. We are thinking about having the user input from a file be what is sent directly to the REST interface. For example, a file could contain this JSON {"paramKey": "paramValue"}, which would be forwarded to the backend. With our current functionality that would be the equivalent of passing -p paramKey paramValue, which would be converted to {"key": "paramKey", "value": "paramValue"} before sent to the backend.

Forgive my ignorance - below is my first go code. If we read a JSON object and then can separate the key and value pairs, I don't see why the mapping can't happen entirely in the CLI for now.
package main

import "encoding/json"
import "fmt"

func main() {
    bytes := []byte(`{"a":"A","b":["B","C"]}`)
    var data map[string]interface{}
    if err := json.Unmarshal(bytes, &data); err != nil {
        panic(err)
    }
    fmt.Println(data)

    keys := make([]string, len(data))
    values := make([]interface{}, len(data))

    i := 0
    for k, v := range data {
       keys[i] = k
       values[i] = v
       i++
    }

    fmt.Println(keys)
    fmt.Println(values)
}

> go run main.go
map[a:A b:[B C]]
[a b]
[A [B C]]

@rabbah, yes I was able to achieve the above. From here we need to add the key/value labels, then encode the JSON back into a struct.

Added key/value labels and encoded the JSON. Will have to test to see if we can go further with this example.

import "encoding/json"
import "fmt"

type KeyValue struct {
    Key  string 	`json:"key"`
    Value interface{}	`json:"value"`
}

func main() {
    bytes := []byte(`{"a":"A","b":["B","C"], "testBool": false}`)
    var data map[string]interface{}
    if err := json.Unmarshal(bytes, &data); err != nil {
        panic(err)
    }

    keys := make([]string, len(data))
    values := make([]interface{}, len(data))

    i := 0
    for k, v := range data {
       keys[i] = k
       values[i] = v

	keyValue := KeyValue{
		Key:  keys[i],
		Value: values[i],

    	}

       p, _ := json.Marshal(keyValue)
       s := string(p)
       fmt.Println("str " + s)

       i++
    }
}```


[Feature Request] Add additional debug information for Triton Error [CUDA]: device kernel image is invalid

Hello, I've come across a few issues (from both the torch.compile and Triton sides) related to the Triton Error [CUDA]: device kernel image is invalid.
As a newcomer, I'm finding it challenging to debug this problem. Would you mind guiding me through the common root cause of this issue and refining the check logic with more detailed bug information to offer better insights for solving it?
I would greatly appreciate your help :)

This seems to be related to the version of the CUDA driver. Have you tried upgrading the CUDA driver to a higher version?

Hey @Li-dongyang, thanks for your assistance. What's the minimum version required? Also, are there any docs regarding the compatibility of CUDA driver versions with Triton versions?

For my configuration (triton 2.2.0, cuda 12.2, nvcc 11.8 on A100), this error is resolved by upgrading the nvidia driver from 470.57.02 to 535.104.05.
the minimum version required by cuda and cuda toolkit could be checked on https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html
I’m sorry I know nothing about the compatibility of CUDA driver versions with Triton versions, and I can’t guarantee that my method works for everyone. 🤦♂It seems that the triton team has not provided any information about this issue and note of minimum version except this:
https://github.com/openai/triton/blob/055ef627fce76290d6622c5700810ad53e0c43ca/README.md?plain=1#L160C12-L167C14

Triton uses a very recent ptxas.
You can point to the ptxas version that works for your driver by setting TRITON_PTXAS_PATH

upgrading the nvidia driver

could you give a link about how to upgrade driver

upgrading the nvidia driver

could you give a link about how to upgrade driver
there is solution in the follow issue
https://github.com/openai/triton/issues/1955#issuecomment-1929908209

upgrading the nvidia driver

could you give a link about how to upgrade driver
there is solution in the follow issue
#1955 (comment)

Thanks for your guidance; it works for me!

I faced the same error in the cuda 11.x environment and could resolve it with pip install triton==2.1.0. it's easier than the source build so I think it's a good first step to manage to fix the error.

I faced the same error in the cuda 11.x environment and could resolve it with pip install triton==2.1.0. it's easier than the source build so I think it's a good first step to manage to fix the error.

Thanks, it works.

I faced the same error in the cuda 11.x environment and could resolve it with pip install triton==2.1.0. it's easier than the source build so I think it's a good first step to manage to fix the error.

Thanks,when encountering this issue, the method you provided proves to be faster and more convenient!


mixpanel.track mutates attributes

You can decide whether or not you consider this a bug, but I thought I'd at least post it here.
We have some code that calls mixpanel.track with a second argument (event attributes). After this call, the attributes have been mutated.
const attrs = { foo: 1 };
mixpanel.track('some-event', attrs);
console.log(attrs);
// => {foo: 1, token: "6f39bdxyxy2345xyzyxf341a058dd2ce5e87f"}

This came as a gotcha to me, and I think it would be better if you left the attributes alone.

Duplicate of https://github.com/mixpanel/mixpanel-js/issues/107, please add any discussion there, thanks.


Expand unit testing of command tasks

Some of the new command tasks e.g. those added by #45, are a little more awkward to unit test.  We ought to expand the testing a little to cope better with them - something like a Mock object to stand-in for subprocess or similar

Closed by #49


platformio-ide-terminal no longer installs on new Atom version 1.52.0

[ ] I have reset Atom to defaults prior to submitting report.
[x ] I have not reset Atom to defaults prior to submitting report.

Description

platformio-ide-terminal stops working on new Atom (1.52.0).
Steps to reproduce

i updated Atom
platformio-ide-terminal threw an installation error (error messages below)

Expected behavior:
platformio-ide-terminal should have kept on working
Actual behavior:
error message upon install:
Installing<EMAIL_ADDRESS>failed.Hide output…

<EMAIL_ADDRESS>install /private/var/folders/4g/4wpmdzbd7tj0cwctcd99wz680000gp/T/apm-install-dir-2020919-88197-l99pqc.upj2e/node_modules/platformio-ide-terminal/node_modules/node-pty-prebuilt-multiarch
prebuild-install || node scripts/install.js

prebuild-install WARN install No prebuilt binaries found (target=6.1.12 runtime=electron arch=x64 libc= platform=darwin)
No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.
No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.
No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.
gyp: No Xcode or CLT version detected!
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
gyp ERR! stack     at ChildProcess.emit (events.js:200:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Darwin 19.6.0
gyp ERR! command "/Applications/Atom.app/Contents/Resources/app/apm/bin/node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /private/var/folders/4g/4wpmdzbd7tj0cwctcd99wz680000gp/T/apm-install-dir-2020919-88197-l99pqc.upj2e/node_modules/platformio-ide-terminal/node_modules/node-pty-prebuilt-multiarch
gyp ERR! node -v v12.4.0
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
npm WARN enoent ENOENT: no such file or directory, open '/private/var/folders/4g/4wpmdzbd7tj0cwctcd99wz680000gp/T/apm-install-dir-2020919-88197-l99pqc.upj2e/package.json'
npm WARN apm-install-dir-2020919-88197-l99pqc.upj2e No description
npm WARN apm-install-dir-2020919-88197-l99pqc.upj2e No repository field.
npm WARN apm-install-dir-2020919-88197-l99pqc.upj2e No README data
npm WARN apm-install-dir-2020919-88197-l99pqc.upj2e No license field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: prebuild-install || node scripts/install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/Negorashi2011/.atom/.apm/_logs/2020-10-19T07_10_06_974Z-debug.log`
Reproduces how often:
always
Versions

> atom --version
Atom    : 1.52.0
Electron: 6.1.12
Chrome  : 76.0.3809.146
Node    : 12.4.0

> apm --version
apm  2.5.2
npm  6.14.8
node 12.4.0 x64
atom 1.52.0
python 3.8.3
git 2.28.0

OS name and version: macOS 10.15.7
Platformio-ide-terminal version: 2.10.0
Additional Information

Although the error message says that macOS CLT cannot be found, i have CLT installed.
I installed XCode. Same error message.

same problem here

same here

same

Same here. My favorite terminal stopped working a few days ago and cannot be reinstalled. Any news or clues to solve it?

me too
please see issue #543
https://github.com/platformio/platformio-atom-ide-terminal/issues/543

https://atom.io/packages/terminus seems to be working, if anyone is looking for a quick alternative

Terminus works!
If you want to use ctrl-enter instead of ctrl-i to insert selected text (i.e. to send a command from a text file into the terminal and run it), add this command to the end of your keymap.cson file:
'atom-workspace atom-text-editor:not([mini])': 'ctrl-enter': 'terminus:insert-selected-text'
the keymap.cson file is opened by going to Atom/Keymap...

Same here

same issue

same issue

Same issue here

I was able to get this to work by rebuilding the package. I made sure that I had Xcode installed. (I had to launch Xcode in order to complete the installation. Then I:

uninstalled Platform-IDE-Terminal
Quit and restarted Atom
Re-installed Platform-IDE-Terminal
Quit and restarted Atom
Clicked on the little red ladybug in the lower-right status bar.
Clicked on the "Rebuild Package" button to rebuild Platform-IDE-Terminal
Quit and restarted Atom

Back in action!

https://atom.io/packages/terminus


Check the exit code from the server process

Check the exit code from the server, and make the test suite fail if non-zero.
Should work for master and 1_1_0-stable

@bernd-edlinger - I tried to merge this but our git hooks threw an error. The git author field is listed with your hotmail email address. In our CLA database this is registered against both the CCLA for your employer and against your personal ICLA...so we can't tell which one is in use for submissions from this email address. Can you clarify? Should submissions from your hotmail address be treated as personal or from your employer? If the latter it is probably better to use a corporate email address in the author field.

Oh, sorry.
It hardly makes any difference to me, I was asked to sign an ICLA too, so I did it.
This is due to the new policy at https://www.openssl.org/policies/cla.html
requiring both a CCLA and a ICLA, so this is probably a new use case,
that is not yet correctly understood by your git hook.
Also note, that the author e-mail is just whatever I write in .git/config/[user]/email,
Only the github account "bernd-edlinger" is actually authenticated (with a password).

I see. It does however make a difference to us. We want to ensure we have a clear understanding about who is making a submission (an individual or an entity). To make that as simple as possible we prefer to have a different email used for corporate submissions vs individual submissions. To fix this I need to modify our database so that your hotmail address only appears against one of your CLAs. So just to be clear: who is making this submission? You, or your employer?

Ok, then please modify the database so that my hotmail account refers to my ICLA.

Sorry for hijacking this pull request, but ... if the email address has to be associated with at most one of the ICLA and CCLA, then how is the ICLA requirement going to be enforced for CCLA contributions?  I don't want to submit an ICLA with my work email address on it if it's going to break things...

Merged.
master: 57a19206b5aad7ca67f0d5ebae05af2799609819
1.1.0: 408eb66aea74b5dfe52386f7a8756bd81b890a26


Update uk-tax-mtd.md

fix note

OPS Build status updates of commit c0a3544:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit c0a3544:
:clock10: Incremental building: average incremental building time is 25 sec(s)

OPS Build status updates of commit c0a3544:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamics-gp/financials/uk-tax-mtd.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


pcie: devicetree: Add helper macros

At the moment PCIE BDF is hacked into REG_ADDR and PCIE ID is hacked into REG_SIZE. Add those macros so that the code looks readable.
Fixes: #26109

Shouldn't you also add an include statement to the bottom of include/zephyr/devicetree.h?

Hi @galak @mbolivar-nordic , the current way of using PCIE in devicetree is hacking into REG_ADDR and REG_SIZE like shown below:
https://github.com/zephyrproject-rtos/zephyr/blob/878edeb6ff190a713910a0e5cb9022704c5934a3/dts/x86/intel/elkhart_lake.dtsi#L57-L68
and then the code using this register and size looks really ugly like:
https://github.com/zephyrproject-rtos/zephyr/blob/878edeb6ff190a713910a0e5cb9022704c5934a3/drivers/serial/uart_ns16550.c#L1068-L1077
This macro programming stuff is already unreadable and hiding PCI_ID into REG_SIZE, etc  making it even harder to understand.

NAK: we shouldn't be propagating the incorrect PCI/PCIe addressing in devicetree by adding APIs around it.

Agreed.

I think it would be more productive to continue the discussion in #26109

I think it would be more productive to continue the discussion in #26109

I read this thread, and I'm going to leave my -1 on this PR because the requested changes apply regardless of the outcome of that discussion.

Closing it, PR #52107 fixes the issue.


Upgrades _ lib from underscore to lodash for performance

This is a drop-in improvement. Tested with a dependent application and found no issues.

This is now just a whitespace change after #81 was opened in my absence.


Warning: package ember-json-api is not a properly formatted package

test_frontend$ ember install:addon ember-json-api
version: 0.2.1
Installed packages for tooling via npm.
The package `ember-json-api` is not a properly formatted package, we have used a fallback lookup to resolve it at `/Users/<snip>/test_frontend/node_modules/ember-json-api`. This is generally caused by an addon not having a `main` entry point (or `index.js`).
Installed addon package.

Scroll the pasted message to the right to see the relevant part of the warning.

@spundun Seems the path to the main entry in package.json is malformed. I'll whip up a pull request to fix it.

Great! I'm glad I could help. :+1:

Came here to report the same thing. Happy to see it's already PR'd :+1:

same here! :+1:

I'm getting this issue too, will this be pushed to master so we don't need to point to the patch-2 branch?

@MarkLunney The pull request merges directly into the master of this repo. But I think @kurko is a but too busy at RailsConf right now.

:+1: seems like an easy merge to solve this annoying error :).

Closing this issue because the related pull request has been merged into master. If anyone still encounters any issues I'll reopen it.


Update README.md to include sample CR/example

This PR adds sections on

sample CR
How descheduler-operator works

/cc @sjenning

/lgtm


syslog/file: Remove syslog_dev_uninitialize in syslog_file_channel

it is impossible that syslog device get initialized before
since board_app_initialize call syslog_file_channel only once
Signed-off-by: Xiang Xiao<EMAIL_ADDRESS>Change-Id: Ia72c931f5e19f771e1864f63ede8565624c8c6b4

Also fix a build erorr noted here:
https://github.com/apache/incubator-nuttx/pull/366

@juniskane Please try this patch.

Should I wait for Juha's comments to merge?  I cannot select him as a reviewer.

Sure, let's wait hist feedback until tomorrow.

This is completely unacceptable. I have applications that call syslog_file_channel() based on run-time command-line arguments, to change the syslog destination on the fly. That is a useful functionality and there is no reason to limit this API to one-time initialization only. The patch causing build failure should be reverted instead i.e. do not make that one symbol static.

This is completely unacceptable. I have applications that call syslog_file_channel() based on run-time command-line arguments, to change the syslog destination on the fly. That is a useful functionality and there is no reason to limit this API to one-time initialization only. The patch causing build failure should be reverted instead i.e. do not make that one symbol static.

This API is for kernel use only, all mainline caller is from board_app_iniitialize, but you have a program call syslog_file_channel from userspace, do you have case launch this program multiple times?

I see no reason to restrict this to kernel only and that limitation is not in the API documentation. The ability to change syslog stream dynamically is extremely useful for testing. I can envision board level logic doing that after some BOARDIOC so it is not relevant if this function is called directly from app code or not. I currently use the "side effect" of (syslog internal) variables retaining their value in flat builds over multiple program invocations:

const char syslog_file;
/ ... this is in app main(), ... get syslog_file from argv... */
if (syslog_file)
{
#ifdef CONFIG_SYSLOG_FILE
/* Convenience names. */
if (strcmp(syslog_file, "usb") == 0)
syslog_file = "/dev/ttyACM0";
else if (strcmp(syslog_file, "uart") == 0)
syslog_file = "/dev/ttyS3";
if (syslog_file_channel(syslog_file) < 0)
fprintf(stderr, "Cannot set syslog to %s\n", syslog_file);
#else
fprintf(stderr, "Cannot set syslog to %s\n", syslog_file);
#endif
exit(0);
}

@juniskane Ok, the new fix should address your concern, please take a look.

This works otherwise, but not in the case syslog_file_channel() fails ever, even once. Cannot recover back to working device without reboot:
nsh> app -l /dev/nonexistent
Cannot set syslog to /dev/nonexistent
nsh> app -l usb
Cannot set syslog to /dev/ttyACM0
nsh> app -l uart
Cannot set syslog to /dev/ttyS3
nsh>

So it is still a regression of old, working functionality.

@juniskane syslog_dev_uninitialize shouldn't return error in the 2nd patch if there isn't the initialization yet, please try the 3rd patch again, thanks.

Does not even compile, or am I missing an interim patch?
syslog/syslog_device.c: In function 'syslog_dev_outputready':
syslog/syslog_device.c:268:15: error: void value not ignored as it ought to be
           ret = syslog_dev_initialize(g_syslog_dev.sl_devpath,
               ^
syslog/syslog_device.c: At top level:
syslog/syslog_device.c:316:5: error: conflicting types for 'syslog_dev_initialize'
 int syslog_dev_initialize(FAR const char *devpath, int oflags, int mode)
     ^~~~~~~~~~~~~~~~~~~~~
In file included from syslog/syslog_device.c:59:0:
syslog/syslog.h:99:6: note: previous declaration of 'syslog_dev_initialize' was here
 void syslog_dev_initialize(FAR const char *devpath, int oflags, int mode);
      ^~~~~~~~~~~~~~~~~~~~~
syslog/syslog_device.c:416:6: error: conflicting types for 'syslog_dev_uninitialize'
 void syslog_dev_uninitialize(void)
      ^~~~~~~~~~~~~~~~~~~~~~~
In file included from syslog/syslog_device.c:59:0:
syslog/syslog.h:122:5: note: previous declaration of 'syslog_dev_uninitialize' was here
 int syslog_dev_uninitialize(void);
     ^~~~~~~~~~~~~~~~~~~~~~~
Makefile:126: recipe for target 'syslog_device.o' failed
make[1]: *** [syslog_device.o] Error 1
make[1]: Leaving directory '/home/jni/u/yard/workarea/nuttx/drivers'
tools/LibTargets.mk:104: recipe for target 'drivers/libdrivers.a' failed

Does not even compile, or am I missing an interim patch?
syslog/syslog_device.c: In function 'syslog_dev_outputready':
syslog/syslog_device.c:268:15: error: void value not ignored as it ought to be
           ret = syslog_dev_initialize(g_syslog_dev.sl_devpath,
               ^
syslog/syslog_device.c: At top level:
syslog/syslog_device.c:316:5: error: conflicting types for 'syslog_dev_initialize'
 int syslog_dev_initialize(FAR const char *devpath, int oflags, int mode)
     ^~~~~~~~~~~~~~~~~~~~~
In file included from syslog/syslog_device.c:59:0:
syslog/syslog.h:99:6: note: previous declaration of 'syslog_dev_initialize' was here
 void syslog_dev_initialize(FAR const char *devpath, int oflags, int mode);
      ^~~~~~~~~~~~~~~~~~~~~
syslog/syslog_device.c:416:6: error: conflicting types for 'syslog_dev_uninitialize'
 void syslog_dev_uninitialize(void)
      ^~~~~~~~~~~~~~~~~~~~~~~
In file included from syslog/syslog_device.c:59:0:
syslog/syslog.h:122:5: note: previous declaration of 'syslog_dev_uninitialize' was here
 int syslog_dev_uninitialize(void);
     ^~~~~~~~~~~~~~~~~~~~~~~
Makefile:126: recipe for target 'syslog_device.o' failed
make[1]: *** [syslog_device.o] Error 1
make[1]: Leaving directory '/home/jni/u/yard/workarea/nuttx/drivers'
tools/LibTargets.mk:104: recipe for target 'drivers/libdrivers.a' failed

Sorry, I change the wrong function prototype, how about the new patch? It is hard to test my patch local since there isn't official config enabled this option.

Ok, now it seems be working as before.

@patacongo this patch is ready to merege now.

I have applications that call syslog_file_channel() based on run-time command-line arguments,

You know that that is a violation of the POSIX OS interface.  We cannot be responsible for people's use of internal, OS standard OS functions.  Don't count on that kind of portability in the future; we won't support it.


Post build event - adding files to path inside .nupkg.

I have some files I need to write to a specific path in my .nupkg file.  After a successful build, I would like to place several files into a specific path (runtimes/win7-x64/native) instead of the default 'lib/net45' folder.
Right now, I have to open the .nupkg file (I use Nuget Package Explorer) and manually create the (runtimes/win7-x64/native) folder structure then add the appropriate files. Note - these files have to be in this specific path in order for them to work in my project.
Basically, how do I go about using nuproj to handle this for me and eliminate the need for me to do it manually? I've attached an image to better illustrate my question (the part in red is what I'm trying to automate).

This is how I add extra files to the nupkg before it's created. In this example, I'm copying assemblies that were placed in the lib\portable- folder into lib\dotnet as well. But you can simply add File items with TargetPath metadata to do whatever you want.
  <Target Name="CopyAssemblyToLibDotNetFolder" DependsOnTargets="ConvertItems" AfterTargets="ConvertItems">
    <!-- NuProj doesn't yet support populating the lib\dotnet folder. So we do it ourselves. -->
    <ItemGroup>
      <File Include="@(File)"
            Condition=" '%(File.TargetFrameworkMoniker)' == '.NETPortable,Version=v4.5,Profile=Profile111' ">
        <TargetPath Condition=" '%(File.WithCulture)' != 'true' ">lib\dotnet\%(FileName)%(Extension)</TargetPath>
        <TargetPath Condition=" '%(File.WithCulture)' == 'true' ">lib\dotnet\%(File.Culture)\%(FileName)%(Extension)</TargetPath>
        <TargetPath Condition=" '%(File.MSBuildSourceTargetName)' == 'SatelliteDllsProjectOutputGroup' ">lib\dotnet\$([System.IO.Path]::GetFileName($([System.IO.Path]::GetDirectoryName(%(Identity)))))\%(FileName)%(Extension)</TargetPath>
      </File>
    </ItemGroup>
  </Target>


Emphasis not rendered recursively within footnote

Using the latest fontspec and LuaLaTeX or XeLaTeX, emphasis does not render within a footnote, as in the following example:
\documentclass{article}

\usepackage{fontspec}

\begin{document}

This is a \emph{test\footnote{\emph{test}} of emphasis}.

\end{document}

It works as expected if one removes the \usepackage{fontspec} line.

After I looked a bit at the fontspec modification of  \em I tried the following
\documentclass{article}

\usepackage{fontspec}

\begin{document}

\section{\textit{a \emph{test} of emphasis}}

\end{document}

and the inner emphasis does not render (it should be upright) with lualatex/xelatex contrarily to pdftex (without fontspec)

in my previous comment you can spare the \section,
for some reason I forget I was looking at some table of contents example initially,
anyway \textit{a \emph{test} of emphasis} behaves differently with or without fontspec

fontspec changes the implementation of \em and \emph, see section 6 in the manual, subsection Emphasis and nested emphasis.
There is a shortcoming that should be solved by fontspec itself; you can temporarily fix it by redefining \reset@font:
\documentclass{article}
\usepackage{fontspec}

\ExplSyntaxOn
\cs_set:cpn { reset@font } { \normalfont \int_zero:N \l__fontspec_em_int }
\ExplSyntaxOff

\setlength{\textheight}{2cm} % just for the example

\begin{document}

This is a \emph{test\footnote{\emph{test}} of emphasis}.

\end{document}

Thanks Enrico! This has been fixed in the source. Not promises for a new release soon though.

A public interface for resetting the \em level would also be welcome, see http://tex.stackexchange.com/questions/318374/

I should have realised that there would be lots of cases where people would want \textit{\emph{...}} (or equiv.) to do something sensible. Maybe I should explicitly check for that case in the redefinition of \em.
When you say a public interface to redefine the \em level, would you imagine something like
`\fontspec_set_em_level:n {1}`

or
`\EmLevel{1}`

or ... ? (Maybe best to reply with a new issue number :) )

Since \l__fontspec_em_int is “private”, but it seems to be needed also in user's contexts, a public interface such as \fontspec_set_em_level:n {1} should be sufficient; a higher level interface can be easily built upon this. I just hate using private variables at the top level so making Frank unhappy. ;-)

Not promises for a new release soon though.
Maybe some bugfix 2.5b release with just existing commits added? Just for fixing already found bugs.

Some pretty big updates in this area in commit #8c4306ccb82d54853e730f546f0bdab4167574af. \fontspec_set_em_level:n is provided (although not officially documented yet), but more importantly it should be much more robust to manual font changes.


Add Clipboard Interactions and User Input Suggestions

In this PR, I've been drafting Clipboard Interactions and User Input Suggestions to the project using Pyperclip for clipboard management and regular expressions for extracting code snippets from messages.
Key Features:

Added custom key bindings for copying messages or code snippets to the clipboard using Pyperclip.
Implemented regular expressions to extract and copy only code snippets from messages using Pyperclip.
Added AutoSuggestFromHistory to provide input suggestions based on past entries when using the user input suggestions feature.

Technical Details:

Added Pyperclip dependency for clipboard management using pip install Pyperclip.
Implemented PyperclipClipboard class for Pyperclip integration.
Implemented regular expression pattern matching using re module and re.compile() method for extracting code snippets from messages using Pyperclip.
Implemented AutoSuggestFromHistory functionality using history module for providing input suggestions based on past entries.

Goal:
This PR is an opportunity to experiment and draft how we could implement Clipboard Interactions and User Input Suggestions to the project using Pyperclip for clipboard management and regular expressions for extracting code snippets from messages.
This also provides us with the opportunity to plan out and design custom key bindings for copying messages or code snippets to the clipboard.
These features should make using the project more convenient and efficient for users.

I'll do this either later tonight or tomorrow. I'm in the middle of a few personal projects and I just started working again, still trying to get back into the swing of things. Moving the source code to a new module is trivial.
Maybe think about making source a proper package by adding an __init__.py and renaming it to rich_chat? I think we should do this in a separate PR once we merge this PR and iron out the basics.
What do you think?

Interesting. I already did this on my PC. Yes sure because we will have different modules.

Interesting. I already did this on my PC.

Okay. I bit the bullet.
It's the same as before, with the difference that it's a executable module, e.g.
python -m rich_chat.rich-chat --help

I've also given some thought to the naming convention for the "rich_chat" module, and I think following the Python convention of using an underscore (_) for library modules would be a good idea for consistency. This means renaming the current "rich-chat.py" file to something like "rich_chat.py" or "rich_chat_cli.py".
Here's how we could run the module as an executable using this new naming convention:
python -m rich_chat.rich_chat_cli --help

The decision on which naming convention to use depends.
Alternatively, we could use __main__.py for the entry point file, but that would require encapsulating all packages and modules within the package structure. This approach has its own set of pros and cons, such as increased complexity and better encapsulation.

I think this is a good checkpoint for the current implementation.
The introduced keybindings are designed to minimize conflicts with commonly used shortcuts, offering a straightforward way for users to interact with past messages, especially for yanking text:

ctrl + s: Initiates control selection.
ctrl + s a: Selects all text from a message.
ctrl + s s: Specifically selects code snippets within a message.

For instance, ctrl + s s 1 would copy a code snippet from the most recent message into the clipboard, assuming a snippet exists. To extract from specific messages, users can easily adjust the trailing digit, such as ctrl + s s 3 for a snippet from the third most recent message. Similarly, ctrl + s a 1 would copy the entirety of the most recent message.
This setup is admittedly basic and could benefit from refinement. It's a starting point, enabling some level of functionality while we explore other approaches.
I'm open to feedback, particularly any ideas to enhance usability or introduce more intuitive interactions.


Generate custom menu view

hi
How do you like menu out of it and append class to sub ul?

Link1

sub link 1

this is what childrenAttributes are about (they are attributes for the list of children): https://github.com/KnpLabs/KnpMenu/blob/master/doc/01-Basic-Menus.markdown#menu-attributes


support -y/--yes global flag to the atomicSwapCmd

When this (boolean) flag is defined as true, it should prevent any Y/N questions being asked to the user in the atomic swap commands.
The global flag can be added to atomicSwapCmd  using https://godoc.org/github.com/spf13/cobra#Command.PersistentFlags, and calling the BoolVarP method on that returned flag set (see other flags in our client code to see our conventions about how to define these flag properties and such).
Once this flag is added we want to put an if !atomicSwapcfg.YesToAll {} check around following code blocks:

https://github.com/rivine/rivine/blob/a4d74b1139ee4f0918c74d59a7d919a73f086323/pkg/client/atomicswap.go#L217-L224
https://github.com/rivine/rivine/blob/a4d74b1139ee4f0918c74d59a7d919a73f086323/pkg/client/atomicswap.go#L590-L597

This check will ensure two things:

To not print the contract to STDOUT, and thus not interfering with the regular output, a very important thing for an automated environment;
To not ask a Y/N question and simply assume Yes instead for this question, as indicated by the -y/--yes flag;

This issue has to be resolved should you want to use the atomic swap commands in an automated environment.

Code for this is ready. Will do pull request today!

Why don't we adjust
func askYesNoQuestion(str string) bool {
so it returns the value? This way we don't have to include a check in every individual code block.
If we don't print to std::out, how will we ever interpret (json) output in an automated environment?

Impl ready and pushed, will test this afternoon

You proposed earlier to put the YesToAll property check in the askYesNoQuestion  function (https://github.com/rivine/rivine/blob/84349693e539652219bbb7d94f911244c4ffbec4/pkg/client/atomicswap.go#L716), at the top, and yes I agree with that. Feel free to put an if yesToAll { return true } check at the top.
I thought about this before, but at that point it made sense to me to not print the contract review. However, that does mean that you wan to ensure that https://github.com/rivine/rivine/blob/84349693e539652219bbb7d94f911244c4ffbec4/pkg/client/atomicswap.go#L218-L219 is only executed when the encodingType is human (a check possible for when #366 is (being) resolved).
Same goes for https://github.com/rivine/rivine/blob/84349693e539652219bbb7d94f911244c4ffbec4/pkg/client/atomicswap.go#L592-L593.


Context-Path missing in Swagger-ui links/try when behind Proxy

I am using Springfox swagger 3.0.0 (via springfox-boot-starter maven dependency).
I encounter exactly the same problem as explained in old issue [https://github.com/springfox/springfox/issues/1210], with apache httpd configuration for the reverse proxy.
Direct links on the host look like this:
"http://service-host:8081/api"
whereas links to be routed via reverse proxy like this:
"https://portal-host/service-context/api"
The problem was declared as solved in 2.5.0, within this commit [https://github.com/springfox/springfox/pull/1217]
However with 3.0.0, my swagger-ui page has "try-out" links like "https://portal-host/api/XXXX" wich do not contain anymore the context-path "/service-context"
With debugger, i have inspected in WebMvcBasePathAndHostnameTransformationFilter#transform. I am not sure that is the most appropriate class to debug, but i see :

the HttpServletRequest instance received is of type org.springframework.web.filter.ForwardedHeaderFilter$ForwardedHeaderExtractingRequest
this request incudes one field ForwardedHeaderFilter$ForwardedPrefixExtractor.forwardedPrefix = "/service-context/api", and invocation of getContextPath() returns "/service-context/api"
i do not know the role of the "swagger" feeded instance, but i see that the WebMvcBasePathAndHostnameTransformationFilter simply erases the complete base path "/service-context/api""

Does anyone have an idea of the problem in 3.0.0 ? Is it possible that some code refactoring disabled the 2.5.0 1217 fix, OR is my context different from the original issue ...
Best Regards.
Fabien.

same issue here,DocumentationType.SWAGGER_2works fine, where DocumentationType.OAS_30 does not use the context-path for try-out feature.


Can't set clientOuput with an environment variable

Hi! First of all, thanks for making this patch available.
I have not so common requirement (I assume), which is setting prisma's output directory through an environment variable. e.g.
generator client {
  provider      = "prisma-client-js"
  output        = env("PRISMA_OUT_DIR")
  binaryTargets = ["native", "linux-musl"]
}

When I don't define clientOuput it fallbacks to .prisma/client
generator json {
  provider     = "prisma-json-types-generator"
}

Error:
✔ Generated Prisma Client (4.7.1 | library) to ./apps/payments/node_modules/prisma-generated in 267ms
Cannot find module '/path/to/repo/apps/payments/.prisma/client'
Require stack:

When I define clientOutput as env("PRISMA_OUT_DIR") it looks like it doesn't evaluate the function
generator json {
  provider     = "prisma-json-types-generator"
  clientOutput        = env("PRISMA_OUT_DIR")
}

Error:
✔ Generated Prisma Client (4.7.1 | library) to ./apps/payments/node_modules/prisma-generated in 259ms
ENOENT: no such file or directory, open '/path/to/repo/apps/payments/prisma/(function)/index.d.ts'

Finally if I harcode the same value as PRISMA_OUT_DIR it works
generator json {
  provider     = "prisma-json-types-generator"
  clientOutput = "../node_modules/prisma-generated"
}

Unfortunately I need the output to be set dynamically through the aforementioned variable. Any chance this is an easy fix?

Hey @abonifacio, this seems like a very good feature, you're up to a PR?

Update: prisma does not support it for now. See https://github.com/prisma/prisma/issues/19065

This is a well known issue since 2021. I wouldn't get high hopes on it being implemented.
https://github.com/prisma/prisma/issues/8990

What I could do, if you really need this issue and don't have any workarounds, is to add a string syntax like ::OUTPUT to this generator itself try to resolve from env.

Hi @arthurfiorette thanks for looking into this, in my case I ended up casting the types for now 🤷🏽♂ . I appreciate the goodwill but I think this should be fixed by Prisma


HttpModule for query string encryption

@madskristensen you wrote a piece of code for query string encryption at http://madskristensen.net/post/httpmodule-for-query-string-encryption#comments
By any chance are you planning to write something for .NET 5 or perhaps this will be already part of the framework. Please advise, thanks.

It's not currently part of any plans to provide this in the box. You can port this module to a middleware though.

Thank you.


fix date issue reported by sun yuan; add translation

Signed-off-by: David Liang<EMAIL_ADDRESS>

LGTM


Blogger : Get profiles & blog data

Hello,
I would like to integrate my application with Blogger.
After authenticate user with $authUrl = $client->createAuthUrl(), is it possible to get user's profile data  with Access token?
I have tried with 'me' as user_id in parameter, but it return error   "message": "We're sorry, but the value for field resource_id was not valid."
Thanks..

Try with scope google plus :)

$oauth2 = new Google_Service_Oauth2($client);

dump($oauth2->userinfo->get());


{AKS} Bump the minimum required cli core version to 2.56.0

This checklist is used to make sure that common guidelines for a pull request are followed.
In the new SDK used in aks-preview since 2.0.0b7, it starts using SensitiveHeaderCleanupPolicy provided by azure.core. aks-preview does not separately declare its dependency on the version of azure.core, but inherits from the declaration in azure-cli. In azure-cli PR #27783, the dependency on azure.core is bumped to 1.28.0 (in which SensitiveHeaderCleanupPolicy was introduced). Changes in #27783 were released in 2.56.0. So changing the minimum required cli core version to 2.56.0.
Sample error
File \"/opt/az/lib/python3.10/site-packages/knack/cli.py\", line 233, in invoke
    cmd_result = self.invocation.execute(args)
  File \"/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py\", line 663, in execute
    raise ex
  File \"/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py\", line 726, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File \"/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py\", line 697, in _run_job
    result = cmd_copy(params)
  File \"/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py\", line 333, in __call__
    return self.handler(*args, **kwargs)
  File \"/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/command_operation.py\", line 112, in handler
    client = self.client_factory(self.cli_ctx, command_args) if self.client_factory else None
  File \"/root/.azure/cliextensions/aks-preview/azext_aks_preview/_client_factory.py\", line 31, in cf_managed_clusters
    return get_container_service_client(cli_ctx).managed_clusters
  File \"/root/.azure/cliextensions/aks-preview/azext_aks_preview/_client_factory.py\", line 23, in get_container_service_client
    return get_mgmt_service_client(cli_ctx, CUSTOM_MGMT_AKS_PREVIEW, subscription_id=subscription_id)
  File \"/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/client_factory.py\", line 83, in get_mgmt_service_client
    client, _ = _get_mgmt_service_client(cli_ctx, client_type, subscription_id=subscription_id,
  File \"/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/client_factory.py\", line 251, in _get_mgmt_service_client
    client = client_type(credential, subscription_id, **client_kwargs)
  File \"/root/.azure/cliextensions/aks-preview/azext_aks_preview/vendored_sdks/azure_mgmt_preview_aks/_container_service_client.py\", line 98, in __init__
    policies.SensitiveHeaderCleanupPolicy(**kwargs) if self._config.redirect_policy else None,
AttributeError: module 'azure.core.pipeline.policies' has no attribute 'SensitiveHeaderCleanupPolicy'
To check existing issues, please visit: https://github.com/Azure/azure-cli/issues"

Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[ ] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

AKS


Update gettingstarted.rst

About this pull request
Update the code to mention that the utils portion is needed
Changes
Update to mention needed discord slash utils
Checklist

[ ] I've checked this pull request runs on Python 3.6.X.
[ ] This fixes something in Issues.

Issue:

[ ] This adds something new.
[ ] There is/are breaking change(s).
[ ] (If required) Relavent documentation has been updated/added.
[x] This is not a code change. (README, docs, etc.)

Merging this pull request, thank you for contributing!

🥳


Google Cloud VMware Engine plugin

GCVE is untested by us, but the PR can be reviewed. We can perform testing once we get access to GCVE.
@KonradSchieban has had good luck so far.
resolves https://github.com/observIQ/stanza-plugins/issues/242

This has not been merged because it is unclear to us if gcve engine outputs json for all users.