Getting device object during bootstrap session.

Hi guys,
got the question cause I cannot find the solution. Is it the possibility to retrieve some other information from the connected device during the bootstrap session? E.g. if I'd like to receive the serial number of the connected device?
Many thanks.

AFAIK, there is no way to do that with LWM2M v1.0 (so this is not available in Leshan v1.x)
For LWM2M v1.1, there is a new Bootstrap Read request but it is limited to object 1 or 2 :confused: :

In this specification the only acceptable targets for the "Bootstrap-Read" operation is the LwM2M Server Object (Object ID: 1) and the Access Control Object (Object ID:2).

(Just to let you know, for now, Bootstrap-Read is not yet implemented in Leshan 2.x but it could be if needed)
So as understand the specification, there is no way to do that strictly following the specification.
But some "out of the spec" / "not interoperable" way could be :

having a device which allow BootstrapReadon the Device Object (Object Id:3) or more limited just the Serial Number Resource (/3/0/2)
using some Bootstrap-Request additional(out of spec)   attributes

For 1.  Bootstrap-Read should be added to Leshan and we need to find a way to configure that. (I can work on it if needed)
For 2. there is already a way to get additional attribute : bootstrapSession.getBootstrapRequest(). getAdditionalAttributes(). This can be tested with leshan-client-demo -bsaa command line option.
 -bsaa <arg>                     Use additional attributes at bootstrap time, syntax is
                                 -bsaa attrName1=attrValue1 attrName2=\"attrValue2\" ...

Ok, got it.
Many thanks for your comprehensive answer.

@gerardolenski  Just let me know if you need the Bootstrap Read request feature.

Well,
I must support bootstrap with LWM2M 1.0.2 and I'm using v1.3.1 of the Bootstrap Server Leshan library.
So it won't help in my case if I understood correctly ;(


Add ReCaptcha for creating an account

To prevent someone from spam-creating accounts.

Closed by #1526 for now, we'll see if ReCaptcha becomes necessary in the future.


download method local file path

When calling the download method ,
a file object is created with the same path as the requested file to download ,
paths like /Documents/somefile won't exist usually  under the local filesystems where the
library is being used .
The default path to write the file contents could be the local CWD plus the name of the file being downloaded , and the method could accept a keyword argument in order to explicitly tell the desired path where to write the file contents.

@chaps Is this what you're looking for? https://github.com/smartfile/client-python/pull/17

Hi @cabarnes ,
I'm looking for something more like this : https://github.com/chaps/client-python/commit/89a816a4fc30b562002b8b5c14189ad6b4afb52c


About Pose Matrixs Transformation

Hello, thanks u for awesome work.
I have some confusion about the Pose matrixs transformation among world, camera, objects. I cannot understand the meaning behind them. I wanna ask if there are some blogs i can refer to ?
Thanks in advance~

Hi, CeoiZidung,
We use the notations for poses similar to SLAM systems, i.e., you can search for transformation SLAM Tcw Twc as a reference.

transformation SLAM Tcw Twc

Thanks u！


Handle error async using CompletableFuture.completeExceptionally

See my commment on the issue here https://github.com/playframework/playframework/issues/10512#issuecomment-1007172728

@FXHibon Thanks for this example. I will try it in the next couple of days/week.

@FXHibon Just saw your other message, seems it's not working like you expected. Thanks anyway for trying :)


CHANGE_TYPE_ANNOTATION to handle unreferenceable type

Similar to #46910

https://dart-review.googlesource.com/c/sdk/+/210960


NextJS api login getting spammed

When filing a bug report, please confirm you've done the following:

Have you set onVerifyTokenError and onTokenRefreshError in your config and checked for any helpful errors? Yes
Have you set debug: true in your config and read through server-side and client-side debug logs for any helpful messages? Yes
Have you tried the example app with your own Firebase credentials?
Have you read through the troubleshooting Q&A? Yes

Describe the bug
A clear and concise description of the bug.
As mentioned in the title /api/login is being requested at every refresh or redirect of page. Is this normal behavior?
Versions
next-firebase-auth version: ^1.0.2
Firebase JS SDK (firebase): ^10.7.2
Firebase admin SDK (firebase-admin):  ^12.0.0
Next.js: 13.5.6
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Debug and error logs
Please provide debug logs or errors from onVerifyTokenError and onTokenRefreshError.
Additional context
Add any other context about the problem here.

Thanks! I believe this is a duplicate of #424, but let me know if it differs.


Update dependencies

Updates hyper to 0.9 (removes dependency on old url, which may cause a problem in the future due to github.com/servo/rust-url/issues/195), as well as the xml parser.

Thanks for the PRs. Had a few issues merging, but everything should be fine now. Docs are updated, and version will be up on cargo in a second.


Weird behavior with recursive generic types

🔎 Search Terms
recursive generic types
🕗 Version & Regression Information
v5.6.2
⏯ Playground Link
https://www.typescriptlang.org/play/?#code/C4TwDgpgBAysD2AnCAeAqgZwogIgQ2DwD4oBeKAbwCgooBzCYALigAoBKMkzbfQgbhpQszNgBMCeFj1yTOpEgDd4ASzGCAvoKqhIUAIJhIAOzEBheMeAQAHsACMKQ2ACiiiFYA0UGX2JlKITA8ZCsWFwAbCABbJyM3D2BvX0kiTW1daGcPc0trOwAmONd3Lx8sWUIScmpaYNDRSJjihLKUqvSqKgAzAFdjAGNgFUsoCPg6AAUQxJbSpPLeVNZ6xPCo2OdWhfbidhZlNUoNLoGIvAwMKCbN+Pnkir8SWuEEZAB+FjgkVF20rtoeCMOVYQxsLGypgsVlsDjmiQeSyq+yghzEgVotHGUxmVlBwBsADpVlZ2IJaCcTlQBpYMMAoGD7BDgVC8rDHMYIO5EN5jL1ogAjbDVY5QC4GFm5GF2Dlc7DeOmIFTGOj-am0+lggrMkxS-LAIqc7m8-lCxAiigaMVXSF62GGuU815KlVpIA
💻 Code
type Store<UserData> = {
  get: () => UserData;
  set: (data: UserData) => void;
};

type AppendContext1<AppEvent, UserData> = {
  parent: Elem<AppEvent, UserData>;
};

type AppendContext2<AppEvent, UserData> = {
  parent: Elem<AppEvent, UserData>;
};

function logParent<AppEvent, UserData>(parent: Elem<AppEvent, UserData>): void {}

class Elem<AppEvent, UserData> {
  store?: Store<UserData>;

  append(ctx: AppendContext1<AppEvent, UserData>): void {
    logParent(ctx.parent);
  }
}

const ctx1: AppendContext1<never, number> = {} as AppendContext1<never, string>;

const ctx2: AppendContext2<never, number> = {} as AppendContext2<never, string>;

🙁 Actual behavior
Only the second assignment errors
🙂 Expected behavior
Both assignment should error because their respective Stores differ
Additional information about the issue
This is the most minimal reproducible example that I could create and it probably has the most weird bits of behavior in TS that I've ever seen:

if you remove the AppEvent parameter (that doesn't really affect anything as it would seem) from everywhere, both assignments result in an error, just like they should
if you remove append method from the Elem class, both assigments result in an error
if you replace the parent parameter type in logParent with any, both assigments result in an error
finally if you remove the logParent statement (which definitely shouldn't affect typings in this case), again both assignments error

This can happen due to shortfalls in the variance measurement algorithm when you have mutually-recursive types like this. See https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/#optional-variance-annotations-for-type-parameters - the code here is basically isomorphic to the example in the blog post.

Thank you so much for clearing this out for me! I've wasted hours on this problem, glad to finally figure out what was wrong with my code. Honestly never heard of these explicit in/out before and there doesn't seem to be a lot of info/help online about those, but they look quite powerful when applied correctly. Again thank you so much!


Glimmer release

Hi,
I'm just in the process of trying to update to Glimmer & was wondering if you are planning to publish a new version to npm soon or whether I should start by using this github repo for now.
Thanks.

@chrism This is a difficult addon to update, since it uses some private APIs. I believe @chrislopresto is taking a look at it :)

@tim-evans ok, thanks for letting me know :)

@tim-evans This branch of ember-wormhole https://github.com/yapplabs/ember-wormhole/tree/range-safely (along with a small hack working around a glimmer bug) should unblock development on glimmer-compatible wormhole-based versions of document-title and favicon components.

@chrislopresto I have a wip branch here: https://github.com/paddle8/ember-document-title/tree/using-wormhole
The most interesting bug so far is that didInsertElement isn't called in hierarchical order, which causes a bunch of test failures. I'm not sure why it does that, and I'm not sure whether it's a bug or not- when the render hooks were called, the order was determinable.
Other than that, I'm trying to do prepends, which I've written a copy of appendRange.
The last detail is that I cannot write this addon as a tagless view. If that's not possible, I think that's an ok compromise for stability.

