Sporadic ECONNRESET that breaks connection in nearlib

When using nearlib in a long running node.js app the connection is sometimes getting randomly dropped and the entire app crashes with ECONNRESET error. This is a blocker for the bridge since bridge relayers are long running node.js services that should not crash.
This error is not easy to reproduce since it is random and does not seem to depend on the code that uses nearlib.

During load testing, @ailisp discovered that there is a hard limit on Node.js that does not allow more than 200 parallel connections to a single host (if I recall it correctly). Thus, it was not a bug of near-api-js. Are you sure that you don't hit this same limit?

I have only one or maybe two connections open to a single host, unless nearlib opens them for me.

Your described ECONNRESET is probably due to occasional network disconnect/packet loss. It is possible to catch/retry to recover from ECONNRESET error, e.g. i was able to run near-ops/loadtest.js with a lot of ECONNRESET for a week but not crash

Well, even if we would not encounter those errors, you should handle such errors and retry. Unless this happens like tens of times reproducibly, there is nothing wrong with it. Otherwise, we need to debug the network, there is nothing on near-api-js side, it is a simple wrapper around fetch API.
@nearmax I am going to close it. Feel free to reopen it if you feel that there is still an action item here.

@ailisp This happens consistently with the local node, like a dozen times a day, as I am working with the local node using near-api-js.
@frol It sounds like it is within the scope of near-api-js responsibility to do those retries. The action item would be to implement such functionality. Reopening this issue. (Thank you for closing though! I think we should not hesitate to close the issues)

On local test to a local node I had encounter ECONNRESET too. It seem to happen due to neard has some error. I agree with @nearmax this should be handled in nearlib, ideally it should not expose any low level error like this, but nearlib defined error classes.

Assigning it to @frol since it is relevant to RPC and it creates problems for the bridge which are both in the Middleware scope.

@nearmax @frol is it still relevant? Is it still a problem for the bridge?

I haven't heard about it since then. I believe it was a load-balancer configuration issue or something with infrastructure which we never identified.

Ok, then I will close it. @nearmax feel free to open it if we will face this issue again.


Eliminate Opinionated Context Parameters

Update terraform-null-label to generalize context/label parameters, with backward compatibility
Update atmos to eliminate dependency on namespace, name, stage, environment, tenant, etc context parameters

This is already supported today with name_template (not to be confused with name_pattern)

#560

https://atmos.tools/cli/configuration/stacks/


Compiler won't work outside of src repo

I am trying to use the capnpc-ts compiler but it only works if I run it from inside a checkout of https://github.com/jdiaz5513/capnp-ts.
For example:
$ pwd
/Users/madhavajay/dev/capnp-ts
$ capnpc -o ./node_modules/capnpc-ts/bin/capnpc-ts.js address.capnp
$ ls | grep address
address.capnp
address.capnp.d.ts
address.capnp.js

However if I use either:
$ npm install -g capnpc-ts
$ pwd
/Users/madhavajay/dev/my_project
$ capnpc -o ts address.capnp

or the same with:
$ capnpc -o ts./node_modules/capnpc-ts/bin/capnpc-ts.js address.capnp

Error:
DeprecationWarning: 'createTypeReferenceNode' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createIdentifier' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createToken' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createThis' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createNamespaceImport' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createImportClause' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createLiteral' has been deprecated since v4.0.0. Use `factory.createStringLiteral`, `factory.createStringLiteralFromNode`, `factory.createNumericLiteral`, `factory.createBigIntLiteral`, `factory.createTrue`, `factory.createFalse`, or the factory supplied by your transformation context instead.
DeprecationWarning: 'createImportDeclaration' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createExpressionStatement' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createVariableDeclaration' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createVariableDeclarationList' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createVariableStatement' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createPropertyAssignment' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createNumericLiteral' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createNewExpression' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createObjectLiteralExpression' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createPropertyDeclaration' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: '' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createCallExpression' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createReturnStatement' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createBlock' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createMethodDeclaration' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createParameterDeclaration' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createBinaryExpression' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createExpressionWithTypeArguments' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createHeritageClause' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
DeprecationWarning: 'createClassDeclaration' has been deprecated since v4.0.0. Use the appropriate method on 'ts.factory' or the 'factory' supplied by your transformation context instead.
TypeError: Cannot create property 'pos' on string 'Foo'
    at setTextRangePos (/Users/madhavajay/my_proj/node_modules/typescript/lib/typescript.js:21342:19)
    at Object.setTextRangePosEnd (/Users/madhavajay/my_proj/node_modules/typescript/lib/typescript.js:21360:32)
    at createNodeArray (/Users/madhavajay/my_proj/node_modules/typescript/lib/typescript.js:22985:16)
    at asNodeArray (/Users/madhavajay/my_proj/node_modules/typescript/lib/typescript.js:27581:28)
    at createBaseGenericNamedDeclaration (/Users/madhavajay/my_proj/node_modules/typescript/lib/typescript.js:23037:35)
    at createBaseInterfaceOrClassLikeDeclaration (/Users/madhavajay/my_proj/node_modules/typescript/lib/typescript.js:23072:24)
    at createBaseClassLikeDeclaration (/Users/madhavajay/my_proj/node_modules/typescript/lib/typescript.js:23078:24)
    at Object.createClassDeclaration (/Users/madhavajay/my_proj/node_modules/typescript/lib/typescript.js:25474:24)
    at Object.createClassDeclaration (/Users/madhavajay/my_proj/node_modules/typescript/lib/typescript.js:3138:29)
    at generateStructNode (/Users/madhavajay/my_proj/node_modules/capnpc-ts/src/generators.js:488:36)
./node_modules/capnpc-ts/bin/capnpc-ts.js: plugin failed: exit code 1

I have tried copying a few of the tsconfig files over but I think im missing something more obvious.
package.json
{
  "name": "js",
  "version": "1.0.0",
  "description": "",
  "main": "testing.js",
  "dependencies": {
    "capnp-ts": "^0.7.0",
    "capnpc-ts": "^0.7.0",
    "fetch": "^1.1.0",
    "goog": "^0.2.1",
    "node-fetch": "^3.1.0",
    "system-sleep": "^1.3.7"
  },
  "devDependencies": {
    "ts-node": "^9.1.1",
    "typescript": "^4.2.4"
  },
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "type": "module",
  "author": "",
  "license": "ISC"
}

I'm getting same error TypeError: Cannot create property 'pos' on string 'Query' with the latest version 0.7.0. Haven't tested with local build, master is ahead by 3 commits so i wonder if there is a fix there, that's why it's working for @madhavajay


Changes to config trigger rebuild, but are not reflected

I tried all three allowed config filenames, and it seems with .ejsrc I got a change reflected in the rebuild once... But was unable to replicate it. I'm on Windows if that matters (Parcel is really buggy here it seems).

I think i encountered the same issue running version 0.2.0 of parcel-transformer-ejs with parcel 2.4.1 on Linux. Changes to the config file trigger a build but it seems like the cached version of the config file is not invalidated. I added some console.log statements and dumped the contents from "config.getConfig(...)" to the console and it seems like it's the same on every build although the file has changed on disk for sure.

Thanks @hyvyys and @sailerinteractive for opening an issue. I will take a look at this and try fix it over the weekend. However, you can submit a PR if you are able to fix the issue before then.

I also have this problem.Has it been fixed?

Hi @songxingguo, does this problem occur in version 0.2.1 or 1.0.1. I suggest using any one of these two as they are more stable

I use version 1.0.1, but three are still problems.


Make a note that caide has a command line app

Build failure is unrelated to my changes.

LGTM. Thanks for the PR :)


[Bug] variable interpolation not working

Steps To Reproduce

Install plugin and setup .babelrc.json
Interpolate a const variable into the styled-jsx SCSS codeblock
Observe the style not being applied

Minimal example
https://stackblitz.com/edit/nextjs-1uw1yf?file=pages/index.js

Hey! :wave:
Thanks for your report! @SwiftWinds
I guess that's more a styled-jsx than an issue with this plugin, as, without this plugin, it still doesn't work, maybe worth opening an issue on vercel/styled-jsx repo.

Hmm... OK. I'm looking at index.js and struggling to understand what's going on. I'll perhaps get some sleep and come back tomorrow to take a fresh look. In the meantime, got any suitable workarounds?

How am I supposed to turn a plain JavaScript variable into a SASS variable though? I need to use the constant in places besides SASS.

in 4.0.2 same problem with interpolation still exists when generating className using css.resolve and trying to use ${someVar} for root element styles, so in regular SASS terms it would be
const { className, styles } = css.resolve`
  & {
    color: ${primatyColor};
  }
`;

