[mesh validate] Race condition failing validation for multiple services

Describe the bug

Validation for multiple services runs in parallel, but only the validation errors of a single service are reported (the one which fails first).
To Reproduce
Steps to reproduce the behavior:

Find/Create two invalid APIs¹ (e.g. OpenAPI) - (sorry can't share and those are hard to find in public)
Add them to a new meshrc.yml config
mesh build && mesh validate

Expected behavior

Continue listing all validation errors of all services after the first one failed, ending with a list of services, which schema validations failed.
(Also validation is missing a success message.)
Environment:

OS: node:14-alpine or macOS
<EMAIL_ADDRESS>NodeJS: 14

Additional context

Discovered when trying mesh validation on internal services: https://github.com/Urigo/graphql-mesh/issues/2606
¹ Invalid source schemas might need to be similar in sizes for the race condition to be flaky

Could you try with the canary versions released by the CI for this PR;
https://github.com/Urigo/graphql-mesh/pull/2850#issuecomment-926594572

mesh validate
🕸: Reading Mesh configuration
🕸: Generating Mesh schema
🕸: Artifacts has¹ been validated successfully

¹Fix grammar: have been
The failures list looks good, and next time I try that DEBUG flag ;)

I think this has been released by now :)


Docker requirement 20.10

I want to suggest to add the docker version requirements to the documentation: https://spatie.be/docs/ray/v1/environment-specific-configuration/docker
I use Ubuntu and I had docker 19.03 installed and that did not work. I then updated to 20.10 and that worked.

There's an edit button on the page, feel free to PR improvements 👍

There's an edit button on the page, feel free to PR improvements 👍


terraform1

I have my .pem file in my cookbook and still mentioned in kitchen.yaml too

you ssh key is not identified by kitchen, so mention path like this ssh_key: ./terraform1.pem


feat: Add support for running Azure CNI without Overlay Networking Enabled

Tell us about your request
Karpenter users should be able to use the Azure CNI without overlay networking.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Currently the only part that karpenter needs to do differently for this support is to generate additional ip configurations for IPAM to consume on the nics we create.
Are you currently working around this issue?
no existing workarounds
Additional Context
No response
Attachments
No response
Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

See more details in the PR description linked.

@Bryce-Soghigian I just want to thank you for this work you are doing. I honestly can't wait for this to be done 😄

this is a blocker issue for us. Azure Application Gateway cannot be used when  azure-cni with overlay is enabled. hopefully it gets resolved soon.


Limits entry is not emitted when attaching files

Bug Report
Limits entry is not emitted when attaching files due to incompatibility with Adobe Reader
Description of the problem
See info at https://github.com/foliojs/pdfkit/pull/1226
We should evaluate if is possible to implement file attachment in a more compliant way

