Need support for hotkey combination

Version: 1.0.0-alpha.62
Platform: win32 10.0.14393
Plugins:
I'm using screen on my remote ubuntu, it use Ctrl+A, Ctrl+D to detach. Many ssh tool support this functionality, I'm looking forward to meet it on Terminus!

Terminus uses screen internally for tab persistence - disable it or set it to tmux under settings, and remove the standard Ctrl-A hotkeys.

I don't see this option anywhere. Where is it?

@davidone if you're using a recent version, Ctrl-A hotkeys shouldn't be mapped on Windows at all. You should be able to use screen right away.

I'm using tmux (with Ctrl+a as binding sequence).
This is my config file:
hotkeys:
  copy:
    - Ctrl-c
  paste:
    - Ctrl-v
  settings:
    - Ctrl-s
  zoom-in:
    - Ctrl-+
  zoom-out:
    - Ctrl--
  previous-word: []
  next-word: []
  delete-previous-word: []
  delete-next-word: []
  clear: []
  reset-zoom: []
  new-tab: []
  ctrl-c: []
  shell:
    wsl:
      - Ctrl-n
  next-tab:
    - Ctrl-ArrowRight
  previous-tab:
    - Ctrl-ArrowLeft
ssh: {}
terminal:
  colorScheme:
    name: Material
    foreground: '#eceff1'
    background: 'rgba(38, 50, 56, 1)'
    cursor: '#FFCC00'
    colors:
      - '#000000'
      - '#D62341'
      - '#9ECE58'
      - '#FAED70'
      - '#396FE2'
      - '#BB80B3'
      - '#2DDAFD'
      - '#d0d0d0'
      - 'rgba(255, 255, 255, 0.2)'
      - '#FF5370'
      - '#C3E88D'
      - '#FFCB6B'
      - '#82AAFF'
      - '#C792EA'
      - '#89DDFF'
      - '#ffffff'
  environment: {}
  shell: wsl
  workingDirectory: ''
  autoOpen: true
  bell: visual
  background: theme
  bracketedPaste: false
  copyOnSelect: false
  altIsMeta: false
  ligatures: false
appearance:
  vibrancy: false
  opacity: 1
  frame: thin
  dock: 'off'
  theme: Windows 10
  vibrancyType: blur
enableAnalytics: false

and this is (part of) my .tmux.conf:
# Use CTRL-A as prefix-key (screen-like)
set -g prefix C-a
unbind C-b
bind C-a send-prefix


Add FC116: Cookbook depends on the deprecated compat_resource cookbook

compat_resource isn't required with later released of Chef 12 and should
not be used in modern cookbooks.
Signed-off-by: Tim Smith<EMAIL_ADDRESS>

Yes please.
/me runs this over sous-chefs.


versioning this, since the next image will change it

I also edited this into /gscmnt/gc2560/core/processing-profile/cwl-pipeline/31e873b623e2454e9b68a53dac9356c4/tools/somatic_docm_filter.cwl so the current default PP doesn't break when we push changes

This got resolved in a previous PR where I versioned everything.  Closing


Add custom formatting

Hi,
Great gem - wish we had it recently instead of lots of duplicate code adding prefixes in lots of ActionMailers :grimacing:
Ideally I would like to be able to add a prefix to the subject with just the stage name/environment in all environments except production where it would just be the default subject.
This PR adds a subject_format config option which can be a String or something that responds to call so that the user can entirely customise the subject header as desired - hope this is OK and something you would like added?
The default behaviour is as before but now I have the ability to customise the format for my need. My format would be something like the README example.

thanks for the contribution @rob-murray!
I'm going to take some time to review this and will let you know my thoughts.  It's a pretty big change, but i'm definitely in favor of extending the gem for more flexible email prefixes.

@rob-murray let me know what you think of the changes in #4.  it's an attempt to allow for overriding the configuration builder property with a custom proc so you can fully control the output prefix.

The PR #4 works for me :+1:
A reason I used a lambda with arguments was so that it was obvious to the user what was available without having to look at and call on the configuration class but no problem with this.
Thanks.

@wireframe Just from a code review point of view; what did you not like about this implementation or why did you prefer to change it? No problems just like the feedback.

Sure thing, I'm happy to provide more feedback.

supporting both string and lambda configuration adds unnecessary complexity IMO
lambdas with positional parameters are difficult API's to grok and it's very easy to accidentally use a positioned argument incorrectly.  using keyword arguments or an options hash makes the contract much more explicit and also much cleaner for future enhancements/refactoring.
I needed to do some internal refactoring anyways which made this pull request more difficult to merge.  (ex: extract builder from interceptor, test cleanup, etc)

thanks again for taking the time to put this together, and I couldn't have implemented this feature without your kicking it off!

Cool, thanks.. good to know!


FIX: Regression with category-topics block

Needs an explicit injection of the store service.

Thanks @CvX


lib.types: Add deferredModule

Description of changes
Great for submodule defaults. Example: network.defaults in NixOps.
Accepts modules, returns a list of modules, with a good default module location.
I'll quote the docs below. Also look at the example.
types.deferredModule
Whereas submodule represents an option tree, deferredModule represents a module value, such as a module file or a configuration.
It can be set multiple times.
Module authors can use its value, which is always a list of module values, in imports or in submoduleWith's modules parameter.
Note that imports must be evaluated before the module fixpoint. Because of this, deferred modules can only be imported into "other" fixpoints, such as submodules.
One use case for this type is the type of a "default" module that allow the user to affect all submodules in an attrsOf submodule at once. This is more convenient and discoverable than expecting the module user to type-merge with the attrsOf submodule option.
Refs https://github.com/NixOS/nixops/pull/1508
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

cc @infinisil

Nice change :D

Turns out deferredModule is just what was needed there

Nice! I've already used it in flake.parts perSystem, NixOps 2, and I will use it again in #176557

Thanks @infinisil!

@roberth do you have any usage examples? This looks useful but the only examples I could find were two mentions in a test case that didn't reveal much.

flake-parts perSystem is one. It's for modeling anything that's a function of system, as used by the new Nix Flakes CLI.


加 BMT 選項

總統樂觀各方即將捐大批BMT， 本站仍渾然不知，並非超前部署。屆時害使用者須再次登錄補之。