but it throws with error Error: Top-level selectors may not contain the parent selector "&"
and stack trace:
Uncaught     at Object.wrapException (file:///project/node_modules/sass/sass.dart.js:6290:17)
    at SelectorList0.resolveParentSelectors$2$implicitParent (file:///project/node_modules/sass/sass.dart.js:83252:17)
    at _EvaluateVisitor_visitStyleRule_closure17.call$0 (file:///project/node_modules/sass/sass.dart.js:79693:17)
    at _EvaluateVisitor1._evaluate0$_addExceptionSpan$1$2 (file:///project/node_modules/sass/sass.dart.js:78710:23)
    at _EvaluateVisitor1._evaluate0$_addExceptionSpan$2 (file:///project/node_modules/sass/sass.dart.js:78731:19)
    at _EvaluateVisitor1.visitStyleRule$1 (file:///project/node_modules/sass/sass.dart.js:77828:33)
    at StyleRule0.accept$1$1 (file:///project/node_modules/sass/sass.dart.js:89894:22)
    at StyleRule0.accept$1 (file:///project/node_modules/sass/sass.dart.js:89897:19)
    at _EvaluateVisitor1.visitStylesheet$1 (file:///project/node_modules/sass/sass.dart.js:77311:16)
    at _EvaluateVisitor__execute_closure1.call$0 (file:///project/node_modules/sass/sass.dart.js:79085:10)
    at _EvaluateVisitor1._evaluate0$_withEnvironment$1$2 (file:///project/node_modules/sass/sass.dart.js:78517:25)
    at _EvaluateVisitor1._evaluate0$_withEnvironment$2 (file:///project/node_modules/sass/sass.dart.js:78522:19)
    at _EvaluateVisitor1._evaluate0$_execute$5$configuration$namesInErrors$nodeWithSpan (file:///project/node_modules/sass/sass.dart.js:77202:13)
    at _EvaluateVisitor1._evaluate0$_execute$2 (file:///project/node_modules/sass/sass.dart.js:77212:19)
    at _EvaluateVisitor_run_closure1.call$0 (file:///project/node_modules/sass/sass.dart.js:78977:67)
    at Object._rootRun (file:///project/node_modules/sass/sass.dart.js:12412:16)
    at processResult (file:///project/node_modules/next/dist/compiled/webpack/bundle5.js:62187:19)
    at <unknown> (file:///project/node_modules/next/dist/compiled/webpack/bundle5.js:62289:5)
    at <unknown> (file:///project/node_modules/next/dist/compiled/webpack/bundle5.js:27510:11)
    at <unknown> (file:///project/node_modules/next/dist/compiled/webpack/bundle5.js:27362:18)
    at context.callback (file:///project/node_modules/next/dist/compiled/webpack/bundle5.js:27235:13)
    at <unknown> (file:///project/node_modules/next/dist/build/webpack/loaders/babel-loader/src/index.js:4:106)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at runNextTicks (internal/process/task_queues.js:64:3)
    at processImmediate (internal/timers.js:437:9)

so the only workaround I found for this case is to use some root-level selector like div which results to div.jsx-3079332898 selector in CSS

Hmm... I'm sorry this isn't terribly useful, @belkosyak, but you could always look into fixing it yourself and pull-requesting. I'm sorry, but I'm not the owner of this repo nor a very active contributor, so I'm not sure if I can dedicate any time to write a solution to the problem you mentioned. Sorry about that


Update Wacom tablet drivers

Thank you for the contribution. It was merged directly as 5a03d44e968178f3d63756eecb4eb509ffee8c37 to keep commit history cleaner. Your contribution is still credited to you.


Fix tests in travis using docker

Coverage increased (+1.01%) to 81.081% when pulling 6f0e5bb564698fffe5fcf7c7590a4663a337ceef on dantswain:fix_travis2 into 055f311fbc9e47e647b9d00a9fd91bbc5eaf95e2 on pinterest:pure_elixir_implementation.

Coverage increased (+1.01%) to 81.081% when pulling 6f0e5bb564698fffe5fcf7c7590a4663a337ceef on dantswain:fix_travis2 into 055f311fbc9e47e647b9d00a9fd91bbc5eaf95e2 on pinterest:pure_elixir_implementation.


Can't compile in MSVC 2019 with /std:c++latest

vcpkg\installed\x64-windows\include\g3log/future.hpp(45): error C2039: 'result_of': is not a member of 'std'
Looks like result_of was removed in C++20:
https://en.cppreference.com/w/cpp/types/result_of

G3log supports C++14, C++17 but not yet C++20

We have been using g3log for several years and we would like to do so for many to come. But some are having uneasy feelings this important component is currently preventing c++20 compatibility tests. I have also have looked at this issue, and whether it could be resolved in a day or so. Sadly, the answer is likely not, because of the impact it may have on concurrency and IO. I guess anybody needs to have such changes tested thoroughly.
Question: @KjellKod can you say anything about c++20 support somewhere. I know that building os software can be pain in the $ss, thus, the answers: "not in 2020" and "please do it yourself" are understandable.
regards HJ

At this point, g3log does not support c++20.  Moving from C++14/17 to C++20
is a breaking change (unless I want to keep a bunch of ifdefs in the code)
The changes are fairly trivial and involve like you called out some
concurrency changes in regard to packed tasks and futures. The changes are
well specified and contained.
At this point, I have not planned to take on this work in 2020 but nothing
is really stopping me or the community to take it on.
Since a while back I mostly rely on the community to drive the changes in
g3log. I am happy to provide guidance, support and review PRs that would
address the move to C++20.
For company critical support - such as upgrading g3log to support C++20
within a given timeframe - driven by me, not by the community - I would ask
that to be handled on a contract basis. You can reach me on my private
email (ref my github page) if that is of interest.
On Wed, Sep 9, 2020 at 7:27 AM Henk-Jan Lebbink<EMAIL_ADDRESS>wrote:

We have been using g3log for several years and we would like to do so for
many to come. But some are having uneasy feelings this important component
is currently preventing c++20 compatibility tests. I have also have looked
at this issue, and whether it could be resolved in a day or so. Sadly, the
answer is likely not, because of the impact it may have on concurrency and
IO. I guess anybody needs to have such changes tested thoroughly.
Question: @KjellKod https://github.com/KjellKod can you say anything
about c++20 support somewhere. I know that building os software can be pain
in the $ss, thus, the answers: "not in 2020" and "please do it yourself"
are understandable.
regards HJ
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/KjellKod/g3log/issues/351#issuecomment-689562735, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACQ7XXZIW3OOVIBR2XSPVLSE57EDANCNFSM4NIROKMQ
.


Remove ASP.NET Core references

ASP.NET will be rebranded to ASP.NET Core... but the current release is
still ASP.NET 5 (so reverting the title/text changes).
Resolves #131

cc @danroth27

:shipit:

:shipit:


How to downgrade to older version

Hello I have a question. How to downgrade to an older version of ETS2
I want to play TruckersMP but it is not compatible with the newest update.
Regards,
SquadraMunter

In Steam Library, right click on ETS2, properties, choose BETA tab. Select the latest version from the list.
https://i.imgur.com/VL4OJVg.png
When selected what version you want it will start to download the downgraded version.

Append -beta <name_of_beta> after the steamid:
https://github.com/lhark/truckersmp-cli/blob/8e95826bacab03044073fdba6c30fb4ebef97d36/truckersmp-cli#L338
- +app_update "$steamid" validate \
+ +app_update "$steamid" -beta <name_of_beta> validate \

--beta VERSION option (e.g. --beta temporary_1_36) has been implemented in 8aa88ca.


"cannot find module 'Browser'

The error says elm-make failed. This suggests a need to change elm-live to the 0.19 syntax of elm make without the hyphen. The project builds fine with elm make.

If you are getting and error that says elm-make then you have an older version of elm-live installed. Try removing it completely from your project as well as globally then re-installing it.

I only have elm-live installed globally and npm ls --global | grep elm gives me<EMAIL_ADDRESS>which should be the latest version I think.

Yeah someone else had that issue with their global install and they had to delete the package manually and re-install.


ca-certificate generation in ubuntu

hi there! we're using this AMI and noticed that cluster autoscaler stopped working as it doesn't generate the certificates on startup. furthermore, the certificates are located at a different endpoint.

You can also solve this problem by changing the example deployment of cluster-autoscaler to use a hostPath volume with path: /etc/ssl/certs/ca-certificates.crt instead of path: /etc/ssl/certs/ca-bundle.crt. That seems like the preferable solution to messing with the distro's cert management.


add LICENSE file

Added missing LICENSE file.

The failing test isn't related to this commit. The request is just for the LICENSE file. The reason I created and pushed this file, is because there is a link to it on README, which is currently broken.
https://travis-ci.org/Vuedo/vuedo/requests
Could anybody take a look at this? Maybe restart the build Travis.

Hey @crabbly,
Yeah, I know. Sometimes, lorempixel's issues make the tests fail.
Thanks for the contribution.


Fix for #2: Adding support for excluding  tags

This adds support for excluding css files, which was missing from the original plugin.

@Yona-Appletree That's a good idea. The whole point of this plugin is to allow us to control what can be included in the output. And the  tag was the missing piece.

Thanks for merging this, I needed to exclude all my theme css files so that I could conditionally include them at runtime. Looks like you already added a mention for that exact use case to the README 👍


Update font awesome and url

Update a very old url
update to a font-awesome 5, should be backwards compatible, ruby gem (license MIT https://github.com/tomkr4l/font_awesome5_rails/blob/master/LICENSE)

No idea why this introduces breakage (involving the manifest.js)
Maybe some alternate sass getting pulled in by this somehow...

That did it!

Unfortunately, many icons fail & we have a problem in production. I'll have to temporarily revert to get things back to a safer state for now :-(. Hopefully we can reinstate this soon, it looks like the right thing to do but there are some surprises.


POLIO-1595: remove the delete button from vaccine stocks

Explain what problem this PR is resolving

remove the delete button from vaccine stocks list
Related JIRA tickets : POLIO-1595

Self proofreading checklist

[x] Did I use eslint and black formatters
[ ] Is my code clear enough and well documented
[ ] Are my typescript files well typed
[ ] New translations have been added or updated if new strings have been introduced in the frontend
[ ] My migrations file are included
[ ] Are there enough tests
[ ] Documentation has been included (for new feature)

Changes

remove the delete button from vaccine stocks list

How to test

Go in Polio -> Vaccine Module -> Stock management
Check if the delete button on each stock is not there anymore

Print screen / video

Please delete useDeleteStock hook as well if it's not used anymore

@quang-le Change request fixed


Remote server error while deploying az function

Does this occur consistently?
Repro steps:

Action: azureFunctions.deploy
Error type: BadRequest
Error Message: There was a conflict. The remote server returned an error: (403) Forbidden.
Version: 1.0.1
OS: win32
OS Release: 10.0.18363
Product: Visual Studio Code
Product Version: 1.51.1
Language: en

Call Stack
new RestError extension.bundle.js:46:109835
extension.bundle.js:48:167633extension.bundle.js:48:167633
processTicksAndRejections task_queues.js:94:5

Please add repro steps


feat: add scroll to top button for all pages.

Here's a preview of how it looks

https://github.com/Saurav-Pant/Blood-Donation-Project/assets/104001201/f0aa7e4a-63cb-4c90-acfc-af940c520c9c
Tasks

[x] Add scroll to top button.

Issue #88 completed✔

Thank you @Saurav-Pant


unable to install service catalog using helm 3

helm install catalog svc-cat/catalog --namespace catalog --version 0.3.1 command gives the following error
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1", unable to recognize "": no matches for kind "ClusterRole" in version "rbac.authorization.k8s.io/v1beta1", unable to recognize "": no matches for kind "ClusterRoleBinding" in version "rbac.authorization.k8s.io/v1beta1", unable to recognize "": no matches for kind "MutatingWebhookConfiguration" in version "admissionregistration.k8s.io/v1beta1", unable to recognize "": no matches for kind "ValidatingWebhookConfiguration" in version "admissionregistration.k8s.io/v1beta1"]
Would be nice if you'll could help us fix this issue.

Wich k8s version do you use (we install it successfully on k3s 1.20)

It appears the chart refers to deprecated artifacts as of 1.22.  Example:
“The apiextensions.k8s.io/v1beta1 API version of CustomResourceDefinition is no longer served as of v1.22.”

any updates on this issue? We are facing the same error when installing service catalog v0.3.1 to K3S v1.23.3+k3s1.

This project is being archived, closing open issues and PRs.
Please see this PR for more information: https://github.com/kubernetes/community/pull/6632


[Windows] Update Install Edge logic

Description
This PR updates Install Edge logic to use the same version for Edge Driver which Edge browser already has.
Related issue:
https://github.com/actions/virtual-environments-internal/issues/3395
Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[x] Changes are tested and related VM images are successfully generated

18 Şubat 2022 Cuma tarihinde Nikolay Frolov @.***>
yazdı:

Description
This PR updates Install Edge logic to use the same version for Edge Driver
which Edge browser already has.
Related issue:
actions/virtual-environments-internal#3395
https://github.com/actions/virtual-environments-internal/issues/3395
Check list

Zzzz Related issue / work item is attached
Tests are written (if applicable)
Documentation is updated (if applicable)
Changes are tested and related VM images are successfully generated

You can view, comment on, or merge this pull request online at:
https://github.com/actions/virtual-environments/pull/5106
Commit Summary

e2f0452
https://github.com/actions/virtual-environments/pull/5106/commits/e2f0452431f7595410c1f7a0371d0459522558fc
[Windows] Update Intstall Edge logic

File Changes
(1 file https://github.com/actions/virtual-environments/pull/5106/files)

M images/win/scripts/Installers/Install-Edge.ps1
https://github.com/actions/virtual-environments/pull/5106/files#diff-53d0eff6e9c011e5c0a15e354cf4d2876dd2eb7bb973ab97ee0419918e2c2abd
(11)

Patch Links:

https://github.com/actions/virtual-environments/pull/5106.patch
https://github.com/actions/virtual-environments/pull/5106.diff

—
Reply to this email directly, view it on GitHub
https://github.com/actions/virtual-environments/pull/5106, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AXZMN6YAO43GXKOIHVQGP5DU32EAFANCNFSM5OYV35PA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Fuel game does not watch ads every 30 mins

Hi @thebrumby,
The Fuel game serves ads every 30 mins. However the fuel bot seems like watching it only once during the full claim, and then it sleeps for 12 hours. I would like the bot to watch ads as soon as they appear, as it increases the mining speed. I'm wondering if I can just update the config or need to modify the code? (I was going through the code, but didn't understand it yet)
Here is the log file showing it:

Step 110 - watch an advert done
After that more than 1 hour passed, no attemp to watch it

Keep in mind, sometimes the advert button ("Increase multiplier by..") is available but there are no ads to show and this windows appears:

Hi @bulat-gab ,
It looks like we could benefit from moving some of the code about in the def full_claim(). I'm not at home for testing right now, but I would remove  this:
                xpath = "//a[text()='Upgrades']"
                move_and_click(xpath, 10, True, "click the 'Upgrades' button", step, "clickable")
                xpath = "//button[contains(., 'Increase multiplier by')]"
                advert = move_and_click(xpath, 10, True, "watch an advert", step, "clickable")
                if advert:
                    output(f"Step {step} - Waiting 60 seconds for the advert to play.",3)
                    time.sleep(60)
                    increase_step()
                    get_balance(True)

And paste it in to here before it returns the remaining time. I just changed the output text to reflect the 30-minute advert check and forced remaining_wait_time = 30 :
    if wait_time_text != "Filled":
        try:
            time_parts = wait_time_text.split()
            hours = int(time_parts[0].strip('h'))
            minutes = int(time_parts[1].strip('m'))
            remaining_wait_time = (hours * 60 + minutes)
            if remaining_wait_time < 5 or settings["forceClaim"]:
                settings['forceClaim'] = True
                output(f"Step {step} - the remaining time to claim is less than the random offset, so applying: settings['forceClaim'] = True", 3)
            else:
                remaining_wait_time = 30
                output(f"STATUS: Pot not ready for claiming - let's come back in 30 minutes to check for adverts.", 1)
                return remaining_wait_time
        except ValueError:
            # Handle the case where wait_time_text can't be parsed
            pass

If we do it this way around, it will let us check for the "recycle" after the main claim, which I wonder if it should say "refine" if it's converting oil into petrol :)
Cheers

I have pushed the update
auto refine + advert

Great stuff, thank yo @Wellynounet!


UI - Contributor Console - Module Cleanup

Summary
UI - Contributor Console - Module Cleanup.
Background

[x] Remove unused modules in the Contributor Console.  Ensure modules are not used or referenced.  Remove HTML, CSS, Module Definition and Typescript logic.
[x] Remove any unused functions in the cla.services.ts (if any remain)
[x] Confirm UI still builds and works as expected.

User Story
As a developer, I want to reduce the UI clutter and not have extra unused files/modules in the source code repository.
Acceptance Criteria
The "done" criteria when this feature or problem is resolved. Such as:

Unit Tests added and running in CI
Functional Tests updated to cover feature, if applicable
Demonstrate the set of capabilities to the product team while the code is running in the STAGING environment.

References
(Optional) Provide any code or specification references that would be helpful for the developer implementing this feature.

REsolved

Verified below scenarios

Scenario
Status
Bug
Comments

Redirect to Contributor Console when clicked on CLA NOT SIGNED in github PR
Passed

Only Individual option is displayed when only ICLA is enabled for the project
Passed

UI alignment when only Individual option is displayed
Passed

UI alignment when only Individual option is clicked
Passed

Individual contribution when only ICLA is enabled
Passed

Only Corporate option is displayed when only CCLA is enabled for the project
Passed

UI alignment when only Corporate option is displayed
Passed

Company Selection Popup when clicked on Corporate
Passed

Company Selection Popup search functionality
Passed

Not signed Company popup when requesting for authorization
Passed

Both Individual and Corporate options are displayed when both ICLA and CCLA is enabled for the project
Passed

UI alignment when both Individual and Corporate options are displayed
Passed

Individual contribution when both CCLA and ICLA are enabled
Passed

Employee request for authorization by selecting cla manager from list when company has signed CLA
Passed

Employee request for authorization by directly entering cla manager from list when company has signed CLA
Passed

Whitelisted employee contribution when ICLA signature is required
Passed

Whitelisted employee contribution when ICLA signature is not required
Passed

Employee request for authorization when company is not in list and when contributor is not cla manager
Passed

Employee request for authorization when company is not in list and when contributor is cla manager. User redirected to Corporate Console
Passed


Date picker browser issue

There's an issue with different browsers displaying date in create event page. The date picker might either only work on Chrome or Firefox.

Closed in PR #1260


[Tests] Recreate keystores used in TLS tests with RSA key algorithm & SHA256 to support JDK 11 & TLS 1.3

Fixes #9720
Motivation
The current client.keystore.jks key is invalid for JDK 11:

SHA1 signature algorithm isn't accepted in JDK11 since it includes a change "JEP 288: Disable SHA-1 Certificates".
TLS 1.3 algorithm also forbids the usage of SHA1 signature algorithm. In TLS1.3, the key must be a RSA key and the signature algorithm at least SHA256. TLS 1.3 is bundled in JDK 8 since 8u261 so it's not specific to JDK11.
Other
There's a separate issue for changing the default TLS protocols, #10335 .
Modifications

add script for creating keystores for tests
update documentation to include -keyalg RSA when creating keys
update keystores used in tests

Updated keystore

There are also some invalid certificate files created as .pem files. Here's a list of the invalid ones which use SHA1:
❯ find -name "*.pem" |grep src |xargs -i{} bash -c "{ openssl x509 -text -in {} 2>/dev/null | grep -q 'Signature Algorithm: sha1'; } && echo {}"
./bouncy-castle/bcfips-include-test/src/test/resources/authentication/tls/broker-cert.pem
./bouncy-castle/bcfips-include-test/src/test/resources/authentication/tls/client-cert.pem
./bouncy-castle/bcfips-include-test/src/test/resources/authentication/tls/cacert.pem
./pulsar-proxy/src/test/resources/authentication/tls/client-cert.pem
./pulsar-proxy/src/test/resources/authentication/tls/server-cert.pem
./pulsar-proxy/src/test/resources/authentication/tls/ProxyWithAuthorizationTest/proxy-cacert.pem
./pulsar-proxy/src/test/resources/authentication/tls/ProxyWithAuthorizationTest/client-cacert.pem
./pulsar-proxy/src/test/resources/authentication/tls/ProxyWithAuthorizationTest/broker-cert.pem
./pulsar-proxy/src/test/resources/authentication/tls/ProxyWithAuthorizationTest/proxy-cert.pem
./pulsar-proxy/src/test/resources/authentication/tls/ProxyWithAuthorizationTest/client-cert.pem
./pulsar-proxy/src/test/resources/authentication/tls/ProxyWithAuthorizationTest/broker-cacert.pem
./pulsar-proxy/src/test/resources/authentication/tls/cacert.pem

@merlimat Please review

@merlimat @aahmed-se Please review


Add JWT login to Django

It focuses on enabling secure user login and token-based authentication for API endpoints.

This has been taken care of and tested. The associated files are under the auth_review folder. Check out the models.py, views.py, urls.py, and serializers.py. Please test this on your end and validate.

I can see the relevant brach being pulled - closing the issue


[move-vm] separate error code for vector ops

The ABORTED error code is reserved for the Move abort operation.
Runtime errors originated from vector operations should have their own
error category (similar to ARITHMETIC_ERROR). This commit adds the new
error category VECTOR_OPERATION_ERROR.
NOTE: this change applies to the vector bytecode only but not the native
functions in move-stdlib. These native functions still return ABORTED with
a sub error code. This is achieved by mapping VECTOR_OPERATION_ERROR
into ABORTED at the native function adapter layer.
NOTE: a few test cases in move-stdlib VectorTests.move need to take
the following adjustment:
#[expected_failure(abort_code = 1) --> #[expected_failure]
This is due to a limitation documented in #8338 that the unit-test result
checker only checks sub error code when the major error code is ABORTED.
Now with VECTOR_OPERATION_ERROR being the major error code,
these sub code won't be caught by the unit-test framework, which is similar
to the situation of ARITHMETIC_ERROR discussed in the issue. Double
checking with @tzakian to see whether this needs to be address in this PR.

Motivation
Consistency of error codes
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
CI, especially the test cases in the move-vm

Fixed. The native functions' behaviors are reverted back, they still return ABORTED now.

/land


release: v1.3.0 on May 31

1.2 hubs will auto terminate on Jun 14.
1.3 changes are tracked here: https://github.com/farcasterxyz/hub-monorepo/issues/895
Most notable user facing changes in this release are https://github.com/farcasterxyz/protocol/discussions/86 (not yet implemented) and https://github.com/farcasterxyz/hub-monorepo/pull/928
Planning to release to testnet around May 22 (depending on when multisignatures work gets in and the kind of dev coordination work required for it) and cut a release the following week.


Context propagation API

type Context interface {
    Put(Container) Context
    Container() Container
    Resolver() Resolver
    Raw() context.Context
}

Context propagation is possible via di.Context abstraction. Quick example:
var container = di.NewContainer()
container.Implementation(newCircle())

var (
    ctx = di.Ctx(context.Background).Put(container)
    shp Shape
)

err = ctx.Resolver().Resolve(&shp) // err == nil

Codecov Report

Merging #6 (0b0ae00) into master (c96a0d7) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master        #6   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         5    +1
  Lines          383       399   +16
=========================================
+ Hits           383       399   +16

Impacted Files
Coverage Δ

context.go
100.00% <100.00%> (ø)

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 c96a0d7...0b0ae00. Read the comment docs.

Looks fine


Full master merge

Don't look at this until #893 is in. But after that it's pretty straightforward.

ok, should be good to go--I'll leave it in y'alls hands while I'm on vacation

@dotnet-bot test this please

GitHub's baseline for what's getting dragged in is wrong, I think. But I don't know how to fix that. I don't think there's actually much of interest in the merge other than the Roslyn reference I had to add, though.

:shipit:


Submit all boss kc on plugin startup

I think it would be helpful if the plugin submitted all of my boss KC on startup, or when visiting the collection log, or something similar, instead of just on a boss kill. Just like how all skill xp is reported without needing to gain XP first! I'm not sure if the chat commands plugin has an easy way to access that, but you'd have to change some of the logic here https://github.com/Equinox-/runelite-influxdb/blob/master/src/main/java/net/machpi/runelite/influxdb/InfluxDbPlugin.java#L122-L135

As I'm building out some Grafana dashboards, another way would be to report when the chat command is used. Again I'm not sure of any hooks that we could tie into this, but if it's easier it's certainly doable to just !kc boss to populate some numbers initially. I realize this data logging is best for showing increases over time and not "current stats"" though.

I can easily report the current state from the same place I receive updates on plugin load.  Already have it working, just have to push it up.

I have some more work I want to do before I push changes up to the plugin hub, so the most recent changes won't show up there immediately.


Debugger not hitting 'GetToken'

The debugger not hitting this method at all.
 public async static Task<string> GetToken(string authority, string resource, string scope)
    {
        var authContext = new AuthenticationContext(authority);
        AuthenticationResult result = await authContext.AcquireTokenAsync(resource, _clientCredential);

        if (result == null)
            throw new InvalidOperationException("Failed to obtain the access token");
        return result.AccessToken;
    }

I have the following code, still not hitting
   private static void InitializeAzureKeyVaultProvider()
    {
        _clientCredential = new ClientCredential(applicationId, clientKey);

        SqlColumnEncryptionAzureKeyVaultProvider azureKeyVaultProvider =
          new SqlColumnEncryptionAzureKeyVaultProvider(GetToken);

        Dictionary<string, SqlColumnEncryptionKeyStoreProvider> providers =
          new Dictionary<string, SqlColumnEncryptionKeyStoreProvider>();

        providers.Add(SqlColumnEncryptionAzureKeyVaultProvider.ProviderName, azureKeyVaultProvider);
        SqlConnection.RegisterColumnEncryptionKeyStoreProviders(providers);
    }

What I may be missing?

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

ID: ddcad97f-02c6-4307-7ed8-85ba7ae23ecc
Version Independent ID: 51a5e20b-c221-ee05-cb44-a479bfcf1a00
Content: Configure Always Encrypted by using Azure Key Vault - Azure SQL Database
Content Source: articles/azure-sql/database/always-encrypted-azure-key-vault-configure.md
Service: sql-database
Sub-service: security
GitHub Login: @VanMSFT
Microsoft Alias: vanto

@codemaker We are looking into this and will get back.

Tested the example, and it still works as instructed by the documentation.

Yes, it works. My bad.  I used the wrong application ID.

@codemaker Thank you for letting us know. We are closing this issue but let us know if you need any further help.


Manual testing of UtUtils class generation

Initial set-up
Check that the IntelliJ Idea UTBot plugin can be successfully installed

[x] Take latest build from main
[x] Download plugin
[x] Check downloaded zip-file size < 100 MB
[x] Open IntelliJ IDE
[x] Remove previously installed UTBot plugin
[x] Clone or reuse UTBot project (https://github.com/UnitTestBot/UTBotJava.git)
[x] Open the project in the IDE
[x] Install the downloaded plugin

Go through manual scenarios

[x] 1
[x] 2
[x] 3
[x] 4
[x] 5
[x] 6

Pre-condition
Condition
Class under test
Output

1
No UtUtils class
Generate a test class, that does not need utility methods
IntExamples.java
No UtUtils class is produced.

2
No UtUtils class
Generate a test class, that (a) needs a utility method, (b) does not use mocking
QueueUsages.java
Regular UtUtils class (without mocking support) is produced.

3
Regular UtUtils class (without mocking support) exists
Generate a test class, that (a) needs a utility method, (b) uses mocking
CommonMocksExample.java
UtUtils class with mocking support is produced.

4
UtUtils class with mocking support exists
Generate a test class, that (a) needs a utility method, (b) does not use mocking
QueueUsages.java
UtUtils class with mocking support from the previous generation stays the same.

5
UtUtils class with mocking support exists
Generate another test class, that (a) needs a utility method, (b) does not use mocking + create and choose another Test sources root: utbot-sample/src/test/java2
QueueUsages.java
No additional UtUtils class is generated in utbot-sample/src/test/java2. UtUtils class with mocking support from the previous generation stays the same.

6
No UtUtils class (delete previously generated test classes and UtUtils classes)
Generate a test class, that (a) does not need utility methods (b) uses mocking
MockRandomExamples.java and choose the method randomAsParameter() for test generation
No UtUtils class is produced.

IDEA interaction checks

[ ] Gradle / Maven / IntelliJ
[x] in new test sources root
[ ] in test sources root in other module

Tested with (#503)[https://github.com/UnitTestBot/UTBotJava/actions/runs/3377312923] and IDEA 2022.2.3


added process.env.PARSE_SERVER_SERVERURL

added handling of serverURL as process.env variable

Closing, please combine in #591


gns3-gui, gns3-server: 2.2.49 -> 2.2.50

https://github.com/GNS3/gns3-gui/compare/v2.2.49...v2.2.50
https://github.com/GNS3/gns3-server/compare/v2.2.49...v2.2.50

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 350775

x86_64-linux

:white_check_mark: 4 packages built:

gns3-gui
gns3-gui.dist
gns3-server
gns3-server.dist


Allow prepared statements with WHERE age = $1

Closes #400 .

Please note that this change should target Elm.

There's a lot of places where we depend on Consts. It will be quite hairy to drill params everywhere... Are we guaranteed to know the value at this stage?

There's a lot of places where we depend on Consts. It will be quite hairy to drill params everywhere... Are we guaranteed to know the Param's value at this stage?

Not sure. I think the query is planned with the specific value in mind, and then executed. But if you're thinking about swapping Param for Const when rewriting the query... hm, it could defy the purpose of parametrizing in some unpredictable way, like make sql injection possible? I don't know, I'm just guessing.
But maybe you have something other in mind.
Anyway, after I sort out the pg 14 problem, I'll go through the spots where we use Const and see what these are about. Thank you for the great point.

There's a lot of places where we depend on Consts. It will be quite hairy to drill params everywhere...

Okay, finally I got around to this. There's not that many places, the relevant I think are:
1/ what this PR intends to do, so WHERE
2/ substring verification in untrusted mode
3/ bin size verification in untrusted mode (money style stuff)
So I guess we can live with the drilling. I don't have any smart solution, I thought about implementing a custom type to hold Param together with its value, and pass that around, but I think this would be overdone by a lot.

Are we guaranteed to know the Param's value at this stage?

I had doubts about this given the pg 14 mishap, but I think right now I'm confident that yes, we know the value. This comes in just before PostgreSQL planner, which to my understanding of the docs, will use those values.

Please note that this change should target Elm.

re @cristianberneanu
Actually, having gone through the above, I think this PR targets Fir (which has the WHERE at all), while the issue, together with changes (2/) and (3/) will target Elm and Fir. Or am I confusing something? If not then I'll remove the "clo-ses #400" and make a follow-up PR for (2/) and (3/) -> release/elm.

There's not that many places, the relevant I think are:

The SQL seed depends on the constant arguments as well.

... I think this PR targets Fir ...

Except the changes to handling WHERE clauses, everything else applies to Elm. I think it would have been cleaner to first update Elm, merge the Elm branch to master, then do the remaining WHERE update for Fir. But the other way around is fine with me too.

There's not that many places, the relevant I think are:

The SQL seed depends on the constant arguments as well.

Hm, this is (1/) and handled in this PR.

... I think this PR targets Fir ...

Except the changes to handling WHERE clauses, everything else applies to Elm.

Exactly what I have written, this PR is (1/) only => WHERE only => Fir. Or am I completely lost?

I think it would have been cleaner to first update Elm, merge the Elm branch to master, then do the remaining WHERE update for Fir. But the other way around is fine with me too.

:+1: OK, I'll see how to play this out.

Hm, this is (1/) and handled in this PR.
Exactly what I have written, this PR is (1/) only => WHERE only => Fir. Or am I completely lost?

I don't understand what you mean to say here. Constants/parameters can appear in two locations of interest to us: generalization expressions and equality comparisons. The former applies to GROUP BY (implicit or explicit) and WHERE clauses, the latter applies only to WHERE clauses.

I don't understand what you mean to say here. Constants/parameters can appear in two locations of interest to us: generalization expressions and equality comparisons. The former applies to GROUP BY (implicit or explicit) and WHERE clauses, the latter applies only to WHERE clauses.

So this PR is only the "latter". I think we're talking about the same thing, let's defer discussion to when there's a reviewable PR(s).


Take U, CX out of default basis for the Unroller pass

The unroller currently implicitly assumes that U and CX are in the basis whenever any unrolling happens. @jaygambetta mentioned that we should remove this behavior in favor of always explicitly specifying the basis. If the circuit cannot be unrolled to the given basis, an exception must be raised.

I'm closing this because duplicate with #1697. This one was previous, but in #1697 there is a longer discussion and explanation. @ajavadia let me know if they are not the same.


Remove IFs with sys_version_info from boa3.constants to remove python 3.7, 3.8 & 3.9 support

Task linked: CU-86a0aw4v6 Remove IFs with sys_version_info from boa3.constants to remove python 3.7, 3.8 & 3.9 support

coverage: 91.855% (-0.2%) from 92.049% when pulling 164b88353edad8bef41e4927e1baa276f457fec5 on CU-86a0aw4v6 into 5fdb414bf096051a7eb8d188ca3ce13468d02272 on development.


Add DuckDuckGo AI Chat

Pre-flight Checklist
Please ensure you've completed all of the following.

[x] I have read the Contributing Guidelines for this project.
[x] I agree to follow the Code of Conduct that this project adheres to.
[ ] I updated the version package Updating

Description of Change

@all-contributors please add @mdSlash for code


Testing | Have a backend that will be used by the OPCT officials. Officials will be able to register and log in.

[ ] documentation
[ ] front end task
[ ] back end task
[ ] testing


[1.12] Update Postgres components reference

Update the Postgres components reference: state store, binding, config store.
Need to add:

Support for Azure AD
New/updated metadata properties

Code PRs:

dapr/components-contrib#2970
dapr/components-contrib#2971

/assign

@ItalyPaleAle friendly bump

closed by #3811


TypeError: pad_sequence(): argument 'padding_value' (position 3) must be float, not NoneType

我使用llava的框架，把LLM替换成其他的大语言模型，运行过程中报错TypeError: pad_sequence(): argument 'padding_value' (position 3) must be float, not NoneType具体错误如下

请问各位大佬具体是哪里的问题

I am also getting the same error which base model you are using?

I am also getting the same error which base model you are using?

I am using Qwen-7B，Could you please help me with a solution?

You can check whether the pad_token is undefined in your tokenizer.
When I adapt Qwen to llava, the pad_token is None in QwenTokenizer, which caused the same error.

You can check whether the pad_token is undefined in your tokenizer.
When I adapt Qwen to llava, the pad_token is None in QwenTokenizer, which caused the same error.

How can I check? If it turns out as you mentioned, how can I solve it? Thank you for your response.

I am also using Qwen-7b actually for llama unk_token is  but qwen it is null. SO it is causing error. Pad sequence error.
unk_token == null  for Qwen
unk_token""
If you want to validate it is available in tokenizer_config.json
After modifying training initiated but loss is zero.

Anyone help me to resolve the issue.

@haotian-liu  Could you please give your insights how we can train using qwen7b base model and solve the issue?

The pad_token is used to make attention mask, just set the pad_token_id as -100 directly in the training code will solve it.

Have you trained model by assigning pad_token_id  to -100, could you please share config if feasible otherwise make comment over accuracy for the model you have trained.

I also try to use llama3-8b as llm, and i add the code "tokenizer.pad_token_id=-100", after that when i start pretrain, i get the error: OverflowError: out of range integral type conversion attempted

Here's the fix, if you're not using the LLaVA-NeXT codebase:
Add the following to line 909 in train.py (https://github.com/haotian-liu/LLaVA/blob/main/llava/train/train.py#L909)
    if "llama-3" in model_args.model_name_or_path.lower():
        # hack for the LLaMA 3 using Qwen tokenizer, by default Qwen doesn't have a pad token but we can assign it EOT as pad.
        # more information: https://github.com/QwenLM/Qwen/blob/main/tokenization_note.md
        logging.warn(f"Model name: {model_args.model_name_or_path.lower()}")
        logging.warn("Making the new pad token for the tokenizer")
        # this is the hack you need because later in the logic, it adds the unk token
        tokenizer.pad_token='<|eot_id|>'
        tokenizer.unk_token='<|eot_id|>'
        logging.warn(f"Tokenizer pad token! {tokenizer.pad_token}")

This follows from the suggestion for Qwen adding pad tokens (llama 3 is based on qwen)

在train.py中当--version plain时会强制改变tokenizer.pad_token为tokenizer.unk_token，跟着tokenizer.pad_token_id索引不到对应的值就变为了None，所以报错了，我这么理解的，这里我设置--version v0会保留LLM原来的tokenizer.pad_token，就不报错了


fix newline windows issue in generate_csv

Please read through our contribution guide prior to
creating your pull request.

Note that there is a section on requirements related to adding a new DataPipe.

Fixes #674
Changes
-updated tutorial in documentation to specify the newline explitly
writer = csv.DictWriter(open(f"sample_data{file_label}.csv", "w", newline=''), fieldnames=fieldnames)
instead of:
writer = csv.DictWriter(open(f"sample_data{file_label}.csv", "w"), fieldnames=fieldnames)
Testing

tested by running the generate_csv function before and after on a windows machine, before was creating newlines between lines and throwing errors, after the created files don't have newlines and full tutorial works

Same problem discussed here with this as a solution: https://stackoverflow.com/questions/3348460/csv-file-written-with-python-has-blank-lines-between-each-row


url-encoded links

Hello
I love this extension and I use it all the time. Thanks so much for making it!
I do wish however that when inserting a link to another file, it would automatically replace spaces ( ) in the filename with the url-encoded space character ( %20) to make sure it's clickable.
See screenshot

@cristianmtr great idea! Thank you for the feedback. I made a very minor PR to resolve the issue where there are files getting linked with spaces. This PR should get merged sometime later this week.


layer-shell: Fix crash when cursor is intially outside any output

On the X11 backend the cursor position might be outside the output
window so no output is returned leading to the assert to trigger. Use
sane fallback instead of crashing.

Yeah, I was a bit undecided if this is a protocol error since the client requested s.th. the compositor could not fulfill or not. Updated.


DTSRD-90: Spring boot upgrade

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Duplicate of DTSRD-59


ci: Check Dockerfile build & fix well-formedness issue

Fixes https://github.com/sourcegraph/scip-go/issues/85

If there are further suggestions, we can fix them post merge.


v0.14.0

Checklist

[x] I have read the Contributing Guidelines
[x] I acknowledge that any submitted code will be licensed under the ISC License
[x] I confirm that submitted code is my own work
[x] I have tested the code, and confirm that it works

Enviroment

Operating System: Win 10
Node version: 16
npm version: 8

Description

This is a big one!

added initial API structure
added overhauled user system with /api/user API routes
added Nano ID package for random generation
use new webhook library (https://github.com/tycrek/discord-hookr)
feat: display ass version in Webhook author 20db648bc1592f903cf230bec9b8ca006b76a422
fix: image was full-width on web but stretched 73631d01b4b1d85f4eedf151d355a605c4270aca
feat: allow using the generated ID in the web viewer fe79d8466246ae2323bd1abe338adf63b06dd2df
feat: added server side embed configs d7b57e5e95b7427f19f906a53b17a36dbe283585
feat: add creating users via API 4663ce40c971fc6bbc3fd3f06eb561e39e959b5a
feat: added script to add users by CLI 69bf9aaa8617691d43c0a11bf408382eb25c68f0

fuck it we mergin


Add PPP

Part of https://github.com/AY2122S1-CS2103T-W16-2/tp/issues/207.
Preview here.

Codecov Report

Merging #252 (e440d34) into master (6217ca6) will increase coverage by 0.02%.
The diff coverage is 80.00%.

@@             Coverage Diff              @@
##             master     #252      +/-   ##
============================================
+ Coverage     77.48%   77.50%   +0.02%
  Complexity     1149     1149
============================================
  Files           139      139
  Lines          3344     3348       +4
  Branches        374      374
============================================
+ Hits           2591     2595       +4
  Misses          657      657
  Partials         96       96

Impacted Files
Coverage Δ

...22s1_cs2103t_w16_2/btbb/commons/core/Messages.java
0.00% <ø> (ø)

..._2/btbb/logic/commands/order/DoneOrderCommand.java
91.30% <ø> (ø)

.../btbb/logic/commands/order/UndoneOrderCommand.java
91.30% <ø> (ø)

...122s1_cs2103t_w16_2/btbb/model/order/Deadline.java
91.66% <ø> (ø)

...tbb/model/predicate/ValueWithinRangePredicate.java
92.85% <ø> (ø)

...ava/ay2122s1_cs2103t_w16_2/btbb/ui/MainWindow.java
0.00% <ø> (ø)

...16_2/btbb/model/predicate/PredicateCollection.java
91.17% <60.00%> (ø)

...6_2/btbb/logic/commands/order/AddOrderCommand.java
100.00% <100.00%> (ø)

... and 1 more

Continue to review full report at Codecov.

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


Basic example fails to build

Describe the bug
I'm trying to add a reproducible setup to the basic example via Docker. Can't seem to build the example project.
cd examples/basic
docker build --tag nest-next-basic .

Dockerfile
FROM node:14-alpine

WORKDIR /app

COPY package.json /app
RUN yarn install

COPY . /app

EXPOSE 3000

RUN yarn build

#8 3.690 Failed to compile.
#8 3.690
#8 3.690 ./src/application.module.ts:13:9
#8 3.690 Type error: Type '{ useFilesystemPublicRoutes: false; }' is not assignable to type 'NextConfig'.
#8 3.690   Type '{ useFilesystemPublicRoutes: false; }' is missing the following properties from type '{ i18n?: { locales: string[]; defaultLocale: string; domains?: DomainLocales | undefined; localeDetection?: false | undefined; } | null | undefined; headers?: (() => Promise<Header[]>) | undefined; ... 4 more ...; experimental: { ...; }; }': future, experimental
#8 3.690
#8 3.690   11 |       Next({
#8 3.690   12 |         dev: process.env.NODE_ENV !== 'production',
#8 3.690 > 13 |         conf: { useFilesystemPublicRoutes: false },
#8 3.690      |         ^
#8 3.690   14 |       }),
#8 3.690   15 |     ),
#8 3.690   16 |   ],
#8 3.705 error Command failed with exit code 1.

To Reproduce

Repository URL: https://github.com/thisismydesign/nest-next/tree/add-docker-to-basic-example
Version
As defined in the example.
"nest-next": "^9.3.0",
"next": "10",

This is interesting... are you getting this error when building locally too? Or is it limited to the container?

I don't have a local setup, just docker. I noticed you don't have yarn.lock committed or a docker setup. I think it would be great to have a reproducible setup as I don't think the current one is reliable long term.
FWIW if I ignore the offending file from TS, the example works fine.

I agree with you about both the yarn.lock and dockerfile, that is a good idea. I will work on getting a Dockerfile working locally, which will hopefully resolve the issue.
Before I am able to do that though, you should be able to typescript to stop erroring out with the following:
Next({
  dev: process.env.NODE_ENV !== 'production',
  conf: { useFilesystemPublicRoutes: false } as any,
}),

Note that this isn't considered good practice but I don't want to block your ability to make progress.

Thank Kyle, yes, working around the TS issue is a good temporary solution for me.


glyph-icons are showing up as rectangles

I am using bootstrap-sass 3.3.3.
The glyphicons are showing up as square rectangles []
I have no errors when i inspect element
application.scss
@import "bootstrap-sprockets";
@import "bootstrap";
application.js
//= require bootstrap-sprockets

I have the same error.
I checked the complied code, and find that the definition of font-face(Glyphicons Halflings) is surrounding by at-root tag.
Is it the problem of sass?
My bootstrap-sass version: 3.3.5.
My sass version: 3.4.15.

Delete the surrounding at-root tag in assets/stylesheets/bootstrap/_glyphicons.scss can solve this problem.

Deleting at-root worked for me !

I can't repro with Sass 3.4.15 (Selective Steve); there's no @at-root in the output.
bootstrap-sass now requires Sass >=3.3.x. See #920.
@Kelvin-09 Can you please triple-check that you're using the right versions of Sass and bootstrap-sass?

Thank you, @cvrebert .
I just complied the source code with sass, and the at-root was disappeared this time.
But when I'm using grunt and grunt-sass to complie the source code, the problem happens again.
I think there's something goes wrong in my grunt configuration file.

@cvandermeer What version of Sass are you using?

I was using sass-rails 4.0.3

Oh, I get it.
The version of my Sass and bootstrap-sass are both the latest.
But I forget to update grunt-sass from 0.14.0 to 1.0.0.
Hope this can help you, @cvandermeer .

@cvandermeer Looks like that depends on sass ~> 3.1. Can you check what actual version of Sass you have installed?

AH Its 3.2 So that might be the issue

Ok, closing this as a duplicate of #920 then.

Updating sass fixed it!

Great!


Bought a domain through cloudflare, does fruition work with it?

My custom domain name was bought through Cloudflare, which seems to create an issue of pointing my worker to my custom domain. Has any found any answers to this? Or did they just transfer domains to another provider?

What is the issue?

me too. I have the same issues to setup.

@DudeThatsErin The issue ( I think) is that you cannot change nameservers within Cloudflare if you host a domain through them. Then the workers can't communicate between Notion and the actual domain.


Improved AgentConfig options

An admin should be able to tell a natlas agent to scan all ports with -p- and not use the natlas-services file. In some environments where not all ports are yet known, some could be outside the top 1000 or unknown of entirely, performing a scan of everything until an operator can limit their scope would be fantastic.

I'll implement this at the same time that I implement a script group selector for --script so that we move beyond just allowing default script scans.


Declare type exports

Type exports for the connect package are currently not explicitly specified.

Adds explicit type exports for every entrypoint of the connect package.
Puts the type exports for all packages first (in accordance with the documentation: https://www.typescriptlang.org/docs/handbook/esm-node.html)
Removes typesVersions which shouldn't be necessary afaik (please correct me if I'm missing sth.)

Thanks for the contrib, @fubhy ❤
We do need the "typesVersion", unfortunately.
The repo uses "Node" module resolution, and if you run make build without "typesVersion", you'll see that failing with:
src/connect-transport.ts:47:8 - error TS7016: Could not find a declaration file for module '@bufbuild/connect/protocol'. '/Users/ts/buf/connect-es/packages/connect/protocol.js' implicitly has an 'any' type.
  If the '@bufbuild/connect' package actually exposes this module, try adding a new declaration (.d.ts) file containing `declare module '@bufbuild/connect/protocol';`

47 } from "@bufbuild/connect/protocol";
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Many projects are stuck with the node module resolution algorithm. It's still used when you run create-react-app. We need to support it.
Can you revert this one? Otherwise, this looks good to me!

Ah right. Good catch, thanks! Will revert tha tone in a moment.


Use react_component method in ReactOnRailsHelper inside a lib model object.

I am wanting to server side render a react component from a ruby model object located inside my lib folder.  I am able to use the react_component method in my haml file to server side render my component, but I am not able to access the method when wanting to use it to generate the html from inside a model object residing in my lib folder.
Is there an equivalent method inside the react_on_fails lib folder that I can include to get the html, or can I include the ReactOnRailsHelper module in some way to achieve this?  With the react-rails gem I was previously using, I was able to find the ruby code that server-side rendered the component inside their lib folder.  However, with this gem, all I see is the ReactOnRailsHelper file under the app/helpers folder.
file path is the following:  lib/error/error_view
def initialize(data = {})

  @name = data[:name]
  @description = data[:description]

end

# Public: Renders the ErrorView into a HTML String.
#
# template - The ActionView instance rendering the ErrorView.
#
# Returns a HTML String.
def render_with_template(_template)

  # cannot find react_component
  react_component('ErrorView',
                                     props: {'name': @name,
                                             'description': @description},
                                     prerender: true)

end

@kschuste This should be no different than trying to use any view helper outside of a view.

I'm trying to do a thing quite similar: Rendering a React component on the server from a Sidekiq worker. My goal is to take a snapshot of a React component and save it as a PNG. There are no requests, controllers or mailers involved.
This is how the beginning of my class which renders the ERB template looks like:
class TileRenderer
  include ReactOnRailsHelper
  include ActionView::Helpers::TagHelper

So, I can use the react_component helper in my ERB template. But when I do, it throws the following error:
NameError - undefined local variable or method `controller' for #<TileRenderer:0x007f46cf4da630>
21:01:39 web.1    | Did you mean?  content_for:
21:01:39 web.1    |   react_on_rails (6.3.1) app/helpers/react_on_rails_helper.rb:405:in `in_mailer?'
21:01:39 web.1    |   react_on_rails (6.3.1) app/helpers/react_on_rails_helper.rb:348:in `rails_context'
21:01:39 web.1    |   react_on_rails (6.3.1) app/helpers/react_on_rails_helper.rb:285:in `server_rendered_react_component_html'
21:01:39 web.1    |   react_on_rails (6.3.1) app/helpers/react_on_rails_helper.rb:112:in `react_component'

The line throwing the error is this:
def in_mailer?
    return false unless controller.present?

Shouldn't it be something like: defined? controller
Or am I missing something here? Is it even possible to do what I wanted?

@marcaltmann See the https://github.com/shakacode/react_on_rails/blob/master/CHANGELOG.md. Your issue got fixed last week.

@justin808 It seems that the issue didn't actually get fixed. The in_mailer? method fails with a NameError. It probably should be defined? controller.

@marcaltmann or @jtibbertsma Any chance one of you can provide a PR with a failing test that demonstrates the issue and a fix that passes the test?


Synced Networked Variables

See linked RFC document →
RFC for the synced NetworkedVariables

hey @jeffreyrainy — do you think this RFC represents what's being worked on so far?
if so, do you think it's ready to be merged & get in?
if not, do you think we need to update this one and continue from here or are you planning to close this one out and start fresh on a new one?

hey @jeffreyrainy — do you think this RFC represents what's being worked on so far?
if so, do you think it's ready to be merged & get in?
if not, do you think we need to update this one and continue from here or are you planning to close this one out and start fresh on a new one?

No, this gets closed. And new ones should be coming up for the Snapshot System (and maybe even just NetworkVariables)
Thanks for the reminder.


AWS Integration test doesn't clean bucket

After running integration test camel-quarkus-integration-test-aws2-s3 the bucket isn't cleaned.

Some S3 tests had not delete the objects. And it should log the WARN message
WARN: Could not close org.apache.camel.quarkus.component.aws2.Aws2S3TestEnvCustomizer$$Lambda$1305/0x00000008406ad840@41ec4271
software.amazon.awssdk.services.s3.model.S3Exception: The bucket you tried to delete is not empty (Service: S3, Status Code: 409, Request ID: asdfasdfsdafds, Extended Request ID: MzRISOwyjmnupC97B93A60D1C2C767/JypPGXLh0OVFGcJaaO3KW/hRAqKOpIEEp)

But we can not find anything like this in the console output.


SQLSyntaxErrorException

Version

Paper 1.20.1-22
MySQL 8

Describe
when i use /home list it will show this error in log
Server Logs
https://mclo.gs/dCL3J8A

Already fixed in 4.4.1 dev versions — download from Modrinth :)


Property AccountAlias does not exist - version 4.0.1

I'm trying to Query the accounting accounts list and both 'FindAll' and 'Query' methods are throwing me back the same exception: Property AccountAlias does not exist
I've been using the sample code so I don't think there's anything wrong, considering I'm able to query other resources the same way (customers, vendors, items...).
Has AccountAlias been removed in the latest version of the SDK ?
Any help appreciated ✌

Is there an alternate way to get a list of accounts in the current version?
Thanks


ci: remove node setup

What did you fix?
n/a

Reproduction steps

Evidence/screenshot/link to line

Considerations

Does this contain a new dependency? [Yes/No]
Does this introduce opinionated data formatting or manual data entry? [Yes/No]
Does this pr include updated data files in a separate commit that can be reverted for a clean code-only pr? [Yes/No]
Have I run the linter? [Yes/No]
Is is a bug fix, feature request, or enhancement? [Bug Fix/Feature/Enhancement/Docs/Maintenance]

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

v0.2.0
GitHub release

Your semantic-release bot :package::rocket:


Suggestion for a different response code for invalid credentials in password grant

Description:
When we give invalid credentials while calling "/token" endpoint with password grant, the server returns HTTP status code 400 in response.
Sample request for token on a newly installed APIM setup:
curl -L -w "\\n%{http_code} %{url_effective}\\n" -k -X POST https://localhost:8243/token -d "grant_type=password&username=admin01&password=admin" -H "Authorization: Basic <client_key:client_secret>"
Response:
{"error_description":"Authentication failed for admin01","error":"invalid_grant"}
Http error code: 400 (Bad request)
Expectation:
Usually, HTTP error code 401 is used as the response code for invalid credentials.
Error code 400 indicates (RFC 7231, section 6.5.1: 400 Bad Request):

The 400 (Bad Request) status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Please note that, if Basic header is wrong, server returns 401 status code in response but 400 for invalid credentials.
With 400 response code, there is a confusion if the request itself was invalid.
Tested with APIM Version: 3.0.0, 2.6.0
Solution:
Change the response code to 401 or a custom error code (if needed) when credentials are invalid to avoid confusion.
I would like to contribute towards the solution if the team thinks this is a valid issue.
Attaching screenshot for reference.

Hi @ankit-agrawal07
Please go ahead with the contribution.


edit distance solution added

There are two versions of edit distance, one is of O(mn) space complexity and other is of O(min(m,n)) space complexity where m,n are length of two strings. First file is O(mn) space complexity and second is of O(m) space complexity. Backtracking is also added.

Please consider it under Hacktoberfest label.

@Thuva4 , please review it and suggest any changes if you find anything wrong.

@amankh99 Update the Readme :+1:

@Thuva4 , please review the changes and suggest further changes.


create software development mcq

Hi @talktonok, great job. your questions are tabulated. however they are not categorised by Soft Skill, Technical Skill and Cognitive Ability as indicated in the ReadMe instruction. good work though

Hi @talktonok, great job. your questions are tabulated. however they are not categorized by Soft Skill, Technical Skill, and Cognitive Ability as indicated in the ReadMe instruction. good work though

Thank you so much @Paul-Ben I noticed that and already working on it.

This is a amazing work. In addition to @Paul-Ben review, Please don't forget to take a second look at the domain.  I am ready to assist with the refactoring, should my assistant be needed

Hi @talktonok, great job. your questions are tabulated. however they are not categorized by Soft Skill, Technical Skill, and Cognitive Ability as indicated in the ReadMe instruction. good work though

Thank you so much @Paul-Ben I noticed that and already working on it.

Great to hear that you're working on it.


Set box-sizing for border-box universal styles

When a universal CSS selector applies box-sizing: border-box; (which is a common pattern in CSS and commonly included in resets), the styling on the autocomplete icon is a bit broken:
box-sizing: border-box, key icon overlapping with text:

box-sizing: content-box, key icon not overlapping with text:

This PR ensures that the autocomplete icon will use the correct box sizing.
See also https://github.com/uiwjs/react-codemirror/issues/411, which this PR would resolve.

An alternative to this would be to use CSS properties for the sizing that behave the same in both box models...

Merged, thanks.

Glad to help, thanks for the merge! Will this be published as a part of<EMAIL_ADDRESS>


chore!: Serialize, Deserialize and NoteInterface as Traits

Closes: https://github.com/AztecProtocol/aztec-packages/issues/3756, https://github.com/AztecProtocol/aztec-packages/issues/2838
Taking advantage of @jfecher's fantastic work in https://github.com/noir-lang/noir/pull/4000, implemented Serialize<N> and Deserialize<N>. Together with NoteInterface, they make possible getting rid of all the serialization interfaces, which greatly simplify how the storage is handled and opens the door to further improvements. Still some clutter to go, the lengths are still needed in some places.

I'm so sorry.

Benchmark results
Metrics with a significant change:

batch_insert_into_append_only_tree_16_depth_ms (8): 13.7 (-43%)
batch_insert_into_append_only_tree_16_depth_hash_ms (8): 0.542 (-31%)
batch_insert_into_append_only_tree_32_depth_ms (512): 255 (-34%)
batch_insert_into_append_only_tree_32_depth_hash_ms (512): 0.446 (-33%)
node_database_size_in_bytes (10): 3,646,454 (-30%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 7308e31c and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,380
179,492
716,036

l1_rollup_calldata_gas
220,964
866,360
3,447,620

l1_rollup_execution_gas
928,736
3,900,174
24,034,091

l2_block_processing_time_in_ms
1,459 (-7%)
5,268
22,126 (+3%)

note_successful_decrypting_time_in_ms
314 (+2%)
912 (-1%)
3,432 (+2%)

note_trial_decrypting_time_in_ms
24.1 (+39%)
38.4 (-17%)
146 (-3%)

l2_block_building_time_in_ms
16,163
64,027
257,646 (+1%)

l2_block_rollup_simulation_time_in_ms
11,748
46,691
188,493 (+1%)

l2_block_public_tx_process_time_in_ms
4,380
17,252
68,868

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,982
30,620 (+1%)

note_history_successful_decrypting_time_in_ms
2,116 (-2%)
4,248

note_history_trial_decrypting_time_in_ms
98.5 (-64%)
185 (+7%)

node_database_size_in_bytes
3,581,420
:warning: 3,646,454 (-30%)

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
212
44,681
25,561

private-kernel-ordering
165
43,753
14,809

base-rollup
1,199
128,338
881

root-rollup
79.0
4,088
677

private-kernel-inner
293 (+1%)
71,208
25,561

public-kernel-private-input
206
31,863
25,561

public-kernel-non-first-iteration
204
31,905
25,561

merge-rollup
7.62
2,608
881

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
15,455
32,221

Transaction processing duration by data writes.

Metric
0 new commitments
1 new commitments

tx_pxe_processing_time_ms
376 (+1%)
1,083

Metric
1 public data writes

tx_sequencer_processing_time_ms
536

@AztecProtocol/devrel docs are updated and I wrote a short migration guide, but might be missing something!


Abort stream on exit

Problem
Stream hang on break #16
Solution
Added AbortController to abort after exit

LGTM
Though an example would be great


feat(server): plugins can add middlewares and routes

closes https://github.com/denoland/fresh/issues/516
supersedes https://github.com/denoland/fresh/pull/1009
This is basically the same as 1009, except I've added a nice test showing how this is used. It's also updated to the latest changes in Fresh, mainly relevant because https://github.com/denoland/fresh/pull/745 introduced a filter in the form of const syncPlugins = opts.plugins.filter((p) => p.render);, so the filter that 1009 does in render.ts is no longer necessary.
As a followup I can create a new example page called "Writing a plugin which adds routes" or something like that.

This is useful if we want to provide a first party GA4 or CORS middleware plugin, which would probably save people a lot of time.

This looks good to me. Let's add RoeHH as a co-author of the commit since the changes here are most of his work. This SO answer has an explanation on how to do that in git https://stackoverflow.com/questions/7442112/how-to-attribute-a-single-commit-to-multiple-developers

Thanks, good tip. I'll do that in future as well.


update dev

:tada: This issue has been resolved in version 2.6.1-rc.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 2.6.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add tests / more robust support for dynamically enabling and disabling InteractionBehaviours and whole InteractionManagers

One of our developers expressed a user story wherein they desired to have the ability to enable and disable the Interaction Engine as a solution for a specific setup, when trying to insert it into an existing project. They already had a solution for Oculus & Vive controllers and sought to use the Interaction Engine for Leap-specific situations only. However, they had to modify InteractionBehaviour to see if their special 'platform' enum was set to "Leap" to be able to enable and disable the whole Interaction Engine.
Enabling and disabling the interaction engine should be as simple as enabling and disabling the Interaction Manager; there shouldn't be any additional work involved. InteractionBehaviours who lack an Interaction Manager or who have their managers disabled should simply become no-op components -- and potentially also disable themselves to provide peace of mind that they really aren't doing anything.
Since the Interaction Engine also modifies things like object Layers and isKinematic state, we'll essentially need to make sure that InteractionBehaviours remember the pre-IE state of any Rigidbodies or Colliders that it may modify while the engine is active. When the engine is re-enabled, we don't have to resume Controller<>Object relationships, but obviously things like layers need to be adjusted again.
We should also have tests for this, to make sure that we don't spew errors or produce unexpected behavior when entire Interaction Managers turn on and off.

Closing here. Tracking as Unity-755.


Avoid using --save-dev in readme.md

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/15139/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15139/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15139/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15139/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15139/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15139/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15139/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15139/merge#BCU1XR#0

WebGL2 visualization test reporter:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15139/merge/testResults/webgl2playwright/index.html

Visualization tests for WebGPU (Experimental)
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15139/merge/testResults/webgpuplaywright/index.html


Handle equal file size checks properly

The previous code wasn't working for file sizes like 1000, 1000000, etc. because it was only doing less than and greater than checks, no equal checks.
Also, for a file with size 1000001, it would show 1000001MB which is not right, it was missing the needed divisions to turn bytes into megabytes and so on which I have added now.
I also added some tests for the Path::size_string_formatter function.
Closes #1

Thanks! I did forget to actually divide the bytes 😅. Thanks for also introducing testing, once I fix the conflicts with the previous PR I will merge this.


Hotfix: Exclude failed donations from totals

Related to: https://github.com/Giveth/giveth-dapps-v2/issues/1922#issuecomment-1345409267

I don't think we should write a migration to fix all projects, I don't think there are many failed donations, rare case in my opinion. We can fix them manually by donating to them. Like the project Griff mentioned.
https://giveth.io/project/relocating-web3-iranians
But from here on out after this PR, this issue will not happen again.

@mohammadranjbarz Let me know if you agree.

@MoeNick also optimized the queries from 6 to 3. Which is more efficient.

@mohammadranjbarz Let me know if you agree.

Yeah Carlos, I agree with you


Refactor nested ternary expression

Nested ternary expressions are deprecated as of PHP 7.4. I've replaced it with a null coalescing expression as it's more easy to read.
See: https://wiki.php.net/rfc/ternary_associativity

Thanks for the pr


Support for disabling health check

Crate
relayer-cli
Summary
A feedback from the Cephalopod ops team is that they would like a method to optionally disable the health checkup that Hermes does indiscriminately.
Problem Definition
Whenever Hermes starts up, before running any command, it runs a health checkup mechanism that involves a few rounds of RPC calls to each chain. This functionality is especially useful for users who have not much experience with using Hermes (because the health check can surface problems that would otherwise be hidden cf https://github.com/informalsystems/ibc-rs/issues/697). The functionality, however, is not very useful for power-users such as relayer operators.
The health checkup involves pulling the genesis file, and some chains (e.g., hub-4) have very large genesis files (~100MB). This means that the health check is a liability slowing down the whole ops process.
Proposal
A new option is necessary to allow disabling the health checkup mechanism.
This is necessary in particular for CLIs such as:

tx raw packet-recv,
packet-ack,
query unreceived-acks or
query unreceived-packets.

Acceptance Criteria

[ ] Disable the health checkup mechanism for all existing CLIs

by default, upon starting the runtime for a chain, we should not longer call into the health check-related methods:
https://github.com/informalsystems/ibc-rs/blob/85446586daf6dba652271eef31dae29f35da86c2/relayer/src/chain/cosmos.rs#L740-L741

[ ] Add a new CLI hermes health-check

this new CLI should bootstrap chain runtimes for all chains in the config.toml so that the runtimes call the above two methods; thus checking that Hermes has a healthy connection to each chain

For Admin Use

[x] Not duplicate issue
[x] Appropriate labels applied
[x] Appropriate milestone (priority) applied
[x] Appropriate contributors tagged
[x] Contributor assigned/self-assigned

It is unclear which method would be best for disabling the health checkup, either a new config.toml option or a global CLI flag. This can be decided as we go along after consulting with Cephalopod.

I think such commands should just never do the health check (but we can add a command that does just that). This could be achieved by supplying an option to the chain runtime when starting it, but there is no need to expose this in the config file or the CLI options (aside perhaps for the start command).

It is unclear which method would be best for disabling the health checkup, either a new config.toml option or a global CLI flag. This can be decided as we go along after consulting with Cephalopod.

I think such commands should just never do the health check (but we can add a command that does just that). This could be achieved by supplying an option to the chain runtime when starting it, but there is no need to expose this in the config file or the CLI options (aside perhaps for the start command).

Perfect timing for this suggestion, Romain. Mircea and I were reading your idea and concluded it would be the best way to go forward. It seems not even the start command would require the health checkup.
Concrete notes after discussing with Cephalopod:

Between the option of having a global flag for all CLIs (e.g., --no-health-check or a config.toml toggle), best would be to entirely bypass the health check in all CLIs, except for a dedicated new CLI that does solely the health check, e.g., hermes health-check
the health check proved useful at least on occasions when the operator misconfigured the max_tx_size to exceed the genesis/max_block_bytes parameter, so the check itself is useful

@adizere and @romac, I will look into this one. Also for the health check for the max_block_bytes I'll try to replace the logic. Using the /genesis endpoint might not be optimal because the genesis information might be huge and might time out when retrieving the information, probably a better RPC to get that information is the /consensus_params endpoint like https://rpc-cosmos.cosmostation.io/consensus_params?height=7511042.
This endpoint might provide a better performance and these params can be changed through governance so it's better to take a value close to the latest block height available to ensure it's accurate. The genesis value might not reflect the current value for that parameter.