chore(deps): update config-no-service (major)

This PR contains the following updates:

Package
Type
Update
Change

@tanstack/react-query (source)
dependencies
major
4.32.6 -> 5.0.5

Microsoft.AspNetCore.TestHost (source)
nuget
major
6.0.22 -> 7.0.13

actions/checkout
action
major
v3 -> v4

ava (source)
dependencies
major
4.3.0 -> 5.3.1

certifi

major
==2022.12.7 -> ==2023.7.22

cookies-next
dependencies
major
2.1.2 -> 4.0.0

cypress
devDependencies
major
10.4.0 -> 13.3.3

docker/build-push-action
action
major
v3.3.1 -> v5.0.0

docker/setup-buildx-action
action
major
v2 -> v3

docker/setup-qemu-action
action
major
v2 -> v3

dotenv-expand
dependencies
major
^8.0.3 -> ^10.0.0

eslint-config-next (source)
devDependencies
major
13.4.19 -> 14.0.0

flask (changelog)

major
==2.3.3 -> ==3.0.0

go.opentelemetry.io/otel/sdk/metric
require
major
v0.39.0 -> v1.19.0

go.opentelemetry.io/otel/sdk/metric
require
major
v0.40.0 -> v1.19.0

greenlet

major
==2.0.2 -> ==3.0.1

mcr.microsoft.com/dotnet/runtime-deps
final
major
6.0.15-alpine3.16 -> 7.0.4-alpine3.16

mcr.microsoft.com/dotnet/sdk
stage
major
6.0.412 -> 7.0.403

next (source)
dependencies
major
12.3.4 -> 14.0.0

node
final
major
16-alpine -> 21-alpine

node
stage
major
16-alpine -> 21-alpine

node
final
major
18-alpine -> 21-alpine

node
stage
major
18-alpine -> 21-alpine

node-fetch
dependencies
major
2.6.7 -> 3.3.2

werkzeug (changelog)

major
==2.3.7 -> ==3.0.1

com.github.johnrengelman.shadow
plugin
major
7.1.2 -> 8.1.1

Release Notes

TanStack/query (@tanstack/react-query)
v5.0.5
Compare Source
Version 5.0.5 - 10/23/2023, 1:19 AM
Changes
Fix

