Question about  IOEither - Applicative

🐛 Question
Cool library!
Current Behavior
I have an array of job desciptions, which I map to an array of IOEither, which i then sequence using the IOEIther.Applicative instance.
const dumpJobs = (destination: string) => (jobs: DumpJob[]) =>
	pipe(
		jobs,
		A.mapWithIndex(dumpJob(destination, jobs.length)),
		A.map(IOEither.map(buf => buf.toString())),
		A.sequence(IOEither.Applicative)
	);

All jobs are always executed, irrespective of failures.
Expected behavior
Bail out when a job fails.
Question
Is this intentional behavior?
If so, is there something in fp-ts which I can use to get the desired behavior?
Could this behavior be clarified in the documentation, or is this what most people expect to happen?
Or am I doing something wrong?

sequenceT takes a tuple of HKT<F, A> where F is of the Apply class (applicative functor minus the pure/of lifting function). I looked at the code, and it appears to bail on the first failure.
export function sequenceT<F>(F: Apply<F>): any {
  return <A>(...args: Array<HKT<F, A>>) => {
    const len = args.length
    const f = getTupleConstructor(len)
    let fas = F.map(args[0], f)
    for (let i = 1; i < len; i++) {
      fas = F.ap(fas, args[i])
    }
    return fas
  }
}

This code doesn't show the short circuiting, but if you check out, for example, the code for Option's ap, it will only eval the "second" option if the first is Some<A> rather than None.

Hi @kylegoetz, thank you for your response.
I cannot use sequenceT, because the array of jobs is of dynamic length.
Further, I don't think sequenceT would give bailout on error behavior for IOEither.Applicative, because the following code fragment also does not bail out on error:
import * as IOEither from 'fp-ts/lib/IOEither';
import { log } from 'fp-ts/lib/Console';
import { toError } from "fp-ts/lib/Either";
import { pipe } from 'fp-ts/lib/function';

const firstTask = IOEither.left(Error("Crash and burn"));
const secondTask = IOEither.tryCatch(log("Second task here"), toError);
const collect = () => () => "We are happy"

const result = pipe(
	IOEither.right(collect),
	IOEither.ap(firstTask),
	IOEither.ap(secondTask)
)()

When running this, the output is:
Second task here
But the first task always has a left-value.

The analogue with Either:
const firstEither = Either.left(Error("Crash and burn"));
const secondEither: Either.Either<Error, string> = Either.right("Second Either here");

const result = pipe(
	Either.right(collect),
	Either.ap(firstEither),
	Either.ap(secondEither)
)

console.log(
	Either.getOrElse((left: Error) => left.toString())(result)
);

does bail-out with "Error: Crash and burn", as expected.

@twiggler I think we can export two Applicative instances (like in TaskEither)

ApplicativePar (does not bail out)
ApplicativeSeq (does bail out)

and deprecate Applicative in favour of ApplicativePar.
See https://github.com/gcanti/fp-ts/pull/1325

@gcanti Thank you!
This seems to be a great solution  🥳.
I will test the PR and will get back to you on Saturday,

@gcanti I have checked out the PR, and it works splendidly.

@twiggler thanks for checking out, released.


can't install

can you tell me how to install it using "go install" please?
because the "go get -u" command is deprecated
go get: installing executables with 'go get' in module mode is deprecated.
	Use 'go install pkg@version' instead.
	For more information, see https://golang.org/doc/go-get-install-deprecation
	or run 'go help get' or 'go help install'.

I ran:
sudo go install github.com/jaeles-project/gospider@latest
on my ubuntu20 but it doen't work
but it is working on macOS, please help ...

I ran: sudo go install github.com/jaeles-project/gospider@latest on my ubuntu20 but it doen't work but it is working on macOS, please help ...

Go to releases page and download the version for your distr. like following,
wget https://github.com/jaeles-project/gospider/releases/download/v1.1.6/gospider_v1.1.6_linux_x86_64.zip

then unzip and use it.


