Swagger spec for RESTful API

@yaron2  I am willing to work on this issue to kick start

Thats great, excited too see this happen.

@yaron2 - could you elaborate more on the issue and requirement please?

@HarshKhatore We need to create Open APi specification for Dapr http rest apos so that clients can be autogenerated in various languages.

@s-m-sufyian Is this still something you're planning to or would like to tackle? I might also be interested.

@RichiCoder1 I am planning to do this , lets pair ?

@s-m-sufyian Sure! What did you have in mind?
Looking at how endpoints are defined (and also not being too familiar with the metadata capabilities of go), it looks like the OpenAPI document needs to be handwritten. Api docs are here, so will just be translating those a openapi.yaml/json that lives in this repo right?

Maybe we can use something like this?
https://github.com/go-swagger/go-swagger/blob/master/docs/use/spec.md

Hi! Is there any progress with it? If no, I would like to pick up and start creating open API files based on oficial API documentation. Thank you.

Hi! Is there any progress with it? If no, I would like to pick up and start creating open API files based on oficial API documentation. Thank you.

Thank you for wanting to pick this up!
@RichiCoder1 @s-m-sufyian have you made any progress with this?
Also I recommend looking into what @waqasraz posted.

Hi! Is there any progress with it? If no, I would like to pick up and start creating open API files based on oficial API documentation. Thank you.

Looks like it's all yours. Should I assign you?

Yes, please. I made some progress. Will submit for review soon.

hey @dancadana, any progress?

@yaron2 Hi!
I've done Service Invocation Swagger. Trying to test it. Hopefully will do it today, or will get back to you with questions.

@yaron2  Global security scheme shouldn't be defined in service Invocation Swagger, should it?

@yaron2 Global security scheme shouldn't be defined in service Invocation Swagger, should it?

A security scheme is optional.
For OpenAPI it would look like this:
ApiKeyAuth:
      type: apiKey
      in: header
      name: dapr-api-token

@yaron2 Where can I upload it?

@yaron2 Where can I upload it?

Create a PR and put it under dapr/dapr/proto: https://github.com/dapr/dapr/tree/master/dapr
Thanks!


Feedback needed: Fractal update functions thanks to lenses

Hi guys,
Quick disclaimer
I am very new to Elm and while reading An introduction to Elm something bugged me. The fact that only views are shown as composable (cf. https://guide.elm-lang.org/reuse).
I tried to find an elegant solution to let sub components/modules/functional slices of the app/... update their own model without having to know about the top level app model.
This is a very humble proposal and it's probably missing a lot of cases (for example Command are not handled in my current proposal). I am looking for feedback on this idea. There might be a way that I missed to do that already, so I am up for any feedback :)
It's highly inspired of the Cycle.js way to do that (with cycle-onionify and lenses https://github.com/staltz/cycle-onionify).
In the rest of the issue I'll use the term component to talk about a functional slice of an app (something that knows how to render, that possesses the business logic to update its own state and that returns some effects (the former is not part of this proposal)).
My problem: Components cannot define their own update function
So far, what I see is that there can only be a single signature for any update function of the app update : AppMessage -> AppModel -> AppModel.
Whether you are building an update function for the root component or for a nested leaf component, the function will always take a full AppModel.
The problem is that leaf component then need to know about the structure of AppModel and cannot be reused in another context (only their view can be reused).
Concrete example: the checkbox example
Let's work on a concrete example to illustrate my proposal. The checkbox example is a good one I think http://elm-lang.org/examples/checkboxes
The model looks like this
type alias Model =
  { notifications : Bool
  , autoplay : Bool
  , location : Bool
  }

The views are factorized with the checkbox function
The update method is defined by the parent that handles all the messages from the checkbox views.
Lenses to the rescue
The idea is to be able to select a specific slice of the main model and let the component work on that slice independently. This way the component can work without knowing anything about the app structure.
In order to achieve that, I came up with an isolate function that will feed the component the right slice of the model and when an update occurs, update the parent model with the updated model of the component.
type alias Getter parentModel childModel =
    parentModel -> childModel

type alias Setter parentModel childModel =
    parentModel -> childModel -> parentModel

type alias Update message model =
    message -> model -> model

isolate : Getter parentModel childModel -> Setter parentModel childModel -> Update message childModel -> Update message parentModel
isolate getter setter update message model =
    setter model (update message (getter model))

Final result
Here is the current update function of the given example
update : Msg -> Model -> Model
update msg model =
  case msg of
    ToggleNotifications ->
      { model | notifications = not model.notifications }

    ToggleAutoplay ->
      { model | autoplay = not model.autoplay }

    ToggleLocation ->
      { model | location = not model.location }

Here is the isolated version
-- checkbox.elm
checkboxUpdate: Msg -> Bool -> Bool
checkboxUpdate msg model = not model

-- main.elm
notificationUpdate = isolate (model -> model.notification) (model -> notification -> {model | notification = notification}) checkbodUpdate (\_ -> model -> model)
-- same for autoplay and location

update: Msg -> Model -> Model
update msg model = notificationUpdate msg >> autoplayUpdate msg >> locationUpdate msg

This enable easy reuse of components at different level of the application without having to write a reducer every single time.
Limitations
This proposal is not yet a viable option for, as far as I know, two reasons:

Commands are not handles (I might have a idea for that)
messages are not isolated, meaning that all the checkbox will react to a click on a single one of them (I have no idea yet how to fix that).
... probably some other limitations that I cannot see due to my limited knowledge of Elm.

What I am looking for?
Pretty much anything from "this is a super bad idea because of this, this and that" or "this is not the elm philosophy at all" to "Good idea, I might have some idea to fix the limitations" or "Well, is already possible with this solution".
Working on this was super interesting anyway and I really had a great time working on this, so even if this is a bad idea, my time was not lost at all ;)
BTW: really :heart: the language!!

Thanks for posting this!
A quick first reply to your initial problem. A nested component can have its own isolated update function. Consider this change on your example:
type alias Model =
    { notifications : Notifications.Model
    , autoplay : Autoplay.Model
    , location : Location.Model
    }

type Msg
    = NotificationsMsg Notifications.Msg
    | AutoplayMsg Autoplay.Msg
    | LocationMsg Location.Msg

update : Msg -> Model -> ( Model, Cmd Msg )
update msg model =
    case msg of
        NotificationsMsg msg ->
            let
                ( notificationsModel, cmd ) =
                    Notifications.update msg model.notifications
            in
                ( { model | notifications = notificationsModel }, Cmd.Map NotificationsMsg cmd )
        ...

As you can see, the update function in the Notifications module is isolated and has its own Msg -> Model -> ( Model, Cmd Msg ) signature. Also, this module handles itself its Notifications.Msg and only them. The Main module does not need to know the internals of Notifications, and vice versa. Same principles can be applied for view, init and subscriptions. What do you think?

Hello, this type of discussion is suited for https://discourse.elm-lang.org (whereas github issues are used by Elm only for specific bugs that will be fixed) -- If you want to discuss further, please move the discussion there, thanks!

Oh sure @avh4 !! I didn't realize there was a discourse for that. My apologies.
I created the topic there (pending at the moment) and will close this Issue now.
Sorry for the noise

@cedricss just replying here quickly as for the moment the thread is not yet active on discourse.
Thanks for this reply, it is interesting indeed. Quick question though, I am not sure I was clear about the fact that notifications location and autoplay are not 3 different components but 3 "instances" of the same component.
You piece of code would look like this, if I am not mistaking
type alias Model =
    { notifications : Checkbox.Model
    , autoplay : Checkbox.Model
    , location : Checkbox.Model
    }

type Msg
    = NotificationsMsg Checkbox.Msg
    | AutoplayMsg Checkbox.Msg
    | LocationMsg Checkbox.Msg

update : Msg -> Model -> ( Model, Cmd Msg )
update msg model =
    case msg of
        NotificationsMsg notificationsMsg ->
            let
                ( notificationsModel, notificationsCmd ) =
                    Checkbox.update notificationsMsg model.notifications
            in
                ( { model | notifications = notificationsModel }
                , Cmd.Map NotificationsMsg notificationsCmd
                )
        ...

It would probably work, I'll need to try this out :)
I believe there is something I am missing though, how do you map checkbox messages to the Msg type? This is not something the parent has control over, Am I wrong?


Reveal pins to appium for Automation Testing

Hi,
I am using Mapsui 1.4. I am currently engaging in Automation testing using Appium. The testing team could not able to select pins on the map. Can you let me know, how to set automation properties for Mapsui map and pins?
Thanks

I have not looked into appium. I assume it hooks into native widgets. The pins on the map are rendered with skia so no native widgets. So i think this will not be possible in it s current form.
Is there an easy way to enable Mapsui for appium?
For performance reasons I do not intend to replace all pins with XF widgets.


Update Survey and Table App Font

Update the headings and body font on the ODK-X Survey and Tables app to meet the ODK-X design guidelines
Check this issue for guidance: https://github.com/odk-x/tool-suite-X/issues/453

hello @Redeem-Grimm-Satoshi can this issue be assigned to me?

hello @Redeem-Grimm-Satoshi can this issue be assigned to me?

Finish with the starter issue first very important!

Update the headings and body font on the ODK-X Survey and Tables app to meet the ODK-X design guidelines
Check this issue for guidance: #453

