Cleanup dependencies

Pull Request Checklist:

[x] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #799, fixes #794 and addresses discussions from the internal slack.

[x] Tests for the changes have been added (for bug fixes / features)
[x] Documentation has been added / updated (for bug fixes / features)
[x] HISTORY.rst has been updated (with summary of main changes)
[ ] bumpversion (major / minor / patch) has been called on this branch
[ ] Tags have been pushed (git push --tags)
[ ] The relevant author information has been added to .zenodo.json

What kind of change does this PR introduce?

Removes all the "extra" dependencies from setup.py except "dev". All tools needed for testing, documenting and developping xclim are listed in requirements_dev.py.
Fixes a doctest issue triggered by cftime 1.5.
Removes the line that was installing cftime 1.4.1 in the test suite (!!!!)
Unpin pandas
Removes the mention of ".ipynb" as a source suffix in docs/conf.py. That variable, when it is a list, will associate all those files with the RST parser. Before nbsphinx 0.8.7 (10 Aug 2021), the plugin would override the current configuration, but now it doesn't, so the bug showed itself.

Does this PR introduce a breaking change?
I don't know if this count as a "breaking change", but installation options have changed.
Other information:
@Zeitsperre I removed some packages from the dev reqs:
ipykernel, ipython, jupyter_client, wheel, watchdog, twine

I was able to follow all the steps of the "contributing" page of the doc. Are any of those explicitely needed by developers nonetheless? I see that some are needed for packaging, but I think we can leave them out of the dev reqs, as only you or few others will ever do that task.
I haven't addressed #795, but could do it here if people agree with the idea.

@Zeitsperre I removed some packages from the dev reqs:
ipykernel, ipython, jupyter_client, wheel, watchdog, twine

I was able to follow all the steps of the "contributing" page of the doc. Are any of those explicitely needed by developers nonetheless? I see that some are needed for packaging, but I think we can leave them out of the dev reqs, as only you or few others will ever do that task.

wheel and twine are only needed for uploading releases. Seeing as this is a major library of ours, it would be good to have the steps in the development docs. Feel free to keep them removed for now, but I'll open an issue to finish the packaging docs on another PR.
For the Jupyter-related libraries, we need a minimal environment in the dev recipe for running the notebooks via pytest at the very least. If we can get away without those libraries, great!
I had no idea watchdog was in there. Is that library used for some form of provenance tracking?

I haven't addressed #795, but could do it here if people agree with the idea.

I have some thoughts on this, but I'll add to the issue. My vote is to hold off for now.

After our discussion from the other day, we'll go forward with the suggestion of bundling the testing dependencies into the GitHub source environment.yml. Once that's in, we should be good to merge!


Dates in matrix rows should be able to re-order

Are you requesting a feature, reporting a bug or asking a question?
question/feature
What is the current behavior?
Date fields(custom datepicker) can be added to a matrix dynamic
What is the expected behavior?
Rows in matrix dynamic should be able to re-order based on latest date being at the top/bottom
How would you reproduce the current behavior (if this is a bug)?
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code
{             pages: [                 {                     name: "page1",                     elements: [                         {                             type: "matrixdynamic",                             name: "ComplexMedicalNeeds",                             titleLocation: "hidden",                             columns: [                                 {                                     name: "Date",                                     cellType: "datepicker",                                     dateFormat: "mm/dd/yy",                                     config: {                                         showOn: "button",                                         buttonImage:                                         "assets/icons/date.svg",                                         buttonImageOnly: true,                                         buttonText: "Select date",                                         maxDate: "+0D"                                     },                                     inputType: "date"                                 },                                 {                                     name: "Narrative",                                     cellType: "comment",                                     maxLength: 2000,                                     validators: [                                         {                                             type: "text",                                             allowDigits: true,                                             minLength: 0,                                             maxLength: 2000                                         }                                     ]                                 },                                 {                                     name: "Actions",                                     visibleIf: "1 = 2"                                 }                             ],                             cellType: "text",                             rowCount: 0,                             addRowLocation: "top",                             addRowText: "ADD COMPLEX NEED  +",                             removeRowText: " ",                             confirmDelete: true,                             confirmDeleteText: "Are you sure you want to delete medical/nursing needs record?"                         }                     ]                 }             ],             showTitle: false,             showQuestionNumbers: "off",             questionErrorLocation: "bottom"         }
your_code_here

Specify your

browser: chrome
browser version:
surveyjs platform (angular or react or jquery or knockout or vue): angular 5
surveyjs version: 1.0.35

Could you please share your use case? It doesn't seem for me as a survey must have functionality. It looks like you need integrate a grid control (e.g. https://datatables.net/) as a custom widget.

Our use case is that we should be able to add dynamic rows (which has one of the column as datepicker).
Once the survey is saved and come back again, the date should be re-order based on chronological order of the dates.

You can reorder survey data on your side before assigning to the survey.data


Creating Go Client Libraries for KFservice CRD

What this PR does / why we need it:
This PR is for creating a static go client for KFservice CRD. This has a script to create a go client from the KFService types file using the kubernetes code-generator that can be used to create custom informers and other kubernetes like CRUD API for KFservice CRD.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #161
Special notes for your reviewer:
This PR changes the Gopkg.toml file to avoid pruning some non go files for the code generator package. Please run dep ensure before generating the client files using the hack shell script.

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

None

This change is

/ok-to-test

Looks cool, @SachinVarghese  where do you intend to use this client go library ?

/ok-to-test

Please run dep ensure before generating the client files using the hack shell script.

Should we include this in the hack script then? This isn't a good thing for developers to remember. These scripts should be self contained

@ellis-bigelow I think @SachinVarghese means that he has not included updates to the vendor folder needed for the PR as per our practice this needs to be done by a project admin.

@yuzisun @SachinVarghese works at Seldon and plans to use it for our enterprise UI to ML deployment management.

Please run dep ensure before generating the client files using the hack shell script.

Should we include this in the hack script then? This isn't a good thing for developers to remember. These scripts should be self contained

@ellis-bigelow the dep ensure command is for the project admin to get the vendor updates for this PR and is not required to generate the go client files every time, just the hack script is enough.
Also, I see that there are failed tests in this PR but could not find info on what exactly went wrong. It would be great to get some more details on this.

Please run dep ensure before generating the client files using the hack shell script.

Should we include this in the hack script then? This isn't a good thing for developers to remember. These scripts should be self contained

@ellis-bigelow the dep ensure command is for the project admin to get the vendor updates for this PR and is not required to generate the go client files every time, just the hack script is enough.
Also, I see that there are failed tests in this PR but could not find info on what exactly went wrong. It would be great to get some more details on this.

Ah -- yes :) I'll take care of this.

@yuzisun @SachinVarghese works at Seldon and plans to use it for our enterprise UI to ML deployment management.

@cliveseldon @SachinVarghese I am currently working on similar deployment management internally, I'd be interested in hearing how you guys are doing it.

/lgtm
/approve


Strange typing_extensions position

Before<EMAIL_ADDRESS>my typing_extension imports were positioned in 3rd-party section. Which, I guess, is the correct place for them.
Example:
from typing import Generic

from typing_extensions import Final

from returns.hkt import Kind

After the update my code started to look like this:
from typing import Generic

from returns.hkt import Kind
from typing_extensions import Final

It does not seem right to me.
Repo to try: https://github.com/dry-python/returns
Config: https://github.com/dry-python/returns/blob/master/setup.cfg

