fix: skip path parameters when validating parameters for KwargsModel

Description

The path parameters were only skipped for field definitions which resulted in an error being raised if path parameters were included as part of layered parameters. This fixes that by skipping path parameters in the validation step when creating KwargsModel.

Closes
Fixes #3197.

Note that we have had this in our docs since layered parameters were implemented (https://github.com/litestar-org/litestar/pull/261):

I think that maybe this is the kind of ambiguity that is being avoided:

@get("/{some_value: int}")
def get_some_value(some_value: int) -> Whatever:...   # some_value is path parameter

@get("/something-else")
def get_something_else(some_value: int) -> WhateverElse: ...  # some_value is query parameter

app = Litestar(
    route_handlers=[handle_get_some_value, get_something_else],
    parameters={"some_value": Parameter(description="this is some value that you want")},  # should this apply to both?
)

Note that we have had this in our docs since layered parameters were implemented (#261):

I think that maybe this is the kind of ambiguity that is being avoided:
@get("/{some_value: int}")
def get_some_value(some_value: int) -> Whatever:...   # some_value is path parameter

@get("/something-else")
def get_something_else(some_value: int) -> WhateverElse: ...  # some_value is query parameter

app = Litestar(
    route_handlers=[handle_get_some_value, get_something_else],
    parameters={"some_value": Parameter(description="this is some value that you want")},  # should this apply to both?
)

Aah I hadn't realized this. Yeah, there can be some ambiguity in the example you've shown though we could consider that as a path parameter if you don't specify query in Parameter. That being said, even if we are going to do that, that would be a feature request and it should be something we consider separately.
For now, I'm thinking the fix should be to change the error message so that it is more accurate and displays a message explaining that path parameters can't be used as layered parameters.

Is there really a problem here:
@get("/{some_value: int}")
def get_some_value(some_value: int) -> Whatever:...   # some_value is path parameter

@get("/something-else")
def get_something_else(some_value: int) -> WhateverElse: ...  # some_value is query parameter

app = Litestar(
    route_handlers=[handle_get_some_value, get_something_else],
    parameters={"some_value": Parameter(description="this is some value that you want")},  # should this apply to both?
)

Yes, it would apply to both (whichever gets read first, I guess). User's choice to use similar naming so it's intentional.
Next evolution would be to support:
app = Litestar(
    ...,
    parameters={
        "path_param": Path(description="this is some value that you want")
        "query_param": Query(description="this is some value that you want")
        "any_param": Parameter(description="this is some value that you want")
    },
)

I guess currently that would be:
app = Litestar(
    ...,
    parameters={
        "path_param": Parameter(path=..., description="this is some value that you want")
        "query_param": Parameter(query=..., description="this is some value that you want")
        "any_param": Parameter(description="this is some value that you want")
    },
)

Is there really a problem here:

Well, we can either accept that the ambiguity exists and call it a feature, or disallow it. For better or worse, since layered parameters were introduced this pattern has been explicitly documented as disallowed and so the best that can happen is we develop this change as a feature, but from what I've read, there doesn't seem to be much support for doing so at this time.

app = Litestar(
    ...,
    parameters={
        "path_param": Path(description="this is some value that you want"),
        "query_param": Query(description="this is some value that you want"),
        "any_param": Parameter(description="this is some value that you want"),
    },
)

I'd be interested in exploring along these lines to target v3. Having distinct types for the different types of parameter is more explicit (i.e., there's no domain knowledge necessary to know that thing: Annotated[int, Query(gt=3)] is implicitly a query parameter), and it would remove the need to double supply the name of the header/cookie when it is the same as the func param (thing: Annotated[int, Parameter(header="thing")], vs thing: Annotated[int, Header()]).
I'll close this PR - no point fragmenting discussion between here and in #3197.
@guacs I'll cherry pick your fix for the exception message into another PR.

Fair enough, expecting to see a lot of good stuff, perhaps also that Query/Path/Cookie/whatnot separation, in 3.0 😄
Should I open a ticket about it, or did one exist already...

Fair enough, expecting to see a lot of good stuff, perhaps also that Query/Path/Cookie/whatnot separation, in 3.0 😄
Should I open a ticket about it, or did one exist already...

#3053 is the issue to track this.


Modified UI for Age Calculator

Calculator Functions
The current age calculator accepts birthday as the input, displays current date and outputs age. But the User Interface can be improved to a great extent. Please assign this issue to me so that I can make the necessary changes.
Contribution Event
GSSOC22
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

Is anyone working with this issue !!

yes @harinadh76


Remove deprecation warning on monomorphic fold1

While this was originally deprecated in #42, purescript-arrays and purescript-lists are exporting monomorphic versions of fold/fold1. So, we are removing the deprecation notice here to keep things consistent. See Harry's comment for more context

Should we also bother with the other folds (foldl1, foldr1 and foldMap1)?

If the reasoning behind this was to keep consistency, then I think those should be added.

Should this still be merged?


Proposal logo/Icon

hi, i want to contribute about this great project. I'm not saying your logo is ugly. if you allow me to propose a new logo / icon for you. thank you

We're good, thanks.


[Bug] [dolphinscheduler-ui 2.0.0-alpha]  npm ERR

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
Hello, everyone
I tried to build dolphinscheduler-2.0.0-alpha binaries on win10 and had the following problems:
[INFO] ----------< org.apache.dolphinscheduler:dolphinscheduler-ui >-----------
[INFO] Building dolphinscheduler-ui 2.0.0-alpha                         [26/35]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ dolphinscheduler-ui ---
[INFO] Deleting C:\Users...\Desktop\dolphinscheduler-2.0.0-alpha\dolphinscheduler-ui\target
[INFO]
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ dolphinscheduler-ui ---
[INFO]
[INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) @ dolphinscheduler-ui ---
[INFO]
[INFO] --- frontend-maven-plugin:1.6:install-node-and-npm (install node and npm) @ dolphinscheduler-ui ---
[INFO] Node v12.20.2 is already installed.
[INFO] NPM 6.14.11 is already installed.
[INFO]
[INFO] --- frontend-maven-plugin:1.6:npm (npm install node-sass --unsafe-perm) @ dolphinscheduler-ui ---
[INFO] Running 'npm install node-sass --unsafe-perm' in C:\Users...\Desktop\dolphinscheduler-2.0.0-alpha\dolphinscheduler-ui
[WARNING] npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EACCES: request to https://registry.npmjs.org/node-sass failed, reason: connect EACCES <IP_ADDRESS>:443
[WARNING] npm WARN registry Using stale data from https://registry.npmjs.org/ due to a request error during revalidation.
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
[INFO]
[INFO] ><EMAIL_ADDRESS>install C:\Users...\Desktop\dolphinscheduler-2.0.0-alpha\dolphinscheduler-ui\node_modules\node-sass
[INFO] > node scripts/install.js
[INFO]
[INFO] Cached binary found at C:\Users...\AppData\Roaming\npm-cache\node-sass\4.14.1\win32-x64-72_binding.node
[INFO]
[INFO] ><EMAIL_ADDRESS>postinstall C:\Users...\Desktop\dolphinscheduler-2.0.0-alpha\dolphinscheduler-ui\node_modules\node-sass
[INFO] > node scripts/build.js
[INFO]
[INFO] Binary found at C:\Users...\Desktop\dolphinscheduler-2.0.0-alpha\dolphinscheduler-ui\node_modules\node-sass\vendor\win32-x64-72\binding.node
[INFO] Testing binary
[INFO] Binary is fine
[INFO] +<EMAIL_ADDRESS>[INFO] removed 1309 packages and updated 1 package in 13.248s
[INFO]
[INFO] 1 package is looking for funding
[INFO]   run npm fund for details
[INFO]
[INFO]
[INFO] --- frontend-maven-plugin:1.6:npm (npm install) @ dolphinscheduler-ui ---
[INFO] Running 'npm install' in C:\Users...\Desktop\dolphinscheduler-2.0.0-alpha\dolphinscheduler-ui
[WARNING] npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EACCES: request to https://registry.npmjs.org/acorn failed, reason: connect EACCES <IP_ADDRESS>:443
[WARNING] npm WARN registry Using stale data from https://registry.npmjs.org/ due to a request error during revalidation.
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>This loader has been deprecated. Please use eslint-webpack-plugin
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>3.x is no longer supported
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
[WARNING] npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a sl
owdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>Deprecated due to CVE-2021-21366 resolved in 0.5.0
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
[INFO]
[INFO] ><EMAIL_ADDRESS>preinstall C:\Users...\Desktop\dolphinscheduler-2.0.0-alpha\dolphinscheduler-ui\node_modules\cssnano-preset-default\node_modules\coa
[INFO] > start /B node compile.js & node compile.js
[INFO]
[ERROR] internal/modules/cjs/loader.js:818
[ERROR]   throw err;
[ERROR]   ^
[ERROR]
[ERROR] Error: Cannot find module 'C:\Users...\Desktop\dolphinscheduler-2.0.0-alpha\dolphinscheduler-ui\node_modules\cssnano-preset-default\node_modules\coa\compile.js'
[ERROR]     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
[ERROR]     at Function.Module._load (internal/modules/cjs/loader.js:667:27)
[ERROR]     at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
[ERROR]     at internal/main/run_main_module.js:17:47 {
[ERROR]   code: 'MODULE_NOT_FOUND',
[ERROR]   requireStack: []
[ERROR] }
[ERROR] internal/modules/cjs/loader.js:818
[ERROR]   throw err;
[ERROR]   ^
[ERROR]
[ERROR] Error: Cannot find module 'C:\Users...\Desktop\dolphinscheduler-2.0.0-alpha\dolphinscheduler-ui\node_modules\cssnano-preset-default\node_modules\coa\compile.js'
[ERROR]     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
[ERROR]     at Function.Module._load (internal/modules/cjs/loader.js:667:27)
[ERROR]     at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
[ERROR]     at internal/main/run_main_module.js:17:47 {
[ERROR]   code: 'MODULE_NOT_FOUND',
[ERROR]   requireStack: []
[ERROR] }
[WARNING] npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\chokidar\node_modules\fsevents):
[WARNING] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
[WARNING] npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\watchpack-chokidar2\node_modules\chokidar\node_modules\fsevents):
[WARNING] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
[WARNING] npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\webpack-dev-server\node_modules\chokidar\node_modules\fsevents):
[WARNING] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
[ERROR]
[ERROR] npm ERR! code ELIFECYCLE
[ERROR] npm ERR! errno 1
[ERROR] npm ERR<EMAIL_ADDRESS>preinstall: start /B node compile.js & node compile.js
[ERROR] npm ERR! Exit status 1
[ERROR] npm ERR!
[ERROR] npm ERR! Failed at the<EMAIL_ADDRESS>preinstall script.
[ERROR] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[ERROR]
[ERROR] npm ERR!      C:\Users***\AppData\Roaming\npm-cache_logs\2021-11-05T01_57_17_340Z-debug.log
What you expected to happen
Maybe it's the network environment
How to reproduce
Try building DS on different environments
Anything else
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

