Workflow not being added on refresh organization

I have a new GitHub repo that is not currently on the my workflows page, however I can't seem to add it by doing any refresh.
Refresh organisation - does not add
Refresh all workflows - fails due to https://github.com/ga4gh/dockstore/issues/2299
Tested on
DockstoreAPI - 1.6.0-rc.0
DockstoreUI - 2.3.0-rc.1
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 1.6
┆Sprint: Seabright Sprint 7 Gondola
┆Issue Number: DOCK-630

@agduncan94 please take an initial look, give me a shout if it turns hairy

Not able to reproduce this locally, even with the staging database.

What about your account? Can you replicate with a new account, might it be related to the side/tokens/something specific?

So the issue is that our library is grabbing all of our owned repositories and putting them in a mapping of repository name -> repository object. Originally we assumed this would only grab in my case, agduncan94/* repositories. We had another function to grab repositories from organisations you belong to.
Turns out "owned" repositories is not only those in your namespace (ex. agduncan94), but also include others. So if you had a repository agduncan94/foo and another one you "owned" called dockstore/foo, only one would show up in the mapping.
The function returns all repos according to the following:

List repositories that are accessible to the authenticated user (public and private) using the specified page size.
 * This includes repositories owned by the authenticated user, repositories that belong to other user, where the authenticated user is a collaborator, and other organizations' repositories that the authenticateduser has access to through an organization membership.

What we actually want is is just the first point (repositories owned by the authenticated user)

https://github.com/ga4gh/dockstore/issues/2311

Verified that refreshing github organizations now grabs repositories owned by the authenticated user even if repo has the same name or is forked from a github organization that the user also belongs to. For example, both Databiosphere/toolbox and Ldcabansay/toolbox show on refresh.
DockstoreAPI - 1.6.0-rc.1
DockstoreUI - 2.3.0-rc.2


change type of apiToken from "" to string

This will prevent typescript from throwing an error  Type 'string' is not assignable to type '""'

Thank you! 🙏


Could filtered transformations accept an optional filter_spec?

Hi Patrick, I was thinking more about #618, and I was wondering your thoughts on the following:
@partial(eqx.filter_grad, filter_spec=filter_spec)
def loss_fn(model, x, y):
    return jnp.sum((y - model(x))**2)

x, y = …
model = SomeComplicatedModule(…)
filter_spec = … # create a filter spec of model
grads = loss_fn(model, x, y)

In the above, filter_grad would take an optional filter_spec that is a prefix of model. I know the current paradigm is explicit calls to eqx.partition and eqx.combine, but I think this addition would make working with filtered transformations more user friendly for people that are new to pytrees, jax, and equinox (this is very important for my library). In general I’d like do this with filter_vmap and filter_pmap as well. What do you think?
My current solution is to create wrappers that do something like this (see here). However, I’m not a big fan of doing this in my library and am wondering if you’ve thought about if something like this belongs in equinox. I imagine there is some implementation detail that complicates things that I don’t understand here.

Haha! This actually used to exist: they got removed in Equinox v0.10.0.
In practice they were used very rarely for filter_grad and essentially never for the other transformations, so it made sense to get rid of them. This gave us dramatically simpler code -- besides being easier to maintain, I think this makes it a lot more convincing to believe that operations like eqx.filter_* really are fairly thin wrappers around their jax.* counterparts.
For this reason I'm afraid it's unlikely these will every appear in Equinox -- we already tried them and we didn't like them! :)

This totally makes sense, very good to know. If you have any warnings against doing this in practice, please let me know! I’ve implemented this in the linked code with wrappers around eqx.filter_* (which is admittedly a little tedious).

There's nothing really wrong with it. In the context of user friendliness (which you mention), I think the only thing I'd say is that it ended up being a complicated part of an API that a new user would see very early on, which was another contributing reason to its demise.


multiple changes

this PR should be merged once ploneintranet/ploneintranet.prototype#158 and Patternslib/Patterns#413 are merged.

@garbas: When you make pull requests, please provide a summary of the changes you implemented and the problem you're trying to solve with the pull request.

@jcbrand description is in commit messages

@jcbrand fixed things from your comments.


[Event Request] Page 440 Issued Reminder List

Can you expand the Event OnBeforePrintRecords with is Handled (Like in Page 438).
    [IntegrationEvent(false, false)]
    local procedure OnBeforePrintRecords(IssuedReminderHeaderRec: Record "Issued Reminder Header"; var IssuedReminderHeaderToPrint: Record "Issued Reminder Header"; var IsHandled: Boolean)
    begin
    end;

action("&Print")
            {
                ApplicationArea = Basic, Suite;
                Caption = '&Print';
                Ellipsis = true;
                Image = Print;
                Promoted = true;
                PromotedCategory = Process;
                ToolTip = 'Prepare to print the document. The report request window for the document opens where you can specify what to include on the print-out.';

                trigger OnAction()
                var
                    IssuedReminderHeader: Record "Issued Reminder Header";
                begin
                    IssuedReminderHeader := Rec;
>> NEW CODE
                    IsHandled := false;
                    //OnBeforePrintRecords(Rec, IssuedReminderHeader);
                    OnBeforePrintRecords(Rec, IssuedReminderHeader, IsHandled);
                    if IsHandled then
                        exit;
<< NEW CODE
                    CurrPage.SetSelectionFilter(IssuedReminderHeader);
                    IssuedReminderHeader.PrintRecords(true, false, false);
                end;
            }
            action("Send by &Email")
            {
                ApplicationArea = Basic, Suite;
                Caption = 'Send by &Email';
                Image = Email;
                Promoted = true;
                PromotedCategory = Process;
                ToolTip = 'Prepare to send the document by email. The Send Email window opens prefilled for the customer where you can add or change information before you send the email.';

                trigger OnAction()
                var
                    IssuedReminderHeader: Record "Issued Reminder Header";
                    IssuedReminderHeader2: Record "Issued Reminder Header";
                    PrevCustomerNo: Code[20];
                begin
                    IssuedReminderHeader := Rec;
>>NEW CODE
                    OnBeforeSendRecords(Rec, IssuedReminderHeader, IsHandled);
                    if IsHandled then
                        exit;
<< NEW CODE
                    CurrPage.SetSelectionFilter(IssuedReminderHeader);
                    CurrPage.SetSelectionFilter(IssuedReminderHeader2);
                    IssuedReminderHeader.SetCurrentKey("Customer No.");
                    if IssuedReminderHeader.FindSet then
                        repeat
                            if IssuedReminderHeader."Customer No." <> PrevCustomerNo then begin
                                IssuedReminderHeader2.SetRange("Customer No.", IssuedReminderHeader."Customer No.");
                                IssuedReminderHeader2.PrintRecords(false, true, false);
                            end;
                            PrevCustomerNo := IssuedReminderHeader."Customer No.";
                        until IssuedReminderHeader.Next = 0;
                end;
            }

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


ci: adds GITHUB_TOKEN as an env

adds GITHUB_TOKEN as an env to fix the github_token missing error during release workflow

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

v1.0.2
GitHub release

Your semantic-release bot :package::rocket:


need help with loading screen

Describe your problem here.
i did some shit to enable the loading screen and now songs refuse to load and are just stuck in the first line of the loading screen
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
i did the things people said on issues such as deleting NO_PRELOAD_ALL and #end's

https://github.com/ShadowMario/FNF-PsychEngine/issues/1912
That's literally it.
Also the loading screen has no use on Desktop builds.


I can't install on ionic 5

I get an error when I want to install the plugin in ionic 5
`No scripts found for hook "before_plugin_add".
Calling plugman.fetch on plugin "https://github.com/amicaldo/cordova-plugin-kiosk-mode"
fetch: Installing https://github.com/amicaldo/cordova-plugin-kiosk-mode to E:\Xcustomer360\apps\XcustomerAppCleanKiosko
Running command: npm install https://github.com/amicaldo/cordova-plugin-kiosk-mode --save-dev
Command finished with error code<PHONE_NUMBER>: npm install,https://github.com/amicaldo/cordova-plugin-kiosk-mode,--save-dev
Failed to fetch plugin https://github.com/amicaldo/cordova-plugin-kiosk-mode via registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Check your connection and plugin name/version/URL.
CordovaError: Error: npm: Command failed with exit code<PHONE_NUMBER> Error output:
npm ERR! code ENOENT
npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno -4058
npm ERR! enoent Error while executing:
npm ERR! enoent undefined ls-remote -h -t https://github.com/amicaldo/cordova-plugin-kiosk-mode.git
npm ERR! enoent
npm ERR! enoent
npm ERR! enoent spawn git ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR!      C:\Users\the_e\AppData\Roaming\npm-cache_logs\2021-04-28T17_29_01_044Z-debug.log
CordovaError: Failed to fetch plugin https://github.com/amicaldo/cordova-plugin-kiosk-mode via registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Check your connection and plugin name/version/URL.
CordovaError: Error: npm: Command failed with exit code<PHONE_NUMBER> Error output:
npm ERR! code ENOENT
npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno -4058
npm ERR! enoent Error while executing:
npm ERR! enoent undefined ls-remote -h -t https://github.com/amicaldo/cordova-plugin-kiosk-mode.git
npm ERR! enoent
npm ERR! enoent
npm ERR! enoent spawn git ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR!      C:\Users\the_e\AppData\Roaming\npm-cache_logs\2021-04-28T17_29_01_044Z-debug.log
at C:\Users\the_e\AppData\Roaming\npm\node_modules\cordova\node_modules\cordova-lib\src\plugman\fetch.js:140:43
at processTicksAndRejections (internal/process/task_queues.js:93:5)`
Thanks for you reply

Please, have you solved this?

Which command did you enter exactly to get this output?


Matrix Apps: Enable them by default

and remove the setting from Settings > LABS

I hope you meant: move the setting out of LABS. I would be very sad if it became impossible to disable Matrix Apps.

The initial plan was to remove them to be aligned with riot-web and riot-ios.
But we may be able to find a place for this setting elsewhere.

Currently, there is no good section in settings to host this setting, so it will stay in LABS until we reorganise this long settings page.
So, the only required change is to enable them by default so that people will be no more surprised to not find their widgets.


API - Cannot update a component status - always creates a new component

When using the /api/components API, it is not possible to update the status of an existing component.
Instead, a new component with the same name is created every time.
This occurs for both of the following JSON payloads:
{"status":"2","name":"test2"}

{"status":"2","name":"test2","id":2}

Can you confirm which version of Cacht you're using?

Sorry, I misread your issue. This is in the list for #359.

Could you try now please?

Posted data to https://status.cachethq.io/api/components
{"status":"2","name":"Website","id":3}
New result:
{"data":[{"id":1,"name":"API","description":"Used by third-parties to connect to us","status_id":1,"status":"Operational","incident_count":0,"created_at":1424680368,"updated_at":1424680368},{"id":2,"name":"Payments","description":"Backed by Stripe","status_id":1,"status":"Operational","incident_count":0,"created_at":1424680368,"updated_at":1424680368},{"id":3,"name":"Website","description":"","status_id":1,"status":"Operational","incident_count":0,"created_at":1424680368,"updated_at":1424680368},{"id":4,"name":"Website","description":"","status_id":2,"status":"Performance Issues","incident_count":0,"created_at":1424686692,"updated_at":1424686692}]}
ie a new component with id=4 was created, with the name 'Website' and the status 2 'Performance Issues'
I'm happy to send you the perl script I'm using, or add it in to the project somewhere.

@joecohens as part of #359

Roger :)

@georgehansper sorry for the delay in this. You are sending the request as a PUT method, right?

I've just tested with a PUT method and the component updated just fine :)

If you can confirm, I'll close this issue.

I'm going to close this @georgehansper if it's still a problem for you, please re-open and we'll take another look :+1:

Actually, I'm using the POST method as per the API described in:
https://docs.cachethq.io/v1.0/docs/components-api
There is no mention of a PUT method for updating components.
Can you please post a sample of the working code?
When I change the method to 'PUT' in Perl LWP, I get the following error message:
{"message":"405 Method Not Allowed","status_code":405}
The response headers include:
Server: cloudflare-nginx
Allow: GET, HEAD, POST
Are we using the same API ?

I really need to sort out the documentation :/

Commenting as I am also encountering this issue and want to stay updated. Adding my experience below:
The following creates a new component with status 2:
curl -X POST -H "Content-Type: application/json" -H "X-Cachet-Token: SECRET" http://myurl.com/api/components -d '{"status":"2","name":"Homepage","id":"1"}'
The following receives a 405 Method Not Allowed response:
curl -X PUT -H "Content-Type: application/json" -H "X-Cachet-Token: SECRET" http://myurl.com/api/components -d '{"status":"2","name":"Homepage","id":"1"}'
Changing the payload to remove the name attribute has no effect.
Would appreciate an example of what this should look like in order be able to update from API. I get the same 405 response on any update attempt (metrics too).

When you're updating a component you need to use this endpoint:
PUT https://demo.cachethq.io/api/components/:component_id

Hi, thank you for the quick response, I got it working!
For anyone else who might get stuck and reach this thread the following command is what worked:
curl -X PUT -H "Content-Type: application/json" -H "X-Cachet-Token: SECRET" http://myurl.com/api/components/1 -d '{"status":"2","id":"1"}'

Thanks @tomer-h I'm working on the documentation now too; http://docs.cachethq.io

@tomer-h just noticed that you don't need to send through the id key/value pair anymore.

When sending data to a webserver, normally there are 2 approaches:

PUT - all the data is in the URL
POST - all the data is in the body

(this is actually a requirement for the application to be 'restful'. See http://en.wikipedia.org/wiki/Representational_state_transfer)
If the Cachet API is accepting data in the body of the HTTP request, POST is a more appropriate method than PUT.
PUT should look something like:
http://myurl.com/api/components/1?status=2
or
http://myurl.com/api/components?status=2&id=1
and have no data in the body. The header can still contain 'X-Cachet-Token: SECRET'

In our API we're using POST to create and PUT to update. http://cachet.readme.io/v1.0/docs/post-parameters

The usual docs link is far too cached again...

@jbrooksuk I think Cloudflare is denying PUT requests on the 'try it out' page: http://cachet.readme.io/v1.0/docs/update-a-component
server: cloudflare-nginx
date: Mon, 16 Mar 2015 03:40:00 GMT
content-type: application/json
transfer-encoding: chunked
connection: close
set-cookie: __cfduid=dddf66179e6b0f971ba4b8ca8af959e321426477200; expires=Tue, 15-Mar-16 03:40:00 GMT; path=/; domain=.cachethq.io; HttpOnly,cachet_session=eyJpdiI6IjU4a01QdjM3ajF3OGJXeGFEOEdwTUE9PSIsInZhbHVlIjoia09HXC9jOWRaK0dXcGdXYlNTVXoxU2RnaEYxVWhHRmhLQmxneitqNXFHYU9hYUREek5yNXZON3VWMGM1Y1IyYnNpeDNMWVYyUlBcL09TdU9LdFcyVzRiQT09IiwibWFjIjoiNjEyMGE1ZmZmNTllYWMxNWM5NjIzZjBjNjYyMjMwY2JhODA2NjA1ZGQ3ZjhiZTAzNmMzNjk3NDFmN2Y0NTQzMyJ9; expires=Mon, 16-Mar-2015 13:40:00 GMT; Max-Age=36000; path=/; httponly
x-powered-by: PHP/5.6.6
cache-control: no-cache
via: 1.1 vegur
cf-ray: 1c7d6f23cb860f21-IAD

Urgh, CloudFlare.
Could you try and add a _method=PUT parameter please?

I don't think you should be running Cloudflare on the API though - I can't see any value in doing so anyway - Cloudflare is meant to cache static content and help protect against malicious traffic to websites. It's not really designed to MITM an API. Why not just have the API access directly but the websites cached behind Cloudflare?

I could turn off CloudFlare for some routes I guess.

It might be wise to have the API on a domain prefix, I.e. api.demo.cachethq.com and not have that on Cloudflare.

Perhaps in the future we'll allow the API to run from a subdomain.
Could you try with a PUT request now please?

No difference:
server: cloudflare-nginx
date: Mon, 16 Mar 2015 08:22:59 GMT
content-type: application/json
transfer-encoding: chunked
connection: close
set-cookie: __cfduid=dea8ad9763962860a9b8f8502953884ad1426494179; expires=Tue, 15-Mar-16 08:22:59 GMT; path=/; domain=.cachethq.io; HttpOnly,cachet_session=eyJpdiI6ImJGTGxKbTNQcm84Q0g0U2pPT0ROYlE9PSIsInZhbHVlIjoiS2cwdzQ5dFpUN2k1d001TkxJSVZOMEZsQWZsQ2w0UWpGMldUaDY4Njd1S1ZuU1BjbGE0cTFPSjlLOVFXOVF4Vk52Z3VNc3F0T2ZRSHdSTzVkM3BzUEE9PSIsIm1hYyI6IjI5ZGUyNTA4MzFjY2JkMjdmZDQ3NDFjYjQyNWM0ZWIwMjFmNWJiMzg2ZGQzMjQ2YjJiZmU0ZTliYzFjMjQyNDIifQ%3D%3D; expires=Mon, 16-Mar-2015 18:22:59 GMT; Max-Age=36000; path=/; httponly
x-powered-by: PHP/5.6.6
cache-control: no-cache
via: 1.1 vegur
cf-ray: 1c7f0dad45dd0f03-IAD

I don't know this system at all but is domain=.cachethq.io correct? I thought it was demo.cachethq.io ?

It's a CNAME under cachethq.io.

Might be taking a little bit to update.

OK - if you need a hand with cloudflare I'm happy to login and take a look

That may be a good idea @sammcj I'll email you the deets.

ok cool, can't promise anything but I won't break anything else.


Milestone 1 feedback

2. Project set-up: Mechanics
Comments
Where is the release?
3. Project proposal: reasoning
Comments
What packages will you use for EDA what types of methods?
What about class balance, there could be an imbalance in the classes, in which you would have to under sample or oversample. Which one will you utilize?
What about missing data, how will you handle the missing data?
For these algorithms, what packages will you use? Have you thought of using wrapper algorithms (boruta algorithm) for feature selection?
Will you do cross-validation?
A suggestion for metrics, to determine the performance of your models is Area Under Curve (AUC). The Area Under the Curve (AUC) is the measure of the ability of a classifier to distinguish between classes and is used as a summary of the ROC curve. Also look into and SHAP (SHapley Additive exPlanations) which explains the direction of each variable compared to the outcome variable.
5. Exploratory data analysis in a literate code document: VIZ
Comments
I don't understand the graphs you created, you need an explanation for all of them, as well as a clarification of all the variables. IF this is not done the EDA, which is to inform of what variables are key, and some preliminary hypothesis is useless. In addition, EDA should be able to inform you on how to do some data wrangling and i don't see those conclusions.
5. Exploratory data analysis in a literate code document: REASONING
Comments
Why are you using some of those EDA techniques? What's the purpose of a heat map etc.? Variables lists are useless unless you define what the variables represent. Needs higher resolution.

Thanks for your comments @andytai7! In regards to the project proposal, I wasn't sure whether to make changes in the proposal or just ensure that we address them in the final report. I decided to go with the later option.
Here are some specifics:
What packages will you use for EDA what types of methods?

We made mention in our final report that altair was used for EDA

What about class balance, there could be an imbalance in the classes, in which you would have to under sample or oversample. Which one will you utilize?

We mention in the final report (in the EDA section) that we do have class imbalance, and therefore we decided to optimize the class_weight hyperparameter of LogisticRegression. It turns out that setting class_weight="balanced" does improve model performance.

What about missing data, how will you handle the missing data?

We used a SimpleImputer, though there wasn't much missing data

Will you do cross-validation?

Yes, we performed cross validation as part of our hyperparameter optimization

Thank you for addressing these comments!
Best,
Andy

Hi @andytai7 ,
In addition to the response from @jcasoli , please note the following below:
Where is the release?

The release is in the github repo under the Releases tab. It was already a part of the Milestone-1 submission: https://github.com/UBC-MDS/Telco_Customer_Churn_Prediction_Group12/releases/tag/Milestone1

Why are you using some of those EDA techniques? What's the purpose of a heat map etc.? Variables lists are useless unless you define what the variables represent. Needs higher resolution.

The detail explanations for each plot and additional analysis, including Pandas profiling, were covered in the EDA notebook. In the final report, we have captured the important analysis. We have tried to use easy to interpret techniques and self-explanatory variable names, such as Total Charges. However, we will look into these again to see if something is not clear.

Hope that clarifies.

Thank you @Anupriya-Sri for more clarification.
Best,
Andy

Discussed and closed.


Initial upgrade procedure documentation

This is my first draft of documentation for our upgrade procedure.

I think you should have a pointer to the upgrade instructions at the top of the relevant install instructions.  e.g. "These instructions will take you through first time installation of Calico...  If you want to upgrade an existing version of Calico, then see..."
Do you think we need to say anything about the upgrade instructions only working to upgrade versions after 0.xx (whatever xx is, in practice)?

Thanks @ed-harrison @alexwlchan, those markups have been made.
@ed-harrison, I don't think we need that tag in the upgrade instructions at this time. I think we consider the pre-etcd days to be the dark past of this project, and so we just don't really want to worry about it.

LGTM


RBD: Image metadata created by cephcsi on rbd images is not  mirrored or copied  when clone is created.

Currently, these are the metadata keys used by cephcsi to set on rbd images
// Encryption

// image metadata key for encryption
encryptionMetaKey = ".rbd.csi.ceph.com/encrypted"
// metadataDEK is the key in the image metadata where the (encrypted) DEK is stored.
metadataDEK = ".rbd.csi.ceph.com/dek"

// Thick Provisioner
// image metadata key for thick-provisioning
thickProvisionMetaKey = ".rbd.csi.ceph.com/thick-provisioned"

From RBD keys starting with ".rbd" are considered internal and not mirrored and such keys are not copied when cloning or deep-copying locally either.
We need to change the key from .rbd to rbd so that metadata is available when mirroring is enabled  or when we create internal clones
This issue is to track below items

[ ] Change metadata key  for thick provisioning
[ ] Change metadata key for clones
[ ] During other operations like (snapshot and clone) copy keys only if the key is starting with .rbd

More details at https://github.com/ceph/ceph-csi/issues/2121

To summarize, because of this one we cannot support mirroring of the Thick, Encrypted PVC created from older cephcsi releases.


Update @modulus/standard

Bump @modulus/standard from v0.6.0 --> v1.0.0

Closes #12

👍

:+1: but are you gonna relint?

Already did. Passed 😄

:shipit:


Submit Queue: Retest PRs every 48 hours

We don't actually test every PR every 48 hours. Only those which seem close to merge. They have LGTM, their tests look good, etc.  If this were to run right this instant, it would hit against 4 PRs.

fixes https://github.com/kubernetes/contrib/issues/197


Fixes spelling in README

Sorry to be that guy 🙈 Was reading over the README and noticed some small spelling mistakes.

@ZachOrr Lovely, thank you 👍


Which ATP Plan is required? Why ATP and not AIP?

Is it ATP Plan 1 or ATP Plan 2 required to apply WIP policy based on sensitivity label? Is that capability going to be remain within ATP in the long term, or is there a chance it will be moved to the AIP license where the other sensitivity label capabilities such as encryption and scenarios of protection based on labels are better aligned?
Also, it's really confusing to use "endpoint DLP" and "WIP" interchangably when "DLP" is its own thing within O365.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 561d91d8-458d-bc0c-45af-c0a9ccacee93
Version Independent ID: 7c1fd8f1-74b6-f7d4-fcb0-0e41a0d6ff42
Content: How Windows Information Protection (WIP) protects files with a sensitivity label (Windows 10) - Microsoft 365 Security
Content Source: windows/security/information-protection/windows-information-protection/how-wip-works-with-labels.md
Product: w10
Technology: windows
GitHub Login: @DulceMontemayor
Microsoft Alias: dansimp

The issues section of this repository is intended for documentation and content-related problems and fixes.
Windows Community would be a better channel to seek answers to your query.
Thank you.


UI: Enable Targets page in Querier UI

Signed-off-by: Prem Saraswat<EMAIL_ADDRESS>

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

Added the missing field globalUrl in proto, which was used in the UI
Added Targets page to the Querier nav bar

Verification
The json response format of Querier API matches with the response from Prometheus API.

maybe it's time to make --target & other flags not hidden anymore?

Oh, I was not aware that it is hidden. I also agree to make this not hidden.

maybe it's time to make --target & other flags not hidden anymore?

Oh, I was not aware that it is hidden. I also agree to make this not hidden.

Should we unhide them in a separate PR before merging this one? :P

maybe it's time to make --target & other flags not hidden anymore?

Oh, I was not aware that it is hidden. I also agree to make this not hidden.

Should we unhide them in a separate PR before merging this one? :P

:+1:

I would propose to not UNHIDE them until @hitanshu-mehta project of unificating those into single endpoint flag as planned in https://thanos.io/tip/proposals/202101_endpoint_discovery.md/ WDYT?

I think it would lead to lots of questions about what is that page for and why one cannot any instructions about how to use it :thinking:

So I guess one solution is to make targets page working but leave it out from the nav bar (similar to a hidden flag, a hidden page). So, whenever we decide to make the flag non-hidden (or we move to the --endpoint flag), we can make the page non-hidden too. WDYT?

I have rebased this and made the Targets page hidden from Navbar (one can manually go to /new/targets though). If we want to unhide the --target flag and the Targets page, we can do that in a separate PR.


Implement CI for releases

As of today, I am doing releases locally in a clumsy way:

Update the release tag on Docker Compose and VS Code config files
Add release commit and tag
Rebuild and push the containers locally with the new tag

But the release process should be automated to avoid me missing steps or making mistakes.

A big chunk of this ticket's goal has been implemented as part of https://github.com/leograba/TorizonOSBuildStatus/pull/25
It automates the process of updating the release version, commit and tag, and then open a PR.
The next steps will be to improve the test pipeline, and implement steps to build (or re-tag rc) the final containers.


Linting warnings are not a fun developer experience.

Currently in js-ipfs there are 98 linting warnings in master. I don't know when the decision was made not to fail CI on these but I think it's worth revisiting this.
As a developer wanting to contribute to a repo if I have to scroll through several pages of output to try to see if any of my changes introduced errors is very frustrating.  This is compounded by the fact that linting fails locally on warnings but passes CI.
I think we should fix the warnings in all the repos and enforce them in CI.

Absolutely, I agree. Something quick we can do now that wouldn't affect things as far as I know, is to just not display warnings at all.
The alternative solution is to turn warnings into errors, but then suddenly linting on CI is gonna start breaking everywhere, even for unrelated changes and that feels a bit too much.


getMarkdownText for link

Case 1
if source text:
[qqqq](https://t.me)

then getMarkdownText work fine:
[qqqq](https://t.me)

Case 2
but if source text with escaped square brackets:
[\[qqqq\]](https://t.me)

then getMarkdownText work wrong:
[qqqq]

getMarkdownText returns a user-friendly formatted Markdown text by an ordinary formatted text. It doesn't receive anything like "[qqqq]".


Improve owner/maintainer documentation

From user testing:
On the 'collaborators' page in the management UI, we currently have information about what an owner and maintainer can do:

I think that we could improve this to be more specific about what each user can delete:

Owner
Owns a project, may add other collaborators for that project, and upload releases for a project.
May delete files or releases. Can delete the entire project.
Maintainer
May upload releases for a project. Cannot add collaborators, delete files, delete releases or delete the project.

cc @brainwane for help with this text.

Good First Issue: This issue is good for first time contributors. If you've already contributed to Warehouse, please work on another issue without this label instead. If there is not a corresponding pull request for this issue, it is up for grabs. For directions for getting set up, see our Getting Started Guide. If you are working on this issue and have questions, please feel free to ask them here, #pypa-dev on Freenode, or the pypa-dev mailing list.

This is a followup to #2745, and, to some extent, to #2059.

Fixed in #3313.


chore(main): release homestar 0.5.0

:robot: I have created a release beep boop
0.5.0 (2023-11-09)
Features

improve the exports (dd980af)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fission-codes/stack/releases/tag/homestar-v0.5.0 :sunflower:


feature request: shift-tab

Please add a mapping shift-tab to go back one entry;
or stop shift from resetting the current selection to the first entry.
It is very common in applications to be able to select the next entry with tab and the previous with shift-tab. since tab works in tofi, one would assume that shift-tab does too, but instead the selections resets and then you cannot simply use the back arrow anymore which is annoying.
Great tool, kr

Alright, this should be working in ef585fcbe156e6622222cd4a018776a5e1fb194b. I hadn't noticed that shift/ctrl etc. were resetting the selection, thanks for mentioning that.
I think one of the next things I should do is clean up the keybindings and make them customisable, as it's a bit messy and inflexible right now.


Compiler warnings

I get 2 compiler warnings that should be very easy to fix:
[C++ Warning] tinyxml2.cpp(474): W8008 Condition is always true
[C++ Warning] tinyxml2.cpp(504): W8008 Condition is always true
Because digit is an unsigned int you don't have to test if it's >= 0, so that can be left out.

Pull request please, thanks!

Actually these warnings are completely useless.

Created pull request...

Thanks!


Use Python 3.11 for upstream CI build

Hopefully closes https://github.com/dask/dask/issues/10593
https://github.com/dask/dask/pull/10594 extended with fixes for https://github.com/pandas-dev/pandas/pull/55636

this looks like it's got a lot of failures now as a result of NEP 50


Cannot create Location by Java Client

Affected module
Does it impact the UI, backend or Ingestion Framework?
Backend.
Describe the bug
A clear and concise description of what the bug is.
When I use the Java Client:
        <dependency>
            <groupId>org.open-metadata</groupId>
            <artifactId>openmetadata-java-client</artifactId>
            <version>0.11.1</version>
        </dependency>

to create location, it responsed 400:
{
	"code": 400,
	"message": "Unrecognized field \"extension\" (class org.openmetadata.catalog.api.data.CreateLocation), not marked as ignorable (8 known properties: \"owner\", \"path\", \"tags\", \"name\", \"description\", \"displayName\", \"locationType\", \"service\"])\n at [Source: (org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream); line: 1, column: 56] (through reference chain: org.openmetadata.catalog.api.data.CreateLocation[\"extension\"])"
}

To Reproduce
Screenshots or steps to reproduce
CreateLocation createLocation = new CreateLocation();
Location location = locationsApi.createLocation(createLocation);

Expected behavior
A clear and concise description of what you expected to happen.
Response 200, and get the location I created.
Version:

OS: [e.g. iOS]
Python version:
OpenMetadata version: 0.11.0
OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==XYZ]

Additional context
Add any other context about the problem here.

@TheFu527  Closing this , need to use OpenMetadata or we can add apiClient.getObjectMapper().setSerializationInclusion(JsonInclude.Include.NON_NULL); in case we want to build the client manually do it manually


Draft CorrelationId using Activity

Let me know what you think. It will bring some hours of work so I will only continue if you agree that it would be a cool feature and we should have it implemented like the WebHost and the HttpClient

@msallin the activity stuff it is definitely a good idea. A couple of remarks:

I just would like to decouple it from the Consumer and maybe even outsource it into another package
Some time ago I added the behaviors with exactly such kind of scenario in mind, have a look and see if we could move the magic from the consumer into a behavior! https://beagle1984.github.io/silverback/docs/quickstart/behaviors

Let me know what do you think. I'll be out a couple of days but I'll have a closer look as soon as I'm back (saturday or sunday).
Thanks for contributing!

Will reopen it as soon as I got the first working (and understandable) version.


gsasl: 1.10.0 -> 2.0.1

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1131

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1177

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 186893 run on x86_64-linux 1

15 packages built:

automysqlbackup
curlFull
dico
gobby
gsasl
gsignondPlugins.sasl
haskellPackages.gsasl
libinfinity
libjreen
mailutils
mpop
msmtp
pokerth
pokerth-server
vmime

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

dico:

warning: EvalError
Cannot evaluate attribute ‘dico’ in ‘/nix/store/a6pkvxssrph09ih0xkaxrwmx9mxllm62-nixpkgs’.

gobby:

warning: EvalError
Cannot evaluate attribute ‘gobby’ in ‘/nix/store/a6pkvxssrph09ih0xkaxrwmx9mxllm62-nixpkgs’.

gsasl:

warning: EvalError
Cannot evaluate attribute ‘gsasl’ in ‘/nix/store/a6pkvxssrph09ih0xkaxrwmx9mxllm62-nixpkgs’.

gsignondPlugins.sasl:

warning: EvalError
Cannot evaluate attribute ‘gsignondPlugins.sasl’ in ‘/nix/store/a6pkvxssrph09ih0xkaxrwmx9mxllm62-nixpkgs’.

haskellPackages.gsasl:

warning: EvalError
Cannot evaluate attribute ‘haskellPackages.gsasl’ in ‘/nix/store/a6pkvxssrph09ih0xkaxrwmx9mxllm62-nixpkgs’.

libinfinity:

warning: EvalError
Cannot evaluate attribute ‘libinfinity’ in ‘/nix/store/a6pkvxssrph09ih0xkaxrwmx9mxllm62-nixpkgs’.

libjreen:

warning: EvalError
Cannot evaluate attribute ‘libjreen’ in ‘/nix/store/a6pkvxssrph09ih0xkaxrwmx9mxllm62-nixpkgs’.

mailutils:

warning: EvalError
Cannot evaluate attribute ‘mailutils’ in ‘/nix/store/a6pkvxssrph09ih0xkaxrwmx9mxllm62-nixpkgs’.

mpop:

warning: EvalError
Cannot evaluate attribute ‘mpop’ in ‘/nix/store/a6pkvxssrph09ih0xkaxrwmx9mxllm62-nixpkgs’.

pokerth:

warning: EvalError
Cannot evaluate attribute ‘pokerth’ in ‘/nix/store/a6pkvxssrph09ih0xkaxrwmx9mxllm62-nixpkgs’.

pokerth-server:

warning: EvalError
Cannot evaluate attribute ‘pokerth-server’ in ‘/nix/store/a6pkvxssrph09ih0xkaxrwmx9mxllm62-nixpkgs’.

vmime:

warning: EvalError
Cannot evaluate attribute ‘vmime’ in ‘/nix/store/a6pkvxssrph09ih0xkaxrwmx9mxllm62-nixpkgs’.


Ordering Data section articles

The Data on the Blockchain section is a good place to start because it provides a general overview of Data on blockchains. This will give the reader a good foundation before they move on to the more specific topics of NEAR Data Flow and Token Transfer Flow.
The NEAR Data Flow section and the Token Transfer Flow section are related, so it makes sense to put them together. The Token Transfer Flow section even references the NEAR Data Flow section as it is previous article, so it is helpful to have those two sections in close proximity.

@mlibre , if you want to change the sort order, you should edit the sidebars.json file

@mlibre , if you want to change the sort order, you should edit the website/sidebars.json file

Oh. did not know. fixed!


Web Server: duplicate flow parameters after closing the popup.

This is a low priority bug, but most likely an easy one to fix, and quite disturbing sometimes: basically, when you Prepare execution, close the popup, and open it again, overridden properties appear duplicated in the Flow parameters tab.
How to reproduce it

Open any flow, and click Schedule / Execute Flow;
Select the Flow parameters tab;
Override a property of your choice (say foo = bar);
Run the flow
Once execution is completed (either with a success or with a failure), open it and click Prepare Execution;
Close the popup by either hitting Esc or clicking the Cancel button;
Click on Prepare Execution again;
Select the Flow parameters tab.

Expected behaviour: the foo = bar overridden parameter appears only once.
Actual behaviour: it appears twice.

Thanks for reporting this issue and the detailed repro steps!
Are you interested in fixing this issue? Please see the updated dev guide for instructions.
https://github.com/azkaban/azkaban/blob/master/CONTRIBUTING.md

Hi,
I worked on this today, and managed to write a fix. I'll push it later tomorrow, after a few more checks.
I also took the chance to fix another small bug on the flow parameters input, I hope it won't be a problem if I push them together.

Cool. Thanks.
I would suggest a separate PR for unrelated changes. It will increase your chance of getting a quicker review.

Sure, I'll open another bug then, and submit two PRs. Thanks

Thanks!


zenodo dataset has two versions

The zenodo dataset has two versions, which one to use?
https://zenodo.org/record/6034088

The newer one

The Zenodo dataset proteins are different from the original PDBBind. Can you explain how these were processed? I did not see any details in the paper or code.
Thanks!


[Mobile/iOS/UI] Token balance can be truncated & show currency

Wallet balance should be labeled with G$

verified


previousFlags private property?

Hi, how can i know previous states of reachability (without saving it locally) in reachabilityChanged notification handler?
'previousFlags' property is private even though its marked under public properties (mistake?)

Yeah - that was a mistake. Currently you need to save the state locally. I'm considering updating the whenReachable  closure signature to something like:
(status: NetworkStatus, previousStatus: NetworkStatus, reachability:Reachability) -> ()
I'm guessing that would solve your problem?


Night mode tint color, menu text color

It would be great if there is possibility to also set tint color, text color, or highlighted text color in night mode. For example tint color of bar button items in navigation bar.

Do you want a different tintColor while in night mode?

there is a parameter for setting these colors, https://github.com/FolioReader/FolioReaderKit/blob/master/Source/FolioReaderConfig.swift#L106


Broken links in README.md.

📚 Documentation
Hello,
There are broken links in README.md on  Dueling-DQN and Reinforce sections.

@ninfueng nice, mind send a quick PR?

Jumping in because I noticed that the DQN link (listed under Examples) in the pytorch-lightning docs is also broken. They all point to https://pytorch-lightning-bolts.readthedocs.io/en/latest/reinforce_learn.html. From PyTorchLightning/pytorch-lightning-bolts#192 it seems that links are broken because RL was temporarily removed from master. When building the bolts docs from the master_RL branch the links all work. Not sure where they should point to until RL is added back?

@Borda I do not mind but somehow the links are working again. Maybe I should close this issue?

then all goos lol :] anyway thx for your report... 🐰


Error building from source

Hi all,
I'm trying to build TF from source so that I can run it in development mode and be able to expand the functionality of some of the modules, but am running into some snags with the bazel building.
Environment info
Operating System:
Mac OSX Yosemite
If installed from source, provide

The commit hash (git rev-parse HEAD)
ec7f37e40fedb23435bfb7e28668e5fa63ff52f3

The output of bazel version
Build label: 0.3.2-2016-10-22 (@088bbc6)
Build target: bazel-out/local-    opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Sun Oct 23 00:04:18 2016<PHONE_NUMBER>)
Build timestamp:<PHONE_NUMBER>
Build timestamp as int:<PHONE_NUMBER>

Running: bazel build -c opt //tensorflow/tools/pip_package:build_pip_package --verbose_failures
gives
WARNING: Sandboxed execution is not supported on your system and thus hermeticity of actions cannot be guaranteed. See http://bazel.io/docs/bazel-user-manual.html#sandboxing for more information. You can turn off this warning via --ignore_unsupported_sandboxing.
ERROR: /Users/mihaileric/Documents/Research/tensorflow/tensorflow/python/BUILD:1806:1: in cc_library rule //tensorflow/python:tf_session_helper: non-test target '//tensorflow/python:tf_session_helper' depends on testonly target '//tensorflow/python:construction_fails_op' and doesn't have testonly attribute set.
ERROR: Analysis of target '//tensorflow/tools/pip_package:build_pip_package' failed; build aborted.
INFO: Elapsed time: 0.848s

I'm having a lot of difficulty interpreting these error messages  and am not finding too much on Stack Overflow or other TF git threads. Any help would be greatly appreciated!

@mihail911 : Thanks for the error report. There indeed seems to be an error in the BUILD file, tehre the //tensorflow/python:tf_session_helper target has a dependency on a library meant only for tests. That dependency shouldn't exist and I'll try to clear that up.
Amusingly though, this was not an error till very very recently. Since you're using bazel built from source, it includes the change https://github.com/bazelbuild/bazel/commit/5f026f96118e76c8a6357c61e5710e0bd1bf0f54 , which makes this an error.
As a short term workaround for you, can you use the release version of bazel (0.3.2?) instead of from head. I'm going to try to fix the TensorFlow BUILD file regardless

Amusingly though, this was not an error till very very recently. Since you're using bazel built from source, it includes the change bazelbuild/bazel@5f026f9 , which makes this an error.

Ah. I have the same issue :-)

(and, yes, doing git checkout 0.3.2 before building bazel does indeed workaround the issue)

I can confirm that the above fix by @asimshankar does work. Thanks for the help!

can confirm @asimshankar fix. Thanks!

I have same issue using bazel 0.4.0 on Ubuntu 16.0.4

Please update to a recent tenorflow.

@drpngx Hello, which TF version would that be?
I'm also having this issue with the current v0.11.0 RC2 release. Also using bazel 0.4.0 on Ubuntu 16.04.
Note that @asimshankar closed his merge request https://github.com/tensorflow/tensorflow/pull/5144 stating

Nevermind, this fix doesn't work. Need something else.

@jart I think fixed this, I think. Can you confirm?

@drpngx Ok, it works with a more recent version than v0.11.0 RC2 (I used SHA 9d045888a3b565e856287381b581eed02750f976). It also compiles in v0.11.0 RC2 by just commenting out "testonly = 1" in tensorflow/python/BUILD like you did it in your branch a few posts above.

Great, thanks!

I'm having the same problem on the latest release v0.11.0, which was released just two days ago. Did the fix not make it to the latest release? I'm using bazel 0.4.0

@waleedka : The fix (https://github.com/tensorflow/tensorflow/commit/c8929e2e6e1dcb7e8e0feda6f917bf9b61d851b1) was not included in 0.11. You'll have to manually remove testonly=1 from tensorflow/python/BUILD as mentioned above.

I am still having this issue, same error code ;[i followed this guide](https://github.com/tensorflow/models/tree/master/syntaxnet#getting-started), do you have a quick fix ?

@Ecolow : Unfortunately, the syntaxnet model that you're using is currently pinned to a specific snapshot of the TensorFlow repository and it does not update with changes to the TensorFlow repository. So, the workaround for now would be to remove testonly=1 from the snapshot of the TensorFlow repository it uses - (inside tensorflow/models/syntaxnet/tensorflow/tensorflow/python/BUILD)

I just tested with the master branch and got the same error. I confirmed that the testonly = 1 flag has been removed, so there might be another issue.
I did find another fix, though. Adding the bazel option --spawn_strategy=standalone  solves the problem for me. It worked when I compiled inside a Docker container, and it also worked when compiling on a native linux box.
And in case it's relevant, I should also mention that I'm not compiling tensorflow itself, but rather compiling a C++ app that has tensorflow as a dependency, and this app is in a separate folder and links to tensorflow in the WORKSPACE file.

I have the similar issue in my Macbook Pro with macOS Sierra+pip 2.7+bazel 0.4.0+latest master branch of tensorflow/models. I solved the problem by remove "testonly=1" from /private/var/tmp/_bazel_macusername/temphashid/external/org_tensorflow/tensorflow/python/BUILD. I don't know why but I did this change and it works for me.

For me, deleting testonly=1 from BUILD fixed the problem.

I have the same issue with a fresh clone from today (commit=821d3da7b4bffc199553d3adc46b706fb7794f91)


add test for run --ip

ping @dongluochen

Likely need to change space to tab in the test file.

@dongluochen my bad, PTAL

ping @abronan

LGTM

test failure unrelated

LGTM.


Permissions Issue on winget installation

When installing clink via winget it gets written to "Programm File (x86)" If then trying to write the Config File it shows some lua error, maybe there could be a notice retry as admin or so, like you can in vscode.

What "Config File"?  Do you mean "flexprompt_autoconfig.lua"?
How is flexprompt_autoconfig.lua getting written to Program Files?
It should be getting written to the directory that contains the flexprompt_wizard.lua file.
Do you have Lua script files in Program Files?
How did they get there?
They don't belong in Program Files.

What "Config File"?  Do you mean "flexprompt_autoconfig.lua"?
How is flexprompt_autoconfig.lua getting written to Program Files?
It should be getting written to the directory that contains the flexprompt_wizard.lua file.
Do you have Lua script files in Program Files?
How did they get there?
They don't belong in Program Files.

Oh I misunderstood that part of the config, I thought it belongs to the first entry of the scripts block inside clink info.
Yeah, then all makes sense.
Should clink_start.cmd also go into that other scripts folder?

Clink doesn't tell you where to put things.  You put there where you want them, and tell Clink where they are.  And to help getting started fast without needing to configure a lot of things, there are some default places it looks.
Re: Lua script directories
That lists the places Clink is currently configured to look for Lua scripts, in the order that they're loaded from.
See Location of Lua Scripts for more info.
You could make a directory where you put all your scripts, and add it to the list via any of the ways listed there.
Or you could have multiple script directories and add all of them.  E.g. one directory for clink-completions repo, one for clink-flex-prompt, one for clink-gizmos, one for your own custom scripts, etc.
Re: clink_start.cmd file
See Startup Cmd Script.
If you don't specify a specific file via the clink.autostart setting, then it looks in the places mentioned there by default.

P.S.  If you install via the setup exe (and winget does, because winget doesn't know how to install from zip files, unfortunately) then by default it will install Clink into Program Files.  Because of how Program Files works, that means you can't/shouldn't put scripts in the Clink program directory.
But if you install Clink into a different directory, then you can put scripts in the Clink program directory.
That's just how Windows works.

Oh okay I see. Thanks yeah then no problem :)
Thanks btw. really nice project!


chore: bdd-spring-1575438004 to 0.0.1

chore: Promote bdd-spring-1575438004 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Version 1.2.2 openshift-install-powervs the SNAT setup appears to change after a  running machine config to set SMT

Brand new Cluster in Toronto Colo,
Create Cluster no issues testing each node with ping -c 3 <IP_ADDRESS> ; curl https://www.google.com all works.
After running OCP machine config to set SMT levels on Worker nodes 4 of the 6 fail the above tests now.
Two still work as desired.
failing worker-0
2: env2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether fa:f7:90:6a:40:20 brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/22 brd <IP_ADDRESS> scope global dynamic noprefixroute env2
valid_lft 10425sec preferred_lft 10425sec
inet6 fe80::f8f7:90ff:fe6a:4020/64 scope link noprefixroute
valid_lft forever preferred_lft forever
working worker-3
2: env2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether fa:57:b5:ab:dc:20 brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/22 brd <IP_ADDRESS> scope global dynamic noprefixroute env2
valid_lft 8597sec preferred_lft 8597sec
inet6 fe80::f857:b5ff:feab:dc20/64 scope link noprefixroute
valid_lft forever preferred_lft forever
Route failing worker
[root@tor46-23-2a70-tor01-worker-0 ~]# ip route show
default via <IP_ADDRESS> dev env2 proto dhcp metric 100
<IP_ADDRESS>/14 dev tun0 scope link
<IP_ADDRESS>/16 dev tun0
<IP_ADDRESS>/22 dev env2 proto kernel scope link src <IP_ADDRESS> metric 100
route working node
[root@tor46-23-2a70-tor01-worker-3 ~]# ip route show
default via <IP_ADDRESS> dev env2 proto dhcp metric 100
<IP_ADDRESS>/14 dev tun0 scope link
<IP_ADDRESS>/16 dev tun0
<IP_ADDRESS>/22 dev env2 proto kernel scope link src <IP_ADDRESS> metric 100

probable solution of the problem:
If bastion is rebooted any time we could see issues with the SNAT GW as  ethtool settings  are not persistent across reboot.  The known fix/workaround of disabling CSUM offloads must be either re-run after a  reboot, or on RHEL the ethtool settings can be made persistent by running: nmcli con mod <NIC> ethtool.feature-rx off.

@o10222 : Please confirm if this solves the issue .

There should be a PR to make this change in the code - https://github.com/ocp-power-automation/ocp4-upi-powervs/blob/master/modules/5_install/install.tf#L242
cc @Prajyot-Parab @cs-zhang @aishwaryabk


add: requests to Pipfile

Codecov Report

Merging #1050 (a4c9e5e) into main (0e9737d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1050   +/-   ##
=======================================
  Coverage   78.21%   78.21%
=======================================
  Files         151      151
  Lines        5394     5394
  Branches      865      865
=======================================
  Hits         4219     4219
  Misses       1043     1043
  Partials      132      132

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0e9737d...a4c9e5e. Read the comment docs.


EN Content: File uploader component

Summary: Documentation of component guidance in EN for the File uploader component on the Design System website.
Including use cases, how to use guidance, accessibility guidelines and more.
Acceptance Criteria:

[x] Component Kickoff
[x] Component review
[x] Sync with Dev and Design
[x] Research and consulting other design libraries
[x] Component ID (name, definition, example image
[x] Use case (when to use guidance & related components)
[x] How to use guidance
[x] Accessibility guidelines
[x] Inclusive language
[x] Descriptive text for images
[ ] Translation & Localization
[ ] Bilingual review – content design
[ ] Ensure consistency: ordering, terminology, high level voice/tone/style
[ ] Final review

Pending @SmartMouthWords  we will be able to send this to translation

@dylanzheng94 possible to get a link to this file for review?

Reviewing English draft 👀
https://docs.google.com/document/d/1z-te5Aa8FfZIXxHvPRNH3y6UOIv-UeSoQA_-jee8QrU/edit

Reviewed draft and added comments. Meeting with Dylan and Anik today to review and clarify sone outstanding questions about:

file uploader capabilities and options for users
relationship between uploading a file, removing a file, and submitting
error validation
plain language equivalents

✅ Final bilingual content review complete
🚀 Ready for dev

EN: https://docs.google.com/document/d/1z-te5Aa8FfZIXxHvPRNH3y6UOIv-UeSoQA_-jee8QrU/edit
FR: https://docs.google.com/document/d/17SfiyWnxd8E3m9-jlxk-ZLBQBVGwAeZ4U-sFP_Vo_vk/edit

CC @ethanWallace @melaniebmn @dylanzheng94  @ClementineHahn

PR to add file uploader content to the documentation site:
https://github.com/cds-snc/gcds-docs/pull/175


New command infers index-id from the index-uri

Right now the index-id is inferred from the index storage uri...
I wonder if this is a good idea?

@guilload  @fmassot

This idea came to my mind when I updated the CLI. I like setting the ID explicitly, it's clearer for the user.
And if we set the metastore-uri in the context, I think we're good.

Assigning to @evanxg852000:

add an index-id option to all commands and stop extracting the index ID from the index URI.
clean up code, i.e., remove functions such as extract_index_id_from_index_uri.
use env variable QUICKWIT_METASTORE_URI as fallback for metastore-uri.

Now, one limitation is that for single-file-metastore-backed-indexes, quickwit serve can only serve multiple indexes sharing the same parent directory.


V2 🚀

Resolvers V2 🚀
Root branch for V2 work.
Global improvements
Breaking changes: no  🟩

Add code of conduct
Add contributing
Add issue template
Add funding
Release process: add beta branch
Vest: fix validate all criteria #110
Better TypeScript support #110
Add tests #110

Better modules support - https://github.com/react-hook-form/resolvers/pull/104
First of all, huge thank to the preact hard work. This PR is heavily inspired of their modules structure.
Breaking changes: no  🟩
Related: https://github.com/react-hook-form/resolvers/issues/71 & https://github.com/react-hook-form/resolvers/issues/100

Remove IE11 support
Move resolvers into separate folders
Use microbundle to generate bundles
Multiple bundles per resolver: CJS, ESM, UMD (modern coming later)
Add exports map in package.json + support node 13 (thank to preact)

Can we remove transformToNestObject import from react-hook-form?
// Todo: to be removed
import set from '../utils/set';
import isKey from '../utils/isKey';
import { FieldValues } from '../types';

export default (data: FieldValues, value: Record<string, any> = {}): any => {
  for (const key in data) {
    !isKey(key) ? set(value, key, data[key]) : (value[key] = data[key]);
  }
  return value;
};

I think we can export set function from react-hook-form.

Can we remove transformToNestObject import from react-hook-form?
// Todo: to be removed
import set from '../utils/set';
import isKey from '../utils/isKey';
import { FieldValues } from '../types';

export default (data: FieldValues, value: Record<string, any> = {}): any => {
  for (const key in data) {
    !isKey(key) ? set(value, key, data[key]) : (value[key] = data[key]);
  }
  return value;
};

I think we can export set function from react-hook-form.

Can we remove transformToNestObject import from react-hook-form?
// Todo: to be removed
import set from '../utils/set';
import isKey from '../utils/isKey';
import { FieldValues } from '../types';

export default (data: FieldValues, value: Record<string, any> = {}): any => {
  for (const key in data) {
    !isKey(key) ? set(value, key, data[key]) : (value[key] = data[key]);
  }
  return value;
};

I think we can export set function from react-hook-form.
I did a quick test by removed that function transformToNestObject, looks like only vest needs it.

Yes you can replace this function

Can we remove transformToNestObject import from react-hook-form?
// Todo: to be removed
import set from '../utils/set';
import isKey from '../utils/isKey';
import { FieldValues } from '../types';

export default (data: FieldValues, value: Record<string, any> = {}): any => {
  for (const key in data) {
    !isKey(key) ? set(value, key, data[key]) : (value[key] = data[key]);
  }
  return value;
};

I think we can export set function from react-hook-form.
I did a quick test by removed that function transformToNestObject, looks like only vest needs it.

Yes you can replace this function

I will release a patch on react hook form 6.14.3 to export set and send you a PR.

I will release a patch on react hook form 6.14.3 to export set and send you a PR.

Hey @jorisre,
More of a question, Do we need to include the src folders? cause i didn't include src in react-hook-form.

Hey @bluebill1049
I'm not sure to understand, what's your needs ?

It's minor don't worry about it @jorisre. I was referring to the src folder been generated inside of dist during the build.

I noticed that the superstruct types are missing from the root of the package. Is that normal? (2.0.0-rc.1)


arguments.length will always be the same as n

https://github.com/ramda/ramda/blob/998f798d9ac6297bb9f5b45136e3ff06a56df09a/source/constructN.js#L48-L49
arguments.length will always be the same as n, so there's no need to dynamically calculate arguments' length. And switch(n) may be more clear to source code readers?

I think you're right, because of the currying, but I would like to think it over a bit more to make sure there are no corner cases.

nAry but not curry, guarantees that n equals to arguments.length.
nAry can limit number of parameters and arguments more strictly than _arity and curryN.

I was wondering about the case where someone used this with a consructor that has optional parameters, ones that are baked in by constructN.  When called with fewer than n arguments, I had been thinking, there might be some difference in behavior because arguments.length is less than n.  But because of the currying, that would just return a function expecting the remaining ones.
It was because I considered this, even though I quickly saw that it didn't matter, that I want to spend a little time ensuring that there are no additional such cases that actually matter.


Fixed tutorial link

The installation tutorial is not available in 3.9 docs, so I changed the link to 4.0 where it can be found.

@mabelzhang related to #146.


Provisioning cache for bicep-provider

fix: https://github.com/Azure/azure-dev/issues/376
This PR adds local and remote cache for bicep.
The feature is added as an alpha-feature (requires manual enablement).
Once enabled, azd will create a bicep.cache file after azd provision succeeds.
The file is saved within the environment (local files). Allowing each environment to have its own cache.
After azd creates a deployment-plan (after compiling bicep), if there is a cache file for the environment, azd will check if it is the same and skip provisioning if yes.
Users can also enable remote-cache (this pr adds support for Azure Storage blobs).
Remote-cache enables working locally and also from GitHub pipelines, for example.
User can turn remote-cache per environment by setting an env-var with the configuration for the remote-cache.

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/2691/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2691/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2691 --version '' --verbose --skip-verify

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

Windows
PowerShell install
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2691/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/2691/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2691' -Version '' -SkipVerify -Verbose;"

MSI install
powershell -c "irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2691/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/2691/azd-linux-amd64.tar.gz
ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2691/azd-linux-arm64-beta.tar.gz

MacOS -

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

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

MSI

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

Container
docker run -it azdevcliextacr.azurecr.io/azure-dev:pr-2691

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: 09/02/2023
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 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 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: Lists all configuration values.
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 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
Lists all configuration values.
Synopsis
Lists 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 list [flags]

Options
      --docs   Opens the documentation for azd config 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 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 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 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.
  -h, --help                  Gets help for init.
  -l, --location string       Azure location for the new environment
      --subscription string   Name or ID of an Azure subscription to use for the new environment
  -t, --template string       The template to use when you initialize the project. 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                  Deploys 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.

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.
      --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 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

In our discussion today we talked about what sort of flag we'd want to use to opt out of this behavior.  Canidates were --force and --no-cache.  I think that --no-cache is better here.  --force is nice because it's more general, and perhaps makes sense to be used by different IaC backends (where as cache is very specific to this bicep provider), but I think we want to save --force to mean "This may warn me about something, and if it doesn, silence the warning and continue" as we have for things like azd down.
I don't think it's worthwhile to add --no-cache to azd up yet, but if we did need to expose it because we want to flow the value to the provision sub-command, a --no-cache on azd up doesn't seem so bad.
One thought - If we move to the model where the deployment object is the source of truth, this does feel a little less like caching as when previously proposed, and we kept literal cache files.  Now its more of a "if the deployment we would run matches the previous deployment (same template hash and parameters) then assume the infrastructure is already up to date, and skip it".  I'm wondering if something like --assume-outdated or --force-update could be better.
Maybe @savannahostrowski or others have some thoughts on the above, I think that --no-cache would be fine as well, I could be overthinking things here.

That makes sense to me - thanks for thinking through this, @ellismg!
I agree with starting with provision but I do think that if we don't also enable --no-cache for up, it will be a fast followed ask.
Super, super excited for this to land! Thanks @vhvb1989 !!

closed in favor of: https://github.com/Azure/azure-dev/pull/2725