@sobolevn isort 5.0.0 uses a new finding strategy that is guaranteed to be the same across environments, CI/CD etc. However, it is able to do this only by no longer taking env, requirements etc into the equation (see: https://github.com/timothycrosley/isort/issues/1147). I think you should get the behaviour you want on 5.0.0 simply by removing this line from your config: https://github.com/dry-python/returns/blob/master/setup.cfg#L74. otherwise, you can enable the old magical finding behaviour by enabling --magic-placement: https://timothycrosley.github.io/isort/docs/configuration/options/#old-finders

Yes, removing default_section = FIRSTPARTY solves my issue.
Thanks a lot for isort and quick help! 👍


Refactor code base of Subject, BehaviorSubject and ReplaySubject

Bug Report
Current Behavior
The functionality is completely fine. This issue is related to some refactoring work that could be done.
The following issue is related to the following files:

src/internal/Subject.ts
src/internal/BehaviorSubject.ts
src/internal/ReplaySubject.ts
src/internal/WebSocketSubject.ts

Suggested changes
Subject.ts:

[x] Referencing a class property consistently. Also, referencing properties over this instead of destruction this.

A good example of inconsistency in referencing class properties is here:
https://github.com/ReactiveX/rxjs/blob/b24d3ea85d33b893e4c020fb4fa9f6fa4d05dc0b/src/internal/Subject.ts#L165-L170
Switching to referencing properties over this would take away the mental load of understanding object destruction and is applicable through the whole file.

[x] Using array first-class functions instead of for loops.

To iterate through the observers of the subject a for loops is used. This could be improved by using array first-class functions. As a side-effect of this refactoring, we can get rid of multiple constants.
A good example could is the next method:
https://github.com/ReactiveX/rxjs/blob/b24d3ea85d33b893e4c020fb4fa9f6fa4d05dc0b/src/internal/Subject.ts#L66-L71

[ ] Get rid of Symbol. As it is internal stuff there is no need for depreciation, we can just delete it.
Detailed information can be found here: Why check RxSubscriberSymbol in toSubscriber

https://github.com/ReactiveX/rxjs/blob/b24d3ea85d33b893e4c020fb4fa9f6fa4d05dc0b/src/internal/Subject.ts#L30
BehaviorSubject.ts:

[x] We could remove typing of subscription as it not needed. super._subscriber already returns Subscription.
https://github.com/ReactiveX/rxjs/blob/b24d3ea85d33b893e4c020fb4fa9f6fa4d05dc0b/src/internal/BehaviorSubject.ts#L26

ReplaySubject.ts:

[x] Replacing ReplayEvent class with an interface as it does not bring any additional value and it's also less performant.

https://github.com/ReactiveX/rxjs/blob/b24d3ea85d33b893e4c020fb4fa9f6fa4d05dc0b/src/internal/ReplaySubject.ts#L50
https://github.com/ReactiveX/rxjs/blob/b24d3ea85d33b893e4c020fb4fa9f6fa4d05dc0b/src/internal/ReplaySubject.ts#L133-L136
WebSocketSubject.ts:
TBD
Possible Solution
I'm in progress of preparing a PR for this. The current status can be found here:
https://github.com/BioPhoton/rxjs/commit/b7a7b61a7bea76aa8ad9b951dbca42d8538aa78c

I'm just curious what is the plan with BehaviorSubject.getValue()? I think there was a discussion whether it should be deprecated because it encourages "imperative" approach but I can't find it anywhere now.

@cartant
Do you think it is a good decision to remove the Symbol?

Get rid of Symbol. As it is internal stuff there is no need for depreciation, we can just delete it.
Detailed information can be found here: Why check RxSubscriberSymbol in toSubscriber

Just so you know:

It's more efficient to pull properties out into variables to prevent duplicate property lookups.
for loops are more efficient for iterating arrays, and we never want to use forEach (or really even for...of) to iterate over arrays.
The symbol stuff is indeed a breaking change at our scale. I guarantee someone is using it. So it needs to be documented as such and included in a major revision.

I appreciate all of the thought here, but we might want to discuss this sort of thing before you dive in next time :)

Also for this:
if (nextOrObserver) {
    if (nextOrObserver instanceof Subscriber) {
      return (<Subscriber<T>>nextOrObserver);
    }
    if ((nextOrObserver as any).constructor
      && (nextOrObserver as any).constructor.name.indexOf('Subject') !== -1) {
       return new SubjectSubscriber(nextOrObserver as Subject<T>) as Subscriber<T>;
    }
  }

The new version is going to be vastly less efficient. It's the difference between a single property lookup and two property lookups plus searching a string. This isn't to mention that part of the reason we had that check was to ensure that the instance we had was actually from this instance of the library. I know that sounds weird, but there are plenty of cases in node development where there is more than one version or copy of rxjs in node_modules, and we need to differentiate. This change would break those cases.
RxJS is hot-path code for folks, so micro optimizations here actually matter.

I'm sorry I didn't see this issue until now. We really should have discuss this before you set out on this. I feel really bad closing it, as you've clearly put in a lot of thought and effort.
So sorry, @BioPhoton. ❤


The uploaded files are deleted by accidentally posting a removefile request immediately after submitting a runtask with uploaded files

Vue2-dropzone Version:2.3.5
Node Version : 6.11.4
NPM Version : 3.10.10
OS: Ubuntu 16.04

Description:
vue-dropzone is used to upload files. Frontend code is built with webpack and deployed to server with docker-compose. The uploaded files are deleted by accidentally posting a removefile request immediately after submitting a runtask with uploaded files. Can someone help me to avoid unnecessary deleting?
    destroyed: function() {
      document.querySelectorAll('input.dz-hidden-input').forEach(function (elem) { elem.parentNode.removeChild(elem) })
    }

The code above may issue the removefile request.

I am experiencing the same issue. A vdropzone-removed-file event is emitted when the component is destroyed. Since i'm listening to the event and deleting images on the server all the images get deleted. I dont think that's expected behaviour.

Hi @lomholdt
This is fixed in v3 which I will hopefully release some time in the coming week. Feel free to take a look at the v3 branch if you'd like a more immediate fix.

Hi' @rowanwins. Sounds, and looks great! Thanks a ton! I will add the fix manually for now until the new version is out. Thanks again :)

Hi @lomholdt & @zhangzhen
V3 is now released for feel free to check it out, it contains a property to cancel the destroy event so hopefully it helps.

Thanks! :) Much appreciated.

Problem still exists in 3.6.0. Hitting the back button that fires the following code
$router.go(-1) on a button click destroys the vue2 dropzone component triggering unwanted calls to @vdropzone-removed-file="vremoved" removing the uploaded files.
Any solution yet ? Thanks.


Azure Cloud Tutorials

Updated links to unity release packages.

Docs Build status updates of commit f42149a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/mr-learning-azure-01.md
:warning:Warning
View
Details

mixed-reality-docs/mr-learning-asa-01.md
:bulb:Suggestion
View
Details

mixed-reality-docs/mr-learning-azure-03.md
:bulb:Suggestion
View
Details

mixed-reality-docs/community.md
:white_check_mark:Succeeded
View

mixed-reality-docs/direct-manipulation.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hand-menu.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-player.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-troubleshooting.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-version-history.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_AffordanceExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_SizeExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-03.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-04.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/porting-guides.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-01.md

Line 66, Column 32: [Warning-file-not-found] Invalid file link: 'mr-learning-base.md'.
Line 102, Column 80: [Warning-file-not-found] Invalid file link: 'mr-learning-base-ch1.md'.
Line 185, Column 100: [Warning-file-not-found] Invalid file link: 'mr-learning-base-ch1.md'.

mixed-reality-docs/mr-learning-asa-01.md

Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '1. Introduction' is duplicated with other articles: 'mr-learning-asa-01.md(12,1), mr-learning-base-01.md(12,1), mr-learning-sharing-01.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

mixed-reality-docs/mr-learning-azure-03.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Azure Cloud Tutorials - 3. Integrating Azure Custom Vision - Mixed Reality' is duplicated in: 'mrlearning-azure-03.md(2,8), mr-learning-azure-03.md(2,8)'. Titles must be unique within a docset.
Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '3. Integrating Azure Custom Vision' is duplicated with other articles: 'mrlearning-azure-03.md(12,1), mr-learning-azure-03.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit edf92d7:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/mr-learning-azure-01.md
:warning:Warning
View
Details

mixed-reality-docs/mr-learning-asa-01.md
:bulb:Suggestion
View
Details

mixed-reality-docs/mr-learning-azure-03.md
:bulb:Suggestion
View
Details

mixed-reality-docs/community.md
:white_check_mark:Succeeded
View

mixed-reality-docs/direct-manipulation.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hand-menu.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-player.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-troubleshooting.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-version-history.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_AffordanceExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_SizeExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-03.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-04.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/porting-guides.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-01.md

Line 102, Column 80: [Warning-bookmark-not-found] Cannot find bookmark '#import-the-mixed-reality-toolkit' in 'mr-learning-base-01.md'.
Line 185, Column 100: [Warning-bookmark-not-found] Cannot find bookmark '#build-your-application-to-your-device' in 'mr-learning-base-01.md'.

mixed-reality-docs/mr-learning-asa-01.md

Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '1. Introduction' is duplicated with other articles: 'mr-learning-asa-01.md(12,1), mr-learning-base-01.md(12,1), mr-learning-sharing-01.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