you can try TaoBao npm image.
1.临时使用
npm --registry https://registry.npm.taobao.org install express
2.持久使用
npm config set registry https://registry.npm.taobao.org


Function_pointer action error spam

Hi, when setting the Function_Pointer's Active Button to Vr Action and set the name of one of my actions (100% defined in the project's Input map) the editor is filled with the error message
The InputMap action "vr_right_trigger" doesn't exist. Did you mean "ui_right"?

The message disappears when I remove the tool declaration from the script (obviously). But I am not sure if it needs to be a tool.

dangit, it needs to be a tool script for some of the options to work, which is annoying, but it needs extra checks to skip over the process code when running in the editor.

Closing this as it is no longer an issue in the latest version. Note that in Godot 4 we've switched over to using the action map.


Request: disable Managed-Aggregator by default

Request: disable Managed-Aggregator by default
Reason:  aggregator does not normally run a VA test, it aggregates test results from other collectors

Delivered in v1.3.17


Toggle selector bugs in ie11

When the selector has an icon, the icon grows enormous when the input is selector (in ie11)
The items are also not vertically aligned in ie11. Could be related to this issue

:tada: This issue has been resolved in version 4.5.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add a validation webhook

Objective: Mutual Exclusion in the Synapse Spec for the settings related to the synapse configuration file (Crafted using user-provided values VS Loaded from a user-created ConfigMap)

Instead of using a validation webhook to ensure that only one of Spec.Homeserver.ConfigMap and Spec.Homserver.Values is set, we should look into using a Kustomize patch (to be added in config/crd/patches) in order to add a “OneOf'' flag in the swagger OpenAPI v3 schema.


Support for embedding images as base64 with LuaLaTeX

Thanks for this awesome package. I was however a bit unhappy by the fact that image data had to be moved around in separate files, always adding some extra hassle when automatically updating figures from Python. Therefore I created the LuaLaTeX package luaimageembed, which allows for base64-encoded image files to be decoded on-the-fly and inserted into a document; and the necessary changes to tikzplotlib within this PR. (I had initially developed this for figures in my PhD thesis in 2017, and ported it to current HEAD).
While this might not be everyone's use case, I think people with similar problems would be happy about this possibility.
PS: Coverage browsing on codecov.io currently seems broken.

A nice package, but probably too niche to warrant to the changes. I might change my mind if this gains a larger user base in the future. That said, I really like the package.

PS: Coverage browsing on codecov.io currently seems broken.

Fixed now.

A nice package, but probably too niche to warrant to the changes. I might change my mind if this gains a larger user base in the future. That said, I really like the package.

Thanks for the response. I understand that this is a niche application. I would then keep this PR open, so that people with a similar problem can find it. The luaimageembed package is part of TeX Live and as such every recent, complete TeX Live installation has it. The embedding as within this PR is a non-default behavior which has to be enabled by passing embed_images=True to save() or get_tikz_code().

PS: Coverage browsing on codecov.io currently seems broken.

Fixed now.

The branch name is correct now, but opening e.g. https://codecov.io/gh/nschloe/tikzplotlib/src/main/tikzplotlib/_save.py still gives me a "GitHub API: Forbidden" error.

I would then keep this PR open, so that people with a similar problem can find it.

Sounds good to me.

The branch name is correct now, but opening e.g. https://codecov.io/gh/nschloe/tikzplotlib/src/main/tikzplotlib/_save.py still gives me a "GitHub API: Forbidden" error.

Interesting. No idea why that should be, perhaps an authorization issue at codecov? Works well for me (logged in), but should of course be visible to everyone.

I would then keep this PR open, so that people with a similar problem can find it.

Sounds good to me.

The branch name is correct now, but opening e.g. https://codecov.io/gh/nschloe/tikzplotlib/src/main/tikzplotlib/_save.py still gives me a "GitHub API: Forbidden" error.

Interesting. No idea why that should be, perhaps an authorization issue at codecov? Works well for me (logged in), but should of course be visible to everyone.

Now it works ... maybe some cache on their side. Thanks for fixing.


feat(lending): adapter, protocol use async to init config

[x] remove lending protocol token config, use real-time api instead
[x] make Adapter LendingProtocol to asynchronous to handle getReserveTokens
[ ] test:unit
[x] yarn changeset

LGTM


OpenCensus: Use new CallTracer interfaces

This change mostly aims to get OpenCensus to use the new ServerCallTracer interface. Note that the interfaces nor the code are in their final states. There are a bunch of moving pieces, but I thought this might be a nice mid-step to check-in and make sure that our internal traces can also work with these changes.
Overall changes -

call_tracer.h shows what the hierarchy of new call tracer interfaces looks like. Open to renaming suggestions.
Moved most of the common interface between CallAttemptTracer and ServerCallTracer into a common CallTracerInterface. We should be able to eventually move RecordReceivedTrailingMetadata and RecordEnd as well to these common interfaces, but it requires some additional work.
The compression filter is now responsible for recording the recv and send messages for both the subchannel call and the server, and adds in ability to record compressed and decompressed messages as well.
The OpenCensus server filter now uses the new ServerCallTracer interface, and so doesn't need to be a filter anymore.
A new ServerCallTracerFilter was added. Ideally, we should be able to move it to the current connected filter, but it is in a bit of an interesting state right now, so I would prefer making those changes in a separate PR with Craig's eyes on it.
A new context element GRPC_CONTEXT_CALL_TRACER_ANNOTATION_INTERFACE was created that replaces the old GRPC_CONTEXT_CALL_TRACER, and the new GRPC_CONTEXT_CALL_TRACER is mainly to pass the CallAttemptTracer down the stack. This should go away in the new promise-based world.

This change is

If you're waiting for my input, please feel free to ping me on chat.
It'd be especially nice to get a heads up on reviews on promise based calls right now.


Docker utilities to help build and test on Linux

@swift-ci please smoke test

We should add some documentation in Development.md on how to use these utilities.

@aciidb0mb3r Is this documentation enough?

I have a couple additional bits in my personal bits, so I'm just going to mention these here:

RUN update-alternatives --install /bin/sh sh /bin/bash 100 just to be safe w.r.t. accidental bash-isms that may have snuck in :)
RUN apt-get install -y vim to have a sane editor inside the container
CMD ["/bin/bash"] which avoids having to specify "bash" on when doing "run"

@neonichu I've followed your suggestions. Thanks!

I fixed the comments and removed vim.

@swift-ci please smoke test

@hartbit In future please squash and/or rebase into a series of atomic, logical commits as appropriate.
It's best to avoid having the intermediate states from code review (like "removed vim" or "fixed spelling error from previous commit") end up in master - this helps with bisecting and history readability.

@jakepetroules will make sure to do so. Thanks!


Quick preview doesn't work - com.typesafe.config.ConfigException$Parse

Trying to run the quickstart

Cloned repo

Checked out master

docker-compose up -d

Error in kafkahq container:
 com.typesafe.config.ConfigException$Parse: /app/application.conf: 1: Expecting end of input or a comma, got ':' (if you intended ':' to be part of a key or string value, try enclosing the key or value in double quotes)

Looking at the container:
Env has been set correctly:
/app # env
JAVA_ALPINE_VERSION=8.191.12-r0
HOSTNAME=c5e34470976b
SHLVL=1
HOME=/root
KAFKAHQ_CONFIGURATION=kafkahq:
  connections:
    docker-kafka-server:
      properties:
        bootstrap.servers: "kafka:9092"
      schema-registry: "http://schema-registry:8085"
      connect: "http://connect:8083"

JAVA_VERSION=8u191
TERM=xterm
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/lib/jvm/java-1.8-openjdk/jre/bin:/usr/lib/jvm/java-1.8-openjdk/bin
LANG=C.UTF-8
JAVA_HOME=/usr/lib/jvm/java-1.8-openjdk/jre
PWD=/app

But config file has no line breaks:
/app # cat application.conf
kafkahq: connections: docker-kafka-server: properties: bootstrap.servers: "kafka:9092" schema-registry: "http://schema-registry:8085" connect: "http://connect:8083"

Strangely, if I run this manually the file is written correctly:
/app # echo "${KAFKAHQ_CONFIGURATION}" > /tmp/foo
/app # cat /tmp/foo
kafkahq:
  connections:
    docker-kafka-server:
      properties:
        bootstrap.servers: "kafka:9092"
      schema-registry: "http://schema-registry:8085"
      connect: "http://connect:8083"

Do you have pull the last version ?
It's really strange that you are talking about application.conf and com.typesafe.config.ConfigException
All the configuration is now in application.yaml  and don't rely on typesafe.
Do you have done a docker pull tchiotludo/kafkahq ?
I've the impression that you have a very old local image

