[Bug]: page.waitForResponse results in "Buffer is not defined" error when reading response

Bug description
Steps to reproduce the problem:

…

const [res] = await Promise.all([
            page.waitForResponse(res => res.url().includes('something') && res.request().method().toUpperCase() != "OPTIONS"),
            page.goto('https://example.com', {waitUntil: "domcontentloaded"}),
        ]);

console.log(await res?.buffer())

You'll need to adjust the URL/matcher, but when you call res.buffer() (or .text() or .json()) it raises a Buffer is not defined error.
I tested the same code on the core Puppeteer library and it worked fine.
Puppeteer version
0.0.4
Node.js version
16
npm version
9.5.1
What operating system are you seeing the problem on?
macOS
Relevant log output
No response

I wanted to share I am getting a very similar error on my worker which was previously working from a few days ago where I take a screenshot of my own site.
            browser = await puppeteer.launch(env.OG_IMAGE_BROWSER);
            page = await browser.newPage();
            page.setViewport({ width: 1920, height: 1080, deviceScaleFactor: 2 });

            // Open Game Page
            await page.goto(`https://steambase.io/games/${appId}`);
            await page.waitForSelector('#app-stats-line-chart.loaded');

            // Capture Screenshot
            const img = await page.screenshot({
                type: 'png'
            });

This is the error I get when viewing the CF worker logs:
    {
      "message": [
        "ReferenceError: Buffer is not defined"
      ],
      "level": "error",
      "timestamp":<PHONE_NUMBER>979
    }

Same here.

mine is failing at initializing browser.
const browser = await puppeteer.launch(env.MYBROWSER);

Same here.

update your dependencies incl. node to node 18 lts and try to add: compatibility_flags = [ "nodejs_compat" ]
https://github.com/cloudflare/puppeteer/pull/15#issuecomment-1666001790

@denu5 Thank you. I tried all Node versions from 16 to 19 (with nodejs_compact flag enabled), but it didn't help.

I have the same problem even though i enabled nodejs_compact flag

I had the same problem when initializing the browser and I found a comment in Cloudflare's Discord with this solution:
import { Buffer } from 'node:buffer';
import puppeteer from "@cloudflare/puppeteer";

globalThis.Buffer = Buffer;

Basically, import the Buffer before puppeteer and register globally, so the library can be access from anywhere.
Hope that helps.

@bhanderivaibhav That error can be due to a mismatch between the variable name defined in wrangler.toml and the name used in the worker code itself. So, in wrangler.toml:
browser = { binding = "MY_BROWSER", type = "browser" }

and in the worker
export default {
	async fetch(request, env, ctx) {
		const browser = await puppeteer.launch(env.MY_BROWSER); // MUST equal the binding name defined in wrangler
                 //....
        }
}

@apeacock1991 Can you try with the latest versions of wrangler (3.5.1) and cloudflare/puppeteer (0.0.5)? Can reproduce that error with version 0.0.4 but not with 0.0.5 version. Other things to check out for in wrangler.toml:
compatibility_date = "2023-05-12"

