Adding examples to label epilepsy patients electrodes

For iEEG data, we propose to describe the final conclusion drawn by an epileptologist on the electrodes involved in the seizures in the _electrodes.tsv. The final conclusion for each channel will be described in an additional column - seizure_zone, following HED format.
Please review @dorahermes

lgtm! @sappelhoff this example for electrode labeling in epilepsy has been reviewed by several neurologists from different large epilepsy sites, when should we merge this?

Do electrodes.json files even pass the validator? 🤔 I thought that the JSON file for electrodes.tsv is the coordsystem.json?

I think @dvanblooijs has done this and I believe it passed the validator.
I remember it was a design decision to name _coordinatesystem.json different than _electrodes to ensure that _electrodes.json could be used for these purposes per the general spec that every .tsv file could have an accompanying .json.

If I read the manual correctly: coordystem.json is another file describing the location of fiducials, anatomical landmarks and coordinate system. We used the electrodes.json file to describe extra fields in our table that are not present in the BIDS version, like DKT atlases, resected area, and seizure onset zone.  It passes the validator if you locate the electrodes.json file in the same folder as the electrodes.tsv. When you don´t have an electrodes.json but you do have extra fields in your electrodes.tsv, you will get warnings that some fields are not described in electrodes.json.

Thanks for trying this out @dvanblooijs  and for your explanations @dorahermes and @dvanblooijs.
I have looked into how this is implemented in the validator, and opened this issue: https://github.com/bids-standard/bids-validator/issues/1118
Basically, the support for this is there in both the spec and the validator. We just need to slightly adjust the validator to also allow electrodes.tsv+JSON at the "top" level and the "session" level ... mainly for consistency reasons. I don't think specifying electrods.tsv/json at the top level makes sense (however, specifying at the session level does make sense).
So that something like this would be possible (session level):
README
CHANGES
participants.tsv
sub-01/
    ses-01/
        sub-01_ses-01_electrodes.tsv
        sub-01_ses-01_electrodes.json
        sub-01_ses-01_coordsystem.json
        ieeg/
            sub-01_ses-01_task-rest_ieeg.edf
            sub-01_ses-01_task-rest_ieeg.json
            sub-01_ses-01_task-rest_channels.tsv

or this (top level):
README
CHANGES
participants.tsv
task-rest_electrodes.tsv
task-rest_electrodes.json
task-rest_coordsystem.json
sub-01/
    ses-01/
        ieeg/
            sub-01_ses-01_task-rest_ieeg.edf
            sub-01_ses-01_task-rest_ieeg.json
            sub-01_ses-01_task-rest_channels.tsv

I totally agree that an electrodes.json at session level or at top level makes sense! We had that previously but this gave an error when running the bids validator. I had the same problem with the events.json at top level. I asked this on neurostars (https://neurostars.org/t/quick-validation-failed-the-general-folder-structure-does-not-resemble-a-bids-dataset/2416/13), because the bids validator states that events.json could be at top level, but it gave an error when it was located at top level. Maybe this could be added to this issue?

We had that previously but this gave an error when running the bids validator. I had the same problem with the events.json at top level.

There is also some discussion on this here: https://github.com/bids-standard/bids-specification/issues/528 and in the PRs/issues linked from there.
I think the regular expressions currently cover more than 90% of valid use cases ... but there are still some use cases that are not appropriately covered. It'd need a really good look at it, or stepwise improvements. Feel free to suggest such improvements as issues to bids-validator like I just did in https://github.com/bids-standard/bids-validator/issues/1118 :-)

I will leave this issue open until it is officially resolved in the validator.

Thank you all for the inputs, I will leave this issue open until it is officially resolved in the validator.

I finally found a minute to adjust the validator with this PR: https://github.com/bids-standard/bids-validator/pull/1142
let's wait until it's merged, then we can merge this.

Thank you all for the inputs, I will leave this issue open until it is officially resolved in the validator.

I finally found a minute to adjust the validator with this PR: https://github.com/bids-standard/bids-validator/pull/1142
let's wait until it's merged, then we can merge this.

Thank you all for the inputs, I will leave this issue open until it is officially resolved in the validator.

I finally found a minute to adjust the validator with this PR: bids-standard/bids-validator#1142
let's wait until it's merged, then we can merge this.

as the PR on the validator got merge I will also merge this one.

Thanks @Remi-Gau, I completely forgot :face_with_head_bandage:


Update NuGet package structure to conform with other Office packages

This PR brings the order and capitalisation of the Content and Scripts folder in line with other, similar NuGet packages, such as Office.js

Looks good to me.

I'll merge this in and cherry pick it over to the 'release/2.1.0' branch so that we can finish releasing 2.1.0.


Finka->echo update

Trying to contribute. Fix for #84

Hi @nick-kim-96 ,
Thank you for contributing to R6 counters! Unfortunately, I think you have potentially made the changes in the wrong file. See this wiki page for how to add new counters for an operator: https://github.com/BurkusCat/r6-operator-counters/wiki/How-to:-Add-counters-for-an-operator
Here are a couple of example pull requests that add/change counters:
https://github.com/BurkusCat/r6-operator-counters/pull/178
https://github.com/BurkusCat/r6-operator-counters/pull/172
The only file that needs changed should be finka.js. Would you be able to remove your changes to package-lock.json and r6OperatorCounters.json please?

Hey @nick-kim-96 ,
I just wanted to check if you are still interested in making this change! Give me a shout if you have any questions about how to make the changes :)
Thanks,
Burkus


turning term suggestions off by default

Codecov Report

Merging #189 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #189   +/-   ##
=======================================
  Coverage   71.25%   71.25%
=======================================
  Files         245      245
  Lines       15551    15551
  Branches     1662     1662
=======================================
  Hits        11081    11081
  Misses       4470     4470

Impacted Files
Coverage Δ

