GA Review for ockam_transport_tcp crate

Checklist

[x] 🤔 Should this file exist?
[x] ❤ Is the Public API friendly?
[x] 📚 Are all Public functions documented?
[x] 🪂 Do public functions have rust doc examples?
[x] 🆗 Do all functions return the correct errors?
[x] 🛃 Are all error results returned inside the implementation being handled correctly?
[x] ✅ Do all modules have sufficient test coverage?
[x] 🪵 Is there sufficient logging and are the correct levels being used?
[x] 🛌 N/A Are all modules ready for use on embedded?
[x] 📦 Are we using the correct Cargo features in all files and Cargo.toml?
[x] ☣ N/A Has all unsafe code been audited?

Open Questions

🤔 Should the buffer size in src/portal/portal_receiver.rs#L8 be hardcoded?
🤔 There are some outstanding TODO's in src/portal/portal_worker.rs#L148-L190
🤔 Are processors affected by @spacekookie's recent work on Processor

New Tests

♻ src/lib.rs - test_parse_socket_address()

Refactored

♻ src/router/mod.rs - Moved TcpRouter into its own file tcp_router.rs
❤ src/router/mod.rs - friendlify code organisation of ockam_transport_tcp::TcpRouter
❤ src/router/handle.rs - friendlify code organisation of ockam_transport_tcp::TcpRouterHandle
❤ src/workers/listener.rs - friendlify code organisation of ockam_transport_tcp::TcpListenProcessor
❤ src/workers/sender.rs - friendlify code organisation of ockam_transport_tcp::TcpSendWorker

Grrf

Uh, hm. I was going to merge this now, but the conflicts from the rebase look... really hairy, so do you mind rebasing?

Uh, hm. I was going to merge this now, but the conflicts from the rebase look... really hairy, so do you mind rebasing?

Hairy rebase was indeed hairy :-)
I've pushed it but we're now getting build errors during for the Rust / Rust - Nightly * checks:
   Compiling os_pipe v0.9.2
error[E0658]: trait bounds other than `Sized` on const fn parameters are unstable
   --> /usr/rust/cargo/registry/src/github.com-1ecc6299db9ec823/lock_api-0.4.7/src/mutex.rs:150:6
    |