Ah, that may well be it
$ docker images|grep kafkahq
tchiotludo/kafkahq                                                         latest              28df7ef7b65d        2 months ago        118MB
tchiotludo/kafkahq                                                         <none>              23d475f33a6e        2 months ago        85MB

Perfect 👍
kafkahq_1          | 2019-04-24 13:54:48,775 INFO  main       i.m.runtime.Micronaut      Startup completed in 14014ms. Server Running: http://622791ce22a8:8080

Maybe docker-compose pull should be the first step in the quickstart?


Not enough advanced examples for glob patterns for folders

There is only one examples for folders and it's basic. Need more advanced examples, such as nested folders.

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

ID: b913056a-d919-94b4-15a9-305ca835ac9b
Version Independent ID: 000c1ff3-85a6-1134-ead4-1d2628a32375
Content: File matching patterns reference - Azure Pipelines
Content Source: docs/pipelines/tasks/file-matching-patterns.md
Service: azure-devops-pipelines
Sub-service: azure-devops-pipelines-tasks
GitHub Login: @steved0x
Microsoft Alias: sdanie

@abatishchev -- Alexander, thank you for your feedback.  Please consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

@steved0x -- Steve, please look into this issue.

Thanks for your feedback! We've moved this issue to our internal tracking system as we transition to a new feedback system.


Added compat with Ducks

Link to the mod: https://steamcommunity.com/sharedfiles/filedetails/?id=2377069366


Resolvers imported from another modules break the type of fields

Strawberry breaks when you try to use a resolver from a different module than where the type is defined in. e.g. the following code does not work:
import strawberry
from my_resolvers import value_resolver

@strawberry.type
class Foo:
    bar: 'Bar' = strawberry.field(resolver=value_resolver)

@strawberry.type
class Bar:
    name: str

It fails with the following error:
TypeError: Foo fields cannot be resolved. Unexpected type 'None'

Is problem solved?

Indeed. #1449 has been merged and this got fixed.


importScripts for libflac in React

Trying to import the script into worker and getting this:
export default () => {
  console.log(location)
  onerror = err => console.log(err)
  importScripts('libflac4-1.3.2.min.js');
  console.log(location)
}

Same for all other script versions
Looks like I am missing something here, could you please help?

Could you provide some more details?
E.g. the details/other fields and stack trace of the error, and the script code of the worker itself?

@russaa Thanks, it's all in React being called like this:
import WebWorker from '../../utils/WebWorker';
import flacworker from '../../utils/flacworker.js';

componentDidMount = async () => {
  this.flacworker = new WebWorker(flacworker);
  this.flacworker.onmessage = event => {
   const { cmd, buf } = event.data;
   console.log(cmd, buf);
  }
}

WebWorker.js
export default class WebWorker {
  constructor(worker) {
    const code = worker.toString();
    const blob = new Blob(['('+code+')()']);
    return new Worker(URL.createObjectURL(blob));
  }
}

flacworker.js (libflac is located in the same folder)
export default () => {
  console.log(location)
  onerror = err => console.log(err)
  importScripts('libflac4-1.3.2.min.js');
  console.log(location)
}

I'm using this construction for loading scripts in other workers without issues
Where can I get the stack trace to debug this kind of things?

so, I am not a react expert, but it seems to me, that this problem is related to the build process you are using:
I tried to create a skeleton project with react and use your code snippets, and the example project that is create by npx create-react-app ... which uses react-scripts for building the app.
And react-scripts uses webpack:
in another project I was able to integrate libflac.js via webpack, but it did require some specific configuration.
Anyway, the default configuration of react-scripts does not seem to be able to handle the inclusion correctly:

for the "single file" variants of libflac.js, e.g. libflac4-1.3.2.js and libflac4-1.3.2.dev.js, I get various build-warnings related to the fact that libflac.js is an UMD library and internally checks, if it is run in node or in a browser (or in a WebWorker), or loaded as an AMD module...
but the webpack configuration of react-scripts does not seem to handle this well, and throws build errors for supposedly undefined variables etc (which really are check via the UMD mechanism) -> to suppress this, you'd need to modify the webpack build configuration
=> could you check/confirm, if/that there are build errors when your app is compiled?
for the other library variants, like the min or webpack versions that have an additional binary file, you'd actually need to configure webpack to include the binary file(s)

Although at some point I would like to, I currently do not have the time to further look into the react build process to find out, what exactly needs to be done to get it to work.
However, in another project, I did use a webpack configuration to accomplish this, but I do not know, if it would work with react.
The basic steps for this are:

use webpack plugin worker-loader for WebWorkers
for variants with binary files, use webpack plugin file-loader to include the "raw" binary files
for suppressing webpack problems due the UMD mechanism, you may need to configure the node setting for webpack (e.g. setting path and fs to false, and crypto to false or "empty")

Thank you for such a thorough answer, will use it on the weekend and report you back!

OK, I had another look, and found a solution for react-scripts when ejecting, i.e. you'd need to run
npm run eject

first (this makes later updates for react etc somewhat more complicated)
after running eject you get the webpack configuration in
config/webpack.config.js

where you'd need to modify the webpack's module.rules array (for me it was somewhere around line 335):
insert somewhere at the beginning of the array the following configuration:
  {
    //this must match the file-name of the worker script:
    test:  /\bflacjs-worker\.js$/i,
    use: {
      loader: 'worker-loader',
      options: { name: 'worker-[name].[hash].js' }
    }
  },
  //OPTIONALLY if .wasm or .min variant: for including the binary file
  {
    test: /\.wasm$/i,
    use: {
      loader: 'file-loader',
      options: {
        //NOTE binary file must be include with its original file name,
        //     so that libfalc lib can find it:
        name: function(file) {
          return path.basename(file)
        }
      }
    },
  },
  {
    test:  /\bflacjs-worker\.js$/i, //this must match the file-name of the worker script
    use: {
      loader: 'worker-loader',
      options: { name: 'worker-[name].[hash].js' }
    }
  },

And then you'd need to change, how the Web Worker is included:
instead of using the helper module ../../utils/WebWorker, directly require the worker script and invoke it as a constructor, e.g.
//import WebWorker from '../../utils/WebWorker';
//import flacworker from '../../utils/flacworker.js';

componentDidMount = async () => {
  //this.flacworker = new WebWorker(flacworker);
  this.flacworker = require('../../utils/flacworker.js')();
  this.flacworker.onmessage = event => {
   const { cmd, buf } = event.data;
   console.log(cmd, buf);
  }
}

Then in the worker script itself, include the libflac.js library with require() instead of importScript()
(also: the webpack configuration above will not compile the worker script any more, so I used "pure javascript", but with some time and effort you could probably figure out, how to pass the worker script to the babel-compiler again):
//flacworker.js
//export default () => {
  self.console.log(location)
  self.onerror = function(err){ console.log(err) };
  //importScripts('libflac4-1.3.2.min.js');

  //for including a "single file variant" of libflac.js, e.g. the standard version:
  var Flac = require('./libflac4-1.3.2.js');

  //or: for including a .wasm variant, e.g standard-wasm:
  require.resolve('./libflac4-1.3.2.wasm.wasm') // <- force webpack to include the binary file
  var Flac = require('./libflac4-1.3.2.wasm.js')

  self.console.log(Flac)
}

... if you install libflac.js e.g.
npm install git+https://github.com/mmig/libflac.js.git