update

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:WLQ7FjhxPnbJgomY5bXUYzFzvJi1qZj58yupo9HQDi5
Token Name:Atypical WL
Token Symbol:$ATP
Logo: (logo should be uploaded under assets/mainnet/WLQ7FjhxPnbJgomY5bXUYzFzvJi1qZj58yupo9HQDi5/*.<png/svg>)
Link to the official homepage of token:https://solscan.io/token/WLQ7FjhxPnbJgomY5bXUYzFzvJi1qZj58yupo9HQDi5

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

Add atypical token


Native support for Ruby 3.1

I started working on adding native (precompiled) support for Ruby 3.1. Unfortunately it appears that Ruby 3.1 introduced a change that breaks how we use mkmf's pkg_config method, so I'm creating this issue to make that issue visible.
In summary, ruby-magic's extconf.rb was relying on the ability to pass multiple flags:
https://github.com/kwilczynski/ruby-magic/blob/f1a875bfdf0f6f78d1a337879fa4436bf3512031/ext/magic/extconf.rb#L299-L301
Unfortunately, this commit in Ruby breaks the behavior we were relying on:
https://github.com/ruby/ruby/commit/dff8d12
and so as a result, the build breaks with this error output:
...
Building Ruby Magic with a packaged version of libmagic-5.39.
Activating libmagic 5.39 (from /home/flavorjones/code/oss/ruby-magic/ports/x86_64-redhat-linux/libmagic/5.39)...
*** ../../../../ext/magic/extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
	--with-opt-dir
	--without-opt-dir
	--with-opt-include
	--without-opt-include=${opt-dir}/include
	--with-opt-lib
	--without-opt-lib=${opt-dir}/lib
	--with-make-prog
	--without-make-prog
	--srcdir=../../../../ext/magic
	--curdir
	--ruby=/usr/local/rake-compiler/ruby/x86_64-redhat-linux/ruby-3.1.0/bin/$(RUBY_BASE_NAME)
	--help
	--clean
	--enable-system-libraries
	--disable-system-libraries
	--use-system-libraries
	--enable-static
	--enable-cross-build
	--with-libmagic-dir
	--without-libmagic-dir
	--with-libmagic-include
	--without-libmagic-include=${libmagic-dir}/include
	--with-libmagic-lib
	--without-libmagic-lib=${libmagic-dir}/lib
	--with-libmagic-config
	--without-libmagic-config
	--with-pkg-config
	--without-pkg-config
../../../../ext/magic/extconf.rb:304:in `<main>': Please install the `pkg-config` utility (RuntimeError)

and the contents of mkmf.log are:
LD_LIBRARY_PATH=.:/usr/local/rake-compiler/ruby/x86_64-redhat-linux/ruby-3.1.0/lib:/opt/rh/devtoolset-10/root/usr/lib64:/opt/rh/devtoolset-10/root/usr/lib:/opt/rh/devtoolset-10/root/usr/lib64/dyninst:/opt/rh/devtoolset-10/root/usr/lib/dyninst:/usr/local/lib64 pkg-config --exists libmagic
LD_LIBRARY_PATH=.:/usr/local/rake-compiler/ruby/x86_64-redhat-linux/ruby-3.1.0/lib:/opt/rh/devtoolset-10/root/usr/lib64:/opt/rh/devtoolset-10/root/usr/lib:/opt/rh/devtoolset-10/root/usr/lib64/dyninst:/opt/rh/devtoolset-10/root/usr/lib/dyninst:/usr/local/lib64 pkg-config --libs --static libmagic |
=> "Unknown option --libs --static\n"

I think the right thing to do is to submit a PR upstream to Ruby to allow passing multiple options to pkg_config, but that will take some time. We could also monkeypatch pkg_config but it's a rather long and complicated method and so that may be a bit risky.
I'm curious if anybody has any other clever ideas for working around this? I do believe we need to pass both --libs and --static to pkg_config to get the right flags for the ruby-magic build, though I guess we could work around it for now by passing just --libs and then hardcoding -lz.

Note that #30 takes the approached mentioned last above, passing just --libs to pkg-config and hardcoding -lz.

I'm working on a PR to send upstream to Ruby for mkmf pkg-config support.

Thanks @flavorjones! That seems like the right approach. I don't see a way to inject multiple arguments now.

See upstream PR at https://github.com/ruby/ruby/pull/5436. If that goes green I'll open a new issue at https://bugs.ruby-lang.org/ for review.

Hi @flavorjones,
Thank you for the heads up! And for working towards a fix (both here and in the upstream Ruby). I really appreciate that!
@stanhu thank you for looking into this!
I had a brief look a the pkg-config Ruby Gem, however, it does not offer what we need here.

PR submitted upstream at https://bugs.ruby-lang.org/issues/18490

The upstream PR has been merged into 3.2.0.dev / ruby head. I've updated #32 to only monkeypatch Ruby 3.1.x.


Can you please tell me what the accuracy of you CNN?


pythran: change 'l0', 'l1' to 'arr0', 'arr1'

they are like '10', '11'

@hainm thanks for the doc improvement!

@serge-sans-paille the only easy I  think help now. :P
I am trying pythran and if there is any thing that is not clear in doc, I can help with this (as a part of my learning).
Hai


Run box_dimensionaler_multicam without a chessboard

Required Info

Camera Model
D455

Platform
PC

Language
python

Hello
I am measuring the volume using box_dimensionaler_multicam as python. After storing the corner coordinate values of the chessboard, we will load the coordinate values from the same location and run them next time.
I would like to know why the value when coordinate points2D is output in the presence of a chessboard board and the points2D stored and output power of the chessboard board come out differently.
(Run with the chessboard on)

(Save and load)

Hi @HyeYumKim  In your previous question on this subject in https://github.com/IntelRealSense/librealsense/issues/9951#issuecomment-966039933 it was recommended that if you are using a single camera then the intrinsics and extrinsics of the camera could be stored to enable use of the program without a chessboard.  Have you tried this approach, please?
Comparing your two sets of Points2D results, they do not seem to be very different.  Does using the set of saved-and-loaded values make a noticeable difference to the measurements of the volume?

As you said then, the value was hard-coded and executed. When hard-coded, it catches completely different places from the object.
Is there a reason?

The chessboard is designed to enable multiple cameras to calibrate their positions in relation to each other when placed around the outside of the chessboard.  So when a single camera is used, you should be able to use the intrinsics and extrinsics of that one camera instead of having to have the chessboard present to calibrate the camera against.
In your opening message, you said that you were "storing the corner coordinate values of the chessboard".  Could you explain more about this please, as it does not sound as though you are storing the intrinsic and extrinsic values of the camera.  Thanks very much.

I want to get only the corner coordinates of the chessboard board, not the internal and external values of the camera.
What I understand is that the camera corrects the corner coordinates taken. So I think we only need to know the coordinate values of the corners taken by each camera.
Did I get it wrong? Please tell me if there's anything wrong.
Thank you.

The title of this issue 'Run box_dimensionaler_multicam without a chessboard' suggested to me that you want to measure the volume of an object without using a calibration chessboard.  I apologize if I have misunderstood what you are aiming to achieve.
I went back to the start of the case to read it again.  It sounds as though you want to store the corner coordinates of the chessboard at the first time that you take a measurement and then take the chessboard away so that you can perform subsequent measurement sessions with the stored corner values without having to have the chessboard present.
For this to work, the camera would likely have to be fixed in the same position all the time and the measured object would have  to be placed at roughly the same position in front of the camera each time, because the program would not be able to use the chessboard to calibrate the camera to the board position if the board was not there or the program had been altered so that it does not perform the initial chessboard calibration phase.

Yes, that’s right.
I'll try a few more times.
Thank you so much for your help!

You are very welcome, @HyeYumKim - I look forward to your next report.  Good luck!

Hi @HyeYumKim  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.

@HyeYumKim did you have success with removing the chessboard calibration? Can you share what was done and how you achieved it?

Hi everyone,
I want to ask a question. I want to measure objects without a chessboard with a camera. Where should I save the information you mentioned here or where should I make changes in the python code? Can you help me?

Hi @dreamerinthe  I believe that @HyeYumKim would be the best person to provide advice on this subject, because as far as I know they are the only RealSense user who has attempted this boardless adaptation and made progress with programming it,

Hi dear @HyeYumKim can you help us?


Concordance emits an additional vcf of filtered true and false negatives

@takutosato could you review this addition to the concordance tool?

@davidbenjamin back to you


Called variants gene count

Run on demo demo data and call variants on all genes. There are no called variants for RAI1, but the calling did take place. The bar at the top shows that 5 of 6 genes are called which is misleading. 6 of 6 were called, 5 of 6 have variants returned. I imagine a user will think that calling failed on a gene, so I would say we show 6 of 6 if all genes were called on

This was fixed by  #1007 which addressed a problem in DangerSummary where we were not caching a changed DangerSummary after calling variants.


dnacenter_wireless_enterprise_ssid WPA3 SSIDs fail to provision due to missing parameter

Prerequisites

[ x] Have you tested the operation in the API directly?
[ x] Do you have the latest Terraform provider version?
[ x] Review the compatibility matrix before opening an issue.

Describe the bug
SSIDs created using the dnacenter_wireless_enterprise_ssid resource with WPA3 enterprise cannot be provision to WLC due to parameter "protected_management_frame" missing from the terraform resource. This parameter is available via the DNAC API, and for WPA3 SSIDs, it has to be set to required, else provisioning of the SSID fails.
Expected behavior
"protected_management_frame" paramter is available to set via the terraform resource with, "Optional", "Required" and "Disabled" values. I can see that there is some code in the .go, but the implementation is not complete:
On resource_wireless_enterprise_ssid.go:
									"protected_management_frame": &schema.Schema{
										Description: `Protected Management Frame`,
										Type:        schema.TypeString,
										Computed:    true,
									},

Screenshots
Please provide an screenshot of the successful API call with cuRL, Postman, etc.
Environment (please complete the following information):
Cisco DNA Center version and patch: <IP_ADDRESS> - 70852
Terraform version: 1.5.6
Cisco DNA Center provider version: 1.1.22-beta
OS Version: Ubuntu
Additional context
Add any other context about the problem here.

@edudppaz, Parameter was include in provider v1.1.24-beta

Hi @fmunozmiranda . The value is added now to the provider, but on each plan/apply, the resource is trying to apply the value again.
it also seems like its trying to apply the "ssid_name" value, on each plan/apply even if no changes have been made.
This behaviour is not present in 1.1.22-beta
# dnacenter_wireless_enterprise_ssid.this["HSO Gjest"] will be updated in-place
  ~ resource "dnacenter_wireless_enterprise_ssid" "this" {
        id   = "name:=HSO Gjest"
        # (1 unchanged attribute hidden)

      ~ parameters {
            name                                  = "HSO Gjest"
          ~ protected_management_frame            = "Optional" -> "Required"
          + ssid_name                             = "HSO Gjest"
            # (17 unchanged attributes hidden)
        }
    }

  # dnacenter_wireless_enterprise_ssid.this["HSO IoT"] will be updated in-place
  ~ resource "dnacenter_wireless_enterprise_ssid" "this" {
        id   = "name:=HSO IoT"
        # (1 unchanged attribute hidden)

      ~ parameters {
            name                                  = "HSO IoT"
          ~ protected_management_frame            = "Optional" -> "Required"
          + ssid_name                             = "HSO IoT"
            # (17 unchanged attributes hidden)
        }
    }

  # dnacenter_wireless_enterprise_ssid.this["HSO Voice"] will be updated in-place
  ~ resource "dnacenter_wireless_enterprise_ssid" "this" {
        id   = "name:=HSO Voice"
        # (1 unchanged attribute hidden)

      ~ parameters {
            name                                  = "HSO Voice"
          ~ protected_management_frame            = "Optional" -> "Required"
          + ssid_name                             = "HSO Voice"
            # (17 unchanged attributes hidden)
        }
    }

  # dnacenter_wireless_enterprise_ssid.this["HSO Wireless"] will be updated in-place
  ~ resource "dnacenter_wireless_enterprise_ssid" "this" {
        id   = "name:=HSO Wireless"
        # (1 unchanged attribute hidden)

      ~ parameters {
            name                                  = "HSO Wireless"
          ~ protected_management_frame            = "Optional" -> "Required"
          + ssid_name                             = "HSO Wireless"
            # (17 unchanged attributes hidden)
        }
    }

  # dnacenter_wireless_enterprise_ssid.this["eduroam"] will be updated in-place
  ~ resource "dnacenter_wireless_enterprise_ssid" "this" {
        id   = "name:=eduroam"
        # (1 unchanged attribute hidden)

      ~ parameters {
            name                                  = "eduroam"
          ~ protected_management_frame            = "Optional" -> "Required"
          + ssid_name                             = "eduroam"
            # (17 unchanged attributes hidden)
        }
    }

Hi @edudppaz , please try it with new provider version, ssid_name now is mapped.

Hi @fmunozmiranda , the issue with the ssid name being pushed on each apply is fixed, however, when trying to set the protected_management_frame to Required, it is not updated on the tfstate and it keeps trying to update it on each apply:
terraform state show 'dnacenter_wireless_enterprise_ssid.this["HSO Voice"]'
# dnacenter_wireless_enterprise_ssid.this["HSO Voice"]:
resource "dnacenter_wireless_enterprise_ssid" "this" {
    id   = "name:=HSO Voice"
    item = [
        {
            group_uuid           = "-1"
            inherited_group_name = ""
            inherited_group_uuid = ""
            instance_uuid        = "d918afb3-a402-4e63-9cee-27c34fdf7356"
            ssid_details         = [
                {
                    aaa_override                   = "false"
                    auth_server                    = "auth_ise"
                    client_rate_limit              = 0
                    coverage_hole_detection_enable = "false"
                    enable_broadcast_ssi_d         = "true"
                    enable_fast_lane               = "false"
                    enable_mac_filtering           = "false"
                    fast_transition                = "Adaptive"
                    is_enabled                     = "true"
                    is_fabric                      = "false"
                    multi_psk_settings             = []
                    name                           = "HSO Voice"
                    nas_options                    = []
                    passphrase                     = ""
                    protected_management_frame     = "Optional"
                    radio_policy                   = "Triple band operation (2.4GHz, 5GHz and 6GHz)"
                    security_level                 = "wpa3_enterprise"
                    traffic_type                   = "voicedata"
                    wlan_type                      = "Enterprise"
                },
            ]
            version              = 307
        },
    ]

    parameters {
        basic_service_set_client_idle_timeout = 300
        client_exclusion_timeout              = 180
        enable_basic_service_set_max_idle     = "true"
        enable_broadcast_ssi_d                = "true"
        enable_client_exclusion               = "true"
        enable_directed_multicast_service     = "true"
        enable_fast_lane                      = "false"
        enable_mac_filtering                  = "false"
        enable_neighbor_list                  = "true"
        enable_session_time_out               = "true"
        fast_transition                       = "Adaptive"
        mfp_client_protection                 = "Optional"
        name                                  = "HSO Voice"
        nas_options                           = []
        protected_management_frame            = "Optional"
        radio_policy                          = "Triple band operation (2.4GHz, 5GHz and 6GHz)"
        security_level                        = "wpa3_enterprise"
        session_time_out                      = 1800
        ssid_name                             = "HSO Voice"
        traffic_type                          = "voicedata"
    }
}
admedupoz@ubuntu:~/Git/tf-dnac$ terraform apply -target='dnacenter_wireless_enterprise_ssid.this["HSO Voice"]'
dnacenter_wireless_enterprise_ssid.this["HSO Voice"]: Refreshing state... [id=name:=HSO Voice]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # dnacenter_wireless_enterprise_ssid.this["HSO Voice"] will be updated in-place
  ~ resource "dnacenter_wireless_enterprise_ssid" "this" {
        id   = "name:=HSO Voice"
        # (1 unchanged attribute hidden)

      ~ parameters {
            name                                  = "HSO Voice"
          ~ protected_management_frame            = "Optional" -> "Required"
            # (18 unchanged attributes hidden)
        }
    }

Plan: 0 to add, 1 to change, 0 to destroy.
╷
│ Warning: Resource targeting is in effect
│
│ You are creating a plan with the -target option, which means that the result of this plan may not represent all of the changes requested by the current configuration.
│
│ The -target option is not for routine use, and is provided only for exceptional situations such as recovering from errors or mistakes, or when Terraform specifically suggests to use it as part of an
│ error message.
╵

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

dnacenter_wireless_enterprise_ssid.this["HSO Voice"]: Modifying... [id=name:=HSO Voice]
dnacenter_wireless_enterprise_ssid.this["HSO Voice"]: Modifications complete after 5s [id=name:=HSO Voice]
╷
│ Warning: Applied changes may be incomplete
│
│ The plan was created with the -target option in effect, so some changes requested in the configuration may have been ignored and the output values may not be fully updated. Run the following command
│ to verify that no other changes are pending:
│     terraform plan
│
│ Note that the -target option is not suitable for routine use, and is provided only for exceptional situations such as recovering from errors or mistakes, or when Terraform specifically suggests to
│ use it as part of an error message.
╵

Apply complete! Resources: 0 added, 1 changed, 0 destroyed.

Outputs:

vns = <sensitive>
admedupoz@ubuntu:~/Git/tf-dnac$ terraform state show 'dnacenter_wireless_enterprise_ssid.this["HSO Voice"]'
# dnacenter_wireless_enterprise_ssid.this["HSO Voice"]:
resource "dnacenter_wireless_enterprise_ssid" "this" {
    id   = "name:=HSO Voice"
    item = [
        {
            group_uuid           = "-1"
            inherited_group_name = ""
            inherited_group_uuid = ""
            instance_uuid        = "d918afb3-a402-4e63-9cee-27c34fdf7356"
            ssid_details         = [
                {
                    aaa_override                   = "false"
                    auth_server                    = "auth_ise"
                    client_rate_limit              = 0
                    coverage_hole_detection_enable = "false"
                    enable_broadcast_ssi_d         = "true"
                    enable_fast_lane               = "false"
                    enable_mac_filtering           = "false"
                    fast_transition                = "Adaptive"
                    is_enabled                     = "true"
                    is_fabric                      = "false"
                    multi_psk_settings             = []
                    name                           = "HSO Voice"
                    nas_options                    = []
                    passphrase                     = ""
                    protected_management_frame     = "Optional"
                    radio_policy                   = "Triple band operation (2.4GHz, 5GHz and 6GHz)"
                    security_level                 = "wpa3_enterprise"
                    traffic_type                   = "voicedata"
                    wlan_type                      = "Enterprise"
                },
            ]
            version              = 307
        },
    ]

    parameters {
        basic_service_set_client_idle_timeout = 300
        client_exclusion_timeout              = 180
        enable_basic_service_set_max_idle     = "true"
        enable_broadcast_ssi_d                = "true"
        enable_client_exclusion               = "true"
        enable_directed_multicast_service     = "true"
        enable_fast_lane                      = "false"
        enable_mac_filtering                  = "false"
        enable_neighbor_list                  = "true"
        enable_session_time_out               = "true"
        fast_transition                       = "Adaptive"
        mfp_client_protection                 = "Optional"
        name                                  = "HSO Voice"
        nas_options                           = []
        protected_management_frame            = "Optional"
        radio_policy                          = "Triple band operation (2.4GHz, 5GHz and 6GHz)"
        security_level                        = "wpa3_enterprise"
        session_time_out                      = 1800
        ssid_name                             = "HSO Voice"
        traffic_type                          = "voicedata"
    }
}

@edudppaz, and could verify if protected_management_frame changes from Optional to Required in Dnac too?

Hi @fmunozmiranda . pmf was not configured on DNAC. But after manually removing all SSIDs and applying from scratch from terraform, it seems to be working fine. PMF is now properly configured and subsequent applies inform that the configuration matches the infrastructure.
Is not the best outcome (as we have to manually remove all SSID configurations), but the main issue is fixed.

Ok, I'm going to close this issue.
If there's something ese wey can please open a new issue.
Thanks.


ModuleNotFoundError: No module named 'rod.element'

Just installed rod from the README instruction:
pip install git+https://github.com/ami-iit/rod

Trying to import it afterwards:
Python 3.8.10 (default, Jun 22 2022, 20:18:18)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import rod
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "~/.local/lib/python3.8/site-packages/rod/__init__.py", line 1, in <module>
    from .collision import Collision
  File "~/.local/lib/python3.8/site-packages/rod/collision.py", line 6, in <module>
    from .common import Pose
  File "~/.local/lib/python3.8/site-packages/rod/common.py", line 6, in <module>
    from .element import Element
ModuleNotFoundError: No module named 'rod.element'

Hi @stephane-caron, thanks for the feedback. My bad, fixed in ca82e0aea0c426ddc2163b01b1d823aa99774054. Let me know if it works now, the library is still very young :)

No worries :smiley: I reinstalled and it works now :ok_hand: Thanks for the quick fix!


Fix: validate timeline

What kind of change does this PR introduce?
Avoiding future issues

What is the current behavior?
There was an issue last week where the Timeline crashed due to having kind-of-invalid data in it.

What is the new behavior (if this is a feature change)?
The Timeline is now getting validated so that such issues are caught early.

Other information:

Status

[x] Code documentation for the relevant parts in the code have been added/updated by the PR author
[ ] The functionality has been tested by the PR author
[ ] The functionality has been tested by NRK

Codecov Report
Base: 68.41% // Head: 68.42% // Increases project coverage by +0.00% :tada:

Coverage data is based on head (5ce5ffd) compared to base (ee5ab0e).
Patch coverage: 80.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           release47     #770   +/-   ##
==========================================
  Coverage      68.41%   68.42%
==========================================
  Files            278      278
  Lines          33865    33884   +19
  Branches        4605     4607    +2
==========================================
+ Hits           23169    23184   +15
- Misses         10242    10246    +4
  Partials         454      454

Impacted Files
Coverage Δ

...ckages/job-worker/src/playout/timeline/generate.ts
69.56% <75.00%> (+0.09%)
:arrow_up:

packages/job-worker/src/blueprints/postProcess.ts
66.75% <83.33%> (+0.43%)
:arrow_up:

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


godot 4 reimporting normal map can cos error spam

Godot version
v4.0.dev.calinou [4cb406e02]
System information
Win 10 64, AMD RX 480
Issue description
Pressing the re-import of normal map gives console spam.

drivers/vulkan/rendering_device_vulkan.cpp:7153 - Condition "!uniform_set" is true.
Uniforms supplied for set (3):
Set: 3 Binding: 0 Type: UniformBuffer Length: 128
Set: 3 Binding: 1 Type: Texture Length: 1
Set: 3 Binding: 2 Type: Texture Length: 1
Set: 3 Binding: 3 Type: Texture Length: 1
are not the same format as required by the pipeline shader. Pipeline shader requires the following bindings:
Set: 0 Binding: 1 Type: Sampler Length: 12
Set: 0 Binding: 2 Type: Sampler Length: 1
Set: 0 Binding: 3 Type: Sampler Length: 1
Set: 0 Binding: 4 Type: Sampler Length: 1
Set: 0 Binding: 5 Type: StorageBuffer Length: 0
Set: 0 Binding: 6 Type: StorageBuffer Length: 0
Set: 0 Binding: 7 Type: StorageBuffer Length: 0
Set: 0 Binding: 8 Type: UniformBuffer Length: 4224
Set: 0 Binding: 9 Type: StorageBuffer Length: 0
Set: 0 Binding: 10 Type: StorageBuffer Length: 0
Set: 0 Binding: 11 Type: Texture Length: 1
Set: 0 Binding: 12 Type: Texture Length: 1
Set: 0 Binding: 13 Type: StorageBuffer Length: 0
Set: 0 Binding: 14 Type: StorageBuffer Length: 0
Set: 0 Binding: 15 Type: UniformBuffer Length: 368
Set: 1 Binding: 0 Type: UniformBuffer Length: 2656
Set: 1 Binding: 1 Type: StorageBuffer Length: 0
Set: 1 Binding: 2 Type: Texture Length: 1
Set: 1 Binding: 3 Type: Texture Length: 1
Set: 1 Binding: 4 Type: Texture Length: 1
Set: 1 Binding: 5 Type: Texture Length: 1
Set: 1 Binding: 6 Type: Texture Length: 8
Set: 1 Binding: 7 Type: Texture Length: 8
Set: 1 Binding: 8 Type: StorageBuffer Length: 0
Set: 1 Binding: 9 Type: Texture Length: 1
Set: 1 Binding: 10 Type: Texture Length: 1
Set: 1 Binding: 11 Type: Texture Length: 1
Set: 1 Binding: 12 Type: Texture Length: 1
Set: 1 Binding: 13 Type: Texture Length: 1
Set: 1 Binding: 14 Type: Texture Length: 1
Set: 1 Binding: 15 Type: Texture Length: 1
Set: 1 Binding: 16 Type: Texture Length: 1
Set: 1 Binding: 17 Type: UniformBuffer Length: 896
Set: 1 Binding: 18 Type: Texture Length: 1
Set: 2 Binding: 0 Type: StorageBuffer Length: 0
Set: 3 Binding: 0 Type: UniformBuffer Length: 128
Set: 3 Binding: 1 Type: Texture Length: 1
Set: 3 Binding: 2 Type: Texture Length: 1
Set: 3 Binding: 3 Type: Texture Length: 1
Set: 3 Binding: 4 Type: Texture Length: 1
drivers/vulkan/rendering_device_vulkan.cpp:7153 - Condition "!uniform_set" is true.
Uniforms were never supplied for set (3) at the time of drawing, which are required by the pipeline
drivers/vulkan/rendering_device_vulkan.cpp:7153 - Condition "!uniform_set" is true.
Uniforms were never supplied for set (3) at the time of drawing, which are required by the pipeline
drivers/vulkan/rendering_device_vulkan.cpp:7153 - Condition "!uniform_set" is true.

Steps to reproduce
create a scene
add meshinstance -> make box
add a standard material -> check normal map.
go to the normal map import settings and check settings and reimport.
add the normal texture to the shader. and re-import.
Video: https://drive.google.com/file/d/1rgJrInhxweaKPx_D4kH6f37HMFQnoWwT/view?usp=sharing
Minimal reproduction project
No response

This was already reported in https://github.com/godotengine/godot/issues/48886 (it's from the same cause). However, the issue doesn't appear to be fixed yet, so I'll leave it open. I can still reproduce it here on master 85186bc0c.
This can be worked around by reloading the current scene after saving it (Scene > Reload Saved Scene).


new field in GetMatchDetails

New field in GetMatchDetails - "match_outcome". If dire won "match_outcome": 3, if radiant "match_outcome": 2. No more "radiant_win".
Check this out:

https://yasp.co/matches/2452904337

https://yasp.co/matches/2452896443

https://yasp.co/matches/2452895531

https://yasp.co/matches/2452912581

Yes, I was right. Аttached screenshots from the dota.

Ouch! Not there :D


Firestore Auto-update not happening

How is the auto-update configured?  It looks like it's not working for Firestore:

@ulukaya can you take a look at this?

My script just finds "Podfile"s and updates them. https://github.com/GoogleCloudPlatform/repository-gardener/blob/master/use-latest-deps-ios.sh#L67
Somehow the latest Podfile update stopped it. I'll check what's going on.

I don't see any errors but looks like it got timed out. I updated manually for now, that should make the next iteration work. I'll investigate further if it gets stuck again.

https://github.com/firebase/quickstart-ios/commit/92f82d085c829271c8b2a812cd742e88c160bdae

Reopening since this is still a problem as can be seen from repo's main page's directories' last update messages.

Reopening since this is still a problem as can be seen from repo's main page's directories' last update messages.

The culprit seems to be gRPC-C++:
Installing gRPC-C++ (1.28.2)
[!] /bin/bash -c
set -e
sed -E -i '' 's;#include <openssl/(.*)>;#if COCOAPODS==1\
  #include <openssl_grpc/\1>\
#else\
  #include <openssl/\1>\
#endif;g' $(find src/core -type f \( -path '*.h' -or -path '*.cc' \) -print | xargs grep -H -c '#include <openssl_grpc/' | grep 0$ | cut -d':' -f1)
    find src/core/ third_party/upb/ -type f \( -name '*.h' -or -name '*.c' -or -name '*.cc' \) -print0 | xargs -0 -L1 sed -E -i'.grpc_back' 's;#include "upb/(.*)";#if COCOAPODS==1\
  #include  "third_party/upb/upb/\1"\
#else\
  #include  "upb/\1"\
#endif;g'
    find src/core/ third_party/upb/ -type f -name '*.grpc_back' -print0 | xargs -0 rm
    find src/core/ src/cpp/ -type f \( -name '*.h' -or -name '*.c' -or -name '*.cc' \) -print0 | xargs -0 -L1 sed -E -i'.grpc_back' 's;#include "(.*).upb.h";#if COCOAPODS==1\
  #include  "src/core/ext/upb-generated/\1.upb.h"\
#else\
  #include  "\1.upb.h"\
#endif;g'
    find src/core/ src/cpp/ -type f -name '*.grpc_back' -print0 | xargs -0 rm

sed: can't read s;#include <openssl/(.*)>;#if COCOAPODS==1\
  #include <openssl_grpc/\1>\
#else\
  #include <openssl/\1>\
#endif;g: No such file or directory

Maybe related to the wrong sed on the machine? https://github.com/firebase/firebase-ios-sdk/issues/736#issuecomment-362338481

Based on this flag (--platform=ubuntu) in the build logs, the kokoro jobs are running on ubuntu. Moving them to macOS will probably fix the issue.

Moved jobs to macOS in cl/379353433. Will re-test and see if Firestore works now.

Kokoro is even more broken now. Going to roll the CLs back while I figure out what in the script is causing failures.

This has been fixed in the gRPC podspec, and will be fixed in Firestore whenver they update their gRPC dependency.

Will be fixed in M114.


rename variables, change thread idx to bufferIdx,which lead to misunderstanding

--slice buffer variable rename: pSliceInThread replace by pSliceBuffer
--slice buffer variable rename:sSliceThreadInfo replace by sSliceBufferInfo
-- slice buffer variable rename:sSliceBufferInfo[iThreadIdx] replaced by sSliceBufferInfo[iSlcBuffIdx]
--slice buffer variable rename: kiThreadIdx replaced by kiThreadIdx
--slice buffer variable rename:m_iThreadIdx replace by m_iBufferIdx
--slice buffer variable rename:pSlice->uiThreadIdx replaced by pSlice->uiBufferIdx
--slice buffer variable rename:change param name for SetOneSliceBsBufferUnderMultithread
--remove unneed code
RBC1800
RBC1801
RBC1802
RBC1803
RBC1804
RBC1805
RBC1806

latest update for this PR, please refer to #2716


Remove unnecessary call to get_block_header_state

Version of EOSJS
All versions
Describe the bug
generateTapos throws an error on transaction when calling get_block_header_state, but does not actually need to call it.
To Reproduce
Steps to reproduce the behavior:

Spin up a new chain
Generate a transaction
Error in console when transact calls generateTapos

Expected behavior
Should not throw if calling generateTapos without a valid last_irreversible_block_num.
Additional context
Porting this over from https://github.com/EOSIO/eosjs/pull/698
Co-Authored By: @UMU618<EMAIL_ADDRESS>

mark #698

Fixed in above PR.


Renamed cmdlets name and description

Renamed cmdlets name and description

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@dariomws @tseward @get-itips

Hello @bishalgautam-ms
Are you a Microsoft employee?
Here is a site you can use to see the mappings between GitHub and Microsoft aliases: https://repos.opensource.microsoft.com/people?q=bishalgautam-ms
And if you have a Microsoft alias you can link your accounts in GitHub so that a blue "Microsoft submitter" label appears to any PR's you submit. Guidance on it here: https://docs.opensource.microsoft.com/tools/github/index.html
There are some build errors because of the file name change, can you review them?

Docs Build status updates of commit 3ee4a19:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionErrorReport.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmTeam.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmUser.md
:white_check_mark:Succeeded
View (teams-ps)

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

Hello @bishalgautam-ms Are you a Microsoft employee?
Here is a site you can use to see the mappings between GitHub and Microsoft aliases: https://repos.opensource.microsoft.com/people?q=bishalgautam-ms
And if you have a Microsoft alias you can link your accounts in GitHub so that a blue "Microsoft submitter" label appears to any PR's you submit. Guidance on it here: https://docs.opensource.microsoft.com/tools/github/index.html
There are some build errors because of the file name change, can you review them?

Hi @get-itips , yes I am a Microsoft employee. I can see the mapping between my GitHub alias and Microsoft alias in the above link.
I just fixed the build errors. Please have a look again. Thank you!

I couldn't find these cmdlets in 3.0.0 or 3.0.1-preview, is this going live in the next GA or Public Preview of the module? Thanks

Yes, we are planning to release it in the next GA, we will try to release this public doc update and that release as close as possible.

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

File
Status
Preview URL
Details

exchange/exchange-ps/toc.yml
:warning:Warning
View (exchange-ps)
Details

teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionConnector.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionErrorReport.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionOperation.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionSyncResult.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmTeam.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmUser.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsShiftsConnectionBatchTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsShiftsConnectionTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Remove-CsTeamsShiftsScheduleRecord.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Set-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Test-CsTeamsShiftsConnectionValidate.md
:white_check_mark:Succeeded
View (teams-ps)

exchange/exchange-ps/toc.yml

Line 5, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#active-directory' in 'exchange-ps/exchange/index.yml'.
Line 38, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#antispam-antimalware' in 'exchange-ps/exchange/index.yml'.
Line 279, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#client-access' in 'exchange-ps/exchange/index.yml'.
Line 372, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#client-access-servers' in 'exchange-ps/exchange/index.yml'.
Line 471, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#database-availability-groups' in 'exchange-ps/exchange/index.yml'.
Line 518, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#defender-for-office-365' in 'exchange-ps/exchange/index.yml'.
Line 605, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#devices' in 'exchange-ps/exchange/index.yml', did you mean '#options'?
Line 714, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#email-addresses-and-address-books' in 'exchange-ps/exchange/index.yml'.
Line 787, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#encryption-and-certificates' in 'exchange-ps/exchange/index.yml'.
Line 854, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#exchangepowershell' in 'exchange-ps/exchange/index.yml'.
Line 875, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#federation-and-hybrid' in 'exchange-ps/exchange/index.yml'.
Line 954, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#mailbox-databases-and-servers' in 'exchange-ps/exchange/index.yml'.
Line 1017, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#mailboxes' in 'exchange-ps/exchange/index.yml'.
Line 1238, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#mail-flow' in 'exchange-ps/exchange/index.yml'.
Line 1439, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#move-and-migration' in 'exchange-ps/exchange/index.yml'.
Line 1536, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#organization' in 'exchange-ps/exchange/index.yml'.
Line 1637, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance' in 'exchange-ps/exchange/index.yml'.
Line 1792, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance-audit' in 'exchange-ps/exchange/index.yml'.
Line 1843, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance-content-search' in 'exchange-ps/exchange/index.yml'.
Line 1888, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance-dlp' in 'exchange-ps/exchange/index.yml'.
Line 2001, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance-ediscovery' in 'exchange-ps/exchange/index.yml'.
Line 2044, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance-retention' in 'exchange-ps/exchange/index.yml'.
Line 2233, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#powershell-v2-module' in 'exchange-ps/exchange/index.yml'.
Line 2272, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#reporting' in 'exchange-ps/exchange/index.yml'.
Line 2385, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#role-based-access-control' in 'exchange-ps/exchange/index.yml'.
Line 2442, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#server-health-and-performance' in 'exchange-ps/exchange/index.yml'.
Line 2499, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#sharing-and-collaboration' in 'exchange-ps/exchange/index.yml'.
Line 2610, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#unified-messaging' in 'exchange-ps/exchange/index.yml'.
Line 2719, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#users-and-groups' in 'exchange-ps/exchange/index.yml'.

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

@bishalgautam-ms Bishal, your last commit seem to impact the build, can you check please?

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

File
Status
Preview URL
Details

exchange/exchange-ps/toc.yml
:warning:Warning
View (exchange-ps)
Details

teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionConnector.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionErrorReport.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionOperation.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionSyncResult.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmTeam.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmUser.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsShiftsConnectionBatchTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsShiftsConnectionTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Remove-CsTeamsShiftsScheduleRecord.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Set-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Test-CsTeamsShiftsConnectionValidate.md
:white_check_mark:Succeeded
View (teams-ps)

exchange/exchange-ps/toc.yml

Line 5, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#active-directory' in 'exchange-ps/exchange/index.yml'.
Line 38, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#antispam-antimalware' in 'exchange-ps/exchange/index.yml'.
Line 279, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#client-access' in 'exchange-ps/exchange/index.yml'.
Line 372, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#client-access-servers' in 'exchange-ps/exchange/index.yml'.
Line 471, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#database-availability-groups' in 'exchange-ps/exchange/index.yml'.
Line 518, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#defender-for-office-365' in 'exchange-ps/exchange/index.yml'.
Line 605, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#devices' in 'exchange-ps/exchange/index.yml', did you mean '#options'?
Line 714, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#email-addresses-and-address-books' in 'exchange-ps/exchange/index.yml'.
Line 787, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#encryption-and-certificates' in 'exchange-ps/exchange/index.yml'.
Line 854, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#exchangepowershell' in 'exchange-ps/exchange/index.yml'.
Line 875, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#federation-and-hybrid' in 'exchange-ps/exchange/index.yml'.
Line 954, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#mailbox-databases-and-servers' in 'exchange-ps/exchange/index.yml'.
Line 1017, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#mailboxes' in 'exchange-ps/exchange/index.yml'.
Line 1238, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#mail-flow' in 'exchange-ps/exchange/index.yml'.
Line 1439, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#move-and-migration' in 'exchange-ps/exchange/index.yml'.
Line 1536, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#organization' in 'exchange-ps/exchange/index.yml'.
Line 1637, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance' in 'exchange-ps/exchange/index.yml'.
Line 1792, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance-audit' in 'exchange-ps/exchange/index.yml'.
Line 1843, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance-content-search' in 'exchange-ps/exchange/index.yml'.
Line 1888, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance-dlp' in 'exchange-ps/exchange/index.yml'.
Line 2001, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance-ediscovery' in 'exchange-ps/exchange/index.yml'.
Line 2044, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance-retention' in 'exchange-ps/exchange/index.yml'.
Line 2233, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#powershell-v2-module' in 'exchange-ps/exchange/index.yml'.
Line 2272, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#reporting' in 'exchange-ps/exchange/index.yml'.
Line 2385, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#role-based-access-control' in 'exchange-ps/exchange/index.yml'.
Line 2442, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#server-health-and-performance' in 'exchange-ps/exchange/index.yml'.
Line 2499, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#sharing-and-collaboration' in 'exchange-ps/exchange/index.yml'.
Line 2610, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#unified-messaging' in 'exchange-ps/exchange/index.yml'.
Line 2719, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#users-and-groups' in 'exchange-ps/exchange/index.yml'.

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

Docs Build status updates of commit 5fc231d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

exchange/exchange-ps/toc.yml
:warning:Warning
View (exchange-ps)
Details

teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionConnector.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionErrorReport.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionOperation.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionSyncResult.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmTeam.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmUser.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsShiftsConnectionBatchTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsShiftsConnectionTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Remove-CsTeamsShiftsScheduleRecord.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Set-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Test-CsTeamsShiftsConnectionValidate.md
:white_check_mark:Succeeded
View (teams-ps)

exchange/exchange-ps/toc.yml

Line 5, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#active-directory' in 'exchange-ps/exchange/index.yml'.
Line 38, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#antispam-antimalware' in 'exchange-ps/exchange/index.yml'.
Line 279, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#client-access' in 'exchange-ps/exchange/index.yml'.
Line 372, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#client-access-servers' in 'exchange-ps/exchange/index.yml'.
Line 471, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#database-availability-groups' in 'exchange-ps/exchange/index.yml'.
Line 518, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#defender-for-office-365' in 'exchange-ps/exchange/index.yml'.
Line 605, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#devices' in 'exchange-ps/exchange/index.yml', did you mean '#options'?
Line 714, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#email-addresses-and-address-books' in 'exchange-ps/exchange/index.yml'.
Line 787, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#encryption-and-certificates' in 'exchange-ps/exchange/index.yml'.
Line 854, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#exchangepowershell' in 'exchange-ps/exchange/index.yml'.
Line 875, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#federation-and-hybrid' in 'exchange-ps/exchange/index.yml'.
Line 954, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#mailbox-databases-and-servers' in 'exchange-ps/exchange/index.yml'.
Line 1017, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#mailboxes' in 'exchange-ps/exchange/index.yml'.
Line 1238, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#mail-flow' in 'exchange-ps/exchange/index.yml'.
Line 1439, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#move-and-migration' in 'exchange-ps/exchange/index.yml'.
Line 1536, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#organization' in 'exchange-ps/exchange/index.yml'.
Line 1637, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance' in 'exchange-ps/exchange/index.yml'.
Line 1792, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance-audit' in 'exchange-ps/exchange/index.yml'.
Line 1843, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance-content-search' in 'exchange-ps/exchange/index.yml'.
Line 1888, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance-dlp' in 'exchange-ps/exchange/index.yml'.
Line 2001, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance-ediscovery' in 'exchange-ps/exchange/index.yml'.
Line 2044, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-and-compliance-retention' in 'exchange-ps/exchange/index.yml'.
Line 2233, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#powershell-v2-module' in 'exchange-ps/exchange/index.yml'.
Line 2272, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#reporting' in 'exchange-ps/exchange/index.yml'.
Line 2385, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#role-based-access-control' in 'exchange-ps/exchange/index.yml'.
Line 2442, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#server-health-and-performance' in 'exchange-ps/exchange/index.yml'.
Line 2499, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#sharing-and-collaboration' in 'exchange-ps/exchange/index.yml'.
Line 2610, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#unified-messaging' in 'exchange-ps/exchange/index.yml'.
Line 2719, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#users-and-groups' in 'exchange-ps/exchange/index.yml'.

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

@bishalgautam-ms Bishal, your last commit seem to impact the build, can you check please?

Seems like build warning errors are coming for the file which does not even exist in the project (exchange/exchange-ps/toc.yml). I have not made any changes in files under that folder. This looks quite strange to me.

Maybe @tiburd or @traya1  can help with that

looking into the issue

Docs Build status updates of commit 68f27e5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionConnector.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionErrorReport.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionOperation.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionSyncResult.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmTeam.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmUser.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsShiftsConnectionBatchTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsShiftsConnectionTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Remove-CsTeamsShiftsScheduleRecord.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Set-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Test-CsTeamsShiftsConnectionValidate.md
:white_check_mark:Succeeded
View (teams-ps)

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

Docs Build status updates of commit 8faba04:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionConnector.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionErrorReport.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionOperation.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionSyncResult.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmTeam.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmUser.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsShiftsConnectionBatchTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsShiftsConnectionTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionTeamMap.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Remove-CsTeamsShiftsScheduleRecord.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Set-CsTeamsShiftsConnectionInstance.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Test-CsTeamsShiftsConnectionValidate.md
:white_check_mark:Succeeded
View (teams-ps)

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


Not Catching Subtitles

I am trying to download subtitles for a video and using --list-subs  it tells me no subtitles available when there is,
if i open the master m3u8 files i see the subtitle links and i can even download them but here its not finding them
"[generic] master: Requesting header
WARNING: [generic] Falling back on generic information extractor.
[generic] master: Downloading webpage
[generic] master: Downloading m3u8 information
WARNING: [generic] Ignoring subtitle tracks found in the HLS manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
master has no subtitles"

Be sure to call yt-dlp with the --verbose flag and include its complete output.

From the very little info you have provided, we can only assume that the issue will be fixed by #515 and will hence be closed with it
IGNORING THE ISSUE TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
If the issue persists after next release, create a new issue using the correct template with all necessary information including the entire --verbose output

Sorry for not being more specific but the issue was fixed by #515 thanks so much


-3: There is no avalible space to install App

please can you help me with this problem ? I uninstall all apps and i have still low space

Kodi needs at least 300MB of free space to install. You'll need to make more space.

Yes, I uninstalled everything and I still have the same memory. I've tried to restart everything and nothing. Maybe I could try a factory reset my oled tv.

FYI: You can delete contents in /media/preload/storedemo/ to free up spaces. They're pretty much useless and if you do have large files there, it will save you more than 500MB of space.

I see. It appears that you don't have root and in this case, you'll need to root the TV then make some spaces.


fixes dm typo

fixes a typo that was causing an error

Unless this is needed asap, please let me write a test for this before merging.


bash 3.x compatibility; avoid mapfile

Use of mapfile was introduced in da2472ff784ab6ed427f9827d79bb10ac11c0060 (to fix a shellcheck) and 509678c036900a38e9a47cbcc56e567d987b087d (to support awscli v2). mapfile was introduced in bash 4.x, but there are many systems that ship with bash 3.x (perhaps just macOS, but there's a lot of macOS systems 😅).
This patch takes advice from shellcheck at https://github.com/koalaman/shellcheck/wiki/SC2207 to use bash 3.x compatible read -a to remove the dependency on mapfile while also avoiding the previous shellcheck warnings.
Fixes #46, closes #47.
Ping: @pdbreen @ryansdwilson @kkolk

@pda bash is always beyond my bash!
I think we might have to remove the integration test for now, on our new untrusted VM world

Removing that acceptance test in #49

Thanks for jumping on this fix Paul, I tried running this this morning with your patch and got:
 line 134: account_ids[*]: unbound variable

this is what my pipeline config looks like:
- ecr#5b8f36f57f756f65b1b4fbe265e99e91844996d0:
          login: true
          no-include-email: true

Any idea why account_ids is unbound?

Thanks @pda - and very timely.  Turned out much of my day was working on pipelines and this helped speed up the change/test cycle time by an amazing amount by testing local.  Other than needing to set account_ids like Brett mentioned, worked great.

Interesting… is appears bash 3.x treats ${array[*]} as unbound if the array is empty, while newer bash works as expected.
for ver in 3.2 4.4 5.0; do
    docker run --rm bash:$ver bash -u -c 'echo $BASH_VERSION; a=(); echo ${a[*]} ok';
done

# 3.2.57(1)-release
# bash: a[*]: unbound variable

# 4.4.23(1)-release
# ok

# 5.0.17(1)-release
# ok

I've pushed a change to check for emptiness in a different way:
-  if [[ -z ${account_ids[*]} ]]; then
+  if [[ ${#account_ids[@]} -eq 0 ]]; then

The semantics are slightly different if the array contains a single empty string:
set -u
a=("")
echo "count: ${#a[@]}"
if [[ -z "${a[*]}" ]]; then echo "empty"; else echo "non-empty"; fi

# count: 1
# empty

But I don't think that's a problem for us 🤞🏼

Actually I ended up using a combination of the two approaches, to keep the old behaviour but avoid the bash 3.x error:
-  if [[ ${#account_ids[@]} -eq 0 ]]; then
+  if [[ ${#account_ids[@]} -eq 0 || -z "${account_ids[*]}" ]]; then

It only reaches the -z "${account_ids[*]}" part if the array is not empty, so that avoids the bash 3.x weirdness.

(also, rebased onto #49 to get rid of the already-failing acceptance test; should give us a ✅ on this PR)


Write unit tests for meta-stuff with sk-learn compatibility

e.g. pipelines, gridsearch
Collection of sklearn tools that should be supported with our estimates (best would be to have a parameterized test for this, estimators x tools):

[x] pipelines (implemented for a special case)
[ ] grid search (other CV methods?)

CV methods are not robustly realizable due to the implementation in sklearn


Configurable connection string support

Configurable connection string support
Allow ServiceBinding to produce a configurable connection string URL.
The updated version of #61
Fixes #60
Background
ServiceBinding creates a Kubernetes Secret with 3 fields: uri, username, and password. If we run applications that require fully qualified MongoDB connections string URI this is not sufficient.
Proposal

Enable ServiceBinding to produce the connection_string field (in addition to uri, username, and password).
Add connectionString parameter to ServiceBinding spec parameters to make the connection_string configurable.

Documentation
After success binding, a Kubernetes Secret containing connection details has a connection_string field. By default it contains a connection string URI in the DNS Seedlist Connection Format with credentials: e.g. mongodb+srv://username:password@host. The connections string can be configured through connectionString parameter of ServiceBinding resource's spec.

Name
Type
Default
Description

skipCredentials
bool
false
Controlls whether credentials should be included in the URI

database
string
''
Database name portion of the connection string URI

format
'standard' or 'srv'
'srv'
Scheme portion of the connection string URI: mongodb or mongodb+srv

options
list
[]
Options portion of the connection string URI

Example ServiceBinding resource spec:
apiVersion: servicecatalog.k8s.io/v1beta1
kind: ServiceBinding
metadata:
  name: atlas-cluster-binding
spec:
  instanceRef:
    name: atlas-cluster-instance
  parameters:
    user:
      roles:
      ...
    connectionString:
      skipCredentials: false
      database: test
      format: standard
      options:
        connectTimeoutMS: 1000
        tlsAllowInvalidCertificates: true
        w: "majority"

TODO
I couldn't find any sources of https://docs.mongodb.com/atlas-open-service-broker/ so official documentation remains unchanged.

[x] Add unit tests
[ ] Update documentation

Thanks for your interest in the AOSB.
We've decided to deprecate this codebase, and are recommending that users switch to mongodb/mongodb-atlas-kubernetes instead.


Two back buttons

The user shouldn't see two back buttons at once. The bottom one is only for after booking interface.
https://www.dropbox.com/s/xly4rvt8rz3nn37/Screenshot 2018-06-20 23.57.25.png?dl=0

is this issue still persistent? or can we close it?

No idea how to recreate it, so I guess we can close it.


Big Vec::try_reserve OOMs Miri

On both GitHub CI default linux runner (should have 16GB RAM), and locally (also linux, 64GB RAM), the following test will run out of memory in Miri, but panic in normal cargo test:
#[test]
fn try_allocate_a_lot() {
    let mut v = Vec::<u8>::new();
    v.try_reserve(128 * 1024 * 1024 * 1024).unwrap();
    let _ = v;
}

cargo test panics: called `Result::unwrap()` on an `Err` value: TryReserveError { kind: AllocError { layout: Layout { size:<PHONE_NUMBER>72, align: 1 (1 << 0) }, non_exhaustive: () } }
cargo miri test will try allocating and get killed for OOM, CTRL+C does not stop it

Apologies if this has been reported before, I could not find another issue for this.

CTRL+C does not stop it

Does a second ctrl-c stop it? Also since https://github.com/rust-lang/rust/pull/125523 it should exit at most 100ms after a ctrl-c.

Yeah this is pretty much known, see https://github.com/rust-lang/miri/issues/613. We don't make any attempt at recovering from allocation failure.

However, what I would expect to happen is that Miri itself aborts due to OOM. Maybe the reason this does not happen is that Miri uses jemalloc under the hood, whereas cargo test will use the system allocator. So maybe malloc fails immediately on an allocation of that size but jemalloc tries anyway, and then your system grinds to a halt due to swapping.

FWIW when I try to run that function locally, the program gets swiftly killed. So I can't reproduce the hang you seem to be seeing.

Does a second ctrl-c stop it? Also since https://github.com/rust-lang/rust/pull/125523 it should exit at most 100ms after a ctrl-c.

I was on 1.80.0-nightly (1ba35e9bb 2024-05-25), CTRL+C would exit cargo but miri would still be in the background allocating, forcing me to kill it manually.
I just updated to rustc 1.80.0-nightly (bdbbb6c6a 2024-05-26) and now it does exit fully.

This example program tries to allocate 128 GB which is a totally plausible amount of memory to have. For example, it's the amount of physical memory my desktop has. I suggest that if you want to write a test for OOMs you use a number that's a few factors of 2 higher.
This doesn't immediately abort the interpreter because jemalloc sets the flag MAP_NORESERVE. The interpreter looks like it is stuck, because every allocation in the interpreter is a Box<[u8]> which is the actual bytes for the data in the allocation, and the initialization state is tracked explicitly alongside. The bytes are always initialized, and the runtime you're seeing is almost certainly all the page faults from zeroing all the memory. Which yes is silly because mmap returns zeroed memory and we could totally use MaybeUninit here for efficiency, but the risk of getting it wrong seems sketchy. We try rather hard to avoid unsafe code in the interpreter.

Note that on my desktop, the threshold for an allocation failing with jemalloc is somewhere between 64 and 128 TB
use jemallocator::Jemalloc;
#[global_allocator]
static GLOBAL: Jemalloc = Jemalloc;

fn main() {
    let mut v = Vec::<u8>::new();
    v.try_reserve(128 * 1024 * 1024 * 1024 * 1024).unwrap();
    let _ = v;
}

Trying to allocate an uninit Allocation<_, _, Bytes> using Allocation::uninit() calls Bytes::zeroed which for MiriBytes uses alloc::alloc_zeroed, which should make the allocator either zero the bytes for us or if it mmap'ed a large allocation directly return the pre-zeroed mmap'ed range.

Yeah, we are using efficient zero-init if the allocator supports it.

The page faults are coming from <miri::machine::MiriMachine as rustc_const_eval::interpret::machine::Machine>::adjust_allocation. I think MiriAllocBytes is copying the allocation's data, I'm just not sure where exactly. I'm fighting with perf and bootstrap to find the right flags across Miri and the compiler that will let me profile this.

I still haven't made bootstrap cooperate, but I'm pretty sure this is just the overhead from the fact that Miri's adjust_allocation clones all allocations.

Oh right, we always go through adjust_allocation... that's kind of silly.


Add error messages for app config modules and parse clearly in parseConfigurationObject

WHY are these changes introduced?
Improves upon solution suggested in https://github.com/Shopify/cli/pull/3275

WHAT is this pull request doing?

This PR does two things:

Updates parseConfigurationObject to go through zod error messages, and creates a line in the format
• [${path}]: ${issue.message}\n.
Updates each app config module to have a message that will be used to emit a human readable schema failure error

Before:

After:

How to test your changes?

To tophat:

Pull this branch
Create an app and connect to your Partners account
Break the shopify.app.toml, here's a good example

client_id = "48ddcaff136e3e64f83717d17e40280f"
name="alkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdfalkjdshflakjhdkfhaldsjhalhjdf"
embedded = false

[build]
include_config_on_deploy = true

[auth]
redirect_urls = [ "https://shopify.dev/apps/default-app-home/api/auth" ]

[webhooks]
api_version = "2024-01"

[webhooks.privacy_compliance]
customer_deletion_url= "pubsub://projects/shopify-app-380402/topics/testing"

[pos]
embedded = false

Observe updated errors
Extra credit: Break app TOML in different ways and report back if error reporting breaks

Post-release steps

Measuring impact
How do we know this change was effective? Please choose one:

[x] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[x] Existing analytics will cater for this addition
[x] PR includes analytics changes to measure impact

Checklist

[ ] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[ ] I've considered possible documentation changes
[ ] I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

I tried all the following cases separately and it works as I’d expected ✅
[webhooks.privacy_compliance]
customer_deletion_url= "pubsub://shopify-app-380402:testing" # WORKS

[[webhooks.subscriptions]]
topics = ["products/update"]
uri = "pubsub://projects/shopify-app-380402/topics/testing" # FAILS

[[webhooks.subscriptions]]
topics = ["products/update"]
uri = "pubsub://shopify-app-380402:testing" # WORKS

[[webhooks.subscriptions]]
topics = ["products/update"]
uri = "arn:aws:events:us-ab-1::event-source/aws.partner/shopify.com.test/12aaaaa34/123" # FAILS

[[webhooks.subscriptions]]
topics = ["products/update"]
uri = "pubsub://projects/shopify-app-380402/topics/testing" # FAILS

[[webhooks.subscriptions]]
topics = ["products/update"]
uri = "http://an-url.com/" # WORKS

I also tried several combinations of trailing slash and capital/lower cases and ✅
I don’t know if it’s in scope, but I find the following behaviour weird:
If I put them all in the same toml together, I get 2 errors:
  • [webhooks.subscriptions.0.uri]: URI isn't correct URI format of https://, pubsub://{project}:topic or Eventbridge ARN
  • [webhooks.subscriptions.3.topics.0.products/update]: You can’t have duplicate subscriptions with the exact same `topic` and `uri`

Subscriptions 0 and 3 are the same, but they are both wrong ❓
If they were not wrong, I'd see several errors of the file, as I expect. However, now I fix it changing the topic of subscription 3 to products/create and I only get
  • [webhooks.subscriptions.0.uri]: URI isn't correct URI format of https://, pubsub://{project}:topic or Eventbridge ARN

❓
which makes me think that I only get the first error of each type of errors (duplicates and wrong urls)
Shouldn't I get all the webhooks.subscriptions.X.uri that are wrong or are we failing on the first and expecting the dev to fix iteratively?

This issue sounds like a limitation of zod schema validation and outside of the scope of this PR. In this case, it seems reasonable to allow the dev to fail and fix the webhook subscription errors iteratively.


[Collision] Moving to the right at the same time you jump prevents you to jump to the full height

Steps to reproduce

Stand as seen on the screenshot.
Move the joystick to the right.
Jump

Expected behaviour
You don't reach the platform.
Actual behaviour
You jump the same distance and reach the platform.
Game version
0.4
Screenshots

This is actually intended. It is usefuk when you are next to a wall and must have an extra impulse, because you do not have X offset to reach the top, since you are close to the wall, so the only time where you can move in the X axis is when you get to the top in the Y pos


Support for ESLint's new (flat) config file available in v8.21+

https://eslint.org/blog/2022/08/new-config-system-part-1/
https://eslint.org/blog/2022/08/new-config-system-part-2/

Sounds like a good PR for anyone who would like to make one

In the meantime, could we make use of @eslint/compat? Maybe an example in your README?

Quick note: flat config file compatibility could be developed in the first instance with full v9 compatibility coming later as @eslint/compat could be used in the interim.
This is the approach eslint-plugin-compat has taken.


Memory leak when using tensorflow c++ api

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04.3 LTS
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): 1.15.0
Python version:
Bazel version (if compiling from source): 0.24.1
GCC/Compiler version (if compiling from source): 5.5.0/c++11
CUDA/cuDNN version:
GPU model and memory:

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the current behavior
Our project using bazel and tensorflow c++ api for inference.
In our workspace, we using "https://github.com/tensorflow/tensorflow/archive/v1.15.0.tar.gz".
When inference on features repeatedly, memory keeps rising.
Our model is an old style pb file, not saved model. It is generated from onnx to tensorflow project.  Our graph has two inputs and one output. Here is some key code.
class TfModel {
 public:
  /**
   * @brief Construct.
   */
  TfModel() : pb_path_(xxx), input_names_{"input1:0", "input2:0"}, output_names_{"output:0"}) {
    sess_options_.config.set_use_per_session_threads(true);
    sess_options_.config.set_intra_op_parallelism_threads(0);
    sess_options_.config.set_inter_op_parallelism_threads(0);

    sess_.reset(tensorflow::NewSession(sess_options_));
    tensorflow::GraphDef graph_def;
    auto default_env = tensorflow::Env::Default();
    auto status = tensorflow::ReadBinaryProto(default_env, pb_path, &graph_def);
    if (!status.ok()) {
      throw std::invalid_argument("Error!");
    }
    sess_->Create(graph_def);
  }

  /**
   * @brief Compute.
   */
  void Compute(const tensorflow::Tensor &tensor1,
               const tensorflow::Tensor &tensor2) const {
    std::vector<std::pair<std::string, tensorflow::Tensor>> tf_input;
    tf_input.emplace_back(input_names_[0], tensor1);
    tf_input.emplace_back(input_names_[1], tensor2);
    std::vector<tensorflow::Tensor> output;
    auto status = sess_->Run(tf_input, output_names_, {}, &output);
  }

 private:
  const std::string pb_path_;
  const std::vector<std::string> input_names_;
  const std::vector<std::string> output_names_;
  std::unique_ptr<tensorflow::Session> sess_;
  tensorflow::SessionOptions sess_options_;
};