compatibility_flags = ["nodejs_compat"]
```

The solution by @roelmagdaleno fixed the problem for me. Thank you!


Remove code for ignoring ambiguous spectra from MSFReader.cpp

A user had a problem that spectra which matched more than one peptide in a .pdresult file were not being put into the .blib even if "Keep ambiguous spectra" was checked.
https://skyline.ms/announcements/home/support/thread.view?rowId=64796
MSFReader has its own code for preventing ambiguous spectra from being included in the .blib which does not pay attention to the "-K" command-line parameter.
As far as I can tell, there is no reason for that code to exist, so I figured that we should probably just remove it.

Could this be a performance issue with large pdResult files? Perhaps this internal way of eliminating ambiguous spectra is faster than relying on BiblioSpec's generic method?

I am, however, thinking that the correct fix for this behavior is not to actually remove this code like in this pull request. Instead, maybe the code should keep all PSMs that score as well as the best PSM and discard all PSMs that score worse. In this way, the scores that are tied for best place will be kept if "-K" was specified and discarded if "-K" was not specified.
I think the way I have things in this pull request might make the behavior worse in the cases where there are some PSMs that clearly scored worse compared to the best PSMs. I will investigate that.

Actually, I think that the code changes that I have in this pull request are what we should go with.
This other idea that I was proposing here where we only keep the best scoring PSM among multiple PSMs that scored better than the cutoff would be very different behavior from what we do for other types of search results.

Yes. That sounds like the entire point of BlibFilter and the redundancy is
expected before it is run. We even name the file .redundant.blib
On Sun, Sep 8, 2024 at 7:45 PM nickshulman @.***> wrote:

I am, however, thinking that the correct fix for this behavior is not to
actually remove this code like in this pull request. Instead, maybe the
code should keep all PSMs that score as well as the best PSM and discard
all PSMs that score worse. In this way, the scores that are tied for best
place will be kept if "-K" was specified and discarded if "-K" was not
specified.
I think the way I have things in this pull request might make the behavior
worse in the cases where there are some PSMs that clearly scored worse
compared to the best PSMs. I will investigate that.
Actually, I think that the code changes that I have in this pull request
are what we should go with.
This other idea that I was proposing here where we only keep the best
scoring PSM among multiple PSMs that scored better than the cutoff would be
very different behavior from what we do for other types of search results.
—
Reply to this email directly, view it on GitHub
https://github.com/ProteoWizard/pwiz/pull/3111#issuecomment-2337003485,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYBWUAPATC4OPXFACGH5RDZVUDVHAVCNFSM6AAAAABMHKJWZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZXGAYDGNBYGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


DLL Error and Defender Detecting Payload

deliver.exe is detected by AV and deleted. Whenever I try to run agressor.dll I get this:

that because you have compiled your DLL in Debug mode, change it to release mode and try again.there is new version comes after a time to bypass again

No i am not. The whole project is set up to release


Replace ureq with minreq

Multiple projects in the rust-bitcoin space are currently planning a migration away from ureq to minreq, as it provides better MSRV guarantees.
In this PR we trivially replace the ureq dependency by minreq. Note that this doesn't necessarily lower the MSRV right away due to the included rustls dependency, but is a preparatory step.
Also see https://github.com/RCasatta/electrsd/pull/58.

Multiple projects in the rust-bitcoin space are currently planning a migration away from ureq to minreq

could you please mention some?

Unfortunately it looks making clippy happy breaks other things...

CI failure seems unrelated:

Yeah, I reckicked

ACK f9b4cf201202917b60e541e6d47f1a04b4f52bf6

Should I release 0.29.4 ?


docker: no matching manifest for linux/amd64 in the manifest list entries.  when using asp.net MVC project (.net framework)

from here:https://hub.docker.com/_/microsoft-dotnet-framework
if i run this test locally
docker run -it --rm -p 8000:80 --name aspnet_sample mcr.microsoft.com/dotnet/framework/samples:aspnetapp
i get this failure:
\aspnetmvcapp> docker run -it --rm -p 8000:80 --name aspnet_sample mcr.microsoft.com/dotnet/framework/samples:aspnetapp
Unable to find image 'mcr.microsoft.com/dotnet/framework/samples:aspnetapp' locally
aspnetapp: Pulling from dotnet/framework/samples
docker: no matching manifest for linux/amd64 in the manifest list entries.
See 'docker run --help'.
i have windows 10
docker destktop installed
i can work/build other images or samples in .net core.
i can not create images ussing .net framework form Dockefile.
any help to get around this error ?

docker: no matching manifest for linux/amd64 in the manifest list entries.

This implies that your Docker Desktop is configured to target Linux containers.  There are no .NET Framework images available for Linux because .NET Framework only runs on Windows.  Are you wanting to use .NET Core/.NET 5 instead?

docker: no matching manifest for linux/amd64 in the manifest list entries.

This implies that your Docker Desktop is configured to target Linux containers. There are no .NET Framework images available for Linux because .NET Framework only runs on Windows. Are you wanting to use .NET Core/.NET 5 instead?

Yes, actually i wanted to run and test it using .net framework . maybe i can right click on "docker desktop " and "switch to windows containers "  but not sure if that would be a solution to get it working.
all i want is run this locally from my windows 10 machine .
docker run -it --rm -p 8000:80 --name aspnet_sample mcr.microsoft.com/dotnet/framework/samples:aspnetapp


Added more information when we receive an invalid token response

Possible solution to https://github.com/twilio/authy-java/issues/56

Codecov Report

Merging #57 into master will decrease coverage by 0.22%.
The diff coverage is 79.16%.

@@            Coverage Diff             @@
##           master      #57      +/-   ##
==========================================
- Coverage   73.83%   73.61%   -0.23%
==========================================
  Files          23       23
  Lines         921      936      +15
  Branches       95       95
==========================================
+ Hits          680      689       +9
- Misses        201      207       +6
  Partials       40       40

Impacted Files
Coverage Δ

src/main/java/com/authy/AuthyException.java
80% <77.77%> (-20%)
:arrow_down:

src/main/java/com/authy/api/Tokens.java
88.09% <83.33%> (-0.28%)
:arrow_down:

src/main/java/com/authy/api/Token.java
23.07% <0%> (-15.39%)
:arrow_down:


Added a "break 2;", When overriding the Driver file

Added a "break 2;", When overriding the driver file in an other folder, it would try to load all files corresponding to this name and create an error because of a double file loading

Hi @philsturgeon as you said on pull request #353 I put you directly in the message.
This is just a quick fix that doesn't need that much testing.
When the driver tries to load the file there are two "foreach" loops
but the break in the second loop is not a *break 2" it means it will still loop through the files and try to find another file even if the first one is found.
I found it when working on some loader stuff I may pull one day.
Bye


Add tutorials in Help for new billing plans

Requested by Lukas K
https://apifier.slack.com/archives/CMXTZ3VLG/p1611142585006500

Another idea regarding pricing and videos. I guess you already have something in your mind. I think it would be great to have a several short videos how you go through the subscription funnel. One video for a specific use-case

Buy a plan and scrape with overage
Buy a team plan and convert to org
Buy a plan and add proxies as add-ons


Upgrade prettier, eslint and Typescript

First step of modernizing rumors-site.
We will try updating Next.JS to at least 12 (which supports PostCSS 8 and should be able to install TailwindCSS) and then migrating to TailwindCSS if possible.

Storybook build failed, will not be included in this week's release

We will be implementing new site directly.


API > cycle (please always send attributes)

:grey_question: Context
Actually, we can get a null answer on some cycle link attribute :

And it can cause some issues on client code :

Cannot merge the following node because of null property
value for 'link': (:EOLCycle {link: null})

:bulb: Feature request

Please always send back the attribute

Affected fields :

eol
support
latest
latestReleaseDate
releaseDate

:bomb: Consequence
:point_right: I'm not able to load these attributes... then restricting data for all nodes (event the ones who implement these attributes).
:information_source: NB
The script was working until recently when mageia was added (but it's a general issue) :
[
  {
    "cycle": "8",
    "releaseDate": "2021-02-26",
    "eol": false,
    "lts": false
  },
  {
    "cycle": "7",
    "eol": "2021-06-30",
    "releaseDate": "2019-07-01",
    "lts": false
  },
  {
    "cycle": "6",
    "eol": "2019-09-30",
    "releaseDate": "2017-07-16",
    "lts": false
  },
  {
    "cycle": "5",
    "eol": "2017-12-31",
    "releaseDate": "2015-06-19",
    "lts": false
  },
  {
    "cycle": "4",
    "eol": "2015-09-19",
    "releaseDate": "2014-02-01",
    "lts": false
  },
  {
    "cycle": "3",
    "eol": "2014-11-26",
    "releaseDate": "2013-05-19",
    "lts": false
  },
  {
    "cycle": "2",
    "eol": "2013-11-22",
    "releaseDate": "2012-05-22",
    "lts": false
  },
  {
    "cycle": "1",
    "eol": "2012-12-01",
    "releaseDate": "2011-06-01",
    "lts": false
  }
]

:bookmark: Related stuff

https://github.com/endoflife-date/endoflife.date/commit/ddbbabbc070c262d2e5707de4d37e7c9c7f55190
https://github.com/endoflife-date/endoflife.date/pull/2049

Even if we add a link field, it would still be null. Would this be fixed if we mark the link parameter as optional in the schema?

Hmmm, in fact, I don't think so. It will delegate the task of performing queries to the client side... still that would be a good beginning :+1:
:bulb: Would there be an option to be able to only get the entries that implement mandatory fields :grey_question:
In a second time, I'll implement dedicated client scripts that should deal with loack of fields.

bulb Would there be an option to be able to only get the entries that implement mandatory fields grey_question

link is not a mandatory field. This issue seems related to #2362.

:+1: It's related  schema validation


Federation explicit denylist and allowlist support

Similar to Synapse's options: config options and/or admin room commands to support denying federation with certain servers, and allowlist servers for an allowlist-only federation setup.

Rethinking this now, I don't think this feature is particularly useful in practice. Malicious/offensive events will just be federated to you through other servers in the room.
It's only somewhat useful for blocking DMs / room invites from a server, and even then it needs to be extended to client /sync not just on the receiving federation endpoints.
Additionally, a private federation setup should be done with a firewall and not purely on the application level.
Conduwuit has implemented a lot of moderation utilities since this was made. If a better use-case for this comes up that existing tools cannot cover, we can look at this again. The work in the submitted PR may be repurposed or referenced for some other future things.


feat: add secure option for sending traces via otlphttp

Adds support for sending traces via otlphttp securely

Hi @kevwan any chance we can get this merged?

Hi @kevwan any chance we can get this merged?

Sure, in next release. Thanks for your contribution!


compile and build stargarzers

Hi, I'm unable to build stargazers:
$ go get github.com/spencerkimball/stargazers
package github.com/cockroachdb/cockroach/util/log: cannot find package "github.com/cockroachdb/cockroach/util/log" in any of:
	/usr/lib/go-1.7/src/github.com/cockroachdb/cockroach/util/log (from $GOROOT)
	/tmp/src/github.com/cockroachdb/cockroach/util/log (from $GOPATH)
package github.com/cockroachdb/cockroach/util: cannot find package "github.com/cockroachdb/cockroach/util" in any of:
	/usr/lib/go-1.7/src/github.com/cockroachdb/cockroach/util (from $GOROOT)
	/tmp/src/github.com/cockroachdb/cockroach/util (from $GOPATH)

Any idea?

me too, I cant understand how is possible there is people writing code putting it on the internet and not even add 1 minute to explain how to use, im not a go affictionate and i get problems with go install and im not even sure it's me or the project, but really feels bad not even a build.md file, why there are still repos like this?


When one of the links in the navigation is clicked then the UI scrolls to the corresponding section

this is done


feat(mitre): fill DataType, DataVersion, affected

If this Pull Request is work in progress, Add a prefix of “[WIP]” in the title.
What did you implement:
fill DataType, DataVersion, affected
Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
before
$ go-cve-dictionary fetch mitre 2024
$ go-cve-dictionary search cve CVE-2024-5732

after
$ go-cve-dictionary fetch mitre 2024
$ go-cve-dictionary search cve CVE-2024-5732

Checklist:
You don't have to satisfy all of the following.

[ ] Write tests
[ ] Write documentation
[x] Check that there aren't other open pull requests for the same issue/feature
[x] Format your source code by make fmt
[x] Pass the test by make test
[x] Provide verification config / commands
[x] Enable "Allow edits from maintainers" for this PR
[x] Update the messages below

Is this ready for review?: YES
Reference

Tested OK with:

CVE-2024-36971 CVE_RECORD 5.1
CVE-2023-1249 CVE_RECORD 5.0

This also answer my question in comment https://github.com/vulsio/go-cve-dictionary/pull/392#issuecomment-2203085132
Cannot see a difference regarding "affected" of course, no change in the code about this.
Minor: you probably forgot something in the "after" above, same as "before".

before/after diff
--- before.txt	2024-07-05 09:39:58.294334024 +0900
+++ after.txt	2024-07-05 09:40:17.166817550 +0900
@@ -7,8 +7,8 @@
   "Fortinets": [],
   "Mitres": [
     {
-      "DataType": "",
-      "DataVersion": "",
+      "DataType": "CVE_RECORD",
+      "DataVersion": "5.1",
       "CVEMetadata": {
         "CVEID": "CVE-2024-5732",
         "AssignerOrgID": "1af790b2-7ee1-4545-860a-a788eba489b5",
@@ -42,6 +42,43 @@
               "SupportingMedia": []
             }
           ],
+          "Affected": [
+            {
+              "Vendor": "n/a",
+              "Product": "Clash",
+              "CollectionURL": null,
+              "PackageName": null,
+              "Cpes": [],
+              "Modules": [
+                {
+                  "Module": "Proxy Port"
+                }
+              ],
+              "ProgramFiles": [],
+              "ProgramRoutines": [],
+              "Platforms": [],
+              "Repo": null,
+              "DefaultStatus": null,
+              "Versions": [
+                {
+                  "Status": "affected",
+                  "VersionType": null,
+                  "Version": "0.20.0",
+                  "LessThan": null,
+                  "LessThanOrEqual": null,
+                  "Changes": []
+                },
+                {
+                  "Status": "affected",
+                  "VersionType": null,
+                  "Version": "0.20.1",
+                  "LessThan": null,
+                  "LessThanOrEqual": null,
+                  "Changes": []
+                }
+              ]
+            }
+          ],
           "ProblemTypes": [
             {
               "Descriptions": [
@@ -218,6 +255,7 @@
           },
           "Title": "CISA ADP Vulnrichment",
           "Descriptions": [],
+          "Affected": [],
           "ProblemTypes": [],
           "Impacts": [],
           "Metrics": [

I can confirm I see the MITRE details for "affected" with the precise sha1 and the list of involved source code files as ""ProgramFiles" for ex on CVE-2024-36971. I must have missed a pull request or something.
@MaineK00n this is a fantastic change for me! I do embedded systems, and build everything from sources. Thus I have a compilation database generated with bear, and the full git history. These 2 types of data allow to filter the 95% of false positive CVE on my kernels. Previously I would resort to some heuristics and could only reach max 75% automatic filtering. But with these changes, go-cve-dictionary gives me the potential to go up to 95% with pure automation. This changes everything for me. Thank you so much to you and your colleagues! :star_struck: :fireworks: :champagne: :partying_face:


Breadcrumbs

When email subject is too long (so it's arranged into two lines in breadcrumbs) content disappears.
Chrome for Mac (Version 50.0.2661.86 (64-bit)), screen resolution 1280px

hi. fixed


Document dependencies and app setup process

There should be some sort of project setup documentation on the README. It would be super rad if there were a vagrant config included, which would make setup easier.
Here are my notes from setting up:
sudo apt-get update

# https://www.digitalocean.com/community/tutorials/how-to-install-and-use-postgresql-on-ubuntu-12-04
sudo apt-get install postgresql postgresql-contrib libpq-dev

# create a postgres user: panlexicon/panlexicon
sudo su - postgres
createuser --pwprompt

# Configure db user/password in panlexicon-rails/config/database.yml defaults

# update postgres user local authentication method (because of auth issues from `bin/rake db:setup`, "peer authentication failed")
sudo su - postgres
cd /etc/postgresql/9.1/main/
vi pg_hba.conf
# Change:
# > local   all             postgres                                peer
# to:
# > local   all             postgres                                md5
# Restart postgres
sudo service postgresql restart

# http://rvm.io/rvm/install
sudo gpg --keyserver hkp://keys.gnupg.net --recv-keys D39DC0E3
sudo \curl -sSL https://get.rvm.io | bash -s stable --rails

# Application setup
cd /var/www/sites/panlexicon-rails

# Get dependencies via gem (gem comes with ruby)
gem install bundler

# At this point I had to update Gemfile and .ruby-version to specify Ruby 2.1.5
bundle install

# Install a JS runtime: https://github.com/sstephenson/execjs
# https://github.com/joyent/node/wiki/installing-node.js-via-package-manager
# Install from the "nodesource" apt repository
curl -sL https://deb.nodesource.com/setup | sudo bash -
sudo apt-get install nodejs

# Create the database and schema
bin/rake db:setup

# Import data
# Download the thesaurus from http://www.gutenberg.org/ebooks/3202
bin/rake import:moby[mthesaur.txt]

# Start the rails dev server
bin/rails server

# If the thesaurus isn't fully loaded, and the word "thesaurus" hasn't been imported yet, then the front page will throw an error

I've added a Dockerfile and docker-compose.yml which should ease the dependency setup in #212. I've also documented the (hopefully brief) steps necessary for building the application for development using Docker: https://github.com/bensheldon/panlexicon-rails#docker-setup


Fetching om director config does not get s3 credentials

While using S3 blobstore on AWS, when I run following command, I expect it to get S3 access_key and secret_key under properties-configuration.director_configuration.s3_blobstore_options' key in director.yaml`. However its not there. This may seem like a minor annoyance, but it is more than that.
When I try to initialize (not an existing director config) with this config file, I get an "S3 access_key can't be empty" error.
As  result any automation that tries to use a clean room environment, breaks.
om staged-director-config --no-redact > director.yaml

Version of OM cli: 4.6.0
Version of OM: Pivotal Ops Manager v2.8.0-build.187

@yogendra, we don't have an OpsMan director configured with an s3 blobstore at the momnet.
Are you able to run om with the --trace command? This will output the HTTP request and responses done. I'd be curious to know if you see the output you expect in there.
If not, this might an issue with OpsMan not om.

Hi
Here is what I did for getting trace output.

Create  a new foundation on AWS using terraform
Configured director (using the provided script in terraforming-aws)
Manually added s3 details in the blobstore section of director config
Ran om --trace staged-director-configuration --no-redact

Here is the output. (I have redacted private keys and sectes etc.)
om --trace staged-director-config --no-redact
GET /api/v0/staged/products HTTP/1.1
Content-Type: application/json

HTTP/1.1 200 OK
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Wed, 29 Apr 2020 18:17:28 GMT
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Pragma: no-cache
Referrer-Policy: strict-origin-when-cross-origin
Server: Ops Manager
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: 080a13ce-4239-4eae-90fa-518a116384e6
X-Runtime: 0.044149
X-Xss-Protection: 1; mode=block

a8
[{"installation_name":"p-bosh","guid":"p-bosh-335c90cb702024c95679","type":"p-bosh","product_version":"2.9.0-build.106","label":"BOSH Director","service_broker":false}]
0

GET /api/v0/staged/director/availability_zones HTTP/1.1
Content-Type: application/json

HTTP/1.1 200 OK
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Wed, 29 Apr 2020 18:17:29 GMT
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Pragma: no-cache
Referrer-Policy: strict-origin-when-cross-origin
Server: Ops Manager
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: fbd4f223-7c13-46fd-af7f-eaeb06b2deac
X-Runtime: 0.043414
X-Xss-Protection: 1; mode=block