Regarding the name, maybe call it BMT/Pfizer.
I'm not sure. If it is not an official choice yet, at least have it grayed-out meaning that you are at least aware of it. But then you would need a notice on the very first page that says if you want BMT then don't bother filling in the forms yet, come back later.

既然是意願調查，未列 BMT ... 無理。
連訂貨卻無貨，商家仍會略提及其該商品。
不准選此意願代表未來不准。

大批 BMT 即將淹沒 Moderna, 本站不知情。


tags, versions and the status of this repository

Is this repository authoritative?
There are no tags/releases here and the version of the csrf-magic here is apparently still 1.0.4 while http://repo.or.cz/csrf-magic.git have 1.0.5.
Is there a chance to merge with 1.0.5 and make a new formal release please?
Thanks.

This repository is based upon the original repository from a code history point of view.  And Ezyang is the original author.  Doesn't seem like there's much activity but since those two points align, I would say yes.  For tags, I have tags on my repo which is based upon this one and those came from the original I believe.

@ezyang doesn't appear to be closing off old issue though.

For reference, I also created a new patch based on this repo which is currently open as a pull request which adds a bunch of functionality and configuration options.


Use fsspec.parquet module for better remote-storage read_parquet performance

Depends on fsspec#813
The new fsspec.parquet.open_parquet_file function offers an optimized version of fs.open for parquet-formatted data files. This PR updates both the "pyarrow" and "fastparquet" read_parquet implementations to (optionally) leverage this new feature.
API:
The new API change proposed in this PR is to add an open_file_options kwarg to read_parquet. This kwarg is intended as a central dictionary location for the user to define all options related to data-file opening.  Within this dictionary, the user can specify an optimized "parquet" precaching strategy within a nested "cache_options" dictionary:
ddf = dd.read_parquet(paths, ..., open_file_options={"cache_options": {"precache": "parquet"}})

We choose to define all cache-related options under "cache_options" to simplify current and future fsspec integration.  Although fsspec does not yet support the "precache" sub-field directly, there seems to be agreement that such a key can be recognized in the future (within fs.open and related).  Until then, Dask can simply perform a manual check for {"precache": "parquet"} and redirect the fs.open call to open_parquet_file.
Blockers:

[x] Merge/release fsspec#813 (or check that CI passes with master fsspec branch)
[x] Ensure that the ability to import fsspec.parquet is a sufficient check for compatibility (or improve this check if it is not)
[x] Add test to confirm that passing an open_parquet_file={} kwarg to read_parquet can be used to pass kwargs to fsspec.parquet.open_parquet_file

Performance Motivation
import dask.dataframe as dd

%%time
df = dd.read_parquet(
    ["gs://my-bucket/criteo-parquet/day_0.parquet"],
    columns=["I10"],
    split_row_groups=10,
    engine=...,
    storage_options=...,
    open_file_options={"cache_options": {"precache": "parquet"}},
)

# Main Branch - "fastparquet" Engine
CPU times: user 6.65 s, sys: 5 s, total: 11.6 s
Wall time: 8.52 s

# Main Branch - "pyarrow" Engine
CPU times: user 6.83 s, sys: 4.75 s, total: 11.6 s
Wall time: 8.04 s

# This PR - "fastparquet" Engine
CPU times: user 5.51 s, sys: 3.7 s, total: 9.21 s
Wall time: 4.78 s

# This PR - "pyarrow" Engine
CPU times: user 5.37 s, sys: 3.7 s, total: 9.07 s
Wall time: 4.75 s

I am not fully sure if the pyarrow-based engine should (always) make use of this. Similar optimization are already done by the parquet/dataset readers, and so if we don't get benefit of that when used through dask (which seems to be the case based on your timings above), we should maybe rather investigate why this is not the case.

I am not fully sure if the pyarrow-based engine should (always) make use of this. Similar optimization are already done by the parquet/dataset readers, and so if we don't get benefit of that when used through dask (which seems to be the case based on your timings above), we should maybe rather investigate why this is not the case.

Yes - There is no reason that pyarrow cannot optimize the data transfer in a similar way, and so I do want the final iteration of this to make the fsspec.parquet.open_parquet_file approach to be optional (with the default perhaps depending on the pyarrow version).

I am pretty busy in company things this week, but I'll get to it. Any chance #8470 can precede this one?

I am pretty busy in company things this week, but I'll get to it

Understandable - The only pressing thing about that PR is the decision of "how" to expose the file-opening options to the user. Right now its in a open_options={"file_format": "parquet", ...} kwarg.  There is pressure to use the fsspec.parquet optimization in RAPIDS/NVTabular, so the decision will be made in one of those libraries if we don't make it in Dask first :)

Any chance #8470 can precede this one?

Sure! I'll prioritize it for today.  Sorry - Just seeing that PR now (my notifications are a mess right now).

There is pressure to use the fsspec.parquet optimization in RAPIDS/NVTabular, so the decision will be made in one of those libraries if we don't make it in Dask first

That's fine. I am a little surprised, though - I had pictures the parquet module going out with the release and having a longer period of general community feedback following the blog post.

I think I am persuaded to push ahead, since then we get RAPIDS users too, and maybe more eyes on the fsspec code :)

@martindurant - I know it will take time before you can give this a careful review. That is totally fine - No rush on my end.
The only question I’d like to get your thoughts on “sooner” (rather than later) is the public change to the read_parquet API.  Right now, this PR proposes a new open_options parameter, where the user can pass in a dictionary of key-word arguments for a new dd.io.utils.open_input_files function. Within this dictionary, the user is free to specify a specific “file_format” item to turn on/off format-optimized file-opening behavior. Therefore, for read_parquet, {“file_format”: “parquet”} will be added to open_options automatically if the user does not specify {“file_format”: None} (or {“open_file_cb”: …} for a custom-open function).
Therefore, if a user want s to avoid using fsspec.parquet, they would need to do something like: dd.read_parquet(path, open_options={“file_format”: None}).  If they also wanted to use a non-default caching strategy, it would be something like:  dd.read_parquet(path, open_options={“file_format”: None, “cache_type”: “all”}).

Does this seem reasonable to you? Does the open_options dictionary and/or the "file_format" key make sense?  I am happy to revise and discuss.

To the specific API:

I think it's fine to add the extra kwarg. The term open_options is ambiguous, though, because the dataset is also "opened". Maybe file_open_options
adding open_input_files is fine, but in practice I don't expect any user to call it or know about it, and I don't expect the "open_file_cb" argument to be used either. The docs of what this all means probably go elsewhere
{"file_format": "parquet"} should still be considered experimental and not the default? It's also a bit confusing in the name, since indeed the format is parquet, here we are saying that we want to use parquet-specific logic for our file access pattern (i.e., precaching). It feels more like an fsspec storage_option. Maybe fsspec's open functions should allow for an open_options that gets passed to the fs.open calls? That latter idea is definitely a good idea, on reflection, but I'm not sure if it helps simplify the code here at all (maybe stuff the rg, cols into cache_options... etc).

I think it's fine to add the extra kwarg. The term open_options is ambiguous, though, because the dataset is also "opened". Maybe file_open_options

file_open_options works for me.  Note that soon after (or possibly before) this PR, I’d also like to revise the way kwargs are handled in read_parquet. That is, I’d like the function signature (and docstring) to include dataset_options= and read_options= (rather than just looking for these options under the “dataset” and “read” keys of kwargs). The reason I chose open_options= was just that this particular trio of names seemed to make the most sense: ’dataset_options’, open_options, and read_options.

adding open_input_files is fine, but in practice I don't expect any user to call it or know about it, and I don't expect the "open_file_cb" argument to be used either. The docs of what this all means probably go elsewhere

I see - I also don’t expect any users to know or care about open_input_files, but I wanted to create one clear point of logic for file-opening optimizations.  Perhaps it would be best to make this function more-explicitly private, and use the read_parquet docstring to explain behavior?

Regarding "open_file_cb”: The key use case here is the direct generation of native Arrow-file objects. For engine=“pyarrow” with S3, S3FileSystem.open_input_file is likely to have similar performance as fsspec.parquet.open_parquet_file.  However, there may be cases where the native file is preferable, and we will certainly want to be able to compare performance if/when there are improvements in pyarrow.  What I am really trying to say here is that I feel strongly that we need to allow the user to override the default file-open function, but I don’t care much about what that mechanism is exactly.

{“file_format": "parquet"} should still be considered experimental and not the default?

I am fine with leaving the vanilla fs.open as the default for now.

It's also a bit confusing in the name, since indeed the format is parquet, here we are saying that we want to use parquet-specific logic for our file access pattern (i.e., precaching). It feels more like an fsspec storage_option. Maybe fsspec's open functions should allow for an open_options that gets passed to the fs.open calls? That latter idea is definitely a good idea, on reflection, but I'm not sure if it helps simplify the code here at all (maybe stuff the rg, cols into cache_options... etc).

I agree that it would be nice for these new “options” to be included in storage_options under open_options, but it is also seems possible that a user may want to read both CSV and Parquet files using the same fs.  I think you hit the nail on the head when you said that we mostly want to control the “precaching” mechanism for a specific fs.open(…, cache_type=“parts”) call.
Perhaps the simplest solution to all this confusion is to simply check for cache_type=“parquet” in fs.open, and redirect the call through fsspec.parquet.open_parquet_file when this criteria is met?  This way, the user could include all format-specific options within cache_options, and the same private _open_input_files utility  could be used before and after the fsspec change to handle format-specific file opening (note that open_parquet_file arguments would just be included in cache_options):
_open_input_files(
    paths,
    fs=None,
    open_func=None,  # Defaults to `fs.open`
    cache_type=None,  # Allow "parquet" (in addition to "parts", etc)
    cache_options=None,
    **kwargs,
):

Update: After an offline discussion with @martindurant, I decided to go with the following design:

The new read_parquet kwarg is called open_file_options
The dictionary of key-value arguments defined within open_file_options is passed to fs.open when a parquet data file is open for reading.  However, there are two keys that receive special treatment:

If "open_file_func" is defined, the (callable) value will be used in lieu of fs.open. The purpose of this option is mostly to enable the optional use of native Arrow file-systems.
If "cache_options" is defined, Dask will check if this (sub-)dictionary contains {"precache": "parquet"}. If so, the fsspec.parquet.open_parquet_file function will be used in lieu of fs.open (with the other elements of cache_options being used as kwargs for that function call).

Important Note: In the future,  this "precache" option should be handled upstream in fs.open (and fsspec.open_files). In other words, we shouldn't need to manually call open_parquet_file in Dask. However, I don't feel this upstream change should be a blocker for this PR.  The only "blocker" is that we establish that the "precache" option (and kwargs for the appropriate precaching function) should be stored under the existing cache_options argument to fs.open.

I agree with everything in the comment above.

Thanks @martindurant !  Before I settle on what we currently have in this PR, can I get your thoughts on the alternative proposal I recently described in fsspec#885? Note that I am currently favoring the "v2b" proposal (and the temporary logic required on the Dask side is only a minor change from what we have here).

I will comment there soon

Further Update to Previous Status:
Due to a slight change in preference after compiling fsspec#885, all precache-related options should now be passed to open_file_options under a new "precache_options" key (and not under "cache_options"). These options must include a "method" key to specify the specific precaching method/function to be used.
This change is minor in terms of modified lines in this PR, and so I would be happy to further modify or roll back the tweak if necessary.  However, to summarize the basic motivation: I feel that the precache phase must be explicitly seperate from cache initialization, and so a distinct argument for this separate phase seems necessary to me.

It seems like you are generally supportive of the rough proposal in fsspec#885 @martindurant - Does this mean the precache_options approach used in this PR is reasonable?  I'm cautiously optimistic that I may not need to completely revise this PR again - Woohoo

yes, supportive!

Is there any interest or time for a review this week @dask/io?  Also, do we know of new people that we can invite to join the "dask/io" team? :)
If no one has time to look through this in the next few days, I will likely do a deep review myself and merge on Friday.

@martindurant - I plan to give this a final review soon, and will probably merge by the end of the day if there are no objections :)

no objections here


Authenticating from a remote client