mixed-reality-docs/mr-learning-azure-03.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Azure Cloud Tutorials - 3. Integrating Azure Custom Vision - Mixed Reality' is duplicated in: 'mrlearning-azure-03.md(2,8), mr-learning-azure-03.md(2,8)'. Titles must be unique within a docset.
Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '3. Integrating Azure Custom Vision' is duplicated with other articles: 'mrlearning-azure-03.md(12,1), mr-learning-azure-03.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1c3069d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/TOC.md
:warning:Warning
View
Details

mixed-reality-docs/mr-learning-azure-01.md
:warning:Warning
View
Details

mixed-reality-docs/mr-learning-asa-01.md
:bulb:Suggestion
View
Details

mixed-reality-docs/mr-learning-azure-03.md
:bulb:Suggestion
View
Details

mixed-reality-docs/community.md
:white_check_mark:Succeeded
View

mixed-reality-docs/direct-manipulation.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hand-menu.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-player.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-troubleshooting.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-version-history.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_AffordanceExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_SizeExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-03.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-04.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/porting-guides.md
:white_check_mark:Succeeded
View

mixed-reality-docs/TOC.md

Line 151, Column 7: [Warning-file-not-found] Invalid file link: 'mr-learning-04.md'.
Line 152, Column 7: [Warning-file-not-found] Invalid file link: 'mr-learning-05.md'.

mixed-reality-docs/mr-learning-azure-01.md

Line 102, Column 80: [Warning-bookmark-not-found] Cannot find bookmark '#import-the-mixed-reality-toolkit' in 'mr-learning-base-02.md', did you mean '#importing-the-mixed-reality-toolkit'?
Line 185, Column 100: [Warning-bookmark-not-found] Cannot find bookmark '#build-your-application-to-your-device' in 'mr-learning-base-02.md'.

mixed-reality-docs/mr-learning-asa-01.md

Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '1. Introduction' is duplicated with other articles: 'mr-learning-asa-01.md(12,1), mr-learning-base-01.md(12,1), mr-learning-sharing-01.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

mixed-reality-docs/mr-learning-azure-03.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Azure Cloud Tutorials - 3. Integrating Azure Custom Vision - Mixed Reality' is duplicated in: 'mrlearning-azure-03.md(2,8), mr-learning-azure-03.md(2,8)'. Titles must be unique within a docset.
Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '3. Integrating Azure Custom Vision' is duplicated with other articles: 'mrlearning-azure-03.md(12,1), mr-learning-azure-03.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 7582f8d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/TOC.md
:warning:Warning
View
Details

mixed-reality-docs/mr-learning-azure-01.md
:warning:Warning
View
Details

mixed-reality-docs/mr-learning-asa-01.md
:bulb:Suggestion
View
Details

mixed-reality-docs/mr-learning-azure-03.md
:bulb:Suggestion
View
Details

mixed-reality-docs/community.md
:white_check_mark:Succeeded
View

mixed-reality-docs/direct-manipulation.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hand-menu.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-player.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-troubleshooting.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-version-history.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_AffordanceExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_SizeExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-03.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-04.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/porting-guides.md
:white_check_mark:Succeeded
View

mixed-reality-docs/TOC.md

Line 151, Column 7: [Warning-file-not-found] Invalid file link: 'mr-learning-04.md'.
Line 152, Column 7: [Warning-file-not-found] Invalid file link: 'mr-learning-05.md'.

mixed-reality-docs/mr-learning-azure-01.md

Line 185, Column 100: [Warning-bookmark-not-found] Cannot find bookmark '#building-your-application-to-your-HoloLens-2' in 'mr-learning-base-02.md', did you mean '#building-your-application-to-your-hololens-2'?

mixed-reality-docs/mr-learning-asa-01.md

Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '1. Introduction' is duplicated with other articles: 'mr-learning-asa-01.md(12,1), mr-learning-base-01.md(12,1), mr-learning-sharing-01.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

mixed-reality-docs/mr-learning-azure-03.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Azure Cloud Tutorials - 3. Integrating Azure Custom Vision - Mixed Reality' is duplicated in: 'mrlearning-azure-03.md(2,8), mr-learning-azure-03.md(2,8)'. Titles must be unique within a docset.
Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '3. Integrating Azure Custom Vision' is duplicated with other articles: 'mrlearning-azure-03.md(12,1), mr-learning-azure-03.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 7c0fc48:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/mr-learning-azure-01.md
:warning:Warning
View
Details

mixed-reality-docs/mr-learning-asa-01.md
:bulb:Suggestion
View
Details

mixed-reality-docs/mr-learning-azure-03.md
:bulb:Suggestion
View
Details

mixed-reality-docs/TOC.md
:white_check_mark:Succeeded
View

mixed-reality-docs/community.md
:white_check_mark:Succeeded
View

mixed-reality-docs/direct-manipulation.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hand-menu.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-player.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-troubleshooting.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-version-history.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_AffordanceExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_SizeExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-03.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-04.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/porting-guides.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-01.md

Line 185, Column 100: [Warning-bookmark-not-found] Cannot find bookmark '#building-your-application-to-your-holoLens-2' in 'mr-learning-base-02.md', did you mean '#building-your-application-to-your-hololens-2'?

mixed-reality-docs/mr-learning-asa-01.md

Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '1. Introduction' is duplicated with other articles: 'mr-learning-asa-01.md(12,1), mr-learning-base-01.md(12,1), mr-learning-sharing-01.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

mixed-reality-docs/mr-learning-azure-03.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Azure Cloud Tutorials - 3. Integrating Azure Custom Vision - Mixed Reality' is duplicated in: 'mrlearning-azure-03.md(2,8), mr-learning-azure-03.md(2,8)'. Titles must be unique within a docset.
Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '3. Integrating Azure Custom Vision' is duplicated with other articles: 'mrlearning-azure-03.md(12,1), mr-learning-azure-03.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 584438a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/mr-learning-azure-01.md
:warning:Warning
View
Details

mixed-reality-docs/mr-learning-asa-01.md
:bulb:Suggestion
View
Details

mixed-reality-docs/mr-learning-azure-03.md
:bulb:Suggestion
View
Details

mixed-reality-docs/TOC.md
:white_check_mark:Succeeded
View

mixed-reality-docs/community.md
:white_check_mark:Succeeded
View

mixed-reality-docs/direct-manipulation.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hand-menu.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-player.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-troubleshooting.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-version-history.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_AffordanceExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_SizeExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-03.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-04.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/porting-guides.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-01.md

Line 187, Column 0: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 188, Column 100: [Warning-bookmark-not-found] Cannot find bookmark '#building-your-application-to-your-holoLens-2' in 'mr-learning-base-02.md', did you mean '#building-your-application-to-your-hololens-2'?
Line 185, Column 1: [Suggestion-merge-conflict] File contains merge conflict markers. NOTE: This Suggestion will become a Warning on 06/30/2020.

mixed-reality-docs/mr-learning-asa-01.md

Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '1. Introduction' is duplicated with other articles: 'mr-learning-asa-01.md(12,1), mr-learning-base-01.md(12,1), mr-learning-sharing-01.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

mixed-reality-docs/mr-learning-azure-03.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Azure Cloud Tutorials - 3. Integrating Azure Custom Vision - Mixed Reality' is duplicated in: 'mrlearning-azure-03.md(2,8), mr-learning-azure-03.md(2,8)'. Titles must be unique within a docset.
Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '3. Integrating Azure Custom Vision' is duplicated with other articles: 'mrlearning-azure-03.md(12,1), mr-learning-azure-03.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit b721dca:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/mr-learning-azure-01.md
:warning:Warning
View
Details

mixed-reality-docs/mr-learning-asa-01.md
:bulb:Suggestion
View
Details

mixed-reality-docs/TOC.md
:white_check_mark:Succeeded
View

mixed-reality-docs/community.md
:white_check_mark:Succeeded
View

mixed-reality-docs/direct-manipulation.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hand-menu.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-player.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-troubleshooting.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-version-history.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_AffordanceExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_SizeExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-03.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-04.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-03.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mrlearning-azure-03.md
:white_check_mark:Succeeded

mixed-reality-docs/porting-guides.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-01.md

Line 187, Column 0: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 188, Column 100: [Warning-bookmark-not-found] Cannot find bookmark '#building-your-application-to-your-holoLens-2' in 'mr-learning-base-02.md', did you mean '#building-your-application-to-your-hololens-2'?
Line 185, Column 1: [Suggestion-merge-conflict] File contains merge conflict markers. NOTE: This Suggestion will become a Warning on 06/30/2020.

