karpenter Not Pre-spinning any replacement nodes when draining and deleting the nodes manually.

Description
Observed Behavior:
https://karpenter.sh/preview/concepts/deprovisioning/#deprovisioning-controller
As per Docs For each deprovisionable node, execute a scheduling simulation with the pods on the node to find if any replacement nodes are needed.
Cordon the node(s) to prevent pods from scheduling to it.
Pre-spin any replacement nodes needed as calculated in Step (2), and wait for them to become ready.
If a replacement node fails to initialize, un-cordon the node(s), and restart from Step (1), starting at the first deprovisioning method again.
When executing below commands manually it is just evicting the pods without pre creating the replacement node.
kubectl delete machine
kubectl delete node
kubectl drain
When we execute this command pods go to Pending state and then karpenter creates new nodes in response to pending pods.
We need to manually upgrade AMI of this nodes from one kubernetes version to other . For this we updated awsnodetemplates with newer version AMI and we are rotating the existing nodes using kubectl drain
This will cause downtime as pods are going to Pending state.
Expected Behavior:
when we run this below commands Karpenter should pre create the replacement nodes prior to evicting the pods so that pods will go to new nodes immediately after eviction.
kubectl delete machine
kubectl delete node
kubectl drain
Reproduction Steps (Please include YAML):
Run this commands on the nodes karpenter created
kubectl delete machine
kubectl delete node
kubectl drain
Versions:

Chart Version: v0.30.0
Kubernetes Version (kubectl version): 1.27

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

It sounds like you don't have PDBs on your workloads.  PDBs are the only thing that slows the draining of nodes. If you apply them, you should see behavior closer to what you want.

Using kubectl delete machine or kubectl delete node is seen as a forceful action in Karpenter's perspective. If you're looking for a less forceful way to do this, I think https://github.com/aws/karpenter/issues/4231 would fit your use-case.

@njtran obvious use case here is a cluster upgrade where you want to upgrade your nodes. kubectl delete node is a way of doing that, but i would like to see a way that spins up a new node with the same size before the node is deleted to reduce the time for pods to be scheduled, and in a statefulset its even more time consuming

When you're upgrading your nodes, you mean changing the AMIs, right? For upgrading AMIs, the best way to drive this is through drift. Using kubectl delete node is only enabled through using Karpenter. If you try to kubectl delete node non-Karpenter owned nodes, it forcefully unregisters the node from the cluster.
It seems like #4231 fits your use-case, so I'll close this. If there's anything not included/explained by the deprovisioning docs feel free to cut an issue/PR and let us know how we can do better!


Tracking for last unread message

When user comes to chat he sees old messages. There is no such behaviour if user manually marks all messages as read.
So it seems like a problem with tracking.

@FoggyFinder can you explain this issue in more detail?  Other users don't see this issue, so we need more detail to investigate.

can you explain this issue in more detail?

@timabbott I can try :-)
It is something with unread-counter-and-pointer#navigation

Zulip will always take you to the place you left off (your first unread message) to make it more easy for you to catch up with all the discussions that happened while you were away from your computer.

For example, today, when I opened chat :

So, I've wrote some messages after this time but pointer not changed location.

@FoggyFinder are you still able to reproduce this issue?

Yep

If so, I'd like to debug it with you.

What can I do? I know near nothing about Python :-)

I think this is very likely #1529.


Unable to delete characters, entering shifts highlight

O OSX Ventura 13.2 (22D49)
clean checkout (commit 6ccbb581), now inside example I execute
flutter run -d  macOS
platform:macOS, arch:arm64,
I have the following problem:
I am unable to delete any characters using the backspace key.
Also, with every single character I enter, the highlight in the paragraph immediately following my position, as well as in all subsequent paragraphs, is shifted left. This is not true for the blueish highlight.
In console.
[NSTextView layout] failed to converge after 5 iterations

Thank you for reporting! Can you share a gif/vid of your issue. Seems rather odd. I'd expect backspace to work.

I can confirm,
macOS Ventura 13.2.1
terminal
git clone https://github.com/visual-space/visual-editor.git
cd example
flutter doctor
[✓] Flutter (Channel stable, 3.7.12, on macOS 13.2.1 22D68 darwin-arm64
(Rosetta), locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.1)
[✓] VS Code (version 1.78.2)
[✓] Connected device (5 available)
[✓] HTTP Host Availability
• No issues found!
flutter clean
Cleaning Xcode workspace...                                      1,144ms
Cleaning Xcode workspace...                                      1,757ms
Deleting build...                                                             55ms
Deleting .dart_tool...                                                     2ms
Deleting Generated.xcconfig...                                    0ms
Deleting flutter_export_environment.sh...                  0ms
Deleting ephemeral...                                                   0ms
Deleting .flutter-plugins-dependencies...                  0ms
Deleting .flutter-plugins...                                           0ms
flutter run -d macos
Running "flutter pub get" in example...

Launching lib/main.dart on macOS in debug mode...
Running pod install...                                             724ms
2023-05-27 08:22:02.957 xcodebuild[62618:8518867] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:macOS, arch:x86_64, id:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx }
{ platform:macOS, arch:arm64, id:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx }
warning: Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Flutter Assemble' from project 'Runner')
Building macOS application...
Syncing files to device macOS...                                   226ms
Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h List all available interactive commands.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).
💪 Running with sound null safety 💪
An Observatory debugger and profiler on macOS is available at: http://<IP_ADDRESS>:49767/VA9oDlKkVPI=/
The Flutter DevTools debugger and profiler on macOS is available at:
http://<IP_ADDRESS>:9103?uri=http://<IP_ADDRESS>:49767/VA9oDlKkVPI=/

Placed carat at end of 'Custom highlights
None for the follow worked ... tried keyboard backspace, delete, cursor up, cursor down, cursor left, cursor right, undo, redo.

No point in creating a gif/vid. There is nothing to see!
Hope this helps.

Looks like the issue appears only on mac, in windows the backspace works as expected.
When it comes to the highlight, we know about the issue https://github.com/visual-space/visual-editor/issues/200
We are working on it.

Can confirm the issue, neither backspace, highlight or navigation with the arrow keys works on MacOS as of now

We will have a look and fix it. However we are fully booked for the next 2 months. If you have a PR in the meantime I'll double check it. Thank you!

Duplicates #200


[enhancement] Add highlighting for flags/options/arguments

So instead of

You seem to want ZSH_HIGHLIGHT_STYLES[single-hyphen-option]=fg=yellow; the full list of styles for the main highlighter is at https://github.com/zsh-users/zsh-syntax-highlighting/blob/master/docs/highlighters/main.md .

Okay, I've set it up and it's working how I expected. Thanks!


[Backport] NETOBSERV-915 add conversation direction

Backport of https://github.com/netobserv/network-observability-console-plugin/pull/317

/lgtm

/approve


Update links to the repo since it was moved

Hiiii I was trying to find this repo so I went to https://crates.io/crates/cargo-hakari, clicked on the repository link, saw that https://github.com/facebookarchive/cargo-guppy is archived and 😱😱😱😱
But then I found this repo! But this repo still links to the old one!!
I tried to find all places that contained facebookincubator and update them, except for links to issues and PRs.
I separated the sorts of places that I updated into separate commits in case some shouldn't be updated or I did them wrong.

cargo-hakari 0.9.15 is out with a fix for this. Thanks again for your patience.


add option for complete on visibilitychange

The next tagged release would break many existing projects as the animations would not keep running but immediately complete on visibilitychange.
This should not be the case by default and just be enabled with another parameter when creating a Walkway instance.
It could also make sense to provide an argument (function) to override the behavior when the visibility of the tab changes. Should the animation reset or complete? Or should the visibilitychange in the current master be removed and developers have to add the desired behavior to their own code?
Because like you said in another issue, Walkway should not depend on any viewport things and just be used for the actual animation.

would not keep running but immediately complete on visibilitychange

It won't break anything, for two reasons. First, it is actually already in the current release https://github.com/ConnorAtherton/walkway/blob/v0.0.7/src/walkway.js#L114. Second, that was explicitly added because the alternative was buggy. It doesn't matter if the animation keeps going, because having that event fire means it will not be seen anyway (due to being in another tab, or something).

This should not be the case by default