For feature requests, please fill in the next sections:
What feature are you missing?
My workflow involves developing on a remote server by connecting to it via ssh. When I do graphcool init , it gives me a message about opening the browser for auth. Since the server is headless with no browser installed, this message stays indefinitely, and I cannot proceed.
I worked around this by following changes to /dist/src/api/GraphcoolAuthServer.js
 32    -       while (true) {
 32    +       console.log(`${constants_1.authUIEndpoint}?cliToken=${cliToken}&authTrigger=${this.authTrigger}`);
 33    +       while (true) {

How could this feature look like in detail? Tradeoffs?
Would like to have a timeout where if it has not authenticated in a while (60 sec?), console prints a link to the screen, to manually open the browser and authenticate.
I would submit a pull request, but there's no code or anything about contributing in the repo, yet.

Hey @hammadfauz have you seen the graphcool auth --token command? You can get a valid token from within the project settings in the Console.

@marktani No, I haven't tried that. But even with the token, as a new user, I wouldn't know the auth url.

Hey @hammadfauz, let's continue the discussion in https://github.com/graphcool/cli/issues/281 :)


ms.topic -> reference

Docs Build status updates of commit 783ce47:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/latest/abort-controller-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/advisor.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/ai-form-recognizer-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/ai-metrics-advisor-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/ai-text-analytics-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/analysis-services.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/app-configuration-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/appservice.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/authorization.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/automation.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/backup.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/batchai.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/cdn.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/cognitive-services/bing-auto-suggest-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/cognitive-services/bing-custom-image-search-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/cognitive-services/bing-custom-search-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/cognitive-services/bing-entity-search-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/cognitive-services/bing-image-search-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/cognitive-services/bing-news-search-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/cognitive-services/bing-spell-check-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/cognitive-services/bing-video-search-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/cognitive-services/bing-visual-search-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/cognitive-services/bing-web-search-api-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/commerce.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/communication-chat-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/communication-common-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/communication-identity-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/communication-phone-numbers-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/communication-sms-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/container-registry.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/container-service.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/core-amqp-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/core-auth-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/core-client-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/core-http-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/core-lro-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/core-paging-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/core-rest-pipeline-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/data-lake-analytics.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/data-lake-store.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/data-tables-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/devtest-labs.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/digital-twins-core-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/dns.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/event-hub.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/event-hubs-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/eventgrid-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/identity-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/iot-hub.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/key-vault-index.md
:warning:Warning
View (azure-node-latest)
Details

This comment lists only the first 50 files in the pull request.

docs-ref-services/latest/abort-controller-readme.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/advisor.md

Line 10, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'Advisor'.
Line 39, Column 70: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/samples/browse/?languages=nodejs' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/ai-form-recognizer-readme.md

Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 27, Column 1: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/ai-form-recognizer' will be broken in isolated environments. Replace with a relative link.
Line 28, Column 1: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/form-recognizer/' will be broken in isolated environments. Replace with a relative link.
Line 37, Column 5: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/cognitive-services-apis-create-account?tabs=multiservice%2Cwindows' will be broken in isolated environments. Replace with a relative link.
Line 37, Column 158: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 41, Column 31: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/cognitive-services-apis-create-account?tabs=multiservice%2Cwindows' will be broken in isolated environments. Replace with a relative link.
Line 47, Column 15: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/cognitive-services-apis-create-account-cli?tabs=windows' will be broken in isolated environments. Replace with a relative link.
Line 75, Column 120: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 83, Column 117: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 107, Column 66: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/authentication#assign-a-role-to-a-service-principal' will be broken in isolated environments. Replace with a relative link.
Line 132, Column 281: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/form-recognizer/overview#train-without-labels' will be broken in isolated environments. Replace with a relative link.
Line 133, Column 290: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/form-recognizer/overview#train-with-labels' will be broken in isolated environments. Replace with a relative link.
Line 138, Column 90: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/form-recognizer/label-tool?tabs=v2-1' will be broken in isolated environments. Replace with a relative link.
Line 350, Column 457: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/form-recognizer/quickstarts/curl-train-extract#train-a-form-recognizer-model' will be broken in isolated environments. Replace with a relative link.
Line 406, Column 64: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/form-recognizer/label-tool?tabs=v2-1' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/ai-metrics-advisor-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'metricsadvisor'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 27, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/ai-metrics-advisor' will be broken in isolated environments. Replace with a relative link.
Line 28, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/metrics-advisor/' will be broken in isolated environments. Replace with a relative link.
Line 43, Column 15: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/cognitive-services-apis-create-account' will be broken in isolated environments. Replace with a relative link.
Line 43, Column 169: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 63, Column 120: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 76, Column 126: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 162, Column 17: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/metrics-advisor/glossary' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/ai-text-analytics-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'textanalytics'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 41, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/ai-text-analytics' will be broken in isolated environments. Replace with a relative link.
Line 42, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/text-analytics/' will be broken in isolated environments. Replace with a relative link.
Line 57, Column 15: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/cognitive-services-apis-create-account' will be broken in isolated environments. Replace with a relative link.
Line 57, Column 168: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 77, Column 119: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 85, Column 116: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 110, Column 23: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/authentication#assign-a-role-to-a-service-principal' will be broken in isolated environments. Replace with a relative link.
Line 151, Column 5: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/text-analytics/overview#data-limits' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/analysis-services.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 10, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 12, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'Analysis Services'.
Line 34, Column 70: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/samples/browse/?languages=javascript' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/app-configuration-readme.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'appconfiguration'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 16, Column 1: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/overview' will be broken in isolated environments. Replace with a relative link.
Line 27, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/app-configuration' will be broken in isolated environments. Replace with a relative link.
Line 28, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/' will be broken in isolated environments. Replace with a relative link.
Line 49, Column 6: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/' will be broken in isolated environments. Replace with a relative link.
Line 53, Column 65: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 71, Column 60: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/concept-enable-rbac#azure-built-in-roles-for-azure-app-configuration' will be broken in isolated environments. Replace with a relative link.
Line 104, Column 5: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/app-configuration/appconfigurationclient' will be broken in isolated environments. Replace with a relative link.
Line 106, Column 38: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/app-configuration/configurationsetting' will be broken in isolated environments. Replace with a relative link.
Line 109, Column 50: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/app-configuration/configurationsetting' will be broken in isolated environments. Replace with a relative link.
Line 109, Column 207: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/app-configuration/configurationsettingparam' will be broken in isolated environments. Replace with a relative link.
Line 109, Column 334: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/app-configuration/configurationsettingid' will be broken in isolated environments. Replace with a relative link.
Line 207, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/overview' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/appservice.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 10, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 12, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'appservice'.
Line 40, Column 68: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/samples/browse/?languages=javascript' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/authorization.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 10, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 12, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'Authorization'.
Line 37, Column 70: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/samples/browse/?languages=javascript' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/automation.md

Line 10, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'Automation'.
Line 33, Column 70: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/samples/browse/?languages=javascript' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/backup.md

Line 10, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'Backup'.
Line 33, Column 70: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/samples/browse/?languages=javascript' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/batchai.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 10, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.

docs-ref-services/latest/cdn.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 10, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 12, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'CDN'.
Line 35, Column 70: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/samples/browse/?languages=javascript' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/cognitive-services/bing-auto-suggest-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitive-services/bing-custom-image-search-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitive-services/bing-custom-search-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitive-services/bing-entity-search-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitive-services/bing-image-search-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitive-services/bing-news-search-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitive-services/bing-spell-check-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitive-services/bing-video-search-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitive-services/bing-visual-search-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitive-services/bing-web-search-api-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/commerce.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 10, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 12, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'Commerce'.
Line 35, Column 70: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/samples/browse/?languages=javascript' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/communication-chat-readme.md

Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 19, Column 46: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/overview' will be broken in isolated environments. Replace with a relative link.
Line 26, Column 134: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/powershell/module/az.communication/new-azcommunicationservice' will be broken in isolated environments. Replace with a relative link.
Line 26, Column 179: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 175, Column 34: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/concepts/authentication?tabs=javascript' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/communication-common-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'communication'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 24, Column 134: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/powershell/module/az.communication/new-azcommunicationservice' will be broken in isolated environments. Replace with a relative link.
Line 24, Column 179: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 96, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/concepts/authentication?tabs=javascript' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/communication-identity-readme.md

Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 24, Column 133: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/powershell/module/az.communication/new-azcommunicationservice' will be broken in isolated environments. Replace with a relative link.
Line 24, Column 178: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/communication-phone-numbers-readme.md

Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 26, Column 133: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/powershell/module/az.communication/new-azcommunicationservice' will be broken in isolated environments. Replace with a relative link.
Line 26, Column 178: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/communication-sms-readme.md

Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 24, Column 134: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/powershell/module/az.communication/new-azcommunicationservice' will be broken in isolated environments. Replace with a relative link.
Line 24, Column 179: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 35, Column 214: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/quickstarts/telephony-sms/get-phone-number' will be broken in isolated environments. Replace with a relative link.
Line 153, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/quickstarts/telephony-sms/send?pivots=programming-language-javascript' will be broken in isolated environments. Replace with a relative link.
Line 154, Column 102: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/quickstarts/telephony-sms/handle-sms-events' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/container-registry.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 10, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 12, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'Container Registry'.
Line 33, Column 70: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/samples/browse/?languages=javascript' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/container-service.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 10, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 12, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'Container Service'.
Line 32, Column 70: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/samples/browse/?languages=javascript' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/core-amqp-readme.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 114, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Contributing') are not allowed. You can only have one top-level heading.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 17, Column 20: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-amqp-protocol-guide' will be broken in isolated environments. Replace with a relative link.
Line 38, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-amqp-protocol-guide#claims-based-authorization' will be broken in isolated environments. Replace with a relative link.
Line 39, Column 29: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-amqp-protocol-guide#amqp-management' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/core-auth-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'core'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/core-client-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'core'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/core-http-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'core'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 46, Column 46: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure/?view=azure-cli-latest' will be broken in isolated environments. Replace with a relative link.
Line 46, Column 46: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/cli/azure/?view=azure-cli-latest. Otherwise, remove the view parameter.

docs-ref-services/latest/core-lro-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'core'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 26, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/core-lro' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/core-paging-readme.md

Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/core-rest-pipeline-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'core'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/data-lake-analytics.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 10, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 12, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'Data Lake Analytics'.
Line 33, Column 70: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/samples/browse/?languages=nodejs' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/data-lake-store.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 10, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 12, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'Data Lake Store'.
Line 33, Column 70: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/samples/browse/?languages=nodejs' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/data-tables-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'tables'.
Line 65, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#tableserviceclient-with-azurenamedkeycredential' in 'docs-ref-services/latest/data-tables-readme.md'.
Line 70, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#tableclient-with-tokencredential-aad' in 'docs-ref-services/latest/data-tables-readme.md'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 36, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/data-tables' will be broken in isolated environments. Replace with a relative link.
Line 37, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/tables/table-storage-overview/' will be broken in isolated environments. Replace with a relative link.
Line 49, Column 80: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/tables/table-storage-quickstart-portal' will be broken in isolated environments. Replace with a relative link.
Line 49, Column 185: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/create-cosmosdb-resources-portal' will be broken in isolated environments. Replace with a relative link.
Line 84, Column 20: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/rest/api/storageservices/cross-origin-resource-sharing--cors--support-for-the-azure-storage-services' will be broken in isolated environments. Replace with a relative link.
Line 373, Column 1: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/rest/api/storageservices/table-service-error-codes' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/devtest-labs.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 10, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 12, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'DevTest Labs'.
Line 5, Column 12: [Suggestion-ms-author-invalid] Invalid value for 'ms.author', 'v-craic' is not a valid Microsoft alias.
Line 33, Column 70: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/samples/browse/?languages=javascript' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/digital-twins-core-readme.md

Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 130, Column 58: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/digital-twins/' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/dns.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 10, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 12, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'DNS'.
Line 33, Column 70: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/samples/browse/?languages=javascript' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/event-hub.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 10, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 12, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'Event Hub'.
Line 25, Column 74: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/arm-eventhub' will be broken in isolated environments. Replace with a relative link.
Line 33, Column 114: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/event-hubs' will be broken in isolated environments. Replace with a relative link.
Line 34, Column 114: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/eventhubs-checkpointstore-blob/' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/event-hubs-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'eventhubs'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 17, Column 344: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/event-hubs-about' will be broken in isolated environments. Replace with a relative link.
Line 24, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/event-hubs' will be broken in isolated environments. Replace with a relative link.
Line 55, Column 6: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/' will be broken in isolated environments. Replace with a relative link.
Line 70, Column 1: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/event-hubs/eventhubconsumerclient' will be broken in isolated environments. Replace with a relative link.
Line 71, Column 23: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/event-hubs/eventhubproducerclient' will be broken in isolated environments. Replace with a relative link.
Line 76, Column 336: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/event-hubs-get-connection-string#get-connection-string-from-the-portal' will be broken in isolated environments. Replace with a relative link.
Line 107, Column 710: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/authorize-access-azure-active-directory' will be broken in isolated environments. Replace with a relative link.
Line 133, Column 47: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/event-hubs-features' will be broken in isolated environments. Replace with a relative link.
Line 204, Column 47: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/event-hubs/eventhubproducerclient#createbatch-createbatchoptions-' will be broken in isolated environments. Replace with a relative link.
Line 205, Column 37: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/event-hubs/eventdatabatch#tryadd-eventdata--tryaddoptions-' will be broken in isolated environments. Replace with a relative link.
Line 207, Column 38: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/event-hubs/eventhubproducerclient#sendbatch-eventdatabatch--sendbatchoptions-' will be broken in isolated environments. Replace with a relative link.
Line 249, Column 48: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/event-hubs/eventhubconsumerclient' will be broken in isolated environments. Replace with a relative link.
Line 385, Column 12: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/event-processor-balance-partition-load' will be broken in isolated environments. Replace with a relative link.
Line 446, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/iot-hub/iot-hub-devguide-messages-read-builtin' will be broken in isolated environments. Replace with a relative link.
Line 522, Column 1: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/event-hubs-about' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/eventgrid-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'eventgrid'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 28, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/eventgrid/' will be broken in isolated environments. Replace with a relative link.
Line 29, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/' will be broken in isolated environments. Replace with a relative link.
Line 46, Column 15: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid' will be broken in isolated environments. Replace with a relative link.
Line 46, Column 141: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 74, Column 112: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 82, Column 115: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 190, Column 88: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 215, Column 47: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/kubernetes/' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/identity-readme.md

Line 0, Column 0: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 17, Column 132: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/core-auth/tokencredential' will be broken in isolated environments. Replace with a relative link.
Line 21, Column 174: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/identity' will be broken in isolated environments. Replace with a relative link.
Line 37, Column 7: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 55, Column 26: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 65, Column 206: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/scenario-spa-app-registration' will be broken in isolated environments. Replace with a relative link.
Line 172, Column 5: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/overview' will be broken in isolated environments. Replace with a relative link.
Line 174, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/how-to-use-vm-token' will be broken in isolated environments. Replace with a relative link.
Line 175, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/app-service/overview-managed-identity' will be broken in isolated environments. Replace with a relative link.
Line 176, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/aks/use-managed-identity' will be broken in isolated environments. Replace with a relative link.
Line 177, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cloud-shell/msi-authorization' will be broken in isolated environments. Replace with a relative link.
Line 178, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/azure-arc/servers/managed-identity-authentication' will be broken in isolated environments. Replace with a relative link.
Line 179, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-fabric/concepts-managed-identity' will be broken in isolated environments. Replace with a relative link.
Line 198, Column 290: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/app-objects-and-service-principals' will be broken in isolated environments. Replace with a relative link.
Line 199, Column 290: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/app-objects-and-service-principals' will be broken in isolated environments. Replace with a relative link.
Line 205, Column 469: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/v2-oauth2-auth-code-flow' will be broken in isolated environments. Replace with a relative link.
Line 206, Column 454: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/v2-oauth2-device-code' will be broken in isolated environments. Replace with a relative link.
Line 207, Column 454: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/v2-oauth-ropc' will be broken in isolated environments. Replace with a relative link.
Line 208, Column 454: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/v2-oauth2-auth-code-flow' will be broken in isolated environments. Replace with a relative link.
Line 214, Column 294: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure/authenticate-azure-cli' will be broken in isolated environments. Replace with a relative link.
Line 237, Column 56: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/identity' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/iot-hub.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 10, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 43, Column 68: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/samples/browse/?languages=javascript' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/key-vault-index.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 10, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 25, Column 74: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/arm-keyvault' will be broken in isolated environments. Replace with a relative link.
Line 34, Column 92: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/keyvault-keys' will be broken in isolated environments. Replace with a relative link.
Line 35, Column 92: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/keyvault-secrets' will be broken in isolated environments. Replace with a relative link.
Line 36, Column 92: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/keyvault-certificates' will be broken in isolated environments. Replace with a relative link.
Line 37, Column 92: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@azure/keyvault-admin' will be broken in isolated environments. Replace with a relative link.

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Custom Sort Events

Use case
Pre-Sorted Columns can be achieved from server but I what if I the table is sorted on any other column order. Is there any way to emit events with [clrDgSortBy]?
Examples
For instance if I want to store the sorting state in ngrx and update the store on each column filtering

Hi @technbuzz
You should subscribe to (clrDgRefresh), it emits a common event for every operation that might lead to server-side data update, including - sorting, filtering, paging.
You can see details and the format of the event here:
https://vmware.github.io/clarity/documentation/v0.13/datagrid/server-driven


wrong position of bounding box

https://forum.babylonjs.com/t/wrong-position-of-bounding-box/51828
(while the forum thread is marked as solved, the solution is just a workaround for my specific use-case, the bug itself is still present)
Repro

Bug repro on playground:
Expected result: clicking the violin attached to bone will show bounding box in correct position
Current result: violin's bounding box is misplaced

Screenshots

Desktop (please complete the following information):

OS: macOS 14.6
Browser Firefox
Version 128

There is no bug. You are picking the root and not the violin itself
Here is a fix: https://playground.babylonjs.com/#6QTQLT#19
The root even if flagged as a mesh has no geometry.

To be a bit more complete:

The getHierarchyBoundingVectors API return the min and max in world space
The boundingInfo constructor expects the min and max to be in local space for the given object
The main problem with your approach is to rebuild a boundingInfo for a specific object out of data outside of its local space
One solution could be to get the min and max of each child (but in their local space), transform that vectors into world space (this is not what you get out of minimumWorld and maximumWorld because this one are axis aligned before being returned) and then convert these vectors into main object local space to build its bbox

Example: https://playground.babylonjs.com/#6QTQLT#22

ok, thank you.


剪切板增强工具

推荐一个新的剪切板增强工具哈。
Copa，https://www.copyable.cn/?

@CodingBingo 使用很顺滑？😆

还行吧

https://clipy-app.com/ clipy

We have a bunch of high quality clipboard apps in the list already. What makes this one special?


Any function for log rotate?

Like auto archive log by date or size?

maybe revel would provide revel.SetLogger() function to do so?

rotate log file by date or size is a strong demand

Pr #1213 has this feature, give it a thumbs up to vote for its
implementation
On Tue, Aug 1, 2017, 3:24 AM Rambone<EMAIL_ADDRESS>wrote:

rotate log file by date or size is a strong demand
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/revel/revel/issues/568#issuecomment-319331799, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABUsBjfwM-qPbKp69rYA6cNWSdHXAsapks5sTvz2gaJpZM4BtN9M
.


Dotted lists don't display correctly in the debugger

Even though they do in the tree diagram. Weird!

Though of course dotted lists won't be present in the final version, so this probably won't matter anyway.


"groups" claim maybe weird in OIDC with Harbor

Particularly in OIDC auth.
Configuring OIDC auth for my Harbor:
Casdoor Organinzation: built-in
User Groups:

admin
admin-harbor (sub of admin)

In harbor, I configured "Group Claim Name" to "groups" as mentioned in #1929 and "OIDC Admin Group" to admin-harbor.
However when user registered and logged in he is not admin. And "Groups" page in harbor recognized a "built-in" group. Confusing.
I do noticed that /api/get-account returned "groups" field, in which groups are listed as uuids, but even if I alted "OIDC Admin Group" in harbor to the uuid of any group, nothing happens. Maybe the "groups" claim in fact delivered "build-in", the organization name to harbor is the issue?
PS. weird that commit mentioned in #1929 is marked unsuccessful...

@WinterOfBit please show your result for get-account API like:

and what do you get and what do you expect in Harbor?

@WinterOfBit please show your result for get-account API like:

and what do you get and what do you expect in Harbor?

Seems /api/get-account stills returns group-uuids. Already bumped to v1.342.0 and recreated groups:

Do I need to purge my database as well?
I hope harbor to recognize my user group and assign admin correctly. For now harbor claimed organization name "built-in" from "groups" claim

@WinterOfBit

Do I need to purge my database as well?

Yes, please delete DB
And use latest code: https://github.com/casdoor/casdoor/commit/58aa7dba6a32c840ce21e215250c16f46123a7a1
Then restart Casdoor


[chip-test] chip_sw_ast_sys_clk_jitter

Test point name
chip_sw_ast_sys_clk_jitter
Host side component
No response
OpenTitanTool infrastructure implemented
No response
Contact person
@tjaychen
Checklist
Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.

[ ] Check if existing test covers most or all of this testpoint (if so, either extend said test to cover all points, or skip the next 3 checkboxes)
[ ] Device-side (C) component developed
[ ] Bazel build rules developed
[ ] Host-side component developed
[ ] HJSON test plan updated with test name (so it shows up in the dashboard)
[ ] Test added to dvsim nightly regression (and passing at time of checking)

Looks like we haven't filed an issue for this test. @tjaychen could you tag a priority for this?

hmmm... i believe this test is about verifying AST's jitter clock is actually fetching entropy and varying its frequency as expected.
So this would make it more of a closed source test than an open source test.
@sha-ron
@msfschaffner
can you guys confirm if this is what you remember?

actually this was added a long time ago, I think the spirit of this test may have already been satisfied by the clkmgr_jitter test, so maybe this is something we can remove.
@sha-ron i think it's probably a valid question on how you guys want to verify the jitter is doing what it's supposed to on the closed source side thoughg.

Looks like clkmgr_jitter covers what it should in the open source and we will check the rest of the functionality in the closed source side so I think it can be closed.

sounds good. thanks Sha-ron.
@weicaiyang i'll remove this from the testplan and then we can close this issue.


Enhance CRI workflow to support pod level user namespace

What is the problem you're trying to solve
There are ongoing works to enable pod level user namespace：
https://github.com/kubernetes/enhancements/issues/127
https://github.com/kubernetes/enhancements/pull/3275
User namespace (uid/gid remap) has already been supported by ctr, containerd core  and runC, but there are still some issues in the CRI subsystem.  When doing PoC for pod level user namespace, the first issue we encountered is:
RunPodSandbox for &PodSandboxMetadata{Name:nginx-sandbox,Uid:018b4704-222a-4657-990e-bb568b870f4b,Namespace:default,Attempt:1,} failed, error  error="failed to create containerd task: failed to create shim task: OCI runtime create failed: container_linux.go:346: starting container process caused \"process_linux.go:449: container init caused \\\"rootfs_linux.go:58: mounting \\\\\\\"sysfs\\\\\\\" to rootfs \\\\\\\"/home/wanglei01/opt/open/go_project/containerd_upstream/bin/run/containerd/io.containerd.runtime.v2.task/k8s.io/7388141ccd209d9df243a1b7df52c9510436e5d89b072904bd6778400d82301c/rootfs\\\\\\\" at \\\\\\\"/sys\\\\\\\" caused \\\\\\\"operation not permitted\\\\\\\"\\\"\": unknown"

After some investigation, we have found that the failure is caused by the flow to create namespaces.
When mounting sysfs, linux kernel checks that current user has CAP_SYS_ADMIN cap in the user namespace associated with the net namespace. And the current flow to create namespaces for sandbox/infra container is:

call netns to create net ns for the pod if the net namespace mode is not NODE.
call cni to initialize the pod network
configure other namespace for the infrastructure/app containers
call container runtime to create other namespaces for the container, including the user ns.

With above flow, the net namespace will be associated with the init user ns because it's created before the pod user ns. And it fails to mount the sysfs in the pod user ns.
Describe the solution you'd like
We could tune the flow to create namespaces and initialize the pod network for sandbox as below:

configure all needed namespaces for the sandbox/infra container, including the user namespace
call runtime to start the infra container and creates all needed namespaces
call CNI to initialize pod network with the net ns created by the runtime for the infra container

Additional context
No response

@jiangliu Hi! Please tag me in the userns containerd related issues, I'm actively working on the KEP and containerd patches, I would love to help with any related issue found.
I've done some PoC patches (based on some other PoC patches made by a coworker) and we hit this issue too but we chose a different solution IIUC.
Containerd CRI plugin now creates the netns and then calls the OCI runtime to create the other namespaces. Do you propose to create the userns and netns (so the netns is owned by the userns) and then call the OCI runtime? Am I understanding correctly?
What I'm doing in the PoC patches I wrote is different. We don't create the netns at all, we just specify to the OCI runtime that we want a usernamespace too, and the OCI runtime creates all the needed namespaces in the proper order, so permissions work as expected. If a netns and userns needs to be created, the userns is created first and all by the OCI runtime.
Then, we get the netns from the pid (/proc/pid/ns/net) and use it for the CNI setup (bind mounting and all). This works fine and it is quite simple. Furthermore, we also remove the tricks with the go runtime containerd has today, as we don't need to create a netns for linux at all (we just hand off this task to the OCI runtime).
What do you think of this approach?
I haven't polished the code and at the PoC level this is currently it probably breaks windows, I was planning to improve it once the KEP changes are merged for 1.25 and open a PR.
Would you like to join forces for the containerd patches for K8s user namespaces support? :)