7d
{"availability_zones":[{"name":"us-east-1a","guid":"dc42bfcce17090ec25f0","iaas_configuration_guid":"08bf526a3bed16f8c95a"}]}
0

GET /api/v0/staged/director/iaas_configurations HTTP/1.1
Content-Type: application/json

HTTP/1.1 200 OK
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Wed, 29 Apr 2020 18:17:30 GMT
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Pragma: no-cache
Referrer-Policy: strict-origin-when-cross-origin
Server: Ops Manager
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: 5f1d2c53-dd80-4487-80db-4f3d00ac2d8c
X-Runtime: 0.048868
X-Xss-Protection: 1; mode=block

11e
{"iaas_configurations":[{"guid":"08bf526a3bed16f8c95a","name":"default","additional_cloud_properties":{},"iam_instance_profile":"demo_ops_manager","security_group":"sg-019f4a38691f54b0b","key_pair_name":"demo-ops-manager-key","region":"us-east-1","encrypted":false,"kms_key_arn":null}]}
0

GET /api/v0/staged/director/properties?redact=false HTTP/1.1
Content-Type: application/json

HTTP/1.1 200 OK
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Wed, 29 Apr 2020 18:17:31 GMT
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Pragma: no-cache
Referrer-Policy: strict-origin-when-cross-origin
Server: Ops Manager
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: c4b300c6-f9b8-465a-9b9d-a65924587ad3
X-Runtime: 0.055995
X-Xss-Protection: 1; mode=block

1aad
{"director_configuration":{"ntp_servers_string":"<IP_ADDRESS>","resurrector_enabled":false,"director_hostname":null,"max_threads":null,"custom_ssh_banner":null,"opentsdb_ip":null,"director_worker_count":5,"post_deploy_enabled":false,"bosh_recreate_on_next_deploy":false,"bosh_director_recreate_on_next_deploy":false,"bosh_recreate_persistent_disks_on_next_deploy":false,"retry_bosh_deploys":false,"keep_unreachable_vms":false,"identification_tags":{},"skip_director_drain":false,"job_configuration_on_tmpfs":false,"nats_max_payload_mb":null,"database_type":"internal","blobstore_type":"s3","s3_blobstore_options":{"endpoint":"https://s3.us-east-1.amazonaws.com","bucket_name":"demo-runs-on-cf-blonstore","signature_version":"2","region":null,"backup_strategy":"none","backup_bucket_region":"","backup_bucket_name":"","enable_signed_urls":true,"url_style":"domain-style"},"hm_pager_duty_options":{"enabled":false},"hm_emailer_options":{"enabled":false},"encryption":{"keys":[],"providers":[]}},"dns_configuration":{"excluded_recursors":[],"recursor_selection":null,"recursor_timeout":null,"handlers":[]},"security_configuration":{"trusted_certificates":"-----BEGIN CERTIFICATE-----<snip>-----END CERTIFICATE-----\n","generate_vm_passwords":true,"opsmanager_root_ca_trusted_certs":false},"syslog_configuration":{"enabled":false},"iaas_configuration":{"guid":"08bf526a3bed16f8c95a","name":"default","additional_cloud_properties":{},"iam_instance_profile":"demo_ops_manager","security_group":"sg-019f4a38691f54b0b","key_pair_name":"demo-ops-manager-key","region":"us-east-1","encrypted":false,"kms_key_arn":null,"access_key_id":"AK<snip>","secret_access_key":"M<snip>V","ssh_private_key":"-----BEGIN RSA PRIVATE KEY-----<snip>\n-----END RSA PRIVATE KEY-----\n"}}
0

GET /api/v0/staged/director/iaas_configurations?redact=false HTTP/1.1
Content-Type: application/json

HTTP/1.1 200 OK
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Wed, 29 Apr 2020 18:17:32 GMT
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Pragma: no-cache
Referrer-Policy: strict-origin-when-cross-origin
Server: Ops Manager
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: 7a70b045-08ea-4f85-a805-d9a3a12b3be5
X-Runtime: 0.044880
X-Xss-Protection: 1; mode=block

e7b
{"iaas_configurations":[{"guid":"08bf526a3bed16f8c95a","name":"default","additional_cloud_properties":{},"iam_instance_profile":"demo_ops_manager","security_group":"sg-019f4a38691f54b0b","key_pair_name":"demo-ops-manager-key","region":"us-east-1","encrypted":false,"kms_key_arn":null,"access_key_id":"AK<snip>","secret_access_key":"M<snip>V","ssh_private_key":"-----BEGIN RSA PRIVATE KEY-----<snip>-----END RSA PRIVATE KEY-----\n"}]}
0

GET /api/v0/staged/director/networks HTTP/1.1
Content-Type: application/json

HTTP/1.1 200 OK
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Wed, 29 Apr 2020 18:17:33 GMT
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Pragma: no-cache
Referrer-Policy: strict-origin-when-cross-origin
Server: Ops Manager
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: af4ba799-1be6-4c73-a2f9-93c53c76bc76
X-Runtime: 0.055508
X-Xss-Protection: 1; mode=block

389
{"icmp_checks_enabled":false,"networks":[{"guid":"674694b26bd0aa3a94ab","name":"ops-manager","subnets":[{"guid":"9198078b4e0f4b27b8bb","iaas_identifier":"subnet-047988a744f735026","cidr":"<IP_ADDRESS>/28","dns":"<IP_ADDRESS>","gateway":"<IP_ADDRESS>","reserved_ip_ranges":"<IP_ADDRESS>-<IP_ADDRESS>","availability_zone_names":["us-east-1a"]}]},{"guid":"195ae4f3e064db28651e","name":"pks","subnets":[{"guid":"4209ff648d366051a668","iaas_identifier":"subnet-0b8d71961155a1598","cidr":"<IP_ADDRESS>/24","dns":"<IP_ADDRESS>","gateway":"<IP_ADDRESS>","reserved_ip_ranges":"<IP_ADDRESS>-<IP_ADDRESS>","availability_zone_names":["us-east-1a"]}]},{"guid":"06aeb3c7c1249efe028d","name":"services","subnets":[{"guid":"cff38ecc39deca3f11e8","iaas_identifier":"subnet-0b3f392911888cfe6","cidr":"<IP_ADDRESS>/24","dns":"<IP_ADDRESS>","gateway":"<IP_ADDRESS>","reserved_ip_ranges":"<IP_ADDRESS>-<IP_ADDRESS>","availability_zone_names":["us-east-1a"]}]}]}
0

GET /api/v0/staged/products/p-bosh-335c90cb702024c95679/networks_and_azs HTTP/1.1
Content-Type: application/json

HTTP/1.1 200 OK
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Wed, 29 Apr 2020 18:17:34 GMT
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Pragma: no-cache
Referrer-Policy: strict-origin-when-cross-origin
Server: Ops Manager
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: 170500cb-a674-4d92-b67d-26b5564c6aa3
X-Runtime: 0.087866
X-Xss-Protection: 1; mode=block

89
{"networks_and_azs":{"singleton_availability_zone":{"name":"us-east-1a"},"other_availability_zones":[],"network":{"name":"ops-manager"}}}
0

GET /api/v0/staged/products/p-bosh-335c90cb702024c95679/jobs HTTP/1.1
Content-Type: application/json

HTTP/1.1 200 OK
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Wed, 29 Apr 2020 18:17:35 GMT
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Pragma: no-cache
Referrer-Policy: strict-origin-when-cross-origin
Server: Ops Manager
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: 89995a5e-08aa-4bc7-960e-03aea6bb3a40
X-Runtime: 0.115138
X-Xss-Protection: 1; mode=block

86
{"jobs":[{"name":"director","guid":"director-105cfd717b9fe8f78f1a"},{"name":"compilation","guid":"compilation-589aa3c4b0090667f467"}]}
0

GET /api/v0/staged/vm_extensions HTTP/1.1
Content-Type: application/json

HTTP/1.1 200 OK
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Wed, 29 Apr 2020 18:17:36 GMT
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Pragma: no-cache
Referrer-Policy: strict-origin-when-cross-origin
Server: Ops Manager
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: deafc6c4-4d6f-48a5-8d1b-2113b7baae5b
X-Runtime: 0.093137
X-Xss-Protection: 1; mode=block

14
{"vm_extensions":[]}
0

GET /api/v0/vm_types HTTP/1.1
Content-Type: application/json

HTTP/1.1 200 OK
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Wed, 29 Apr 2020 18:17:36 GMT
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Pragma: no-cache
Referrer-Policy: strict-origin-when-cross-origin
Server: Ops Manager
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: a0493544-9418-449c-b7ed-5350dc245136
X-Runtime: 0.073610
X-Xss-Protection: 1; mode=block

897
{"vm_types":[{"name":"t3.micro","ram":1024,"cpu":1,"ephemeral_disk":8192,"raw_instance_storage":false,"builtin":true},{"name":"t3.small","ram":2048,"cpu":1,"ephemeral_disk":8192,"raw_instance_storage":false,"builtin":true},{"name":"t3.medium","ram":3840,"cpu":1,"ephemeral_disk":32768,"raw_instance_storage":false,"builtin":true},{"name":"c5.large","ram":3840,"cpu":2,"ephemeral_disk":32768,"raw_instance_storage":false,"builtin":true},{"name":"m5.large","ram":7680,"cpu":2,"ephemeral_disk":32768,"raw_instance_storage":false,"builtin":true},{"name":"r5.large","ram":15616,"cpu":2,"ephemeral_disk":65536,"raw_instance_storage":false,"builtin":true},{"name":"c5.xlarge","ram":7680,"cpu":4,"ephemeral_disk":65536,"raw_instance_storage":false,"builtin":true},{"name":"m5.xlarge","ram":15616,"cpu":4,"ephemeral_disk":65536,"raw_instance_storage":false,"builtin":true},{"name":"r5.xlarge","ram":31232,"cpu":4,"ephemeral_disk":131072,"raw_instance_storage":false,"builtin":true},{"name":"c5.2xlarge","ram":15616,"cpu":8,"ephemeral_disk":131072,"raw_instance_storage":false,"builtin":true},{"name":"m5.2xlarge","ram":30720,"cpu":8,"ephemeral_disk":131072,"raw_instance_storage":false,"builtin":true},{"name":"r5.2xlarge","ram":62464,"cpu":8,"ephemeral_disk":262144,"raw_instance_storage":false,"builtin":true},{"name":"c5.4xlarge","ram":30720,"cpu":16,"ephemeral_disk":262144,"raw_instance_storage":false,"builtin":true},{"name":"m5.4xlarge","ram":65536,"cpu":16,"ephemeral_disk":262144,"raw_instance_storage":false,"builtin":true},{"name":"r5.4xlarge","ram":124928,"cpu":16,"ephemeral_disk":524288,"raw_instance_storage":false,"builtin":true},{"name":"c5.9xlarge","ram":73728,"cpu":36,"ephemeral_disk":524288,"raw_instance_storage":false,"builtin":true},{"name":"m5.12xlarge","ram":196608,"cpu":48,"ephemeral_disk":1048576,"raw_instance_storage":false,"builtin":true},{"name":"r5.12xlarge","ram":393216,"cpu":48,"ephemeral_disk":2097152,"raw_instance_storage":false,"builtin":true},{"name":"i3.8xlarge","ram":249856,"cpu":32,"ephemeral_disk":983040,"raw_instance_storage":true,"builtin":true},{"name":"d2.8xlarge","ram":249856,"cpu":36,"ephemeral_disk":983040,"raw_instance_storage":true,"builtin":true}]}
0