svelte-query: Make combine work for createQueries (#6222) (b35fe32) by Lachlan Collins

Chore

Module resolution bundler (#6217) (129f8c9) by Lachlan Collins
Disable vitest globals (#6216) (c014ea7) by Lachlan Collins
Update dev dependencies (#6215) (b5c74f9) by Lachlan Collins

Docs

repo-header (4e2f425) by Dominik Dorfmeister
community projects (#6221) (0a0e490) by Dominik Dorfmeister

Packages

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
v5.0.0
Compare Source
Version 5.0.0 - 10/17/2023, 12:23 PM
Changes
Read the announcement post here: https://tanstack.com/blog/announcing-tanstack-query-v5
Read the migration guide here: https://tanstack.com/query/v5/docs/react/guides/migrating-to-v5
Packages

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
v4.36.1
Compare Source
Version 4.36.1 - 10/7/2023, 7:08 AM
Changes
Fix

fix release (2b0fc95) by Dominik Dorfmeister

Packages

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
v4.35.7
Compare Source
Version 4.35.7 - 10/1/2023, 10:15 AM
Changes
Fix

hydration: do not alter fetchStatus when hydrating existing queries (#6088) (a29f1a6) by Dominik Dorfmeister

Chore

Update CONTRIBUTING.md (b29824a) by Dominik Dorfmeister

Docs

Update dependent-queries.md (#6066) (7a9f851) by @weiliang903

Packages

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
v4.35.3
Compare Source
Version 4.35.3 - 9/13/2023, 6:28 AM
Changes
Fix

avoid reverting state to a fetching one (#5997) (88a8b30) by @Andarist

Docs

Update dependent-queries.md (#5963) (4d859e9) by Favourite Jome

Packages

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
v4.35.0
Compare Source
Version 4.35.0 - 9/7/2023, 8:04 AM
Changes
Feat

vue-query: useQuery support ref args (#5027) (d11280e) by @aa900031

Chore

query-core: add deprecated hint for isDataEqual (#5962) (716c5d8) by @Mini-ghost
prepare possibility to have rc releases (2017359) by Dominik Dorfmeister

Docs

update suspensive-react-query.md (#5961) (ef5125f) by @manudeli
Update queries.md (#5958) (84cd232) by @weisisheng

Packages

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
v4.33.0
Compare Source
Version 4.33.0 - 8/19/2023, 11:33 AM
Changes
Feat

query-core: expose Query class (#5874) (fc3c404) by Eliya Cohen

Chore

pnpm-lock.yaml: update (#5848) (314f23e) by @manudeli

Packages

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

dotnet/aspnetcore (Microsoft.AspNetCore.TestHost)
v7.0.13: .NET 7.0.13
Release
v7.0.12: .NET 7.0.12
Release
v7.0.11: .NET 7.0.11
Release
v7.0.10: .NET 7.0.10
Release
v7.0.9: .NET 7.0.9
Release
v7.0.8: .NET 7.0.8
Release
v7.0.7: .NET 7.0.7
Release
v7.0.5: .NET 7.0.5
Release
v7.0.4: .NET 7.0.4
Release
v7.0.3: .NET 7.0.3
Release
v7.0.2: .NET 7.0.2
Release
v7.0.1: .NET 7.0.1
Release
v7.0.0: .NET 7.0.0
Release
v6.0.24: .NET 6.0.24
Release
v6.0.23: .NET 6.0.23
Release

actions/checkout (actions/checkout)
v4
Compare Source

Add support for partial checkout filters

avajs/ava (ava)
v5.3.1
Compare Source
What's Changed

Update t.like() to support Symbol keys and ignore non-enumerable properties by @gibson042 in https://github.com/avajs/ava/pull/3209
Fix circular selector detection in t.like() by @novemberborn in https://github.com/avajs/ava/pull/3212

Full Changelog: https://github.com/avajs/ava/compare/v5.3.0...v5.3.1
v5.3.0
Compare Source
What's Changed

Support arrays in t.like() assertions by @tommy-mitchell in https://github.com/avajs/ava/pull/3185
Recognize typical assertion errors (expect and assert) and use their formatting by @Irvenae in https://github.com/avajs/ava/pull/3187

New Contributors

@MartynasZilinskas made their first contribution in https://github.com/avajs/ava/pull/3172
@flovogt made their first contribution in https://github.com/avajs/ava/pull/3194
@ondreian made their first contribution in https://github.com/avajs/ava/pull/3192
@tommy-mitchell made their first contribution in https://github.com/avajs/ava/pull/3185
@craigahobbs made their first contribution in https://github.com/avajs/ava/pull/3198
@Irvenae made their first contribution in https://github.com/avajs/ava/pull/3187

Full Changelog: https://github.com/avajs/ava/compare/v5.2.0...v5.3.0
v5.2.0
Compare Source
What's Changed

Infer thrown error from expectations by @tao-cumplido in https://github.com/avajs/ava/pull/3156

New Contributors

@tao-cumplido made their first contribution in https://github.com/avajs/ava/pull/3156

Full Changelog: https://github.com/avajs/ava/compare/v5.1.1...v5.2.0
v5.1.1
Compare Source
What's Changed

Fix de-registration of shared workers to ensure AVA exits correctly, by @codetheweb in https://github.com/avajs/ava/pull/3149 & https://github.com/avajs/ava/pull/3151

Full Changelog: https://github.com/avajs/ava/compare/v5.1.0...v5.1.1
v5.1.0
Compare Source
What's Changed

Output logs for tests that remain pending when AVA exits by @kevo1ution in https://github.com/avajs/ava/pull/3125
Check for --config file extensions after they fail to load, allowing custom loaders by @panva in https://github.com/avajs/ava/pull/3135

New Contributors

@kevo1ution made their first contribution in https://github.com/avajs/ava/pull/3125
@panva made their first contribution in https://github.com/avajs/ava/pull/3135

Full Changelog: https://github.com/avajs/ava/compare/v5.0.1...v5.1.0
v5.0.1
Compare Source
Despite the major version bump this is a relatively minor release. Node.js 12 is no longer supported. The type definitions are now distributed to be compatible with TypeScript 4.7 or newer.
npm install --save-dev ava

Breaking Changes

AVA now requires Node.js 14.19, 16.15 or 18. https://github.com/avajs/ava/pull/3043
Type definition distribution assumes at least TypeScript 4.7. https://github.com/avajs/ava/pull/3041
We're now exporting types rather than interfaces. https://github.com/avajs/ava/pull/3096

Improvements

Detect process.exit() called from tests by @gibson042 in https://github.com/avajs/ava/pull/3080
Improve test result accessibility by @gibson042 in https://github.com/avajs/ava/pull/3082
Parse for line numbers with latest supported ECMA version by @novemberborn in https://github.com/avajs/ava/pull/3063
Work around os.cpus() returning an empty array on unsupported platforms by @catink123 in https://github.com/avajs/ava/pull/3095
Count timeouts separately from the timed out tests by @novemberborn in https://github.com/avajs/ava/pull/3099
Cap idle timeouts to the maximum possible value by @creestor in https://github.com/avajs/ava/pull/3100

New Contributors

@Prinzhorn made their first contribution in https://github.com/avajs/ava/pull/3073
@catink123 made their first contribution in https://github.com/avajs/ava/pull/3095
@creestor made their first contribution in https://github.com/avajs/ava/pull/3100
@DavidVujic made their first contribution in https://github.com/avajs/ava/pull/3109

Full Changelog: https://github.com/avajs/ava/compare/v4.3.3...v5.0.1
v5.0.0
Compare Source
Despite the major version bump this is a relatively minor release. Node.js 12 is no longer supported. The type definitions are now distributed to be compatible with TypeScript 4.7 or newer.
It's available as a pre-release under the next tag for the next few weeks:
npm install --save-dev ava@next

Breaking Changes

AVA now requires Node.js 14.19, 16.15 or 18. https://github.com/avajs/ava/pull/3043
Type definition distribution is no longer compatible with TypeScript versions before 4.7. https://github.com/avajs/ava/pull/3041
We're now exporting types rather than interfaces. https://github.com/avajs/ava/pull/3096

Improvements

Detect process.exit() called from tests by @gibson042 in https://github.com/avajs/ava/pull/3080
Improve test result accessibility by @gibson042 in https://github.com/avajs/ava/pull/3082
Parse for line numbers with latest supported ECMA version by @novemberborn in https://github.com/avajs/ava/pull/3063
Work around os.cpus() returning an empty array on unsupported platforms by @catink123 in https://github.com/avajs/ava/pull/3095
Count timeouts separately from the timed out tests by @novemberborn in https://github.com/avajs/ava/pull/3099

New Contributors

@Prinzhorn made their first contribution in https://github.com/avajs/ava/pull/3073
@catink123 made their first contribution in https://github.com/avajs/ava/pull/3095

Full Changelog: https://github.com/avajs/ava/compare/v4.3.3...v5.0.0
v4.3.3
Compare Source
Add compatibility with Node.js 18.8, thanks @Brooooooklyn #3091.
 This may introduce issues with registry and runtime support (e.g. Google Cloud Run and AWS Lambda). You can optionally disable the default provenance attestation functionality using provenance: false.

warn if docker config can't be parsed by @crazy-max in https://github.com/docker/build-push-action/pull/957

Full Changelog: https://github.com/docker/build-push-action/compare/v4.2.0...v4.2.1
v4.2.0
Compare Source

Note
Buildx v0.10 enables support for a minimal SLSA Provenance attestation, which requires support for OCI-compliant multi-platform images. This may introduce issues with registry and runtime support (e.g. Google Cloud Run and AWS Lambda). You can optionally disable the default provenance attestation functionality using provenance: false.

display proxy configuration  by @crazy-max in https://github.com/docker/build-push-action/pull/872
chore(deps): Bump @docker/actions-toolkit from 0.6.0 to 0.8.0 in https://github.com/docker/build-push-action/pull/930
chore(deps): Bump word-wrap from 1.2.3 to 1.2.5 in https://github.com/docker/build-push-action/pull/925
chore(deps): Bump semver from 6.3.0 to 6.3.1 in https://github.com/docker/build-push-action/pull/902

Full Changelog: https://github.com/docker/build-push-action/compare/v4.1.1...v4.2.0
v4.1.1
Compare Source

Note
Buildx v0.10 enables support for a minimal SLSA Provenance attestation, which requires support for OCI-compliant multi-platform images. This may introduce issues with registry and runtime support (e.g. Google Cloud Run and AWS Lambda). You can optionally disable the default provenance attestation functionality using provenance: false.

Bump @docker/actions-toolkit from 0.3.0 to 0.5.0 by @crazy-max in https://github.com/docker/build-push-action/pull/880

Full Changelog: https://github.com/docker/build-push-action/compare/v4.1.0...v4.1.1
v4.1.0
Compare Source

Note
Buildx v0.10 enables support for a minimal SLSA Provenance attestation, which requires support for OCI-compliant multi-platform images. This may introduce issues with registry and runtime support (e.g. Google Cloud Run and AWS Lambda). You can optionally disable the default provenance attestation functionality using provenance: false.

Switch to actions-toolkit implementation by @crazy-max in https://github.com/docker/build-push-action/pull/811 https://github.com/docker/build-push-action/pull/838 https://github.com/docker/build-push-action/pull/855 https://github.com/docker/build-push-action/pull/860 https://github.com/docker/build-push-action/pull/875
e2e: quay.io by @crazy-max in https://github.com/docker/build-push-action/pull/799 https://github.com/docker/build-push-action/pull/805
e2e: local harbor and nexus by @crazy-max in https://github.com/docker/build-push-action/pull/800
e2e: add artifactory container registry to test against by @jedevc in https://github.com/docker/build-push-action/pull/804
e2e: add distribution tests by @jedevc in https://github.com/docker/build-push-action/pull/814 https://github.com/docker/build-push-action/pull/815

Full Changelog: https://github.com/docker/build-push-action/compare/v4.0.0...v4.1.0
v4.0.0
Compare Source

Note
Buildx v0.10 enables support for a minimal SLSA Provenance attestation, which requires support for OCI-compliant multi-platform images. This may introduce issues with registry and runtime support (e.g. Google Cloud Run and AWS Lambda). You can optionally disable the default provenance attestation functionality using provenance: false.

Enable provenance by default if not set by @crazy-max in https://github.com/docker/build-push-action/pull/784

Full Changelog: https://github.com/docker/build-push-action/compare/v3.3.1...v4.0.0

docker/setup-buildx-action (docker/setup-buildx-action)
v3
Compare Source

docker/setup-qemu-action (docker/setup-qemu-action)
v3
Compare Source

motdotla/dotenv-expand (dotenv-expand)
v10.0.0
Compare Source
Added

Support special characters in default expansion (#74)

v9.0.0
Compare Source
Added

Proper support for preload and cli args (#78)

vercel/next.js (eslint-config-next)
v14.0.0
Compare Source
Core Changes

perf: fix server trace file logic : #56898
feat: drop Node.js 16: #56896
Update React from d900fad to 09fbee8. Removes server context and experimental prefix for server action APIs: #56809
feat(env): upgrade dotenv: #38481
Update Babel dependencies: #51962
perf: fix tracing for routes: #56924
build: Update swc_core to v0.86.1: #56770
feat: set status code to 500 if unexpected error occurs before streaming in app router: #56236
cache: add unstable_noStore API: #56930
Adding  compon

Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: src/productcatalogservice/go.sum
Command failed: go get -d -t ./...
go: github.com/opentelemetry/opentelemetry-demo/src/productcatalogservice imports
	go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc imports
	go.opentelemetry.io/otel/exporters/otlp/internal: cannot find module providing package go.opentelemetry.io/otel/exporters/otlp/internal
go: github.com/opentelemetry/opentelemetry-demo/src/productcatalogservice imports
	go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc imports
	go.opentelemetry.io/otel/sdk/metric/aggregation: cannot find module providing package go.opentelemetry.io/otel/sdk/metric/aggregation
go: github.com/opentelemetry/opentelemetry-demo/src/productcatalogservice imports
	go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc imports
	go.opentelemetry.io/otel/exporters/otlp/otlpmetric/internal/oconf imports
	go.opentelemetry.io/otel/exporters/otlp/internal/envconfig: cannot find module providing package go.opentelemetry.io/otel/exporters/otlp/internal/envconfig
go: module github.com/golang/protobuf is deprecated: Use the "google.golang.org/protobuf" module instead.


Show Block Status

Note this is my first pull request ever, so any feedback would be greatly appreciated!
Inform user when she is blocked
Fixes #{1511}
Description
Fixes #{Inform user when she is blocked, 1511}
When an authenticated activity is created, a snackbar will be displayed if the user is blocked from Wikimedia Commons
Tests performed
Tested on API level 27 on Nexus 5 Emulator, with betaDebug build.
Screenshots showing what changed
Snackbar Popup

Thanks for your contribution. Can you try rebase master on your branch? A recent change I made there will make the Travis CI build should pass, I believe.

Yeah I can, thanks for the info! I probably won't be able to until tomorrow or tuesday though

@whym once I rebase master onto my branch, do I need to make another pull request? Or is there a way to update this one?

Oh I didn't notice the "Add more commits by pushing to the show-block-status branch on seannemann21/apps-android-commons." message

I'm failing Codacy/PR Quality Review for repeated string literals in my test cases such as here:
    assertBasicRequestParameters(server, "GET").let { userBlockedRequest ->
        parseQueryParams(userBlockedRequest).let { body ->
            assertEquals("xml", body["format"])
            assertEquals("query", body["action"])
            assertEquals("userinfo", body["meta"])
            assertEquals("blockinfo", body["uiprop"])
        }
    }

Should I add constants? Or just ignore the failed check? I was just following what other people had written in their test cases

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@30e5312). Click here to learn what that means.
The diff coverage is 0%.

@@           Coverage Diff            @@
##             master   #1573   +/-   ##
========================================
  Coverage          ?    3.9%
========================================
  Files             ?     146
  Lines             ?    7480
  Branches          ?     717
========================================
  Hits              ?     292
  Misses            ?    7171
  Partials          ?      17

Impacted Files
Coverage Δ

...n/java/fr/free/nrw/commons/auth/LoginActivity.java
0% <0%> (ø)

...r/free/nrw/commons/auth/AuthenticatedActivity.java
0% <0%> (ø)

...rw/commons/mwapi/ApacheHttpClientMediaWikiApi.java
5.13% <0%> (ø)

Continue to review full report at Codecov.

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

Also now that the Travis CI build has passed, is there anything else that I need to do? Potentially something with the Codecov report? Any information would be greatly appreciated!

@neslihanturan thank you very much! I'm sure there will be something I have to fix, but it wasn't too bad! I think I kinda overthought some things, but everyone was very helpful!

Thank you very much for the help and reviewing it!


Hold only a certain number of latest builds

Let's keep:

last 5 stable builds
last 5 beta builds
and 20 of dev builds.

Others can be removed.

we know currently only about the current and previous stable/beta/dev build. so there's no easy way to do this. we should probably just stop uploading to Toggl download server (assuming this issue is about Toggl download server) and drop the whole build archive once its done and all the updates point to Github.


[BUG] Dao parameter used mutliple times causes generator error

In code:
  @Query("""
    SELECT * FROM
    mytable s
    LEFT JOIN my_other_table ss ON ss.id = s.other_id
      AND s.spec_id = :spec_id
      AND ss.spec_id = :spec_id
  """)
  Future<List<MyEntity>> getMyEntitiesBySpecId(int spec_id);

I used :spec_id twice and it caused:
[SEVERE] floor_generator:floor_generator on lib/models/floor_database/database.dart:
Error running FloorGenerator
SQL query arguments and method parameters have to match.
package:my_flutter/models/dao/my_entity_dao.dart:28:31
   ╷
28 │   Future<List<MyEntity>> getMyEntitiesBySpecId(
   │                               ^^^^^^^^^^^^^^^^^^^^^^^
   ╵

If I use it only once then there is no error.

Right now, parameters can only be used once in a query. Thus, you would need to pass the same value to the function multiple time. Related issue #142

Closing as a duplicate of #142


Conditional use resource

I'm playing with this lib (the initial-implementation branch) and I'm wondering how to get a @use with a conditional.
I have a set of logic deciding when to fetch the data, but using the decorator alone doesn't seem to be possible to decide if I should execute my resource.  Looking at the RFC, the useResource might be a good option. However, I still need to get the state in "tracked matter".  Maybe a combination of effect and useResource?
Any help here would be awesome, as I experiment with use & resources.
Here is a high-level example:
// Works!
class MyComponent extends Componnet {
  @use accounts = watchQuery(this.args.myArgs);
}

// Well, just something that will not work...
class MyComponent extends Componnet {
  @tracked accounts; // ???

  constructor(owner, args) {
    super(owner, args);

    this.accounts = use(
      this,
      watchQuery(() => [
         ...this.args.myArgs
      ])
    ).state;

    console.log(this.accounts);
  }
}

PS, this watchQuery resource is an Apollo GraphQL thing that I'm working on..  Here is a sketch of that resource: https://gist.github.com/josemarluedke/2e60b6d7303d4eb4fdfbba157e11dc34

Sorry I left this for so long! I've updated with a new API in general and finally gotten it out the door.
So the issue you're trying to solve is, you want to conditionally load data based on another argument?

Yeah, I just catching up with the changes (great blog post btw). Yes, my original motivation was to load the data depending on another argument/tracked property.
However, as I worked more on this, I think my original issue is not valid. Looking around in the React ecosystem, they usually solve this issue by returning a function from the hook that would trigger the underlining resource to load. Here is an example that I still need to test out to see if works with this addon:
class MyComponent extends Componnet {
  @use myData = lazyFetchData({id: this.args.id });

  @action loadMyData() {
    this.myData.load();
  }
}

Another way is to have an isEnabled argument:
class MyComponent extends Componnet {
  @tracked shouldLoad = false
  @use myQuery = fetchData({ isEnabled: this.shouldLoad, id: this.args.id });

  @action loadMyData() {
    this.shouldLoad = true
  }
}

Anyway, I don't think this is an issue anymore. Thanks for getting back to me.


Pull to load more

要是把上拉加载更多 集成进去，就无敌了

+1, 期待中

+1,期待中
2015-01-02 13:42 GMT+08:00 xianyo<EMAIL_ADDRESS>
+1, 期待中
—
Reply to this email directly or view it on GitHub
https://github.com/liaohuqiu/android-Ultra-Pull-To-Refresh/issues/8#issuecomment-68509798
.

+1，期待中   最好是可以设置开关，是否显示“加载更多”

加载更多应该是ContentView自己去实现吧，最好不要放在PTR里面

@grumoon 同意你的观点。

+1

@grumoon @liaohuqiu 为何加载更多不能放在PTR里面，能简单说明下吗？

@AvatarQing  I really agree with u

RecyclerView can add endless scrolling but I do not like it ,it is kind of bad for user interface

@liaohuqiu so r  u gonna add pull to load more interface for this lib?

Probably not. Load more is easy to implement and it's independent from Pull to refresh.
I've implemented load more for ListView and GridView. If I've plenty of time, I will implement load more for RecyclerView

@liaohuqiu i clone the project but can't find demo for load more for ListView and GridView. r u not push  yet ?

@littletanker  It's here https://github.com/liaohuqiu/android-cube-app

@liaohuqiu  yes it is easy to implement load more feature like GIF above ,but what I was saying is pull up to load more like xlistview https://github.com/Maxwin-z/XListView-Android/wiki

@EzimetYusup Ptr supports all the views, but LoadMore only supports ListView and GridView, (RecycleView will be supported in days), so we should not put these two futures together.

@liaohuqiu  Thanks for replying , waiting for your pull up to   LoadMore feature of RecyclerView

+1

+1 发自网易邮箱大师 在2015年03月20日 11:17 ，Vurtex(李一轩)写道： +1 — Reply to this email directly or view it on GitHub.

+1

+1

期待加上拉加载更多

Closed.
As mentioned in #45 .
And here is a solution for load-more:
https://github.com/etao-open-source/cube-sdk
Here is the demo project: https://github.com/liaohuqiu/android-cube-app/tree/master/src/in/srain/cube/demo/ui/loadmore

在给出的 cube-sdk demo 中，是根据不同的 View 分别做不同的处理，使之实现 load more 功能。
把 loadMoreView 作为 View 的一部分，感觉这样耦合太严重了。
尤其是 RecyclerView，需要根据 LayoutManager 做不同处理，还要把 loadMoreView 加到 RecyclerView item 中，实现方式太 dirty。
不同的 View 要用不同的方法来实现同一个功能(load more)，很琐碎。像 ptr 一样，附加一个 footerView 作为 loadMoreView ，封装 load more 这一功能，使之对于 ptr 支持的 View 类型全部支持，会不会是更好的设计呢？
@see https://github.com/liaohuqiu/cube-sdk/issues/66

我感觉也是，没有上拉加载很多情形都无法使用


Adds "Clip Region" clipping to ConsoleDriver

As part of the new View architecture, we will need a more sophisticated clipping mechanism than just a single rectangle.
This PR adds such a thing, retaining the previous ConsoleDriver.Clip functionality.
The clip region is exposed via ClipRegion which is a List<Rect>. IsInClipRegion() (private) tests whether a coordinate is within the region or not.
ConsoleDriver.IsValidClip has been renamed to IsValidLocation (it was mis-named before because it also validates the coordinates are within the screen bounds).
Also:

cleans up ConsoleDriver code

Other than ensuring I didn't break anything and adding unit tests, I've not exercised this functionality for realz yet. That will come soon, hence this is still a draft PR.

Still a draft.
I've discovered a bunch of things in all the drivers that need to be tweaked to make this work. No way am I going to do it all 4 times. Instead, I'm going to work on #666 (which I started in the code in this PR) as a separate PR first.  Much can be moved into ConsoleDriver in a way that makes unit testing it all much better.


Broken link in documentation

There is a broken link in http://mimesis.readthedocs.io/#locales
The broken link points to http://mimesis.readthedocs.io/en/latest/locales.html but there is no such page.
Also, where can I find the supported locales?

@vladcalin You can find supported locales in README.md.

@vladcalin I'll fix it ASAP.


fix(sec): upgrade gopkg.in/yaml.v3 to 3.0.0

What happened？
There are 1 security vulnerabilities found in gopkg.in/yaml.v3 v3.0.0-20210107192922-496545a6307b

CVE-2022-28948

What did I do？
Upgrade gopkg.in/yaml.v3 from v3.0.0-20210107192922-496545a6307b to 3.0.0 for vulnerability fix
What did you expect to happen？
Ideally, no insecure libs should be used.
The specification of the pull request
PR Specification from OSCS

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

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

@chncaption please sign the CLA if you would like us to merge this. Otherwise, I plan to do a PR soon to update all deps and we will capture the update there.

Also, the security issue is a false positive because even though gopkg.in/yaml.v3 shows up in the go.mod file, it doesn't actually end up in the final binary (you can confirm with go version -m, only v2 ends up being used)

Fixed with #780


cmd line vs browser

From what I can tell, this module has to be used in the browser with browserify (or whatever)?
Is this correct? If so, why is this? Is there any reason I shouldn't be able to write a script and just run it with node?

Closed with https://github.com/mapbox/geocode-many/pull/6


make remix-headers a const function

All the other functions use const except the headers.
https://github.com/amimaro/remix-run-snippets/blob/main/snippets/typescript.json#L66
can we please make it also be a const?

Done. Thank you for this issue!
I believe in a few minutes the new release (1.0.7) will be available.


Cache and Future work together

I don't find a right way for execute some query in the future and in the same time cache the results. Is possible? Example:
ctx.BookingRequests.Where(x => x.Id > 1).FromCache().Future();
ctx.Bookings.Where(x => x.Name != "xxx").FromCache().Future();
ctx.Clients.Where(x => x.Phone != null).FromCache().Future();

Hello hanc2006,
Unfortunately, query cache & query future cannot work yet together.
This limitation will probably be fixed in the next major version. However, we don't know yet when we will start the next major version or when it will be completed.
So in short, it's not possible for now.
Best Regards,
Jonathan

This issue has been added to milestone 2.0


All the events are unsound

They form no lifetime relationship and thus very short living callbacks are allowed, causing use after frees among other undefined behavior.
Here's an example of this:
let mut button = Button::new(&ui, "Button");
{
    let x = String::new();
    button.on_clicked(&ui, {
        |btn| {
            println!("{}", x);
        }
    });
    drop(x);
}

The button's click event references the String x, but it gets dropped before the event ever happens. Once it does happen, the dropped String is still used.

Duplicate of #41, this will be solved immenently


Added general PPMS plugin

Added the PPMS plugin. Up to now, it can deal with ETO and ACT measurements. More types like magnetization measurement will follow soon.

FYI @budschi

hi @JonathanNoky
few points:

you find now  def set_entrydata_definition(self): around in the code. Here is where you can add any kind of class that must be used by the parser. In this way, you can inherit and specialize this parser into your plugin, you can change the classes used, and also extend the set of variable defined to include new classes
if you use the virtualenvironment where nomad is installed you get also the ruff linting tools (ruff check . --fix and `ruff format .) so you get linted code
more comments in specific lines of the MR

It seems to be coming when using nomad.search in the ppms parser.
    #
    # This file is part of NOMAD. See https://nomad-lab.eu/ for further info.
    #
    # Licensed under the Apache License, Version 2.0 (the "License");
    # you may not use this file except in compliance with the License.
    # You may obtain a copy of the License at
    #
    #     http://www.apache.org/licenses/LICENSE-2.0
    #
    # Unless required by applicable law or agreed to in writing, software
    # distributed under the License is distributed on an "AS IS" BASIS,
    # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    # See the License for the specific language governing permissions and
    # limitations under the License.
    #

    """
    This module provides function to establish connections to the database, searchengine, etc.
    infrastructure services. Usually everything is setup at once with :func:`setup`. This
    is run once for each *api* and *worker* process. Individual functions for partial setups
    exist to facilitate testing, aspects of :py:mod:`nomad.cli`, etc.
    """

    import os.path
    import os
    import shutil
    from elasticsearch_dsl import connections
>   from mongoengine import connect, disconnect
E   ModuleNotFoundError: No module named 'mongoengine'

If you see in this branch, I moved the test file for XRD in a dedicated folder. I will need to change the paths in the test.
IS it okay for you to organize the test files in subfolders @ka-sarthak ?

@aalbino2 Sure, tests/data/xrd looks good

I will merge this PR and open new issues for further development @JonathanNoky


Core/SSH: libssh2 upgraded to version 1.11.1

libssh2 upgraded from 1.10 to 1.11.1
It brings in many fixes, improvements and deprecations.  The list of changes made to the underlying libssh2 can be found here
Core/SSH:

SshSession now allows computation of public key from private key.
Channel creation methods are deprecated in favor of traditional class constructors (with a deprecation warning).
Deprecated libssh2 hook installers substituted with the new ones.

Hos safe are these changes? Do you have some kind of test suite that can verify the code? I am thinking whenever we should merge it before 2024.1 or after.

Hos safe are these changes? Do you have some kind of test suite that can verify the code? I am thinking whenever we should merge it before 2024.1 or after.

Changes are solid. Under-the-hood changes were why I waited libssh2 version 1.11.1. Fixes many problems, moves to OpenSSL3, removes very old unsafe algorithms. (See 1.11.0 & 1.11.1 release notes.). We've already skipped ver 1.11.0, since it was an upgrade to libssh2, and brought in some regressions, as well as ton of improvements. But with 1.11.1 they are fixed. Also, we are using libssh2's own test suite since the beginning (I periodically run them on my setups) and only strip them from the final package (to reduce its size).
As for the merge, I believe this can wait and should be merged right after 2024.1.

Will merge happen anytime soon? Changes now also includes some important last minute fixes.


Read Device Twin from Device

On subscribe, I get notifications when an update is performed on device twin. In such cases, the update is partial and only sends the changed parameters of desired.
The iothub services client of azure-iot-sdk-c has provision to read,but the iothub_client can only subscribe and not read
Is there a way for a device to read the entire device twin?

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

ID: 8ff6fbb2-5679-a9e7-b9f3-40d638cadae8
Version Independent ID: fa51c99a-0df6-cebf-aecc-b08df5f85454
Content: Understand Azure IoT Hub device twins
Content Source: articles/iot-hub/iot-hub-devguide-device-twins.md
Service: iot-hub
GitHub Login: @fsautomata
Microsoft Alias: elioda

@gkottur Thanks for the question. We are actively investigating and will get back to you soon.

Thank you for taking the time to share your product and documentation feedback with us. Your input is valued because it helps us create the right documentation for our customers. Due to the volume of issues in our queue, we are closing open issues older than 90 days. We hope to continue hearing from you. Thank you.


merge from template-arlac77-github

package.json

chore(deps): add ^7.23.7 remove ^7.23.6 (devDependencies.npm-pkgbuild)

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

v1.10.35
GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


178 zkllvm compatibility

Also maybe change the description of the PR from "zkllvm compatibility" to a bit longer text describing the change.


spawnParticles NPE

When I try to spawn a particle, it throws a NPE. This doesn't happen with SpongeForge. This was introduced with SpongePowered/SpongeCommon#702.
Pastebin : http://pastebin.com/56b11Yad
Code Reference : Here

Caused by SpongeParticleHelper.java#L123 due to MixinEntity.java#L49-L53

@Cybermaxke

Any ETA on when this will be fixed? 🐱


Download image after anonymous metadata

Dear,
I use dicomParser to anonymous private patient's information but I have not really known the whole code because I have worked with javascript for one week.
After anonymous implemented, where is the image stored?
In doc, it telled that the file is stored in cornerstoneFileImageLoader and we must config the path. but i did not find the config find. I want to know that, this config will be written in this file.html which we want to run.
Thank you so much!

I know that the information which user post like Image, will transfer into the cornerstoneFileImageLoader. And this file is depended on my configure. It is right?

I am sorry but you are asking basic web development questions that are not appropriate for this forum.  If you need more consulting help, please try the cornerstone forum


Gmail blocking third party scripts?

I'm not sure if this is a known issue, but I don't see any notice of it so I'm posting an issue:
Attempting to inject via console throws the error below.  It looks like gmail is blocking all third party scripts?
[Report Only] Refused to load the script 'https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js' because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' 'unsafe-eval' https://talkgadget.google.com/ https://www.googleapis.com/appsmarket/v2/installedApps/ https://www-gm-opensocial.googleusercontent.com/gadgets/js/ https://docs.google.com/static/doclist/client/js/ https://www.google.com/tools/feedback/ https://s.ytimg.com/yts/jsbin/ https://www.youtube.com/iframe_api https://ssl.google-analytics.com/ https://apis.google.com/_/scs/abc-static/ https://apis.google.com/js/ https://clients1.google.com/complete/ https://apis.google.com/_/scs/apps-static/_/js/ https://ssl.gstatic.com/inputtools/js/ https://ssl.gstatic.com/cloudsearch/static/o/js/ https://www.gstatic.com/feedback/js/ https://www.gstatic.com/common_sharing/static/client/js/ https://www.gstatic.com/og/_/js/".

I understand this is a workaround to the CSP but what are the risks of this workaround? Why is it ok to do this?


Interner Explorer 11 example?

Hi
This script looks very useful, I was wondering could you show an example of how it could be implemented to serve an alternative CSS file for IE11?
I'm using Tailwind CSS, which doesn't support IE11. I'd like to be able to use Tailwind for modern browsers and fall back to ie11.css if IE11 is detected.
// If IE11 load this
    <link rel="stylesheet" href="/css/ie11.css">
// else use Tailwind
    <link rel="stylesheet" href="/css/tailwind.css">

Hope you can help.

Hi, just wondering if this is possible?

You can use this script only on server side. You can do something like that:
$BrowserDetection = new BrowserDetection();
$browser = $BrowserDetection->getBrowser($_SERVER['HTTP_USER_AGENT']);

if ($browser['browser_name'] === 'Internet Explorer') {
    echo '<link rel="stylesheet" href="/css/ie11.css">';
}
else {
    echo '<link rel="stylesheet" href="/css/tailwind.css">';
}

Hi,
Indeed, this library works on the server side.


Problem with box "Options" of query

The box "Options" of query GUI interface seems not working. The following string is not accepted:
{fields: {gradicentigradi: 0 }}

@mttstt you need json object here (not .js object) so add quotes to property names.

ok thanks


[keymgr] enable / disable usage

keymgr enable/disable checking is using strict instead of loose type.
This means as long as the enable is made to something that is "not disable", there could be unexpected behavior.
The check should be made more loose to cover this.

On second review of keymgr code, it seems a strict check is used in all places where the signal is used a single bit enable.
So this should mean that if the enable is made to something that's intermediate, it will still be interpreted as disable, and that is the desired effect.


FIX: CI: avoid passing Cython files to ruff

Reference issue

resolves CI lint issues discovered in https://github.com/scipy/scipy/pull/17961

What does this implement/fix?

avoids passing unsupported Cython files to Ruff linter

Additional information

I took the liberty of resolving the merge conflict; should be good now. I ran it locally and saw no linting errors. Thanks @mckib2!


Scroll not working on a SliverList.list inside a CustomScrollView, but yes with a SliverList.builder

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
I have a NestedScrollViewwith a SliverAppBar, and a CustomScrollView as a child. Inside the CustomScrollView, if I use a SliverList.builder everything works fine, but if I use a SliverList.listthe scroll doesn't work. This only happens with the normal SliverAppBar. If you use a SliverAppBar.mediumor a SliverAppBar.large, both SliverLists works fine.
Expected results
Scrolling with SliverList.listshould scroll as it does SliverList.builder.
Actual results
SliverList.builder scrolls but SliverList.listdoesn't.
Code sample
In case you wonder why I want to use a SliverList.list instead of a SliverList.builder it's because I want to build a settings screen, with a list of different settings. The screen doesn't contain a list of ListTile that are the exact same widget but with different data. All the widgets on the list have different structure.
Code sample
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      theme: ThemeData(
        useMaterial3: true
      ),
      home: const MyStatelessWidget(),
    );
  }
}

class MyStatelessWidget extends StatelessWidget {
  const MyStatelessWidget({super.key});

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: NestedScrollView(
        headerSliverBuilder: (BuildContext context, bool innerBoxIsScrolled) {
          return <Widget>[
            SliverOverlapAbsorber(
              handle: NestedScrollView.sliverOverlapAbsorberHandleFor(context),
              sliver: SliverAppBar(
                title: const Text("Title"),
                pinned: true,
                floating: true,
                centerTitle: false,
                forceElevated: innerBoxIsScrolled,
              ),
            ),
          ];
        },
        body: SafeArea(
          top: false,
          bottom: false,
          child: Builder(
            builder: (context) => CustomScrollView(
              slivers: [
                SliverOverlapInjector(
                  handle: NestedScrollView.sliverOverlapAbsorberHandleFor(context),
                ),
                SliverList.list(
                  children: [
                    ListTile(
                      title: const Text("List tile"),
                      subtitle: const Text("Navigate to second screen"),
                      onTap: () => Navigator.push(context, MaterialPageRoute(
                        builder: (context) => const SecondScreen()
                      )),
                    ),
                    ListTile(
                      title: const Text("List tile"),
                      subtitle: const Text("Navigate to second screen"),
                      onTap: () => Navigator.push(context, MaterialPageRoute(
                        builder: (context) => const SecondScreen()
                      )),
                    ),
                    ListTile(
                      title: const Text("List tile"),
                      subtitle: const Text("Navigate to second screen"),
                      onTap: () => Navigator.push(context, MaterialPageRoute(
                        builder: (context) => const SecondScreen()
                      )),
                    ),
                    ListTile(
                      title: const Text("List tile"),
                      subtitle: const Text("Navigate to second screen"),
                      onTap: () => Navigator.push(context, MaterialPageRoute(
                        builder: (context) => const SecondScreen()
                      )),
                    ),
                    ListTile(
                      title: const Text("List tile"),
                      subtitle: const Text("Navigate to second screen"),
                      onTap: () => Navigator.push(context, MaterialPageRoute(
                        builder: (context) => const SecondScreen()
                      )),
                    ),
                    ListTile(
                      title: const Text("List tile"),
                      subtitle: const Text("Navigate to second screen"),
                      onTap: () => Navigator.push(context, MaterialPageRoute(
                        builder: (context) => const SecondScreen()
                      )),
                    ),
                    ListTile(
                      title: const Text("List tile"),
                      subtitle: const Text("Navigate to second screen"),
                      onTap: () => Navigator.push(context, MaterialPageRoute(
                        builder: (context) => const SecondScreen()
                      )),
                    ),
                    ListTile(
                      title: const Text("List tile"),
                      subtitle: const Text("Navigate to second screen"),
                      onTap: () => Navigator.push(context, MaterialPageRoute(
                        builder: (context) => const SecondScreen()
                      )),
                    ),
                    ListTile(
                      title: const Text("List tile"),
                      subtitle: const Text("Navigate to second screen"),
                      onTap: () => Navigator.push(context, MaterialPageRoute(
                        builder: (context) => const SecondScreen()
                      )),
                    ),
                    ListTile(
                      title: const Text("List tile"),
                      subtitle: const Text("Navigate to second screen"),
                      onTap: () => Navigator.push(context, MaterialPageRoute(
                        builder: (context) => const SecondScreen()
                      )),
                    ),
                    ListTile(
                      title: const Text("List tile"),
                      subtitle: const Text("Navigate to second screen"),
                      onTap: () => Navigator.push(context, MaterialPageRoute(
                        builder: (context) => const SecondScreen()
                      )),
                    ),
                    ListTile(
                      title: const Text("List tile"),
                      subtitle: const Text("Navigate to second screen"),
                      onTap: () => Navigator.push(context, MaterialPageRoute(
                        builder: (context) => const SecondScreen()
                      )),
                    ),
                    ListTile(
                      title: const Text("List tile"),
                      subtitle: const Text("Navigate to second screen"),
                      onTap: () => Navigator.push(context, MaterialPageRoute(
                        builder: (context) => const SecondScreen()
                      )),
                    ),
                  ]
                ),
                // SliverList.builder(
                //   itemCount: 30,
                //   itemBuilder: (context, index) => ListTile(
                //     title: Text("List tile $index"),
                //     subtitle: const Text("Navigate to second screen"),
                //     onTap: () => Navigator.push(context, MaterialPageRoute(
                //       builder: (context) => const SecondScreen()
                //     )),
                //   )
                // )
              ],
            ),
          )
        )
      ),
    );
  }
}

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

  @override
  State<SecondScreen> createState() => _SecondScreenState();
}

class _SecondScreenState extends State<SecondScreen> {
  int count = 30;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: NestedScrollView(
        headerSliverBuilder: (context, innerBoxIsScrolled) => [
          SliverOverlapAbsorber(
            handle: NestedScrollView.sliverOverlapAbsorberHandleFor(context),
            sliver: SliverAppBar.large(
              leading: IconButton(
                onPressed: () => Navigator.pop(context),
                icon: const Icon(Icons.close)
              ),
              pinned: true,
              floating: true,
              centerTitle: false,
              forceElevated: innerBoxIsScrolled,
              title: const Text("Second screen"),
              actions: [
                IconButton(
                  onPressed: () => setState(() => count++),
                  icon: const Icon(Icons.add)
                ),
                const SizedBox(width: 10)
              ],
            ),
          )
        ],
        body: SafeArea(
          top: false,
          bottom: false,
          child: Builder(
            builder: (context) => CustomScrollView(
              slivers: [
                SliverOverlapInjector(
                  handle: NestedScrollView.sliverOverlapAbsorberHandleFor(context),
                ),
                SliverList.builder(
                  itemCount: count,
                  itemBuilder: (context, index) => ListTile(
                    title: Text("Item $index"),
                  ),
                )
              ],
            ),
          )
        ),
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
https://github.com/flutter/flutter/assets/47545344/a2e1d684-81e2-4508-a2fe-d7335c8ad433

Logs
No response
Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.10.1, on macOS 13.3.1 22E772610a darwin-arm64, locale es-ES)
    • Flutter version 3.10.1 on channel stable at /Users/juan/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision d3d8effc68 (4 days ago), 2023-05-16 17:59:05 -0700
    • Engine revision b4fb11214d
    • Dart version 3.0.1
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/juan/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/juan/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.2

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

[✓] Android Studio (version 2022.1)
    • Android Studio at /Applications/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 11.0.15+0-b2043.56-8887301)

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

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64  • Android 13 (API 33) (emulator)
    • sdk gphone64 arm64 (mobile) • emulator-5556 • android-arm64  • Android 12 (API 31) (emulator)
    • macOS (desktop)             • macos         • darwin-arm64   • macOS 13.3.1 22E772610a darwin-arm64
    • Chrome (web)                • chrome        • web-javascript • Google Chrome 113.0.5672.126

[✓] Network resources
    • All expected network resources are available.

• No issues found!```

</details>

It seems you're experiencing an issue with scrolling when using a NestedScrollView with a SliverAppBar and a CustomScrollView as its child. Specifically, you mentioned that using SliverList.builder works fine, but using SliverList.list causes the scroll to not work properly. However, when using SliverAppBar.medium or SliverAppBar.large, both SliverLists work fine.
This behavior could be due to a combination of factors related to how the different components interact and handle scrolling events. Without seeing your specific code, it's difficult to pinpoint the exact cause. However, I can provide you with some general insights and suggestions that might help you troubleshoot and resolve the issue.
Ensure correct configuration: Make sure that you have set up the NestedScrollView and CustomScrollView correctly. Double-check that you have assigned the appropriate scroll controllers and axis directions.
Check content size: Confirm that the content within the CustomScrollView is large enough to require scrolling. If the content is small, it might not trigger the scroll behavior.
Nested scrolling conflicts: In some cases, conflicts can arise when using nested scrolling components like NestedScrollView. If you have other nested scrolling widgets or conflicting gestures within your app, they might interfere with the scroll behavior. Make sure that there are no conflicting gestures or scrolling behaviors that could be preventing the expected scrolling.
Check for errors or warnings: Examine the logs or console output for any errors or warnings related to the scroll behavior. Sometimes, error messages or warnings can provide valuable clues about what might be going wrong.
Debugging and isolating the issue: Try to isolate the issue by gradually removing or simplifying parts of your code while testing the scroll behavior. By doing so, you can identify if there's a specific widget or configuration that is causing the problem.
Consider alternative approaches: If you're unable to resolve the issue directly, you could consider alternative approaches to achieve the desired layout and scrolling behavior. For instance, you might explore using a CustomScrollView directly without the NestedScrollView or using a different combination of sliver widgets to achieve your desired layout.
Remember to consult the Flutter documentation and relevant resources for further guidance on how to use the specific widgets correctly. Additionally, seeking help from the Flutter community, such as forums or chat groups, can provide insights from other developers who may have encountered similar issues.

It seems you're experiencing an issue with scrolling when using a NestedScrollView with a SliverAppBar and a CustomScrollView as its child. Specifically, you mentioned that using SliverList.builder works fine, but using SliverList.list causes the scroll to not work properly. However, when using SliverAppBar.medium or SliverAppBar.large, both SliverLists work fine.
This behavior could be due to a combination of factors related to how the different components interact and handle scrolling events. Without seeing your specific code, it's difficult to pinpoint the exact cause. However, I can provide you with some general insights and suggestions that might help you troubleshoot and resolve the issue.
Ensure correct configuration: Make sure that you have set up the NestedScrollView and CustomScrollView correctly. Double-check that you have assigned the appropriate scroll controllers and axis directions.
Check content size: Confirm that the content within the CustomScrollView is large enough to require scrolling. If the content is small, it might not trigger the scroll behavior.
Nested scrolling conflicts: In some cases, conflicts can arise when using nested scrolling components like NestedScrollView. If you have other nested scrolling widgets or conflicting gestures within your app, they might interfere with the scroll behavior. Make sure that there are no conflicting gestures or scrolling behaviors that could be preventing the expected scrolling.
Check for errors or warnings: Examine the logs or console output for any errors or warnings related to the scroll behavior. Sometimes, error messages or warnings can provide valuable clues about what might be going wrong.
Debugging and isolating the issue: Try to isolate the issue by gradually removing or simplifying parts of your code while testing the scroll behavior. By doing so, you can identify if there's a specific widget or configuration that is causing the problem.
Consider alternative approaches: If you're unable to resolve the issue directly, you could consider alternative approaches to achieve the desired layout and scrolling behavior. For instance, you might explore using a CustomScrollView directly without the NestedScrollView or using a different combination of sliver widgets to achieve your desired layout.
Remember to consult the Flutter documentation and relevant resources for further guidance on how to use the specific widgets correctly. Additionally, seeking help from the Flutter community, such as forums or chat groups, can provide insights from other developers who may have encountered similar issues.

The thing is that it shouldn't be any difference on the behavior between SliverList.list and SliverList.builder because as far I know, the only difference is that the builder paints the list widgets when they are going to be displayed, instead of painting the whole list at one time. Also I don't understand why with SliverAppBar.large it works fine but not with a normal SliverAppBar.

Thanks for the report. I also can reproduce this issue on the latest master channel.
This seems to be introduced by PR https://github.com/flutter/flutter/pull/116605. Labeling the issue for further insights.

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.10.1, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.10.1 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision d3d8effc68 (26 hours ago), 2023-05-16 17:59:05 -0700
    • Engine revision b4fb11214d
    • Dart version 3.0.1
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 32.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

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

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/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 17.0.6+0-17.0.6b802.4-9586694)

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

[✓] Connected device (3 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D • android-arm64  • Android 11 (API 30)
    • macOS (desktop)  • macos            • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)     • chrome           • web-javascript • Google Chrome 113.0.5672.126

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[!] Flutter (Channel master, 3.11.0-10.0.pre.44, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.11.0-10.0.pre.44 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ab573048e7 (35 hours ago), 2023-05-20 11:32:26 -0400
    • Engine revision aac0919568
    • Dart version 3.1.0 (build 3.1.0-129.0.dev)
    • DevTools version 2.23.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 32.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

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

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/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 17.0.6+0-17.0.6b802.4-9586694)

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

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 113.0.5672.126

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

This is not caused by #116605 as using a SliverList without the .list constructor, and manually providing a SliverListDelegate reproduces the same issue.
import 'package:flutter/material.dart';

// ignore_for_file: prefer_const_constructors
// ignore_for_file: use_key_in_widget_constructors

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      theme: ThemeData(
        useMaterial3: true
      ),
      home: FullCase(),
    );
  }
}

class SimpleCase extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: CustomScrollView(
        slivers: [
          SliverAppBar(
          // SliverAppBar.medium(
          // SliverAppBar.large(
            pinned: true,
            title: Text('Simple'),
          ),
          SliverList.list(
            children: List.generate(50, (index) => Text('Index $index'))
          ),
        ],
      ),
    );
  }

}

class FullCase extends StatelessWidget {
  const FullCase({super.key});

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: NestedScrollView(
        headerSliverBuilder: (BuildContext context, bool innerBoxIsScrolled) {
          return <Widget>[
            SliverOverlapAbsorber(
              handle: NestedScrollView.sliverOverlapAbsorberHandleFor(context),
              sliver:
                SliverAppBar(
                // SliverAppBar.medium(
                // SliverAppBar.large(
                title: const Text('Nested'),
                pinned: true,
                floating: true,
                forceElevated: innerBoxIsScrolled,
              ),
            ),
          ];
        },
        body: SafeArea(
          top: false,
          bottom: false,
          child: Builder(
            builder: (context) => CustomScrollView(
              slivers: [
                SliverOverlapInjector(
                  handle: NestedScrollView.sliverOverlapAbsorberHandleFor(context),
                ),
                SliverList(
                  delegate: SliverChildListDelegate(
                    List.generate(50, (index) => Text('Index $index'))
                  ),
                ),
                // SliverList.list(
                //   children: List.generate(50, (index) => Text('Index $index'))
                // ),
              ],
            ),
          )
        )
      ),
    );
  }
}

It seems to only happen in the case where SliverAppBar.pinned is true, or SliverAppBar.pinned and floating are true. I would be surprised if this bug was always here, but without knowing when it did work, tracking down the actual change that may have regressed this will be difficult. Has anyone know this to work at some version of Flutter?

More details: The issue does not exist when scrolling with a physical mouse wheel, only a trackpad so far (which includes magic mouse).

Nice job 👍


[T2A2][T09-A4] Gauri Joshi

Ready for review.

Great job! Do see the comments on each line of code I wrote above ^ 👍


Revert "fix(ast): fix JSON serialization of BindingPattern (#3856)"

Revert "fix(ast): fix JSON serialization of BindingPattern (#3856)"
This reverts commit 66f404c2f379021092e9e2a33f0421d9933a5af3.
Revert "refactor(ast): add span field to the BindingPattern type. (#3855)"
This reverts commit 363d3d57d7af5dcfc80421bc272388714d4d55d1.

#3899  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rzvxa and the rest of your teammates on  Graphite


[FLINK-12223][Runtime]HeapMemorySegment.getArray should return null a…

…rs in HybridMemorySegment

What is the purpose of the change
Fix a bug in class HeapMemorySegment. The getArray method should return null after the segment is freed. But it does not.
Brief change log

Fix the bug in class HeapMemorySegment
Add a UT in HeapMemorySegmentTest.

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

Test HeapMemorySegmentTest.testGetArrayAfterFree will fail without this fix, and it runs successfully with this patch.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)

Hi @zentol , would you please take a look at this PR?

@flinkbot attention @StephanEwen

@liyafan82
I rebased the PR and squashed the commits. Please, take a look if the final state is ok, then I will merge it when CI is green.

@liyafan82
I rebased the PR and squashed the commits. Please, take a look if the final state is ok, then I will merge it when CI is green.

LGTM, thanks for your effort.

@flinkbot run travis


Add support for emulating the mailgun HTTP api

Mailgun is an email service provider, recommending you send email messages via http rather than smtp.
This feature adds functionality to mailcatcher so that it implements the mailgun API, allowing a (in my case rails) application to be configured to think it's delivering to mailgun over http, but in fact delivering to mailcatcher.
To configure a rails on localhost to talk to mailcatcher also on localhost (here, picking port 3025):
In rails development.rb:
config.action_mailer.mailgun_settings = {
  api_key: 'dontcare',
  domain: 'example.com',
  api_host: 'localhost:3025',
  api_ssl: false
}

Then run mailcatcher as:
bundle exec bin/mailcatcher --mailgun-ip '<IP_ADDRESS>' --mailgun-port 3025 -f

Thank you for the contribution, but I'm sorry this will not be accepted. MailCatcher is an SMTP server. Making it a fake mailgun server would open the door to supporting every mail provider which has non-smtp interfaces, and that is not within the scope of this project, sorry.


DevOps Module 1 - Create seed doesn't account for us-east-2

The doc says it will be configured for you just fine, but clicking on us-east will only generate the seed file for us-east-1. There is no option for us-east-2.
I do not know how to get past this step.

us-east-2 is not currently a supported region for this workshop. We will update to add support shortly. In the meantime, can you run in a different region?

@samdengler We should make sure the base CloudFormation template that drives the code commit repo seeding is part of this repo, I don't see it here. We should also move the templates to the main wildrydes-[REGION] buckets. Let me know if you need help setting that up.

Thanks for your feedback.  We've update the DevOps Serverless Workshop with new content: https://cicd.serverlessworkshops.io/


op_guide: highlight rbac setup

We need to highlight the rbac setup part just before creating the operator since it's easy to skim past the RBAC docs link in the overview.
A few users have already faced this problem and with rbac being default in k8s 1.6 this will become more common.
[skip ci]
/cc @hongchaodeng @xiang90

lgtm


JSON Schema preview is broken

Describe the bug
If I try to preview a JSON schema file which has no connection to AsyncAPI, I get a white page with black text that says only:

Error: The asyncapi field is missing.

How to Reproduce
Create a file test.schema.json with the following content:
{"$schema": "https://json-schema.org/draft-07/schema"}

Then click the "Preview AsyncAPI" button or Cmd+Shift+P (macOS) and select the option.

This appears to be identical to this issue from a similar plugin for IDEA.
Expected behavior
Either the preview option should be unavailable (because it doesn't work on this file type) or, even better, I should see a nice overview of the schema (assuming it was not trivial, like the example I gave).

@kbolino thanks for reporting this issue.
We will fix this disabling AsyncAPI preview for non asyncapi files.

So while debugging I found out that the isAsyncapi value could have caused the issue->
For asyncapi.yaml files

For asyncapi.json files

For non asyncapi files

So by just adding the following condition AsyncAPI preview will be disable for non asyncapi files ->

Also for best practices would prefer using parenthesis here ->

Should I open a pull request?


Handling duplicate elements in JSON payload

What is the best way with Json.NET to restrict occurrence of duplicate elements in JSON payload?
For example:
{
"role" : "default",
"username" : "mallory",
"role": "admin",
"password" : "Evil123!"
}

I would like to know how to do this using the JSON.NET schema library as well.

According to the spec as well:
2.2.  Objects
An object structure is represented as a pair of curly brackets
surrounding zero or more name/value pairs (or members).  A name is a
string.  A single colon comes after each name, separating the name
from the value.  A single comma separates a value from a following
name.  The names within an object SHOULD be unique.
  object = begin-object [ member *( value-separator member ) ]
  end-object

  member = string name-separator value

You will need to use JsonTextReader

We tried that.  The text reader does not restrict duplicates, in fact it
seems to allow them and uses the last property/value combination specified.
On Jun 6, 2016 5:28 PM, "James Newton-King"<EMAIL_ADDRESS>wrote:

You will need to use JsonTextReader
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/JamesNK/Newtonsoft.Json/issues/931#issuecomment-224093989,
or mute the thread
https://github.com/notifications/unsubscribe/AEXsnAuZRa6o5Bd4mTLbt_twpIwhuIjNks5qJJEDgaJpZM4IvInf
.

Oh I misunderstood. There is no way in Json.NET to restrict them. It will use the last value.

Seeing as the JSON spec indicates valid JSON should contain unique names
within an object it seems like this should be a feature of the
validation/schema library of JSON.NET?  Perhaps a feature request is in
order?
On Jun 6, 2016 6:09 PM, "James Newton-King"<EMAIL_ADDRESS>wrote:

Oh I misunderstood. There is no way in Json.NET to restrict them. It will
use the last value.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/JamesNK/Newtonsoft.Json/issues/931#issuecomment-224104005,
or mute the thread
https://github.com/notifications/unsubscribe/AEXsnNF-j9VzoT7x5IHyUAEzMosVJL1-ks5qJJqngaJpZM4IvInf
.

        try
        {
            var message =   "{" +
                                "\"DeviceAdded\" :" +
                                "{" +
                                    "\"DeviceId\" : \"SN123456\"," +
                                    "\"Protocols\" : []," +
                                    "\"DeviceType\" : \"UPS\"," +
                                    "\"Model\" : \"12345\"," +
                                    "\"HardwareVersion\" : \"<IP_ADDRESS>\"," +
                                    "\"FirmwareVersion\" : \"<IP_ADDRESS>\"," +
                                    "\"SoftwareVersion\" : \"<IP_ADDRESS>\"," +
                                    "\"SerialNumber\" : \"1\"," +
                                    "\"SerialNumber\" : \"456\"" +
                                "}" +
                            "}";

            var jobj = JsonConvert.DeserializeObject<JObject>(message);
            Console.WriteLine(jobj);
        }
        catch (Exception ex)
        {
            Console.WriteLine(ex.GetType());
            Console.WriteLine(ex.Message);
        }

If I use Newtonsoft.Json 6.0.8 I get exception System.ArgumentException: Can not add property SerialNumber to Newtonsoft.Json.Linq.JObject. Property with the same name already exists on object.
If I use Newtonsoft.Json 8.0.2 the code executes without error. What changed between these two versions? How with Newtonsoft.Json 6.0.8 I can get the same behavior as with Newtonsoft.Json 6.0.8?

What changed between these two versions? How with Newtonsoft.Json 6.0.8 I can get the same behavior as with Newtonsoft.Json 6.0.8?

A lot I suspect.  You've accidentally specified the same version twice in your sentence.

I would like 8.0.2 to behave as 6.0.8 in that when duplicate elements occurs in JSON payload an exception to be thrown. For example:
var message = "{" +
""role" : "default"," +
""username" : "mallory"," +
""role" : "admin"," +
""password" : "password!"" +
"}";
var jobj = JsonConvert.DeserializeObject(message);
Here "role" element occurs twice. In this case 6.0.8 will throw a System.ArgumentException exception, where 8.0.2 deserialize it successfully with admin value for the "role".

@JamesNK  My team would really like to be able to detect this case. Would you be amenable to a PR that adds a new JsonSerializerSettings option for switching between the current "accept last" behavior and "emit parse error" behavior?

I just found this issue too. I thought it was supposed to throw, and it didn't.

How can this functionality be employed by patterns that use JsonConvert.DeserializeObject? If it can't, I'd like to open an issue to add this functionality to JsonSerializerSettings.

see #1922:
JsonLoadSettings settings = new JsonLoadSettings { DuplicatePropertyNamesHandling = DuplicatePropertyNamesHandling.Throw }

How can this functionality be employed by patterns that use JsonConvert.DeserializeObject? If it can't, I'd like to open an issue to add this functionality to JsonSerializerSettings.

see #1922:
new JsonLoadSettings { DuplicatePropertyNamesHandling = DuplicatePropertyNamesHandling.Throw }

@mikhail-barg could you elaborate on how one can pass the JsonLoadSettings into JsonConvert.DeserializeObject, which, as I understand, only takes a string and JsonSerializerSettings as arguments?
public static T DeserializeObject<T>(string value, JsonSerializerSettings settings)

Thanks!

+1 for adding this as a property to JsonSerializerSettings.
I'm using Json.NET indirectly through ASP.NET Core, and I was surprised to see it behaving this way.

While we wait for JsonSerializerSettings to get this behavior, I have found this code to work:
public object SerializeObject(string json, JsonSerializerSettings settings)
{
	JsonSerializer jsonSerializer = JsonSerializer.CreateDefault(settings);
	using (var stringReader = new StringReader(json))
	using (var jsonTextReader = new JsonTextReader(stringReader))
	{
		JsonLoadSettings loadSettings = new JsonLoadSettings {
												DuplicatePropertyNameHandling = DuplicatePropertyNameHandling.Error
											};
		var jtoken = JToken.ReadFrom(jsonTextReader, loadSettings);
		return jtoken.ToObject<object>(jsonSerializer);
	}
}


refactor: purge aesop_cat_nonterminal

aesop_cat_nonterminal is a non-terminal variant of aesop. It's not supposed to be used in production code since it's even worse than non-terminal simp. However, there were a few occurrences left (presumably from the port), which this PR removes.
The only nontrivial change is that I add mathlib's rfl tactic to the CategoryTheory Aesop rule set.

Otherwise, LGTM.
bors d+

Thanks for the review!
bors r+


move Http directory

Move Http directory to be under app; correct use statements throughout application

#125
Will look into a few more Issues over the weekend.


Feature: Attrs functionality

while building a UI library with this I've run into a number of scenarios where I've wanted to have the attrs functionality that styled has. My use case doesn't require the complexity (or even dynamic capabilities) that styled has, I mainly just want be able to attach attributes to the element like, type, role, aria-*, etc.

any update on this?


Allow user driven Websocket compression

We want to allow the user to configure Websocket compression to be automatic or manual. In the latter case we need specific commands to send compressed frames, whereas normal frames would be uncompressed (or the reverse).

This is done in my local copy. Push later today!


Add Slaughterhouse X congratulations by Post x Crim3s

Song Name
Slaughterhouse X congratulations
Artist Name
Post x Crim3s
Source
Youtube
Youtube Link
3LEOTNE0h0s
Direct File Link
No response
Song ID
945695
Start Offset [ms]
0.9
Extra
Created from Auto Nong.
Created for level: 27690100
Downloaded: No

Comment

Didn't mean to close with comment

Erm can it reopen?


Replace logging system in proxy

The logging should be cleaned up in a major way. Some of the logging should be removed and replaced with prometheus statuses. The remaining logs should use appropriate log level (Info, Debug, Error, etc). Also consider using a different library if the core golang logging is insufficient.

Check out some alternates to core logging library (see if there's a good reason to switch). Also, remove logs that were just for coding, only have info, debug, etc that will be useful in prod.


Fix mypy failure: set plt.subplots squeeze=False in _image.py

Fixes a build failure introduced by the new types hints in matplotlib 3.9.1.
_image.py uses f, axs = plt.subplots(nrows=nrows, ncols=cols). Mypy determines with the new matplotlib type hints that axs will be a ndarray (expected in our case) or an Axes object (if nrows==ncols==1), and complains that our code will fail in the latter case.
Passing squeeze=False to plt.subplots ensures that axs is always a numpy array.

@CloseChoice FYI, it would be good to get this one reviewed/merged, as the build is currently broken on all PRs

Note to self- it would be great to have some more comprehensive tests for the image plot.


Results progressively slower

We have written the needed data into your clipboard because it was too large to send. Please paste.
Issue Type: Performance Issue
one sql window, with 2 or more different sql statements
highlight one, and execute
hightlight the next, execute
repeat, and results become slower and slower to appear on screen
with the results rows being blank, and then eventually populating
and eventually to the stage where results section does not appear for several minutes but the messages section does
execution time in message does not change
Azure Data Studio version: azuredatastudio 1.6.0 (eb35dae1d1238e03f1cab3bd45e151f381b22aef, 2019-04-17T07:11:15.944Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700T CPU @ 2.80GHz (8 x 2808)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.89GB (8.16GB free)

Process Argv

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    1	   123	 17724	azuredatastudio main
    0	   470	  7996	   gpu-process
    0	    55	 17440	   shared-process
    0	   240	 21760	   window (● contributions_transfer_in.sql - ps-test-rds.DEV_puntersouthall (Integrated) - Azure Data Studio)
    0	   109	 22968	     extensionHost
    0	    20	  7868	       "c:\Users\Nigel\AppData\Local\Programs\Azure Data Studio\resources\app\extensions\mssql\sqltoolsservice\Windows\1.5.0-alpha.85\MicrosoftSqlToolsCredentials.exe" --log-file C:\Users\Nigel\AppData\Roaming\azuredatastudio\mssql\credentialstore_22968.log --tracing-level Critical
    0	     5	 19988	         console-window-host (Windows internal process)
    0	    21	 14228	       "c:\Users\Nigel\AppData\Local\Programs\Azure Data Studio\resources\app\extensions\mssql\sqltoolsservice\Windows\1.5.0-alpha.85\SqlToolsResourceProviderService.exe" --log-file C:\Users\Nigel\AppData\Roaming\azuredatastudio\mssql\resourceprovider_22968.log --tracing-level Critical
    0	     6	 15156	         console-window-host (Windows internal process)
    0	    99	 22724	       "c:\Users\Nigel\AppData\Local\Programs\Azure Data Studio\resources\app\extensions\mssql\sqltoolsservice\Windows\1.5.0-alpha.85\MicrosoftSqlToolsServiceLayer.exe" --log-file C:\Users\Nigel\AppData\Roaming\azuredatastudio\mssql\sqltools_22968.log --tracing-level Critical
    0	     5	 21492	         console-window-host (Windows internal process)
    0	    77	 24016	   window (Issue Reporter)

Workspace Info
;

Extensions: none

Do you have any information on what type of queries you are running to exhibit this behaviour? I can't seem to repro using just generic select all statements.


Scrolling animation in scrollview.py not working on android

The animation handling in scrollview.py widget does noet work, because the touch.dx and touch.dy are always zero. Scrolling works, but immediately stops when touch_up event is received.
Version info:
Kivy launcher <IP_ADDRESS>
android 3.1
Galaxy tab 10.1
On a HTC phone it does work good.
Can also be seen in the settings screen, the list of settings can be scrolled but animation after touch does not work.

I can confirm that I also have the last touch dx/dy = 0 problem with a touchscreen on windows. Let me know if I can help debug something.

Ok then, with or without this issue, i think that someone should really help with math. Using the last event is leading to issues like this. It should be more something like accumulating the change during 1s. Then if it's released, check what's the acceleration / speed, in which direction. And continue the scrolling according to it.

But there might also be a bug in the events which are not mouse events. As I found out, the same touch object has the right dx, dy values, while in the on_touch_move callback, but once he gets sent to on_touch_up touch.dx/dy are reset to 0 and touch.time_end is set at -1. A dirty fix which works for me is storing the dx/dy/ in touch_move and then in on_touch_up if end_time == -1 retrieve the stored values. At least this workaround works for me on windows and android samsung galaxy tab.
Naturally doing more advanced calculation could give a better feel

Ok, you just point to 2 differents issues that should be not messed up :)
The time_end = -1 seem to be the case for all the input providers except mouse provider. Thanks for this, i'll open an new issue in order to fix it properly.
As for dx/dy, if you got 2 touch move at the same position, it's normal that the dx/dy is going to 0, because their is no movement between last and current touch. And it can be also the case for a touch up. Even if you think that you're doing a big/fast movement, an hardware event can be at the same position at the end. So it's not something we must rely.
I've found an article about kinectic scrolling implementation within Qt: http://www.developer.nokia.com/Community/Wiki/Qt_Kinetic_scrolling_-_from_idea_to_implementation
Even if it look ok, their real implementation is far more complex: http://qt.gitorious.org/qt-labs/kineticscroller/blobs/7f241982bf395fa703d8c0c91fa4e7e25085cca3/scroller/qkineticscroller.cpp
Started to implement the new way, need to test on android now.

hello tito, i had no time last weeks.... is there something testable now on android, if so please give some pointers....


Naming: Document as an MD file in /docs

Description

[ ] Document as an MD file in /docs

[ ]

[ ]

References #46

https://github.com/retaildevcrews/ngsa/blob/naming-convention/docs/NamingConvention.md


Separate tests into different suites based on WG-owned tests

Based on ideas from https://docs.google.com/document/d/1wpSUSuTjNP95jL2WuQ4sMO4v7tt1U0Gabw4xlAqHCH0/ this issue would cover

Splitting out e2es to better determine what failed and allow the ability to run only certain suites locally
Provide WG owned dashboards to track flakiness/general test health
- k8s SIG-Network e2e example

Steps:

[ ] Review k8s framework setup to see how we can re-use the same istio setup for multiple runs
[ ] Split auth tests & other special environments into separate setup suites
[ ] Create spreadsheet with WG owned tests
[ ] Decorate tests and separate into separate suites with relevant framework setup
[ ] Update testgrid to organize WG tests into different dashboards

Need a bit of context on the work. Is there a existing model we want to follow (references)? What's coming out this? Does it help with better triaging? or solving some specific problems today?

@xiaolanz Added more context in description

Tests should be populated now by related PRs, closing this issue for now


os.getenv not work in custom plugin

handler.lua
function CtgLogHandler:log(conf)
  CtgLogHandler.super.log(self)

  --  os.getenv("PATH")  not work, eq nil
  ngx.log(ngx.DEBUG, "[ctg-log] env - path: ", os.getenv("PATH"))

  local ok, err = timer_at(0, log, conf, serializer.serialize(ngx))
  if not ok then
    ngx.log(ngx.ERR, "[ctg-log] could not create timer: ", err)
  end
end

I can not get my environment variables in handler.lua of custom plugin.

You need to add env PATH to your nginx.conf / Kong template file.
env PATH;

Hi,
Indeed @jeremyjpj0916 is right, this is an expected behaviour from Nginx, which only adds declared environment variables to the worker processes environ variable.
BTW, better avoid calling such non JIT-able functions like os.getenv in hot-code paths and cache them somewhere instead (like the top-level chunk of your Lua module for example).


consistent air temperature naming

A lot of pvlib uses the term temp_air for ~2 m air temperature. The get_solarposition function (perhaps among others) uses temperature, which causes some confusion (see https://github.com/pvlib/pvlib-python/pull/893#issuecomment-587052032). We should standardize the naming.
My vote is temperature. I really dislike temp_air.
Note that MetPy recently went through a similar parameter name refactoring and chose temperature (among other things): https://github.com/Unidata/MetPy/pull/1299

I'm okay with temperature for dry bulb temperature, and then just dew_point for dew point temperature. Are there any other potential conflicts?

I can accede to temperature for ambient temperature for compatibility with metpy and I'm OK with dew_point. We should also agree on names for the other temperature quantities: cell temperature (currently temp_cell in functions, cell_temperature attribute of ModelChain), module temperature (unnamed), (future) inverter temperature (unnamed). Do we distinguish between dry-bulb and wet-bulb air temperatures?

I guess I prefer cell_temperature but I think a style guide is appropriate here:

One style seems to be the main property name first, eg: temp subscripted by some qualifier like _air or _cell
The other style seems to be more verbose and just uses plain human readable terms, replacung spaces with underscores like, cell_temperature, absolute_airmass, or dew_point

We should just pick a style, explain it as best as we can, ask that it be followed, keep a record of standardized terminology, and hope that it's mostly general enough. Sound good? This could possibly be a GSoC task, but maybe too easy?

@mikofski I generally prefer the first style you list but with the qualifier to be first. This makes it easier to find the variable in an IDE's auto-completion when you might have six different temperatures in the form temp_xyz, temp_abc, etc. as opposed to typing x + TAB and getting right to xyz_temp.
I'm fine with your second style as long as a third full length word isn't added to the snake-cased variable. Sometimes it really helps to have it easily human readable.
If I see just temperature I immediately wonder "what temperature?". Having the qualifier without having to base it on the context of the function is preferable.

To be clear, I only care about naming for the public API. Use whatever you want within functions so long as it's readable.

The other style seems to be more verbose and just uses plain human readable terms, replacung spaces with underscores like, cell_temperature, absolute_airmass, or dew_point

+1
I think we're safe to assume that temperature or air_temperature is a dry bulb temperature. I'm not aware of any functions that care about wet bulb temperature.
I also prefer dew_point over dew_point_temperature

I think it would help to compile a glossary of what's currently used in the API, by topic. I can take a crack at that.


Blm Auto-rotation

I tried this on my black mage that was only lvl 50, it seemed to work fine....... then i level skipped to 80, now it will not load, is there something I can do to fix this?

Monk is in the same state as blm - was working up to L50 last time I checked (few months ago), but nowhere near polished.
Don't think there's any way to expedite that - I'm writing modules as I'm leveling classes. Next would be DRG, then probably BLM.


Feature/add redux toolkit

React Boilerplate
Thank you for contributing! Please take a moment to review our contributing guidelines
to make the process easy and effective for everyone involved.
Please open an issue before embarking on any significant pull request, especially those that
add a new library or change existing tests, otherwise you risk spending a lot of time working
on something that might not end up being merged into the project.
Before opening a pull request, please ensure:

[x] You have followed our contributing guidelines
[x] Double-check your branch is based on dev and targets dev
[x] Pull request has tests (we are going for 100% coverage!)
[x] Code is well-commented, linted and follows project conventions
[x] Documentation is updated (if necessary)
[x] Internal code generators and templates are updated (if necessary)
[x] Description explains the issue/use-case resolved and auto-closes related issues

Be kind to code reviewers, please try to keep pull requests as small and focused as possible :)
IMPORTANT: By submitting a patch, you agree to allow the project
owners to license your work under the terms of the MIT License.
Details
This PR demonstrates how to convert part of the built-in example application to use Redux Toolkit, as described in #2806 .
It is not meant to be complete and merged as-is, but rather to serve as a starting point for conversion if the maintainers choose.
Changes

Added Redux Toolkit
Removed the explicit dependency on Redux, since RTK re-exports everything.  (I also attempted to remove the Immer and Reselect dependencies, but saw that there were other reducers that currently depend on Immer, and a couple components that depend on Reselect's createStructuredSelector, so I re-added those explicit dependencies.)
Converted the store setup logic in configureStore.js to use RTK's configureStore method
Added a new containers/App/appSlice.js file that contains equivalent logic to the existing App/reducers.js and App/actions.js files
Modified other uses of App/actions to use the action creators exported by appSlice.js
Removed obsolete store setup tests that checked for calling the DevTools Extension global API

I have some other changes I'd like to suggest as well, which I'll write up in the issue rather than here.

Looking at the Travis logs, it appears that the tests themselves are passing, but the global code coverage stats have fallen below a 98% threshold.

Hey it's the redux overlord! Thanks for this, tbh I have no idea what redux-toolkit even is so this will be cool to take a look at.

I'd like to turn the PR over to you folks at this point.  You know the react-boilerplate codebase and requirements way better than I do, and I have my own priorities atm (like rewriting most of the Redux docs).
Happy to answer any questions about using RTK as you work through this, though!

hi @markerikson thank you for this PR!

Reselect might not be removable, given that there are uses of createStructuredSelector, which RTK does not re-export

i don't think it's a huge deal to keep reselect dependency, but would you consider adding createStructuredSelector to RTK exports? maybe in a utility export with other commonly used tools from libs, such as redux's compose?

We do re-export everything from Redux already.
I'd like to avoid explicitly re-exporting createStructuredSelector for now.  If someone really needs it, they can just declare the dependency on Reselect themselves.  Since RTK already pulls that in, it's just adding another entry to package.json.

I'm merging this into a React Boilerplate branch called redux-toolkit so we can continue working there.

See #2808 for ongoing work into this.


Automatically close hamburger after selecting an option

Problem:
Currently, when using the hamburger menu, after selecting an option, the menu remains open, which can be inconvenient and disrupt the user experience.
Solution:
Implement automatic closure of the hamburger menu upon selecting an option, enhancing user flow and ensuring a smoother navigation experience.

can you add a level of this task @Suchitra-Sahoo

@Suchitra-Sahoo I also want to work on that

@Suchitra-Sahoo please assign the level of isssue like level1,level2,level3

Thank you for assigning me this task. I have completed it. Please check the pull request and also add a level label on this issue. @Suchitra-Sahoo

Add Level Please @Suchitra-Sahoo


Website not showing

Click here link is not working
It shows 404 error

I'm glad you noticed and pointed out that I put the wrong link, I have corrected it.


string expected, got nil

I was trying to test vLuau by running a script like this:
local loadstring = require(workspace.needed.MainModule)

function Test()
print("Hello world!")
print("Test1C")
wait(0.1)
print(math.min(1)+1)
print("Test2C")
wait(0.1)
print(math.pi)
print(1*9*100)
	print("All completed.")
end

loadstring(Test())

but it kept getting the error:
workspace.needed.MainModule:52: invalid argument #2 to 'unpack' (string expected, got nil)
what does this mean and how to fix the issue?

Arguments should be only strings.
Your usage is wrong.

local loadstring = require(workspace.needed.MainModule)

loadstring([[
function Test()
print("Hello world!")
print("Test1C")
wait(0.1)
print(math.min(1)+1)
print("Test2C")
wait(0.1)
print(math.pi)
print(1*9*100)
	print("All completed.")
end
]])()


Adjust entity fields

Goal

Adjust the various fields in entities to ensure that are correctly set to nullable etc
Requirements

Set User's username, email and password to be not nullable

Extra notes

Design

Closed due to moving issues to Jira (issue)


Issue 219

closes #219 by combining relationship names from both models into one connection string.

@keonik Could you please consider making an alpha release with this fix?

I will push as is but the relationship for many to x is messed up for sure. I haven't had time to work on it for a while. Meaning alpha will not be published for a bit


Ubuntu 16.04 cuda dependency issue

Required Info

Camera Model
{ D435 }

Firmware Version
(<IP_ADDRESS>)

Operating System & Version
Ubuntu 16- Xenial

Kernel Version (Linux Only)
(e.g. 4.15)

Platform
PC

SDK Version
{ 2.x- latest one  }

Language
{C }

Segment
{Robot }

Issue Description
When i try to install from source or through   the debian package i get this error.
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
cuda-libraries-dev-10-1 : Depends: libcublas-dev (>= <IP_ADDRESS>) but it is not installable
cuda-samples-10-1 : Depends: libcublas-dev (>= <IP_ADDRESS>) but it is not installable
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

Hi, same problem here. How did you fixed it?