Oh, sorry, now that I see the PR it seems you are doing mostly the same thing there, right? Sorry for the noise, I misunderstood the text description, then :D

:-)

Would you like to join forces for the containerd patches for K8s user namespaces support? :)
That will be really great:) I have followed most discussion related to KEP127 and feel it's exciting to get IDMapping ready for use. But it takes time to wait for the IDMapping feature the field:)
On the other hand, we have some workloads depending on user namespace, to support some special capabilities requirements of sidecar containers. So our short-term solution is to enable user namespace with identity mapping.
Feel some work will helps to pave the way for IDMapping, so contribute them to the community.

And we hope we could support both pod-level user namespace and container-level user namespace. The pod-level user namespace is already covered by the IDMapping KEP, but the container-level user namespace seems likes something uncovered yet. We hope to use container-level user namespace to support host network mode, though I know that's a challenging task:)

@jiangliu great, as I mentioned here, I'm Rodrigo Campos/rata at CNCF slack or k8s slack. Please write me there, I couldn't find you with your github username. We can coordinate there so we don't duplicate our efforts with the PRs :)
Also, please note that the KEP is not tied to idmap mounts. In fact, phase 1 should work without idmap mounts (just chowning in containerd, plus adding the metacopy overlayfs param to make the chown faster should be enough). Later phases of the KEP will probably require idmap (maybe not, maybe some improved limited support will be possible when idmap mounts is not there), but idmap is not in the OCI runtime-spec yet and the KEP parts have not been proposed. Nor the CRI changes for that (need to be in sync with OCI runtime-spec changes, probably).
Also, after the runtime-spec changes are done, support will be needed in runc for idmap mounts. It is going to be a long jurney for idmap mounts support.
Please write me on slack, I'm curious to ask more question about what you want for nested userns for the containers too :)