GET /api/v0/staged/products/p-bosh-335c90cb702024c95679/jobs/director-105cfd717b9fe8f78f1a/resource_config HTTP/1.1
Content-Type: application/json

HTTP/1.1 200 OK
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Wed, 29 Apr 2020 18:17:37 GMT
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Pragma: no-cache
Referrer-Policy: strict-origin-when-cross-origin
Server: Ops Manager
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: cb6f7ead-5215-4b7d-8bef-f7d3fe5eb5d8
X-Runtime: 0.091740
X-Xss-Protection: 1; mode=block

f4
{"instance_type":{"id":"automatic"},"instances":"automatic","additional_networks":[],"internet_connected":false,"elb_names":[],"persistent_disk":{"size_mb":"automatic"},"additional_vm_extensions":[],"swap_as_percent_of_memory_size":"automatic"}
0

GET /api/v0/staged/products/p-bosh-335c90cb702024c95679/jobs/compilation-589aa3c4b0090667f467/resource_config HTTP/1.1
Content-Type: application/json

HTTP/1.1 200 OK
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Wed, 29 Apr 2020 18:17:38 GMT
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Pragma: no-cache
Referrer-Policy: strict-origin-when-cross-origin
Server: Ops Manager
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: bcb4fdb7-f3fb-4c11-aafb-85a2573b49de
X-Runtime: 0.095244
X-Xss-Protection: 1; mode=block

ca
{"instance_type":{"id":"automatic"},"instances":"automatic","additional_networks":[],"internet_connected":false,"elb_names":[],"additional_vm_extensions":[],"swap_as_percent_of_memory_size":"automatic"}
0

az-configuration:
- name: us-east-1a
  iaas_configuration_name: default
  guid: dc42bfcce17090ec25f0
iaas-configurations:
- access_key_id: AK<snip>
  additional_cloud_properties: {}
  encrypted: false
  iam_instance_profile: demo_ops_manager
  key_pair_name: demo-ops-manager-key
  name: default
  region: us-east-1
  secret_access_key: M<snip>V
  security_group: sg-019f4a38691f54b0b
  ssh_private_key: |
    -----BEGIN RSA PRIVATE KEY-----
    <sip>
    -----END RSA PRIVATE KEY-----
network-assignment:
  network:
    name: ops-manager
  other_availability_zones: []
  singleton_availability_zone:
    name: us-east-1a
networks-configuration:
  icmp_checks_enabled: false
  networks:
  - name: ops-manager
    subnets:
    - iaas_identifier: subnet-047988a744f735026
      cidr: <IP_ADDRESS>/28
      dns: <IP_ADDRESS>
      gateway: <IP_ADDRESS>
      reserved_ip_ranges: <IP_ADDRESS>-<IP_ADDRESS>
      availability_zone_names:
      - us-east-1a
  - name: pks
    subnets:
    - iaas_identifier: subnet-0b8d71961155a1598
      cidr: <IP_ADDRESS>/24
      dns: <IP_ADDRESS>
      gateway: <IP_ADDRESS>
      reserved_ip_ranges: <IP_ADDRESS>-<IP_ADDRESS>
      availability_zone_names:
      - us-east-1a
  - name: services
    subnets:
    - iaas_identifier: subnet-0b3f392911888cfe6
      cidr: <IP_ADDRESS>/24
      dns: <IP_ADDRESS>
      gateway: <IP_ADDRESS>
      reserved_ip_ranges: <IP_ADDRESS>-<IP_ADDRESS>
      availability_zone_names:
      - us-east-1a
properties-configuration:
  director_configuration:
    blobstore_type: s3
    bosh_director_recreate_on_next_deploy: false
    bosh_recreate_on_next_deploy: false
    bosh_recreate_persistent_disks_on_next_deploy: false
    database_type: internal
    director_worker_count: 5
    encryption:
      keys: []
      providers: []
    hm_emailer_options:
      enabled: false
    hm_pager_duty_options:
      enabled: false
    identification_tags: {}
    job_configuration_on_tmpfs: false
    keep_unreachable_vms: false
    ntp_servers_string: <IP_ADDRESS>
    post_deploy_enabled: false
    resurrector_enabled: false
    retry_bosh_deploys: false
    s3_blobstore_options:
      backup_bucket_name: ""
      backup_bucket_region: ""
      backup_strategy: none
      bucket_name: demo-runs-on-cf-blonstore
      enable_signed_urls: true
      endpoint: https://s3.us-east-1.amazonaws.com
      signature_version: "2"
      url_style: domain-style
    skip_director_drain: false
  dns_configuration:
    excluded_recursors: []
    handlers: []
  security_configuration:
    generate_vm_passwords: true
    opsmanager_root_ca_trusted_certs: false
    trusted_certificates: |
      -----BEGIN CERTIFICATE-----
      MIIFFzCCA3+gAwIBAgIQDcHzIPAWVz+3L7IK+LjkUDANBgkqhkiG9w0BAQsFADCB
      ozEeMBwGA1UEChMVbWtjZXJ0IGRldmVsb3BtZW50IENBMTwwOgYDVQQLDDN5cmFt
      cHVyaWFAeXJhbXB1cmlhLW1icDE1LmxvY2FsIChZb2dlbmRyYSBSYW1wdXJpYSkx
      QzBBBgNVBAMMOm1rY2VydCB5cmFtcHVyaWFAeXJhbXB1cmlhLW1icDE1LmxvY2Fs
      IChZb2dlbmRyYSBSYW1wdXJpYSkwHhcNMjAwMjA4MDkxODM2WhcNMzAwMjA4MDkx
      ODM2WjCBozEeMBwGA1UEChMVbWtjZXJ0IGRldmVsb3BtZW50IENBMTwwOgYDVQQL
      DDN5cmFtcHVyaWFAeXJhbXB1cmlhLW1icDE1LmxvY2FsIChZb2dlbmRyYSBSYW1w
      dXJpYSkxQzBBBgNVBAMMOm1rY2VydCB5cmFtcHVyaWFAeXJhbXB1cmlhLW1icDE1
      LmxvY2FsIChZb2dlbmRyYSBSYW1wdXJpYSkwggGiMA0GCSqGSIb3DQEBAQUAA4IB
      jwAwggGKAoIBgQDABBkhpN5vQ6Cg9dpv68m1jjKAzqRHkXjbcZQCEGUdw3RJy8dX
      baSRHCYRiny/m3DiyXOvacRJYOMeIChFqytv65Ljmpu0Lvct/fg3LUnDCLJP8/Os
      6MbXVikOIF2oRc0UuY5YAHVqi3SXG2hnVPBf30PWt5yKNeFxY/qnLedE573CmvUw
      +9C1UpaoToLOVj6GXvgDG+ECtYx78We3ffNOADj4LUYrrduhzVpEVZeh1euXZnqt
      747dhfIg3mAgfFgOiykSop3Sg4rX0bqHuBzZ+8HAQas3TAqAtvHylpTaH4tDaE3k
      /qx5sMjXvmISt43XGZhJv6ONEEdkc7mFq7wx3umgObVPsyLmK1qMIQlbe9LtyFWB
      13lKTUsRZxK/7RNG7UA4jaHf8b5ulFzggF6mBJwrB2u46bMxvGb0tVlMt0i+Yunv
      /w2vWVsxJzkm8KLIpWkGYsJZMIP48h0GbQub3QR6ozDXAzkJOYZt73+cBawpJYY2
      il2ZzYQzgbNTW28CAwEAAaNFMEMwDgYDVR0PAQH/BAQDAgIEMBIGA1UdEwEB/wQI
      MAYBAf8CAQAwHQYDVR0OBBYEFAY093T67LXnkMU7NoTD8eUhPVU9MA0GCSqGSIb3
      DQEBCwUAA4IBgQCDnfZTzmM+mbJZd3wurUAiPIcX9PufYsnkGzeYc7A+cIWpeJBL
      HxUwX+bRZE3VUGILorl/mo9jwFUuCVrwZJDtvDpbGDxfVAkN0UrGBuyvN1+Eg+Ef
      UeE5Pf80wOwz4DlEOX785sZilZIw8iWKpQZyDQoKnZYr/dXOrgotS4R9a36zAGUs
      Jo4ykNHvkNohEDselmpgvYgdEht2gavnaW99J5JOKCPd3zSlQqrjCi4vBsBzLL7i
      BRC5e2IfZ49eCtTpubYfgr9QivJP/kwWJ7kxHOpz8n3ZgRwPuZKZdWzQlWmx49D5
      adQhyEH0eDfX+OB3DkceH2IWFd+YTl6LKFoBFZwVdcZyytw+R/I3A82hREIghYj+
      cRp8gIuzuChTTqRIOiH5m3DZ0S4mcv3Zh3jok/Q8U2n5weh0kIC4ayk/Pxqu5+AY
      qY03bjRywPxqMtaysWfZYLcrNyNezQez9ttR2HFq7NtwD4OlLq9xhmzgFkLVHirM
      VRC29GkGNb23aZs=
      -----END CERTIFICATE-----
  syslog_configuration:
    enabled: false
resource-configuration:
  compilation:
    additional_networks: []
    additional_vm_extensions: []
    elb_names: []
    instance_type:
      id: automatic
    instances: automatic
    internet_connected: false
    swap_as_percent_of_memory_size: automatic
  director:
    additional_networks: []
    additional_vm_extensions: []
    elb_names: []
    instance_type:
      id: automatic
    instances: automatic
    internet_connected: false
    persistent_disk:
      size_mb: automatic
    swap_as_percent_of_memory_size: automatic
vmextensions-configuration: []
vmtypes-configuration: {}

In the ops manager source code:
elsif @director_configuration.blobstore_type == 's3'
              {
                'blobstore_type' => @director_configuration.blobstore_type,
                's3_blobstore_options' => {
                  'endpoint' => @director_configuration.s3_blobstore_options.endpoint,
                  'bucket_name' => @director_configuration.s3_blobstore_options.bucket_name,
                  'signature_version' => @director_configuration.s3_blobstore_options.signature_version,
                  'region' => @director_configuration.s3_blobstore_options.region,
                  'backup_strategy' => @director_configuration.s3_blobstore_options.backup_strategy,
                  'backup_bucket_region' => @director_configuration.s3_blobstore_options.backup_bucket_region,
                  'backup_bucket_name' => @director_configuration.s3_blobstore_options.backup_bucket_name,
                  'enable_signed_urls' => @director_configuration.s3_blobstore_options.enable_signed_urls?,
                  'url_style' => @director_configuration.s3_blobstore_options.url_style
                }
              }

it doesn't look like those values even get returned by the ops manager API. There's not a lot om can do about it if we don't have access.
@ystros might be able to weigh in on something we could do about this here. Maybe there's an endpoint available that we don't know about.

Unfortunately, I'm not sure there's an alternate endpoint that gives this information. I'd consider this a bug in Ops Manager's API, as it violates the usual expected contract for the redacted flag.
I've created a tracker bug for Ops Manager 2.7 onwards, and will discuss more with our PMs soon. https://www.pivotaltracker.com/story/show/172592927

I'm going to close this issue, as there isn't a way for us to get back this information in om. If/when we get information about when the bug gets fixed, we can update this issue with the appropriate OM versions to use.


Feature/console example elasticsearchloggerprovider

Add an example that uses Essential.LoggerProvider.Elasticsearch, a stand alone logger provider that uses ECS. (i.e. not part of a third party logging framework like Serilog or NLog that goes through a bridge/adapter, but a logger provider that connects directly to Microsoft.Extensions.Logging).
The example also includes a docker compose file to get Elasticsearch + Kibana up and running locally, and also demonstrates the use of the Microsoft LoggerMessage for high performance logging.
** NOTE: I am the author of the ElasticsearchLoggerProvider package. **

