Dependabot/npm and yarn/tough cookie and lerna 4.1.3

⚠  Dependabot is rebasing this PR ⚠
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

⚠  Dependabot is rebasing this PR ⚠
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

Bumps tough-cookie to 4.1.3 and updates ancestor dependency lerna. These dependencies need to be updated together.
Updates tough-cookie from 4.0.0 to 4.1.3

Release notes
Sourced from tough-cookie's releases.

4.1.3
Security fix for Prototype Pollution discovery in #282. This is a minor release, although output from the inspect utility is affected by this change, we felt this change was important enough to be pushed into the next patch.
4.1.2 -- Patch and Bugfix Release
What's Changed

fix: allow set cookies with localhost by @colincasey in salesforce/tough-cookie#253

Full Changelog: https://github.com/salesforce/tough-cookie/compare/v4.1.1...v4.1.2
4.1.1
Patch Release
What's Changed

fix: allow special use domains by default by @colincasey in salesforce/tough-cookie#249
4.1.1 Patch -- allow special use domains by default by @awaterma in salesforce/tough-cookie#250

Full Changelog: https://github.com/salesforce/tough-cookie/compare/v4.1.0...v4.1.1
4.1.0
v4.1.0
Minor release, focused mainly on resolving reported issues and some minor feature work.
What's Changed

