text:
[WIP] Unique index for distributed

WIP - DO NOT MERGE!

Codecov Report

Merging #9350 into develop will decrease coverage by 0.00%.
The diff coverage is 30.55%.

@@              Coverage Diff              @@
##             develop    #9350      +/-   ##
=============================================
- Coverage      54.19%   54.19%   -0.01%
- Complexity     35442    35451       +9
=============================================
  Files           2421     2421
  Lines         191494   191530      +36
  Branches       34963    34971       +8
=============================================
+ Hits          103774   103793      +19
- Misses         72827    72843      +16
- Partials       14893    14894       +1

Impacted Files
Coverage Δ
Complexity Δ

...ntechnologies/orient/core/index/OCompositeKey.java
94.44% <ø> (ø)
34.00 <0.00> (ø)

...s/orient/core/sql/executor/FetchFromIndexStep.java
58.57% <ø> (ø)
120.00 <0.00> (ø)

...rientechnologies/orient/core/storage/OStorage.java
100.00% <ø> (ø)
0.00 <0.00> (ø)

...nologies/orient/core/storage/OStorageAbstract.java
70.00% <ø> (ø)
23.00 <0.00> (ø)

...ogies/orient/core/storage/cache/OCachePointer.java
60.44% <ø> (ø)
31.00 <0.00> (ø)

...torage/impl/local/paginated/base/ODurablePage.java
65.71% <ø> (ø)
34.00 <0.00> (ø)

.../storage/impl/local/OAbstractPaginatedStorage.java
46.86% <30.55%> (-0.11%)
400.00 <6.00> (+7.00)
:arrow_down:

...gies/common/concur/lock/OInterruptedException.java
0.00% <0.00%> (-50.00%)
0.00% <0.00%> (-1.00%)

...nologies/common/concur/resource/OResourcePool.java
81.81% <0.00%> (-3.90%)
20.00% <0.00%> (ø%)

...rient/core/query/live/OLiveQueryQueueThreadV2.java
80.76% <0.00%> (-3.85%)
5.00% <0.00%> (-1.00%)

... and 26 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 42c462b...c6abc1e. Read the comment docs.

authors: codecov-commenter dritter-sap


text:
add timing, warm start to bayes, standardize

Adds timing feature to TuningBayes
Adds warm start option to TuningBayes
Refactors the API to standardize evaluate and warm start
Adds tests

Closes #22
Closes #23

Codecov Report

Merging #24 into master will decrease coverage by 1.77%.
The diff coverage is 81.81%.

@@            Coverage Diff             @@
##           master      #24      +/-   ##
==========================================
- Coverage   93.66%   91.89%   -1.78%
==========================================
  Files           6        6
  Lines         426      481      +55
==========================================
+ Hits          399      442      +43
- Misses         27       39      +12

Impacted Files
Coverage Δ

tuningdeap/tuningdeap.py
96.35% <100%> (+0.96%)
:arrow_up:

tuningdeap/base_tuner.py
88.11% <60%> (-1.52%)
:arrow_down:

tuningdeap/tuningbayes.py
90.09% <78.26%> (-9.91%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 761c400...8b04cba. Read the comment docs.

source: gharchive/pull-request

authors: codecov-io orionw

repo: orionw/tuningDEAP

license: MIT

license_type: permissive

license_source: github-api


text:
ready function not working.

Ready function is not triggering any event

more info is required

Actually issue was with my chrome browser, its working good now.

source: gharchive/issue

repo: orizens/ngx-youtube-player


text:
HTMLRenderer | Requested Plugin Could Not Be Found / Slate Plugin Error

The following shows the ory state renderer using the slate() initialization with no plugins. This leads to the Requested Plugin Could Not Be Found error:

Aside from that, if I uncomment the new_slate where I insert the plugins, then the editor doesn't work.
import React from 'react'
import ReactDOM from 'react-dom'

import axios from 'axios'

// Load some exemplary plugins:
import slate from 'ory-editor-plugins-slate' // The rich text area plugin
import { defaultPlugins } from 'ory-editor-plugins-slate/lib/hooks'
import 'ory-editor-plugins-slate/lib/index.css' // Stylesheets for the rich text area plugin

import parallax from 'ory-editor-plugins-parallax-background' // A plugin for parallax background images
import 'ory-editor-plugins-parallax-background/lib/index.css' // Stylesheets for parallax background images

import video from 'ory-editor-plugins-video'
import 'ory-editor-plugins-video/lib/index.css'

import spacer from 'ory-editor-plugins-spacer'
import 'ory-editor-plugins-spacer/lib/index.css'

import CustomImage from './components/custom-image'
import 'ory-editor-plugins-image/lib/index.css'

import divider from 'ory-editor-plugins-divider'

import KatexBlock from './components/katex-custom'
import KatexInlinePlugin from './components/katex-inline'

import SubscriptPlugin from './components/subscript'

import native from 'ory-editor-plugins-default-native'

import axios from 'axios'

import ParagraphPlugin, { P } from './components/slate/src/plugins/paragraph'
import { Document, Html, Raw, State, Plain } from 'slate'
const DEFAULT_NODE = P

// instance of plugins
const MathPlugin = new KatexInlinePlugin({ DEFAULT_NODE });
const SubPlugin = new SubscriptPlugin({ DEFAULT_NODE });

// push to array
//const slate_plugins = defaultPlugins.push(MathPlugin, SubPlugin);

export const new_slate = slate(); //{plugins: defaultPlugins}
//export const new_slate = slate()
// Define which plugins we want to use. We only have slate and parallax available, so load those.
export const plugins = {
  content: [new_slate, CustomImage, video, spacer, KatexBlock, divider], // Define plugins for content cells
  layout: [parallax({ defaultPlugin: new_slate })], // Define plugins for layout cells
  native
}

import { HTMLRenderer } from 'ory-editor-renderer'

class OryViewer extends React.Component {
  constructor(props){
    super(props);
    this.state = {
      body: ''
    }
  }

  componentDidMount(){
    const self = this;
    axios.get('/get_brief_state', {
      params: {
        brief_id: this.props.brief_id
      }
    })
    .then((res) => {
      self.setState({
        body: res.data.state
      })
    })
  }

  render(){
    let {body} = this.state;
    let $output = null;
    if (body) {
      let parsed_body = JSON.parse(body);
      $output = (<HTMLRenderer state={parsed_body} plugins={plugins} />);
    } else {
      $output = (

);
    }
    return(

        {$output}

    )
  }

}

Remove all the push stuff (it's not correct) and replace with:
const new_slate = slate([...defaultPlugins, MathPlugin, SubPlugin]);

This worked for the editor, but I'm still getting the same error on the HTMLRenderer

Is this still an issue or where you able to resolve it? Reopening for now.

@arekkas See #495

authors: Knorrke YanivSilberman arekkas

repo: ory/editor

license: mit

license_source: bigquery


text:
function id_from_list_dict added

get_user_id method added to Users class
refactor: get_user_id and get_channel_id use the same lines.

@juanpabloaj Thank you for this. Two things... Can you rename id_from_list_dict with something like get_item_id_by_name? Also, can you rebase to clean up your changes so get_user_id will be added after that function? Therefore, it will not appear in commit history twice.

ok, I renamed id_from_list_dict function.
but I don't understand the second thing, If I make a rebase, I need make a force push ? to overwrite this branch
and, I need make this rebase and force push :
 git checkout id_from_list_dict
 git rebase master
 git rebase master id_from_list_dict
 git push -f juanpabloaj id_from_list_dict

... ?

What I’m trying to say is that the pull request should only include what matters. You can change a variable name hundreds of times and have individual commits for each. But it’s the latest version only that matters, not the changes you’ve made in between. So instead of a history like:

Add get_channel_id function.
Add get_item_id_by_name function.
Rewrite get_channel_id using get_item_id_by_name.

It’s better to have:

Add get_item_by_name function.
Add get_channel_id function.

but, this sequence is the history of development

Add get_user_id function with very similar code to get_channel_id
Add get_item_id_by_name function, refactor because get_channel_id and get_user_id are very similar
rename get_channel_id to  get_item_id_by_name.

if you prefer I can open other pull request, with two commits

Add get_item_by_name function.
Add get_channel_id function.

or all changes in one single commit

reorder commits in pull request #21

authors: juanpabloaj os

repo: os/slacker


text:
Blueprint schema updates cause updated blueprints pushes to end up with missing fields

Describe the bug
If you change the schema of a blueprint, for instance:
Data64          string `json:"ignition_data,omitempty" toml:"ignition_data,omitempty"`

to
Data64          string `json:"data,omitempty" toml:"data,omitempty"`

then update an associated blueprint that has been already pushed (aka bump the version and replace the old field with the new field and push it), when  you show the blueprint the new updated field will not show up. No errors/warnings on the logs.
Environment

OS version (/etc/os-release and /etc/redhat-release): Red Hat Enterprise Linux release 9.1 (Plow)
osbuild-composer version (rpm -qi osbuild-composer): upstream version, latest commit 5457b9fba2ef634e5be798c8503842d749ec29df

To Reproduce
Steps to reproduce the behavior:
Use the following PR branch: https://github.com/osbuild/osbuild-composer/pull/3161,

push the following blueprint

name = "embedded-data"
description = ""
version = "0.0.1"

[customizations]
installation_device = "/dev/vda"

[customizations.ignition.embedded]
data = "eyJpZ25pdGlvbiI6eyJjb25maWciOnsibWVyZ2UiOlt7InNvdXJjZSI6Imh0dHA6Ly8xOTIuMTY4\nLjEyMi4xOjgwMDAvc2FtcGxlLmlnbiJ9XX0sInRpbWVvdXRzIjp7Imh0dHBUb3RhbCI6MzB9LCJ2\nZXJzaW9uIjoiMy4zLjAifSwicGFzc3dkIjp7InVzZXJzIjpbeyJncm91cHMiOlsid2hlZWwiXSwi\nbmFtZSI6ImNvcmUiLCJwYXNzd29yZEhhc2giOiIkNiRqZnVObk85dDFCdjdOLjdrJEhxUnhxMmJs\ndFIzek15QUhqc1N6YmU3dUJIWEVyTzFZdnFwaTZsamNJMDZkUUJrZldYWFpDdUUubUpja2xQVHdh\nQTlyL3hwSmlFZFdEcXR4bGU3aDgxIiwic3NoQXV0aG9yaXplZEtleXMiOlsic3NoLWVkMjU1MTkg\nQUFBQUMzTnphQzFsWkRJMU5URTVBQUFBSUJXT0dlNTFyNDA0SlNYRW5hbktaampCOHJVb2hnMWRB\nYXpydDFKd3lNVXogY2FyZG5vOjAwMDAgQTAxMDMxMjUiXX1dfSwic3RvcmFnZSI6eyJmaWxlcyI6\nW3sicGF0aCI6Ii9ldGMvTmV0d29ya01hbmFnZXIvc3lzdGVtLWNvbm5lY3Rpb25zL2VucDFzMC5u\nbWNvbm5lY3Rpb24iLCJjb250ZW50cyI6eyJjb21wcmVzc2lvbiI6Imd6aXAiLCJzb3VyY2UiOiJk\nYXRhOjtiYXNlNjQsSDRzSUFBQUFBQUFDLzB5S1VjckNNQkFHMy9jc2YvT2JVS1FpZTVMU2h5WDVT\nZ1BOTmlTcjBOdUxnaUR6Tk1QTThWQkZ0SHpvUWpreHRQcCtJVHNyR0xhaEtZeXlHdG9xRVlOS3dm\nZVpjMzJPQzBsS0RiMTc5cmZnL0hWeVBnUTNodjh3L3YwV1QwazdUKzdEL1MxRGg3UzRNUlU1aDFY\neXpxdnNIVlJnMjVHNGlENWtwMWNBQUFELy82Q3ZxMmloQUFBQSJ9LCJtb2RlIjozODR9LHsicGF0\naCI6Ii91c3IvbG9jYWwvYmluL3N0YXJ0dXAuc2giLCJjb250ZW50cyI6eyJzb3VyY2UiOiJkYXRh\nOjtiYXNlNjQsSXlFdlltbHVMMkpoYzJnS1pXTm9ieUFpU0dWc2JHOHNJRmR2Y214a0lTSUsifSwi\nbW9kZSI6NDkzfV19LCJzeXN0ZW1kIjp7InVuaXRzIjpbeyJjb250ZW50cyI6IltVbml0XVxuRGVz\nY3JpcHRpb249QSBoZWxsbyB3b3JsZFxuW0luc3RhbGxdXG5XYW50ZWRCeT1tdWx0aS11c2VyLnRh\ncmdldCIsImVuYWJsZWQiOnRydWUsIm5hbWUiOiJoZWxsby5zZXJ2aWNlIn0seyJkcm9waW5zIjpb\neyJjb250ZW50cyI6IltTZXJ2aWNlXVxuRW52aXJvbm1lbnQ9TE9HX0xFVkVMPXRyYWNlXG4iLCJu\nYW1lIjoibG9nX3RyYWNlLmNvbmYifV0sIm5hbWUiOiJmZG8tY2xpZW50LWxpbnV4YXBwLnNlcnZp\nY2UifV19fQo="

change the data field to whatever you like in internal/blueprint/customizations.go
re-compile
update the previous blueprint bumping the version and updating the changed field name
push this new updated blueprint
show and you will get a blueprint with the updated section missing:

name = "new-blueprint"
description = ""
version = "0.0.2"
packages = []
modules = []
groups = []
distro = ""

[customizations]
installation_device = "/dev/vda"

Expected behavior
I would expect that the new pushed blueprint would get the updated schema.
Additional context
Add any other context about the problem here.

CC @achilleas-k

repo: osbuild/osbuild-composer


text:
Add unit tests for client functions

The client module has relatively simple wrappers for the API routes, these should be unit tested against the mocked server to make sure they are correct, including returning errors.

PR #404 handles this and more.


text:
Service maintenance test

We have 2 choices really, either remove the records entirely or just zero out the manifest. This PR removes them entirely. Happy to drop this in favour of just removing the manifest however.

If multiple osbuild jobs per depsolve are ever implemented, this
will not break.

Won't it break the data retention promise, though? If depsolve was done more than 14 days ago, the latest osbuild job based on it might be much newer/.

The assumption in this script is that the build happened within 24 hours of the depsolve. I we are working towards this, then we can't do this.

We might need the osbuild result  around for a long time for registering purposes. For this reason I'll just open a PR which zeros out the manifest (and depsolve?) job results.


text:
[skip ci] ci: switch to using automerge

Instead of using merify which seems to not do what we want, use a combination of mergify and automerge. We let mergify review dependabot PRs. We let mergify dismiss reviews on updates but exclude those from Schutzbot. We then let Schutzbot update and merge the PRs via automerge if the ci:automerge label is set.

Admin-merge since skip-ci.

repo: osbuild/osbuild


text:
Consider adding async-graphql-relay to SeaORM showcase!

Hey @oscartbeaumont, feel free to submit a PR to showcase your project!

https://github.com/SeaQL/sea-orm/issues/403

I am closing this as I have stopped using this project and do not intend to continue maintaining it to the level required to be promoting it.
Thanks for your consideration of adding it to the showcase!

repo: oscartbeaumont/async-graphql-relay


text:
No such schema “org.gnome.gedit.preferences.editor”

Hey,
minor problem with the 3.2.0 release - when typing yin-yang -t in the console, this message shows up:
No such schema “org.gnome.gedit.preferences.editor”
I don't have gedit installed - I'm using KDE Plasma & VSCode.
Thanks for help!

My fault - this is not the cause of the issue.
However, it seems that the upgrade to v3.2.0 purged my previous configuration.

What exactly happened to your config?

repo: oskarsh/Yin-Yang


text:
Add banner

import banner component from tailwind ui library and added this to dashboard page

Banner appearance looks good, but let's make the close button work before merging.

authors: bisectors miabrahams

repo: oslabs-beta/KubeSentry


text:
Feature/add details to join exit pool reponse

What is the purpose of the change
This PR adds more information to response of join/exit pool handlers so the caller of the transaction in ICA receives these information on acknowledgment.
Brief Changelog

Added tokenIn sdk.Coins, sharesOut sdk.Int to return of JoinPoolNoSwap
share_out_amount and token_in fields to MsgJoinPoolResponse
token_out field to MsgExitPoolResponse

Testing and Verifying
This change added tests and can be verified as follows:

Extended integration test for TestJoinPoolNoSwap

Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? (yes)
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? (no)
How is the feature or change documented? (not documented)

Needs changelog entry as well

https://github.com/quasar-finance/osmosis/pull/2

authors: Ehsan-saradar ValarDragon

repo: osmosis-labs/osmosis


text:
[CL]: Join-time tracker sumtree

Pulled from #3886
What is the purpose of the change

Note to reviewer: the majority of the file diff is updating wiring for sumtree usage (switching Int to Dec)

This PR implements a join-time tracker sumtree that dynamically updates as positions are changed in a given pool. This allows us to get the amount of liquidity that joined a pool before, at, or after a given join time, allowing us to incentivize uptime.
Once we finalize our process for reward calculation post-#3894 & decide on whether we want to support multiple uptime tiers per incentive token, we can add a second sum to our sumtree to track accumulated rewards.
Brief Changelog

Change sumtree to accumulate sdk.Dec instead of sdk.Int
Populate a sumtree tracking position join times for each pool every time a position is updated
Thoroughly fuzz test new sumtree logic

Testing and Verifying
All of the new logic is heavily tested in position_test.go (both by expanding existing tests & adding new robust fuzz tests)
Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? (no)
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? (no)
How is the feature or change documented? (not documented)

Thanks for the comments all – I just realized that this sumtree logic needs another layer to track tick range for joins for it to be useful for incentives, so converting this to a draft while I flesh out what needs to be done on that front


text:
REFERENCE: Pool Yield & Farm

Opening as draft PR to more easily track changes

Closing this PR, but leaving the branch open until F1 spec is done.


text:
Tab system for service docs view

See #122.
Services grouped by responsibles. Responsibles should not be clickable atm. Keep the graph view in independent unfilterable tab for now.

Closed by #129

repo: osrgroup/msadoc


text:
docker build issue

The docker container cannot be built using
docker build -t ort ..
Build error:
Version '0.40.0-3ubuntu1~18.04.1' for 'cargo' was not found
build.log

That was already fixed meanwhile as part of https://github.com/oss-review-toolkit/ort/pull/2476/commits/dbc5b3734108663cd0b83613099a16db4c8b1c23.

authors: pilvikala sschuberth

repo: oss-review-toolkit/ort


text:
"TLS/SSL connection has been closed" during Docker build on Apple M1

Summary: scripts/docker_build.sh throws this error:
#9 50.63 Reading state information...
#9 50.68 E: Unable to locate package lib32stdc++6
#9 50.68 E: Couldn't find any package by regex 'lib32stdc++6'
#9 50.68 E: Unable to locate package sbt
------
executor failed running [/bin/sh -c apt-get update &&     apt-get install -y --no-install-recommends ca-certificates gnupg software-properties-common &&     echo "deb https://repo.scala-sbt.org/scalasbt/debian all main" | tee -a /etc/apt/sources.list.d/sbt.list &&     curl -ksS "https://keyserver.ubuntu.com/pks/lookup?op=get&options=mr&search=0x2EE0EA64E40A89B84B2DF73499E82A75642AC823" | apt-key adv --import - &&     curl -sL https://deb.nodesource.com/setup_16.x | bash - &&     add-apt-repository -y ppa:git-core/ppa &&     apt-get update &&     apt-get install -y --no-install-recommends         lib32stdc++6         libffi-dev         libgmp-dev         libxext6         libxi6         libxrender1         libxtst6         make         netbase         openssh-client         unzip         xz-utils         zlib1g-dev         cvs         git         mercurial         subversion         cargo=$CARGO_VERSION         composer=$COMPOSER_VERSION         nodejs         python-is-python3         python-setuptools         python2-dev         python3-dev         python3-pip         python3-setuptools         ruby-dev         sbt=$SBT_VERSION     &&     rm -rf /var/lib/apt/lists/*]: exit code: 100

Platform:

MacOS 11.6
M1 2020

Requirements status:
requirements-log.txt
Runtime log:
ort-log.txt

Probably related to https://github.com/oss-review-toolkit/ort/issues/5411 which was (hopefully) addressed by https://github.com/oss-review-toolkit/ort/pull/5832 that was just merged 10 hours ago. Have you tried a version of ORT with that PR included?

Thanks for this suggestion. fetch and rebase made the earlier issue go away. There is now a different failure in the build process. Log: log2.txt
Highlight of the log:
#0 153.5 ## Run `sudo apt-get install -y nodejs` to install Node.js 16.x and npm
#0 153.5 ## You may also need development tools to build native addons:
#0 153.5      sudo apt-get install gcc g++ make
#0 153.5 ## To install the Yarn package manager, run:
#0 153.5      curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/yarnkey.gpg >/dev/null
#0 153.5      echo "deb [signed-by=/usr/share/keyrings/yarnkey.gpg] https://dl.yarnpkg.com/debian stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
#0 153.5      sudo apt-get update && sudo apt-get install yarn

Notes:

Just before running the above command I did nvm use 16
yarn is already installed

Highlight of the log:

I believe that's not the crucial part, but
#0 172.3 Traceback (most recent call last):
#0 172.3   File "/usr/bin/add-apt-repository", line 364, in <module>
#0 172.3     sys.exit(0 if addaptrepo.main() else 1)
...
#0 172.3 ssl.SSLZeroReturnError: TLS/SSL connection has been closed (EOF) (_ssl.c:997)

So maybe just network flakyness? Anyway, hard to debug without an M1. For the fun of it you could try to omit the line add-apt-repository -y ppa:git-core/ppa.

Anyway, hard to debug without an M1.

Maybe @MarcelBochtler can help here.

@MarcelBochtler @lucasgonze can you help to find out the current status of building the Docker image on Apple Mx?

@MarcelBochtler @lucasgonze can you help to find out the current status of building the Docker image on Apple Mx?

My understanding from conversations with Connect5G is that they are doing ARM builds using Kubernetes. I think they don't use the same process I referenced above. I personally haven't run through this recently and would have to spend a fair amount of time to reproduce the problem myself.

I got similar failure today on multiarch local build in a Mac M1.
Honestly something is playing very weirdly since 15.0.0 and I don't t think is direct ort issue, but some transient dependency.
I will keep running some tests tomorrow, but my current guess is that the fault is on docker side
I have both M1 and M2 around to test.

There was no feedback for this issue in a while, and @lancedikson confirmed on Slack that it's working for him, so I'm closing this. Feel free to reopen if the issue persists.

authors: heliocastro lucasgonze sschuberth


text:
node EBADENGINE

We get this error:
EBADENGINE Unsupported engine {
EBADENGINE   package: 'xxx@2.16.0',
EBADENGINE   required: { node: '>=16 <18' },
EBADENGINE   current: { node: 'v18.12.1', npm: '8.15.1' }
EBADENGINE }

Does ORT use the installed node version? What if it isn't installed? I think it should not use whatever is installed, but the required version. I think ORT should use https://github.com/tj/n which is what node developers use to use different node versions.
This is specially important for multi-repo systems using different versions of node.

Does ORT use the installed node version?

Yes, ORT uses the node version in PATH (the same is true for all external tools ORT depends on). But depending on how you run ORT that may mean different things. If you run ORT from the Docker image, the node version (currently 18.14.2) from the Docker image will be used, not the one from the host.

What if it isn't installed?

Analysis will fail completely. ORT will not try to bootstrap node or any other tool.

I think ORT should use https://github.com/tj/n which is what node developers use to use different node versions.

The combination of bootstrapping n plus running n auto or n engine indeed looks interesting.

This is specially important for multi-repo systems using different versions of node.

Which means the bootstrapping would need to happen in beforeResolution, not once in the Docker image.

authors: dgutson sschuberth


text:
declared-license-mapping: Remove abiguous mappings

Remove mappings where the version of a license is not obvious from the
source string. For these declared licenses package specific declared
license mappings should be created instead.
This is a draft for discussion, and to be able to test the impact of this change. Ideally package specific declared license mappings should be created in the ort-config repository before the change is merged, at least for those removed mappings where the source package can be found, for example from the message of the commit that introduced the mapping.

I would like to bring this PR to a vote by ORT TSC as  'as-is' it would cause serious disruption to ORT users and tens/hundreds of hours of additional work.

@tsteenbe FYI, this is the discussion that this PR originated from: https://github.com/oss-review-toolkit/ort/pull/5123#discussion_r816937603

Closing this in favor of the approach discussed in the community meeting on 2022-11-24.

authors: mnonnenmacher sschuberth tsteenbe


text:
Starting the change by editing the css

This is the start of the feature request of the highlight effect

I made the markers look more retro and until we find a better marker icon I think thats the best we can do for now. and it simultaneously highlights from the right side clickable note to the left and the cursor changes.


text:
main.py 파일의 21번째 줄에 오타가있습니다

이런 건 이미지가 아니라 텍스트로 인용해 주세요 이미지가 알아보기 더 힘듭니다

def main():
    try:

        parser = argparse.ArgumentParser(
            description='A CLI utility for processing data.',
            epilog='Enjoy using the CLI utility!'
        )

        # Adding command line options
        parser.add_argument('-i', '--input', type=str, help='Specify the input YAML data file path. (required)')
        parser.add_argument('-o', '--output', type=str, help='Specify the output image file path. (optional).')
        parser.add_argument('-f', '--format', choices=['graph', 'table'], default='graph',
                            help='Sepcify the output format (graph, table). Defaults to graph.')

이런 식으로요

authors: hateauk12 kyagrd kyahnu


text:
Switch to using a single worker

Change "workers" cli option to be in pkg/config/operator and use ALLSTAR_NUM_WORKERS envvar with same default at 5. Update staging and prod config to use 1 worker to save concurrent memory usage.

cc @raghavkaul I'm looking to use this in prod, and I don't have a good way to use cli options now, jut env vars. The initial setup was for all operator config to be in pkg/config/operator. Some cli options were added later for test/debug purposes.

repo: ossf/allstar


text:
Feature - Support Maven Central in the packaging check

Is your feature request related to a problem? Please describe.
Java projects which publish to Maven Central are not included in the packaging scorecards check.
Describe the solution you'd like
We could extract the groupId/artifactId from the pom.xml and then search Maven Central via e.g. https://search.maven.org/artifact/org.apache.santuario/xmlsec and check if the latest release has packaged jars.
Alternatively we could check the README for a badge which redirects to Maven Central, e.g. something like https://maven-badges.herokuapp.com/maven-central/org.apache.santuario/xmlsec
If I got some feedback on this proposal I could work on a PR

Thanks for the report. I think the original goal of the Packaging check was to verify whether users have open-source release pipeline, to help consumers know that the build corresponds to the source code. We test if mvn command is used in https://github.com/ossf/scorecard/blob/main/checks/fileparser/github_workflow.go#L462.
For the project you are using, do you use a workflow to build  publish?
NOTE: the packaging check starts to overlap with SLSA / signed releases, though.

We test if mvn command is used in https://github.com/ossf/scorecard/blob/main/checks/fileparser/github_workflow.go#L462.

E.g. for (my) https://github.com/MariaDB4j/MariaDB4j/ where I've added Scorecard in https://github.com/MariaDB4j/MariaDB4j/issues/661 on https://securityscorecards.dev/viewer/?uri=github.com/MariaDB4j/MariaDB4j it says ? for Packaging and Signed-Releases. The problem seems to be that I still run mvn deploy locally when doing a release, not in a GitHub Action. (As in, I do have GitHub Actions which contain ./mvnd for CI, but then don't deploy.) So scanning for a pom.xml and checking if an artifact is available as suggested above would detect this better than (only) scanning for run in GitHub Workflow Actions .

authors: coheigea laurentsimon vorburger

repo: ossf/scorecard


text:
🐛 Ignore nil values in Branch-Protection check

Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] PR title follows the guidelines defined in  https://github.com/ossf/scorecard/blob/main/CONTRIBUTING.md#pr-process

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Part of #1242.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No.

LGTM, thanks for the quick fix. One question I have: when we ignore some setting, shall we add a 0 score to scores array? Otherwise the score won't see a difference when we run with or without admin token.

Not sure what you mean. The scores array collects scores across branches. But each branch only has a single score int. I have refactored the branch_protection check a bit more. Take a look and let me know.

LGTM, thanks for the quick fix. One question I have: when we ignore some setting, shall we add a 0 score to scores array? Otherwise the score won't see a difference when we run with or without admin token.

Not sure what you mean. The scores array collects scores across branches. But each branch only has a single score int. I have refactored the branch_protection check a bit more. Take a look and let me know.

If run with admin token, there will be more settings we check for. I think this this means that when run with admin token, the overall score would drop (compared to a non-admin run) if all the settings that need admin settings are disabled

do you know if it fixes both https://github.com/ossf/scorecard/issues/1247 and https://github.com/ossf/scorecard/issues/1246?
I'm pretty sure it fixes the former.

I'm not sure it works as expected. With this patch applied (with the same token) I got
{
  "date": "2021-11-11",
  "repo": {
    "name": "github.com/evverx/systemd",
    "commit": "33796123bccabdcc91ee9b87b5c042710bf50362"
  },
  "scorecard": {
    "version": "3.1.1-47-ga15225c",
    "commit": "a15225c59c0fb7d60f139795882990f8fde7badd"
  },
  "score": 3.0,
  "checks": [
    {
      "details": [
        "Warn: 'force pushes' enabled on branch 'main'",
        "Info: 'allow deletion' disabled on branch 'main'",
        "Warn: linear history disabled on branch 'main'",
        "Warn: 'administrator' PRs are exempt from reviews on branch 'main'",
        "Info: strict status check enabled on branch 'main'",
        "Warn: status checks for merging have no specific status to check on branch 'main'",
        "Warn: number of required reviewers is only 0 on branch 'main'",
        "Info: Stale review dismissal enabled on branch 'main'",
        "Warn: Owner review not required on branch 'main'"
      ],
      "score": 3,
      "reason": "branch protection is not maximal on development and all release branches",
      "name": "Branch-Protection",
      "documentation": {
        "url": "https://github.com/ossf/scorecard/blob/a15225c59c0fb7d60f139795882990f8fde7badd/docs/checks.md#branch-protection",
        "short": "Determines if the default and release branches are protected with GitHub's branch protection settings."
      }
    }
  ],
  "metadata": null
}

and here's what the rules look like
{
  "url": "https://api.github.com/repos/evverx/systemd/branches/main/protection",
  "required_pull_request_reviews": {
    "url": "https://api.github.com/repos/evverx/systemd/branches/main/protection/required_pull_request_reviews",
    "dismiss_stale_reviews": true,
    "require_code_owner_reviews": false,
    "required_approving_review_count": 2
  },
  "required_signatures": {
    "url": "https://api.github.com/repos/evverx/systemd/branches/main/protection/required_signatures",
    "enabled": false
  },
  "enforce_admins": {
    "url": "https://api.github.com/repos/evverx/systemd/branches/main/protection/enforce_admins",
    "enabled": false
  },
  "required_linear_history": {
    "enabled": false
  },
  "allow_force_pushes": {
    "enabled": true
  },
  "allow_deletions": {
    "enabled": false
  },
  "required_conversation_resolution": {
    "enabled": false
  }
}

It seems at least two subchecks aren't correct

It seems at least two subchecks aren't correct

This is very surprising. I tested this PR both against your repo and a personal repo with an admin token and it is returning the expected results (matching with GitHub API). My only hunch here would be that somehow there is a delay between GitHub REST API and GraphQL APIs, so when you modify the settings and immediately test with Scorecard, the results seem off.
I'm going to submit this PR for now, since it is clearly an improvement over what we have today. Could you please try once more after the PR is submitted and let me know the results? If the issue persists, we can continue the debugging over #1246  and #1247.

authors: azeemshaikh38 evverx laurentsimon


text:
Add examples for create account and password reset

Signed-off-by: David A. Wheeler dwheeler@dwheeler.com

+1

The positives are far more than the negatives, and it turns out that the OWASP Forgot Password Cheat Sheet suggests the same for password resets.

authors: brianf david-a-wheeler

repo: ossf/secure-sw-dev-fundamentals


text:
srs4.0能不能webrtc转hls播放

注意：不提供以下信息的Issue会被直接删除(Please follow issue template, or we will delete it)

注意：咨询和讨论请提交到SRS星球(Please ask question at) http://bbs.ossrs.net

描述(Description)

描述你遇到了什么问题(Please description your issue here)

SRS版本(Version): 4.0
SRS的日志如下(Log):
[2021-08-31 01:27:04.637][Trace][1][03877010] RTC: session address change 113.71.138.158:58714 -> 113.69.42.179:11854, cached=1, nn_change=2/1, nn_address=2
[2021-08-31 01:27:04.637][Warn][1][03877010][11] VIDEO: stream not monotonically increase, please open mix_correct.
[2021-08-31 01:27:04.637][Trace][1][03877010] 35B video sh,  codec(7, profile=Baseline, level=3.1, 720x416, 0kbps, 0.0fps, 0.0s)
[2021-08-31 01:27:04.637][Trace][1][03877010] set ts=4284641379, header=30743, lost=30744
[2021-08-31 01:27:04.637][Trace][1][03877010] NACK: update seq=30743, nack range [30743, 30752]
[2021-08-31 01:27:04.700][Trace][1][03877010] -> HLS time=474358740ms, sno=7839, ts=livestream12-7838.ts, dur=0.00, dva=0p
[2021-08-31 01:27:04.873][Trace][1][03877010] NACK: update seq=30758, nack range [30756, 30758]
[2021-08-31 01:27:04.875][Warn][1][v8xac3r5][11] handle udp pkt, count=10/10, err: code=5015 : size=54, data=[90 7d 78 17 ff 62 70 63] : marker=0, pt=125, seq=30743, ts=4284641379, ssrc=383066872, pad=0, payload=34B : rtp unprotect r0=9
thread [1][v8xac3r5]: cycle() [src/app/srs_app_listener.cpp:630][errno=11]
thread [1][03877010]: on_rtp() [src/app/srs_app_rtc_conn.cpp:1309][errno=11]
thread [1][03877010]: unprotect_rtp() [src/app/srs_app_rtc_dtls.cpp:1145][errno=11]
[2021-08-31 01:27:04.924][Trace][1][03877010] NACK: update seq=30760, nack range [30759, 30760]
[2021-08-31 01:27:04.936][Trace][1][qygp40tz] Hybrid cpu=0.00%,18MB, cid=36,6, timer=62,10,47, clock=0,42,5,0,0,0,0,0,0, free=1, objs=(pkt:490,raw:48,fua:442,msg:639,oth:1,buf:269)
[2021-08-31 01:27:04.936][Trace][1][qygp40tz] RTC: Server conns=1, rpkts=(140,rtp:136,stun:1,rtcp:2), spkts=(8,rtp:0,stun:1,rtcp:12), rtcp=(pli:1,twcc:5,rr:1), snk=(49,a:24,v:24,h:1), fid=(id:1,fid:140,ffid:0,addr:1,faddr:140)
[2021-08-31 01:27:04.988][Trace][1][qygp40tz][MAYBE] RTC: NACK timeout=1, request PLI, track=55087aa2-378c-4b27-884b-a2734e35f8e3, ssrc=383066872
[2021-08-31 01:27:08.502][Trace][1][03877010] 35B video sh,  codec(7, profile=Baseline, level=3.2, 960x544, 0kbps, 0.0fps, 0.0s)
[2021-08-31 01:27:08.502][Warn][1][03877010][11] dvr: ignore video error code=3085 : write video : encode video : write sample : doesn't support avcc change
thread [1][03877010]: on_video() [src/app/srs_app_dvr.cpp:651][errno=11]
thread [1][03877010]: write_video() [src/app/srs_app_dvr.cpp:146][errno=11]
thread [1][03877010]: encode_video() [src/app/srs_app_dvr.cpp:503][errno=11]
thread [1][03877010]: copy_sequence_header() [src/kernel/srs_kernel_mp4.cpp:5999][errno=11]
[2021-08-31 01:27:08.502][Trace][1][03877010] set ts=4284988599, header=31347, lost=31348
[2021-08-31 01:27:09.936][Trace][1][qygp40tz] Hybrid cpu=4.00%,19MB, cid=9,4, timer=62,3,17, clock=0,45,3,1,0,0,0,0,0, free=1, objs=(pkt:137,raw:22,fua:115,msg:189,oth:1,buf:77)
[2021-08-31 01:27:09.936][Trace][1][qygp40tz] RTC: Server conns=1, rpkts=(140,rtp:136,stun:1,rtcp:2), spkts=(8,rtp:0,stun:1,rtcp:12), rtcp=(pli:1,twcc:5,rr:1), snk=(49,a:24,v:24,h:1), fid=(id:1,fid:140,ffid:0,addr:1,faddr:140)
[2021-08-31 01:27:13.158][Trace][1][qygp40tz] RTC: Need PLI ssrc=383066872, play=[qygp40tz], publish=[03877010], count=1/1
[2021-08-31 01:27:13.158][Trace][1][03877010] RTC: Request PLI ssrc=383066872, play=[qygp40tz], count=1/1, bytes=12B
[2021-08-31 01:27:13.218][Trace][1][03877010] 35B video sh,  codec(7, profile=Baseline, level=3.2, 960x544, 0kbps, 0.0fps, 0.0s)
[2021-08-31 01:27:13.218][Trace][1][03877010] set ts=4285414299, header=32374, lost=32375
[2021-08-31 01:27:14.478][Trace][1][v8xac3r5] <- RTC RECV #10, udp 2488, pps 227/248, schedule 2488
[2021-08-31 01:27:14.718][Trace][1][03877010] -> HLS time=484384358ms, sno=7946, ts=livestream12-7945.ts, dur=0.00, dva=0p
[2021-08-31 01:27:14.936][Trace][1][qygp40tz] Hybrid cpu=4.00%,19MB, cid=9,4, timer=62,3,17, clock=0,45,3,1,0,0,0,0,0, free=1, objs=(pkt:137,raw:22,fua:115,msg:189,oth:1,buf:77)
[2021-08-31 01:27:14.936][Trace][1][qygp40tz] RTC: Server conns=1, rpkts=(258,rtp:252,stun:1,rtcp:4), spkts=(14,rtp:0,stun:1,rtcp:24), rtcp=(pli:1,twcc:9,rr:1), snk=(96,a:48,v:48,h:1), fid=(id:0,fid:258,ffid:0,addr:1,faddr:258)
[2021-08-31 01:27:19.937][Trace][1][qygp40tz] Hybrid cpu=3.00%,19MB, cid=9,4, timer=62,3,17, clock=0,45,3,1,0,0,0,0,0, free=1, objs=(pkt:137,raw:22,fua:115,msg:189,oth:1,buf:77)
[2021-08-31 01:27:19.937][Trace][1][qygp40tz] RTC: Server conns=1, rpkts=(258,rtp:252,stun:1,rtcp:4), spkts=(14,rtp:0,stun:1,rtcp:24), rtcp=(pli:1,twcc:9,rr:1), snk=(96,a:48,v:48,h:1), fid=(id:0,fid:258,ffid:0,addr:1,faddr:258)
[2021-08-31 01:27:23.215][Trace][1][qygp40tz] RTC: Need PLI ssrc=383066872, play=[qygp40tz], publish=[03877010], count=2/2
[2021-08-31 01:27:23.215][Trace][1][03877010] RTC: Request PLI ssrc=383066872, play=[qygp40tz], count=2/2, bytes=12B
[2021-08-31 01:27:23.279][Trace][1][03877010] 35B video sh,  codec(7, profile=Baseline, level=3.2, 960x544, 0kbps, 0.0fps, 0.0s)
[2021-08-31 01:27:23.279][Trace][1][03877010] set ts=4286319969, header=34678, lost=34679
[2021-08-31 01:27:24.488][Trace][1][v8xac3r5] <- RTC RECV #10, udp 2862, pps 228/285, schedule 2862
[2021-08-31 01:27:24.718][Trace][1][03877010] -> HLS time=494387469ms, sno=8113, ts=livestream12-8112.ts, dur=0.00, dva=67p
[2021-08-31 01:27:24.937][Trace][1][qygp40tz] Hybrid cpu=3.00%,19MB, cid=35,6, timer=62,11,48, clock=0,44,4,1,0,0,0,0,0, objs=(pkt:505,raw:50,fua:455,msg:659,oth:1,buf:278)
[2021-08-31 01:27:24.937][Trace][1][qygp40tz] RTC: Server conns=1, rpkts=(258,rtp:252,stun:1,rtcp:4), spkts=(14,rtp:0,stun:1,rtcp:24), rtcp=(pli:1,twcc:9,rr:1), snk=(96,a:48,v:48,h:1), fid=(id:0,fid:258,ffid:0,addr:1,faddr:258)
[2021-08-31 01:27:29.834][Trace][1][03877010] RTC: session address change 113.69.42.179:11854 -> 113.71.138.158:58714, cached=1, nn_change=3/2, nn_address=2
[2021-08-31 01:27:29.937][Trace][1][qygp40tz] Hybrid cpu=3.00%,19MB, cid=35,6, timer=62,11,48, clock=0,44,4,1,0,0,0,0,0, objs=(pkt:505,raw:50,fua:455,msg:659,oth:1,buf:278)
[2021-08-31 01:27:29.937][Trace][1][qygp40tz] RTC: Server conns=1, rpkts=(283,rtp:277,stun:1,rtcp:5), spkts=(14,rtp:0,stun:1,rtcp:23), rtcp=(pli:1,twcc:9,rr:1), snk=(97,a:48,v:48,h:0), fid=(id:0,fid:283,ffid:0,addr:1,faddr:283)
[2021-08-31 01:27:30.667][Trace][1][03877010] 35B video sh,  codec(7, profile=Baseline, level=3.2, 960x544, 0kbps, 0.0fps, 0.0s)
[2021-08-31 01:27:30.667][Trace][1][03877010] set ts=4286985519, header=36351, lost=36352
[2021-08-31 01:27:31.843][Trace][1][03877010] RTC: session address change 113.71.138.158:58714 -> 113.69.42.179:11854, cached=1, nn_change=4/2, nn_address=2
[2021-08-31 01:27:33.272][Trace][1][qygp40tz] RTC: Need PLI ssrc=383066872, play=[qygp40tz], publish=[03877010], count=3/3
[2021-08-31 01:27:33.273][Trace][1][03877010] RTC: Request PLI ssrc=383066872, play=[qygp40tz], count=3/3, bytes=12B
[2021-08-31 01:27:33.347][Trace][1][03877010] 35B video sh,  codec(7, profile=Baseline, level=3.2, 960x544, 0kbps, 0.0fps, 0.0s)
[2021-08-31 01:27:33.347][Trace][1][03877010] set ts=4287225459, header=36975, lost=36976
[2021-08-31 01:27:34.485][Trace][1][v8xac3r5] <- RTC RECV #10, udp 2845, pps 229/284, schedule 2845
[2021-08-31 01:27:34.750][Trace][1][03877010] -> HLS time=504421179ms, sno=8282, ts=livestream12-8281.ts, dur=0.00, dva=0p
SRS的配置如下(Config):

listen              1935;
max_connections     1000;
daemon              off;
srs_log_tank        console;

http_server {
    enabled         on;
    listen          8080;
    dir             ./objs/nginx/html;
}

http_api {
    enabled         on;
    listen          1985;
}
stats {
    network         0;
}
rtc_server {
    enabled on;
    # Listen at udp://8000
    listen 8000;
    #
    # The $CANDIDATE means fetch from env, if not configed, use * as default.
    #
    # The * means retrieving server IP automatically, from all network interfaces,
    # @see https://github.com/ossrs/srs/wiki/v4_CN_RTCWiki#config-candidate
    candidate $CANDIDATE;
}

vhost __defaultVhost__ {
    rtc {
        enabled     on;
        rtc_to_rtmp on;
        pli_for_rtmp 10;
    }
    http_remux {
        enabled     on;
        mount       [vhost]/[app]/[stream].flv;
    }
    dvr {
        enabled         on;
        dvr_path        ./conf/[app]/[stream].[timestamp].mp4;
    }
    hls {
        enabled         on;
        hls_cleanup     off;
        hls_fragment    10;
        hls_path        ./conf/m3u8;
        hls_m3u8_file   [app]/[stream].m3u8;
        hls_ts_file     [app]/[stream]-[seq].ts;
    }
}

重现(Replay)

重现Bug的步骤(How to replay bug?)

webrtc推流
使用hls无法播放
rtmp是可以的，但是ts文件只有几k，使用rtmp推流是可以的

期望行为(Expect)

描述你期望发生的事情(Please describe your expectation)

缺少日志，所以请志宏大神看看是否能重现，如果不能重现我就删除了。

原本的设计有webrtc to hls的功能吗？我看到文档是没有的。本来想webrtc to rtmp能转hls，但是测试过是不行的，视频为h264+aac，还有个问题，当webrtc推流时，控制台分辨率会变，录制的mp4文件就无效了。

这个问题好像和 #2470 一样

把配置文件中的hls_path        ./conf/m3u8;删掉试试？

[2021-08-31 01:27:08.502][Trace][1][03877010] 35B video sh, codec(7, profile=Baseline, level=3.2, 960x544, 0kbps, 0.0fps, 0.0s)
[2021-08-31 01:27:08.502][Warn][1][03877010][11] dvr: ignore video error code=3085 : write video : encode video : write sample : doesn't support avcc change
thread [1][03877010]: on_video() [src/app/srs_app_dvr.cpp:651][errno=11]
thread [1][03877010]: write_video() [src/app/srs_app_dvr.cpp:146][errno=11]
thread [1][03877010]: encode_video() [src/app/srs_app_dvr.cpp:503][errno=11]
thread [1][03877010]: copy_sequence_header() [src/kernel/srs_kernel_mp4.cpp:5999][errno=11]

现在录制mp4不支持分辨率变化

[2021-08-31 01:27:08.502][Trace][1][03877010] 35B video sh, codec(7, profile=Baseline, level=3.2, 960x544, 0kbps, 0.0fps, 0.0s)
[2021-08-31 01:27:08.502][Warn][1][03877010][11] dvr: ignore video error code=3085 : write video : encode video : write sample : doesn't support avcc change
thread [1][03877010]: on_video() [src/app/srs_app_dvr.cpp:651][errno=11]
thread [1][03877010]: write_video() [src/app/srs_app_dvr.cpp:146][errno=11]
thread [1][03877010]: encode_video() [src/app/srs_app_dvr.cpp:503][errno=11]
thread [1][03877010]: copy_sequence_header() [src/kernel/srs_kernel_mp4.cpp:5999][errno=11]

现在录制mp4不支持分辨率变化

是webrtc自动变的。。怎样能固定？

已经解决, 关闭了

authors: akanchi timfengzi winlinvip xiaozhihong

repo: ossrs/srs


text:
Memory leak observation SRS 4.0

注意：不提供以下信息的Issue会被直接删除(Please follow issue template, or we will delete it)

注意：咨询和讨论请提交到SRS星球(Please ask question at) http://bbs.ossrs.net

描述(Description)

描述你遇到了什么问题(Please description your issue here)

Memory leak in SRS when running as a an RTMP service inside a pod on k8s (maybe the memory leak is present when running SRS outside of k8s too?)
We are monitoring CPU and memory usage of SRS via the http_api which is very useful, however we notice that while cpu does return to pre-stream level, memory remains high, see attached graphs for a single RTMP stream running on SRS:

I attached memleax to the process and can see memory which could be freed (maybe this helps?):
CallStack[232]: memory expires with 48 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x00000000005097b3  srs  _ZN9__gnu_cxx13new_allocatorISt13_Rb_tree_nodeISt4pairIKlP19SrsSharedPtrMessageEEE8allocateEmPKv()+73  e/c++/4.8.2/new:115
    0x0000000000509416  srs  _ZNSt8_Rb_treeIlSt4pairIKlP19SrsSharedPtrMessageESt10_Select1stIS4_ESt4lessIlESaIS4_EE11_M_get_nodeEv()+34  e/c++/4.8.2/new:115
    0x0000000000508aef  srs  _ZNSt8_Rb_treeIlSt4pairIKlP19SrsSharedPtrMessageESt10_Select1stIS4_ESt4lessIlESaIS4_EE14_M_create_nodeIJS0_IlS3_EEEEPSt13_Rb_tree_nodeIS4_EDpOT_()+29  e/c++/4.8.2/new:115
    0x000000000050789b  srs  _ZNSt8_Rb_treeIlSt4pairIKlP19SrsSharedPtrMessageESt10_Select1stIS4_ESt4lessIlESaIS4_EE10_M_insert_IS0_IlS3_EEESt17_Rb_tree_iteratorIS4_EPSt18_Rb_tree_node_baseSG_OT_()+169  e/c++/4.8.2/new:115
    0x00000000005063b6  srs  _ZNSt8_Rb_treeIlSt4pairIKlP19SrsSharedPtrMessageESt10_Select1stIS4_ESt4lessIlESaIS4_EE15_M_insert_equalIS0_IlS3_EEESt17_Rb_tree_iteratorIS4_EOT_()+96  e/c++/4.8.2/new:115
    0x0000000000505742  srs  _ZNSt8multimapIlP19SrsSharedPtrMessageSt4lessIlESaISt4pairIKlS1_EEE6insertIS4_IlS1_EvEESt17_Rb_tree_iteratorIS6_EOT_()+46  e/c++/4.8.2/new:115
    0x00000000004fb7b2  srs  _ZN11SrsMixQueue4pushEP19SrsSharedPtrMessage()+70  e/c++/4.8.2/new:115
    0x0000000000502aa4  srs  _ZN13SrsLiveSource8on_audioEP16SrsCommonMessage()+426  e/c++/4.8.2/new:115
    0x00000000004f5f8d  srs  _ZN11SrsRtmpConn23process_publish_messageEP13SrsLiveSourceP16SrsCommonMessage()+203  e/c++/4.8.2/new:115
    0x00000000004f5e3b  srs  _ZN11SrsRtmpConn22handle_publish_messageEP13SrsLiveSourceP16SrsCommonMessage()+825  e/c++/4.8.2/new:115
    0x00000000005a5e1e  srs  _ZN20SrsPublishRecvThread7consumeEP16SrsCommonMessage()+254  e/c++/4.8.2/new:115
    0x00000000005a507c  srs  _ZN13SrsRecvThread8do_cycleEv()+266  e/c++/4.8.2/new:115
    0x00000000005a4ee8  srs  _ZN13SrsRecvThread5cycleEv()+112  e/c++/4.8.2/new:115
    0x00000000005233e9  srs  _ZN16SrsFastCoroutine5cycleEv()+191  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x00000000030bcc60  ??
CallStack[227]: memory expires with 40 bytes, 6 times again
CallStack[227]: memory expires with 40 bytes, 7 times again
CallStack[224]: memory expires with 901 bytes, 17 times again
CallStack[226]: memory expires with 48 bytes, 10 times again
CallStack[231]: memory expires with 40 bytes, 2 times again
CallStack[232]: memory expires with 48 bytes, 2 times again
CallStack[228]: memory expires with 40 bytes, 8 times again
CallStack[228]: memory expires with 40 bytes, 9 times again
CallStack[224]: memory expires with 5 bytes, 18 times again
CallStack[225]: memory expires with 48 bytes, 8 times again
CallStack[233]: memory expires with 40 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x000000000041e79f  srs  _ZN19SrsSharedPtrMessage5copy2Ev()+23  e/c++/4.8.2/new:115
    0x000000000041e75f  srs  _ZN19SrsSharedPtrMessage4copyEv()+73  e/c++/4.8.2/new:115
    0x000000000050342a  srs  _ZN13SrsLiveSource8on_videoEP16SrsCommonMessage()+686  e/c++/4.8.2/new:115
    0x00000000004f6008  srs  _ZN11SrsRtmpConn23process_publish_messageEP13SrsLiveSourceP16SrsCommonMessage()+326  e/c++/4.8.2/new:115
    0x00000000004f5e3b  srs  _ZN11SrsRtmpConn22handle_publish_messageEP13SrsLiveSourceP16SrsCommonMessage()+825  e/c++/4.8.2/new:115
    0x00000000005a5e1e  srs  _ZN20SrsPublishRecvThread7consumeEP16SrsCommonMessage()+254  e/c++/4.8.2/new:115
    0x00000000005a507c  srs  _ZN13SrsRecvThread8do_cycleEv()+266  e/c++/4.8.2/new:115
    0x00000000005a4ee8  srs  _ZN13SrsRecvThread5cycleEv()+112  e/c++/4.8.2/new:115
    0x00000000005233e9  srs  _ZN16SrsFastCoroutine5cycleEv()+191  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x00000000030bcc60  ??
CallStack[234]: memory expires with 48 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x00000000005097b3  srs  _ZN9__gnu_cxx13new_allocatorISt13_Rb_tree_nodeISt4pairIKlP19SrsSharedPtrMessageEEE8allocateEmPKv()+73  e/c++/4.8.2/new:115
    0x0000000000509416  srs  _ZNSt8_Rb_treeIlSt4pairIKlP19SrsSharedPtrMessageESt10_Select1stIS4_ESt4lessIlESaIS4_EE11_M_get_nodeEv()+34  e/c++/4.8.2/new:115
    0x0000000000508aef  srs  _ZNSt8_Rb_treeIlSt4pairIKlP19SrsSharedPtrMessageESt10_Select1stIS4_ESt4lessIlESaIS4_EE14_M_create_nodeIJS0_IlS3_EEEEPSt13_Rb_tree_nodeIS4_EDpOT_()+29  e/c++/4.8.2/new:115
    0x000000000050789b  srs  _ZNSt8_Rb_treeIlSt4pairIKlP19SrsSharedPtrMessageESt10_Select1stIS4_ESt4lessIlESaIS4_EE10_M_insert_IS0_IlS3_EEESt17_Rb_tree_iteratorIS4_EPSt18_Rb_tree_node_baseSG_OT_()+169  e/c++/4.8.2/new:115
    0x00000000005063b6  srs  _ZNSt8_Rb_treeIlSt4pairIKlP19SrsSharedPtrMessageESt10_Select1stIS4_ESt4lessIlESaIS4_EE15_M_insert_equalIS0_IlS3_EEESt17_Rb_tree_iteratorIS4_EOT_()+96  e/c++/4.8.2/new:115
    0x0000000000505742  srs  _ZNSt8multimapIlP19SrsSharedPtrMessageSt4lessIlESaISt4pairIKlS1_EEE6insertIS4_IlS1_EvEESt17_Rb_tree_iteratorIS6_EOT_()+46  e/c++/4.8.2/new:115
    0x00000000004fb7b2  srs  _ZN11SrsMixQueue4pushEP19SrsSharedPtrMessage()+70  e/c++/4.8.2/new:115
    0x0000000000503440  srs  _ZN13SrsLiveSource8on_videoEP16SrsCommonMessage()+708  e/c++/4.8.2/new:115
    0x00000000004f6008  srs  _ZN11SrsRtmpConn23process_publish_messageEP13SrsLiveSourceP16SrsCommonMessage()+326  e/c++/4.8.2/new:115
    0x00000000004f5e3b  srs  _ZN11SrsRtmpConn22handle_publish_messageEP13SrsLiveSourceP16SrsCommonMessage()+825  e/c++/4.8.2/new:115
    0x00000000005a5e1e  srs  _ZN20SrsPublishRecvThread7consumeEP16SrsCommonMessage()+254  e/c++/4.8.2/new:115
    0x00000000005a507c  srs  _ZN13SrsRecvThread8do_cycleEv()+266  e/c++/4.8.2/new:115
    0x00000000005a4ee8  srs  _ZN13SrsRecvThread5cycleEv()+112  e/c++/4.8.2/new:115
    0x00000000005233e9  srs  _ZN16SrsFastCoroutine5cycleEv()+191  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x00000000030bcc60  ??
CallStack[229]: memory expires with 40 bytes, 4 times again
CallStack[229]: memory expires with 40 bytes, 5 times again
CallStack[235]: memory expires with 34 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x00007fcb80f39cd9  libstdc++.so  _ZNSs4_Rep9_S_createEmmRKSaIcE()+89
    0x00007fcb80f39e96  libstdc++.so  _ZNSs9_M_mutateEmmm()+102
    0x00007fcb80f3a45e  libstdc++.so  _ZNSs15_M_replace_safeEmmPKcm()+30
    0x000000000041662f  srs  _ZN12SrsCplxError6createEPKcS1_iiS1_z()+243
    0x00000000005232fe  srs  _ZN16SrsFastCoroutine9interruptEv()+110  e/c++/4.8.2/new:115
    0x00000000005231c1  srs  _ZN16SrsFastCoroutine4stopEv()+49  e/c++/4.8.2/new:115
    0x0000000000522d38  srs  _ZN14SrsSTCoroutine4stopEv()+28  e/c++/4.8.2/new:115
    0x00000000005cb2c7  srs  _ZN9SrsNgExec12on_unpublishEv()+43
    0x00000000004fdc3e  srs  _ZN12SrsOriginHub12on_unpublishEv()+202  e/c++/4.8.2/new:115
    0x0000000000504406  srs  _ZN13SrsLiveSource12on_unpublishEv()+72  e/c++/4.8.2/new:115
    0x00000000004f5aff  srs  _ZN11SrsRtmpConn15release_publishEP13SrsLiveSource()+87  e/c++/4.8.2/new:115
    0x00000000004f4b2b  srs  _ZN11SrsRtmpConn10publishingEP13SrsLiveSource()+803  e/c++/4.8.2/new:115
    0x00000000004f235c  srs  _ZN11SrsRtmpConn20stream_service_cycleEv()+3750  e/c++/4.8.2/new:115
    0x00000000004f11d0  srs  _ZN11SrsRtmpConn13service_cycleEv()+1474  e/c++/4.8.2/new:115
    0x00000000004efe1d  srs  _ZN11SrsRtmpConn8do_cycleEv()+2151  e/c++/4.8.2/new:115
    0x00000000004f8012  srs  _ZN11SrsRtmpConn5cycleEv()+50  e/c++/4.8.2/new:115
    0x00000000005233e9  srs  _ZN16SrsFastCoroutine5cycleEv()+191  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x0000000002fcb350  ??
CallStack[236]: memory expires with 47 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x00007fcb80f39cd9  libstdc++.so  _ZNSs4_Rep9_S_createEmmRKSaIcE()+89
    0x00007fcb80f39e96  libstdc++.so  _ZNSs9_M_mutateEmmm()+102
    0x00007fcb80f3a45e  libstdc++.so  _ZNSs15_M_replace_safeEmmPKcm()+30
    0x000000000041664c  srs  _ZN12SrsCplxError6createEPKcS1_iiS1_z()+272
    0x00000000005232fe  srs  _ZN16SrsFastCoroutine9interruptEv()+110  e/c++/4.8.2/new:115
    0x00000000005231c1  srs  _ZN16SrsFastCoroutine4stopEv()+49  e/c++/4.8.2/new:115
    0x0000000000522d38  srs  _ZN14SrsSTCoroutine4stopEv()+28  e/c++/4.8.2/new:115
    0x00000000005cb2c7  srs  _ZN9SrsNgExec12on_unpublishEv()+43
    0x00000000004fdc3e  srs  _ZN12SrsOriginHub12on_unpublishEv()+202  e/c++/4.8.2/new:115
    0x0000000000504406  srs  _ZN13SrsLiveSource12on_unpublishEv()+72  e/c++/4.8.2/new:115
    0x00000000004f5aff  srs  _ZN11SrsRtmpConn15release_publishEP13SrsLiveSource()+87  e/c++/4.8.2/new:115
    0x00000000004f4b2b  srs  _ZN11SrsRtmpConn10publishingEP13SrsLiveSource()+803  e/c++/4.8.2/new:115
    0x00000000004f235c  srs  _ZN11SrsRtmpConn20stream_service_cycleEv()+3750  e/c++/4.8.2/new:115
    0x00000000004f11d0  srs  _ZN11SrsRtmpConn13service_cycleEv()+1474  e/c++/4.8.2/new:115
    0x00000000004efe1d  srs  _ZN11SrsRtmpConn8do_cycleEv()+2151  e/c++/4.8.2/new:115
    0x00000000004f8012  srs  _ZN11SrsRtmpConn5cycleEv()+50  e/c++/4.8.2/new:115
    0x00000000005233e9  srs  _ZN16SrsFastCoroutine5cycleEv()+191  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x0000000002fcb350  ??
CallStack[237]: memory expires with 36 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x00007fcb80f39cd9  libstdc++.so  _ZNSs4_Rep9_S_createEmmRKSaIcE()+89
    0x00007fcb80f39e96  libstdc++.so  _ZNSs9_M_mutateEmmm()+102
    0x00007fcb80f3a45e  libstdc++.so  _ZNSs15_M_replace_safeEmmPKcm()+30
    0x0000000000416694  srs  _ZN12SrsCplxError6createEPKcS1_iiS1_z()+344
    0x00000000005232fe  srs  _ZN16SrsFastCoroutine9interruptEv()+110  e/c++/4.8.2/new:115
    0x00000000005231c1  srs  _ZN16SrsFastCoroutine4stopEv()+49  e/c++/4.8.2/new:115
    0x0000000000522d38  srs  _ZN14SrsSTCoroutine4stopEv()+28  e/c++/4.8.2/new:115
    0x00000000005cb2c7  srs  _ZN9SrsNgExec12on_unpublishEv()+43
    0x00000000004fdc3e  srs  _ZN12SrsOriginHub12on_unpublishEv()+202  e/c++/4.8.2/new:115
    0x0000000000504406  srs  _ZN13SrsLiveSource12on_unpublishEv()+72  e/c++/4.8.2/new:115
    0x00000000004f5aff  srs  _ZN11SrsRtmpConn15release_publishEP13SrsLiveSource()+87  e/c++/4.8.2/new:115
    0x00000000004f4b2b  srs  _ZN11SrsRtmpConn10publishingEP13SrsLiveSource()+803  e/c++/4.8.2/new:115
    0x00000000004f235c  srs  _ZN11SrsRtmpConn20stream_service_cycleEv()+3750  e/c++/4.8.2/new:115
    0x00000000004f11d0  srs  _ZN11SrsRtmpConn13service_cycleEv()+1474  e/c++/4.8.2/new:115
    0x00000000004efe1d  srs  _ZN11SrsRtmpConn8do_cycleEv()+2151  e/c++/4.8.2/new:115
    0x00000000004f8012  srs  _ZN11SrsRtmpConn5cycleEv()+50  e/c++/4.8.2/new:115
    0x00000000005233e9  srs  _ZN16SrsFastCoroutine5cycleEv()+191  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x0000000002fcb350  ??
CallStack[238]: memory expires with 96 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x0000000000416928  srs  _ZN12SrsCplxError4copyEPS_()+42
    0x00000000005234fe  srs  _ZN16SrsFastCoroutine4pullEv()+48  e/c++/4.8.2/new:115
    0x0000000000522d74  srs  _ZN14SrsSTCoroutine4pullEv()+28  e/c++/4.8.2/new:115
    0x00000000005cb316  srs  _ZN9SrsNgExec5cycleEv()+54
    0x00000000005233e9  srs  _ZN16SrsFastCoroutine5cycleEv()+191  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x0000000002f7de90  ??
CallStack[239]: memory expires with 96 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x00000000004167d3  srs  _ZN12SrsCplxError4wrapEPKcS1_iPS_S1_z()+197
    0x00000000005cb34c  srs  _ZN9SrsNgExec5cycleEv()+108
    0x00000000005233e9  srs  _ZN16SrsFastCoroutine5cycleEv()+191  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x0000000002f7de90  ??
CallStack[240]: memory expires with 30 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x00007fcb80f39cd9  libstdc++.so  _ZNSs4_Rep9_S_createEmmRKSaIcE()+89
    0x00007fcb80f39e96  libstdc++.so  _ZNSs9_M_mutateEmmm()+102
    0x00007fcb80f3a45e  libstdc++.so  _ZNSs15_M_replace_safeEmmPKcm()+30
    0x0000000000416802  srs  _ZN12SrsCplxError4wrapEPKcS1_iPS_S1_z()+244
    0x00000000005cb34c  srs  _ZN9SrsNgExec5cycleEv()+108
    0x00000000005233e9  srs  _ZN16SrsFastCoroutine5cycleEv()+191  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x0000000002f7de90  ??
CallStack[241]: memory expires with 52 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x00007fcb80f39cd9  libstdc++.so  _ZNSs4_Rep9_S_createEmmRKSaIcE()+89
    0x00007fcb80f39e96  libstdc++.so  _ZNSs9_M_mutateEmmm()+102
    0x00007fcb80f3a45e  libstdc++.so  _ZNSs15_M_replace_safeEmmPKcm()+30
    0x000000000041681f  srs  _ZN12SrsCplxError4wrapEPKcS1_iPS_S1_z()+273
    0x00000000005cb34c  srs  _ZN9SrsNgExec5cycleEv()+108
    0x00000000005233e9  srs  _ZN16SrsFastCoroutine5cycleEv()+191  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x0000000002f7de90  ??
CallStack[242]: memory expires with 38 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x00007fcb80f39cd9  libstdc++.so  _ZNSs4_Rep9_S_createEmmRKSaIcE()+89
    0x00007fcb80f39e96  libstdc++.so  _ZNSs9_M_mutateEmmm()+102
    0x00007fcb80f3a45e  libstdc++.so  _ZNSs15_M_replace_safeEmmPKcm()+30
    0x0000000000416875  srs  _ZN12SrsCplxError4wrapEPKcS1_iPS_S1_z()+359
    0x00000000005cb34c  srs  _ZN9SrsNgExec5cycleEv()+108
    0x00000000005233e9  srs  _ZN16SrsFastCoroutine5cycleEv()+191  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x0000000002f7de90  ??
CallStack[243]: memory expires with 96 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x00000000004167d3  srs  _ZN12SrsCplxError4wrapEPKcS1_iPS_S1_z()+197
    0x000000000052341a  srs  _ZN16SrsFastCoroutine5cycleEv()+240  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x0000000002f7de90  ??
CallStack[244]: memory expires with 30 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x00007fcb80f39cd9  libstdc++.so  _ZNSs4_Rep9_S_createEmmRKSaIcE()+89
    0x00007fcb80f39e96  libstdc++.so  _ZNSs9_M_mutateEmmm()+102
    0x00007fcb80f3a45e  libstdc++.so  _ZNSs15_M_replace_safeEmmPKcm()+30
    0x0000000000416802  srs  _ZN12SrsCplxError4wrapEPKcS1_iPS_S1_z()+244
    0x000000000052341a  srs  _ZN16SrsFastCoroutine5cycleEv()+240  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x0000000002f7de90  ??
CallStack[245]: memory expires with 47 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x00007fcb80f39cd9  libstdc++.so  _ZNSs4_Rep9_S_createEmmRKSaIcE()+89
    0x00007fcb80f39e96  libstdc++.so  _ZNSs9_M_mutateEmmm()+102
    0x00007fcb80f3a45e  libstdc++.so  _ZNSs15_M_replace_safeEmmPKcm()+30
    0x000000000041681f  srs  _ZN12SrsCplxError4wrapEPKcS1_iPS_S1_z()+273
    0x000000000052341a  srs  _ZN16SrsFastCoroutine5cycleEv()+240  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x0000000002f7de90  ??
CallStack[246]: memory expires with 40 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x00007fcb80f39cd9  libstdc++.so  _ZNSs4_Rep9_S_createEmmRKSaIcE()+89
    0x00007fcb80f39e96  libstdc++.so  _ZNSs9_M_mutateEmmm()+102
    0x00007fcb80f3a45e  libstdc++.so  _ZNSs15_M_replace_safeEmmPKcm()+30
    0x0000000000416875  srs  _ZN12SrsCplxError4wrapEPKcS1_iPS_S1_z()+359
    0x000000000052341a  srs  _ZN16SrsFastCoroutine5cycleEv()+240  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x0000000002f7de90  ??
CallStack[247]: memory expires with 40 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x000000000041e79f  srs  _ZN19SrsSharedPtrMessage5copy2Ev()+23  e/c++/4.8.2/new:115
    0x000000000041e75f  srs  _ZN19SrsSharedPtrMessage4copyEv()+73  e/c++/4.8.2/new:115
    0x00000000004ff831  srs  _ZN12SrsMetaCache19update_previous_vshEv()+125  e/c++/4.8.2/new:115
    0x0000000000504450  srs  _ZN13SrsLiveSource12on_unpublishEv()+146  e/c++/4.8.2/new:115
    0x00000000004f5aff  srs  _ZN11SrsRtmpConn15release_publishEP13SrsLiveSource()+87  e/c++/4.8.2/new:115
    0x00000000004f4b2b  srs  _ZN11SrsRtmpConn10publishingEP13SrsLiveSource()+803  e/c++/4.8.2/new:115
    0x00000000004f235c  srs  _ZN11SrsRtmpConn20stream_service_cycleEv()+3750  e/c++/4.8.2/new:115
    0x00000000004f11d0  srs  _ZN11SrsRtmpConn13service_cycleEv()+1474  e/c++/4.8.2/new:115
    0x00000000004efe1d  srs  _ZN11SrsRtmpConn8do_cycleEv()+2151  e/c++/4.8.2/new:115
    0x00000000004f8012  srs  _ZN11SrsRtmpConn5cycleEv()+50  e/c++/4.8.2/new:115
    0x00000000005233e9  srs  _ZN16SrsFastCoroutine5cycleEv()+191  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x0000000002fcb350  ??
CallStack[248]: memory expires with 40 bytes, backtrace:
    0x00007fcb8061b6b0  libc-2.17.so  malloc()+0
    0x00007fcb80edb18d  libstdc++.so  _Znwm()+29
    0x000000000041e79f  srs  _ZN19SrsSharedPtrMessage5copy2Ev()+23  e/c++/4.8.2/new:115
    0x000000000041e75f  srs  _ZN19SrsSharedPtrMessage4copyEv()+73  e/c++/4.8.2/new:115
    0x00000000004ff8bf  srs  _ZN12SrsMetaCache19update_previous_ashEv()+125  e/c++/4.8.2/new:115
    0x0000000000504475  srs  _ZN13SrsLiveSource12on_unpublishEv()+183  e/c++/4.8.2/new:115
    0x00000000004f5aff  srs  _ZN11SrsRtmpConn15release_publishEP13SrsLiveSource()+87  e/c++/4.8.2/new:115
    0x00000000004f4b2b  srs  _ZN11SrsRtmpConn10publishingEP13SrsLiveSource()+803  e/c++/4.8.2/new:115
    0x00000000004f235c  srs  _ZN11SrsRtmpConn20stream_service_cycleEv()+3750  e/c++/4.8.2/new:115
    0x00000000004f11d0  srs  _ZN11SrsRtmpConn13service_cycleEv()+1474  e/c++/4.8.2/new:115
    0x00000000004efe1d  srs  _ZN11SrsRtmpConn8do_cycleEv()+2151  e/c++/4.8.2/new:115
    0x00000000004f8012  srs  _ZN11SrsRtmpConn5cycleEv()+50  e/c++/4.8.2/new:115
    0x00000000005233e9  srs  _ZN16SrsFastCoroutine5cycleEv()+191  e/c++/4.8.2/new:115
    0x000000000052346c  srs  _ZN16SrsFastCoroutine3pfnEPv()+32  e/c++/4.8.2/new:115
    0x000000000066397f  srs  _st_thread_main()+40  sched.c:363
    0x00000000006641f2  srs  st_thread_create()+306  sched.c:694
    0x0000000002fcb350  ??
CallStack[224]: expired-memory frees after 31 seconds
CallStack[225]: expired-memory frees after 31 seconds
CallStack[227]: expired-memory frees after 31 seconds
CallStack[224]: expired-memory frees after 31 seconds
CallStack[226]: expired-memory frees after 31 seconds
CallStack[228]: expired-memory frees after 31 seconds
CallStack[224]: expired-memory frees after 31 seconds
Warning: too many expired-free at CallStack[224]. will not show this CallStack later

I am going to try some older container versions of 4.0 to see if the problem exists there also.

SRS版本(Version): 4.0.167
SRS的日志如下(Log):

[2021-10-12 09:39:43.903][Trace][17][87276367] XCORE-SRS/4.0.167(Leo)
[2021-10-12 09:39:43.903][Trace][17][87276367] config parse complete
[2021-10-12 09:39:43.903][Trace][17][87276367] write log to console
[2021-10-12 09:39:43.904][Warn][17][87276367][22] stats network use index=0, ip=10.8.13.11, ifname=enp193s0
[2021-10-12 09:39:43.904][Warn][17][87276367][22] stats disk not configed, disk iops disabled.
[2021-10-12 09:39:43.904][Warn][17][87276367][22] SRS/4.0.167 is not stable
[2021-10-12 09:39:43.908][Warn][17][yq40fgq3][22] use public address as ip: 157.XX.XX.XX, ifname=enp195s0

SRS的配置如下(Config):

listen              157.XX.XX.XX:1935 10.8.13.3:1935;
max_connections     10000;
srs_log_tank        console;
srs_log_level       warn;
daemon              off;
http_api {
    enabled         on;
    listen           1985;
}
http_server {
    enabled         on;
    listen          1995;
    dir             ./objs/nginx/html;
}
srt_server {
    enabled on;
    listen 10080;
    maxbw 1000000000;
    connect_timeout 4000;
    peerlatency 300;
    recvlatency 300;
}
vhost __defaultVhost__ {
    http_hooks {
        enabled     on;
        on_publish http://10.8.13.3:8089/srs/on_publish/;
        on_unpublish http://10.8.13.3:8089/srs/on_unpublish/;
        on_play http://10.8.13.3:8089/srs/on_play/;
    }
    publish {
        firstpkt_timeout    30000;
        normal_timeout      15000;
    }
}

重现(Replay)

重现Bug的步骤(How to replay bug?)

Run SRS docker image
Observe memory usage by curl http_api
Connect a single RTMP stream
Observe memory usage again by curl http_api
Disconnect single RTMP stream
Observe memory usage again by curl http_api

期望行为(Expect)

描述你期望发生的事情(Please describe your expectation)

I would expect memory usage after a stream has ended to return to roughly the same level as prior to the stream beginning.

It maybe cache, not leak. Please run for a long time, for example, 10 days, and it leaks if the memory grow all time.

We believe this memory issues occurs when our stream validation system validates a stream key - but the stream does not contain a valid video stream, so only audio is streamed - our transcoding pipeline then rejects the stream, but because the validation server already accepted the connection srs continues to stream the data, but nothing pulls from it...

We are still suffering from this memory issue - it seems to be related to streams which throw the warning/error:
clear gop cache for guess pure audio overflow

Which I thought meant that the stream had no video - I tested this theory by using Wirecast and setting the encoder to only broadcast the audio portion of the RTMP stream - I did not see any of the above warning/error messages in the log even though there was no video
I'm amazed that more users have not reported this issue?

It seems some strange stream causes this issue, the gop cache can't detect the size of audio.

You can disable the gop cache by gop_cache off;, note that without gop cache, viewer need to wait more to see the first frame.
If you need gop cache, you can try to replay this issue, seems it's caused by some pure audio stream, without invalid timestamp.

It's not a general use case for memoty leak, so it's not common.

This is a still a pretty major problem for us, is there any chance you could be persuaded to look at it. We see an SRS instance around once a week do this behaviour. When it happens the node its on slows down all the other connections, introducing buffering up to 100s of clients can be impacted causing a massive degradation of the service.
The problem then becomes worse than this, because the offending user then reconnects and takes out another SRS node, this then repeats and thousands of streams can become impacted quickly, causing a service wide outage. When you combine this with the lack of ip blocking, it leaves SRS vulnerable to a DOS type attack making it very hard to build a reliable User facing service.

这个问题看起来不是内存泄露，而是异常的内容导致缓存增加，比如无法识别的音视频包导致gop cache增大。由于涉及到具体的音视频内容，需要详细看具体是什么内容导致的。
比较简单绕过去的方法，是隔离这部分用户。或者反过来隔离正常的用户，比如将重点用户调度到隔离的SRS节点。
由于内容和用户相关，网络隔离是比较有效的方法。

authors: matclayton ufou winlinvip


text:
fix: set label tag for label, add htmlFor

htmlFor support
use <label>-tag

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


text:
container: Force on anonymous fetches if no config file

We've seen a weird error out of the container stack when we're not authorized to fetch an image, and no pull secret is set up.
e.g.  https://github.com/coreos/fedora-coreos-tracker/issues/1328#issuecomment-1292067775
error: remote error: getting username and password: 1 error occurred:
	* reading JSON file "/run/containers/62011/auth.json": open /run/containers/62011/auth.json: permission denied

We don't want the containers/image stack trying to read the "standard" config paths at the moment for a few reasons; one is that the standard paths conflate "root" and "the system".  We want to support separate pull secrets.  But, it should also work to symlink the authfile.

Draft since I'd like to add tests for this, and it could use some design discussion.
Perhaps we should read the standard container auth paths.  (In the privsep case we'd need some code to read the secret as root).

repo: ostreedev/ostree-rs-ext


text:
Add license file

Of course GPL V3
I love this one ❤

Implemented.

repo: osu-Karaoke/osu-framework-microphone


text:
Click the pop-up window that appears when pairing：faile to communicate with device......

Problems that occur when everything is configured normally

Not sure there's anything I can do about it without any more information.

Under what circumstances will it be impossible to connect?
------------------ 原始邮件 ------------------
发件人:                                                                                "osy/Jitterbug"                                                                                @.>;
发送时间: 2021年9月6日(星期一) 凌晨2:39
@.>;
@.@.>;
主题: Re: [osy/Jitterbug] Click the pop-up window that appears when pairing：faile to communicate with device...... (#25)
Not sure there's anything I can do about it without any more information.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Closing due to insufficient information.

authors: CD-D osy

repo: osy/Jitterbug


text:
Make end screen title left aligned

Headline alignment is central - looks a bit off compared to other H5P content types, I recommend left alignment.

https://github.com/otacke/h5p-game-map/commit/e508b9a5f09db857c7c4a62098f5ca032b6dc124


text:
Keywords within jsx tags are highlighted as errors

Adding jsxRegion to javascriptNoReserved fixes it, although I am not sure it is the best solution.

Fixed in https://github.com/mxw/vim-jsx/commit/bc86a24c3fc8d97c1929963daa588d6fcbe16606

license: Vim


text:
UMAP SPlatters

We'd love to get UMAP Splatters working in JS

test unito

authors: alterfero valentin-feron

repo: otosense/oui


text:
Update block gas target formatting

On the London screen, show the percentage of the gas usage relative to the gas target, like "18,450,975 (+23.01%)" and remove the gas target column.
Use two decimal places when showing the basefee.

will merge this one, although I've hid the london link from homepage, I think we'll probably remove this page in future.

repo: otterscan/otterscan


text:
hw 8

Выполнено ДЗ №
Развернул кластер в яндекс облаке
otus@linux:~$ kubectl get nodes
NAME                        STATUS   ROLES    AGE     VERSION
cl1i8i4254toic9otp36-ixuz   Ready       3m10s   v1.20.11
cl1psh2gs2jl8gst29di-oxyk   Ready       2m47s   v1.20.11
cl1psh2gs2jl8gst29di-upaf   Ready       2m53s   v1.20.11
cl1psh2gs2jl8gst29di-uvam   Ready       2m50s   v1.20.11
Установил микросервисы.
otus@linux:~$ kubectl get pods -n microservices-demo -o wide
NAME                                     READY   STATUS              RESTARTS   AGE   IP             NODE                        NOMINATED NODE   READINESS GATES
adservice-56d56d89cc-t9wcc               0/1     ContainerCreating   0          50s            cl1i8i4254toic9otp36-ixuz
cartservice-c8b9fc586-l4pr8              0/1     ContainerCreating   0          51s            cl1i8i4254toic9otp36-ixuz
checkoutservice-74f4c5464f-9cxtt         1/1     Running             0          52s   10.112.128.9   cl1i8i4254toic9otp36-ixuz
currencyservice-7df4d74b7c-rqjfj         0/1     ContainerCreating   0          50s            cl1i8i4254toic9otp36-ixuz
emailservice-86794489df-b7pqb            1/1     Running             0          53s   10.112.128.8   cl1i8i4254toic9otp36-ixuz
frontend-cf49f7975-x56cj                 0/1     ContainerCreating   0          52s            cl1i8i4254toic9otp36-ixuz
loadgenerator-7fdb874b-r6vh5             0/1     ContainerCreating   0          50s            cl1i8i4254toic9otp36-ixuz
paymentservice-5768d9bb67-p2k5c          0/1     ContainerCreating   0          51s            cl1i8i4254toic9otp36-ixuz
productcatalogservice-84fd74ccc9-9xgq6   0/1     ContainerCreating   0          51s            cl1i8i4254toic9otp36-ixuz
recommendationservice-6fcb597467-cbbwp   0/1     ContainerCreating   0          52s            cl1i8i4254toic9otp36-ixuz
redis-cart-55d76945cb-bwktg              0/1     ContainerCreating   0          50s            cl1i8i4254toic9otp36-ixuz
shippingservice-6bc75ffff-lcj7s          0/1     ContainerCreating   0          50s            cl1i8i4254toic9otp36-ixuz
Установил средством helm
elasticsearch
kibana
fluent-bit
Установил prometheus-operator  в неймспейс observability
Установил loki
helm repo add loki https://grafana.github.io/loki/charts
helm repo update
helm upgrade --install loki loki/loki-stack --namespace observability -f loki.values.yaml
PR checklist:

[ ] Выставлен label с темой домашнего задания

Добрый день!Дз  выполнено верно


text:
Добавить табы в описание продуктов

Когда информации о товаре достаточно много и её разделяют на табы.

Необходимо реализовать табы (например: описание, характеристики, обзоры)
добавить мок данные в описание некоторых товаров,
**сделать возможность открывать указанный таб по дополнительно вложенному URL
тоесть url базовый - /product-detail/1
url и открыть 2й таб - /product-detail/1/tab/2

Взяла в работу! Кристина Малькова

#43

repo: otusteamedu/Vuemmerce


text:
Nova Pagination load-more not Loading More rows

When using then Nova Config: 'pagination' => 'load-more', the HasMany component is not adding the new rows received by the response.

Fixing this would somewhat solve the issue of #10 because you won't need to move it across pages.

Heya! Version 3.3.0 addresses this issue. Please try it out. :) Thanks!

authors: Tarpsvo jjjrmy


text:
[Request] Mind the Time Add-on Theme

First of all, this is an excellent repo! I've been trolling r/FirefoxCSS infrequently for months and only just came across the 3-month-old post. I found the more popular r/Firefox post after a search afterward.
I'm requesting a theme for the Mind the Time add-on! It has a popup and a full summary page. It's a pretty lightweight add-on, so I don't think it would be too difficult to style, but I obviously don't expect you to make it a priority.
Might I also suggest adding a basic color styling guide to fit the theme's design language? That way it would be easier for users to make pull requests for new add-ons. It could be simply comments in the color variables file, or a wiki page with more detailed explanations.

Glad you stumbled across the project @lhindir!
I'll look at Mind the Time when I get a chance :) If it's a lightweight one, I'll probably be able to get to it soon.
That's a good suggestion for the color styling guide though!  I think that would help out a lot as well

Sounds good! Looking forward to it.

Styling for Mind the Time has been added.  If there's any issues with it, feel free to let me know.
Please keep in mind that since I don't use the extension, if problems arise, I won't know about it unless I am notified.

authors: lhindir overdodactyl

repo: overdodactyl/ShadowFox


text:
Allow ignoring specified @Beta interfaces

FindBugs does not provide a plugin configuration mechanism so we use
the system properties instead.  Note that this functionality requires
setting jvmArgs in the findbug-maven-plugin configuration stanza.
Fixes #1.

Any hope of merging this pull request? The Accumulo project has interest in using the plugin but ran into this same problem. See reference above.

@baens @brocarlson @majgis Does Overstock have a maintainer who can merge this and push a release?

@andrewgaul I will ask around...

Looks good to me, I'll get this published here as soon as I can.

Thank you, we are excited to use this plugin.

Bear with me a little bit, this has been a little bit trickier to deploy then I thought. But I am working on it!

Erik, let me know if I can offer any assistance. Deploying to sonatype's
oss server can be a bit daunting the first time :).
On Thu, Sep 21, 2017 at 1:53 PM, Erik Lindblom notifications@github.com
wrote:

Bear with me a little bit, this has been a little bit trickier to deploy
then I thought. But I am working on it!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/overstock/library-detectors/pull/2#issuecomment-331263398,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJZ9ftvOLEnCuEw9R_PZtiDzkZaARe1ks5skr69gaJpZM4CeObx
.

@baens Did a new release of this plugin get published?

@milleruntime thank you thank you for your patients. I have still failed to published and have spent an embarrsing amount of time trying.
@irobertson can you take a try please? The instructions have seem to have changed from the last time (...years ago...) I've tried this and I seem to be playing error wack-a-mole...

I'd be happy to take a stab at this; can you add me as a collaborator to repository so that I can run the maven release plugin? I can also update the changes.xml file, and the https://overstock.github.io/library-detectors/ page.

@irobertson thanks for stepping up.  Any progress on a release?

Thanks for the prod. I finally figured it out; they've changed a fair
amount since the last time I did this. In any case, version 1.2.0 has been
released, and the project site (FWIW) is updated at
http://overstock.github.io/library-detectors/index.html.
http://overstock.github.io/library-detectors/index.html
Sorry for the long delay!

Ian

On Fri, Dec 8, 2017 at 10:56 AM, Mike Miller notifications@github.com
wrote:

@irobertson https://github.com/irobertson thanks for stepping up. Any
progress on a release?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/overstock/library-detectors/pull/2#issuecomment-350329053,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJZ9eOB7zkZVWr07CoF0q2HTM_uMc2tks5s-Xg9gaJpZM4CeObx
.

authors: andrewgaul baens irobertson majgis milleruntime

repo: overstock/library-detectors


text:
是否有接入小程序的计划

小程序登录接口文档 https://mp.weixin.qq.com/debug/wxadoc/dev/api/api-login.html?t=20161122

抱歉，没有这个计划，而且，它是 js 玩法，不需要 PHP 的封装。

并不是纯JS的，用户登录是可以有后端部分的，可以仔细看下文档

repo: overtrue/wechat


text:
[oui-flag]: background-image url

Description
Steps to reproduce

Visit: https://unpkg.com/@ovh-ux/ui-kit@4.0.4/dist/css/oui.css
Search export default
See errors

Expected behavior:
A valid URL should be specified.
Actual behavior:
A wrong URL is defined probably due to an Issue when compiling the styles.
Frequency:
Always.
Additional information
Our current shared webpack configuration is not able to build a package that rely on this version (v4.0.4).

Has been fixed with in this release: https://github.com/ovh/ovh-ui-kit/blob/master/packages/libs/ui-kit/CHANGELOG.md#405-2020-03-26

authors: AxelPeter antleblanc

repo: ovh/ovh-ui-kit


text:
In which version dvr of fip port forwarding is implemented

hello, I used kolla-ansible to deploy openstack yoga and victoria with ovn banckend. And I create floating ip port forwarding. But I found that, in yoga, the  port forwarding traffic flows directly from compute nodes.  In victoria, the  port forwarding traffic still goes through network nodes
I would like to ask, is this related to the neutron version, or is it caused by a different ovn version?
the ovn version in yoga is 22.06.1, and the ovn version in Victoria is 20.03.2

I think this is related to how OVN is deployed so it's probably best to discuss with the kolla-ansible folks

authors: HanGuangyu dceara

repo: ovn-org/ovn


text:
MOVE a file into same folder with same name returns 404 instead of 403

In oCIS
curl -X MOVE -u admin:admin https://localhost:9200/remote.php/webdav/parent.txt \
-H "Destination: https://localhost:9200/remote.php/webdav/parent.txt" -v

Response:
> MOVE /remote.php/webdav/parent.txt HTTP/1.1
> Host: localhost:9200
> Authorization: Basic YWRtaW46YWRtaW4=
> User-Agent: curl/7.68.0
> Accept: */*
> Destination: https://localhost:9200/remote.php/webdav/parent.txt
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< Access-Control-Allow-Origin: *
< Content-Length: 0
< Content-Security-Policy: default-src 'none';
< Date: Wed, 28 Apr 2021 05:01:56 GMT
< Vary: Origin
< X-Content-Type-Options: nosniff
< X-Download-Options: noopen
< X-Frame-Options: SAMEORIGIN
< X-Permitted-Cross-Domain-Policies: none
< X-Robots-Tag: none
< X-Xss-Protection: 1; mode=block

In oC10
curl -X MOVE -u admin:admin http://localhost/core/remote.php/webdav/parent.txt \
-H "Destination: http://localhost/core/remote.php/webdav/parent.txt" -v

Response
> MOVE /core/remote.php/webdav/parent.txt HTTP/1.1
> Host: localhost
> Authorization: Basic YWRtaW46YWRtaW4=
> User-Agent: curl/7.68.0
> Accept: */*
> Destination: http://localhost/core/remote.php/webdav/parent.txt
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 403 Forbidden
< Date: Wed, 28 Apr 2021 05:04:14 GMT
< Server: Apache/2.4.41 (Ubuntu)
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 0
< X-Robots-Tag: none
< X-Frame-Options: SAMEORIGIN
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Set-Cookie: ocjtwb0rhxgi=hnkdelloappo0d76hb85pq8jsq; path=/core; HttpOnly; SameSite=Strict
< Expires: Thu, 19 Nov 1981 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate
< Pragma: no-cache
< Set-Cookie: oc_sessionPassphrase=M63uA%2FZQMmvNHRFA4ZC4LsJawP7p3%2BRk7mgIV%2BmYqzhnORC4%2Bd4CXGilSgfjL6csOguGvokjXhCehBMX%2FEJz9nuyK69wwRbiWIRQX0vVdBpYHQvrtBSdkt1LRUei391c; path=/core; HttpOnly; SameSite=Strict
< Content-Security-Policy: default-src 'none';
< Set-Cookie: ocjtwb0rhxgi=re1crtnse3cop4fi92ivg6pci7; path=/core; HttpOnly; SameSite=Strict
< Set-Cookie: cookie_test=test; expires=Wed, 28-Apr-2021 06:04:14 GMT; Max-Age=3600
< Content-Length: 234
< Content-Type: application/xml; charset=utf-8
<
<?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
  <s:exception>Sabre\DAV\Exception\Forbidden</s:exception>
  <s:message>Source and destination uri are identical.</s:message>
</d:error>

I can confirm that this is happening. local server oCIS version 1.11.0
curl -X MOVE -u admin:admin https://localhost:9200/remote.php/webdav/parent.txt \ -H "Destination: https://localhost:9200/remote.php/webdav/parent.txt" -v get 404 and move file to trash

re-tested with oCIS 1.19.1, still relevant

re-tested with ocis 3.1.0-rc.1+712d98e0a2, still relevant

Added test coverage in https://github.com/owncloud/ocis/pull/8135

While doing MOVE using file-id with Editor role, the server responds 502 instead of 403.
curl -XMOVE -udemo:demo https://localhost:9200/remote.php/dav/spaces/69ab559f-cd8d-42e8-85e3-1ef1e023d736\$9d591cf5-334f-4e40-b651-cecc0cdd8cad\!14627e65-47de-4ccb-9d4e-df0709f73b2f \
-H "Destination: https://localhost:9200/remote.php/dav/spaces/a0ca6a90-a365-4782-871e-d44447bbc668\$a0ca6a90-a365-4782-871e-d44447bbc668/myfolder/afile.txt" -vk

< HTTP/1.1 502 Bad Gateway

<?xml version="1.0" encoding="UTF-8"?>
<d:error xmlns:d="DAV" xmlns:s="http://sabredav.org/ns"><s:exception></s:exception><s:message>cross storage moves are not supported, use copy and delete</s:message></d:error>

authors: ScharfViktor amrita-shrestha saw-jan

repo: owncloud/ocis


text:
Get latest web acceptance tests running in oCIS CI

The web acceptance tests recently started making use of the test middleware to execute various scenario setup Given steps.
The web in oCIS is now being updated, The oCIS drone CI needs to have the test middleware running so that the web tests can pass.
PR #2846 bumps web to 4.6.0 - make CI pass.

web PR https://github.com/owncloud/web/pull/5136 implemented the middleware in web CI. drone starlark changes there are probably what is needed in oCIS.

done in https://github.com/owncloud/ocis/pull/2848
this will be fixed in https://github.com/owncloud/ocis/pull/2846

The commit has been cherry-picked to #2846 and CI is running. Waiting for the result.

https://github.com/owncloud/ocis/pull/2846 has been merged

authors: dpakach phil-davis


text:
webUISharingInternalGroupsEdgeCases/shareWithGroupsEdgeCases.feature:41 is passing on ocis

The scenario webUISharingInternalGroupsEdgeCases/shareWithGroupsEdgeCases.feature:41 was expected to fail but is now passing on OCIS and is causing OCIS to fail in the nightly build.

Todo:

[x] Investigate it (Checked it manually and locally)
[ ] Remove it from expected to failure https://github.com/owncloud/ocis/pull/4198

The passing test has been removed from expected to fail. So closing this issue


text:
enhancement: add Graph API Token Information Endpoint

Description
We have introduced a new endpoint to the Graph API that allows users to retrieve information about a token.
This endpoint serves as the Graph API's counterpart to the GET /ocs/v1.php/apps/files_sharing/api/v1/tokeninfo/unprotected/TOKEN_ID
endpoint in the OCS API, providing users with more comprehensive access to token information.
Related Issue

Fixes https://github.com/owncloud/ocis/issues/8617

Motivation and Context
Decision pending, we have to decide whether to proceed with this implementation or see if we find a cleaner solution without that endpoint.
How Has This Been Tested?

...

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

ToDo:

[x] decide if we need it that way
[ ] Unit tests
[ ] Acceptance tests
[ ] Add to libregraph spec

we've decided to add the info endpoint to the graph api, unfortunately i wasn't able to finalize the ticket before my vacation, @kobergj knows the details and could take it over.


text:
Change result format

The output will be a unique tibble (not a list like now): with the following columns: cohort_definition_id, table_id, table_name, window_id, window_name, concept_id, concept_name, concept_type, concept_count, denominator_count
concept_type will be "Standard", "Non-standard", or "Classification" for the moment all will be "Standard"

@catalamarti Do we still want the obscure counts?

When obscured we will change denominator _count and/or numerator_count to <5

authors: MimiYuchenGuo catalamarti


text:
Hoist list_platforms above option parsing

I noticed the --list CLI command was erroring with a NoMethodError; it's because the method necessary to list the platforms is defined after the option parsing.

Thank you!

authors: gjtorikian ianks

repo: oxidize-rb/rb-sys


text:
🛑 Ox Street is down

In 59264e6, Ox Street (https://oxstreet.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ox Street is back up in 133a97c.

repo: oxstreet/oxstreet-status-page


text:
stuck at "manage merchants" page

Self-hosting, localhost, docker
After login, it'll get stuck on this page. Nothing at all happens

Which version are you using? This issue should be fixed in the latest release

An old one which was release in August.
I've removed the repo, re-cloned it, re-created a docker image, but it still is using on old version:
docker-compose -f docker-compose.local.yml up --force-recreate --build oxygen

[.................]

oxygen-oxygen-1    | {"level":"info","service":"oxygen","version":"2761fee189884718ea48ba32522a17eecf170a5e","env":"production","host":"0830d8b85e3c","channel":"scheduler","cron_spec":"@every 30s","job":"checkIncomingTransactionsProgress","job_id":"checkIncomingTransactionsProgress-1696295488","time":"2023-10-03T01:14:28Z","caller":"/src/internal/app/app.go:306","message":"job completed"}

where 2761fee189884718ea48ba32522a17eecf170a5e is  as hash of v0.5.1
Why?

repo: oxygenpay/oxygen


text:
Adding footer to the website

a footer containing all the important information
pls mark it under hacktoberfest-accepted and hacktoberfest label

assigned to you

thnks

if I contribute on this project, will that be counted on hacktoberfest?
Newbie :(

I want to make the footer section!

if I contribute on this project, will that be counted on hacktoberfest? I want to make the footer section!
Newbie :(

yes, your contribution in this repository will be counted in hacktoberfes
2nd this issue is already assigned to @Vansh16aug , if they dont able to do it then i will assign you.

are there any other issues that I can work on related to html css or react?

Can you plz assign me this issue, if someone is working already then please assign me any other issue

repo: oyepriyansh/DevProfiles

license: Unlicense


text:
Move implementation to BleepScriptRunner

I see that you have refactored BleepScript to just one class. Feel free to close this PR if you're happy with the current design.
But if you entertain me for a sec, I'd like to present to you the rationale for having both BleepScript and BleepScriptRunner: It seemed to me a better, more future-proof design to have

just an interface, unburdened by any implementation, so that we can have a way to refer to all possible plugins, e.g. List[BleepScript], or Map[String, BleepScript], and
a class to make it easier for implementers to create Bloop scripts, hence BleepScriptRunner

Yes, it's two classes instead of one, but the additional complexity is very small, so I think it's worth having it. The benefit being more clean and future-proof design.

I don't think I see the need. The way to talk about more than one script is scripts: JsonMap[ScriptName, JsonList[ScriptDef]] from the model. all the user written scripts may tap into different platforms and so on, so there is no guarantee either way that you can put them all in a list.

authors: oyvindberg sideeffffect

repo: oyvindberg/bleep


text:
Listing Management - "Pending, org." number indicator is cut off when a state is highlighted

When you Highlight a state, numbers show for Published, needs action, Returned, draft...but the number seems to get cut off after pending, org.

Is this the same as #152 or is this something different?

We have so far been unable to reproduce this in order to adjust the styling. Are there any additional details you could provide? @jloveland18

no..i really can't..all i did was go back and forth clicking on all, published, needs action, pending org., returned, and draft..but it doesn't seem to be happeing now..i can't recreate it either at the moment.

authors: clarkjefcoat jloveland18 sdeighan

repo: ozone-development/ozp-center


text:
masked out prefix in val set

In the solution string that the model is being finetuned on, 90% of the string is just MCTS state and goal (problem statement). Those should not be evaluated on, since we do not want to measure whether the model is able to predict the MCTS state and the goal, but we want to measure whether the model is able to predict the next actions to be taken
This PR masks the loss on this 'prefix' s.t. loss is only calculated on the actions.

Should we mask everything except ???Y and ???N instead?

authors: emergenz maharajamihir

repo: p-doom/gc-minimo


text:
Support generic base machines in PSharp compiler

Currently, if in the *.psharp file, if I inherit from a machine that takes generic types, I get a compiler error. This forces me to write all the state machine specification (events and transitions) by hand in CSharp file which is very cumbersome. Another workaround is to create a wrapper/proxy class that inherits from the requisite base class specifying all the generics, and have the real state machine class derive from the proxy class. But that is not very clean.
I try to do (in psharp file):
internal partial machine ZoneProvisioningStateMachine : Test.NameSpace.StateMachineBase<object, object>
The error I get:
#error Psharp Compiler Error   /*   Expected base machine identifier. In TestStateMachine.psharp (line 3):  internal partial machine ZoneProvisioningStateMachine : Test.NameSpace.StateMachineBase<object, object> _______________________________________________________________________________________^   */

I've coded a fix. It is available in PR #305.  We'll merge into master soon but feel free to use that branch if it unblocks your progress.

@akashlal : How can I consume this? Will a new nuget be released?

@muwaqar I'm preparing a new release today. Its been a while since our last one. It'll also resolve the other issue that you reported. If you find yourself running into further issues, perhaps it'll be better to take a source dependence on the master branch if you can.

@muwaqar Uploading a package to nuget.org is going to be delayed (new MS rules). We have set up an internal feed in the meantime. If you want the nuget, email me on my MS account: akashl

authors: akashlal muwaqar

repo: p-org/PSharp


text:
default value should set to AssociatedObject

Default value should set to AssociatedObject.
For example, you have a associated UIView. You don't want to recreate a new view every time you access this value.
@AssociatedObject(.OBJC_ASSOCIATION_RETAIN_NONATOMIC)
var someView: UIView = {
    SomeCustomView()
}()

@p-x9 Have got any more free time to review this MR?🤣 I have two more MR waiting.

This was a critical problem...
Thank you for fixing it.

Oh, you are right. I have encounter this error already🤣 Forget to add this commit.

Thanks for fixing it.
(I know it's hard to update test cases. I think we need to do something about it...)


text:
Issue Loading on GoldenForge due to paper Patches

Debug Information
https://mclo.gs/vR47aIf
Description of behavior
Detects paper patches on load and try to load bukkit side instead of forge.
Reproduction Steps
Run on golden forge
Get error

TaterLib Configuration
DOES NOT MATTER
Additional context
To fix this we just need to get the server branding
as goldenforge does customize that.

Probably will just do a basic reflect-check to grab GoldenForgeEntryPoint
Though the updated branding should show in the Server#brand() method in TaterLib itself.


text:
Remove container after run

Current containers linger after each run of p4runtime-shell, consuming resources:
> docker container ls -a | grep p4lang/p4runtime-sh | wc -l
144

This PR add the --rm Docker flag to automatically remove them after they exited. Since p4runtime-shell is mainly for interactive use and creates a fresh one every time, removing stopped containers should cause any data loss.

Codecov Report

Merging #38 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #38   +/-   ##
=======================================
  Coverage   71.77%   71.77%
=======================================
  Files           6        6
  Lines        2002     2002
=======================================
  Hits         1437     1437
  Misses        565      565

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d4b1182...0d57fa6. Read the comment docs.

authors: codecov-commenter pudelkoM