[Rancher2] Missing use of predefined node template in cluster pool settings

Request Summary:
The docs talk about creating a node template for vSphere, but when deploying a cluster for vSphere there is no option to select the predefined node template. You have to fully configure the node settings in each pool.
Details:
Create a cluster with node pools using the node template

@phillipsj, would you be able to address this?

@jtravee there are not predefined node templates in v2prov. The only correct way in RKE2 is for the node settings for each pool. I think having someone from Team 2 look over the docs would be best.

Request Summary: The docs talk about creating a node template for vSphere, but when deploying a cluster for vSphere there is no option to select the predefined node template. You have to fully configure the node settings in each pool.
Details: Create a cluster with node pools using the node template

Hi @johnwc, could you confirm that for the scenario you're describing, you are provisioning an RKE2 cluster? If so, RKE2 provisioning doesn't utilize node templates and so as you stated, there would be no way currently of refining or reusing one. This would be something we could request as a UI enhancement. Please confirm and thanks!

Yes, it is for RKE2. Prior to creating this issue, I was not aware that the node templates were only for RKE and not RKE2. I created a issue over in the dashboard repo about this as well https://github.com/rancher/dashboard/issues/6020, and apparently there is a feature request for this very thing as well https://github.com/rancher/dashboard/issues/5981.

Closing at this time as this pertains to a UI enhancement.


Add support for enabling ShareProcessNamespace

Hi, I would like to run a sidecar that can communicate with the Qdrant container on the same pod. I believe this should be a simple change, just need to allow enabling the shareProcessNamespace field on the statefulset's pod template https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#podspec-v1-core https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/
Happy to raise a PR for this issue if required

Hello,
Can you tell me more about your use case ?

Sure, essentially I want to run Qdrant in a cluster and have automated snapshots taken and uploaded to remote storage. One way I could do this would be to run a script that connects to each pod and uses kubectl cp to transfer data out but this seemed clunky. By having a sidecar run alongside the container I could containerize my snapshot script and have snapshots uploaded with labels to indicate the pod's identity

Hello,
Sure we can add your request as long as this setting is optional. Do you have time to do the PR?


[WFCORE-4359] Ensure the CLI embedded stdio and log contexts are used for CLI loggers.

WFCORE-4358
This commit just upgrades the log manager with a single commit to expose the LogContext.getLogContextSelector() which is required for the second commit.
WFCORE-4358
This commit fixes the issue where the incorrect log context could be used when creating CLI loggers and the incorrect StdioContext being used when CLI writes log messages.
Instead of just wrapping the current LogContext this wraps the CLI ThreadLocalContextSelector instead to ensure the correct contexts are used. I tested both the embed-server and embed-host-controller with the jboss-cli.sh script and the jboss-cli-client.jar. Log messages from CLI will now use the jboss-cli-logging.properties configuration (assuming that's used) and log messages from the server us the correct contexts from the server itself.
@jfdenise Could you please have a look and approve this?

Core - Full Integration Build 8395 outcome was FAILURE using a merge of 50b983f127bd008cad30fe17d33b8578521887d5
Summary: Exit code 1 (Step: Build & test full (Maven)) (new) Build time: 00:02:54

Note the ModuleInfoTestCase.testModuleInfo consistently fail when a log manager upgrade is done. It's due to the dependency not being found in the repository cache. It can be manually done or the tests can be run the next day after the cache is replicated.


Troubleshoot false negative on exec base64

Sample: libidee/0.1 (triage UI http://localhost:3000/package/pypi/libidee/0.1)

Expected to match https://github.com/DataDog/guarddog/blob/main/guarddog/analyzer/sourcecode/exec-base64.yml

Removed the large string in the beginning and kept the smaller base64 decode, and it caught the rule above.
I think this is semgrep erroring out and it might be an interesting metadata heuristic


PlotWidget: Added sigBackendChanged

Added sigBackendChanged to PlotWidget
Related to #3876
Closes #3883
Changelog:

Added sigBackendChanged to PlotWidget

I was thinking of added current, previous params to the signal.
Usually if you don't do that, the user of the API have to store the backend reference on its side. So i think it could be done without much problem.

That's a good idea i have updated the stuff.

I was thinking of added current, previous params to the signal.

If it's needed, why not.
It's not Qt-like but some other signals of PlotWidget already provides current, previous params.
But this means you'll give back a previous backend that is no longer used by a PlotWidget, not sure what it's useful for, and risky if used.

aboutToConnect/aboutToDisconnect, but i feel like it's overkill.

I agree.
sigBackendChanged can also only provide the current backend, that more Qt-like and does cause trouble with giving access to a disconnected backend.
It's fine as it for me.


looks like clear() not fires any event

When we are using custom elements and input groups like described here https://chmln.github.io/flatpickr/#strap looks like there no way to catch "clear" action.
So how it should be:

Calling onChange handler in the end of clear().
or
Making custom onClear handler.

Hello,
Firing onChange sounds good.
You can check if the dateobj is null/undefined to catch the clear action


Bump up 0.7 version

After updating for the last Gleam version (let assert mainly) it wasn't pushed to Hex, could you upgrade the version (I guess it's 0.7.0) and publish it? Thanks in advance.

Yes sorry I'll do that today

done


Don't sort ProjectChecker messages by line number

ProjectChecker messages are sorted here and because of the comparison function for messages they get sorted by line number, column and then rule id.
I don't think this makes sense specifically for rules that operate on the whole project. I would prefer the checker output didn't get sorted at all in run_project_checks() and so the order would be up to the checker. But sorting by source path first would also be an improvement.

Good point. At this point I would even consider current behaviour as a bug.


HBASE-26028 The view as json page shows exception when using TinyLfuB…

…lockCache

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  5s
Docker mode activated.


Changed supported versions

Your current package.xml only supports Woltlab Suite 5.4 and higher. I changed the Readme.

Just how I forgot that. Thanks


You'll need to create the conda environment with the python arg.

You'll need to create the conda environment with the python arg.
See here https://code.visualstudio.com/docs/python/environments#_conda-environments
Originally posted by @DonJayamanne in https://github.com/Microsoft/vscode-python/issues/3732#issuecomment-447985108

I believe
conda create -n myenv
conda activate myenv
conda install python=x.x.x
is an exceptable way to create a conda environment.  Could the plugin survey the CONDAROOT/envs directory?

Restarted the app and it now picks up my new environment.


How to set local storage key-value pairs before chromedp.Navigate(url)

What versions are you running?

$ go list -m github.com/chromedp/chromedp
latest git version
$ chromium-browser --version
Chromium 73.0.3683.86 Fedora Project
$ go version
go version go1.12.5 linux/amd64

thanks

Please follow the full issue template.
Also, provide links to what you mean by local storage key-value pairs. For example, does Puppeteer support this? If so, how?

You would do this with runtime.Evaluate() call:
package main

import (
	"context"
	"log"

	"github.com/chromedp/cdproto/runtime"
	"github.com/chromedp/chromedp"
)

func main() {
	ctx, cancel := chromedp.NewContext(context.Background(), chromedp.WithDebugf(log.Printf))
	defer cancel()

	if err := chromedp.Run(ctx,
		chromedp.Navigate("https://www.google.com/"),
		chromedp.ActionFunc(func(ctx context.Context) error {
			_, exp, err := runtime.Evaluate(`window.localStorage.setItem('foo', 'bar')`).Do(ctx)
			if err != nil {
				return err
			}
			if exp != nil {
				return exp
			}
			return nil
		})); err != nil {
		log.Fatal(err)
	}
}

See: https://stackoverflow.com/questions/51789038/set-localstorage-items-before-page-loads-in-puppeteer

The question was on how to set local storage BEFORE Navigate.
Example shows usage AFTER Navigate
But if you try to set storage values before, you'll get
DOMException: Failed to read the 'localStorage' property from 'Window': Access is denied for this document
Would there be any resolution to this issue?

The question was on how to set local storage BEFORE Navigate.
Example shows usage AFTER Navigate
But if you try to set storage values before, you'll get
DOMException: Failed to read the 'localStorage' property from 'Window': Access is denied for this document
Would there be any resolution to this issue?

The question was on how to set local storage BEFORE Navigate. Example shows usage AFTER Navigate But if you try to set storage values before, you'll get DOMException: Failed to read the 'localStorage' property from 'Window': Access is denied for this document Would there be any resolution to this issue?
hi,any resolution? playwright has

storage = await context.storage_state(path="state.json")
# Create a new context with the saved storage state.
context = await browser.new_context(storage_state="state.json")


Correspondence due to change of serializable interface of PHP8.1

ref: https://www.php.net/manual/class.serializable.php

@shunji-onodera would you please follow up on the CLA check? It seems to be a pre-requisite for reviews 😄

@google-cla I signed it!

@lcobucci
I registered with CLA and tried to rescan but got a 400 error. 🤔

@lcobucci
I registered with CLA and tried to rescan but got a 400 error. 🤔

Maybe the link expired?

I think the return type declarations won't work for PHP 5.x, but I don't know of the top of my head if omitting them works for PHP >= 7.4 😕

@lcobucci
I still get a 400 error on rescan and can't seem to do anything about it. I'll try to close the PR once and submit it again.

@lcobucci @jeromegamez
I re-did it (and got rid of the type declaration of the return value). https://github.com/GoogleCloudPlatform/grpc-gcp-php/pull/45


bump: k8s to 1.23

In preparation for the 1.23 release, bumping to the 1.23 release candidate for soak time
ref https://github.com/kubernetes-sigs/descheduler/issues/641

/retest

@damemi haven't PSPs been removed in K8s v1.23?

@damemi haven't PSPs been removed in K8s v1.23?

If I recall correctly they are still deprecated. They will be removed in v1.25.

@damemi haven't PSPs been removed in K8s v1.23?

If I recall correctly they are still deprecated. They will be removed in v1.25.

https://kubernetes.io/blog/2021/04/06/podsecuritypolicy-deprecation-past-present-and-future/

Thanks @seanmalloy, that would have been too easy.
@damemi are there any API version overrides in the values being used? Maybe for the cronjob? I'm not in front of my computer, so just guessing but might be able to take a proper look tomorrow.

@stevehipwell oh yeah! probably https://github.com/kubernetes-sigs/descheduler/pull/577

Hm, actually looks like we should still be good with v1beta1 until 1.25 https://kubernetes.io/docs/reference/using-api/deprecation-guide/#cronjob-v125
/retest
maybe it's just a flake?

Now that 1.23 has released, I'm just updating this to use the GA tag. Still need to sort out why Helm test is failing, we have some ideas above.
In the meantime, we also need to make the regular updates to test-infra to run against k8s 1.23 and add a test for the release-1.23 branch. If there are any volunteers to make that change please feel free!

Ran this locally and saw this error in the pod logs:
$ kubectl logs pod/descheduler-ci-27319252-5lpdg -n kube-system
Error: unknown flag: --v

which looks like we need the change to initialize klog, similar to this. I'll add that and report back

Green now, so this should be ready to merge

Running locally with -v=4 I don't see the descheduler logs

Running locally with -v=4 I don't see the descheduler logs

well that's not good...
/hold

Klog seems to work, it's just the --v option that's not properly wired to it probably

Because https://github.com/kubernetes/kubernetes/pull/106090

/lgtm
/hold cancel

Thanks again @ingvagabund for solving that problem!


Simplify and improve battery state calculations

I've come across a few inconsistencies in the battery state calculations so I had a go at the code to try and make it simpler and fix some of the issues. This PR includes:

Calculating the battery state from just the energy values. Using other values for the total capacity was resulting in broken results in other cases. Since the energy information is already enough and was already present this simplifies the code and avoids the inconsistency.
Clamp battery states above 100%. This can happen when the battery recalibrates and charges more than the capacity it thinks it has. Just show 100% in those cases.
Round the battery state so that 99.9% shows as 100%. This avoids some cases where the last bit of battery doesn't charge but the battery is effectively full already.
Whenever the capacity has been calculated as 100% show the state as full, so that the formatting rules are applied accordingly

I don't have a way to check as I don't have a removable second battery but this may help with #490. To fully fix that it's probably best to enumerate all the batteries on update instead of generating the list of batteries on startup.

LGTM, thanks!
Can you add your idea about enumerate all the batteries on update?

I've now also added making full-at show the battery at 100% when the state is at full-at. Before it was capping at the full-at value which doesn't really make sense. This way the range is back to 0-100% with full-at being the new 100%.

Enumerating batteries on update doesn't sound too hard but it will do two things that may not be wanted:

If the config has a specific battery and that has disappeared it will throw an error. That can be worked around to just show that battery as unknown but I don't have a way to test this.
There will be a lot of inotify_add_watch and inotify_rm_watch calls on every update. No idea what that does for performance.

I've implemented the hotplug stuff without doing any storm of inotify_watch calls. The only thing I'm missing is a way to have refreshBatteries() be called only when the CREATE or DELETE inotify event happened instead of every time. That would make the performance better. But maybe this is enough.
Since my laptop doesn't have a removable battery I have no way to test if this has solved the hotplug stuff though.

Could you add a TODO about calling refreshBatteries() only on CREATE and DELETE event?

The TODO is already there.
By the way that reminds me that this and other modules should have a refresh every time the clock advances quickly or similar. When returning from suspend the battery updates very slowly.

@pedrocr We should create a separate issue for that.
I'll merge this PR, thanks!


Hide smart update icon when disabled

It is only hidden when smart update is disabled AND there is no predicted release date.
When smart update is disabled that icon doesn't have much purpose other than maybe checking the prediction, but when there is no prediction it should be hidden.

Before
After

Only hide when disabled

Only hide when disabled

What do you mean? Hide if smart update is disabled regardless of if there's a predicted release date?

Only hide when disabled

What do you mean? Hide if smart update is disabled regardless of if there's a predicted release date?

Yes. Otherwise people might be confused why it isn't present for a handful of entries.

Actually I misunderstood the purpose of the PR. The PR is fine as-id but I want some more opinion on this change.

Okay, so what you want to do is have the hourglass icon disappear only when there’s no available prediction, right? (Assuming that the 4th smart update parameter is not checked)
Otherwise, even with the 4th parameter unchecked, the hourglass icon and predicted time window will still appear like normal.
Asking ’cause your wording has me a little confused.

That's currently how the PR is.
I was thinking that the prediction isn't even that reliable so maybe hide it altogether if the 4th parameter is unchecked would be a better idea.
But that's up to the mihon people to decide

I was thinking that the prediction isn't even that reliable so maybe hide it altogether if the 4th parameter is unchecked would be a better idea.

Yes, I was thinking about this as well. It would also help users with configuring smart update, as the 4th parameter gives close to no feedback as to what it does.
“Predict next release time? Don’t I already have a time window prediction even with it off?”

Any updates on this?


[DO NOT MERGE - testing GHA] test(push-test): Update push-test.yml

#TICKET_NUMBER

Restore E2E tests to hit local containers again instead of dev BE. But building containers is so slow though. Not sure if we should do this along with better Docker layer caching?
context: https://github.com/chanzuckerberg/single-cell-data-portal/pull/2853#pullrequestreview-1039667667
Reviewers
Functional:
Readability:

Changes

add
remove
modify

QA steps (optional)
Notes for Reviewer

closing this for now, since we don't have plan to switch back yet


Video preview only plays first take

When a take has not been selected yet, the video preview only plays the first take despite all takes appearing on the UI. It should play through all takes in order.

@emmapainter  review priority label here and edit as you feel is needed depending on your desire for take detection


workflow maintenance

What this PR does / why we need it:
This PR includes some necessary maintenance for the Github workflows.

updated dependencies to latest versions
replaced hard coded repository names
upgraded deprecated set-output commands to using Environment Files

Which issue(s) this PR fixes:
Fixes #215
Special notes for your reviewer:
Release note:

/cla


Implement Breadcrumb navigation

This feature is missing from current version.
It was requested in current mockups:
https://www.figma.com/proto/zmTCRqUbcH4FHMdKbh2lnu/Clinical-Site-SSApp?node-id=1375%3A741&scaling=min-zoom&page-id=0%3A1&starting-point-node-id=1%3A50&show-proto-sidebar=1

component is implemented https://github.com/PharmaLedger-IMI/iot-pmed-workspace/commit/1bc2763b9d232a61d9eff89746a1c61fa25931ed

@cosmintuca will further use it on all pages


[Bug] Possible memory leak with --is-miner option (?)

🐛 Bug Report
Probably memory leak.
I just run miner and it consume whole RAM and swap.
 I tried to restrict threads count via taskset --cpu-list 1,3,5,7,9,11,13,15 snarkos ..., but it just took a bit more time to consume all memory.
Expected Behavior
SnarkOS mines blocks and consume limited amount of memory.
Your Environment

SnarkOS 1.3.17 (installed via cargo)
Ubuntu 18.04 with core 5.11.16
Ryzen 5950X, 64G RAM

I use memory limits in systemd and it kills and start miner every 30 minutes
[Unit]
Description=Aleo Miner
After=network-online.target

[Service]
User=aleo
ExecStart=/home/aleo/run-miner.sh
Restart=always
RestartSec=10
LimitNOFILE=10000
MemoryAccounting=true
MemoryHigh=24G
MemoryMax=32G

[Install]
WantedBy=multi-user.target

Thanks for the report, @yatsvic! I'm going to try to reproduce this.

There's definitely a leak related to mining alright; I'm able to reproduce it reliably, going to try to fix it :factory_worker:.

@ljedrz I am not experienced in Rust, so I can suggest only to test fix when it is ready.

After having memory-profiled a miner node using different tools, I actually don't think there is a leak, but rather an issue with the allocator, where the node doesn't release memory "proactively" enough.
@yatsvic while I'm still working on a general solution, could you try out my temporary branch, which uses the jemalloc allocator, and run it with JEMALLOC_SYS_WITH_MALLOC_CONF="background_thread:true,narenas:1,tcache:false,dirty_decay_ms:0,muzzy_decay_ms:0,abort_conf:true" <snarkos binary and its arguments>? With this aggressive allocator setup I was able to mine over 100 blocks without running out of memory.

I have further confirmed that this is caused by the system allocator by using gdb and calling malloc_trim :heavy_check_mark:.

@ljedrz thanks! I am trying your branch with JEMALLOC_SYS_WITH_MALLOC_CONF.
It mined 27 blocks in 24 minutes and it is in 4 - 12 GB RAM, more time is about 5GB.
Looks like it is not leaking!
I will report long run results in 8-9 hours (my morning, it is night at my location).

@ljedrz it is definitely running fine!
I started it 9.5 hours ago, it works without crashes and restarts. And currently it consumes 10.5Gb RAM.

It has been running for two days without restarts!

@ljedrz did you have a chance to fix it? Thanks

@yatsvic since the beginning of testnet2, the node has undergone a full rewrite, so this issue is unlikely to be applicable anymore; however, until it is certain that the new implementation is staying for good, the issues applicable to testnet1 remain open.


How can we update a scheduleMessage in boltJs

I have an application that uses both postMessage and scheduleMessage. I have noticed that the post message can be updated as it has ts attached to it that we can pass to the client.chat.update
However in case of scheduleMessage, we do not have the ts available, however we have the post_at
Now if I want to update the scheduleMessage, what would be the ideal solution to it.
scheduleMessage
const message = await client.chat.scheduleMessage({
        channel: channelId,
        post_at: scheduleTime.valueOf() / 1000,
        icon_url: userInfo?.image_192,
        username,
        blocks: [
          {
            type: "section",
            text: {
              type: "mrkdwn",
              text: "*Hello*",
            },
          },
        ],
        text: "Hello",
        //@ts-ignore
        attachments: responseMarkdown,
      });
    }

update message
await client.chat.update({
      channel: channelId,
      ts,
      icon_url: userInfo?.image_192,
      username,
      blocks: [
        {
          type: "section",

          text: {
            type: "mrkdwn",
            text: "*Hello",
          },
        },
      ],
      text: "Hello",
      // @ts-ignore
      attachments: responseMarkdown,

The schedule message is working as expected, however when I try to update it, it throws an error message_not_found and I guess it could be due to the fact thta ts is not available.
Also could it be because of the format of the ts(1405894322.002768) and post_at(1685084154595)
Reproducible in:
The Slack SDK version
(Paste the output of
npm ls | grep -o "\S\+@\S\+$" | tr @ ' ' | awk -v q='"' '{print q$1q": "q"^"$2q","}' | grep slack

or refer to your package.json)
Node.js runtime version
v 18.16.0
OS info
MacOS Venture (chip m2)
Steps to reproduce:
(Share the commands to run, source code, and project settings)

Expected result:
I want to update the scheduleMessage
Actual result:
It throws the error, message_not_found
Requirements
For general questions/issues about Slack API platform or its server-side, could you submit questions at https://my.slack.com/help/requests/new instead. :bow:
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

Hi @SyedSibtainRazvi , there is no way to edit scheduled messages via public APIs.
Instead, you can delete it and create a new one. chat.scheduleMessage API method returns "scheduled_message_id" in its repsonse. You can call chat.deleteScheduledMessage API to delete the existing scheduled message with the ID first, and then create a new one with updated message content.
I hope this helps.

Hi @seratch , thank you for your quick response, I really appreciate it. I have a follow-up question.
We should be easily able to delete the old scheduled message and schedule a new one. And till it is not posted in the channel, everything is good.
However when we delete the message that has been posted already, then that message will be removed from chat history and when we send a new message that will appear as a normal new message to someone who does not know that this message was sent to update something, how will. another user who by looking at this new message can understand that it was meant to update an old message and is not a new message.
It would have been really simple if scheduled message api had a ts attached to it.

@SyedSibtainRazvi When a message is already posted, calling chat.deleteScheduledMessage no longer works. In this case, all your app can do is to tell an end-user that the scheduled message is already posted. Identifying the ts of the posted message in the scenario is not so easy, so I can share the feedback internally. However,

It would have been really simple if scheduled message api had a ts attached to it.

This won't be implemented even in the long run because scheduled messages are not yet posted.
I hope my answer here clarifies. If you don't have any other questions on this, would you mind closing this issue now?

Thank you @seratch, you have been indeed very kind and helpful.


Disable rolling if cannot claim?

is there any way to not roll if your account is on claiming cooldown?

Closing as rolling even without claim still has benefits of getting keys or potential kakera loots


[Bug]: Yubikey Webauthn 2FA fails to authenticate.

Preflight Checklist

[X] I could not find a solution in the documentation, the existing issues or discussions
[ ] I have joined the ZITADEL chat

Environment
Self-hosted
Version
2.28.0
Describe the problem caused by this bug
I had my Yubikey set up as a second factor for quite a while and never had any issues until now.
When attempting to authenticate as of late, touching my Yubikey produces the following error:

I have confirmed that the Yubikey is working correctly by authenticating on another site.
I am also definitely not using the wrong key because I used the workaround below and then added the key once again which made no difference.
To reproduce
I'm not entirely sure what may have caused this or how it can be reproduced. I am using the current latest version of Zitadel in Docker (ghcr.io/zitadel/zitadel:latest) with postgres 14 (I realise pg is experimental, but I highly doubt the issue is related).
The logs do not appear interesting but I attach them below anyway.
Screenshots
No response
Expected behavior
No response
Operating System
OS: openSUSE Tumbleweed Linux (latest snapshot)
Browser: Brave 1.52.117 (Chromium 114.0.5735.90)
Relevant Configuration
No response
Additional Context

Logs
time="2023-06-03T22:33:56Z" level=info msg="setup started" caller="/home/runner/work/zitadel/zitadel/cmd/setup/setup.go:63"
time="2023-06-03T22:33:56Z" level=warning msg="postgres is currently in beta" caller="/home/runner/work/zitadel/zitadel/internal/database/postgres/config.go:62"
time="2023-06-03T22:33:56Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39" name=01_tables
time="2023-06-03T22:33:56Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39" name=02_assets
time="2023-06-03T22:33:56Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39" name=03_default_instance
time="2023-06-03T22:33:56Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39" name=04_eventstore_indexes
time="2023-06-03T22:33:56Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39" name=05_last_failed
time="2023-06-03T22:33:56Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39" name=06_resource_owner_columns
time="2023-06-03T22:33:56Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39" name=07_logstore
time="2023-06-03T22:33:56Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39" name=08_auth_token_indexes
time="2023-06-03T22:33:56Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39" name=09_optimise_indexes
time="2023-06-03T22:33:56Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39" name=10_correct_creation_date
time="2023-06-03T22:33:56Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39" name=11_event_created_at
time="2023-06-03T22:33:56Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39" name=config_change
time="2023-06-03T22:33:56Z" level=info msg="verify migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:39" name=projection_tables
time="2023-06-03T22:33:56Z" level=warning msg="postgres is currently in beta" caller="/home/runner/work/zitadel/zitadel/internal/database/postgres/config.go:62"
time="2023-06-03T22:33:57Z" level=warning msg="execution logs are currently in beta" caller="/home/runner/work/zitadel/zitadel/cmd/start/start.go:207"
time="2023-06-03T22:33:57Z" level=info msg="spooler started" caller="/home/runner/work/zitadel/zitadel/internal/eventstore/v1/spooler/spooler.go:73" lockerID=216989193186844994 workers=1
time="2023-06-03T22:33:57Z" level=info msg="spooler started" caller="/home/runner/work/zitadel/zitadel/internal/eventstore/v1/spooler/spooler.go:73" lockerID=216989193186910530 workers=1
time="2023-06-03T22:33:58Z" level=info msg="server is listening on [::]:8080" caller="/home/runner/work/zitadel/zitadel/cmd/start/start.go:412"

Workaround
The 2FA can temporarily be disabled by manually editing the database. This can be dangerous, but seems to have worked fine for me:
UPDATE auth.users2 SET u2f_tokens=null WHERE<EMAIL_ADDRESS>UPDATE auth.users SET u2f_tokens=null WHERE<EMAIL_ADDRESS>

Hei @0x1a8510f2
Thanks for reporting.
We will have a look at it.

@peintnermax @muhlemmer Can you link the pr that fixed that issue and close it if it is already done?

#5983 fixes the decoding of the credential id

Workaround fix (revert) was already part of the 2.28.1 image. The final fix from Max will be part of version 2.29.
Closing as completed.

Can confirm, the latest docker image appears to work as expected. Thanks for the fix!


grunt build can't find setImmediate polyfill

With latest code, running grunt build reports the following:
{ name: 'Missing polyfill source file',
  message: 'Path ..../polyfill-service/polyfills/__versions/v1.0.2/setImmediate/polyfill-onreadystatechange.js not found' }

I looked and I found it under with a . instead of a - naming convention.
Like so: ..../polyfill-service/polyfills/__versions/v1.0.2/setImmediate/polyfill.onreadystatechange.js

Sorry, that output could be clearer - it's an error in an earlier version of the library, which we can't fix because it's a locked version (it was, in fact, fixed in the next version of the library).  It doesn't cause a build failure, but I could and probably should suppress the error entirely.

Ahh, okay. Totally up to you then. Probalby would be a good idea as it'll likely just come up again by someone else if they try and build their own.


feat(ngAria[ngClick]): preventDefault on pressing Space so the page doesn't scroll

This is a bug fix for the ngAria ngClick directive.
When a user presses space on a "normal" button, the page should not scroll. However, with a "fake", [role="button"], pressing space doesn't preventDefault(), so it scrolls the page.
You can see the bad behavior here: https://plnkr.co/edit/SPxQ0X2RQvvfvAmDVTNA?p=preview
This PR adds event.preventDefault(); so that pressing Space doesn't activate the native browser function.

Seems straight forward enough for me. I verified it still works when the div has an interactive child element: https://plnkr.co/edit/SPxQ0X2RQvvfvAmDVTNA?p=preview
But it highlights another problem, which I will file as an issue: ngAria needs to check for at least one interactive child element before binding role="button" and tabindex="0" because otherwise you get interactive elements wrapped around other interactive elements. This is a problem for screen reader users, and why a <button> element wrapping other <button> elements is invalid HTML.

I've somehow missed that :smiley: LGTM, except for the lack of tests.
@stowball, would you be interested in adding some?

Leave a commement

I'm new to testing. How would we go about testing the whether the window scroll position changed?

It would be a little involved, because you would have to make sure there is room to scroll and then check the windows scrollTop probably. But I don't think you have to. You can just check that preventDefault() is called on the dispatched event (for ENTER, SPACEBAR only).


Updates devcenter config usage

Resolves #3826
Devcenter configuration can exist at multiple levels for azd

Environment variables
Global azd configuration
Project configuration in azure.yaml
azd envrionment configuration within .azure/<env-name>/config.json

Since the config object was being injected as a transient component changes to the config where not getting picked up when changes where made based on user prompts.
This PR removes the config from an injected param of a couple components and into a function param for consumed components.  This allows the correct config to flow through to the required functions.
In addition to this this enables us to now only save updates to the config based on what has changed from the originally loaded value as part of the azd environment configuration.

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

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

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

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

MacOS -

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

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

MSI

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

Documentation

learn.microsoft.com documentation

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

See also

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

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

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

See also

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

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

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

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

See also

azd auth: Authenticate with Azure.
Back to top

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

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

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

See also

azd auth: Authenticate with Azure.
Back to top

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

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

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

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

See also

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

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

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

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

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

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

See also

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

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

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

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

See also

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

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

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

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

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

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

See also

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

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

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

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

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

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

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

See also

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

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

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

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

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

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

See also

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

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

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

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

Examples
azd config unset defaults.location

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

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

See also

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

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

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

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

See also

Back to top

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

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

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

See also

Back to top

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

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

See also

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

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

See also

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

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

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

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

See also

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

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

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

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

See also

Back to top

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

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

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

See also

Back to top

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

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

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

See also

Back to top

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

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

See also

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

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

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

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

See also

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

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

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

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

See also

Back to top

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

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

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

See also

Back to top

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

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

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

See also

Back to top

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

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

See also

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

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

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

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

See also

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

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

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

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

See also

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

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

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

See also

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

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

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

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

See also

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

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

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

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

See also

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

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

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

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

See also

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

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

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

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

See also

Back to top

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

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

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

See also

Back to top

Nice improvement!
I'm still a little confused on the whole cachedConfig vs config thing. I ended up checking out this PR and spending some time in VS Code trying to better understand when it gets set to try to puzzle out what the invariants are, but I didn't feel super confident I understood what's going on.
I think the goal here is that we track this so that if PromptForConfig added stuff to it, we could write that stuff into the env.Config bag when Reload was called later. I wonder if it would be possible to say that a responsibility of PromptForConfig is to also write an state that needs to become durrable into the env.Config at that point, instead of waiting for Reload to be called. If we did that, I wonder if we'd need to track cachedConfig as member level state at all.
If it does need to stick around, I think it might be helpful to have a little comment about what's going on and how we use it - the cached prefix here was a little confusing to me and it wasn't clear at first how it related to config.
But either way, this makes the system a lot easier to reason about - thanks for this!

Thanks for the feedback Matt.  You are right, except in some cases we don't yet have an environment to write to after we prompt for configuration.
Use case:
Some list of environments exist, but you don't have any locally.  Some devcenter configuration may be set globally or as part of the project config.

User calls azd env select <env-name> which exists on the remote.
Azd prompts for more info if needed (Which Project??)
Azd now has enough info to find the environment and it get created locally and hydrated from the remote.
Azd now needs to save that project selection back into the new env config so we don't need to prompt the user for it again.


[CompactIndexClient] Synchronize access to the list of fetched endpoints

Should fix #5142.

@indirect r?

both a mutex and 1 worker? shouldn't either one or the other make it work?

It needs to be mutexed for all rubies

@bundlerbot r+


docs/Homebrew-on-Linux: Centre the logo

Maybe we can fix the sponsor badges as well? It might be worthwhile to add some or an _include to https://github.com/Homebrew/brew.sh for prettier images.

Maybe we can fix the sponsor badges as well?

Done.

Closing in favour of
https://github.com/Homebrew/brew.sh/pull/342

The sizes of the images should be fixed by PR https://github.com/Homebrew/brew.sh/pull/342, but it doesn't centre the images, which was the original purpose of this PR.

For some unknown reason I can't reopen this PR, so I've opened PR https://github.com/Homebrew/brew/pull/5886


fix(dev): keep dev server running when build fails

Closes #5631
Closes #5711

Closes: #

[ ] Docs
[ ] Tests

Testing Strategy:

@MichaelDeBoey did you verify that these changes fix #5711 . I think that issue is related, but not necessarily fixed by this change. The goal of this PR is to fix regressions especially for the old, stable dev server. #5711 doesn't seem to be a regression and is only affecting unstable_dev


refactor [circleci] integration

refs #1358

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @chris48s!

:book:

Thanks for contributing to our documentation. We :heart: our documentarians!

  Generated by :no_entry_sign: dangerJS

Hey @chris48s this needs some conflict resolution. Since the changes here to server.js are simple, it should be easiest to grab the version from master, and then delete the circle implementation (and remove unused helper functions). I'm planning to validate the master branch and deploy tonight (UTC-7). It would be great to include this one, too!

It would be great to include this one, too!

There are 2 bits of work going on in this PR:

Refactoring the existing code (which has a bug)
Fixing a bug

Do you mean you want to get the refactored (but still buggy) code into a state where you can merge it and then treat the bugfix as a different job?
If you want to just get all the service code out of server.js another option is to convert this into a LegacyService and I'll just rebase and deal with it.. I don't think it makes much difference.

Ah, no, sorry, I forgot about the issue with multiple builds. I’m flexible. We can do this in whatever order makes the most sense to you.

Right, I've sorted out the merge conflicts and pushed that. What's here now is refactored into the new structure maintaining the existing functionality (only looking at the most recent one build).
I've had a look at some examples and I think using workflows.workflow_id to group related builds is the right thing to do so I'm going to look at that next.
If you want to merge this in the meantime, I can submit that as a new PR. If not, I'll append it to this one.

I spotted another issue with the way I've done the static examples, so this now needs another review.
I'm now quite close to being able to submit a fix for #1792 but this has spiralled into quite a complex job as I've found more and more edge cases. The fix will require adding a lot of additional code and tests. As such, I think once I've got another :+1: on this I'll merge this as it stands and we will deal with that as another PR to make the review easier to deal with because we won't be trying to deal with that and the refactoring all at once.


Protobuf support in TF Java

Right now, the TensorFlow Java client from the repository does not expose directly protobufs that are part of the contract of the C API (Though in this thread, it was mentioned that protobufs would be eventually removed from the API but I have a feeling this won't happen anytime soon).
Instead, it compiles and distribute the protobufs Java bindings as a separate artifact and the client itself remains agnostic of the content of the messages and simply expose unmapped byte arrays, like here.
We need to decide how we want to handle those protobufs in the new distribution. Possible choices are:

We keep distributing the compiled protobufs as an external artifact like now from the core repository build
We keep distributing the compiled protobufs as an external artifact but from our new repository build
We compile and distribute the Java protobuf bindings within the new TF Java client artifact so they get exposed directly by our API
We compile the Java protobuf bindings with the new TF Java client but wrap them so they are not exposed directly by our API (in case they are removed in TF core, see previous thread link)
Any other idea?

Note that if we decide to compile the protobufs from the new TF Java client, it will brings its load of additional dependencies, such as grpc.
CC: @sjamesr

Interesting archeological discovery related to this issue, according to this unit test, protobuf Java bindings were meant to be distributed with the Java client but couldn't due to some complications with Bazel, hence the reason they were distributed separately.

Resolved by #38


Use of throw in all-packages.nix breaks nix-build with almost no information given

In commit 25a3563102e2beeae64257671581c93a2ef6e4b0, the activator attribute was changed to:
  activator = throw ''
    Typesafe Activator was removed in 2017-05-08 as the actual package reaches end of life.

    See https://github.com/NixOS/nixpkgs/pull/25616
    and http://www.lightbend.com/community/core-tools/activator-and-sbt
    for more information.
  '';

This appears to completely break nix-build, as I get this exception no matter what I try to build, even though I'm not using the activator attribute anywhere. Further, when throw aborts nix-build, adding --show-trace gives no additional information about why I'm getting this error.
If I delete the activator attribute entirely, it fixes the problem, proving that I wasn't doing anything that actually needed the attribute value.  So, it seems that when nix-build goes to evaluate all-packages.nix, it encounters this throw and executes it, even though it's not a path that needs to be taken.
I see two aspects to this issue:

Using throw should not break nix-build on expressions that shouldn't be evaluating the throw.

If throw does occur, --show-trace should work, in order to find out why the throw is happening.

The only case in which I could see this happening is if your nix-build invocation is trying to build an attrset that includes all of our packages. Are you not passing -A into it, or is an attrset somehow sneaking into the thing it sees? If nix-build encounters an attrset it'll try to build derivations as keys, so if you're re-exporting nixpkgs somehow, you'll see the behavior.
As an example, I've been using nix-build -A foo against nixpkgs (it's my primary way of testing things I contribute) for ages since that throw appeared and it's never caused me issues.

I was using nix-build "<nixpkgs>" gnustep-make rather than nix-build "<nixpkgs>" -A pkgs.gnustep-make.  The latter works, the former gives that strange error.  Is the -A flag required for nix-build to work?

Before the throw change, it appears I would get:
error: assertion failed at /Users/johnw/.nix-defexpr/nixpkgs-next/pkgs/games/adom/default.nix:4:1

So I guess nix-build never worked without -A.


Add max-lines rule?

http://eslint.org/docs/rules/max-lines
I'm thinking adding it as a warning.
What would be a good max? The default is 300 (excluding comments and empty lines). I think that's a good default.

// @jamestalmage @SamVerschueren @kevva

I think 300 is good. That's already really long


feat: new functional dependencies pipeline RequireMarginal

This PR adds RequireMarginalFunctionalDependencies, which specifies that in order to compute a message on some edge rule requires marginal on the same edge. The interface is pretty much the same as for RequireInboundFunctionalDependencies.
Do not merge, tests are not implemented (yet).

Codecov Report

Merging #160 (0576ca3) into master (4f85423) will decrease coverage by 0.77%.
The diff coverage is 44.00%.

:exclamation: Current head 0576ca3 differs from pull request most recent head 75d79f8. Consider uploading reports for the commit 75d79f8 to get more accurate results

@@            Coverage Diff             @@
##           master     #160      +/-   ##
==========================================
- Coverage   76.02%   75.25%   -0.78%
==========================================
  Files         179      179
  Lines        6445     6126     -319
==========================================
- Hits         4900     4610     -290
+ Misses       1545     1516      -29

Impacted Files
Coverage Δ

src/node.jl
82.08% <44.00%> (-3.63%)
:arrow_down:

src/approximations/gausshermite.jl
37.50% <0.00%> (-6.95%)
:arrow_down:

src/algebra/companion_matrix.jl
41.02% <0.00%> (-5.57%)
:arrow_down:

src/nodes/bifm.jl
72.72% <0.00%> (-5.33%)
:arrow_down:

src/math.jl
76.00% <0.00%> (-4.77%)
:arrow_down:

src/nodes/gamma_mixture.jl
0.00% <0.00%> (-4.45%)
:arrow_down:

src/constraints/form/form_sample_list.jl
30.00% <0.00%> (-3.34%)
:arrow_down:

src/constraints/spec/form_spec.jl
58.33% <0.00%> (-3.21%)
:arrow_down:

src/constraints/prod/prod_generic.jl
32.91% <0.00%> (-2.46%)
:arrow_down:

src/macrohelpers.jl
59.57% <0.00%> (-2.13%)
:arrow_down:

... and 56 more

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 4f85423...75d79f8. Read the comment docs.


You can uppercut and slam a fortified orisa

Created by: BringBackDoom
When you slam the orisa they will get pushed toward you and when you uppercut them they will still get shot into the air during fortify

moved from ow1_emulator_backup#551


[DOCS-441] Asset tags

Changelog
Updated

Page
Deploy Preview
Comment

Define Your Assets > Asset Details
Link

Glossary > Asset Tag
Link

Preview This Change
To see how this change looks in production, scroll down to Deploy Preview. Select the link that looks like https://deploy-preview-<num>--cobalt-docs.netlify.app/
Variables
Help us support a “Write once, publish everywhere” single source of truth. If you see a line that looks like:
{{% asset-categories %}}
You’ve found a shortcode that we include in multiple documents.
You’ll find the content of the shortcode in the following directory:
https://github.com/cobalthq/cobalt-product-public-docs/tree/main/layouts/shortcodes
That shortcode has the same base name as what you see in the PR, such as asset-categories.html.
Checklist for PR Author
[ ] Did you check for broken links and alt text?
Be sure to check for broken links and Alt Text issues. We have a partially automated process,
as described in this section of our repository README:
Test Links and Alt Attributes.

@eugenerevzin Thank you for bringing other use cases to my attention!
I have updated the definition and added these use cases.


Outdated information regarding Workday Connector "Test Connection"

The information regarding "Test Connection" for Workday Connector ( under "Configure a Global Element" #5) is outdated and only applies to version 11 or less.  It doesn't work for version 11 and above
https://docs.mulesoft.com/workday-connector/15.0/workday-connector-studio
https://github.com/mulesoft/docs-connectors/blob/latest/workday/15.0/modules/ROOT/pages/workday-connector-studio.adoc
The correct information is:

Grant the user account access to Performance_Management service and Get_Degrees operation.( Connector version 11.0 and later )
For earlier versions, grant the Identity_Management and Get_Workday_Account_Signons ( Older Connector versions  )

Source:  https://help.mulesoft.com/s/article/Workday-Connector-Test-Connectivity-Error-It-Was-Impossible-to-Connect-to-the-Workday-Instance

Hey @eugef66 -- thanks for reporting this. We've updated this information in this PR. https://github.com/mulesoft/docs-connectors/pull/1936


changed totalSegs in buildCircle; minor cleanup in GraphicsRender

See issue #1928 - used the value from @aeauseth's comment for totalSegs.

I made 2 fiddles to compare the results:
before:
http://jsfiddle.net/n4w4w7yj/
now:
http://jsfiddle.net/7aLhx5r9/

I will split this into multiple PR's. Diff is a bit messy...


Support authentication for plugin repositories

In https://github.com/gradle/gradle-build-action/issues/933 the gradle configurations were enhanced to support a custom plugin repository provided by the user.  These plugin repositories can require authentication but there is currently no mechanism to also provide a credentials block to this configuration.
It would be helpful if we could also provide a username and password to the custom plugin repository e.g.
  repositories {
    maven {
      url "<private gradle plugin repository>
      credentials {
        username = System.getenv("USERNAME")
        password = System.getenv("PASSWORD")
      }
    }
  }

Yep, this makes sense. Would you be willing to develop, test and submit a fix?
The implementation should be a pretty simple change to this file, but I don't have an environment to easily test this functionality.

@bigdaz I did attempt this a while back and I couldn't seem to use the the project credentials:  e.g.
    val user: String by project
    val password: String by project

I think I'm misunderstanding the startup behavior of gradle and these 'init' scripts, the behavior is different than our typical method of gradle configuration.  The only work around I found was to reference environment variables directly.

You won't be able to access the project instance from within the init-script. The script is loaded very early well before any project is loaded.
Just a thought: before trying to modify the init-script to load 2 new environment variables, can you try using a repository URL like:
<EMAIL_ADDRESS>This is a valid URL format, but I'm not certain if Gradle will translate it to the correct AUTH headers.


[version_0.5]Parking and coffee poi icon not central display

step:
1.Enter coffee poi detail page and check the poi icon in map
2.Enter parking poi detail page and check the poi icon in map
expect:
Parking and coffee poi icon central display
actual:
Parking and coffee poi icon not central display

Fixed.


[FEAT]: Implement Multi-Language Support for the NexMeet Event Platform

Description:
To enhance user experience and accessibility, we propose adding multi-language support to the NexMeet Event Platform. This feature will allow users to view the platform in their preferred language, making it more inclusive for a global audience.
How to Implement:
Language Selection: Create a dropdown menu for users to select their preferred language.
Translation Files: Set up JSON files for each language containing key-value pairs for text elements used in the application.
Dynamic Content Loading: Use JavaScript to load the appropriate translation file based on the user's selection and dynamically update the content on the page without requiring a full reload.
Why:
Implementing multi-language support will make the NexMeet platform more accessible to users from various linguistic backgrounds, potentially increasing user engagement and satisfaction. It aligns with our goal of creating an inclusive community around events.

Hey, I won't be able to complete this assigned tasks due to reasons, so this issue is open for anyone to take over.

okay

Assign this to me

sir make update

sir make update

okay, wokring

sir je jaldi karoo

sir je jaldi karoo

Aaaj mil jayegi, PR


AL0601: Table 'Product Group' is removed. Reason: Product Groups became first level children of Item Categories.. Tag: 15.0. This warning will become an error in a future release.

Describe the bug
I have updated my AL Language extension into 5.0.254558 then it is giving me this warning.
May i know how to resolve this warning. Any help would be appreciated. Thank you.
To Reproduce
Steps and to reproduce the behavior:

Make sure you are using the updated AL Language extension
Declare a field having a TableRelated property into the Product Group table.

AL Code to reproduce the issue
Expected behavior
This should not produce any warnings.
Screenshots
If applicable, add screenshots to help explain your problem.

5. Versions:

AL Language: 5.0.254558

Business Central: 16.0.11209.0 (Preview)

Hi @dyepri, it seems that the extension declaring the table "Product Group" has marked its table as obsolete removed. It means that the extension declaring it does not maintain this extension anymore. The AL compiler reports then errors or warnings to warn you about it and let you update your extension.
This means that you should stop using this table. The obsolete reason: 'Product Groups became first level children of Item Categories' gives you an indication on what to do to achieve the same scenario as you used to.


DRILL-8317: Convert LogRegex Format Plugin to EVF V2

DRILL-8317: Convert LogRegex Format Plugin to EVF V2
Description
This PR converts the log/regex reader to use EVF V2.   It also incorporates DRILL-7029 which relocates the log regex reader to the contrib folder.  This has the advantage of making the README file in a place where it is more likely to be found.
Documentation
No user facing changes.
Testing
Ran existing unit tests.

@jnturton Thanks for the quick review!


Question: Check available storage on device

Hello,
I am back again.
Can you please help me in providing a typescript example for using the SystemInfo API to find out free INTERNAL storage space left on device?
For example the Tizen Web App will download some files (to the Downloads folder), but needs to check first there is enough free space available.
(Tizen 4.0 - 6.0)
Thank you!
PS: https://docs.tizen.org/application/web/api/4.0/device_api/mobile/tizen/systeminfo.html#SystemInfoStorage

Hi check the followed code.
import { systeminfo } from 'tizen-common-web
systeminfo.getPropertyValue('STORAGE', (property)=>{
    console.log('property')
})

Then I got storage property like below
SystemInfoStorage {units: Array(1)}
  units: Array(1)
    0: SystemInfoStorageUnit
      availableCapacity: 905261056
      capacity:<PHONE_NUMBER>
      isRemovable: false
      isRemoveable: (...)
      type: "INTERNAL"
    get isRemoveable: ƒ ()
    set isRemoveable: ƒ ()
    __proto__: Object
    length: 1
  __proto__: Array(0)

Hello, thank you for your reply.
yes I tried:
import { systeminfo } from 'tizen-common-web
systeminfo.getPropertyValue('STORAGE', (property)=>{
    console.log('property')
})

However the code did not work (the application is running on SSSP displays - digital signage), I thought maybe STORAGE is not implemented on some displays.
I was wondering how I can extract and use availableCapacity in code.
Should I first get systeminfo.getPropertyValue('STORAGE', ...) and then somehow extract the values from the SystemInfoStorage interface!!??

There is difference between us. My device is a TV.
Can you connect to forum?
This package is for supporting typescript API. And I guess, the 'systeminfo.getProperty` doesn't work on the digital signage.


augment side-channel topic-stub to full-fledged topic

I have links to PR's and other blog posts, for now I'll leave them out, and add them if it's deemed appropriate.
Maybe the the topic: exfiltration resistant signing [ers] should point to side-channels now? Currently the ers topic is a stub.
I built this locally, and checked formatting, trailing spaces, etc. I.e. As per Gandalf the Wise, It Shall Pass...I hope.

@Xekyo or @harding do you have feedback on the additional content for the side-channel topic as proposed here?