I modified the demo/attachment.js test script (source here) to reproduce this issue with a second embedded file (resulting pdf here, then validated it with verapdf's PDF/A-3A validation profile, this is the result.
(Github doesn't allow .js or .xml uploads, so those files are uploaded as .txt instead)
A few issues came up with the embedded files (some of which should probably be fixed), but none of them mentioned the missing /Limits key. Is it possible verapdf doesn't check for that?
I can not create the same pdf with Adobe Acrobat, because embedding files seems to be a paid feature.
The free version can only add files with annotations, which as far as I know doesn't add entries to the /EmbeddedFiles dictionary anyways.
Here is a pdf with multiple embedded files created with Foxit Reader instead, which also opens correctly in Adobe Reader.
If you (or anyone else) want to take a closer look at the pdf created with Foxit, I recommend these PDF Tools to make sense of the compressed /ObjStm at 20 0 obj, it includes the /Pages and /EmbeddedFiles dictionaries.
Anyways, these are the contents of that Object stream:
"1 0 2 37 6 81 8 125 13 229 14 290 16 362 17 429 19 505
<</Type/Pages/Kids[ 7 0 R ]/Count 1>>
<</Dests<</Names[]>>/EmbeddedFiles 17 0 R >>
<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]>>
<</ModDate(D:20210326135820+01'00')/Producer 9 0 R /Title 12 0 R /Creator 10 0 R /CreationDate 11 0 R >>
<</Fields[]/DA(/Helv 0 Tf 0 g)/DR<</Font<</Helv 14 0 R >>>>>>
<</BaseFont/Helvetica/Encoding/WinAnsiEncoding/Subtype/Type1/Type/Font>>
<</UF(test.png)/EF<</F 15 0 R >>/Desc()/F(test.png)/Type/Filespec>>
<</Names[(\xfe\xff\x00C\x00H\x00A\x00N\x00G\x00E\x00L\x00O\x00G\x00.\x00m\x00d) 19 0 R (\xfe\xff\x00t\x00e\x00s\x00t\x00.\x00p\x00n\x00g) 16 0 R ]>>
<</UF(CHANGELOG.md)/EF<</F 18 0 R >>/Desc()/F(CHANGELOG.md)/Type/Filespec>>"

I believe the <</Names[(\xfe… part is the /EmbeddedFiles dictionary, and it seems to not include /Limits in here either - did the specification on Name Trees change so that Limits is not required anymore?
Maybe it's not actually an issue if Foxit Reader is doing the same thing.

Maybe it's not actually an issue if Foxit Reader is doing the same thing.

Yes. its a possibility. Just want to keep track


Set up React Native structure and install primary dependencies for MVP

Look into example/best-practice structure

@tiffeli too

In order to do multiple pages, we'll need some sort of routing plugin (probably react-router-redux)


rustc proxy may fail to invoke a rustc using shared libraries even when LD_LIBRARY_PATH is set.

Problem
I have a custom Rust toolchain for development installed locally, call it rust-shared. I run it by setting LD_LIBRARY_PATH whenever I need to e.g. invoke the rustup cargo proxy. In the past, rustup has been able to call my custom Rust toolchain just fine, including locating its shared libraries. However, as of a recent release (I don't know which), I've found that rustup is inconsistent as to whether invoking my custom rustc will succeed or fail to find its shared libraries even when LD_LIBRARY_PATH has been set previously.
This behavior is inconsistent, but I've found a way to trigger the problem consistently via a contrived sequence.
Steps
Prerequisites

Compile a rustc using a shared LLVM :).
Add this toolchain to rustup via rustup toolchain link shared-rust /path/to/rust/root
Create a sample crate, e.g. cargo init --lib testing
Compile the crate using your shared toolchain: LD_LIBRARY_PATH=/path/to/llvm/libs cargo +shared-rust build. This should succeed.

rustup Seems To Find Shared Libraries Without LD_LIBRARY_PATH
Up to this point, all commands have expected behavior for me. Steps 5 and 6 have odd behavior to me.

Run cargo +shared-rust clean once without setting LD_LIBRARY_PATH. This succeeds on my machine. I would not expect this to succeed because I didn't specify where the shared libraries for rustc live. I've accidentally forgotten to set LD_LIBRARY_PATH a number of times in normal usage :).
Run cargo +shared-rust clean again without setting LD_LIBRARY_PATH. This fails with "error while loading shared libraries", which is the behavior I expected in step 5.

rustup Seems To Disregard LD_LIBRARY_PATH
If I rebuild the crate using +shared-rust at this point, compilation will still succeed. However, the next set of commands will result in shared-rust not finding its shared libraries.

Run cargo +nightly build. This should succeed just fine.

Run cargo +shared-rust clean once without setting LD_LIBRARY_PATH. This fails with "error while loading shared libraries" on my machine, as I would expect.

We've already shown in step 4 that compilation with shared-rust works. However, when I attempt to run LD_LIBRARY_PATH=/path/to/llvm/libs cargo +shared-rust build or LD_LIBRARY_PATH=/path/to/llvm/libs cargo +shared-rust clean after running steps 7 and 8, I get the following error:
william@xubuntu-dtrain:~/Projects/toolchains/testing$ LD_LIBRARY_PATH=$SHARED_LLVM_LIBS cargo +shared-rust build
error: process didn't exit successfully: `rustc -vV` (exit status: 127)
--- stderr
/home/william/.rustup/toolchains/shared-rust/bin/rustc: error while loading shared libraries: libLLVMX86AsmParser.so.12: cannot open shared object file: No such file or directory

Notice that I explicitly set LD_LIBRARY_PATH, yet rustc still can't find its shared libraries!

Running cargo +nightly clean or cargo +nightly build makes compilation with shared-rust functional again, like in step 4.

Possible Solution(s)
I'm personally unsure how to debug this further. It seems that cargo +toolchain clean is the trigger to switch rustup's state between "will find the shared libraries" versus "will not find the shared libraries". I think the inconsistent behavior I saw in step 5 and 6 is related, as its perhaps "toggling" some internal state in rustup?
Running LD_LIBRARY_PATH=/path/to/llvm/libs cargo +shared-rust clean does not trigger the above behavior in steps 5 and beyond, unless we're already in the "rustc has decided not to find its shared libraries" state, like in step 9.
Notes
System Information:
william@xubuntu-dtrain:~/Projects/toolchains/rust$ uname -a
Linux xubuntu-dtrain 5.4.0-72-generic rust-lang/rustup#80-Ubuntu SMP Mon Apr 12 17:35:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

william@xubuntu-dtrain:~/Projects/toolchains/rust$ rustup -V
rustup 1.24.1 (a01bd6b0d 2021-04-27)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.53.0-nightly (9d9c2c92b 2021-04-19)`

william@xubuntu-dtrain:~/Projects/toolchains/rust$ cargo +nightly -Vv
cargo 1.53.0-nightly (65d57e6f3 2021-04-04)
release: 1.53.0
commit-hash: 65d57e6f384c2317f76626eac116f683e2b63665
commit-date: 2021-04-04

william@xubuntu-dtrain:~/Projects/toolchains/rust$ rustc +nightly -Vv
rustc 1.53.0-nightly (9d9c2c92b 2021-04-19)
binary: rustc
commit-hash: 9d9c2c92b834c430f102ea96f65119e37320776e
commit-date: 2021-04-19
host: x86_64-unknown-linux-gnu
release: 1.53.0-nightly
LLVM version: 12.0.0

william@xubuntu-dtrain:~/Projects/toolchains/rust$ LD_LIBRARY_PATH=$SHARED_LLVM_LIBS rustc +shared-rust -Vv
rustc 1.54.0-dev
binary: rustc
commit-hash: unknown
commit-date: unknown
host: x86_64-unknown-linux-gnu
release: 1.54.0-dev
LLVM version: 12.0.0

shared-rust is rustc 1.54.0-dev, commit e5f83d24aee. I can provide cmake invocations for LLVM and the config.toml I used to build upon request.

tl:dr: To repro just chmod a-x your/rustc, cargo clean then cargo build, now it's cached, do chmod u+x your/rustc, run cargo build, same (cached)error.

This cache reusal in step 9, I'm seeing it happen for my rustc, if I run it too quickly, without doing a cargo clean first, it caches that this Permission denied happened because not all dirs have execute attribute yet:
error: process didn't exit successfully: `/home/user/sandbox/rust/05_sandbox/tests/exit1/myrust -vV` (exit status: 126)
--- stderr
/home/user/sandbox/rust/05_sandbox/tests/exit1/myrust: line 10: /var/tmp/portage/dev-lang/rust-1.76.0-r1/work/rustc-1.76.0-src/build/x86_64-unknown-linux-gnu/stage1/bin/rustc: Permission denied

but then later when the dirs have all the right permissions, it re-uses that cache and keeps displaying it, so I've to either cargo clean or delete target/.rustc_info.json then it picks up the changes.


feat(mdi-icon): version 5.4.55

General summary
Update the mdi dependency to the version 5.4.55
New icon is required for new development
Screenshots
Check list

[ ] (if has style) Add need: review-integration label
[ ] (if has textual documentation) Add need: review-doc label
[x] (if has code) Add need: review-frontend label
[ ] (if has react) Check through the react dev check list
[ ] (if fix or feature) Add need: test label

Check out the contribution guide for general guidelines for submissions to the design system.

@gcornut ok, should we manually add aliases?
Is there a changelog?

@gcornut ok, should we manually add aliases?
Is there a changelog?

It could be a solution but I have no idea where or if these changes are logged


Release: v0.7.1

cc @lvwerra

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


chore(deps): update module github.com/cloudflare/cloudflare-go to v0.104.0

This PR contains the following updates:

Package
Type
Update
Change

github.com/cloudflare/cloudflare-go
require
minor
v0.25.0 -> v0.104.0

Release Notes

cloudflare/cloudflare-go (github.com/cloudflare/cloudflare-go)
v0.104.0
Compare Source
BREAKING CHANGES:

dns: removed deprecated ZoneID and ZoneName fields (#2986)

ENHANCEMENTS:

bot_management: add ai_bots_protection to public API (#2974)

DEPENDENCIES:

deps: bumps golang.org/x/net from 0.28.0 to 0.29.0 (#3030)
deps: bumps golang.org/x/time from 0.5.0 to 0.6.0 (#2816)

v0.103.0
Compare Source
ENHANCEMENTS:

errors: implement the Unwrap method for custom error types to access the wrapped errors via errors.Is and errors.As (#2857)
rulesets: add "contains" field to custom cache key header (#2935)
teams_certificates: renamed enabled to in_use (#2937)
waiting_room: add support for enabled_origin_commands (#2931)

DEPENDENCIES:

deps: bumps github.com/urfave/cli/v2 from 2.27.3 to 2.27.4 (#2863)

v0.102.0
Compare Source
ENHANCEMENTS:

rulesets: Add DeleteRulesetRule (#2833)
rulesets: Export DeleteRulesetRuleParams fields (#2886)
teams_accounts: Add disable_for_time attribute (#2797)

DEPENDENCIES:

deps: bumps golang.org/x/net from 0.27.0 to 0.28.0 (#2835)

v0.101.0
Compare Source
ENHANCEMENTS:

access_application: add skip_app_launcher_login_page flag to skip the App Launcher landing page (#2793)
device_posture_rule: support extended_key_usage, check_private_key, and locations for client_certificate_v2 posture rule (#1685)
devices_policy: Add new tunnel_protocol field to policy (#2778)
risk_score_integration: Add support for Risk Score Integrations (#2786)

DEPENDENCIES:

deps: bumps github.com/urfave/cli/v2 from 2.27.2 to 2.27.3 (#2787)

v0.100.0
Compare Source
BREAKING CHANGES:

teams_accounts: rename TeamsCertificate in TeamsAccountConfiguration to TeamsCertificateSetting (#2754)

ENHANCEMENTS:

Add CloudConnectorAPI Client (#2698)
gateway_categories: add ListGatewayCategories which returns all gateway categories. (#2722)
teams_certificates: add TeamsCertificate resource to manage gateway certificates (#2754)

DEPENDENCIES:

deps: bumps dependabot/fetch-metadata from 2.1.0 to 2.2.0 (#2727)
deps: bumps golang.org/x/net from 0.26.0 to 0.27.0 (#2726)

v0.99.0
Compare Source
ENHANCEMENTS:

teams: added per account certificate setting to teams gateway configuration (#2713)
teams_list: Added description to ZT list item (#2621)
teams_rules: Added ZT rule settings ignore_cname_category_matches (#2621)

DEPENDENCIES:

deps: bumps github.com/hashicorp/go-retryablehttp from 0.7.1 to 0.7.7 (#2699)

v0.98.0
Compare Source
ENHANCEMENTS:

access_application: Add support for SaaS OIDC Access Token Lifetime (#2455)

DEPENDENCIES:

deps: bumps golang.org/x/net from 0.25.0 to 0.26.0 (#2364)
deps: bumps goreleaser/goreleaser-action from 5.1.0 to 6.0.0 (#2365)

v0.97.0
Compare Source
ENHANCEMENTS:

access_application: Add support for Hybrid/Implicit flows and options (#2131)
teams_account: Add Zero Trust connectivity settings (#2165)
teams_accounts: Add use_zt_virtual_ip attribute (#2126)

DEPENDENCIES:

deps: bumps github.com/goccy/go-json from 0.10.2 to 0.10.3 (#2107)
deps: bumps github.com/hashicorp/go-retryablehttp from 0.7.6 to 0.7.7 (#2249)

v0.96.0
Compare Source
ENHANCEMENTS:

access_application: Add Refresh Token, Custom Claims, and PKCE Without Client Secret support for OIDC SaaS configurations (#1981)
ruleset: add support for action parameters fonts and disable_rum (#1832)

DEPENDENCIES:

deps: bumps bflad/action-milestone-comment from 1 to 2 (#1991)
deps: bumps github.com/hashicorp/go-retryablehttp from 0.7.5 to 0.7.6 (#1993)
deps: bumps goreleaser/goreleaser-action from 5.0.0 to 5.1.0 (#1992)

v0.95.0
Compare Source
ENHANCEMENTS:

access_application: add support for policies array (#1956)
access_application: add support for scim_config (#1921)
access_policy: add support for reusable policies (#1956)
dlp: add support for zt risk behavior configuration (#1887)

BUG FIXES:

access_application: fix scim configuration authentication json marshalling (#1959)

DEPENDENCIES:

deps: bumps dependabot/fetch-metadata from 2.0.0 to 2.1.0 (#1839)
deps: bumps github.com/urfave/cli/v2 from 2.27.1 to 2.27.2 (#1861)
deps: bumps golang.org/x/net from 0.24.0 to 0.25.0 (#1974)
deps: bumps golangci/golangci-lint-action from 4 to 5 (#1845)
deps: bumps golangci/golangci-lint-action from 5 to 6 (#1975)

v0.94.0
Compare Source
ENHANCEMENTS:

access_application: support options_preflight_bypass for access_application (#1790)
gateway: added ecs_support field to teams_location resource (#1826)
teams_account: adds custom certificate setting to teams account configuration (#1811)
workers: support deleting namespaced Workers (#1737)

DEPENDENCIES:

deps: bumps golang.org/x/net from 0.19.0 to 0.23.0 (#1825)

v0.93.0
Compare Source
BREAKING CHANGES:

dns: Remove "locked" flag which is always false (#1618)

ENHANCEMENTS:

magic_transit_ipsec_tunnel: Adds support for replay_protection boolean flag (#1710)

DEPENDENCIES:

deps: bumps golang.org/x/net from 0.22.0 to 0.24.0 (#1688)

v0.92.0
Compare Source
ENHANCEMENTS:

dlp: Adds support for ocr_enabled boolean flag (#1600)

BUG FIXES:

teams_rules: add "resolve" to allowable actions (#1615)

DEPENDENCIES:

deps: bumps dependabot/fetch-metadata from 1.6.0 to 1.7.0 (#1593)
deps: bumps dependabot/fetch-metadata from 1.7.0 to 2.0.0 (#1607)

v0.91.0
Compare Source
ENHANCEMENTS:

access_application: add support for saml_attribute_transform_jsonata in saas apps (#1562)

DEPENDENCIES:

deps: bumps actions/checkout from 2 to 4 (#1573)
deps: bumps google.golang.org/protobuf from 1.28.0 to 1.33.0 (#1558)

v0.90.0
Compare Source
ENHANCEMENTS:

access_mutual_tls_certificates: add support for mutual tls hostname settings (#1516)
device_posture_rule: support last_seen and state for crowdstrike_s2s posture rule (#1509)
dlp: add support for Context Awareness in DLP profiles (#1497)
workers: Add Workers for Platforms support for getting a Worker, content and bindings (#1508)
workers_for_platforms: Add ability to list Workers for Platforms namespaces, get a namespace, create a new namespace or delete a namespace. (#1508)

BUG FIXES:

dlp: added optional ContextAwareness support (#1510)

DEPENDENCIES:

deps: bumps github.com/stretchr/testify from 1.8.4 to 1.9.0 (#1511)
deps: bumps golang.org/x/net from 0.21.0 to 0.22.0 (#1513)

v0.89.0
Compare Source
NOTES:

zaraz: replace deprecated neoEvents with Actions on Zaraz Config tools schema (#1490)

ENHANCEMENTS:

magic-transit: Adds IPsec tunnel healthcheck direction & rate parameters (#1503)

BUG FIXES:

registrar: Fix request method to call domain list endpoint from POST to GET (#1506)

v0.88.0
Compare Source
ENHANCEMENTS:

access_application: Add support for OIDC SaaS Applications (#1500)
access_application: Add support for allow_authenticate_via_warp (#1496)
access_application: add support for name_id_transform_jsonata in saas apps (#1505)
access_organization: Add support for allow_authenticate_via_warp and warp_auth_session_duration (#1496)
hyperdrive: Add support for hyperdrive CRUD operations (#1492)
images_variants: Add support for Images Variants CRUD operations (#1494)
teams_rules: AntiVirus settings includes notification settings (#1499)

BUG FIXES:

hyperdrive: password should be nested in origin (#1501)

DEPENDENCIES:

deps: bumps golang.org/x/net from 0.20.0 to 0.21.0 (#1502)
deps: bumps golangci/golangci-lint-action from 3 to 4 (#1504)

v0.87.0
Compare Source
ENHANCEMENTS:

access_seats: Add UpdateAccessUsersSeats with an array as input for multiple operations (#1480)
dlp: add support for EDM and CWL datasets (#1485)
logpush: Add support for Output Options (#1468)
pages_project: Add build_caching attribute (#1489)
streams: adds support for stream create parameters for tus upload initiate (#1386)
teams_accounts: add support for extended email matching (#1486)

BUG FIXES:

access_seats: UpdateAccessUserSeat: fix parameters not being an array when sending to the api. This caused an error when updating a user's seat (#1480)
access_users: ListAccessUsers was returning wrong values in pointer fields due to variable missused in loop (#1482)
flarectl: alias zone certs to "ct" instead of duplicating the "c" alias (#1484)

DEPENDENCIES:

deps: bumps actions/cache from 3 to 4 (#1483)

v0.86.0
Compare Source
ENHANCEMENTS:

access_application: Add support for default_relay_state in saas apps (#1477)
zaraz: Add support for CRUD APIs (#1474)

DEPENDENCIES:

deps: bumps github.com/cloudflare/circl from 1.3.3 to 1.3.7 (#1475)
deps: bumps golang.org/x/net from 0.19.0 to 0.20.0 (#1476)

v0.85.0
Compare Source
DEPENDENCIES:

deps: bumps github.com/go-git/go-git/v5 from 5.4.2 to 5.11.0 (#1470)
deps: bumps github.com/urfave/cli/v2 from 2.26.0 to 2.27.0 (#1471)
deps: bumps github.com/urfave/cli/v2 from 2.27.0 to 2.27.1 (#1472)

v0.84.0
Compare Source
ENHANCEMENTS:

access_group: Add support for email lists (#1445)
device_posture_rules: add support for Access client fields in device posture integrations (#1464)
page_shield: added support for page shield (#1459)

DEPENDENCIES:

deps: bumps actions/setup-go from 4 to 5 (#1460)
deps: bumps github/codeql-action from 2 to 3 (#1462)
deps: bumps golang.org/x/crypto from 0.14.0 to 0.17.0 (#1466)

v0.83.0
Compare Source
ENHANCEMENTS:

cloudflare: Add ResultInfo to RawResponse (#1453)
devices_policy: add fields for Opt-In Split Tunnel Overlapping IPs feature. (#1454)
stream: Add ScheduledDeletion to StreamCreateVideoParameters (#1457)
stream: Add ScheduledDeletion to StreamUploadFromURLParameters (#1457)
stream: Add ScheduledDeletion to StreamVideo (#1457)
stream: Add ScheduledDeletion to StreamVideoCreate (#1457)
worker_bindings: Fixing form element name for d1 binding (#1450)
worker_bindings: add support for d1 bindings (#1446)

DEPENDENCIES:

deps: bumps github.com/urfave/cli/v2 from 2.25.7 to 2.26.0 (#1456)
deps: bumps golang.org/x/net from 0.18.0 to 0.19.0 (#1452)
deps: bumps golang.org/x/time from 0.4.0 to 0.5.0 (#1449)

v0.82.0
Compare Source
ENHANCEMENTS:

ip_access_rules: Add ListIPAccessRules() to list IP Access Rules (#1428)
load_balancing: add healthy field to LoadBalancerPool (#1442)

BUG FIXES:

load_balancing: Add support for virtual network id in origins (#1441)
per_hostname_tls_setting: use buildURI for defining the query parameters when sorting (#1440)

DEPENDENCIES:

deps: bumps github.com/hashicorp/go-retryablehttp from 0.7.4 to 0.7.5 (#1438)
deps: bumps golang.org/x/net from 0.17.0 to 0.18.0 (#1439)

v0.81.0
Compare Source
BREAKING CHANGES:

devices_policy: CreateDeviceSettingsPolicy is updated with method signatures matching the library conventions (#1433)
devices_policy: DeleteDeviceSettingsPolicy is updated with method signatures matching the library conventions (#1433)
devices_policy: DeviceClientCertificates is renamed to DeviceClientCertificates (#1433)
devices_policy: GetDefaultDeviceSettingsPolicy is updated with method signatures matching the library conventions (#1433)
devices_policy: GetDeviceClientCertificatesZone is renamed to GetDeviceClientCertificates with updated method signatures (#1433)
devices_policy: GetDeviceClientCertificates is updated with method signatures matching the library conventions (#1433)
devices_policy: GetDeviceSettingsPolicy is updated with method signatures matching the library conventions (#1433)
devices_policy: UpdateDefaultDeviceSettingsPolicy is updated with method signatures matching the library conventions (#1433)
devices_policy: UpdateDeviceClientCertificatesZone is renamed to UpdateDeviceClientCertificates with updated method signatures (#1433)
devices_policy: UpdateDeviceSettingsPolicy is updated with method signatures matching the library conventions (#1433)

ENHANCEMENTS:

access_seats: Add UpdateAccessUserSeat() to list IP Access Rules (#1427)
access_user: Add GetAccessUserActiveSessions() to get all active sessions for a Access/Zero-Trust user. (#1427)
access_user: Add GetAccessUserFailedLogins() to get all failed login attempts for a Access/Zero-Trust user. (#1427)
access_user: Add GetAccessUserLastSeenIdentity() to get last seen identity for a Access/Zero-Trust user. (#1427)
access_user: Add GetAccessUserSingleActiveSession() to get an active session for a Access/Zero-Trust user. (#1427)
access_user: Add ListAccessUsers() to get a list of users for a Access/Zero-Trust account. (#1427)
devices_policy: Add support for listing device settings policies (#1433)
teams_rules: Add support for resolver policies (#1436)

DEPENDENCIES:

deps: bumps golang.org/x/time from 0.3.0 to 0.4.0 (#1434)

v0.80.0
Compare Source
BREAKING CHANGES:

teams: BrowserIsolation.UrlBrowserIsolationEnabled has changed from bool to *bool to meet the library conventions (#1424)

ENHANCEMENTS:

access_application: Add support for app launcher customization fields (#1407)
api_shield_schema: Add support for Get/Update API Shield Operation Schema Validation Settings (#1422)
api_shield_schema: Add support for Get/Update API Shield Schema Validation Settings (#1418)
teams: Add support for body_scanning (Enhanced File Detection) in teams account configuration (#1423)
load_balancing: extend documentation for least_connections steering policy (#1414)
teams: Add non_identity_enabled boolean in browser isolation settings (#1424)

DEPENDENCIES:

deps: bumps golang.org/x/net from 0.7.0 to 0.17.0 (#1421)

v0.79.0
Compare Source
ENHANCEMENTS:

access_organization: Add support for session_duration (#1415)
access_policy: Add support for session_duration (#1415)
api_shield_discovery: Add support for Get/Patch API Shield API Discovery Operations (#1413)
api_shield_schema: Add support for managing schemas for API Shield Schema Validation 2.0 (#1406)
d1: adds support for d1 (#1417)
teams: Add audit_ssh_settings endpoints (#1419)

BUG FIXES:

custom_nameservers: change NSSet from string to int to match API response (#1410)
observatory: fix double url encoding (#1412)

v0.78.0
Compare Source
BREAKING CHANGES:

account_role: AccountRole has been renamed to GetAccountRole to align with the updated method conventions (#1405)
account_role: AccountRoles has been renamed to ListAccountRoles to align with the updated method conventions (#1405)

ENHANCEMENTS:

access_application: Add support for tags (#1403)
access_tag: Add support for tags (#1403)
list_item: allow filtering by search term, cursor and per page attributes (#1409)
observatory: add support for observatory API (#1401)

BUG FIXES:

account_role: autopaginate all available results instead of a static number (#1405)
semgrep: Improved IPv4 validation by implementing a new pattern to handle cases where non-IPv4 addresses were previously accepted. (#1382)

DEPENDENCIES:

deps: bumps codecov/codecov-action from 3 to 4 (#1402)

v0.77.0
Compare Source
ENHANCEMENTS:

access_identity_provider: add support for email_claim_name and authorization_server_id (#1390)
access_identity_provider: add support for ping_env_id (#1391)
dcv_delegation: add GET for DCV Delegation UUID (#1384)
streams: adds support to initiate tus upload (#1359)
tunnel: add support for include_prefix, exclude_prefix in list operations (#1385)

BUG FIXES:

dns: keep comments when calling UpdateDNSRecord with zero values of UpdateDNSRecordParams (#1393)

DEPENDENCIES:

deps: bumps actions/checkout from 3 to 4 (#1387)
deps: bumps golang.org/x/net from 0.14.0 to 0.15.0 (#1389)
deps: bumps goreleaser/goreleaser-action from 4.4.0 to 4.6.0 (#1388)
deps: bumps goreleaser/goreleaser-action from 4.6.0 to 5.0.0 (#1396)

v0.76.0
Compare Source
BREAKING CHANGES:

images: Renamed Image struct "Metadata" field to "Meta" (#1379)

ENHANCEMENTS:

access_application: added custom_non_identity_deny_url (#1373)
load_balancer_monitor: add support for consecutive_up, consecutive_down (#1380)
workers: Add support for retrieving and uploading only script content. (#1361)
workers: Add support for retrieving and uploading only script metadata. (#1361)
workers: allow namespaced scripts to be used as Worker tail consumers (#1377)

BUG FIXES:

access_application: Use autopaginate flag as expected (#1372)
access_ca_certificate: Use autopaginate flag as expected (#1372)
access_group: Use autopaginate flag as expected (#1372)
access_mutual_tls_certifcate: Use autopaginate flag as expected (#1372)
access_policy: Use autopaginate flag as expected (#1372)
images: Fix issue parsing Image Details from API due to incorrect struct json field (#1379)
pagination: Will look at total_count and per_page to calculate total_pages if total_pages is zero (#1372)

v0.75.0
Compare Source
BREAKING CHANGES:

cloudflare: Raw method now returns a RawResponse rather than the raw JSON Result message (#1355)
rulesets: Rename RulesetPhaseRateLimit to RulesetPhaseHTTPRatelimit, to match the phase name (#1367)
rulesets: Rename RulesetPhaseSuperBotFightMode to RulesetPhaseHTTPRequestSBFM, to match the phase name (#1367)

NOTES:

rulesets: Remove non-existent allow action (#1367)
rulesets: Remove non-existent http_request_main phase (#1367)
rulesets: Remove non-public http_response_headers_transform_managed and http_request_late_transform_managed phases (#1367)

ENHANCEMENTS:

access_group: add auth_context group ruletype (#1344)
access_identity_provider: add attr conditional_access_enabled (#1344)
access_identity_provider: add auth context list/put endpoint (#1344)
access_service_token: add support for managing Duration (#1347)
bot_management: add support for bot_management API (#1363)
cloudflare: swap encoding/json for github.com/goccy/go-json (#1360)
device_posture_rule: support eid_last_seen and risk_level and correct total_score for Tanium posture rule (#1366)
per_hostname_tls_settings: add support for managing hostname level TLS settings (#1356)
rulesets: Add the ddos_mitigation action (#1367)
waiting_room: add support for queueing_status_code (#1357)
web_analytics: add support for web_analytics API (#1348)
workers: add support for tagging Worker scripts (#1368)
zone_hold: add support for zone hold API (#1365)

BUG FIXES:

cache_purge: don't escape HTML entity values in URLs for cache keys (#1360)

DEPENDENCIES:

deps: bumps golang.org/x/net from 0.12.0 to 0.13.0 (#1353)
deps: bumps golang.org/x/net from 0.13.0 to 0.14.0 (#1362)
deps: bumps goreleaser/goreleaser-action from 4.3.0 to 4.4.0 (#1369)

v0.74.0
Compare Source
ENHANCEMENTS:

access_application: Add support for custom pages (#1343)
access_custom_page: Add support for custom pages (#1343)
access_organization: add support for custom pages (#1343)
rulesets: Remove internal-only schema kind (#1346)
rulesets: Remove some request parameters that are not allowed or have no effect (#1346)
rulesets: Update API reference links (#1346)
teams-accounts: Adds support for protocol detection (#1340)
workers: Add pipeline_hash field to Workers script response struct. (#1330)
workers: Add support for declaring arbitrary bindings with UnsafeBinding. (#1330)
workers: Add support for uploading scripts to a Workers for Platforms namespace. (#1330)
workers: Add support for uploading workers with Workers for Platforms namespace bindings. (#1330)

BUG FIXES:

flarectl: allow for create or update to actually create the record (#1341)
load_balancing: Fix pool creation with MinimumOrigins set to 0 (#1338)
workers: Fix namespace dispatch upload API path (#1345)

v0.73.0
Compare Source
BREAKING CHANGES:

pages_deployment: add support for auto pagination (#1264)
pages_deployment: change DeletePagesDeploymentParams to contain all parameters (#1264)
pages_project: change to use ResourceContainer for account ID (#1264)
pages_project: rename PagesProject to GetPagesProject (#1264)
rulesets: CreateAccountRuleset is removed in favour of CreateRuleset (#1333)
rulesets: CreateZoneRuleset is removed in favour of CreateRuleset (#1333)
rulesets: DeleteAccountRuleset is removed in favour of DeleteRuleset (#1333)
rulesets: DeleteZoneRuleset is removed in favour of DeleteRuleset (#1333)
rulesets: GetAccountRulesetPhase is removed in favour of GetEntrypointRuleset (#1333)
rulesets: GetAccountRuleset is removed in favour of GetRuleset (#1333)
rulesets: GetZoneRulesetPhase is removed in favour of GetEntrypointRuleset (#1333)
rulesets: GetZoneRuleset is removed in favour of GetRuleset (#1333)
rulesets: UpdateAccountRulesetPhase is removed in favour of UpdateEntrypointRuleset (#1333)
rulesets: UpdateAccountRuleset is removed in favour of UpdateRuleset (#1333)
rulesets: UpdateZoneRulesetPhase is removed in favour of UpdateEntrypointRuleset (#1333)
rulesets: UpdateZoneRuleset is removed in favour of UpdateRuleset (#1333)

ENHANCEMENTS:

device_posture_rule: support active_threats, network_status, infected, and is_active for sentinelone_s2s posture rule (#1339)
device_posture_rule: support certificate_id and cn for client_certificate posture rule (#1339)
images: adds ability to upload image by url (#1335)
load_balancing: support header session affinity policy (#1302)
zone: Added GetRegionalTieredCache and UpdateRegionalTieredCache to allow setting Regional Tiered Cache for a zone. (#1336)

DEPENDENCIES:

deps: bumps golang.org/x/net from 0.11.0 to 0.12.0 (#1328)

v0.72.0
Compare Source
BREAKING CHANGES:

logpush: CheckAccountLogpushDestinationExists is removed in favour of CheckLogpushDestinationExists with ResourceContainer method parameter (#1326)
logpush: CheckZoneLogpushDestinationExists is removed in favour of CheckLogpushDestinationExists with ResourceContainer method parameter (#1326)
logpush: CreateAccountLogpushJob is removed in favour of CreateLogpushJob with ResourceContainer method parameter (#1326)
logpush: CreateZoneLogpushJob is removed in favour of CreateLogpushJob with ResourceContainer method parameter (#1326)
logpush: DeleteAccountLogpushJob is removed in favour of DeleteLogpushJob with ResourceContainer method parameter (#1326)
logpush: DeleteZoneLogpushJob is removed in favour of DeleteLogpushJob with ResourceContainer method parameter (#1326)
logpush: GetAccountLogpushFields is removed in favour of GetLogpushFields with ResourceContainer method parameter (#1326)
logpush: GetAccountLogpushJob is removed in favour of GetLogpushJob with ResourceContainer method parameter (#1326)
logpush: GetAccountLogpushOwnershipChallenge is removed in favour of GetLogpushOwnershipChallenge with ResourceContainer method parameter (#1326)
logpush: GetZoneLogpushFields is removed in favour of GetLogpushFields with ResourceContainer method parameter (#1326)
logpush: GetZoneLogpushJob is removed in favour of GetLogpushJob with ResourceContainer method parameter (#1326)
logpush: GetZoneLogpushOwnershipChallenge is removed in favour of GetLogpushOwnershipChallenge with ResourceContainer method parameter (#1326)
logpush: ListAccountLogpushJobsForDataset is removed in favour of ListLogpushJobsForDataset with ResourceContainer method parameter (#1326)
logpush: ListAccountLogpushJobs is removed in favour of ListLogpushJobs with ResourceContainer method parameter (#1326)
logpush: ListZoneLogpushJobsForDataset is removed in favour of ListLogpushJobsForDataset with ResourceContainer method parameter (#1326)
logpush: ListZoneLogpushJobs is removed in favour of ListLogpushJobs with ResourceContainer method parameter (#1326)
logpush: UpdateAccountLogpushJob is removed in favour of UpdateLogpushJob with ResourceContainer method parameter (#1326)
logpush: UpdateZoneLogpushJob is removed in favour of UpdateLogpushJob with ResourceContainer method parameter (#1326)
logpush: ValidateAccountLogpushOwnershipChallenge is removed in favour of ValidateLogpushOwnershipChallenge with ResourceContainer method parameter (#1326)
logpush: ValidateZoneLogpushOwnershipChallenge is removed in favour of ValidateLogpushOwnershipChallenge with ResourceContainer method parameter (#1326)
logpush: all methods are updated to use the newer client conventions for method signatures (#1326)

ENHANCEMENTS:

resource_container: expose Type on *ResourceContainer to explicitly denote what type of resource it is instead of inferring from Level. (#1325)

v0.71.0
Compare Source
BREAKING CHANGES:

access_application: refactor methods to use ResourceContainer instead of dedicated account/zone methods (#1319)
access_ca_certificate: refactor methods to use ResourceContainer instead of dedicated account/zone methods (#1319)
access_group: refactor methods to use ResourceContainer instead of dedicated account/zone methods (#1319)
access_identity_provider: refactor methods to use ResourceContainer instead of dedicated account/zone methods (#1319)
access_mutual_tls_certificates: refactor methods to use ResourceContainer instead of dedicated account/zone methods (#1319)
access_organization: refactor methods to use ResourceContainer instead of dedicated account/zone methods (#1319)
access_policy: refactor methods to use ResourceContainer instead of dedicated account/zone methods (#1319)
access_service_tokens: refactor methods to use ResourceContainer instead of dedicated account/zone methods (#1319)
access_user_token: refactor methods to use ResourceContainer instead of dedicated account/zone methods (#1319)
images: renamed BaseImage to GetBaseImage to match library conventions (#1322)
images: renamed ImageDetails to GetImage to match library conventions (#1322)
images: renamed ImagesStats to GetImagesStats to match library conventions (#1322)
images: updated method signatures of DeleteImage to match newer conventions and standards (#1322)
images: updated method signatures of ListImages to match newer conventions and standards (#1322)
images: updated method signatures of UpdateImage to match newer conventions and standards (#1322)
images: updated method signatures of UploadImage to match newer conventions and standards (#1322)

ENHANCEMENTS:

access_application: add support for auto pagination (#1319)
access_ca_certificate: add support for auto pagination (#1319)
access_group: add support for auto pagination (#1319)
access_identity_provider: add support for auto pagination (#1319)
access_mutual_tls_certificates: add support for auto pagination (#1319)
access_policy: add support for auto pagination (#1319)
device_posture_rule: support os_version_extra (#1316)
images: adds support for v2 when uploading images directly (#1322)
workers: Add ability to specify tail Workers in script metadata (#1317)

DEPENDENCIES:

deps: bumps dependabot/fetch-metadata from 1.5.1 to 1.6.0 (#1320)

Note: flarectl binary archives are now all tar.gz as opposed to the mixed extensions previously used.

v0.70.0
Compare Source
BREAKING CHANGES:

cloudflare: remove UsingAccount in favour of resource specific attributes (#1315)
cloudflare: remove api.AccountID from client struct (#1315)
dns_firewall: modernise method signatures and conventions to align with the experimental client (#1313)
railgun: remove support for railgun (#1312)
tunnel: swap ConnectTimeout, TLSTimeout, TCPKeepAlive and KeepAliveTimeout to TunnelDuration instead of time.Duration (#1303)
virtualdns: remove support in favour of newer DNS firewall methods (#1313)

ENHANCEMENTS:

custom_nameservers: add support for managing custom nameservers (#1304)
load_balancing: extend documentation for least_outstanding_requests steering policy (#1293)
waiting_room: add support for additional_routes and cookie_suffix (#1311)

DEPENDENCIES:

deps: bumps github.com/hashicorp/go-retryablehttp from 0.7.3 to 0.7.4 (#1301)
deps: bumps github.com/urfave/cli/v2 from 2.25.5 to 2.25.6 (#1305)
deps: bumps github.com/urfave/cli/v2 from 2.25.6 to 2.25.7 (#1314)
deps: bumps golang.org/x/net from 0.10.0 to 0.11.0 (#1307)
deps: bumps goreleaser/goreleaser-action from 4.2.0 to 4.3.0 (#1306)

v0.69.0
Compare Source
BREAKING CHANGES:

stream: StreamVideo.Duration has changed from int to float64. ([#1190](https://redirect.g

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

2 additional dependencies were updated

Details:

Package
Change

github.com/urfave/cli/v2
v2.27.3 -> v2.27.4

golang.org/x/net
v0.28.0 -> v0.29.0

Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (v0.104.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


Ruby Paketo Buildpack promotion RFC

Readable

@kvedurmu as this is a single-team concern I'm ready to merge it without unanimous consent.


Is it possible to combine/compose multiple routers?

First, thank you so much for hattip, I absolutely love working with it!
I'm building a server that needs to combine multiple "apps" into one, and I was hoping I could combine two routers like so:
let productRouter = createRouter();
productRouter.get("/a/:product", ...);

let widgetRouter = createRouter();
widgetRouter.get("/b/:widget", ...);

productRouter.use(widgetRouter.buildHandler());

createServer(productRouter.buildHandler());

This would let me serve both /a/product and /b/widget.
However, I noticed that productRouter.use(widgetRouter.buildHandler()) causes widgetRouter to call passThrough() if it can't respond to the request, so the productRouter's routes never get run. The passThrough causes a 404.
Hopefully this question makes sense, but I can provide more details if needed!
Thank you again!

FWIW I'm doing this to get around the 404s...
let widgetHandler = widgetRouter.buildHandler();

productRouter.use((ctx) => {
  return async (ctx) => {
    let response = await widgetHandler(ctx);
    if (response.status !== 404) {
      return response;
    }
  };
});

Hi,
Sorry for the late response.
It is possible to turn a HattipHandler into a RouteHandler to embed one router into another. The following function will do just that:
function handlerToMiddleware<P>(handler: HattipHandler<P>): RouteHandler<any, P> {
  return async (ctx) => {
    let passThroughCalled = false;
    const subcontext: typeof ctx = {
      ...ctx,
      passThrough() {
        passThroughCalled = true;
      }
    }

    const response = await handler(subcontext);
    if (!response || passThroughCalled) {
      return ctx.next();
    }

    return response;
  }
}

Now you can usewidgetRouterinproductRouter` like this:
productRouter.use(handlerToMiddleware(widgetRouter.buildHandler()));

I'm planning on creating an entirely different router, until then you can use this (slightly hackey 😄) solution.

Oh awesome, this is great! Thank you :)


Implementing PluginManager

Known issue: (un)install a plugin that just un(-)installed will crash npm.

"Reload all" button will lost server config


coccinelle: Use Docker image to patch issues

Developers likely won't have Coccinelle installed on their system so we should allow them to use the Coccinelle Docker image to fix any issue found by the GitHub action.

Coverage decreased (-0.008%) to 44.508% when pulling 5716bef3a71d09cda7b3bf8f702aafd7212375e3 on pr/pchaigno/cocci-fix-using-docker into 854f625d341e70bee2ed2d9f5605b863b4dca28a on master.


Conformance tests for pool_test and containerdisk

What this PR does
This PR aims to identify and label the tests in the pool_test and containerdisk files.
Release note

NONE

/hold
waiting for https://github.com/kubevirt/kubevirt/pull/10441

/unhold

@xpivarc @0xFelix 2 approve and 0 lgtm :)