mixed-reality-docs/mr-learning-asa-01.md

Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '1. Introduction' is duplicated with other articles: 'mr-learning-asa-01.md(12,1), mr-learning-base-01.md(12,1), mr-learning-sharing-01.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit f07a521:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/mr-learning-azure-01.md
:warning:Warning
View
Details

mixed-reality-docs/mr-learning-asa-01.md
:bulb:Suggestion
View
Details

mixed-reality-docs/TOC.md
:white_check_mark:Succeeded
View

mixed-reality-docs/community.md
:white_check_mark:Succeeded
View

mixed-reality-docs/direct-manipulation.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hand-menu.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-player.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-troubleshooting.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-version-history.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_AffordanceExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_SizeExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-03.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-04.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-03.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mrlearning-azure-03.md
:white_check_mark:Succeeded

mixed-reality-docs/porting-guides.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-01.md

Line 187, Column 0: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 188, Column 100: [Warning-bookmark-not-found] Cannot find bookmark '#building-your-application-to-your-holoLens-2' in 'mr-learning-base-02.md', did you mean '#building-your-application-to-your-hololens-2'?
Line 185, Column 1: [Suggestion-merge-conflict] File contains merge conflict markers. NOTE: This Suggestion will become a Warning on 06/30/2020.

mixed-reality-docs/mr-learning-asa-01.md

Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '1. Introduction' is duplicated with other articles: 'mr-learning-asa-01.md(12,1), mr-learning-base-01.md(12,1), mr-learning-sharing-01.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit dfecebc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/mr-learning-asa-01.md
:bulb:Suggestion
View
Details

mixed-reality-docs/TOC.md
:white_check_mark:Succeeded
View

mixed-reality-docs/community.md
:white_check_mark:Succeeded
View

mixed-reality-docs/direct-manipulation.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hand-menu.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-player.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-troubleshooting.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-version-history.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_AffordanceExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_SizeExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-03.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-04.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-01.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-03.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mrlearning-azure-03.md
:white_check_mark:Succeeded

mixed-reality-docs/porting-guides.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-01.md

Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '1. Introduction' is duplicated with other articles: 'mr-learning-asa-01.md(12,1), mr-learning-base-01.md(12,1), mr-learning-sharing-01.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@jessemcculloch

@mr0ng Have these gone through the Flesche readability score check?

@hferrone here are the readability results:

@jessemcculloch This one's ready too!

@mr0ng @varunsiddaraju - There are merge conflicts that need to be resolved on this one

Docs Build status updates of commit 32e24ad:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/mr-learning-asa-01.md
:bulb:Suggestion
View
Details

mixed-reality-docs/TOC.md
:white_check_mark:Succeeded
View

mixed-reality-docs/community.md
:white_check_mark:Succeeded
View

mixed-reality-docs/direct-manipulation.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hand-menu.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-player.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-troubleshooting.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-version-history.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_AffordanceExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_SizeExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-03.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-04.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-01.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-03.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mrlearning-azure-03.md
:white_check_mark:Succeeded

mixed-reality-docs/porting-guides.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-01.md

Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '1. Introduction' is duplicated with other articles: 'mr-learning-asa-01.md(12,1), mr-learning-base-01.md(12,1), mr-learning-sharing-01.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@jessemcculloch Resolved all merge conflicts.

Docs Build status updates of commit e965435:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/mr-learning-asa-01.md
:bulb:Suggestion
View
Details

mixed-reality-docs/TOC.md
:white_check_mark:Succeeded
View

mixed-reality-docs/community.md
:white_check_mark:Succeeded
View

mixed-reality-docs/direct-manipulation.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hand-menu.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-player.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-troubleshooting.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-version-history.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_AffordanceExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/UX/HandMenu_SizeExample.png
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-03.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-04.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-01.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-02.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-03.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-05.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mrlearning-azure-03.md
:white_check_mark:Succeeded

mixed-reality-docs/porting-guides.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-asa-01.md

Line 12, Column 1: [Suggestion-duplicate-h1s] H1 '1. Introduction' is duplicated with other articles: 'mr-learning-asa-01.md(12,1), mr-learning-base-01.md(12,1), mr-learning-sharing-01.md(12,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[Bug]: light card color temperature slider does not show coldest temperatures

Current Behavior
When light has color temperature capability, HA displays the slider going from coldest to warmest temp as a blue to orange gradient.
Mushroom card shows the slider going from white to orange.

In your original implementation, the cold temp was correctly shown (and still on the readme example image), but later a PR #48 removed this to set to white as the coldest temp.
While I did see there was a technical reason, I do believe this is actually kind of a UI issue.
Couple of reason:

The most obvious is that by having white as coldest light: you don't know what color you are setting! Quite a few HA integrations have spent some time aligning the scales so that the white HA is really the white of the light. Using the mushroom card, I cannot exactly see where is the actual white lamp.
When you bring up the HA more info panel for that light, the scale shows to from blue to orange, so having a white to orange scale in mushroom card is inconsistent and will throw user off balance as it is not expected. (I did thought there was an issue with my setup until I dig through the code of the mushroom card...)
I would argue that having the light icon to match the color temp slider is less of a priority for good design than having consistent slider scale with HA and being able to set colors properly

Expected Behavior
Having the same color temperature slider as HA in the mushroom card.
Steps To Reproduce
No response
Environment
- OS:
- Node:
- Version:
- Hassio: 2022.5.4

Anything else?
No response

We can't follow the slider gradient because I think we can't detect that a light is in temp_color mode.
The icon color is based on rgb_color attributes.

@alessandroias  Thanks for explaining that, I actually had never realized that the light icon color appear wrong on HA more info panel as well. Fixing that in HA would seem to be the first step. Thanks for opening an issue there!
But in the meantime we could basically replicate the HA behaviour in mushroom card. I.e: slider going from blue to orange, and light icon grey to orange.
@piitaya , I am not sure how mushroom card get the light details, but it seems (on my light at least) that the current color_mode and mi_red value is part of the attributes:

Not sure if that is the case for every light though.

if hass.states[entity_id].attributes.color_mode === "color_temp" is true its in color temp mode.
You probably don't want to adjust the color temp slider based on the brightness value of the light as it will be quite confusing when its all pale grey.

Closing as the color temperature of HA changed with updates.


Ability to disable practice mode for challenge from yaml

Sometimes, we want the ability to run a challenge and have students not be able to see the source.
For instance, when teaching web security we want to mimic a situation where the attacker does not have access to source code. Having the practice mode significantly complicates this, as the code can be hidden using permissions, it will then be visible in practice mode (with the user having sudo).
It would also help b/c sometimes practice mode is useless for a challenge and only serves to confuse the users.

Done!


How to make custom selected value by quarter of selected date?

Hey, I am having some issue to make my datepicker to show quarter as selected input.
I am using quarter picker:
    <Month
            ref="quarter"
            day={new Date()}
            selected={this.state.startDate}
            className="quarter_date_picker"
            placeholderText={"Select here"}
            showQuarterYearPicker
            onChange={this.handleChangeStart.bind(this)}
            dateFormat="yyyy-MM"
            onChangeRaw={this.handleDateChangeRaw}
      />

And it returns start date of a quarter. Maybe there is possibility to return year and quarter. For example:
2020 Q3
Maybe someone had same use case?

I found in documentation. Sorry.


Fixed dead link

I haven't tested my changes on a local copy. Just a quick fix.
fixes #7912

@nsgonultas Thanks for the PR, But Please follow the Contribution Guidelines hence on.

@nsgonultas I agree with @raisedadead - be sure to test this locally before submitting the PR next time. This said, I have tested it and it works. Thanks for your contribution!


Add Collection Time on All Server Dashboard

Is your feature request related to a problem? Please describe.
It's very important to know when the data collection happened while analyzing the data.
So need to add collection_time on All Server Dashboard panels.


Averaging

Adding averaging jobtype to Runner.
Also added a mock Communication Jobtype just to get to the Averaging test.
Please do me an approve friendo.
No am many lines code change.
(P.S. the integration test for the Communication Manager looks horrific, I know, but just imagine how hard it was to make the test!)