I see your point. It initially wasn't but we had issues where people preferred the alternative behaviour, for things to work well by default, instead of people using this and ending up with half-drawn elements on the page and not knowing why.

like you said in another issue, Walkway should not depend on any viewport things

Apologies for my mis-quote. I was trying to refer to the example you gave in your examples, which talked about bringing elements in from outside the viewport at different times, in which case I said the app should deal with that and Walkway focuses on just animating the elements.

Ok. But why not add an option to disable the complete call on visibilitychange events? Or is this not a good idea to overwrite this behavior?
At least I just got 0.0.6 with npm install, no 0.0.7 release.


up upgrade not working on ArchLinux

Error: installing: moving: rename /tmp/unpackit-688898816/up /usr/local/bin/up: invalid cross-device link
And the workaround is not working either:
~$ curl -sfL https://raw.githubusercontent.com/apex/up/master/install.sh | sudo sh
apex/up: checking GitHub for latest version
apex/up: found version 0.2.4 for linux/amd64
apex/up: downloading https://github.com/apex/up/releases/download/v0.2.4/up_0.2.4_linux_amd64.tar.gz
apex/up: verifying checksums
curl: (22) The requested URL returned error: 404 Not Found

The v0.2.4 release has renamed the checksum file to up_0.2.4_checksums.txt instead of up_checksums.txt, which is causing the install.sh script to fail on a 404.

workaround is that you fork install.sh and rename the checksum file to match the release.
or you can use mine instead.
curl -sfL https://gist.githubusercontent.com/quocnguyen/4fdb93be6049f2311c7be6d2eaf90238/raw/7b85022f0ac5ff5fa72b7a0b8d21e955396ff4c7/install.sh | sh

sorry about that! goreleaser must have made some small changes there, updated it recently

Regression with 0.2.5?
mbp:~ kaihendry$ curl -sfL https://raw.githubusercontent.com/apex/up/master/install.sh | sh
apex/up: checking GitHub for latest version
apex/up: found version 0.2.5 for darwin/amd64
apex/up: downloading https://github.com/apex/up/releases/download/v0.2.5/up_0.2.5_darwin_amd64.tar.gz
curl: (22) The requested URL returned error: 404 Not Found

@kaihendry are you still seeing that? I re-released the binaries (one was missing), but maybe GH's download server is confused now

@tj think it's working again. Upgraded successfully curl -sfL https://raw.githubusercontent.com/apex/up/master/install.sh | sh my mbp & t460s.

Oh btw, not sure how this got closed but this bug is still an issue on Archlinux!
Error: installing: moving: rename /tmp/unpackit-639905158/up /usr/local/bin/up: invalid cross-device link

Sidenote: I did notice https://aur.archlinux.org/packages/apex-bin/ but it seems horribly out of date. I wonder if it can be automated with a git hook or something...

ah you can't do atomic renames across partitions. Hmm maybe we could detect that and fall back on just doing a copy


Changing text of Label3D leaks memory and uses more CPU while window is minimized.

Godot version
v4.0.3.stable.mono.official [5222a99f5]
System information
Windows 10 Home 64-bit, 8GB RAM
Issue description
When the text of a Label3D is changed while minimized, it appears to leak memory (viewable in the Task Manager). This is evident when changing the text in the _process function, and when multiple Label3Ds are being simultaneously changed. It also appears that the CPU does more work too.
When the window is re-opened, the leaks stop yet the already leaked memory is never freed. The CPU, though, relaxes when it is reopened.
This leak happens when testing with the editor, and after the project is exported. It also happens even if the same text is applied.
I've tried using GDScript and C#, both have the same effect. Both interpolation and concatenation in C# have the same effect. The Label3Ds continue to leak memory regardless.
The issue isn't specific to the .NET version of Godot.
https://github.com/godotengine/godot/assets/97438474/1d4f865b-a41f-453e-bd5a-75b766402c54
https://github.com/godotengine/godot/assets/97438474/9b782122-e26f-4a43-898e-897ecc7a3d93
Steps to reproduce

Insert a Label3D.
Write a script that changes the text.
Run the scene.
Open Task Manager and find the debug play test window.
4.1. Select that task to see it move easier.
4.2. Check its current memory and CPU usage.
Minimize the window. Now, check its memory and CPU usage rise up in the Task Manager.
Re-open the window to see the RAM free of just a small amount of memory. If the RAM use is around 500 MB, when doing this step, it'll stay around 460 MB instead of what was shown in step 4.2.

Minimal reproduction project
Reproduction projects:
GDScript and C# (.NET Version)
This repro ZIP contains two scenes with names ending in "Demonstration". Open and run either one with "Run Current Scene", and do the repro steps starting with step 4.
GDScript Only
Simply run the repro project, and do the repro steps starting with step 4.

Can you reproduce this with a MeshInstance3D that uses a primitive mesh, when changing its parameters (such as radius or number of sides) while the window is minimized?

Can you reproduce this with a MeshInstance3D that uses a primitive mesh, when changing its parameters (such as radius or number of sides) while the window is minimized? I wonder if this is due to mesh generation.

It appears it does happen with MeshInstance3Ds as well. I have a recording here, with 42 MI3Ds, with a script that makes each of their meshes unique and rescales their sizes with sine values:
https://github.com/godotengine/godot/assets/97438474/3026cf12-bb8c-4736-8c1c-565ab77e1598


Add run server

This will be a port of our internal Golang project.

Pushing back

Isn't this is a dup of #98

Yes closing


chore: use short identifier for vanilla-extract

Proposed solution
https://github.com/vanilla-extract-css/vanilla-extract/issues/771#issuecomment-1249524366

@ginnun should we merge this PR?

@pczeglik-iohk solved the hang problem by disabling source map generation in the staking project. But this change is still a good improvement. There is already another conversation happening on the topic which you are a part of. Let's wait for it.


Update Posts “a-scheduled-post”

Automatically generated by Netlify CMS

👷 Deploy Preview for thunderous-brigadeiros-23902d processing.

Name
Link

🔨 Latest commit
a905e1279150a224cd6f55bd1038f8937f2cf6f4

🔍 Latest deploy log
https://app.netlify.com/sites/thunderous-brigadeiros-23902d/deploys/6331b5e26a1c050008accc5f


WIP: add public SSS rank getter

I think it would be a good moment to expose a public SSS rank lookup function.
@Eric89GXL @agramfort cc @jjnurminen so far I'm not 100% sure what it means when we find multiple SSS records in the processing history. It seems the definitive one is the first, at least according to our tests. If I take the last one we get crashes, but this is trivial, as our test just compares the maths to the n_free of the first entry. In our testing dataset the first entry suggests 112, the second 120 components. Which one is the right one?
cc @SherazKhan.

Sorry my ignorance, but where do 'multiple SSS records' come from? It doesn't make sense to do the SSS operation (i.e. data -> multipole terms) more than once.

I don't actually know what was the story sbout multiple SSS records and share your confusion. @Eric89GXL was this about manual corrections?

I think SSS was run on that file twice by mistake. In practice I doubt people actually use it. I guess we could use the min if we want, but what we already have is probably okay.
We should probably get rid of the bad file from the repo (we could purge from history to save some bytes even) and just use one of the correct files in the testing repo.

I think SSS was run on that file twice by mistake

How does this happen in practice?
Elekta MaxFilter and mne.preprocessing.maxwell_filter both seem to disallow such an operation.

--force in MaxFilter

Makes sense. Let's look up the min components and later on change the test
file.
On Mon, 10 Apr 2017 at 10:06, Eric Larson<EMAIL_ADDRESS>wrote:

--force in MaxFilter
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/4177#issuecomment-292959526,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fivpCfCMye_a9PY-WC9jd6YSLQmMHks5rujdPgaJpZM4M35eO
.

yes. Not yet implemented.
On Tue, Apr 11, 2017 at 4:02 PM Alexandre Gramfort<EMAIL_ADDRESS>wrote:

@agramfort commented on this pull request.
In mne/io/tests/test_proc_history.py
https://github.com/mne-tools/mne-python/pull/4177#discussion_r110999542:

@@ -40,7 +40,10 @@ def test_maxfilter_io():

def test_maxfilter_get_rank():
"""Test maxfilter rank lookup."""