/hold cancel


#32: estimatesmartfee

I'll also open a Pull Request of #34 after my Pull Requests are merged (to prevent conflicts).

I didn't check which Core clients have estimatesmartfee, in case they add it in the future.

Should I add this too? (It removes the probability of setting too high fee):
if settxfee > 10*smarttxfee:
    use(smarttxfee)
else:
    use(settxfee)

Hi, so i updated btcatomicswap to use estimatesmartfee, and i'd like to use the same code for all forks which will need it eventually too.  If you want to go ahead and port that change, that would be appreciated, otherwise I'll close this PR and do it myself.

Of course, I'll do it today.


Analoge Clock moves 1 hour behind

My analog Clock runs one hour late. With the digital Clock are no Problems.
Writing from Germany, perhaps a Problem with the time Zone?
Regards
Robert

Strange!  Maybe something odd with locale or something.  :thinking: Can you let me know your settings for the following so we can try to recreate this?

System language
Time zone
Time format (12 vs 24hr)
Android version
Screenshot (preferably including your notification bar with the digital time displayed)

Thanks!

Now it works, don t know why. I will Close the Bug.


information

how to do?
@Query(sql)
Future findBySql(String sql);
in .g.dart
@override
Future findBySql(String sql) async {
return _queryAdapter.query(sql, mapper: _tMapper);
}