Ok, since it's not dependent on the Blockchain code, let's remove the code related to it (NEW_INFO, the code I removed from the optimizers in PR #26, etc).
About the COMM code, it sounds like there's less boilerplate/temp code to be written in this PR if the COMM PR is submitted first, so why don't we get the COMM PR out first and then we come back to this one? It will make reviewing both/ approving both easier for both of us.

Ok, this PR will have to wait on the Gateway PR and then the COMM PR then.
NEW_INFO, etc. is not dependent on the Blockchain code. So it should stay in regardless.

This PR is ready to be merged. @neeleshdodda44 Please review.


Update sbt-tpolecat to 0.1.12

Updates io.github.davidgregory084:sbt-tpolecat from 0.1.11 to 0.1.12.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.github.davidgregory084", artifactId = "sbt-tpolecat" } ]

labels: sbt-plugin-update, semver-patch

Codecov Report

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

@@            Coverage Diff            @@
##            master        #6   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines           55        55
  Branches         2         2
=========================================
  Hits            55        55

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 d0ed6eb...d858cd6. Read the comment docs.


Give better explanation for double machine learning in documentation

Explain that the final model is linear and that the functional form is partially linear and semiparametric.

Updated in commits 73b8494 and b84bb08.


Tensorflow 2.1: How does the metric 'tf.keras.metrics.PrecisionAtRecall' works with multiclass-classification?

I am wondering how this metrics works in case of multiclass classification. Does it compute the average between values of precision belonging to each class?
I have a multiclass-classification problem, with three classes. I am interested in calculate the PrecisionAtRecall when the recall value is equal to 0.76, only for a specific class . What I have done was just setting 0.76 in brackets :
'' model.compile(optimizer='adam', loss='categorical_crossentropy', metrics=['accuracy', tf.keras.metrics.PrecisionAtRecall(0.76)], sample_weight_mode='temporal') ''
But I am sure is not the right way.
How can I adjust my code to reach my goal?
Thanks

Thanks for your question. This doesn't not concern tensorflow addons. Tensorflow addons is imported with import tensorflow_addons. For matters related to tf.keras, see the tensorflow/tensorflow repository.


Can't find the Options

Hi,
Running Home Assistant 0.118.4 ecowitt 0.5 installed using HACS 1.6.2 on raspberry pi 3b.
Ecowitt GW1000 up and running and configured to send on port 4199.
I'm new to using HACS and can't find where the Options for ecowitt integration are entered.  Nothing seems to happen after ecowitt is installed and HA restarted other than it appears in the HACS integrations list and the followings appear in the Log:
2020-11-27 21:23:37 DEBUG (MainThread) [custom_components.hacs.repository.integration.garbled1.homeassistant_ecowitt] Getting repository information
2020-11-27 21:23:37 DEBUG (MainThread) [custom_components.hacs.repository.integration.garbled1.homeassistant_ecowitt] Running checks against 0.5
What am I missing?

Go to integrations, hit the + and search for ecowitt, Click on it and it should give you instructions to fill in the port # and do the remainder of the setup.  Once it's setup, you can go back into integrations, find the ecowitt integration, and select options at the bottom of the card.

Thanks for that, I go it now.
The part I found confusing is that HACS also has an "Integrations" page so when the instructions say "Go to Integrations" I thought that meant in HACS.
To make it clearer for the next person who isn't sure how to install the component using HACS:

Go to HACS -> Integrations -> Click "+"

Search for "Ecowitt Weather Station" repository and add to HACS

Restart Home Assistant when it says to.

In Home Assistant, go to Configuration -> Integrations  -> Click "+ Add Integration"

Search for "Ecowitt Weather Station" and follow the instructions to setup.

Ecowitt should now appear as a card under the HA Integrations page with "Options" selection available at the bottom of the card.

I have followed steps 1-4, however when I get to step 5, Ecowitt is not found. I've restarted HA and the Pi its running on several times. Any suggestions?

In the logs does it show you are running a custom integration for ecowitt?

Seeing the following in logs, so I'm assuming this means its installed:
2020-12-22 11:46:08 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for ecowitt which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
and
2020-12-22 11:46:39 DEBUG (MainThread) [custom_components.hacs] <Integration hacs/integration> Getting repository information 2020-12-22 11:46:39 DEBUG (MainThread) [custom_components.hacs] <Integration garbled1/homeassistant_ecowitt> Getting repository information 2020-12-22 11:46:39 DEBUG (MainThread) [custom_components.hacs] <Integration garbled1/homeassistant_ecowitt> Running checks against 0.5 2020-12-22 11:46:39 DEBUG (MainThread) [custom_components.hacs] <Integration hacs/integration> Running checks against 1.9.0

Tried one more time just now and it showed up. Strange. But it's now working.


Stop Ble Mesh Node advertisement which is shown in mobile while scanning for bluetooth devices  (IDFGH-10612)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Hi,
We have developed a ble mesh product with esp32 utilising esp-idf 4.4.4. I want to know is there a way to stop a ble mesh node to stop ble advertisements which can be shown in mobile phones while scanning for nearby bluetooth devices. When scanning, the mesh node is identified as "ESP_BLE_MESH" in the bluetooth scanner and I dont want it to be visible in the bluetooth scanner.
Can someone guide me as how to disable the ble advertisements of a ble mesh node?
PS: Stopping advertisements shouldn't affect my provisioning process. Its ble advertisements should only be disabled after provisioning as to avoid being visible in the bluetooth scanner

Hi, @sriha99
You can try disabling the BLE Mesh GATT Proxy Server in Component -> Config -> ESP BLE Mesh Support. to see if it meets your requirements.


[5.2] Cookies sent in test are not present in request.

Basically, I'm unable to test if controller accepts cookie no matter what i try.
Here's my test:
public function test_cookie_passed_to_request(){
    $cookie = cookie('name', 'value');
    $this->call('get', 'test', [], [$cookie]);
    $this->assertEquals('value', $this->response->content());
}

And here is the route:
Route::get('test', [
    'middleware' => 'web',
    function (\Illuminate\Http\Request $request) {
        return $request->cookie('name');
    }
]);

Test fails: expected "value", got "".
Discussion on laracasts for reference.

The route has the web middleware?

This is not a bug, but instead the cookie should be passed as an array of values, not as a Symfony\Component\HttpFoundation\Cookie instance. Test should be changed to read:
    public function test_cookie_passed_to_request(){
        $cookie = ['name' => Crypt::encrypt('value')];

        $this->call('GET', 'test', [], $cookie);

        $this->assertEquals('value', $this->response->content());
    }

Top tip. Avoid calling global functions inside tests. ;)

And I did some more digging:
$cookie1 = ['name1' => Crypt::encrypt('value1')];
$cookie2 = ['name2' => Crypt::encrypt('value2')];
$this->call('get', 'test', [], [$cookie1, $cookie2]);
$this->assertEquals('value1', $this->response->content());

That test fails.
And here is method definition from src:
public function call($method, $uri, $parameters = [], $cookies = [], $files = [], $server = [], $content = null)

It says $cookies and not cookie. Yet it accepts only one cookie and that one should be weirdly parsed.

as per my answer on the Laracasts thread, the cookies need to be set like:
    public function test_cookies_passed_to_request()
    {
        $cookies = [
            'name1' => Crypt::encrypt('value1'),
            'name2' => Crypt::encrypt('value2')
        ];
        $this->call('get', 'test', [], $cookies);
        $this->assertEquals('value1', $this->response->content());
    }

Here's the final solution.
The test:
public function test_cookie_passed_to_request()
{
    $this->disableCookiesEncryption('name');
    $cookie = [ 'name' => 'value' ];
    $this->call('get', 'test', [ ], $cookie);
    $this->assertEquals('value', $this->response->content());
}

The route:
Route::get('test', [
    'middleware' => 'web',
    function (\Illuminate\Http\Request $request) {
        return $request->cookie('name');
    }
]);

TestCase function to disable cookie encryption:
    /**
     * @param array|string $cookies
     * @return $this
     */
protected function disableCookiesEncryption($cookies)
{
    $this->app->resolving(EncryptCookies::class,
        function ($object) use ($cookies) {
            $object->disableFor($cookies);
        });

    return $this;
}

Working in 5.4

Thanks @asvae! Works perfectly in 5.6

Can we do it without creating routes?

Thank you.