mf = read_info(raw_fname)['proc_history'][0]['max_info']

raw = read_raw_fif(raw_fname)

mf = raw.info['proc_history'][0]['max_info']

use min of all?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/4177#discussion_r110999542,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fimmawlxZlaEoJNzYv3Tc7N_3zZylks5ru9w9gaJpZM4M35eO
.

Looks like this is superseded by #4637


Spinner missing after parent becoms visible

I'm using IE 11.0.9600.18349 and have noticed the following issue.  If you set the parent container to display none and then revert the child spinner is no longer visible in IE.  Here is a codepen reproducing the issue.  I have attempted calling the componentHandler to update the DOM but the spinner remains hidden.  This only happens on IE not on chrome or firefox
To reproduce:
-open codpen
-SEE spinner in transparent container
-click button
-SEE parent and child now hidden
-click button again
-EXPECTED parent and child now visible again
-RESULTS parent is visible but child is not

A way I have managed to get around this issue is by setting the parents height to 0 and removing the is-active class on the spinner.  The spinner still takes space in the DOM doing this but I can position it out of the way.

Looks like it has to do with this IE11 bug. It's not that the spinner is not visible, it's that the spinner is not animating . For example, in your pen in IE, try opening F12 Developer Tools and toggling the animation property on the different mdl-spinner__layer elements. You'll notice that it triggers an animation but then stops.
This is unfortunately an IE problem and MS pretty much doesn't patch any IE11 bugs except for critical security issues (I've filed bugs with them in the past around their animation engine and have received that response). If your workaround works however, I'd suggest sticking with that.


Add linting github actions

I had to temporarily disable the "required" nature of

lint-workflows / Lint Workflows
lint-workflows / changes
because the files weren't there.

Need to add the appropriate workflow files.
Are the linter GitHub Actions in template-go?

Resolved by: https://github.com/senzing-garage/go-rest-api-service-legacy/pull/10

Closing as completed. The linter action failures in this repo are resolved and the workflow files are reflected in the template repositories.


fixed the /tasks/id route

Issue - while sending the patch request to /task/:id route, was getting a response message as "User doesn't exist" with status 404
screenshot of the bug

fix - in updateTask controller just changed the if condition from req.body?.assignee -> task.taskData.assignee and also pass username in fetchUser function as task.taskData.assignee
screenshot after the fix

This was a false alarm, the change can break existing flow


Failed to set up

I have a Beurer TL 100 that worked with this integration on my HA before. After my SD Card got corrupted during the last OS upgrade I reinstalled and now see "Failed to set up: Check the logs".
The log itself says (paraphrased)
Traceback (most recent call last):
config_entries.py, line 387, in async_setup
beurer/init.py, line 22, in async_setup_entry
AttributeError: 'ConfigEntries' object has no attribute 'async_setup_platforms'
Did something change in the interface recently?

Please compare https://github.com/home-assistant/core/commit/739963b5ee1a49039eb19a1831bb569dab255fcc


Remove references to El Nino

No longer temporarally relevant
Fixes #180

Coverage remained the same at 97.717% when pulling c8a5ab68264d9f7f2db3140b239855cb535547b2 on remove-references-to-el-nino into 37a769072d4e3fed803872cca5d9f9022127625d on production.


[Style] Only display the warning once

This prevent to be flooded by the warnings when navigator.userAgent is not set.
Warning: Material-UI expects the global navigator.userAgent to be defined
        for server-side rendering. Set this property when receiving the request headers.
Warning: Material-UI expects the global navigator.userAgent to be defined
        for server-side rendering. Set this property when receiving the request headers.
Warning: Material-UI expects the global navigator.userAgent to be defined
        for server-side rendering. Set this property when receiving the request headers.
Warning: Material-UI expects the global navigator.userAgent to be defined
        for server-side rendering. Set this property when receiving the request headers.
Warning: Material-UI expects the global navigator.userAgent to be defined
        for server-side rendering. Set this property when receiving the request

Any change we can make this contextual? maybe with theme? I mean globals hurt SSR. so a contextual userAgent can be passed down from the root with each request. the theme object is already on it. so maybe add it to the them?

Any change we can make this contextual? maybe with theme? I mean globals hurt SSR. so a contextual userAgent can be passed down from the root with each request. the theme object is already on it. so maybe add it to the them?

Yeah, I agree! This PR is WIP, this first commit can be merged like this, but I'm working on:

deprecating: set
using the context to pass the user-agent
allow to prefix for all user-agent and disabling the autoprefixer.

I see. Thanks a lot. This will surely close a huge number of issues :grin: :grin:

@alitaheri I have updated the PR. Take your time to review it. That's affecting almost all of our component.

I have updated the PR, I'm happy with it.

It's good for now :+1: :+1: We'll address more issues when we decide on transformers :+1:
Feel free to merge :grin:

Awesome, I'm gonna add a section on the doc for the server side rendering first.

Added.

All good :+1: :+1: Thanks a lot @oliviertassinari

@newoga Do you want to have a final view at this PR before merging?

@oliviertassinari Sorry, I looked earlier and I think I was good for now in terms of a first iteration. I'll do one last quick check! :smile:

@oliviertassinari @alitaheri Yup, let's get this in :+1:
I'm not too familiar with server side rendering with React so I can't comment too much in that regard, but I think this is a good first step. We can look at more approaches to refactoring auto-prefix use in separate PRs.
Part of #2986 motivation was developing an approach for removing auto prefixing from the transformation cycle. Since this PR solves it with a similar but different means, maybe we should hold off on #2986?
I can create a new PR (or modify #2986) that doesn't expose the composition and customization of style transformers but still puts our own version of prepareStyles in context if that's still useful. I think some of the changes like ensuring the prepareStyles (not just ensureDirection) gets called only once is still worth it.

@newoga Awesome :tada:.

still puts our own version of prepareStyles in context if that's still useful

This PR is making us one step closer to the goal of #2986.
Right now, on the master branch, prepareStyles is working without the muiTheme.
This PR makes it mandatory.
I definitely think that moving everything into the context will make thing more coherent, easier to reason about and be more customizable.

I definitely think that moving everything into the context will make thing more coherent, easier to reason about and be more customizable.

Yes I agree :+1: :+1:

Yay! I have been trying to do server-side rendering and am facing this very same issue. Do you know when this will be released on npm?

@shilpan We're getting ready for 0.14.3 release very soon! #3028

By the way. I the only advantage of this PR for my project is to remove the warning.
I wasn't provind a global navigator (that display a warning) in order to prefix for all the user agent on the server side. Then, on the client side, I'm only prefixing for the browser user agent.

I just upgraded to 14.3, and the warning "Material UI: userAgent should be supplied in the muiTheme context for server-side rendering." is back. I had this working before using this hack:
    app.use(function(req, res, next) {
      GLOBAL.navigator = {
        userAgent: req.headers['user-agent']
      }
      next();
    });

How am I supposed to set the userAgent to get SSR working again? (now checksums don't match, and I get the warning, once).
I'm using the decorator in main component App.jsx:
import MyRawTheme from 'theme/my-material-ui.config';
@themeDecorator(ThemeManager.getMuiTheme(MyRawTheme))
export default class App extends Component {

"my-material-ui.config.js":
import Colors from 'material-ui/lib/styles/colors';
import ColorManipulator from 'material-ui/lib/utils/color-manipulator';
import Spacing from 'material-ui/lib/styles/spacing';

export default {
  spacing: Spacing,
  // userAgent: req.headers['user-agent'],
  // userAgent: GLOBAL.navigator.userAgent,
  // userAgent: 'all',
  fontFamily: 'Roboto, sans-serif',
  palette: {
    primary1Color: Colors.blueGrey500,
    primary2Color: Colors.blueGrey700
  }
};

@tomasztomys Just want to make sure. I noticed your userAgent key is commented in the my-material-ui.config.js. Can did you try uncommenting your userAgent?

I get weird spacing spacing issues in the mismatch error:
(client) ow:0 1px 6px rgba(0, 0, 0, 0.12), 0 1px
(server) ow:0 1px 6px rgba(0,0,0,0.12),

This is how I set it up.
const muiTheme = getMuiTheme(null, {
    userAgent: 'all',
});
export default themeDecorator(muiTheme)(App);

Okay, there's a PR (#3112) that's related to this that I'm going to review soon. I'll see what I find.

Changing from
@themeDecorator(ThemeManager.getMuiTheme(MyRawTheme))
to
@themeDecorator(ThemeManager.getMuiTheme(MyRawTheme, { userAgent: 'all'}))
fixed it, thank you :-)
That is, I still get the warning from material-ui, but React don't complain anymore (checksum match).

For future reference in case somebody else is reading all 1000 posts related to this topic, this worked better for me. Defining my custom theme directly and passing the userAgent as second option.
FYI using all instead of false made the UI about 10x slower so using that was not an option. Somehow need to figure out how to make the (real) calling client agent available in App.js though.
const muiTheme = getMuiTheme({
  palette: {
    primary1Color: Colors.indigo500,
    etc...
  },
}, {
    userAgent: 'false'
});


Remove legacy module

Removes the legacy module in favour for reflection, not tested.
If they are using legacy they can deal with the bad performance of reflection

Also, I feel it is important to stress that this is untested and it possible it will not work. Do not merge, just approve

even if, it would "just" destroy our trunk without further impact

Also, I feel it is important to stress that this is untested and it possible it will not work. Do not merge, just approve
even if, it would "just" destroy our trunk without further impact

but stress is a good keyword. since you mentioned "bad performance", this is worth a stress testing

The actions are messed up cause there isnt a master branch. GH actions only supports workflow "chaining" on master/main branches. Will test later

but why are those commits in this branch?


fix: Aggressively GC wasm instances

Looks not-unreasonable, but let's hold off on merging until we fix issue with occasional stuck workers since it's easier to trigger that failure mode without this patch in ;)

Looks okay, and I agree with @callahad on holding on to this. Alternatively we can give the VM significantly more memory to use


Events with the same time are displayed on top each other

Hi,
Please look at the attached images.
Events with the same time are displayed on top each other in day/week view.
Can you improve this display like showing the events side by side?
Many thanks.

for sure, this could be better.

Hi man,
Do you have an estimation when this enhancement will be done?

Hello
Can you fix this bug - each new event is falling on the previous event - making it impossible to see previous events.

Hey folks.
Apologize, I was not available recently.
Check out the latet version, which has an approach pretty much close to Google Calendar.
Feel free to re-open if it still has issues.

Thank you, it looks much better now.

In addition, when clicking on the date picker, the calendar crashes.

Yeah, since version 2.7.0 this Scheduler needs a x-date pickers version >= 6
I assume you still have version 5?

Indeed, Thanks!


bazel build issue

Maven can build fat-jar and relocate dependencies. I did not find a way to do both. I already contacted bazel community.

Things were fixed. Closing it.


Retry installing test dependencies to mitigate network timeout impacts during builds

Issue # (if available):
N/A
Description of changes:
I noticed a lot of build failures during dependency installation like https://travis-ci.org/awslabs/s2n/jobs/487108904 and https://docs.travis-ci.com/user/common-build-problems/#timeouts-installing-dependencies recommends using this built in travis function. I can't find a case where it logged that did retry something but it doesn't seem to hurt either.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Good point, I found https://travis-ci.community/t/then-sudo-apt-get-update-failed-public-key-is-not-available-no-pubkey-6b05f25d762e3157-in-ubuntu-xenial/1728 which appears to be a recent travis issue from this year. As a temporary fix I will add the key in a before install step. I think the retry could still be useful but is a band-aid ignore the root cause.


Propagate changes to work around DNS resolution issue in Linux

See: https://github.com/Azure/azure-sdk-for-java/pull/10576/files
We've seen issues where DNS resolution fails in Ubuntu 18. This workaround fixes that problem. This only needs to run on Ubuntu 18 instances.

@chradek, @richardpark-msft Any chance this can solve our dns woes with linux in SB and EH?

Closing this issue. We already have this integrated with a step to bypass local DNS using common template.


⚠ SceneTime has degraded performance

In d43c56c, SceneTime ($ST) experienced degraded performance:

HTTP code: 503
Response time: 20753 ms

Resolved: SceneTime performance has improved in 559d4de after 6 minutes.


Add embedded readmes for track 2 java

Docs Build status updates of commit 16c1c52:
:clock10: Full build: the average full build time is 74 min(s) 44 sec(s), this is based on the last 453 build(s) for this repository.

Docs Build status updates of commit 16c1c52:
:clock10: Full build: the average full build time is 74 min(s) 44 sec(s), this is based on the last 453 build(s) for this repository.

Docs Build status updates of commit 16c1c52:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/cosmos-readme.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/identity-readme.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/messaging-eventhubs-checkpointstore-blob-readme.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/messaging-eventhubs-readme.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/messaging-servicebus-readme.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/search-documents-readme.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/security-keyvault-keys-readme.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/storage-blob-batch-readme.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/storage-file-share-readme.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/storage-queue-readme.md
:warning:Warning
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)
Details

docs-ref-services/keyvault.md
:warning:Warning
View (azure-java-stable) View (azure-java-legacy)
Details

docs-ref-mapping/reference-latest.yml
:white_check_mark:Succeeded

docs-ref-services/ai-textanalytics-readme.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

docs-ref-services/core-tracing-opentelemetry-readme.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

docs-ref-services/data-appconfiguration-readme.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

docs-ref-services/security-keyvault-certificates-readme.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

docs-ref-services/security-keyvault-secrets-readme.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

docs-ref-services/storage-blob-cryptography-readme.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

docs-ref-services/storage-blob-readme.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

docs-ref-services/cosmos-readme.md