Close by https://github.com/containerd/containerd/pull/7679


request to add Olalekan Ikotun to the triage team.

Please add Olalekan Ikotun to the triage members.

Alright, I haven't seen any objections or anything, so I added to the triage group 👍 . I know from the last meeting we are working to document out the process, so just holding this PR to make sure I didn't miss something when adding.

Closing out PR as I confirmed that @lekanikotun is in the group and we are working to pull membership data directly from the GitHub team.


Add-SPONavigation cmdlet cannot add anything to TopNavigation

I cannot add anything to the Top Navigation anymore.
Quicklaunch works fine.
cmd written in may version of the cmdlet works fine:
Add-SPONavigationNode -Title "TEST" -Location Top
Cmd written in June version:
Add-SPONavigationNode -Title "TEST" -Location TopNavigationBar
Note that Location has changed from top to TopNavigationBar.
There is also a new choice: SearchNav

The last time this cmdlet was changed in code was on the 12th of March 2013. However, when I use
Add-SPONavigation_Node -Title "TEST" -Location Top -Url https://www.test.com
The node is added as expected.
The location parameter is using an enumeration that hasn't changed either since several months ago.

Hi.
I also succeed with the same command as you:
Add-SPONavigationNode -Location TopNavigationBar -Title Test -Url https://test
But if I do not use the -Url, it does not work.
Add-SPONavigationNode -Location TopNavigationBar -Title Test
So we can therefore perhaps conclude with the url is a required property, and that the cmdlet will work even if the Location parameter values changes (from Top to TopNavigationBar)
The result I am looking for is to add a heading (Folder) and then multiple links under this heading.
Perhaps it will be possible to add this as a new feature?

