Exception when trying to use Ammonite REPL

// build.sbt

name := "test-repl"

version := "1.0"

scalaVersion := "2.11.5"

libraryDependencies += "com.lihaoyi" %% "ammonite" % "0.1.6"

libraryDependencies += "com.lihaoyi" %% "ammonite-repl" % "0.1.6"

initialCommands in console := "ammonite.repl.Repl.main(null)"

#Command Line

jon$ sbt console
[info] Loading project definition from /Users/jon/code/test-repl/project
[info] Set current project to test-repl (in build file:/Users/jon/code/test-repl/)
[info] Starting scala interpreter...
[info]
java.lang.AbstractMethodError
  at scala.tools.nsc.backend.JavaPlatform$class.$init$(JavaPlatform.scala:22)
  at ammonite.repl.interp.Compiler$$anon$1$$anon$6.<init>(Compiler.scala:70)
  at ammonite.repl.interp.Compiler$$anon$1.platform$lzycompute(Compiler.scala:70)
  at ammonite.repl.interp.Compiler$$anon$1.platform(Compiler.scala:70)
  at scala.tools.nsc.interactive.Global$$anon$8.<init>(Global.scala:401)
  at scala.tools.nsc.interactive.Global.loaders$lzycompute(Global.scala:399)
  at scala.tools.nsc.interactive.Global.loaders(Global.scala:399)
  at scala.tools.nsc.Global$GlobalMirror.rootLoader(Global.scala:65)
  at scala.reflect.internal.Mirrors$Roots$RootClass.<init>(Mirrors.scala:307)
  at scala.reflect.internal.Mirrors$Roots.RootClass$lzycompute(Mirrors.scala:321)
  at scala.reflect.internal.Mirrors$Roots.RootClass(Mirrors.scala:321)
  at scala.reflect.internal.Mirrors$Roots$EmptyPackageClass.<init>(Mirrors.scala:330)
  at scala.reflect.internal.Mirrors$Roots.EmptyPackageClass$lzycompute(Mirrors.scala:336)
  at scala.reflect.internal.Mirrors$Roots.EmptyPackageClass(Mirrors.scala:336)
  at scala.reflect.internal.Mirrors$Roots.EmptyPackageClass(Mirrors.scala:276)
  at scala.reflect.internal.Mirrors$RootsBase.init(Mirrors.scala:250)
  at scala.tools.nsc.Global.rootMirror$lzycompute(Global.scala:74)
  at scala.tools.nsc.Global.rootMirror(Global.scala:72)
  at scala.tools.nsc.Global.rootMirror(Global.scala:40)
  at scala.reflect.internal.Definitions$DefinitionsClass.ObjectClass$lzycompute(Definitions.scala:257)
  at scala.reflect.internal.Definitions$DefinitionsClass.ObjectClass(Definitions.scala:257)
  at scala.reflect.internal.Definitions$DefinitionsClass.init(Definitions.scala:1391)
  at scala.tools.nsc.Global$Run.<init>(Global.scala:1216)
  at scala.tools.nsc.interactive.Global$TyperRun.<init>(Global.scala:1208)
  at scala.tools.nsc.interactive.Global.newTyperRun(Global.scala:1231)
  at scala.tools.nsc.interactive.Global.<init>(Global.scala:297)
  at ammonite.repl.interp.Compiler$$anon$1.<init>(Compiler.scala:68)
  at ammonite.repl.interp.Compiler.<init>(Compiler.scala:68)
  at ammonite.repl.interp.Interpreter.init(Interpreter.scala:23)
  at ammonite.repl.interp.Interpreter.<init>(Interpreter.scala:55)
  at ammonite.repl.Repl.<init>(Repl.scala:11)
  at ammonite.repl.Repl$.main(Repl.scala:73)
  ... 39 elided
Welcome to Scala version 2.11.5 (Java HotSpot(TM) 64-Bit Server VM, Java 1.8.0_25).
Type in expressions to have them evaluated.
Type :help for more information.

scala>

Hmm try scala 2.11.4 or Java 8? Those are the things that come to mind

Yes, It works on 2.11.4
Does it work on 2.10.4? I had a resolution problem.

Doesn't work with 2.10.4

Maybe at some point I'll cross publish; for now 2.11.4 it is ^_^

I also experience this issue, scala version is 2.11.4 and java version is 1.8.0_25.

@jchayat @jarandaf  The latest version is cross-published, the older ones don't. Have you tried that?

@jarandaf @lihaoyi Binary incompatibilities in the scala-compiler JAR are quite common, I ran into one between 2.10.4/2.10.5 (macro related methods that changed), there are also some in 2.11 (2.11.2 vs 2.11.4 or 5 for sure, ran into it with the spark repl jar). Using the exact same version as ammonite should be recommended.

@alexarchambault should we cross-publish Ammonite against different minor versions of Scala? How does one even do that? Presumably it's possible