Create CHANGELOG.md by @ShivanKaul in salesforce/tough-cookie#189
Missing param validation issue145 by @medelibero-sfdc in salesforce/tough-cookie#193
Create SECURITY.md by @ShivanKaul in salesforce/tough-cookie#201
Create CODE_OF_CONDUCT.md by @ShivanKaul in salesforce/tough-cookie#200
Fix for issue #195 by @medelibero-sfdc in salesforce/tough-cookie#202
Add explanation and more special-use domains by @ShivanKaul in salesforce/tough-cookie#203
Sync of constructor options for serialization by @medelibero-sfdc in salesforce/tough-cookie#204
Returned null in case of empty cookie value by @vsin12 in salesforce/tough-cookie#196
132 str trim not a function by @awaterma in salesforce/tough-cookie#209
Fix for issue #153 by @medelibero-sfdc in salesforce/tough-cookie#210
Fix permuteDomain with trailing dot by @ruoho-sfdc in salesforce/tough-cookie#216
Issue #213 -- added gh-actions flow for building and testing tough-co… by @awaterma in salesforce/tough-cookie#218
Issue #210 -- Updated workflow to use npm install. by @awaterma in salesforce/tough-cookie#220
@GH-215 -- Tests that document localhost behavior when set as domain. by @awaterma in salesforce/tough-cookie#221
fix: MemoryCookieStore methods should exist on the prototype, not on the class. by @wjhsf in salesforce/tough-cookie#226
Unit test cases for allowSpecialUseDomain option by @colincasey in salesforce/tough-cookie#225
[Snyk] Upgrade universalify from 0.1.2 to 0.2.0 by @snyk-bot in salesforce/tough-cookie#228
React Native Support by @colincasey in salesforce/tough-cookie#227
Adding Updating CODEOWNERS with ECCN as per Export Control Compliance by @svc-scm in salesforce/tough-cookie#223
fix: domain match routine by @colincasey in salesforce/tough-cookie#236
Stop using the internal NodeJS punycode module by @gboer in salesforce/tough-cookie#238
Initial documentation review by @mcarey86 in salesforce/tough-cookie#234
fix: distinguish between no samesite and samesite=none by @colincasey in salesforce/tough-cookie#240
Prepare tough-cookie 4.1 for publishing (updated GitHub actions, move… by @awaterma in salesforce/tough-cookie#242
4.1.0 release to NPM by @awaterma in salesforce/tough-cookie#245

... (truncated)

Commits

4ff4d29 4.1.3 release preparation, update the package and lib/version to 4.1.3. (#284)
12d4747 Prevent prototype pollution in cookie memstore (#283)
f06b72d Fix documentation for store.findCookies, missing allowSpecialUseDomain proper...
b1a8898 fix: allow set cookies with localhost (#253)
ec70796 4.1.1 Patch -- allow special use domains by default (#250)
d4ac580 fix: allow special use domains by default (#249)
79c2f7d 4.1.0 release to NPM (#245)
4fafc17 Prepare tough-cookie 4.1 for publishing (updated GitHub actions, move Dockerf...
aa4396d fix: distinguish between no samesite and samesite=none (#240)
b8d7511 Modernize README (#234)
Additional commits viewable in compare view

Updates lerna from 4.0.0 to 8.0.0

Release notes
Sourced from lerna's releases.

v8.0.0
BREAKING CHANGES

After updating we strongly recommend running lerna repair in your project. This will migrate your lerna.json to the latest and greatest and remove any outdated options.

As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.

node v16 support is dropped because it is end of life

When a node version becomes end of life (EOL) it means that it does not receive any updates or maintenance whatsoever, even if critical security vulnerabilities have been uncovered.
We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:
https://github.com/nodejs/release#release-schedule

lerna's task runner for lerna run now depends on nx v17 instead of v16

lerna run gets to benefit from all of the further performance improvements in the nx v17 task runner behind scenes.

@lerna/child-process is no longer a separately published package

Lerna is a monorepo management tool with versioning and publishing capabilities, it is not a child process manager. There are lots of good options out there in the ecosystem to help you with managing child processes in nodejs, and it does not really make sense to treat some of lerna's implementation details around child processes as if they were a public API. The package will be officially deprecated on npm in the future. You can of course take the code and fork it and adapt it for your own purposes if you wish!

Older packages under @lerna/ on npm have been officially marked as deprecated

Under prior stewardship the lerna repo used to publish a very large (>65) number of packages. The vast majority of these should not form part of the public API of lerna and so they have no longer been published as packages since v6. We have now officially marked them as deprecated packages on the npm registry so that users get clear feedback that they are using packages which are no longer maintained (which they can of course fork and do whatever they want with). NOTE: We have not yet marked @lerna/child-process as deprecated so as not to create noise for lerna v7 users until they have had chance to migrate to v8.
Features

version: add --premajor-version-bump option to force patch bumps for non-breaking changes in premajor packages (#3876) (3b05947)
version: use corepack for install when enabled (#3877) (a3cb7ca)

v7.4.2
7.4.2 (2023-10-27)
Bug Fixes

version: support changelog-presets using async factory funcs (#3873) (bb5e7d7)

v7.4.1
7.4.1 (2023-10-18)
7.4.0 contained a malformed dist directory, please bump to 7.4.1 for the correct artifacts

... (truncated)

Changelog
Sourced from lerna's changelog.

8.0.0 (2023-11-23)
Features

version: add --premajor-version-bump option to force patch bumps for non-breaking changes in premajor packages (#3876) (3b05947)

8.0.0-alpha.0 (2023-11-22)
Features

version: add --premajor-version-bump option to force patch bumps for non-breaking changes in premajor packages (#3876) (3b05947)

7.4.2 (2023-10-27)
Bug Fixes

version: support changelog-presets using async factory funcs (#3873) (bb5e7d7)

7.4.1 (2023-10-18)
Note: Version bump only for package lerna
7.4.0 (2023-10-17)
Features

version: add json option (#3858) (86f22f4)
version: add option to force version update (#3852) (914dd96)

7.3.1 (2023-10-10)
Bug Fixes

core: update package engines.node to correctly include only >=16 (#3861) (0674555)

7.3.0 (2023-09-13)
Bug Fixes

update make-dir to 4.0.0 and npm audit fix (#3828) (373b8bc)

Features

version: add --sync-dist-version option (#3787) (ba8b946)
version: option to not ignore scripts on lock update (#3823) (4843c3c)

7.2.0 (2023-08-29)
Note: Version bump only for package lerna

... (truncated)

Commits

b664840 chore(misc): publish 8.0.0
32d9f63 chore: fix formatting
2ff3705 chore: add missing updates
4f5edee feat!: stop publishing @lerna/child-process (#3909)
4445fce chore(run): enable strict type checking (#3907)
837af93 feat!(deps): update yargs and yargs-parser to latest (#3903)
3b05947 feat(version): add --premajor-version-bump option to force patch bumps for no...
83e3f7a feat!: migrate to nx 17.1 (#3897)
1c19f0d chore(exec): enable strict type checking (#3901)
0a2f1c4 feat!: drop support for Node 16 (#3888)
Additional commits viewable in compare view

Maintainer changes
This version was pushed to npm by jameshenry, a new releaser for lerna since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot recreate

@dependabot recreate


[backport-v2.1][nrf fromtree] twister: fix bug retrieving subtests

During the recent overhaul, some code was left retrieving cases the old way.
Fixes #48897
Signed-off-by: Anas Nashif<EMAIL_ADDRESS>Signed-off-by: Andrzej Głąbek<EMAIL_ADDRESS>(cherry picked from commit f28a8d224098e3fcbccd9ef5e6597502d81a1526)

There is similar problem to this one described by me in this PR:
https://github.com/nrfconnect/sdk-zephyr/pull/884#issuecomment-1243895716
Due to the fact that CI_LIB in Jenkinsfile is not "freeze" with appropriate version, then in PR like this Jenkins try to use the newest version of CI_LIB which is not compatible with older sdk-zephyr branches. I'm still working on solving this problem for the future, but at this moment I can propose only this temporary solution:
I made on my private Jenkins special configuration for this PR which uses older CI_LIB version and it should give us proper test results:
https://jenkins-ncs.nordicsemi.no/blue/organizations/jenkins/buran%2Fpigo%2Fsdk-zephyr/detail/PR-922/3/pipeline/121

@carlescufi Considering the above and that all the integration tests in https://github.com/nrfconnect/sdk-nrf/pull/8921 also passed, could this one be merged?


docs(kuma-cp): add short explanation of high availability

Some questions have come up about this. Let's add a note about this, something that shows up when you search "high availability".
Rendered

a bit xrel https://github.com/kumahq/kuma-website/issues/1951


Dropdown menu is not working on this page

Describe the bug
dropdown menu is not working on this page
https://circuitverse.org/groups/4023
To Reproduce
Steps to reproduce the behaviour:

Go to 'groups'
Click on 'profile'
See error

Screenshots
https://user-images.githubusercontent.com/88880988/151709363-e1299a59-e145-4c6f-8829-2511651a159d.mp4
Expected behaviour

Device Information [optional]:

OS: [windows]
Browser [chrome]

Are you working on this issue? (Yes)

I want to work on this issue, pls asign it to me.

the link which you provided https://circuitverse.org/groups/4023 is unable to acces it shows:
"You are not authorized to do the requested operation"

I am working on it bro

@Arunesh-Tiwari   you can't access it
Log in to your account and create grups and the see error

@vedant-jain03  can you please assign this issue to me

@mudassir1231 I'd like to work on this issue. Can you please direct me to the file/folder where changes can be made!

solved #2739


Add support for TABLESAMPLE

This PR adds support for the TABLESAMPLE option in the following dialects:

Standard SQL: https://jakewheat.github.io/sql-overview/sql-2016-foundation-grammar.html#sample-clause
Snowflake: https://docs.snowflake.com/en/sql-reference/constructs/sample
Hive: https://cwiki.apache.org/confluence/display/hive/languagemanual+sampling
Clickhouse: https://clickhouse.com/docs/en/sql-reference/statements/select/sample

Collateral work includes expanding the use of a constructor function to create Table structs in unit tests to avoid modifying many files when adding default options to the Table struct.

@iffyio please see latest commit

Thanks @yoavcloud and @iffyio


Static openssl and libssh2 deps

I switched to static openssl and libssh2 deps as they where before FMake. So apps will not bundle big openssl dylib
I also set mime type to ios_error.h

Hi,
When I tried to upload a new version of a-Shell using the static versions, as used in this PR, I received an error about a mixture of static libraries in a dynamic framework. Also, when I revert to the dynamic versions of libssh2 and openssl, I received another error:
ERROR ITMS-90066: Invalid MinimumOSVersion. The value for the Info.plist key MinimumOSVersion could not be parsed .

Which I think comes from these lines in the Info.plist in libssh2 and openssl:
 <key>MinimumOSVersion</key>
 <string>ios_version_min</string>

It's no big deal. Did you have the same issues? (it only happens when uploading a release to the AppStore. Everything else works fine).

Hmm.  I will look tomorrow at this.


UNCHANGED now introduces Apalache assignments, if possible

[] Tests added for any new code
[x] Ran make fmt-fix (or had formatting run automatically on all files edited)
[ ] Documentation added for any new functionality
[x] Entry added to UNRELEASED.md for any new functionality

As per our discussions, UNCHANGED x now produces x' := x, instead of x' = x, when x is a NameEx. The behavior in the case of UNCHANGED F[x] remains unchanged; (F[x]') = F[x]

Codecov Report

Merging #1346 (2a4ee1e) into unstable (dec42b8) will decrease coverage by 0.01%.
The diff coverage is 50.00%.

@@             Coverage Diff              @@
##           unstable    #1346      +/-   ##
============================================
- Coverage     75.09%   75.08%   -0.02%
============================================
  Files           333      333
  Lines         10821    10823       +2
  Branches        536      530       -6
============================================
  Hits           8126     8126
- Misses         2695     2697       +2

Impacted Files
Coverage Δ

...yte/apalache/tla/pp/passes/DesugarerPassImpl.scala
0.00% <0.00%> (ø)

...orsyte/apalache/tla/pp/passes/PreproPassImpl.scala
0.00% <0.00%> (ø)

...n/scala/at/forsyte/apalache/tla/pp/Desugarer.scala
83.07% <80.00%> (+0.13%)
:arrow_up:

...he/io/annotations/parser/CommentPreprocessor.scala
92.77% <0.00%> (-1.21%)
: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 dec42b8...2a4ee1e. Read the comment docs.


Watching for files being added

When using globs, e.g. data/**/*.txt it would be nice if ibazel could watch this directory for new file additions and then rebuild. It would be even nicer if one could also specify to just watch for file additions, as e.g. for runfiles there is often no need to actually rebuild and the binary can just pick up the changed files due to it being a symlink.
Not sure how difficult this would be to implement, but with some thoughts/pointers on this I would be happy to look into this as well when I get some time for it.

If you edit a BUILD file that is part of the sources, it should trigger a requery and find files. I looked into the idea of detecting these globs and doing my own globbing. https://github.com/google/skylark/issues/109 is where I asked about it publicly and I believe the analysis in there is correct. It would be great, but unfortunately it is going to take a massive quantity of code to do it. If you have theories on ways we can achieve this, I would LOVE to hear your input.
Thanks!

Yeah, doing it in the way discussed in the ticket would be great i.e. that bazel watcher could parse the build files in parallel or get that information from bazel in a streaming, non-blocking fashion. But given that this is currently not possible I can only think of some kind of heuristics, where we could use buildozer to analyse some of the targets we get back from query (maybe even limiting it to filegroups), as well as the main target itself. Or maybe even simpler, if we have a target we just check if there is a filegroup of name like <target>-globs or <target>-extra-watch-files. None of these solutions are ideal but if well documented and/or opt-in then at least some people can get some file addition watching. What do you think?
Also just thinking about it in theory, what would be nice is to have something akin to the build event protocol / build event service, like loading event protocol, or analysis event protocol where bazel streams the information it finds during loading or analysis phase to a specified service with the nodes of the graph that it finds, and I suppose specifically for the watcher use-case also with some metadata about the original state of the input, i.e. this file is part of that glob.
Thinking about it further, if bazel query could give out some metadata about the original state of the rule attributes that would already help us get there and if ibazel had a flag to allow to set a different --output_base people who know that all of their external repositories are cached in the repository_cache could already make use of parallelization today.
I often like thinking about how could we get to a solution in the most ideal way and how can we actually get to a solution today, hence there are just a lot of thoughts spilled out and they evolved a bit as I was writing but curios to hear your thoughts on the topic.

In my case, I'd settle for something as simple as have ibazel kick bazel when any file is added to the workspace that is not excluded by a .gitignore.
How does ibazel currently tell bazel that something has changed?

How does ibazel currently tell bazel that something has changed?

iBazel uses the bazel query command in ibazel.go to determine the list of files that are included, transitively, in the build. All the BUILD file parsing is left to the Bazel server. The response from the Bazel server is a list of the files that are included and not the list of expressions that are used to find the files. Since we don't have access to the expressions (the input to Bazel) and only have access to the files (the output of Bazel) there is no way for us to get this data out of the current server. In order to get that data we would need to rewrite a large chunk of Bazel in Go. To quote from alandonovan's (omitted @ because I'm merely citing, not trying to drag him into this) response to this question:

it can't be done in less than 10,000 additional lines of Go code. The difference between that functionality and a complete rewrite of 'bazel query' is really very small.

Bazel is written by a team of dozens of full time engineers. I'm a hobbyist who works on this in the fleeting hours after midnight and before bed. 10,000 lines of Go and a nearly complete rewrite is a bit out of scope for me.
That, however, doesn't mean it is out of scope for everyone. If you, or anyone reading this, want to go down the road of reimplementing the rules logic in Go, I would be extremely happy to call into a library you expose.

A minimal approach here might suffice. Would you accept a pull request that adds a new CLI option -watch_for_additions=<directory>? For each instance of that flag, ibazel would watch for new files or directories being added to the given directory (non-recursively), and treat such events as if a dependency of every target had changed.


feat(STONEINTG-837): update url of redhat-appstudio/integration-examples

update url of redhat-appstudio/integration-examples since it is migrated to konflux-ci

Signed-off-by: Hongwei Liu<EMAIL_ADDRESS>Fixes
STONEINTG-837
Description
update url of redhat-appstudio/integration-examples since it is migrated to konflux-ci
Type of change

[ ] Feature
[ ] Bugfix
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Screen shots / Gifs for design review

How to test or reproduce?

Browser conformance:

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

integration-examples has been migrated to konflux-ci, can anyone help to review this PR? Thanks!

/ok-to-test

/lgtm

@Katka92 @jrichter1 Can one you guys verify and add your approval to the PR?

/approve

/approve


[types] add ChainID to user txn

Motivation
Adding ChainId to a user txn, to prevent txns potentially being replayed across networks (chains). The ChainID is represented as a u64
In addition to the regular ChainId, this PR also adds the ReservedChain type to specify chain IDs that are reserved. This enum type is primarily used to increase human readability of chain ID in config files and CLI (is used as an adaptor from string to the actual u64 representation of the chain ID).
Test plan
Checked that CLI and config can consume both human-readable and numeric input of chain ID

some of the changes are uncharted territory for me personally, especially KeyManager/secure/config things, so please take a look and make sure I'm not doing something obviously clowny! @JoshLind

@zekun000 I think we should definitely read it from genesis, otherwise validators with different configs will disagree...

sounds like a good on chain config value :)

Good job on the PR! This looks good to me (besides the ChainId u64 -> Enum), as this is touching a lot of stuff I feel like someone else should approve this :D

not for this pr, but it's worth discussing whether we want to read the chain id from genesis upon start to eliminate two source of truth (config + genesis)

I would prefer that we have it in both the config AND the genesis, this way if my config says "testnet" but I start with the "mainnet" genesis then it won't work. A good way to avoid configuration mistakes and be explicit about what we're doing.

Good job on the PR! This looks good to me (besides the ChainId u64 -> Enum), as this is touching a lot of stuff I feel like someone else than me should approve this :D

I also prefer enums to plain numbers in general, but Move does not have enums... So I would vote for sticking with the u64 to avoid Rust -> Move conversion surprises.

I would prefer that we have it in both the config AND the genesis, this way if my config says "testnet" but I start with the "mainnet" genesis then it won't work. A good way to avoid configuration mistakes and be explicit about what we're doing.

Makes sense, but at what point in the code should we compare genesis to the config and fail?

Thanks for pushing this PR out! It has been a loooong time coming :D!!!!
How did we land on using a u64 to represent the ChainId versus the string earlier? My guess is so that it could be incorporated into the transaction at low cost?
Couple of discussion thoughts / topics:

How do we distinguish against the internal / external / third-party chains?
How do we ensure that admins properly update this value in their config?

One idea we had floating around was to make the ChainId deterministic computation of shared data plus some fixed shared counter. E.g., "ledger version:ledger hash:counter", but that would be a lot of fields and in a string, so not that great... Have we considered a hash?
Also one concern about this being within an "on-chain config" is -- would that make it mutable? Is that a property we want to have? Is it possible to have immutable values in on-chain configs?

Also one concern about this being within an "on-chain config" is -- would that make it mutable? Is that a property we want to have? Is it possible to have immutable values in on-chain configs?

Agreed that we probably don't want this to be an on-chain config because it's immutable. It should just be an ordinary constant written at genesis.

I'm a little confused about immutability, if the mainnet forks do we want to change the chain id e.g. a fork enabling more risk smart contracts? from what I heard from @aching we do, or we simply change it by writeset.

I think immutable is right.  Supporting easy forks doesn't seem to be a use case.  Writeset seems reasonable to me.

How did we land on using a u64 to represent the ChainId versus the string earlier? My guess is so that it could be incorporated into the transaction at low cost?

u64, u32, enum, etc. become a single byte if mainnet is 0.

Couple of discussion thoughts / topics:

How do we distinguish against the internal / external / third-party chains?

I think the only idea is LA will define a set of chains (i.e. mainnet = 0).  Any other chain can pick any id. Perhaps if we want LA could also define ranges for private chains, testnet chains, etc.

How do we ensure that admins properly update this value in their config?

One idea we had floating around was to make the ChainId deterministic computation of shared data plus some fixed shared counter. E.g., "ledger version:ledger hash:counter", but that would be a lot of fields and in a string, so not that great... Have we considered a hash?

This is about a tradeoff of debuggability of safety vs size.  Hash is bigger than a byte. =)

Also one concern about this being within an "on-chain config" is -- would that make it mutable? Is that a property we want to have? Is it possible to have immutable values in on-chain configs?

Agree on immutable.

:umbrella: The latest upstream changes (presumably 2f6a8024c13c9265e524cf4d0c7932c723bc9a8e) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably 0f911dd91fb895f0d06b2af1f86d44df36ca9395) made this pull request unmergeable. Please resolve the merge conflicts.

please also add changes to json-rpc/types/view.rs to show chainID in JSONRPC

as well as updating "json-rpc-spec.md"

LGTM on jsonrpc side.

@bors-libra r=aching

:pushpin: Commit 76a7c36 has been approved by aching

:hourglass: Testing commit 76a7c3689982629946f91db1fdfcf38f4d2568f2 with merge fbd735248052a3621861594f1c16bdcf91f5c2b3...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: aching
Pushing fbd735248052a3621861594f1c16bdcf91f5c2b3 to master...


hakushinring implementation

Hmm I just pulled this and looked at it - something doesn't seem right here... I'm not sure how it's adding attack of all things.

Config: https://viewer.gcsim.app/share/bB4ZUB3xcrLnOAXqENh0C

Hmm I just pulled this and looked at it - something doesn't seem right here... I'm not sure how it's adding attack of all things.

Config: https://viewer.gcsim.app/share/bB4ZUB3xcrLnOAXqENh0C

was not able to reproduce


Install GCC 7.4 on zLinux s390x machines (Can replace 7.3)

Ref: https://github.com/AdoptOpenJDK/openjdk-build/issues/841

Finalised and live - closing


Refactoring db

Why?
Noticing errors that ids bring upon our code and dependency issues, we refactored the codebase to no longer use HashMaps with keys being IDs and switch to ArrayLists eliminating the use for ID's. This also helped conform to CA as IDs were pointing outwards to different layers instead of being self contained.
What?
We went through each use case individually and refactored the code to remove all dependencies of usernames and switch to emails which are a part of the entity itself.  The interface adapter code was modified to receive the entity email data instead of the username, which allowed consistency between club and student entities.
What this means?
Full abstraction between each layer due to the self containment of data in the entity and removal of strong dependencies for the underlying data structure in our codebase. The next step which may be beyond our scope would be to create a wrapper class for our data structure so that any changes to the data structure would require minimal change to the code base such as this one, further conforming to the Open Closed, Liskov and other SOLID principles.
Also, fixed bugs with in memory database by combining all entities into one master ArrayList.
Contributors:
Kabir Kumar & Karl-Alexandre Michaud

Okay, just added all the fixes.
Fred, it turns out that the java docs were not necessary when overriding a method or inheriting a method from a class or when implementing an interface as they are already defined there.
Moving forward, we will keep that in mind. Thanks for checking out the code. Is it ready to be merged?


Remove p class from page_related

Hello Michael
how can I remove this p class from the page_related at the bottom of the page?, some of those pages contain code, they are HTML, if I could remove that or from all the posts from showing its content
The GeoPackage Encoding Standard describes a set of conventions for storing the following within an SQLite database:

Regards,
Rafael

It should use it. How are you using the theme? Ruby gem or remote theme?

I have a Gemfile that says
source "https://rubygems.org"
#gem 'github-pages', '170', group: :jekyll_plugins
gem "github-pages", group: :jekyll_plugins
gem "minimal-mistakes-jekyll"
and in the _config.yml I have
theme                  : "minimal-mistakes-jekyll"
remote_theme             : "mmistakes/minimal-mistakes"
minimal_mistakes_skin    : "dark" #"default" # "air", "aqua", "contrast", "dark", "dirt", "neon", "mint", "plum" "sunrise"

Is the repo public?
Could be any number of things. Caching, using Ruby gem and remote theme at the same time, not pushing content to force a GH Pages rebuild, etc etc etc.

I'm serving it locally with bundle exec jekyll serve and then push it to github

If you're using GitHub Pages then you need to use it as a remote_theme as they don't support 3rd party gems. So you can remove the MM gem from Gemfile and the theme: line from _config.yml
When you say you "push it to github"? Are you pushing the source files (posts' Markdown, includes, etc) or are you pushing the contents of _site to GitHub?
Overriding _includes and _layouts does work, but sounds like to me you have things setup incorrectly. If you can link to a public repo I can let you know pretty quick what's the problem.  It doesn't exist in your repo therefore there's nothing to override the one bundled in the theme.

but how come it doesnt change locally having archive__single.html ?

No exactly sure since I can only test what I see in your actual repo on GH.
But seeing how you have all sorts of other layouts and includes that don't apply to the theme, or the fact that you have both the Ruby gem and remote theme versions installed at the same time... you aren't doing Jekyll any favors. Wires could be getting crossed somewhere.

I got it thanks a lot, yeah I have to check my environment


fix(apps/gc/prow/release): enable report for jenkins-operator

Ref: https://github.com/PingCAP-QE/ci/issues/2186
Signed-off-by: wuhuizuo<EMAIL_ADDRESS>

/approve


Retry failed uploads?

Is it on the roadmap to add automatic retry for failed uploads?

I do not have a road map. Unfortunately, I am not currently working in react native regularly, so this project is not a priority for me. That being said, I think there is a lot of potential to improve this project. I'll file an issue asking if anyone would like to take over and own this project.


Get rid of jQuery dependency.

Taking a look in the code, you're barely using much from jQuery at all. It might make sense to get rid of it as a dependency and use some smaller libraries for Ajax and whatever $.parsecss does.

amen... let me think about it

Fixed https://github.com/tparisi/glam/commit/17548b796ebfc09adc8be6a0ba20db8b23b59e2a


Create New Playbook Solution for Standalone

Required items, please complete
Change(s):

Added existing Playbooks specified below:
a. Enrich multiple entities - AlienVault-OTX
b. Add IP Entity To Named Location
c. Create Zendesk ticket
d. Create-AzureDevOpsTask- this has 2 playbooks of incident and alert

Reason for Change(s):

We want to support playbook for Standalone new solution

Version Updated:

Added 2.0.0 as Data file version

Testing Completed:

Yes, tested it by deploying as a custom deployment way to test and deployment was successful.

Checked that the validations are passing and have addressed any issues that are present:

Yes

@v-amolpatil , please fix the review comments in all the files. i have provided comment at one place only... Thanks!!


@Ignore Annotation is not ignoring fields when inserting an entity..

using version 0.1.0
When using @ignore fields kept saving in Datastore.

Confirmed that this is a bug. The com.jmethods.catatumbo.Ignore Annotation class is missing Runtime Retention and hence and the annotation is not preserved at runtime.

Fixed the issue and added test cases for Insert, Update and Load of fields with @Ignore annotation

@bugyboo - just wanted to thank you for reporting this. Also wanted to let you know that the new version 0.2.0 has a fix for this.

Thanks to you for making this amazing framework. 🌷


gnupg: 2.3.3 -> 2.3.4

Motivation for this change

Update gnupg to 2.3.4
https://dev.gnupg.org/T5654
Remove unneeded SOURCE_DATE_EPOCH patch
Remove unneeded Darwin warning patch
Fix default keyserver patch

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Still building locally

Built OK on x86_64-linux

Builds and run fine on x86_64-darwin.


Increase buffer size

Hi, may I know how I could manually increase the buffer size? I need to send and receive some quite large pieces of data and currently, I'm receiving the "Too long packet" error.
I tried to change MaxBuffer in common.h but it doesn't seem to work for me.

Hello,
That's a great opportunity for you to try out this Pull Request
Let me know how it goes

Hi,
I've tried it. It indeed increases the buffer size, but the problem is that when I get the body of the request with request.body(), the body contains HTTP headers like

Hi,  I've been able to reproduce this by setting the maxBufferSize to 1MB, and sending a 512kb file with the curl command line.  At first glance, it looks like the problem is that the HTTP header parsing only expects headers to appear at the beginning of a message (which makes sense for a 4k limit) - I'll try and address this in my pull request (#83) some time this week(end).

I have checked what curl actually sent with nc. There is only one header at the beginning of the request, and the body is continuous (from what nc received).

By the way, why does the program hangs if I simply change the MaxBuffer to a larger value, say 20 MB? (this is on master, without the PR).

Hello, I am also having a similar issue. To solve it I tried what @koallen suggested and increased the value of MaxBuffer in common.h.  I then recompiled pistache and tried to make a post request with the large amount of data using curl. This however did not work out of the box; it would just hang. I had to add the -H "Expected:" header to my request for it to go through.

@leojcollard so for you it's working if you change MaxBuffer in the master branch and add the header in cURL?

I have tested it again and it worked! @leojcollard
I guess previously there was a typo when I tried to disable the Expect header. So let me try to summarize the situation:

We could adjust MaxBuffer in include/common.h, then make sure requests don't have the Expect header set to 100-continue. If the buffer is too large, you may need to increase the stack size limit with ulimit -s <new-limit>.
Try pull request #83 , but it's quite buggy currently. To make it "work", I have to also increase the BufferSize (include/common.h). But even if I call .maxBufferSize() with 20 MB, I still cannot receive requests of 10 MB+, I can only receive up to a few MBs.

If the buffer is too large, you may need to increase the stack size limit with ulimit -s <new-limit>.
I have experienced the buffer size limitation as well.
For large buffer sizes I would use the heap instead, even if it is for a local function. Performance-wise won't be different, but you avoid an unexpected stack overflow if you are not familiar with the implementation.

I successfully changed the buffer from char buffer[maxSize] to std::unique_ptr<char[]> buffer( new char[maxSize] );, which works fine.

Pistache has had dynamic buffer sizes for a few months.  I'm going to close this ticket as fixed or obsolete.

Thanks. I was not aware of this. Do you mind confirming if #263 is the one that fixes this limitation?

#263 works in that you can set an upper limit on the receive buffer size, and receive up to that many octets.  For my own personal project which uses pistache, I have this set to 256k and it works.  iirc, the author of the PR tested with 4M buffer.  I think that the buffer is allocated on the heap and not the stack, but I no longer recall with certainty.  Try it for yourself!


[SPARK-36900][TESTS][BUILD] Increase test memory to 6g for Java 11

What changes were proposed in this pull request?
Increase JVM test memory from 4g to 6g.
Why are the changes needed?
Running tests under Java 11 fails consistently on a few tests without more memory. The tests do legitimately grab a lot of memory, I believe. It's not super clear why memory usage is different in Java 11, but, also seems fine to just give comfortably more heap to tests for now.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing tests, run manually with Java 11.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/48467/

Seems it fails with OOM in GA.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48500/

I can't quite make out if the test failure is spurious or not, or due to memory?

Since it landed to master/3.2, could you monitor the GitHub Action status on those branches for a while, @srowen ?

Looks like TPC-DS got flaky after this change ..

Hm, weird, I wonder how more memory can cause a problem? is the VM running OOM? (where do I see the error)
I can dial it back to 5g and see how it goes?

Yeah


add temporary drawer

got the drawer anyway, still working on that toolbar

I forgot to change index.js, my bad. It was late last night. I also accidentally created this PR from my master as well...feel free to delete this one so I can create one from the proper branch.


float is not precise enough for UTM coordinates.

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
Autoware can load maps using UTM coordinate system, yet it stores a lot of xyz data using float type.
The problem is that float is not precise enough to manipulate UTM coordinates.
Here is a simple example:
Tokyo station is located at lat=35.6785133, lon=139.763416
With this converter, I get:

MGRS local coordinates: x=88096, y=48996
UTM local coordinates: x=388096, y=3948996

According to this IEEE-754 float converter:

The next representable float value after 88096.0 is 88096.0078125
The next representable float value after 3948996.0 is 3948996.25

In other words, if I use MGRS coordinate system around Tokyo, coordinate float precision is 7 millimeter. If I use UTM, float is only 25 centimeter precise...
One could argue that 7 millimeters is not that precise when using MGRS. Certainly, everyone will agree that 25 centimeters is unacceptable. Unless you are lucky enough to be somewhere with low UTM coordinates, it is basically suicide to use Autoware with UTM maps.
I don't see many solutions:

either Autoware should drop UTM support
or Autoware should use double type everywhere (in such case we would be nm precise even in the worst UTM cases)
or Autoware should move the map frame, so that coordinates expressed in map frame have low values (for example, by changing the map origin to the first point of the map).

Expected behavior
Autoware is precise enough.
Actual behavior
Not precise enough if UTM are used.
Steps to reproduce
N/A
Versions
No response
Possible causes
No response
Additional context
No response

float issue is already known issue in TIER IV.
Since there are many source codes that assumes float at the moment (like PCL), TIER IV decided to use MGRS.
If people prefer to use other coordinate, they can select UTM projector + origin to assign their preferred origin to keep the converted numbers low enough to keep their required precision.
https://github.com/autowarefoundation/autoware.universe/blob/main/map/map_loader/config/lanelet2_map_loader.param.yaml


[NEMO-51] Intermediate data location aware scheduling

JIRA: NEMO-51: Intermediate data location aware scheduling
Major changes:

Implement intermediate data location aware scheduling

Minor changes to note:

N/A.

Tests for the changes:

Existing integration tests which testing large shuffle optimization cover this change.

Other comments:

N/A.

resolves NEMO-51

@johnyangk Thanks for your review! I addressed your comments.


[BUG] Codex hangs when creating a storage request for a big file using the REST api

Describe the bug
I uploaded an MP4 file of 583.7 MB size. When I am trying to create a storage request for this file using the REST API, the codex client hangs and I am not able to make any requests anymore.
To Reproduce
Steps to reproduce the behavior:

Upload a MP4 file with size ~ 500 MB
Get the CID
Create a storage request with these parameters:

{
    "duration":"3600",
    "reward":"2",
    "proofProbability":"3",
    "nodes":"2",
    "tollerance":"0",
    "collateral":"10",
    "expiry":"900"
}

Expected behavior
The storage request is created and I receive the request ID. I am expecting not to be blocked while making the request.
Environment:

OS: Linux Mint
Version: 22
Arch x86_64

Additional context
When the storage request expires, the client is not hanging anymore.
When I kill (Ctrl + C) the client during a hanging phase, the client crashes with these logs.
Traceback (most recent call last, using override)
/home/arnaud/Work/codex/nim-codex/codex.nim(142) codex
/home/arnaud/Work/codex/nim-codex/vendor/nim-chronos/chronos/asyncloop.nim(263) _ZN9asyncloop4pollE
/home/arnaud/Work/codex/nim-codex/vendor/nim-chronos/chronos/asyncfutures2.nim(318) _ZN9asyncloop14futureContinueE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/codex/node.nim(451) _ZN12setupRequest12setupRequestE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/codex/slots/builder/builder.nim(287) _ZN7builder13buildManifestE12SlotsBuilderI10MerkleTreeI2FrI6staticIN18curves_declaration5CurveEEEN9poseidon216PoseidonKeysEnumEE2FrI6staticIN18curves_declaration5CurveEEEE
/home/arnaud/Work/codex/nim-codex/vendor/nim-chronos/chronos/asyncfutures2.nim(318) _ZN9asyncloop14futureContinueE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/codex/slots/builder/builder.nim(288) _ZN13buildManifest13buildManifestE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/codex/slots/builder/builder.nim(257) _ZN7builder10buildSlotsE12SlotsBuilderI10MerkleTreeI2FrI6staticIN18curves_declaration5CurveEEEN9poseidon216PoseidonKeysEnumEE2FrI6staticIN18curves_declaration5CurveEEEE
/home/arnaud/Work/codex/nim-codex/vendor/nim-chronos/chronos/asyncfutures2.nim(318) _ZN9asyncloop14futureContinueE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/codex/slots/builder/builder.nim(270) _ZN10buildSlots10buildSlotsE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/codex/slots/builder/builder.nim(218) _ZN7builder9buildSlotE12SlotsBuilderI10MerkleTreeI2FrI6staticIN18curves_declaration5CurveEEEN9poseidon216PoseidonKeysEnumEE2FrI6staticIN18curves_declaration5CurveEEEE25range09223372036854775807
/home/arnaud/Work/codex/nim-codex/vendor/nim-chronos/chronos/asyncfutures2.nim(318) _ZN9asyncloop14futureContinueE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/codex/slots/builder/builder.nim(231) _ZN9buildSlot9buildSlotE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/codex/slots/builder/builder.nim(206) _ZN7builder13buildSlotTreeE12SlotsBuilderI10MerkleTreeI2FrI6staticIN18curves_declaration5CurveEEEN9poseidon216PoseidonKeysEnumEE2FrI6staticIN18curves_declaration5CurveEEEE25range09223372036854775807
/home/arnaud/Work/codex/nim-codex/vendor/nim-chronos/chronos/asyncfutures2.nim(318) _ZN9asyncloop14futureContinueE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/codex/slots/builder/builder.nim(212) _ZN13buildSlotTree13buildSlotTreeE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/codex/slots/builder/builder.nim(171) _ZN7builder13getCellHashesE12SlotsBuilderI10MerkleTreeI2FrI6staticIN18curves_declaration5CurveEEEN9poseidon216PoseidonKeysEnumEE2FrI6staticIN18curves_declaration5CurveEEEE25range09223372036854775807
/home/arnaud/Work/codex/nim-codex/vendor/nim-chronos/chronos/asyncfutures2.nim(318) _ZN9asyncloop14futureContinueE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/codex/slots/builder/builder.nim(196) _ZN13getCellHashes13getCellHashesE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/codex/slots/builder/builder.nim(136) _ZN7builder14buildBlockTreeE12SlotsBuilderI10MerkleTreeI2FrI6staticIN18curves_declaration5CurveEEEN9poseidon216PoseidonKeysEnumEE2FrI6staticIN18curves_declaration5CurveEEEE25range0922337203685477580725range09223372036854775807
/home/arnaud/Work/codex/nim-codex/vendor/nim-chronos/chronos/asyncfutures2.nim(318) _ZN9asyncloop14futureContinueE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/codex/slots/builder/builder.nim(157) _ZN14buildBlockTree14buildBlockTreeE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/codex/stores/repostore/store.nim(73) _ZN5store8getBlockE3refIN5types25RepoStorecolonObjectType_EEN3cid3CidE25range09223372036854775807
/home/arnaud/Work/codex/nim-codex/vendor/nim-chronos/chronos/asyncfutures2.nim(318) _ZN9asyncloop14futureContinueE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/codex/stores/repostore/store.nim(74) _ZN8getBlock44getBlock
/home/arnaud/Work/codex/nim-codex/codex/stores/repostore/operations.nim(55) _ZN10operations15getLeafMetadataE3refIN5types25RepoStorecolonObjectType_EEN3cid3CidE25range09223372036854775807
/home/arnaud/Work/codex/nim-codex/vendor/nim-chronos/chronos/asyncfutures2.nim(318) _ZN9asyncloop14futureContinueE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/codex/stores/repostore/operations.nim(59) _ZN15getLeafMetadata15getLeafMetadataE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/vendor/nim-datastore/datastore/typedds.nim(98) _ZN7typedds3getE3refIN7typedds30TypedDatastorecolonObjectType_EEN3key3KeyE
/home/arnaud/Work/codex/nim-codex/vendor/nim-chronos/chronos/asyncfutures2.nim(318) _ZN9asyncloop14futureContinueE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/vendor/nim-datastore/datastore/typedds.nim(101) _ZN3get45get
/home/arnaud/Work/codex/nim-codex/vendor/nim-datastore/datastore/leveldb/leveldbds.nim(43) _ZN9leveldbds3getE3refIN9leveldbds32LevelDbDatastorecolonObjectType_EEN3key3KeyE
/home/arnaud/Work/codex/nim-codex/vendor/nim-chronos/chronos/asyncfutures2.nim(318) _ZN9asyncloop14futureContinueE3refIN7futures26FutureBasecolonObjectType_EE
/home/arnaud/Work/codex/nim-codex/vendor/nim-datastore/datastore/leveldb/leveldbds.nim(45) _ZN3get59get
/home/arnaud/Work/codex/nim-codex/vendor/nim-leveldbstatic/leveldbstatic.nim(230) _ZN13leveldbstatic3getE3refIN13leveldbstatic23LevelDbcolonObjectType_EE6string
/home/arnaud/Work/codex/nim-codex/vendor/nim-leveldbstatic/vendor/db/c.cc(206) leveldb_get
/home/arnaud/Work/codex/nim-codex/vendor/nimbus-build-system/vendor/Nim/lib/system/excpt.nim(631) signalHandler
/home/arnaud/Work/codex/nim-codex/vendor/nimbus-build-system/vendor/Nim/lib/system/excpt.nim(314) _ZN6system18rawWriteStackTraceE3varI6stringE
/home/arnaud/Work/codex/nim-codex/vendor/nimbus-build-system/vendor/Nim/lib/system/stacktraces.nim(59) _ZN11stacktraces30auxWriteStackTraceWithOverrideE3varI6stringE
SIGSEGV: Illegal storage access. (Attempt to read from nil?)
./start-client-node.sh: line 9: 360563 Segmentation fault      (core dumped)

When you POST to /storage/request/{cid}, the following work is being done by the application:

Erasure coding: expands the dataset (if you have 5 nodes + 5 tolerance, the dataset will be 2x as large after EC)
Slot building: Organize the expanded dataset into a number of slots.
For each slot, we build a new merkle tree with poseidon2 hashing (which is actually built on top of tiny poseidon2-trees of each block)
With all the slot roots, we build a new dataset root with poseidon2

The hashing and erasure-coding a CPU-intense operations. None of this is being performed on a separate thread. If you have a large dataset, this process might take a while and the app will be completely unresponsive during that time. This is a real problem, not just for users but also: during this time the app doesn't respond to network traffic. Other nodes may consider your node lost, and drop you from their routing tables.
Needless to say, this is something client-team has to fix. An obvious approach would be to move the erasure-coding/slot-building to another thread. Ideally, the API would have a "work object" that represents the inputs, outputs, and status of this entire process, so that the user could have some feedback (and the POST itself wouldn't need to block till it's finished).

This will be addressed by:

#854 (required so we can offload the EC to a separate thread)
#808 (moves prover to another thread)


Is it possible to use moead with 3 objectives in version 1.6.0?

This is my implementation of MOEAD that I wrote following the documentation:
algorithm = MOEAD(
                problem=problem,
                population_size=100,
                crossover=DifferentialEvolutionCrossover(CR=1.0, F=0.5, K=0.5),
                mutation=PolynomialMutation(probability=1.0 / problem.number_of_variables(), distribution_index=20),
                aggregative_function=Tschebycheff(dimension=problem.number_of_objectives()),
                neighbor_size=12,
                neighbourhood_selection_probability=0.7,
                max_number_of_replaced_solutions=2,
                weight_files_path='resources/MOEAD_weights',
                termination_criterion=StoppingByEvaluations(max_evaluations=10000)
            )

When I try to run MOEAD using a 3-objective problem I get the following error:
FileNotFoundError: Failed to initialize weights: resources/MOEAD_weights/W3D_100.dat not found
But, looking in the library installed on my computer via pip, there is no 'resources' folder.
Is there a solution for this problem?
Thank you in advance for your responses

Hi.
You can find the resources folder in the project repository (https://github.com/jMetal/jMetalPy).
Regards,
Antonio

Hi, thank you for your answer.
Where should I put the resources folder? Because I tried putting it in the root of the jmetalpy library at the same level as the algorithm, core, lab and so on folders but it doesn't work.
I also tried putting it one level above (so in the python3.11 site-packages folder) but it is not found there either when running MOEAD

Hi. You can find the resources folder in the project repository (https://github.com/jMetal/jMetalPy).
Regards,
Antonio

Hi, thank you for your answer.
Where should I put the resources folder? Because I tried putting it in the root of the jmetalpy library at the same level as the algorithm, core, lab and so on folders but it doesn't work.
I also tried putting it one level above (so in the python3.11 site-packages folder) but it is not found there either when running MOEAD

Hi.
You can find the resources folder in the project repository (https://github.com/jMetal/jMetalPy).
Regards,
Antonio

How are you running the algorithm?. The point is to set the working directory to the root of the jMetalPy project.
In my case, I use PyCharm as IDE and I have modified the run configuration to set it:

I followed your advice and was able to solve the problem. i mistakenly thought i should put the resources folder inside the library folder but instead i should put it in the root of my project.
Thank you very much for your help :D
Just one more question. I saw that there are various files in the resources folder but there is no one related to a weight of 24. Do you know how I can calculate it?
I saw that in the class neighborhood.py inside the utils folder of jmetalpy there is this note:
"""Precomputed weights from

        * Zhang, Multiobjective Optimization Problems With Complicated Pareto Sets, MOEA/D and NSGA-II

        Downloaded from.

        * http://dces.essex.ac.uk/staff/qzhang/MOEAcompetition/CEC09final/code/ZhangMOEADcode/moead030510.rar
        """

The problem is that the link doesn't work and I was hoping there would be a reference on how to calculate the weights

MOEA/D relies heavily on weight vectors to produce high quality diversity fronts. These vectors depends of the number of objectives and the population size. Just compare the results of optimizing the DTLZ1 problem with a population of 91 and a population of 100. One method to produce such weight vectors is the Das Dennis algorithm (https://github.com/jMetal/DasDennis).
You can take a look to the resources folder of the jMetal project (https://github.com/jMetal/jMetal/tree/main/resources/weightVectorFiles/moead) to find files containing weight vectors.


ssl certificate error for data download

I am getting a certificate error when attempting to download the model data.
This happens with fresh installs on Mac OS X with both Anaconda Python 2 and 3 with spacy installed with either conda (version 0.100.7) or pip (version 0.101.0).
Spacy installs correctly, but when I run python -m spacy.en.download, the following error occurs.
Traceback (most recent call last):
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/runpy.py", line 174, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/site-packages/spacy/en/download.py", line 13, in <module>
    plac.call(main)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/site-packages/plac_core.py", line 328, in call
    cmd, result = parser.consume(arglist)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/site-packages/plac_core.py", line 207, in consume
    return cmd, self.func(*(args + varargs + extraopts), **kwargs)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/site-packages/spacy/en/download.py", line 9, in main
    download('en', force)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/site-packages/spacy/download.py", line 24, in download
    package = sputnik.install(about.__title__, about.__version__, about.__models__[lang])
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/site-packages/sputnik-0.9.3-py2.7.egg/sputnik/__init__.py", line 37, in install
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/site-packages/sputnik-0.9.3-py2.7.egg/sputnik/index.py", line 84, in update
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/site-packages/sputnik-0.9.3-py2.7.egg/sputnik/session.py", line 43, in open
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/urllib2.py", line 429, in open
    response = self._open(req, data)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/urllib2.py", line 447, in _open
    '_open', req)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/urllib2.py", line 407, in _call_chain
    result = func(*args)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/urllib2.py", line 1241, in https_open
    context=self._context)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/urllib2.py", line 1195, in do_open
    h.request(req.get_method(), req.get_selector(), req.data, headers)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/httplib.py", line 1057, in request
    self._send_request(method, url, body, headers)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/httplib.py", line 1097, in _send_request
    self.endheaders(body)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/httplib.py", line 1053, in endheaders
    self._send_output(message_body)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/httplib.py", line 897, in _send_output
    self.send(msg)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/httplib.py", line 859, in send
    self.connect()
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/httplib.py", line 1278, in connect
    server_hostname=server_hostname)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/ssl.py", line 353, in wrap_socket
    _context=self)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/ssl.py", line 601, in __init__
    self.do_handshake()
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/ssl.py", line 838, in do_handshake
    match_hostname(self.getpeercert(), self.server_hostname)
  File "/Users/iain/anaconda3/envs/py2/lib/python2.7/ssl.py", line 272, in match_hostname
    % (hostname, ', '.join(map(repr, dnsnames))))
ssl.CertificateError: hostname 'index.spacy.io' doesn't match either of '*.s3.amazonaws.com', 's3.amazonaws.com'

though almost certainly connected with Issue 485

I'd say this is a side-effect of 485, yes --- closing this.

Should hopefully be fixed now – just posted this in #507:

We've been moving the site over to new servers and fixing the SSL certificate to finally address the model downloading issues. The problem was that @honnibal was using CloudFlare's "flexible" SSL option. We now got rid of that and installed a certificate from Let's Encrypt (which is great, btw!)
Make sure to flush your DNS cache before you reload and try again:
In Chrome: chrome://net-internals/#dns
On Mac / OSX 10.11+: sudo dscacheutil -flushcache
Alternatively, you can also use Google Public DNS, which has already updated. That's also what we used for debugging internally for the past few hours. Unfortunately, the DNS is still propagating and seems to be taking forever (see here for the current status).

If you're still having problems, let us know over at #507.


Release for opam package?

I would like to have nproc in the main opam repository. Would you consider making a release including fixes since 0.5.1?

Hey, I started using Nproc for some of my projects and don't mind maintaining it, so I'll go ahead and create an opam package for it.
You can transfere the ownership of the repository to my username instead of deleting this repo.
I already forked it but if you decide to transfere it I can delete my fork (the opam package will work seamlessly since the URL will be the same).
Let me know if you have any additional suggestions.

@rizo Great. I gave you admin rights to MyLifeLabs/nproc which I believe will let you transfer it to your account. Let me know how it goes.

Hey, thanks! I am adding the project to the opam repository (here), as soon as it gets merged I'll make the switch!

Obviously I was not the best candidate for the job: took me half a year to answer your message, sorry about that. Anyway @rizo thanks for publishing nproc to opam!

Hey! I'm thinking about moving my fork of nproc (the one that is published on opam`) to ocaml-cummunity. I think it will benefit from this since I practically haven't made any changes since the release.
@mjambon I think it would be better to either archive this repo or leave a link to the ocaml-community one once I move it. What do you think?

@rizo I'd rather move the original, which has 3 super old issues and 4 forks including yours. I think only yours may be active. To avoid orphaning the forks, it may be best to move the original to ocaml-community rather than your fork. If this seems like a good idea to you, please submit a request to merge your fork. I'm adding you as a team member so you can take care of the transfer.


feature request: pvc accessmode configurable

Can you please add the feature to make the PVC Accessmode configurable.
It would only comprise of changing both entries in the _pvcSpec.tpl:
accessModes:
        - "ReadWriteOnce"

to
accessModes:
        - {{ .accessMode }}

Thanks for raising this @n-able-consulting.


Adding Audio tracks and Subtitle tracks column

Hi there LesFerch,
I would like to know if there is a way to add Audio tracks and Subtitle tracks column in WinSetView. I use these columns frequently for video editing MKV files.
These columns may not be from the stock Windows explorer column, but obtained after installing audio/video codec pack like K-Lite Codec Pack.
Sincere.

I'll take a look and get back to you.

I have those properties from Icaros.
Here's a dump using PropertySystemView:
Icaros.AudioTracks,Audio tracks,,,Yes,Yes,String,No,"{6F6B78A7-F4A2-4F9F-86B1-C6AAA6DEC9A5},4",,1638
Icaros.BitDepth,Bit depth,,,Yes,Yes,Unsigned Integer (4-Byte),No,"{306F083E-E7A8-4315-A3B6-63E9564E00B8},8",,1639
Icaros.ContainsChapters,Contains chapters,,,Yes,Yes,Boolean,No,"{3FA85462-4CB5-49F7-A8C9-A5E902BEFE90},7",,1640
Icaros.ContentCompression,Content compression,,,Yes,Yes,String,No,"{819B1E2D-989A-4346-A436-F2A8F67F19B3},6",,1641
Icaros.SubtitleGroup,Subtitles,,,Yes,Yes,Null,No,"{7CE8A423-7DE1-461D-9CB9-A9F9798FB505},7",,1642
Icaros.SubtitleTracks,Subtitle tracks,,,Yes,Yes,String,No,"{451B194C-28E4-4AFE-B3C1-2A04E616359C},5",,1643
Icaros.VideoTracks,Video tracks,,,Yes,Yes,String,No,"{EC59938F-E25E-4592-82E3-8013018EDB74},3",,1644
This will be challenging. WinSetView currently only includes System properties that are on all machines.
Providing a facility to import additional properties might be doable, but it will be a big project. I'll try to work on it this winter.

WinSetView 2.95 now includes the Icaros properties. They will be shown only if that property handler is installed.


Fix file_idx type to uint16_t from 11 bits.

file_idx type is NOT uint16_t, provide 11 bits.
if file_idx is 2691
file_idx = 2691 (0b101010000011) <-- 12bits
file_idx provides 11 bits.
so, file_idx variable changed from 2691(0b101010000011) to 643(0b01010000011).
https://bugs.llvm.org/show_bug.cgi?id=39816

Thanks for the patch. This should go into lldb on llvm.org first and then should be cherry-picked here if need be.

Thank you.
I will check this bug in next version.
we have being use custom lldb. T T


Is this rx-resume site affiliated with Reactive Resume?

Hi creators of Reactive Resume, is this domain yours?
https://rx-resume.web.app/
If so, the new-line and nested lists markdown doe not appear to be working - among other markdown functions.
Cheers, and thanks!

No, they are not associated in any way with Reactive Resume. You can import a reactive resume in rx-resume though.

Actually it is the same Reactive Resume, but one of the very first and initial versions of the app.
I have had 2 earlier versions, https://v1.rxresu.me and https://v2.rxresu.me
There's no more support for these versions anymore, but those who continue to maintain their resume on the platform could have a way to do so.


x/vuln: read goos/goarch from binary instead of current environment

We should read goos/goarch from the binary itself the same way we do Go version, instead of the current environment.

Fixed in https://go-review.git.corp.google.com/c/vuln/+/430035.


[1.11] Logistical transporter

The logistical transporter pipes do not work correctly with vanilla chests (and possibly other storages). Items are being overwritten when they should be added to the chest.
How to reproduce:

Place a chest with a pipe on top, with a chest on top of that.
Put a stack items in the top chest
Change the upper part of the pipe to PULL with a configurator
Watch the bottom chest.

It's not only the Logistical transporter, it's also any factory block with autosort on. Every block which is moved to another slot gets deleted.

@aidancbrady the original issue (first post of this) isn't solved in the latest version.


Seed ratio stats (amount or % of data sent to peers)

What version of WebTorrent Desktop? (See the 'About WebTorrent' menu)
0.12.0 (0.96.3)
What operating system and version?
Gentoo Linux Base System 2.2 x86_64
What did you do?
It would be great for persons still on a limited internet quota/month to get info on how much a completed torrent in "seed mode" has been seeded already.
What did you expect to happen?
Have a way to check the amount of data seeded / torrent
What actually happened?
No way to do it for now.
Thank you for your great work, the overall out of the box experience is SPLENDID ! Kudos !

@Myu-Unix instead of showing a per-torrent seed ratio (which I think will be too much UI clutter), how about adding an option to limit the seed ratio?
For people on metered connections, that sounds more directly useful. See #435
Do you think that would be enough?

Thank you for your great work, the overall out of the box experience is SPLENDID ! Kudos !

Glad you like it!


On-Premises links go to 404s

Both links to on-premises info go to 404s.

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

ID: b815d4ba-337b-3edf-dbe5-85c373949dd4
Version Independent ID: e85a164c-287a-a404-f798-e490ae802804
Content: New-PnPTenantSite (SharePointPnPPowerShell)
Content Source: sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSite.md
GitHub Login: @Techwriter40
Microsoft Alias: kirks

Hello @SteveClements
how are you?
Even though the PnP documentation articles are on this repository, I need to kindly redirect you to open PnP cmdlets issues here, in that repository, where a member of the PnP community will be able to correct the article with your feedback.
The documentation for PnP cmdlets is then sync from that repo into this one.
Thank you!

@get-itips Thank you very much for the contribution and sharing this explanation. @SteveClements Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


add version-locked psycopg2 and openssl to environment avoid problems

also adds the click package, which is needed for the CLI

Tested the new environment.yml and also works for me.


Support initialDirectory and title in Linux' showOpenDialog

This was #496, which is quite old and already merged, but I just now realized it was never merged to linux-1547.

I suppose you have already tested (I didn't) and since is the same as the one already merge I'm going for it.
Thank you.


pre load data

There is a delay in loading data for every request in the function where_is_point.
...
    land_shp = gpd.read_file('./data/natural_earth/land/ne_10m_land.shp')
...
    water_shp = gpd.GeoDataFrame(pd.concat([gpd.read_file(shp) for shp in water_shp_files], ignore_index=True))

same for loading clima model data.
I suggest loading data during the initial phase, while the question is being typed or the coordinates are being selected. Here is an example, thanks to 4o:
import threading
import time

# Function to load data in the background
def load_data():
    print("Loading data...")
    time.sleep(5)  # Simulate a delay in data loading
    print("Data loading completed.")

# Start the data loading thread
data_thread = threading.Thread(target=load_data)
data_thread.start()

# Handle user input in the main thread
user_input = input("Please enter something: ")
print(f"User input: {user_input}")

# Ensure the data loading thread has completed
data_thread.join()
print("Main thread is done.")

Pre loading data make sense, as we need them for every call anyway. I would constantly try to optimise the loading sown the road, as there is nothing worse than a slow app :)


Chore/project init

Summary by CodeRabbit

New Features

Introduced Continuous Integration (CI) workflows for automated testing and building on main branch updates and pull requests.
Added commit message validation and pre-commit checks using Husky to improve code quality and commit standards.

Refactor

Updated ESLint configurations across various applications and packages for better code analysis and consistency.
Reorganized ESLint settings for Node.js applications, React libraries, and the monorepo root to enhance coding practices.

Chores

Implemented base lint-staged configurations to automate linting and fixing of code issues during commits.

@coderabbitai review


(BOLT-914) Clean up Bolt-as-a-library includes

When loading Bolt as a library, the main entry point is bolt/executor.
It previously required Config and CLI, both of which are unnecessary for
the Executor. Clean up config so bolt and bolt/executor don't bring
in unused files, especially the CLI (which loads r10k and is not as
careful about side-effects).

Ran through acceptance tests as well.

Tested that it fixes https://github.com/puppetlabs/puppetlabs-reboot/pull/171 as well.

can we try to run the puppet_agent package tests with this commit

Tested both https://github.com/puppetlabs/bolt/pull/662 and https://github.com/puppetlabs/puppetlabs-puppet_agent/tree/master/task_spec.


VB.Net RAT

RAT VB.Net

I'm sorry I will not convert this to vb.net. but you are welcome to do it and share it.


Fix issue with checkbox checking and unicode

fix #16147
It would be better if goldmark could output the character position but it fixes the issue.

Codecov Report

Merging #16148 (5a52c76) into main (15fbf23) will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main   #16148      +/-   ##
==========================================
+ Coverage   44.57%   44.60%   +0.02%
==========================================
  Files         699      699
  Lines       82765    82765
==========================================
+ Hits        36896    36918      +22
+ Misses      39888    39868      -20
+ Partials     5981     5979       -2

Impacted Files
Coverage Δ

routers/api/v1/repo/pull.go
28.74% <0.00%> (+0.59%)
:arrow_up:

modules/queue/workerpool.go
55.34% <0.00%> (+1.52%)
:arrow_up:

modules/log/file.go
75.39% <0.00%> (+1.58%)
:arrow_up:

modules/notification/mail/mail.go
40.00% <0.00%> (+2.10%)
:arrow_up:

modules/queue/manager.go
68.36% <0.00%> (+2.82%)
:arrow_up:

modules/charset/charset.go
75.75% <0.00%> (+4.04%)
:arrow_up:

services/mailer/mail_comment.go
85.18% <0.00%> (+7.40%)
:arrow_up:

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 15fbf23...5a52c76. Read the comment docs.


Jaeger fragile in the face of cassandra failures

We've been observing Jaeger components - specifically the collectors and query - fail to recover after Cassandra has any sort of outage. While Cassandra reliability is clearly not a topic for here ;), Jaeger's resilience to issues is.
What we see happen is this a stuck process which is only logging one thing even hours after the issue is fixed... gocql: no hosts available in the pool
What we'd like to see happen is a recovery after a few minutes without manual intervention. This is related to, but distinct from, #562

That sounds like a bug in the gocql though, not Jaeger directly.

we have a fixit week coming up, & want to try upgrading the driver

@burmanm whether it is a bug in gocql or not doesn't really matter:

if it is a gocql bug; until it is both fixed and the updated version is in use, Jaeger will still be suffering the issue, and so a tracking bug is relevant
if it isn't (or if gocql say they won't fix because of some reason), then a local workaround needs to be done to solve the issue.

Either way, a bug in this repo is relevant while the defect is present :).

@rbtcollins are you still experiencing this? The driver has been updated as part of #829.

I'll see about that, got a few things up in the air just now. Anything stopping doing a release?

I'm closing this one, but feel free to reopen if you are still experiencing this after 1.5.0

I'd like to re-open this as I'm seeing the same problem after 1.5.0.
Related gocql issue: https://github.com/gocql/gocql/issues/915
I see there is a setting in gocql ReconnectInterval:
	// If not zero, gocql attempt to reconnect known DOWN nodes in every ReconnectInterval.
	ReconnectInterval time.Duration

I'm not super familiar with C* yet so haven't worked out a great way to test this. I believe I've mostly seen it when resizing the cluster.
Assuming that setting works as advertised... I believe the suggestion would be to add a flag to jaeger for cassandra reconnect interval, and set the default to some reasonable value.

I believe the suggestion would be to add a flag to jaeger for cassandra reconnect interval, and set the default to some reasonable value.

Would you like to contribute a patch?

@jpkrohling Sure :100: Opened #934


LLVM IR generator definition pass error

I'm trying to compile Safe contracts for zksync, but I'm facing an error:

Error in plugin @matterlabs/hardhat-zksync-solc: The contract contracts/proxies/GnosisSafeProxyFactory.sol:GnosisSafeProxyFactory LLVM IR generator definition pass error: Contract with identifier GnosisSafeProxy_39.GnosisSafeProxy_39_deployed not found in the project

I've tried it with Solidity 0.7.6 and 0.8.15, same error in both cases
To reproduce, you can use https://github.com/safe-global/safe-contracts/tree/zksync:

Clone the repo
run yarn

I'm using macOS 12.5 with an M1 laptop. Would appreciate your help in debugging

Thanks for the feedback @mikhailxyz!
We'll take a look at it shortly.
cc @AntonD3 @hedgar2017

The problem is type(*).runtimeCode. We do not support it.
I can improve the error message though.

Is there a specified solution to this issue?
The problem seems to be arising from imports?

what should we do ? how to solve this bug ?

what should we do ? how to solve this bug ?

It is not a bug, but a feature  unsupported on our architecture.
The only way is to remove runtimeCode access from the dependency.

Any solutions guys?

Can't run any test in every directory

Could you elaborate?

Can't run any test in every directory

Could you elaborate?

https://github.com/matter-labs/hardhat-zksync/issues/1040

Can't run any test in every directory

Could you elaborate?

Since i download the foundry-zksync i can't run any test in every directory via forge test. I receive the issue above 👆  Any thoughts? I have found the guy who has the same issue and he couldn't resolve it also. He

Can't run any test in every directory

Could you elaborate?

How to get rid of it ? 😁


added a post processing script to remove 'last updated' from pages ot…

@onevcat I've added a post processing script to remove 'last updated' from pages other than index.html.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Open in external editor

Being used to (Neo)vim, I would be very pleased if I could open the current todo list or the highlighted task in an external editor. Is it possible to do this from pter?

Currently not, but sounds like an easy task. I’ll get on it.


New Case Event Buttons Added and Event Details

Motivation and Context
Need to see case event details
What has changed
The case events now show up in order of most recent first and operate as buttons. When clicked on the event details such as time/date, channel, source and payload come up
How to test?
Load a sample. Run the UI using make run-dev-ui and go to http://localhost:3000 then search for a case and open the details. Then play around with event buttons
Links
https://trello.com/c/stv0HmYA
Screenshots (if appropriate):

 Support tool- Case view - PART TWO (5)

I think the correlation ID on the event would also be useful on the details, should be easy to add? Perhaps also the processed at time and message ID, would all help avoid manual trips into the database. Also added a small comment on the column name.

From what I can see, Leo addressed these comments @AdamHawtin


[gatsby-theme-minimal-blog]: Code blocks do not use syntax highlighting, titles, etc

Firstly, thanks for making this awesome theme. I'm really enjoying it.
Description
The code blocks are not using syntax highlighting (the colours), or the titles, or anything else. They just appear as plain grey blocks
An example of the code block examples post is shown below.

Steps to reproduce

npx gatsby new gatsby-starter-minimal-blog https://github.com/LekoArts/gatsby-starter-minimal-blog
cd gatsby-starter-minimal-blog
npm run develop
Then navigate to the code block examples page: http://localhost:8001/code-block-examples

You should see the code block with only plain grey syntax highlighting.
Expected result
Colours syntax highlighting, code title blocks, etc
Actual result
No syntax highlight, no title blocks, etc
Environment
  System:
    OS: macOS 12.6
    CPU: (10) arm64 Apple M1 Pro
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
  Browsers:
    Chrome: 106.0.5249.103
    Firefox: 102.0.1
    Safari: 16.0
  npmPackages:
    gatsby: ^4.24.1 => 4.24.3
    gatsby-plugin-feed: ^4.24.0 => 4.24.0
    gatsby-plugin-image: ^2.24.0 => 2.24.0
    gatsby-plugin-manifest: ^4.24.0 => 4.24.0
    gatsby-plugin-sharp: ^4.24.0 => 4.24.0
    gatsby-plugin-sitemap: ^5.24.0 => 5.24.0
    gatsby-plugin-webpack-bundle-analyser-v2: ^1.1.27 => 1.1.27
    gatsby-source-filesystem: ^4.24.0 => 4.24.0
    gatsby-transformer-sharp: ^4.24.0 => 4.24.0
  npmGlobalPackages:
    gatsby-cli: 4.24.0

Thanks! Please remove your node_modules, the lock file and reinstall again. It should work now.

Working :) Thanks for such a quick fix.


fix(writer): use WindowEventMap for cut/copy/paste events

Fixes #139
#92 added a workaround to map cut/copy/paste events as they previously did not exist on WindowEventMap.
Now that these are mapped in the WindowEventMap interface in TypeScript lib.dom.d.ts definitions, fix this to avoid TS errors.

Fixed in v0.20.3


I keep having to renew

From time to time, about once per week, it fails to show my agenda saying I have to auth again and after I do this it works again.
I did just as in here to create my own google app id and key for this: https://github.com/insanum/gcalcli#login-information.
Could it be that there is some expiry time I am not aware of? What can be happening here?

I have the same issue

did you ever find a solution to this issue? I have the same issue also.

Per https://github.com/insanum/gcalcli/issues/611 , if we can figure out how to get gcalcli to pass a redirect_uri parameter to the Python Google OAuth2 module, it should be possible to publish the app without Google review and have longer-lasting tokens. I also filed an Ubuntu bug report at https://bugs.launchpad.net/ubuntu/+source/python-oauth2client/+bug/1983216 since it appears upstream is no longer maintaining the relevant library https://github.com/googleapis/oauth2client/issues/317

I'm assuming that's similar to how other projects like https://github.com/mbrt/gmailctl are doing the auth? I use that project too and I don't think I've ever had to reauth like that.

Likely fixed now that I merged https://github.com/insanum/gcalcli/pull/683. Please let me know if issues remain. Thanks!


More descriptive return type for primality checks

Currently the primality checking functions return bool, which may occasionally be confusing, and also does not distinguish between "definitely prime" and "probably prime" (although with the intended usage of this library, the former would be pretty rare, since we can only tell that during the trial division phase). Should we instead follow num-prime and return an enum like Primality?

Added in 0a2bed4c06fa8ce76a6eaf32ad0baa722d95b95b for hazmat functions. The ones in presets will continue to return bool because the idea of presets is that it contains a vetted sequence of checks that is supposed to be trusted.


Intermediate rule evaluation results

Proposal
I commonly find teams having to do multiple recording rules in order to arrive at the final result they need, for example due to needing to do range queries on the result in the next step. Contrieved example:
groups:
- name: example
  rules:
  - record: step1
    expr: histogram_quantile(0.9, sum by (le) (rate(duration_seconds_bucket[5m])))
  - record: step2
    expr: max(step1)
  - record: step3
    expr: step2 > bool 5
  - record: step4
    expr: avg_over_time(step3[7d])

In this case, we don't really care about saving steps 1-2 (step 3 would need to be kept since we do a range on it). This both leads to unnecessary storage and "worthless" metrics floating around.
Could we add a new directive, maybe discard: true, to instruct Prometheus not to persist the result but instead drop it after the group has finished?

That's not how Prometheus storage works internally, once it's added it's added from a performance standpoint.

Ah, ok. So then it would merely be the cluttering aspect then (typically they are now named things like "temp_result_xyz").
But should I interpret this as it not being even possible?

I'm not saying it's not possible, but there's not much point.

We are currently running a bug scrub with the team.
You could actually write this whole thing as one expression thanks to sub-queries.
If you still want to write it as separate expressions for better readability, that boils down to templating or macro expansion or whatever you want to call it, which is something we currently deliberately want to avoid inside Prometheus.
So we decided to close this as "won't fix".


Unhandled Exception: LateInitializationError: Field 'requestPort' has not been initialized.

Describe the bug
When you start the call after ending one call that call is not starting, even the local video view is not starting
To Reproduce
Steps to reproduce the behavior:

Start one call wait for both person to come live
End that call
Start Another call
See error

Expected behavior
When i start another call i should be able to start it normally just like the previous one
Smartphone (please complete the following information):

Device: Redmi note 8 Pro, Pixel 6
OS: Android
Version Android 11 and 13

Additional context
#0      _ApiCallExecutor.requestPort (package:agora_rtc_engine/src/impl/api_caller.dart)
#1      _ApiCallExecutor.callIrisApiWithUin8ListAsync (package:agora_rtc_engine/src/impl/api_caller.dart:280:5)
#2      ApiCaller.callIrisApiWithUin8ListAsync (package:agora_rtc_engine/src/impl/api_caller.dart:99:10)
#3      ApiCaller.callIrisApi (package:agora_rtc_engine/src/impl/api_caller.dart:107:12)
#4      RtcEngineImpl.leaveChannel (package:agora_rtc_engine/src/impl/agora_rtc_engine_impl.dart:759:25)
#5      ChatVideoCallModel.dispose (package:agreed/feature/chat/video_call/video_call_model.dart:152:18)
#6      _runGuarded (package:riverpod/src/framework/container.dart:5:7)
#7      Iterable.forEach (dart:core/iterable.dart:325:35)
#8      ProviderElementBase._runOnDispose (package:riverpod/src/framework/provider_base.dart:909:26)
#9      ProviderElementBase.dispose (package:riverpod/src/framework/provider_base.dart:860:5)
#10     ProviderContainer._disposeProvider (package:riverpod/src/framework/container.dart:354:13)
#11     _ProviderScheduler._performDispose (package:riverpod/src/framework/scheduler.dart:81:26)
#12     _ProviderScheduler._task (package:riverpod/src/framework/scheduler.dart:42:5)
#13     _UncontrolledProviderScopeElement.build (package:flutter_riverpod/src/framework.dart:303:12)
#14     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4878:15)
#15     Element.rebuild (package:flutter/src/widgets/framework.dart:4604:5)
#16     BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2667:19)
#17     WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:882:21)
#18     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1175:15)
#19     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1104:9)

E/flutter ( 3742): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: IsolateSpawnException: Unable to spawn isolate: Could not prepare the child

E/flutter ( 3742): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: LateInitializationError: Field 'requestPort' has not been initialized.
#0      _ApiCallExecutor.requestPort (package:agora_rtc_engine/src/impl/api_caller.dart)
#1      _ApiCallExecutor.callIrisApiWithUin8ListAsync (package:agora_rtc_engine/src/impl/api_caller.dart:280:5)
#2      ApiCaller.callIrisApiWithUin8ListAsync (package:agora_rtc_engine/src/impl/api_caller.dart:99:10)
#3      ApiCaller.callIrisApi (package:agora_rtc_engine/src/impl/api_caller.dart:107:12)
#4      RtcEngineImpl.leaveChannel (package:agora_rtc_engine/src/impl/agora_rtc_engine_impl.dart:759:25)
#5      ChatVideoCallModel.dispose (package:agreed/feature/chat/video_call/video_call_model.dart:152:18)
#6      _runGuarded (package:riverpod/src/framework/container.dart:5:7)
#7      Iterable.forEach (dart:core/iterable.dart:325:35)
#8      ProviderElementBase._runOnDispose (package:riverpod/src/framework/provider_base.dart:909:26)
#9      ProviderElementBase.dispose (package:riverpod/src/framework/provider_base.dart:860:5)
#10     ProviderContainer._disposeProvider (package:riverpod/src/framework/container.dart:354:13)
#11     _ProviderScheduler._performDispose (package:riverpod/src/framework/scheduler.dart:81:26)
#12     _ProviderScheduler._task (package:riverpod/src/framework/scheduler.dart:42:5)
#13     _UncontrolledProviderScopeElement.build (package:flutter_riverpod/src/framework.dart:303:12)
#14     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4878:15)
#15     Element.rebuild (package:flutter/src/widgets/framework.dart:4604:5)
#16     BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2667:19)
#17     WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:882:21)
#18     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1175:15)
#19     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1104:9)```

Can you share API call logs? There should be something like the below log to the console.
[2023-02-06 15:07:57.542] [84585] [debug] [iris_rtc_engine_impl.cc:112] api name RtcEngine_initialize params {"context":{"appId":"******"}}
[2023-02-06 15:07:57.621] [84585] [debug] [iris_rtc_device_manager_impl.cc:29] IrisRtcDeviceManagerImpl Initialize

@bhavykoshti
Hey did you solve it?
I am also getting the same error.

@littleGnAl hello,
I am also getting the same error on the same steps. I am pasting my logs below.
[VERBOSE-2:dart_vm_initializer.cc(41)] Unhandled Exception: LateInitializationError: Field 'requestPort' has not been initialized.
#0      _ApiCallExecutor.requestPort (package:agora_rtc_engine/src/impl/api_caller.dart)
api_caller.dart:1
#1      _ApiCallExecutor.callIrisApiWithUin8ListAsync
api_caller.dart:273
#2      ApiCaller.callIrisApiWithUin8ListAsync
api_caller.dart:110
#3      ApiCaller.callIrisApi
api_caller.dart:118
#4      RtcEngineImpl.setupRemoteVideo
agora_rtc_engine_impl.dart:687
#5      VideoViewControllerBaseMixin.disposeRender
video_view_controller_impl.dart:72
#6      _AgoraRtcRenderPlatformViewState._disposeRender
agora_video_view_impl.dart:115
#7      _AgoraRtcRenderPlatformViewState.dispose

did you resolve it
?

Please check this comment
https://github.com/AgoraIO-Extensions/Agora-Flutter-SDK/issues/860#issuecomment-1370420470

This occurs when your initialization is not properly done, Will check in few days if it occurs again, if not then will close this issue

Resolved from my side

What changes have you made? @adiShinwari

I am creating a single instance of agora rtc at the start of the app using getit package. And I am using it.

I'm addressing a fix here, but I still need more tests before it can be merged.
https://github.com/AgoraIO-Extensions/Agora-Flutter-SDK/pull/905

I am getting the same error? Video or audio call is not connecting, throwing this error.

This fix https://github.com/AgoraIO-Extensions/Agora-Flutter-SDK/pull/905 has landed main branch

Am getting the same error here is my implementation
_engine = createAgoraRtcEngine();
await _engine.initialize(RtcEngineContext(
appId: APP_ID,
));
await _engine.enableVideo();
_engine.registerEventHandler(
  RtcEngineEventHandler(
    onJoinChannelSuccess: (RtcConnection connection, int elapsed) async {
      dev.log("Joined live uid => ${connection.localUid}");

      await Wakelock.enable();
    },
    onUserJoined: (RtcConnection connection, int uid, int elapsed) {
      dev.log("Joined live");
      setState(
        () {
          _users.add(LiveUser(id: uid, videoMuted: false, audioMuted: false));
        },
      );
    },
    onUserMuteVideo: (connection, id, mute) {
      setState(() {
        _users[_users.indexWhere((element) => element.id == id)].videoMuted = mute;
      });
    },
    onUserMuteAudio: (connection, uid, mute) {
      setState(() {
        _users[_users.indexWhere((element) => element.id == uid)].audioMuted = mute;
      });
    },
    onUserOffline: (connection, uid, reasonType) {
      // if (uid == guestID) {
      //   setState(() {
      //     accepted = false;
      //   });
      // }
      setState(() {
        _users.removeWhere((element) => element.id == uid);
      });
    },
    onError: (typr, e) {
      dev.log(e.toString());
    },
    onLeaveChannel: (connection, stats) {
      setState(
        () {
          _users.clear();
        },
      );
    },
  ),
);

final viewModel = context.read<LiveViewModel>();
final parsedInviteId = viewModel.parseInviteId(
  widget.inviteId,
);

ChannelMediaOptions options = ChannelMediaOptions(
  clientRoleType: ClientRoleType.clientRoleBroadcaster,
  channelProfile: ChannelProfileType.channelProfileLiveBroadcasting,
);

await _engine.joinChannel(
  token: parsedInviteId['token'],
  channelId: parsedInviteId['channelName'],
  uid: context.read<UserViewModel>().user_id,
  options: options,
);

  agora_rtc_engine:
    git:
      url: https://github.com/AgoraIO-Extensions/Agora-Flutter-SDK.git
      ref: main

instead your library in yaml

@bhavykoshti
am not getting any camera preview from when i initialize the engine, i have enabled video and also start preview when video view is created. and also when i release the engine the spawned isolate still remains


Implementing Benefactor Entity

Hello,
Please explain a little in order to be more clear for QA to test.
Is it in the Admin panel or the site?

@Polina1985 Benefactor is the person that donates
You might find more info at https://docs.podkrepi.bg/general/architecture/glossary#daritel


Firebase folder is not being created in dist/vendor

As far as I can tell I have followed the steps in the developer guide and I have an angularfire2 folder in vendor now but no firebase folder. I used the cli to make the project and used the steps in dev guide part one with no success.
As an aside the /vendor/angular2 is giving 404 errors even though it does exist. I can post any files on request but I am not sure where to start. Thanks for any and all help!

Something similar happened to me once, but it was because I had ran ng serve before ng build after modifying system-config.ts, so the folders weren't created.  Anyway, I'd suggest you to post here the important parts of your system-config.ts file (const map and const packages) and the code inside angular-cli-build.js.

Ty. Will do

(100th) ng build did it.. I must have messed something up.. then fixed it recently... THANK YOU!


[Akka Streams] Allow creation of sources without message acknowledgement

Hi everyone,
I hope you are all well.
Currently when we create a source the messages are automatically acknowledged
There is use cases when we would like to decouple message receipt and acknowledgement.
For example when we do event sourcing we would like to keep the last received message unacknowledged until a new message is received to do things like this :
val pulsarSource = source(consumerFn, Some(MessageId.latest))
val acknowledgeSink = Sink.foreach[MessageId](id => consumerFn().acknowledge(id))
pulsarSource.runWith(acknowledgeSink)

This could allow to always keep the last state of the application as the first unacknowledged message and handle crashes by simply re-reading the topic without having to search the acknowledged messages (maybe using topic compaction) and treating the states as data in the streams
I'm not sure how much work this would take or if it's a good idea. It's more of a suggestion.

Instead of source, use committableSource ;)

Instead of source, use committableSource ;)

That's right. That gives you CommittableMessage instead of ConsumerMessage. For each message, you can call the ack or nack method.


add token rate in verbose mode

#293
add token rate in verbose mode

@canzden it ends up eval_count and eval_duration give us what we need here, since you can calculate the generated tokens/s with it. Sorry for creating #293 – I had overlooked this! Feel free to re-open this PR if you feel like we should add some other metrics, though!


Make active targets the default URI

Make /upstreams/:upstream_name_or_id/targets/active/ become the default one.(/upstreams/:upstream_name_or_id/targets/)
Introduce /upstreams/:upstream_name_or_id/targets/all to show all the targets.

@thefosk what do you mean by target here?

@thefosk @thibaultcha
Just wanted to make sure if the following sounds correct:

The current default route /upstreams/:upstream_name_or_id/targets/  should instead be /upstreams/:upstream_name_or_id/targets/all.
The /upstreams/:upstream_name_or_id/targets/active/ remains as is.

Making the current default route as active seems incorrect to me.

@hbagdi What the @thefosk means here, is that when a user queries /upstreams/:upstream_name_or_id/targets/, we think the user should see the currently active Targets or a given Upstream (the physical hosts currently on the balancing wheel). Only when a user queries /upstreams/:upstream_name_or_id/targets/all, should they see the entire list of Targets (old and current). The /.../active one would disappear.
Today, a request to /upstreams/:upstream_name_or_id/targets/ returns all Targets, even previous ones. As you may know, Targets are immutable. They can only be created, but not modified nor deleted. To update/remove a Target, one must make create a new one with a different weight (0 for disabling it). We think this is confusing, and we wish to hide this underlying implementation details to the user, so that they interact with this endpoint in a more RESTful fashion.

@thibaultcha thanks for the lucid explanation!
I'll take this up and send you a PR soon.

Done with #3049