hi, I'd need this too:

possibility to create headings
possibility to set audiences

currently not available, right?
br, mos


kandane algorithm

added a code of kandane's algorithm in c++

Sorry to inform but this repository has been excluded from hacktoberfest. So inorder to make your PR count towards hacktoberfest, request you to make your contribution in this repository -> https://github.com/SR-Sunny-Raj/Hacktoberfest2022-for-all


Documented using event handlers to handle input without direct DOM reads or refs

Thanks for the edit, this is definitely a better approach.

Thanks for the edit, this is definitely a better approach.


in Data Viz tab, allow user to specify line types, marker types, etc.

related issues:
specify mins and maxes
force same vertical mins and maxes when y0 and y1 are both plotted

This will be related to the overall overhaul of data viz

This is already possible by clicking the green check mark above the plots. We may still want to improve the dialogs somehow.


feat(git-node): add git node vote

This PR adds git node vote command, which can be used to participate to a vote using Caritat. The idea of integrating that in ncu is that TSC folks are very likely to already have ncu installed and configured on their local machine, reducing the possible friction for a user to cast a vote, as they don't need to provide their GitHub credentials to make the API calls.
Code reviews are welcome, note that we should wait for the transfer of Caritat npm package to the @node-core scope to be completed before landing.

@nodejs/node-core-utils given this PR is relatively large, it would help to have some extra pair(s) of eyes to review it :)

Since this is specific to tsc, why not make it “git node tsc-vote”?


Upgrade flow-bin dependecy to the latest version.

@frewsxcv were you planning on resolving that conflict? I think this is ready to merge otherwise.

I'm going to close this for now since I'm going to assume it's abandoned. If you want to resolve those conflicts feel free to open another PR.


PHP: change phpunit version from 4.8.36 to 5.7.27

Update PHPUnit version from 4.8.36 to 5.7.27

There are mismatches - so please run ./tools/buildgen/generate_projects.sh. There are diffs on these 2 files
  modified:   tools/dockerfile/interoptest/grpc_interop_php/Dockerfile
  modified:   tools/dockerfile/test/php_jessie_x64/Dockerfile