Line 27: [Warning] Invalid link: 'API Documentation'. The file docs-ref-services/cosmos-readme.md doesn't contain a bookmark named 'api-documentation'.
Line 27: [Warning] Invalid link: 'API Documentation'. The file docs-ref-services/cosmos-readme.md doesn't contain a bookmark named 'api-documentation'.
Line 27: [Warning] Invalid link: 'API Documentation'. The file docs-ref-services/cosmos-readme.md doesn't contain a bookmark named 'api-documentation'.
Line 28: [Warning] Invalid link: 'Usage Code Sample'. The file docs-ref-services/cosmos-readme.md doesn't contain a bookmark named 'usage-code-sample'.
Line 28: [Warning] Invalid link: 'Usage Code Sample'. The file docs-ref-services/cosmos-readme.md doesn't contain a bookmark named 'usage-code-sample'.
Line 28: [Warning] Invalid link: 'Usage Code Sample'. The file docs-ref-services/cosmos-readme.md doesn't contain a bookmark named 'usage-code-sample'.
Line 29: [Warning] Invalid link: 'Guide for Prod'. The file docs-ref-services/cosmos-readme.md doesn't contain a bookmark named 'guide-for-prod'.
Line 29: [Warning] Invalid link: 'Guide for Prod'. The file docs-ref-services/cosmos-readme.md doesn't contain a bookmark named 'guide-for-prod'.
Line 29: [Warning] Invalid link: 'Guide for Prod'. The file docs-ref-services/cosmos-readme.md doesn't contain a bookmark named 'guide-for-prod'.
Line 39: [Warning] Invalid file link:(~/docs-ref-services/microsoft-azure-cosmos-examples/src/main/java/com/azure/data/cosmos/examples/HelloWorldDemo.java).
Line 39: [Warning] Invalid file link:(~/docs-ref-services/microsoft-azure-cosmos-examples/src/main/java/com/azure/data/cosmos/examples/HelloWorldDemo.java).
Line 39: [Warning] Invalid file link:(~/docs-ref-services/microsoft-azure-cosmos-examples/src/main/java/com/azure/data/cosmos/examples/HelloWorldDemo.java).
Line 92: [Warning] Invalid file link:(~/docs-ref-services/examples/src/test/java/com/microsoft/azure/cosmosdb/rx/examples).
Line 92: [Warning] Invalid file link:(~/docs-ref-services/examples/src/test/java/com/microsoft/azure/cosmosdb/rx/examples).
Line 92: [Warning] Invalid file link:(~/docs-ref-services/examples/src/test/java/com/microsoft/azure/cosmosdb/rx/examples).
Line 96: [Warning] Link 'https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-sql-query' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 96: [Warning] Link 'https://azure.microsoft.com/en-us/services/cosmos-db/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 96: [Warning] Link 'https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-sql-query' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 96: [Warning] Link 'https://azure.microsoft.com/en-us/services/cosmos-db/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 96: [Warning] Link 'https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-sql-query' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 96: [Warning] Link 'https://azure.microsoft.com/en-us/services/cosmos-db/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 116: [Warning] Link 'https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-resources' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 116: [Warning] Link 'https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-resources' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 116: [Warning] Link 'https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-resources' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 117: [Warning] Link 'https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-sql-query' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 117: [Warning] Link 'https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-sql-query' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 117: [Warning] Link 'https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-sql-query' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 119: [Warning] Invalid file link:(~/docs-ref-services/faq/).
Line 119: [Warning] Invalid file link:(~/docs-ref-services/faq/).
Line 119: [Warning] Invalid file link:(~/docs-ref-services/faq/).
Line 124: [Warning] Link 'https://docs.microsoft.com/en-us/azure/cosmos-db/local-emulator-export-ssl-certificates' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 124: [Warning] Link 'https://docs.microsoft.com/en-us/azure/cosmos-db/local-emulator-export-ssl-certificates' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 124: [Warning] Link 'https://docs.microsoft.com/en-us/azure/cosmos-db/local-emulator-export-ssl-certificates' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 287: [Warning] Link 'https://docs.microsoft.com/en-us/azure/cosmos-db/performance-tips-async-java' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 287: [Warning] Link 'https://docs.microsoft.com/en-us/azure/cosmos-db/performance-tips-async-java' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 287: [Warning] Link 'https://docs.microsoft.com/en-us/azure/cosmos-db/performance-tips-async-java' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 291: [Warning] Invalid file link:(~/docs-ref-services/faq/).
Line 291: [Warning] Invalid file link:(~/docs-ref-services/faq/).
Line 291: [Warning] Invalid file link:(~/docs-ref-services/faq/).
Line 295: [Warning] Invalid file link:(~/docs-ref-services/changelog/).
Line 295: [Warning] Invalid file link:(~/docs-ref-services/changelog/).
Line 295: [Warning] Invalid file link:(~/docs-ref-services/changelog/).
Line 299: [Warning] Invalid file link:(~/docs-ref-services/dev.md).
Line 299: [Warning] Invalid file link:(~/docs-ref-services/dev.md).
Line 299: [Warning] Invalid file link:(~/docs-ref-services/dev.md).
Line 299: [Warning] Invalid file link:(~/docs-ref-services/dev.md).
Line 299: [Warning] Invalid file link:(~/docs-ref-services/dev.md).
Line 299: [Warning] Invalid file link:(~/docs-ref-services/dev.md).
Line 305: [Warning] Invalid file link:(~/docs-ref-services/LICENSE).
Line 305: [Warning] Invalid file link:(~/docs-ref-services/LICENSE).
Line 305: [Warning] Invalid file link:(~/docs-ref-services/LICENSE).

docs-ref-services/identity-readme.md

Line 24: [Warning] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth-ropc' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 24: [Warning] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth-ropc' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 24: [Warning] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth-ropc' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 269: [Warning] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow#request-an-authorization-code' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 269: [Warning] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow#request-an-authorization-code' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 269: [Warning] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow#request-an-authorization-code' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/messaging-eventhubs-checkpointstore-blob-readme.md

Line 96: [Warning] Invalid file link:(~/docs-ref-services/src/main/java/com/azure/messaging/eventhubs/EventProcessorClient.java).
Line 96: [Warning] Invalid file link:(~/docs-ref-services/src/main/java/com/azure/messaging/eventhubs/EventProcessorClient.java).
Line 96: [Warning] Invalid file link:(~/docs-ref-services/src/main/java/com/azure/messaging/eventhubs/EventProcessorClient.java).
Line 100: [Warning] Invalid file link:(~/docs-ref-services/src/main/java/com/azure/messaging/eventhubs/EventProcessorClient.java).
Line 100: [Warning] Invalid file link:(~/docs-ref-services/src/main/java/com/azure/messaging/eventhubs/EventProcessorClient.java).
Line 100: [Warning] Invalid file link:(~/docs-ref-services/src/main/java/com/azure/messaging/eventhubs/EventProcessorClient.java).
Line 104: [Warning] Invalid file link:(~/docs-ref-services/src/main/java/com/azure/messaging/eventhubs/EventProcessorClient.java).
Line 104: [Warning] Invalid file link:(~/docs-ref-services/src/main/java/com/azure/messaging/eventhubs/EventProcessorClient.java).
Line 104: [Warning] Invalid file link:(~/docs-ref-services/src/main/java/com/azure/messaging/eventhubs/EventProcessorClient.java).

docs-ref-services/messaging-eventhubs-readme.md

[Warning] Uid(azure.java.sdk.landingpage.services.eventhub.Client) has already been defined in docs-ref-services/messaging-eventhubs-readme.md.

docs-ref-services/messaging-servicebus-readme.md

Line 19: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 119: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/authenticate-application#built-in-rbac-roles-for-azure-service-bus' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 119: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/authenticate-application#built-in-rbac-roles-for-azure-service-bus' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 119: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/authenticate-application#built-in-rbac-roles-for-azure-service-bus' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 121: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/authenticate-application' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 121: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/authenticate-application' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 121: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/authenticate-application' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 128: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview#queues' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 128: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview#queues' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 128: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview#queues' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 131: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview#topics' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 131: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview#topics' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 131: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview#topics' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 134: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-queues-topics-subscriptions#topics-and-subscriptions' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 134: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-queues-topics-subscriptions#topics-and-subscriptions' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 134: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-queues-topics-subscriptions#topics-and-subscriptions' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 141: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-create-namespace-portal#get-the-connection-string' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 141: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-create-namespace-portal#get-the-connection-string' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 141: [Warning] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-create-namespace-portal#get-the-connection-string' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/search-documents-readme.md

Line 16: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 16: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 16: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 21: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 21: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 21: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 41: [Warning] Link 'https://azure.microsoft.com/en-us/services/search/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 41: [Warning] Link 'https://azure.microsoft.com/en-us/services/search/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 41: [Warning] Link 'https://azure.microsoft.com/en-us/services/search/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 46: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/search-security-api-keys' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 46: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/search-security-api-keys' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 46: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/search-security-api-keys' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 55: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/search-create-service-portal#get-a-key-and-url-endpoint' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 55: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/search-create-service-portal#get-a-key-and-url-endpoint' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 55: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/search-create-service-portal#get-a-key-and-url-endpoint' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 56: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/search-security-api-keys' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 56: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/search-security-api-keys' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 56: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/search-security-api-keys' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 79: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/search-create-service-portal#get-a-key-and-url-endpoint' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 79: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/search-create-service-portal#get-a-key-and-url-endpoint' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 79: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/search-create-service-portal#get-a-key-and-url-endpoint' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 80: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/search-security-api-keys' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 80: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/search-security-api-keys' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 80: [Warning] Link 'https://docs.microsoft.com/en-us/azure/search/search-security-api-keys' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 112: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/index-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 112: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/index-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 112: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/index-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 113: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/document-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 113: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/document-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 113: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/document-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 114: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/indexer-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 114: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/indexer-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 114: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/indexer-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 115: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/skillset-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 115: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/skillset-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 115: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/skillset-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 116: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/synonym-map-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 116: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/synonym-map-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 116: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/synonym-map-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 122: [Warning] Invalid file link:(~/docs-ref-services/Create-a-SearchIndexClient).
Line 122: [Warning] Invalid file link:(~/docs-ref-services/Create-a-SearchIndexClient).
Line 122: [Warning] Invalid file link:(~/docs-ref-services/Create-a-SearchIndexClient).
Line 177: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/http-status-codes' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 177: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/http-status-codes' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 177: [Warning] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/http-status-codes' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/security-keyvault-keys-readme.md