you can use its module ID in the require statements (and don't need to include/copy the files into the source directories):
the compiled javascript files of libflac.js are located in its dist/ directory, so the require-strings from above would change to:
  require.resolve('libflacjs/dist/libflac4-1.3.2.wasm.wasm')
  var Flac = require('libflacjs/dist/libflac4-1.3.2.wasm.js')


Limit the max. amount of players to 10.

Add a limit for the maximum amount of players that can play at the same time. You can't play poker with 11 or more players.

Added via the last push of newUi-Branch


Temporary fix now.sh deployment

For some strange reason sometimes deployment of branch fails (mostly on the first push). I think it's a Vercel issue. This is just the attempt to temporary fix it on our side.
https://vercel.com/oacore/dashboard/qm8ffsra7

Why do you call 'temporary'

IMHO it should be fixed by Vercel guys. It worked before and that directory should exist before calling post-install script I assume. I mean I am not sure why sometimes deploy succeed and sometimes not. Maybe it will be a permanent fix. 😄

Maybe it will be a permanent fix. 😄

That is why I am against 'temporary' fixes. They are almost always 'permanent'


[Feature/Identity] REST APIs for user GET and DELETE

Description
Adds GET and DELETE rest APIs for User operations. Extension of #5990
Issues Resolved
Resolves #5882 #5883
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

seems like the timeout issue here is caused by loadAsync(events, callback) method in ConfigurationLoader where sometimes it just takes too long for request to be completed. I experimented by doubling the wait time to 10s but the flaky behavior persisted.
https://github.com/opensearch-project/OpenSearch/blob/935e65d3b35885231d123d19e08818112c79c6f9/sandbox/modules/identity/src/main/java/org/opensearch/identity/configuration/ConfigurationLoader.java#L128

Codecov Report

Merging #6189 (18b8f5c) into feature/identity (74ee8d2) will decrease coverage by 0.59%.
The diff coverage is 18.62%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@                  Coverage Diff                   @@
##             feature/identity    #6189      +/-   ##
======================================================
- Coverage               71.06%   70.47%   -0.59%
+ Complexity              59484    59110     -374
======================================================
  Files                    4866     4883      +17
  Lines                  283490   283765     +275
  Branches                40800    40810      +10
======================================================
- Hits                   201474   199997    -1477
- Misses                  65805    67322    +1517
- Partials                16211    16446     +235

Impacted Files
Coverage Δ

...pensearch/identity/rest/IdentityRestConstants.java
0.00% <ø> (ø)

...org/opensearch/identity/rest/user/UserService.java
7.62% <0.00%> (-4.54%)
:arrow_down:

.../identity/rest/user/delete/DeleteUserResponse.java
0.00% <0.00%> (ø)

...ntity/rest/user/delete/DeleteUserResponseInfo.java
0.00% <0.00%> (ø)

...tity/rest/user/get/multi/MultiGetUserResponse.java
0.00% <0.00%> (ø)

...identity/rest/user/get/single/GetUserResponse.java
0.00% <0.00%> (ø)

...tity/rest/user/get/single/GetUserResponseInfo.java
0.00% <0.00%> (ø)

...search/identity/rest/user/put/PutUserResponse.java
0.00% <0.00%> (ø)

...arch/identity/rest/user/put/RestPutUserAction.java
100.00% <ø> (ø)

...ntity/rest/user/get/multi/MultiGetUserRequest.java
11.11% <11.11%> (ø)

... and 487 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

I would prefer 2 separate actions and we can modify it in future to get "bulk" users too instead of all by passing comma-separated values


Add support DNS_Prefix naming convention

The dns_prefix must contain between 3 and 45 characters, and can contain only letters, numbers, and hyphens. It must start with a letter and must end with a letter or a number.

Added implementation in V.0.3.1


fix: typos

Explain your changes:

when walk through readme found some typos with spell checker

Explain how you tested your changes:

don't need

Checklist:

[ ] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[x] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them

Closes #0000

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me


Vouching.create now requires the dependency address to be a contract.

Fixes issue [zOS2V-O03] of the Nomic audit (part of #203).

@nventuro failing vouching test, please review

Ha, that's what I get for not running tests after merging for conflicts.


Public dashboards with Solr Search

I would like to create public dashboard with Solr Search, but there is no such option.
These dashboards would be available to any user without logging in, which is quite adequadro to open data.
These users without login certainly could not edit the Dashboard, having only read access.

The discussion is on https://issues.cloudera.org/browse/HUE-3306


Build with -Wunused, -Wall and -Werror

Also, fix what looks like a typo in the is_ipv4_mapped_ipv6 branch of
kretprobe__tcp_v6_connect.

@alban @iaguis please take a look. I'm not sure about the typo (i.e. is &t4 correct here?) and if we should keep a comment regarding IPPROTO_TCP.

This looks correct to me. Does it work on a 4.4 kernel?

Does it work on a 4.4 kernel?

We run the tests on 4.4.45.

LGTM

This needs to be rebased & recompiled to resolve the conflict.

Rebased.


Auditing branch doesnt work with --whodoneit-map

Whatwasit.Repo calls always module.get_whodoneit_name_and_id/1 in insert_version/3.
With --whodoneit-map this doesn't work, since that code is not generated and can not return sensible values anyway.

Added a fix: #19


jumpTo crashes when overscrolling a synced list

The idea is simple: I have a list on the left, a list on the right, I want to move both when scrolling the right list. The issue is that < 0 and > max crashes it because jumpTo can't work with overscroll.

Flutter's jumpTo could consider overscroll (and therefore not crash)
There could be a better method for syncing scroll controllers.

(video is kind of unclear, but after reaching top it freezes and console gets populated with exceptions)
https://user-images.githubusercontent.com/351125/129304616-bb5e556e-5e63-41a1-a0e4-08088ec104b0.mov

console error log
======== Exception caught by gesture ===============================================================
The following StackOverflowError was thrown while handling a gesture:
Stack Overflow

When the exception was thrown, this was the stack:
#0      _GraphViewState.build.<anonymous closure>.<anonymous closure> (package:acp/git_page.dart:672:27)
#1      NotificationListener._dispatch (package:flutter/src/widgets/notification_listener.dart:206:42)
#2      ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
#3      Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
#4      ScrollActivity.dispatchScrollEndNotification (package:flutter/src/widgets/scroll_activity.dart:104:63)
#5      ScrollPosition.beginActivity (package:flutter/src/widgets/scroll_position.dart:875:9)
#6      ScrollPositionWithSingleContext.beginActivity (package:flutter/src/widgets/scroll_position_with_single_context.dart:114:11)
#7      ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:195:5)
#8      ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:173:16)
#9      _GraphViewState.build.<anonymous closure>.<anonymous closure> (package:acp/git_page.dart:675:29)
#10     NotificationListener._dispatch (package:flutter/src/widgets/notification_listener.dart:206:42)
#11     ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
#12     Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
#13     ScrollActivity.dispatchScrollEndNotification (package:flutter/src/widgets/scroll_activity.dart:104:63)
#14     ScrollPosition.beginActivity (package:flutter/src/widgets/scroll_position.dart:875:9)
#15     ScrollPositionWithSingleContext.beginActivity (package:flutter/src/widgets/scroll_position_with_single_context.dart:114:11)
#16     ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:195:5)
#17     ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:173:16)
#18     _GraphViewState.build.<anonymous closure>.<anonymous closure> (package:acp/git_page.dart:675:29)
#19     NotificationListener._dispatch (package:flutter/src/widgets/notification_listener.dart:206:42)
#20     ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
#21     Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
#22     ScrollActivity.dispatchScrollEndNotification (package:flutter/src/widgets/scroll_activity.dart:104:63)
#23     ScrollPosition.beginActivity (package:flutter/src/widgets/scroll_position.dart:875:9)
#24     ScrollPositionWithSingleContext.beginActivity (package:flutter/src/widgets/scroll_position_with_single_context.dart:114:11)
#25     ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:195:5)
#26     ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:173:16)
#27     _GraphViewState.build.<anonymous closure>.<anonymous closure> (package:acp/git_page.dart:675:29)
#28     NotificationListener._dispatch (package:flutter/src/widgets/notification_listener.dart:206:42)
#29     ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
#30     Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
#31     ScrollActivity.dispatchScrollEndNotification (package:flutter/src/widgets/scroll_activity.dart:104:63)
#32     ScrollPosition.beginActivity (package:flutter/src/widgets/scroll_position.dart:875:9)
#33     ScrollPositionWithSingleContext.beginActivity (package:flutter/src/widgets/scroll_position_with_single_context.dart:114:11)
#34     ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:195:5)
#35     ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:173:16)
#36     _GraphViewState.build.<anonymous closure>.<anonymous closure> (package:acp/git_page.dart:675:29)
#37     NotificationListener._dispatch (package:flutter/src/widgets/notification_listener.dart:206:42)
#38     ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
...
...
#5518   Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
#5519   ScrollActivity.dispatchScrollEndNotification (package:flutter/src/widgets/scroll_activity.dart:104:63)
#5520   ScrollPosition.beginActivity (package:flutter/src/widgets/scroll_position.dart:875:9)
#5521   ScrollPositionWithSingleContext.beginActivity (package:flutter/src/widgets/scroll_position_with_single_context.dart:114:11)
#5522   ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:195:5)
#5523   ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:173:16)
#5524   _GraphViewState.build.<anonymous closure>.<anonymous closure> (package:acp/git_page.dart:675:29)
#5525   NotificationListener._dispatch (package:flutter/src/widgets/notification_listener.dart:206:42)
#5526   ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
#5527   Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
#5528   Notification.dispatch (package:flutter/src/widgets/notification_listener.dart:138:13)
#5529   ScrollActivity.dispatchScrollStartNotification (package:flutter/src/widgets/scroll_activity.dart:89:65)
#5530   ScrollPosition.didStartScroll (package:flutter/src/widgets/scroll_position.dart:894:15)
#5531   ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:199:7)
#5532   RawScrollbarState._updateScrollPosition (package:flutter/src/widgets/scrollbar.dart:1404:16)
#5533   RawScrollbarState.handleThumbPressUpdate (package:flutter/src/widgets/scrollbar.dart:1469:5)
#5534   RawScrollbarState._gestures.<anonymous closure>.<anonymous closure> (package:flutter/src/widgets/scrollbar.dart:1594:84)
#5535   LongPressGestureRecognizer._checkLongPressMoveUpdate.<anonymous closure> (package:flutter/src/gestures/long_press.dart:756:85)
#5536   GestureRecognizer.invokeCallback (package:flutter/src/gestures/recognizer.dart:193:24)
#5537   LongPressGestureRecognizer._checkLongPressMoveUpdate (package:flutter/src/gestures/long_press.dart:756:11)
#5538   LongPressGestureRecognizer.handlePrimaryPointer (package:flutter/src/gestures/long_press.dart:652:9)
#5539   PrimaryPointerGestureRecognizer.handleEvent (package:flutter/src/gestures/recognizer.dart:558:9)
#5540   PointerRouter._dispatch (package:flutter/src/gestures/pointer_router.dart:94:12)
#5541   PointerRouter._dispatchEventToRoutes.<anonymous closure> (package:flutter/src/gestures/pointer_router.dart:139:9)
#5542   _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:400:8)
#5543   PointerRouter._dispatchEventToRoutes (package:flutter/src/gestures/pointer_router.dart:137:18)
#5544   PointerRouter.route (package:flutter/src/gestures/pointer_router.dart:123:7)
#5545   GestureBinding.handleEvent (package:flutter/src/gestures/binding.dart:440:19)
#5546   GestureBinding.dispatchEvent (package:flutter/src/gestures/binding.dart:420:22)
#5547   RendererBinding.dispatchEvent (package:flutter/src/rendering/binding.dart:278:11)
#5548   GestureBinding._handlePointerEventImmediately (package:flutter/src/gestures/binding.dart:374:7)
#5549   GestureBinding.handlePointerEvent (package:flutter/src/gestures/binding.dart:338:5)
#5550   GestureBinding._flushPointerEventQueue (package:flutter/src/gestures/binding.dart:296:7)
#5551   GestureBinding._handlePointerDataPacket (package:flutter/src/gestures/binding.dart:279:7)
#5555   _invoke1 (dart:ui/hooks.dart:185:10)
#5556   PlatformDispatcher._dispatchPointerDataPacket (dart:ui/platform_dispatcher.dart:293:7)
#5557   _dispatchPointerDataPacket (dart:ui/hooks.dart:98:31)
(elided 3 frames from dart:async)
Handler: "onLongPressMoveUpdate"
Recognizer: _ThumbPressGestureRecognizer#88f90
  debugOwner: _MaterialScrollbarState#8f208(tickers: tracking 2 tickers)
  state: possible
====================================================================================================

code sample
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(),
      home: const HomePage(),
    );
  }
}