Sadly we don't allow completely dynamic queries like yours. Your use-case might be an exception but generally this is also not a good idea because of sql-injections and other issues.
It might be possible to use @rawQuery/isRaw for this once it is implemented (see #315), but you will miss auto-updated Streams and static type validation, which can only be done on queries which are known at compile time.

is that in some cases it is necessary to take only one field, in other cases it is necessary to make a count, in other cases it is necessary to do sum, the dynamic query would greatly decrease the creation of methods.

I made this implementation to give me this power:
ex:
Future<List> findListBySql(String sql) async {
final rows = await dbHelper.database.rawQuery(sql);
return rows.map((row) => Account.fromJson(row)).toList();
}


apk: add wolfi repo support

Question:
How should the interface look to choose alpine vs wolfi? For now I added wolfi Optional[bool] but that's not a great solution
Question/Comment:
For the conflicts returned by pkgResolver.GetPackagesWithDependencies, I believe those are just the list of conflicts declared by the packages themselves, not a conflict with the resolved package dependencies. Since we're installing all packages to a scratch container, I think we can just ignore conflicts since we don't have a base OS to check for the potentially conflicted packages.

How should the interface look to choose alpine vs wolfi? For now I added wolfi Optional[bool] but that's not a great solution

Ideally I think we should go for something where we support any "apk conforming" repository but give users the ability to use some common pre-defined apk repositories.
Different ways of approaching this, but one would be to have this module be totally generic and just accept the various URLs needed (repository, releases json, key, etc.) and then have separate modules for Alpine and Wolfi that depend on this one and set the URLs to their correct values for that "apk distro".

For the conflicts returned by pkgResolver.GetPackagesWithDependencies, I believe those are just the list of conflicts declared by the packages themselves, not a conflict with the resolved package dependencies.

I'm not totally sure what exactly we are supposed to do with these conflicts, but it seems like that may be a at least partially unresolved question upstream too (just having done superficial looking into it, I could be misunderstanding): https://github.com/chainguard-dev/go-apk/issues/159#issue-1995376426
So yeah I am good with ignoring them for now also :-)