@lihaoyi  shapeless is doing it with scala 2.10 (see https://github.com/milessabin/shapeless#shapeless-210), but it's cumbersome for its users.  You could just recommend to use the latest scala version.

To go the cross publishing route, it should just be a matter of adding
crossVersion := CrossVersion.full

crossScalaVersions := (0 to 5).filterNot(3.==).map(i => s"2.11.$i") ++ ...

in build.sbt, and for the users, use
"com.lihaoyi" %% "ammonite-..." % "..." cross CrossVersion.full

as a dependency instead of just
"com.lihaoyi" %% "ammonite-..." % "..."

(after-thought: not that cumbersome)

Using same scala version as Ammonite seems to solve the problem (or at least, the REPL starts). I am facing another problem now (see #35), probably not directly related.

Fixed in 0.2.8


channelId parameter should be omitted when not needed

If channelId parameter is omitted in getDeviceCameraStatus and setDeviceCameraStatus when for enableType with scope device.
This will fix issues reported in https://github.com/user2684/imou_life/issues/82

What I have found in the API documentation about channelId is something about NVR. But could it also be that devises with two lenses/cameras uses the channelId?
Any way I have now sorted out the mess in my form. If you would like to see a suggestion to solve it you can find it here:
https://github.com/user2684/imouapi/compare/master...Strixx76:imouapi:remove-channelid
If you think that is a good solution I can make a pull request.

@Strixx76 I like your approach. let me see if I can refactor it together with another couple of changes I need to do in the short term and I'll come back to you. Many thanks!

Could I also the suggest that you change so that the "sensors" gets updated asynchronous?
If you change the for-loop in ImouDevice.async_get_data to use asyncio.gather() you will speed up things. That will also do that the sensors not failing will be updated. Now the loop breaks when one of the sensor fails to update. You could of course instead simply catch all exceptions here and log them like I did to be able to find out what was casing the bug.


Feature/add modal components

Codecov Report

Merging #18 (5f8bd3e) into develop (19f6aec) will decrease coverage by 0.00%.
The diff coverage is 99.69%.

@@             Coverage Diff             @@
##           develop      #18      +/-   ##
===========================================
- Coverage    99.74%   99.73%   -0.01%
===========================================
  Files           19       23       +4
  Lines         1565     1890     +325
  Branches        59       68       +9
===========================================
+ Hits          1561     1885     +324
- Misses           4        5       +1

Impacted Files
Coverage Δ

src/components/HOC/Backdrops/Backdrop.tsx
98.94% <98.94%> (ø)

src/components/Cards/Card.tsx
100.00% <100.00%> (ø)

src/components/Drawers/Drawer.tsx
100.00% <100.00%> (ø)

src/components/Modals/Modal.tsx
100.00% <100.00%> (ø)

src/styles/keyframes.ts
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Documentation: Fixes ReadManyItemsStreamAsync example

Updated ReadManyItemsStreamAsync example code snippet with proper working code to fix 3033
Pull Request Template
Description
Please include a summary of the change and which issue is fixed. Include samples if adding new API, and include relevant motivation and context. List any dependencies that are required for this change.
Type of change
Please delete options that are not relevant.

[] Bug fix (non-breaking change which fixes an issue)
[] New feature (non-breaking change which adds functionality)
[] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[] This change requires a documentation update

Closing issues
To automatically close an issue: closes #IssueNumber

/azp run


Bump up native SDK versions

Summary

Bump up to latest iOS and Android version
Motivation

Testing

[ ] Added tests
[ ] Modified tests
[x] Manually verified

Screenshots

Before
After

before screenshot
after screenshot

@stripe/stripe-identity-observers


only 20% mIou

Thanks for a great job!
I am a student who is following your job. All of my operations are based on  README.md, however , I got very strange mIou, about 20%.
I download the trained model from Github and the test result is normal, about 76.5%. The results mean that the testing process was fine. I also changed the pre-trained model to resnet101 which is trained on ImageNet. The result always about 20%. Sadly, I couldn't find any problem during training.
My PyTorch version is 1.7. I want to know if the PyTorch version will affect my results. when I training, I just changed the IMAGE.SIZE.TRAIN=289,257 ....
The following result is that IMAGE.SIZE.TRAIN=289, GPU 1 3060, pre-trained model = deeplabv2_resnet101_msc-vocaug-20000.pth.
{
"Class IoU": {
"0": 0.7948632887014013,
"1": 0.3304257442805647,
"2": 0.11077134876825119,
"3": 0.07046620852376487,
"4": 0.10895940525580272,
"5": 0.04745116392110705,
"6": 0.31005641398703143,
"7": 0.2915453936066487,
"8": 0.23258285017371,
"9": 0.005347773696150551,
"10": 0.10445717208326169,
"11": 0.10978767179703398,
"12": 0.18345830368166063,
"13": 0.12426651067058993,
"14": 0.2462254036792113,
"15": 0.415199601472948,
"16": 0.050153233366977974,
"17": 0.15261392666663348,
"18": 0.02888480390809123,
"19": 0.27664375976635347,
"20": 0.13747916669502674
},
"Frequency Weighted IoU": 0.6421553231368009,
"Mean Accuracy": 0.2748884341598109,
"Mean IoU": 0.1967447211762962,
"Pixel Accuracy": 0.7687984741459604
}
If you could give me some advice, I will appreciate you very much! thank you!
Best wishes to you!

OK, I will check my codes with the latest PyTorch.
I'm a bit confused about the weights you used for evaluation. Could you clarify the following points?

Trained by yourself?
How you used deeplabv2_resnet101_msc-vocaug-20000.pth?

OK, I will check my codes with the latest PyTorch.
I'm a bit confused about the weights you used for evaluation. Could you clarify the following points?

Trained by yourself?
How you used deeplabv2_resnet101_msc-vocaug-20000.pth?

Thanks for your quick reply!
I trained by myself when I used 'deeplabv2_resnet101_msc-vocaug-20000.pth' as a pre-trained model. I used the trained model as the pre-trained model because I wanted to find the wrong place.   Luckily, When I changed 'model. base.load_state_dict(state_dict, strict=False)' to 'model.load_state_dict(state_dict, strict=False)' in main.py, I solved the problem, and I got the normal results, about 77%.
Although I solved the problem, I don't know the reason. If you know the reason, can you explain it to me? Thank you very much!
Best wishes to you!

It's because of the inconsistency of parameter names.
The parameter names of deeplabv2_resnet101_msc-vocaug-20000.pth begin with the term "base" because of libs.models.msc.MSC class. Therefore, model.base.load_state_dict(state_dict, strict=False) loads nothing (see with strict=True). model has "base" while model.base does not.
import torch
state_dict = torch.load("deeplabv2_resnet101_msc-vocaug-20000.pth")
print(*state_dict.keys(), sep="\n")
# base.layer1.conv1.conv.weight
# base.layer1.conv1.bn.weight
# ...

On the other hand, the default pre-trained model deeplabv1_resnet101-coco.pth does not contain "base", which is converted from the official Caffe weights.

Thank you very much for your detailed explanation.
Best wishes to you!
---Original---
From: "Kazuto @.>
Date: Fri, Mar 26, 2021 10:10 AM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [kazuto1011/deeplab-pytorch] only 20% mIou (#100)
It's because of the inconsistency of parameter names.
The parameter names of deeplabv2_resnet101_msc-vocaug-20000.pth begin with the term "base" because of libs.models.msc.MSC class. Therefore, model.base.load_state_dict(state_dict, strict=False) loads nothing (see with strict=True). model has "base" while model.base does not.
import torch state_dict = torch.load("deeplabv2_resnet101_msc-vocaug-20000.pth") print(*state_dict.keys(), sep="\n") # base.layer1.conv1.conv.weight # base.layer1.conv1.bn.weight # ...
On the other hand, the default pre-trained model deeplabv1_resnet101-coco.pth does not contain "base", which is converted from the official Caffe weights.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Google Search Console says: Incorrect namespace

I'm using PS <IP_ADDRESS>
As I say in the subject Google Search Console returns these errors:

Sitemap index can be read, but has errors
Your Sitemap or Sitemap index file doesn't properly declare the namespace. Line: 2

The problem is only with the Index, the child sitemaps (one for each language) seems to be accepted correctly.

Fixed here: https://github.com/PrestaShop/gsitemap/pull/60


The demo link is not loading

This demo link isn't working, just showing "Loading, please wait..." forever.

I have the same problem too.
I am using the iPad Air  (4th gen) ios 15.4

same from samsung galaxy note 9 and windows pc... always loading please wait

Doesn't work on my Mac or iPhone either

Updated with a new link in the Readme see commit https://github.com/AR-js-org/AR.js/commit/8609ac9689e0e9a4c0bfc44ea6ca7ae795b1da81


[WIP] Update Chart to Cortex 0.3.0

Closes #6 #9 #2 #10

Is this still relevant now that #25 is merged?

No, I don't think it is. I'm going to close it.


Added thresholds configuration for zones

Description:
This adds thresholds definition for Zone entities, so that zones can filter GPS coordinates based either on the accuracy or on circles intersection. The latter works as a minimum portion of accuracy circle area intersecting with zone circle.
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#9350
Example entry for configuration.yaml (if applicable):
zone:
  - name: home
    latitude: !secret home_latitude
    longitude: !secret home_longitude
    icon: mdi:home
    radius: 100
    area_threshold: 0.5
  - name: office
    latitude: !secret office_latitude
    longitude: !secret office_longitude
    icon: mdi:server-network
    radius: 50
    accuracy_threshold: 25

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

This should not be added to zones. It's not a zone concern. The values can differ from check to check, and so can't be attached to a zone. This could be added to the in_zone check.

Hi, @balloob .
I'm not sure I get your comment correctly.
The checks itself are added to in_zone routine. The thresholds config is put into zone entity.
Do you see an alternative entity to put thresholds values to?

Thresholds should not be stored in the zone, as each check against a zone might require differents thresholds.


chore(deps): bump jscodeshift to 0.15.0

Issue
Refs: https://github.com/facebook/jscodeshift/commit/e0afeedbf6b1cc364d1e01a303d2817c6827c025
Description
Bumps jscodeshift to 0.15.0
Testing
CI

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Diff in jscodeshift: https://github.com/facebook/jscodeshift/compare/v0.14.0...v0.15.0


Lianalite login

This PR introduce the new login to the remote backend.
The choice of the used backend is defined per wallet.
The authentication credentials for the remote backend are stored in the settings.json file.
In the installer
The choice between two different backends is  showned to the user that can choose to authenticate to the remote backend or use the local bitcoind.
Between the launcher and the app a new temporary panel: login.
This intermediary state after the choice of network datadir from the user, is used to connect to the remote backend if the wallet information in the settings.json file contains the credentials for the remote backend authentication otherwise the launcher redirects directly to the App state with the embedded daemon running.

Maybe we should make the token more visible in the login email:

(line return + centered + highlight)

here the backgroud color of the buttons don't change on hover:

here maybe we should no display "lianad v" if we connect on remote backend:

i got this once, same issue w/ all mail addresses (w/ or w/o already created wallet on theses addresse), i cannot reproduce after restart liana:

it happen if i try creating a mainnet wallet

It is because LianaLite mainnet website is not yet running. GUI is looking at lianalite.com/api/env to get to which backend it should communicate with.

Lite mainnet website is not

will LianaLite backend run before v7 release?

will LianaLite backend run before v7 release?

Yes, this is the goal


Fix code scanning alert - Overly permissive regular expression range

Tracking issue for:

[x] https://github.com/JDsProjects/JDBot/security/code-scanning/1

Solved

Actually fixed, good to go


Use XDG Base Directory specification in installation files

Motivation
The installation scripts assume $HOME as the default directory to store foundry files. This is not wrong, but we are defiling the $HOME directory.
Some users might have proper configurations so that application-specific data is stored somewhere else logically.
We should follow XDG Base Directory specification.
Solution
Following XDG Base Directory specification, this kind of data should be in $XDG_DATA_HOME.
This PR updates the installation scripts to use this variable instead of $HOME,

I don't know if XDG_*_* env vars are set on all platforms like HOME is. Besides this should probably be XDG_CONFIG_HOME instead of DATA.
Rust's Cargo package manager uses $HOME/.cargo or %USERPROFILE%\.cargo for binaries and the package registry, which I believe is what we were going for initially

@mattsse forgot to default to home

@DaniPopes Yes, this should probably go to the $XDG_CONFIG_HOME. With a $BASE_DIR we can default to $HOME if $XDG_CONFIG_HOME var doesn't exist.

okay, this seems totally fine tested with no xdg setting

If we are going to follow the spec, why not also follow it for CACHE as well?

CACHE_DIR="${XDG_CACHE_HOME:-$HOME/.cache}/forge/<rpc cache, or solc cache, or whatever"


Suggestion: Add documentation

The lines and thing are mostly intuitive, but it would be nice to have a full set of documentation describing what the lines do, what they mean, and how the bot reacts. I know this is very time consuming, but might be nice to do in your free time.

Like I have trouble understanding in the new version what all the circles around the blobs do. I would assume that they are possible attach areas and the bot should avoid/get out of them. But I am confused about the orange zones around viruses and the red one around the player himself.

The lines are mostly for debugging purposes, they change every time I feel like it. The circles right now are the splitting range. If you're inside a red circle, the enemy can split on you for sure. The orange circles are the threat circles of enemies that cannot split, the current size is just a political choice.
You can also see [red - orange] arcs around the player, they show which enemies are marked as current threats. The green arcs are just areas which have the property of never pointing towards an enemy, if you travel towards green areas, you should be safe. In the current version though, green areas are not computed correctly which means the bot will sometimes run into enemies trying to go towards the green.

I like the lines, the bot isn't very interesting (to me) without them, just a blob moving around the screen. I think they should be more than a debugging feature, but that's just me. And why do the green arcs disappear when there are no threats? Seems like an inconsistency to me. What about the giant pink circle around the player? What does that do?

And what are those red dots that look like they are being shot out of the player? At some points they show the outer bounds of an enemy, but at other times, they just float around like they are being shot.

Of course, I keep the good looking lines. The current version looks pretty good for example. And I pay good attention to the way that they are rendered.
I've updated the red dot to be better, pushing next version right now.

Yes, but what is the red line around the player do? My curiosity is killing me!!! And are the tiny yellow circles randomly around the map possible target points to track to?

I responded to that earlier, and a single yellow dot is just a group of food. Instead of taking all the dots one by one, you can just travel to the middle of them.

Related : We should remove the dot under the mouse. It's unusefull (afaik) and annoying. I mean, the user know where his mouse is, right ?

@FliiFe What dot ? the yellow one ?


Dots format 🟢🟡🔴

New dots format with 🟢🟡🔴 discussed in #11 • here.
Now that the format is changed genJson.pl file doesn't work anymore, I don't know Perl so I'm not able to fix it. If necessary I will open a new issue for that.
I was also thinking about that with GitHub pages it's possible to open an endpoint here on GitHub and with a JS script, the abbr.json file will be retrievable by a URL like an API.
After all, I also recommend adding a CHANGELOG.md to track progress and add a license.

Wow, I think that looks cool. Now, arguably, the "-" in front of an abbreviation is not even needed any more, because the coloured dots seemingly serve as bullet points

Thank you.
I agree with u but there's a problem.
However dashes are used to display the markdown format as I can understand of Perl they are used in the genJson.pl file to separate the line with the "-" char.

Wow, it really looks great! I agree that we need to keep the dashes for markdown.
Do you agree with MIT license?
Similarly to JSON we could generate an index.html file too and GitHub pages could display it. The best would be to run [genJson.pl](https://github.com/kisvegabor/abbreviations-in-code/blob/master/genJson.pl) in CI.

Thanks,
Yes the MIT license would be great.
And the site is a great idea. Having the JSON file with JS is easy to generate an HTML without using the genJson.pl

Thanks,
Yes the MIT license would be great.
And the site is a great idea. Having the JSON file with JS is easy to generate an HTML without using the genJson.pl

Or directly from the md use a website that compile in HTML.

Yes the MIT license would be great.

Added.

And the site is a great idea. Having the JSON file with JS is easy to generate an HTML without using the genJson.pl

Once genJson.pl is generating the JSON file it could easily add <li> elements to a HTML files too.

Or directly from the md use a website that compile in HTML.

Using genJson.pl seems simpler to me. One script -> less maintenance

👍

Cool, merging. Thank you!


chewie isnt dislayed when apk built

when i run my application with android studio everything is fine and working, but when i build the apk and install it on my phone and other phones the player doesnt display the video.
are there any requirements for building?
note: I have internet permission in android manifest.

I am also got same issue in some devices, after install apk player widget not displayed. Only displayed video link win white empty widget ?

I am also got same issue in some devices, after install apk player widget not displayed. Only displayed video link win white empty widget ?

Same issue
Would suggest you build it in profile mode to solve the issue. It works in that case.
flutter build apk --profile

Same issue
Would suggest you build it in profile mode to solve the issue. It works in that case.
flutter build apk --profile

updated android example project and tested it with newest versions. Please try again guys and let me know 👍. Follow this PR for actual fixes: https://github.com/brianegan/chewie/pull/475

I have the same problem

I have the same problem


quic: Use GRO for reading packets from the UDP socket in upstream QUIC

This behavior is guarded by the runtime flag envoy.restart_features.prefer_udp_gro.
We previously turned off GRO in EnvoyQuicClientConnection because we weren't sure about the performance (see
https://github.com/envoyproxy/envoy/pull/19088). However, kernel experts have recommended using GRO over recvmmsg as a much more CPU efficient solution for reading multiple UDP packets into a single buffer.
This change also enables setting the option of whether recvmmsg should be used or not, so we can
disable it for client connections, while keeping it for listener sockets.
Risk Level: low (can be turned off with the runtime guard)
Testing: unit tests
Release Notes: included
Runtime guard: envoy.reloadable_features.prefer_udp_gro

@alyssawilk still haven't found a good way to write tests for this PR, relied on running existing tests so far

I can also default it to _FALSE and only enable in Envoy Mobile for starters, though I don't think based on usage patterns that this is a high risk change

two thoughts for testing. You can see if any tests which include a real EnvoyQuicClientConnection can have the TestThreadsafeSingletonInjector added. Even if the test fast-fails you can do an EXPECT_CALL(os_sys_calls_, recvmsg like test/common/quic/quic_io_handle_wrapper_test.cc does, since I believe with the flag false we'd recvmmsg. Alternately there's an expect log message macro somewhere and you could see if any unit tests have an increased level of "starting gro recvmsg with..." logs

I added a test in envoy_quic_client_session_test that mocks the recvmsg, and makes sure recvmsg is called and recvmmsg is not called

LGTM modulo addressing Dan's flag concerns /wait

Done, ready for another round of review

/retest

/retest

/retest

/retest

/retest

thanks for the reviews everyone!


Azure Services Tutorial

New "Azure Services" Tutorials covering as part of the HoloLens 2 tutorial series.

Azure Storage

Azure Cognitive services > Custom Vision

Azure Spatial Anchors

Azure ChatBot and Language Understanding (LUIS) services

Docs Build status updates of commit 92bcc8f:
: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-azure-02.md
:warning:Warning
View
Details

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

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

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

mixed-reality-docs/mrlearning-azure-03.md
:warning:Warning
View
Details

mrtk-docs/index.md
:warning:Warning
View
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

mixed-reality-docs/images/mr-learning-azure/tutorial1-section4-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section5-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section5-step1-2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section5-step1-3.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section6-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section6-step1-2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section6-step1-3.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section6-step1-4.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section6-step1-5.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section7-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section7-step1-2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section7-step1-3.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial2-section4-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial3-section4-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial3-section4-step1-2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial3-section4-step1-3.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial3-section4-step1-4.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial4-section1-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial4-section1-step2-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial4-section1-step3-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section4-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section4-step1-2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section4-step1-3.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section4-step1-4.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section4-step1-5.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section4-step1-6.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section5-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section5-step1-2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section6-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section6-step1-2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section6-step1-3.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section6-step1-4.png
:white_check_mark:Succeeded
View

mixed-reality-docs/mixed-reality-capture-for-developers.md
:white_check_mark:Succeeded
View

mrtk-docs/TOC.yml
:white_check_mark:Succeeded
View

mrtk-docs/breadcrumb/toc.yml
:white_check_mark:Succeeded

mrtk-docs/docfx.json
:white_check_mark:Succeeded

mixed-reality-docs/TOC.md

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

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

Line 66, Column 32: [Warning-file-not-found] Invalid file link: 'mr-learning-base.md'.
Line 82, Column 28: [Warning-file-not-found] Invalid file link: 'mr-learning-base-02.md'.
Line 82, Column 117: [Warning-file-not-found] Invalid file link: 'mr-learning-base-02.md'.
Line 84, Column 4: [Warning-file-not-found] Invalid file link: 'mr-learning-base-02.md'.
Line 85, Column 4: [Warning-file-not-found] Invalid file link: 'mr-learning-base-02.md'.
Line 86, Column 4: [Warning-file-not-found] Invalid file link: 'mr-learning-base-02.md'.
Line 87, Column 4: [Warning-file-not-found] Invalid file link: 'mr-learning-base-02.md'.
Line 88, Column 4: [Warning-file-not-found] Invalid file link: 'mr-learning-base-02.md'.
Line 89, Column 4: [Warning-file-not-found] Invalid file link: 'mr-learning-base-02.md'.
Line 91, Column 17: [Warning-file-not-found] Invalid file link: 'mr-learning-base-03.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-azure-02.md

Line 45, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 63, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial2-section4-step1-1.png'.

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

Line 32, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/cognitive-services/custom-vision-service/getting-started-build-a-classifier#upload-and-tag-images' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 41, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial3-section4-step1-1.png'.
Line 45, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial3-section4-step1-2.png'.
Line 52, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial3-section4-step1-3.png'.
Line 56, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial3-section4-step1-4.png'.
Line 60, Column 120: [Warning-file-not-found] Invalid file link: 'mrlearning-azure-02.md'.
Line 82, Column 1: [Warning-file-not-found] Invalid file link: 'mrlearning-azure-04.md'.
Line 2, Column 8: [Suggestion-duplicate-titles] Attribute 'title' with value 'Azure Cloud Tutorials - 3. Integrating Azure Custom Vision' is duplicated in 'mr-learning-azure-03.md(2,8)', 'mrlearning-azure-03.md(2,8)'. NOTE: This Suggestion will become a Warning in late September, 2020.
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.

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

Line 39, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial4-section1-step1-1.png'.
Line 45, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial4-section1-step2-1.png'.
Line 49, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial4-section1-step3-1.png'.
Line 98, Column 1: [Warning-file-not-found] Invalid file link: 'mrlearning-azure-05.md'.

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

Line 65, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial5-section4-step1-1.png'.
Line 72, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial5-section4-step1-2.png'.
Line 84, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial5-section4-step1-3.png'.
Line 94, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial5-section4-step1-4.png'.
Line 104, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial5-section4-step1-5.png'.
Line 111, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial5-section4-step1-6.png'.
Line 121, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial5-section5-step1-1.png'.
Line 125, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial5-section5-step1-2.png'.
Line 140, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial5-section6-step1-1.png'.
Line 147, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial5-section6-step1-2.png'.
Line 153, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial5-section6-step1-3.png'.
Line 159, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial5-section6-step1-4.png'.

mixed-reality-docs/mrlearning-azure-03.md

Line 32, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/cognitive-services/custom-vision-service/getting-started-build-a-classifier#upload-and-tag-images' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 41, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial3-section4-step1-1.png'.
Line 45, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial3-section4-step1-2.png'.
Line 52, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial3-section4-step1-3.png'.
Line 56, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial3-section4-step1-4.png'.
Line 60, Column 120: [Warning-file-not-found] Invalid file link: 'mrlearning-azure-02.md'.
Line 2, Column 8: [Suggestion-duplicate-titles] Attribute 'title' with value 'Azure Cloud Tutorials - 3. Integrating Azure Custom Vision' is duplicated in 'mr-learning-azure-03.md(2,8)', 'mrlearning-azure-03.md(2,8)'. NOTE: This Suggestion will become a Warning in late September, 2020.
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.

mrtk-docs/index.md

Line 1, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 1, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.

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 ef0a19f:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/mixed-reality, working directory: W:\rzxp-s, target branch: HEAD, target branch commit: 6c44ad30057bf1b6f3d15ffb8e43dcd3389f62c5, source commit: ef0a19f017ea2e28e5c2a2821e3a2b63e04cfd4c.

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 fadf1e4:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/mixed-reality, working directory: W:\dmps-s, target branch: HEAD, target branch commit: 6c44ad30057bf1b6f3d15ffb8e43dcd3389f62c5, source commit: fadf1e432a685f039505a13aae5f5cd2b2dda27e.

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 fadf1e4:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/mixed-reality, working directory: W:\05tp-s, target branch: HEAD, target branch commit: 6c44ad30057bf1b6f3d15ffb8e43dcd3389f62c5, source commit: fadf1e432a685f039505a13aae5f5cd2b2dda27e.

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 45253b2:
: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-azure-02.md
:warning:Warning
View
Details

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

mixed-reality-docs/mrlearning-azure-03.md
:warning:Warning
View
Details

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

mixed-reality-docs/images/mr-learning-azure/tutorial1-section4-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section5-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section5-step1-2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section5-step1-3.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section6-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section6-step1-2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section6-step1-3.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section6-step1-4.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section6-step1-5.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section7-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section7-step1-2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial1-section7-step1-3.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial2-section4-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial3-section4-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial3-section4-step1-2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial3-section4-step1-3.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial3-section4-step1-4.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial4-section1-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial4-section1-step2-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial4-section1-step3-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section4-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section4-step1-2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section4-step1-3.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section4-step1-4.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section4-step1-5.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section4-step1-6.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section5-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section5-step1-2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section6-step1-1.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section6-step1-2.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section6-step1-3.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mr-learning-azure/tutorial5-section6-step1-4.png
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-learning-azure-05.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 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-azure-02.md

Line 45, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

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

Line 58, Column 100: [Warning-file-not-found] Invalid file link: 'mr-learning-base-ch1.md'.

mixed-reality-docs/mrlearning-azure-03.md

Line 32, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/cognitive-services/custom-vision-service/getting-started-build-a-classifier#upload-and-tag-images' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 41, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial3-section4-step1-1.png'.
Line 45, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial3-section4-step1-2.png'.
Line 52, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial3-section4-step1-3.png'.
Line 56, Column 1: [Warning-file-not-found] Invalid file link: 'images/mrlearning-azure/tutorial3-section4-step1-4.png'.
Line 60, Column 120: [Warning-file-not-found] Invalid file link: 'mrlearning-azure-02.md'.
Line 2, Column 8: [Suggestion-duplicate-titles] Attribute 'title' with value 'Azure Cloud Tutorials - 3. Integrating Azure Custom Vision' is duplicated in 'mr-learning-azure-03.md(2,8)', 'mrlearning-azure-03.md(2,8)'. NOTE: This Suggestion will become a Warning in late September, 2020.
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.

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

Line 2, Column 8: [Suggestion-duplicate-titles] Attribute 'title' with value 'Azure Cloud Tutorials - 3. Integrating Azure Custom Vision' is duplicated in 'mr-learning-azure-03.md(2,8)', 'mrlearning-azure-03.md(2,8)'. NOTE: This Suggestion will become a Warning in late September, 2020.
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


Improve the text at the top of the home page

Received the latest home page text from the product team.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: jcwarr95 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Support the recognition of phone numbers, emails, urls and more?

It is an interesting component.
Does it support the recognition of phone numbers, emails and urls that may be in the text?
If it recognizes them will it activate the phone for a phone number, open the mail application for an email and launch Safari Mobile for a web address?
Can we add one or more regex to customize the text and associate an action if the user clicks on it?

Only single-word tags are supported at this time. Tags with more than one word or containing any characters besides letters or numbers are ignored and not removed.
To display a phone number, email address, or link to a website, you need to use compound HTML tags:
+1-222-3333-4455
<a href="mailto:example<EMAIL_ADDRESS>GitHub

All of this is listed in the README file. Please read it carefully.
Also note that this package uses SwiftUI 2. That means that TextView does not support any links. Maybe this can be implemented in SwiftUI 3, but I haven't tried the new versions of the software yet.
Perhaps in the future I will make this package more functional. I will let you know about it here.


Assertion triggered in Mac::HandleTransmitDone() in rare cases (cloud stress test)

023-06-01 19:53:19,729 - INFO - OTNS >>> node=1    dst=fdde:ad00:beef:0:486c:2262:6b9:1907      datasize=32  delay=0.000ms
2023-06-01 19:53:19,729 - INFO - OTNS >>> node=45   dst=fdde:ad00:beef:0:486c:2262:6b9:1907      datasize=32  delay=236.080ms
2023-06-01 19:53:19,729 - INFO - OTNS >>> Done
2023-06-01 19:53:19,729 - INFO - OTNS <<< move 24 592 227
2023-06-01 19:53:19,729 - INFO - OTNS >>> Done
2023-06-01 19:53:19,729 - INFO - OTNS <<< move 25 288 617
2023-06-01 19:53:19,730 - INFO - OTNS >>> Done
2023-06-01 19:53:19,730 - INFO - OTNS <<< move 40 27 209
2023-06-01 19:53:19,730 - INFO - OTNS >>> Done
2023-06-01 19:53:19,730 - INFO - OTNS <<< move 37 765 662
2023-06-01 19:53:19,730 - INFO - OTNS >>> Done
2023-06-01 19:53:19,730 - INFO - OTNS <<< move 11 386 733
2023-06-01 19:53:19,730 - INFO - OTNS >>> Done
2023-06-01 19:53:19,730 - INFO - OTNS <<< go 60
error	2023-06-01 19:53:21.881 - Node 9 process failed: ot-cli-ftd: /home/runner/work/ot-ns/ot-ns/ot-rfsim/openthread/src/core/mac/mac.cpp:1447: void ot::Mac::Mac::HandleTransmitDone(ot::Mac::TxFrame&, ot::Mac::RxFrame*, ot::Error): Assertion `false' failed.
warn	2023-06-01 19:53:26.643 - syncing 1 alive nodes: map[9:{}]
info	2023-06-01 19:53:26.643 - Deleting node 9 due to process failure.
2023-06-01 19:53:36,422 - INFO - OTNS >>> Error: ot-cli-ftd: /home/runner/work/ot-ns/ot-ns/ot-rfsim/openthread/src/core/mac/mac.cpp:1447: void ot::Mac::Mac::HandleTransmitDone(ot::Mac::TxFrame&, ot::Mac::RxFrame*, ot::Error): Assertion `false' failed.
Traceback (most recent call last):
  File "/home/runner/work/ot-ns/ot-ns/pylibs/stress_tests/BaseStressTest.py", line 52, in run_wrapper
    orig_run(self)
  File "/home/runner/work/ot-ns/ot-ns/pylibs/stress_tests/mleid_connectivity.py", line 123, in run
    ns.go(MOVE_INTERVAL)
  File "/home/runner/.local/lib/python3.7/site-packages/pyOTNS-0.0.0-py3.7.egg/otns/cli/OTNS.py", line 98, in go
    self._do_command(cmd)
  File "/home/runner/.local/lib/python3.7/site-packages/pyOTNS-0.0.0-py3.7.egg/otns/cli/OTNS.py", line 216, in _do_command
    raise OTNSCliError(line[7:])
otns.cli.errors.OTNSCliError: ot-cli-ftd: /home/runner/work/ot-ns/ot-ns/ot-rfsim/openthread/src/core/mac/mac.cpp:1447: void ot::Mac::Mac::HandleTransmitDone(ot::Mac::TxFrame&, ot::Mac::RxFrame*, ot::Error): Assertion `false' failed.
2023-06-01 19:53:36,423 - INFO - waiting for OTNS to close ...
info	2023-06-01 19:53:36.423 - program exit: <nil>
info	2023-06-01 19:53:36.423 - stopping simulation and exiting nodes ...
info	2023-06-01 19:53:36.449 - program context waiting routines: map[dispatcher:0 grpcwebproxy:0 handleSignals:0 simulation:1]
Traceback (most recent call last):
  File "/home/runner/work/ot-ns/ot-ns/pylibs/stress_tests/run_stress_suite.py", line 95, in <module>
    main()
  File "/home/runner/work/ot-ns/ot-ns/pylibs/stress_tests/run_stress_suite.py", line 70, in main
    run_suite(script_dir, suite_name)
  File "/home/runner/work/ot-ns/ot-ns/pylibs/stress_tests/run_stress_suite.py", line 91, in run_suite
    t.run(report=True)
  File "/home/runner/work/ot-ns/ot-ns/pylibs/stress_tests/BaseStressTest.py", line 60, in run_wrapper
    self.report()
  File "/home/runner/work/ot-ns/ot-ns/pylibs/stress_tests/BaseStressTest.py", line 120, in report
    raise RuntimeError("Stress test failed: \n" + "\n".join("\t" + msg for msg in self.result._fail_msgs))
RuntimeError: Stress test failed:
Error: 	ot-cli-ftd: /home/runner/work/ot-ns/ot-ns/ot-rfsim/openthread/src/core/mac/mac.cpp:1447: void ot::Mac::Mac::HandleTransmitDone(ot::Mac::TxFrame&, ot::Mac::RxFrame*, ot::Error): Assertion `false' failed.
**[OTNS](https://github.com/openthread/ot-ns) Stress Tests Report Generated at 06/01 19:53:36**
#### ML-EID Connectivity Test **Failed**: ot-cli-ftd: /home/runner/work/ot-ns/ot-ns/ot-rfsim/openthread/src/core/mac/mac.cpp:1447: void ot::Mac::Mac::HandleTransmitDone(ot::Mac::TxFrame&, ot::Mac::RxFrame*, ot::Error): Assertion `false' failed. _(06/01 19:36:06 ~ 06/01 19:53:36)_
| Simulation Time | Max Delay | Min Delay | Avg Delay |
| :-: | :-: | :-: | :-: |
Error: Process completed with exit code 1.

Closing, not recently observed.


⚠ Thumbnails API Endpoint has degraded performance

In d07b7eb, Thumbnails API Endpoint (https://thumbnails.roblox.com/v1/assets?assetIds=82738847&format=Png&isCircular=false&size=30x30) experienced degraded performance:

HTTP code: 200
Response time: 1074 ms

Resolved: Thumbnails API Endpoint performance has improved in 2e3d0d3.


Draft blog post to promote ESRI GeoDev meet-up

Posted: http://citycampnc.org/2017/03/29/esri-geodev-meet-up-on-april-3/


Feat: Add USDC and more initial routes

Resolves #165
This PR is slightly expanded in scope compared to PR #171 , as it adds USDC as foreign asset between Interlay and both, AssetHub and HydraDX, as well as adding USDT route between Interlay and HydraDX.
All new routes:

USDC

Interlay <-> AssetHub
Interlay <-> HydraDX

USDT

Interlay <-> HydraDX

(USDT to/from AssetHub already exists)

Closing this for now to avoid confusion, takes more work to figure out how to correctly configure it.


Sort Index Dropdown and Implement ComboBox

Description
This change sorts the index dropdown. It also uses a ComboBox to add search functionality.

Issues Resolved
Closes #293
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@frankschlehofer can you use the DataSourceSelectable component from the data plugin in OSD for this? it should do the heavy lifting of showing you all the available datasources.
Its used in the Data Explorer plugin like this: https://github.com/opensearch-project/OpenSearch-Dashboards/blob/main/src/plugins/data_explorer/public/components/sidebar/index.tsx#L96-L103

Going to close this now, since we have more work being done on #358.


Compilation of bugs with multiple submodules

Hi @nus-apr,
In the context of another project, I've noticed that all bugs in the Bugs.jar benchmark (except Commons-Math) are composed by multiple submodules.  And I've also noticed that the root pom.xml of some bugs fail to compile but the true buggy submodule compiles successfully.  Have you encountered such odd behaviour while compiling bugs with multiple submodules?
--
Best,
Jose

Thanks @Marti2203.  Why don't we keep this issue open until the problem is formally addressed?

Hi @jose
Thanks for opening the issue,
Indeed I have encountered this in other benchmarks as well, for such instances we change the scope the build to the buggy module. In our meta data file we specify the submodule which should be built and tested. This we achieve via creating our own scripts, which we were able to do so in our own versions of the benchmark.
We may be able to do the same for the bugs.jar as well. Will update this thread when we have updated the benchmark.

In our meta data file we specify the submodule which should be built and tested.

Ok.

Will update this thread when we have updated the benchmark.

Awesome, thanks.


Aspera cli upload failure

i get the below error when i try to browse share from linux cli.
D, [2022-12-13T15:16:05.115536 #1542537] DEBUG -- net.ssh.transport.server_version[bb8]: local is `SSH-2.0-Ruby/Net::SSH_6.1.0 x86_64-linux'
ERROR: Other: connection closed by remote host
/home/svc_aspera/.local/share/gem/ruby/gems/net-ssh-6.1.0/lib/net/ssh/transport/server_version.rb:57:in `rescue in block (2 levels) in negotiate!': connection closed by remote host (Net::SSH::Disconnect)

Best is if you share the command line used. (redacting hostnames, usernames and password).
access to shares should be like this:
ascli shares --url=https://shares.example.com --username=xxx --password=yyy browse /

We used the below commands to save.
ascli config preset update myserver --url=ssh://host:port --username=asperaweb --password=pass_here
updated: myserver
ascli config preset set default server myserver
updated: default→server to myserver
ascli server browse /folder
From: Laurent Martin @.>
Sent: Thursday, December 15, 2022 8:37 PM
To: IBM/aspera-cli @.>
Cc: Surendranathan Ravimanoharan - Network @.>; Author @.>
Subject: [EXTERNAL] Re: [IBM/aspera-cli] Aspera cli upload failure (Issue #98)
EXTERNAL EMAIL: Use caution before replying, clicking links, and opening attachments.
Best is if you share the command line used. (redacting hostnames, usernames and password).
access to shares should be like this:
ascli shares --url=https://shares.example.com --username=xxx --password=yyy browse /

Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIBM%2Faspera-cli%2Fissues%2F98%23issuecomment-1353236337&data=05|01|ravimanoharan_surendranathan%40network.lilly.com|637df9964b6447326ea208dadeadff66|18a59a81eea84c30948ad8824cdc2580|0|0|638067136153906336|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=rDry8HZE5wrUyjsnRyESDs7C6kJLTd3muCYR3DLtdoA%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANS7XPLHKYJCS5ZFXN2RLOTWNMXYVANCNFSM6AAAAAAS72EKIM&data=05|01|ravimanoharan_surendranathan%40network.lilly.com|637df9964b6447326ea208dadeadff66|18a59a81eea84c30948ad8824cdc2580|0|0|638067136153906336|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=BTACrOeUmMNKUXcHDB7JmMJ5KIjQuSpcXo75fW97rpc%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

This command is to access an Aspera HSTS directly through the SSH interface.
But for Aspera Shares, the correct commands are:
ascli config preset update mysharesconf --url=https://shares.example.com --username=_user_here_ --password=_pass_here_
ascli config preset set default shares mysharesconf
ascli shares browse /folder

Again, the server plugin is for direct HSTS access.
For Shares, ... use the shares command.
(In your case, you are using a Shares app, and HSTS is on a different server (through aspera proxy).)

Please see the error:
ERROR: Argument: unknown value for command: browse
Use:

admin
health
repository
Use option -h to get help.
ERROR: Argument: unprocessed values: ["/r_Labcorp_to_Lilly"]
/home/svc_aspera/.local/share/gem/ruby/gems/aspera-cli-4.10.0/lib/aspera/cli/manager.rb:75:in `get_from_list': unknown value for command: browse (Aspera::Cli::CliBadArgument)

'browse' isn't a valid argument for 'ascli shares'
From: Laurent Martin @.>
Sent: Thursday, December 15, 2022 8:46 PM
To: IBM/aspera-cli @.>
Cc: Surendranathan Ravimanoharan - Network @.>; Author @.>
Subject: [EXTERNAL] Re: [IBM/aspera-cli] Aspera cli upload failure (Issue #98)
EXTERNAL EMAIL: Use caution before replying, clicking links, and opening attachments.
This command is to access an Aspera HSTS directly through the SSH interface.
But for Aspera Shares, the correct commands are:
ascli config preset update mysharesconf --url=https://shares.example.com --username=user_here --password=pass_here
ascli config preset set default shares mysharesconf
ascli shares browse /folder
Again, the server plugin is for direct HSTS access.
For Shares, ... use the shares command.
(In your case, you are using a Shares app, and HSTS is on a different server (through aspera proxy).)

Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIBM%2Faspera-cli%2Fissues%2F98%23issuecomment-1353250974&data=05|01|ravimanoharan_surendranathan%40network.lilly.com|d9d5e5acec9a4a72553108dadeaf563b|18a59a81eea84c30948ad8824cdc2580|0|0|638067141892255821|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=C1PIPCKGKxDa0ygd%2Bz8RYw%2Fh0usZm5B4g29X0TWM5VY%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANS7XPOPWRKU742DMOQBMYTWNMY4PANCNFSM6AAAAAAS72EKIM&data=05|01|ravimanoharan_surendranathan%40network.lilly.com|d9d5e5acec9a4a72553108dadeaf563b|18a59a81eea84c30948ad8824cdc2580|0|0|638067141892255821|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=%2Bk9xIBpsK%2Bl%2Ba4TDhC383Xc9zwaSP9iOTOBxeXVVdfM%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

I apologize, there was a typo (fixed above), the correct command is:
ascli shares repo browse /r_Labcorp_to_Lilly

Hi Martin,
It worked.
Can you please share the command to upload file or folder to shares.
From: Laurent Martin @.>
Sent: Thursday, December 15, 2022 9:01 PM
To: IBM/aspera-cli @.>
Cc: Surendranathan Ravimanoharan - Network @.>; Author @.>
Subject: [EXTERNAL] Re: [IBM/aspera-cli] Aspera cli upload failure (Issue #98)
EXTERNAL EMAIL: Use caution before replying, clicking links, and opening attachments.
I apologize, there was a typo (fixed above), the correct command is:
ascli shares repo browse /r_Labcorp_to_Lilly

Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIBM%2Faspera-cli%2Fissues%2F98%23issuecomment-1353273339&data=05|01|ravimanoharan_surendranathan%40network.lilly.com|d1e17bbf8f9748b3609c08dadeb16124|18a59a81eea84c30948ad8824cdc2580|0|0|638067150667250688|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=X%2B%2B3DnL8sH8xOas4NAu1fpKSg%2FaxeqQfL5Yx54OdN6c%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANS7XPPSNUNN6AXUDP3XTM3WNM2TPANCNFSM6AAAAAAS72EKIM&data=05|01|ravimanoharan_surendranathan%40network.lilly.com|d1e17bbf8f9748b3609c08dadeb16124|18a59a81eea84c30948ad8824cdc2580|0|0|638067150667250688|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=aj9h1QoRz5%2FpqhuUZ2WVN2chJXpd7x0pUpYCx%2BjFEiA%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Browse worked,
issue with upload:
[~]$ ascli server upload josh_test2.txt --to-folder=/r_Labcorp_to_Lilly
ERROR: Other: ERROR: transfer spec with token required
ERROR: Argument: unprocessed values: ["upload", "josh_test2.txt"]
Use --log-level=debug to get more details.
please see if you can assist.

eh eh, :)...
again, command is shares, always, for shares.
and repository commands are under: ascli shares repo
I suggest you delete your old configuration like this, to avoid confusion:
ascli config preset delete myserver
ascli conf preset unset default server

you can list shares repository commands like this:
ascli shares repo

Some commands are listed here:
https://github.com/IBM/aspera-cli#plugin-ibm-aspera-shares
So, the correct command is:
ascli shares repo upload josh_test2.txt --to-folder=/r_Labcorp_to_Lilly

you can adjust transfer parameters like this:
ascli shares repo upload josh_test2.txt --to-folder=/r_Labcorp_to_Lilly --ts=@json:'{"target_rate_kbps":100000,"resume_policy":"sparse_csum"}'

transfer parameters are explained here:

https://github.com/IBM/aspera-cli#transfer-parameters

Martin, thanks much. it worked now.


Link to extension schema

Comment left in a mail to<EMAIL_ADDRESS>Link https://dilcis.eu/XML/METS/SIPExtensionMETS/SIPExtensionMETS.xsd does not work

This is a tricky one as it comes with several problems:

The issue is located on the E-ARK-SIP.xml (i.e. the SIP METS profile).
The referred namespace doesn't have to be published on the cited URL, however, it is always nice to find it where it is supposed to be, so my recommendation is to put it on the DILCIS Board website.
The version number should be on the URL path or on the filename as different version of the spec might use different METS profiles
The only XSD we have on the SIP project is the https://github.com/DILCISBoard/E-ARK-SIP/blob/master/schema/DILCISExtensionSIPMETS.xsd which has a different name than SIPExtensionMETS.xsd. So this should be fixed as well on either side.

Also needs the help of @carlwilson

The link in the profile to the schema: https://dilcis.eu/XML/METS/SIPExtensionMETS/DILCISExtensionSIPMETS.xsd isnt working the path should be http://earksip.dilcis.eu/schema/ ???? Also when the reference to the schema is made in xsi:SchemaLocation @carlwilson

Fixed with PR #67


descriptor.md: add descriptions for the extended field

Signed-off-by: Qian Zhang<EMAIL_ADDRESS>

I guess this is fine, but we already have a SHOULD for this IIRC

On Tue, Apr 25, 2017 at 10:33:55AM -0700, v1.0.0.batts wrote:

I guess this is fine, but we already have a SHOULD for this IIRC

The existing SHOULD is in 1.  That SHOULD is tied to the descriptor
location (all descriptors in an index's ‘manifests’, regardless of
whether they link a manifest), while this SHOULD is tied to the
descriptor target (all descriptors linking a manifest, regardless of
whether the descriptor is in an index or not).  So they're similar,
but not quite the same.
Personally, I think the SHOULD proposed here makes more sense if the
platform docs move over to descriptor.md (a Markdown version of #620),
and the current SHOULD makes more sense with the current spec (where
‘platform’ is unspecified outside of the index ‘manifests’ context).
I don't think we want the low-level descriptor.md referencing the very
high-level image-index.md to define descriptor properties.

LGTM

LGTM


[Priority: Medium] Investigate Money.ToString() API calls.

In Hungarian system environment 3.2.ToString() results in 3,2, while in most other environments it results in 3.2. This can lead to unexpected issues.

It will not lead to unexpected issues. NBitcoin properly handles it.
Test code:
Money m = new Money(1);
double n = 1.1;
Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("en-US");
Console.WriteLine(n);
Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("tr-TR");
Console.WriteLine(n);

Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("en-US");
Console.WriteLine(m);
Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("tr-TR");
Console.WriteLine(m);
Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("en-US");
Console.WriteLine(m.ToString());
Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("tr-TR");
Console.WriteLine(m.ToString());

Console.ReadKey();

Output:
1.1
1,1
1
1
0.00000001
0.00000001


Add design for upload tgz file proposal

This design adds the ability to upload a module's tgz file via the /nodes admin end point.
This will allow nodes to be installed that have been generated locally and not published to npm.
There will be some restrictions on where this can be used - for example, it will only be available with the built-in localfilesystem storage plugin.
The feature can be disabled via the editorTheme.palette.upload setting.
As this is the second design note related to node installation, this PR also reorganises the existing design note so we have a collection of designs on this topic.
For ease of review, here's a direct link to the upload-tgz design note: https://github.com/node-red/designs/blob/tgz-upload/designs/node-installation/upload-tgz.md

Adding link to SO question about this sort of thing for reference https://stackoverflow.com/questions/63363349/is-there-a-way-to-install-a-nodered-node-in-a-remote-server/63365092

I try upload module tgz file , but failure by lastest version. Error is
Error: Module not found
at checkModulePath (/usr/local/lib/node_modules/node-red/node_modules/@node-red/registry/lib/installer.js:88:15)
at Unpack.tar.x.on.on (/usr/local/lib/node_modules/node-red/node_modules/@node-red/registry/lib/installer.js:381:34)
at Unpack.emit (events.js:198:13)
at Unpack.[maybeClose] (/usr/local/lib/node_modules/node-red/node_modules/@node-red/registry/node_modules/tar/lib/unpack.js:195:12)
at Unpack.[unpend] (/usr/local/lib/node_modules/node-red/node_modules/@node-red/registry/node_modules/tar/lib/unpack.js:439:21)
at fs.close.er (/usr/local/lib/node_modules/node-red/node_modules/@node-red/registry/node_modules/tar/lib/unpack.js:346:55)
at /usr/local/lib/node_modules/node-red/node_modules/graceful-fs/graceful-fs.js:61:14
at FSReqWrap.args [as oncomplete] (fs.js:140:20)

@gaoguijie please raise an issue on the main node-red repository: https://github.com/node-red/node-red


feat: bumped glob dependency from 8 to 10

PR Checklist

[x] Addresses an existing open issue: fixes #5148
[x] That issue was marked as status: accepting prs
[x] Steps in CONTRIBUTING.md were taken

Overview
Bumps the glob version range in package.json. We can't yet use glob@11, as it only supports Node.js 20 up and Mocha 11 still supports Node.js 18.
The only change to JS source code is a manual 'en' alphabetical sort of glob.sync results. This is to preserve the legacy behavior of what order test files are found and run: https://github.com/mochajs/mocha/pull/5250/files#r1840469747.
I tested this on the https://github.com/eslint/eslint and https://github.com/Microsoft/TypeScript projects and all tests reported passing.

Seems like there are still ways to go for upgrading glob:
<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └─┬<EMAIL_ADDRESS>│ │   └──<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └─┬<EMAIL_ADDRESS>│     └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └─┬<EMAIL_ADDRESS>│     └─┬<EMAIL_ADDRESS>│       └─┬<EMAIL_ADDRESS>│         └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>overridden
│   ├─┬<EMAIL_ADDRESS>│   │ └──<EMAIL_ADDRESS>│   └─┬<EMAIL_ADDRESS>│     └─┬<EMAIL_ADDRESS>│       └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>
I tried to test this branch with https://github.com/Tyriar/vscode-sort-lines, but unfortunately @vscode/test-electron (2.4.1) doesn't work with npm link. So I didn't get far.

Seems like there are still ways to go for upgrading glob:

Yeah, the internal dependencies for this repo have a ways to go 🥲. A lot of them come from the very old docs website setup we have. It's going to be a bit more till we internally are clean & up to date. Tracked in #5207.


Known as a class decorator

Can you elaborate?

The ability to use this as a class decorator:
@known
class Foobar {
    baz = 1;
    someMethod() {}
}

Foobar.crap
> [TypeError] Unknown property: crap

That would indeed be very nice, but decorators is just an ECMAScript stage 1 proposal at the moment.
https://github.com/wycats/javascript-decorators/blob/master/README.md
Would be happy to accept a pull request if it's possible to support it without transpiling this code though.

A decorator is just a function with a pre-defined set of arguments. So it should be perfectly possible.

Hey guys, I'm trying to pick this up but i'm sure if i got the gist of it. Since transpiling is out of the question, wouldnt wrapping it in high order function result in the same invocation, like
known([random class here]).
Thank you


Issue 100: Upgrading and lock version of Gh actions

closes https://github.com/Siemienik/XToolset/issues/100

Merged as important


support the new category tree during publication

at the moment you see only the top-level

actually you see all levels but you have no clue about the nesting

implemented in: https://github.com/twosigma/beaker-notebook/issues/2201


Graphql: Add flights query

@FilipMessa @michalsanger 🚀

@FilipMessa 🚀

There is still some naming with flights so because we assume that in futter it won't be only about flights, we should change all these names.
What do you think?

🙈 you are right, I missed this, I will change it.

@FilipMessa should be no flights left now

Thanks, good job.
But it hard to know if it works without Playground or some FE implementation now, so what about adding there some tests at least?

Yes, I wanted to add some tests, but we need some Testing tool, which I think should be another PR, this is big enough already.
I have an implementation I used to test it which I did not commit. Do you want me to add that?

OK, sure make tests in another PR than, I believe you that it works so. I'll approve this PR.


License?

Thanks for providing this, helped answer some questions missing from Apple's sample code. Can you tell me what this is licensed under, and add a license to the repo if not too much trouble?

This repo is under MIT License. I put a LICENSE in repo. Please check it 😊

Thanks so much!


[Bug] Failed to construct 'Response': Failed to read the 'statusText' property from

📦 Deployment Method
Other
📌 Version
2.15.6
💻 Operating System
Windows
📌 System Version
win 10
🌐 Browser
Chrome
📌 Browser Version
130.0.6723.69
🐛 Bug Description
None of the versions works and gives an error it never happened.
{
  "error": true,
  "message": "Failed to construct 'Response': Failed to read the 'statusText' property from 'ResponseInit': String contains non ISO-8859-1 code point."
}

📷 Recurrence Steps
No response
🚦 Expected Behavior
No response
📝 Additional Information
No response

怎么复现这个问题

I opened the ChatGPTNextWeb application and just started typing my question I press Enter and get this error I rolled back a few versions ago everything works correctly apparently something needs to be fixed something is broken somewhere

err.source().expect("REASON").to_string() may by non ISO-8859-1 code

err.source().expect("REASON").to_string() may by non ISO-8859-1 code

Tell me as a user who uses not develops software What I need to do I just download the application and use it as a user I do not develop it?

应该是非英语用户（Windows操作系统语言非英语）api请求报错的时候，会出现这个错误。
如果API配置正确，应该不会触发这个报错。

@lloydzhou
That's right, I use non-English words in my native language, which is different from English.

no verification works what to do urgently? how to use I have a lot of work to do

bug已经在主分支修复，只是未发布新版本，预计本周发布v2.15.7会包含这个修复


Issues #29 resolve

Get commit time using go-git
closes #29

Sorry, i assume that body.md file is in taitan repository.

Which repository that body.md file belong?

For the given file, current code is referring to bodyPath.ModTime(), which is body.md's ModTime().

Actually, we can check the commit time without specifying repoPath with something like:
exec.Command("git", "log", "--format=%at", "--", filePath)

But, is it safe enough to do raw commands?

Sorry, i assume that body.md file is in taitan repository.
May I knew which repository that body.md file belong?

I guess it's not very clear (i think it's only partially referenced in .env.example), but the two content repositories we use taitan for is https://github.com/datasektionen/bawang-content and https://github.com/datasektionen/styrdokument. And there are loads of body.md-files in them.

[...] But, is it safe enough to do raw bash commands?
Go's exec.Command doesn't use bash, it executes the program (git in the given case) directly, so references to environment variables and other bash-stuff would not do anything. So yes that's definitely safe! It is also what we do to clone the repository.

From some quick testing it also seems like the git cli is way faster than the go-git library, but I didn't do it thoroughly at all.

You can get the api running correctly by copying .env.example to .env and filling anything into the token, as github does not seem to check it since the content repository is public.

[...] Go's exec.Command doesn't use bash
Thank you for the new insight.

I'll try to get the api running

I got it. taitan finds all body.md in $CONTENT_URL. It means the file is not in local, it's on the internet.

Wait, change to stripPrefix instead.

Working on _test.go

There's different directory style between Linux and Windows. Working on it.

Should I let this to platform-dependent on GOOS='Linux'?

It might work on other platforms, but in production we run it on linux and that is what most people are running anyway (sometimes that's because of docker but still counts), so windows is not important to us.
Anyways, thanks very much for your contribution!

Thanks for guiding me through. Sorry for mistakes at the beginning.
See you next time.


iox-#1596 Add check for nullptr in RelativePointer

Pre-Review Checklist for the PR Author

[x] Code follows the coding style of CONTRIBUTING.md
[x] Tests follow the best practice for testing
[x] Changelog updated in the unreleased section including API breaking changes
[x] Branch follows the naming format (iox-123-this-is-a-branch)
[x] Commits messages are according to this guideline

[x] Commit messages have the issue ID (iox-#123 commit text)
[x] Commit messages are signed (git commit -s)
[x] Commit author matches Eclipse Contributor Agreement (and ECA is signed)

[x] Update the PR title

Follow the same conventions as for commit messages
Link to the relevant issue

[x] Relevant issues are linked
[x] Add sensible notes for the reviewer
[x] All checks have passed (except task-list-completed)
[x] All touched (C/C++) source code files from iceoryx_hoofs are added to ./clang-tidy-diff-scans.txt
[x] Assign PR to reviewer

Notes for Reviewer

Add check for nullptr in RelativePointer

Activation/ deactivation of this check will be possible by the user after #1032 was implemented

Checklist for the PR Reviewer

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code according to our coding style and naming conventions
[ ] Unit tests have been written for new behavior
[ ] Public API changes are documented via doxygen
[ ] Copyright owner are updated in the changed files
[ ] All touched (C/C++) source code files from iceoryx_hoofs have been added to ./clang-tidy-diff-scans.txt
[ ] PR title describes the changes

Post-review Checklist for the PR Author

[ ] All open points are addressed and tracked via issues

References

Closes #1596

While I marked changes requested, the change would be to not introduce the check at all.

@MatthiasKillat As written in this thread my suggestion is to go ahead and merge this PR. As part of #1032 we can then add the option to disable the assert-like checks.


The type or namespace name 'RequestContentHelper' does not exist in the namespace

I am working on this internal PR and @azure-tools/typespec-csharp is generating code that does not compile. In this case, there is no RequestContentHelper in the API namespace.:

Severity	Code	Description	Project	File	Line	Suppression State	Details
Error	CS0234	The type or namespace name 'RequestContentHelper' does not exist in the namespace 'ConveyorApi' (are you missing an assembly reference?)	ConveyorApi (net6.0), ConveyorApi (netstandard2.0)

 using BinaryContent content = ConveyorApi.RequestContentHelper.FromObject(body);

Please refer to the PR above, but here is a copy of the versions being used.
    "dependencies": {
      "@azure-tools/typespec-csharp": "0.2.0-beta.20240418.2",
      "@azure-tools/typespec-client-generator-core": "0.42.0-dev.8",
      "@typespec/compiler": "^0.55.0",
      "@typespec/http": "^0.55.0",
      "@typespec/rest": "^0.55.0",
      "@typespec/versioning": "^0.55.0"
    },

  <ItemGroup>
    <PackageReference Include="Azure.Core" Version="1.38.0" />
    <PackageReference Include="System.Text.Json" Version="6.0.7" />
    <PackageReference Include="Microsoft.Azure.AutoRest.CSharp" Version="3.0.0-beta.20240418.2" PrivateAssets="All" />
    <PackageReference Include="System.ClientModel" Version="1.1.0-beta.3" />
  </ItemGroup>

Hi @cataggar this issue has been fixed by this PR: https://github.com/Azure/autorest.csharp/issues/4612
This helper changed its name to BinaryContentHelper to align with the type name


[event request] Codeunit 80 "Sales-Post" add events to PostUpdateInvoiceLine and PostUpdateReturnReceiptLine

Could you please add the events OnAfterPostUpdateInvoiceLine(VAR TempSalesHeader : TEMPORARY Record "Sales Header") and PostUpdateReturnReceiptLine(VAR TempSalesHeader : TEMPORARY Record "Sales Header") to the Sales Post Codeunit?  OnAfterPostUpdateInvoiceLine should be called at the end of the PostUpdateInvoiceLine function (OnAfterPostUpdateInvoiceLine(TempSalesOrderHeader);)  and OnAfterPostUpdateReturnReceiptLine should be called at the end of the PostUpdateReturnReceiptLine function with a temporary table TempSalesReturnHeader containing the updated return orders - similar to how this is done in PostUpdateInvoiceLine.
The same functionality is also needed on Codeunit 90 Purchase-Post.

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


Add Operation and File Metrics [Delta]

Description
Fixes issues #137 and #4
Type of change
The goal was to add new information to the Commit Log entries. On Delta Lake, statistics at the operation level and file level are getting collected. Since Qbeast has a modified implementation of the writing process, we were skipping this part.
In this PR, we use JobStatsTrackers (spark processes that keep track of specific metrics when managing data) to fill in stats information. As a result, the CommitInfo and the AddFile present in the commit log, should contain the following fields:
{
  "commitInfo": {
    ...
    "operationMetrics": {
      "numFiles": "1",
      "numOutputRows": "3",
      "numOutputBytes": "660"
    },
   ...
}

 "add": {
   ...
    "stats": "{\"numRecords\":3,\"minValues\":{\"a\":\"A\",\"b\":1},\"maxValues\":{\"a\":\"C\",\"b\":3},\"nullCount\":{\"a\":0,\"b\":0}}",
   ...
  }
}

UPDATE.
After doing an initial benchmark, we will be leaving the data-skipping strategy for another Pull Request. We saw that reading and filtering twice the Delta Log (as a naïve solution) is creating an overhead on the queries. We should think of a better way os processing this information, but in the meantime, I think it's more important to have this metadata in the commit log.
Checklist:
Here is the list of things you should do before submitting this pull request:

[x] New feature / bug fix has been committed following the Contribution guide.
[x] Add comments to the code (make it easier for the community!).
[x] Change the documentation.
[x] Add tests.
[ ] Your branch is updated to the main branch (dependent changes have been merged).

How Has This Been Tested? (Optional)
Please describe the tests that you ran to verify your changes.
Created a test under QbeastDataSourceIntegrationTest class in which we make sure the information is commited correctly.
Since these additional measurements are going to impact performance, we should also benchmark this againts version 0.3.1.

On the new commit 8e7f304, I added a workaround to filter files using the Stats.
Since Delta Lake has already implemented a DataSkippingReader strategy on the Snapshot class, we would use their method to filter according to the gathered stats. Once we had their filtering and ours, we can join the outputs with the file paths.
This is a first naive implementation. We should think about something more efficient, since we are duplicating the number of collects on the Delta Log, and we can simplify the data skipping with one single process.

After doing an initial benchmark, I think it's best to leave the data-skipping strategy for another Pull Request. We saw that reading and filtering twice the Delta Log (as a naïve solution) is creating an overhead on the queries. We should think of a better way of processing this information, but in the meantime, probably it's more important to have this metadata in the commit log.


Named/multiple outlets support

It would be very nice to have named outlet support.
It's mostly to have easy modals support and being able to write something like:
<body>
<div>
   <router-view name="modal"></router-view>
</div>
<router-view ></router-view>
</body>

router.map({
    '/somewhere/': {
        component: Somewhere,
        subRoutes: {
            'action/': {
                 component: Modal,
                 outlet: 'modal'
            }
        }
    }
});

Then, routing to /somewhere/action/ should bring the Somewhere component and display the modal over.
My case is for modal, but I think whenever you have an outer layout with multiple reusable slots, a single outlet is not sufficient.
If there is already a way of doing this, I'm interested in.

:+1: Would love something like this.

:+1:

I think this can be achieved by using named routes, no? Like <modal v-if="$router.name === 'modal'"></modal>.

To add on to what @azamat-sharapov stated, the named routes feature is documented here: http://vuejs.github.io/vue-router/en/named.html
Though since I believe this use case to be common then I think a cleaner API to handle it would be nice, instead of having $router.name === 'modal' all over.

+1s

Yeah, still waiting for it to implement.

Hi! May be need help? Because it's very important issue(((

This is available in vue-router 2.0.0-rc.* (which is only compatible with Vue 2.0).
Work on vue-router 0.7.* won't really go on until all the 2.0 related release work is done.
@djvonavi If you want to work on a PR, that would be welcome.

How is this possible? Any documentation?

Yes, it's in the router's documentation, chapter "Named Views"

No, this is not possible for Vue-router < 2.0, and we likely won't implement it.

Thanks, Is it possible on Vue-router 2.0?

yes, it is, as the comment above says. Search for named views


Use chrome.storage to save settings

Make use of chrome.storage APIs to sync user settings instead of local storage.
http://developer.chrome.com/extensions/storage.html

Requires new permission with little benefit.


python38Packages.pytest-testmon: 1.1.2 -> 1.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.pytest-testmon is: "This is a py.test plug-in which automatically selects and re-executes only tests affected by recent changes"
meta.homepage for python38Packages.pytest-testmon is: "https://github.com/tarpas/pytest-testmon/"
meta.changelog for python38Packages.pytest-testmon is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.2.0 with grep in /nix/store/v3zyvqya6jili8bk2h0xd8lyis7q5hpd-python3.8-pytest-testmon-1.2.0

found 1.2.0 in filename of file in /nix/store/v3zyvqya6jili8bk2h0xd8lyis7q5hpd-python3.8-pytest-testmon-1.2.0

directory tree listing: https://gist.github.com/385aafa63bf35432a13ced8d75368d8d

du listing: https://gist.github.com/e9fc9193077685f3d1c64a39d07189f8

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python38Packages.pytest-testmon
python39Packages.pytest-testmon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/v3zyvqya6jili8bk2h0xd8lyis7q5hpd-python3.8-pytest-testmon-1.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python38Packages.pytest-testmon https://github.com/r-ryantm/nixpkgs/archive/cb04366863750811dc08b6b103a6fee517f821a6.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/v3zyvqya6jili8bk2h0xd8lyis7q5hpd-python3.8-pytest-testmon-1.2.0
ls -la /nix/store/v3zyvqya6jili8bk2h0xd8lyis7q5hpd-python3.8-pytest-testmon-1.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python38Packages.pytest-testmon
python39Packages.pytest-testmon

Maintainer pings
cc @dmvianna for testing.

Result of nixpkgs-review pr 139049 at cb043668 run on aarch64-linux 1

2 packages built successfully:

python38Packages.pytest-testmon
python39Packages.pytest-testmon


Project metrics still being processed while project is being deleted

Current Behavior
When a project is deleted via REST API or UI, a tombstone event is published to dtrack.metrics.component for every component of that project. This is happening before the project is actually deleted from the API server.
Because the metrics calculation is fast, this can lead to situations where the project has not yet been deleted on the API server side, but metrics updates for the same project are still arriving and processed.
Steps to Reproduce

Create a project
Upload an SBOM to the project
Wait for all related processing to complete
Delete the project
Observe the API server logs

The logs will reveal multiple metrics updates being processed while project deletion is still in progress:
dt-apiserver  | 2023-03-10 12:13:45,064 INFO [ProjectMetricsProcessor] Completed metrics update for project 00651c27-4769-4a68-bd74-8096bd16cde7
dt-apiserver  | 2023-03-10 12:13:45,079 INFO [ProjectMetricsProcessor] Completed metrics update for project 00651c27-4769-4a68-bd74-8096bd16cde7
dt-apiserver  | 2023-03-10 12:13:45,087 INFO [ProjectMetricsProcessor] Completed metrics update for project 00651c27-4769-4a68-bd74-8096bd16cde7
dt-apiserver  | 2023-03-10 12:13:45,099 INFO [ProjectMetricsProcessor] Completed metrics update for project 00651c27-4769-4a68-bd74-8096bd16cde7
dt-apiserver  | 2023-03-10 12:13:45,112 INFO [ProjectMetricsProcessor] Completed metrics update for project 00651c27-4769-4a68-bd74-8096bd16cde7
dt-apiserver  | 2023-03-10 12:13:45,124 INFO [ProjectMetricsProcessor] Completed metrics update for project 00651c27-4769-4a68-bd74-8096bd16cde7
dt-apiserver  | 2023-03-10 12:13:45,191 INFO [ProjectMetricsProcessor] Completed metrics update for project 00651c27-4769-4a68-bd74-8096bd16cde7
dt-apiserver  | 2023-03-10 12:13:45,204 INFO [ProjectMetricsProcessor] Completed metrics update for project 00651c27-4769-4a68-bd74-8096bd16cde7

This ultimately leads to the project not being deletable, as there will still be foreign key constraints in the PROJECTMETRICS table referring to it:
2023-03-10 12:13:39,784 ERROR [Transaction] Operation commit failed on resource: org.datanucleus.store.rdbms.ConnectionFactoryImpl$EmulatedXAResource@76d1c0b1, error code UNKNOWN and transaction [DataNucleus Transaction, ID=-505720900-330152, enlisted resources=[org.datanucleus.store.rdbms.ConnectionFactoryImpl$EmulatedXAResource@76d1c0b1]] : ERROR: update or delete on table "PROJECT" violates foreign key constraint "PROJECTMETRICS_FK1" on table "PROJECTMETRICS"
dt-apiserver  |   Detail: Key (ID)=(1) is still referenced from table "PROJECTMETRICS".

Expected Behavior
Metrics updates of deleted projects should not be processed anymore.
Dependency-Track Version
4.8.0-SNAPSHOT
Dependency-Track Distribution
Container Image, Executable WAR
Database Server
N/A
Database Server Version
No response
Browser
N/A
Checklist

[X] I have read and understand the contributing guidelines
[X] I have checked the existing issues for whether this defect was already reported

Fixed by getting rid of the metrics service.


Nested Accordian does not expand/collapse

Detailed description
When Accordion is nested inside another Accordion , the expand/collapse behavior of the nested Accordion does not work properly (i.e. unable to expand and collapse nested Accordion by clicking on it's header)
Understood from @Donisius that nesting Accordion inside and Accordion is not currently supported but since there is no Tree component till now, need ability to nest Accordion inside an Accordion to implement tree structure.
Carbon-ng version: 4.4

This is something you'll want to bring up with your design team with Carbon. It's fundamentally unsupported from a styling perspective (child accordions inherit parent accordions open style).
Unfortunately this is something you'll need to build out yourself if you require it immediately.