class HomePage extends StatefulWidget {
  const HomePage({Key? key}) : super(key: key);

  @override
  State<HomePage> createState() => _HomePageState();
}

class _HomePageState extends State<HomePage> {
  final ScrollController paintController = ScrollController();
  final ScrollController listController = ScrollController();

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: NotificationListener<ScrollNotification>(
        child: Row(children: [
          Expanded(child: IgnorePointer(child: ListView.builder(
              controller: paintController,
              itemCount: 500,
              itemBuilder: (context, i) {
                return Text("Don't scroll $i");
              }))),
          Expanded(child: ListView.builder(
              controller: listController,
              itemCount: 500,
              itemBuilder: (context, i) {
                return Text("Scroll me $i");
              })),
        ]),
        onNotification: (ScrollNotification scrollInfo) {
          // this will set paintController's offset the same as controller2's
          // listController.
          paintController.jumpTo(listController.offset);
          return true;
        },
      ),
    );
  }
}

[✓] Flutter (Channel dev, 2.5.0-5.0.pre, on macOS 11.4 20F71 darwin-x64, locale en-BR)
    • Flutter version 2.5.0-5.0.pre at /usr/local/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 0f465e5b2a (8 days ago), 2021-08-04 18:59:50 -0400
    • Engine revision a0d89b1a54
    • Dart version 2.14.0 (build 2.14.0-377.0.dev)

Verified this on latest stable and master and see the same behavior with below crash log.

console error log
======== Exception caught by animation library =====================================================
The following StackOverflowError was thrown while notifying listeners for AnimationController:
Stack Overflow

When the exception was thrown, this was the stack:
#0      ScrollMetrics.copyWith (package:flutter/src/widgets/scroll_metrics.dart:43:3)
#1      ScrollPosition.didEndScroll (package:flutter/src/widgets/scroll_position.dart:906:45)
#2      ScrollPosition.beginActivity (package:flutter/src/widgets/scroll_position.dart:875:9)
#3      ScrollPositionWithSingleContext.beginActivity (package:flutter/src/widgets/scroll_position_with_single_context.dart:114:11)
#4      ScrollPositionWithSingleContext.goIdle (package:flutter/src/widgets/scroll_position_with_single_context.dart:129:5)
#5      ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:195:5)
#6      ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:172:16)
#7      _HomePageState.build.<anonymous closure> (package:bug_test/main.dart:54:27)
#8      ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
#9      Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
#10     Notification.dispatch (package:flutter/src/widgets/notification_listener.dart:138:13)
#11     ScrollActivity.dispatchScrollEndNotification (package:flutter/src/widgets/scroll_activity.dart:104:63)
#12     ScrollPosition.didEndScroll (package:flutter/src/widgets/scroll_position.dart:906:15)
#13     ScrollPosition.beginActivity (package:flutter/src/widgets/scroll_position.dart:875:9)
#14     ScrollPositionWithSingleContext.beginActivity (package:flutter/src/widgets/scroll_position_with_single_context.dart:114:11)
#15     ScrollPositionWithSingleContext.goIdle (package:flutter/src/widgets/scroll_position_with_single_context.dart:129:5)
#16     ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:195:5)
#17     ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:172:16)
#18     _HomePageState.build.<anonymous closure> (package:bug_test/main.dart:54:27)
#19     ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
#20     Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
#21     Notification.dispatch (package:flutter/src/widgets/notification_listener.dart:138:13)
#22     ScrollActivity.dispatchScrollEndNotification (package:flutter/src/widgets/scroll_activity.dart:104:63)
#23     ScrollPosition.didEndScroll (package:flutter/src/widgets/scroll_position.dart:906:15)
#24     ScrollPosition.beginActivity (package:flutter/src/widgets/scroll_position.dart:875:9)
#25     ScrollPositionWithSingleContext.beginActivity (package:flutter/src/widgets/scroll_position_with_single_context.dart:114:11)
#26     ScrollPositionWithSingleContext.goIdle (package:flutter/src/widgets/scroll_position_with_single_context.dart:129:5)
#27     ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:195:5)
#28     ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:172:16)
#29     _HomePageState.build.<anonymous closure> (package:bug_test/main.dart:54:27)
#30     ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
#31     Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
#32     Notification.dispatch (package:flutter/src/widgets/notification_listener.dart:138:13)
#33     ScrollActivity.dispatchScrollEndNotification (package:flutter/src/widgets/scroll_activity.dart:104:63)
#34     ScrollPosition.didEndScroll (package:flutter/src/widgets/scroll_position.dart:906:15)
#35     ScrollPosition.beginActivity (package:flutter/src/widgets/scroll_position.dart:875:9)
#36     ScrollPositionWithSingleContext.beginActivity (package:flutter/src/widgets/scroll_position_with_single_context.dart:114:11)
#37     ScrollPositionWithSingleContext.goIdle (package:flutter/src/widgets/scroll_position_with_single_context.dart:129:5)
#38     ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:195:5)
#39     ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:172:16)
#40     _HomePageState.build.<anonymous closure> (package:bug_test/main.dart:54:27)
...
...
#5375   ScrollPosition.beginActivity (package:flutter/src/widgets/scroll_position.dart:886:7)
#5376   ScrollPositionWithSingleContext.beginActivity (package:flutter/src/widgets/scroll_position_with_single_context.dart:114:11)
#5377   ScrollPositionWithSingleContext.goBallistic (package:flutter/src/widgets/scroll_position_with_single_context.dart:146:7)
#5378   ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:203:5)
#5379   ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:172:16)
#5380   _HomePageState.build.<anonymous closure> (package:bug_test/main.dart:54:27)
#5381   ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
#5382   Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
#5383   Notification.dispatch (package:flutter/src/widgets/notification_listener.dart:138:13)
#5384   ScrollActivity.dispatchScrollStartNotification (package:flutter/src/widgets/scroll_activity.dart:89:65)
#5385   ScrollPosition.didStartScroll (package:flutter/src/widgets/scroll_position.dart:894:15)
#5386   ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:199:7)
#5387   ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:172:16)
#5388   _HomePageState.build.<anonymous closure> (package:bug_test/main.dart:54:27)
#5389   ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
#5390   Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
#5391   Notification.dispatch (package:flutter/src/widgets/notification_listener.dart:138:13)
#5392   ScrollActivity.dispatchScrollUpdateNotification (package:flutter/src/widgets/scroll_activity.dart:94:92)
#5393   ScrollPosition.didUpdateScrollPositionBy (package:flutter/src/widgets/scroll_position.dart:899:15)
#5394   ScrollPosition.setPixels (package:flutter/src/widgets/scroll_position.dart:279:9)
#5395   ScrollPositionWithSingleContext.setPixels (package:flutter/src/widgets/scroll_position_with_single_context.dart:82:18)
#5396   BallisticScrollActivity.applyMoveTo (package:flutter/src/widgets/scroll_activity.dart:566:21)
#5397   BallisticScrollActivity._tick (package:flutter/src/widgets/scroll_activity.dart:553:10)
#5398   AnimationLocalListenersMixin.notifyListeners (package:flutter/src/animation/listener_helpers.dart:155:19)
#5399   AnimationController._tick (package:flutter/src/animation/animation_controller.dart:829:5)
#5400   Ticker._tick (package:flutter/src/scheduler/ticker.dart:238:12)
#5401   SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1143:15)
#5402   SchedulerBinding.handleBeginFrame.<anonymous closure> (package:flutter/src/scheduler/binding.dart:1056:11)
#5403   _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:400:8)
#5404   SchedulerBinding.handleBeginFrame (package:flutter/src/scheduler/binding.dart:1054:17)
#5405   SchedulerBinding._handleBeginFrame (package:flutter/src/scheduler/binding.dart:975:5)
#5409   _invoke1 (dart:ui/hooks.dart:185:10)
#5410   PlatformDispatcher._beginFrame (dart:ui/platform_dispatcher.dart:248:5)
#5411   _beginFrame (dart:ui/hooks.dart:116:31)
(elided 3 frames from dart:async)
The AnimationController notifying listeners was: AnimationController#3ed9c(▶ 7661.369; for BallisticScrollActivity)
====================================================================================================

======== Exception caught by animation library =====================================================
The following StackOverflowError was thrown while notifying listeners for AnimationController:
Stack Overflow