Hello @Redeem-Grimm-Satoshi !
How are you doing ?
I’d like to tackle the font update issue (https://github.com/odk-x/tool-suite-X/issues/498) to align with the ODK-X design guidelines. This will significantly improve the app’s usability and aesthetics. Please assign me this issue!
Best,
Collins HAYA

Hello @Redeem-Grimm-Satoshi , please can you assign this to me? I have been able to complete the starter issue and would like to try my hands at this

Hello @Collins-Webdev @TunrayoIlawole go ahead and work on it

Hi @Redeem-Grimm-Satoshi , please I would like to confirm if the font of list items should be updated as well

Hi @Redeem-Grimm-Satoshi , please I would like to confirm if the font of list items should be updated as well

Yes everything need to meet the design standard


Upgrade to Django 1.8 and fix several related issues

I started down this path because dumpdata was broken after our switch to our own user class.
I ended up with this, which is still tangential work but necessary.

I've tested this locally and think it's ready for staging.


Binary provided for macos in release section is not working

Binary provided for macos Orbot.pkg in release section is not working. Showing error Application "ORBOT" can't be opened. Also, I believe build guide is outdated too in README section.

Binary provided for macos Orbot.pkg in release section is not working. Showing error Application "ORBOT" can't be opened.

Yeah, sorry. This is more or less provided "just because". You will need to re-sign with your own credentials.
To be able to distribute this outside the app store, we would need to change the app, so it doesn't provide a "Network Extension", but a "System Extension".
I spent some time on it, already, but to change this is non-trivial, especially in a project which also contains an iOS app using a "Network Extension".
Since the macOS version is just a side-effect of the iOS app and a means for easier debugging, there is currently zero money available to make this happen.

Also, I believe build guide is outdated too in README section.

In what way? Well, the minimal OS and Xcode version is probably slightly outdated. But else?

Need a bit short guide/resources about how to make this work, if i want to sideload this app on macos.

Also, I believe build guide is outdated too in README section.

In what way? Well, the minimal OS and Xcode version is probably slightly outdated. But else?

In git command repo contains different name orbot-ios instead of orbot-apple that's why felt it is outdated, also when I try to build even after resolving this it failed, don't know the exact error.

Oh, ha! Good catch.
When you provide an error log, I might be able to help. Otherwise: 🤷

Need a bit short guide/resources about how to make this work, if i want to sideload this app on macos.

And what about this?

Need a bit short guide/resources about how to make this work, if i want to sideload this app on macos.

And what about this?

Sorry, overlooked that.
Can't help you, there, sorry. Never did it myself. This pkg is seriously provided just because we can. No instructions come along with it.
If you don't want to install from the macOS app store, don't have a clue how to resign an app pkg yourself, then your best bet is to build from scratch.
For the latter, I might be able to help you, if you run into specific problems, but I'm also not an Xcode beginner's tutor.
There's always another option:
You can still just run a plain Tor yourself on macOS. E.g. install via Homebrew. It's a command line tool, which makes it necessary to read some docs, but it has the full power.
And if your whole intention is to do web browsing, anyway, then please just use Tor Browser. Using Tor with another browser can be dangerous, if you don't know, what you're getting yourself into.

If you don't want to install from the macOS app store, don't have a clue how to resign an app pkg yourself, then your best bet is to build from scratch.
For the latter, I might be able to help you, if you run into specific problems, but I'm also not an Xcode beginner's tutor.

Thanks for the update, but I will go with this route when no other option left.

There's always another option:
You can still just run a plain Tor yourself on macOS. E.g. install via Homebrew. It's a command line tool, which makes it necessary to read some docs, but it has the full power.

Basically i want to run TOR as a vpn connection, that's why i chose to go with ORBOT. There is another solution that you mentioned which i already tried with homebrew to install TOR & use it as SOCKS proxy. But i want to use it as vpn connection, if you can help me in this I really appreciate that.

And if your whole intention is to do web browsing, anyway, then please just use Tor Browser. Using Tor with another browser can be dangerous, if you don't know, what you're getting yourself into.

Currently, using tor as testing purposes on VM, so I'm fine with risk that comes along with

I guess, Orbot macOS is actually your best choice, then.


Update exported variables for Mono tool scripts

Update scripts exports even when normal script instances are created to better support tool scripts with exported variables.
Fixes #26753
If the Mono script is marked as a tool script, instance_create is used over placeholder_instance_create, which means _update_exports() is never called. This led to the editor not being able to show the script's exported properties in the inspector.

I don't think we want to do this every time a script instance is created. Instead I think we want to call update_exports() (or _update_exports(), it's the same) at the end of reload().
The only reason it's called in placeholder_instance_create is for the new placeholder instance to be updated. It doesn't need to update all placeholder instances but _update_exports() does it. That should probably be changed, but I'm too afraid to introduce a regression now so I will do that after 3.1.
Can you try adding this to reload() instead and see if it fixes #26753?

Will do, I was also somewhat surprised it called it in create_placeholder_instance.
The only reason I think the impact is likely low is because exports_invalidated will be set to false and then _update_exports will not do much anymore, since the tool-scripts shouldn't have placeholders.

Indeed, I didn't think about that. It's a tool scripts so there will be no placeholders to update. Looks good to me then if you want to leave it as is.

I just pushed an updated version.
Moving it to reload() also fixes the issue for me, and I think it's more appropriate (and sensible) to place it there.

Thanks! :)


nvm node is recognised by npm install script.

NPM version (npm -v): 6.1.0
Node version (node -v): v10.7.0
Node Process (node -p process.versions): { http_parser: '2.8.0',
node: '10.7.0',
v8: '6.7.288.49-node.15',
uv: '1.22.0',
zlib: '1.2.11',
ares: '1.14.0',
modules: '64',
nghttp2: '1.32.0',
napi: '3',
openssl: '1.1.0h',
icu: '62.1',
unicode: '11.0',
cldr: '33.1',
tz: '2018e' }
Node Platform (node -p process.platform): linux
Node architecture (node -p process.arch): x64
npm node-sass versions (npm ls node-sass): missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>PATH (echo $PATH): /root/.nvm/versions/node/v10.7.0/bin:/sbin:/bin:/usr/sbin:/usr/bin

I installed node with nvm install  and PATH variable is having node
When try to install node-sass, install script is not able to identify node command.
Note: I am doing all these activity in root shell
Command Output:
$ npm install node-sass
><EMAIL_ADDRESS>install /home/ajayg/Kora-Web/node_modules/node-sass
> node scripts/install.js
sh: node: command not found
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>install: node scripts/install.js
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-08-08T13_59_17_167Z-debug.log
Log:
1772 warn<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
1773 warn optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
1774 warn notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
1775 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS:    darwin
1775 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch:  any
1775 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS:   linux
1775 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: x64
1776 verbose stack Error<EMAIL_ADDRESS>install: node scripts/install.js
1776 verbose stack spawn ENOENT
1776 verbose stack     at ChildProcess. (/root/.nvm/versions/node/v10.7.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
1776 verbose stack     at ChildProcess.emit (events.js:182:13)
1776 verbose stack     at maybeClose (internal/child_process.js:961:16)
1776 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:5)
1777 verbose pkgid<EMAIL_ADDRESS>1778 verbose cwd /home/ajayg/Kora-Web
1779 verbose Linux 3.10.0-514.el7.x86_64
1780 verbose argv "/root/.nvm/versions/node/v10.7.0/bin/node" "/root/.nvm/versions/node/v10.7.0/bin/npm" "install" "node-sass"
1781 verbose node v10.7.0
1782 verbose npm  v6.1.0
1783 error file sh
1784 error code ELIFECYCLE
1785 error errno ENOENT
1786 error syscall spawn
1787 error<EMAIL_ADDRESS>install: node scripts/install.js
1787 error spawn ENOENT
1788 error Failed at the<EMAIL_ADDRESS>install script.
1788 error This is probably not a problem with npm. There is likely additional logging output above.
1789 verbose exit [ 1, true ]

Sorry, if it's not in the path, there is no way for the install scripts to use them. This would be true for any other project

I already below $PATH value in the issue description.
$echo $PATH
/root/.nvm/versions/node/v10.7.0/bin:/sbin:/bin:/usr/sbin:/usr/bin
$ which node
/root/.nvm/versions/node/v10.7.0/bin/node
$ which npm
/root/.nvm/versions/node/v10.7.0/bin/npm
node is available in the PATH, but still it is not picking.
I found a workaround
npm install --unsafe-perm node-sass
But my question is, why should i pass --unsafe-perm ?

npm runs life cycle scripts as a restricted user. If that user doesn't have
the appropriate permissions you'll need --unsafe-perms. This is why you
should never run npm as sudo.
On Fri., 10 Aug. 2018, 3:40 pm Ajay Choudary<EMAIL_ADDRESS>wrote:

I already below $PATH value in the issue description.
$echo $PATH
/root/.nvm/versions/node/v10.7.0/bin:/sbin:/bin:/usr/sbin:/usr/bin
$ which node
/root/.nvm/versions/node/v10.7.0/bin/node
$ which npm
/root/.nvm/versions/node/v10.7.0/bin/npm
node is available in the PATH, but still it is not picking.
I found a workaround
npm install --unsafe-perm node-sass
But my question is, why should i pass --unsafe-perm ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2470#issuecomment-411980955,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWElDd4Mj50SooAHmhxhqJhFjATPJks5uPRzKgaJpZM4V0Fto
.


Helper Implementations for COM Types

Winapi-rs has has support for COM types through manually declaring the vtable, but I've noticed that using these types is pretty nasty compared to doing so in C (see this example). This could be greatly simplified by adding an impl to the various COM types that wrap up the calls to the vtable functions. I've started implementing this on my fork (see this commit), but I wanted to get some feedback before making a pull request. Is this sort of change in line with the design ethos of winapi-rs? It seems like the idea is to only provide the C bindings to the Windows APIs, so this starts to go beyond that in providing a wrapper around the C bindings to provide a cleaner API. The reason I still think this is a good idea is that it recreates the C++ API that COM is supposed to have, which I would argue still adheres to the design ethos of winapi-rs.
Let me know what you think. If this seems like something worth doing I can make PRs as get things put together.

Not worth doing because that's a lot of typing.
What is worth doing is this:
https://github.com/retep998/winapi-rs/commit/c51c581e3e18b1e1179524a5530c9faced41b21f


Update first_app.rst [16037]

command to build is not correct. Hence corrected.
Added cmake options

Closing due to inactivity. It might be reopened addressing the reviewers comments.


System tray popups behave weirdly.

When right clicking something in tray, and then clicking on an empty "desktop" or a floating terminal, it stays there and behaves weirdly. See video
https://github.com/user-attachments/assets/d50204eb-87e6-4d54-8557-059904732069

oh yeah. this is weird. happens on waybar popups too. i think its something to do with the tooltip package and not this repo.\


fix wrong temperature indicator

remove unrelated value return from current_temp()

Which wrong temperature were you getting? And on which model?
The problem here is that different models use different fields (I think this stands for "real" vs "calculated" measurements).

I have one of the inverted models.
The value of "I_CALC_AT":"5120" is similar to the value of "I_RCT":"5632" and both are changing every few minutes.
For other models, what is the value you see for I_RAT? for me it outputs a local temperature reading.

Thanks for the additional information! I have pushed a slightly different code change that would also better cover other models where the value is found in other fields. I think it should now work for all AC model owners.
I'll be closing the PR without a merge, but this fix is 100% in your credit :)


Install a webaction shouldn’t add a dependency on WebModule

It should be possible for features like Misk’s Config to be used without a web server. But today installing any web action (such as config’s optional web admin) drags in the entire web dependency.

I believe this was fixed by this change: https://github.com/square/misk/pull/327/files
But we should write a test to confirm.

Looks resolved, closing.


Xcode 12 display wrong

Hello,
Since Xcode 12 the calendar display not as usual. Background changed and layout too.
It's not really usable in current state.
Any fix ?
Thanks

Please check this. Hope this will work.
[dateSelectionController.datePicker setPreferredDatePickerStyle:UIDatePickerStyleWheels];

Please check this. Hope this will work.
[dateSelectionController.datePicker setPreferredDatePickerStyle:UIDatePickerStyleWheels];

It works for me ,thanks a lot

Please check this. Hope this will work.
[dateSelectionController.datePicker setPreferredDatePickerStyle:UIDatePickerStyleWheels];

It works for me ,thanks a lot