->withCredentials(

That's what I needed, how did you figure that out, though?

Can we do it without creating routes?

Go ahead and use :
$_COOKIE["whatever_key"] = "whatever_value"

You can use that in your setup function and in teardown be sure to unset that, some stuff don't have nothing to do with Laravel 👍

This works for me in Laravel 8:
$this
    ->withCredentials() // turns out ->withCookies() doesn't work without this call
    ->withCookies([
        'hello' => 'world',
    ])
    ->postJson('/check')

thank you, still works in 2024

This works for me in Laravel 8:
$this
    ->withCredentials() // turns out ->withCookies() doesn't work without this call
    ->withCookies([
        'hello' => 'world',
    ])
    ->postJson('/check')

Thank you


Could not find a declaration file for module 'node-fetch'

Error

node_modules/booru/dist/Constants.d.ts:1:29 - error TS7016: Could not find a declaration file for module 'node-fetch'. '../node_modules/node-fetch/lib/index.js' implicitly has an 'any' type.
  Try `npm i --save-dev @types/node-fetch` if it exists or add a new declaration (.d.ts) file containing `declare module 'node-fetch';`

1 import { RequestInit } from 'node-fetch';
                              ~~~~~~~~~~~~

[17:32:57] Found 1 error. Watching for file changes.

package.json

{
  "devDependencies": {
     "@types/node-fetch": "^3.0.3"
  }
}

Looks like node-fetch bundles typings now so @types/typescript doesn't have any types anymore
I'll update node-fetch and update the package, but if you need the fix now (or can't update booru) you can install the older (working) types package npm i --save-dev<EMAIL_ADDRESS>

nevermind node-fetch changed to be ESM-only and that broke jest and some of my other tooling (see this issue)
i've published<EMAIL_ADDRESS>with dependency updates, but you'll have to pin<EMAIL_ADDRESS>yourself, if npm fails to install the right version
i'll likely move away from node-fetch in a later version if they don't add a non-ESM version, as moving to ESM might break a lot of things really badly for me


Broadcast Skript

This is my official broadcast skript!
Updates will be posted on my github skripts!
Feel free to use it in minehut!
Do you want to use this for servers outside minehut?
Please send me a message!
Enjoy!

People who want to use it for servers outside of Minehut must get permission from the author. If it is going to be used inside of the Minehut Network, no permission is necessary. Credit is required without permission inside of the Minehut Network, though. Anyway, merged the commit. Thank you for open-sourcing you Broadcast Skript.


Load org color at signup controller fixes #4719

This fixes #4719. @ethervoid CR this, please.

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

:+1:


Fixed OSS-issue-22664

Commit Message:
Additional Description:
The bug in
https://oss-fuzz.com/testcase-detail/5186283155750912 (or https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22664)
shows ASSERT(it.identifier().value() <= std::numeric_limits<uint16_t>::max());
Notice that identifier is defined in api/envoy/config/core/v3/protocol.proto as:
google.protobuf.UInt32Value identifier = 1
[ (validate.rules).uint32 = {lte: 65536 gte: 1}, (validate.rules).message = {required: true} ];
The value should range from 0 to 65535 instead of from 1 to 65536.
Because 65536 is greater than uint16::max, it triggers the assert to terminate the program.
The fix is to set it to {lte:65535 gte:0}, instead of {lte: 65536 gte: 1}
Risk Level: low
Testing:
Passed tests with existing corpus and this test case.
[Optional Fixes #Issue] OSS-22664
backup report:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22664
/cc @asraa
/cc @samkerner

Thanks! Was the regex change meant to be in this PR as well?

No! I'm sorry for that.

/cc @asraa I've cleared those irrelevant commits.


xinference.model.audio.whisper 64759 WARNING  Prompt for whisper transcriptions will be ignored:

Describe the bug
xinference.model.audio.whisper 64759 WARNING  Prompt for whisper transcriptions will be ignored:
When I call transcriptions API:
text = model.transcriptions(audio=audio_file.read(), language='chinese', prompt='xxxxxx')
Expected behavior
Hopefully it behaves as described in the api documentation.

Additional context
Add any other context about the problem here.

这个问题我也遇到了，有下文吗？

+1


Rebuild sys crate whenever STEAM_SDK_LOCATION changes

This PR makes cargo rebuild the sys crate whenever STEAM_SDK_LOCATION changes, which helps solve some of the issues from #37.
I also updated the crate to edition 2018 since that only required adding the appropriate line in the Cargo.toml and removing all extern <crane-name>s from lib.rs. I also removed libc from the sys crate since I don't think it was doing anything as its types were never re-exported.
Looking over the library as a whole, I think it would be fairly trivial to remove the libc dependency entirely in favor of relying on std types. I can add it to this PR or create a new one if this is desired.

Thanks!


Inline media playback not working. (?)

I'm submitting a ...

[x] bug report
[ ] feature request
[ ] documentation issue

Bug report
Current behavior:
After adding <preference name="AllowInlineMediaPlayback" value="true" />  to config.xml and also having both 'webkit-playsinline' & 'playsinline' tags in my html,
the videos are still being opened in fullscreen, without playing inline.
Expected behavior:
Videos should play in the inappbrowser instead of opening in fullscreen.
Steps to reproduce:
Create a new ionic project, add <preference name="AllowInlineMediaPlayback" value="true" />  to your config.xml, import this plugin along with wkwebview-engine, open a website (preferably your own, or one with the 'webkit-playsinline' & 'playsinline' tags already added to videos) with any html5 video in inappbrowser, then play the video.
Note: Tested on iPhone 5s (iOS 10.3), iPhone SE (iOS 11.3), iPhone 6 (iOS 11.4.1), iPhone 7 (iOS 12 dev). None of them played videos inline. This issue appeared after switching from UIWebView to WKWebView with this plugin; before that, the videos were playing inline as expected.
Any suggestions?
Thank you in advance. 😄

There were a couple of options which are present in the original UIWebView implementation and are also supported by the WKWebView preferences which hadn't been migrated and this included AllowInlineMediaPlayback. This should now work due to the above commit.

Awesome, it works now. Thank you! :)


Annotations preview on the job level

Motivation and context

This will be helpful for the annotator : bigger picture of their work and the sequences they annotated
This will be helpful for the QA: seeing and accessing specific moments and sequences, seeing the context for hard-to-detect errors
Component can be opened\closed when clicking on "Timeline" button on the right group.
Labels on the top can be clicked and enabled/disabled. Grey labels are disabled and not shown on the timeline. Colored are enabled and showed.
Frame numbers are clickable, when clicked - redirects to according frame number.
Change of the frame in frame input also changes the position of red column and vice versa.
How has this been tested?

It was tested manually
Demo

Checklist

[x] I submit my changes into the develop branch
[ ] I have added a description of my changes into the CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (see GitHub docs)
[ ] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

Hi, @PMazarovich
Thank you again for the contribution.
I believe it is an important feature we want, but it should be implemented another way as one more 2D canvas view  (see cvat-ui/src/components/annotation-page/canvas/views). UX scenarious and design shall be developed in advance. And I see some controversial moments during in the source code. I do not think we are ready to accept and support it now.
It would be very useful if you describe how you are using this feature in your work, what are typical use-cases, maybe some missed features not presented in this implementation, etc.

@PMazarovich , would you like to discuss how we can collaborate? Don't hesitate to contact as by contact at cvat.ai. We will be happy to discuss how to align our efforts and make CVAT better.

@PMazarovich , we are happy to collaborate. Let's close the PR because in the present state it will not be merged. Don't hesitate to contact us.


panic: flag provided but not defined

I would not like to see this garbage:
panic: flag provided but not defined: -b

goroutine 1 [running]:
main.main()
	./main.go:13 +0x45

Steps to reproduce: neogo -b

Duplicate of https://github.com/nspcc-dev/neo-go/issues/2886.


Implement simple lottery.

Content
Implement simple lottery's prove and verify functions. This PR doesn't have tests. Let's see what property tests will test and if it still makes sense to add other tests.
Pre-submit checklist

Branch

[x] Tests are provided (if possible)
[x] Commit sequence broadly makes sense
[x] Key commits have useful messages

PR

[x] No clippy warnings in the CI
[x] Self-reviewed the diff
[x] Useful pull request description
[x] Reviewer requested

Documentation

[x] Update README file (if relevant)
[x] Update documentation website (if relevant)

Issue(s)
Closes #69

I only planned to create an interface for the centralized setting. Let's work on the decentralized interface separately? I would be a different wrapper according to design doc. @rrtoledo

Sure let's do it in a separate PR.
As for the wrapper, we should reuse the existing code so we can see whether we should have 2 wrappers for centralised and decentralised settings in wrapper.rs or not.

@curiecrypt

Are you planning to add/enhance public function docs in another PR?

There is an open issue to do this for all files. #65 Not sure if I will have time this week though.

I would write a simple test function even though the protests will cover most of the cases.