When the exception was thrown, this was the stack:
#0      new _GrowableList.of (dart:core-patch/growable_array.dart:139:3)
#1      new List.of (dart:core-patch/array_patch.dart:50:28)
#2      new List.from (dart:core-patch/array_patch.dart:36:19)
#3      ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:171:43)
#4      _HomePageState.build.<anonymous closure> (package:bug_test/main.dart:54:27)
#5      ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
#6      Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
#7      Notification.dispatch (package:flutter/src/widgets/notification_listener.dart:138:13)
#8      ScrollActivity.dispatchScrollEndNotification (package:flutter/src/widgets/scroll_activity.dart:104:63)
#9      ScrollPosition.didEndScroll (package:flutter/src/widgets/scroll_position.dart:906:15)
#10     ScrollPosition.beginActivity (package:flutter/src/widgets/scroll_position.dart:875:9)
#11     ScrollPositionWithSingleContext.beginActivity (package:flutter/src/widgets/scroll_position_with_single_context.dart:114:11)
#12     ScrollPositionWithSingleContext.goIdle (package:flutter/src/widgets/scroll_position_with_single_context.dart:129:5)
#13     ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:195:5)
#14     ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:172:16)
#15     _HomePageState.build.<anonymous closure> (package:bug_test/main.dart:54:27)
#16     ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
#17     Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
#18     Notification.dispatch (package:flutter/src/widgets/notification_listener.dart:138:13)
#19     ScrollActivity.dispatchScrollEndNotification (package:flutter/src/widgets/scroll_activity.dart:104:63)
#20     ScrollPosition.didEndScroll (package:flutter/src/widgets/scroll_position.dart:906:15)
#21     ScrollPosition.beginActivity (package:flutter/src/widgets/scroll_position.dart:875:9)
#22     ScrollPositionWithSingleContext.beginActivity (package:flutter/src/widgets/scroll_position_with_single_context.dart:114:11)
#23     ScrollPositionWithSingleContext.goIdle (package:flutter/src/widgets/scroll_position_with_single_context.dart:129:5)
#24     ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:195:5)
#25     ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:172:16)
#26     _HomePageState.build.<anonymous closure> (package:bug_test/main.dart:54:27)
#27     ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
#28     Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
#29     Notification.dispatch (package:flutter/src/widgets/notification_listener.dart:138:13)
#30     ScrollActivity.dispatchScrollEndNotification (package:flutter/src/widgets/scroll_activity.dart:104:63)
#31     ScrollPosition.didEndScroll (package:flutter/src/widgets/scroll_position.dart:906:15)
#32     ScrollPosition.beginActivity (package:flutter/src/widgets/scroll_position.dart:875:9)
#33     ScrollPositionWithSingleContext.beginActivity (package:flutter/src/widgets/scroll_position_with_single_context.dart:114:11)
#34     ScrollPositionWithSingleContext.goIdle (package:flutter/src/widgets/scroll_position_with_single_context.dart:129:5)
#35     ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:195:5)
#36     ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:172:16)
#37     _HomePageState.build.<anonymous closure> (package:bug_test/main.dart:54:27)
#38     ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
#39     Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
...
...
#5374   ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:195:5)
#5375   ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:172:16)
#5376   _HomePageState.build.<anonymous closure> (package:bug_test/main.dart:54:27)
#5377   ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
#5378   Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
#5379   Notification.dispatch (package:flutter/src/widgets/notification_listener.dart:138:13)
#5380   ScrollActivity.dispatchScrollEndNotification (package:flutter/src/widgets/scroll_activity.dart:104:63)
#5381   ScrollPosition.didEndScroll (package:flutter/src/widgets/scroll_position.dart:906:15)
#5382   ScrollPosition.beginActivity (package:flutter/src/widgets/scroll_position.dart:875:9)
#5383   ScrollPositionWithSingleContext.beginActivity (package:flutter/src/widgets/scroll_position_with_single_context.dart:114:11)
#5384   ScrollPositionWithSingleContext.goIdle (package:flutter/src/widgets/scroll_position_with_single_context.dart:129:5)
#5385   ScrollPositionWithSingleContext.jumpTo (package:flutter/src/widgets/scroll_position_with_single_context.dart:195:5)
#5386   ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:172:16)
#5387   _HomePageState.build.<anonymous closure> (package:bug_test/main.dart:54:27)
#5388   ViewportNotificationMixin.visitAncestor (package:flutter/src/widgets/scroll_notification.dart:31:18)
#5389   Element.visitAncestorElements (package:flutter/src/widgets/framework.dart:4133:39)
#5390   Notification.dispatch (package:flutter/src/widgets/notification_listener.dart:138:13)
#5391   ScrollActivity.dispatchScrollUpdateNotification (package:flutter/src/widgets/scroll_activity.dart:94:92)
#5392   ScrollPosition.didUpdateScrollPositionBy (package:flutter/src/widgets/scroll_position.dart:899:15)
#5393   ScrollPosition.setPixels (package:flutter/src/widgets/scroll_position.dart:279:9)
#5394   ScrollPositionWithSingleContext.setPixels (package:flutter/src/widgets/scroll_position_with_single_context.dart:82:18)
#5395   BallisticScrollActivity.applyMoveTo (package:flutter/src/widgets/scroll_activity.dart:566:21)
#5396   BallisticScrollActivity._tick (package:flutter/src/widgets/scroll_activity.dart:553:10)
#5397   AnimationLocalListenersMixin.notifyListeners (package:flutter/src/animation/listener_helpers.dart:155:19)
#5398   AnimationController._tick (package:flutter/src/animation/animation_controller.dart:829:5)
#5399   Ticker._tick (package:flutter/src/scheduler/ticker.dart:238:12)
#5400   SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1143:15)
#5401   SchedulerBinding.handleBeginFrame.<anonymous closure> (package:flutter/src/scheduler/binding.dart:1056:11)
#5402   _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:400:8)
#5403   SchedulerBinding.handleBeginFrame (package:flutter/src/scheduler/binding.dart:1054:17)
#5404   SchedulerBinding._handleBeginFrame (package:flutter/src/scheduler/binding.dart:975:5)
#5408   _invoke1 (dart:ui/hooks.dart:185:10)
#5409   PlatformDispatcher._beginFrame (dart:ui/platform_dispatcher.dart:248:5)
#5410   _beginFrame (dart:ui/hooks.dart:116:31)
(elided 3 frames from dart:async)
The AnimationController notifying listeners was: AnimationController#ef64c(▶ 7659.225; for BallisticScrollActivity)
====================================================================================================

 stable and master flutter doctor -v