app/public/config.js
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Storage folders, etc, still visible in /public mode (.htaccess doesn't block)

Subfolders in storage, etc, are not blocked (testing on http://vmsdemo.space)
Happens when put into subfolder (e.,g https://vmsdemo.space/subfolder)

refs #411

Unable to reproduce this, and have phpVMS git master installed in a subdir here. The rewrite rules in public/.htaccess need modifying to work in a subdirectory:
Options -Indexes

<IfModule mod_rewrite.c>
    <IfModule mod_negotiation.c>
        Options -MultiViews
    </IfModule>

    RewriteEngine On

    # Handle Authorization Header
    RewriteCond %{HTTP:Authorization} .
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # Redirect Trailing Slashes If Not A Folder...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.*)/$ /phpVMS/$1 [L,R=301]

    # Handle Front Controller...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^ /phpVMS/index.php [L]
</IfModule>

Thanks, I might include that in the docs... "officially" I'm not supporting subdirectory installs, mainly because Laravel doesn't behave well with it.

Alright, let me start from the oldest bug.
I would like to solve it @nabeelio

@YashGovekar actually this one I can close, it seems to be fixed


Can I reference a key vault in the ARM template itself, or only in the Parameters file

It is unclear to me in this article whether or not it is possible to reference a key vault directly within an ARM template, or if it is only possible within a separate parameters file.  I'm trying to set up a configuration where my infrastructure team manages the template file (including referencing a key vault for secure information), and my "clients" (the application level guys requesting a VM) provide their parameters file which includes only data that they need to provide - which shouldn't include where to find the local admin password for the VM...

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

ID: ecb6fa26-f01e-e9dd-efad-74c0898e2027
Version Independent ID: 4582bdc2-1d26-067d-4343-a63736d4bf8f
Content: Key Vault secret with template - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/key-vault-parameter.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

@HoCGeek - the key vault is referenced in the parameter file, not the template.

Thanks a lot @tfitzmac for helping on the thread.
@HoCGeek  Thank you for reaching out with your query. Please review the information shared by @tfitzmac and let us know if you have any further queries.
Please note that this  channel (the Azure Docs repository) is only for driving improvements related to the Azure documentation. At this point it appears that there's no further edits or updates needed to the documentation. We will go ahead and close this issue for now, however if you have any further queries please tag us in your reply and will be happy to reopen the thread and continue the conversation. Thank you

I’m sorry, but this answer is still unclear/ambiguous.  My question was whether or not a key vault CAN be referenced in an ARM template.  Was your answer meant to say that a key vault cannot be referenced in an ARM template and can only be referenced in a parameters file?  If that is what you were trying to say then that would answer my question, but it will still seem like a strange design choice for an Infrastructure as Code solution…
Thanks,
Dan
From: Tom FitzMacken @.>
Sent: March 11, 2021 6:28 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Carr, Daniel @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Can I reference a key vault in the ARM template itself, or only in the Parameters file (#72021)
@HoCGeekhttps://github.com/HoCGeek - the key vault is referenced in the parameter file, not the template.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/72021#issuecomment-797118639, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL5CUUFNR6ABHAX7FQ7CE3DTDE7WDANCNFSM4ZAUPR7A.

@HoCGeek - Have you explored the option of using Deployment script?  https://docs.microsoft.com/azure/azure-resource-manager/templates/deployment-script-template

@HoCGeek - sorry, I should have provided more info in my response. In the template, you can't reference a key vault from the parameter declaration. Instead, the reference happens in the parameter file.
However, another option is the one shown in the Reference secrets with dynamic ID section. In that approach, you add a nested template. The reference to the key vault still happens in parameters that are passed to the nested template, but the reference is built within the template.


Feature request: Pomodoro

Thank you for develop this beautiful app.
I found that this app would be awesome with build-in Pomodoro, so that I don't have to switch to another application just for time counting
For the pomodoro page, it could change the color gradient base on the amount of time left (as I imagine :D)

Hi @Luvata
Thanks for your suggestion.
I'm a fan of Pomodoro technique myself but I'm not sure if adding this feature to this app will be a good idea.
I try to keep this app simple. Adding good Pomodoro support where you could track time you spend on tasks would complicate things a lot.
Maybe I'll create a separate Pomodoro app in a future. Alternatively I could try to add basic work and pause timer to this app. I'll think about it.

FYI there is already a separate pomodoro app in snap store which has rather good ux https://snapcraft.io/productivity-timer

@madisCW thanks for the link. The app looks very advanced. I see there's a newer version: https://snapcraft.io/pomatez
Source code: https://github.com/roldanjr/pomatez


Fix tiny typo? terminius

There may be a tiny mis typo 'terminius' instead of 'terminus' in draft-inadarei-api-health-check-02.html#status.
ref: https://github.com/godaddy/terminus
ref: https://tools.ietf.org/id/draft-inadarei-api-health-check-02.html#status

Fixed. Thank you


Improving the search facility in map for play version

Fixes https://github.com/fossasia/open-event-android/issues/1637

Improving the search UX by providing the user facility to select the location instead of typing and clearing up the views earlier present on the map fragment.
Putting up the search button it toolbar.

@heysadboy Please provide screenshots

@iamareebjamal These changes are for Google Play variant only, for which I have attached screenshots in the issue. Clicking on search button on toolbar goes like this,

@heysadboy Yeah sorry. Forgot to see the Play variant changes
Also mention what you have changed in OSMapFragment as well please

@iamareebjamal It was a stray button in toolbar to share map, when I removed that from the menu_map.xml to add search option in play version I had to remove that from OSMapFragment to stop the droid version from crashing. I haven't modified any functioning for droid versionother than that.

OK. But now, please create an issue for adding a share button for location sharing and take a look at the suggestion for autocompletetextview

@iamareebjamal Creating issue for that here https://github.com/fossasia/open-event-android/issues/1659. I considered that initially but I didn't use it because a user may not know about all the locations' textual info. like spelling etc. Selecting from a list was a better option as unlike the name of locations displayed in other fragments, no info. is displayed here.

@the-dagger @mariobehling @mananwason Please suggest

I agree  that the user might not know all the locations out there. But on the other hand, if there are a large number of locations, this type of list will make it tough for the user to navigate through @heysadboy
I would suggest to incorporate both. The list will appear when the user has typed nothing and then the search will come into play as soon as user starts typing.

@mahikaw That's a great suggestion. I think that would be the best of both options.

@iamareebjamal Making the required changes, I am using AutoCompleteTextView now.

@heysadboy Please remove Mahika's commit from your PR

@iamareebjamal I tried removing but ended up removing all the commits accidentaly :( , I am really very sorry about this. Please find new one here https://github.com/fossasia/open-event-android/pull/1668


Prepare for 0.8.5

Mainly cause I want @justMaku's work out there asap.

          1 Warning

:warning:
Tests were not updated

  Generated by :no_entry_sign: danger

👍


Stop counting up after time up

Hi there, is it possible to remove some code from the JS to stop the timer counting up after the time has finished? Many thanks in advance!

Hi there,
Thanks for your fast reply. Yes that would definitely also suffice.
Many thanks
On 3/11/2018, at 7:22 PM, Santhosh Raju <notifications<EMAIL_ADDRESS>wrote:
Hello jaysonknz
I have not looked into the code for quite sometime now.
Would an option / checkbox to stop it from counting up also suffice?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/fraggerfox/countdown-timer/issues/1#issuecomment-435564272, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AqpfqCwLGxlKCJFxpK-8rH7v6Lj2vU2_ks5urTYggaJpZM4YMqNO.

I have added a new branch called "allow-overtime-checkbox" which has a checkbox (if unchecked) that helps stop the timer once it hits zero.
The checkbox could use a bit of CSS so that the theme matches the rest of the UI, but I am not proficient enough to make this change accurately.
Let me know how this works out for you.


(How) should we handle the difference between dataset and NLDI NHDPlus versions?

NLDI will need a way to handle the situation where a dataset is provided to the crawler which contains reachcode and measure information from a vintage of NHDPlus that does NOT match the vintage loaded in NLDI.

My feeling on this is that we shouldn't worry about it in the context of the NLDI. At some stage a stand alone service, which may be a resource for the NLDI, should be created that can migrate reachcode/measures from one dataset to another, but that shouldn't be the job of the NLDI its self.
That said, I would see some value in having the NHDPlus V1 - V2 cross walk in the system to support atleast those two datasets. Are there other major versions that would make some sense to support?

Closing in favor of future illustrations of this issue.


Getting Issue In The Function Return Type

Larastan Version: 2.1
8-level used:

Description
I'm Getting the issue of return type getting (void and self) but it returns the only self.
Code

Larastan Error

Reference: https://github.com/laravel/framework/blob/6fb604f43a5f2dbce928c704532fde291f313416/src/Illuminate/Conditionable/Traits/Conditionable.php#L13-L19

We just need to change the return type to (TWhenReturnType is void ? $this : TWhenReturnType) in our stubs. If anyone wants to send PR.

@canvural on which stub we need to add this?

Next version of PHPStan will be able to read stubs from traits, thanks to this. So this will be easy to implement again!

Can Vural is our hero 🦸🏻♂


[BUG] When the tags are used together, an error is reported

https://github.com/alibaba/spring-cloud-alibaba/actions/runs/8826855559
When I adjusted the command order, it is work.
assign @yuluo-yx
/kind enhancement
/milestone Spring Cloud Alibaba AI
/area ai

->

assign @yuluo-yx
/area ai
/kind enhancement
/milestone Spring Cloud Alibaba AI

->

assign @yuluo-yx
/area ai
/milestone Spring Cloud Alibaba AI
/kind enhancement

You can refer to the actions that fail to execute, I found that they only take effect when they are located in the last line of the comment.


[tools,vcs] Make flops use the sampled value of data to avoid races

The "-deraceclockdata" flag changes the simulation model to always use sampled data values in flops.

Which tests failed on it? Is it ok to use the flag also for gate-level simulation?

It may be useful for gate level with zero-delay, but I doubt it would be needed with SDF timing. This was exposed with a new pwrmgr block level test, but it could have been failing undetected all along.

This is interesting, what is default behavior of vcs without this flag?


Update to Gradle 6.5

Additionally enabled new Gradle dependency verification mechanism: https://docs.gradle.org/current/userguide/dependency_verification.html
And some Gradle properties to speed-up local builds.

nice! Thank you


Add some security headers (now that we are e2ee)

https://zeit.co/docs/configuration#project/headers
we just have to update the now.json file.

https://securityheaders.com/?q=https%3A%2F%2Fexcalidraw.com%2F&followRedirects=on


Webpack segmentation faults for newer versions of node-sass

I've been getting segmentation faults from Webpack for a project I work on. From what I have read, the cause of these segfaults is due to the version of node-sass being beyond version 3.4.2. By downgrading or pinning to 3.4.2, people have mitigated the segfaulting from reoccurring.
In the case of the developer who downgraded from 3.5.2 to 3.4.2, there are a small number of changes that were made to node-sass between these versions. It might be easier to pinpoint the offending change, though I'm not familiar enough with Webpack's internals to pinpoint what changes could be causing these segfaults.
I am posting this here because the Webpack team has asked that I report it here instead.

Without a repeatable reproduction there isn't much we can do. There may have only been a few changes to the node-sass JS however there were many changes to LibSass C++ which the majority of this project's code.

You've might have non-standard Sass and are being affected by the issues @xzyfer outlined in #1474

The other thing in play here is sass-loader which uses the importer API

We've set up segfault-handler so we will be able to hopefully figure out the root cause.  In the initial run of segfault-handler, we noticed issues with the node garbage collector, but I don't know what that says about the issue here.

We also need more information: which OS is this, which node engine, and most important: the platform. Also getting a full log from processing may give us some hints. We are currently collecting information for a similar case with grunt: https://github.com/saper/sass_issue_1672 is a complete bug show case and #1672 contains some useful logs.
Can you supply us with the information similar to bug #1672 ?

Operating system: OS X El Capitan 10.11.6 (15G31)
Node engine (assuming you meant version?): 4.5.0
I'm not sure what you mean by "platform". If you mean architecture, I'm on x86_64.
PID 84650 received SIGSEGV for address: 0xb
0   segfault-handler.node               0x00000001015f1fe8 _ZL16segfault_handleriP9__siginfoPv + 280
1   libsystem_platform.dylib            0x00007fff8a45352a _sigtramp + 26
2   ???                                 0x00000000fffffe31 0x0 +<PHONE_NUMBER>
3   node                                0x00000001002cc070 _ZN2v88internal20MarkCompactCollector17EmptyMarkingDequeEv + 724
4   node                                0x00000001002898e5 _ZN2v88internal13GlobalHandles18IterateStrongRootsEPNS0_13ObjectVisitorE + 61
5   node                                0x00000001002aadbd _ZN2v88internal4Heap18IterateStrongRootsEPNS0_13ObjectVisitorENS0_9VisitModeE + 437
6   node                                0x00000001002cb937 _ZN2v88internal20MarkCompactCollector9MarkRootsEPNS0_18RootMarkingVisitorE + 27
7   node                                0x00000001002c6fc2 _ZN2v88internal20MarkCompactCollector15MarkLiveObjectsEv + 204
8   node                                0x00000001002c6ea0 _ZN2v88internal20MarkCompactCollector14CollectGarbageEv + 14
9   node                                0x000000010029fe0f _ZN2v88internal4Heap11MarkCompactEv + 107
10  node                                0x000000010029f161 _ZN2v88internal4Heap24PerformGarbageCollectionENS0_16GarbageCollectorENS_15GCCallbackFlagsE + 549
11  node                                0x000000010029ed05 _ZN2v88internal4Heap14CollectGarbageENS0_16GarbageCollectorEPKcS4_NS_15GCCallbackFlagsE + 419
12  node                                0x000000010029eaff _ZN2v88internal4Heap26CollectAllAvailableGarbageEPKc + 117
13  node                                0x0000000100270756 _ZN2v88internal7Factory19NewRawTwoByteStringEiNS0_13PretenureFlagE + 240
14  node                                0x00000001001702c6 _ZN2v88internal10JsonParserILb0EE18SlowScanJsonStringINS0_16SeqTwoByteStringEtEENS0_6HandleINS0_6StringEEES7_ii + 102
15  node                                0x000000010016d830 _ZN2v88internal10JsonParserILb0EE14ParseJsonValueEv + 114
16  node                                0x000000010016fb62 _ZN2v88internal10JsonParserILb0EE14ParseJsonArrayEv + 518
17  node                                0x000000010016d8e6 _ZN2v88internal10JsonParserILb0EE14ParseJsonValueEv + 296
18  node                                0x000000010016f008 _ZN2v88internal10JsonParserILb0EE15ParseJsonObjectEv + 896
19  node                                0x000000010016d8d9 _ZN2v88internal10JsonParserILb0EE14ParseJsonValueEv + 283
20  node                                0x000000010016d559 _ZN2v88internal10JsonParserILb0EE9ParseJsonEv + 207
21  node                                0x000000010041aaf6 _ZN2v88internal17Runtime_ParseJsonEiPPNS0_6ObjectEPNS0_7IsolateE + 285
22  ???                                 0x0000107cec10963b 0x0 +<PHONE_NUMBER>9131
23  ???                                 0x0000107cec2d4ec0 0x0 +<PHONE_NUMBER>1376
24  ???                                 0x0000107cec109ff7 0x0 +<PHONE_NUMBER>1623
25  ???                                 0x0000107cf11bb5d4 0x0 +<PHONE_NUMBER>4196
26  ???                                 0x0000107cf11ba461 0x0 +<PHONE_NUMBER>9729
27  ???                                 0x0000107cf11b8e4e 0x0 +<PHONE_NUMBER>4078
28  ???                                 0x0000107cf11b86ed 0x0 +<PHONE_NUMBER>2189

Thank you. Looks like it crashes in code the node engine provides to the V8 garbage collector (similar issues). Having said that, we still cannot preclude that it is not node-sass or libsass fault, especially since we mix C++ runtime libraries on MacOS X, which is asking for trouble. As this happens during some JSON parsing by node it is also possible that node-sass is not involved here.
As per @bnoordhuis troubleshooting advice in https://github.com/nodejs/node/issues/7654 can you try running node with --verify-heap? The next step would be to compile node from source by hand with debugging (./configure && make -C out BUILDTYPE=Debug), and trying again with --verify-heap as well.

Also, it is very important to have a possibly small repository to reproduce this problem.

The strangest part about the segfault issues we've been encountering is that they're not easy to reproduce. I was able to successfully do npm run build, but nothing was changed on the codebase.
Unfortunately, I cannot provide a repository which can reproduce this problem as we have written software that cannot be released publicly.

I would also like to note that I installed node4-lts using brew.

Since the exception occurs in the garbage collector it relies on some specific memory allocation pattern and some specific situation where garbage collection may be triggered. It would be interesting to see if the stacktraces are similar between crashes.
Please also try the newest node-sass code released (3.8.0). Also I'd recommend trying the same with node 6.x and see if the newer V8 engine somehow fixed or worked around the problem (even if the core cause is somewhere else). Please  try building this on Linux/FreeBSD and see if you can reproduce this there.
Basically there are the following possibilities to continue troubleshooting this:

somebody by chance discovers a way to reproduce this without using your code
somebody finds the issue (V8/node/node-sass/libsass) independently
you are lucky with finding the cause with --verify-heap and/or debugger
you begin working on stripping your code down to the minimal reproduction case you can release publicly. Very often during the stripping process the issue becomes obvious or at least provides some cues (hey, "A" works, "B" doesn't).
you hire somebody to dig into your proprietary code base

@saper I've found a case where a segmentation fault occurs. I don't know if it's the same as what was causing @zg's problem, but it consistently fails for me.
I believe I've found the minimum possible case. Anything left out of this causes a valid error message instead of a Segmentation fault.
Here's the SCSS:
:not(.something) {
  @extend .something;
  cursor: pointer;
}

The cursor property can be anything but must be there to cause the segmentation fault. I tried updating node-sass like you said and the segmentation fault still happens.
Before I deleted everything, .something was defined, so this isn't happening because that isn't there. Adding a definition for .something to the code above still results in Segmentation fault.
The :not() selector wasn't alone in my original code either. When I was deleting code I found that it doesn't really matter what the selector looks like so long as the .something in the :not() is the same as the argument to @extend.
$ ./node_modules/.bin/node-sass --version
node-sass	3.9.3	(Wrapper)	[JavaScript]
libsass  	3.3.6	(Sass Compiler)	[C/C++]
$ ./node_modules/.bin/node-sass segfault.scss
Segmentation fault

Excellent find, @sunjay!

This is great @sunjay. On my box it looks like the infinite loop that eats up all the memory.

So, the good news is: this has been fixed in the current libsass master code:
m> ./bin/sassc -v
sassc: 3.3.6-11-g077a
libsass: 3.3.6-112-g6de5
sass2scss: 1.0.6
sass: 3.4
m> ./bin/sassc test.scss
:not(.something) {
  cursor: pointer; }

@zg I wonder how can we check if your issue is the same as the one @sunjay posted here

Unfortunately I've since left the company and cannot see if this was the issue, though I have forwarded the comment by @sunjay to someone I know personally and he might look into it.

I understand - I'll close the issue for now - if anyone comes up with a way to reproduce it, we can always reopen it. Thank you.

@sunjay nope, if you use the binary file downloaded via npm install it includes a specific libsass version bundled with it. There is [https://github.com/sass/node-sass/pull/763 a way to build the binding with your own libsass], but you are on your own then.... We need a new libsass release (coming soon) and the next node-sass will usually follow shortly.


Adding ssh port 10443 for some of missing groups

can you explain the reason behind this in the pull request description? Just for posterity.

Telus infra net did not allow user to connect to server from port 22
So, Royston used port 443 to work around this problem.
However, nowadays, some project uses port 443 for SSL so this has to be addressed to port 10443

https://tree.taiga.io/project/jscott-skynet-3/us/3049?milestone=39730


chore(build): fix build issues with typescript 2.1

Short description of what this resolves:
The code base was not yet ready for TypeScript 2.1, spitting out some type errors when running npm run build.
This patch fixes some type annotations to be compatible with both TypeScript 2.0 and 2.1.
This is one step in fixing #197 (and #649 where support for TypeScript 2.1 seems to be a pre-condition).

Rebased and fixed conflict.

@danbucholtz this PR does not change the version of the typescript dependency, just ensures it properly compiles with both 2.0 and 2.1:-)

Cool, I will merge at some point in the next day or so.
Thanks,
Dan

An open question is why we have a dependency on typescript while also specifying a peerDependency on it.
I think we should change it from dependency to devDependency.
The current setup leads to some inconsistency on which TSC is used: when using the dev environment, the compiler in the actual app (our peer dependency) is used; when using prod (--prod), the compiler of the app-scripts (our dependency) is used.
When specifying typescript as a devDependency we should be using the same compiler in both environments. So it's up to the projects if they want to take a risk and use some yet unsupported versions:-) (we are using TS 2.1.5 with success already)
I would not propose this due to some risks (npm not properly enforcing the peerDependency installation), but the ionic start CLI command generates a proper package.json including a dependency on a supported typescript package. This makes me think that the cases you support (Ionic proper:-) should be fine while giving other some more flexibility and being more consistent regarding environments.

We have Typescript as a peerDependency so it's version is managed by the Ionic project's package.json, and then also as a devDependency for local development.
https://github.com/driftyco/ionic-app-scripts/blob/master/package.json#L98
Thanks,
Dan

@danbucholtz Damn! Of course you do! My bad:-)
I was using a npm link version... All good:-) Thanks!

@huerlisi,
Thanks again. These are really good PRs! We appreciate it! 🐱
Thanks,
Dan


LocalStorage filling up with oidc. entries

I don't know if this is a bug or i have configured something wrong somewhere.
I can see that localstorage is filling up with entries like this
Key: oidc.
Value: {"id":"","created":12345678,"nonce":"12345678","authority":"https://theauthserver.com","client_id":"clientuniqueid"}
and i cannot figure out why? They seem to never be deleted.
What are these used for?
The oidc.user: token i store in SessionStorage so i thought that is that storage that would be used for all related items?

This is the state for the protocol flow and it's not getting cleaned up because the protocol workflow is not getting completed. I guess you're doing a lot of testing? There's an API to clean them up automatically: https://github.com/IdentityModel/oidc-client-js/blob/dev/sample/public/user-manager-sample.js#L82

Yes I am doing a lot of testing, replacing oidc-manager with this one. :)
But i wonder if i am doing something else wrong too, as even for what i would expect to be the normal flow of Signing-in, navigate around for a bit and then Sign-out. These entries does not get cleaned up.
I am working in an Angular 1.4.x app so i could have configured something wrong somewhere. I have not been able to find any examples for full implicit flow for Angular 1.4.x.
Do you know of any examples?

I'd clear them all out and then complete one successful test to login and see if the localStorage entry remains. If so, then you're right -- something is not cleaning it up. You'd debug into this on the xxxCallback page.

Thanks @brockallen seems like something is wrong in my Callback page, i will debug and see what i find.

Hi @robbaman were you able to find what the issue was? I am using angular 1.5 and having exact issue.
When I log out they the oidc. are not cleared and on login more entries are added to the local storage.

@john1452 in my logout script i run the clearStaleState() function, which removes the old entries.

@Robban1980 Thanks a lot! it works


About running the project on a Windows device

Hello, I’ve read your paper and tried to reappear this project on my device, since the PolyFormer is attractive to me. However, I met some problems during the first step -- “Installation”.
I made the Installation successfully on a Linux device several days ago. But unfortunately, that device was out of storage for preparing pre-training and fine-tuning data because it was shared by several of my companions.
As the memory was filled by their projects, I decided to use my Windows (Windows 10) device to reappear this project. Compared to that Linux device, my Windows device has very ample space to store pre-training and fine-tuning data.
Therefore, before trying to run PolyFormer on my Windows device, I need to ask you for some suggestions:

What improvements do I need during the Installation session (especially in “requirements.txt”) on my Windows device? If I follow it directly to build the 'polyformer' virtual environment, there is a chance that I will make an error in the "pycocotools build wheels" session even though I installed the latest Visual C++ Build Tools.
After the installation session, what do I need to be aware of during the subsequent part of the project?

Thank you for your reading. I will be appreciated for receiving your reply soon.

There's a good news that the Installation was successful on my Windows device by just running an extra command conda install -c conda-forge pycocotools.  In this way, the error in the "pycocotools build wheels" was not occured.
Hence, my problem is simplified. It means that the 2nd suggestion in my last comment is currently needed.


introduces configurator

Implements the ability to configure the SDK per specs.
Resolves #10 when merged.

One general comment about logging: currently we are not logging to file by default, which the agent does, and which can be helpful for debugging (in fairness, usually debug logs need to be set up to collect the really useful debugging information). Do we want to change the default device on the logger?

One general comment about logging: currently we are not logging to file by default, which the agent does, and which can be helpful for debugging (in fairness, usually debug logs need to be set up to collect the really useful debugging information). Do we want to change the default device, at least on the Logger we supply by default?

We talked about this as a team and it seems that default logging to STDOUT until a customized logger is supplied is a widely accepted pattern.


git clone fails with gnutls_handshake() failed error in the push function

git clone https://github.com/waveform80/pistreaming.git  fails as noted on my new RPi Zero W
A different git clone done moments before worked fine:
git clone https://github.com/silvanmelchior/RPi_Cam_Web_Interface.git
Any ideas on what's wrong and how to fix?

worked using sudo git clone https://github.com/waveform80/pistreaming.git
suggest adding "sudo" to the installation instructions.


[DBZ-1690] Update Mongo java driver to version 3.12.0

The failing test seems to be related to Mysql and I didn't modify stuff related to it.

Nice, thanks a lot, @oscerd!


On terminal startup, gives Fish syntax error message relating to the use of && rather than ; and in fish, plus more relating to the use of variable setting. Essentially it seems that thefuck --alias gives out a result that only runs in bash.

 Maybe thefuck --alias is outputting the bash function rather than the fish function..?

I'm fairly sure that's the issue; I believe that's what the PR fixes.

Fixed in 6290560


Adjust order of backlog items along order of process type

current: Depending on the process chosen to create your project—Agile, Scrum, or CMMI— the items in your backlog may be called product backlog items (PBIs), user stories, or requirements.
suggestion for improvement: Depending on the process chosen to create your project—Agile, Scrum, or CMMI— the items in your backlog may be called user stories, product backlog items (PBIs), or requirements.

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

ID: 58aacca7-05a2-e8dd-6a6f-3025d734ef20
Version Independent ID: 3eea19c1-8bda-6b60-e77d-8c0e82c3f096
Content: Create & manage bugs using Agile tools - VSTS & TFS
Content Source: docs/boards/backlogs/manage-bugs.md
Product: devops
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@mapfel - Thank you for the feedback. I'm updating several articles to correct the order of items.


nz-cascader nzClear not working or implemented

Reproduction link
https://github.com/NG-ZORRO/ng-zorro-antd/blob/ab63d7e25aabab8c2fbb2c63294b6b7c08c30480/components/cascader/cascader.component.ts#L252
Steps to reproduce
Try to consume the EventEmitter for nz-cascader called nzClear.
What is expected?
It should emit to the consumer of the component using the nzClear event emitter somewhere, probably in the clearSelection method:
cascader.component.ts line 466
What is actually happening?
It doesn't emit anything.

Environment
Info

ng-zorro-antd
11.4.2

Browser
Chrome (Doesn't matter)

I searched through the cascader service and found a method called prepareEmitValue, but nzClear is never emitted anywhere as far as I'm able to see.

PR is welcomed!

@wendellhu95 Okay cool, I'll make the change now and create the PR. Do I create the PR to "master" branch? What is your ALM model for a fix like this? Do you have a QAS channel?

Nevermind, it seems like you're using trunking with rebase. I'll create a branch and PR for the fix now.

The "npm run test" command is failing from the root package.json file.
I'll try again later when I have more time.


[Android] Collection was modified; enumeration operation may not execute.

Hi,
I'm using Mapsui with Xamarin.Forms. When I'm dragging and zooming in/out the map, I often get this exception. And I'm not sure where to catch it.
Mapsui version is 1.4.2
This is StackTrace I get:
07-22 14:33:27.716 I/MonoDroid(11986): System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
07-22 14:33:27.716 I/MonoDroid(11986):   at System.ThrowHelper.ThrowInvalidOperationException (System.ExceptionResource resource) [0x0000b] in <f32579baafc1404fa37ba3ec1abdc0bd>:0
07-22 14:33:27.716 I/MonoDroid(11986):   at System.Collections.Generic.List`1+Enumerator[T].MoveNextRare () [0x00013] in <f32579baafc1404fa37ba3ec1abdc0bd>:0
07-22 14:33:27.716 I/MonoDroid(11986):   at System.Collections.Generic.List`1+Enumerator[T].MoveNext () [0x0004a] in <f32579baafc1404fa37ba3ec1abdc0bd>:0
07-22 14:33:27.716 I/MonoDroid(11986):   at Mapsui.Map.get_Envelope () [0x0003e] in <bd6c770b2d1b4c27bce3851e2242b36f>:0
07-22 14:33:27.716 I/MonoDroid(11986):   at Mapsui.UI.Android.MapControl.MapView_Touch (System.Object sender, Android.Views.View+TouchEventArgs args) [0x0021b] in <c13b5b47cf5c441089ad69c9299ca90f>:0
07-22 14:33:27.716 I/MonoDroid(11986):   at Android.Views.View+IOnTouchListenerImplementor.OnTouch (Android.Views.View v, Android.Views.MotionEvent e) [0x00014] in <263adecfa58f4c449f1ff56156d886fd>:0
07-22 14:33:27.716 I/MonoDroid(11986):   at Android.Views.View+IOnTouchListenerInvoker.n_OnTouch_Landroid_view_View_Landroid_view_MotionEvent_ (System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_v, System.IntPtr native_e) [0x00017] in <263adecfa58f4c449f1ff56156d886fd>:0
07-22 14:33:27.716 I/MonoDroid(11986):   at (wrapper dynamic-method) System.Object.b879ca1a-12ab-4dd9-b8d8-e8a7923d0c07(intptr,intptr,intptr,intptr)

What kind of layers do you use?

For map layer I'm using OpenStreetMap layer from Mapsui.Utilities.
Besides that I also use layer with points I add to the map and it's infolayer. There are more then 10k points total. I show them only after specific Resolution. If resolution is lower than the one specified, I remove that layer.
I've also added a lock before the code where I add and remove the layer.

I closed it by accident. Sorry for that.

What kind of layer do you use as point layer?

I create Features to which I add Feature with Geometry as a point, with  Lebel and some extra parameters added as KeyValues. Then I add Features to the Layer as a DataSource with MemoryProvider. I also add specific Style to the Layer. I add this layer to Layers property of my map and InfoLayer property.

So you type of layer is a regular 'Layer'. What type is your DataSource?

That is correct. DataSource is of type MemoryProvider, which is constructed with type Feature.

I know there is an issue the with MemoryProvider.Clear. Do you call it explicitly at some point?

If resolution is lower than the one specified, I remove that layer.
How do you remove it?

No.
I tried to reproduce the issue. The way I did it was swiping around like crazy, zooming in and out. Also zooming over the threshold where I remove the layer. And then zoomin againg, to display it again. And at some point it crashes with the same exception. Do you have any suggestion how I could catch that?

How do you remove the layer?

Here is the snippet
var locationLayer = mapControl.NativeMap.Layers.FirstOrDefault(l => l.Name == "MyLayerName");                 if (locationLayer != null)                 {                     if (locationLayer != null)                         mapControl.NativeMap.Layers.Remove(locationLayer);                     mapControl.NativeMap.ViewChanged(true);                 }

There should be catch in the OnTouch of the Android MapControl to catch this. I don't think that you can catch it.
Can you reproduce the problem if you do not remove the layer?

No, I haven't been able to reproduce that. I am quite sure that the problem is there. That's why I added lock around add and remove statements. So they can't be triggered one over another.

I tried that. It gets stuck at:
mapControl.NativeMap.ViewChanged(true);

which I call right after
layer.Enabled = false;

This was also a reason I started working with add remove.

@MaticDiba btw, You can use the MemoryProvider2 without upgrading to 1.4.5. You can just copy the file to your project.
https://raw.githubusercontent.com/Mapsui/Mapsui/1.4/Mapsui/Providers/MemoryProvider2.cs

@MaticDiba In 1.4.7 you can just use MemoryProvider, without the 2.

@MaticDiba Very interested to see if this fixes your problem.

Hi Paul,
sorry for my late replay. I'm away until 5th of August. I will test it when I come back.

@MaticDiba Is this fixed now?

Hi, Paul. Yes, this worked. Sorry for late replay.

@MaticDiba Thanks for wrapping this up. These kind of errors are high priority.

I closing this until there is a way to reproduce this.


Adding custom provision provider

Submitting this as a conversation starter. The goal is to enable people to not use any of the built in providers but instead allow them to execute the provisioning tools they want to use. This basically makes a dummy "custom" provider that no-ops the main steps but pre and post hook commands still run. This enables people to do what they need at the right stages and not be blocked because they don't want to use bicep or terraform.
@weikanglim @ellismg @jongio @rajeshkamal5050

This is interesting.  I wonder if we really need a custom provider for enabling hooks.
I think folks can use pre-deploy or post-package instead (from a project w/o infra).
I wonder if it would make more sense to have an ephemeral or void provider  for this.  IMO, custom sounds like the customer can define how it would behave, but it reality, this is a no-op provider

I was also wondering if we should just let someone launch a process here.
I think what you described mostly does what I was looking for but I'm not sure about the contract of emitting a empty arm template. I literally don't want the deployment to happen via the ARM call in this case.

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

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

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

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

MacOS -

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

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

MSI

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

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

Documentation

learn.microsoft.com documentation

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

See also

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

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

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

See also

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

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

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

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

See also

azd auth: Authenticate with Azure.
Back to top

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

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

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

See also

azd auth: Authenticate with Azure.
Back to top

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

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

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

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

See also

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

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

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

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

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

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

See also

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

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

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

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

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

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

See also

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

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

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

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

See also

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

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

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

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

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

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

See also

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

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

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

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

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

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

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

See also

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

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

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

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

Examples
azd config unset defaults.location

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

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

See also

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

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

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

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

See also

Back to top

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

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

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

See also

Back to top

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

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

See also

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

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

Options
  -b, --branch string         The template branch to initialize from. Must be used with a template argument (--template or -t).
      --docs                  Opens the documentation for azd init in your web browser.
  -e, --environment string    The name of the environment to use.
  -h, --help                  Gets help for init.
  -l, --location string       Azure location for the new environment
  -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                  Deploys all services that are listed in azure.yaml
      --docs                 Opens the documentation for azd package in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for package.
      --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.
      --preview              Preview changes to Azure resources.

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

See also

Back to top

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

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

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

See also

Back to top

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

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

See also

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

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

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

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

See also

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

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

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

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

See also

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

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

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

See also

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

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

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

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

See also

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

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

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

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

See also

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

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

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

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

See also

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

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

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

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

See also

Back to top

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

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

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

See also

Back to top

What is azd's role in provisioning, now that provisioning itself is delegated away? Would running <my provision tool> achieve the same outcome? Is azd a facade?

Its always been intended to be partially a facade in the sense that we want to enable people to do whatever they need to do while still providing a consistent interface for tools above it. We also intend to make provisioning in different ways better and better by investing in concrete implementations of them like bicep and TF where the tool can provide more insight in places where there is first class integration. The key to me is that the first class integration can't get in the way of people doing something else as part of the flow.

As a developer, I would like to be able to:

Bypass any azd command
Provide a custom implementation for any azd command

Bypass:

azd augments azure.yaml schema to allow the user to signal the command is bypassed

Custom:

azd allows the user to define a hook for commands:

for example:
hooks:
  - provision:

If the hook is defined then that is run instead of the azd command.
This type of design would allow us to implement this behavior for any command, not just provision.
Aside: A less desirable UX (IMO) would be, instruct the user to have a hook/command no-op script if they want to bypass a command.

hooks:
  - provision:

If the hook is defined then that is run instead of the azd command.
This type of design would allow us to implement this behavior for any command, not just provision.

Yes! This is inline with what I was thinking as well.  Today the hooks only expose pre and post.  If a user wants to take control over any project/service command they should simply be able to set that in the hooks configuration and take control of that process.
This same concept can then be easily applied to any other commands we want to enable this level of flexibility.
hooks:
  # Run this script in place of default azd implementation
  provision:
    run: ./scripts/provision.sh

And in the case of a real noop use case our default provision provider (bicep) maybe shouldn't error if it doesn't find what it needs.  If a main.bicep or other required files doesn't exist azd could respond with something like:
SKIPPED - No IaC Templates found
With a warning message to add IaC templates into the infra folder and try again.  Returning a noop here would still allow an azd up experience to work without having to create a custom provider or hook noop implementation.

In my mind, this is really very similar to what we had planned for provision extensibility in some ways. Would also be interesting to think about how something like this fit in with other plans we had in this space (e.g. Pulumi). In my mind, both require us "delegating" provisioning to something else, getting outputs and then using them to deploy etc.

Agreed. I think in some cases we would delegate and expect a contract with the component. In these cases, we would know more and could have a more feature rich experience.
So are we concluding that we should do what Jon suggested? Allow a hook for all the mainline commands that lets you run a command instead of the standard action?
For the skip case. what do people think? Should it just be an empty hook for provision?

I think extending hooks to surface core azd commands seems like a really nice UX. I also like @wbreza's suggestion for a noop case. The main thing I want to make sure of is that no additional overhead/YAML is needed in azure.yaml if you just want to do the "vanilla" azd thing and default to our command implementations/definitions.  The UX should also remain unchanged in that case.
Extra YAML should only be required if you want to customize/override the experience.

Yup, that makes sense. I'm a bit sad that bicep is the default and that the "easier" solutions were going to implement in the future will require more yaml :(

I think that with some of the abstraction work we are thinking about the Bicep bits could be hidden from a developer on Day 0, FWIW.

I think that with some of the abstraction work we are thinking about the Bicep bits could be hidden from a developer on Day 0, FWIW.

Yeah, I think we're likely going to have to make the "default" provision provider more than just Bicep to keep the yaml clean for the simple case.

In fact, I'm wondering if we should start forcing people to put "bicep" in their azure.yaml right away. Start with a deprecation warning and then move it to a requirement at some point?

I think that's probably going to happen as we start to identify the exact UX we want for abstraction.

So more questions here:
How does someone specify "noop"?
Is it by overriding with the hook and specifying nothing?
Should they set the string to "noop"?
Should they be able to do it without hooks and specify noop as the infra type?
If someone specifies "noop" however we decide that is done:
Should the pre and post hooks for that command still run?

Here's my proposal.
See the current behavior and how I would change it to support no-op in an easy way (and backwards compatible):

azure.yaml - infra field
Current behavior
Change to:

Empty -
Expectation:         folder: infra     file: infra/main.bicep             Use bicep provider    ** Fail if    expectations are missing
Smart detection:       Use folder infra if present.    Do no-op if infra folder not present. Hooks        for pre-provision and post-provision can still be set and are dispatched.                 When infra   folder is present:       Look for either (using        priority order):         main.bicep     terraform     cdk / other        Fallback to no-op if infra folder is empty or nothing        known was found.                  ** azd never fails. It always fall   back to no-op as worst case.

Infra.module =      Infra.path =      Infra.provider =
Expectation:         folder:      file: infra/.[bicep/tf]     Provider:              Use      ** Fail if    expectations are missing
No smart detection.       Azd follows the explicit         user-definitions.     Use infra.provider         = null to use         the no-op provider.             ** azd fails if something is missing

Combination of:       Infra.module = [empty | module]   Infra.path = [empty | path]   Infra.provider = [empty | provider]
Use a default for each empty field
Do smart-detection when only  is        set:         try to detect the provider         and module or fall-back to no-op.        Do explicit-expectation when  and/or         are set.         Fail if missing config.

I think that the behaviour of an empty infra field in azure.yaml may need to change as we think about abstraction. Empty in a world where we allow a user to potentially define only services (with hosts, languages, paths; manually or via the simplified init) could in theory leverage smart defaults + Bicep modules "generated" out into tmp/ for provision. This would result in no infra/ at all in the project root, not visible to the user.
Not saying that's the decided solution but arguably an option since we are also already generating IaC in the new simplified init flow and persisting it to the project.

In that case, would they set an alternate location for the infra folder where all the generated stuff will be?

Not sure if you're asking Victor or me :)
I'll elaborate anyway...
My initial thinking is for a Day 0 experience, where someone is coming off of the simplified init flow, there is no infra/ folder that the user has to think about. They just have to think about azure.yaml and azd handles the rest.
I'm imagining that if a user wanted to expand/eject out of the abstracted, day 0 experience because they now want to tweak configurations and want to take ownership of the IaC bits, they could run something like azd infra synth  to spit out the Bicep files we'd been using "under the hood" and land them in an experience very similar to what it looks like today (but there's also composability in the picture so management of resources gets a bit easier). The directory we choose to expand the IaC out into could be infra/ by default but overridable via a prompt under that command.
IMO, this overriding of provision provider/no-op scenario is only really applicable to folks who have "expanded"/"ejected". In that case, I think we'd probably want something like @vhvb1989 has in the top-right box. I think that addresses both abstracted and non-abstracted views of IaC.

@savannahostrowski

they could run something like azd infra synth to spit out the Bicep files we'd been using "under the hood"

If azd spits out the IaC to /infra since day-0, we don't need to have this extra azd infra synth.
Also, azd would use either ARM/bicep under the hood anyway.  I don't see why to keep it hidden.
Having an azd-only abstraction for IaC can't be scale-up to all Azure w/o a high cost.  What would it be its limits?
Is it a few popular services for getting-started samples ?

The piece to consider here is that these IaC files are noise and overwhelming to folks that don't understand Azure/Bicep/IaC. They just want to go from A->B.

I agree that we want to move in a direction where, if the info for the infra is provided in some other form and is generated, those become intermediate build artifacts and not put into the source tree.

I'm going to close this for now - the pressing issues for this specific feature have been addressed in other ways.  We're still thinking about extensibility in this area, but there's no clear step forward for this PR right now.  Happy to have the discussion continue here, however.


Add options to randomize delay between typestroke

Description
Addressing todo: Add human-like option that varies character delays slightly
And the great feedback here:
https://github.com/straversi/Typer.js/pull/11#issuecomment-480467293
I added options:

data-delay-variance (default value is 0)

Example Usage / Demo

https://jsfiddle.net/Lvc1pqno/
Modified docs preview:
https://raw.githack.com/rizdaprasetya/Typer.js/patch-2/docs/index.html

Awesome! Thanks so much for addressing the feedback. Looks great.


Fails to install 2.2.2 or 2.2.3 on os x 10.10.4

I have rbenv and ruby-build installed and up to date with brew.
I get
...
installing extension headers: /Users/mollerhoj/.rbenv/versions/2.2.2/include/ruby-2.2.0/ruby
installing default gems:      /Users/mollerhoj/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0 (build_info, cache, doc, extensions, gems, specifications)
                              bigdecimal 1.2.6
                              io-console 0.4.3
                              json 1.8.1
                              psych 2.0.8
                              rake 10.4.2
                              rdoc 4.2.0
skip installing bundle gems because of lacking zlib
installing rdoc:              /Users/mollerhoj/.rbenv/versions/2.2.2/share/ri/2.2.0/system
installing capi-docs:         /Users/mollerhoj/.rbenv/versions/2.2.2/share/doc/ruby
The Ruby zlib extension was not compiled.
ERROR: Ruby install aborted due to missing extensions
Configure options used:
  --prefix=/Users/mollerhoj/.rbenv/versions/2.2.2
  --with-openssl-dir=/usr/local/opt/openssl
  --with-readline-dir=/usr/local/opt/readline
  CC=clang
  CFLAGS= -O3 -Wno-error=shorten-64-to-32
  LDFLAGS=-L/Users/mollerhoj/.rbenv/versions/2.2.2/lib
  CPPFLAGS=-I/Users/mollerhoj/.rbenv/versions/2.2.2/include

Can you try the solution hinted in https://github.com/sstephenson/ruby-build/issues/780#issuecomment-118707211? zlib should be present on your system. Please update Xcode and then reinstall Ruby to properly link against zlib. If you have difficulties please comment on the other ticket. Thanks!


nimble/ll: Fix setting anchor point and WFR for sync PDUs

Don't set anchor point in the middle of expected window for first
packet. Now we set anchor to calculated point in time and adjust
WFR with window widenning (and offset if synchronizing).

@haukepetersen   seems like riot port is broken with latest master, could you check this?


Minor typo fixes

Hey, I've fixed some typos, Kindly review it.

Hey, @MarkDaoust has approved the changes but it requires 2 more reviews. @yashk2810 and @wolffg kindly review it.


Replace backticks with $() command substitution

There's no need to mix both.

Thanks - these may almost be the only remaining backticks in the codebase.
Can you verify if any of these can be double-quoted? Testing these is very difficult, which is why I haven't changed them thus far.

@ljharb I usually check stuff with http://www.shellcheck.net/ For this file, it also shows other small issues, that might require a fix. As far as I can see most of the changes I added are variable assignments, which do not require double quotes.

I also use shellcheck; many of the remaining warnings are false positives. Thanks for confirming about the quotes.
I'll test this manually before merging.

Seems this will need a rebase onto the latest master

Rebased.

Thanks!


some wrong

Description
What steps will reproduce the problem?

What is the expected output? What do you see instead?
Please provide any additional information below
File "C:\ProgramData\Anaconda3\lib\site-packages\spyder\plugins\ipythonconsole.py", line 1273, in close_client
self.create_new_client()
File "C:\ProgramData\Anaconda3\lib\site-packages\spyder\plugins\ipythonconsole.py", line 991, in create_new_client
self.connect_client_to_kernel(client)
File "C:\ProgramData\Anaconda3\lib\site-packages\spyder\plugins\ipythonconsole.py", line 1027, in connect_client_to_kernel
kc.start_channels(shell=True, iopub=True)
File "C:\ProgramData\Anaconda3\lib\site-packages\qtconsole\kernel_mixins.py", line 43, in start_channels
super(QtKernelClientMixin, self).start_channels(*args, **kw)
File "C:\ProgramData\Anaconda3\lib\site-packages\jupyter_client\threaded.py", line 209, in start_channels
self.shell_channel._inspect = self._check_kernel_info_reply
File "C:\ProgramData\Anaconda3\lib\site-packages\jupyter_client\client.py", line 143, in shell_channel
socket, self.session, self.ioloop
File "C:\ProgramData\Anaconda3\lib\site-packages\jupyter_client\threaded.py", line 202, in ioloop
self._ioloop = ioloop.IOLoop()
File "C:\ProgramData\Anaconda3\lib\site-packages\tornado\util.py", line 312, in new
instance.initialize(*args, **init_kwargs)
File "C:\ProgramData\A

This is fixed in our latest version. Please update by opening the Anaconda Prompt and running there
conda install spyder=3.3.6


Added PTCycleTest & PmlMaxHeightMixInTest tests

I've added some TODO in code.
Do you want me to correct it ?

TODOs are fine, we'll probably need lots of them :) Thanks for adding tests!!


Bump node azure-servicefabric version to 2.0.1

This should resolve the issue where we generated an incorrect GitHub link.

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-go

Automation for azure-sdk-for-python

Automation for azure-sdk-for-java

Automation for azure-sdk-for-node

@autorestci rebuild azure-sdk-for-node

@amarzavery Can you take a look or reassign it someone from the Node SDK team

Sorry for any inconvenience :)

@autorestci regenerate azure-sdk-for-node

Encountered an unknown error
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/urllib3/connectionpool.py", line 600, in urlopen
    chunked=chunked)
  File "/usr/local/lib/python3.6/dist-packages/urllib3/connectionpool.py", line 343, in _make_request
    self._validate_conn(conn)
  File "/usr/local/lib/python3.6/dist-packages/urllib3/connectionpool.py", line 849, in _validate_conn
    conn.connect()
  File "/usr/local/lib/python3.6/dist-packages/urllib3/connection.py", line 356, in connect
    ssl_context=context)
  File "/usr/local/lib/python3.6/dist-packages/urllib3/util/ssl_.py", line 359, in ssl_wrap_socket
    return context.wrap_socket(sock, server_hostname=server_hostname)
  File "/usr/lib/python3.6/ssl.py", line 407, in wrap_socket
    _context=self, _session=session)
  File "/usr/lib/python3.6/ssl.py", line 814, in __init__
    self.do_handshake()
  File "/usr/lib/python3.6/ssl.py", line 1068, in do_handshake
    self._sslobj.do_handshake()
  File "/usr/lib/python3.6/ssl.py", line 689, in do_handshake
    self._sslobj.do_handshake()
OSError: [Errno 0] Error

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/requests/adapters.py", line 445, in send
    timeout=timeout
  File "/usr/local/lib/python3.6/dist-packages/urllib3/connectionpool.py", line 638, in urlopen
    _stacktrace=sys.exc_info()[2])
  File "/usr/local/lib/python3.6/dist-packages/urllib3/util/retry.py", line 367, in increment
    raise six.reraise(type(error), error, _stacktrace)
  File "/usr/local/lib/python3.6/dist-packages/urllib3/packages/six.py", line 685, in reraise
    raise value.with_traceback(tb)
  File "/usr/local/lib/python3.6/dist-packages/urllib3/connectionpool.py", line 600, in urlopen
    chunked=chunked)
  File "/usr/local/lib/python3.6/dist-packages/urllib3/connectionpool.py", line 343, in _make_request
    self._validate_conn(conn)
  File "/usr/local/lib/python3.6/dist-packages/urllib3/connectionpool.py", line 849, in _validate_conn
    conn.connect()
  File "/usr/local/lib/python3.6/dist-packages/urllib3/connection.py", line 356, in connect
    ssl_context=context)
  File "/usr/local/lib/python3.6/dist-packages/urllib3/util/ssl_.py", line 359, in ssl_wrap_socket
    return context.wrap_socket(sock, server_hostname=server_hostname)
  File "/usr/lib/python3.6/ssl.py", line 407, in wrap_socket
    _context=self, _session=session)
  File "/usr/lib/python3.6/ssl.py", line 814, in __init__
    self.do_handshake()
  File "/usr/lib/python3.6/ssl.py", line 1068, in do_handshake
    self._sslobj.do_handshake()
  File "/usr/lib/python3.6/ssl.py", line 689, in do_handshake
    self._sslobj.do_handshake()