int main() {
  model = TfModel();
  while (true) {
    model.Compute(tensor1, tensor2);
    PrintRssMemory();
  }
}

I have searched some solutions and try tcmalloc. The memory leak seems negligible, but is ~25% slower than before, which is not acceptable.
The memory leak problem seems very severe if I set inter_thead and intra_thead to 0. If set to 1, the problem seems disappear. But we must use larger inter_thead and intra_thead for multi-thead.
I don't attach model since it's a little large. Hope anyone can help, Thanks.
Describe the expected behavior
No memory leak.
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.

I'm being troubled by the same problem, and the memory still keeps growing even when I set the intra and inter multi thread num to 1. After trying lots of solutions supplied by others, nothing gets better.
Any useful suggestion will be appreciated.
THX!

Hi There,
We are checking to see if you still need help on this, as you are using an older version of tensorflow which is officially considered end of life . We recommend that you upgrade to the latest 2.x version and let us know if the issue still persists in newer versions. Please open a new issue for any help you need against 2.x, and we will get you the right help.
This issue will be closed automatically 7 days from now. If you still need help with this issue, please provide us with more information.


Ability to merge json models into final model

Currently the cli allows for merged model to be created on existing json files in a directory structure.
For a use case, wherein, we want to have a final json model on a daily basis based on all json files received on that day, the volume of files we need to save on the directory structure to achieve the merged model is very large and isn't possible. We get millions per day.
If there is an ability to allow merge of models, then we can implement the use case for iterative model creation based on every message received - which becomes the final model at end of day.
For ex - steps as below:

For message1, create model1
For message 2, create model2
Merge model1+model2 as model1
Repeat the above for every new message coming - so at end of day the last model created by merge of above steps is the final model

Hey @a1nayak - first off, if you are needing to derive schemas (I think you call these models) from millions of JSON instances, then you should check out the Spark-based runtime for Schema Guru rather than the CLI one.
On the wider point - allowing merge of models - this is an interesting idea. Is this because you want to evolve a fixed set of models on a daily basis, i.e. schema_d_tuesday should be the addition of schema_d_monday and all_instance_d_tuesday[]? If you could share your use case in a bit more detail, that would be helpful.

Thanks @alexanderdean for response.
We have a kafka-storm-druid pipeline for analytics purposes wherein we capture data form multiple sources. Sometimes when the json data is sent, some attributes are missing or some may be added.
Since we are already capturing all messages in the pipeline, we wanted to extend to catch the schema drift - diff between a schema model for a particular source today vs the same source yesterday.
To capture schema drift - we would merge all the schema models generated for the source on that day and save it in filesystem. Similarly do it for next day - and then use jsondiff to highlight what got added or changed. This is a very important pointer for us as well as probably for your team too - when large data sets are involved and there is need to know how the drift is occurring
Addition of schema models for all days is achievable also with the same principles. But our use case presently was to capture the schema drift and eventually the data drift as it occurs per day basis.