150 | impl<R: RawMutex, T> Mutex<R, T> {
    |      ^
...
154 |     pub const fn new(val: T) -> Mutex<R, T> {
    |     --------------------------------------- function declared as const here
    |
    = note: see issue #93706 <https://github.com/rust-lang/rust/issues/93706> for more information
    = help: add `#![feature(const_fn_trait_bound)]` to the crate attributes to enable

I can't reproduce it locally so it looks like the lock_api sub-dependency pushed some changes which assumes a newer nightly than the CI machine:
rustup default nightly
  shell: sh -e {0}
info: using existing install for 'nightly-x86_64-unknown-linux-gnu'
info: default toolchain set to 'nightly-x86_64-unknown-linux-gnu'

  nightly-x86_64-unknown-linux-gnu unchanged - rustc 1.61.0-nightly (68369a041 2022-02-22)

Shouldn't rustup be checking and updating that automatically though?
 Please rebase (some changes are trivial but some I'm guessing at, and it would be a bad way to write a bug)
We should land this ASAP after you fix the rebase, since it seems very fragile.

since it shouldn't be so hairy

Should have kept my mouth shut -- I definitely spoke too soon. Please rebase (some changes are trivial but some I'm guessing at, and it would be a bad way to write a bug)
We should land this ASAP after you fix the rebase, since it seems very fragile.

Aurgh, there goes another morning. 😫
This branch should probably have been merged immediately after I rebased it on Wednesday, before merging the transport type changes:
https://github.com/ockam-network/ockam/commit/55ffce6af0ae1453d6901d192682bf70fa9edfc1
…which undoes all the work I did on the rebase.
What I'll try do is create a new branch off develop, back out the transport type changes, merge my changes and then rebase the transport type changes on top of mine as they are pretty mechanical.

Acke, just chatted with @SanjoDeundiak and we're going to have to do this a 3rd time if we're not careful! 🤣
How about:

I hold off on rebasing this branch until @SanjoDeundiak's tcp reconnect branch lands.
I do the hairy rebase
We put a freeze on landing anything else that touches ockam_transport_tcp until we've landed this ga review branch.
We review & land this branch
Back to business as usual

It would be nice to get this in, since I think it's the one of the last bigish chunks of GA work that has not landed.

I won't land anything that touches that code until then.

🚀 …and all your rebase are belong to us!  *touch.wood* we should be good to go.


Remove XXOutput loss operators

Description
These operators are often used with mx.module APIs. Removing them for mxnet 2.0. You can find equivalent loss functions in mx.gluon.loss namespace.
These APIs will still be maintained in the 1.x branch
https://github.com/apache/incubator-mxnet/issues/17676
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Will there be an efficient equivalent for SoftmaxOutput in 2.0 that also supports label smoothing?

@eric-haibin-lin @fhieber I’ve written a new loss layer in the numpy API: https://github.com/dmlc/gluon-nlp/blob/b714eaccc67619d7bdcbd1574d30be87d9c73f0c/src/gluonnlp/loss.py#L4
I’ve evaluated and the speed + memory cost is better than calculating the cross-entropy between softmax and smoothed label.

@eric-haibin-lin Thanks for the pointer. We had tried custom operators in a separate project (int8 quantization) but found them to be not suitable for performance reasons.
@sxjscience Thanks! I will take a look. I haven't benchmarked SoftmaxOutput and a Gluon implementation recently. Mid 2019 we still observed a ~15-20% slowdown when not using SoftmaxOutput. I will give your label smoothing implementation a try, but my guess is that the combination of Softmax forward pass, (smoothed) cross-entropy gradient backward pass, and support for easy masking without creating an explicit mask, all implemented in a single operator, will still have a slight edge over an implementation with multiple operators.

CC @sandeep-krishnamurthy
Are custom operators actually causing a slow-down? Speak, the same code, one time directly compiled and the other one dynamically loaded are not creating the same performance?

@samskalicky is there any evidence that dynamic ops are slower?

No, dynamic C++ custom ops are significantly faster than Python custom ops. I believe @fhieber and his team found dynamic C++ custom ops to be within 10% of built in operators. There are some overheads that are a result of our design choices (we chose easier implementation rather than speed). But our goal was never equal performance as built in operators.

Just to follow up on this and provide some numbers. I tried the label smoothing implementation by @sxjscience (thanks!) in Sockeye, making sure scaling and normalization is equivalent to how we currently use SoftmaxOutput.
While this is much faster than a naive implementation of label smoothing with dense, smoothed labels, SoftmaxOutput is still 5-10% faster than the optimized implementation.


python38Packages.elasticsearch: Revert updates >7.13.1

Motivation for this change
In 7.14.0, the package was intentionally made incompatible with the OSS version: https://github.com/elastic/elasticsearch-py/issues/1639. Since the updates don't seem to fix any serious vulnerabilities, it's probably best to revert the update and hold off. Likely, many dependents will switch to using https://github.com/opensearch-project/opensearch-py instead, which will solve the issue.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 137174 at e12c6677 run on aarch64-linux 1

12 packages built successfully:

archivy
elasticsearch-curator
mailman-web (python39Packages.mailman-web)
python38Packages.elasticsearch
python38Packages.elasticsearchdsl (python38Packages.elasticsearch-dsl)
python38Packages.flask_elastic
python38Packages.hyperkitty
python38Packages.mailman-web
python39Packages.elasticsearch
python39Packages.elasticsearchdsl (python39Packages.elasticsearch-dsl)
python39Packages.flask_elastic
python39Packages.hyperkitty

1 suggestion:

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/elasticsearch/default.nix:24:0:
   |
24 |     description = "Official low-level client for Elasticsearch";
   | ^

Please add a comment explaining the situation that further updates are blocked.

Done.


[Feature Request] Duplicate Card Option

Feature that allows for a user to duplicate a card as it is

This will be solved on 2.1.2
Keeping the issue open on  #103


config.json: Add missing core key; Run configlet fmt

Summary:

Add missing core key to collatz-conjecture.
Run configlet fmt.

I'm making this PR because I noticed that the Scheme track is currently the only track with an exercise that lacks a core key.
Feel free to squash these commits if desired.

Hi @ee7 , thanks for catching this!
It's probably not documented well enough, but the config.json file is actually output based on the contents of the config/track.ss file. To make the fix you should add a (core . #f) field to the collatz entry there.
https://github.com/exercism/scheme/blob/master/config/track.ss
A fresh config.json can be updated by running make config.json from the terminal.

@jitwit Ah, I see. Thanks.
I force-pushed changes to config/track.ss such that config.json is generated with the previous changes. Does it look ok now?
I notice you already have some code for doing configlet-compliant formatting:
https://github.com/exercism/scheme/blob/88222372fe13916265ad0de4b57904cac53fc9d6/code/outils.sls#L138-L159
So to catch things like missing keys in the future, perhaps consider adding to CI something like:
./bin/configlet fmt . && git diff --exit-code

Something like this is done by at least the following tracks:

cpp
haskell
nim
python
rust

Hey @ee7 we use configlet lint . to make sure the config.json complies with what exercism wants, but I see that there may be some benefit to running configlet fmt . as well, since it seems to add some missing parts.
With respect to catching missing fields, I've been meaning to add more checks like that to code/lint.sls. Currently, it only checks if exercises are missing the uuid. Checking for missing fields like core or topics is on the invisible todo list!
Ideally, running make locally will be the way to catch these issues. At the moment the CI mostly serves to verify that all the exercises and test cases work on a fresh machine in both guile scheme and chez scheme. Doing the check you suggested locally might be nice.
I'm a little confused by why the force push was needed; were you committing changes after running configlet fmt?

I'm good with merging this, just want to confirm whether the config.json was given a configlet fmt . pass, and if so to consider re-adding that pass as well as simplifying the json work from inside scheme.
The main reason for doing the json printing from scheme is to use more kebab case -- configlet happily converts some keys, but not all (I think auto_approve or unlocked_by are examples?)

I'm a little confused by why the force push was needed

Sorry for the confusion. I preferred to edit the previous commits to include their respective change to track.ss. I generally try to make each commit do only one thing and be individually correct so that:

It's easier for me to write clear commit messages.
PRs can be merged without squashing when desired.

But the second force-push (to tweak a commit message) was extra noise that made it harder to review on GitHub, sorry. The diff for the first force-push is here.

I'm good with merging this, just want to confirm whether the config.json was given a configlet fmt . pass

I can confirm that running configlet fmt makes no changes to this PR's config.json. However, running make config.json generates config.json without a final newline, which is added when configlet fmt is run.
So I think this PR should only be merged either:

In the current state with the final newline in config.json, but then make config.json should be changed to add a final newline (in this or a later PR).
Or without the final newline in config.json.

Your choice! If you pick option 1 and want the make config.json change included in this PR then you'd have to let me know the patch you want.

Option 1 sounds good, no need to add extra work, when it appears the json outputting should be tweaked a bit at any rate!

By the way, thanks again!

Sounds good to me too. Thanks!


Recycle Week Between Sensors Not Matching

The two sensors have been setup.
The Recycle bin in Brisbane Bin Day, reports the Recycle as False, but under the Recycle sensor it reports true.
I have confirmed my address and zone, the API is reporting the correct data.
https://data.brisbane.qld.gov.au/api/explore/v2.1/catalog/datasets/waste-collection-days-collection-weeks/records?where=week_starting = date'2024-12-02' AND search(zone, '1')
Tomorrow, Friday is my Bin day and should be recycling, which matches above.

Please provide a copy of your configuration
From: memphisraynz @.>
Sent: Thursday, 5 December 2024 8:16 PM
To: mark1foley/Brisbane-Bin-Day-Sensor @.>
Cc: Subscribed @.***>
Subject: [mark1foley/Brisbane-Bin-Day-Sensor] Recycle Week Between Sensors Not Matching (Issue #2)
The two sensors have been setup.
The Recycle bin in Brisbane Bin Day, reports the Recycle as False, but under the Recycle sensor it reports true.
I have confirmed my address and zone, the API is reporting the correct data.
https://data.brisbane.qld.gov.au/api/explore/v2.1/catalog/datasets/waste-collection-days-collection-weeks/records?where=week_starting = date'2024-12-02' AND search(zone, '1')
Tomorrow, Friday is my Bin day and should be recycling, which matches above.
—
Reply to this email directly, view it on GitHubhttps://github.com/mark1foley/Brisbane-Bin-Day-Sensor/issues/2, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL6CAIDVSLRH5AW5TRBBXDL2EARUHAVCNFSM6AAAAABTCDIP7KVHI2DSMVQWIX3LMV43ASLTON2WKOZSG4YTSOJWHAZTOOA.
You are receiving this because you are subscribed to this thread.Message ID<EMAIL_ADDRESS>

Hi copy of my sensor config
- platform: bne_wc   name: Brisbane Bin Day   scan_interval: 300   base_url: https://www.data.brisbane.qld.gov.au/api/explore/v2.1/catalog/datasets/{dataset_id}/records?where={query}&limit=1   days_table: waste-collection-days-collection-days   weeks_table: waste-collection-days-collection-weeks   property_number: 454726
not sure if the api results have change
{   "total_count": 1,   "results": [     {       "week_starting": "2024-12-02",       "zone": "Zone 1"     }   ] }

Hi, I added your property number (454726) to my config and it looks to be working ok.  Here are the sensor attributes.
sensor.brisbane_bin_day
Alert Hours: 12
Property Number: 454726
Suburb: BRIGHTON
Street: HIGH ST
House Number: "28"
Collection Day: FRIDAY
Collection Zone: ZONE 1
Next Collection Date: "2024-12-13T00:00:00"
Extra Bin: ""
Due In: 159
Recycle Week: false
icon: mdi:trash-can
friendly_name: Brisbane Bin Day

sensor.brisbane_bin_day_recycle
Alert Hours: 12
Property Number: 454726
Suburb: BRIGHTON
Street: HIGH ST
House Number: "28"
Collection Day: FRIDAY
Collection Zone: ZONE 1
Next Collection Date: "2024-12-20T00:00:00"
Extra Bin: Yellow/Recycling
Due In: 327
Recycle Week: true
icon: mdi:recycle
friendly_name: Brisbane Bin Day (Recycle)

So it looks to be working ok to me as it matches the calendar in the BCC app

Are you getting different results to this?

Hi,
I am sure the results I was getting differed. The problem is I only remembered to take screenshots this morning so they don't show the data as of last night.
Is there a way in the config to continue to report today (bin day) as this week.
My bin day is Friday, and at a minimum Recycling was correct on Thursday. It was reporting what Bin was due for this week, but on Bin day, it switched the results to next week.
For me if I forget to put the bins out on Thursday and do it Friday morning, the sensor would show what I should do for the next week.

Hi, so is the issue that your bin gets collected later in the day on collection day?  My bin gets collected at silly o'clock so I didn't really think about that when writing it.  I guess I could add a "Collection Hour" configuration item and instead of setting the collection date to midnight on collection day it would use the hour specified.  That would stop the sensor flicking over to the next week until the specified hour is reached on "bin day".  The "Due In" would also be the number of hours until the specified hour instead of midnight.  Would that work for you?

Honestly, it may be that I just had different expectations from that the sensor was showing.
When i first put the sensor in, it was the day before Bin day. The recycing sensor show everything correct.
The main sesnor had
Next Collection Date: "2024-12-13" (where the next collection date for my bins was the 6th, but I'm gusseing this is next collection for the bin underneath.)
Extra Bin: "Green/Garden"
Recycle Week: false ( this also threw me, as I thought this being the main sensor it should show true, becuase tomorrow was recycling)
As I see it now, its really two sesnors, one for the Green bin and another for the Yellow bin.
I did end up playing with the code to put in an Offset, to push the time the bins are "collected" at.

Ok, no problems.  If you would like to share the code you changes I could like at incorporating it.  I have to do some work on the integration soon anyway.  I convinced BCC to add a dataset to their open data site for the annual kerbside collection so wanted implement that.
Regards,
Mark
From: memphisraynz @.>
Sent: Saturday, 7 December 2024 5:08 AM
To: mark1foley/Brisbane-Bin-Day-Sensor @.>
Cc: Mark Foley @.>; Comment @.>
Subject: Re: [mark1foley/Brisbane-Bin-Day-Sensor] Recycle Week Between Sensors Not Matching (Issue #2)
Honestly, it may be that I just had different expectations from that the sensor was showing.
When i first put the sensor in, it was the day before Bin day. The recycing sensor show everything correct.
The main sesnor had
Next Collection Date: "2024-12-13" (where the next collection date for my bins was the 6th, but I'm gusseing this is next collection for the bin underneath.)
Extra Bin: "Green/Garden"
Recycle Week: false ( this also threw me, as I thought this being the main sensor it should show true, becuase tomorrow was recycling)
As I see it now, its really two sesnors, one for the Green bin and another for the Yellow bin.
I did end up playing with the code to put in an Offset, to push the time the bins are "collected" at.
—
Reply to this email directly, view it on GitHubhttps://github.com/mark1foley/Brisbane-Bin-Day-Sensor/issues/2#issuecomment-2523976982, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL6CAIBSOCWLEQ7OR6OV43D2EHYZTAVCNFSM6AAAAABTCDIP7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRTHE3TMOJYGI.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>

Hi,
I forked your repository as I wasn't sure if these changes really just suited me.
https://github.com/memphisraynz/Brisbane-Bin-Day-Sensor


Get get-key command to 100% test coverage

Bounty: 125 tokens
The scope of this Issue is to add tests to the get-key command test library in order to achieve 100% test coverage. It is currently at 61% test coverage. Make any changes needed to the get-key.js library necessary to facilitate mocks and test coverage.

The burn-tokens tests and other commands have achieved 100% test coverage. This provides a good example of the patterns that will be needed to complete this Issue.

This YouTube video covers JavaScript design and testing patterns that should be followed.

This YouTube video shows how to generate test coverage reports. These reports will help you identify the lines that are not being covered by current tests.

Acceptance Criteria

A Pull Request (PR) should be submitted that meet the above criteria. The PR should be from a branch and not a fork. In order to create a branch, you'll need commit to access to this repository.
All tests should pass when running npm test.
The command targeted by this Issue should show 100% test coverage when tests are run.
All commands should still be fully functional.
The bounty will be awarded upon successfully merging of the PR into the master branch.

This Issue resolved by #15

125 PSF tokens awarded to Stoyan for work on get-key command of slp-cli-wallet.  TXID:
ce401b22b3489a4bb0155a0dc47c03a5551b1f60cffa2ee83ee367e5f05d45c9


XR_FB_space_warp extension not present

I am using OpenXR SDK to develop a PC VR app with Oculus Quest 2 in cable link (quest link). I have enabled the OpenXR runtime in the Oculus app and the developer mode that gives additional openXR extensions.
When logging the available extensions, I get 37 extensions. Some of them are XR_FB_... or XR_OCULUS_...
However, I get the following error when I try to use XR_FB_space_warp extension:
Error [GENERAL | xrCreateInstance | OpenXR-Loader] : LoaderInstance::CreateInstance, no support found for requested extension: XR_FB_space_warp
Error [GENERAL | xrCreateInstance | OpenXR-Loader] : xrCreateInstance failed
[16:06:23.692][Error  ] XrResult failure [XR_ERROR_EXTENSION_NOT_PRESENT]

I am using v46.0 for Oculus app and OpenXR SDK 1.0.24, which shloud be ok since XR_FB_space_warp is apparently supported from OpenXR SDK 1.0.23.
Could you give me a hint about on to make this missing extension available ? Thanks

The extensions that are available on a given runtime differ. SDK support for an extension just means that it includes the documentation, headers, etc. for that extension, not that any particular runtimes support it. In particular, the extensions available on a Quest 2 over link cable can and do differ from those available when running directly on the Quest, because it is two different runtimes, and Meta has not chosen to make all the same functionality available, as far as I know.
There is crowd-sourced information on extensions available in different runtimes at https://github.khronos.org/OpenXR-Inventory/extension_support.html There is not (yet) a listing explicitly for quest 2 over link cable, but I think it works effectively like the entry for "Meta (PC)"


remove-compat-file

Could you share why?

collect-protocol has different file name, so some files would be ignored by goapi


[MISC] Switch test app interface

Switch test-app interface from first-database to database
Update libs

THANK YOU!


Enhanced the main page using the trailing cursor

https://github.com/user-attachments/assets/d5f00499-9536-4b91-b6d8-a4fca145b408

Not required in the main page of the site


Add admin panel

I think it would be great to add lightweight integration of admin panel.

Please look at my PR: https://github.com/zenwalker/django-micro/pull/9

Released in 1.6.0 but I’ve renamed the argument to django_admin=True.


obsidian: 0.11.3 -> 0.11.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for obsidian is: "A powerful knowledge base that works on top of a local folder of plain text Markdown files"
meta.homepage for obsidian is: "https://obsidian.md"
meta.changelog for obsidian is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.11.5 with grep in /nix/store/q6cyw9rwimgbjq689kbrr4vy2pb30wpl-obsidian-0.11.5

directory tree listing: https://gist.github.com/89744c6de4d6ff78403340f64739fa79

du listing: https://gist.github.com/a038a06e8460d59f3efba8f533db77af

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

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
obsidian

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/q6cyw9rwimgbjq689kbrr4vy2pb30wpl-obsidian-0.11.5 \
  --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 obsidian https://github.com/r-ryantm/nixpkgs/archive/1d1acce658e25c845a2e1db474b6ecfeafeeef15.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/q6cyw9rwimgbjq689kbrr4vy2pb30wpl-obsidian-0.11.5
ls -la /nix/store/q6cyw9rwimgbjq689kbrr4vy2pb30wpl-obsidian-0.11.5/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:

obsidian

Maintainer pings
cc @ConradMearns @zaninime for testing.

Result of nixpkgs-review pr 116161 run on x86_64-linux 1

1 package built:

obsidian


[CI] build is failing when using serialization

See http://cdash-bipop.inrialpes.fr/viewBuildError.php?buildid=17829
We should make sure that we don't use make -jN, N > 2 in that case.

This appears fixed. Close?


Changes to the Makefile

I would love to use this as the alternatives mentioned above have been depreciated. The fork of roteltcp which is "active" does not work for me.
I have HA Core installed on a RPi5, connected to a Rotel A14 via RS232-USB cable. The Rotel also has a wired ethernet connection. Mosquitto MQTT broker is running in Docker.
I have generated a Docker token, and installed Go on the RPi.
When I try to build the repo, I get "unauthorized: unauthenticated: User cannot be authenticated with the token provided"
Which lines do I need to change in the Makefile to allow this to work?

Hi Narelle, sorry about the issues you are having. You shouldn't need to build this repo unless you are wanting to update the features. You can simply pull the existing docker image. For Intel processors,
docker pull ghcr.io/djthorpe/rotel-linux-x86_64:1.0.8

For ARM:
docker pull ghcr.io/djthorpe/rotel-linux-aarch64:1.0.7

Once you have a package locally, you then run it like this, replacing the name of the docker image, the MQTT address and the USB port that your amplifier is connected to:
docker run --rm --name rotel --device=/dev/ttyUSB1 \
  ghcr.io/djthorpe/ghcr.io/djthorpe/rotel-linux-x86_64:1.0.8 \
  rotel -mqtt localhost:1883 -tty /dev/ttyUSB1

Once this is running, you should be able to create a new card in Home Assistant like the one in the README for basic amplifier control. Let me know if this is working for you. It's very basic and I should really add the remaining features I mentioned in the README file. Let me know how it goes for you.

....and just on the message unauthorized: unauthenticated: User cannot be authenticated with the token provided this is likely because the Makefile includes my repository. you can set the following environment variables as part of the make process to change the repo location:
DOCKER_REGISTRY := "ghcr.io"
DOCKER_USER := "djthorpe"
DOCKER_REPOSITORY := "${DOCKER_USER}/go-rotel"

So for example, if you forked this repository into your own account on github,
git clone git@github.com:nirvine/go-rotel.git
cd go-rotel
DOCKER_USER=nirvine make docker

This MIGHT work, if you want to build it for yourself. And if you add any features, I always appreciate pull requests.

Thank you for replying so quickly.
I am unlikely to add anything, as I am not a programmer - I am a determined user.
I ran the command for arm64 and got the following message:

1.0.7: Pulling from djthorpe/rotel-linux-aarch64
Digest: sha256:0792afccefc09f72b3ae4862e2d9a7db5f25295e3c20f77c3af6fe52d26a3c20
Status: Image is up to date for ghcr.io/djthorpe/rotel-linux-aarch64:1.0.7
ghcr.io/djthorpe/rotel-linux-aarch64:1.0.7

But the second command to run the container gives

MQTT: Connection refused

I am running eclipse-mosquitto with no user control, on port 1883.

OK, you should be able to see in either the logs for MQTT why it is refusing the connection. Maybe it requires a username/password?

I had set a username and password in MQTT Integration of Home Assistant. the logs for MQTT refers to 'u'hass (the username  entered).
It is a bit hard to identify requests because Portainer seems to obfuscate names.

2024-10-13T08:59:53.973136842Z<PHONE_NUMBER>: mosquitto version 2.0.19 starting
2024-10-13T08:59:53.982171435Z<PHONE_NUMBER>: Config loaded from /mosquitto/config/mosquitto.conf.
2024-10-13T08:59:53.982184861Z<PHONE_NUMBER>: Opening ipv4 listen socket on port 1883.
2024-10-13T08:59:53.982187583Z<PHONE_NUMBER>: Opening ipv6 listen socket on port 1883.
2024-10-13T08:59:53.982190009Z<PHONE_NUMBER>: mosquitto version 2.0.19 running
2024-10-13T09:01:04.851964715Z<PHONE_NUMBER>: New connection from <IP_ADDRESS>:59631 on port 1883.
2024-10-13T09:01:04.864209011Z<PHONE_NUMBER>: New client connected from <IP_ADDRESS>:59631 as 0Qyp11RFKWJSiVKKxM59Tw (p2, c1, k60).
2024-10-13T09:04:38.475657148Z<PHONE_NUMBER>: New connection from <IP_ADDRESS>:35847 on port 1883.
2024-10-13T09:04:38.475773128Z<PHONE_NUMBER>: New client connected from <IP_ADDRESS>:35847 as 3jorEUPxTdrHQXaUIlboLb (p2, c1, k60, u'hass').
2024-10-13T09:04:38.475936348Z<PHONE_NUMBER>: Client 3jorEUPxTdrHQXaUIlboLb disconnected.
2024-10-13T09:05:01.842486943Z<PHONE_NUMBER>: Client 0Qyp11RFKWJSiVKKxM59Tw disconnected.
2024-10-13T09:05:01.851640760Z<PHONE_NUMBER>: New connection from <IP_ADDRESS>:52229 on port 1883.
2024-10-13T09:05:01.855922189Z<PHONE_NUMBER>: New client connected from <IP_ADDRESS>:52229 as 4rBigEXpaZiaBhE3MRyytC (p2, c1, k60, u'hass').
2024-10-13T09:05:28.912132975Z<PHONE_NUMBER>: Client 4rBigEXpaZiaBhE3MRyytC closed its connection.
2024-10-13T09:05:40.304793603Z<PHONE_NUMBER>: New connection from <IP_ADDRESS>:59695 on port 1883.

Ok I could add in the ability to set credentials in go-rotel if that would help.

I did try removing the user and password on the MQTT integration, rebotting and running the docker go-rotel command again. But I still got the MQTT connection refused message. I think your suggestion would help.

Thanks.  Could you share the docker command you are using to run the MQTT broker and then I can also test it myself.

It was set up in Portainer. I hope this is what you need!

mosquitto.conf file:

persistence true
persistence_location /mosquitto/data
user mosquitto
listener 1883
allow_anonymous true
log_dest file /mosquitto/log/mosquitto.log
log_dest stdout

Thank you for providing me with all that information. I now understand that the issue isn't credentials (since you have allow_anonymous true in your MQTT broker configuration but with the server address (the -mqtt localhost:1883 argument). You need to change the docker command to the following:
docker run --rm --name rotel --device=/dev/ttyUSB1 \
  ghcr.io/djthorpe/rotel-linux-aarch64:1.0.9 \
  rotel -mqtt ipaddress:1883 -tty /dev/ttyUSB1

Where "ipaddress" is the IP address of your host computer, rather than localhost.  On a local LAN this is often of the format 192.168.XXX.XXX ... but depends on your router. The reason is that "localhost" resolves to inside the container network, rather than routing to the MQTT container.
I did actually add the credentials as well in version v1.0.9 so if you need to use a username/password, that should also be possible now.
Let me know how it goes.

Great!


No License

How is this code licensed? As it stands, the original author holds the copyright. Anyone using this repository without explicit permission is on shakey legal grounds.

Hey @AlexanderNenninger thanks for pointing that out! Just added a LICENSE 😸


Second round of tweaks for datapoints tables.

Handles comments left by @iksaif on review #58 after it was committed.

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


H1 Title Centered

H1 Title are allways centered in this Theme wich is quite unusual as default setting
Is it possible to have an option to have them Align on the right like the other title level through the "Theme Setting"

Quick and dirty fix with custom css snipet :
.markdown-rendered h1, .HyperMD-header-1 {
text-align: left !important;
}
Don't know if it's the best selector to use but it seems to work

After the last update, there is now a quick option in Style Settings to have H1 left-aligned. Thank you for sharing with me the idea.


Enable creation of phantom refs for JARs without dependencies

This PR enables the creation of phantom refs for JARs without dependencies.

Codecov Report

Merging #136 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #136      +/-   ##
============================================
+ Coverage     85.84%   85.86%   +0.02%
  Complexity      260      260
============================================
  Files            27       27
  Lines           551      552       +1
  Branches        119      119
============================================
+ Hits            473      474       +1
  Misses           22       22
  Partials         56       56

Impacted Files
Coverage Δ
Complexity Δ

...raphgenerator/jimple/LibraryUsageGraphGenerator.kt
86.95% <100%> (+0.59%)
10 <0> (ø)
: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 9a6f114...9fca85f. Read the comment docs.


The stream loses data

In this use case we send a file. All data are lost if the file is small, or received partially if the file is big.
How to reproduce:
const fs = require('fs')
const reader = fs.ReadStream('index.js')
const writer = fs.WriteStream('out')
const socket = require('websocket-stream')('ws://echo.websocket.org')

reader.pipe(socket).pipe(writer)

// Now compare the size of the input and output files

Node.js v8.6.0

Found the the data written to the stream are just ignored unless the socket is connected. What is a rationale behind such decision?

This module is very old, and there might not be a good rationale behind some of the code. If you want to help maintaining this you are welcome to propose a change.

With modern Node.js making a stream over a WebSocket (ws module) seems quite simple for a trivial use case.
May a complete refactoring be considered?

As long as the API stays similar and the tests passes, I see no problem.


This credential provider not chosen on webauthn.io registration

Pixel 7
Android 14 - Jan 5, 2024 update
Chrome - 120.0.6099.230 - Pixel 7 Build/AP11.231215.009
I selected the MyCredentialProvider in the "Settings/Passwords and Accounts" screen and turned off the Google Password Manager. When I try to register with webauthn.io to the MyCredentialManager, it saves it to the Google Password Manager. When the "Create a Passkey" screen pops up, the first clue that something is wrong is that the icon for Google Password Manager shows instead of the MyCredentialProvider icon. The video shows the flow. I'm not sure what I'm doing wrong here. Thanks for the help on this.
https://github.com/ko-koiwai/MyCredentialManager/assets/149169088/cc219378-755c-4eec-900f-238d122d2010

I didn't have the chrome flag on.


Real QC Backends

Add IBM Qiskit and Xandau QC support. Trivially, conceptually, however, it requires converting our circuit format to their library functions calls and parsing the resulting data.

Completed, waiting on Frontend for graphics + any additonal logic

Working GUI for Qiskit


Package upgrade: firebase_crashlytics 2.0.3 --> 2.0.4

Summary
Package upgrade: firebase_crashlytics 2.0.3 --> 2.0.4
Changelog
[General] [Change] - Upgrade firebase_crashlytics from 2.0.3 to 2.0.4 (changelog)
Test Plan
Regression test the following areas:
./lib/main.dart

Consolidating with PR #1368


Change to proxies lazy

:pushpin: References

Issue: #1, #2
Related PRs: #3, #4

What does the PR achieve/Which part improves the PR?

What is the overall concept of the implementation?

:thinking: DOD Checklist

[ ] My code passes the lint checks.
[ ] My changes are covered with proper tests.
[ ] All tests are pass.
[ ] My changes update the documentation.
[ ] My changes are reflected in the changelog.

Closed since the compile time increases too much


[General] Unable to access esp-idf ble_wifi_provisioning component

I'm attempting to use the "ble_wifi_provisioning" component from the esp-idf library.  Under the top level CMakeLists.txt, I've included the component to be linked, yet it doesn't recognize the header files where app_main() is located.  Where do I need to look to makes the necessary changes for this to work?

Hardware board: ESP32-WROOM-32E
IDE used: None
Operating System: Windows 10
Code version: 202012.01
Project/Demo: mqtt_demo_mutual_auth

From CMakeLists.txt
cmake_minimum_required(VERSION 3.13)

project(freertos_examples)

add_executable(afr_demo src/main.c)

# Tell IDF build to link against this target.
set(IDF_PROJECT_EXECUTABLE afr_demo)

# Add some extra components. IDF_EXTRA_COMPONENT_DIRS is an variable used by ESP-IDF
# to collect extra components.
get_filename_component(
    EXTRA_COMPONENT_DIRS
    "components/sys" ABSOLUTE
)
list(APPEND IDF_EXTRA_COMPONENT_DIRS ${EXTRA_COMPONENT_DIRS})

get_filename_component(
    EXTRA_COMPONENT_DIRS
    "components/foo" ABSOLUTE
)
list(APPEND IDF_EXTRA_COMPONENT_DIRS ${EXTRA_COMPONENT_DIRS})

# As of now there's no offical way to redefine config files outside of FreeRTOS source tree.
# This is a temporary approach to inject an include path so that this takes precedence over the
# config file directory inside FreeRTOS.
include_directories(BEFORE freertos-configs)

# Add freertos as an subdirectory. AFR_BOARD tells which board to target.
set(AFR_BOARD espressif.esp32_devkitc CACHE INTERNAL "")
add_subdirectory(freertos)

# Link against the mqtt demo so that we can use it. Dependencies of this demo are transitively
# linked.
target_link_libraries(
    afr_demo
    PRIVATE
    AFR::demo_core_mqtt
    AFR::common_io
    AFR::ble_wifi_provisioning
)

In main.c
#include "wifi_provisioning\manager.h"
#include "wifi_provisioning\wifi_config.h"
#include "wifi_provisioning\scheme_ble.h"
.
.
.
    ESP_ERROR_CHECK(esp_event_handler_register(WIFI_PROV_EVENT, ESP_EVENT_ANY_ID, &event_handler, NULL));
    ESP_ERROR_CHECK(esp_event_handler_register(WIFI_EVENT, ESP_EVENT_ANY_ID, &event_handler, NULL));
    ESP_ERROR_CHECK(esp_event_handler_register(IP_EVENT, IP_EVENT_STA_GOT_IP, &event_handler, NULL));

Compile error
../src/main.c
../src/main.c:70:39: fatal error: wifi_provisioning\manager.h: No such file or directory
compilation terminated.
ninja: build stopped: subcommand failed.
ninja failed with exit code 1

Taking a look. Getting my workspace setup for my mac. I'll reply when I have more information on your issue.

Some questions for you:

How did you download the code? Did you check out aws/freertos from Github or did you use the AWS 'Device Software' page in the AWS console?
Have you recursively checked out submodules? I checked out the code from the repo, synced my submodules, and am seeing the wifi_provisioning files under /vendors/espressif/esp-idf/components/wifi_provisioning/include/wifi_provisioning
Have you tried building off of the existing BLE demo? You can select a demo following the instructions here

How did you download the code? Did you check out aws/freertos from Github or did you use the AWS 'Device Software' page in the AWS console?

I checked it out it directly from the AWS github repo.

Have you recursively checked out submodules? I checked out the code from the repo, synced my submodules, and am seeing the wifi_provisioning files under /vendors/espressif/esp-idf/components/wifi_provisioning/include/wifi_provisioning

It was recursively checked out.  I can see the source.  I just can’t reference certain files in the make process.

Have you tried building off of the existing BLE demo? You can select a demo following the instructions here

Building individual demos works, but I need to combine features from multiple demos.  That’s when I have problems.

Some further questions because I'm failing to set this up (or understand how it was setup).
You're directory structure looks something like the following, right?
|- CMakeLists.txt
|- src
|    |- main.c
|- freertos (amazon-freertos clone)
|    |-demos
|    |-freertos-kernel
|    |-(etc...)

Can you tell me more about how you've structured your project?

When I try this directory structure I'm greeted by 2 errors when I run cmake -B build -S .
This first error seems to stem from the fact that the IDF_PROJECT_EXECUTABLE is being added as an executable both in this top level CMakeLists.txt of yours and in the esp32 board CMakeLists.txt found here.
CMake Error at amazon-freertos/vendors/espressif/boards/esp32/CMakeLists.txt:434 (add_executable):
  add_executable cannot create target "afr_demo" because another target with
  the same name already exists.  The existing target is an executable created
  in source directory "/Users/kstribrn/workspace/oncall".  See documentation
  for policy CMP0002 for more details.
Call Stack (most recent call first):
  amazon-freertos/CMakeLists.txt:78 (include)

This second error might stem from the first one.
CMake Error at amazon-freertos/vendors/espressif/esp-idf/components/esp32/project_include.cmake:21 (message):
  Internal error, toolchain has not been set correctly by project (or an
  invalid CMakeCache.txt file has been generated somehow)
Call Stack (most recent call first):
  amazon-freertos/vendors/espressif/esp-idf/tools/cmake/build.cmake:312 (include)
  amazon-freertos/vendors/espressif/esp-idf/tools/cmake/build.cmake:457 (__build_process_project_includes)
  amazon-freertos/vendors/espressif/boards/esp32/CMakeLists.txt:595 (idf_build_process)
  amazon-freertos/CMakeLists.txt:78 (include)

How did you download the code? Did you check out aws/freertos from Github or did you use the AWS 'Device Software' page in the AWS console?
I checked it out it directly from the AWS github repo.

Have you recursively checked out submodules? I checked out the code from the repo, synced my submodules, and am seeing the wifi_provisioning files under /vendors/espressif/esp-idf/components/wifi_provisioning/include/wifi_provisioning
It was recursively checked out.  I can see the source.  I just can’t reference certain files in the make process.

Have you tried building off of the existing BLE demo? You can select a demo following the instructions herehttps://docs.aws.amazon.com/freertos/latest/userguide/getting_started_esp32wroom-32se.html#configure-demos-esp32wroom-32s-idf42
Building individual demos works, but I need to combine features from multiple demos.  That’s when I have problems.

—
Reply to this email directly, view it on GitHubhttps://github.com/aws/amazon-freertos/issues/3535#issuecomment-1262892628, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXFNZHPN5KSZLBIL7WH2ZOTWAYKZLANCNFSM6AAAAAAQXCV4QM.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

I structured my project where the amazon-freertos repo is brought in a submodule.  The reason is keep my code separate from the amazon repo.  I structured it this way based on the ticket linked here.
I then added my individual components in its own directory with a CMakeLists.txt file to reference include and source directories.

Thanks for linking to the amazon-freertos-examples repo. I dug around a bit and think I found what might be the source of your issue - though I don't have the solution just yet.
amazon-freertos-examples submodules this commit of amazon-freertos which in turn submodules Espressif's esp-idf (this commit).
This is important as it's the esp-idf 'wifi_provisioning' component which includes the wifi_provisioning/* header files your build is failing to find - see the wifi_provisioning component Cmake. The AWS 'ble_wifi_provisioning' module from AFR does not include these headers (from what I'm seeing). The 'ble_wifi_provisioning' module comes from the c-sdk which is independent of platform - see this Cmake.
As for how to fix this - I'm still figuring this out. The esp-idf documentation suggests that this component is available and included by default but this is clearly not the case.

As for why I think the component is available, below are some snippets from building the tgsong/amazon-freertos-examples...
-- Building for target esp32
-- Component names: soc log heap freertos vfs newlib esp_ringbuf driver esp_event ethernet mbedtls micro-ecc efuse bootloader_support partition_table app_update spi_flash nvs_flash lwip tcpip_adapter xtensa-debug-module app_trace pthread smartconfig_ack wpa_supplicant espcoredump esp32 cxx foo amazon-freertos-common secure_sockets bootloader nimble bt console esp_adc_cal nghttp esp_http_server esptool_py expat wear_levelling sdmmc fatfs freemodbus idf_test json mdns openssl protobuf-c protocomm spiffs ulp wifi_provisioning
-- Component paths: [some paths redacted for brevity];/Users/kstribrn/amazon-freertos-examples/freertos/vendors/espressif/esp-idf/components/wifi_provisioning
...
...
.espressif/tools/xtensa-esp32-elf/1.22.0-80-g6c4433a-5.2.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc -DAFR_ESP_LWIP -DESP_PLATFORM -DGCC_NOT_5_2_0=0 -DHAVE_CONFIG_H [some more removed stuff] -I/Users/kstribrn//amazon-freertos-examples/freertos/vendors/espressif/esp-idf/components/wifi_provisioning/include

Played around some more and found a couple work arounds...
The simplest for me was to change your imports from using a backslash to a forward slash. This should fix your build. From what I found backslash support is a per-compiler thing. The xtensa compiler might just not handle them as you expect.
#include "wifi_provisioning/manager.h"
#include "wifi_provisioning/wifi_config.h"
#include "wifi_provisioning/scheme_ble.h"

Now the more involved thing you can try if this doesn't work is to copy aws-freertos-examples/freertos/vendors/espressif/esp-idf/components/wifi_provisioning/include/wifi_provisioning/* to a single level up (aka aws-freertos-examples/freertos/vendors/espressif/esp-idf/components/wifi_provisioning/include/*). This results in two copies of the header files. You'll also need to modify your imports in main.c to...
#include "manager.h"
#include "wifi_config.h"
//#include "scheme_ble.h" //commenting this out as the copy causes further path issues.

and build this. If this works but the forward slash didn't work then the issue could lie in the specific commit of esp-idf in Amazon FreeRTOS (though I'm doubtful of this).

I'm going to close this since there hasn't been further activity. Feel free to reopen this if your issue still exists.


docs: Update FAQ

Fix indentation, grammar and some wording. Correct some factual claims or make them more precise (e.g. engine vs. connection string)

I don't know why the lint check failed. Maybe I have to specify python3 instead of python in the code blocks? But then again #23 shouldn't have worked..

I don't know why the lint check failed. Maybe I have to specify python3 instead of python in the code blocks? But then again #23 shouldn't have worked..
EDIT: it's something about trailing whitespace

I will fix it its related to pre-commit i guess you didn't run bash scripts/format.sh

I didn't even set up a venv or anything, I thought making documentation changes wouldn't require it. Seems I underestimated the depth these linters crawl through..

Thank you @iron3oxide 🙏🏻


fix: DeprecationWarning for negative y_true values in ndcg_score

Reference Issues/PRs
Will fix the following:
https://github.com/scikit-learn/scikit-learn/issues/17639
What does this implement/fix?
Implements a Deprecation Warning for negative values in the y_true ndarray when using ndcg_score
Any other comments?
Please add any other changes required for the docs or code in this branch
Please Review.

[x] @ciaran-h Does not need to commit any more changes
[x] @ciaran-h has reviewed
[x] @VKo232 Does not need to commit any more changes
[x] @VKo232 has reviewed
[x] @trinhcon has reviewed

Closed this PR because of a github issue to meet the proper checks, will open another one to properly address the issue


Return 400 on webhook handler error

Fix errors from webhooks firing out of order (eg. Stripe price before product).

Fix errors from webhooks firing out of order (eg. Stripe price before product).

The order doesn't matter as we simply upsert products and prices. What errors are you seeing?

The problem here is Stripe doesn’t fire it’s webhooks in order. So when the price webhook fires before the product there is an error, because of the foreign key constraint. If there’s no 400 it’s very difficult to determine what’s going on. This happened to me several times, when trying to get started.

@rprwhite I forgot about the foreign key product_id text references products,, you are quite right indeed, thank you!


remove the dialog blocking back button exit on WP8.1

should find that pressing back button will not be handled by unity now and the app closes cleanly on WP8.1 and the live tiles update. There is still a Quit button in the scene which will call Application.Quit, anything that calls this on WP8.1 will cause the app to crash out, and normal lifecycle flow will not occur (e.g. OnVisibilityChanged etc.). There is no way to programmatically invoke the back button after displaying a message dialog, so they should be avoided. If they do end up getting used on a game, then the side effect is no live tile processing, unless the player uses windows key (which most do) rather than back button to exit game.
Will test this in morning when i can deploy to phone and update.

Application.Quit is required by design it seems with Unity handling the back button exclusively so we'll not workaround this and instead raise with them that this does not cleanly exit the application as within an app.


Separate Scratchpad for edited file

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Is your feature request related to a problem? Please describe.
It makes that hard to be in line with graph contributors/coworkers when everybody has to reimport Scratchpad in drawio just to have the latest templates. To have personal Scratchpad intact, while importing another, I also have to export it and reimport on demand, which is time consuming. That also impacts my colleagues.
Describe the solution you'd like
Separate Scratchpad embedded into file - because then we don't have to reimport personal Scratchpad or make everybody ever touch "Edit" and "Import" buttons in that section, while collaborating on several diagrams with different shapes.
Describe alternatives you've considered
Of course, one can export desired Scratchpad with a lots of shapes and make everybody in team to import it, but one may have personal Scratchpad that was not saved or no time for importing utility scratchpads at all (considering this pencil icon in "Scratchpad" section is very small to notice for novice, which is different story about UI/UX).
Additional context
There is kind of similar issue #5, but contents unlike title don't have bearing on actually embedding Scratchpad into file.

And using libraries doesn't solve this?


[DISCUSS] Naming of variables during transformation

We have lots of implicit agreement on variable naming, for example:

lv means local variable, while gv means global variable
sh means shape variable
storage means storage, alloc and tensor both mean allocated tensor
...

Those naming conventions often are introduced by different transformation pass and the reflected property are often orthogonal, for example, a variable can be a local variable also a shape variable. Using those conventions together would make the final program a mess. For example:
Orignal program:
@tvm.script.ir_module
class Module:
    @relax.function
    def foo(x: Tensor[_, "float32"]) -> Tensor[_, _]:
        # block 0
        with relax.dataflow():
            sh = relax.call_packed("vm.builtin.shape_of", x)
            x0 = relax.match_shape(sh, (n, m))
            y = relax.call_dps((n, (m * 2)), "test.vm.tile", x)
            relax.output(y)
        return y

After lowering:
@tvm.script.ir_module
class Module:
    @tir.prim_func
    def shape_func(heap_1: tir.handle) -> None:
        # function attr dict
        tir.func_attr({"global_symbol": "shape_func"})
        H_1 = tir.match_buffer(heap_1, [tir.int64(4)], dtype="int64")
        # body
        tir.store(H_1.data, 2, tir.load("int64", H_1.data, 0) * (tir.load("int64", H_1.data, 1) * tir.int64(2)) * tir.int64(4), True)

    @tir.prim_func
    def shape_func1(heap_1: tir.handle) -> None:
        # function attr dict
        tir.func_attr({"global_symbol": "shape_func1"})
        H_1 = tir.match_buffer(heap_1, [tir.int64(4)], dtype="int64")
        # body
        tir.store(H_1.data, 0, tir.load("int64", H_1.data, 0), True)
        tir.store(H_1.data, 3, tir.load("int64", H_1.data, 1) * tir.int64(2), True)

    @relax.function
    def foo(x: Tensor[_, "float32"]) -> Tensor[_, _]:
        # block 0
        shape_heap: Tensor[(4,), "int64"] = relax.call_packed("vm.builtin.alloc_shape_heap", (4,))
        # block 1
        sh = relax.call_packed("vm.builtin.shape_of", x)
        gv = relax.vm.builtin.store_shape(sh, shape_heap, indices=[0, 1], attrs_type_key="relax.attrs.ShapeHeapAttrs")
        _ = shape_func(shape_heap)
        sh1 = relax.vm.builtin.load_shape(shape_heap, indices=[2], attrs_type_key="relax.attrs.ShapeHeapAttrs")
        storage = relax.vm.builtin.alloc_storage(sh1, device_type=1, dtype="float32", attrs_type_key="relax.attrs.AllocStorageAttrs")
        _1 = shape_func1(shape_heap)
        sh11 = relax.vm.builtin.load_shape(shape_heap, indices=[0, 3], attrs_type_key="relax.attrs.ShapeHeapAttrs")
        tensor = relax.vm.builtin.alloc_tensor(storage, sh11, offset=0, dtype="float32", attrs_type_key="relax.attrs.AllocTensorAttrs")
        alloc = tensor
        _2 = relax.call_packed("test.vm.tile", x, alloc)
        y = alloc
        # block 2
        return y

We might want to have a unified naming convention instead of creating one by one in each transformation to improve readability.

summary of offline discussion during open source meeting:

We should definitely standardize the naming convention across passes at least. It would be good to keep some semantic hint in the name if possible, although this might need some further discussion to agree on a convention.
We should have a single NameTable that lives across the entire compilation pipeline, so that passes can query it without causing duplicate names (currently a new NameTable is created for every BlockBuilder, so each pass has a new NameTable).
People prefer the unique names to start with index 0, e.g. "x" -> "x0" (the first time gettin a unique name for "x").
There could still be potential for edge case unique name generation causing something like "x1" -> "x11". We should try to identify the causes and prevent this if possible.


[Login page] Wrong alignment of the welcoming text.

Environment: Nexus 4, Android 11.0
Reproducible: always.
Build found: v1.0.502.
Steps to reproduce

Go to the 'Login' page.
Verify the alignment of the text on the top of the page.

Actual result

The alignment of the "Welcome to" text is wrong.

Expected result

The "Welcome to" text is aligned as displayed on the mock-up.

User story and test case links
E.g.: "User story #244
Labels to be added
"Bug" ("bug"), Priority ("pri: low")

tested on 4 devices, no problems detected
!(https://ibb.co/ZgnnSXt)
!(https://ibb.co/YQ07FZ4)
!(https://ibb.co/VDdhC9m)
!(https://ibb.co/Hn1L7qZ)


Get preview / thumbnail / image of individual slides in PowerPoint using OfficeJS and Office Add-Ins (Web)

We need to obtain image previews or thumbnails of each slide in an Office Add-In. We are currently developing a functionality using Office Add-Ins (PowerPoint), where users can open a PowerPoint presentation (hosted remotely) and click on the presentation to view all slides (with preview images) in the right panel of the Office Add-In. They should also be able to select a slide and insert it. We have searched through the Office Add-Ins documentation, but we could not find any method that can be used to generate thumbnail of the slides. We would greatly appreciate any assistance or alternative solutions to achieve this in Office Add-Ins.

Hi @pg-dev0,
You are correct that there is not a current mechanism to get a slide thumbnail from the JS APIs. I'm going to transfer this issue to the product repo so the right folks can take a look at this feature request.


Xamarin Forms: MediaElement: Feature Request: Stick the control bar always on top of the screen

I am using MediaElement for playing audio. My problem is the controls(Play, pause, and duration bar) are not showing always. If I tap on the MediaElement the controls are showing else only a black screen. I need to keep the controls always there at the whole time of audio play.
Currently audios are playing like below:

I tried true value for KeepScreenOn and ShowsPlaybackControls properties, but no luck.
I need output like below screenshot:

I can't use webview here because I need to perform some operations when the audio play end.

I think this issue was fixed. @sreejithsree139 could you please install the latest pre-release of the Xamarin.CommunityToolkit and verify this works for you?

@jfversluis not fixed yet
The request is keeping playback controls always visible, as I understand

https://stackoverflow.com/questions/4458529/mediacontroller-always-show-on-android

Well, seems it's hard to achieve it on iOS

That's not possible. There is not any Public API of AVPlayerViewController to keep playback controls visible all time. You must have to make your own custom playback controls for this i.e. play button, seekbar, duration label etc.

https://stackoverflow.com/questions/53944561/avplayerviewcontroller-how-to-display-always-playback-controls#:~:text=There is not any Public,%2C seekbar%2C duration label etc.
@jfversluis are we going to implement it then?

It seems the "always visible" control bar supposed to be a custom-built solution.
Put media element inside absolute layout, then put custom controls above (buttons, slider etc.)

@jfversluis and @AndreiMisiukevich  I have installed the latest xamarin forms pre-release.
Getting below error for MediaElement:
Severity	Code	Description	Project	File	Line	Suppression State	Suppression State
Error		 : XamlC error XFC0000 : Cannot resolve type "MediaElement"

@sreejithsree139 MediaElement migrated to XamarinCommunityToolkit

I'm kind of confused what is all going on in this issue :D The title speaks of a feature request, but in the issue I see bugs.
Anyhow, as per your latest comment @sreejithsree139 you will need to import the Xamarin.CommunityToolkit namespace first and use that. For example:
<ContentPage xmlns:toolkit="http://xamarin.com/schemas/2020/toolkit">
    <toolkit:MediaElement />
</ContentPage>

Also see the example page here: https://github.com/xamarin/XamarinCommunityToolkit/blob/main/samples/XCT.Sample/Pages/Views/MediaElementPage.xaml

For now I would say we're not going to implement this. The MediaElement works as expected on the native platforms and I think you have all the events, methods and properties to create your own playback controls, see the Docs here. It might be something nice to add in the future, but for now I think other things will have priority for the MediaElement.
Closing this issue as such, if you believe there is an actual bug or a feature request, please open an issue with the right template and provide as much detail as possible.
This might be something good to note though on the MediaElement Docs pages that "ShowPlaybackControls" is only temporary on iOS.


Multiple database support

Related to #94 Rails 6 has multiple database connections.
Do you plan on adding support for checking the health of multiple databases, very crudely:
ActiveRecord::Base.configurations.configs_for.select { |con| con.env_name == Rails.env }

?

@nikolai-b you can check an alternative

At this point, No, I am not intending to code for multiple database support, but am happy to accept a PR if you want to code it.
If you send me a PR, or a custom health check, I can look at including it.


Hotfix/qj scheduler quota support

这个 PR 实现什么功能/修复什么问题:
修正：调度时候需要考虑配额的约束，不能调度到无配额的区域
是否需要 backport 到之前的 release 分支:

release/2.13
release/2.14
release/3.0

/area region
/area scheduler
/cc @zexi @wanyaoqi @ioito

Codecov Report

Merging #4488 into master will decrease coverage by <.01%.
The diff coverage is 1.11%.

@@            Coverage Diff            @@
##           master   #4488      +/-   ##
=========================================
- Coverage    6.84%   6.83%   -0.01%
=========================================
  Files         521     522       +1
  Lines       88448   88572     +124
=========================================
  Hits         6050    6050
- Misses      81893   82016     +123
- Partials      505     506       +1

Flag
Coverage Δ

#aFlag
6.83% <1.11%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/compute/models/guestnetworks.go
0.21% <ø> (ø)
:arrow_up:

pkg/compute/models/projectquota.go
25% <0%> (-1.75%)
:arrow_down:

pkg/cloudcommon/db/modelbase.go
1.42% <0%> (-0.04%)
:arrow_down:

pkg/compute/models/quotas.go
7.41% <0%> (-0.41%)
:arrow_down:

pkg/compute/models/regionquota.go
8.09% <0%> (-0.89%)
:arrow_down:

pkg/compute/models/networks.go
0.54% <0%> (ø)
:arrow_up:

pkg/cloudcommon/db/quotas/context.go
0% <0%> (ø)

pkg/compute/models/cloudaccounts.go
0.86% <0%> (ø)
:arrow_up:

pkg/compute/models/guest_actions.go
0% <0%> (ø)
:arrow_up:

pkg/compute/models/guests.go
0.56% <0%> (ø)
:arrow_up:

... and 7 more

Continue to review full report at Codecov.

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

/lgtm

/lgtm

/hold

/lgtm
/approve

/hold cancel

/lgtm


New ACS Commons compatible with AEM 6.3

A new set of ACS commons bundles (currently at 3.4.0) are need which are compatible with AEM 6.3.
This is needed in order to validated the upgrade of AEM from 6.x to 6.3 prior to the official release of the 6.3 GA.
Later Edit: The bundles should be applicable for snapshots/load post AEM 6.3 Load 14

@chibulcuteanu the latest release (3.5.0) is compatible with the latest AEM 6.3 internal load. I'm going to keep this issue open until 6.3 is GA as additional changes may be necessary. Please report any issues you find here.

AEM 6.3L15 Content Fragment editor UI breaks due to the inclusion of: /apps/acs-commons/touchui-widgets/source/icon-picker.js
$('[data-init~=graphiciconselect] > select') is undefined.
$(document).on('cui-contentloaded.data-api', function (e) {
    $('[data-init~=graphiciconselect] > select').fontIconPicker({
        'theme' : 'fip-coral'
    });
});

@davidjgonzalez that looks weird. if the selector [data-init~=graphiciconselect] > select doesn't match any elements, jQuery is supposed to return an empty set, not undefined.

@justinedelson when trying to install this content package over a 6.3 L16 upgraded instance, the acs-aem-tools-bundle-0.0.28.jar bundle cannot start due to the fact that "com.day.cq.widget,version=[5.5,6) -- Cannot be resolved" Is there something on acs part that needs to be added/modified?

Please report Tools issues in the Tools project.
On Mon, Dec 19, 2016 at 9:51 AM chibulcuteanu<EMAIL_ADDRESS>wrote:

@justinedelson https://github.com/justinedelson when trying to install
this content package over a 6.3 L16 upgraded instance, the
acs-aem-tools-bundle-0.0.28.jar bundle cannot start due to the fact that
"com.day.cq.widget,version=[5.5,6) -- Cannot be resolved" Is there
something on acs part that needs to be added/modified?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/855#issuecomment-267982584,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEBclZ-1ee1QTQVmGJROgDMtY-Qg87wks5rJpnvgaJpZM4K-qkE
.

@justinedelson we good to close this with 3.8.0 release?

I feel like we should keep this open until 6.3 is actually released. But let's be optimistic and close and reopen if necessary.


[silicon_creator] refactor OTBN boot services to enable generating TPM or DICE keys

This fixes #22622 to enable generating TPM attestation keys off of the keymgr sealing side and DICE attestation keys off of the keymgr attestation side.
Additionally, this cleans up the DICE lib to reduce code size and align naming conventions.

Oops, sorry @vbendeb , meant to submit this to the upstream repo. My appologies!


PageHeader: PageHeader redesign v.2 (Part I: core changes)

Review feedback

@ayeshakmaz a better implementation for border color with tokens?

Summary
What changed?
PageHeader now supports:

Badge in title
Helper button in title
Thubnail in title
Second block for secondary components such as Datapoint or form fields
Responsiveness to lg, md, sm, and mobile breakpoints
Full vis diff test coverage

Follow up PRs:

II: Improve unit testing
III: Update Docs with updated documentation

Before

After

Why?
Increase support to m10n teams needs and increase PageHeader adoptions
Breaking Changes
PageHeader V.2 comes with breakpoint responsiveness. Under sm breakpoint, primary and secondary actions (if secondary is present) get displayed as options in a Dropdown.
Run the following codemod to locate PageHeader with secondaryAction prop so manual changes can be done. If secondaryAction prop is present, two props become required dropdownItems and dropdownAccessibilityLabel
yarn codemod detectManualReplacement ~/path/to/your/code --component=PageHeader --prop=primaryAction
Links

TDD
Figma

Checklist

[ ] Added unit and Flow Tests
[X] Added documentation + accessibility tests
[ ] Verified accessibility: keyboard & screen reader interaction
[X] Checked dark mode, responsiveness, and right-to-left support
[X] Checked stakeholder feedback (e.g. Gestalt designers)

Is the 1px height difference in the existing snapshots expected?
It also looks like a number of snapshots are adding significant whitespace below the component — is that expected?

Yes, that's because I need space below the PageHeader to capture the Dropdown on xs breakpoint

The alignment with the badge and icon button looks off…is this intended?
Can we set a width on the parent of this example (and possibly others) to show how the component will display on large viewports?  These also look pretty odd:


Update the map between console color to VT sequences

PR Summary
Update the map between console color to VT sequences.
The ConsoleColor to VT Escape Sequences mapping in VTUtils.cs is not accurate, and thus is updated according to https://docs.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences#text-formatting
https://github.com/PowerShell/PowerShell/blob/895d4b3f3ebb51193d68095d2a95549b0b92c5fc/src/System.Management.Automation/utils/VTUtils.cs#L25-L43
The update is needed as "Bright foreground color" (e.g. bright red \x1b[91m) is rendered differently from bold color (e.g. \x1b[1;31m) in some front-end client, such as the Jupyter Notebook client.
See the 3rd and 4th output below as an example:

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

Did you check the color rendering on Linux and/or macOS and Windows Terminal?

I did check on console host and win terminal, but not Linux and macOS yet. Will do that and update here.

I tested the changes on console host, windows terminal, Linux terminal and macOS terminal, and all look good:
Windows console host

Windows terminal

Linux

macOS
screenshot is coming up soon

@SteveL-MSFT Please update your review

LGTM.   Let's merge so we can start the build

Since I have tested it on all platforms, I'm OK to merge this PR.

I am OK to merge this PR.


Job variables not passed to image

Might be that I missed something obvious but it seems that job variables aren't exported to Docker executor. The following example works in Gitlab CI but not in gitlab-ci-local:
entrypoint.sh:
#!/usr/bin/env bash

: "${SPECIAL_VARIABLE?"Requires SPECIAL_VARIABLE"}"

echo "Special variable: $SPECIAL_VARIABLE"

Dockerfile:
from bash:5

COPY entrypoint.sh /entrypoint.sh
ENTRYPOINT /entrypoint.sh

.gitlab-ci.yml:
job-variable-test:
  image: spikeb/gcl:job-variable-test  # built using the files above
  variables:
    SPECIAL_VARIABLE: "test"
  stage: build
  script:
    - echo "$SPECIAL_VARIABLE"

Expected output:
❯ gitlab-ci-local job-variable-test
yml files         processed in 36 ms
job-variable-test starting gcl:variable-expansion (build)
job-variable-test pulling gcl:variable-expansion
job-variable-test pulled in 217 ms
job-variable-test copying to container /builds/
job-variable-test copied in 249 ms
job-variable-test > Special variable: test
job-variable-test finished in 1.25 s
test
successful job-variable-test

What I get instead:
❯ gitlab-ci-local job-variable-test
yml files         processed in 31 ms
job-variable-test starting spikeb/gcl:job-variable-test (build)
job-variable-test pulling spikeb/gcl:job-variable-test
job-variable-test pulled in 415 ms
job-variable-test copying to container /builds/
job-variable-test copied in 274 ms
job-variable-test > /entrypoint.sh: line 3: SPECIAL_VARIABLE: Requires SPECIAL_VARIABLE
job-variable-test finished in 1.6 s exited with code 1

failure job-variable-test

@okuuva Nah its me thats missing something obvious 😊
Fix coming up tomorrow...

https://github.com/firecow/gitlab-ci-local/pull/100 @okuuva
This is fixed, when the PR is merged, and a new version is published


Allow generate-raw to run single witx files

Previously, the witx path was hard-coded to a snapshot but this change allows me to use it for wasi-nn.

I think this'll need some CI tweaks to work as well? Otherwise seems good to me!


Show suggestions for misspelled words

typo.js has a suggest function, but it seems there's not a way for a user to invoke it and get suggestions for their misspelled words.

A feature like this would need a significant amount of work to make it look clean and polished. But I'll keep this open as an idea.

+1
I would love to see this feature. Any plans to implement it ?

If someone submits a polished PR, then it would likely be merged in.


console title should change after youtube-dl finishes [fails in Terminal.app]

Reported by @joeschmoe40:
If you use --console-title, the console title is left changed (messed up)
after the program exits (at least on Mac OSX).

If someone wants this to work in Terminal.app and it doesn't now, please make a new issue quoting this.


Revert "Nice log" - 77

[Auto generated]
Number: [#77]

github-gitlab-webhook-server: Closing issue for PR: Revert "Nice log".
PR was closed.


Getting 504: GATEWAY_TIMEOUT for supabase route

URL I'm trying to access is: https://llmctx.com/supabase-js

Ah, it might be too big, or Supabase changed something in their repo. Don't have time to check currently, but if anyone wants to take a look, I'd appreciate that.


InnertubeError: Comments page did not have any content.

Steps to reproduce
While commenting on a video, the comments were working fine until last week. Now getting this error.
Simple code -
 await yt.session.signIn(creds);

    const comment_section = await yt.getComments(video_id);

    console.info(`This video has ${comment_section.header?.comments_count.toString() || 'N/A'} comments.\n`);

    await comment_section.createComment(content_to_post);

Failure Logs
InnertubeError: Comments page did not have any content.
    at new Comments (/Users/yash.bansal/workspace/YouComment/node/node_modules/youtubei.js/src/parser/youtube/Comments.ts:29:13)
    at Innertube.<anonymous> (/Users/yash.bansal/workspace/YouComment/node/node_modules/youtubei.js/src/Innertube.ts:192:12)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/yash.bansal/workspace/YouComment/node/node_modules/tslib/tslib.js:166:62)
    at processTicksAndRejections (node:internal/process/task_queues:95:5) {
  date: 2023-10-11T03:22:16.442Z,
  version: '6.4.1'

Expected behavior
The comment to be posted on youtube
Current behavior
Getting the above exception
Version
Edge
Anything else?
Using latest version - 6.4.1
Checklist

[X] I am running the latest version.
[X] I checked the documentation and found no answer.
[X] I have searched the existing issues and made sure this is not a duplicate.
[X] I have provided sufficient information.

Any updates on this?

Are you getting this error for every video? It's coming from this line: https://github.com/LuanRT/YouTube.js/blob/e02139532b2c07aaf72dd1bd8610f63b6780001d/src/parser/youtube/Comments.ts#L28-L29 And means YouTube returned a response without any relevant content. Not a lot we can do about it without knowing how you are using the library.

I'm getting this error -
InnertubeError: Request to https://www.youtube.com/youtubei/v1/comment/create_comment?prettyPrint=false&alt=json failed with status 400     at HTTPClient.<anonymous> (/Users/yash.bansal/workspace/YouComment/node/node_modules/youtubei.js/src/utils/HTTPClient.ts:145:11)     at Generator.next (<anonymous>)     at fulfilled (/Users/yash.bansal/workspace/YouComment/node/node_modules/tslib/tslib.js:166:62)     at processTicksAndRejections (node:internal/process/task_queues:95:5) {   info: '{\n' +     '  "error": {\n' +     '    "code": 400,\n' +     '    "message": "Request contains an invalid argument.",\n' +     '    "errors": [\n' +     '      {\n' +     '        "message": "Request contains an invalid argument.",\n' +     '        "domain": "global",\n' +     '        "reason": "badRequest"\n' +     '      }\n' +     '    ],\n' +     '    "status": "INVALID_ARGUMENT"\n' +     '  }\n' +     '}\n',   date: 2023-11-01T17:41:22.454Z,   version: '7.0.0' }
I'm using it like this
`    const comment_section = await yt.getComments(video_id);
console.info(`This video has ${comment_section.header?.comments_count.toString() || 'N/A'} comments.\n`);

await comment_section.createComment(content_to_post);`


SQL: Ditch CalciteConnection layer and add DruidMeta, extension aggregators.

Switched from CalciteConnection to Planner, bringing benefits:

CalciteConnection's JDBC interface no longer sits between the SQL server
(HTTP/Avatica) and Druid's query layer. Instead, the SQL servers can use
Druid Sequence objects directly, reducing overhead in the query return path.

Implemented our own Planner-based Avatica Meta, letting us control
connection timeouts and connection / statement limits. The previous
CalciteConnection-based implementation didn't have any limits or timeouts.

The Planner interface lets us override the operator table, opening up
SQL language extensions. This patch includes two: APPROX_COUNT_DISTINCT
in core, and a QUANTILE aggregator in the druid-histogram extension.

Also:

Added INFORMATION_SCHEMA metadata schema.

Added tests for Unicode literals and escapes.

👍

cool, :+1:


Feature request: Stop services when not usable

I'm not sure if it is feasible but it would be nice if the LocationServiceV2 is stopped immediately if there isn't at least one backend enabled; the same for GeocodeServiceV1

That's not possible: The services are bound by the system, stopping them will cause location/geocode to be unavailable until next reboot.
Also note there is no reason to stop services: "running" services is mostly a state, not actual code being executed and thus no harm to battery. The memory footprint of these services is also negligible.


Repair and stock

I found necessary to repair sometimes as the nav beacon can be hit..
Also there is a known bug in ED with the passenger cabins. If the cabin needs to be replenish, if you do it through the passenger missions menu (the bot will trigger it trying to select the cabin for the mission) the game will crash. To avoid this you can use the option stock while docked in the main menu

it seems that you add two clicks to repair and restock button, so plz edit the comments in those codes from force refuel to force xxx


usetoast.ts Runtime Error useState

Hey folks,
I want to use the toast and I installed it via CLI. In my ui folder there is a toast.tsx, toaster.tsx and use-toast.ts file. I just wanted to try the example code of the docs on my page.tsx file.
import { Button } from '@/components/ui/button';
import { useToast } from '@/components/ui/use-toast';

export default function Home() {
  const { toast } = useToast();
  return (
    <div>
      <Button
        onClick={() => {
          toast({
            title: 'Scheduled: Catch up',
            description: 'Friday, February 10, 2023 at 5:57 PM',
          });
        }}
      >
        Show Toast
      </Button>
    </div>
  );
}

But when I run dev there is a runtime error, which says: Error: useState only works in Client Components.
components/ui/use-toast.ts (168:28) @ React

function useToast() {
const [state, setState] = React.useState<State>(memoryState);

React.useEffect(() => {
listeners.push(setState);

My component.json:
{
  "$schema": "https://ui.shadcn.com/schema.json",
  "style": "new-york",
  "rsc": true,
  "tsx": true,
  "tailwind": {
    "config": "tailwind.config.js",
    "css": "app/globals.css",
    "baseColor": "neutral",
    "cssVariables": true
  },
  "aliases": {
    "components": "@/components",
    "utils": "@/lib/utils"
  }
}

I am a little bit confused. Somebody can give me a hint.

Each page file is a RSC by default which is why you're getting this error. You'll need to add the "use client" directive to mark it is a Client Component otherwise it won't work.
You can make a separate component for that as well and use it in your page.tsx file

You are right, I just had a thinking error.


Add direct control of extra labels for scanner jobs / pods

Is your feature request related to a problem? Please describe.
On constrained cluster, i.e., clusters where all nodes are tainted, thus pod spec without tolerations do not have a chance to be scheduled, it is necessary to manipulate job template for kubeclarity's scanners in order to achieve proper scheduling.
However, on those clusters there may be pod-manipulating policies (such as Kyverno's) that enable scheduling of appropriately-labeled pods.
Describe the solution you'd like
Having the ability to add arbitrary labels to scanner jobs and their pods should be enough to achieve more controllability of scanner pod scheduling.
It is desirable to have control of extra labels to add in job template, both here (for pod's labels) and here (for job's labels).
Describe alternatives you've considered
Adding (Kyverno) policy targeting kubeclarity's scanner jobs/pods should be also feasible, but there's a catch: job is labeled with a simple "app: scanner", which my prove too generic to be useful in order to pinpoint ONLY Kubeclarity's pods. Maybe adding some other labels which include kubeclarity's name can make this way more predictable with respect to result.

That would be great, thank you @FrimIdan !👍


Program should exits with appropriate error codes and helpful error messages. If there are no errors, exit with 0. Otherwise, exit with a non-zero exit code (e.g., 1).

When files are translated successfully, exit with code 1
When there are errors, such as missing API Key or missing files arguments, exits with code 0

Added appropriate exit codes, and helpful error messages.


Not finding cuda library for jobs that do NOT require GPU

I am having this error when I use the slurm (http://slurm.schedmd.com/) workload manager. When I run some tensorflow python scripts, sometimes it results in an error (attached). It seems that it can't find cuda library installed but I am running scripts that do not require GPUs.  Therefore, I find it very confusing why cuda would be an issue at all. Why is cuda installation an issue if I don't need it?

Operating System:   CentOS Linux release 7.2.1511
Installed version of CUDA and cuDNN (calling ls -l /usr/lib/libcuda.so.352.63):
-rwxr-xr-x 1 root root 14272428 Dec 15  2015 /usr/lib/libcuda.so.352.63
If installed from binary pip package, provide:
tensorflow (0.9.0)

The output from python -c "import tensorflow; print(tensorflow.__version__)". running this seems to produce different results from the error I expected. what it outputs:

I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcublas.so locally
I tensorflow/stream_executor/dso_loader.cc:102] Couldn't open CUDA library libcudnn.so. LD_LIBRARY_PATH: /cm/shared/openmind/cuda/7.5/lib64:/cm/shared/openmind/cuda/7.5/lib
I tensorflow/stream_executor/cuda/cuda_dnn.cc:2092] Unable to load cuDNN DSO
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcufft.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcuda.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcurand.so locally

the error I expected:
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcublas.so locally
I tensorflow/stream_executor/dso_loader.cc:102] Couldn't open CUDA library libcudnn.so. LD_LIBRARY_PATH: /cm/shared/openmind/cuda/7.5/lib64:/cm/shared/openmind/cuda/7.5/lib
I tensorflow/stream_executor/cuda/cuda_dnn.cc:2092] Unable to load cuDNN DSO
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcufft.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcuda.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcurand.so locally
E tensorflow/stream_executor/cuda/cuda_driver.cc:491] failed call to cuInit: CUDA_ERROR_NO_DEVICE
I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:153] retrieving CUDA diagnostic information for host: node047
I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:160] hostname: node047
I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:185] libcuda reported version is: Not found: was unable to find libcuda.so DSO loaded into this program
I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:347] driver version file contents: """NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.63  Sat Nov  7 21:25:42 PST 2015
GCC version:  gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC)
"""
I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:189] kernel reported version is: 352.63.0
I tensorflow/core/common_runtime/gpu/gpu_init.cc:81] No GPU devices available on machine.

Steps to reproduce

run the sbatch command in slurm and dispatch about 1000 jobs running an idential tensorflow script. Returns that error.

What have you tried?

I've tried logging into the node directly throwing the error and run tensorflow jobs but it seems when I do that there are no errors.

Logs or other output that would be helpful
(If logs are large, please upload as attachment).
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcublas.so locally
I tensorflow/stream_executor/dso_loader.cc:102] Couldn't open CUDA library libcudnn.so. LD_LIBRARY_PATH: /cm/shared/openmind/cuda/7.5/lib64:/cm/shared/openmind/cuda/7.5/lib
I tensorflow/stream_executor/cuda/cuda_dnn.cc:2092] Unable to load cuDNN DSO
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcufft.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcuda.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcurand.so locally
E tensorflow/stream_executor/cuda/cuda_driver.cc:491] failed call to cuInit: CUDA_ERROR_NO_DEVICE
I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:153] retrieving CUDA diagnostic information for host: node047
I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:160] hostname: node047
I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:185] libcuda reported version is: Not found: was unable to find libcuda.so DSO loaded into this program
I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:347] driver version file contents: """NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.63  Sat Nov  7 21:25:42 PST 2015
GCC version:  gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC)
"""
I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:189] kernel reported version is: 352.63.0
I tensorflow/core/common_runtime/gpu/gpu_init.cc:81] No GPU devices available on machine.

