Split component implementation and execution

Fixes #257
This is a proof of concept to split the implementation and execution of components. I've updated the components of the controlnet pipeline to test this (it works) and show the impact.
Advantages are:

Pandas components can use __init__ instead of setup, which is probably more familiar to users
Other components can use __init__ as well instead of receiving all arguments to their transform or equivalent method, aligning implementation of different component types
Component implementation and execution should be easier to test separately

I see some disadvantages as well though:

Passing the arguments to __init__ for all components leads to additional boilerplate (see the write_to_hub component)
The spec argument needs to be passed for generic components (eg. the write_to_hub component), which means all components need to accept this as an unused argument (see all other components)
Nit: IDEs will show the warning Call to __init__ of super class is missed. I tried to solve this by using Protocols instead, but apparently they cannot define the signature of the __init__ method

I borrowed the executor terminology from KfP.

I am still a fan of this idea. Imo the advantages clearly outweigh the disadvantages here. Especially we could define a clean way to design component unit tests.
For instance we could add a default TestExecuter that allows to limit the unit test on the transform method.
One additional thought. A PandasXComponent requires a PandasXExecuter, and a DaskXComponent requires a DaskXExecuter, and so on. I think this would be the ideal usage for the good old factory pattern. Alternatively we could add a default method to the component which returns the executer.
if __name__ == "__main__":
    executor = GeneratePromptsComponent.get_executer()
    executor.execute()

As user I don't have to care about the right combination of executer and component anymore.
One more final thought. I think this approach is bulletproofed against future changes. If someday a different execution logic is coming up, we could easily replace the underlying executer without touching the transform method (and potential unit tests) itself.

I am still a fan of this idea. Imo the advantages clearly outweigh the disadvantages here. Especially we could define a clean way to design component unit tests. For instance we could add a default TestExecuter that allows to limit the unit test on the transform method.

Interesting, hadn't thought of that yet.

One additional thought. A PandasXComponent requires a PandasXExecuter, and a DaskXComponent requires a DaskXExecuter, and so on. I think this would be the ideal usage for the good old factory pattern. Alternatively we could add a default method to the component which returns the executer.
if __name__ == "__main__":
    executor = GeneratePromptsComponent.get_executer()
    executor.execute()

As user I don't have to care about the right combination of executer and component anymore.

Yes, definitely agree. I was already playing with this idea a bit, but decided to keep it out of the PoC for simplicity. Ideally we can even leave out the whole if __name__ == "__main__ block. Should be possible if we call some fondant function as the container entrypoint, instead of main.py directly. KfP does something similar.

Passing the arguments to init for all components leads to additional boilerplate (see the write_to_hub component)

Can you elaborate? Is this related to having to write a few extra lines

Yes, I mean the assignment of all variables to self.variable.

Will close this PR and open a new one to keep the original description and discussion here.


Update ember test helpers for Ember 2.0.0-beta.3.

We're starting to give Emberx-select some Glimmer/2.0.0 love and just ran into this today:
https://travis-ci.org/thefrontside/emberx-select/jobs/71832198
Looks related :P
Fixes #46

You need to add a resolution for ember-data in bower.json, that is what caused the Travis failure here.

Any progress on this?  I am on ember v1.13.3 and having memory issues but can't upgrade because I get test failures as described here: https://github.com/emberjs/ember.js/issues/11738.  Supposedly upgrading to ember v1.13.5 and using ember-test-helpers v0.5.2 solves the test failures I'm getting so this PR should be exactly what I need.  Thanks!

Yeah, I got one test passing and hung up on another complaining about normalizeResponse if I remember correctly.

AWESOME!!! Thanks for all the hard work @Robdel12!

@dgeb - Can you bump (I'm mobile ATM)?

@rwjblue no prob - a couple questions:

ok to merge https://github.com/switchfly/ember-mocha/pull/48 first?

does anything in this PR justify a bump to v0.9.0, or should I stick with v0.8.1?

48 is merged (thank you), and this is a compat update so point release is fine.

@rwjblue sounds good - thanks!
And of course thanks to @Robdel12 for all this work!
v0.8.1 has been published.

:+1:

No problem :) Thanks for providing this!!


Update IIS-Lev2.psrc

Fix missing comma.

@alexandair,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


teringlijers ik verlies mijn knaken door jullie

teringlijers ik verlies mijn knaken door jullie

Originally posted by @emadami in https://github.com/safemoonprotocol/Safemoon.sol/issues/32#issuecomment-825774463

teringlijers ik verlies mijn knaken door jullie

Originally posted by @emadami in https://github.com/safemoonprotocol/Safemoon.sol/issues/32#issuecomment-825774463

25800
در تاریخ یکشنبه ۳۰ مهٔ ۲۰۲۱، ۱۷:۵۰ emadami @.***> نوشت:

Closed #1 https://github.com/emadami/assets/issues/1.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/emadami/assets/issues/1#event-4817137384, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ATM6Q6MZ7OFYZR3OBCOHBP3TQI3RNANCNFSM43O6RDJQ
.


Unexpected behavior of const data in compile time loop unrolling

const warn = @import("std").debug.warn;

//This just gives us something to vary the
//const string data with
const Iter = struct {
    Seventeen: f32,
    One: f32,
    Three: f32,
};

test "comptime loop unrolling const behavior" {
    warn("\n");
    comptime var i = 0;
    inline while(i < @memberCount(Iter)) : (i += 1) {
        const FieldName = @memberName(Iter, i);
        warn("|{}|\n", FieldName[0..]);
    }
}

Taking a slice of a const in an comptime unrolled loop yields unexpected results. Possibly related to #699.

This is a bug in Zig when a var or const has different types in different comptime iterations of the while loop.
For example, when i is 0, @typeOf(FieldName) == [9]u8, but when i is 1, @typeOf(FieldName) == [3]u8.
A workaround until the bug is fixed is to make it an expression instead of saving it in a variable:
test "comptime loop unrolling const behavior" {
    warn("\n");
    comptime var i = 0;
    inline while(i < @memberCount(Iter)) : (i += 1) {
        warn("|{}|\n", @memberName(Iter, i)[0..]);
    }
}


How to draw route between to points or Adding polyline on the super-cluster?

Please help me! Thanks you!
Example

Inside <ClusteredMapView /> you can render anything you would render within a normal react-native-maps, so please refer to its official doc for drawing a polyline.


crash when matched view width or height is 0

caused by HeroCoreAnimationViewContext : setSize
subview.center = CGPoint(x: center.x / oldSize.width * newSize.width, y: center.y / oldSize.height * newSize.height)
<- divide by 0 if oldSize or newSize width or height is 0

the same crash as you.

any fixes for this?

I had a similar problem. I spent more than 4 hours on it.
I looked at the logs that the fall occurs at oldSize.height: 0.0.
I use Story boards to work and decided to see what is wrong.
As a result, it turned out that the textLabel had no height construct.


quickwit: 0.8.0 -> 0.8.1, default config file

[x] Based on #300659, merge that first
https://github.com/quickwit-oss/quickwit/releases/tag/v0.8.1
Also fix:

#289000

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Building this still fails on my 128 GB RAM machine with:
thread 'actors::indexer::tests::test_indexer_triggers_commit_on_timeout' panicked at quickwit-indexing/src/actors/indexer.rs:1039:9:
assertion `left == right` failed
  left: MemoryLimit
 right: Timeout

See: https://github.com/NixOS/nixpkgs/issues/289000#issuecomment-2029514548

I observed the same failure when building 0.8.0
Let's skip this test if that's ok with you.

Let's skip this test if that's ok with you.

Fine by me, I don't know yet how to disable specific Rust tests though. Feel free to push into my PR here in case you know it!

I'm not close to a keyboard for long enough to push a commit, but here is an example.
  checkFlags = [
    # tries to make a network access
    "--skip=sinks::loki::tests::healthcheck_grafana_cloud"

so it shoulb be something like --skip='actors::indexer::tests::test_indexer_triggers_commit_on_timeout
I should have time this weekend, I'm just posting this in case you have time before.

Hey guys I've been trying to build quickwit with the UI (and finally managed to do it).
I've also added the recommended build-features. Maybe it would worth to add that with this PR ?

That would indeed be appreciated. Would you he okay with pushing to the branch ?

I already left some comments on your PR #307808

Hey guys I've been trying to build quickwit with the UI (and finally managed to do it).
I've also added the recommended build-features

@tcheronneau Where are those changes, do you have a branch? Feel free to push them into this PR as additional commits for me to review, if you have permission to do that. Otherwise, let me know and I'll pull them.

Hey guys I've been trying to build quickwit with the UI (and finally managed to do it).
I've also added the recommended build-features

@tcheronneau Where are those changes, do you have a branch? Feel free to push them into this PR as additional commits for me to review, if you have permission to do that. Otherwise, let me know and I'll pull them.

@nh2 I don't really know how to come in your PR (not used to github).
But you can find the change there : https://github.com/NixOS/nixpkgs/commit/be916fcec5c99b9f6c7208f3434c7e70d003eec3.

I've prepared a PR but I cannot push to your repo.
In the end the build features does not work for now.
I'll try to debug I got a dev from quickwit I could maybe contact to help.
For now the working package with UI is there : https://gist.github.com/tcheronneau/8c0417705e8acc28e37289255dbb6b45

Sorry folks - I didn't see this one when I pushed up #317152.

Done in #317152.


[MetricsAdvisor]CreateAndGetAlertConfigurationWithOptionalSingleMetricConfigurationMembers failing in nightly runs

MetricsAdvisor nightly test runs are failing with:

Error message:
Azure.RequestFailedException : Service request failed.
Status: 400 (Bad Request)
Content:
{"code":"ERROR_CONFIG_NOT_FOUND","message":"Config 'alert-n-email-setting' cannot be found."}
Headers:
X-Request-ID: f066d517-0804-4b77-ac8d-7698edd5a137
x-envoy-upstream-service-time: 102
apim-request-id: f066d517-0804-4b77-ac8d-7698edd5a137
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
X-Content-Type-Options: nosniff
x-ms-region: REDACTED
Date: Thu, 27 Oct 2022 12:58:44 GMT
Content-Length: 93
Content-Type: application/json; charset=utf-8
Stack trace:
at Azure.AI.MetricsAdvisor.MicrosoftAzureMetricsAdvisorRestAPIOpenAPIV2RestClient.CreateHook(NotificationHook body, CancellationToken cancellationToken) in /Users/runner/work/1/s/sdk/metricsadvisor/Azure.AI.MetricsAdvisor/src/Generated/MicrosoftAzureMetricsAdvisorRestAPIOpenAPIV2RestClient.cs:line 2373
at Azure.AI.MetricsAdvisor.Administration.MetricsAdvisorAdministrationClient.CreateHook(NotificationHook hook, CancellationToken cancellationToken) in /Users/runner/work/1/s/sdk/metricsadvisor/Azure.AI.MetricsAdvisor/src/MetricsAdvisorAdministrationClient.cs:line 1573
--- End of stack trace from previous location where exception was thrown ---
at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.<>c__DisplayClass4_01.<<WrapAsyncResultCore>g__Await|0>d.MoveNext() in /Users/runner/work/1/s/sdk/core/Azure.Core.TestFramework/src/Instrumentation/DiagnosticScopeValidatingInterceptor.cs:line 120 --- End of stack trace from previous location where exception was thrown ---    at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.<>c__DisplayClass5_01.<b__0>d.MoveNext() in /Users/runner/work/1/s/sdk/core/Azure.Core.TestFramework/src/Instrumentation/DiagnosticScopeValidatingInterceptor.cs:line 171
--- End of stack trace from previous location where exception was thrown ---
at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.ValidateDiagnosticScope[T](Func1 action, MethodInfo methodInfo, String source) in /Users/runner/work/1/s/sdk/core/Azure.Core.TestFramework/src/Instrumentation/DiagnosticScopeValidatingInterceptor.cs:line 201    at Azure.AI.MetricsAdvisor.Tests.DisposableNotificationHook.CreateHookAsync(MetricsAdvisorAdministrationClient adminClient, NotificationHook hook) in /Users/runner/work/1/s/sdk/metricsadvisor/Azure.AI.MetricsAdvisor/tests/DisposableNotificationHook.cs:line 49    at Azure.AI.MetricsAdvisor.Tests.AnomalyAlertConfigurationLiveTests.CreateAndGetAlertConfigurationWithOptionalSingleMetricConfigurationMembers() in /Users/runner/work/1/s/sdk/metricsadvisor/Azure.AI.MetricsAdvisor/tests/MetricsAdvisorAdministrationClient/AnomalyAlertConfigurationLiveTests.cs:line 196    at Azure.AI.MetricsAdvisor.Tests.AnomalyAlertConfigurationLiveTests.CreateAndGetAlertConfigurationWithOptionalSingleMetricConfigurationMembers() in /Users/runner/work/1/s/sdk/metricsadvisor/Azure.AI.MetricsAdvisor/tests/MetricsAdvisorAdministrationClient/AnomalyAlertConfigurationLiveTests.cs:line 269    at Azure.AI.MetricsAdvisor.Tests.AnomalyAlertConfigurationLiveTests.CreateAndGetAlertConfigurationWithOptionalSingleMetricConfigurationMembers() in /Users/runner/work/1/s/sdk/metricsadvisor/Azure.AI.MetricsAdvisor/tests/MetricsAdvisorAdministrationClient/AnomalyAlertConfigurationLiveTests.cs:line 269    at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter1.GetResult()
at NUnit.Framework.Internal.AsyncToSyncAdapter.Await(Func`1 invoke)
at NUnit.Framework.Internal.Commands.TestMethodCommand.RunTestMethod(TestExecutionContext context)
at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context)
at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.<>c__DisplayClass1_0.b__0()
at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.RunTestMethodInThreadAbortSafeZone(TestExecutionContext context, Action action)

For more details check here:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1948828&view=results
@jsquire for notification.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.23229685,App Configuration:0.09174481,Extensions:0.07714261'

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.23229685,App Configuration:0.09174481,Extensions:0.07714261'


Invalid test case with_open

Traceback (most recent call last):
  File "tests/cases/with_open.py", line 7, in <module>
    with NamedTemporaryFile(mode="+") as temp_file:
  File "/usr/local/Caskroom/miniconda/base/lib/python3.8/tempfile.py", line 543, in NamedTemporaryFile
    file = _io.open(fd, mode, buffering=buffering,
ValueError: Must have exactly one of create/read/write/append mode and at most one plus

Also occurs on Python 3.9

Fix coming.
https://github.com/adsharma/py2many/issues/283 is for generator support in rust. We can add back the generator test once that is ready. For now I'm deleting it.
with_open code for rust is blocked on having access to the dependent rust library. The generated code passed when I manually tested it.


Set or Unset members in project is not correct.

In GitLab by @liyanq528 on Mar 19, 2020, 08:59

1,The project "mrlipro" was created by mrli and then execute unset member action of many times.

2, Mrli is a system admin user and all project's members has included it when after login.

In GitLab by @luotian-github on Mar 30, 2020, 07:10
assigned to @liyanq528 and unassigned @wknet123

In GitLab by @luotian-github on May 6, 2020, 06:05
operate web too quick, fix it in the next release

In GitLab by @luotian-github on Jun 24, 2020, 02:59
assigned to @cuiaq123 and unassigned @liyanq528

In GitLab by @luotian-github on Jun 24, 2020, 02:59
fixed by wangkun

In GitLab by @cuiaq123 on Jun 24, 2020, 07:11
assigned to @liyanq528 and unassigned @cuiaq123

In GitLab by @liyanq528 on Jul 6, 2020, 07:17
closed


Add unique constraint and a smoke test to check that addresses are unique

We have previously found an edge case whereby an issue with the addressbase import managed to create 2 copies of each address (including duplicated UPRN)
We should:

add a unique constraint to the address table on UPRN
add a smoke test to check that address results for a given postcode contain no duplicates

@aldavidson, i'm asked by @KamalaHB to work on postcodeinfo this week

Address.uprn is already a primary key, so it should be unique already.
do you remember which post code it is? so we can use it for the smoke test.

@cliffxuan  It's an obscure issue to do with the particular way we import the data - it's a lot of data (~29m addresses) so we do a few architectural tricks to make it work in a reasonable amount of time (around 4hrs IIRC). Probably easiest if I come and talk to you in person tomorrow morning?

sure. that'll be good. let's have a chat tomorrow.

summary of the chat with Al.
it's a very weird problem. in theory it shouldn't happen, as uprn is a primary key, which should be unique always. when it happens, it's more likely a bug with postgres. also when it happens, all the post code has duplicates, so a smoke test with 20 is probably sufficient to expose the problem.
i'm not able to reproduce it yet. let's close it but keep an eye on it.


User Panel UI + API Token Tab content

Overview of the Feature Request
This is the initial work for the user panel in the SPA.
This work will include:

Add links to the user panel in the User dropdown from the application header.
Add routing to the user panel.
Create 4 tabs panel with tab open by default according to url query param.
Only the API Token tab content will be created, the rest of the tabs will remain empty for now, maybe disabling tabs.

Note that this is only UI work, it wont show real info about API token yet.
What kind of user is the feature intended for?
All logged in users.
What inspired the request?
Q3 Roadmap Nices To Have

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Initial work has already been done but is moving to “This Sprint” to prioritize another issue for the time being.


An accessor cannot be declared in an ambient context.

Firstly I love this component. I'm amazed there isn't an official popover in the angular material library. Great work and filling an important need!
Bug, feature request, or proposal:
When I add this component to my angular 8 projects I get a bunch of build errors like
90     get focusTrapEnabled(): boolean;            ~~~~~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:91:9 - error TS1086: An accessor cannot be declared in an ambient context.
I've had to enabled skipLibCheck in my tsconfig to get it to build.
Is this an issue with my app or this library? From what I've gathered its related to a breaking change typescript introduce. Any chance the library can be updated to handle more recent typescript versions?

I wasn't able to npm install the latest version
`><EMAIL_ADDRESS>postinstall C:\dolphin\PTCCompass.Web.Angular\node_modules@material-extended\mde

ngcc --properties es2015 browser module main --first-only --create-ivy-entry-points

'ngcc' is not recognized as an internal or external command,`

I still get the ambient context errors
ERROR in ../node_modules/@material-extended/mde/lib/popover/popover-trigger.d.ts:64:9 - error TS1086: An accessor cannot be declared in an ambient context. 64     get popoverOpen(): boolean;            ~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover-trigger.d.ts:79:9 - error TS1086: An accessor cannot be declared in an ambient context. 79     get dir(): Direction;            ~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:42:9 - error TS1086: An accessor cannot be declared in an ambient context. 42     get positionX(): MdePopoverPositionX; chunk {polyfills-es5} polyfills-es5.js, polyfills-es5.js.map (polyfills-es5) 531 kB [initial] [rendered]            ~~~~~~~~~ chunk {runtime} runtime.js, runtime.js.map (runtime) 6.15 kB [entry] [rendered] chunk {scripts} scripts.js, scripts.js.map (scripts) 1.18 MB [entry] [rendered] chunk {styles} styles.js, styles.js.map (styles) 4.84 MB [initial] [rendered] chunk {vendor} vendor.js, vendor.js.map (vendor) 340 kB [initial] [rendered] ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:43:9 - error TS1086: An accessor cannot be declared in an ambient context. Date: 2020-06-15T12:03:42.191Z - Hash: 0791687c50b5319ff64f - Time: 52603ms 43     set positionX(value: MdePopoverPositionX);            ~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:45:9 - error TS1086: An accessor cannot be declared in an ambient context. 45     get positionY(): MdePopoverPositionY;            ~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:46:9 - error TS1086: An accessor cannot be declared in an ambient context. 46     set positionY(value: MdePopoverPositionY);            ~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:48:9 - error TS1086: An accessor cannot be declared in an ambient context. 48     get triggerEvent(): MdePopoverTriggerEvent;            ~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:49:9 - error TS1086: An accessor cannot be declared in an ambient context. 49     set triggerEvent(value: MdePopoverTriggerEvent);            ~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:51:9 - error TS1086: An accessor cannot be declared in an ambient context. 51     get enterDelay(): number;            ~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:52:9 - error TS1086: An accessor cannot be declared in an ambient context. 52     set enterDelay(value: number);            ~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:54:9 - error TS1086: An accessor cannot be declared in an ambient context. 54     get leaveDelay(): number;            ~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:55:9 - error TS1086: An accessor cannot be declared in an ambient context. 55     set leaveDelay(value: number);            ~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:57:9 - error TS1086: An accessor cannot be declared in an ambient context. 57     get overlapTrigger(): boolean;            ~~~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:58:9 - error TS1086: An accessor cannot be declared in an ambient context. 58     set overlapTrigger(value: boolean);            ~~~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:60:9 - error TS1086: An accessor cannot be declared in an ambient context. 60     get targetOffsetX(): number;            ~~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:61:9 - error TS1086: An accessor cannot be declared in an ambient context. 61     set targetOffsetX(value: number);            ~~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:63:9 - error TS1086: An accessor cannot be declared in an ambient context. 63     get targetOffsetY(): number;            ~~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:64:9 - error TS1086: An accessor cannot be declared in an ambient context. 64     set targetOffsetY(value: number);            ~~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:66:9 - error TS1086: An accessor cannot be declared in an ambient context. 66     get arrowOffsetX(): number;            ~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:67:9 - error TS1086: An accessor cannot be declared in an ambient context. 67     set arrowOffsetX(value: number);            ~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:69:9 - error TS1086: An accessor cannot be declared in an ambient context. 69     get arrowWidth(): number;            ~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:70:9 - error TS1086: An accessor cannot be declared in an ambient context. 70     set arrowWidth(value: number);            ~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:72:9 - error TS1086: An accessor cannot be declared in an ambient context. 72     get arrowColor(): string;            ~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:73:9 - error TS1086: An accessor cannot be declared in an ambient context. 73     set arrowColor(value: string);            ~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:78:9 - error TS1086: An accessor cannot be declared in an ambient context. 78     get closeOnClick(): boolean;            ~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:79:9 - error TS1086: An accessor cannot be declared in an ambient context. 79     set closeOnClick(value: boolean);            ~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:84:9 - error TS1086: An accessor cannot be declared in an ambient context. 84     get disableAnimation(): boolean;            ~~~~~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:85:9 - error TS1086: An accessor cannot be declared in an ambient context. 85     set disableAnimation(value: boolean);            ~~~~~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:90:9 - error TS1086: An accessor cannot be declared in an ambient context. 90     get focusTrapEnabled(): boolean;            ~~~~~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:91:9 - error TS1086: An accessor cannot be declared in an ambient context. 91     set focusTrapEnabled(value: boolean);            ~~~~~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:96:9 - error TS1086: An accessor cannot be declared in an ambient context. 96     get focusTrapAutoCaptureEnabled(): boolean;            ~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:97:9 - error TS1086: An accessor cannot be declared in an ambient context. 97     set focusTrapAutoCaptureEnabled(value: boolean);            ~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:104:9 - error TS1086: An accessor cannot be declared in an ambient context. 104     set panelClass(classes: string);             ~~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:111:9 - error TS1086: An accessor cannot be declared in an ambient context. 111     get classList(): string;             ~~~~~~~~~ ../node_modules/@material-extended/mde/lib/popover/popover.d.ts:112:9 - error TS1086: An accessor cannot be declared in an ambient context. 112     set classList(classes: string);

Same Problem in angular 8 project.  Is there any solution to this problem?
This my package.json
"dependencies": {
"@angular/animations": "8.2.12",
"@angular/cdk": "^8.2.3",
"@angular/common": "8.2.12",
"@angular/compiler": "8.2.12",
"@angular/core": "8.2.12",
"@angular/forms": "8.2.12",
"@angular/material": "^8.2.3",
"@angular/platform-browser": "8.2.12",
"@angular/platform-browser-dynamic": "8.2.12",
"@angular/platform-server": "8.2.12",
"@angular/router": "8.2.12",
"@material-extended/mde": "^3.0.3",
"@nguniversal/module-map-ngfactory-loader": "8.1.1",
"aspnet-prerendering": "^3.0.1",
"bootstrap": "^4.3.1",
"core-js": "^3.3.3",
"hammerjs": "^2.0.8",
"jquery": "3.4.1",
"ng-recaptcha": "^5.0.0",
"oidc-client": "^1.9.1",
"popper.js": "^1.16.0",
"rxjs": "^6.5.3",
"zone.js": "0.9.1"
},
"devDependencies": {
"@angular-devkit/build-angular": "^0.803.14",
"@angular/cli": "8.3.14",
"@angular/compiler-cli": "8.2.12",
"@angular/language-service": "8.2.12",
"@types/jasmine": "~3.4.4",
"@types/jasminewd2": "~2.0.8",
"@types/node": "~12.11.6",
"codelyzer": "^5.2.0",
"jasmine-core": "~3.5.0",
"jasmine-spec-reporter": "~4.2.1",
"karma": "^4.4.1",
"karma-chrome-launcher": "~3.1.0",
"karma-coverage-istanbul-reporter": "~2.1.0",
"karma-jasmine": "~2.0.1",
"karma-jasmine-html-reporter": "^1.4.2",
"typescript": "3.5.3"
},
"optionalDependencies": {
"node-sass": "^4.12.0",
"protractor": "~5.4.2",
"ts-node": "~8.4.1",
"tslint": "~5.20.0"
}

@PTC-JoshuaMatthews
@linhongyi
Sorry I missed that you're using Angular 8, I should document v3 is for angular 9.
Please try v2.3.1, let me know if you still have issues with that version and I'll try and set up a repo to test the issue on.
Is there any reason the projects haven't migrated to Angular 9?

@joejordanbrown  v2.3.1 does seem to work on Angular 8, thanks for pointing that out!
v3 was working fine for me by skipping library check so I may just keep using that.
I have a large app to upgrade with a lot to regression test, and the last time I tried to enable Ivy on angular 8 I got a wall of errors, so not looking forward to 9 where its default and I have to fix them all.  Definitely will upgrade sooner than later but it will be big task so it keeps getting pushed back.

@joejordanbrown
It's work in Angular 9 project with v2.3.1 version.
I have to develop client & server project in Visual Studio IDE. The default version of the angular project is 8.0 in Visual Studio. I try to up angular version to 9.0, but has some problem in Visual Studio.

@PTC-JoshuaMatthews
Yeah with a large app switching to Ivy can be a pain. We moved our apps to Ivy a long time back and remember the long weekends fixing everything, I'm hoping the errors are a lot clearer now though because I remember when it was first released debugging was a nightmare.
@linhongyi
I would recommend removing your reliance with the Visual Studio IDE template, I know it's easy to get started with those types of templates but a lot of the time they can be a pain to maintain and update as the frameworks are updated regularly
I'm not familiar with the IDE Angular template but does it use the Angular CLI?

Btw v3 has lots of bug fixes, which have not been backported to v2. I'm not sure if I have time to maintain v2 but you're welcome to create pull requests if the fixes are required for your projects.
I'm also spending a lot of time updating the internals and there will be API changes when v4 is released in the near future. It will use a cleaner API for configuring, provide a lot more fine-tuning and auto calculating the arrow position offset.


SynchronossPartHttpMessageReader created millions of temporary directories

Describe the bug
I found that wheather Content-Type is multipart/form-data or application/json, SynchronossPartHttpMessageReader will create a temporal directory with prefix "synchronoss-file-upload-" every request come, and these temporal directoriese will not be cleared by docker, so now I can't execute commands such as ls in the /tmp directory.
Is it possible to postpone the execution of createTempDirectory()?

    public class SynchronossPartHttpMessageReader extends LoggingCodecSupport implements HttpMessageReader<Part> {

	private static final String FILE_STORAGE_DIRECTORY_PREFIX = "synchronoss-file-upload-";
        private Path fileStorageDirectory = createTempDirectory();

        @Override
        public Flux<Part> read(ResolvableType elementType, ReactiveHttpInputMessage message, Map<String, Object> hints) {
            return Flux.create(new SynchronossPartGenerator(message, this.fileStorageDirectory))
                    .doOnNext(part -> {
                        if (!Hints.isLoggingSuppressed(hints)) {
                            LogFormatUtils.traceDebug(logger, traceOn -> Hints.getLogPrefix(hints) + "Parsed " +
                                    (isEnableLoggingRequestDetails() ?
                                            LogFormatUtils.formatValue(part, !traceOn) :
                                            "parts '" + part.name() + "' (content masked)"));
                        }
                    });
        }

        private static Path createTempDirectory() {
            try {
                return Files.createTempDirectory(FILE_STORAGE_DIRECTORY_PREFIX);
            } catch (IOException ex) {
                throw new UncheckedIOException(ex);
            }
        }

    }

Spring Version:

        <dependency>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-starter-gateway</artifactId>
            <version>2.2.8.RELEASE</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-web</artifactId>
            <version>5.2.15.RELEASE</version>
        </dependency>

Sample
curl -XPOST -H 'Content-Type: application/json' "https://spring-cloud-gateway/path"

Whether frequent directory creation will cause the pod (in docker) memory increasing continuously, thereby affecting the stability of the application.
At present, I found that pod memory usage as high as 90% or more.

Closing in favor of https://github.com/spring-projects/spring-framework/issues/27092


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/110658

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/114656

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/116736

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/117337

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/118755


Implemented (Python) Counting Sort

🛠 Issue (Number)

Issue no #121
👨💻 Changes proposed

Added implementation for Counting Sort in Python.
✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots
Code:

Output:

@Kumar-laxmi @072arushi @siddhi-244 @zugzwang03
Requesting a review. Thank you.

@stiwari-ds Only output screenshot is enough


Backport of ISPN-7781 to 8.2.x

Upstream Issue: https://issues.jboss.org/browse/ISPN-7781

Looks good, thx @rpelisse!


Use scene-graph for damage tracking

Depends on: https://github.com/Hjdskes/cage/pull/197
This PR goes one step further and delegates damage tracking to the scene-graph via https://github.com/swaywm/wlroots/pull/3117.

Merged into https://github.com/Hjdskes/cage/pull/197


Wrong Field Number in Table Extension

https://github.com/microsoft/ALAppExtensions/blob/main/Apps/W1/StatisticalAccounts/app/src/StatAccSourceCodeSetup.TableExt.al
This TableExtension for Source Code Setup uses the wrong field number. This will conflict with customer extensions.
{
field(50050; "Statistical Account Journal"; Code[10])
{
Caption = 'Statistical Account Journal';
TableRelation = "Source Code";
}
}

Unfortunately, this field was already released with 2023 Wave 1 and giving it a new ID would hence be a breaking change. The field has been deprecated and replaced with a new one in 2023 Wave 2. We'll see what we can do to prevent this from happening.


should use builtin_cpu_supports on gnu/linux

i.e. https://gcc.gnu.org/onlinedocs/gcc-6.1.0/gcc/PowerPC-Built-in-Functions.html#PowerPC-Built-in-Functions
this should be a tiny bit faster than getauxval() when it is supported.

Thx for noticing, the code is indeed quite compact.
For now I'm a bit reluctant to add optimizations based on compilers because it will make the code more complicated.
The design of this library is to pay a small price at startup to collect features, but it's not designed to pay the smallest price possible.
I'm happy to implement this change if this issue collects many :+1: reactions though.


Prevent Default Forms

It would be nicer to prevent default form submissions and then submit the request later.

I don't think this is necessary anymore unless we need more async logic before the form submission happens. Currently, the only async stuff we need in the form handler is the screenshot handler from the background thread. However, I was able to get this working without needed this. Closing this for now.


Add rename field to json annotation and build.yaml

Due to varying field naming conventions, Crimson should have support for renaming all fields in a class by providing an enum value to the json annotation with whatever case the fields come in. All that is provided currently is the name field on the JsonField annotation. json_serializable has support for kebab, screamingSnake, pascal, and snake via its FieldRename enum. This should also apply to enums as well.

Just implemented this. You can now use @jsonKebabCase and @jsonSnakeCase. Check out the readme 🙂


Update for consistency with KinKal v3.0.1 and with https://github.com/Mu2e/Offline/pull/1227

Trigger performance should improve slightly as less time is spent building the KalSeed.  Tested with all 744K NoPrimary2BB and ~100K CeEndpoint

Hi Giani,
I should have been more clear, this PR needs Offline PR 1227 as some KinKal
options changed.  You will need to use an older version of mu2e_trig_config
to ru the trigger till that’s merged.
Dave
David Brown            @.***
Office Phone<PHONE_NUMBER>
Lawrence Berkeley National Lab
M/S 50R5008 (50-6026C)  Berkeley, CA 94720
On Fri, Mar 29, 2024 at 02:26 Gianantonio Pezzullo @.***>
wrote:

Merged #19 https://github.com/Mu2e/mu2e_trig_config/pull/19 into main.
—
Reply to this email directly, view it on GitHub
https://github.com/Mu2e/mu2e_trig_config/pull/19#event-12293126654, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAH57Z2RPQCRMEIO6AODJDY2UQUBAVCNFSM6AAAAABFNPQWLWVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGI4TGMJSGY3DKNA
.
You are receiving this because you authored the thread.Message ID:
@.***>


BUG: fix sparse .mean to return a scalar instead of a matrix

Fix #5948.
Also added test to make sure that the output of .mean and .sum is a scalar
since this assert_array_equal does not make any difference between a
scalar and an array of any shape with a single element, e.g. this doesn't raise an error:
import numpy as np

np.testing.assert_array_equal(1, np.array([[1]]))

@@            master   #5949   diff @@
======================================
  Files          238     238
  Stmts        43710   43711     +1
  Branches      8200    8200
  Methods          0       0
======================================
- Hit          34139   34138     -1
- Partial       2599    2600     +1
- Missed        6972    6973     +1

Review entire Coverage Diff as of 1768612

Powered by Codecov. Updated on successful CI builds.

LGTM, once the tests are fixed.

Merged. Thanks, @lesteve!


Factor in DX for comparison with Go

Good DX is a decisive factor for many people, so we should mention it.

@rojvv what is this waiting for?

It is waiting for the Russian label to be renamed to :ru: RU.

Done.


Convert node-uuid to ES6 module definition style

Following the ideas of #6112 and #6125
The following code compiles using the current type definition:
/// <reference path="../typings/node-uuid/node-uuid" />

console.log(uuid.v4());

but fails at runtime.
For those, like me, who use SystemJS (or other modules loaders) to load modules, we need to declare dependencies via imports, and generally rely on the compiler to tell us when we have missed one (as is the case here).
This PR creates two (linked) versions of the type definition:

For those people who use module loaders and want the above code to be a compile error because they haven't imported node-uuid, they should use node-uuid.d.ts
For those wanting the existing behaviour, they should reference node-uuid-global.d.ts

So if instead I reference the node-uuid.d.ts in this PR, the above code would give a compile error:
error TS2304: Cannot find name 'uuid'

This forces me to import:
/// <reference path="../typings/node-uuid/node-uuid" />

import * as uuid from "node-uuid";

console.log(uuid.v4());

@vvakame - can I get your thoughts on this, given you touched this last?

I'm thinking about this pattern often, but I can't get my answer yet...
old style design is not confuse my brain at writing code.
@basarat do you have some opinions?

do you have some opinions

I like this pattern over what is there in react. @vvakame I'd be happy to merge this if its okay with you. Especially true for packages that are NPM first (like this one , lodash , react).
@myitcv sorry for the delayed attention, please wait for a response from a team member before working on others as your time is precious :rose:

@basarat

I like this pattern over what is there in react.

Could you expand? This is very similar to what React looks like with the exception of the additional common file. Is that what you were referring to?
React:

react.d.ts (contains __React and "react")
react-global.d.ts (contains React)

This PR:

common.d.ts (contains __UUID)
node-uuid.d.ts (contains "node-uuid")
node-uuid-global.d.ts (contains UUID)

Is that what you were referring to?

Yes. Just that when a new PR comes we have to ask the person to update two files

@basarat - no apology needed. I feel like I've been bombarding you and others with requests recently so any apology due is probably from me!
More important to take time on trying to get this "right" in the hope this PR can be used as a template for other that are looking to become ES6 module compatible/compliant.
@jbrantly do you have any concerns on this approach (particularly given your previous thoughts)?
Would be happy to pick up the question of 'duplication' between test files in this issue

Nope, no concerns on layout (having a common file).
I think you could possibly simplify things a bit though by:

Removing declare var in the common file
Removing declare var and declare type in the global file and instead use import uuid =
Don't nest in the common file. Just create a namespace and put v1, parse, etc on it instead of in a separate interface.

The downside to that approach though would be that both the value-side and the type-side would have the same casing (uuid) vs how the PR is currently is (value is uuid and type is UUID). So definitely feel free to ignore :grin: just something that jumped out at me.

@myitcv , is this still relevant? I had a PR a few weeks back which already splits the definitions per environment.

@use-strict - thanks, hadn't seen that. Yes, looks like some overlap.
Your merge raises some interesting questions:

Which definition should be the 'default'? You elected the node environment
I notice you named the 'module' version node-uuid-cjs.d.ts - what's the thinking behind the naming here? Don't think this is exclusive to CommonJS

I only chose node as default because the library is called node-uuid. Somehow naming the file node-uuid-node.d.ts seemed a bit off.
I didn't have a particular reason here. I know the actual module system is probably irrelevant as TypeScript abstracts it. However, I only tested with CommonJS, so I may have been biased.

@use-strict thanks. This PR however can be closed from my perspective. Yours is much more comprehensive (and follows the concept of shared .d.ts files too)


strange backlight behavior

the functionality is working. But when the numpad is turned off, pressing any key on the keyboard turns on the backlight. At the same time, the touchpad does not start working as a numpad, only the backlight.   UM3402YAR Zenbook, M433IA

The problem was with Hyprland. I just deleted input.numlock_by_default = true and everything worked


Removed common trace/debug functionality

Functionality moved into https://www.npmjs.com/package/@google/cloud-diagnostics-common

LGTM.


api: handle field_migrate.rename

Description:
api: handle field_migrate.rename in proto migrate.
Risk Level: Low
Testing: CI
Docs Changes: API_VERSIONING.md
Release Notes: N/A

based on #9251 and #9262.


Add Alias column support in join condition for JoinIndex rule

Describe the issue
Add support for org.apache.spark.sql.catalyst.expressions.Alias as column type in JoinIndexRule.scala. Currently, this rule only supports Join Conditions on org.apache.spark.sql.catalyst.expressions.Attributes . Consider a case where a column c from the base table has an alias aliasC. A Join query with c will be able to utilize indexes but a query with aliasC won't be.
To Reproduce
Create a query plan of the form
select T1.A, T2Temp.B
from T1
INNER JOIN (
   select c as aliasC
   from T2
) as T2Temp
where T1.C = T2Temp.aliasC

Expected behavior
Query utilizes index
Screenshots
NA
Desktop (please complete the following information):
NA
Additional context
NA

CC: @sezruby

CC: @imback82

I think this should have been fixed by https://github.com/apache/spark/pull/26943 in Spark 3.0.
For the following:
spark.conf.set("spark.sql.autoBroadcastJoinThreshold", "-1")
sql("drop table t1")
sql("drop table t2")
val df1 = (0 until 100).map(i => (i % 5, i % 11)).toDF("i1", "j1")
val df2 = (0 until 100).map(i => (i % 7, i % 11)).toDF("i2", "j2")
df1.write.format("parquet").bucketBy(8, "i1").saveAsTable("t1")
df2.write.format("parquet").bucketBy(8, "i2").saveAsTable("t2")
sql("SELECT t1.i1, t2Temp.aliasC FROM t1 INNER JOIN (SELECT i2 as aliasC from t2) as t2Temp WHERE t1.i1 = t2Temp.aliasC").explain

Spark 2.4.5 outputs:
== Physical Plan ==
*(5) SortMergeJoin [i1#31], [aliasC#37], Inner
:- *(2) Sort [i1#31 ASC NULLS FIRST], false, 0
:  +- Exchange hashpartitioning(i1#31, 200)
:     +- *(1) Project [i1#31]
:        +- *(1) Filter isnotnull(i1#31)
:           +- *(1) FileScan parquet default.t1[i1#31] Batched: true, Format: Parquet, Location: InMemoryFileIndex[file:...], PartitionFilters: [], PushedFilters: [IsNotNull(i1)], ReadSchema: struct<i1:int>, SelectedBucketsCount: 8 out of 8
+- *(4) Sort [aliasC#37 ASC NULLS FIRST], false, 0
   +- Exchange hashpartitioning(aliasC#37, 200)
      +- *(3) Project [i2#33 AS aliasC#37]
         +- *(3) Filter isnotnull(i2#33)
            +- *(3) FileScan parquet default.t2[i2#33] Batched: true, Format: Parquet, Location: InMemoryFileIndex[file:...], PartitionFilters: [], PushedFilters: [IsNotNull(i2)], ReadSchema: struct<i2:int>, SelectedBucketsCount: 8 out of 8

whereas Spark 3.0 prints:
== Physical Plan ==
*(3) SortMergeJoin [i1#27], [aliasC#33], Inner
:- *(1) Sort [i1#27 ASC NULLS FIRST], false, 0
:  +- *(1) Project [i1#27]
:     +- *(1) Filter isnotnull(i1#27)
:        +- *(1) ColumnarToRow
:           +- FileScan parquet default.t1[i1#27] Batched: true, DataFilters: [isnotnull(i1#27)], Format: Parquet, Location: InMemoryFileIndex[file:...], PartitionFilters: [], PushedFilters: [IsNotNull(i1)], ReadSchema: struct<i1:int>, SelectedBucketsCount: 8 out of 8
+- *(2) Sort [aliasC#33 ASC NULLS FIRST], false, 0
   +- *(2) Project [i2#29 AS aliasC#33]
      +- *(2) Filter isnotnull(i2#29)
         +- *(2) ColumnarToRow
            +- FileScan parquet default.t2[i2#29] Batched: true, DataFilters: [isnotnull(i2#29)], Format: Parquet, Location: InMemoryFileIndex[file:...], PartitionFilters: [], PushedFilters: [IsNotNull(i2)], ReadSchema: struct<i2:int>, SelectedBucketsCount: 8 out of 8

Great thanks! I'm closing this issue.

@apoorvedave1 Can you confirm if this is not needed in the join rule? I see that we clean up the aliases, so matching should be ok, right?


Does it support multi-hop ssh

Is it possible to use sftp when I have to access the target machine through several gates? For example, localhost is A, target machine is D. I have to ssh into D, through A->B->C>D.

No :(

See connection hopping.


Regarding Resubmission of Source Code

Hi,
I just wanted to know if there is any way I can resubmit my solution?

Rereading the email, I think that they may clone your repo if you gave them the link. Then, you just have to make sure your repo is up to date.


NoMethodError

I'm using countries with country_select. Any method call results in the following error:
NoMethodError: undefined method `data' for #Object:0x00000001e04600
with trace leading to /gems/countries-0.9.3/lib/countries/country.rb:51:in `=='
Could you please take a look?

Should be solved by #177


Scan for overlapping memory range is very, very slow

As it is currently implemented, an out-of-memory can occur in some situations. Need to think of a better method.

The current implementation is sort of brain dead. We know that ArrayBuffers don't overlap. The whole problem is simply self-inflicted. A lot of the C++ code is relics from a failed approach and should be removed. Pointer synchronization should be handled by JS.


Update components.md

Should be “a” not “an”

An "at" code block. Across the docs we say "at" for @ when reading the text.


environment variable not set pusher key

Hi Antonio
I have a problem when I try installing antonioribeiro/ci package.
And the error "environment variable not set: PUSHER_KEY" appear at step "Create a database, configure on your Laravel app and migrate it" when i run "php artisan migrate --package=pragmarx/ci"
I have looked for on Google and still do not know the reason why ?
Please help me fix this problem!
Thank a lot ! :)
https://gyazo.com/8b3374b01c21ffcd4eeb9da0af5e9663

I'm having this same issue. Has this been resolved?

A quick fix for this is to comment out or set defaults in the config files where these environment variables are referenced. PUSHER_KEY is used in config/broadcasting.php

This was related to another package. Already fixed. Please check the latest version, lots of new stuff.


Change to a Rust neofetch alternative

One possible option is 'freshfetch' but it's not stable yet.
File containing existing code can be found here.
I would like to include a similar configuration file too.

Consider it done by https://github.com/xrhstosmour/arch-tuner/pull/8.


Remove unused context.Context parameter from cmd.NewRootCmd

Does what it says on the tin.

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

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

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

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

MacOS -

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

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

MSI

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

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

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: 01/28/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.
  -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       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                  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

@ellismg Just trying to build a mental model for my own sake on how we should think about ctx when designing new programs. We definitely do pass and include ctx as a method signature in other places even when unused. What differs for root.NewRootCmd? Leaving it seems more consistent based on my current understanding.

This is an injected param from IoC container - so if it's not needed anymore than no need to inject it.

@ellismg Just trying to build a mental model for my own sake on how we should think about ctx when designing new components. We definitely do pass and include ctx as a method signature in other places even when unused. What differs for root.NewRootCmd? Leaving it seems more consistent based on my current understanding.

Yeah - it's a good question here, @weikanglim.
When I discovered this, I was thinking it about as a "parameter which is injected by DI" (and I was struggling to understand "is the context I'm passing in here say captured and used as the root context for every command that is returned by NewRootCmd when it runs (which was important to me as I was trying to refactor stuff for the vs-server and understand how things were working).  Once I realized it was not actually captured and used - I was like: "Let me just remove it, so the method is easier to understand).
To be honest, I didn't even think of it as being used as a normal go context object (i.e. as a way to observe cancellation while the NewRootCmd method is running).  I do see how it would make sense to keep it (and I'm happy to revert this PR and add it back with a comment that explains what exactly the context object is used for, i.e for observing cancellation during construction (and to be passed to any calls it makes that do I/O and need to be canceled) but I also am fine with the current design where it just not present.
I think if this was not used as a .ctor in our IoC system, I would not have done this PR.


Add the ability to store PackingPlan in the state manager

Add the basic PackingPlan CRUD operations to IStateManager and it's implementations.

 That said, #1110 does not happen to me.

Any other comments on this ticket or can I get a ship it?

+1

:+1:


How to reproduce the n shot VQA, OKVQA and GQA results from Table -1? No eval script is available

Hey Authors,
Awesome work, could you please provide me with the fewshot/zeroshot eval script to reproduce your VQA/OKVQA/GQA results in Table-1? cc @benbrandt @countably1nfinite @sdtblck @Mayukhdeb.

Seconded! It would be very helpful to have the evaluation scripts.

Hi,
currently the eval scripts are not in a releasable state. I might clean them up and add them at some point but can't promise.
We largely follow the implementation in https://github.com/GT-Vision-Lab/VQA/tree/master.
The rest of the details is in our paper https://arxiv.org/abs/2112.05253.
I hope this helps, if there are questions left feel free to ask :-)
Best,
Constantin


[BUG] Workflow load fails to load categorical encodings during transform

Hi there,
Describe the bug
I create an nvt.Workflow object called proc which I fit to a given nvt.Dataset instance. Afterwards I save this object to an empty directory proc.save(workflow_path).
If I try to load this workflow and transform the very same dataset in a separate Python process it fails since it cannot find the key for the first column in the dictionary where it tries to lookup the paths for the categorical encodings. It somehow doesn't seem to store them there in the first case since it yields a KeyError.
ailed to transform operator <nvtabular.ops.categorify.Categorify object at 0x7fc6f35759d0>
Traceback (most recent call last):
  File "/home/mkurovski/miniconda3/envs/recsys/lib/python3.8/site-packages/nvtabular-0.5.3+3.g50f04df-py3.8.egg/nvtabular/ops/categorify.py", line 397, in transform
    path = self.categories[storage_name]
KeyError: 'hashtags'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/mkurovski/miniconda3/envs/recsys/lib/python3.8/site-packages/nvtabular-0.5.3+3.g50f04df-py3.8.egg/nvtabular/workflow.py", line 346, in _transform_partition
    df = column_group.op.transform(column_group.input_column_names, df)
  File "/home/mkurovski/miniconda3/envs/recsys/lib/python3.8/contextlib.py", line 75, in inner
    return func(*args, **kwds)
  File "/home/mkurovski/miniconda3/envs/recsys/lib/python3.8/site-packages/nvtabular-0.5.3+3.g50f04df-py3.8.egg/nvtabular/ops/categorify.py", line 417, in transform
    raise RuntimeError(f"Failed to categorical encode column {name}") from e
RuntimeError: Failed to categorical encode column hashtags

Steps/Code to reproduce bug
Steps to generate and save the corresponding workflow
trains_itrs = nvt.Dataset(
    filepaths,
    engine="parquet",
    part_size="2GB",
)
# all_feat_columns is a a <ColumnGroup + output> object that incorporates various feature columns with transformations like `Categorify`
proc = nvt.Workflow(all_feat_columns)
proc.fit(trains_itrs)

workflow_path = "/home/mkurovski/data/workflow/"
proc.save(workflow_path)

Steps to retrieve and apply the workflow (in a different session afterwards, time-wise decoupled)
workflow_path = "/home/mkurovski/data/workflow/"
os.listdir(workflow_path)  # returns ['categories', 'workflow.pkl', 'metadata.json']
trains_itrs = nvt.Dataset(
    filepaths,
    engine="parquet",
    part_size="2GB",
)
proc.load(workflow_path)  # returns <nvtabular.workflow.Workflow at 0x7fc548064370>

# this is where it fails with the error message above
proc.transform(trains_itrs).to_parquet(
    output_path=output_folder, preserve_files=True
)

Expected behavior
I expect it to find the paths properly when loading a persisted workflow. This seems to run into an error if you try to retrieve in in another session, so maybe it's not persisting the workflow properly in the first place.
Environment details (please complete the following information):
nvtabular-0.5.3+3.g50f04df installed from source
Happy to answer any follow-up questions
Thanks and Best Regards,
Marcel

```Workflow.load`` is a classmethod that works like an alternate constructor, and returns a Workflow object.
Can you try
proc = nvt.Workflow.load(workflow_path)

instead?

Thanks, this way it works!

Awesome - great!


Address #2539 by caching auth token

Fix Issue #2539.
Changes
Cache the Authentication Token provided by CredentialEnvelope to improve performance and eliminate a continuous trace loop.
Introduce a CachedReflectionCredentialEnvelope class, derived from ReflectionCredentialEnvelope and use it when constructing the credential envelope in TelemetryConfiguration. The cached version will check if the cached auth token still has enough remaining lifetime (at least 5 minutes, by default) to be re-used.
Checklist

[x] I ran Unit Tests locally.
[x] CHANGELOG.md updated with one line description of the fix, and a link to the original issue if available.

@TimothyMothra PTAL

@TimothyMothra, PTAL


fet: resolve #10 pkgproto

Looks good; I will make some changes later on, it's already on the (roadmap to Copacabana 0.5)[https://github.com/orgs/Projeto-Pindorama/projects/1].
I will be a little bit busy until I can touch this repository again, but already got a date to.


linux to windows - server crash with new save

I converted my save, this went well and it said "Fix has been applied!".
Copying that new save back into the server and booting up the server went fine as well.
The moment I try to load in, the server crashes without showing errors.

Have you fixed this problem? I also get the "Fix has been applied", and the server started successfully, but I cannot hop in. Just loading forever.

not yet, the infinte loading is bcs the server crashes.

Have you fixed this problem? I also get the "Fix has been applied", and the server started successfully, but I cannot hop in. Just loading forever.

I fixed it, I had to run the command from inside the new server save folder.
So short explanation:

Your old server save file, you copy the complete folder in the "0". So the first folder is the one with all the numbers and letters and everything inside it.
You place that one in your "0" folder of your new server.
Make sure to change your gameserversettings to the new numbers and letters save folder
You run your new server, join and create a new character so there is a new save file
quit the server, close the server
Run the command from inside the new server save folder, like so :

python fix-host-save.py <uesave.exe> <SAVEFOLDER OF NEW SERVER, ENDING WITH THE LETTERS AND NUMBERS FOLDER>

This did the trick for me.
Before when the server crashed on join, that script finished in like 2-5 seconds. Now it took over 5 minutes per save file and it worked.


[Packaging | License] - Add a license to the project

After having investigated and getting familiarised with

Proprietary / non-commercial licenses
Copyleft licenses
Permissive and open licenses

A permissive free software license should be used (Apache License 2.0 seems a good choice)

Any scenario in where a copyleft license could be useful or needed ?

Permissive permits proprietary derivative works. If we want our project to be 100% free (and guarantee that anyone who uses this code to make their code open), we may use a copyleft license (e.g., GNU GPL).

Also, are you familiarised with the re-licensing of a repository / project ? Please investigate under which circumstances this can be done and by whom.

It depends on the original license and the final license. The original license of the extension template is BSD (permissive), so it could be done. With copyleft licenses this would be more difficult. In addition, when we use the copier command in the tutorial, it creates the license with the "extension author name" (me), so I think I can modify the license.


chore(base): fix comment for parallelized mapping

Description
Sorry for the late review and now #141 is merged, I've created a PR to update the comments that should have been done in #141.
This PR fixes comments for ParallelizeMapByChunkSize and ParallelizeMap.

CI failure is a known issue. See https://github.com/kroma-network/tachyon/issues/129


Added Apply Google's DNS to all connections under disable Telemetry s…

…ection

Love the idea, but this would mess all my systems up as I host my own DNS and don't use google dns. This can be added as an option, but never part of the essential tweaks.
Personally Cloudflare and Level3 will be more performant if doing this to systems.
<IP_ADDRESS>
<IP_ADDRESS>
Respectively.


Clean also the downloads history?

Could you please add an option to clean also the downloads history?
Firefox never does it, for some reason..

Don't make this a default. Unlike the history, the downloads are important to me and I have far less downloaded files than internet history. I don't want my downloads like important pictures or documents to be accidentally deleted by Firefox.

This is a duplicate of #2