Hi @a1nayak - thanks for sharing that detail, it's super-interesting.
We don't have a direct problem with schema drift at Snowplow because we use self-describing JSONs which have to pass validation against their schema to progress down the pipeline - there's no concept of schemas changing without the business making the change. However, I agree that your approach would be nice for dynamic third-party sources (like some of our webhooks) where we can't control the end schemas and vendors can change them unilaterally (despite our efforts to record them faithfully in Iglu Central).
For your specific use case - can't you just use Secor or similar to get all JSONs from Kafka to S3, then run Schema Guru Spark on each day's data? In other words, I think the existing Schema Guru functionality should suffice?

@alexanderdean  That's exactly I started doing - created a file directory structure per hour per each source and than ran schema guru on base. But the volume in very high in Walmartlabs as we are in large scale processing taking events from multiple sources (which we can't control). Each souce generates close to 10 million files - which we wouldn't be able to keep in a file system to run at end of day
So the alternative was that I process them in memory - schema guru acts on message - but schema model generated is in memory as model1, next message comes in - becomes model2 and then model 1 gets replaced with model1+model2.
The above use case is for single thread.
But it also works for multi-threading wherein multiple spouts get message and genertae there own models and then it gets streamed to a single bolt which merges all the models into one and repeats for next set as explained in single threading.
The amount of data we run - we need 10-20 TB to store even for single day.