Add support for io.jsonwebtoken:jjwt-impl:0.11.5

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Yes, refer to https://github.com/jwtk/jjwt/issues/637 .

Describe the solution you'd like
A clear and concise description of what you want to happen.

Add support for io.jsonwebtoken:jjwt-impl:0.11.5 .

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Null.

Additional context
Add any other context or screenshots about the feature request here.

Metadata generated at https://github.com/linghengqian/graalvm-trace-metadata-smoketest/issues/1 .

I am working on this issue.


LSTM Incompatibility with torch-rnn

I am working on a cuDNN fork of torch-rnn to pick up the speed and memory improvements/flexibility. A simple initial look indicates that the LSTM module should be mostly a drop-in replacement for the one in torch-rnn. Replacing the line nn.lstm(num_input,num_hidden) with cudnn.lstm(num_input,num_hidden,1,false,0,true) yields a network that runs but outputs gibberish.
Looking at the architecture, the torch-rnn language model is batch x time dimension ordering, but running with batch-first set to true results in an error. Am I missing something about the parameter? I am still a newcomer to Torch and deep learning in general, so it is likely that I missed something there.

this fork has cudnn support: https://github.com/ngimel/torch-rnn#cudnn-support-optional

Thanks for letting me know!


Is synapse must depend on AWS?

Is synapse must depend on AWS? if i haven't AWS ,can i launch it ?

@zouyx it is a dependency in the gemspec because of the Ec2TagWatcher, but if you are not using that watcher then the aws-sdk will just be an unused dependency.
Synapse itself does not depend on running in AWS and can run fine in your own datacenters.
Does that answer your question?

@zouyx I'm going to close this, please reopen with more context if it's still a problem.


Privacy Policy link in README.md 404s

Your Environment

Plugin version: All
Platform: Both
Device OS version: Any
Device manufacturer / model: All
XCode version: Any
Capacitor info (npx cap doctor)
Plugin config provided to #ready:

curl -I https://github.com/transistorsoft/capacitor-background-geolocation/blob/master/help/PRIVACY_POLICY.md

Expected Behavior
Privacy policy link in README.MD references an up to date privacy policy.
Actual Behavior
Privacy policy link in README.md is broken.
Steps to Reproduce

Click Privacy Policy link in this repo's README.md

Context
I would like to gain awareness of this plugin's privacy policy.
Debug logs

Logs
HTTP/2 404
server: GitHub.com
date: Sat, 05 Nov 2022 14:01:10 GMT
content-type: text/html; charset=utf-8
vary: X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, Accept-Encoding, Accept, X-Requested-With
...

This plugin does not capture or upload any data to transistorsoft.com or any other 3rd party.


How to export hive data from one ocp cluster and import to another ocp cluster

If I need to move from one ocp cluster to an other ocp cluster, how I can export all hive data(cluster, machine pool, clusterpool, clusterclaim etc) from the original ocp cluster to the new ocp cluster, so that new operation can be resumed from the new ocp cluster?

Check out the ClusterRelocate API, this is for moving a ClusterDeployment from one Hive to another. Apologies it is not documented today other than the go types.

Can you please provide some sample steps and payloads?


hot to get the required parameters of the distributions in a systematic way

I am trying with no success to obtain information about the parameters required for instantiating a particular distribution. In particular continuous distributions.
I know that all of them share the loc and scale parameter.
But, for example, lets say that I have the stats.ksone. Is there a way to know in advance (before calling any method) that this particular distribution requires also the n parameter?
I would need to do this argument parsing for all the continuous distributions:
dist_continu = [d for d in dir(stats) if isinstance(getattr(stats, d), stats.rv_continuous)]
but after spending a few hours on it I don't know how to proceed.
I tried with inspect and also by parsing the docstring but I only get *args and **kwargs as result
Any suggestion would be appreciated

>>> from scipy import stats
>>> stats.beta.shapes
'a, b'
>>> stats.ksone.shapes
'n'

>>> from scipy import stats
>>> stats.beta.shapes
'a, b'
>>> stats.ksone.shapes
'n'

Thank very much you for the answer. Anyway to also have information about the range of this arguments or if it is floating or integer?


I am using a Mac

buy a cheap windows pc and use hshop next time

https://github.com/shijimasoft/cia-unix/tree/experimental


make iterator usage safer after intermediate commits