Since 1.13 is released, and 2.0 is coming up soon, I think I'm going to try to tackle this at an Ember project night. I'm going to also change the semver so this addon will skip 1.0 and go straight to 2.0 to make it follow http://emberjs.com/blog/2015/06/16/ember-project-at-2-0.html

@tim-evans nice! looking forward to it.

@rwjblue do you have any thoughts regarding the APIs used here?

There's some changes on master that will be the solution for 1.13.0. The work now is documenting and providing htmlbars AST transformations to support this.

@tim-evans so master should work with 1.13?

Yessir! I removed the need to depend on ember-wormhole.

I'm getting Uncaught TypeError: Cannot read property 'appendMorph' of undefined"
line 53 of document-title.js: this._morph = buffer.dom.appendMorph(titleTag);
Any ideas?

@caseyjenks It's not actually released yet. You can use the package by referencing git, but there's still some work to be done. That's why this ticket isn't closed.

Released 1.13.0.
Deprecation warnings should show up in your console with old style of rendering the title. Open any issues if you have trouble. :tada:

:rocket: yay!

nice work!

@tim-evans - Thank you for your hard work on this!


Refactor factories

close #53

Coverage remained the same at 96.09% when pulling 65811dfc8eccbd617ff2beb7296d4d2df49d48ee on refactor-factories into 829c62a4ce80e1cb514ce257c47cc831175ca7ed on master.

Coverage remained the same at 96.09% when pulling 97758cfeefbdc480b603cbb8cc2dac620968b80e on refactor-factories into 829c62a4ce80e1cb514ce257c47cc831175ca7ed on master.

:smile:


Cookies with expiry date is not handled correctly in CookieFilter

Cookies which contains an expiry date that is not adhering to the 'expired date format' specified at

http://web.archive.org/web/20020803110822/http://wp.netscape.com/newsref/std/cookie_spec.html