urllib3.exceptions.ProtocolError: ('Connection aborted.', OSError(0, 'Error'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/azure_devtools/ci_tools/github_tools.py", line 33, in exception_to_github
    yield context
  File "/usr/local/lib/python3.6/dist-packages/azure_devtools/ci_tools/bot_framework.py", line 105, in manage_comment
    response = getattr(self.handler, orderstr)(webhook_data.issue, *split_text)
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/restapi/restbot.py", line 54, in regenerate
    return self.rebuild(issue, repotag)
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/restapi/restbot.py", line 36, in rebuild
    self.sdk_default_base
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/restapi/github_handler.py", line 151, in rest_pr_management
    sdk_tag=sdk_tag
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/SwaggerToSdkNewCLI.py", line 254, in generate_sdk_from_git_object
    with manage_git_folder(gh_token, Path(temp_dir) / Path("rest"), branched_rest_api_id, pr_number=pr_number) as restapi_git_folder, \
  File "/usr/lib/python3.6/contextlib.py", line 81, in __enter__
    return next(self.gen)
  File "/usr/local/lib/python3.6/dist-packages/azure_devtools/ci_tools/github_tools.py", line 272, in manage_git_folder
    clone_to_path(gh_token, temp_dir, split_git_id[0], branch_or_commit=branch, pr_number=pr_number)
  File "/usr/local/lib/python3.6/dist-packages/azure_devtools/ci_tools/github_tools.py", line 187, in clone_to_path
    login = user_from_token(gh_token).login
  File "/usr/local/lib/python3.6/dist-packages/github/AuthenticatedUser.py", line 226, in login
    self._completeIfNotSet(self._login)
  File "/usr/local/lib/python3.6/dist-packages/github/GithubObject.py", line 259, in _completeIfNotSet
    self._completeIfNeeded()
  File "/usr/local/lib/python3.6/dist-packages/github/GithubObject.py", line 263, in _completeIfNeeded
    self.__complete()
  File "/usr/local/lib/python3.6/dist-packages/github/GithubObject.py", line 268, in __complete
    self._url.value
  File "/usr/local/lib/python3.6/dist-packages/github/Requester.py", line 260, in requestJsonAndCheck
    return self.__check(*self.requestJson(verb, url, parameters, headers, input, self.__customConnection(url)))
  File "/usr/local/lib/python3.6/dist-packages/github/Requester.py", line 317, in requestJson
    return self.__requestEncode(cnx, verb, url, parameters, headers, input, encode)
  File "/usr/local/lib/python3.6/dist-packages/github/Requester.py", line 370, in __requestEncode
    status, responseHeaders, output = self.__requestRaw(cnx, verb, url, requestHeaders, encoded_input)
  File "/usr/local/lib/python3.6/dist-packages/github/Requester.py", line 394, in __requestRaw
    response = cnx.getresponse()
  File "/usr/local/lib/python3.6/dist-packages/github/Requester.py", line 107, in getresponse
    r = verb(url, headers=self.headers, data=self.input, timeout=self.timeout, verify=self.verify)
  File "/usr/local/lib/python3.6/dist-packages/requests/sessions.py", line 525, in get
    return self.request('GET', url, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/requests/sessions.py", line 512, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.6/dist-packages/requests/sessions.py", line 622, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/requests/adapters.py", line 495, in send
    raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', OSError(0, 'Error'))

@AutorestCI regenerate azure-sdk-for-node

Automation for azure-sdk-for-js


Backend Specific RunConditions and Space Flags in xr crate

Add Backend Specific session_running and session_available to allow for non OpenXR backends while compiling for something other than wasm
Add SpaceFlags to bevy_mod_xr to detect loss of tracking without needing to depend on bevy_mod_openxr directly

I don't think this has breaking changes