Scope & Purpose
Backport of https://github.com/arangodb/arangodb/pull/14346
When a transaction triggers an intermediate commit, this may affect rocksdb::Iterator objects used by the transaction. These may become silently invalidated if they point to nodes in the committed transaction's WriteBatchWithIndex's index (i.e. the SkipList).
This change tries to rebuild any such iterators after an intermediate commit, by tracking the last key an iterator was pointing at when leaving iterator-related code.
When re-entering iterator code, there is a check if an intermediate commit has happened in the meantime, and if so, the iterator will be rebuilt from scratch and will seek back to the last tracked key. This seems to be the only safe way to make sure the previous iterator does not point to any data that is now invalid after the previous transaction committed.
For read-only transactions, this behavior is turned off, i.e. there should be no overhead. For write-transactions, there will be (hopefully) neglible overhead, because the last seen key is copied to already allocated memory only when iterator-related code is left. Tracking keys will only happen for every 1,000 keys or so.
The PR also removes superfluous out-of-bounds checks for read-only transactions, which could even see a small speedup due to the changes.
We should add a lot more tests for these changes and the behavior. In our normal tests, intermediate commits are not happening frequently.

[x] :hankey: Bugfix (requires CHANGELOG entry)
[ ] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification
[ ] :book: CHANGELOG entry made

Backports:

[x] No backports required

Testing & Verification

[ ] This change is a trivial rework / code cleanup without any test coverage.
[x] The behavior in this PR was manually tested
[x] This change is already covered by existing tests, such as shell_server_aql, shell_client.
[ ] This PR adds tests that were used to verify all changes:

[ ] Added new C++ Unit tests
[ ] Added new integration tests (e.g. in shell_server / shell_server_aql)
[ ] Added new resilience tests (only if the feature is impacted by failovers)

[ ] There are tests in an external testing repository:
[ ] I ensured this code runs with ASan / TSan or other static verification tools

Requires a different fix. Closing this now until a working solution is available in devel, and then will restart work on the backport.


Replacement of "compile" with "implementation"

As "compile" is going to be deprecated end-2018, this PR replaces with "implementation" that is the new usage.

Does not work

thank you for your contribution. this is in master 5.0.0-alpha1


Timezone for variables inside history view

Variables 'Created' column inside process instance history view should be in local timezone like in other tabs.
Right now it's displayed as is in UTC

well, on for me variables in history tab are in my personal timezone,
I've a spring-boot application as in https://github.com/bogdartysh/spring-boot-datakurre-plugins-webjar/tree/main/sample/camunda-euler

I added time zone support quite recently so I might have forgotten it from some places. I will keep this open until I have checked that.


Improve alert to users signing an Aggregate Bonded transaction

=== Background
Many users from the Japanese community have reported that they have received spam/scam transactions pending signature, in order to be scammed out of their funds.
When a user innocently approves this transaction, maybe out of inertia, some or all of their funds will be transferred most likely against their wishes.

Affected user: https://twitter.com/gehari3sei/status/1442883477485936651
Affected user: https://twitter.com/Yiddish816/status/1443084024872800256


Have ability to choose HMT source for funding escrow contracts (as opposed to relying always on our gas payer)

Make hmt-escrow able to let the user decide from where to grab HMT and fund the escrow contract (i.e., transform the gas_payer environment variable into a function parameter).
Then, change all services which use hmt-escrow accordingly.

@gaieges There was a similar stretch issue that I was assigned last year, I couldn't find it and link it here... Perhaps you remember which repo was it in? Searched in hmt-escrow and hmt-servers.

@excerebrose any issues with this?

There are a couple of issues with the hmt-escrow changes related to the mainnet launch... Take, for instance, the problem of who pays for the gas of the tx by which that user funds the escrow: him, or us (remember, it's mainnet)? Then, you must ensure that the user buys HMT at the same address that they launch the job with us (for which we have the private key in paymentagent's users db), otherwise the job launching process will not be automatic (or, fast) because we will have to wait for the user to approve the transfer.

I think this makes sense, will be helpful in the plans we have down the road as well.


Parsing a string that looks like a number seem to not work

Hello,
console.log(require("yaml").parse("example:<PHONE_NUMBER>"))

returns
{ example: 681924019 }

Would there be a way to parse the value of example as a string?
My understanding of the spec is that it shouldn't be considered as an integer as it doesn't match the  0|-?[1-9][0-9]* regexp

The part of the spec that you're linking to is the JSON Schema integer, which has a different definition than the default Core Schema integer, which detects numbers according to the pattern [-+]?[0-9]+.
In your case, just switching to the JSON schema probably isn't what you're looking for, as it does not support scalar tag resolution for non-specific tags (and hence will fail when encountering example). In other words, it works just like JSON in this respect. On the other hand, the Failsafe Schema might be suitable, as it considers all scalars to have string values:
YAML.parse('example:<PHONE_NUMBER>', { schema: 'failsafe' })
// { example: '0681924019' }

Amazingly detailed answer! Thanks.


Update geojson-jackson to version 1.6

Is it possible to update geojson-jackson depency to version 1.6 ?

geojson-jackon 1.3 use jackson 2.4
geojson-jackon 1.3 use jackson 2.7... who required java 1.7
and fongo is, for now, compatible with java 6


Chore Set the maintainer for the FE ENV file

Proposed changes
we need to set the maintainer for the FE ENV file, which is a critical file for starting FE. We have experienced multiple instances of resource leaks due to incorrect modifications. Therefore, we need to add someone familiar with this file as the maintainer. Any changes to this file must be reviewed and approved by the maintainer before they can be merged.

run buildall

Hi, @morningman @dataroaring I'm inviting you to be the maintainer of this File. If anyone else is familiar with this, feel free to add yourself as a maintainer as well.


[Question] Example / how to use SpanDecorator?