TensorFlow has separate builds for CPU and GPU binaries (http://ci.tensorflow.org/view/Nightly/) You seem to be running a GPU build on a machine that has no GPUs, hence the warning. However, it should still work regardless, this message is purely informational.

@yaroslavvb however, the observed behavior is that the job just stalls and does not move on. Is there some way to go around this? I never requested it to run on GPUs in the first place so its confusing that its doing this.

Job stalling is unrelated to the message. GPU initialization happens when TensorFlow library is loaded, regardless of whether you actually need GPU or not.

I also made a stackoverflow question for it: http://stackoverflow.com/questions/38727375/why-do-jobs-in-slurm-freeze-indefinitely-when-they-are-tensorflow-scripts and currently put a bounty of 100 on it.
I'd love to be able to solve this and why its stalling. Not sure if its tensorflow or the computers/nodes themselves.

Just to add more information to the discussion, in slurm one can explicitly say to assign jobs to nodes with GPU's. I've observed that the apparent "stalling" only happens when jobs are sent to machine that are suppose to be CPU only.
If the machine is artificially restricted to only use CPU but tensorflow detects GPUs, can tensorflow accidentally get stuck?

Is there anything I can do to help get this resolved? Thanks! :)

@brando90 I've added some suggestions on the stackoverflow thread (remove queues, add session timeouts, use cpu-only binary, try to match env to reproduce locally, isolate exactly which line gets stuck). From the description it's not clear that there's anything wrong with tensorflow

It's possible there's a bug with the nvidia driver -- I've seen reports of people updating their driver and solving some issues like these.  In particular, TF shouldn't be doing anything with your GPUs after trying to initialize them if you never use them.  I'm going to close this for now unless there's more evidence that there's something in TF we're doing wrong (we can't really reproduce this, so you'd have to do some debugging to help us out, not sure what other help we can offer).

I was checkpointing my tensorflow models and once I stopped doing that the stalling issue stopped (for the moment). Not sure if that was it but it might be some way locking works with tensorflow interferes with slurm.


Preview resolution settings

Hello everyone,
Recently we developed a custom camera module. We encountered a problem. When using libcamera-still, there is some difference between the field of view previewed and the field of view of the final stored image (the default is the maximum resolution). By looking at the code, we found that the current preview resolution is set to 1280x960, but our camera cannot use the binning mode to obtain the maximum field of view at this resolution. Is there any way to solve this problem?Maybe we can manually set the preview resolution?

Hi, thanks for the questions.
You can certainly change the 1280x960 preview resolution to something that works better for you, there should be no problem in doing that. I've sometimes wondering about changing these values, perhaps to half the full sensor width and height so that one would often pick up the 2x2 binning mode, but there's still no absolute guarantee that you would get what you want. Another idea might be to add options so that you can choose on the command line. Would that be helpful?
The slightly longer answer to this is that libcamera doesn't give you terribly good control currently over which mode gets chosen (for example, would the application want a faster framerate, or a greater bit-depth, or a larger field of view?) and this is an on-going discussion!

I've sometimes wondering about changing these values, perhaps to half the full sensor width and height so that one would often pick up the 2x2 binning mode, but there's still no absolute guarantee that you would get what you want. Another idea might be to add options so that you can choose on the command line. Would that be helpful?

We have the same idea. At present, these two methods are effective for us, but specified by command line parameters seems to be more general. Maybe it is possible to combine the two methods?

It worked very well for me, thank you very much!


Web5 test vectors setup & integration

Removes the copied test vectors, and instead pulls them in from the web5-spec repository, which is added to this repo as a submodule.
Also added the necessary Github actions to upload artifacts and trigger a SDK report runner build.

looks good so far!

import XCTest

@testable import Web5

final class Web5TestVectorsDidJwk: XCTestCase {

    func test_resolve() throws {
        let testVector = try TestVector<String, DIDResolutionResult>(
            fileName: "resolve",
            subdirectory: "test-vectors/did_jwk"
        )

        testVector.run { vector in
            let expectation = XCTestExpectation(description: "async resolve")
            Task {
                let didURI = vector.input
                let result = await DIDJWK.resolve(didURI: didURI)
                XCTAssertNoDifference(result, vector.output)
                expectation.fulfill()
            }

            wait(for: [expectation], timeout: 1)
        }
    }

}

so I see the test name is test_resolve.
For it to just 'work out of the box' and be the same as everything else the test name should be resolve
If this is not possible or a massive anti pattern it is ok to keep it and we can change the runner to accept this

import XCTest

@testable import Web5

final class Web5TestVectorsDidJwk: XCTestCase {

    func test_resolve() throws {
        let testVector = try TestVector<String, DIDResolutionResult>(
            fileName: "resolve",
            subdirectory: "test-vectors/did_jwk"
        )

        testVector.run { vector in
            let expectation = XCTestExpectation(description: "async resolve")
            Task {
                let didURI = vector.input
                let result = await DIDJWK.resolve(didURI: didURI)
                XCTAssertNoDifference(result, vector.output)
                expectation.fulfill()
            }

            wait(for: [expectation], timeout: 1)
        }
    }

}

so I see the test name is test_resolve.
For it to just 'work out of the box' and be the same as everything else the test name should be resolve
If this is not possible or a massive anti pattern it is ok to keep it and we can change the runner to accept this

Unfortunately, this won't be possible. In order for a function to be considered a test case, it must have the test prefix.


The storage account name shows 'null' when updating CORS rules for the services under one SAS attached account

Storage Explorer Version: 1.17.0
Build Number: 20210120.8
Branch: main
Platform/OS: Windows 10/ CentOS 7.6.1810 (Core)/ MacOS Catalina
Architecture: ia32/x64
Regression From:  Not a regression
Steps to Reproduce

Select one storage account -> Attach it via SAS -> Expand the attached account.
Right click the Blob Containers node -> Click 'Configure CORS Setting...' -> Click 'Save'.
Observer the activities -> Check whether the account name shows well in the activity log.

Expected Experience
The account name shows well.
Actual Experience
The account name shows 'null'

Additional Context

This issue also reproduces for File Shares /Queues /Tables node.
This issue also reproduces under one SAS attached ADLS Gen2 account.

Verified on build 20210313.6.
Show inconsistent account names in the updating CORS activity log between the Queues and the Blob, File Share, Table services.