if (@available(iOS 13.4, *)) {         [dateSelectionController.datePicker setPreferredDatePickerStyle:UIDatePickerStyleWheels];     } else {         // Fallback on earlier versions     }

if (@available(iOS 13.4, *)) {         [dateSelectionController.datePicker setPreferredDatePickerStyle:UIDatePickerStyleWheels];     } else {         // Fallback on earlier versions     }


IE & iOS

Hi Sam,
Your demo pages are not showing the gallery on IE11 and any browser on iOS. The data for the gallery seems to be rendered in the source of the page in each case.
https://ecodev.ch/natural-gallery/demo/
The same is happening with our own instance of Natural Gallery.
http://eleven.ort.org/gallery/
Thank you for improving the responsive square feature.
Best wishes

Hi Sadler,
It's not a bug, it's a feature :)
iOS9 and older + IE11 and older represents ~4% of internet traffic. These browsers don't always respect the W3C standards, that's a reason I've chosen to drop support for this versions. This allow me to use a js compilation method that reduces the file size for the other users.
I'd like to stay focused on the future and features, and not allocate too much time to old browsers. I hope you understand.
Thanks again for using this lib and sending feedbacks.
Best regards !


[BUG] In Jupyter mode have the link target to "_blank"

You may find a solution to your problem in the docs or issues.
Describe the bug
When using jupyter.print([link=http://my.cool.link.com]cool link[/link]) and when trying to follow the link it tries to open the link in the resulting cell and getting a broken link. I would suggest to fix this link rendering a bit:
https://github.com/Textualize/rich/blob/master/rich/jupyter.py#L66
by adding the following (target="_blank"):
text = f'{text}' so it will open the link in a new window
Platform

Click to expand
What platform (Win/Linux/Mac) are you running on? What terminal software are you using?
I may ask you to cut and paste the output of the following commands. It may save some time if you do it now.
python -m rich.diagnose
python -m rich._windows
pip freeze | grep rich

Care to submit a PR for that?

I'll open a PR

Care to submit a PR for that?

sorry just saw your message! I see someone already beat me to it :)
Thanks for the quick fix...


Kedau-under 'cheltechat' is missing...means 'blistered' should it be under melau as well?

Kedau-under 'cheltechat' is missing...means 'blistered' should it be under melau as well? created by<EMAIL_ADDRESS>on 2017-01-03 08:13:23

<EMAIL_ADDRESS>replied, melau (tour/tmau) has initial T in its base, but not D. KEDAU seems to be v.recip. (do something each to other), but not melau (heat, cook etc.). i don't even know, which word could be related with KEDAU... interesting

<EMAIL_ADDRESS>replied, Aleks, it's actually 'dmau ' not tmau

<EMAIL_ADDRESS>replied, Aleks, it's actually 'dmau' not tmau.  But for this thread, we need still to learn the meaning of KEDAU as it appears here:chachetechat	v.recip.	wound each other.chachetechat a ketemall; di du el mengetechat; tomall a bedengir; chetechat a bedengeir; KEDAU a bedengir, chetechetil.And also figure out the main verb form of KEDAU.

<EMAIL_ADDRESS>replied, melau:melul: delau:delul


add support for todo.txt syntax

I recently changed horses and got into todo.txt. It seems to be more popular this days than taskpaper. I would love to see support for the syntax in taskpaperplus.
https://github.com/ginatrapani/todo.txt-cli/wiki/The-Todo.txt-Format

The link above is empty, see https://github.com/todotxt/todo.txt for the format of todo.txt files.


Internal error for URLs with percent encoding

E.g.
https://pub.dartlang.org/api/packages/http/versions/0.9.2+%40
gives 'Internal error'
whereas the "same" request
https://pub.dartlang.org/api/packages/http/versions/0.9.2+A
gives 404

These are not the same urls since "%40" corresponds to "@".
The version "0.9.2+@" is not a valid semantic version, so we get an semantic version parsing exception.
I think an "Internal error" is not as bad as it sounds, but I can make an update to the API handling to return "400 Bad Request".

CL up for review for package:pub_server: https://codereview.chromium.org/1231753007/

The URL https://pub.dartlang.org/api/packages/http/versions/0.9.2+%40 will now return
{"error":{"message":"Version string \"0.9.2+@\" is not a valid semantic version."}}


Yahoo

There are specific instructions on using Yahoo external login provider!

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

ID: 5f869636-630e-2542-b029-199154ef70c3
Version Independent ID: cea7e5a6-383f-aeb5-2476-7c7d0a8bb851
Content: External OAuth authentication providers
Content Source: aspnetcore/security/authentication/social/other-logins.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@dsiddananja  sorry about that. And we don't have the resources to add that either.


[SPARK-46020][INFRA] Add Python 3.12 to Infra docker image

What changes were proposed in this pull request?
This PR aims to add Python 3.12 to Infra docker images.
Note that Python 3.12 has a breaking change in the installation.

distutils module itself is removed at Python 3.12 via PEP-632 in favor of packaging package.
Apache Spark 4.0.0 is ready for Python 3.12 via SPARK-45390 by removing distutils usages

https://github.com/apache/spark/pull/43192

However, some 3rd party packages are not ready for Python 3.12. So, this PR skips those kind of packages.

Why are the changes needed?
This PR is a preparation to add a daily Python 3.12 GitHub Action job later for Apache Spark 4.0.0.
As of today, Apache Spark 4.0.0 has Python 3.8 ~ Python 3.11 test coverage.

Python 3.9 (Main)

https://github.com/apache/spark/blob/master/.github/workflows/build_and_test.yml

PyPy3.8, Python 3.10, Python 3.11 (Daily)

https://github.com/apache/spark/actions/workflows/build_python.yml

Does this PR introduce any user-facing change?
No.

No.

Could you review this PR, @HyukjinKwon ?

Thank you, @HyukjinKwon !

Merged to master.


Release WordPressCS 3.0.1

:warning: DO NOT MERGE (YET) :warning:
Please do add approvals if you agree as otherwise we won't be able to release.
PR for tracking changes for the 3.0.1 release. Target release date: Thursday September 14, 2023.
Release checklist
General

[x] Verify, and if necessary, update the allowed version ranges for various dependencies in the composer.json - N/A
[x] PHPCS: check if there have been releases since the last WordPressCS release and check through the changelog to see if there is anything WordPressCS could take advantage of - N/A
[x] PHPCSUtils: check if there have been releases since the last WordPressCS release and update WordPressCS code to take advantage of any new utilities - N/A
[x] PHPCSExtra: check if there have been releases since the last WordPressCS release and check through the changelog to see if there is anything WordPressCS could take advantage of - PR #2387
[x] Check if the minimum WP version property needs updating in MinimumWPVersionTrait::$default_minimum_wp_version and if so, action it - N/A
[x] Check if any of the list based sniffs need updating and if so, action it.
:pencil2: Make sure the "last updated" annotation in the docblocks for these lists has also been updated!
List based sniffs:

[x] WordPress.WP.ClassNameCase - N/A
[x] WordPress.WP.DeprecatedClasses - N/A
[x] WordPress.WP.DeprecatedFunctions - N/A
[x] WordPress.WP.DeprecatedParameters - N/A
[x] WordPress.WP.DeprecatedParameterValues - N/A

[x] Check if any of the other lists containing information about WP Core need updating and if so, action it.

[x] $allowed_core_constants in WordPress.NamingConventions.PrefixAllGlobals - N/A
[x] $pluggable_functions in WordPress.NamingConventions.PrefixAllGlobals - N/A
[x] $pluggable_classes in WordPress.NamingConventions.PrefixAllGlobals - N/A
[x] $target_functions in WordPress.Security.PluginMenuSlug - N/A
[x] $reserved_names in WordPress.NamingConventions.ValidPostTypeSlug - N/A
[x] $wp_time_constants in WordPress.WP.CronInterval - N/A
[x] $known_test_classes in IsUnitTestTrait - N/A

Release prep

[x] Add changelog for the release - PR #2385
:pencil2: Remember to add a release link at the bottom!
[x] Update README (if applicable) - N/A
[x] Update wiki (new customizable properties etc.) N/A

Release

[x] Merge this PR.
[x] Make sure all CI builds are green.
[x] Tag and create a release against main (careful, GH defaults to develop!) & copy & paste the changelog to it.
:pencil2: Check if anything from the link collection at the bottom of the changelog needs to be copied in!
[x] Make sure all CI builds are green.
[x] Close the milestone.
[x] Open a new milestone for the next release.
[x] If any open PRs/issues which were milestoned for this release did not make it into the release, update their milestone.
[x] Fast-forward develop to be equal to main.

After release

[x] Open a Trac ticket for WordPress Core to update. - N/A

Publicize

[x] [Major releases only] Publish post about the release on Make WordPress. N/A
[x] Tweet, toot, etc about the release.
[x] Post about it in Slack.
[x] Submit for "Month in WordPress".
[x] Submit for the "Monthy Dev Roundup".

Release toot: https://phpc.social/@made_by_denis/111062294819051767
Release tweet: https://twitter.com/made_by_denis/status/1702221382346490235


[Search] API updates for upcoming search release

Library name
Azure.Search.Documents
Please describe the feature.
For upcoming search release, consider the following API changes:

[x] Implement vector search and semantic search updates as per https://github.com/Azure/azure-rest-api-specs/pull/23779
[x] Update readme and add samples for Vector Search
[x]  Update the readme to include information about AAD authentication
[x] [Swagger] [Ref] We should probably rename Dimensions to something like VectorSearchDimensions to align it next to VectorSearchConfiguration in intellisense and docs.
[x] [Swagger] [Ref]  We probably need to add "format": "arm-id" for AuthResourceId in the swagger so this generates as a Azure.Core.ResourceIdentifier.
[x] [Swagger] [Ref] We should probably make SearchQueryVector.Fields look more like SearchOptions.Select by changing to an array in swagger with a "format": "csv" or whatever's appropriate.
[x] [Ref] We should give SearchQueryVector.K (Number of nearest neighbors to return as top hits) a better name. We understand that we want the HNSW params be oriented to data scientists defining/tuning the index, but it'd help the folks actually making the searches to pick something more descriptive.

[x] KNearestNeighborsCount
[ ] NearestNeighborsCount
[ ] KNeighbors

- [ ] [Swagger] [Ref]  We should probably change Input to Options for QueryResultDocumentRerankerInput. -  This is the input to the reranker and not options so it should be kept as “Input”

[x] [Swagger] [Ref] We should work on simplifying some of these type names if we can.

[x] SemanticFieldState

[x] [SDK] Update the code in SearchResult to add SearchResult.DocumentDebugInfo property because we've customized the serialization for custom user schemas.
[x] Define VectorSearchAlgorithmConfiguration as the polymorphic base type that is derived by HnswVectorSearchAlgorithmConfiguration, ensuring that there won't be a breaking change when new algorithm configurations are added.

[x] Swagger changes - https://github.com/Azure/azure-rest-api-specs/commit/0cfd102a6ecb172f04ec915732bd8ca6f6b2a7af

[x] Bug - When passing QueryCaptionsType.None in semantic search, it gets serialized down to none|highlight-false/none|highlight-true, which is an invalid response to the service. none does not accept any highlight parameters - https://github.com/Azure/azure-sdk-for-net/issues/37164

.NET Search package 11.5.0-beta.3 has been released -<EMAIL_ADDRESS>


SyntaxError: Cannot use import statement outside a module

Getting this error with version 0.0.10, didn't have any error before on 0.0.7, not sure what changed?
node_modules/@vectopus/atlas-icons-react/index.js:1
import _extends from '@babel/runtime/helpers/extends';
^^^^^^

SyntaxError: Cannot use import statement outside a module

Found a solution:
you need to add
transpilePackages: ["@vectopus/atlas-icons-react"],
to nextConfig in next.config.js


Refreshing slots cache infinite loop issue

Environment

ElastiCache (Redis 7.0.7)
Shard count: 3
Node Per Shard Count: 2 (1 Master and 1 Replica)
ioredis v5.2.4

Symptoms
When I call any command through the ioredis library, it throws a MOVED error, performs a refreshing slot cache, and succeeds in getting the correct cluster slot information. However, in the reset part, it is not reset correctly, causing a loop in the refreshing slot cache operation.
If the loop continues like that and exceeds the maximum number of times specified in the options, it will exit with a 'Too Many Redirections' error.
Redis Cluster Setup
this._client = new Redis.Cluster([{
  host,
  port
}], {
  scaleReads: 'slave',
  maxRedirections: envManager.atcsRedisClusterMaxRedirections,
  retryDelayOnMoved: 1000,
  redisOptions: {
    username: user,
    password,
    tls: isLocalEnv ? undefined : {
      host,
      port,
      rejectUnauthorized: false
    }
  }
})

ioredis debug log
2023-06-08T06:44:18.333Z ioredis:delayqueue send 1 commands in moved queue
2023-06-08T06:44:18.333Z ioredis:cluster command mget is moved to <redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379
2023-06-08T06:44:18.334Z ioredis:redis write command[<IP_ADDRESS>:6379]: 0 -> mget([ '<redacted>:{9998:default:2}:max_rps', '<redacted>:{9998:default:2}:current_request_count' ])
2023-06-08T06:44:18.334Z ioredis:cluster refreshing slot caches... (triggered by MOVED error)
2023-06-08T06:44:18.334Z ioredis:cluster getting slot cache from <redacted>-0003-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379
2023-06-08T06:44:18.334Z ioredis:redis status[<redacted>-0003-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379 (ioredis-cluster(refresher))]: wait -> wait
2023-06-08T06:44:18.334Z ioredis:redis status[<redacted>-0003-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379 (ioredis-cluster(refresher))]: wait -> connecting
2023-06-08T06:44:18.334Z ioredis:redis queue command[<redacted>-0003-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379 (ioredis-cluster(refresher))]: 0 -> cluster([ 'SLOTS' ])
2023-06-08T06:44:18.344Z ioredis:redis status[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: connecting -> connect
2023-06-08T06:44:18.344Z ioredis:redis write command[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: 0 -> auth([ 'default', 'redispw' ])
2023-06-08T06:44:18.344Z ioredis:redis status[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: connect -> ready
2023-06-08T06:44:18.345Z ioredis:connection set the connection name [ioredis-cluster(refresher)]
2023-06-08T06:44:18.345Z ioredis:redis write command[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: 0 -> client([ 'setname', 'ioredis-cluster(refresher)' ])
2023-06-08T06:44:18.345Z ioredis:connection set the connection to readonly mode
2023-06-08T06:44:18.345Z ioredis:redis write command[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: 0 -> readonly([])
2023-06-08T06:44:18.345Z ioredis:connection send 1 commands in offline queue
2023-06-08T06:44:18.345Z ioredis:redis write command[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: 0 -> cluster([ 'SLOTS' ])
2023-06-08T06:44:18.346Z ioredis:cluster cluster slots result count: 7
2023-06-08T06:44:18.346Z ioredis:cluster cluster slots result [0]: slots 0~545 served by [
  '<redacted>-0001-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0001-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:18.346Z ioredis:cluster cluster slots result [1]: slots 546~3275 served by [
  '<redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0003-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:18.347Z ioredis:cluster cluster slots result [2]: slots 3276~5110 served by [
  '<redacted>-0001-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0001-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:18.347Z ioredis:cluster cluster slots result [3]: slots 5111~8726 served by [
  '<redacted>-0002-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0002-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:18.347Z ioredis:cluster cluster slots result [4]: slots 8727~11457 served by [
  '<redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0003-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:18.347Z ioredis:cluster cluster slots result [5]: slots 11458~13302 served by [
  '<redacted>-0002-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0002-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:18.347Z ioredis:cluster cluster slots result [6]: slots 13303~16383 served by [
  '<redacted>-0001-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0001-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:18.371Z ioredis:cluster:connectionPool Reset with '[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object  ... <REDACTED full-length="223">'
2023-06-08T06:44:18.373Z ioredis:redis status[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: ready -> close
2023-06-08T06:44:18.373Z ioredis:connection skip reconnecting since the connection is manually closed.
2023-06-08T06:44:18.373Z ioredis:redis status[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: close -> end
2023-06-08T06:44:19.336Z ioredis:delayqueue send 1 commands in moved queue
2023-06-08T06:44:19.336Z ioredis:cluster command mget is moved to <redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379
2023-06-08T06:44:19.336Z ioredis:redis write command[<IP_ADDRESS>:6379]: 0 -> mget([ '<redacted>:{9998:default:2}:max_rps', '<redacted>:{9998:default:2}:current_request_count' ])
2023-06-08T06:44:19.337Z ioredis:cluster refreshing slot caches... (triggered by MOVED error)
2023-06-08T06:44:19.337Z ioredis:cluster getting slot cache from <redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379
2023-06-08T06:44:19.337Z ioredis:redis status[<redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379 (ioredis-cluster(refresher))]: wait -> wait
2023-06-08T06:44:19.337Z ioredis:redis status[<redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379 (ioredis-cluster(refresher))]: wait -> connecting
2023-06-08T06:44:19.337Z ioredis:redis queue command[<redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379 (ioredis-cluster(refresher))]: 0 -> cluster([ 'SLOTS' ])
2023-06-08T06:44:19.348Z ioredis:redis status[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: connecting -> connect
2023-06-08T06:44:19.348Z ioredis:redis write command[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: 0 -> auth([ 'default', 'redispw' ])
2023-06-08T06:44:19.348Z ioredis:redis status[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: connect -> ready
2023-06-08T06:44:19.348Z ioredis:connection set the connection name [ioredis-cluster(refresher)]
2023-06-08T06:44:19.348Z ioredis:redis write command[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: 0 -> client([ 'setname', 'ioredis-cluster(refresher)' ])
2023-06-08T06:44:19.348Z ioredis:connection send 1 commands in offline queue
2023-06-08T06:44:19.348Z ioredis:redis write command[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: 0 -> cluster([ 'SLOTS' ])
2023-06-08T06:44:19.350Z ioredis:cluster cluster slots result count: 7
2023-06-08T06:44:19.350Z ioredis:cluster cluster slots result [0]: slots 0~545 served by [
  '<redacted>-0001-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0001-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:19.350Z ioredis:cluster cluster slots result [1]: slots 546~3275 served by [
  '<redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0003-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:19.350Z ioredis:cluster cluster slots result [2]: slots 3276~5110 served by [
  '<redacted>-0001-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0001-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:19.350Z ioredis:cluster cluster slots result [3]: slots 5111~8726 served by [
  '<redacted>-0002-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0002-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:19.350Z ioredis:cluster cluster slots result [4]: slots 8727~11457 served by [
  '<redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0003-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:19.350Z ioredis:cluster cluster slots result [5]: slots 11458~13302 served by [
  '<redacted>-0002-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0002-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:19.351Z ioredis:cluster cluster slots result [6]: slots 13303~16383 served by [
  '<redacted>-0001-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0001-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:19.370Z ioredis:cluster:connectionPool Reset with '[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object  ... <REDACTED full-length="223">'
2023-06-08T06:44:19.371Z ioredis:redis status[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: ready -> close
2023-06-08T06:44:19.371Z ioredis:connection skip reconnecting since the connection is manually closed.
2023-06-08T06:44:19.371Z ioredis:redis status[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: close -> end
2023-06-08T06:44:20.338Z ioredis:delayqueue send 1 commands in moved queue
2023-06-08T06:44:20.338Z ioredis:cluster command mget is moved to <redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379
2023-06-08T06:44:20.338Z ioredis:redis write command[<IP_ADDRESS>:6379]: 0 -> mget([ '<redacted>:{9998:default:2}:max_rps', '<redacted>:{9998:default:2}:current_request_count' ])
2023-06-08T06:44:20.339Z ioredis:cluster refreshing slot caches... (triggered by MOVED error)
2023-06-08T06:44:20.339Z ioredis:cluster getting slot cache from <redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379
2023-06-08T06:44:20.339Z ioredis:redis status[<redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379 (ioredis-cluster(refresher))]: wait -> wait
2023-06-08T06:44:20.339Z ioredis:redis status[<redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379 (ioredis-cluster(refresher))]: wait -> connecting
2023-06-08T06:44:20.339Z ioredis:redis queue command[<redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379 (ioredis-cluster(refresher))]: 0 -> cluster([ 'SLOTS' ])
2023-06-08T06:44:20.350Z ioredis:redis status[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: connecting -> connect
2023-06-08T06:44:20.350Z ioredis:redis write command[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: 0 -> auth([ 'default', 'redispw' ])
2023-06-08T06:44:20.350Z ioredis:redis status[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: connect -> ready
2023-06-08T06:44:20.350Z ioredis:connection set the connection name [ioredis-cluster(refresher)]
2023-06-08T06:44:20.350Z ioredis:redis write command[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: 0 -> client([ 'setname', 'ioredis-cluster(refresher)' ])
2023-06-08T06:44:20.350Z ioredis:connection send 1 commands in offline queue
2023-06-08T06:44:20.351Z ioredis:redis write command[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: 0 -> cluster([ 'SLOTS' ])
2023-06-08T06:44:20.354Z ioredis:cluster cluster slots result count: 7
2023-06-08T06:44:20.354Z ioredis:cluster cluster slots result [0]: slots 0~545 served by [
  '<redacted>-0001-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0001-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:20.355Z ioredis:cluster cluster slots result [1]: slots 546~3275 served by [
  '<redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0003-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:20.355Z ioredis:cluster cluster slots result [2]: slots 3276~5110 served by [
  '<redacted>-0001-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0001-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:20.355Z ioredis:cluster cluster slots result [3]: slots 5111~8726 served by [
  '<redacted>-0002-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0002-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:20.355Z ioredis:cluster cluster slots result [4]: slots 8727~11457 served by [
  '<redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0003-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:20.355Z ioredis:cluster cluster slots result [5]: slots 11458~13302 served by [
  '<redacted>-0002-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0002-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:20.355Z ioredis:cluster cluster slots result [6]: slots 13303~16383 served by [
  '<redacted>-0001-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0001-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:20.375Z ioredis:cluster:connectionPool Reset with '[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object  ... <REDACTED full-length="223">'
2023-06-08T06:44:20.376Z ioredis:redis status[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: ready -> close
2023-06-08T06:44:20.376Z ioredis:connection skip reconnecting since the connection is manually closed.
2023-06-08T06:44:20.376Z ioredis:redis status[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: close -> end
2023-06-08T06:44:21.340Z ioredis:delayqueue send 1 commands in moved queue
2023-06-08T06:44:21.341Z ioredis:cluster command mget is moved to <redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379
2023-06-08T06:44:21.341Z ioredis:redis write command[<IP_ADDRESS>:6379]: 0 -> mget([ '<redacted>:{9998:default:2}:max_rps', '<redacted>:{9998:default:2}:current_request_count' ])
2023-06-08T06:44:21.341Z ioredis:cluster refreshing slot caches... (triggered by MOVED error)
2023-06-08T06:44:21.341Z ioredis:cluster getting slot cache from <redacted>-0001-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379
2023-06-08T06:44:21.341Z ioredis:redis status[<redacted>-0001-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379 (ioredis-cluster(refresher))]: wait -> wait
2023-06-08T06:44:21.341Z ioredis:redis status[<redacted>-0001-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379 (ioredis-cluster(refresher))]: wait -> connecting
2023-06-08T06:44:21.341Z ioredis:redis queue command[<redacted>-0001-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379 (ioredis-cluster(refresher))]: 0 -> cluster([ 'SLOTS' ])
2023-06-08T06:44:21.359Z ioredis:redis status[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: connecting -> connect
2023-06-08T06:44:21.359Z ioredis:redis write command[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: 0 -> auth([ 'default', 'redispw' ])
2023-06-08T06:44:21.359Z ioredis:redis status[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: connect -> ready
2023-06-08T06:44:21.359Z ioredis:connection set the connection name [ioredis-cluster(refresher)]
2023-06-08T06:44:21.360Z ioredis:redis write command[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: 0 -> client([ 'setname', 'ioredis-cluster(refresher)' ])
2023-06-08T06:44:21.360Z ioredis:connection set the connection to readonly mode
2023-06-08T06:44:21.360Z ioredis:redis write command[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: 0 -> readonly([])
2023-06-08T06:44:21.360Z ioredis:connection send 1 commands in offline queue
2023-06-08T06:44:21.360Z ioredis:redis write command[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: 0 -> cluster([ 'SLOTS' ])
2023-06-08T06:44:21.364Z ioredis:cluster cluster slots result count: 7
2023-06-08T06:44:21.364Z ioredis:cluster cluster slots result [0]: slots 0~545 served by [
  '<redacted>-0001-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0001-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:21.364Z ioredis:cluster cluster slots result [1]: slots 546~3275 served by [
  '<redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0003-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:21.365Z ioredis:cluster cluster slots result [2]: slots 3276~5110 served by [
  '<redacted>-0001-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0001-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:21.365Z ioredis:cluster cluster slots result [3]: slots 5111~8726 served by [
  '<redacted>-0002-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0002-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:21.367Z ioredis:cluster cluster slots result [4]: slots 8727~11457 served by [
  '<redacted>-0003-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0003-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:21.367Z ioredis:cluster cluster slots result [5]: slots 11458~13302 served by [
  '<redacted>-0002-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0002-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:21.367Z ioredis:cluster cluster slots result [6]: slots 13303~16383 served by [
  '<redacted>-0001-001.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379',
  '<redacted>-0001-002.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379'
]
2023-06-08T06:44:21.390Z ioredis:cluster:connectionPool Reset with '[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object  ... <REDACTED full-length="223">'
2023-06-08T06:44:21.392Z ioredis:redis status[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: ready -> close
2023-06-08T06:44:21.392Z ioredis:connection skip reconnecting since the connection is manually closed.
2023-06-08T06:44:21.392Z ioredis:redis status[<IP_ADDRESS>:6379 (ioredis-cluster(refresher))]: close -> end
...loop

Is anyone else experiencing similar symptoms to me?

If you change the host value in lib/cluster/index.ts on line 863 to get the IP value first if there is an IP value, the above infinite loop problem will be solved.
for (let i = 0; i < result.length; ++i) {
  const items = result[i];
  const slotRangeStart = items[0];
  const slotRangeEnd = items[1];

  const keys = [];
  for (let j = 2; j < items.length; j++) {
    if (!items[j][0]) {
      continue;
    }
    const node = this.natMapper({
      host: items[j][3]?.[1] as string ?? items[j][0],
      port: items[j][1],
    });
    node.readOnly = j !== 2;
    nodes.push(node);
    keys.push(node.host + ":" + node.port);
  }

I think the above infinite loop problem would be solved by prioritizing the host value in lib/cluster/index.ts line 863 to get the IP value first if it has an IP value.
clustercfg.<redacted>.uusa8q.apn2.cache.amazonaws.com:6379> cluster slots
1) 1) (integer) 0
   2) (integer) 8191
   3) 1) "<redacted>-0001-001.dev-nxcmd-atcs-apn2.uusa8q.apn2.cache.amazonaws.com"
      2) (integer) 6379
      3) "912f0c3b7373a15a81b06cfc0c67bcd82b4c96cc"
      4) 1) "ip"
         2) "<IP_ADDRESS>"
   4) 1) "<redacted>-0001-002.dev-nxcmd-atcs-apn2.uusa8q.apn2.cache.amazonaws.com"
      2) (integer) 6379
      3) "285c7f723d4c530e8da544453243581bd7e4603e"
      4) 1) "ip"
         2) "<IP_ADDRESS>"
2) 1) (integer) 8192
   2) (integer) 16383
   3) 1) "<redacted>-0002-001.dev-nxcmd-atcs-apn2.uusa8q.apn2.cache.amazonaws.com"
      2) (integer) 6379
      3) "7b5d4f6e3dfe986eab9acadec48097c82c8c4fc8"
      4) 1) "ip"
         2) "<IP_ADDRESS>"
   4) 1) "<redacted>-0002-002.dev-nxcmd-atcs-apn2.uusa8q.apn2.cache.amazonaws.com"
      2) (integer) 6379
      3) "2b6ab8b3e821d14c951c0b055ae6572cab3990fd"
      4) 1) "ip"
         2) "<IP_ADDRESS>"

Removing host and port from the tls attribute in the cluster constructor options eliminated the reset infinite loop issue. We need to find the cause of this symptom.
this._client = new Redis.Cluster([{
  host,
  port
}], {
  scaleReads: 'slave',
  maxRedirections: envManager.atcsRedisClusterMaxRedirections,
  retryDelayOnMoved: 100,
  redisOptions: {
    username: user,
    password,
    tls: isLocalEnv ? undefined : {
      rejectUnauthorized: false
    }
  }
})

Not sure if I have the same issue, but
I'm using aws redis cluster. For me this works:
const redis = new Redis.Cluster(
  ['rediss://username:password@clustercfg.redis.memorydb.region.amazonaws.com:6379'],
  {
    dnsLookup: (address, callback) => callback(null, address),
    redisOptions: {
      commandTimeout: 1000,
      password: 'password',
      username: 'username',
      tls: {},
    }
  }
)

Any other option like no username/password in redisOptions, or no redisOptions, causes infinitely awaited commands (e.g. await redis.get('some')). commandTimeout is ignored.
Maybe it's because of using url + opts, anyway this is frustrating.


Add SMTP server health check

It would be useful to have a library of commonly used health checks. In the scope of this issue, a health check should be implemented that checks if a mail server (SMTP) is alive and can be used to send emails, e.g. by using Golangs  https://pkg.go.dev/net/smtp package.
A few constraints to keep things clean and simple:

The check should be added to the checks module that you can find in the development branch.
As with all health check functions of this library, the check implementation should support accepting and forwarding context.Context that is being passed to each health check function.
If the health check requires external external modules or other dependencies, the check should be implemented as a separate Go module(similarly how it is done for the tests, that require dependencies to other packages as well). This is required to avoid that when people import the base library, they also need to import all dependencies of all provided checks.
The check should have a README.md in its root directory that describes how to use it and maybe what to look out for.
You should provide a test that checks at least the happy path. If a docker container is required to properly test the check, the docker container can be added to the docker-compose.yaml file in the checks base package.

Very nice. Sure!

Resolved with #54


Add ONE_DIR Documentation

Right now (if I'm not mistaken) ONE_DIR is only "documented" in the Dockerfile. It's missing from the README.me.

You're right. I'll try to do it.


Wings stop working after some playtime with them

I was playing like usual and suddenly after dying by an archer the wings stopped working. I have them on my back but I cannot glide. I also even try to remove my wings and craft them again but I cannot use them neither

This is a FallFlyingLib bug, which (hopefully) be superseded by an official Fabric API module: https://github.com/FabricMC/fabric/pull/1815
Once the module is merged, I'll work on a version that uses the Fabric API module and this will (hopefully²) be fixed.


Easy way to exclude

I was just wondering, since I saw the not_exact filter type for choicefields, is there a similar way to do this for other fields (integer, char, etc)? When I apply the not_exact filter type for any of those I get:
FieldError at /api/deals/
Unsupported lookup 'not_exact' for CharField or join on the field not permitted.

I know i can make a custom field with an exclude, but I like the way of the not_exact filter type better.

Please direct usage questions to Stack Overflow Thanks.


test-branch/execute-job/quoted-authorization/4c079f06-9993-4fe8-83bd-b5fa7b23ff29

PR for testing ba41173db31da7c9a5e30dfe8a6a7c9db787cdb2

/canonical/self-hosted-runners/run-workflows ba41173db31da7c9a5e30dfe8a6a7c9db787cdb2


AMBARI-23158. Fix NPE in Host Components query.

What changes were proposed in this pull request?
Fixed NPE happening in HostComponentResourceProvider.
How was this patch tested?
Compiled.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1006/
Test FAILed.
Test FAILured.


Getting crashes when using alongside mod Universal Graves

Hello, I'm new to posting so I hope I'm doing this correctly, apologies ahead of time.
I recently started a modded Minecraft server and after about a week or two of running it, I had decided to place an Anti-Xray, coming across yours. I have been using the mod Universal Graves since almost the beginning so I haven't ran into this issue yet. I'm also no expert so I hope I am seeing this right and it's these two that are causing issues.
I've noticed that when a player dies and their grave spawns, that chunk that they died in becomes almost unplayable. All players are affected in that chunk and will be timed out indefinitely until the grave is broken or destroys on its own. Now this sounds like a Universal Graves mod problem but I have yet to have this kind of issues with it until I added the Anti X-Ray today. It's been crashing my server non stop it seems like when players die and I'm getting this crash message every time it happens, pointing to Anti X-Ray and Universal Graves.
Here is the crash report:
---- Minecraft Crash Report ----
// I blame Dinnerbone.

Time: 11/22/21, 5:44 AM
Description: Ticking block entity

java.lang.ArrayIndexOutOfBoundsException: Index 33554438 out of bounds for length 81223
	at me.drex.antixray.util.ChunkPacketBlockControllerAntiXray.onBlockChange(ChunkPacketBlockControllerAntiXray.java:545)
	at net.minecraft.class_1937.redirect$zzd000$onBlockChanged(class_1937.java:1101)
	at net.minecraft.class_1937.method_30092(class_1937.java:211)
	at net.minecraft.class_1937.method_8652(class_1937.java:196)
	at net.minecraft.class_1937.method_8501(class_1937.java:311)
	at eu.pb4.graves.grave.GraveBlockEntity.tick(GraveBlockEntity.java:193)
	at net.minecraft.class_2818$class_5563.method_31703(class_2818.java:886)
	at net.minecraft.class_2818$class_5564.method_31703(class_2818.java:941)
	at net.minecraft.class_1937.method_18471(class_1937.java:474)
	at net.minecraft.class_3218.method_18765(class_3218.java:422)
	at net.minecraft.server.MinecraftServer.method_3813(MinecraftServer.java:891)
	at net.minecraft.class_3176.method_3813(class_3176.java:335)
	at net.minecraft.server.MinecraftServer.method_3748(MinecraftServer.java:831)
	at net.minecraft.server.MinecraftServer.method_29741(MinecraftServer.java:697)
	at net.minecraft.server.MinecraftServer.method_29739(MinecraftServer.java:270)
	at java.base/java.lang.Thread.run(Thread.java:831)

A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Thread: Server thread
Stacktrace:
	at me.drex.antixray.util.ChunkPacketBlockControllerAntiXray.onBlockChange(ChunkPacketBlockControllerAntiXray.java:545)
	at net.minecraft.class_1937.redirect$zzd000$onBlockChanged(class_1937.java:1101)
	at net.minecraft.class_1937.method_30092(class_1937.java:211)
	at net.minecraft.class_1937.method_8652(class_1937.java:196)
	at net.minecraft.class_1937.method_8501(class_1937.java:311)
	at eu.pb4.graves.grave.GraveBlockEntity.tick(GraveBlockEntity.java:193)

-- Block entity being ticked --
Details:
	Name: universal_graves:grave // eu.pb4.graves.grave.GraveBlockEntity
	Block: Block{universal_graves:grave}[is_locked=false,rotation=7]
	Block location: World: (735,78,655), Section: (at 15,14,15 in 45,4,40; chunk contains blocks 720,-64,640 to 735,319,655), Region: (1,1; contains chunks 32,32 to 63,63, blocks 512,-64,512 to 1023,319,1023)
	Block: Block{universal_graves:grave}[is_locked=false,rotation=7]
	Block location: World: (735,78,655), Section: (at 15,14,15 in 45,4,40; chunk contains blocks 720,-64,640 to 735,319,655), Region: (1,1; contains chunks 32,32 to 63,63, blocks 512,-64,512 to 1023,319,1023)
Stacktrace:
	at net.minecraft.class_2818$class_5563.method_31703(class_2818.java:886)
	at net.minecraft.class_2818$class_5564.method_31703(class_2818.java:941)
	at net.minecraft.class_1937.method_18471(class_1937.java:474)
	at net.minecraft.class_3218.method_18765(class_3218.java:422)

-- Affected level --
Details:
	All players: 3 total; [class_3222['Zeromega89'/374, l='ServerLevel[world]', x=-167.12, y=63.00, z=-663.82], class_3222['JayXReaper'/846, l='ServerLevel[world]', x=-596.91, y=60.00, z=-755.03], class_3222['KiddTheJuice'/3331, l='ServerLevel[world]', x=706.26, y=78.23, z=643.90]]
	Chunk stats: 5822
	Level dimension: minecraft:overworld
	Level spawn location: World: (-595,65,160), Section: (at 13,1,0 in -38,4,10; chunk contains blocks -608,-64,160 to -593,319,175), Region: (-2,0; contains chunks -64,0 to -33,31, blocks -1024,-64,0 to -513,319,511)
	Level time: 18450380 game time, 25452427 day time
	Level name: world
	Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
	Level weather: Rain time: 10803 (now: false), thunder time: 133714 (now: false)
	Known server brands: fabric
	Level was modded: true
	Level storage version: 0x04ABD - Anvil
Stacktrace:
	at net.minecraft.server.MinecraftServer.method_3813(MinecraftServer.java:891)
	at net.minecraft.class_3176.method_3813(class_3176.java:335)
	at net.minecraft.server.MinecraftServer.method_3748(MinecraftServer.java:831)
	at net.minecraft.server.MinecraftServer.method_29741(MinecraftServer.java:697)
	at net.minecraft.server.MinecraftServer.method_29739(MinecraftServer.java:270)
	at java.base/java.lang.Thread.run(Thread.java:831)

-- System Details --
Details:
	Minecraft Version: 1.17.1
	Minecraft Version ID: 1.17.1
	Operating System: Linux (amd64) version 4.4.232-1.el7.elrepo.x86_64
	Java Version: 16.0.1, AdoptOpenJDK
	Java VM Version: OpenJDK 64-Bit Server VM (mixed mode, sharing), AdoptOpenJDK
	Memory:<PHONE_NUMBER> bytes (2365 MiB) /<PHONE_NUMBER> bytes (7200 MiB) up to<PHONE_NUMBER>4 bytes (15704 MiB)
	CPUs: 5
	Processor Vendor: GenuineIntel
	Processor Name: Intel(R) Xeon(R) E-2288G CPU @ 3.70GHz
	Identifier: Intel64 Family 6 Model 158 Stepping 13
	Microarchitecture: unknown
	Frequency (GHz): 3.70
	Number of physical packages: 1
	Number of physical CPUs: 8
	Number of logical CPUs: 16
	Graphics card #0 name: unknown
	Graphics card #0 vendor: unknown
	Graphics card #0 VRAM (MB): 0.00
	Graphics card #0 deviceId: unknown
	Graphics card #0 versionInfo: unknown
	Virtual memory max (MB): 163664.72
	Virtual memory used (MB): 118491.75
	Swap memory total (MB): 99325.98
	Swap memory used (MB): 24344.47
	JVM Flags: 2 total; -Xmx15700M -Xms128M
	Fabric Mods:
		amecsapi: Amecs API 1.1.5+mc21w16a
		antixray: AntiXray 1.1.0
		appleskin: AppleSkin mc1.17.1-2.2.0
		architectury: Architectury 2.6.35
		attributefix: Attribute Fix {FABRIC} 1.0.3
		backslot: BackSlot 1.2.2
		backslotaddon: BackSlot Addon 1.0.7
		balm-fabric: Balm 1.8.0+0
		bannerpp: Banner++ 2.0.3+mc.1.17-rc1
		bclib: BCLib 0.5.2
		bedbenefitsfabric: Bed Benefits 1.17.1-0.1.1
		betterend: Better End 0.12.3
		bettermineshafts: YUNG's Better Mineshafts 1.17-1.0.1
		betternether: Better Nether 5.1.3
		blue_endless_jankson: jankson 1.2.1
		boatcontainer: BoatContainer 1.0.3
		bountiful: Bountiful 1.0.0
		caelus: Caelus API 0.0.16-1.17
		cardinal-components-base: Cardinal Components API (base) 3.1.1
		cardinal-components-entity: Cardinal Components API (entities) 3.1.1
		chat_plus: Chat+ 2.1.5
		cloth-basic-math: cloth-basic-math 0.6.0
		cloth-config2: Cloth Config v5 5.1.40
		clumps: Clumps 7.0.10
		collective-fabric: Collective (Fabric) 1.64
		com_moandjiezana_toml_toml4j: toml4j 0.7.2
		comforts: Comforts 0.0.7-1.17.1
		copperarmorandtools: Copper Armor & Tools 1.4.5
		croptopia: Croptopia 1.6.3
		dripstone_fluid_lib: Dripstone Fluid Lib 1.0.0
		dual_riders: DualRiders 1.0.5
		dummmmmmy: MmmMmmMmmMmm 1.17-1.4.1
		dungeons_arise: When Dungeons Arise 2.1.47-fabric
		elytratrinket: Elytra Trinket 2.0.1-1.17
		enchant_giver: Enchant Giver 1.1.0
		enchantmentdescriptions: Enchantment Descriptions 4.0.1
		endrem: End Remastered 4.1.0
		entitybanners: Entity Banners 1.0.2-BETA+1.17
		fabric: Fabric API 0.42.1+1.17
		fabric-api-base: Fabric API Base 0.4.0+5847535018
		fabric-api-lookup-api-v1: Fabric API Lookup API (v1) 1.3.1+5847535018
		fabric-biome-api-v1: Fabric Biome API (v1) 3.2.2+5847535018
		fabric-command-api-v1: Fabric Command API (v1) 1.1.4+5847535018
		fabric-commands-v0: Fabric Commands (v0) 0.2.3+5847535018
		fabric-containers-v0: Fabric Containers (v0) 0.1.13+5847535018
		fabric-content-registries-v0: Fabric Content Registries (v0) 0.3.1+5847535018
		fabric-crash-report-info-v1: Fabric Crash Report Info (v1) 0.1.6+5847535018
		fabric-dimensions-v1: Fabric Dimensions API (v1) 2.0.13+5847535018
		fabric-entity-events-v1: Fabric Entity Events (v1) 1.3.1+5847535018
		fabric-events-interaction-v0: Fabric Events Interaction (v0) 0.4.11+5847535018
		fabric-events-lifecycle-v0: Fabric Events Lifecycle (v0) 0.2.2+5847535018
		fabric-game-rule-api-v1: Fabric Game Rule API (v1) 1.0.8+5847535018
		fabric-item-api-v1: Fabric Item API (v1) 1.2.5+5847535018
		fabric-item-groups-v0: Fabric Item Groups (v0) 0.3.1+5847535018
		fabric-language-kotlin: Fabric Language Kotlin 1.6.5+kotlin.1.5.31
		fabric-lifecycle-events-v1: Fabric Lifecycle Events (v1) 1.4.5+5847535018
		fabric-loot-tables-v1: Fabric Loot Tables (v1) 1.0.5+5847535018
		fabric-mining-level-api-v1: Fabric Mining Level API (v1) 1.0.2+6d0fac4218
		fabric-mining-levels-v0: Fabric Mining Levels (v0) 0.1.5+6d0fac4218
		fabric-networking-api-v1: Fabric Networking API (v1) 1.0.14+5847535018
		fabric-networking-blockentity-v0: Fabric Networking Block Entity (v0) 0.2.12+5847535018
		fabric-networking-v0: Fabric Networking (v0) 0.3.3+5847535018
		fabric-object-builder-api-v1: Fabric Object Builder API (v1) 1.10.11+6d0fac4218
		fabric-object-builders-v0: Fabric Object Builders (v0) 0.7.5+6d0fac4218
		fabric-particles-v1: Fabric Particles (v1) 0.2.5+5847535018
		fabric-permissions-api-v0: fabric-permissions-api 0.1-SNAPSHOT
		fabric-registry-sync-v0: Fabric Registry Sync (v0) 0.7.13+5847535018
		fabric-rendering-data-attachment-v1: Fabric Rendering Data Attachment (v1) 0.1.6+5847535018
		fabric-rendering-fluids-v1: Fabric Rendering Fluids (v1) 0.2.1+6d0fac4218
		fabric-resource-loader-v0: Fabric Resource Loader (v0) 0.4.9+5847535018
		fabric-screen-handler-api-v1: Fabric Screen Handler API (v1) 1.1.9+5847535018
		fabric-structure-api-v1: Fabric Structure API (v1) 1.1.14+5847535018
		fabric-tag-extensions-v0: Fabric Tag Extensions (v0) 1.2.2+5847535018
		fabric-tool-attribute-api-v1: Fabric Tool Attribute API (v1) 1.3.1+eb76084f18
		fabric-transfer-api-v1: Fabric Transfer API (v1) 1.5.1+6d0fac4218
		fabricloader: Fabric Loader 0.12.5
		fiber: fiber 0.23.0-2
		flan: Flan 1.17.1-1.6.2
		flytre-lib-base: Flytre Lib - Base Module 1.3.0
		flytre-lib-compat: Flytre Lib - Compat Module 1.0.0
		flytre-lib-config: Flytre Lib - Config Module 1.1.0
		flytre-lib-event: Flytre Lib - Event Module 1.0.1
		flytre-lib-gui: Flytre Lib - GUI Module 1.0.0
		flytre-lib-storage: Flytre Lib - Storage Module 2.3.2
		flytre_lib: Flytre Lib 1.4.2
		hologram-api: Hologram API 0.2.1+1.17.1
		hookshot: Hookshot 22.0
		iceberg: Iceberg 1.0.23
		interactic: Interactic 0.1.6-1.17
		inventorysorter: Inventory Sorter 1.8.0-1.17
		jankson: Jankson 3.0.1+j1.2.0
		java: OpenJDK 64-Bit Server VM 16
		justplayerheads-fabric: Just Player Heads (Fabric) 1.8
		kambrik: Kambrik 1.1.0
		keeptherain: Keep The Rain! 0.2.0
		kyrptconfig: Kytpt Config 1.1.10-1.17
		levelz: LevelZ 1.0.15
		libgui: LibGui 4.1.6+1.17.1
		libninepatch: LibNinePatch 1.1.0
		lovely_snails: Lovely Snails 1.0.3+1.17
		maybe-data: Maybe data 1.0.1-1.17
		mcda: MC Dungeons Armors 1.7.15
		mcdar: MC Dungeons Artifacts 1.4.2
		mcdw: MC Dungeons Weapons 3.6.0
		milk_plus: Milk+ 1.2.1
		minecraft: Minecraft 1.17.1
		morebannerfeatures: More Banner Features 1.1.1
		morevillagers-fabric: MoreVillagersFabric 2.1.1-SNAPSHOT
		mostructures: Mo' Structures 1.3.0-pre1-1.17.1
		omega-config: OmegaConfig 1.0.8
		org_jetbrains_kotlin_kotlin-reflect: kotlin-reflect 1.5.31
		org_jetbrains_kotlin_kotlin-stdlib: kotlin-stdlib 1.5.31
		org_jetbrains_kotlin_kotlin-stdlib-jdk7: kotlin-stdlib-jdk7 1.5.31
		org_jetbrains_kotlin_kotlin-stdlib-jdk8: kotlin-stdlib-jdk8 1.5.31
		org_jetbrains_kotlinx_kotlinx-coroutines-core-jvm: kotlinx-coroutines-core-jvm 1.5.2
		org_jetbrains_kotlinx_kotlinx-coroutines-jdk8: kotlinx-coroutines-jdk8 1.5.2
		org_jetbrains_kotlinx_kotlinx-serialization-core-jvm: kotlinx-serialization-core-jvm 1.3.0
		org_jetbrains_kotlinx_kotlinx-serialization-json-jvm: kotlinx-serialization-json-jvm 1.3.0
		packet_tweaker: Packet Tweaker 0.2.0+1.17.1
		placeholder-api: Placeholder API 1.1.1+1.17.1
		player-data-api: Player Data API 0.1.0+1.17.1
		polymer: Polymer 0.1.8+1.17.1
		quickspyglasser: Quick Spyglasser 0.3.0
		reach-entity-attributes: Reach Entity Attributes 2.1.1
		repurposed_structures: Repurposed Structures 2.5.7+1.17.1
		rotten: FleshZ 1.4.3
		roughlyenoughitems: Roughly Enough Items 6.2.335
		secondchance: Second Chance 1.2.0
		seedy-behavior: Seedy Behavior 1.0.2+1.17.1
		server_translations_api: Server Translations API 1.4.6+1.17
		sgui: SGui 1.0.0-rc4+1.17.1
		sit: Sit 1.17.1-13
		somnus: Somnus API 0.0.13-1.17.1
		sound_physics_remastered: Sound Physics Remastered 1.17.1-1.0.2
		static-content: Static Content 1.0.1-1.16.2
		staticdata: Static Data 1.1.2
		stoneholm: Stoneholm 1.3
		styled-nicknames: Styled Nicknames 1.0.0
		terralith: Terralith for Fabric 1.6.1
		travelersbackpack: Traveler's Backpack 1.17.1-6.0.0
		treeharvester-fabric: Tree Harvester (Fabric) 4.0
		trinkets: Trinkets 3.0.4
		universal-graves: Universal Graves 1.1.3+1.17.1
		villagernames: Villager Names 2.0.1
		voicechat: Simple Voice Chat 1.17.1-2.1.12
		waystones: Waystones 8.2.0+0
		wolveswitharmor: Wolves With Armor 1.6.1-1.17.1
		worldedit: WorldEdit 7.2.7+9f3e795
		xaerominimap: Xaero's Minimap 21.22.2
		xaeroworldmap: Xaero's World Map <IP_ADDRESS>
		yungsapi: YUNG's API 1.17-Fabric-19
	Player Count: 3 / 100; [class_3222['Zeromega89'/374, l='ServerLevel[world]', x=-167.12, y=63.00, z=-663.82], class_3222['JayXReaper'/846, l='ServerLevel[world]', x=-596.91, y=60.00, z=-755.03], class_3222['KiddTheJuice'/3331, l='ServerLevel[world]', x=706.26, y=78.23, z=643.90]]
	Data Packs: vanilla, Fabric Mods, file/kiddocraft, file/VanillaTweaks_c944383.zip, file/afk display v1.1.0.zip, file/custom nether portals v2.3.2.zip, file/durability ping v1.1.0.zip, file/kill empty boats v1.1.1.zip, file/larger phantoms v1.2.1.zip, file/tag v2.1.0.zip, file/track raw statistics v1.5.0.zip, file/1.16_Datapack_ChainmailArmorCraft (incompatible)
	Is Modded: Definitely; Server brand changed to 'fabric'
	Type: Dedicated Server (map_server.txt)

Hello, Thanks for the detailed issue. I have just uploaded a commit that should fix the described issue.
Before officially releasing this though I would love to hear back from you, wherever this actually fixed your issue.
Please make sure to grab the latest version from Github actions and test your issue.
 I am just now seeing this, I checked your GitHub earlier
but haven't been in my email today.
I actually did some testing with another mod and was able to get things
working on my server with my set up that I have going. I will however try
to test yours out when I get a chance to. At the moment I have things fixed
with the current mod list but I appreciate you looking into the issue. When
I bring my server back down for maintenance, I'll run your mod with it and
test your new fix.
I apologize brother!
On Mon, Nov 22, 2021 at 3:21 PM Drex @.***> wrote:

Hello, Thanks for the detailed issue. I have just uploaded a commit that
should fix the described issue.
Before officially releasing this though I would love to hear back from
you, wherever this actually fixed your issue.
Please make sure to grab the latest version from Github actions
https://github.com/DrexHD/AntiXray/actions/runs/1492166032 and test
your issue.
Kind regards,
Drex
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/DrexHD/AntiXray/issues/11#issuecomment-975929490, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AWTN6X673MQZWKIAR6SGBGDUNKX6JANCNFSM5IQE75TQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Kind Regards,
Matthew Hasley | KiddSisco
Content Creator | Twitch Affiliate
@.***
Twitter: @kiddsiscotv https://twitter.com/KiddSiscoTV
Instagram: @kiddsiscotv https://instagram.com/KiddSiscoTV
Facebook: KiddSisco TV https://www.facebook.com/kiddsiscotv/

DrexHD/AntiXray
Lovely news, just got through testing out the Anti-Xray with my modpack and
it seems to be working great! I am not getting the lag I was previously. I
am about to release this to the public and let the players test it out so
fingers crossed! Thank you again!
On Mon, Nov 22, 2021 at 3:21 PM Drex @.***> wrote:

Hello, Thanks for the detailed issue. I have just uploaded a commit that
should fix the described issue.
Before officially releasing this though I would love to hear back from
you, wherever this actually fixed your issue.
Please make sure to grab the latest version from Github actions
https://github.com/DrexHD/AntiXray/actions/runs/1492166032 and test
your issue.
Kind regards,
Drex
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/DrexHD/AntiXray/issues/11#issuecomment-975929490, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AWTN6X673MQZWKIAR6SGBGDUNKX6JANCNFSM5IQE75TQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Stackoverflow clone

Description
Description of the project here
Code of Conduct

[X] I follow Contributing Guidelines of this project.

/assign


enable enterprise deployment

Apply Kong 2.5 deployment

We should avoid making pre-baked configurations that combine unrelated options--whether or not you use Enterprise or not should not have any impact on which database you use, and you should be able to mix and match those independently, so that you have something like:
builder.WithPostgreSQL()
builder.WithEnterprise(...)

Agree, same as  Shane Utt pointed it out - Enterprise w w/o database (Cassandra or PostgresQL); Non-Enterprise w, w/o database ((Cassandra or PostgresQL)), which is similar as how we apply it in KIC.

to create an Enterprise Postgres instance, rather than defining a new dbmode or making a complete prebuilt "Enterprise with Postgres" mode. Kong has a lot of independent features and it's hard to know which set you'll need for a test case in advance.
I'd also recommend making image selection its own thing (I don't see anything for this currently, so we just always use the default image, which happens to be OSS). Instead of WithEnterprise() selecting a predetermined image, you'd have:
builder.WithImage(repository string, tag string)

That allows you to test with older images and/or custom repo images as well as Enterprise images, and removes the need to update and release a new KTF version every time we want to update a tag.
With the image separated, WithEnterprise() would instead be for setting up Enterprise features; you could make the license an argument as suggested and add other Enterprise features like an RBAC boolean. It may make sense to make those discrete builder functions though--instead of a single WithEnterprise() you have WithLicense(), WithRBAC(), WithWorkspace(), etc. That makes sense for workspace setup in particular, where you may want to set up multiple workspaces, each with their own settings, and calling that function multiple times may be cleaner than providing an array of workspace structs or similar.

Both Shane and Travis have more advanced enterprise integration ideas. 👍  would like to follow up further on.
For release purpose, we want to carry the compatibility between 2.0 KIC and 2.5 Gateway, ensure nothing is broken for the new KIC tag. It is a good idea to pass the test image tag in since image repo is static, generally.

I like the WithImage(image, tag string) idea, and would like to see it in this PR but @rainest if you're open to it I think perhaps we shouldn't consider it a strict blocker for this PR as it seems the immediate requirement is to have something like "the latest version of enterprise" available. Let me know your thoughts?
However, it should be pretty easy to get the best of both worlds, something like:
const (
    defaultEnterpriseImage = "kong/kong-enterprise"
    defaultEnterpriseImageTag = "latest"
)

func (b *Builder) WithEnterprise(license string) *Builder {
    b.enterpriseLicense = license
    return b.WithImage(defaultEnterpriseImage, defaultEnterpriseImageTag)
}

func (b *Builder) WithImage(image, tag string) *Builder {
    b.image = image
    b.tag = tag
    return b
}

So as simple as it is if we can just add that great.

I like the WithImage(image, tag string) idea, and would like to see it in this PR but @rainest if you're open to it I think perhaps we shouldn't consider it a strict blocker for this PR as it seems the immediate requirement is to have something like "the latest version of enterprise" available. Let me know your thoughts?
However, it should be pretty easy to get the best of both worlds, something like:
const (
    defaultEnterpriseImage = "kong/kong-enterprise"
    defaultEnterpriseImageTag = "latest"
)

latest is invalid
(
EnterpriseimageRepo = "kong/kong-enterprise"
EnterpriseimageTag = "<IP_ADDRESS>-alpine"
)

func (b *Builder) WithEnterprise(license string) *Builder {
b.enterpriseLicense = license
return b.WithImage(defaultEnterpriseImage, defaultEnterpriseImageTag)
}
func (b *Builder) WithImage(image, tag string) *Builder {
b.image = image
b.tag = tag
return b
}

So as simple as it is if we can just add that great.

You mean "
"

latest is not accurate

Yes you're right, that was just an example please do change as you see fit :bow:

@ccfishk is this still WIP or are we ready for re-review?

@ccfishk is this still WIP or are we ready for re-review?

Shane, will give an update within 1 hour.

This PR has gotten quite long in the comments, so I'm going to resolve all of my previous comments and try a fresh start, so just consider everything before this comment resolved and everything after the things I would like to see resolved.

This PR has gotten quite long in the comments, so I'm going to resolve all of my previous comments and try a fresh start, so just consider everything before this comment resolved and everything after the things I would like to see resolved.

This PR mainly setup the test bed for KIC enterprise integration tests. Almost all of the comments was resolved , Kindly help to get this merged and unblock further KIC testing. 🙇♀ 🙇♀


image icon doesn't work

Hi, first of all thank you for your job, i think it's very nice.
About my problem:
i don't like use cocoapods so i have imported CdAlertView manually but when i call the alert view the image in the center doesn't work. this is a sample

 CDAlertView icon bug


Update vendor-boringssl to save modulemap

Motivation:
The vendor-boringssl script rewrites include, which leads to deletion of module.modulemap.
Modification:
Save a copy of modulemap to tmp dir and copy it back at the end.
Result:
module.modulemap remains after running the script.

@swift-server-bot test this please


feat: get NodeInfos from the MagicEndpoint

Description
Call MagicEndpoint::node_infos() to get a Vec<NodeInfo>, or list connection information on all nodes we know about.
NodeInfo is aliased from super::magicsock::EndpointInfo.
/// The type of connection we have to the node.
#[derive(Debug, Clone, Eq, PartialEq)]
pub enum ConnectionType {
    /// Direct UDP connection
    Direct(SocketAddr),
    /// Relay connection over DERP
    Relay(u16),
    /// We have no verified connection to this peer
    None,
}

/// Details about an Endpoint
#[derive(Debug, Clone, Eq, PartialEq)]
pub struct EndpointInfo {
    /// The id in the peer_map
    pub id: usize,
    /// The public key of the endpoint.
    pub public_key: PublicKey,
    /// Derp region, if available.
    pub derp_region: Option<u16>,
    /// List of addresses at which this node might be reachable, plus any latency information we
    /// have about that address.
    pub addrs: Vec<(SocketAddr, Option<Duration>)>,
    /// The type of connection we have to the peer, either direct or over relay.
    ///
    /// Depending on the expiry time, we may still have a direct connection to the peer
    /// but our best address for the peer may have timed out.
    /// Until we verify that connection, we assume that we may only have a relay
    /// connection to that peer.
    pub conn_type: ConnectionType,
    /// The latency of the `conn_type`.
    pub latency: Option<Duration>,
}

Notes & open questions
Please let me know if the above EndpointInfo + ConnectionType is enough for our UI and sync purposes!
Change checklist

[ ] Self-review.
[ ] Documentation updates if relevant.
[ ] Tests if relevant.

We've been shifting away from Peer as a term since https://github.com/n0-computer/iroh/pull/137  , what do you think about NodeInfo?

NodeInfo is very confusing to me, I think it should be at least sth like RemoteNodeInfo, otherwise I would assume it is the local node

Out of band discussion, we settled on ConnectionInfo

closing this PR in favor of #1435


fix(versions): update Activiti/activiti-cloud-notifications-graphql versions into master

UpdateBot pushed maven dependency: org.activiti.cloud.notifications.graphql:activiti-cloud-notifications-graphql-dependencies to: 7.1.190

UpdateBot commands:
updatebot push-version --kind maven org.activiti.cloud.notifications.graphql:activiti-cloud-notifications-graphql-dependencies 7.1.190


fix(ci): Skip GCP CI jobs on PRs from external contributors, let mergify test them after approval

Motivation
This is a quick fix for CI failures on PRs from external repositories.
We've asked the ZSA and ZSF teams to submit PRs, so let's make it a good experience for them.
Close #4529.
PR Author Checklist
Check before marking the PR as ready for review:

[x] Will the PR name make sense to users?
[x] Does the PR have a priority label?
[x] Have you added or updated tests?
[x] Is the documentation up to date?

For significant changes:

[ ] Is there a summary in the CHANGELOG?
[ ] Can these changes be split into multiple PRs?

If a checkbox isn't relevant to the PR, mark it as done.
This is a significant change for external developers, but we can add it to the changelog in another PR.
Specifications
GitHub context and the difference between ref and head_ref:
https://docs.github.com/en/actions/learn-github-actions/contexts#github-context
Skipping individual job steps:
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsif
Example PRs and branch names
Internal PR: rate-limit-getaddr #7955
Recent external PR: rex4539/typos #7865
Dependabot: dependabot/github_actions/devops-599883908b #7948
Mergify: mergify/merge-queue/d948c06290 #7954
Complex Code or Requirements
We need to skip external branches in the actual CI jobs, but only run on changed files.
Then we need to run on external branches in the patch jobs, or run on unchanged files. This requires two patch workflow files. (Conditions in the same workflow file are both required, but we want either condition.)
Solution

Skip GCP workflows on external PRs
Add patch workflows for GCP workflows that run dummy jobs on external PRs
Skip optional steps on external PRs because they are failing

Extra changes:

Document some workflows
Add a trivial Rust change so Rust GCP workflows run on this PR
Cleanup some unnecessary workflow conditions and timeouts

Testing
We can check this using this branch, which is from @teor2345's external repository. But it won't be fully tested until we merge it, and get a branch from someone who isn't a ZF GitHub org member.
Review
I'd like to get this merged quickly so external developers have a good experience, and sort out any non-blocking changes later.
Reviewer Checklist
Check before approving the PR:

[x] Does the PR scope match the ticket?
[ ] Are there enough tests to make sure it works? Do the tests cover the PR motivation?
[x] Are all the PR blockers dealt with?
PR blockers can be dealt with in new tickets or PRs.

And check the PR Author checklist is complete.

I just checked after the merge, and we're still running GCP jobs on the main branch. So all we have to check now is another PR from a non-Zebra contributor.

This PR is from an external repository already

That's correct, but it wasn't from an external contributor (which is the trigger for the permission issues). I just didn't want to wait until an external contributor made a contribution to confirm it's working as expected.

This PR is from an external repository already

That's correct, but it wasn't from an external contributor (which is the trigger for the permission issue). I just didn't want to wait until an external contributor made a contribution to confirm it's working as expected.

I think there might have been some miscommunication here. We're expecting multiple PRs from the ZSA and sustainability fund teams over the next few weeks. The first one is #7978, which would have run CI, but it has merge conflicts.


Anomaly Scoring - missing some clarity

Reading your docs here, watching your YouTube covering it https://www.youtube.com/watch?v=NJQAxXMDwT8
But, while you say there is a severity level for rules, there isn't any way to see the severity level of the rules in the interface.
Something seems to be missing.
I even created a new policy using the current policy template and no visibility or control of a rule's severity.
Not sure if there is something missing in the docs to explain how/where to get to the severity, or if a product issue where not showing a value associated with the rule.  No "column chooser" option to show it in the app.
Thanks.

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

ID: b3abaaaa-87a3-f5b6-4265-a5cff6206ed4
Version Independent ID: c93fe969-c631-0d2d-fcb7-c347da3a96d9
Content: What is Azure Web Application Firewall on Azure Application Gateway? - Azure Web Application Firewall
Content Source: articles/web-application-firewall/ag/ag-overview.md
Service: web-application-firewall
GitHub Login: @vhorne
Microsoft Alias: victorh

@JFBDO2022
Thanks for your feedback! We will investigate and update as appropriate.

@JFBDO2022
I'm going to assign this to the document author so they can take a look at it accordingly.
@vhorne
Please review it.

This is by design. The work required to change this situation is currently lower priority.
#please-close

Ok, so perhaps a note that indicates that the visibility of the scores on the rules and such are not available but are intended to be at a future date?
At the moment, it is forcing people on a scavenger hunt for unavailable information.
Thanks.
From: Vic @.>
Sent: Monday, April 8, 2024 3:41 PM
To: MicrosoftDocs/azure-docs @.>
Cc: John Fedor @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Anomaly Scoring - missing some clarity (Issue #121209)
Attention: This email was sent from someone outside of BDO USA. Always use caution when opening attachments or clicking links from unknown senders or when receiving unexpected emails.
This is by design. The work required to change this situation is currently lower priority.
#please-close

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/121209#issuecomment-2043607613, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZAU3OHAMP6AFU4NUVUKRSDY4L6GXAVCNFSM6AAAAABFPFDQKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBTGYYDONRRGM.
You are receiving this because you were mentioned.Message ID: @.***>
BDO Digital, LLC, a Delaware limited liability company, is a wholly-owned subsidiary of BDO USA, P.C. BDO USA, P.C., a Virginia professional service corporation, is the U.S. member of BDO International Limited, a UK company limited by guarantee, and forms part of the international BDO network of independent member firms.
BDO is the brand name for the BDO network and for each of the BDO Member Firms.
IMPORTANT NOTICES
The contents of this email and any attachments to it may contain privileged and confidential information from BDO Digital, LLC. This information is only for the viewing or use of the intended recipient. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of, or the taking of any action in reliance upon, the information contained in this e-mail, or any of the attachments to this e-mail, is strictly prohibited and that this e-mail and all of the attachments to this e-mail, if any, must be immediately returned to BDO Digital, LLC or destroyed and, in either case, this e-mail and all attachments to this e-mail must be immediately deleted from your computer without making any copies hereof. If you have received this e-mail in error, please notify BDO Digital, LLC by e-mail immediately.

Trying again without the hashtag command inline.
From: John Fedor
Sent: Monday, April 8, 2024 3:44 PM
To: MicrosoftDocs/azure-docs @.>; MicrosoftDocs/azure-docs @.>
Cc: Mention @.***>
Subject: RE: [MicrosoftDocs/azure-docs] Anomaly Scoring - missing some clarity (Issue #121209)
Ok, so perhaps a note that indicates that the visibility of the scores on the rules and such are not available but are intended to be at a future date?
At the moment, it is forcing people on a scavenger hunt for unavailable information.
Thanks.
From: Vic<EMAIL_ADDRESS>Sent: Monday, April 8, 2024 3:41 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: John Fedor<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Anomaly Scoring - missing some clarity (Issue #121209)
Attention: This email was sent from someone outside of BDO USA. Always use caution when opening attachments or clicking links from unknown senders or when receiving unexpected emails.
This is by design. The work required to change this situation is currently lower priority.

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/121209#issuecomment-2043607613, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZAU3OHAMP6AFU4NUVUKRSDY4L6GXAVCNFSM6AAAAABFPFDQKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBTGYYDONRRGM.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>BDO Digital, LLC, a Delaware limited liability company, is a wholly-owned subsidiary of BDO USA, P.C. BDO USA, P.C., a Virginia professional service corporation, is the U.S. member of BDO International Limited, a UK company limited by guarantee, and forms part of the international BDO network of independent member firms.
BDO is the brand name for the BDO network and for each of the BDO Member Firms.
IMPORTANT NOTICES
The contents of this email and any attachments to it may contain privileged and confidential information from BDO Digital, LLC. This information is only for the viewing or use of the intended recipient. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of, or the taking of any action in reliance upon, the information contained in this e-mail, or any of the attachments to this e-mail, is strictly prohibited and that this e-mail and all of the attachments to this e-mail, if any, must be immediately returned to BDO Digital, LLC or destroyed and, in either case, this e-mail and all attachments to this e-mail must be immediately deleted from your computer without making any copies hereof. If you have received this e-mail in error, please notify BDO Digital, LLC by e-mail immediately.