Hey @a1nayak - that makes sense. I don't see why we can't expose a method in Schema Guru to merge one schema with another instance (or another schema) to product schema'. PR welcome!


what should I use

There are two libraries which should I use.
polymer_interop
polymer.dart

Use for what? If you want to use Polymer then use

https://pub.dartlang.org/packages/polymer

version 1.0.0-rc.16 is the most recent. You need to click on All xxx versions... to find it because pre-releases (with a - in the version) are listed below normal releases.
You also probably want to use

https://pub.dartlang.org/packages/polymer_elements

version 1.0.0-rc.8 is the most recent here. Don't be discouraged by "Currently Unsupported" this applies only to an very old version. The front page is only updated when a normal release is published. The supported version is also still a pre-release.
Github issues are for bug reports and feature requests. For support questions please use other channels https://www.dartlang.org/support/


[Runtime and Toolkit Bug]: HDRIs clipping/artifacting

Describe the bug
.exr/.hdr converted HDRIs with the NVIDIA Texture Tools Exporter using the BC6S format have severe clipping and artifacts inside the toolkit and runtime (with RR off, its a black dot, with RR on, the denoiser freaks out, causing artificing as seen in the video below)
https://github.com/user-attachments/assets/626e968f-45e9-433c-a4c2-960183fc7d47 (video)