Line 274: [Warning] Invalid link: 'Encrypt Asynchronously'. The file docs-ref-services/security-keyvault-keys-readme.md doesn't contain a bookmark named 'encryp-asynchronously'.
Line 274: [Warning] Invalid link: 'Encrypt Asynchronously'. The file docs-ref-services/security-keyvault-keys-readme.md doesn't contain a bookmark named 'encryp-asynchronously'.
Line 274: [Warning] Invalid link: 'Encrypt Asynchronously'. The file docs-ref-services/security-keyvault-keys-readme.md doesn't contain a bookmark named 'encryp-asynchronously'.

docs-ref-services/storage-blob-batch-readme.md

Line 68: [Warning] Invalid link: 'Creating BlobBatchClient'. The file docs-ref-services/storage-blob-batch-readme.md doesn't contain a bookmark named 'create-blobbatchclient'.
Line 68: [Warning] Invalid link: 'Creating BlobBatchClient'. The file docs-ref-services/storage-blob-batch-readme.md doesn't contain a bookmark named 'create-blobbatchclient'.
Line 68: [Warning] Invalid link: 'Creating BlobBatchClient'. The file docs-ref-services/storage-blob-batch-readme.md doesn't contain a bookmark named 'create-blobbatchclient'.

docs-ref-services/storage-file-share-readme.md

Line 131: [Warning] Invalid link: 'File Share Service Client'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'share-service'.
Line 131: [Warning] Invalid link: 'File Share Service Client'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'share-service'.
Line 131: [Warning] Invalid link: 'File Share Service Client'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'share-service'.
Line 228: [Warning] Invalid link: 'Abort copy a File'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Abort-copy-a-file'.
Line 228: [Warning] Invalid link: 'Abort copy a File'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Abort-copy-a-file'.
Line 228: [Warning] Invalid link: 'Abort copy a File'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Abort-copy-a-file'.
Line 235: [Warning] Invalid link: 'Set a Share metadata'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Set-a-share-metadata'.
Line 235: [Warning] Invalid link: 'Set a Share metadata'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Set-a-share-metadata'.
Line 235: [Warning] Invalid link: 'Set a Share metadata'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Set-a-share-metadata'.
Line 236: [Warning] Invalid link: 'Get a Share access policy'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Get-a-share-access-policy'.
Line 236: [Warning] Invalid link: 'Get a Share access policy'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Get-a-share-access-policy'.
Line 236: [Warning] Invalid link: 'Get a Share access policy'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Get-a-share-access-policy'.
Line 237: [Warning] Invalid link: 'Set a Share access policy'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Set-a-share-access-policy'.
Line 237: [Warning] Invalid link: 'Set a Share access policy'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Set-a-share-access-policy'.
Line 237: [Warning] Invalid link: 'Set a Share access policy'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Set-a-share-access-policy'.
Line 238: [Warning] Invalid link: 'Get handles on Directory and File'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Get-handles-on-directory-file'.
Line 238: [Warning] Invalid link: 'Get handles on Directory and File'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Get-handles-on-directory-file'.
Line 238: [Warning] Invalid link: 'Get handles on Directory and File'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Get-handles-on-directory-file'.
Line 239: [Warning] Invalid link: 'Force close handles on handle id'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Force-close-handles-on-handle-id'.
Line 239: [Warning] Invalid link: 'Force close handles on handle id'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Force-close-handles-on-handle-id'.
Line 239: [Warning] Invalid link: 'Force close handles on handle id'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Force-close-handles-on-handle-id'.
Line 240: [Warning] Invalid link: 'Set quota on Share'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Set-quota-on-share'.
Line 240: [Warning] Invalid link: 'Set quota on Share'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Set-quota-on-share'.
Line 240: [Warning] Invalid link: 'Set quota on Share'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Set-quota-on-share'.
Line 241: [Warning] Invalid link: 'Set file httpHeaders'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Set-file-httpheaders'.
Line 241: [Warning] Invalid link: 'Set file httpHeaders'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Set-file-httpheaders'.
Line 241: [Warning] Invalid link: 'Set file httpHeaders'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Set-file-httpheaders'.
Line 270: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 270: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 270: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 278: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 278: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 278: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 294: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 294: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 294: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 301: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 301: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 301: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 308: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 308: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 308: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 315: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 315: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 315: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 323: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 323: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 323: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 331: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 331: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 331: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 339: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 339: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 339: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 347: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 347: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 347: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 355: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 355: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 355: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 364: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 364: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 364: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 371: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 371: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 371: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 378: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 378: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 378: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 404: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 404: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 404: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 412: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 412: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 412: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 419: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 419: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 419: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 431: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 431: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 431: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 438: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 438: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 438: [Warning] Invalid link: '${directoryClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Directory'.
Line 446: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 446: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 446: [Warning] Invalid link: '${shareClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'Share'.
Line 454: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 454: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.
Line 454: [Warning] Invalid link: '${fileClient}'. The file docs-ref-services/storage-file-share-readme.md doesn't contain a bookmark named 'File'.

docs-ref-services/storage-queue-readme.md

Line 218: [Warning] Invalid link: 'Dequeue messages from a queue'. The file docs-ref-services/storage-queue-readme.md doesn't contain a bookmark named 'dequeue-messages-from-a-queue'.
Line 218: [Warning] Invalid link: 'Dequeue messages from a queue'. The file docs-ref-services/storage-queue-readme.md doesn't contain a bookmark named 'dequeue-messages-from-a-queue'.
Line 218: [Warning] Invalid link: 'Dequeue messages from a queue'. The file docs-ref-services/storage-queue-readme.md doesn't contain a bookmark named 'dequeue-messages-from-a-queue'.

docs-ref-services/keyvault.md

[Warning] Uid(azure.java.sdk.landingpage.services.keyvault) has already been defined in docs-ref-services/keyvault.md.

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


Variable Explorer not Working

Issue Report Checklist

[Y] Searched the issues page for similar reports
[ Y] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ Y] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda) using pip.
[ Y] Could not reproduce inside jupyter qtconsole (if console-related)
[Y ] Tried basic troubleshooting (if a bug/error) => I tried reinstalling python and spyder

[Y ] Restarted Spyder
[ Y] Reset preferences with spyder --reset
[ not applicable] Reinstalled the latest version of Anaconda
[ Y] Tried the other applicable steps from the Troubleshooting Guide

Problem Description
Variable explorer doesnt show the created variables. I can do calculations with the variables, just i cannot see them in the variable explorer tab. Can anyone help me please??
What steps reproduce the problem?

I upgraded spyder to a new version, but the terminal stopped working. I tried uninstalling  spyder (both versions spyder3 the old one and spyder -the new version- were in my computer). I also uninstalled python making my computer crash. After some hours I was able to reinstall python using recovery mode and spyder. Now the terminal works, it runs code and let me do calculation with variables just doesnt show the variables created in the variable explorer.
I AM NOT USING ANACONDA
Tried reinstalling Ipython kernals.
tried changing preferences on the variable explorer tab. THERE ARE NO EXCLUSIONS.

What is the expected output? What do you see instead?
I Expect to have Spyder working properly, being able to view the variables i created on the variable explorer tab.
Paste Traceback/Error Below (if applicable)

IPython 7.13.0 -- An enhanced Interactive Python.

Traceback (most recent call last):

  File "/tmp/ipykernel_7853/3436525850.py", line 1, in <cell line: 1>
    get_ipython().kernel._show_mpl_backend_errors()

AttributeError: 'SpyderKernel' object has no attribute '_show_mpl_backend_errors'

Versions

Spyder version: Spyder 3.3.6
Python version: Python 3.8.10 64-bit
Qt version:  Qt 5.12.8
PyQt version: PyQt5 5.14.1
Operating System name/version:  Linux 5.13.0-35-generic

Dependencies

IPython >=4.0     :  7.13.0 (OK)
cython >=0.21     :  0.29.30 (OK)
jedi >=0.9.0      :  0.15.2 (OK)
matplotlib >=2.0.0:  3.5.2 (OK)
nbconvert >=4.0   :  5.6.1 (OK)
numpy >=1.7       :  1.22.4 (OK)
pandas >=0.13.1   :  1.4.2 (OK)
psutil >=0.3      :  5.5.1 (OK)
pycodestyle >=2.3 :  2.5.0 (OK)
pyflakes >=0.6.0  :  2.1.1 (OK)
pygments >=2.0    :  2.3.1 (OK)
pylint >=0.25     :  2.4.4 (OK)
qtconsole >=4.2.0 :  4.6.0 (OK)
rope >=0.9.4      :  0.10.5 (OK)
sphinx >=0.6.6    :  1.8.5 (OK)
sympy >=0.7.3     :  1.10.1 (OK)