Have just signed the CLA. Thanks.

https://github.com/sgryphon/essential-logging/tree/master/src/Essential.LoggerProvider.Elasticsearch
Looks amazing! What are your feelings towards getting that into this repository?
I don't know how I feel accepting an example to a lib that's external to this repository.
I would love to go all in on the whole thing or add a call out to your amazing work in our README.
@russcam thoughts?

:broken_heart: Build Failed

Expand to view the summary

Build stats

Build Cause: [Branch indexing]

Start Time: 2020-05-09T00:23:34.169+0000

Duration: 4 min 56 sec (235604)

Commit: defe521aa02f75f877e1e90f290d0e78029d888e

Steps errors
Expand to view the steps failures

Name: Error signal

Description: githubPrCheckApproved: The PR is not allowed to run in the CI yet. (Only users with write permission

Result: FAILURE

Duration: 0 min 0 sec

Start Time: 2020-05-09T00:27:27.542+0000

log

Log output
Expand to view the last 100 lines of log output

[2020-05-09T00:27:22.623Z] Checking out Revision 71893138f047a8e74d16639ac82657b3d6d55b84 (PR-69)
[2020-05-09T00:27:22.725Z] Commit message: "Merge commit 'a5bf899ee42361553962d89f20378d6b8b9f679c' into HEAD"
[2020-05-09T00:27:22.725Z] First time build. Skipping changelog.
[2020-05-09T00:27:22.725Z] Cleaning workspace
[2020-05-09T00:27:22.426Z]  > git config core.sparsecheckout # timeout=10
[2020-05-09T00:27:22.428Z]  > git checkout -f defe521aa02f75f877e1e90f290d0e78029d888e # timeout=15
[2020-05-09T00:27:22.472Z]  > git remote # timeout=10
[2020-05-09T00:27:22.476Z]  > git config --get remote.origin.url # timeout=10
[2020-05-09T00:27:22.486Z] using GIT_SSH to set credentials GitHub user @elasticmachine SSH key
[2020-05-09T00:27:22.488Z]  > git merge a5bf899ee42361553962d89f20378d6b8b9f679c # timeout=10
[2020-05-09T00:27:22.617Z]  > git rev-parse HEAD^{commit} # timeout=10
[2020-05-09T00:27:22.624Z]  > git config core.sparsecheckout # timeout=10
[2020-05-09T00:27:22.629Z]  > git checkout -f 71893138f047a8e74d16639ac82657b3d6d55b84 # timeout=15
[2020-05-09T00:27:22.726Z]  > git rev-parse --verify HEAD # timeout=10
[2020-05-09T00:27:22.729Z] Resetting working tree
[2020-05-09T00:27:22.729Z]  > git reset --hard # timeout=10
[2020-05-09T00:27:22.813Z]  > git clean -fdx # timeout=10
[2020-05-09T00:27:23.424Z] Masking supported pattern matches of $GIT_USERNAME or $GIT_PASSWORD
[2020-05-09T00:27:24.014Z] + git fetch<EMAIL_ADDRESS>+refs/pull/*/head:refs/remotes/origin/pr/*
[2020-05-09T00:27:24.592Z] From https://github.com/elastic/ecs-dotnet
[2020-05-09T00:27:24.592Z]  * [new ref]         refs/pull/1/head  -> origin/pr/1
[2020-05-09T00:27:24.592Z]  * [new ref]         refs/pull/10/head -> origin/pr/10
[2020-05-09T00:27:24.592Z]  * [new ref]         refs/pull/11/head -> origin/pr/11
[2020-05-09T00:27:24.592Z]  * [new ref]         refs/pull/12/head -> origin/pr/12
[2020-05-09T00:27:24.592Z]  * [new ref]         refs/pull/14/head -> origin/pr/14
[2020-05-09T00:27:24.592Z]  * [new ref]         refs/pull/15/head -> origin/pr/15
[2020-05-09T00:27:24.592Z]  * [new ref]         refs/pull/16/head -> origin/pr/16
[2020-05-09T00:27:24.592Z]  * [new ref]         refs/pull/19/head -> origin/pr/19
[2020-05-09T00:27:24.592Z]  * [new ref]         refs/pull/2/head  -> origin/pr/2
[2020-05-09T00:27:24.592Z]  * [new ref]         refs/pull/22/head -> origin/pr/22
[2020-05-09T00:27:24.592Z]  * [new ref]         refs/pull/23/head -> origin/pr/23
[2020-05-09T00:27:24.592Z]  * [new ref]         refs/pull/24/head -> origin/pr/24
[2020-05-09T00:27:24.592Z]  * [new ref]         refs/pull/25/head -> origin/pr/25
[2020-05-09T00:27:24.592Z]  * [new ref]         refs/pull/26/head -> origin/pr/26
[2020-05-09T00:27:24.592Z]  * [new ref]         refs/pull/27/head -> origin/pr/27
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/28/head -> origin/pr/28
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/33/head -> origin/pr/33
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/34/head -> origin/pr/34
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/35/head -> origin/pr/35
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/36/head -> origin/pr/36
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/37/head -> origin/pr/37
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/38/head -> origin/pr/38
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/39/head -> origin/pr/39
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/4/head  -> origin/pr/4
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/40/head -> origin/pr/40
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/43/head -> origin/pr/43
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/44/head -> origin/pr/44
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/45/head -> origin/pr/45
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/47/head -> origin/pr/47
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/48/head -> origin/pr/48
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/49/head -> origin/pr/49
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/5/head  -> origin/pr/5
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/50/head -> origin/pr/50
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/51/head -> origin/pr/51
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/52/head -> origin/pr/52
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/53/head -> origin/pr/53
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/57/head -> origin/pr/57
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/59/head -> origin/pr/59
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/6/head  -> origin/pr/6
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/60/head -> origin/pr/60
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/63/head -> origin/pr/63
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/65/head -> origin/pr/65
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/66/head -> origin/pr/66
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/67/head -> origin/pr/67
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/69/head -> origin/pr/69
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/7/head  -> origin/pr/7
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/70/head -> origin/pr/70
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/74/head -> origin/pr/74
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/75/head -> origin/pr/75
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/8/head  -> origin/pr/8
[2020-05-09T00:27:24.593Z]  * [new ref]         refs/pull/9/head  -> origin/pr/9
[2020-05-09T00:27:24.593Z]  * [new tag]         1.2.0-alpha1      -> 1.2.0-alpha1
[2020-05-09T00:27:24.593Z]  * [new tag]         1.4.0             -> 1.4.0
[2020-05-09T00:27:24.593Z]  * [new tag]         1.4.0-beta1       -> 1.4.0-beta1
[2020-05-09T00:27:24.593Z]  * [new tag]         1.4.1             -> 1.4.1
[2020-05-09T00:27:24.593Z]  * [new tag]         1.4.2             -> 1.4.2
[2020-05-09T00:27:24.593Z]  * [new tag]         1.4.3             -> 1.4.3
[2020-05-09T00:27:24.593Z]  * [new tag]         1.4.4             -> 1.4.4
[2020-05-09T00:27:24.593Z]  * [new tag]         1.5.0             -> 1.5.0
[2020-05-09T00:27:25.261Z] + git rev-parse HEAD
[2020-05-09T00:27:25.612Z] + git rev-parse HEAD
[2020-05-09T00:27:25.910Z] + git rev-parse origin/pr/69
[2020-05-09T00:27:25.943Z] [INFO] githubEnv: Found Git Build Cause: pr
[2020-05-09T00:27:26.360Z] Masking supported pattern matches of $GITHUB_TOKEN
[2020-05-09T00:27:27.326Z] [WARN] githubApiCall: The REST API call https://api.github.com/repos/elastic/ecs-dotnet/pulls/69/reviews return 0 elements
[2020-05-09T00:27:27.344Z] [INFO] githubPrCheckApproved: Title: Feature/console example elasticsearchloggerprovider - User: sgryphon - Author Association: FIRST_TIME_CONTRIBUTOR
[2020-05-09T00:27:28.512Z] Stage "Sanity checks" skipped due to earlier failure(s)
[2020-05-09T00:27:28.535Z] Stage "Parallel" skipped due to earlier failure(s)
[2020-05-09T00:27:28.563Z] Stage "Linux" skipped due to earlier failure(s)
[2020-05-09T00:27:28.564Z] Stage "Windows" skipped due to earlier failure(s)
[2020-05-09T00:27:28.572Z] Failed in branch Linux
[2020-05-09T00:27:28.585Z] Stage "Windows" skipped due to earlier failure(s)
[2020-05-09T00:27:28.608Z] Stage "Windows" skipped due to earlier failure(s)
[2020-05-09T00:27:28.630Z] Failed in branch Windows
[2020-05-09T00:27:29.081Z] Running on Jenkins in /var/lib/jenkins/workspace/gent-dotnet_ecs-dotnet-mbp_PR-69
[2020-05-09T00:27:29.323Z] [INFO] getVaultSecret: Getting secrets
[2020-05-09T00:27:29.379Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2020-05-09T00:27:30.031Z] + chmod 755 generate-build-data.sh
[2020-05-09T00:27:30.031Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-dotnet/ecs-dotnet-mbp/PR-69/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-dotnet/ecs-dotnet-mbp/PR-69/runs/2 FAILURE 235604
[2020-05-09T00:27:30.582Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-dotnet/ecs-dotnet-mbp/PR-69/runs/2/steps/?limit=10000 -o steps-info.json

https://github.com/sgryphon/essential-logging/tree/master/src/Essential.LoggerProvider.Elasticsearch
Looks amazing! What are your feelings towards getting that into this repository?

I would be more than happy to donate/migrate my code to the Elastic project, if you would like it.
The current code is under LGPL, because I like to encourage open source, but happy to re-licence under Apache to be consistent with the rest of your project / sign over licence under your CLA to make it easier to manage.
If you are interested, I can merge across the code in a branch, and then update the assembly name to fit your project (Elastic.CommonSchema.LoggerProvider ?)
Once it is merged, I would put a note on the other project to refer to here.

Closing this as basically merged, with changes


feat(getting-started-etcd): more clarity around reading etcd in a container

Addresses https://github.com/coreos/docs/issues/274

The instruction doesn't worked for me.
There is an error in the document, "It's normally <IP_ADDRESS> and using it is as easy as replacing...."
I had to use the gateway ip of container is 10.240.0.*. to get curl message to work.


SBGN API

Notes:

given the large amount of methods this extension will register, a warning about potential conflicts will be needed

selector documentation for the underlying implementation of sbgn methods

read the sbgn spec and come up with more exact name mapping for methods:  e.g neighbours in the context of the different arrows, neighbours in the different context of sbgn nodes, etc.

This ticket is not that relevant given that this package will just deal with exporting a sbgn stylesheet


Cannot use no-style-please on Jekyll above 3.8.7

All version of no-style-please on Rubygems except for 0.1.0 require Jekyll 3.8.7. As a result, 0.1.0 is installed on Jekyll 4 & above, which has a bug of a missing {{ content }} block in the home layout.

I try to stay compatible with GitHub Pages (see here], so right now this theme is running Jekyll v3.9.0.
Hopefully GitHub Pages will support Jekyll 4 soon.

looks like its out of sync now.  I am using 226 which seems to be the latest version of github-pages.
Bundler could not find compatible versions for gem "jekyll":
  In Gemfile:
    github-pages (~> 226) was resolved to 226, which depends on
      jekyll (= 3.9.2)

    no-style-please was resolved to 0.1.0, which depends on
      jekyll (~> 4.1)
Bundler could not find compatible versions for gem "jekyll-seo-tag":
  In Gemfile:
    github-pages (~> 226) was resolved to 226, which depends on
      jekyll-seo-tag (= 2.8.0)

    no-style-please was resolved to 0.4.7, which depends on
      jekyll-seo-tag (~> 2.7.1)

looks like its out of sync now. I am using 226 which seems to be the latest version of github-pages.
Bundler could not find compatible versions for gem "jekyll":
  In Gemfile:
    github-pages (~> 226) was resolved to 226, which depends on
      jekyll (= 3.9.2)

    no-style-please was resolved to 0.1.0, which depends on
      jekyll (~> 4.1)
Bundler could not find compatible versions for gem "jekyll-seo-tag":
  In Gemfile:
    github-pages (~> 226) was resolved to 226, which depends on
      jekyll-seo-tag (= 2.8.0)

    no-style-please was resolved to 0.4.7, which depends on
      jekyll-seo-tag (~> 2.7.1)

Im having the same problem.

You're probably using version 0.1.0 of no-style-please. Try to use 0.4.7 instead, please :)

I'm getting the same issue as @sockbot, exact same conflict in versions (although now we're on version 232 of github-pages).

This compatibility issue has been addressed in #94.

As of now, this update hasn't been published to RubyGems. One workaround is to reference this theme in your Gemfile as:
gem 'no-style-please', git: 'https://github.com/riggraz/no-style-please', branch: 'master'


Integrate SSE Sidecar

🔥 Summary
Integrate SSE Sidecar with the middleware #278
😤 Problem / Goals

Create REST API endpoint for Sidecar

🤓 Solution

🗒 Additional Notes

As discussed with @gyroflaw there are another problems that we need to address:
https://user-images.githubusercontent.com/3756160/214054657-9ce1ea34-05ca-4f96-92e0-5b481404f5cd.mov

strange fetching problems on /blocks page that happens non-deterministic (but especially when I click load more > 1 time so there are more then 10 records on screen)
sorting again stopped working as expected - if I click on sort and select ascending it not always work (especially if I have > 10 records on screen)
/peers screen needs to be updated - it misses info about uptime now and isAlive


Front page versions do not work (they are older versions)

Describe the bug
The readme in the repo point to 2 versions; neither link works.
To Reproduce
Steps to reproduce the behavior:

Go to the github repo
Click on either version link (i.e. 4.17)
Note you get a 404

Expected behavior
The workshop page for that version

Fixed in repo, also fixed in GitHub Actions


same word used multiple times in one run

I played a game:

The Game (click to expand)
   #####Welcome player!#####
Your score is currently 0. You require 5 points to leave and continue with your life...

"In a state of high anticipation, excitement, or interest."

To which of the following options does this definition pertain?
      wen
      assiduously
      incongruously
      agog

Please enter an integer from 1 - 4
>>> 4
Excellent - you are correct!
Your score is currently 1. You require 5 points to leave and continue with your life...

"(interrogative) At what time? At which time? Upon which occasion or circumstance? Used to introduce direct or indirect questions about time."

To which of the following options does this definition pertain?
      agog
      incongruously
      chary
      wen

Please enter an integer from 1 - 4
>>> 4
Excellent - you are correct!
Your score is currently 2. You require 5 points to leave and continue with your life...

"The finer and more volatile parts of a substance, separated by a solvent; an extract of a part of the substance of a body communicated to the solvent."

To which of the following options does this definition pertain?
      stevedores
      paeans
      striae
      tinctures

Please enter an integer from 1 - 4
>>> 3

For shame... The correct answer was: tinctures
Your score is currently 2. You require 5 points to leave and continue with your life...

"Chaotic, disordered, confused; also, incoherent, rambling."

To which of the following options does this definition pertain?
      piqued
      inchoate
      agog
      liminal

Please enter an integer from 1 - 4
>>> 2
Excellent - you are correct!
Your score is currently 3. You require 5 points to leave and continue with your life...

"To add variety to something."

To which of the following options does this definition pertain?
      variegated
      posset
      scree
      dun

Please enter an integer from 1 - 4
>>> 1
Excellent - you are correct!
Your score is currently 4. You require 5 points to leave and continue with your life...

"In a state of high anticipation, excitement, or interest."

To which of the following options does this definition pertain?
      wen
      assiduously
      chary
      agog

Please enter an integer from 1 - 4

In this game I got the same definition twice (1st go - agog; 6th go - agog). This seems undesirable.
In particular, it seems undesirable to repeat a word that was successfully guessed.

Partially solved as now sampling means less repition of words. Leaving open in order to represent further issue:
"In particular, it seems undesirable to repeat a word that was successfully guessed."

Due to ability to save player progress between games and sampling alteration, this is considered fixed. Any repetition that (by chance) occurs now should not impact user with a wider vocab library to draw from


Update image generation process with more consistent naming

Signed-off-by: Nick Young<EMAIL_ADDRESS>
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This PR adds some tooling around building admission-server images, so that we end up with:

all images built and pushed are labelled with the standard Prow version string, like v20220209-v0.4.0-114-g36b4551.
Images built for a semver branch or tag are also labelled with the branch or tag name
Images built for a semver branch or tag that don't have a prerelease marker (like -rc2, -beta1 or similar are labelled latest.

This will mean that we can now generate consistent manifest YAML for the admission-server when we release a bundle by tagging a branch with a semver tag, since the images will be available by v0.4.1 or whatever.
I'll leave changing out the build to a multiarch one (#627) for another PR. Having it in a script should make that easier though.
Which issue(s) this PR fixes:
Updates #916
Does this PR introduce a user-facing change?:
NONE

I think I've got the interactions between Prow, cloud build, and our Makefile correct, but looking forward to reviews around that. I'm not sure how to test there.

I spoke to a couple of other VMware folks, and they were both of the "suck it and see" school when it comes to testing these changes.
I made sure that this change doesn't need any test-infra changes, so, assuming that cloudbuild.yaml works as advertised, it all should just work (tm).

Okay, some testing of the script itself.
tl;dr The script appears to work.
First, I changed all the actual docker commands to echo the command instead:
echo docker build --build-arg COMMIT=${BINARY_VERSION} --build-arg TAG=${VERSION_TAG} \
  			-t ${REGISTRY}/admission-server:${GIT_TAG} .

echo docker push ${REGISTRY}/admission-server:${GIT_TAG}

Now, let's check the various combinations of variables. Each of these should set the binary version in the docker build command to $COMMIT.
This combination should push only the $GIT_TAG label.
export REGISTRY=gcr.io/k8s-staging-gateway-api
export GIT_TAG=v0.4.0-rc1-210-gcd7d431
export BASE_REF=master
export COMMIT=$(git rev-parse --short HEAD)
./hack/build-and-push.sh

gives
docker build --build-arg COMMIT=cd7d431 --build-arg TAG=v0.4.0-rc1-210-gcd7d431 -t gcr.io/k8s-staging-gateway-api/admission-server:v0.4.0-rc1-210-gcd7d431 .
docker push gcr.io/k8s-staging-gateway-api/admission-server:v0.4.0-rc1-210-gcd7d431

If $BASE_REF is semver with a prerelase marker, we should get the semver set as the change, but no :latest label on the image.
export REGISTRY=gcr.io/k8s-staging-gateway-api
export GIT_TAG=v0.4.0-rc1-210-gcd7d431
export BASE_REF=v0.5.0-rc1
export COMMIT=$(git rev-parse --short HEAD)
./hack/build-and-push.sh

gives
docker build --build-arg COMMIT=v0.5.0-rc1 --build-arg TAG=v0.5.0-rc1 -t gcr.io/k8s-staging-gateway-api/admission-server:v0.4.0-rc1-210-gcd7d431 .
docker push gcr.io/k8s-staging-gateway-api/admission-server:v0.4.0-rc1-210-gcd7d431
docker tag gcr.io/k8s-staging-gateway-api/admission-server:v0.4.0-rc1-210-gcd7d431 gcr.io/k8s-staging-gateway-api/admission-server:v0.5.0-rc1
docker push gcr.io/k8s-staging-gateway-api/admission-server:v0.5.0-rc1

If $BASE_REF is semver with no prerelase marker, we should get the semver set as the change, with a :latest label on the image as well.
export REGISTRY=gcr.io/k8s-staging-gateway-api
export GIT_TAG=v0.4.0-rc1-210-gcd7d431
export BASE_REF=v0.5.0
export COMMIT=$(git rev-parse --short HEAD)
./hack/build-and-push.sh

gives
docker build --build-arg COMMIT=v0.5.0 --build-arg TAG=v0.5.0 -t gcr.io/k8s-staging-gateway-api/admission-server:v0.4.0-rc1-210-gcd7d431 .
docker push gcr.io/k8s-staging-gateway-api/admission-server:v0.4.0-rc1-210-gcd7d431
docker tag gcr.io/k8s-staging-gateway-api/admission-server:v0.4.0-rc1-210-gcd7d431 gcr.io/k8s-staging-gateway-api/admission-server:v0.5.0
docker push gcr.io/k8s-staging-gateway-api/admission-server:v0.5.0
docker tag gcr.io/k8s-staging-gateway-api/admission-server:v0.4.0-rc1-210-gcd7d431 gcr.io/k8s-staging-gateway-api/admission-server:latest
docker push gcr.io/k8s-staging-gateway-api/admission-server:latest

Now, to test actually building and pushing:
export REGISTRY=docker.io/youngnick
export GIT_TAG=v0.4.0-rc1-210-gcd7d431
export BASE_REF=v0.5.0
export COMMIT=$(git rev-parse --short HEAD)
./hack/build-and-push.sh

gives
Sending build context to Docker daemon  92.86MB
Step 1/12 : FROM golang:1.16 AS build-env
 ---> 1390628e9890
Step 2/12 : RUN mkdir -p /go/src/sig.k8s.io/gateway-api
 ---> Using cache
 ---> 3a9ddf207c7c
Step 3/12 : WORKDIR /go/src/sig.k8s.io/gateway-api
 ---> Using cache
 ---> 0545b77e58ba
Step 4/12 : COPY  . .
 ---> Using cache
 ---> 642635845bfc
Step 5/12 : ARG TAG
 ---> Using cache
 ---> ba71ac6dabb7
Step 6/12 : ARG COMMIT
 ---> Using cache
 ---> 2a733e843eb2
Step 7/12 : RUN CGO_ENABLED=0 GOARCH=amd64 GOOS=linux go build -a -o gateway-api-webhook       -ldflags "-s -w -X main.VERSION=$TAG -X main.COMMIT=$COMMIT" ./cmd/admission
 ---> Using cache
 ---> 69c7836b37cf
Step 8/12 : FROM gcr.io/distroless/static:nonroot
 ---> 5bc88c360b3e
Step 9/12 : WORKDIR /
 ---> Using cache
 ---> d4f8dcf1018d
Step 10/12 : COPY --from=build-env /go/src/sig.k8s.io/gateway-api/gateway-api-webhook .
 ---> Using cache
 ---> 062d45582ffa
Step 11/12 : USER 65532
 ---> Using cache
 ---> 95ef5fcfce26
Step 12/12 : ENTRYPOINT ["/gateway-api-webhook"]
 ---> Using cache
 ---> 189d27b922e4
Successfully built 189d27b922e4
Successfully tagged youngnick/admission-server:v0.4.0-rc1-210-gcd7d431
The push refers to repository [docker.io/youngnick/admission-server]
34bca3bf2868: Pushed
5b1fa8e3e100: Pushed
v0.4.0-rc1-210-gcd7d431: digest: sha256:c3e2a245095f1e97c097b7345101eafda521f1819cae75a62700c192c04ffabd size: 738
The push refers to repository [docker.io/youngnick/admission-server]
34bca3bf2868: Layer already exists
5b1fa8e3e100: Layer already exists
v0.5.0: digest: sha256:c3e2a245095f1e97c097b7345101eafda521f1819cae75a62700c192c04ffabd size: 738
The push refers to repository [docker.io/youngnick/admission-server]
34bca3bf2868: Layer already exists
5b1fa8e3e100: Layer already exists
latest: digest: sha256:c3e2a245095f1e97c097b7345101eafda521f1819cae75a62700c192c04ffabd size: 738

I had a crack at replicating what Prow does with gcloud builds submit, but Prow does some extra magic with pulling the source for you, and I have no idea where to start there.
overall tl;dr - I'm confident this will do what it intends.

Thanks!
/lgtm


[BugFix] Fix incorrect error message

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

@Mergifyio backport branch-3.0

[FE PR Coverage Check]
:disappointed: fail : 0 / 1 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/common/util/PropertyAnalyzer.java
0
1
00.00%
[392]


onchange event fired multiple times

Prerequisites
Please answer the following questions for yourself before submitting an issue.

[x] I am running the latest version
[x] I checked the documentation and found no answer
[x] I checked to make sure that this issue has not already been filed
[x] I'm reporting the issue to the correct repository (for multi-repository projects)

Expected Behavior
When I have an input value with the onchange event being listened to it should fire off once when changed.
Current Behavior
When I click the input value with the onchange event being listened to it started firing off continually.
Failure Information (for bugs)
This happens when there is an input element inside a form.
I believe it is something to do with the material-kit.min.js script because when that script isn't included it works fine.
Steps to Reproduce

add a form element
add an input element inside form
add onchange event to the input element that writes to the console
open console and click the input element

<form>
    <input type="text" onchange="console.log('on change fired')" />
</form>

here is a plunker to reproduce: https://plnkr.co/edit/Wls1hWw5jlOChqwj7RNU?p=preview

Hello @Beastw00d,
Thank you for using our products, this issue it's from the Bootstrap Material Design library so you need to open an issue on their repository. I reproduce this issue in the video from below to see that it's broken on their product.
onChange.zip(video)
All the best,
Stefan

I think this should be bundled by default with the materialkit js library. Especially in cases when the layout has forms with too many input fields and change event handlers. Hey Creativetim team: may I PR on this? 😺


fixedHeaderOptions not working when selectableRows='none'

Thanks for the feature, it is really useful.
Expected Behavior
When selectableRows == 'none' the first column (whatever it is) should be 'sticky' when setting
fixedHeaderOptions: {
     xAxis: true,
     yAxis: true
}

Current Behavior
The first column is not sticky because it is missing the z-index: 110 css property.
Steps to Reproduce (for bugs)
Take the fixedHeaderOptions demo, add selectableRows == 'none' to options and inspect the first column th/td. The z-index is missing.
Your Environment

Tech
Version

Material-UI
3.9.2

MUI-datatables
2.13.0

React
16.8.4

browser
Chrome 78

Hey @GuyShaanan, I'm having difficulty reproducing. Modifying the simple example to include the options (and enough data to generate scroll bars), I see the following:

Can you create a codesandbox to help me reproduce the problem?

Your gif shows it perfectly- the "Name" column which is the first column isn't "fixed" in place. It scrolls when you scroll horizontaly, when it should actually stay in place.

Actually, that behavior is intentional, and as far as I can tell, it has always worked that way. The fixed y-axis behavior means that whatever column you are over is the column header that shows. It will not show a "Name" header once you've scrolled past "Name" and are looking at "Title." I believe that doing otherwise would cause more confusion, as the header would not correspond to the column that shows. If you remove the fixed y-axis behavior, you will not see the header stick to the column, it will just scroll past. Maybe that's the behavior you're looking for?

I updated the original message to be more readable:
When you open the demo, the first column is the row selection checkboxes.
When you scroll horizontally, that first column stays in view as you scroll. Thats OK.
Now set selectedRows: 'none'. Now the "Name" column is the first column,
Now when you scroll horizontally, that first column doesn't stay in view as you scroll. Thats the problem.
Am I misinterpreting the yAxis feature? That stickiness of the column header is a known feature and I'm not referring to it in this ticket).
Thanks!

Hopefully this clears it up. The intended behavior of xAxis is as follows:

With selectable rows on and xAxis on, the whole column of checkboxes is horizontally sticky, and stays in view as you scroll horizontally
With selectable rows off and xAxis on only the header name is horizontally sticky, but as you scroll horizontally, the header name will change to match the column that is visible so that you do not see a header name above a column that would be incorrect
With selectable rows on and xAxis off, the checkboxes are not sticky. They do not stay in view as you scroll horizontally
With selectable rows off and xAxis off, the header is not horizontally sticky, and will not stay in view as you scroll horizontally

To test the behavior of these, you need enough columns and small enough view to generate horizontal scroll bars. In my testing, everything works here exactly as intended.

Great, thanks, that clears the issue.
But- the behavior it too unpredictable (and hard to infer from the documentation). The combination of these two- seemingly unrelated- options (selectableRows and fixedHeaderOptions) results in too many different UI behaviors.
Also- why would it make sense to only make the checkboxes column sticky, but not the first column when selectableRows == 'none'? (which is what #236 asks)

Agreed, it's not clear from the API that selectableRows would alter the behavior. With "fixed header" the natural expectation would be that it affects only the header, which it does, except in cases where we have selectable rows. I think that distinction exists just because the utility when we have selectable rows is really high. However, I'm open to suggestions for ways to rename/clear up the API around this.

Just an FYI, this bug is still present in the table: https://github.com/gregnb/mui-datatables/issues/900
I was about to submit a PR to fix it (I have it fixed in my mui-dt repo), but I noticed the API change. The bug described in that ticket is a bad bug, the table does not work right in "scroll" mode in Safari. Because of how "position: sticky" works in Safari, I don't think you can achieve all of the modes you described above.
I would recommend a partial revert of the API change. Instead of discarding fixedHeader, I'd change it to only govern the stickiness of the header, and then add an option called "fixedLeft" that defaulted to true that governed if the select column was sticky.
Any changes to this really should be tested in Safari on a Mac, since the implementation of "sticky" is different in that browser. Also, if you have an iPhone, you can use Chrome and see the same bug listed in the ticket I mentioned.

I just put in a PR (https://github.com/gregnb/mui-datatables/pull/1088) to fix https://github.com/gregnb/mui-datatables/issues/900 and to allow for an optional fixed header and optional fixed select column.

Hi,
any news on this one? I do have the same problem and this fix would save my day...
Regards.


Dicovery: The runtime discovery based clients have on windows, compared to linux, a mich higher call overhead.

This is very odd, and might stem from compiler differences wehen compiling under windows and linux. Godbolt might be able to help here.

After having restructured the project internal layout, the penatily on using the runtime detection on windows is only around 7% compared to linux. I don't think we can optimize this better than it's now. This problem also vanishes of course, once the enabling the needed target features statically at compile time.


feat(protocol-engine): ProtocolEngine ProtocolContextInterface implements load labware

Overview
The ProtocolEngine accepts a LoadLabwareRequest command.
Acceptance Criteria

[ ] ~load_labware method in ProtocolContextInterface derived class created in #7323 sends LoadLabwareRequest command to ProtocolEngine.~ This acceptance criteria moved to #7390
[ ] Return an instance of LabwareInterface defined in #7332

This ticket can be closed, right?

Oops, yeah. I must've messed up the autoclose comment or somrthing


Implement Moussu Picchu stages

Similar to WWRift, the Wind/Rain levels in MoPi affect mouse populations/attraction proportions, and are located at user["quests"]["QuestMoussuPicchu"]["elements"]["wind/rain"]["level"]. Not sure how you'd implement this but it's vital for my tools 😀
There are 5 levels and 25 combinations (pasted below for reference):

none-none (Gouda / SB+ / GG)
none-low (Windy / Rainy / Dragonvine)
none-medium
none-high
none-max
low-none
low-low
low-medium
low-high
low-max
medium-none
medium-low
medium-medium
medium-high
medium-max
high-none
high-low
high-medium
high-high
high-max
max-none
max-low
max-medium
max-High
max-max (Ful'Mina 100% Dragonvine)

done

@DevJackSmith
Revised unique stages.
None (Gouda / SB+ / GG)

Nightshade Flower Girl, Nightshade Maiden, Spore Salesman, Breeze Borrower, Windy Farmer, Cloud Collector, Rainwater Purifier, Homeopathic Apothecary

Wind (Windy Cheese)

Low (Wind Watcher + Charming Chimer)
Medium (Fluttering Flutist + Cycloness)
High (Cycloness + Wind Warrior)
Max (Wind Warrior = 100%)

Rain (Rainy Cheese)

Low (Rain Collector + Rain Wallower)
Medium (Rain Summoner + Monsoon Maker)
High (Monsoon Maker + Rainmancer)
Max (Rainmancer = 100%)

Storm (Dragonvine Cheese)

Low (Thunder Strike + Violet Stormchild)
Medium (Thunderlord + Thundering Watcher)
High (Thundering Watcher + Dragoon + Ful'Mina)
Max (Ful'Mina = 100%)

By none you mean Any. Because they are not limited by no wind, and no rain. And by storm you mean both levels are at least that high, but one of them could be higher?

Yup!


SEO Testing - Images on the homepage have alt attributes

Description: Verify that images on the homepage have alt attributes.
Preconditions: The website https://oportunitatisicariere.ro/ is live and accessible.

Step 2: Navigate to https://oportunitatisicariere.ro/).
Expected Result: All 'img' tags should have alt attributes with descriptive text.

Step 3:	Check the 'img' tags for the presence of alt attributes.
Expected Result: All 'img' tags should have alt attributes with descriptive text.


Scanning of composite types -- is it possible?

What do you want to change?
I've been trying to solve a problem and haven't been able to find an elegant way of doing it.
Here is what I am trying to do (using postgres with pgx v5):
I have some table
CREATE TABLE  foos (
    id BIGSERIAL PRIMARY KEY,
    title TEXT,
    description TEXT
 );

And I want to track the history, so I created  a trigger:
CREATE TABLE IF NOT EXISTS foos_history
(
   id           BIGSERIAL NOT NULL,
   foo_id BIGINT NOT NULL,
   changed_at   TIMESTAMP DEFAULT timezone('utc', now()) NOT NULL,
   new_value    foos,
   operation    TEXT NOT NULL
);

CREATE INDEX IF NOT EXISTS idx_id_time ON foos_history (foo_id, changed_at);
CREATE INDEX IF NOT EXISTS idx_time_id ON foos_history (changed_at, foo_id);

CREATE OR REPLACE FUNCTION foos_history_func() RETURNS TRIGGER AS
$foo_history$
BEGIN
   IF (tg_op = 'DELETE' OR tg_op = 'UPDATE') THEN
       INSERT INTO foos_history (foo_id, changed_at, new_value,
                                       operation)
       SELECT old.id, timezone('utc', now()), new, tg_op;
   ELSEIF (tg_op = 'INSERT') THEN
       INSERT INTO foos_history (foo_id, changed_at, new_value,
                                       operation)
       SELECT new.id, timezone('utc', now()), new, tg_op;
   END IF;
   RETURN NULL; -- this is an AFTER trigger. Return result ignored.
END;
$foo_history$ LANGUAGE plpgsql;

-- NOTE: TRUNCATE cannot be triggered on with a row level trigger
-- and will not be saved in history currently.
CREATE TRIGGER foos_history_trigger
   AFTER INSERT OR UPDATE OR DELETE
   ON foos
   FOR EACH ROW
EXECUTE FUNCTION foos_history_func();

In the foos_history table, the new_value is the composite foos type which is implicitly defined by the foos table. https://www.postgresql.org/docs/current/rowtypes.html
I wanted to generate query that would allow me to read the history table:
-- name: ListFoosHistory :many
SELECT * FROM foos_history WHERE
    (sqlc.narg(filter_id)::bigint IS NULL OR sqlc.narg(filter_id)::bigint = foo_id)
    AND (sqlc.narg(start_timestamp)::timestamp IS NULL OR changed_at >= sqlc.narg(start_timestamp)::timestamp)
    AND (sqlc.narg(end_timestamp)::timestamp IS NULL OR changed_at <= sqlc.narg(end_timestamp)::timestamp)
ORDER BY
    id
LIMIT @limit_
OFFSET @offset_
;

I tried overriding the type of new_value to be a foo in my sqlc.yaml:
          - column: 'foos_history.new_value'
            go_type:
              type: '*Foo'

But the generated code doesn't know how to map the text representation of a foo composite into a golang Foo struct. I don't see any good way to do that without manually writing a scanner interface for Foo that works from the composite text interface. (though that would be brittle, I would love to be able to generate it somehow).
For reference, the error I get back from sqlc is:
cannot scan unknown type (OID 16396) in text format into **db.Foo

I know pgxtypes has https://pkg.go.dev/github.com/thoohv5/pgx/pgtype#CompositeIndexScanner and https://pkg.go.dev/github.com/thoohv5/pgx/pgtype#CompositeFields but documentation is light, without much discussion the web that I could find. Another option I thought was to use postgres inheritance rather than embedding the field, but I don't think that would be as elegant.
Would appreciate any thoughts.
What database engines need to be changed?
PostgreSQL
What programming language backends need to be changed?
Go

Looks like this is sort of a duplicate of #2760. I'll close this so the discussion can be centralized.


⚠ ClamAV has degraded performance

In 181e432, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 200 ms

Resolved: ClamAV performance has improved in 7bcf28c.


Enhance: Support insert a single bean param, Support select sth in #{array|collection}

support sql in query with whole array or collection,such as: "select * from Users where tag in(#{tagsCollectionOrArray})"

2 )support insert a whole bean,such as "insert info Users(name,pasw) Values(#{user})" Instead Of "insert info Users(name,pasw) Values(#{user.name}, #{user.pasw})"

Hi @houkx ,
Thank you for the PR, but we cannot accept this change.
1) has been requested several times, but <foreach /> is much more flexible and easy enough to use.
Regarding 2), the use case is quite limited, I think. If you need this for your project, check out @InsertProvider.
http://www.mybatis.org/mybatis-3/java-api.html


[Sync] kserve/modelmesh-serving-v0.11.0-rc0 to main branch

Description

This is Release Sync. Detail information is here:

Sync Date:
kserve/modelmesh release issue: https://github.com/kserve/modelmesh-serving/pull/390
kserve/rest-proxy release version : v0.11.0-rc0
odh/rest-proxy branch: main

How Has This Been Tested?

Tested it with this ticket: https://github.com/opendatahub-io/modelmesh-serving/pull/107
Merge criteria:

[ ] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[X] The developer has manually tested the changes and verified that the changes work

/retest

openshift ci have a problem so it needs to be merged manually but a new fast image was built and tested by this PR:https://github.com/opendatahub-io/modelmesh-serving/pull/107


Website and Form Color Selection Improvement

The design of the website is nice but it can be improved by making some color adjustments. Through some color modification and styling, I can make this website and form look even better.
I want to work on this issue as a part of GSSoC-23.

I want to work in this issue ,Please give me a chance .I am a contributor in GSSOC'23 @Pallavi-star2002


Improve documentation on path option, or rename

It'd be nice if the annotations could be limited to files that changed or were added as part of the PR. If understand correctly right now, I can only limit the action to a single folder (path), or filter files out with globs (skip) which does not quite cover this.
If you are running with only_warn then its possible you'll end up with the same unaddressed misspells being annotated on every pull request (which could become quite noisy in a large monorepo).

You should be able to pass in multiple paths (you can on codespell CLI), so I guess it's a case of whether you can generate a list of changed files and pass it into an action. However this doesn't guarantee the outstanding issues won't be elsewhere in the files you're checking.
Given codespell doesn't really care about context, generating a list of the added/changed lines and checking them for typos might be best, perhaps combined with loads of blank padding in the files so they kept the same line numbers. Or probably more simply a filter to run on the output of codespell which removes warnings/errors on lines which weren't in the PR. This feels like something that may have been or could be solved more generally for annotations, rather than in an individual tool like this.

See also https://github.com/TrueBrain/actions-flake8/issues/35 although heed my warning about other breakages within those files.

You should be able to pass in multiple paths (you can on codespell CLI), so I guess it's a case of whether you can generate a list of changed files and pass it into an action.

Interesting, the documentation led me to believe it would be a single path since it says: "Indicates the path to run codespell in."
Is "path" really just the [files [files ...]] in the codespell usage? I'll experiment with it now.

Perhaps the documentation could be updated to make this clearer? I'd even go so far as to rename the argument from path to files in a major release. 😄

@robin-wayve can you please show an example of how you pass changes files in the current pr to this action?

@Justin-JHG you probably want an action that checks out the pull request HEAD instead of a merge commit and then do a git-diff --name-only against the target branch (I can't remember what the Github Actions provided variable for that is).
Putting that list of files into an environment variable is one way to pass them to the codespell action.
echo "PR_CHANGED_FILES=$(git diff --name-only ...)" >> $GITHUB_ENV

and then
path: ${{ env.PR_CHANGED_FILES }}

Thank you @robin-wayve 👍
I figured out the same and posted my full workflow in #65


forced var

Describe the rule you'd like to see added and to what rule set
When 'var' can be used (not as Object/dynamic), it should not allow explicit  type declaration:
Example:
Bad:
String a= "";
Map m=<String, dynamic>{};
goog:
var a="";
var m=<String, dynamic>{};

Does the omit_local_variable_types  lint accomplish what you are looking for?

Oh sorry, you opened this issue in package:lints, not the linter repository itself.
I don't think package:lints will include this lint by default, as some users prefer to always explicitly type variables. You can always enable extra lints yourself though in your project's analysis_options.yaml file or choose a different prebuilt set which enables it by default.

I think I mentioned it in a wrong thread. I didn't know about omit_local_variable_types

I think I mentioned it in a wrong thread. I didn't know about omit_local_variable_types


Tables remove sync stack and tracing context flags

Fixes #41910

API change check
API changes are not detected in this pull request.


BIGTOP-2317. Add smoke tests for QFS

This change adds some simple testing for qfs running under hadoop. The bigtop
repository already has smoke tests for the hadoop mapreduce framework. It simply
runs the examples through the hadoop infrastructure and ensures that the output
is valid and expected files within the filesystem are present. This change
modifies the bigtop code to support running the same examples but using qfs as
the backend filesystem. This is done through dynamically supplying the hadoop
command to use. In the hadoop hdfs mapreduce scenario, we use the standard
hadoop command that uses hdfs as the backend filesystem. In the hadoop qfs
mapreduce scenario, we use the hadoop-qfs command that uses qfs as the backend
filesystem. The qfs tests simply reference the mapreduce tests and tell it to
use the hadoop-qfs command instead of the hadoop command.
I have tested this works by running the qfs smoke tests using the BigTop
provisioner under docker. The build and tests pass without issue.

This change was committed to the bigtop repository already. Closing out the pull request.


CORE-353 - Handle CERT downtime for network data

Closes CORE-353

:tada: This PR is included in version 4.8.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


cant add tiles

hia ,
just a quick one I can't add any tiles might just be me but whenever I select a tile I want the page just says "Uh Oh something broke :(" .
also, i installed it via add-ons store in Hassio

This should be fixed when we release v1.0, please try again once that version is released. Keep an eye on this repository, or the Home Assistant community forums for an announcement!


initial a test plan

Signed-off-by: U-WBIxa22633<EMAIL_ADDRESS>this is a template of IEEE 829 test plan. we can start review and add contents based on this

Can you please convert this to RST (restructuredtext)?

@nashif can you have a review for the updated patch?

@nashif update style

@hakehuang It would be nice to move this under doc and integrate it into the documentation build. Test it with 'make html' in the doc/ directory.

@nashif  move to doc folder. and below is the make html log

Running Sphinx v1.6.5
making output directory...
loading pickled environment... not yet created
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 2 source files that are out of date
updating environment: 2 added, 0 changed, 0 removed
reading sources... [100%] plans/index
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [100%] plans/index
generating indices... genindex
writing additional pages... search
copying static files... WARNING: html_static_path entry '/home/shared/disk/zephyr_project/qm/doc/_static' does not exist
done
copying extra files... done
dumping search index in English (code: en) ... done
dumping object inventory... done
build succeeded, 1 warning.

Build finished. The HTML pages are in _build/html.

U-WBIxa22633<EMAIL_ADDRESS>
Can you please use a real email? Also use this for the commit (Author)

You also will need to squash your commits into one commit.

@hakehuang please fix the issues reported here:
https://app.shippable.com/github/zephyrproject-rtos/qm/runs/29/1/tests

squash into one commit. @nashif  please check. Thanks

@nashif , I update the patch for format checking and I rename the plan as high level plan. please check again thanks.


SelecUnstyled bug

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
(https://codesandbox.io/s/qo1ny5?file=/demo.js)
Current behavior 😯
when opening the toggle device tool bar and choosing one pf the styledoptions the apps crashed and size the error
:Error: Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops
happend in
Expected behavior 🤔
in normal computer mode its working and choosing the right StyledOption
Context 🔦
trying to use the select hook like it should work
Your environment 🌎

npx @mui/envinfo
  System:
    OS: Windows 10 10.0.22000
  Binaries:
    Node: 17.3.0 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 8.3.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.22000.120.0), Chromium (105.0.1343.42)
  npmPackages:
    @emotion/react: ^11.10.0 => 11.10.0
    @emotion/styled: ^11.10.0 => 11.10.0
    @mui/base:  5.0.0-alpha.94
    @mui/core-downloads-tracker:  5.10.2
    @mui/material: ^5.10.2 => 5.10.2
    @mui/private-theming:  5.9.3
    @mui/styled-engine:  5.10.2
    @mui/system:  5.10.2
    @mui/types:  7.1.5
    @mui/utils:  5.9.3
    @types/react: 18.0.9 => 18.0.9
    react: 18.1.0 => 18.1.0
    react-dom: 18.1.0 => 18.1.0
    typescript: 4.7.2 => 4.7.2

@eilon100 I am not able to reproduce the issue in the provided CodeSandbox.
I see that you are using MUI Base version @mui/base:  5.0.0-alpha.94. Please update to the latest version which is 5.0.0-alpha.98. This issue was fixed in version 5.0.0-alpha.95.


Time machine is broken

Hey @plainspace, I've created #38 to provide a fix for this!
Feel free to review it when you have time! :)