I'm afraid that if I write a test, it would become obsolete when property tests are implemented. However, if they do not test something, I would be happy to revisit this!

Also, I saw a typo in file simple_lottery/init.rs line 27: bound_completess. FYI :)

Thanks, will make a PR with a fix.


Possible performance improvements

Class instances avoidance
I see much usage of the newkeyword.
I am uncertain but it appears as though it may also be used in hot spots( parser runtime) in the code and not only in one time initial definitions?
if that is indeed the case I suggest you try avoiding initializing class instances at parser runtime.
Plain objects ({}) if sufficient would be much faster.
Specific boolean conditions.
This is a minor thing but conditions  such as:
            if (!this.createsAstNode)

Will take longer than a more precise condition:
if (this.createsAstNode === false)

If these kind of conditions appear in enough hot spots in the code base
you may be able to squeeze a a tiny bit of extra performance.

Was this run on Chrome?
If so which version?
I see a slightly different ordering on latest stable chrome 59


pull request for e2e test at 11/10/2016 04:26:09

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.

Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


No sound

Sound does not seem to play, either when triggered or when I press "play". D2 Stats work fine.
Any way I can troubleshoot this?

I just tested it on my machine and there it works.
How is your volume-setting?
As shown in the picture below if you put the slider to the right it is set to 100%

Do you use custom sounds or the ones that come with the download?


I want to change to the five row, how to do?

U can't, there r 6 rows in some months, for example 2016-01

And there r 4 rows sometimes, for example 2015-02

Thanks.


This browser or app may not be secure

[x] I am on the latest Channels version.

[x] I have searched the issues of this repo and believe that this is not a duplicate.

Channels version: v0.2.0

OS version and name: macOS Catalina 10.15.3

Issue
I've downloaded the latest release.
On first run it asked for Google account, I've entered my email and password and had the screen (attached)

I'd also love to use this app, but I'm not able to use it because of the above issue.


Installation fail

Hi !
I have this error on installation,
npm ERR! Darwin 14.3.0
npm ERR! argv "node" "/usr/local/bin/npm" "i"
npm ERR! node v0.12.2
npm ERR! npm  v2.11.1
npm ERR! path /mypath/node_modules/glsl-fxaa/node_modules/glslify/node_modules/replace-method/node_modules/recast/node_modules/esprima/bin/esparse.js
npm ERR! code ENOENT
npm ERR! errno -2

npm ERR! enoent ENOENT, chmod '/mypath/node_modules/glsl-fxaa/node_modules/glslify/node_modules/replace-method/node_modules/recast/node_modules/esprima/bin/esparse.js'

I'm guessing you have to update the glslify dependency to 2.2.1 in your package.json ?
Cheers,

Thanks, I'll update this package to use<EMAIL_ADDRESS>Working on it now :+1:

Ok, fixed everything, updated to glslify2, modernized the demo and cleaned code up. Pushed to 3.0.0. Also published to gh-pages:
http://mattdesl.github.io/glsl-fxaa/demo/

That's awesome Matt thanks !

Just a heads up - eventually I plan to split this into two modules:
glsl-fxaa will just be a single function that targets the simplest use case
glsl-shader-fxaa will be a vertex / fragment shader "ready to go" with the most optimized version of this
This way both modules can be optimized and simplified. Right now it's a bit messy trying to support both use cases.

So you mean you won't provide texcoords in glsl-fxaa ?
In most use case it's better to use the method without having to bother about v_rgbNW, v_rgbNE etc...
Here's how I use it in my current post-processing workflow (i was porting another fxaa implementation before I stumbled on yours that fitted right into how i wanted to use it).
uniform sampler2D tInput;
uniform vec2 resolution;
uniform float time;
varying vec2 vUv;

#pragma glslify: vignette = require(./passes/vignette/vignette.frag)
#pragma glslify: brightness = require(./passes/brightness/brightness.frag)
#pragma glslify: contrast = require(./passes/contrast/contrast.frag)
#pragma glslify: film = require(./passes/film/film.frag)
#pragma glslify: fxaa = require(glsl-fxaa)

void main() {
  vec4 color = fxaa(tInput, vUv * resolution, resolution);
  color = vignette(color, 1.4, 2.3, resolution);
  color = brightness(color, 0.1);
  color = contrast(color, 0.68);
  color = film(color, vUv, time, 2048.0, 0.4, 0.3);

  gl_FragColor = color;
}

Yes the v_rgbNW stuff is annoying to use in practice. So most of the time it's easier just to use it like you are using there.
The "optimized" module would be used like this:
var vert = glslify('glsl-shader-fxaa/vert')
var frag = glslify('glsl-shader-fxaa/frag')
var fxaa = createShader(gl, vert, frag)

It wouldn't have all the weirdness of out function parameters so it would also be really easy to copy + paste if you want to inline it into your custom shaders for more optimization. (Or if you need a different setup for vertex inputs).


Improving embed output in the history channel

This always places the guild locale as the first field, making it more readable and will make you be able to follow the conversation.

Unfortunately, the field value is limited to 1024 characters, where as a discord message can be up to 2000 characters in length, forcing us to truncate up to half of the message, which would diminish the value of this channel.
The way the embed is currently is like that because of these restrictions. An improvement in the current form that I had thought about would be to put the target language version of the message as the standard message, and embed the english version, that way it's at least consistent.

Descriptions could have 2048 as a limit, so the important part (the guild language) will be the description, meanwhile the other could be split up.

Yeah, I would like it fully preserved.

anyone searching either in english or a translated language would find a thread that might help them
moderation. Having a message log is important after the channel expires.

Fields will still be inlined when it's short enough, as it's easier to read them side by side, at least it makes you be able to follow one language by sticking your eyes in just one side. As before, the primary locale of the server is at the left.

If any of the chunks is greater than 1024, then it will be have to split. This also includes code blocks, as code blocks being inlined will make it too thin to be actually be readable.


Add a top-level README, update contribution documentation

Also update the UI README to be more meaningful

Merging for now to have the structure in place. We'll refine this documentation moving forward.


Virtualservice with HTTPMatchRequest doesn't work as expected