How do you reproduce the bug?

Download a HDRI from PolyHaven or other CC0 source such this: https://polyhaven.com/a/rosendal_plains_1
Import the HDRI into NVIDIA Texture Tools, set the Format to BC6S HDR RGB, Save As... a DDS file in a place where both the toolkit and runtime can see it
In the toolkit, select a sphere/dome or other sky-like object, remove albedo map, set albedo color to 0, select the converted HDRI as a emissive map with the emissive intensity at 1 (changing it does not fix the issue)
Map gets lit as you would expect for a HDRI, but has black clipping or denoiser artifacts from areas of high luminance such as the sun or a bright light. This is observable in both the toolkit and in-game

What is the expected behavior?
The runtime should display the HDRI without clipping as shown inside NVIDIA Texture Tools/Photoshop

Version
dxvk-remix: 3b321ad /  bridge-remix: 3e91886
Logs
No response
Crash dumps
No response
Media
No response

REMIX-3721 for tracking


Add EventStream.filter specialisation to the abc

Summary
Add EventStream.filter specialisation to the abc
Checklist

[ ] I have run nox and all the pipelines have passed.
[ ] I have made unittests according to the code I have added/modified/deleted.

Related issues

Would like to check something out before merging this, but LGTM


fix: change target in tsconfig.json

:tada: This PR is included in version 1.4.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: