YT-DLP --live-from-start Slow download speed On Youtube

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I'm running yt-dlp version 2023.07.06 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
USA
Provide a description that is worded well enough to be understood
Downloading livestream from youtube that currently still live streaming has been very slow. What seem to be the issue?
Normally I will be downloading 50 mbps, but now it is slower.
I can still download a normal video at fast speed without any issue.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
C:\Users\Desktop\Downloads\yt-dlp>yt-dlp -vU --live-from-start https://www.youtube.com/watch?v=Pd9YWxxrI1E
[debug] Command-line config: ['-vU', '--live-from-start', 'https://www.youtube.com/watch?v=Pd9YWxxrI1E']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[b532a3481] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg 6.0-full_build-www.gyan.dev (setts), ffprobe 6.0-full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.18.0, brotli-1.0.9, certifi-2023.05.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-11.0.3
[debug] Proxy map: {}
[debug] Loaded 1855 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>Current Build Hash: 5ff3e702171a50175c34397494e2d18ce35d771c2110b1e59bd173ec2fb352aa
yt-dlp is up to date<EMAIL_ADDRESS>[youtube] Extracting URL: https://www.youtube.com/watch?v=Pd9YWxxrI1E
[youtube] Pd9YWxxrI1E: Downloading webpage
[youtube] Pd9YWxxrI1E: Downloading ios player API JSON
[youtube] Pd9YWxxrI1E: Downloading android player API JSON
[youtube] Pd9YWxxrI1E: Downloading MPD manifest
[youtube] Pd9YWxxrI1E: Downloading MPD manifest
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec:vp9.2, channels, acodec, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), channels, acodec, lang, proto, size, br, asr, vext, aext, hasaud, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] Pd9YWxxrI1E: Downloading 1 format(s): 247+140
[debug] Invoking dashsegments downloader on "https://manifest.googlevideo.com/api/manifest/dash/expire/1692617960/ei/iPjiZIPtMrOj_9EPxeWEYA/ip/<IP_ADDRESS>/id/Pd9YWxxrI1E.1/source/yt_live_broadcast/requiressl/yes/tx/24540589/txs/24540582%2C24540583%2C24540584%2C24540585%2C24540586%2C24540587%2C24540588%2C24540589/as/fmp4_audio_clear%2Cwebm_audio_clear%2Cwebm2_audio_clear%2Cfmp4_sd_hd_clear%2Cwebm2_sd_hd_clear/spc/UWF9f8x3DCnJge732mEBXyglLNBZjXk/vprv/1/pacing/0/itag_bl/376%2C377%2C384%2C385%2C612%2C613%2C617%2C619%2C623%2C628%2C655%2C656%2C660%2C662%2C666%2C671/keepalive/yes/fexp/24007246/itag/0/playlist_type/DVR/sparams/expire%2Cei%2Cip%2Cid%2Csource%2Crequiressl%2Ctx%2Ctxs%2Cas%2Cspc%2Cvprv%2Citag%2Cplaylist_type/sig/AOq0QJ8wRAIgdPMXbuMxr6r7qMf11o4kamf3nPCQQm10719WINA922oCIGtt0mEEv5NAMDA_8zO4YWfpZa0sJfmGrJAqYFPB7icc", "https://manifest.googlevideo.com/api/manifest/dash/expire/1692617960/ei/iPjiZIPtMrOj_9EPxeWEYA/ip/<IP_ADDRESS>/id/Pd9YWxxrI1E.1/source/yt_live_broadcast/requiressl/yes/tx/24540589/txs/24540582%2C24540583%2C24540584%2C24540585%2C24540586%2C24540587%2C24540588%2C24540589/as/fmp4_audio_clear%2Cwebm_audio_clear%2Cwebm2_audio_clear%2Cfmp4_sd_hd_clear%2Cwebm2_sd_hd_clear/spc/UWF9f8x3DCnJge732mEBXyglLNBZjXk/vprv/1/pacing/0/itag_bl/376%2C377%2C384%2C385%2C612%2C613%2C617%2C619%2C623%2C628%2C655%2C656%2C660%2C662%2C666%2C671/keepalive/yes/fexp/24007246/itag/0/playlist_type/DVR/sparams/expire%2Cei%2Cip%2Cid%2Csource%2Crequiressl%2Ctx%2Ctxs%2Cas%2Cspc%2Cvprv%2Citag%2Cplaylist_type/sig/AOq0QJ8wRAIgdPMXbuMxr6r7qMf11o4kamf3nPCQQm10719WINA922oCIGtt0mEEv5NAMDA_8zO4YWfpZa0sJfmGrJAqYFPB7icc"
[dashsegments] Total fragments: unknown (live)
[download] Destination: Rain Sounds For Sleeping - 99% Instantly Fall Asleep With Rain And Thunder Sound At Night [Pd9YWxxrI1E].f247.mkv
[debug] File locking is not supported. Proceeding without locking
[dashsegments] Total fragments: unknown (live)
[download] Destination: Rain Sounds For Sleeping - 99% Instantly Fall Asleep With Rain And Thunder Sound At Night [Pd9YWxxrI1E].f140.mkv
[debug] [youtube] [Pd9YWxxrI1E] Generating fragments for format 247
[debug] [youtube] [Pd9YWxxrI1E] Generating fragments for format 140
[download]  903.20KiB at   71.18KiB/s (00:00:21) (frag 2/9837)
[download]  159.71KiB at   12.46KiB/s (00:00:20) (frag 2/9837)

WTF?! Can someone explain me this?! Btw. SeFlow Provider Warwasa KVM Dedicated Server I tested connection https://prnt.sc/W51bEM5-ztoJ
https://prnt.sc/kA91Q8DiTmB_
The download speed is 84kb/s WTF?? .. For the wget I got 58MB/s
https://prnt.sc/VIsA9nR-gR7v

Use -N


troposphere-cli

@markpeek released the cli I'm using to manage stacks if you want to give a try: https://github.com/Omixy/troposphere-cli/blob/master/trop/init.py
Will be happy to submit a PR if you like it.
Cheers,

@jeanphix looks nice! I'd be happy to add it if you want to PR it.

@markpeek Ok, will send it later today.

@jeanphix Is there a PR for this yet? Keen to see this merged :smile:

@jeanphix it would be nice if it supported transforms (package) - then implementing this would make more sense #617.

@tdi

it would be nice if it supported transforms (package)

what do you mean ?

@jeanphix what I mean do the same in the CLI as what aws cloudformation package is doing to AWS::Serverless templates


refactor/SAFEApp: MAID-2554 - move asynchronous operations outside of…

… class constructor to imprive error handling and coverage

Coverage increased (+0.07%) to 91.932% when pulling 296a2a374cad09d08836ee2c57bb65f56e4f10e8 on hunterlester:maid-2554 into 19d8d06577305b3bb139edd9da2bfee14aa19a9c on maidsafe:master.


chore: release main

:robot: I have created a release beep boop
auto-instrumentations-node: 0.37.1
0.37.1 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

dependencies

@opentelemetry/instrumentation-amqplib bumped from ^0.32.4 to ^0.32.5
@opentelemetry/instrumentation-aws-lambda bumped from ^0.35.2 to ^0.35.3
@opentelemetry/instrumentation-aws-sdk bumped from ^0.34.2 to ^0.34.3
@opentelemetry/instrumentation-bunyan bumped from ^0.31.3 to ^0.31.4
@opentelemetry/instrumentation-cassandra-driver bumped from ^0.32.3 to ^0.32.4
@opentelemetry/instrumentation-connect bumped from ^0.31.3 to ^0.31.4
@opentelemetry/instrumentation-dataloader bumped from ^0.4.2 to ^0.4.3
@opentelemetry/instrumentation-dns bumped from ^0.31.4 to ^0.31.5
@opentelemetry/instrumentation-express bumped from ^0.32.3 to ^0.32.4
@opentelemetry/instrumentation-fs bumped from ^0.7.3 to ^0.7.4
@opentelemetry/instrumentation-fastify bumped from ^0.31.3 to ^0.31.4
@opentelemetry/instrumentation-generic-pool bumped from ^0.31.3 to ^0.31.4
@opentelemetry/instrumentation-graphql bumped from ^0.34.2 to ^0.34.3
@opentelemetry/instrumentation-hapi bumped from ^0.31.3 to ^0.31.4
@opentelemetry/instrumentation-ioredis bumped from ^0.34.2 to ^0.34.3
@opentelemetry/instrumentation-knex bumped from ^0.31.3 to ^0.31.4
@opentelemetry/instrumentation-koa bumped from ^0.34.5 to ^0.34.6
@opentelemetry/instrumentation-lru-memoizer bumped from ^0.32.3 to ^0.32.4
@opentelemetry/instrumentation-memcached bumped from ^0.31.3 to ^0.31.4
@opentelemetry/instrumentation-mongodb bumped from ^0.34.3 to ^0.35.0
@opentelemetry/instrumentation-mongoose bumped from ^0.32.3 to ^0.32.4
@opentelemetry/instrumentation-mysql bumped from ^0.33.2 to ^0.33.3
@opentelemetry/instrumentation-mysql2 bumped from ^0.33.3 to ^0.33.4
@opentelemetry/instrumentation-nestjs-core bumped from ^0.32.4 to ^0.32.5
@opentelemetry/instrumentation-net bumped from ^0.31.3 to ^0.31.4
@opentelemetry/instrumentation-pg bumped from ^0.35.2 to ^0.35.3
@opentelemetry/instrumentation-pino bumped from ^0.33.3 to ^0.33.4
@opentelemetry/instrumentation-redis bumped from ^0.34.6 to ^0.34.7
@opentelemetry/instrumentation-redis-4 bumped from ^0.34.5 to ^0.34.6
@opentelemetry/instrumentation-restify bumped from ^0.32.3 to ^0.32.4
@opentelemetry/instrumentation-router bumped from ^0.32.3 to ^0.32.4
@opentelemetry/instrumentation-socket.io bumped from ^0.33.3 to ^0.33.4
@opentelemetry/instrumentation-tedious bumped from ^0.5.3 to ^0.5.4
@opentelemetry/instrumentation-winston bumped from ^0.31.3 to ^0.31.4
@opentelemetry/resource-detector-alibaba-cloud bumped from ^0.27.6 to ^0.27.7
@opentelemetry/resource-detector-aws bumped from ^1.2.4 to ^1.2.5
@opentelemetry/resource-detector-container bumped from ^0.2.4 to ^0.2.5
@opentelemetry/resource-detector-gcp bumped from ^0.28.2 to ^0.28.3

auto-instrumentations-web: 0.32.3
0.32.3 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

dependencies

@opentelemetry/instrumentation-document-load bumped from ^0.32.2 to ^0.32.3
@opentelemetry/instrumentation-user-interaction bumped from ^0.32.3 to ^0.32.4

contrib-test-utils: 0.33.4
0.33.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-amqplib: 0.32.5
0.32.5 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

instrumentation-aws-lambda: 0.35.3
0.35.3 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-aws-sdk: 0.34.3
0.34.3 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

dependencies

@opentelemetry/propagation-utils bumped from ^0.29.4 to ^0.29.5

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

instrumentation-bunyan: 0.31.4
0.31.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-cassandra-driver: 0.32.4
0.32.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

instrumentation-connect: 0.31.4
0.31.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-dataloader: 0.4.3
0.4.3 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-dns: 0.31.5
0.31.5 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-document-load: 0.32.3
0.32.3 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-express: 0.32.4
0.32.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-fastify: 0.31.4
0.31.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-fs: 0.7.4
0.7.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-generic-pool: 0.31.4
0.31.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-graphql: 0.34.3
0.34.3 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-hapi: 0.31.4
0.31.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-ioredis: 0.34.3
0.34.3 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

instrumentation-knex: 0.31.4
0.31.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-koa: 0.34.6
0.34.6 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-long-task: 0.32.5
0.32.5 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-lru-memoizer: 0.32.4
0.32.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

instrumentation-memcached: 0.31.4
0.31.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

instrumentation-mongodb: 0.35.0
0.35.0 (2023-06-12)
Features

mongodb: collect mongodb4 metrics (#1170) (988e1f8)

Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

instrumentation-mongoose: 0.32.4
0.32.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

instrumentation-mysql: 0.33.3
0.33.3 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

instrumentation-mysql2: 0.33.4
0.33.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

instrumentation-nestjs-core: 0.32.5
0.32.5 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-net: 0.31.4
0.31.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-pg: 0.35.3
0.35.3 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

instrumentation-pino: 0.33.4
0.33.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-redis: 0.34.7
0.34.7 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

instrumentation-redis-4: 0.34.6
0.34.6 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

instrumentation-restify: 0.32.4
0.32.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-router: 0.32.4
0.32.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-socket.io: 0.33.4
0.33.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

instrumentation-tedious: 0.5.4
0.5.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

instrumentation-user-interaction: 0.32.4
0.32.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

instrumentation-winston: 0.31.4
0.31.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

@opentelemetry/propagation-utils: 0.29.5
Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

@opentelemetry/resource-detector-alibaba-cloud: 0.27.7
Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

@opentelemetry/resource-detector-aws: 1.2.5
Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

@opentelemetry/resource-detector-container: 0.2.5
Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

@opentelemetry/resource-detector-gcp: 0.28.3
Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

resource-detector-instana: 0.4.4
0.4.4 (2023-06-12)
Bug Fixes

deps: update otel core experimental to ^0.40.0 (#1527) (4e18a46)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.3 to ^0.33.4

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/resource-detector-alibaba-cloud-v0.27.7 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/resource-detector-container-v0.2.5 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/resource-detector-gcp-v0.28.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/resource-detector-instana-v0.4.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/auto-instrumentations-node-v0.37.1 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/auto-instrumentations-web-v0.32.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/propagation-utils-v0.29.5 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/contrib-test-utils-v0.33.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-amqplib-v0.32.5 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-dataloader-v0.4.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-fs-v0.7.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-lru-memoizer-v0.32.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-mongoose-v0.32.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-socket.io-v0.33.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-tedious-v0.5.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-aws-lambda-v0.35.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-aws-sdk-v0.34.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-bunyan-v0.31.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-cassandra-driver-v0.32.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-connect-v0.31.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-dns-v0.31.5 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-express-v0.32.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-fastify-v0.31.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-generic-pool-v0.31.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-graphql-v0.34.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-hapi-v0.31.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-ioredis-v0.34.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-knex-v0.31.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-koa-v0.34.6 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-memcached-v0.31.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-mongodb-v0.35.0 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-mysql-v0.33.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-mysql2-v0.33.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-nestjs-core-v0.32.5 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-net-v0.31.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-pg-v0.35.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-redis-v0.34.7 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-redis-4-v0.34.6 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-restify-v0.32.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-router-v0.32.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-winston-v0.31.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-document-load-v0.32.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-long-task-v0.32.5 :sunflower:


Feat/improvement 1.0

restore back the hidden charts in the following. data is still not ready
/blood-donation
/organ-donation
/covid
/peka-b40

issue:

incorrect data format for organ donation bottom-right chart --> bar_reasons

re-hide the charts until datasets are ready. this merge will only concern the data_as_of timestamps


component with v-cloak not loading

I am using a fresh install of latest version of laravel and adminlte-laravel.
The login page is not able to display because of the v-cloak in <div id="app" v-cloak>.
It seems that the VUE.js is not loading in this situation.

As you can see at:
https://vuejs.org/v2/api/#v-cloak
Vue put this directive on components to allow users avoid
https://en.wikipedia.org/wiki/Flash_of_unstyled_content
This directive will dissapears once the vue instance is ready so I think you maybe have a problem tih vue not loading? Please could you show us an example? DO you have any javascript errors in Browser console?

Thank you Acacha. I finally figure out it is not a bug. I am new to VUE so I don't have any vue instance in my code  and the clean install also do not come with any vue instance in the login module and other v-cloak included module , thus the vue is never being loaded.
I just initiate an empty vue instance and it will load and that the v-cloak will not hide the content any more.
I am not sure if only me being to green to this or you may want to add this as reminder for the new comers.
Anyway, thank you for making and managing such a good package!

I never have a problem like this because prepackaged public/js/app.js comes with vue instance defined so I don't know how you arrive to that problem...
You colud also recreate public files form resources using Laravel elixir and executing npm run dev

Hello acacha,
I have the same problem, after a clean installation of laravel and adminlte, I cannot see the /register or /login form.
I fixed the problem for me, but I think this is a bug in your project. Vue isn't initialized by default...

Laravel has been changed how it exposes Token to javascript. I already changes this in source code but now I see I don't have published correctly compiled files. You can solve the problem with a new fresh installation (I released a new tag) or running npm run dev

https://github.com/acacha/adminlte-laravel/commit/22237bd3afbcbb7a07fa17c99fa17568e9da11fe


datepicker-toggle with outline appearance toggle go out it's normal position  in Edge

Bug:
datepicker-toggle with outline appearance toggle go out it's normal position
What is the expected behavior?
toggle must be verically align to middle
What is the current behavior?
toggle go out its normal position in Edge
What are the steps to reproduce?
Open this url in Edge
https://stackblitz.com/angular/deqmggxqllm

i have proposed a pullrequest to resolve this
https://github.com/angular/material2/pull/13591

Hi @jelbourn what about the resolution of this problem ?


Update OmiseGo

The details of OmiseGo

Cool, I know that in OmiseGo they are also building Plasma. If you have any idea about this, please pull your requests ! Thx !


Add Pull Request template

Add Pull Request Template
Description
Add a Pull Request template to root directory to facilitate future contributions.
Fixes #363
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

[x] Forked repository reproduced existing CI tests

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Thanks, mate.

@Benardi kindly modify the readme.md and link this in Start Contributing section.

Hello @tallalj, do you have another request for this PR?

looks awesome to me  @IonesioJunior  :)

Awesome! Thanks, @tallalj, @hericlesme, and @Benardi for this amazing contribution! : rocket:


Punishment bar

Pull Request Test Coverage Report for Build 318158899

5 of 17 (29.41%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 24.447%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/charts/Bar/Bar.tsx
5
17
29.41%

Totals

Change from base Build 317483176:
-0.02%

Covered Lines:
310

Relevant Lines:
1310

💛  - Coveralls


issue #9 - working on solution to focus lost problem

Signed-off-by: Brian Fitzpatrick<EMAIL_ADDRESS>

This seems to fix the issue, but I'm having problems locally repeating it from run to run. It seems to work the first time and then fails the next time I test locally.

I cannot reproduce the issue locally neither.
Can you try to modify the .travis.yml to remove the --silent when calling npm test please? I hope we will more information when it is failing

Turned test off --silent in travis.yml, so hopefully that will show something

Not sure this is helpful - https://travis-ci.org/camel-tooling/vscode-yeoman/builds/498185791

My npm and node versions are different than Travis is reporting... locally I have npm 6.8.0 and node 10.15.0, but Travis is building with node 8.15.0 and npm 6.4.1 -- wonder if that's part of it?

My npm and node versions are different than Travis is reporting... locally I have npm 6.8.0 and node 10.15.0, but Travis is building with node 8.15.0 and npm 6.4.1 -- wonder if that's part of it?

worth trying to upgrade. For node_js you can specify it this way https://github.com/jboss-fuse/vscode-atlasmap/blob/master/.travis.yml#L2

Well, bumping to version 10 seems to have moved us further - but now we're seeing different errors... https://travis-ci.org/camel-tooling/vscode-yeoman/builds/498205143


Fix module import

Pull Request: Fix Incorrect Module Import in layers.py
Summary
This pull request addresses an issue with an incorrect module import in the axlearn/common/quantized_dot_general/layers.py file. The import and usage of the Context class from the aqt_dot_general module have been corrected to use the appropriate Context class from the aqt_utils module.
Changes
1. Import Correction:

Changed the import from aqt.jax.v2.aqt_dot_general to aqt.jax.v2.utils and aliased it as aqt_utils.

2. Context Class Usage:

Updated the usage of the Context class to use aqt_utils.Context instead of aqt_dot_general.Context.

Code Changes
1. Importing aqt_utils
from aqt.jax.v2 import utils as aqt_utils

2. Taken Reference from the official README of  aqt
context: aqt_dot_general.Context = aqt_dot_general.Context(key=None, train_step=None),

to
context: aqt_utils.Context = aqt_utils.Context(key=None, train_step=None),

Testing

Verified that the changes resolve the AttributeError and the code runs successfully without any issues.

Hey @markblee ,
Could you please take a look at my PR when you get a chance? Thanks!

Hi @markblee,
Both ruomingp and jiarui-lu2 have approved the changes to the PR. Could you please take a final look when you get a chance? Thanks again for your time!
Best,
Vishesh

Hi @vishesh9131, I think PR check was on hold due to a required approval in CI. I've approved it and CI should be starting now

@jiarui-lu2
@ruomingp
@markblee
Do I Need to modify  .circleci/config.yml to include the installation of the latest aqt package, since there is an issue occurring in a CircleCI environment...
I mean modification in  .circleci/config.yml like this :
 build:
    docker:
      - image: circleci/python:3.9
    steps:
      - checkout
      - run:
          name: Install dependencies
          command: |
            python -m pip install --upgrade pip
            pip install aqt
      - run:
          name: Run pytype
          command: pytype -j auto

@jiarui-lu2 @ruomingp @markblee
Do I Need to modify .circleci/config.yml to include the installation of the latest aqt package, since there is an issue occurring in a CircleCI environment... I mean modification in .circleci/config.yml like this :
 build:
    docker:
      - image: circleci/python:3.9
    steps:
      - checkout
      - run:
          name: Install dependencies
          command: |
            python -m pip install --upgrade pip
            pip install aqt
      - run:
          name: Run pytype
          command: pytype -j auto

I don't think upgrading aqt is recommended. Minimum python version supported by axlearn is python3.9, however last time I checked for aqt>=0.5.0, minimum supported python version is python3.10 due to the use of newly introduced typing aliases. If this PR relies on aqt>=0.5.0, I think we should close it until either aqt fixes this issue, or axlearn is ready to upgrade its minimum python version requirements.

Hi @jiarui-lu2 ,
I understand your concerns regarding the aqt package and its compatibility with Python 3.9. I wanted to inform you that the latest version of aqt (>=0.5.0) supports Python 3.10.
Would it be possible to consider upgrading the CircleCI configuration to use Python 3.10? This would allow us to use the latest aqt package and resolve the current issue.
Please let me know your thoughts on this.
Best regards,
@vishesh9131

Hi @jiarui-lu2 ,
I understand your concerns regarding the aqt package and its compatibility with Python 3.9. I wanted to inform you that the latest version of aqt (>=0.5.0) supports Python 3.10. Would it be possible to consider upgrading the CircleCI configuration to use Python 3.10? This would allow us to use the latest aqt package and resolve the current issue. Please let me know your thoughts on this.
Best regards, @vishesh9131

The main concern I have is not of Circle CI. axlearn repo formally supports python3.9 as stated here. Depending on a package aqt>-0.5.0 that has a minimum requirement of python3.10 breaks that support. Which is why I said

I think we should close it until either aqt fixes this issue, or axlearn is ready to upgrade its minimum python version requirements.

Hi @jiarui-lu2 ,
I understand your concern about maintaining Python 3.9 support for the axlearn repo. Given that aqt>=0.5.0 requires Python 3.10, I agree that we should close this PR until either aqt addresses this issue or axlearn is ready to upgrade its minimum Python version requirements.
Thanks for the clarification.
Best,
@vishesh9131

According to discussion, closing PR due to python minimum version support. We should revisit if axlearn increases its minimum python version support to > =3.10

Hey @jiarui-lu2 ,
It was nice talking with you. Let's connect on LinkedIn.

According to the discussions, closing PR due to python minimum version support. We should revisit if axlearn increases its minimum python version support to > =3.10

Hi @jiarui,
Since Axlearn now supports Python 3.10, could you reopen this closed PR? According to the previous discussions, the closure was due to the minimum Python version support issue. Now that the support has been updated, it seems like a good time to revisit.
Best regards,
Vishesh


Add Hide context menu for tiles

Will allow end user to temporarily hide/show a tile, e.g. on a busy dashboard.

Added. Will be in Chromestore version 1.44


refactor: migrate user repo list screen to styled-components

Screenshots

Before
After

Part of #532.

Coverage remained the same at 40.544% when pulling 05b5d87292203cec929912bc9cde62c122202adf on ZahraTee:styled-components-user-repos-screen into 5691f00b5c7a47f405fadba3f560fef55a99d0d3 on gitpoint:master.


FYI: No longer garbles Unicode on xterm

I just figured I'd let you know that I no longer get rekt Unicode after using wsedit on xterm. The issue is mentioned in the readme, so if you can confirm that the problem is resolved then you might as well remove that part from the readme. 🙂

Strange, it's still messy for me. Could you please post your .Xresources (and xterm compile flags, if possible)?
Mine look like this:
xterm*locale: true
xterm*utf8: 1
xterm*eightBitInput: false
xterm*metaSendsEscape: true
xterm*saveLines: 65535
xterm*font: -*-terminus-medium-*-*-*-14-*-*-*-*-*-iso10646-*
xterm*selectToClipboard: true

[boonami@boonami-laptop ~]$ equery u xterm
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for x11-terms/xterm-327:
 U I
 - - Xaw3d    : Add support for the 3d athena widget set
 + + openpty  : Use openpty() in preference to posix_openpt()
 - - toolbar  : Enable the xterm toolbar to be built
 + + truetype : Add support for FreeType and/or FreeType2 fonts
 + + unicode  : Add support for Unicode
 + + xinerama : Add support for the xinerama X11 extension, which is mandatory if you work in multiple monitors setup

I... don't have .Xresources. I'm on OS X, which doesn't use X for windowing.

Oops, my bad. According to http://www.astrobetter.com/blog/2010/08/25/xterm-color/, it is called  .Xdefaults` on OSX.

I don't have that either. Per the article:

For Terminal.app, you can simply use the GUI preferences; it does not read .Xdefaults.

I actually use iTerm, but it's the same deal—it uses GUI settings rather than .Xdefaults, .Xresources, or what have you.

Sorry for not responding for so long, I was a bit busy. After some more testing, I was able to reproduce the issue on a bunch of different linux systems. So I think it's best to leave the warning in and add that it doesn't affect all users (fixed in 8d36c7036a085bc2ebdb95dd856b377214fd2c9d).

Sounds good. Thanks!


update npm registry?

There've been quite a few changes, including the format of config.json ("ip" vs "host" at least).
Pushing an update to npm registry will likely help many users.

Hello,
can you help me? I have install the Plugin and add the IP Adress of my Sony VPL VW 320ES. The Networkmanagment is activated also the Remote Start. But nothing does function. The Projector has no reaction. This is the Failure: „Error getting Power state“.

Hello, in case you were still looking to make this plugin work, you have to add the "ip": "xxx.xxx.xxx.xxx" after the host value under accessories. The error is because the plugin doesn't like the host ip number.
{
"accessory": "sony-sdcp-projector",
"name": "Projector",
"host": "<IP_ADDRESS>",
"ip": "<IP_ADDRESS>"
}
Hope that helps!

Hi. adding "ip": "xxx.xxx.xxx.xxx" worked for me. thanks. if the projector is discinnected and i use the plugin it generates error (which is fine) but also restarts homebridge:
[12/21/2020, 6:14:31 PM] [sony-sdcp-projector] Set CurrentState: true
[12/21/2020, 6:14:31 PM] [sony-sdcp-projector] Turning On
[12/21/2020, 6:14:31 PM] Error: connect EHOSTUNREACH <IP_ADDRESS>:53484 - Local (<IP_ADDRESS>:60031)
at internalConnect (node:net:899:16)
at defaultTriggerAsyncIdScope (node:internal/async_hooks:428:12)
at node:net:991:9
at processTicksAndRejections (node:internal/process/task_queues:75:11)
[12/21/2020, 6:14:31 PM] Got SIGTERM, shutting down Homebridge...
[12/21/2020, 6:14:31 PM] [HubName] INFO - shutdown
[12/21/2020, 6:14:36 PM] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[12/21/2020, 6:14:41 PM] [HB Supervisor] Restarting Homebridge...


Never commit from code, only from Solr

This is the recommended way to handle indexing from Solr's documentation
(https://lucene.apache.org/solr/guide/6_6/near-real-time-searching.html#near-real-time-searching).
Confirmed to work in development. This'll make sync time take 5 minutes
to show up, but will mean reindexes won't result in a ton of hard
commits.

Coverage decreased (-0.2%) to 99.85% when pulling 6054321a55ef688c8d808eb9d2bcf5255b695494 on no_committing into 17a1673a670ec6fe3d0665047ecdb56bde64b65c on master.

We can't deploy this until the changes for this are deployed to SolrCloud.

pul_solr was deployed today to ensure those changes were live.


JavaScript: Testing TicTacToe

In this project, we:

refactored code.
added webpack.
added tests for pure functions using Jest.

Thanks @shloch 👍


AMBARI-25034 Ambari is not updating core-site : "ha.zookeeper.quorum" once a zookeeper server is added or removed (asnaik)

AMBARI-25034 Ambari is not updating core-site : "ha.zookeeper.quorum" once a zookeeper server is added or removed (asnaik)onece a zookeeper server is added or removed (asnaik)
What changes were proposed in this pull request?
Tested in UI, the fix works fine.
How was this patch tested?
(Please explain how this patch was tested. Ex: unit tests, manual tests)
(If this patch involves UI changes, please attach a screen-shot; otherwise, remove this)
Please review Ambari Contributing Guide before opening a pull request.

Hi @hiveww/ @jgolieb  ,
can you please help me review this PR. the issue is reproducible in ambari-2.6.x versions and ambari-2.7.x versions.
attached vide of the issue in JIRA

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/4727/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/4730/
Test FAILed.
Test FAILured.

There is some issues with this code.  I will close thi PR and raise again a new one


docs: fix order

What does this PR do?
Fix docs order and include container methods

Why is it important?

Related issues

@mashail I merged my local branch with current main, that's why you see commits from yugabyte.
My recommendation for OSS contributions would be always use a new branch, not create the commits on main.

@mashail I'm closing this one in favour of the PR in the upstream repo, which includes all your work plus the refinements regarding the docs and CI.
Thanks for your time!

@mashail I merged my local branch with current main, that's why you see commits from yugabyte.
My recommendation for OSS contributions would be always use a new branch, not create the commits on main.

Sure

@mashail I'm closing this one in favour of the PR in the upstream repo, which includes all your work plus the refinements regarding the docs and CI.
Thanks for your time!

Ok let me rebase my main branch


Frontend development

The team has completed the user information and change user information page, and there is a skeleton of the redirect page which will be completed on the next merge. Some tests need to be fixed, I won't merge the PR until those are sorted. This merge will leave only a handful of changes until MVP, the largest being the change password page. I also added some changes to the layout.

It looks like we're still picking up some .vs files, I would like to keep those out of the development branch if at all possible

I added a line to the .gitignore, hopefully .vs folder wont be there in future

I'm having an issue with the account information page. The route is returning status code 500. The same thing happens when I try the same with the old frontend

I'm having an issue with the account information page. The route is returning status code 500. The same thing happens when I try the same with the old frontend

That problem got resolved. This is ready to go I believe.

Read last two commits for more details, but I think this is at MVP minus a few tests.

If this is ready for merge, change the server to the IP instead of localhost and I will approve changes, everything looks great to me!


Remove references to the minimap

Remove references to the minimap
We will not out of the box support minimaps.
https://discord.com/channels/997410333348077620/1009439782402805800/1267398618415894591

Thanks for submitting a issue!
to assign this issue to yourself please comment @aurora-care-bear please assign me


api-linter: 1.67.0 -> 1.67.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/googleapis/api-linter/releases.
meta.description for api-linter is: Linter for APIs defined in protocol buffers
meta.homepage for api-linter is: https://github.com/googleapis/api-linter/
meta.changelog for api-linter is: https://github.com/googleapis/api-linter/releases/tag/v1.67.1
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.67.1 with grep in /nix/store/krshk88yw7wg3xy026s3d26sw950x7p0-api-linter-1.67.1
found 1.67.1 in filename of file in /nix/store/krshk88yw7wg3xy026s3d26sw950x7p0-api-linter-1.67.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

api-linter

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/krshk88yw7wg3xy026s3d26sw950x7p0-api-linter-1.67.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A api-linter https://github.com/r-ryantm/nixpkgs/archive/e4ad7c4345b320377153ca21f44403cd08b92c39.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e4ad7c4345b320377153ca21f44403cd08b92c39#api-linter

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/krshk88yw7wg3xy026s3d26sw950x7p0-api-linter-1.67.1
ls -la /nix/store/krshk88yw7wg3xy026s3d26sw950x7p0-api-linter-1.67.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

api-linter

Maintainer pings
cc @xrelkd for testing.

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

@NixOS/nixpkgs-merge-bot merge


Updated against type-protocols changes

Related to input-output-hk/cardano-node#4221

Closed in favor of #35


PDOException in app/Console/Commands/TeamSpeakCommand.php:81

Error in VATSIM-UK/Core (Laravel)
PDOException in app/Console/Commands/TeamSpeakCommand.php:81
SQLSTATE[HY000] [2002] Connection refused
View on Bugsnag
Stacktrace
app/Console/Commands/TeamSpeakCommand.php:81 - App\Console\Commands\TeamSpeakCommand::handleException
app/Console/Commands/TeamSpeakManager.php:62 - App\Console\Commands\TeamSpeakManager::handle
app/Console/Commands/TeamSpeakCommand.php:41 - App\Console\Commands\TeamSpeakCommand::run

View full stacktrace

An error linked to this issue has been marked as fixed in Bugsnag
PDOException in app/Console/Commands/TeamSpeakCommand.php:81


Multi-node clusters and GenServer exits

Hi, I'm trying to figure out if it's possible to prevent the error from the scheduler genserver when connecting a new node to a cluster.  I know this has been discussed already in #311, but I'm still a little confused...
here's an example Application.ex that I have:
defmodule QuantumTest.Application do
  # See https://hexdocs.pm/elixir/Application.html
  # for more information on OTP Applications
  @moduledoc false

  use Application

  def start(_type, _args) do
    # connect to existing nodes BEFORE starting quantum
    for i <- 1..6, do<EMAIL_ADDRESS>
    # wait for... what?
    # :timer.sleep(1000)

    children = [
      QuantumTest.Scheduler
    ]

    # See https://hexdocs.pm/elixir/Supervisor.html
    # for other strategies and supported options
    opts = [strategy: :one_for_one, name: QuantumTest.Supervisor]
    Supervisor.start_link(children, opts)
  end
end

When I start my first iex session (iex --name<EMAIL_ADDRESS>-S mix), it boots just fine, without any problems.  When I boot the second one (iex --name<EMAIL_ADDRESS>-S mix), it logs an error:
17:35:29.105 [error] GenServer QuantumTest.Scheduler.ExecutorSupervisor terminating
** (stop) killed
Last message: {:EXIT, #PID<0.232.0>, :killed}
State: %ConsumerSupervisor{args: {QuantumTest.Scheduler.ExecutionBroadcaster, QuantumTest.Scheduler.Task.Supervisor, QuantumTest.Scheduler.TaskRegistry}, children: %{}, max_restarts: 3, max_seconds: 5, mod: Quantum.ExecutorSupervisor, name: QuantumTest.Scheduler.ExecutorSupervisor, producers: %{#Reference<0.1712272034.1835532289.184698> => {{#PID<0.235.0>, #Reference<0.1712272034.1835532289.184698>}, 0, 0, 25, 50}}, restarting: 0, restarts: [], strategy: :one_for_one, template: {Quantum.Executor, {Quantum.Executor, :start_link, [{QuantumTest.Scheduler.Task.Supervisor, QuantumTest.Scheduler.TaskRegistry}]}, :temporary, 5000, :worker, [Quantum.Executor]}}

According to my understanding, I'm connecting to the existing node BEFORE starting the quantum process.  But it still logs an error, even if the connection has been successfully ahead of time.
If I introduce a 1 second sleep (as seen commented out in the code above), everything works great, and quantum boots up gracefully with no error on any subsequent node after the first.  Why does the 1 second sleep help?

If you start a process with the name {:global, atom()}, the cluster only starts that process once per cluster. If the node starts before it is connected to the rest of the cluster this means that both the new node and the rest of the cluster have a process running with the same name.
Since the name must be globally unique, one of them will be killed.
My plan is to use swarm in the future to orchestrate the workers. I've no come around to implement this already. This will solve two problems at one:

Nodes can connect to an existing cluster. Both states can be merged together.
If a node disconnects without being properly stoped (eg. network split / power issues / process killed etc.) the rest of the cluster does not restart the node somewhere else. (#334)

@maennchen I think I understand the basic concept behind how :global works, but your statement here is what I don't get: "If the node starts before it is connected to the rest of the cluster this means that both the new node and the rest of the cluster have a process running with the same name"
See my code that I included above, I am connecting to the cluster before starting the quantum process.  From my understanding the code that starts a global process doesn't get run until the quantum scheduler process gets started, is this not the case?
Also, see my comment above about the :timer.sleep call.  If I insert that one second sleep, then the error goes away, indicating that the node is indeed getting connected to the cluster and the name collision never happens.
My question was more about why the sleep would make a difference; why can't just ensuring that the node is getting connected to the cluster before starting the rest of the child processes be enough?

I've upgraded to the latest version of quantum, when I try to start a multi-node cluster using libcluster I get this
17:11:53.855 [info] Application studio exited: Studio.Application.start(:normal, []) returned an error: shutdown: failed to start child: Studio.Scheduler
    ** (EXIT) shutdown: failed to start child: Quantum.TaskRegistry
        ** (EXIT) already started: #PID<43527.2717.0>
{"Kernel pid terminated",application_controller,"{application_start_failure,studio,{{shutdown,{failed_to_start_child,'Elixir.Studio.Scheduler',{shutdown,{failed_to_start_child,'Elixir.Quantum.TaskRegistry',{already_started,<43527.2717.0>}}}}},{'Elixir.Studio.Application',start,[normal,[]]}}}"}
Kernel pid terminated (application_controller) ({application_start_failure,studio,{{shutdown,{failed_to_start_child,'Elixir.Studio.Scheduler',{shutdown,{failed_to_start_child,'Elixir.Quantum.TaskRegis

it crashes the application, before it used to exit the task but the app would still run
Btw I'm using the ErlangHosts Strategy with libcluster.


Returns the status code in the result

The /report command doesn't return the status_code field which is available in the output from the vegeta report CLI command.
The problem is that the status_code block returns the HTTP status code (key) mapped to the code cound (value). Swagger OpenAPI 2.0 doesn't support dynamic keys.
One possible way is to extract the status code into a map[string]string type and then adapt it to the spec, where the spec could be of type
      statusCodes:
        type: object
        properties:
          code:
            type: string
          count:
            type: integer

hello! can i grab this issue?
i have been using go for a year now, but never use go-swagger
can u give me some hint for my start on solving the problem? i tried to explore the code but found no start point.

@andrysds definitely! Let me know if you need any help.

Fixed in #20


[TACHYON-740] Remove 'LOG' in TieredBlockStoreTestUtils

https://tachyon.atlassian.net/browse/TACHYON-740
Variable LOG is not used in TieredBlockStoreTestUtils. Please remove it.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/4442/
Test PASSed.

+1 LGTM


feat: improve icon generator, use icon*.NODE_ENV.png

Details

[x] closes #163
[x] If RFC, it has been approved for implementation.

Code of Conduct

[x] I agree to follow this project's Code of Conduct
[x] I checked the current PR for duplication.

Interesting fallback strategy. This can be further improved to work for other assets as well!

Thanks! I'm also thinking this is a bit narrow and too explicit, for general assets management can be implemented some sort of pattern matching, but i'm not sure what exactly as of now..

@gitpash can you review and test out the new image generator? I did some fun caching as well as applying the environment variable into the name for both base icons, as well as developer-provided icons as well!

@gitpash can you review and test out the new image generator? I did some fun caching as well as applying the environment variable into the name for both base icons, as well as developer-provided icons as well!

It doesn't work for me, although it may be due to my local config, basically what I'm doing is running the fork of Plasmo and test in one of the examples directory.. when I log iconNameList I'm having
iconNameList:  [
  'icon.undefined.png',
  'icon.png',
  'icon512.undefined.png',
  'icon512.png',
  'icon-512.undefined.png',
  'icon-512.png',
  'icon-512x512.undefined.png',
  'icon-512x512.png',
  'icon1024.undefined.png',
  'icon1024.png',
  'icon-1024.undefined.png',
  'icon-1024.png',
  'icon-1024x1024.undefined.png',
  'icon-1024x1024.png'
]

oh oops... we set the environment variable at run-time, so the iconNameList must be created at run-time before the variable is set. By putting it at top-level, it turned into undefined! Derp, I'mma push a fix out soon!


[xmlreport] when a filepath is in multiple source dirs, choose the highest one

fixes #578

@alex Will https://github.com/nedbat/coveragepy/issues/578#issuecomment-413881957 sill work with your update?

Maybe! I'm not sure. I'm also now many yaks deep and mostly turned my attention towards: https://github.com/nedbat/coveragepy/issues/1147

@Alex 😁 nice! Well I put another pr for the docs.

@alex Will #578 (comment) sill work with your update?

@christopherpickering Sorry for jumping in on this, but is this what is still needed to merge this PR? And if so, why is this not covered by the tests?

@gro1m I'm not sure, that was a long time ago.

@christopherpickering I understand that, on the other hand the change is small: the source_path is traversed bottom up from the filesystem tree, i.e. deepest level first to top-level and all tests are green. From that perspective, I do not really see what holds this back and I think to avoid ambiguity it would be really great to have the whole file path and not just the filename. So it would be great if someone could tell what is needed to merge this PR...

Is this still valid? Seems like it passed almost all checks but is a bit old

Is this still valid? Seems like it passed almost all checks but is a bit old

I think so, but I am not a contributor to the project. In the end, we could also fix the issue by using the workaround in https://github.com/nedbat/coveragepy/issues/578#issuecomment-413881957.

At this point, whatever the motivation for this is has long been overcome by events.


Add account data types

Summary
Changes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

8 of 18 (44.44%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 48.597%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/datasources/accounts/accounts.datasource.ts
0
1
0.0%

src/domain/accounts/accounts.repository.ts
0
1
0.0%

src/routes/accounts/accounts.controller.ts
2
3
66.67%

src/routes/accounts/entities/account-data-type.entity.ts
5
8
62.5%

src/routes/accounts/accounts.service.ts
1
5
20.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
4210

Relevant Lines:
6988

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

9 of 20 (45.0%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 48.597%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/datasources/accounts/accounts.datasource.ts
0
1
0.0%

src/domain/accounts/accounts.repository.ts
0
1
0.0%

src/routes/accounts/accounts.controller.ts
2
3
66.67%

src/routes/accounts/accounts.service.ts
1
5
20.0%

src/routes/accounts/entities/account-data-type.entity.ts
6
10
60.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
4211

Relevant Lines:
6990

💛  - Coveralls


Expose Helper Functions

Along with convert(), expose additional helper functions that help decipher the .ics file.
An initial example: unique_keys, a function that returns an array of all of the unique data points that make up each event.

Another potential helper function is event_count, a fast function that can return the number of events in an .ics file.


minor: Adding get secret by name

Adding get secret by name api

:tada: This PR is included in version 2.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Suggestion to add links to resources' log-related pages

Hello,
I currently use this page and its "Service Specific Schemes" section to list in a simple way which resources support diagnostic logs and their tutorials. If I am completely wrong, please tell me so 😄
I suggest adding links to the rows that indicate "Schema not available".
For ExpressRoute:

Monitoring Azure ExpressRoute
Monitoring ExpressRoute data reference

For Azure Virtual Network:

https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-nsg-manage-log
https://docs.microsoft.com/en-us/azure/virtual-network/monitor-virtual-network-reference#resource-logs

For Azure Network Gateways:

https://docs.microsoft.com/en-us/azure/vpn-gateway/troubleshoot-vpn-with-azure-diagnostics
https://docs.microsoft.com/en-us/azure/vpn-gateway/monitor-vpn-gateway

Have a good day,
Loris

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

ID: d2d8c718-c381-78b0-0e0c-99e8e3a157ae
Version Independent ID: 26f65c36-a172-37bb-b906-a23b46ba806d
Content: Azure resource logs supported services and schemas - Azure Monitor
Content Source: articles/azure-monitor/essentials/resource-logs-schema.md
Service: azure-monitor
Sub-service: essentials
GitHub Login: @rboucher
Microsoft Alias: robb

@loris-s-sonarsource Thanks for your comment. We will review the issue and get back to you shortly.

@loris-s-sonarsource Thanks for the feedback! I have fixed the referenced change, and the change should reflect on the doc once approved by content author. We will now proceed to close this thread. If there are further questions regarding this matter, please revert and we will gladly continue the discussion.


How to Hook in the Embeded Ohif Library and send data to a different Location

Hello team,
I have succesfuly ran the embeded Ohif Library.
I want to find a way of hooking in and get measurement data from tools (especially the arow anotate )and save it to a different location without making direct changes in the OHIF code.
What is the best way to do this.
are there call backs that can do this ??
Thanks in advance

You can look into the data sources https://docs.ohif.org/configuration/dataSources/introduction


Enable HOBO data uploads

This PR closes https://github.com/aqualinkorg/aqualink-app/issues/717

@echaidemenos I should have given more details.
This will use the same data upload module. So we are ONLY interested in the temperature data. We won't be uploading survey images at this point.


add royalty to collection creation

@vikiival  added the ability to set royalty on collection (kusama / polkadot assethub)
this royalty will be the default one for all the NFTs in the collection
https://github.com/kodadot/stick/pull/148
need to use this new capability in FE

add the fields to the collection mint form
set_attribute to put the royalty on chain

👋🏼


[ADnD 2E Revised] More sheet settings and books

Changes / Comments
All changes described on the forum: https://app.roll20.net/forum/permalink/10603859/
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[X] Is this a bug fix?
[X] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.


It is not working with spring boot 3.3+

Recently I am upgrading my microservices 3.1+ to 3.3+ after that looking certificate not creating or not renew. Getting this error
Caused by: java.lang.NoSuchFieldError: sphincsPlus_shake_256
at org.bouncycastle.operator.DefaultSignatureAlgorithmIdentifierFinder.(Unknown Source)
at org.bouncycastle.operator.jcajce.JcaContentSignerBuilder.build(Unknown Source)
at com.github.valb3r.letsencrypthelper.tomcat.TomcatWellKnownLetsEncryptChallengeEndpointConfig.selfSign(TomcatWellKnownLetsEncryptChallengeEndpointConfig.java:416)
at com.github.valb3r.letsencrypthelper.tomcat.TomcatWellKnownLetsEncryptChallengeEndpointConfig.createBasicKeystoreWithSelfSignedCert(TomcatWellKnownLetsEncryptChallengeEndpointConfig.java:392)
at com.github.valb3r.letsencrypthelper.tomcat.TomcatWellKnownLetsEncryptChallengeEndpointConfig.createBasicKeystoreIfMissing(TomcatWellKnownLetsEncryptChallengeEndpointConfig.java:301)
at com.github.valb3r.letsencrypthelper.tomcat.TomcatWellKnownLetsEncryptChallengeEndpointConfig$CustomTomcatServletWebServerFactoryCustomizer.customize(TomcatWellKnownLetsEncryptChallengeEndpointConfig.java:265)
at com.github.valb3r.letsencrypthelper.tomcat.TomcatWellKnownLetsEncryptChallengeEndpointConfig$CustomTomcatServletWebServerFactoryCustomizer.customize(TomcatWellKnownLetsEncryptChallengeEndpointConfig.java:252)
at com.github.valb3r.letsencrypthelper.tomcat.TomcatWellKnownLetsEncryptChallengeEndpointConfig$CustomTomcatServletWebServerFactoryCustomizer$$SpringCGLIB$$0.customize()
at org.springframework.boot.web.server.WebServerFactoryCustomizerBeanPostProcessor.lambda$postProcessBeforeInitialization$0(WebServerFactoryCustomizerBeanPostProcessor.java:72)
at org.springframework.boot.util.LambdaSafe$Callbacks.lambda$invoke$0(LambdaSafe.java:287)
at org.springframework.boot.util.LambdaSafe$LambdaSafeCallback.invoke(LambdaSafe.java:159)

@bishwajitcse That's weird, as sphincsPlus_shake_256 is available in BouncyCastle 1.72+ and recent Spring also does seem to work (though it may depend on algorithm list, so not so sure).
Can you check dependency tree for older BouncyCastle on class path (<1.72)

@bishwajitcse That's weird, as sphincsPlus_shake_256 is available in BouncyCastle 1.72+ and recent Spring also does seem to work (though it may depend on algorithm list, so not so sure). Can you check dependency tree for older BouncyCastle on class path (<1.72)

Ok. I will check it more. Thanks


Customize BarcodeDetector

What do you think about features:

Use com.google.android.gms.vision.barcode.BarcodeDetector as singleton by default instead of creating new instance inside init() function. Do we really need different detectors in different readers?

class BarcodeDetectorHolder {
  private static  BarcodeDetector detector;

  static BarcodeDetector getBarcodeDetector(Context context) {
    if (detector == null)
      detector = new BarcodeDetector.Builder(context.getApplicationContext()).setBarcodeFormats(Barcode.QR_CODE).build();
    return detector;
  }
}

  public QREader(final Builder builder) {
    if (barcodeDetector == null)
      barcodeDetector = BarcodeDetectorHolder.getBarcodeDetector(builder.context);
   ...
   }

Allow to set internal BarcodeDetector in Builder. It can be useful, if someone will want to scan not only qr codes.

BarcodeDetector myDetector = ...; //set few barcode formats.
QRReader r = QREader.Builder(MainActivity.this, surfaceView, listener).setDetector(myDetector)

I already made it in my project and can make PR. But I'm not sure about first case.

@punksta I donot fully understand what you are proposing here. Can you provide me with more details.

@nisrulz added samples;

@punksta I think using Singleton would be a nice change as cases of having multiple instances of the same QREader class are very less.
However I would not want to extend QREader to start supporting other reading capability just because I made it specifically to read QRCodes. However there is no harm in providing a config function that open ups the functionality if its desired. The way of implementation should be in such a way that it does not alienate the api to deviate from its core cause of reading QRCodes.
Would love to hear your thoughts on this too.

@nisrulz
I agree. Where is another case of supporting external BarcodeDetector: using one instance for scanning of locally images and using in your reader.


Loader hints

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/59
Originally created by @joshlambert on 2018-08-02 12:13:58

During a discussion with a member of the larger data community, they made the point that it can be helpful for extractors to be aware of the capability of a loader. For example if you are extracting JSON content, it could be helpful to know if the loader/DW is capable of storing JSON documents.
This way the extractor could make some informed decisions about how to structure content. For example our usage ping data, with some fields being JSON, could be an interesting example. (Rather than having to break each field out into individual columns.)

View 3 previous comments from the original issue on GitLab


fix StringUtils.upperCase(String str) java doc

This MR fixes a typo with the StringUtils.upperCase(String str) javadoc
Updated #lowerCase to #upperCase in scenarios where Locale needs to be provided for case transformation

Codecov Report

Merging #911 (00e775d) into master (3228ab0) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #911      +/-   ##
============================================
- Coverage     91.73%   91.73%   -0.01%
+ Complexity     7438     7437       -1
============================================
  Files           188      188
  Lines         15953    15953
  Branches       2999     2999
============================================
- Hits          14635    14634       -1
  Misses          726      726
- Partials        592      593       +1

Impacted Files
Coverage Δ

...ain/java/org/apache/commons/lang3/StringUtils.java
98.71% <ø> (ø)

...apache/commons/lang3/reflect/ConstructorUtils.java
84.00% <0.00%> (-2.00%)
:arrow_down:

Continue to review full report at Codecov.

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


The UT flakeyness is actually a bug in the BucketCache.notifyFileCachingCompleted logic. The UT needs to be changed as well to consistently reproduce the issue, so I will address it in a separate jira.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 53s
Docker mode activated.


Support to data format MSSQL

IN QFIELD CAN I USE DATA FORMAT MSSQL?
IF NOT IS THIS PROVIDED IN NEXT VERSIONS?
THANK YOU

You can use this format via the qfieldsync or offline editing plugin.
On December 26, 2016 8:27:20 PM GMT+01:00, leonardo57<EMAIL_ADDRESS>wrote:

IN QFIELD CAN I USE DATA FORMAT MSSQL?
IF NOT IS THIS PROVIDED IN NEXT VERSIONS?
THANK YOU
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/opengisch/OSGeo4A/issues/16

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Update docs

Updating documents from:

What is rocWMMA
Installation
Programmers guide
README.md

For some reason the updated RTD config that uses mambaforge with doxygen 1.9.8 fails to pull the API functions correctly
Setting WARN_IF_DOC_ERROR to NO will avoid the Doxygen warning when multiple params have the same name

Feedback has been incorporated


unit convertor modified

🛠 Issue (1736)

Closes #1736
Description
Negative values are not accepted as input and a proper alert is displayed.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] I have made this from my own
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] The title of my pull request is a short description of the requested changes.

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@TusharKesarwani @zugzwang03 @harshit-paneri I have done the required changes, please merge this pr


Make simd.h safe for older Ilmbase.h.

We have simd::float4 conversions from and to Imath::V4f. Turns out that
prior to OpenEXR 1.7-ish, there was no V4f. To make things extra fun,
back then OpenEXR/IlmBase did not have any handy #defines to let you
conditionally compile based on the Ilmbase version. Now it does.  So we
punt and only define the (rarely used?) V4f conversions when Ilmbase is
safely >= 2.0, which seems safe moving forward, but this header will
still compile without errors for somebody stuck with Ilmbase 1.0.1
(albeit without the ability to convert to and from V4f, which is moot
anyway for those without such a definition).

Yay! That would be awesome!
In the meanwhile, I'll try to give a huge refresh to IlmBase and OpenEXR in Debian.
Hope it won't be too hard ;-)


Single click action buttons don't show tooltip

Single click action buttons don't show tooltip

This was fixed


[🐞] Extremely unpleasant jumps and flashes for a simple HTML input

Which component is affected?
Qwik Runtime
Describe the bug
I was creating a login form with Qwik. I had to do some validation. I ended up with a very jumpy and flashy field that was not responsive to some characters. This is how it looks:
Video
Reproduction
https://stackblitz.com/edit/qwik-starter-wtnwdb?file=src%2Froutes%2Findex.tsx,src%2Froutes%2Flayout.tsx
Steps to reproduce
1- Create a Qwik project
2- Paste this code:
  const phone = useSignal('');
  const isPhoneEmpty = useComputed$(() => phone.value?.trim() === '');
  const isPhoneInvalid = useSignal(
    () => phone.value?.trim() !== '' && phone.value.length != 11
  );
  return (
    <>
      <input
        value={phone.value}
        onKeyDown$={(e) => (phone.value = e.target.value)}
      />
      {isPhoneEmpty &&
Phone can not be mepty
}
      {isPhoneInvalid &&
Phone is invalid
}
    </>
  );

3- Test it with writing fast in it
System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.3 - /usr/local/bin/pnpm
  npmPackages:
    @builder.io/qwik: ^1.4.3 => 1.4.3
    @builder.io/qwik-city: ^1.4.3 => 1.4.3
    undici: 5.28.2 => 5.28.2
    vite: 4.5.2 => 4.5.2

Additional Information
No response

you're using useSignal the second time when you should use useComputed$
you should use the onInput$ event. This may be why it is jumpy.
you should test the boolean signals by reading .value. This might be causing rerenders which also might cause the jumpiness.

Then generically:

you should use the second argument to events, it is correctly typed too.
bind:value={signal} implements this for you.
for forms, consider using modular-forms
for small reproductions that don't use routing, it's nicer to use https://qwik.dev/playground because you can easily see the generated code

Let me know if you still have trouble after this.

@Nefcanto any update?

@wmertens, today I got a chance (time) to test it. The main point was to use onInput$ instead of onKeyDown$ as you mentioned. While I found that the onInput$ is defined here, it would be awesome if it got its own section on the Events page too. Because I used onKeyDown$ instead of onChange$ based on the content of that page and based on on{EventName}$ formula.
Thank you.

@Nefcanto great to hear it's good now!
If you could spare some time to update the events page so it would have stood out to you, that would be great too!

@wmertens, sorry to answer late. I would love to, but I'm afraid I can't. As I have mentioned many times, I was not able to run a successful clone of Qwik.


clojure: limit jvm warmup phase

this one limits the warmup phase to 5000 posts, decreasing total run time
as an interesting consequence it also slightly speeds up larger data processing (at least on my machine)

Seeing the same speed up...I will try that on the other vm langs.
Main:
| Clojure | 96.90 ms | 1.08 s | 8.89 s | 10.06 s |

This PR:
Clojure:

        Processing time (w/o IO): 97ms
        total: 0.88s memory: 121560k
        Processing time (w/o IO): 98ms
        total: 0.88s memory: 121332k
        Processing time (w/o IO): 98ms
        total: 0.87s memory: 125284k
        Processing time (w/o IO): 99ms
        total: 0.86s memory: 123024k
        Processing time (w/o IO): 96ms
        total: 0.87s memory: 123204k
        Processing time (w/o IO): 101ms
        total: 0.88s memory: 125436k
        Processing time (w/o IO): 99ms
        total: 0.88s memory: 124372k
        Processing time (w/o IO): 96ms
        total: 0.88s memory: 128368k
        Processing time (w/o IO): 98ms
        total: 0.86s memory: 123872k
        Processing time (w/o IO): 98ms
        total: 0.86s memory: 122432k

Clojure:

        Processing time (w/o IO): 1106ms
        total: 2.05s memory: 188796k
        Processing time (w/o IO): 1097ms
        total: 2.06s memory: 182020k
        Processing time (w/o IO): 1083ms
        total: 2.05s memory: 190136k

Clojure:

        Processing time (w/o IO): 9262ms
        total: 10.59s memory: 354256k
        Processing time (w/o IO): 9050ms
        total: 10.31s memory: 331320k
        Processing time (w/o IO): 9054ms
        total: 10.34s memory: 369572k

thanks!
that must be because of the uncertain nature of jvm's jit.. It can vary, i guess.
Just wanted to decrease total time for large collections,.

Running main now shows ~9s so it's not far off.

i was addressing this one
(this one is from yesterday's pr)
rocessing time (w/o IO): 8871ms
        total: 19.02s memory: 332340k
        Processing time (w/o IO): 9052ms
        total: 19.31s memory: 335032k
        Processing time (w/o IO): 8736ms
        total: 18.63s memory: 338596k

so, the total here is 18-19s , and now 10s,
because i removed insanely long warmup phase for huge collections.
thought that waiting 10 extra seconds (unneeded) for every execution was annoying
))


Partial IP match shows as duplicate request

Handling #281510, request #286736 showed as another request from the same IP. When I clicked into that request, it didn't show any matching requests. Looking at the addresses, they are the same but 286736 has an additional digit. (Example - <IP_ADDRESS> vs <IP_ADDRESS>)  Those shouldn't be showing as matching at all.

Never mind, should've dug around a bit first. Duplicate of 482.


Add production of _arguments and _left_env to symbols and allow symbol output to be specified

adds extra symbol entries for

{hash}_arguments - textural clvm sexp of the arguments as specified by the user
{hash}_left_env - specifies whether the matching function's body uses the left side of the env cons to lookup functions and constants (therefore, exclude them from argument decoding).
Adds -g option to enable the extra symbol output in classic.
Adds --symbol-output to specify an output file for symbols

this is one part of https://github.com/Chia-Network/clvm_tools_rs/pull/91 , which supports a vscode debug adapter

it's a bit hard to review as long as it includes the changes from #91. Once that has landed, please rebase this to make it easier to see just the changes in this PR

I'm unsure what you're referring to that this contains from #91 that isn't necessary to its own functioning.  Can you point to a line?


Add janeman98 as reviewer

/assign @sarahmaddox
I want to contribute more. So far, I have 25 commits in this repo.

This change is

/lgtm
/approve
:) yes!

Many thanks, @sarahmaddox !
Working on weekend? I thought today is SAT in Australia.

Ha ha, you got me!


Deployment

Deployment
User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information
Acceptance Criteria
GIVEN a Prework Study Guide website,
WHEN I visit the website using the URL,
THEN I can access my website from any browser

Prework Study guide has now been deployed and is accessible via mifu666.github.io/prework-study-guide


Default headers?

Being able to set default headers would be useful; esp. for things like User-Agent

Hello, feature worth thinking about. As for User-Agent itself, you can just updated it once calling
Smash.setUserAgent("Your-User-Agent")


Windows fixes

Fixes some (not so obvious) compiler issues on Windows with Microsoft Visual Studio 2022.

merge confilicts in intrules.cpp resolved using Matthias version using Int_rules


Could not route to  [..] upload-token, perhaps your object identifier is invalid? [code: 7003]     No route for that URI [code: 7000]

I try to publish to a pages project by using Account Id + API Token within a github action:
on: [push]

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v3
      - name: Publish
        uses<EMAIL_ADDRESS>        with:
          apiToken: ${{ secrets.CF_API_TOKEN }}
          accountId: ${{ secrets.CF_ACCOUNT_ID }}
          command: pages publish src --project-name=unixtimeapp

This fails with:
Could not route to /accounts/***/pages/projects/unixtimeapp/upload-token, perhaps your object identifier is invalid? [code: 7003]
    No route for that URI [code: 7000]

API Token got this permission:
All accounts - Cloudflare Pages:Edit

I am not sure, if it an issue of the API tokens permission or of wrangler itself. I am just here, because the output from the github action pointed me to create an issue here. :)

I also tried it with this other workflow:
jobs:
  deploy:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      deployments: write
    name: Deploy to Cloudflare Pages
    steps:
      - name: Checkout
        uses: actions/checkout@v3
      # Run your project's build step
      # - name: Build
      #   run: npm install && npm run build
      - name: Publish
        uses: cloudflare/pages-action@1
        with:
          apiToken: ${{ secrets.CF_API_TOKEN }}
          accountId: ${{ secrets.CF_ACCOUNT_ID }}
          projectName: unixtimeapp # e.g. 'my-project'
          directory: src # e.g. 'dist'
          gitHubToken: ${{ secrets.GITHUB_TOKEN }}

After re-rolling the token, it works. Maybe it was just taking some time.


ENG-8243-add call in progress event metadata

Call metadata would include the call type (incoming/outgoing) and call progress (ringing/answered/ended/onhold).
Examples of the event:
["CALL_IN_PROGRESS - NO_TARGET - cp=Optional("false") attrs=[type=outgoing, progress=ringing]"]
["CALL_IN_PROGRESS - NO_TARGET - cp=Optional("false") attrs=[type=outgoing, progress=ended]"]

need rebase.


Node states are unknown

Hi,
I'm using docker-centos7-slurm to test a workflow manager. It has been a while since updating, but when trying out the most recent version, I notice that only one node (c1) is up in the container. I am currently testing this in my fork (see pr #1). Briefly, I parametrized test_job_can_run to pass partition to the --partition option. The normal partition works as expected, but debug fails.
If one enters the latest image with
docker run -it -h slurmctl giovtorres/docker-centos7-slurm:latest

running sinfo yields
NODELIST   NODES PARTITION       STATE CPUS    S:C:T MEMORY TMP_DISK WEIGHT AVAIL_FE REASON
c1             1   normal*        idle 1       1:1:1   1000        0      1   (null) none
c2             1   normal*    unknown* 1       1:1:1   1000        0      1   (null) none
c3             1     debug    unknown* 1       1:1:1   1000        0      1   (null) none
c4             1     debug    unknown* 1       1:1:1   1000        0      1   (null) none

See github action resuts, where I added some print statements to see what was going on (nevermind that the test actually passed; I was simply looking at the erroneous slurm output file). I consistently get the feedback that the required nodes are not available; it would seem node c1 is the only node available to sbatch.
Are you able to reproduce this?
Cheers,
Per

Yes, I can reproduce in 21.08, but 20.11.8 appears to be working. Something change in Slurm between those releases and the slurm.conf probably is missing something to accommodate. Help is appreciated 😄

So I actually found a solution; removing redundant NodeHostName statements in slurm.conf seems to work:
NodeName=c1 NodeHostName=slurmctl NodeAddr=<IP_ADDRESS> RealMemory=1000
NodeName=c2 NodeAddr=<IP_ADDRESS> RealMemory=1000
NodeName=c3 NodeAddr=<IP_ADDRESS> RealMemory=1000 Gres=gpu:titanxp:1
NodeName=c4 NodeAddr=<IP_ADDRESS> RealMemory=1000 Gres=gpu:titanxp:1

Not that I could find anything in the docs that would suggest this solution; I basically reacted to this error in the logs:
cat /var/log/slurm/slurmctld.log | grep Duplicated
[2022-02-17T08:33:22.239] error: Duplicated NodeHostName slurmctl in the config file
[2022-02-17T08:33:22.239] error: Duplicated NodeHostName slurmctl in the config file
[2022-02-17T08:33:22.239] error: Duplicated NodeHostName slurmctl in the config file

I'm currently running the test on my fork (see changeset). I'll submit a pr on success.


fix: merge steps for testbased coverage

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix the document to use proper dll loading method + clarify versions

Fix the document to use proper dll loading method + clarify versions

@samlevy-microsoft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Docs Build status updates of commit 3c1f2bf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

data-explorer/kusto/api/powershell/powershell.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@samlevy-microsoft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Docs Build status updates of commit 3498d48:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

data-explorer/kusto/api/powershell/powershell.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

IMPORTANT: When this content is ready to merge, @shsagir must add #sign-off in a comment or the approval may get overlooked.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

https://github.com/MicrosoftDocs/dataexplorer-docs-pr/pull/3367

Docs Build status updates of commit 3498d48:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

data-explorer/kusto/api/powershell/powershell.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Provide docker image list for flux components

It will be great if you can provide list of docker images (especially tags) used in the version set, this would help us mirroring images to our repositories.

This might be more relevant as an issue under the fluxv2 repo. The versions used by the provider are decided by the version that you set in the data source.  If you explicitly set the version I would think it would solve your problem :smile:


Doesn't work with vue language server

My configuration
Vue language server installed with lspinstall
https://github.com/kabouzeid/nvim-lspinstall
:LspInstall vue

local lsp = require'lspconfig'
lsp.vue.setup{...}

vim.g.symbols_outline = {
    highlight_hovered_item = true,
    show_guides = true,
    auto_preview = false, -- experimental
    position = 'right',
    keymaps = {
        close = "<Esc>",
        goto_location = "<Cr>",
        focus_location = "o",
        hover_symbol = "<C-space>",
        rename_symbol = "r",
        code_actions = "a",
    },
    -- lsp_blacklist = {'vue'},
}

When I try to run :SymbolsOutline I am getting the following errors.
Error executing vim.schedule lua callback: ...gged/symbols-outline.nvim/lua/symbols-outline/parser.lua:42: attempt to index field 'selectionRange' (a nil value)

@anton-fomin  can you check now?
tested with a random vue project from github:

Hi @simrat39 , I can open outline now, but for some reason it creates two windows and produces an error
Error executing vim.schedule lua callback: ...vim/plugged/symbols-outline.nvim/lua/symbols-outline.lua:193: Failed to rename buffer
Error executing vim.schedule lua callback: ...vim/plugged/symbols-outline.nvim/lua/symbols-outline.lua:193: Failed to rename buffer
E5108: Error executing lua ...vim/plugged/symbols-outline.nvim/lua/symbols-outline.lua:84: attempt to index local 'node' (a nil value)
E5108: Error executing lua ...vim/plugged/symbols-outline.nvim/lua/symbols-outline.lua:84: attempt to index local 'node' (a nil value)
E5108: Error executing lua ...vim/plugged/symbols-outline.nvim/lua/symbols-outline.lua:84: attempt to index local 'node' (a nil value)

Are you running multiple lsp servers by any chance?

Yes you are right, for this buffer I have 4 active servers efm, html, tailwindcss, vue


[DOC]: Add instructions on how to control the logs per service

How would you describe the priority of this documentation request
None
Please provide a link or source to the relevant docs
https://github.com/NVIDIA/nv-ingest/tree/main#:~:text=You can control this on a per service level via each service's environment variables
Describe the problems in the documentation
The documentation says that the logs can be controlled on a per service level basis here. Besides just saying that it is possible, the instructions on how to do this should be documented
(Optional) Propose a correction or improvement
No response

Closed with https://github.com/NVIDIA/nv-ingest/pull/84


[$250] Billable - Billable toggle becomes disabled when tracking expense with billable toggle enabled

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.83-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4631171
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Precondition:

"Re-bill expenses to clients" is set to "Default to Billable" on Old Dot.

Go to + > Track expense > Manual.
Track a manual expense with billable toggle enabled.
Go to transaction thread.

Expected Result:
Billable toggle will remain enabled.
Actual Result:
Billable toggle becomes disabled.
This issue only happens with tracked expenses and not submitted expenses.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/3a5c5e30-9d58-415b-918f-833bc1835c64

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01d112a7853dd092a2
Upwork Job ID:<PHONE_NUMBER>526046967
Last Price Increase: 2024-07-24

We think this issue might be related to the #collect project.

I think this issue might be related to BE.

I am not able to recreate as I am getting the infinite skeleton loader (context here). Going to see if this can be retested by QA

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

Not overdue as we're waiting for it to be retested by QA

Still waiting for it to be retested, as I cannot recreate

Still waiting for this to be tested, as I still cannot recreate!

Still waiting for this to be tested since my test account is still impacted by the infinite skeleton loader (GH here)

Issue is reproducible during KI retests.
https://github.com/Expensify/App/assets/43995119/2e4318ad-f783-475f-b8d0-b0d0551c5f36

Post in wave collect here

@ishpaul777 based on the comment here can you confirm if this is a BE issue?

So confirmed with Tom that this is VIP-VSB. That is paused for now, so adjusting to weekly

Thanks @ishpaul777 — I've adjusted the tags to reflect and internal issue. @tylerkaraszewski do you have the bandwidth to take this on?
Also @johncschuster I am heading OoO so reassigned this in the meantime to keep eyes on it — thanks!

@CortneyOfstad I don't really have time to work on this right away. If someone else would like to take it, they're welcome.

VIP-VSB has been deprioritized. I wonder if this can be moved to #wave-collect. If not, we will likely need to close this for now.

@trjExpensify, do you feel like this could fit under #wave-collect?

bump for melv

Ah, okay.. it's using track on a workspace. Okay cool, we can move it in.
I could be wrong, but I think it's because TrackExpense here in the TransactionAPI in Web-E doesn't include billable. So we aren't doing anything with that toggle on the frontend.
CC: @thienlnam

That was by design though, tracked expenses are by nature not billable or reimbursable. Is there a use-case for that?

If it was by design, why can you select the Billable toggle when you use Track expense on a workspace?
But either way, yes, I think there's a case for "I'm tracking the expenses I incur for my business on a workspace, and billing some of those expenses on to my clients".

If it was by design, why can you select the Billable toggle when you use Track expense on a workspace?

This was probably added later - but we can have the billable flag get passed to the API. Will require some auth changes as well

I'm back from OoO @johncschuster — thanks for holding down the fort while I was gone!

Just catching up on this one. It sounds like we've come to the conclusion that we could pass the billable flag via the API. Do we all agree that that's the direction we're going to go? If so, who's doing that?

These PRs are currently in review by @pecanoro - looks like she is OOO but should be back next week

https://github.com/Expensify/Auth/pull/11971
https://github.com/Expensify/Web-Expensify/pull/43068

Thanks @thienlnam for the update!

So the PRs went into production today, so with the 7-day holding period, the date will be 8/28, so changing the title to reflect that 👍

Issue not reproducible during KI retests. (First week)


Return location to data forwarding

Let's follow https://docs.ruuvi.com/ruuvi-station-app/gateway as accurately as possible.
If data is not available, we could write it as
"location": {
    "accuracy": undefined,
    "latitude": undefined,
    "longitude": undefined
  },

or undefined -> 0

This is how currently data looks for basic sensor without pressure and humidity. Missing "pressure" field will be parsed to null value and it's completly ok for json. No need to send extra data for null.

Let's just mention in documentation that location won't be included if user opted out for this feature in settings or no location permission provided.

New option in data forwarding settings:

How can we know that it's ok for json parses our customers have created? It is possible that none of the old customers who are using this data forwarding feature have bought 2in1 or 3in1 sensors and they haven't noticed yet that some sensors may have no humidity and pressure fields available.
And if it would be perfectly ok to not to send null values and instead just drop the fields off from the sent json object, why do we send zero values if user hasn't configured offsets?

Most likely customers use some 3rd party parsers for json and most of them should support this. From my experience there are no issues when value is just omitted. I get the data from our Cloud the same way. Also customer who asked about the field didn't mention that dissapeared location field crashed his server or something like that, he still getting data only without coordinates.
Offsets initialized like 0 in app local db.

Discussed in DM this doesn't work for me on S8,  OS9

QA passed


Uncontrolled changing into controlled at an input in a react hook form.

Using the input component in a react hook form triggers the error:
"A component is changing an uncontrolled input to be controlled. This is likely caused by the value changing from undefined to a defined value, which should not happen. Decide between using a controlled or uncontrolled input element for the lifetime of the component."
This happens, because the field object's value property turns from undefined to an actual value once the input is used.

@thepeterkovacs You have to set a defaultValue. See my comment here: https://github.com/shadcn/ui/issues/410#issuecomment-1556705052

Wow, thanks for the quick answer! Cheers!