is not getting applied in subsequent requests.
The cookie expiry date format that is now recommended by IETF is - Expires=Fri, 07 Feb 2020 12:46:00 GMT (https://tools.ietf.org/html/rfc6265). HttpClient though has not updated to this format yet and expects a format - Expires=Fri, 07-Feb-2020 HH:MM:SS GMT. Note the difference in dashes between IETF and Netscape formats.

HttpClient further recommends to use custom configuration of Cookie Policy (https://www.mail-archive.com/dev@hc.apache.org/msg16624.html).

Though we can set the httpClient cookie config, CookieFilter does not use the standards from CookieSpec. If we modify the below code in CookieFilter.java
public CookieFilter(boolean allowMultipleCookiesWithTheSameName) {
        this.allowMultipleCookiesWithTheSameName = allowMultipleCookiesWithTheSameName;
        this.cookieSpec = new DefaultCookieSpec(); //This uses the default dateFormat from netscape
        this.cookieStore = new BasicCookieStore();
    }

to
public CookieFilter(boolean allowMultipleCookiesWithTheSameName) {
        this.allowMultipleCookiesWithTheSameName = allowMultipleCookiesWithTheSameName;
        this.cookieSpec = new DefaultCookieSpec(new String[]{"EEE, dd MMM yyyy HH:mm:ss z"},false);
        this.cookieStore = new BasicCookieStore();
    }

the problem might get resolved. I can raise a PR if this approach sounds good.

Any update on the issue? Will it be considered in any near future releases?

I was able to fix this issue with:
    public CookieFilter(boolean allowMultipleCookiesWithTheSameName) {
        this.allowMultipleCookiesWithTheSameName = allowMultipleCookiesWithTheSameName;
        this.cookieSpec = new RFC6265StrictSpec();
        this.cookieStore = new BasicCookieStore();
    }

Would you want a PR for this?
At the moment, the CookieFilter doesn't work for lots of use-cases, and it took me a while to figure out why. I bet lots of users run into this issue but never figure out why it doesn't work.

Any update? Also, cookies are not handled correctly when following redirects, even with a proper cookie filter.

Great, thanks!


Text layer overlays not exactly

Link to PDF file (or attach file here):
page3.pdf
Configuration:

Web browser and its version: IE 11, Chrome 50
Operating system and its version: Windows 7
PDF.js version: 1.5
Is an extension: No

Steps to reproduce the problem:

Open page3.pdf with viewer.html
Select text: "application mainly"

What is the expected behavior? (add screenshot)
Text layer matches exactly with rendered text.
What went wrong? (add screenshot)

Text layer overlays not exactly. A little bit too far up and too far ahead in the middle of text line.

Closing since this got fixed by #12896 and other work.


Feature/DEV-11875: IIIF Processing

Changes:

Adds IIIF image service using sharp
Tile images in figures.yaml with preset=zoom
Create manifest with choices from figures.yaml data
Output tiles and manifests to iiif/config.js output directory (default content/_iiif)
Moves choices UI to separate component and outside of canvasPanel shortcode

Todo:

Render canvas with choices in modal, will be addressed on a separate branch.

Note: IIIF processing on this branch is always called in theeleventy.before build hook. This is for development and demo purposes, but in image-heavy projects the user will likely want more control over when images are processed, we can determine how that works when we hook IIIF processing into the CLI (for example, quire preview might call processImages by default, but you could specify something like quire preview --please-do-not-process-images if you wanted to preview the project without IIIF resources)

@geealbers @Erin-Cecele Feel free to take a look at the work here, there is a demo page at /iiif-demo

thanks @hbalenda. I just tried it and ran into an error.
I pulled down the branch, ran npm install on node 16.14.2, and then ran npm run dev and got the following errors:
galbers@GT29043 11ty % npm run dev

><EMAIL_ADDRESS>predev
> npm run clean

><EMAIL_ADDRESS>clean
> del ${ELEVENTY_OUTPUT_DIR:-_site}

><EMAIL_ADDRESS>dev
> ELEVENTY_ENV=development eleventy --serve

[11ty] Problem writing Eleventy templates: (more in DEBUG output)
[11ty] The "path" argument must be of type string. Received undefined (via TypeError)
[11ty]
[11ty] Original error stack trace: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
[11ty]     at new NodeError (node:internal/errors:371:5)
[11ty]     at validateString (node:internal/validators:120:11)
[11ty]     at Object.join (node:path:1172:7)
[11ty]     at /Users/galbers/GitHub/quire/packages/11ty/_plugins/iiif/process/tileImage.js:44:25
[11ty]     at /Users/galbers/GitHub/quire/packages/11ty/_plugins/iiif/process/index.js:64:23
[11ty]     at Array.forEach (<anonymous>)
[11ty]     at /Users/galbers/GitHub/quire/packages/11ty/_plugins/iiif/process/index.js:51:21
[11ty]     at AsyncEventEmitter.<anonymous> (/Users/galbers/GitHub/quire/packages/11ty/_plugins/iiif/index.js:9:11)
[11ty]     at /Users/galbers/GitHub/quire/packages/11ty/node_modules/@11ty/eleventy/src/Util/AsyncEventEmitter.js:19:61
[11ty]     at Array.map (<anonymous>)
[11ty] Wrote 0 files in 0.03 seconds (v2.0.0-canary.8)
[11ty] Unhandled rejection in promise: (more in DEBUG output)
[11ty] Invalid URL (via TypeError)
[11ty]
[11ty] Original error stack trace: TypeError [ERR_INVALID_URL]: Invalid URL
[11ty]     at new NodeError (node:internal/errors:371:5)
[11ty]     at onParseError (node:internal/url:552:9)
[11ty]     at new URL (node:internal/url:628:5)
[11ty]     at /Users/galbers/GitHub/quire/packages/11ty/_plugins/iiif/process/createManifest.js:68:30
[11ty]     at Array.map (<anonymous>)
[11ty]     at /Users/galbers/GitHub/quire/packages/11ty/_plugins/iiif/process/createManifest.js:66:37
[11ty]     at A.createCanvas (/Users/galbers/GitHub/quire/packages/11ty/node_modules/iiif-builder/dist/cjs/index.js:1:24862)
[11ty]     at /Users/galbers/GitHub/quire/packages/11ty/_plugins/iiif/process/createManifest.js:62:16
[11ty]     at Be.createManifest (/Users/galbers/GitHub/quire/packages/11ty/node_modules/iiif-builder/dist/cjs/index.js:1:26562)
[11ty]     at /Users/galbers/GitHub/quire/packages/11ty/_plugins/iiif/process/createManifest.js:60:30

@geealbers will you try adding URL=http://localhost:8080 to your .env? Though I will also see if there's a way to make this not required.


use new IO crate

Make JSON module compatible with the new IO crate.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see CONTRIBUTING.md for more information.

This is great, and it's nice to see that it didn't require that many changes!
I will beg the powers that be not to merge this yet though. I don't think the world is ready for std::io yet (there are still some really important things missing that are scheduled for this week), and rustc-serialize is a core library that tons of crates depend on.

I have spent a whole day on migrating my small project to be compatible with the new IO crate. ;)

While std::io may not be fully fleshed out yet I would like to make progress in allowing dependencies to update to using std::io wherever possible. I'm going to publish this as a new series of releases on crates.io so you can still opt-in to the std::old_io behavior. We can also perhaps maintain a branch for a bit with std::old_io as well.

I've created an old-io branch we can use to maintain the 0.2.x series temporarily.


Inject multiple subclasses into "params"

I have a situation similar to the case below:
public class Animal {

}

public class Monkey : Animal {

}

public class Lion : Animal {

}

public class Zoo {

  public readonly Animals;

  [Inject]
  public Zoo(params Animal[] animals) {
    Animals = animals;
  }
}

Is it possible to inject a list of params with multiple subclasses (or the same class, for that matter)?
i.e., something like this:
Container.Bind<Monkey, Lion>().To<Animal[]>().WhenInjectedInto<Zoo>();

Thanks in advance. This framework has been great to work with.

I think this should do what you want:
            Container.Bind<Animal>().To<Monkey>().WhenInjectedInto<Zoo>();
            Container.Bind<Animal>().To<Lion>().WhenInjectedInto<Zoo>();

Or if you want to make it one line you can do that too like this:
Container.Bind<Animal>().To(typeof(Monkey), typeof(Lion)).WhenInjectedInto<Zoo>();

Note that you probably will need to add AsSingle, AsTransient or AsCached to that.

@svermeulen That worked perfectly. I must have missed the List Bindings section in the documentation because I was searching for params. Thanks for the quick response!


feat(InlineEditor): add select option to edit method

In reference to https://github.com/qontu/ngx-inline-editor/issues/58#issuecomment-307801805
I have implemented the select option to use in edit method and rename doFocus option to focus

Tanks for your contribution! 👍


Uncaught SyntaxError: Unexpected end of input

Issue Id: 3c0f493a-37c5-196b-ce04-755343aba4dbVersions - 0.10.6-release-  dfc08dc9edf6607483b193bf934d3badc3fa2e11Stack SyntaxError: Unexpected end of input    at Object.parse (native)/vs/workbench/parts/debug/node/v8Protocol.ts#L129:21 (V8Protocol.dispatch)/vs/workbench/parts/debug/node/v8Protocol.ts#L108:11 (V8Protocol.handleData)/vs/workbench/parts/debug/node/v8Protocol.ts#L63:8 (V8Protocol.connect)    at emitOne (events.js:77:13)    at Socket.emit (events.js:169:7)    at readableAddChunk (_stream_readable.js:146:16)    at Socket.Readable.push (_stream_readable.js:110:10)    at Pipe.onread (net.js:523:20)

@isidorn Most likely this occurs if the debug-adapter is terminated while still sending data. The debug UI should catch exceptions thrown in the JSON parse and terminate the debug session. I expect that the debug session in many cases is already in the process of being shut down (and has actually terminated the debug adapter in the first place).

@weinand I can do that, though terminating a session just because JSON parse fails might be a bit too harsh, no? This could produce weird behavior for other adapter which might be in development and are sending broken jsons. Shouldn't we just ignore the event if we think the debug adapter is going down anyways.

@weinand just to remind you about this.

@isidorn right, when the session is going down anyways, we can ignore the exception. In other cases, we should let the error ripple up and terminate the session with a corresponding error message. We should then self-host on this and get a feel for how often that happens. If it happens too often, we can disable that behaviour in the product. Just silently ignoring the exception in all cases is a bit dangerous...

Makes sense, I have pushed it so we try it out. I append stopping debug adapter at the end so it is more clear to the user what is going on

👍🏽


Add lapindrome checker

Brief Intro
Add a new algorithm, to check if the string is lapindrome or not
More Details
What is lapindrome
Lapindrome is defined as a string which when split in the middle, gives two halves having the same characters and same frequency of each character.

for example

gaga
abccda
xyyx

@gmotzespina YOU ARE RIGHT

I think my PR hasn’t been merged

@gmotzespina oh yes sorry bro

Heyo,
I've added some comments to the PR for revisions. For now let's close this issue since there's already a  PR addressing this!


audacity: 3.2.4 -> 3.2.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/audacity/audacity/releases.
meta.description for audacity is: Sound editor with graphical UI
meta.homepage for audacity is: https://www.audacityteam.org
meta.changelog for audacity is: https://github.com/audacity/audacity/releases
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.2.5 with grep in /nix/store/72fba5ih6wi7pr3ddyw0a6npsbyxix0c-audacity-3.2.5
found 3.2.5 in filename of file in /nix/store/72fba5ih6wi7pr3ddyw0a6npsbyxix0c-audacity-3.2.5

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
audacity

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/72fba5ih6wi7pr3ddyw0a6npsbyxix0c-audacity-3.2.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A audacity https://github.com/r-ryantm/nixpkgs/archive/e46eadb51655cfb7dc60a22afbb00b63b7d390ae.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/72fba5ih6wi7pr3ddyw0a6npsbyxix0c-audacity-3.2.5
ls -la /nix/store/72fba5ih6wi7pr3ddyw0a6npsbyxix0c-audacity-3.2.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

audacity

Maintainer pings
cc @lheckemann @veprbl @wegank for testing.

x86_64-darwin already failing on master: https://hydra.nixos.org/build/210821851


doc/website: add faq page

The entgo.io website can hold many of the common questions in the issue tracker, like:

How to create an entity from a struct (avoid calling Set<F>)
How to create a struct/mutation-level validator
How to write an audit-log extension (see #830)
How to write a custom predicate (runtime and codegen)
How to write unit tests
How to apply ordering on edges
How to rename an edge/field
Recommendation when adding new fields (optional or with default value)
How to implement a cursor-based pagination

Please comment here if you have more suggestions for common questions

Using Custom fields (somewhat related to custom predicates) - https://github.com/facebook/ent/issues/871, https://github.com/facebook/ent/issues/883
General section under query performance - this comes up a lot in different forms. Limiting columns, join types

We could probably add a section for some postgres specific questions - enums, postgis, arrays


DEPLOYMENT

DEPLOYMENT
User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
Acceptance Criteria
GIVEN a Prework Study Guide website,
WHEN I visit the website using the URL,
THEN I can access my website from any browser

If u want a site go to netlify (netlify.com)


Responsiveness

How can i make it responsive on multiple columns... without overflowing table header and table footer... just the horizontal scroll on the body

I haven't used my library since million years, I personally cannot help much I'm sorry


Unable to resolve DNS requests when they get upgraded to TCP - simple fix(rebuild image)

Describe the bug
The latest release was released in January this year. At the time, there was a bug in alpine where the DNS implementation in musl didn't support upgrading to TCP.
The release uses Alpine 3.15. This bug existed in Alpine until 3.18, which was released in may 2023. The last release of this software was in January.
See the mention about the issue in kubernetes docs: https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/
To fix the bug, simply re-build the image.
To Reproduce
exec into the container and use the wget binary that is still there to resolve some domains using the inbuilt resolver. A domain registered by njal.la tends to work, but I don't have any I can disclose.
Expected behavior
DNS resolves
Additional context
Add any other context about the problem here.
Version
0.12.2
Logs
Please paste any relevant logs here

Since this project is not using a version pinned version of alpine when building, simply rebuilding the image should solve the problem: https://github.com/argoproj-labs/argocd-image-updater/blob/master/Dockerfile#L13


Fix Add Project button UI

Fix- issue - 166

Removed Install New Bot button in frontend.
Added Add Project button as shown in UI mock.
Transfer the functionalities of Install New Bot to Add Project

@code-with-om Can you please take a pull from main and fix the merge conflicts?

Thank you @code-with-om for your contribution.


Parameter 'batteryConfigured' and 'pvConfigured' disappeared from rest API

Describe the bug
openHAB evcc binding is evaluating the two parameters 'batteryConfigured' and 'pvConfigured' from rest-API.
The two parameters disappeared without a trace. Was the breaking API change done on intention?
'gridConfigured' is still present.
Steps to reproduce

...
Configuration details
.

Log details
{
   "result":{
      "auth":{
         "vehicles":{

         }
      },
      "battery":[
         {
            "power":305.13,
            "energy":806.3646160000001,
            "soc":60.1,
            "capacity":7.68,
            "controllable":true
         }
      ],
      "batteryCapacity":7.68,
      "batteryDischargeControl":true,
      "batteryEnergy":806.3646160000001,
      "batteryMode":"normal",
      "batteryPower":305.13,
      "batterySoc":60.1,
      "bufferSoc":100,
      "bufferStartSoc":100,
      "currency":"EUR",
      "fatal":null,
      "greenShareHome":0.9862311873579613,
      "greenShareLoadpoints":0,
      "gridConfigured":true,
      "gridCurrents":[
         -0.5720000267028809,
         0.652999997138977,
         0.628000020980835
      ],
      "gridEnergy":1901.719,
      "gridPower":4.300000190734863,
      "homePower":312.30000019073486,
      "loadpoints":[
         {
            "chargeCurrent":0,
            "chargeCurrents":[
               0,
               0,
               0
            ],
            "chargeDuration":21000000000,
            "chargePower":0,
            "chargeRemainingDuration":0,
            "chargeRemainingEnergy":15506.399999999994,
            "chargeTotalImport":5332.7002,
            "chargedEnergy":3.6000000000058208,
            "chargerFeatureHeating":false,
            "chargerFeatureIntegratedDevice":false,
            "chargerIcon":null,
            "chargerPhases1p3p":false,
            "chargerPhysicalPhases":null,
            "charging":false,
            "connected":true,
            "connectedDuration":0,
            "disableThreshold":0,
            "effectiveLimitSoc":100,
            "effectiveMaxCurrent":32,
            "effectiveMinCurrent":6,
            "effectivePlanSoc":0,
            "effectivePlanTime":"0001-01-01T00:00:00Z",
            "effectivePriority":10,
            "enableThreshold":0,
            "enabled":false,
            "limitEnergy":0,
            "limitSoc":0,
            "maxCurrent":32,
            "minCurrent":6,
            "mode":"pv",
            "phaseAction":"inactive",
            "phaseRemaining":0,
            "phasesActive":2,
            "phasesConfigured":3,
            "phasesEnabled":3,
            "planEnergy":0,
            "planOverrun":0,
            "planProjectedStart":"0001-01-01T00:00:00Z",
            "planTime":"0001-01-01T00:00:00Z",
            "priority":10,
            "pvAction":"inactive",
            "pvRemaining":0,
            "sessionCo2PerKWh":null,
            "sessionEnergy":3.6000000000058208,
            "sessionPrice":0.0017524800000028335,
            "sessionPricePerKWh":0.4868,
            "sessionSolarPercentage":0,
            "smartCostActive":false,
            "title":"Wallbox",
            "vehicleClimaterActive":false,
            "vehicleDetectionActive":false,
            "vehicleLimitSoc":0,
            "vehicleName":"Q5",
            "vehicleOdometer":44395,
            "vehicleRange":0,
            "vehicleSoc":1.0229787234042924
         },
         {
            "chargeCurrent":0,
            "chargeDuration":92360000000000,
            "chargePower":0,
            "chargedEnergy":6410.496488163158,
            "chargerFeatureHeating":true,
            "chargerFeatureIntegratedDevice":true,
            "chargerIcon":"waterheater",
            "chargerPhases1p3p":false,
            "chargerPhysicalPhases":1,
            "charging":false,
            "connected":true,
            "connectedDuration":0,
            "disableThreshold":0,
            "effectiveLimitSoc":40,
            "effectiveMaxCurrent":3,
            "effectiveMinCurrent":2,
            "effectivePlanSoc":0,
            "effectivePlanTime":"0001-01-01T00:00:00Z",
            "effectivePriority":10,
            "enableThreshold":0,
            "enabled":false,
            "limitEnergy":0,
            "limitSoc":40,
            "maxCurrent":3,
            "minCurrent":2,
            "mode":"pv",
            "phaseAction":"inactive",
            "phaseRemaining":0,
            "phasesActive":1,
            "phasesConfigured":1,
            "phasesEnabled":1,
            "planEnergy":0,
            "planOverrun":0,
            "planProjectedStart":"0001-01-01T00:00:00Z",
            "planTime":"0001-01-01T00:00:00Z",
            "priority":10,
            "pvAction":"inactive",
            "pvRemaining":0,
            "sessionCo2PerKWh":null,
            "sessionEnergy":6410.496488163158,
            "sessionPrice":0.6097946665645497,
            "sessionPricePerKWh":0.09512440537024273,
            "sessionSolarPercentage":96.75780499746966,
            "smartCostActive":false,
            "title":"Heatpump",
            "vehicleClimaterActive":null,
            "vehicleDetectionActive":false,
            "vehicleLimitSoc":0,
            "vehicleName":"heatpump",
            "vehicleOdometer":0,
            "vehicleRange":0,
            "vehicleSoc":60
         }
      ],
      "prioritySoc":100,
      "pv":[
         {
            "power":2.87
         }
      ],
      "pvEnergy":0,
      "pvPower":2.87,
      "residualPower":100,
      "siteTitle":"home",
      "smartCostType":"pricestatic",
      "sponsor":"...",
      "sponsorTokenExpires":0,
      "statistics":{
         "30d":{
            "avgCo2":0,
            "avgPrice":0.14893148173909884,
            "chargedKWh":208.50557401394784,
            "solarPercentage":83.4655430486416
         },
         "365d":{
            "avgCo2":0,
            "avgPrice":0.26975229340091245,
            "chargedKWh":575.1409692579458,
            "solarPercentage":53.61850459463629
         },
         "total":{
            "avgCo2":0,
            "avgPrice":0.26975229340091245,
            "chargedKWh":575.1409692579458,
            "solarPercentage":53.61850459463629
         }
      },
      "tariffFeedIn":0.082,
      "tariffGrid":0.4868,
      "tariffPriceHome":0.08757361535749725,
      "tariffPriceLoadpoints":0.4868,
      "vehicles":{
         "Q5":{
            "title":"Audi Q5",
            "icon":"car",
            "capacity":14.1,
            "limitSoc":100
         },
         "heatpump":{
            "title":"Heatpump",
            "icon":"waterheater"
         }
      },
      "version":"0.125.0"
   }
}

What type of operating system are you running?
Docker container
Version
0.125.0

Yes, they were deleted intentionally. You can get the same info by checking if pv and battery has entries.
As of now, /api/state structure may be subject to change from release to release. This might change once we've released 1.0.

@naltatis, thanks for confirming my observation and my intended change within the openHAB evcc binding.
Is a similar change foreseen for gridConfigured?

@MikeTheTux yes, very likely. Honestly I'm surprised, that we didn't delete it when we cleaned up pv and battery. As far I know gridConfigured is currently unused by evcc ui.

References:

https://github.com/evcc-io/evcc/pull/12498
https://github.com/evcc-io/evcc/issues/13366


Atlas space for dtseries

For the minimally processed fMRI data, I can see
sub-_ses-baselineYear1Arm1_task-_bold_desc-filtered_timeseries.dtseries.nii
And it says that
"Concatenated functional task dense time series post-DCANBOLDProcessing (regression and filtering) in Atlas space."
What does the Atlas space mean? Is it in MNI space? If I want to use Cole's Atlas (with subcortical parcellation in MNI space) is it correct way to extract parcels?

Hi There! Thanks for the question! We will get back to you with an answer as soon as possible.

Hi Seonjoo!
My apologies for the late reply. The file is encoded in a CIFTI format, where the volumetric space is MNI, and the surface space is the fsaverage_LR32k ( an excellent "unofficial" explanation of the format can be found here, and see here for the associated manuscript on the associated formats). Briefly, the surface space is the freesurfer average template with the left and right hemispheres mirrored. Each hemisphere contains 32,000 vertices -- including the medial wall.
The workbench command cifti-separate can be used to split CIFTI files into GIFTI surface files and a volumetric subcortical file. The volumetric file for the dtseries here will contain the functional MRI timeseries data mapped to the FSL 2006 MNI template. These files will also be quite large.
An alternative is to use workbench to create a label file from the volumetric ROI. To do so, you'll need to check whether Cole's ROIs can be mapped to one of 19 subcortical structures indexed within the CIFTI. Such a label file can easily contain multiple labels. Afterwards, the -cifti-parcellate command can be used to extract a parcellated time-series per label within the label file.
Hope this helps!


fix undefined jinja var "meta"

closes #394
As far as I can tell, the site still renders fine after this change, but I would welcome a second pair of eyes.

Hmmm - I think the question is what happened to meta - did it get deprecated in jinja or something?

I didn't see anything about it in the changelog...

@drammock is there a full log of the doc build where you are seeing the error? (#394 only has the actual error)
It might be that meta is not defined for some special pages like genindex (that's the page where it is failing with this error in https://github.com/sphinx-themes/sphinx-themes.org/pull/70)

Good point @jorisvandenbossche - I bet that you're right. As along as we are confident that we won't miss config elsewhere, then I'm +1 on this. I suppose that if we didn't pass crucial config in other places as a result of removing this, then it'd show up as errors elsewhere in the test suite

@jorisvandenbossche here is the full traceback on our CI: https://app.circleci.com/pipelines/github/mne-tools/mne-python/7914/workflows/246aeec9-b376-484a-af05-81bd0b815be3/jobs/27512#step-139-1859

Thanks, so there it also errored for the genindex page.
I am not sure why it hits us now and not before, but in any case what this PR does (is undefined check) is also how eg rtd theme is doing it: https://github.com/readthedocs/sphinx_rtd_theme/blob/9df65f15c5f62ac5a847c505f559c00586316936/sphinx_rtd_theme/breadcrumbs.html#L1

then I say let's :shipit:

Two things:

can we add a test?
should we add a canary excursion with pip install --pre to catch some of these things sooner?

or perhaps more targetd just our runtime dependencies?

FWIW, meta comes from Sphinx (see https://www.sphinx-doc.org/en/master/templating.html#meta).
As noted already, it can be undefined for some pages, which is why things are failing for sphinx-themes.org. :)

I guess that the test for this should entail building a sphinx site with a genindex (or some other page without a meta tag) and making sure it doesn't error. Does this not already happen in our test suite?
@drammock what do you think?

I suppose the demo docs / tests already do that, but we need an environment with the dev versions of sphinx/jinja to catch this

Ah - so perhaps we need to add another matrix dimension here for Sphinx version?
https://github.com/pydata/pydata-sphinx-theme/blob/master/.github/workflows/tests.yml#L65
Reasonable to strive to keep up with the latest 2 major versions in general + the pre-release (so, 2.x, 3.x, 4.xa)?

Ah - so perhaps we need to add another matrix dimension here for Sphinx version?

Yes, it might indeed be good to test against multiple versions of sphinx.
For now, short term, I quickly added a build that simply installs any pre-release version if available of sphinx and jinja2 (it's actually jinja2 that is causing the error here, not sphinx) -> https://github.com/pydata/pydata-sphinx-theme/pull/402

So CI was failing in https://github.com/pydata/pydata-sphinx-theme/pull/402, and passing now with the fix in this PR. So merging.
Thanks @drammock !

I also made a 0.6.2 release with this fix (https://github.com/pydata/pydata-sphinx-theme/releases/tag/v0.6.2)

Woooo! Thanks @drammock for fixing this!

(BTW, Chris, there is still something very strange with your git ;) For the previous 0.6.1 release, the release commit (https://github.com/pydata/pydata-sphinx-theme/commit/f54466a646cbc084bd1bb4dacb3f3b196598b495) was this time done 3 days in the past .. For the 0.6.0 release you "only" did it one day in the past ;))


Support user interaction in ci_testing

What problem does this solve or what need does it fill?
We test examples using Github Actions, but interacting with these examples while they are running is hard. Github Action runners don't have a keyboard and mouse, nor an actual monitor. We want to test the majority of examples, but are limited to examples that do not require any sort of user interaction.
What solution would you like?
We use bevy_dev_tools's ci_testing module to specify automated actions that should be run, such as to take a screenshot at a specific frame. These actions are specified by the CiTestingEvent enum:
https://github.com/bevyengine/bevy/blob/383314ef627da6654588a704959fc92c67770a52/crates/bevy_dev_tools/src/ci_testing.rs#L42-L47
As brought up by @mockersf in a recent presentation, this enum is lacking additional features that would enable greater interaction. Some ideas for additional features, sorted by usefulness, are:

KeyboardInput
MouseButtonInput
GamepadEvent
TouchInput

I propose KeyboardInput is added to CiTestingEvent so that we can test keyboard interactions in CI. If that is successful, we can re-evaluate whether the other 3 are useful and worth implementing.
What alternative(s) have you considered?
I think that specifying actions using ci_testing is the right direction, thought the list of supported actions is currently very weak. By not implementing this feature, we leave the testing framework underpowered. Testing is one of the best ways to ensure quality, which Rust and Bevy by extension have a reputation for. This is why I believe not implementing user inputs is not an option, though the method used to achieve may vary.
The reason I propose to only support keyboards in the very beginning is because they are very easy to implement, and likely the most useful. The mouse is difficult without moving it, which works on offsets. The gamepad and touch are more obscure are difficult to verify locally without the proper hardware.

A good example of where this could be used is by pressing D in #13507 to automatically add 100 samples. The example is random, but from a deterministic seed.


[draft] tree test code

XRX Tree Tester
This PR adds a library that for instrumenting and evaluating the performance (re: correctness, not speed) of xRx in certain scenarios. There is a library called TreeTestRunner that can be used to a) create a hierarchy of nodes representing the agent execution flow b) run an LLM to answer a series of qualitative questions about each node to determine if the agent successfully completed the scenario. The idea is that by representing agent execution as a tree, we can get fine-grained information about the success or failure of each node, and whether and how those nodes contributed to the (in)ability of the agent to successfully complete the scenario.
For demonstration purposes, I've use the TreeTestRunner to instrument shopify-app. TreeTestRunner supports arbitrary trees; the structure I've chosen is:
- one root node at the top level, representing a conversation between the user and the agent
- many request-response nodes at the second level. Each of these nodes captures a message from the user to the agent and an associated response from the agent back to the user.
- many graph-specific nodes below each request-response node. Each of these corresponds to a specific reasoning task the agent undertakes while formulating a response to the user (`routing`, `chooseTool`, etc.)

Testing
To see TreeTestRunner in action, start shopify-app and interact with the app normally (I'd recommend using interactive_test.py.) When you are finished, say or type 'stop'. Wait for a bit for the tests to run (this may take a while, especially if you get rate-limited by the LLM provider.) After the tests are run the frontend will crash, but you should see
xrx-reasoning     | 2024-11-09 21:53:19,146 INFO:Done writing file!
xrx-reasoning     | 2024-11-09 21:53:19,149 INFO:Done writing simple file!

in the docker-compose output. At this point you can find the output of your test in shopify-app/testOutput. There will be two files, one of the form <name>.json and one of the form <name>-simple.json. The first one is raw output and the second is cleaned up a bit to be more pleasant to read. I recommend using a json prettifier to look at these.
The description of the tests to run is in shopify-app/reasoning/app/treeTestConfig/buySomethingTest.yaml. It includes the goal that the agent is supposed to fulfill, as well as a list of audits for every possible stage. The format should be self-explanatory, but just leave a comment if it's not and I can document it. Feel free to add config for your own scenarios; you can change the test being run by changing the pathname in line 40 of executor.py
You can find some sample outputs under shopify-app/reasoning/app/agent/sample_tests. These were all generated by me interacting with the agent.
TODOs & Cleanup Work

fix naming - I'm used to typescript these days so I keep reflexively using camel case instead of snake case
Perhaps find a way to persist the test runner across requests that doesn't involve pickling
remove various debug cruft (pdb imports)

Next Steps

~Build an LLM-backed "synthetic user" that can interact with the agent based on a prompt~
Push the tests to S3 instead of writing them locally
Come up with a good way to summarize multiple tests - the evaluations are predictably stochastic so we'll likely need to run them lots of times to get a stable signal.
Modify this to accommodate "black box" approaches where we aren't able to instrument the source and instead have to parse the raw output of the system into a tree.
Anything else I'm forgetting!

[Feature] Add Comprehensive Testing Utilities to xRx Framework
1. Overview

What is the feature?
This feature introduces a new testing.py module to the xRx framework, providing robust utilities for building and managing tests for AI-powered reasoning systems. Additionally, the __init__.py file is updated to integrate these testing utilities into the framework.

What changed?

Framework Initialization: Enhanced the __init__.py to include the new testing utilities.
Testing Utilities: Added a comprehensive testing.py module with classes and functions for defining and executing tests.

2. Files Modified

File Name
Changes

__init__.py
• Context: Initializes the xRx agent framework.• Changes [EDIT]: Added an import statement for the new testing.py module to integrate testing functionalities into the framework.

testing.py
• Context: Provides testing utilities for the xRx framework.• Changes [NEW]: Introduced testing.py with 274 lines of code, including classes like TestResult, TaskNode, and TreeTestRunner, as well as functions for configuration management, prompt generation, and audit execution using LLMs.

3. Issues/Improvements

Security. Ensure secure handling of test configurations.
- Sensitive data in test configurations might be exposed.
- Implement encryption or secure access controls for configuration files.

Performance. Assess the impact of testing utilities on framework performance.
- Extensive testing operations could slow down the framework.
- Optimize testing processes and consider asynchronous execution where possible.

Maintainability. Manage increased complexity due to added testing modules.
- The new `testing.py` introduces substantial code that may complicate maintenance.
- Refactor the testing utilities for better modularity and add comprehensive documentation.

Simplification. Potential to streamline configuration merging logic.
- The `deep_merge` function may be overly complex for current needs.
- Explore using standard library functions or simplifying the merging logic to enhance readability and efficiency.

Hi Matt, adding some AI generated descriptions to gather feedback and test prompts!

Hi Matt, adding some AI generated descriptions to gather feedback and test prompts!

awesome, ty!

@mprast: This is fantastic work! Honestly, though, I had to seek LLM help to understand the TreeTestRunner with an example [I chose defaultAudits.yaml], but here's how I finally interpret how the evaluation actually works.
So:
Root questions (4 questions): Evaluated once for entire conversation

Stage questions (for each interaction):
requestResponse (1 question)
routing (2 questions)
chooseTool (2 questions)
identifyToolParams (1 question)
customerResponse (2 questions)

Each interaction gets evaluated against 8 questions (the sum of all stage questions), and then the entire conversation gets evaluated against the 4 root questions at the end.

Aside from the nits (code/function-level docs), I don't have much commentary other than explaining the functionality and the developer guide for developers to take advantage of this test infrastructure as they build use cases with xRx. I would use  defaultAudits.yaml as an example to describe how it works in the guide. That can be a separate and outside of this PR.

@sabbyanandan thanks for taking a look! will address comments
sorry for not including more detail on how the test runner works, the general gist is:

you use the tree runner to build a tree of nodes (nodes are also referred to as tasks); the structure of the tree is arbitrary

each task can succeed or fail

each task has

a stage (and optionally a substage) - this identifies the type of the task. The stage/substage is used to look up audit questions in the config file. These can be arbitrary
task data - this is an arbitrary object which is used to provide context to the LLM when it's asked to answer audit questions about the task. This is the only information the LLM will have about the task when answering the questions
a compositive flag - this indicates whether the task is compositive (see below). By default, tasks are not compositive

the success or failure of a task is calculated like this:

a compositive task simply succeeds if all of its child tasks succeed, and fails otherwise.  The LLM is not consulted to determine whether the task has succeeded or failed. Task data is ignored for compositive tasks.
to evaluate the success of a non-compositive task, the LLM is asked a series of audit questions about the task data attached to the task. Audit questions are fetched from configuration based on the stage & substage of the task. If all of the audit questions are answered in the affirmative, the task succeeds, otherwise it fails. A non-compositive task may succeed even if some of its children have failed.

I'll compile this information and add it to the docs. Thanks!

you can now turn the tree test runner on or off using an env var. xRx will only use a state machine if TREE_TEST_RUNNER_ON is set to "true"


[NWM] Members in Long Range Configuration are unclear.

What are the members in this chart?

@Castronova @itaher1995
An updated legend.

@zhiyuli are these defined anywhere on the page, e.g. what does "member 1 of cycle no 1" mean?

This issue was moved to CUAHSI-APPS/nwm-forecast-viewer#6


emerald quicksorters don't work properly

sorting happens but animation doesn't appear.  json binding in config code has an issue

fixed in 0.1.3


Fix release script to work with multiple dist calls

fixes #130

Verified that @j3tan has signed the CLA. Thanks for the pull request!

+2 :ship: it!


[Megatron dataset] Support loading megatron dataset

PR types

New features
PR changes

APIs
Description

Support loading megatron dataset for llm/llama, llm/gpt3 and model_zoo/gpt/run_pretrain_trainer.py.
Add paddlenlp/data/indexed_dataset.py for megatron.
Add paddlenlp/data/causal_dataset.py for llm.
Add paddlenlp/data/blendable_dataset.py for multi-dataset.
Add model_zoo/gpt/dataset.py so that model_zoo/gpt/run_pretrain_trainer.py can load megatron dataset.
Add model_zoo/gpt/legacy_dataset.py for model_zoo/gpt/run_pretrain_static.py and model_zoo/gpt/run_pretrain.py.
Remove duplicate content in ernie-1.0/data_tools.
Support custom data_cache path.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: KB-Ding:x: dingkunbodingkunbo seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


List all regions when a debug flag is set

By default, azd only lists a subset of the locations that a user has access to. Our filtering huristics exclude both EUAP and the "stage" regions which some customers may have access to but in practice don't always support all of the infrastructure that users of azd may try to provison.
However, when testing new features, it's often useful to be able to select these regions from the picker, instead of forcing folks to run something like azd env set AZURE_LOCATION <short-name-of-region>
This change adds support for setting AZD_DEBUG_INCLUDE_ALL_LOCATIONS to a true value (as recognized by strconv.ParseBool) to prevent us from filtering out these other locations.

@weikanglim @vhvb1989 Proposing this as something we may want to do (perhaps it's better to express it with a user config flag that they can set with azd config set and persists).  I've found recently that many partners from the Aspire team want access to these EUAP or stage regions so they can test in development features and was wondering if there might be away to allow users to opt into listing all the regions.
Just a thought.

Azure Dev CLI Install Instructions
Install scripts
MacOS/Linux

May elevate using sudo on some platforms and configurations

bash:
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3781/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3781/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3781 --version '' --verbose --skip-verify

pwsh:
Invoke-RestMethod 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3781/uninstall-azd.ps1' -OutFile uninstall-azd.ps1; ./uninstall-azd.ps1
Invoke-RestMethod 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3781/install-azd.ps1' -OutFile install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3781' -Version '' -SkipVerify -Verbose

Windows
PowerShell install
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3781/uninstall-azd.ps1' > uninstall-azd.ps1; ./uninstall-azd.ps1;"
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3781/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3781' -Version '' -SkipVerify -Verbose;"

MSI install
powershell -c "irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3781/azd-windows-amd64.msi' -OutFile azd-windows-amd64.msi; msiexec /i azd-windows-amd64.msi /qn"

Standalone Binary

Linux -

x86_64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3781/azd-linux-amd64.tar.gz
ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3781/azd-linux-arm64.tar.gz

MacOS -

x86_64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3781/azd-darwin-amd64.zip
ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3781/azd-darwin-arm64.zip

Windows - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3781/azd-windows-amd64.zip

MSI

https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3781/azd-windows-amd64.msi

Documentation

learn.microsoft.com documentation

title: Azure Developer CLI reference
description: This article explains the syntax and parameters for the various Azure Developer CLI commands.
author: alexwolfmsft
ms.author: alexwolf
ms.date: 04/23/2024
ms.service: azure-dev-cli
ms.topic: conceptual
ms.custom: devx-track-azdevcli
Azure Developer CLI reference
This article explains the syntax and parameters for the various Azure Developer CLI commands.
azd
The Azure Developer CLI (azd) is an open-source tool that helps onboard and manage your application on Azure
Options
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --docs         Opens the documentation for azd in your web browser.
  -h, --help         Gets help for azd.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd auth: Authenticate with Azure.
azd config: Manage azd configurations (ex: default Azure subscription, location).
azd deploy: Deploy the application's code to Azure.
azd down: Delete Azure resources for an application.
azd env: Manage environments.
azd hooks: Develop, test and run hooks for an application. (Beta)
azd init: Initialize a new application.
azd monitor: Monitor a deployed application. (Beta)
azd package: Packages the application's code to be deployed to Azure. (Beta)
azd pipeline: Manage and configure your deployment pipelines. (Beta)
azd provision: Provision the Azure resources for an application.
azd restore: Restores the application's dependencies. (Beta)
azd show: Display information about your app and its resources.
azd template: Find and view template details. (Beta)
azd up: Provision Azure resources, and deploy your project with a single command.
azd version: Print the version number of Azure Developer CLI.

azd auth
Authenticate with Azure.
Options
      --docs   Opens the documentation for azd auth in your web browser.
  -h, --help   Gets help for auth.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd auth login: Log in to Azure.
azd auth logout: Log out of Azure.
Back to top

azd auth login
Log in to Azure.
Synopsis
Log in to Azure.
When run without any arguments, log in interactively using a browser. To log in using a device code, pass
--use-device-code.
To log in as a service principal, pass --client-id and --tenant-id as well as one of: --client-secret,
--client-certificate, or --federated-credential-provider.
azd auth login [flags]

Options
      --check-status                           Checks the log-in status instead of logging in.
      --client-certificate string              The path to the client certificate for the service principal to authenticate with.
      --client-id string                       The client id for the service principal to authenticate with.
      --client-secret string                   The client secret for the service principal to authenticate with. Set to the empty string to read the value from the console.
      --docs                                   Opens the documentation for azd auth login in your web browser.
      --federated-credential-provider string   The provider to use to acquire a federated token to authenticate with.
  -h, --help                                   Gets help for login.
      --redirect-port int                      Choose the port to be used as part of the redirect URI during interactive login.
      --tenant-id string                       The tenant id or domain name to authenticate with.
      --use-device-code[=true]                 When true, log in by using a device code instead of a browser.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd auth: Authenticate with Azure.
Back to top

azd auth logout
Log out of Azure.
Synopsis
Log out of Azure
azd auth logout [flags]

Options
      --docs   Opens the documentation for azd auth logout in your web browser.
  -h, --help   Gets help for logout.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd auth: Authenticate with Azure.
Back to top

azd config
Manage azd configurations (ex: default Azure subscription, location).
Synopsis
Manage the Azure Developer CLI user configuration, which includes your default Azure subscription and location.
Available since azure-dev-cli_0.4.0-beta.1.
The easiest way to configure azd for the first time is to run azd init. The subscription and location you select will be stored in the config.json file located in the config directory. To configure azd anytime afterwards, you'll use azd config set.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
Options
      --docs   Opens the documentation for azd config in your web browser.
  -h, --help   Gets help for config.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config get: Gets a configuration.
azd config list-alpha: Display the list of available features in alpha stage.
azd config reset: Resets configuration to default.
azd config set: Sets a configuration.
azd config show: Show all the configuration values.
azd config unset: Unsets a configuration.
Back to top

azd config get
Gets a configuration.
Synopsis
Gets a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config get <path> [flags]

Options
      --docs   Opens the documentation for azd config get in your web browser.
  -h, --help   Gets help for get.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config list-alpha
Display the list of available features in alpha stage.
azd config list-alpha [flags]

Options
      --docs   Opens the documentation for azd config list-alpha in your web browser.
  -h, --help   Gets help for list-alpha.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config reset
Resets configuration to default.
Synopsis
Resets all configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable to the default.
azd config reset [flags]

Options
      --docs    Opens the documentation for azd config reset in your web browser.
  -f, --force   Force reset without confirmation.
  -h, --help    Gets help for reset.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config set
Sets a configuration.
Synopsis
Sets a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config set <path> <value> [flags]

Examples
azd config set defaults.subscription <yourSubscriptionID>
azd config set defaults.location eastus

Options
      --docs   Opens the documentation for azd config set in your web browser.
  -h, --help   Gets help for set.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config show
Show all the configuration values.
Synopsis
Show all configuration values in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config show [flags]

Options
      --docs   Opens the documentation for azd config show in your web browser.
  -h, --help   Gets help for show.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config unset
Unsets a configuration.
Synopsis
Removes a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config unset <path> [flags]

Examples
azd config unset defaults.location

Options
      --docs   Opens the documentation for azd config unset in your web browser.
  -h, --help   Gets help for unset.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd deploy
Deploy the application's code to Azure.
azd deploy <service> [flags]

Options
      --all                   Deploys all services that are listed in azure.yaml
      --docs                  Opens the documentation for azd deploy in your web browser.
  -e, --environment string    The name of the environment to use.
      --from-package string   Deploys the application from an existing package.
  -h, --help                  Gets help for deploy.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd down
Delete Azure resources for an application.
azd down [flags]

Options
      --docs                 Opens the documentation for azd down in your web browser.
  -e, --environment string   The name of the environment to use.
      --force                Does not require confirmation before it deletes resources.
  -h, --help                 Gets help for down.
      --purge                Does not require confirmation before it permanently deletes resources that are soft-deleted by default (for example, key vaults).

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd env
Manage environments.
Options
      --docs   Opens the documentation for azd env in your web browser.
  -h, --help   Gets help for env.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env get-values: Get all environment values.
azd env list: List environments.
azd env new: Create a new environment and set it as the default.
azd env refresh: Refresh environment settings by using information from a previous infrastructure provision.
azd env select: Set the default environment.
azd env set: Manage your environment settings.
Back to top

azd env get-values
Get all environment values.
azd env get-values [flags]

Options
      --docs                 Opens the documentation for azd env get-values in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for get-values.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env list
List environments.
azd env list [flags]

Options
      --docs   Opens the documentation for azd env list in your web browser.
  -h, --help   Gets help for list.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env new
Create a new environment and set it as the default.
azd env new <environment> [flags]

Options
      --docs                  Opens the documentation for azd env new in your web browser.
  -h, --help                  Gets help for new.
  -l, --location string       Azure location for the new environment
      --subscription string   Name or ID of an Azure subscription to use for the new environment

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env refresh
Refresh environment settings by using information from a previous infrastructure provision.
azd env refresh <environment> [flags]

Options
      --docs                 Opens the documentation for azd env refresh in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for refresh.
      --hint string          Hint to help identify the environment to refresh

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env select
Set the default environment.
azd env select <environment> [flags]

Options
      --docs   Opens the documentation for azd env select in your web browser.
  -h, --help   Gets help for select.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env set
Manage your environment settings.
azd env set <key> <value> [flags]

Options
      --docs                 Opens the documentation for azd env set in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for set.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd hooks
Develop, test and run hooks for an application. (Beta)
Options
      --docs   Opens the documentation for azd hooks in your web browser.
  -h, --help   Gets help for hooks.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd hooks run: Runs the specified hook for the project and services
Back to top

azd hooks run
Runs the specified hook for the project and services
azd hooks run <name> [flags]

Options
      --docs                 Opens the documentation for azd hooks run in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for run.
      --platform string      Forces hooks to run for the specified platform.
      --service string       Only runs hooks for the specified service.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd hooks: Develop, test and run hooks for an application. (Beta)
Back to top

azd init
Initialize a new application.
azd init [flags]

Options
  -b, --branch string         The template branch to initialize from. Must be used with a template argument (--template or -t).
      --docs                  Opens the documentation for azd init in your web browser.
  -e, --environment string    The name of the environment to use.
      --from-code             Initializes a new application from your existing code.
  -h, --help                  Gets help for init.
  -l, --location string       Azure location for the new environment
  -s, --subscription string   Name or ID of an Azure subscription to use for the new environment
  -t, --template string       Initializes a new application from a template. You can use Full URI, <owner>/<repository>, or <repository> if it's part of the azure-samples organization.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd monitor
Monitor a deployed application. (Beta)
azd monitor [flags]

Options
      --docs                 Opens the documentation for azd monitor in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for monitor.
      --live                 Open a browser to Application Insights Live Metrics. Live Metrics is currently not supported for Python apps.
      --logs                 Open a browser to Application Insights Logs.
      --overview             Open a browser to Application Insights Overview Dashboard.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd package
Packages the application's code to be deployed to Azure. (Beta)
azd package <service> [flags]

Options
      --all                  Packages all services that are listed in azure.yaml
      --docs                 Opens the documentation for azd package in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for package.
      --output-path string   File or folder path where the generated packages will be saved.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd pipeline
Manage and configure your deployment pipelines. (Beta)
Options
      --docs   Opens the documentation for azd pipeline in your web browser.
  -h, --help   Gets help for pipeline.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd pipeline config: Configure your deployment pipeline to connect securely to Azure. (Beta)
Back to top

azd pipeline config
Configure your deployment pipeline to connect securely to Azure. (Beta)
azd pipeline config [flags]

Options
      --auth-type string             The authentication type used between the pipeline provider and Azure for deployment (Only valid for GitHub provider). Valid values: federated, client-credentials.
      --docs                         Opens the documentation for azd pipeline config in your web browser.
  -e, --environment string           The name of the environment to use.
  -h, --help                         Gets help for config.
      --principal-id string          The client id of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-name string        The name of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-role stringArray   The roles to assign to the service principal. By default the service principal will be granted the Contributor and User Access Administrator roles. (default [Contributor,User Access Administrator])
      --provider string              The pipeline provider to use (github for Github Actions and azdo for Azure Pipelines).
      --remote-name string           The name of the git remote to configure the pipeline to run on. (default "origin")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd pipeline: Manage and configure your deployment pipelines. (Beta)
Back to top

azd provision
Provision the Azure resources for an application.
azd provision [flags]

Options
      --docs                 Opens the documentation for azd provision in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for provision.
      --no-state             Do not use latest Deployment State (bicep only).
      --preview              Preview changes to Azure resources.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd restore
Restores the application's dependencies. (Beta)
azd restore <service> [flags]

Options
      --all                  Restores all services that are listed in azure.yaml
      --docs                 Opens the documentation for azd restore in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for restore.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd show
Display information about your app and its resources.
azd show [flags]

Options
      --docs                 Opens the documentation for azd show in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for show.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd template
Find and view template details. (Beta)
Options
      --docs   Opens the documentation for azd template in your web browser.
  -h, --help   Gets help for template.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template list: Show list of sample azd templates. (Beta)
azd template show: Show details for a given template. (Beta)
azd template source: View and manage template sources. (Beta)
Back to top

azd template list
Show list of sample azd templates. (Beta)
azd template list [flags]

Options
      --docs            Opens the documentation for azd template list in your web browser.
  -h, --help            Gets help for list.
  -s, --source string   Filters templates by source.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template: Find and view template details. (Beta)
Back to top

azd template show
Show details for a given template. (Beta)
azd template show <template> [flags]

Options
      --docs   Opens the documentation for azd template show in your web browser.
  -h, --help   Gets help for show.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template: Find and view template details. (Beta)
Back to top

azd template source
View and manage template sources. (Beta)
Options
      --docs   Opens the documentation for azd template source in your web browser.
  -h, --help   Gets help for source.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template: Find and view template details. (Beta)
azd template source add: Adds an azd template source at the specified key (Beta)
azd template source list: Lists the configured azd template sources. (Beta)
azd template source remove: Removes the specified azd template source (Beta)
Back to top

azd template source add
Adds an azd template source at the specified key (Beta)
azd template source add <key> [flags]

Options
      --docs              Opens the documentation for azd template source add in your web browser.
  -h, --help              Gets help for add.
  -l, --location string   Location of the template source.
  -n, --name string       Display name of the template source.
  -t, --type string       Kind of the template source.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template source: View and manage template sources. (Beta)
Back to top

azd template source list
Lists the configured azd template sources. (Beta)
azd template source list [flags]

Options
      --docs   Opens the documentation for azd template source list in your web browser.
  -h, --help   Gets help for list.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template source: View and manage template sources. (Beta)
Back to top

azd template source remove
Removes the specified azd template source (Beta)
azd template source remove <key> [flags]

Options
      --docs   Opens the documentation for azd template source remove in your web browser.
  -h, --help   Gets help for remove.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template source: View and manage template sources. (Beta)
Back to top

azd up
Provision Azure resources, and deploy your project with a single command.
azd up [flags]

Options
      --docs                 Opens the documentation for azd up in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for up.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd version
Print the version number of Azure Developer CLI.
azd version [flags]

Options
      --docs   Opens the documentation for azd version in your web browser.
  -h, --help   Gets help for version.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

Ran into this today, would definitely want to show all regions by default so the user doesn't have to hunt for the setting when it doesn't' appear.  I spent roughly 30-60 researching why the region wasn't appearing in the list.  I ultimately had to reach out to Victor who pointed me to this issue.  Our customers won't have that luxury of Victor on call.

Ran into this today, would definitely want to show all regions by default so the user doesn't have to hunt for the setting when it doesn't' appear.

@jongio Which region specifically?  EUAP or others?  I could imagine us always including EUAP but we should hide the others by default I think.  The fact that we are doing filtering here at all is driven by user feedback from the past...  I think these "stage" regions that a bunch of at least MSFT folks have access to just don't work from the point of view of someone who is not an Azure service engineer and if people pick them they will have a very bad time...

I would use an opt-in setting in user config for this @ellismg.   azd config set all.locations on  ->  that would bring the full list all the times.

Ran into this today, would definitely want to show all regions by default so the user doesn't have to hunt for the setting when it doesn't' appear.

@jongio Which region specifically? EUAP or others? I could imagine us always including EUAP but we should hide the others by default I think. The fact that we are doing filtering here at all is driven by user feedback from the past... I think these "stage" regions that a bunch of at least MSFT folks have access to just don't work from the point of view of someone who is not an Azure service engineer and if people pick them they will have a very bad time...

EAUP.  If you use list-locations, then it will only show locations applicable to that sub.  So, shouldn't be a prob

I would use an opt-in setting in user config for this @ellismg. azd config set all.locations on -> that would bring the full list all the times.

I don't know about that one.  Now the user would have to search for that setting to figure out why locations aren't appearing.


Allow standalone extension of Bionty with custom terms

We should allow standalone users to quickly plug in their own terms by adding lines to the DF.
The API could be something like:
bt.extend_ontology(new_terms: pd.DataFrame)
which appends the DataFrame to the Entity DataFrame.

I think an easy way that's following the current design could be:
Simply providing the link to the dataframe instead of the url here:
Disease:
  doid:
    versions:
      2023-01-30: http://purl.obolibrary.org/obo/doid/releases/2023-01-30/doid.obo
  inhouse-vocab:
    versions:
      2023-03-01: s3://myorg/disease-vocab.parquet

Yeah that makes sense, but IMO a one-off user wouldn't have a parquet file ready.
I'm imagining the following use-case.
An ill-experienced user wants to use mondo but with 3 additional diseases that are brand new (I was told yesterday that the human disease ontology adds > 700 diseases a year). Hence, he'd just manually add these real quick to the Pandas DataFrame. I don't see such a user writing a custom parquet somewhere and adding it to the versions.

Want to emphasize that I think that we should really add support for parquet files directly. So +1

This is a core feature of lamindb.


Update Mariner waagent location from sbin to bin

Is this going to be a permanent change from Mariner side?

Yes this is a permanent change. The version of waagent in Mariner has been upgraded to a version that supports Mariner without any patches.

both test builds passed the failing step -- going to merge this and kick master builds
https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=43539229&view=results


Add gui instance hide()/show() methods

The existing open()/close() make the GUI scroll up as if the user clicked the “Close Controls” button. It’d be nice if there was a way to assert that a particular gui is hidden or shown rather than having a global toggle for show all/hide all functionality. The only API for hiding/showing currently is the non-instance-specific dat.GUI.toggleHide(). If you had multiple GUIs, that means you can’t hide one individually. Also, if, depending on how you organized your code, you want to assert that a particular gui instance is shown, you have to keep track of whether or not it is currently shown and decide whether or not to cal dat.GUI.toggleHide().
The sort of thing I’d like to be able to do:
var gui = new dat.GUI();
gui.add({x: 2}, 'x', 1, 3).onChange(function (value) {
    console.log('x changed to: ' + x);
});
gui.hide();
/* And show it in response to some event: */
gui.show();
/* And show it depending on some expression: */
gui.toggleHide(myState == 'showGui');
/* And per-gui simple toggle: */
gui.toggleHide();

wasn't documented, but there's a: GUI.closed getter/setter variable you can set/get accordingly to alter/get the state of it.

Is there a way to hide the GUI by default in the same manner as the user hits the h key?
What I tried:
closed: true  = this only hides the GUI and the "Open Controls" label is still visible
closeOnTop: true = this only moves the "Open Controls" label to the top
I need the menu to be completely hidden when entering the page and then appears when hitting the h key. Maybe someone knows a workaround?

@magdesign i think that dat.GUI.toggleHide() might do that

Fixed by @MacroMan in https://github.com/dataarts/dat.gui/pull/216.

This does not seem to work with Typescript.

The TS typings are maintained externally, and may need to be updated.


PDF freezes when opened with Firefox with HW Acceleration ON despite very powerful PC specs

Attach (recommended) or Link to PDF file here:
31) Statistica Inferenziale 6 + Prove d'ipotesi.pdf
Configuration:

Web browser and its version: FF 127 stable branch 64 bit
Operating system and its version: Windows 11 Pro 23h2 (22631.3737) - Ryzen 7800x3d - 4070ti S - 32gb DDR5 6000mhz - 2TB nvme SSD
PDF.js version: Don't know, whatever comes by default with FF127
Is a browser extension: I've disabled them all

Steps to reproduce the problem:

open the pdf I sent with HW acceleration ON (you probably need to have same cpu/gpu, can't say for sure)
scroll down till the bottom
see it freeze like in my video

What is the expected behavior? (add screenshot)
https://github.com/mozilla/pdf.js/assets/73554423/72143257-c0d3-43d0-bc66-bf22bb5ab225
What went wrong? (add screenshot)
https://github.com/mozilla/pdf.js/assets/73554423/2e01810f-865f-43fb-bebf-76bcfef37ba2
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

We are planning to disable HW acceleration for pdf.js, see https://bugzilla.mozilla.org/show_bug.cgi?id=1902012.

Sorry to re-open this, but in FF129 the issue is still present.
Is the merged pull request not added yet in the stable release?
No hurry at all, just trying to understand if the issue is still present or if another one appeared :)


Use Serialisation Size Hints for optimising buffer chunk usage

Size hints should indicate:

Whether to replace a chunk before starting serialisation (hint > remaining)
Whether to use chained buffers (hint > chunk size)

This was actually implemented with pr #98 the try_reserve(size) method is called in the serialisation method and performs some basic logic to avoid chaining.


Match hostnames case-insensitively

TODO:

[ ] check if the change to FindEntry will affect alias resolution?

To avoid affecting case-sensitive alias resolution, I ideally wanted to perform case-insensitive lookups only for keys under hosts, but doing so required more changes to the implementation I was comfortable with, and the overall approach still feels brittle. Shelving this for now and making a simple workaround in the cli/cli repo.


fix(change app description): fix description display

Description
fixed display of the description correctly
Why
When changing an app description, the german and english fields are replaced and fields should save correctly
Issue
https://github.com/eclipse-tractusx/portal-frontend/issues/551
Checklist
Please delete options that are not relevant.

[x] I have followed the contributing guidelines
[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally

@evegufy Can you please merge this PR?


How does sails default to serve assets/index.html?

I'm having an issue where I'd like to have a catchall route to point to my index.html in assets (an Angular SPA).
In config/routes.js, removing the default root route handler ('/') will cause Sails to serve index.html from assets/ by default. However, I can't find a good way to do this for a catchall route (as I have to find a way to manually serve from .tmp/public).
I've tried a few things but nothing's elegant, so I decided to consult the Sails core to see if I could find where the route resolves to index.html for the default route. I wasn't able to track it down, though. Can anybody shed some light into this?
My thinking is that if I can find where this happens, I can either create a route configuration key (like "asset" or something) to leverage this, or maybe add a hook somewhere to handle it. Something like follows:
module.exports = {
	'/*': {
		asset: 'index.html',
		skipAssets: true
	},
};

Thanks! Please let me know if this would be better posted on SO.

I think the easiest way would be to prefix your api with something like /api/something and then use the 404 to serve the index file for all 404 which do not go to /api/something

'*': {
  target: '/',
  skipAssets: true
}