It looks like use can supply their own span decorators with their tracer 👍
https://github.com/opentracing-contrib/java-spring-web/blob/0933caece7de11ae9f9d411113a5473d35288cf8/opentracing-spring-web/src/main/java/io/opentracing/contrib/spring/web/interceptor/TracingHandlerInterceptor.java#L50
is there an example of how to do it and wire it up? It is not at all obvious how to do it.
Only got to the point of
``` and override onPreHandle and onAfterCompletion. but then what.

but then what.

What is not clear? Just implement the decorator interface 1 and supply it to TracingHandlerInterceptor. If you are using SB starter opentracing-spring-web-starter you can expose the decorator impl as a bean and instrumentation should pick it up.

I will close this, feel free to reopen if you run into any issues.


[Auto-generated] Check & update dependencies (pyproject.toml)

Update dependencies (pyproject.toml)
Automatically created PR based on the 'CI - Check pyproject.toml dependencies' workflow in SINTEF/ci-cd.

Codecov Report

:exclamation: No coverage uploaded for pull request base (ci/dependency-updates@da6b11a). Click here to learn what that means.
The diff coverage is n/a.

@@                   Coverage Diff                    @@
##             ci/dependency-updates     #135   +/-   ##
========================================================
  Coverage                         ?   76.19%
========================================================
  Files                            ?       15
  Lines                            ?      605
  Branches                         ?        0
========================================================
  Hits                             ?      461
  Misses                           ?      144
  Partials                         ?        0

Flag
Coverage Δ

linux
76.19% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.


Take into account baseTexture resolution when registering a BitmapText.

When the base texture has a resolution scale other than 1, then the result of the rendered bitmap text becomes a mess. This change allows you to use bitmap fonts with different screen resolutions.

Thanks, I hope it's correct.

@themoonrat, look good?


Build with rust 1.46.0 fails

https://github.com/psychon/x11rb/runs/7503329086?check_suite_focus=true
Run cargo build --workspace --verbose --all-targets --all-features
    Updating crates.io index
 Downloading crates ...
  Downloaded futures-executor v0.3.21
  Downloaded proc-macro2 v1.0.41
  Downloaded regex v1.6.0
  Downloaded crossbeam-deque v0.[8](https://github.com/psychon/x11rb/runs/7503329086?check_suite_focus=true#step:6:9).2
  Downloaded autocfg v1.1.0
  Downloaded event-listener v2.5.2
  Downloaded futures-macro v0.3.21
  Downloaded log v0.4.17
  Downloaded proc-macro-error-attr v1.0.4
  Downloaded regex-automata v0.1.10
  Downloaded tinytemplate v1.2.1
  Downloaded walkdir v2.3.2
  Downloaded crossbeam-channel v0.5.6
  Downloaded criterion v0.3.6
  Downloaded system-deps v1.3.2
  Downloaded cairo-sys-rs v0.10.0
  Downloaded plotters-svg v0.3.2
  Downloaded waker-fn v1.1.0
  Downloaded once_cell v1.13.0
  Downloaded gobject-sys v0.10.0
  Downloaded glib v0.10.3
  Downloaded xmlparser v0.13.3
  Downloaded strum v0.18.0
  Downloaded nix v0.24.2
  Downloaded plotters v0.3.2
error: failed to parse manifest at `/home/runner/.cargo/registry/src/github.com-1ecc62[9](https://github.com/psychon/x11rb/runs/7503329086?check_suite_focus=true#step:6:10)9db9ec823/plotters-0.3.2/Cargo.toml`

Caused by:
  failed to parse the `edition` key

Caused by:
  this version of Cargo is older than the `2021` edition, and only supports `20[15](https://github.com/psychon/x11rb/runs/7503329086?check_suite_focus=true#step:6:16)` and `20[18](https://github.com/psychon/x11rb/runs/7503329086?check_suite_focus=true#step:6:19)` editions.

Locally, cargo tree says I am using plotters v0.3.1 (the failure is with .2) and I get that dependency via `criterion v0.3.5 (the failure is with criterion .6). plotters v0.3.2 was released 20 days ago and criterion v0.3.6 19 days ago, so no idea why this only starts failing now.

https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html

Dev-dependencies are not used when compiling a package for building, but are used for compiling tests, examples, and benchmarks.

Hm... raise our MSRV or do less testing there by not building tests, examples, benchmarks?

That sounds like a sound solution. 1.56 from 1.46 is a big jump that also breaks the 1.48 boundary.


Wrong delay on blinky example

After trying the blinky and yd-ch582m examples on a YD-CH582M core board, the delay does not work as expected. It's about ~100 times too long, setting delay_ms to 10 gives a ~1s blink (I haven't measured exactly).
Maybe the clock setup is not correct?
I'm using wchisp as a runner/flasher.

Thanks for the report.
I'll check this soon.
Could you help print pac::SYSTICK.CNT values at a certain interval to check the system frequency?
(This is a known method to get the current sysclk freq reliably)

I have a wlink but did not set it up yet, so I don't have a serial console. I'll try it and come back to you, but this might need some soldering first.

I have been unable to enable debugging on the chip with wchisp, I must have done something wrong at some point; I modified the reset value and rebuilt multiple times, but it always comes back to the same value (I realize this is out of scope of this bug). I am not sure if the 2-wire debugging is necessary to get serial output though.

I see. Could you try the release mode using --release?

You're correct, running in release mode, it does run at the correct speed. I was not able to enable the debug mode and flash something (verify fails), but this is something for another bug.
Thanks a lot!


#23 Return Connection instead of ConnectionImpl from ConnectionFactor…

…y.createConnection().
Also made changes to the IT cases to be able to complete the build with -Pall-tests maven profile.

I am not sure whether -Pall-tests suppose to work at all. I saw it succeeded only once. And all other runs failed with different errors, so it looks like IT cases are not stable (at least I have not seen this).

Thanks for reporting both the interface problem(#23) and the testing problem. I'm looking into both right now.

Resolved by #25.


pOnewheel v 3.3 Fatal exception after setting Logging Frequency in android 7.0

Expected behavior
Should after user set Logging Frequency, then click Ok to save it. Applications must be stable, and run well on the device.
Actual behavior
After setting up Logging Frequency, then click Ok to save it. Next, press the back button on the device, suddenly the application crashes. And when I want to reenter the app, the app continues to stop, so the ability to get into the app can not be done anymore.
How to reproduce

Launch app.
Allow application is requesting permission to turn on Bluetooth. Press Yes.
Click on three dots in the top right corner of the display screen.
Select and open Settings feature.
Press or open the Frequency Logging feature.
Add 7 zeros, so be<PHONE_NUMBER>0, then Press OK.
Press the back button on the device.You will get into trouble as I have experienced.

Logcat
 ---------beginning of crash 06-02 05:15:37.451 17392 17392 E AndroidRuntime: FATAL EXCEPTION: main 06-02 05:15:37.451 17392 17392 E AndroidRuntime: Process: net.kwatts.powtools, PID: 17392 06-02 05:15:37.451 17392 17392 E AndroidRuntime: java.lang.NumberFormatException: For input string: "10000000000" 06-02 05:15:37.451 17392 17392 E AndroidRuntime: 	at java.lang.Integer.parseInt(Integer.java:524) 06-02 05:15:37.451 17392 17392 E AndroidRuntime: 	at java.lang.Integer.valueOf(Integer.java:611) 06-02 05:15:37.451 17392 17392 E AndroidRuntime: 	at net.kwatts.powtools.util.SharedPreferencesUtil.getLoggingFrequency(SharedPreferencesUtil.java:59) 06-02 05:15:37.451 17392 17392 E AndroidRuntime: 	at net.kwatts.powtools.MainActivity$9.run(MainActivity.java:681) 06-02 05:15:37.451 17392 17392 E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:751) 06-02 05:15:37.451 17392 17392 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:95) 06-02 05:15:37.451 17392 17392 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:154) 06-02 05:15:37.451 17392 17392 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:6682) 06-02 05:15:37.451 17392 17392 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method) 06-02 05:15:37.451 17392 17392 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1520) 06-02 05:15:37.451 17392 17392 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1410) 06-02 05:15:37.496  3716  6129 D Debug   : !@DumpState : SHIP 06-02 05:15:37.496  3716  6129 D Debug   : !@DumpState : debug level:0x4f4c 06-02 05:15:37.496  3716  6129 D Debug   : !@Dumpstate : Finally, system will skip dumpstate 06-02 05:15:37.506  3716  6129 W ActivityManager:   Force finishing activity
Recording Of The Bug
The following recording video shows the problem that occurred, and the steps how to reproduce the problem correctly. Video taken on Android 7.0 device.
https://youtu.be/rZLE_OdPySA

Cool, thanks for logging. Should be an easy fix.

okay, thanks again.
I want to ask. Would you like to receive a new Logo contribution for this
project. If you want to accept it. I'll be designing a sweet new logo for
this app. And give me some time to work on it for a few days. thank you
Pada tanggal Sen, 18 Jun 2018 01:37, Kevin Watkins<EMAIL_ADDRESS>menulis:

Cool, thanks for logging. Should be an easy fix.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ponewheel/android-ponewheel/issues/70#issuecomment-397897754,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aj-XcpHcuupctVAVPoy6PXTB-Y7CyG2xks5t9qHVgaJpZM4UXccC
.

Ahh thanks for the offer, current logo is fine.
On Sun, Jun 17, 2018, 2:45 PM ammarraisafti<EMAIL_ADDRESS>wrote:

okay, thanks again.
I want to ask. Would you like to receive a new Logo contribution for this
project. If you want to accept it. I'll be designing a sweet new logo for
this app. And give me some time to work on it for a few days. thank you
Pada tanggal Sen, 18 Jun 2018 01:37, Kevin Watkins <
<EMAIL_ADDRESS>menulis:

Cool, thanks for logging. Should be an easy fix.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/ponewheel/android-ponewheel/issues/70#issuecomment-397897754
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/Aj-XcpHcuupctVAVPoy6PXTB-Y7CyG2xks5t9qHVgaJpZM4UXccC
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ponewheel/android-ponewheel/issues/70#issuecomment-397908625,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0LreSmdYSXK_lk1p8HhRrbtC4Goo2pks5t9s3ggaJpZM4UXccC
.


PCB build instructions use part references that are only documented on google sheets

Instructions in pcb build reference things like 'diode D1' and 'resistor R1' but those are nowhere to be found in the repo. They should be specified.
In the meantime, the part references are here.
Either remove references like D1 and just specify the resistor value + code or specify which is which somewhere.

🙈 yeah definitely need to do this

Opened a PR here https://github.com/nasa-jpl/open-source-rover/pull/448

Done.


Shoud a box be closed, or doesn't it matter?

Question
I have just starting to read the docs, and came across this piece:
Before your application exits, you should call Hive.close() to close all open boxes. Don't worry if the app is killed before you close Hive, it doesn't matter.

It's pretty confusing: so should the boxes be closed, or doesn't it matter? Should I strive to always cleanly close the box, or can I just forget about it?

I have an app running on production that doesn't closes open boxes on exit because it's very tricky to know when the app is closed or killed (well, because it's killed it couldn't execute your code anyways).

Right, this would mean each right is 'complete', as in: it writes data to disk completely, and closing doesn't add any kind of footer or whatever, that is required for the box to be correct?
My question was also about the documentation, that it is pretty confusingly worded, because it starts the sentence with 'you should close' but then it says you don't have to care about closing.

@wujek-srujek No need to close boxes.


Docker image under windows

Is your feature request related to a problem? Please describe.
Quick Start guide refer to linux .sh files
Describe the solution you'd like
Since my objective is to run the docker image. It should probably be possible to works under windows
Many thanks for your advice

Hi @goRaspy !
If you want to run the docker image, you can skip the unix-init-install-all.sh file and simply run docker compose up from Server/ and it will work.
If you want to run locally, the .sh script can be executed from Git Bash, a unix-like command line utility that usually comes installed on windows machines (or, you can download it).

Thank you very much for your help. Looks like it run well. Unfortunately I do not have access to anything on <IP_ADDRESS>:8055 is there something else to do to access the web interface ?


Fix hyphenation for fee-waiver => fee waiver

"If you cannot afford to pay the filing fee you can ask the court for a waiver. You can complete a fee-waiver form during this interview."

Even if technically correct, it looks very odd to me. "Fee waiver" is usually used alone, as the title of the form.
Maybe we can rewrite to avoid the unusual term?

If you cannot afford to pay the filing fee you can ask the court for a waiver. You can complete a fee-waiver form during this interview.

to

If you cannot afford to pay the filing fee you can ask the court for permission to file for free. This interview will help you ask the court.

It's technically correct, yes, but the reason to hyphenate a compound adjective is to help avoid ambiguity. A "fee-waiver petition" can only mean a petition for waiving the fee. A "fee waiver petition" could suggest a waiver petition that has a fee attached to it.
It's not a hill I intend to die on in this case. It's difficult for my brain to make sense of the second meaning, and clarity is after all the goal.
(Contrast "small firm website," which could mean a firm website that is small, with "small-firm website," which means the website of a small firm, no matter the size of the website. In that case I will always insist the hyphen is necessary.)
However, if we meant to use the proper title of the form then we should do that, including capitalization to indicate it is a title rather than just a description of a kind of form.
But in the end I prefer your suggested change so I'm going with it and I hope the court agrees.


Initialize GMM parameters with k-means

The general practice seems to be to use GMM as an optimization of k-means. The initializer of GMM should therefore use k-means for the initial parameters, then GMM for fine-tuning.

Yes this is indeed standard. I had thought about implementing this before but I'm not sure how exactly it should look. Certainly I'd like GMM to be accessible without the K-Means initialization. I see two approaches:

Add some new initialization trait/enum similar to K-Means to GMM
Allow a GMM model to be created from_init_clusters.

I think that it might even be worth implementing both of these - with the second suggestion coming first. The second would let us use K-Means to initialize GMM.
And to give a little more information on the K-Means initialization. The idea (from my knowledge) is to use K-Means to determine the location of the clusters (their means) and the data that belongs to them. We then compute the covariance matrix within each cluster (similarly to what we do now for the whole data set). This lets us assume a sensible mixture of gaussians over the whole data set which can be fine tuned.

References
Simple Methods for Initializing the EM Algorithm of GMMs
Small (but englightening) SO question thread

My opinion for the API here is basically the same as it is in #153. We should create a ClusterInitializer trait that has whatever methods we need, and then RandomInitializer and KMeansInitializer structs to do the proper calculations accordingly.

Same here—this issue is also fixed by #155.


Checkbox Label overflow

The first time I have seen this behaviour was on my mobile phone. If the label of a checkbox is longer than there is horizontal space the label will wrap at the end of the line. This however does not reposition the following block objects. Thus the label will float over the next block object.
Here is the codepen to demonstrate the problem on the desktop:
http://codepen.io/steamonimo/pen/aOeOVg
BTW: On a personal note I think that the textfield should use the same font as the input field. But this is just personal preference.
Thanks for listening,
Holger

Thanks for the Codepen! The label definitely needs to expand vertically here. Although I suggest we talk to the MD team how this is supposed to behave.

I ran into this too. I'm guessing it is due to the use of absolute positioning of some of the checkbox children, so even when wrapped in a block element, the label doesn't take up its proper size. As a brutally ugly workaround you can put a couple of br tags in to force separation of the next element, but this is far from ideal in a responsive design, as the number of br tags required changes with screen size.
Is there any guidance on a better workaround pending feedback from the MD team on the correct behaviour here? I would guess a proper fix might require a rethink of the positioning strategy used for the mdl-checkbox children.

I have to admit that I forgot to ask this the last time we talked to the MD team, because I forgot to tag it properly. Will try to rectify asap.

+1

Is there any progress on this issue?

Not fixing the label height at 24 px seems to solve the issue
.mdl-checkbox {
  height: 100%
}

I know it is a completely unrelated documentation page, but the concept of wrap-and-truncate at http://www.google.com/design/spec/components/tabs.html#tabs-content seems interesting for this

+1

Setting the height of the checkbox to 100% does however introduce layout issues in internet explorer and firefox when the checkbox is follow by some other content.

I managed to find a fix that work on all browsers.
.mdl-checkbox {
  height: auto
}

`inherit

Setting height at auto or inherit introduces a new issue. If set, the placement of the checkbox is off when the label text is empty.


README needs more details on Features

Describe the bug
https://github.com/ipfs-shipyard/ipfs-desktop#features
On the readme, I am so excited by the fatures laid out to start/stop a node, and automatically get the ipfs CLI and keep it updated 🤩 ... but I don't see anything in the GUI that reflects these features... It would be very good to expose this more in the readme and docs (https://docs.ipfs.io/install/ipfs-desktop/) 🙏🏼

Note: I am on linux, so this may be partly the issue?

Good point that the Linux tray issue could benefit from being explicitly noted. Thank you!

https://github.com/ipfs-shipyard/ipfs-desktop/pull/1703 should ameliorate a lot of this.
Note: Once that PR is approved/merged, I'll add some highlights (primarily features list) to https://docs.ipfs.io/install/ipfs-desktop/ in a separate PR in the docs repo.

NB: The PR for adding features summary to docs is at https://github.com/ipfs/ipfs-docs/pull/525.


Add option to set active tools

I'd like the ability to set active tools as a plot option in holoviews. The current process of creating hook seems clunky for something that I'm sure many users would like to do.
The hook snippet:
def set_active_tool(plot, element):
    plot.state.toolbar.active_scroll = plot.state.tools[2]

hv.Curve([1, 2, 3]).options(finalize_hooks=[set_active_tool])

Discussed originally here https://stackoverflow.com/questions/50415434/how-to-set-active-tools-in-holoviews/50416512#50416512

syntax:
hv_element.opts(active_tools=['pan','wheel_zoom'])

This doesn't appear to work with DynamicMaps.  Can you set the options below for overlayed DynamicMaps?
active_drag
active_scroll
active_tap
active_inspect

please can you reopen this issue as it is not solved?

@kwunlyou Can you provide an example of something that isn't working? I just tried different combinations of Elements, Overlays and DynamicMaps without issue.
@kwunlyou The API in HoloViews is different, you simply provide the list of active tools instead of defining active_drag, active_scroll etc. tools separately.
I'll happily reopen if you provide an example that isn't working.

@philippjfr thanks for the quick response. I prepared an example based on this official one
import pandas as pd
import holoviews as hv
hv.extension('bokeh')

edges_df = pd.read_csv('./fb_edges.csv')
nodes_df = pd.read_csv('./fb_nodes.csv')

fb_nodes = hv.Nodes(nodes_df).sort()
fb_graph = hv.Graph((edges_df, fb_nodes), label='Facebook Circles')

colors = ['#000000']+hv.Cycle('Category20').values
fb_graph = fb_graph.redim.range(x=(-0.05, 1.05),
                                y=(-0.05, 1.05)
                               )
fb_graph.opts(color_index='circle', width=800, height=800, show_frame=False,
                 xaxis=None, yaxis=None,node_size=10, edge_line_width=1, cmap=colors, active_tools=['pan'])

and here is the result

btw I am using
holoviews==1.12.6
bokeh==1.3.4

@kwunlyou To be clear, you are expecting the tap and hover tools to be disabled? Currently the active_tools only deals with activating tools, it does not deactivate other tools.

@philippjfr yes, I just want to activate pan as I noticed it is a bit slow to scroll my notebook if hover is active

Currently the active_tools only deals with activating tools, it does not deactivate other tools.
so I have to change something in bokeh?

@philippjfr so I have to change something in bokeh?

I'd have to investigate how bokeh handles this and then come back with a proposal, for now you could try something like:
def set_inactive_tool(plot, element):
    plot.state.toolbar.active_inspect = None

hv.Curve([1, 2, 3]).options(tools=['hover'], hooks=[set_inactive_tool])

thank you @philippjfr


meta: v0.24.x release

Currently tendermint-rs v0.24.x, which targets Tendermint Core v0.35.x, is in pre-release. Ideally the following issue(s)/PR(s) will be addressed/merged before cutting a release:

#1092

(Possibly more to come, pending updates from the ibc-rs team)
Until then, please expect breaking changes in the v0.24.x pre-release series.

maybe a feature flag in tendermint-proto for privval gRPC server could be provided:
https://github.com/informalsystems/tendermint-rs/issues/1134 ?

https://github.com/informalsystems/tendermint-rs/pull/1137


Infinite styles compiling (create-react-app and node-sass)

So we have a project which uses create-react-app and node-sass.
I have encountered this error many times over the last 2-3 months. I thought it was only happening to me, but now my colleague sometimes encounters this issue as well.

We have a standard setup from Adding a CSS Preprocessor (Sass, Less etc.).

Actual problem occurs when I edit the styles.scss and save them. Then an infinite compiling loop takes place. It's seriously annoying and it uses a lot of memory as well.
Has anyone had encountered that problem and any ideas how to fix it?

package.json
{
  "name": "ParentPortal",
  "version": "0.1.10",
  "private": true,
  "eslintConfig": {
    "extends": "react-app",
    "env": {
      "jest": true
    }
  },
  "devDependencies": {
    "@octopusdeploy/octopackjs": "0.0.7",
    "bootstrap-sass": "^3.3.7",
    "enzyme": "^2.7.1",
    "flow-bin": "^0.41.0",
    "font-awesome": "^4.7.0",
    "node-sass": "^4.5.0",
    "npm-run-all": "^4.0.1",
    "react-addons-test-utils": "^15.4.2",
    "react-scripts": "^0.9.5",
    "react-test-renderer": "^15.4.2",
    "zip-dir": "^1.0.2"
  },
  "dependencies": {
    //
  },
  "scripts": {
    "build-css": "node-sass src/ -o src/",
    "watch-css": "npm run build-css && node-sass src/ -o src/ --watch",
    "start-js": "react-scripts start",
    "start": "npm-run-all -p watch-css start-js",
    "build": "npm run build-css && react-scripts build",
    "test": "react-scripts test --env=jsdom",
    "eject": "react-scripts eject",
    "flow": "flow",
    "publish": "node scripts/deploy.js"
  }
}

Example

Can you try this workaround and see if it's working? It's not the most performant though.
@gaearon @Timer I think it's better if we nudge people to go to css in js solution like styled-components / styletron / etc. Or update the docs. Been seeing more and more issues about node-sass.

node-sass seems to detect the css file changing.  I changed the script to only look for scss files and it worked for me:
"watch-css": "npm run build-css && node-sass src/*.scss -o src/ --watch --recursive",

Could you please submit a PR detailing that change?

@gaearon @Timer I think it's better if we nudge people to go to css in js solution like styled-components / styletron / etc. Or update the docs. Been seeing more and more issues about node-sass.

If people want to use Sass it’s their choice. If Sass tools are broken, this is an issue with the tooling ecosystem people decided to invest in. IMO we shouldn’t have opinions here—our opinion is already expressed in that it isn’t enabled by default.

That said if there’s an easy fix we should definitely update our doc.

@gaearon yeah, I agree with you. I'm just thinking from Sass to css in js convert and how it made everything easier :). I think @JasonGoemaat solution could be used to update the docs, but we should add note for the undetected changes for new file issue.

I can confirmed this is an issue with node-sass after experiencing the same thing.

I believe this has been resolved in the latest version of node-sass. Please comment here if it's not resolved.

@Timer I believe there is still an issue. i'm on 4.5.2 and I still see this sometimes. using @JasonGoemaat 's tweak to the CLI fixed it for me.

@kellyrmilligan would you be so kind to send a PR fixing the documentation with @JasonGoemaat's suggestion?

@Timer there you go.

is this resolved by https://github.com/facebookincubator/create-react-app/pull/2114 ?

Indeed

i had same problem in vscode, and resolved use by add code --usePolling --polling-interval 500
now my package.json script is
"build-css": "node-sass-chokidar --include-path ./src --include-path ./node_modules src/ -o src/",
"watch-css": "npm run build-css && node-sass-chokidar --include-path ./src --include-path ./node_modules src/ -o src/ --watch --recursive --usePolling --polling-interval 500"

it's run successfully in vscode


Suggest and add new features

Hey, I liked the Idea and would like to contribute to your mission. I have come up with the below suggestion -
Do you want me to add a spinner/loader instead of showing Loading... at the initial render?

@sprakash57 Hey, That would be a very good addition.
I will create a new issue for this and will assign you on that.

Thanks a lot. looking forward to it.


Need help: How work with this API, Add ID to JSON-RPC call

https://hitbtc.com/api#get-currencies
How to add id to JSON-RPC call
{
  "method": "getCurrency",
  "params": {
    "currency": "ETH"
  },
  "id": 123
}

Currently ID cannot be set manually. Why would you need this? ID is set automatically and should not make any differences for you at all..

Sorry, it is work now, but response time is very slow.

ws.on('open', function() {
  // call an RPC method with parameters

    ws.call('getCurrency', {currency: 'ETH'}).then(function(result) {
      console.log(result)
    })

    ws.call('login',{
        "algo": "BASIC",
        "pKey": key,
        "sKey": secret
      }
    ).then(function(result) {
        console.log(result);
        ws.call('getTradingBalance').then(function(result) {
        console.log(result);
      }
  });
})

Its faster if i use ws package .

I highly doubt it it's slower than ws, because I'm using uws instead, which is a lot faster. Can you provide any tests and times?

If you run this code, it take more 10s to response
index.js
const rpc = require('rpc-websockets').Client

const baseUrl = 'wss://api.hitbtc.com/api/2/ws';

var ws = new rpc(baseUrl)

ws.on('open', function() {
  // call an RPC method with parameters
  ws.call('getCurrency', {currency: 'ETH'}).then(function(result) {
    console.log(2);
    console.log(result)
  })
})

index2.js under 5s
const WebSocket = require('ws');

const baseUrl = 'wss://api.hitbtc.com/api/2/ws';

var ws = new WebSocket(baseUrl)
ws.on('open', function() {
    console.log('open');
    ws.send(JSON.stringify({
      "method": "getCurrency",
      "params": {
        "currency": "ETH"
      },
      "id": 123
    }));
})

and its strange, if i combile code in 2 files, then code use rpc-websockets will response immeditely.

On a Mac Mini 1 is 0.13s user 0.03s system 50% cpu 0.307 total and 2 is 0.11s user 0.03s system 46% cpu 0.289 total.
rpc-websockets does some computation with ws data, hence the overhead. But this is nowhere 5 or 10 seconds.

I found out the problem:
Reason is node version. I removed node 8.9 on my Windows Creators then reinstall node 6.x.