Hey @joaquinchimenti97, you're using a way too old Spyder version (3.3.6), which is no longer supported by us. To fix this problem, please create a virtualenv and install Spyder on it.
If you're using the Spyder package provided by your Linux distro, please do not use sudo pip install -U spyder because that will break your system Python and you'll probably have to reinstall your distro.

Great! Glad to know is working fine for you now.


Support for Llama3

Hi! It would fantastic if it supported Llama3. I hit a bug, and I'm unsure whether or not it is caused by quantization or by Ctransformers not being able to handle Llama3.
ERROR: byte not found in vocab: ' '

This error is due to llama3 is not supported. The last update in that nice project was 7 month ago. I think is important somebody take the code, make a fork and continue this great project.

This error is due to llama3 is not supported. The last update in that nice project was 7 month ago. I think is important somebody take the code, make a fork and continue this great project.

why this repository stoped updating ?


Issue:3903841:PDR plugin: adding warnings and protection

https://redmine.mellanox.com/issues/3903841

Can one of the admins verify this patch?


'az eventgrid event-subscription delete' not working

Describe the bug
Using Azure CLI to delete a eventgrid event-subscription is not working
To Reproduce

List evengrid event-subscription
Get the name and id
Run 'az eventgrid event-subscription delete --name [my name] --source-resource-id /subscriptions/[subscription id]/resourceGroups/[ressource group]/providers/Microsoft.Storage/storageAccounts/[storageaccount]/providers/Microsoft.EventGrid/eventSubscriptions/[my name]'
Getting following error:

No registered resource provider found for location 'eastus2' and API version '2019-06-01' for type 'storageAccounts'. The supported api-versions are '2019-04-01, 2018-11-01, 2018-07-01, 2018-03-01-preview, 2018-02-01, 2017-10-01, 2017-06-01, 2016-12-01, 2016-05-01, 2016-01-01, 2015-06-15, 2015-05-01-preview'. The supported locations are 'eastus, eastus2, westus, westeurope, eastasia, southeastasia, japaneast, japanwest, northcentralus, southcentralus, centralus, northeurope, brazilsouth, australiaeast, australiasoutheast, southindia, centralindia, westindia, canadaeast, canadacentral, westus2, westcentralus, uksouth, ukwest, koreacentral, koreasouth, francecentral, australiacentral, southafricanorth, uaenorth'.

Expected behavior
Not getting an error and deleting the subscription
Environment summary
Installation via .msi
CLI 2.0.70
Win10 Pro 1809 64bit
cmd.exe