[✓] Flutter (Channel stable, 2.2.3, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-GB)
    • Flutter version 2.2.3 at /Users/dhs/documents/fluttersdk/flutter
    • Framework revision f4abaa0735 (4 days ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Users/dhs/Library/Android/sdk
    • Java binary at: /Users/dhs/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/202.7486908/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/dhs/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/202.7486908/Android
      Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.57.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (4 available)
    • SM G975F (mobile) • RZ8M802WY0X • android-arm64 • Android 10 (API 29)
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                               •
      web-javascript • Google Chrome 91.0.4472.114

• No issues found!

[✓] Flutter (Channel master, 2.5.0-7.0.pre.65, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-GB)
    • Flutter version 2.5.0-7.0.pre.65 at
      /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4bd8b288bb (11 hours ago), 2021-08-12 18:02:02 -0700
    • Engine revision 670a681c1d
    • Dart version 2.15.0 (build 2.15.0-6.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Users/dhs/Library/Android/sdk
    • Java binary at: /Users/dhs/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/202.7486908/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5.1, Build version 12E507
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/dhs/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/202.7486908/Android
      Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/dhs/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/202.7486908/Android
      Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.57.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (4 available)
    • SM G975F (mobile) • RZ8M802WY0X • android-arm64 • Android 10 (API 29)
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                               •
      web-javascript • Google Chrome 91.0.4472.114

CC @Piinks

Flutter's jumpTo could consider overscroll (and therefore not crash)

I think this is WAI, it is documented that jumpTo cannot overscroll, from the documentation:
/// No overscroll notifications can be generated by this method.

There could be a better method for syncing scroll controllers.

Have you seen this package? It may be what you are looking for: https://pub.dev/packages/linked_scroll_controller

That should work. I didn't see it was an official package. Thanks!


added --yeah as an alternative arg to -y and --yes; updated README.md

Love this little app -- I use it a little too often...


Fixes to the GLTF export with baking and null checks.

Fixes: https://github.com/godotengine/godot/issues/72699

Thanks!


add timeout to httpReadSeeker

Accommodates for unreachable host which will trap image pull forever.
When user try to pull image from unreachable registry which might be responding extremely slow, containerd will be stuck in io.Copy forever and all further pull requests to the same digest will be blocked by duplicationSuppressor mutex forever which will lead to huge mem consumption of containerd.
Signed-off-by: cardy.tang<EMAIL_ADDRESS>

Needs can be met by #00d102da , Closed.


[registrator]

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/160
After the above pull request is merged, it is recommended that you create
a tag on this repository for the registered package version:
git tag -a v0.1.0 -m "<description of version>" 9f6c23aed55c1125514e96100beee7774134d711
git push origin v0.1.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/1414
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.2 -m "<description of version>" 3b7cd89617f7ca079ff62ad161997e771d462adf
git push origin v0.2.2

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/3146
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.4 -m "<description of version>" e027f79f01a713d8c89715786696c63197eece29
git push origin v0.2.4

Also, note the warning: Version 0.2.4 skips over 0.2.3
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/3147
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.3 -m "<description of version>" e3f579b5441a18e27d02df4418265df4fbe37527
git push origin v0.2.3


[WFLY-12896] EE Managed Executors Hung Task Termination feature + EE model bump to 6.0

Issue: https://issues.redhat.com/browse/WFLY-12896

Thanks, @emmartins !

Thanks, @emmartins !


gql not parsed when filename contains [brackets] used in Next.js dynamic routing

Describe the bug
gql tags are not parsed by graphql-code-generator when they are located in files or directories that use Next.js's dynamic filesystem routing conventions such as pages/[directory]/[mypage].tsx (basically path contains brackets)
To Reproduce

create a file src/pages/[directory]/[mypage].tsx
add a simple query such as

gql`query GetDogs { dogs }`

run graphql-code-generator

Here is a CodeSandbox reproduction:

My GraphQL schema:
type Query {
  dogs: [String!]!
}

My codegen.yml config file:
schema: src/type-defs.ts
generates:
  src/hooks-generated.tsx:
    documents:
      - src/**/*.ts
      - src/**/*.tsx
    plugins:
      - typescript
      - typescript-operations
      - typescript-react-apollo
    config:
      withComponent: false
      withHOC: false
      withHooks: true

Expected behavior
src/hooks-generated.tsx should contain types for the GetDogs query if it was in a path containing brackets.
I believe this is the same issue that Next.js encountered with Prettier not being able to handle paths with brackets. They ended up having to use shell-quote to properly escape the paths, something about it interfering with globbing maybe?
Here is a file showing how Next.js fixed it.
Environment:

OS: MacOS Catalina
@graphql-codegen/...: 1.9.1
NodeJS: 13.2.0

@msheakoski where does gql coming from when you use next.js?
We are using graphql-tag-pluck which knows how to pluck operations, but it's not supporting all use cases by default (you can change it with pluckConfig).

I am importing gql from graphql-tag. My current workflow each time I need to run graphql-code-generator is to rename the dirs/files to remove brackets, run graphql-code-generator, and rename them back, adding the brackets again.

Seeing this too, looks like a regression as of the 1.9.x branch.  We're using graphql-tag, and the codegen on 1.9.1 (and 1.9.0) removes all of our queries in files with brackets in their name, e.g. [tag].tsx.

Here is a CodeSandbox reproduction of the issue:

After running yarn graphql-codegen, the only hook that appears in hooks-generated.tsx is useThisWorks based on the query located in pages/works/it-works.tsx.
useThisDoesNotWork based on the query located in pages/does-not-work/[name].tsx does not appear in hooks-generated.tsx

Can also confirm this happens with my Next.js project when query is in /[name].tsx files!

@dotansimha I am not 100% positive since I am not familiar with the internals, but I think maybe it is this commit ardatan/graphql-toolkit@6d99f92 where glob was switched to globby. affecting file-scanner.ts

I just found more evidence to back up my theory: Globby skips folder with symbols in it's name

@ardatan Adding you to the issue since you made the change and have a better understanding of the codebase. Do you think this is likely the cause?

For anyone that needs a quick fix, graphql-code-generator 1.8.3 works with Next.js apps but 1.9.0+ currently does not.

@ardatan can you please take a look? I think it's something we should solve in graphql-toolkit

@dotansimha I spent a lot of time for that but even switching to glob didn't work. It looks like a problem related to micromatch which is used by fast-glob(dependency of globby).
https://github.com/ardatan/graphql-toolkit/issues/370

Available in v1.10.0.

I think this issue is occurring again in 2023? Currently using:
"@graphql-codegen/cli": "^3.0.0"
"@graphql-codegen/client-preset": "^2.0.0"

seems like Its again broken

This time is pages/(directory)/page.tsx
https://nextjs.org/docs/app/building-your-application/routing/route-groups

This time is pages/(directory)/page.tsx https://nextjs.org/docs/app/building-your-application/routing/route-groups

I have the same problem :(


Orderbook enhancements

The Chore
Changes to the order book to improve experience
Tasks

[ ] Never show price levels with 0 orders
[ ] Remove scrolling, so we can ensure the mid is always centered
[ ] Improve aggregation to allow for more and less precision

Additional details / background info

General comments:

important that at a glance you can see the shape of the depth by looking at the overall shape of the bars, i.e.

not excessive spacing between bars / rows
no grid lines
text colour / contrast isn’t overpowering

needs to show the mid price in the centre
ideally should be responsive - if narrow only show price and volume at price, if wider add cumulative volume
No separate bid vol and ask vol
No column headers

Cryptowatch (screenshot below) do it great. Ask @MM0819 for other examples of where it is done well.


Setup Codecov

close #33

Before merging this, secret CODECOV_TOKEN must be added.

CI failure is due to missing dependencies, so adding the following two lines should fix it.
https://github.com/openrr/grid_map/blob/c0ce4112cd20ae04ab9e506470d6c8e5acc47f41/.github/workflows/rust.yml#L23-L24

secret CODECOV_TOKEN must be added.

Indeed. Added the secret.


Lutron. Bugfix callback registration.

Description:

Simplify stuff
Move callback subscription to EVENT_HOMEASSISTANT_START

Related issue (if applicable): fixes #6739
CC #7019

Sorry for the lack of updates folks. Been busy at work and now on vacation.
I'll try to get back to this when I'm back if you don't take care of it
beforehand. The pylutron library itself is not guaranteed to be async safe.
On Apr 11, 2017 11:57 AM, "Paulus Schoutsen"<EMAIL_ADDRESS>wrote:

@balloob commented on this pull request.
In homeassistant/components/lutron.py
https://github.com/home-assistant/home-assistant/pull/7042#discussion_r110942487
:

     """Initialize the device."""

     self._lutron_device = lutron_device
     self._controller = controller
     self._area_name = area_name

   self.hass = hass

   self.object_id = '{} {}'.format(area_name, lutron_device.name)

@asyncio.coroutine
def async_add_to_hass(self):

   """Register callbacks."""
   self._controller.subscribe(self._lutron_device, self._update_callback)

Is this async friendly?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/7042#pullrequestreview-32150459,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABcEMVV4OwJYC0Sp992hIsM__nKWelDaks5ru6MBgaJpZM4M53FJ
.

async_added_to_hass is only for core stuff. So we register a listener on start event for handling callback right way.


Listing default view

Change default Listing Template to include only Text and renamed the old default Template to Summary Template. I think this makes more sense as per default most content types dont even have the image behavior necessary to show something in the current default listing template.

@sneridagh I guess it is time for Volto 11.x :)


Advanced Ctrl+C System

Description of the new feature / enhancement
A tool of multiple copy and paste, where what is copied in sequence is pasted in the respective sequence.
Example:

Let's say I wanted to copy two informations in sequence:
Apple (ctrl+c 01)
Pineapple (ctrl+c 02)

Then, I want each ctrl+v to paste the information into the corresponding copied sequence:
Apple (ctrl+v from ctrl+c 01)
Pineapple (ctrl+v from ctrl+c 02)

In the settings, the user could set the amount of ctrl+c he wants the tool to keep in memory. This tool would work with text, images and files.
In the manager of these ctrl+v (something similar to win+v) will have the options to set a shortcut key for a specific copied information. When this shortcut is registered, this information is never erased from the history except at machine shutdown or restart.
Scenario when this would be used?
Examples of use:

I work with 3D Max. Sometimes, I need to copy several numbers of different inputs to the inputs of other objects so that they have some equal values. With that, I could, for example, copy the X axis value, then the Y axis value, select the other object and in the first ctrl+v paste the X axis value that was the first copied information, then paste the axis value Y which was the second copied information.

A programmer could copy two variables that he is using all the time into specific code. It copies the first information, copies the second information, opens the history settings of ctrl+v, sets the first copy as (ctrl+v+1) and the second copy as (ctrl+v+2) for example.

Let's say you need to pass files from your local computer to the AWS server. However, there are multiple files in different folders that need to be pasted into separate folders on AWS. The first ctrl+c will copy the first file from a folder. The second ctrl+c, the second file from a different folder. I go to the corresponding folder of the first file on AWS and paste with ctrl+v. Then access another AWS folder and paste the second copied file respectively with the second ctrl+v.

Supporting information
No response

Duplicate of #1758

Thanks for your suggestion! This issue is a duplicate.
I'm linking this issue to #1758 to centralize the discussion thread, please go to that thread for discussion. You can add your details there.
Thanks for your help to make PowerToys a better piece of software!

Thanks for your suggestion! This issue is a duplicate. I'm linking this issue to #1758 to centralize the discussion thread, please go to that thread for discussion. You can add your details there.
Thanks for your help to make PowerToys a better piece of software!

Not quite the same thing as in thread #1758. I saw this thread before writing mine, so I just added this person's idea to mine, but my main idea is the ctrl+c and ctrl+v in respective sequences.


Remove nav-link last-child padding

This snippet added an edge to edge last nav-link to container if no header widget is active. I'm not sure if we should keep this or following more the Bootstrap way and delete it.

I always just keep the padding. It helps with the click area as it's on the link, and when styling a background for it.


nltk.tokenize.casual.TweetTokenizer: Add support to tokenize emoji flag sequences

nltk.tokenize.casual.TweetTokenizer: Add support to tokenize emoji flag sequences

TweetTokenizer currently splits emoji flags into individual tokens of enclosed letters, e.g. 🇨🇦 -> '🇨 ', '🇦 '
This patch keeps emoji flag sequences intact
Without this PR:

nltk.tokenize.casual.TweetTokenizer().tokenize(text='Hi 🇨🇦, 😍!!')
['Hi', '🇨', '🇦', ',', '😍', '!', '!']

With this PR:

nltk.tokenize.casual.TweetTokenizer().tokenize(text='Hi 🇨🇦, 😍!!')
['Hi', '🇨🇦', ',', '😍', '!', '!']

See https://github.com/nltk/nltk/issues/2578#issuecomment-1112066105 for some related discussion. In short, I am in favour of adding this behaviour, but I would like to start a discussion on whether it would be wise to include an option to turn it off in TweetTokenizer.__init__.
After all, as you are aware, flags are made up of regional indicator symbols. These symbols are also frequently used outside of the context of flags, like to spell out words: 🇦 🇵 🇵 🇱 🇪. However, this is commonly done with spaces between the tokens, as otherwise that spelling of "APPLE" would have had a Polish flag in the middle. In short, it may not be an issue.
Beyond that discussion, would you be able to write a few tests to back up that your implementation works as intended? For example in here: https://github.com/nltk/nltk/blob/develop/nltk/test/unit/test_tokenize.py
Also, I'm uncertain why the CI is failing. It seems like a third party download of a file used in one of the tests has failed:

curl: (28) Failed to connect to www.cs.unm.edu port 443: Connection timed out

It's unrelated to your PR, though, so no stress.

would you be able to write a few tests to back up that your implementation works as intended? For example in here: https://github.com/nltk/nltk/blob/develop/nltk/test/unit/test_tokenize.py

Yes, I'll modify that file as part of this PR.
Given your comments, what do you think of the decision use a regex that encodes all pairs of enclosed letters as tokens? Under this behavior, your example is tokenized as follow. Is this "correct"? Or should this repo have a record of all ISO country code letter pairs and treat these separately in a much more complicated regex? My preference is to avoid this.

nltk.tokenize.casual.TweetTokenizer().tokenize('🇦🇵🇵🇱🇪')
['🇦🇵', '🇵🇱', '🇪']

I also prefer your current implementation, i.e. any two directly adjacent regional indicator symbols. This is also more future-proof. The behaviour from your little snippet seems like the expected output as well. 👍

I also prefer your current implementation, i.e. any two directly adjacent regional indicator symbols. This is also more future-proof. The behaviour from your little snippet seems like the expected output as well. 👍

Great, implemented with a test in test_tokenize.py.

I've expanded on your test case a little bit, and fixed a merge conflict on the AUTHORS.md file. Should be all set now!
Thank you for this work!


Add 1/2 split of VOC, update README

Add 1/2 split of VOC, update README

@googlebot I signed it!


added support complex op

TF definition https://www.tensorflow.org/api_docs/cc/class/tensorflow/ops/complex

This change is

Can you make sure the model in the email works now with these changes? Thanks Ping!!


added support for amazon linux 2. rev'd spec tests for amazonlinux 20…

…18.03. updated test kitchen to support amazon linux 2.
Signed-off-by: Heusinkveld, Brian<EMAIL_ADDRESS>Description
This change adds support for Amazon Linux 2.  This change also updated spec tests to use a more recent version of amazon linux (2018.03).  chefspec and test kitchen updated to include Amazon Linux 2.
Issues Resolved
Check List

[X] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[X] New functionality includes testing.
[X] New functionality has been documented in the README if applicable
[X] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

@bheusinkveld sorry I missed this PR when you opened it. It's great. I merged it in and I'll get it pushed up


functions-infrastructure-as-code.md: missing DOCKER_REGISTRY_SERVER_* settings leads to HTTP/500

Add more information about unexpected and undocumented behaviour if DOCKER_REGISTRY_SERVER_* settings are missing for a private repo reference.

It took me more than one hour to understand this 500 error. Even if the must-have is documented, the behavior when it is not followed is not clear.

@ggailey777
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks @clook, but I'm going to move your info a different place (and fix the link right there that would have been helpful if it was working. I'll grab your commit so you get credit for helping out 😄


[master] Upgrade to latest dependencies

Produced via:
./hack/update-deps.sh --upgrade
./hack/update-codegen.sh

/cc knative-sandbox/networking-wg-leads
/assign knative-sandbox/networking-wg-leads

/lgtm
/approve

/ok-to-test


FCF Verification

has anyone tried using FCF on combined fleet?
does it work? xD
is ship box colored as gray when two ships retreat?
any bugs on implementation?

I will probably end up using one at some point during this event, if I do do you want me to record my data?

ah if you can just see the ship boxes being marked that will be all. The API was implemented before the event (using data from E.O.) but wasn't actually tested here

This just became number 1 priority.
My friend just had his starter Fubuki K2 sunk because of the lack of FCF indicator

So is the code working to detect it and there is no icon or are both failing?

If he is using KC3Kai, he can check the morale to see if the ship is under FCF or not. After using FCF, the ship morale drops dramatically to 15 (+ mins spent on sortie). That's one way to check for FCF.
Sent from my iPhone

On 14 Aug 2015, at 19:11, Jet Rico<EMAIL_ADDRESS>wrote:
This just became number 1 priority.
My friend just had his starter Fubuki K2 sunk because of the lack of FCF indicator
―
Reply to this email directly or view it on GitHub.

yea I also told him here's still this allowance time between the battle result and the next node formation selection. but its done :sob:

Can kc3 kai show an icon if first fleet flagship equipped with FCF, and also show a bar that display is there any healthy DD left for the eligible use of FCF?

I believe we can generate the marker by determining the drop of morale value, can't we?
as long as the ships fulfill these:

drastic morale drop to 15 or below
happened to two ships in a single node
one of the ships is DD from the second fleet
the other ship has status of "Heavily Damaged"
the flagship of main fleet is using FCF
we can immediately mark this two ships as "being sent home"

also, @c933103's suggestion is quite necessary. showing an indicator whether FCF is being equipped is vital to the combined fleet, especially there is no equipment details in the combined fleet screen.

hm I think it's more of like, marking those this already sent back home as gray, same with in-game, with the HP bar not anymore red, and the box having a faint gray background too
in terms of, if FCF is equipped, I think they can just manually check back on fleet 1 if it's equipped. no need for us to go to the extent of adding indicators for eligibility

Currently, when you use this it marks them grey when they retreat but they don't stay grey after you leave the results screen.

Fixed bug mentioned in @NicolaosGreene 's comment in #646


Remove log peer dependency

Currently log is a peer dependency to provide access to the logging macros (such as info!() and debug!()).
We should find a way to re-export the macros from log through this crate. This is possibly blocked on Rust 2018.
From Discord:

i think in rust 2018 you can pub use macros::your_macro

also from discord :D


Feedback: Transaction Layer

Page: https://cockroachlabs.com/docs/v23.2/architecture/transaction-layer.html
What is the reason for your feedback?
[x] Missing the information I need
[ ] Too complicated
[ ] Out of date
[ ] Something is broken
[ ] Other
Additional details
Unclear from the docs if the timestamp cache is raft replicated. I assume not. Curious what happens to the cache across lease transfers. How does CRDB serialize operations to the new leaseholder to execute after the reads to the old leaseholder?

After looking around for a bit, I find that DB raises this error https://www.cockroachlabs.com/docs/v23.2/transaction-retry-error-reference#abort_reason_new_lease_prevents_txn


unable to download youtube live stream

This is probably a duplicate of some past bug, but I didn't see anything exactly like it.
This is a live stream (don't know if those eventually get converted to static videos).
$ youtube-dl -F 'https://www.youtube.com/watch?v=pyUCR-Sfenc'
[youtube] pyUCR-Sfenc: Downloading webpage
[youtube] pyUCR-Sfenc: Downloading video info webpage
[youtube] pyUCR-Sfenc: Extracting video information
[youtube] pyUCR-Sfenc: Downloading formats manifest
[youtube] pyUCR-Sfenc: Downloading DASH manifest
[info] Available formats for pyUCR-Sfenc:
format code  extension  resolution note
140          m4a        audio only DASH audio  144k , m4a_dash container, aac  @128k (48000Hz)
141          m4a        audio only DASH audio  272k , m4a_dash container, aac  @256k (48000Hz)
160          mp4        256x144    DASH video  124k , 15fps, video only
133          mp4        426x240    DASH video  258k , 30fps, video only
134          mp4        640x360    DASH video  616k , 30fps, video only
135          mp4        854x480    DASH video 1116k , 30fps, video only
136          mp4        1280x720   DASH video 2216k , 30fps, video only
151          mp4        72p        HLS
132          mp4        240p       HLS
92           mp4        240p       HLS
93           mp4        360p       HLS
94           mp4        480p       HLS
95           mp4        720p       HLS  (best)
$ youtube-dl -v 'https://www.youtube.com/watch?v=pyUCR-Sfenc'
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['--restrict-filenames', '-o', '%(title)s-%(id)s-%(uploader)s.%(ext)s', '-w', '-v', 'https://www.youtube.com/watch?v=pyUCR-Sfenc']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.05.15
[debug] Python version 3.4.1 -<EMAIL_ADDRESS>[debug] exe versions: ffmpeg 2.2.14, ffprobe 2.2.14, rtmpdump 2.4
[debug] Proxy map: {}
[youtube] pyUCR-Sfenc: Downloading webpage
[youtube] pyUCR-Sfenc: Downloading video info webpage
[youtube] pyUCR-Sfenc: Extracting video information
[youtube] pyUCR-Sfenc: Downloading formats manifest
[youtube] pyUCR-Sfenc: Downloading DASH manifest
[debug] Invoking downloader on 'https://r6---sn-uo1-53as.googlevideo.com/videoplayback/id/pyUCR-Sfenc.2/itag/136/source/yt_live_broadcast/requiressl/yes/pmbypass/yes/playlist_type/DVR/gcr/us/ratebypass/yes/cmbypass/yes/mime/video%2Fmp4/live/1/gir/yes/fexp/920935,937412,9408142,9408583,9408707,9408710,9408768,9408787,9408855,9408941,9412773,9413053,9413138,945137,947602,948124,952612,952637,952642/key/cms1/upn/VDR1MV18GOQ/sver/3/signature/145057F75F773A31F2E23DF489D397B2E94AC592.3ABD3EB620D3DB985D5138C7466FBF9F5CCEA982/ip/<IP_ADDRESS>/ipbits/0/expire/1432094425/sparams/cmbypass,expire,gcr,gir,id,ip,ipbits,itag,live,mime,mm,mn,ms,mv,pl,playlist_type,pmbypass,ratebypass,requiressl,source/mm/32/mn/sn-uo1-53as/ms/lv/mt/1432072733/mv/u/pl/21'
ERROR: unable to download video data: HTTP Error 400: Bad Request
Traceback (most recent call last):
File "/usr/lib64/python3.4/site-packages/youtube_dl/YoutubeDL.py", line 1411, in process_info
partial_success = dl(fname, new_info)
File "/usr/lib64/python3.4/site-packages/youtube_dl/YoutubeDL.py", line 1359, in dl
return fd.download(name, info)
File "/usr/lib64/python3.4/site-packages/youtube_dl/downloader/common.py", line 342, in download
return self.real_download(filename, info_dict)
File "/usr/lib64/python3.4/site-packages/youtube_dl/downloader/http.py", line 59, in real_download
data = self.ydl.urlopen(request)
File "/usr/lib64/python3.4/site-packages/youtube_dl/YoutubeDL.py", line 1710, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/usr/lib64/python3.4/urllib/request.py", line 461, in open
response = meth(req, response)
File "/usr/lib64/python3.4/urllib/request.py", line 571, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib64/python3.4/urllib/request.py", line 499, in error
return self._call_chain(*args)
File "/usr/lib64/python3.4/urllib/request.py", line 433, in _call_chain
result = func(*args)
File "/usr/lib64/python3.4/urllib/request.py", line 579, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 400: Bad Request

Looks like it's a duplicate of  https://github.com/rg3/youtube-dl/issues/5703 and https://github.com/rg3/youtube-dl/issues/5545

I have never seen the 92-95 formats (or the HSL identifier) before.
Unlike 5703, I was unable to get any of the formats while the stream was live.