We have 2 releases of same API  (test-api), and we want to create virtualservice which sits infront of this and redirects traffic depending on the matching label( like x-api-version ). It always matches the first rule and does the routing, it never considers sencond condition.
`helm list -n sandpit | grep test
test-api-1-x                            sandpit         1               2021-05-03 16:19:00.447819131 +0800 AWST        deployed        example-api-2.0.3              1.0.0
test-api-2-x                            sandpit         1               2021-05-03 16:18:25.62379665 +0800 AWST         deployed        example-api-2.0.3              1.0.0

kubectl get all -n sandpit | grep test
pod/test-api-1-x-67486fd946-8n569                                     2/2     Running            0          47h
pod/test-api-2-x-69d48b8778-xdk2h                                     2/2     Running            0          47h
service/test-api-1-x                              ClusterIP      <IP_ADDRESS>   <none>          80/TCP    47h
service/test-api-2-x                              ClusterIP      <IP_ADDRESS>   <none>          80/TCP    47h
service/test-stuff                                ExternalName   <none>           google.com.au   <none>    243d
deployment.apps/test-api-1-x                              1/1     1            1           47h
deployment.apps/test-api-2-x                              1/1     1            1           47h
replicaset.apps/test-api-1-x-67486fd946                              1         1         1       47h
replicaset.apps/test-api-2-x-69d48b8778                              1         1         1       47h
horizontalpodautoscaler.autoscaling/test-api-1-x                              Deployment/test-api-1-x                              34%/75%, 5%/50%                1         5         1          47h
horizontalpodautoscaler.autoscaling/test-api-2-x                              Deployment/test-api-2-x                              30%/75%, 4%/50%                1         5         1          47h

 kubectl get vs -n sandpit | grep test
test-api-1-x                                              [api-gateway]                                      [snd.api.example.com.au]                                                                                47h
test-api-1-x-virtualbackdoor                              [api-gateway-one-way-tls]                          [snd.api.example.com.au]                                                                                47h
test-api-2-x                                              [api-gateway]                                      [snd.api.example.com.au]                                                                                47h
test-api-2-x-virtualbackdoor                              [api-gateway-one-way-tls]                          [snd.api.example.com.au]                                                                                47h
test-route                                                                                [test]                                                                                243d
test-vs-master                                            [api-gateway]                                      [snd.api.example.com.au]                                                                                102m

kubectl get dr -n sandpit | grep test
test-api-destination-1-x                         test-api-1-x                                      7d
test-api-destination-2-x                         test-api-2-x                                      7d

Destination Rule 1
kubectl describe dr test-api-destination-1-x -n sandpit
Name:         test-api-destination-1-x
Namespace:    sandpit
Labels:       <none>
Annotations:  <none>
API Version:  networking.istio.io/v1beta1
Kind:         DestinationRule
Metadata:
  Creation Timestamp:  2021-04-28T07:09:02Z
  Generation:          1
  Resource Version:    103251300
  Self Link:           /apis/networking.istio.io/v1beta1/namespaces/sandpit/destinationrules/test-api-destination-1-x
  UID:                 a5a06267-90ef-4f4d-af0e-ace9f73c52fb
Spec:
  Host:  test-api-1-x
  Subsets:
    Labels:
      App:  test-api-1-x
    Name:   v1
Events:     <none>

Destination Rule 2

kubectl describe dr test-api-destination-2-x -n sandpit
Name:         test-api-destination-2-x
Namespace:    sandpit
Labels:       <none>
Annotations:  <none>
API Version:  networking.istio.io/v1beta1
Kind:         DestinationRule
Metadata:
  Creation Timestamp:  2021-04-28T07:09:07Z
  Generation:          1
  Resource Version:    103251318
  Self Link:           /apis/networking.istio.io/v1beta1/namespaces/sandpit/destinationrules/test-api-destination-2-x
  UID:                 95970845-a198-4e01-9ae3-69efa51b9388
Spec:
  Host:  test-api-2-x
  Subsets:
    Labels:
      App:  test-api-2-x
    Name:   v2
Events:     <none>

Virtual Service
kubectl describe vs "test-vs-master" -n sandpit
Name:         test-vs-master
Namespace:    sandpit
Labels:       <none>
Annotations:  <none>
API Version:  networking.istio.io/v1beta1
Kind:         VirtualService
Metadata:
  Creation Timestamp:  2021-05-05T05:43:38Z
  Generation:          6
  Resource Version:    106253417
  Self Link:           /apis/networking.istio.io/v1beta1/namespaces/sandpit/virtualservices/test-vs-master
  UID:                 d1513923-4af0-425c-8a37-806579185d72
Spec:
  Gateways:
    api-gateway
  Hosts:
    snd.api.example.com.au
  Http:
    Match:
      Headers:
        X - API - Version:
          Exact:  1.0
      Uri:
        Prefix:  /test-api/
    Route:
      Destination:
        Host:    test-api-1-x
        Subset:  v1
    Match:
      Headers:
        X - API - Version:
          Exact:  2.0
      Uri:
        Prefix:  /test-api/
    Route:
      Destination:
        Host:    test-api-2-x
        Subset:  v2
Events:          <none>`

Affected product area (please put an X in all that apply)
[ ] Docs
[ ] Installation
[ X ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
It should check both the condition and direct traffic accordingly to individual subset/hosts
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
 istioctl version --remote client version: 1.9.4 control plane version: 1.6.5-f508fdd78eb0d3444e2bc2b3f36966d904c5db52 data plane version: 1.6.5 (67 proxies)
kubectl version --short Client Version: v1.21.0 Server Version: v1.16.13 WARNING: version difference between client (1.21) and server (1.16) exceeds the supported minor version skew of +/-1
helm version --short v3.5.4+g1b5edb6
How was Istio installed?
Environment where the bug was observed (cloud vendor, OS, etc)
AKS
Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.

Anyone have their valuable inputs to pass on this ?

Below virtual service works , sharing in case if someone stumbles.
`apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
name: test-vs-master
namespace: sandpit
spec:
gateways:

api-gateway
hosts:
snd.api.example.com.au
http:
match:

headers:
x-version-api:
exact: "1.0"
ignoreUriCase: true
uri:
prefix: /test-api/
name: match v1
route:
destination:
host: test-api-1-x
subset: v1

match:

headers:
x-version-api:
exact: "2.0"
ignoreUriCase: true
uri:
prefix: /test-api/
name: match v2
route:
destination:
host: test-api-2-x
subset: v2

route:

destination:
host: test-api-2-x
subset: v2`

Thanks


Added Capacitor Calculator

fixes #701

You have added Capacitor Calculator but screenshots of 5 Band Resistor is present in the PR description.
Also, don't change the PR template. Fill all the details that is asked properly.

Why file name is index.html.html, pls submit your PR properly, don't be in rush. Separate your styling in style.css file and logic in script.js file inside that folder only @AkhilaSunesh


add NumberFormat tryParse and test

add tryParse (wrap Parse)
add tests

related issue https://github.com/dart-lang/i18n/issues/191
origin pr https://github.com/dart-lang/intl/pull/577

Do I just add it to https://github.com/dart-lang/i18n/blob/main/pkgs/intl/CHANGELOG.md#0181-dev?
I see that 0.18.1 has already been released.

Sorry about that, #635 should fix this - please wait until it is merged, or rebase onto that branch.
Thanks for going through the hassle of refiling the PRs!


Escape sequence inserted around prompt when starting tmux in an ssh session

Windows Terminal version
1.11.3471.0
Windows build number
10.0.19044.0
Other Software
OpenSSH_8.1p1 for Windows,
Hyper-V VM running Debian testing/bookworm
GNU bash, version 5.1.16
tmux 3.2a
Steps to reproduce
Start Windows Terminal
Connect to Linux VM using ssh.exe
In bash, start tmux
Expected Behavior
First line / prompt displays:
simon@debian:~$

Actual Behavior
First line / prompt displays:
^[[>0;10;1csimon@debian:~$ 0;10;1c

Note: this works OK with Powershell instead of Windows Terminal. Haven't verified any other terminal emulators, but I'm pretty sure that it works OK in PuTTY as well.
There are few bug tickets in other projects, like https://github.com/microsoft/WSL/issues/5931, but in my scenario it seems Windows Terminal is the culprit - hence the ticket here

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #11204 for more discussion.
/dup #11204


Better message when not enough nodes with sufficient disk space for a volume

Fixes #507
Sample output
➜  out git:(master) ✗ ./kismatic volume add 100 -r 1

Validating==========================================================================
Reading installation plan file "kismatic-cluster.yaml"                          [OK]
Validating installation plan file                                               [OK]
Validating SSH connectivity to nodes                                            [OK]

Add Persistent Storage Volume=======================================================
Add Gluster Volume                                                              [ERROR]
- Task: verify we have enough storage nodes for the requested volume
  worker001: Not enough nodes with sufficient disk space for the requested volume. Required: 1 Available: 0.[ERROR]
error adding new volume: error running playbook: error running ansible: exit status 2

LGTM!


v0.68.0 Inference bug with optional types

I am running into an issue with flow v0.68.0 as demonstrated here:
https://flow.org/try/#0PTAEAEDMBsHsHcBQBLAtgB1gJwC6hwJ7oCmoA3qAMKwawB2xdOAKkcQDSgCi0xqjOAApZY6AM6gAvqEgjUoAORZiAQwDGOBQG4UtXKABUoFRIBKqjTLmLl6zTsQATYmugrl+NqACyK9AGUcFRxiZlhhUTEAHlN-QQAuUAB5ACMAKxccTn9mAEFmLkTUjI0APlAAXlAACjEgkMSc-K4ASkry2MEdZ1d3UmIAD0x9SABXOg1kelA1egYNKOpURKXMBiZWEiiDUs5OovTM7LyCg5KcUurEUFBUP0Dg0PCRcUTfAPqniPEYuOPm0qIFqJaqzWjrHArGhtCrlVb0ASbYhRAAkABFkJBIFEeHwBN9oktdqBOqVSg5EIQSKACZVyKIcFM6CpoAA1FmjYgAfkSdSwyDoAHNJDpemIJEtQIMQnRHGYLDgAHTwiFRAnlMjXUDKWXELDVNqam43ZQ4UZYOigKKOZAAN1KZBwAAtkGJFegXm6GUyWezoJzJFFgDb7TobpJEBHELM6HVbvdPmFaVVap8YRqtabzZajcbvfRfRziIkAETMYh1EtaiMixDR+hx6h0eYhRx0mMt6p3D6PJOelrVJYtByLOaZYht4DkxBAA
Basically flow is incorrectly inferring the type as undefined when then then optional type should be (undefined | string)
Related issue in flow-typed: https://github.com/flowtype/flow-typed/issues/1997

Confirming it's still present in 0.70

is this a problem with $Diff?

Closing since '*' is removed and that's likely the one causing issue