Thanks for reporting the issue. I had tried the same scenario using the provided steps in eastus2 regions and the command works fine as expected. By looking closer to the provided command, the --source-resource-id is for the event subscription itself rather than the topic to which the event subscription is associated with.
In this context, the command in step 3
[Run 'az eventgrid event-subscription delete --name [my name] --source-resource-id /subscriptions/[subscription id]/resourceGroups/[ressource group]/providers/Microsoft.Storage/storageAccounts/[storageaccount]/providers/Microsoft.EventGrid/eventSubscriptions/[my name]'
should be replaced with
. Run 'az eventgrid event-subscription delete --name [my name] --source-resource-id /subscriptions/[subscription id]/resourceGroups/[ressource group]/providers/Microsoft.Storage/storageAccounts/[storageaccount]'
where event subscriptions parts are removed.
Please try this out and let us know if you still have any issue.
Thanks

Oh right, the error message mislead me: I thought there where an issue with the API versioning.
I tried it with your pattern and it's working, thanks a lot!


[HOLD - EApp #34466] [$500] Workspace - Infinite loading when navigate to workspace link without access

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.22-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Navigate to Workspace link that doesn't have any users (https://staging.new.expensify.com/workspace/77336CD9870F8DB1
)

Expected Result:
There's should be error indicating "You do not have access to this page. Are you trying to join the workspace? Please reach out to the owner of this workspace so they can add you as a member! Something else? Reach out to Concierge"
Actual Result:
Infinite loading remains when user navigate to workspace link without access
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/b1b3de4e-4142-4ce5-902f-10a4bc74358e
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~013aa8ecc43f8d1fee
Upwork Job ID:<PHONE_NUMBER>406260736
Last Price Increase: 2024-01-17

Should be fixed in https://github.com/Expensify/App/pull/34006

Ok, based on this news, I'm going to close this one.

Thanks for flagging!

Issue is still reproducible on the latest build 1.4.26-1
https://github.com/Expensify/App/assets/78819774/30137c65-ed0f-4f59-bc39-56ec1145ef83

This becomes a problem again after the introduction of finallyData  which has the same root cause as https://github.com/Expensify/App/issues/34466

@bernhardoj - should we reopen https://github.com/Expensify/App/pull/34006 or close this issue for https://github.com/Expensify/App/issues/34466? Thanks for your feedback!

@alexpensify maybe we can hold for https://github.com/Expensify/App/issues/34466 and retest after it's deployed to staging. What do you think?

Good plan, I'm updating this to be weekly and we can check in after https://github.com/Expensify/App/issues/34466 is in production.

Weekly Update: Still on hold

Let's hold until next week, looks like there might be a regression.

@c3024 - I think we should take this one off hold. Do you agree? Thanks!

Not reproducible on main now. Could you check once @lanitochka17 ?
https://github.com/Expensify/App/assets/102477862/e1b882ff-d031-4583-9541-14b8f8d3233e

Issue is not reproducible on the latest build 1.4.42-4
https://github.com/Expensify/App/assets/78819774/1597e8d9-6a71-471e-a91f-a8ea8e1bc171

@alexpensify please close this. Issue is not reproducible anymore.

👍🏼


Activemq 5.17.x

CVE-2022-23181 / CVE-2021-42340 - Tomcat minor vulnerabilities

Please, rebase and create a clean PR, this one can't be merge as it is.

my mistake. sorry


StreamSignal Not Working As Expected

With
Signal<int> emitter = createSignal(0);
StreamSignal<int> temp = Stream.periodic(Duration(seconds: 1), (epoc) => 1).listen((data) {
  emitter.value++;
});

Using emitter.value inside a widget will cause a rebuild, as expected. But with
int count = 0;
StreamSignal<int> emitter = Stream.periodic(Duration(seconds: 1), (epoc) => count++).toStreamSignal();

using emitter.value.value does not cause the widget to rebuild.

You need to wrap the second signal with bindSignal() as it is not connected to the widget.
toStreamSignal() just is an extension method to create a StreamSignal and does not come from SignalsMixin.

I see, thanks! Might be a good note to make in future documentation. Would love to see examples/integrations with rxdart as I believe combining these patterns would be really powerful, as it is in the JS ecosystem.

I do have an example with RXDart but yes would love to add more to the docs!


Added start/stop service/component async

Adding the following async route methods

ServiceStartAsync
ServiceStopAsync
ComponentStopAsync (ComponentStartAsync already exists)

@zyndiecate RFR

LGTM


Add [Chigozie123] #personal GDDJYF…S64TWJ

Address: GDDJYFG3FAMKRIV3GOZIOFGNRGU7VUMMKTUM3HSR6EPFYGJ7KPS64TWJ
Tags: personal
Title: Chigozie123
Requested by @chigozie123c

@Chigozie123c Can you please explain what your concern is about this account?


[field_transformations] return field instead of FieldPtr

currently, the transformation return FieldPtr instances, which is used in the TransformedField class.. this should be changed. The transformations could yield actual fields, while TransformedField internally constructs a new ptr from them... this would make the transformations usable in different contexts.

We probably also don't need TransformedField. In general, this header could use some cleanup...


Unattend for sysprep is not supported

long time ask - https://vstf-us-wa-28.partners.extranet.microsoft.com:8443/tfs/ContentIdea/ContentIdea/_workitems?id=78694&_a=edit

@axelgMS : Thanks for your contribution! The author, @glimoli, has been notified to review your proposed change.

Hi @glimoli - Would you review the proposed changes?
Also, could you link your GitHub and Microsoft accounts? Thank you!

Hi @ktoliver , yes I'm ok with this notes under the generalized section.
Regarding linking my account, thank you, that was done.

And in details, we just need to add the following disclaimer on the Generalized section:
A custom unattend.xml is not supported. While we do support the additionalUnattendContent property, that only provides limited support for adding microsoft-windows-shell-setup options into the unattend.xml that the Azure provisioning agent uses. E.g.  they can use additionalUnattendContent to add FirstLogonCommands and LogonCommands. See also https://github.com/Azure/azure-quickstart-templates/issues/1407

Hi @glimoli - Thanks. Should we merge the PR, and then you can add the disclaimer in a new PR in the private repo? Or are you asking the contributor to add the disclaimer? Thanks.

@sign-off

#sign-off

hi @glimoli - based on your #sign-off, we'll merge this PR. @axelgMS - if any additional content changes need to occur, can you submit them in a new PR? Thanks.
note that I've made an edit to the links (removing the 'en-us' location).


Add our Developer Experience Engineer career opportunity to the README

Issue Summary
The role of Developer Experience Engineer just became available and we want to announce it in the README. Here is the copy:
If you're a software engineer who is passionate about #DeveloperExperience and/or #OpenSource, this is an incredible opportunity to join our #DX team as a Developer Experience Engineer and work with @thinkingserious and @aroach! Tell your friends :)
Acceptance Criteria

The above announcement is added to the Announcements section of this README

I'm taking this one.

@thinkingserious Have raised PR for this: https://github.com/mptap/open-source-library-data-collector/pull/1


Fixed bug in SQL Server 2000: the column "state" is not available

Type of Change

[X] Bug fix (non-breaking change, fixes # )
[ ] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

looks fab! 👌 thank you, kind sir

"istilllove2000" 🤣


Apply accessibility guidelines to splink documentation

[ ] Change the current default font to an accessible font that follows Web Content Accessibility Guidelines (WCAG) 2.1.There is functionality to easily do this with mkdocs

[ ] The visual presentation of text  needs to have a contrast ratio of at least 4.5:1 on all colour palettes (light/dark)

additionally there is a way to automatically test for accessibility on websites via the node.js package Pa11y.
Mostly everything passes.
Running it on one of the notebook tutorials however gives

 • Error: Img element missing an alt attribute. Use the alt attribute to specify a short text alternative.
   ├── WCAG2AA.Principle1.Guideline1_1.1_1_1.H37
   ├── html > body > div:nth-child(8) > main > div > div:nth-child(3) > article > div:nth-child(15) > div:nth-child(2) > div > div > div > img
   └── <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAA6QAAAh6CAYAAACbjNB4AAAAAXNSR0IArs4c6QAAIABJREFUeF7snQnYXsPZxyeI2CO2oKEpgqKUNqittdSui4ooTS1FtbS0tTSf1q5pVa0pRZVPlYaitdS+tBKRamlV1RKfJZbEGklskch3/Q4T533ybOfcc94zz3n+c125SJ4zc+75zT33zH9mzjl95syZM8...

So yeah. need to add alt-text to the images we have on the notebooks


Instrument module init in DEV

I end up hacking ad-hoc versions of this into the build all the time so let's just add it as a DEV-only patch. That Metro file barely ever changes so it shouldn't be a burden.
Test plan
Change shouldLog to true locally. Observe the output:

I don't know if this may be helpful for you, but there's a way for "Investigating the Loaded Modules"

Yeah that's nice but not helpful enough because I want to see the dependency tree and the actual timings


[Event Change Request]  Codeunit 13 "Gen. Jnl.-Post Batch" – OnPostGenJournalLineOnBeforeCheckDocumentNo

Describe the request
Hello, can you please add ???GenJnlTemplate??? to the event OnPostGenJournalLineOnBeforeCheckDocumentNo in codeunit 13 "Gen. Jnl.-Post Batch"?
    local procedure PostGenJournalLine(var GenJournalLine: Record "Gen. Journal Line"; CurrentICPartner: Code[20]; ICTransactionNo: Integer) Result: Boolean
    var
        IsPosted: Boolean;
        SavedPostingDate: Date;
        SavedVATReportingDate: Date;
    begin
        if GenJournalLine.NeedCheckZeroAmount() and (GenJournalLine.Amount = 0) and GenJournalLine.IsRecurring() then
            exit(false);

        GenJnlPostLine.SetPreviewMode(PreviewMode);
        LineCount := LineCount + 1;
        if CurrentICPartner <> '' then
            GenJournalLine."IC Partner Code" := CurrentICPartner;
        UpdateDialog(RefPostingState::"Posting Lines", LineCount, NoOfRecords);
        MakeRecurringTexts(GenJournalLine);
        OnPostGenJournalLineOnBeforeCheckDocumentNo(GenJournalLine, GLRegNo, GenJnlTemplate);
        CheckDocumentNo(GenJournalLine);
        GenJnlLine5.Copy(GenJournalLine);
        PrepareGenJnlLineAddCurr(GenJnlLine5);
        UpdateIncomingDocument(GenJnlLine5);
        UpdateDimBalBatchName(GenJnlLine5);

    [IntegrationEvent(false, false)]
    local procedure OnPostGenJournalLineOnBeforeCheckDocumentNo(var GenJnlLine: Record "Gen. Journal Line"; GLRegNo: Integer; GenJournalTemplate: Record "Gen. Journal Template")
    begin
    end;

Additional context
We would like to check if the template is recurring because then we run some additional processing.
Internal work item: AB#545263

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: .


Client will set values it can't deserialize

It documents that values should be strings but it doesn't actually prevent you from doing something like:

client.set(b'key', ('boom, 'shaka', {'1': 'two'}))

Should we just default to using the serializers from serde?

@sontek it was my understanding that that was the functionality. I think that defaulting to using serde would be good, yes. We can make it a kwarg with the serde default.
Let's make this change once the python3 version of serde is shipped, which should be https://github.com/pinterest/pymemcache/pull/112

Current behavior.
>>> from pymemcache.client.base import Client
>>> client = Client(('localhost', 11211))
>>> client.set(b'key', ('boom', 'shaka', {'1': 'two'}))
True
>>> client.get(b'key')
"('boom', 'shaka', {'1': 'two'})"

@sontek I am unclear on what expected behavior you would like to see here.  Closing this ticket for now, but feel free to re-open with more information.

@jogo I think we should leave this open, your snippet shows exactly the behavior I'm complaining about.  You are getting back something you didn't pass in:
Tuple of objects:
('boom', 'shaka', {'1': 'two'})

Bytes:
b"('boom', 'shaka', {'1': 'two'})"

If you are using the client and you pass in a dictionary, tuple, etc you are going to expect that same type back.

(I don't have privileges to re-open)

What are suggestions for fixing here?
I can think of 2:

return an error if you try and pass a non string (this would probably break a bunch of people's usages)
serialize and deserialize always by default, which affects performance.

@sontek do you have any thoughts on these solutions, or any other?

I would suggest doing serialize/deserialize.  Since serde.py is using flags to mark the content I don't think there would be a big performance hit would there?  It would know if it needs to deserialize coming back and its already serializing on the way there (to bytes).

@sontek I don't think that would work, for example:
>>> a = object()
>>> a
<object object at 0x107314e30>
>>> client.set(b'key', a)
True
>>> client.get(b'key')
'<object object at 0x107314e30>'

The return value doesn't have enough information to recreate the original object.

@jogo Thats why we would user serialization to have enough information.  This can be done with jsonpickle, pickle, msgpack, etc.

I guess since there are already args for serializer and deserializer maybe the best option is to just reject the values we can' store properly and tell them to set a serializer?

@sontek that's what I am thinking, I am weary of silently adding in a serializer like this. I think manually setting a serializer for this makes more sense. As for the default behavior, I am little weary of changing it so perhaps for now we can add a flag to change the behavior and re-visit making it the default down the road.

After thinking about this further, I don't think we should change the current default behavior. The current behavior is documented.
http://pymemcache.readthedocs.io/en/latest/apidoc/pymemcache.client.base.html
We can add a no-op serializer that will reject values that aren't already serialized.
Closing ticket for now, but if you would like I can make it easier to avoid this issue or clarify the documentation etc.