wluma: 4.5.1 → 4.6.0

Package Information

Package name: wluma
Latest released version: 4.6.0
Current version on the unstable channel: 4.5.1
Current version on the stable/release channel: 4.5.1

Maintainer Ping
@yshym @jmc-figueira @atemu
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.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.

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

Future reference for testing,
This version build was very resource intensive and Boiled my laptop up to 93°C,
running for almost 20 mins (was watching squid game 2)
So only test it in your free time..

Please squash the last two commits into one wluma: add Rishik-Y to maintainers or something along those lines

Please squash the last two commits into one wluma: add Rishik-Y to maintainers or something along those lines

ngl, this was my first time squashing a git commit.
took me 2 hour to figure it out..
Is it good now Mr @Atemu?

Wait goddamnit, sorry about it

Yesss!
Could you check now Mr @Atemu?

Almost, the convention is to have the component on it's own before the :
You should also remove the other commit titles of the commit message of the squashed commit.

Almost, the convention is to have the component on it's own before the :

Yep did that now!

You should also remove the other commit titles of the commit message of the squashed commit.

I was confused reading this at first,
but after some inspection i understood what you finally meant.
Could you please check again if i made any more mistakes?

The maintainer list commit title is missing the suffix of your name otherwise, that par looks good. I'll hopefully have a look at testing this soon.

Okay 👍
Thank you for guiding me with patience.


fix(types): MergePath merge blank paths correctly

This PR may fix the issue that PR #2347 tries to fix.
Even though the app includes app.route() with blank path '', it should infer the path in the client correctly:
// Server
const app = new Hono().basePath('/api/v1')
const routes = app.route(
  '/me',
  new Hono().route(
    '',
    new Hono().get('', async (c) => {
      return c.json({ name: 'hono' })
    })
  )
)const app = new Hono().basePath('/api/v1')
const routes = app.route(
  '/me',
  new Hono().route(
    '',
    new Hono().get('', async (c) => {
      return c.json({ name: 'hono' })
    })
  )
)

// Client

const client = hc<typeof routes>('http://localhost')
client.api.v1.me // <=== correct

But, in the current implementation, it can't infer correctly:

This PR will fix the issue by fixing the MergePath behavior.
Author should do the followings, if applicable

[x] Add tests
[x] Run tests
[x] yarn denoify to generate files for Deno

Merging now!


Not worwing with make install and autoreconf

Original issue 249 created by<EMAIL_ADDRESS>on 2014-08-15T22:16:55.000Z:
PCLinuxOS 32bit

cd leveldb-1.15.0
'[' 1 -eq 1 ']'
make install DESTDIR=/home/gg/src/rpm/BUILDROOT/leveldb-1.15.0-1.i386
make: *** No rule to make target 'install'.  Stop.
error: Bad exit status from /home/gg/src/tmp/rpm-tmp.9GF1rG (%install)

Ok I can try use autoreconf, but not working ...
autoreconf -ivf
./configure
make %{?_smp_mflags}

cd leveldb-1.15.0
'[' 1 -eq 1 ']'
'[' 1 -eq 1 ']'
autoreconf -ivf
autoreconf: 'configure.ac' or 'configure.in' is required
error: Bad exit status from /home/gg/src/tmp/rpm-tmp.Oa2vFm (%build)

I see OpenSuse use debian path, I will try

Hi @willnorris:
Thanks for submitting this issue. Our goal is to keep both the source/build/docs as minimal as possible. Installation is platform dependent so will probably not be supported by our Makefile.

huh?  why did I get mentioned on this?

Wow - I have no idea. Something wrong with auto-completion (user error?). Sorry Will.


BUG: Fix interactive update of mapping

On main:
https://user-images.githubusercontent.com/2365790/109843507-231c0e80-7c19-11eb-9880-7acfd3686ddc.mp4
On this PR:
https://user-images.githubusercontent.com/2365790/109843519-2616ff00-7c19-11eb-97e7-3fab9588e83d.mp4
I don't know a good wait to test this on CIs unfortunately since it has to do with actual rendering.

we could check that layered_mesh._rng == brain._cmap_range?

we could check that layered_mesh._rng == brain._cmap_range?

Great idea, pushed. Will merge and backport once CIs come back happy

Okay I fought through a bit of a nightmare with control flow with LUT updates. Now:

by use of a context manager we hopefully avoid one param change causing multiple .update calls
make it so programmatic brain.update_lut(...) calls are reflected in the widgets
fix rng[0] == rng[1] not displaying properly -- now it creates what is essentially a binary mask at rng[0] which is what I'd expect

This also makes interaction smoother for me, which is nice. Ready for review/merge from my end @GuillaumeFavelier, hopefully CIs come back happy with this one...

Actually I think I realized a simpler pattern, will implement it tomorrow

Okay @GuillaumeFavelier should be good to go here

Thanks @larsoner !


dart2js unfork performance regression

This issue track dart2js performance regression.
Unfork performance should meet performance metric

Spec mode aggregate: -8.76%
Production mode aggregate: -4.62%
Concerns:

extra casts in SplayTree
Future / Stream slower by 50% (undiagnosed)

Any updates here?

@leafpetersen has a CL that addresses most of the SplayTree regression.

The CL that ported dart:async is here .  I see some new casts in there, and some uses of late (which may not be well-optimized yet).  Some of the new casts are of the T? -> T variety that we can rewrite to a different pattern.  Others can probably be turned back into implicit casts if needed by casting through dynamic.  It would be good to have something slightly more targeted - do we have benchmarks for Future/Stream that we're targetting.

@leafpetersen AsyncStressTest is a group of benchmarks that are currently ~2x slower. They tend to be noisy but the run-by-run bar graphs can be used to judge that.

Spec mode aggregate: -8.55%
Production mode aggregate: -4.43%
Currently investigating if the use of more lazy initializers is responsible for some of the regressions.

CssLib benchmark regression understood. Working on a fix.

Changes for CssLib landed. No numbers yet.

I landed the SplayTree CL which restored parity with the pre-nnbd sdk for the relevant benchmark.

I've looked at the AsyncStressTest issues, I think they'll be easy to resolve.

Spec mode aggregate: -8.21%
Production mode aggregate: -4.07%
I have a CL out that makes some spec mode improvements.

What is the minimum acceptable number we are targeting?

Spec mode aggregate:  -3.656%
Production mode aggregate: -3.142%

No update

I have a CL for the AsyncStressTest regressions here that will go out tonight.  Initial golem results here show the suite in aggregate at 1% faster than the non-nnbd SDK, but with a spread of about -15% to +17% .

With the AsyncStressTest having a fix landed, and the spec mode and production mode cases within a few percent (~3), is this no longer a blocker for unforking? Or are there other severe regressions?

Not quite done. There are some benchmarks outside the AsyncStressTest that are not yet acceptable. I have a CL for one issue and then we need to reassess.

OK, once we reassess, can we please provide an update here with a specific list of issues?

There is one remaining issue which is esoteric enough to be non-blocking.
Partial results which may improve marginally:
spec mode aggregate: -4.27%
prod mode aggregate: -0.67%


runtime: remove unused source (NFCI)

StaticBinaryELF.cpp was listed as an optional source but then unused
by any build target.  As a result, it escaped detection that the file
was no longer in use.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test

@swift-ci please test and merge

@swift-ci please test

@swift-ci please test and merge

Build failed
Swift Test OS X Platform
Git Sha - 8e9cf7cabfeb5b554fcd4608ae7a8dfe6b07006c

Build failed
Swift Test Linux Platform
Git Sha - 8e9cf7cabfeb5b554fcd4608ae7a8dfe6b07006c


per-user platform limit of concurrent syncs

Closes #4395

@juanignaciosl CR please

After the comment, LGTM.

Frontend tests were OK :+1: (details)


Fix readme typo

It should be loopback instead of lookback in README.md, I think it is a typo.

Merged, thanks!


Valid non-object JSON features cause panics

Cc @simone-coelho .
This bug is in relation to Optimizely support ticket #1001007469 .
The bug described in this ticket is in these locations:
https://github.com/optimizely/go-sdk/blob/master/pkg/client/client.go#L935
https://github.com/optimizely/go-sdk/blob/master/pkg/client/client.go#L500
The code always assumes that valid JSON will be returned as a map. It does not check first whether the JSON is a map, array, or scalar value. However, the optimizely web interface allows any valid json value.
We put in a JSON array into a feature in optimizely. This was passed to the optimizely agent, which in turn passed it to this go-sdk. The sdk assumed that because the value was JSON it was necessarily a map and tried to convert it to a map in the linked line of code. It wasn't a map in our case, but an array. This causes a panic, which causes the optimizely agent to sever the TCP connection with the client without so much as a 500 error.
The code herein linked should be changed so that it checks to make sure the JSON is indeed a map before it attempts conversion and issue a polite error if it isn't as expected so that the optimizely agent can give back a polite http code error in turn. Or, change the code to allow for arrays, as is allowed by the optimizely UI.
We appreciate your time.

Hi @djhaskin987,
Thanks for opening this issue. I'll put this in for review.

Thanks @mikechu-optimizely . @simone-coelho said the behavior should be that it should also accept JSON arrays. He said he'd put in a Jira ticket in for it so I'd ask him about that :)

I've coordinated with and taken Simone's finding, opening an active Jira issue.

Hi @djhaskin987,
We are addressing the Go panic directly in the SDK during a future release.
The team responsible for the Web UI and API are ensuring that both of these avenues only accept JSON object types.
Do you have any blockers for this particular GH Issue now that you've configured to use a JSON object?
cc @simone-coelho

No blockers, thanks!


[stable/fluentd] Support custom load balancer IP

Signed-off-by: Austin Orth<EMAIL_ADDRESS>Motivation
We want to be able to set a custom load balancer IP address when the service type is LoadBalancer.
What I Did

Added handling to service template for setting a custom load balancer IP address when service type is LoadBalancer.
Added documentation to readme and default values file.

What this PR does / why we need it:
Which issue this PR fixes

fixes #18495

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

CC: @rendhalver @Miouge1 @hectorj2f

Whoops, did not mean to close this!

My bad again. This is my first time working with forks in a while, and I accidentally deleted my changes. I repeated them with a fresh commit just now, so should be good to go :sweat_smile:

/ok-to-test

/retest


Add missing parameter to collector

@agrare, sorry missed this in the last PR.

Currently seeing this in CI:
/opt/amazon-collector/lib/topological_inventory/amazon/collector.rb:23:in `initialize': wrong number of arguments (given 3, expected 4) (ArgumentError)
from bin/amazon-collector:37:in `new'
from bin/amazon-collector:37:in `<main>'


Write a unit test for "Categories / Edit a category" endpoint

The puzzle 130-c3cfd35c from #130 has to be resolved:
https://github.com/proshin-roman/finapi-java-client/blob/c6cb7175322290db42fc58ed26ba56018b22ed7e/src/main/java/org/proshin/finapi/category/FpCategory.java#L74-L74
The puzzle was created by Roman Proshin on 16-Feb-19.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 130-c3cfd35c has disappeared from the source code, that's why I closed this issue.

@0pdd the puzzle #143 is still not solved.

@0pdd the only puzzle #143 is solved here.


Enable code coverage in release pipeline with 'dotnet vstest'

Description

Add target to copy TraceDataCollector dependencies to publish directory.

Related issue
https://github.com/Microsoft/vstest/issues/981

@dotnet-bot Please test this.

@dotnet-bot test this please

@dotnet-bot test please


virtualenv 20.0.1 breaks zulip installer

When virtualenv 20.0.1 is installed on a system, the zulip installer fails to complete due to an error in scripts/lib/setup_path_on_import.py:
Successfully installed Yarn 1.19.1!
+ mkdir -p /etc/zulip
+ cat
+ '[' -n '' ']'
+ dpkg-query --showformat '${Status}\n' -W rabbitmq-server
+ grep -vq ' not-installed$'
+ cat
+ '[' -n '' ']'
+ case ",$PUPPET_CLASSES," in
+ '[' -z '' ']'
+ cp -a /tmp/tmp.yliyQLjARE/zulip-server-2.1.2/zproject/prod_settings_template.py /etc/zulip/settings.py
+ '[' -n zulip ']'
+ sed -i 's/^EXTERNAL_HOST =.*/EXTERNAL_HOST = '\''zulip'\''/' /etc/zulip/settings.py
+ '[' -n<EMAIL_ADDRESS>']'
+ sed -i 's/^ZULIP_ADMINISTRATOR =.*/ZULIP_ADMINISTRATOR =<EMAIL_ADDRESS>/etc/zulip/settings.py
+ ln -nsf /etc/zulip/settings.py /tmp/tmp.yliyQLjARE/zulip-server-2.1.2/zproject/prod_settings.py
+ /tmp/tmp.yliyQLjARE/zulip-server-2.1.2/scripts/setup/generate_secrets.py --production
Traceback (most recent call last):
  File "/tmp/tmp.yliyQLjARE/zulip-server-2.1.2/scripts/setup/generate_secrets.py", line 11, in <module>
    import scripts.lib.setup_path_on_import
  File "/tmp/tmp.yliyQLjARE/zulip-server-2.1.2/scripts/lib/setup_path_on_import.py", line 14, in <module>
    if not os.path.exists(activate_locals["site_packages"]):
KeyError: 'site_packages'

Zulip installation failed (exit code 1)!

The install process is designed to be idempotent, so you can retry after resolving whatever issue caused the failure (there should be a traceback above). A log of this installation is available in /var/log/zulip/install.log
root@zulip-2001:/tmp/tmp.yliyQLjARE/zulip-server-2.1.2#

Something about how the virtualenv at /srv/zulip-venv-cache/$hash is being created is causing issues (note that I was able to recreate this with Zulip 2.0.7 as well).
Steps to recreate
I provisioned an Ubuntu 18.04 container with LXD and performed the following:

pip3 install virtualenv==20.0.1, then followed the installation guide:

cd $(mktemp -d); wget https://www.zulip.org/dist/releases/zulip-server-latest.tar.gz; tar -xf zulip-server-latest.tar.gz

zulip-server-*/scripts/setup/install --self-signed-cert<EMAIL_ADDRESS>--hostname=zulip

When version 20.0.1 is substituted with 15.1.0 or 16.7.10 on an identical container, the install process finishes without any errors. If virtualenv 20.0.1 isn't supported, I would think a check in the installer to ensure the correct version (or a note on the installation page) would be useful, since I imagine it would be common for people to want the latest version of virtualenv installed on systems.
I can provide more logs if needed. Thanks!

Certainly sounds like a bug.
@andersk can you look into this?

@zulipbot claim

@timabbott @andersk  This is so because in virtualenv>20.0.0 activate_this.py is modified and it does not use the variable 'site_package' thereby giving key error. I guess we have to use 'path' instead of 'site_package' or any other method to verify that the virtual environment is set up or not.


Paypal settings page runs into timeout - Module 5.4.6 - Prestashop v. <IP_ADDRESS>

The module settings page will not load and instead run into a timeout after the update to module version 5.4.6.
Any suggestions here?

Hello @icemansparks
Witch version of the module have you used before update ? Do you have any error to share ?
Before update, have you completely removed the old version of module from Prestashop when you uninstalled it? (to to that, there is a checkbox to delete module folder when you uninstall). If not, can you try it and tell us if that fix your issue ?
Best regards,

Hi @JeromeG202
the module version we used before the update was v5.4.5 and we used the update functionality inside prestashops module manager without deinstalling the module.
i prepared a backup system for testing with the previous version - after doing the same steps to update the module from the module manager page, the module settings page can be accessed with a load time of over 1.5 minutes. (but at least it is not a timeout).
There seems to be a large initial waiting time on the controller itself before anything else will be loaded:
index.php?controller=AdminPayPalSetup&token=xxx
apart from that i cannot see any real "error" message

.

Hi @icemansparks,
I recommend you to contact our support team with all the details and information you can provide. Our dev team will help you with your issue.
Best regards,

Hi @JeromeG202 ,
perhaps you would like to know that the link to a support team provided no longer enables to send them an email, therefore it seems here it is the only option to let them know about issues. Unfortunately it looks like they do not visit these pages too often judging by the other ticket of mine.

Hello @mrabsinthe
We are sorry to hear that. It seams the issue war on Prestashop Addons, not only on the PayPal module but for all the others modules today. Apparently it works, on my side it's ok, you can try it again.
"Unfortunately it looks like they do not visit these pages too often judging by the other ticket of mine."
Have you created a ticket to our support team ? Could you tell me when ? I will see with the support team.
Thank you

Still doesn't work for me I'm afraid.

Same problem here.... @mrabsinthe have you found a solution?

It could be an external call, on itself to check the TLS version or on paypal API.
Anyone could send me a message on PrestaShop and say you are in contact with @clotairer on github issue #114. We need an access to reproduce.
Thank you.

Hi and thank you for your reply. I've done as suggested but no change.
I noticed a colleague of mine working on the same site from his pc doesn't have this issue, so if must be caused by something local, a cookie maybe?

Did you try to remove all your cookie in your domain ?
In the backoffice, the module doesn't change the cookie.

Yes I already tried that...

Any updates about this issue. We cannot reproduce on our side…

Sorry for the delayed answer - we just stopped trying to open the settings page for a while.
We now use shop version <IP_ADDRESS> and module version 5.6.0 and are at least no longer running into a timeout, but still the page takes about 18 seconds to load...

Issue resolved, thanks.
Il giorno mer 27 apr 2022 alle ore 14:17 Dennis @.***>
ha scritto:

Sorry for the delayed answer - we just stopped trying to open the settings
page for a while.
We now use shop version <IP_ADDRESS> and module version 5.6.0 and are at least
no longer running into a timeout, but still the page takes about 18 seconds
to load...
[image: ScreenShot 2022-04-27_14 14 @.***
https://user-images.githubusercontent.com/11578975/165516070-c76725c9-4871-4a17-90eb-3623de9c6eff.png
—
Reply to this email directly, view it on GitHub
https://github.com/202-ecommerce/paypal/issues/114#issuecomment-1110930429,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABWDSTWXQTASJIWE3DYNNSTVHEV7LANCNFSM5HQXCBFQ
.
You are receiving this because you commented.Message ID:
@.***>


A non-informative report is generated when running a *.testcafe fixture file using CLI

What is your Test Scenario?
Need to find out which step of the recorded (*.testcafe)  test fails.
What is the Current behavior?
The report doesn't specify the failed step.
What is the Expected behavior?
It should display the number and/or a description of the failed step.
What is your web application and your TestCafe test code?
recorded-examples.zip

Your complete test report:

 Running tests in:
 - Chrome 91.0.4472.164 / Windows 10

 A set of examples that illustrate how to use TestCafe API
 × 1

   1) AssertionError: expected true to be falsy

      Browser: Chrome 91.0.4472.164 / Windows 10

      10

Steps to Reproduce:

Launch npx testcafe chrome recorded-examples.testcafe

Your Environment details:

testcafe version:                   1.15.0
node.js version:                    16.3.0
command-line arguments:  npx testcafe chrome recorded-examples.testcafe
browser name and version: Chrome 91
platform and version:          Windows 10

@Dmitry-Ostashev I'm using testcafe docker image to execute my tests, and I'm still experiencing this issue
1) AssertionError: expected false to be truthy
--
18 |
19 | Browser: Chrome 101.0.4951.64 / Linux 0.0
20 |
21 | 23

This is the command I'm using
/opt/testcafe/docker/testcafe-docker.sh -c 3 chromium -q --skip-js-errors --assertion-timeout 60000 --selector-timeout 60000 TestsRepo/*.testcafe
Appreciate any help to get this solved?

@sashikamw Thank you for your comment. TestCafe does not show full error information for a failed assertion step. I created a separate issue for this case: https://github.com/DevExpress/testcafe/issues/7089. Please track it to be notified when it is fixed.


Recognize "tr strt tr end"

Perf manages to output that kind when someone accidentally types go run ./demo/demo.go instead of ./demo/demo.go. The trace is horribly
broken, but it feels more user-friendly here to show the horribly
broken trace than to crash.
Fixes #80

Same


Vertical scroll within a panel does not work

Vertical scroll does not work within the different components of the app, making it impossible to select some references when the list is too long and leading to some strange behaviour when the text in the editor is too long.

This was fixed by #40


Refactoring of POSIX netif code, mostly to accommodate BSDs

This code (likely a first attempt, as I'm sure there's some stuff in here that
folks will want to change) does the following:

provides an implementation to manage networking notices from a PF_ROUTE socket,
instead of (the Linux-specific) PF_NETLINK

breaks out some of the platform-specific mechanisms for configuring a tunnel
device (Linux, mac OS, and NetBSD are all different in some ways)

provides handling of I/O to the tun drivers on BSDs (where there's a 4-byte
header prepended to identify the IP version)

adds some debugging info and more deliberate error handling (I suspect
there are some more OpenThread-friendly ways to do some of the
debugging, but I didn't try to figure them out)

I've used most of this code for several months on mac OS and NetBSD, and I
wanted to get a version of it shared for review.  I'd love to see it
merged in so that I don't have to maintain it completely by myself (and perhaps
others will want to use it on those platforms), but I suspect it'll need
some changes first.

@rob-the-dude I think multicast is a requirement for Thread. Do we need to support Apple utun if multicast is not supported?
I find it pretty straightforward to install tuntap through homebrew:
brew cask install tuntap

Then allow the extension according to the formula of tuntap.

I just played on macOS 10.15.3.
➜  openthread git:(pr/4664) ✗ sudo ./output/posix/x86_64-apple-darwin/bin/ot-cli output/x86_64-apple-darwin/bin/ot-rcp 1
> panid 0xface
Done
> ifconfig up
IPV6_JOIN_GROUP failure (22)
Done
> 	thread: ADD [M] ff03:0000:0000:0000:0000:0000:0000:0001 failure (7)
	thread: ADD [M] ff03:0000:0000:0000:0000:0000:0000:00fc failure (7)
	thread:         fe80:0000:0000:0000:aede:48ff:fe00:1122 (remove stack-added link-local)
	thread: ADD [M] ff02:0000:0000:0000:0000:0001:ff00:1122
	thread: ADD [M] ff02:0000:0000:0000:0000:0000:0000:0001 failure (7)
	thread: ADD [M] ff02:0000:0000:0000:0000:0002:ff97:242f
	thread: ADD [M] ff01:0013:0000:0000:0000:0000:0000:0001 failure (3)
	thread: ADD [U] fe80:0000:0000:0000:d4cb:52b7:c36e:74db (already subscribed, ignored)
	thread: ADD [M] ff02:0000:0000:0000:0000:0001:ff6e:74db failure (3)
	thread: DEL [U] fe80:0000:0000:0000:aede:48ff:fe00:1122 (not found, ignored)
	thread: DEL [M] ff02:0000:0000:0000:0000:0001:ff00:1122

>
>
>
>
> thread start
Done
> 	thread: ADD [U] fdde:ad00:beef:0000:85c7:f4f0:0459:6a43 (already subscribed, ignored)
	thread: ADD [M] ff02:0000:0000:0000:0000:0001:ff59:6a43
	thread: ADD [M] ff32:0000:fdde:ad00:beef:0000:0000:0001 failure (3)
	thread: ADD [M] ff33:0040:fdde:ad00:beef:0000:0000:0001 (already subscribed, ignored)

>
>
>
>
> 	thread: ADD [U] fdde:ad00:beef:0000:0000:00ff:fe00:f400 (already subscribed, ignored)
	thread: ADD [M] ff02:0000:0000:0000:0000:0001:ff00:f400 failure (3)
	thread: ADD [U] fdde:ad00:beef:0000:0000:00ff:fe00:fc00 (already subscribed, ignored)
	thread: ADD [M] ff02:0000:0000:0000:0000:0001:ff00:fc00 failure (3)
	thread: ADD [M] ff02:0000:0000:0000:0000:0000:0000:0002 failure (7)
	thread: ADD [M] ff03:0000:0000:0000:0000:0000:0000:0002 failure (7)

>
>
>
> ipaddr
fdde:ad00:beef:0:0:ff:fe00:fc00
fdde:ad00:beef:0:0:ff:fe00:f400
fdde:ad00:beef:0:85c7:f4f0:459:6a43
fe80:0:0:0:d4cb:52b7:c36e:74db
Done
> ipmaddr
ff02:0:0:0:0:1:ff59:6a43
ff33:40:fdde:ad00:beef:0:0:1
ff32:40:fdde:ad00:beef:0:0:1
ff02:0:0:0:0:2:ff97:242f
ff02:0:0:0:0:0:0:2
ff03:0:0:0:0:0:0:2
ff02:0:0:0:0:0:0:1
ff03:0:0:0:0:0:0:1
ff03:0:0:0:0:0:0:fc
Done

There are some failures, I'm not sure they matters. Besides, I hope to verify if multicast addresses are subscribed, and I tried netstat -r -f inet6, but I didn't find addresses listed in OpenThread's ipmaddr. I don't know whether I'm using the correct command to check multicast subscriptions.

@rob-the-dude I think multicast is a requirement for Thread. Do we need to support Apple utun if multicast is not supported?

Fair point.  I certainly don't care to support Apple utun until it supports multicast.  Would you prefer me to remove it?

I find it pretty straightforward to install tuntap through homebrew:
brew cask install tuntap

Then allow the extension according to the formula of tuntap.

It's nice to hear that works.  I don't use brew on my system(s).  I use very few command line tools or system-wide additions that I cannot build from source.
Third-party kernel drivers (like tun-tap) are on the decline on mac OS.  At WWDC last year, they introduced many new ways of doing USB and networking devices outside the kernel -- but for the moment, tun-tap still works.  I don't know if that will remain true after the next OS release or not, but if it isn't, then I'm hopeful that either (a) utun will gain support for multicast, or (b) there'll be a new way to do what tun-tap does.

There are some failures, I'm not sure they matters. Besides, I hope to verify if multicast addresses are subscribed, and I tried netstat -r -f inet6, but I didn't find addresses listed in OpenThread's ipmaddr. I don't know whether I'm using the correct command to check multicast subscriptions.

If you've got a sequence of commands that form a test, I'd be happy to perform them and examine the output on both Linux and mac OS.  During my development, I found that certain address manipulation was also problematic on Linux, but the errors were ignored.  As I point out, I added additional logging -- partially in the hopes that the Linux code would ALSO stop generating errors (not by adding the code, but because the errors now being logged would be corrected by others using the code).  But it's been awhile since I tried debugging the code on Linux.
Again, if you've got a quick sanity test, I'd be happy to run it on both platforms.  Your comment mentions this:
sudo ./output/posix/x86_64-apple-darwin/bin/ot-cli output/x86_64-apple-darwin/bin/ot-rcp 1

panid 0xface
ifconfig up
thread start
ipaddr
ipmaddr

Is that enough?  If so, I can run those commands on an existing Linux build, a new Linux build, and a mac OS build and report back on any differences (I might add the output of "netstat -n -r -f inet6", but that seems to show route information instead of subscribed multicast addresses -- though in practicality, I think I can see how they might end up being the same).

Did some deeper testing and debugging into the error messages.  Would like feedback on a couple cases from @bukepo and @jwhui.
This error message:
 thread: ADD [M] ff02:0000:0000:0000:0000:0001:ff00:f400 failure (3)

Is happening because otIp6SubscribeMulticastAddress is returning OT_ERROR_NO_BUFS.   That's because the default number of external multicast addresses is small (2), and a mac OS system generally has a handful of system processes that want to bind to multicast addresses when they show up in the system and get configured for IFF_UP (i.e., mDNSResponder is one of them).  On Linux, this more or less gets "eaten" (ignored) by the "SuccessOrExit" call inside "processNetIfAddrEvent".  I'm certainly unhappy with that outcome -- silently failing to bind to a multicast address would make system processes fail with practically no hint as to what's wrong.  I'd be happy to special case the handling of  OT_ERROR_NO_BUFS with a particular log message ("no space for address") and a comment in the code that the developer might need to increase OPENTHREAD_CONFIG_IP6_MAX_EXT_MCAST_ADDRS.  But in reality, such a notice might be better placed in "Netif::SubscribeExternalMulticast".
Additionally, I'd ask if, on mac OS specifically, we should increase the default value of OPENTHREAD_CONFIG_IP6_MAX_EXT_MCAST_ADDRS?

Similar to my last comment, I'd like input from @bukepo and @jwhui -- these error messages:
thread: ADD [M] ff02:0000:0000:0000:0000:0000:0000:0002 failure (7)
thread: ADD [M] ff03:0000:0000:0000:0000:0000:0000:0002 failure (7)

Are happening because otIp6SubscribeMulticastAddress (technically, Netif::SubscribeExternalMulticast) recognizes them as one of the "fixed" addresses, and returns OT_ERROR_INVALID_ARGS.
I'm not a fan of this error code from this particular function, mainly because those "fixed" addresses aren't exposed externally -- they're defined in the Netif implementation file and not available elsewhere.  So I can't say, "oh, I got back OT_ERROR_INVALID_ARGS -- did I pass in one of the special addresses?" (or for that matter, detect it's a magic address and not call the function anyway), as opposed to a truly invalid argument (usually, I think of invalid arguments as me passing in something that's a bogus file descriptor, a bogus pointer, or, in this case, something that wasn't actually a valid multicast address).  Instead, I have to know that OT_ERROR_INVALID_ARGS means something special to this particular method, and know that I might sometimes get this error, and it doesn't mean that the address is bad -- it means that it's a special address.  (Indeed, from a quick perusal of the code, it looks like I could totally pass a bogus multicast address (say, a unicast address) to otIp6SubscribeMulticastAddress, and -- as long as it wasn't one of the special ones -- it wouldn't complain at all.  (That seems like a bug to me.)
In any event, I'd probably prefer that otIp6SubscribeMulticastAddress return OT_ERROR_ALREADY for the "special" addresses -- at least I'd know that, "hey, this address is already in our list of multicast address we'll receive packets for" and know that I'm OK.  If that's not going to happen, then I'd like the "special" addresses exposed (or give me a helper function to know it's one of them).  Otherwise, I really have no way to protecting myself from OT_ERROR_INVALID_ARGS actually meaning what I think it might mean, should future changes to the underlying code ever happen.
Finally, (I think) the reason this happens on mac OS and not Linux is that it seems like Linux may filter out PF_NETLINK notifications for changes that our process makes to the device (at least it seems that way for these addresses -- I don't see a PF_NETLINK notification for them, even though they do get added).  The mac OS code doesn't filter by PID (I could try that, but I'm not certain it's correct behavior).  In any event, the error message in this case is telling us something is happening that's more of a programmer error than an actual system misbehavior.  The particular multicast address that you're attempting to add to the interface is indeed already in the list (albeit a special "wouldn't you like to know" list).

Similar to my last comment, I'd like input from @bukepo and @jwhui -- these error messages:
thread: ADD [M] ff02:0000:0000:0000:0000:0000:0000:0002 failure (7)
thread: ADD [M] ff03:0000:0000:0000:0000:0000:0000:0002 failure (7)

Are happening because otIp6SubscribeMulticastAddress (technically, Netif::SubscribeExternalMulticast) recognizes them as one of the "fixed" addresses, and returns OT_ERROR_INVALID_ARGS.
I'm not a fan of this error code from this particular function, mainly because those "fixed" addresses aren't exposed externally -- they're defined in the Netif implementation file and not available elsewhere. So I can't say, "oh, I got back OT_ERROR_INVALID_ARGS -- did I pass in one of the special addresses?" (or for that matter, detect it's a magic address and not call the function anyway), as opposed to a truly invalid argument (usually, I think of invalid arguments as me passing in something that's a bogus file descriptor, a bogus pointer, or, in this case, something that wasn't actually a valid multicast address). Instead, I have to know that OT_ERROR_INVALID_ARGS means something special to this particular method, and know that I might sometimes get this error, and it doesn't mean that the address is bad -- it means that it's a special address. (Indeed, from a quick perusal of the code, it looks like I could totally pass a bogus multicast address (say, a unicast address) to otIp6SubscribeMulticastAddress, and -- as long as it wasn't one of the special ones -- it wouldn't complain at all. (That seems like a bug to me.)
In any event, I'd probably prefer that otIp6SubscribeMulticastAddress return OT_ERROR_ALREADY for the "special" addresses -- at least I'd know that, "hey, this address is already in our list of multicast address we'll receive packets for" and know that I'm OK. If that's not going to happen, then I'd like the "special" addresses exposed (or give me a helper function to know it's one of them). Otherwise, I really have no way to protecting myself from OT_ERROR_INVALID_ARGS actually meaning what I think it might mean, should future changes to the underlying code ever happen.
Finally, (I think) the reason this happens on mac OS and not Linux is that it seems like Linux may filter out PF_NETLINK notifications for changes that our process makes to the device (at least it seems that way for these addresses -- I don't see a PF_NETLINK notification for them, even though they do get added). The mac OS code doesn't filter by PID (I could try that, but I'm not certain it's correct behavior). In any event, the error message in this case is telling us something is happening that's more of a programmer error than an actual system misbehavior. The particular multicast address that you're attempting to add to the interface is indeed already in the list (albeit a special "wouldn't you like to know" list).

Hi @rob-the-dude, I agree that we should return OT_ERROR_ALREADY when subscribing fixed multicast addresses. Thank you for the detailed analysis! Would you like to submit a PR for this issue, or just piggyback on this PR?

@rob-the-dude good to see you here  :) .... Adding some thoughts below.

Returning OT_ERROR_ALREADY for the special/internal multicast addresses may indicate that the address is already available on netif which may be true for "link-local all nodes" but is not necessarily the case for some of the other addresses like "link-local all routers", etc. (which are only added by OT when device is FTD and a router/REED).
On unicast addresses, otIp6AddUnicastAddress() also restricts user from adding/changing some internal addresses, for example, user cannot add any link-local IPv6 address (I think the error is same INVALID_ARGS here).
On wpantund such addresses (for both unicast and multicast) are filtered and not pushed down to NCP.  I agree it requires the knowledge of code and what addresses are considered internal. I would suggest we add documentation of what "internal addresses" are in these OT public APIs.

About running out of unicast/multicast address space on OT core, that can lead to some tricky situations in wpantund as well. User can add an unicast IPv6 address on "wpan0" interface and it would seemingly succeed but later on when wpantund gets the netlink msg about the newly added address and tries to push the same address to NCP, it may get an error NO_BUFS. What to do then?

Do we just log it as an error and let it be? (address would be on "wpan0" but not on NCP side).
Do we remove the address from "wpan0" (how to report to user that adding the address failed?)
Not let user add address on "wpan0" interface and require user to always go through driver and a wpantund command? (not very user-friendly).
The current approach in wpantund (which to be honest I am not a fan of, but I agree is the safest and most noticeable) is to assert/die in wpantund when we cannot sync addresses between host and NCP. This practically causes continuous wpantund restarts and brings down the wpan network and makes it unusable (with the hope that user would then notice).

Thoughts?

@rob-the-dude good to see you here :)

Nice to be here.

Returning OT_ERROR_ALREADY for the special/internal multicast addresses may indicate that the address is already available on netif which may be true for "link-local all nodes" but is not necessarily the case for some of the other addresses like "link-local all routers", etc. (which are only added by OT when device is FTD and a router/REED).

Actually, perhaps this is a good argument for returning OT_ERROR_ALREADY ONLY when those addresses are bound, and returning OT_ERROR_INVALID_ARGS when they are not but still prohibited.
In actual correct practice, no one is going to bind to those addresses -- the only reason the mac OS POSIX daemon is seeing the notification is because OpenThread itself did the bind, and the PF_ROUTE socket told it about it -- in which case, returning OT_ERROR_ALREADY would be "correct".  If you're not a router/REED, then the POSIX daemon won't bind to those address, and if someone else tried to do so, then returning OT_ERROR_INVALID_ARGS seems quite valid -- this address argument is "invalid", at least in the current state.

On unicast addresses, otIp6AddUnicastAddress() also restricts user from adding/changing some internal addresses, for example, user cannot add any link-local IPv6 address (I think the error is same INVALID_ARGS here).

I'd argue for the same behavior -- if I pass down the SAME link-local address that is bound, then the error ought to be OT_ERROR_ALREADY, and otherwise OT_ERROR_INVALID_ARGS is OK.  But at least in this case, there's a simple macro to check if something's a link-local address, and it's easy to document that you can't bind to link-local addresses.  The special multicast addresses require a deeper knowledge of how Thread itself works -- they're not really special in any other context.

On wpantund such addresses (for both unicast and multicast) are filtered and not pushed down to NCP.  I agree it requires the knowledge of code and what addresses are considered internal. I would suggest we add documentation of what "internal addresses" are in these OT public APIs.

Ugh <...shiver...>

About running out of unicast/multicast address space on OT core, that can lead to some tricky situations in wpantund as well. User can add a unicast IPv6 address on "wpan0" interface and it would seemingly succeed but later on when wpantund gets the netlink msg about the newly added address and tries to push the same address to NCP, it may get an error NO_BUFS. What to do then?

Do we just log it as an error and let it be? (address would be on "wpan0" but not on NCP side).
Do we remove the address from "wpan0" (how to report to user that adding the address failed?)
Not let user add address on "wpan0" interface and require user to always go through driver and a wpantund command? (not very user-friendly).

Seems like that would also break a lot of IP software that uses ifreq to do such things.

The current approach in wpantund (which to be honest I am not a fan of, but I agree is the safest and most noticeable) is to assert/die in wpantund when we cannot sync addresses between host and NCP. This practically causes continuous wpantund restarts and brings down the wpan network and makes it unusable (with the hope that user would then notice).

Thoughts?

I can't say that I have anything better, other than documenting -- perhaps in the log message, but at least in the code -- that a common reason for getting OT_ERROR_NO_BUFS is the build-time configuration parameter for max address count.  NO_BUFS is a generic name, and the first time you get that, you're like, "oh, crap, how do I increase the number of buffers" and you start thinking about a problem you probably don't have.  Having a log message that specifically says, "No room for additional addresses" and a comment that specifically says "if you are hitting OT_ERROR_NO_BUFS in this situation, it may mean that your deployment needs to increase the maximum (unicast/multicast) address constants OPENTHREAD_CONFIG_IP6_MAX_EXT_UCAST_ADDRS/OPENTHREAD_CONFIG_IP6_MAX_EXT_MCAST_ADDRS".

Actually, perhaps this is a good argument for returning OT_ERROR_ALREADY ONLY when those addresses are bound, and returning OT_ERROR_INVALID_ARGS when they are not but still prohibited.
In actual correct practice, no one is going to bind to those addresses -- the only reason the mac OS POSIX daemon is seeing the notification is because OpenThread itself did the bind, and the PF_ROUTE socket told it about it -- in which case, returning OT_ERROR_ALREADY would be "correct". If you're not a router/REED, then the POSIX daemon won't bind to those address, and if someone else tried to do so, then returning OT_ERROR_INVALID_ARGS seems quite valid -- this address argument is "invalid", at least in the current state.

Makes sense to me.

I can't say that I have anything better, other than documenting -- perhaps in the log message, but at least in the code -- that a common reason for getting OT_ERROR_NO_BUFS is the build-time configuration parameter for max address count. NO_BUFS is a generic name, and the first time you get that, you're like, "oh, crap, how do I increase the number of buffers" and you start thinking about a problem you probably don't have. Having a log message that specifically says, "No room for additional addresses" and a comment that specifically says "if you are hitting OT_ERROR_NO_BUFS in this situation, it may mean that your deployment needs to increase the maximum (unicast/multicast) address constants OPENTHREAD_CONFIG_IP6_MAX_EXT_UCAST_ADDRS/OPENTHREAD_CONFIG_IP6_MAX_EXT_MCAST_ADDRS".

Agree with documentation and a clear log message at a minimum. The API documentation does have the information, but maybe we could explicitly mention OPENTHREAD_CONFIG_IP6_MAX_EXT_MCAST_ADDRS in the OT_ERROR_NO_BUFS return value documentation.
https://github.com/openthread/openthread/blob/bf1cf97b0ffbf77d52bc8c9346e3280f5bbaf845/include/openthread/ip6.h#L184-L192

Actually, perhaps this is a good argument for returning OT_ERROR_ALREADY ONLY when those addresses are bound, and returning OT_ERROR_INVALID_ARGS when they are not but still prohibited.
In actual correct practice, no one is going to bind to those addresses -- the only reason the mac OS POSIX daemon is seeing the notification is because OpenThread itself did the bind, and the PF_ROUTE socket told it about it -- in which case, returning OT_ERROR_ALREADY would be "correct". If you're not a router/REED, then the POSIX daemon won't bind to those address, and if someone else tried to do so, then returning OT_ERROR_INVALID_ARGS seems quite valid -- this address argument is "invalid", at least in the current state.

Makes sense to me.

Should I file an issue against otIp6SubscribeMulticastAddress/Netif::SubscribeExternalMulticast to implement exactly that behavior (i.e., returning OT_ERROR_ALREADY when bound and OT_ERROR_INVALID_ARGS otherwise)?
I MIGHT be able to provide a patch, but I'm a little nervous about it -- I am not deeply familiar with when those addresses are actually bound and when they aren't.  Right now, the code checks against them in basically a static list -- I'll need to figure out when that list is "active" and when it isn't in order to implement the change.  Regardless, I think that's a separate PR.
BTW, I'm leaning towards withdrawing this PR until after #4687 is done -- and probably until after the correct behavior from otIp6SubscribeMulticastAddress is also implemented.

See https://github.com/openthread/openthread/pull/4693 for the multicast subscribe return value isse.

See #4693 for the multicast subscribe return value issue.

Thanks; tried them out locally and got the expected behavior.  I'll rebase against them once they're merged.  Also eager to get #4687.

@rob-the-dude did you get a chance to update this PR?

@rob-the-dude did you get a chance to update this PR?

I was waiting for #4804 to get merged (even though I'd made a suggestion but apparently didn't submit it -- doh, my bad), and was doing a little bit of additional cleanup based on changes that have gone in since I did the original.  I see now that you've got a change dependent on this.  I'll step it up, but I think it would be better if #4804 could make it in first.

@rob-the-dude #4804 has been merged.

@rob-the-dude not sure if you have time to contribute some test scripts on macOS. currently the macos check is very simple. Current the macOS only checks build. But with this change, we can verify the platform netif and platform udp on macOS with the script/check-posix-pty.

I would love to do that.  Can I do it in a second PR, since it's adding additional functionality, and the existing functionality is being tested on Linux?  There's a lot of changes here, and I get nervous about anyone else touching netif before I can get them in :-).
I've already tried using script/check-posix-pty on mac OS, but only indirectly -- manually running the tests that it automates.  Some things it uses (socat, libcoap) aren't on mac OS by default.  Both appear to be available via homebrew, but I don't know if homebrew is available for GitHub mac OS actions?  I don't use homebrew on my own development systems, so I'll have to be doing this work "live" on my GitHub fork.  I need to come up to speed on what the capabilities of GitHub actions for mac OS look like.

Great work for supporting MacOS/BSD. I'm wondering if we can move some of the functions that are very different on linux and BSD to different files so that we don't need so many macro checks.


Fix amibiguity between sensor and MAS client device names

It fixes #156
But maybe they had the same name for a reason @GiulioRomualdi @lrapetti @traversaro ?

As discussed f2f, we agreed that it is fine at the end to have the mas client and the sensor w/ the same name, because it was handy if you need to use the same configuration for launching wbd internally.
Closing.


Create korayer.de.md

I think there may have been an error? Your file is empty.

i'm sorry, should be okay now.

sorry for the inconvenience. should be fixed now. i am hosting on another server now.
https://tools.pingdom.com/#5fbe830dc1400000


Update CUDA-Z to 0.10.251

Split from #13842.

Thank you for the contribution. It was merged directly as e33c8a270907226aeea6ddf622cc3b3e4dd8ae30 to keep commit history cleaner. Your contribution is still credited to you.


Where InputListener exit and enter call?

Please ensure you have given all the following requested information in your report.
Issue details
I want to detect mouse enter and exit one Label. But after I read source code, there is only mouse moved event in InputEventQueue and no exit and enter judgement after fire mousemoved event. Therefore, is enter and exit not working? How to fix it?
Reproduction steps/code
label= new Label("Test", Label.LabelStyle);
label.addListener(new ClickListener(){
            @Override
            public void clicked(InputEvent event, float x, float y) {
                O.ptln("Test");
            }
            @Override
            public void exit(InputEvent event, float x, float y, int pointer, Actor toActor) {
                O.ptln("Out");
            }

            @Override
            public void enter(InputEvent event, float x, float y, int pointer, Actor toActor) {
                O.ptln("In");
            }
        });
        Stage stage = new Stage();
        stage.addActor(label);
        Gdx.input.setInputProcessor(stage);

Version of libGDX and/or relevant dependencies
    gdxVersion = '1.11.0'

Please select the affected platforms

[ ] Android
[ ] iOS
[ ] HTML/GWT
[x] Windows
[ ] Linux
[ ] macOS

I don't know why it's not working in your case, but here's a simple example I whipped up where it works. I used a ClickListener and Label to more or less match yours.
package com.mygdx.game;

import com.badlogic.gdx.ApplicationAdapter;
import com.badlogic.gdx.Gdx;
import com.badlogic.gdx.graphics.Color;
import com.badlogic.gdx.graphics.g2d.BitmapFont;
import com.badlogic.gdx.scenes.scene2d.Actor;
import com.badlogic.gdx.scenes.scene2d.InputEvent;
import com.badlogic.gdx.scenes.scene2d.Stage;
import com.badlogic.gdx.scenes.scene2d.ui.Label;
import com.badlogic.gdx.scenes.scene2d.utils.ClickListener;
import com.badlogic.gdx.utils.ScreenUtils;

public class MyGdxGame extends ApplicationAdapter {
  Stage stage;

  @Override
  public void create() {
    Label.LabelStyle style = new Label.LabelStyle(new BitmapFont(), Color.WHITE);
    Actor actor = new Label("Test", style);
    actor.addListener(new ClickListener() {
      @Override
      public void enter(InputEvent event, float x, float y, int pointer, Actor fromActor) {
        System.out.println("enter");
      }

      @Override
      public void exit(InputEvent event, float x, float y, int pointer, Actor toActor) {
        System.out.println("exit");
      }
    });

    stage = new Stage();
    stage.addActor(actor);
    Gdx.input.setInputProcessor(stage);
  }

  @Override
  public void render() {
    ScreenUtils.clear(Color.DARK_GRAY);
    stage.act();
    stage.draw();
  }
}

Thank you very much!  I didn't read act function, but this is where enter and exit called. From your code, I understand where should I put stage.act(). Now it works!


made a direct link on getmonero.org

realized I shoulda run it by you first. If it's problematic i'll hit the undo button somehow.
https://github.com/monero-project/monero-site/pull/2101#event-8203482207

all good mate, thanks for the shout! stoked to be in the official docs like that.


support kubernetes 1.23

What

Update task(s) for Kubernetes 1.23.

How

Edit sources and resources according to the maintenance guide.

deprecate CSI inline ephemeral volume (#324 )

deprecate PSP

update PodDisruptionBudget version to v1 ( since v1 was introduced as of 1.21 and v1beta1 will be removed as of 1.25)

migrate kubescheduler.config.k8s.io/v1beta1 to v1beta2 for k8s v1.22 & v1.23 (https://github.com/kubernetes/kubernetes/pull/104782)

Checklist

[ ] Finish implementation of the issue
[ ] Test all functions
[ ] Have enough logs to trace activities
[ ] Notify developers of necessary actions

closed via #431


pop_back cannot instantiate abstract class

CXX is generating invalid C++ code for abstract classes.
The C++ header looks like this:
class IAuthServiceEvent
{
public:
	virtual void onAuthenticationReturn(AuthResult ret) = 0;

I don't need the CxxVector functions for this program, but cxx still generates pop_back glue code:
// gen0.cxx
void cxxbridge1$std$vector$ZOOMSDK$IAuthServiceEvent$pop_back(::std::vector<::ZOOMSDK::IAuthServiceEvent> *v, ::ZOOMSDK::IAuthServiceEvent *out) noexcept {
  ::new (out) ::ZOOMSDK::IAuthServiceEvent(::std::move(v->back()));
  v->pop_back();
}

cargo build throws this error:
autocxx-build-dir\cxx\gen0.cxx(419): error C2259: 'ZOOMSDK::IAuthServiceEvent': cannot instantiate abstract class
Is there a way to disable the generation of cxxbridge1$std$vector functions as workaround?
Version information:

running on Windows and MSVC
cxx version 1.0.49
autocxx version 0.8.0
the C++ library that I'm interfacing with is https://github.com/zoom/zoom-sdk-windows

Stale issue


Forge or Neoforge for 1.20.2+?

i am curious on what mod loader you are going port the mod to for newer mc versions

Neoforge

He already answer here https://github.com/Sinytra/Connector/discussions/128#discussioncomment-6835423

ok


Blender curve import regression in 4.0.2

Godot version
v4.0.2.stable.mono.official [7a0977ce2]
System information
Windows 11
Issue description
According to earlier bug reports, it seems like Godot 3 was able to directly import Bezier curves from Blender as Curve3D's. Now, in Godot 4.0.2, this seems to be no longer possible. Bezier curves are just imported as meshes. This screenshots shows a BezierCurve, BezierCircle and NurbsPath being imported as just a plain mesh.

In my workflow, I am trying to define an object to follow a given path, but ideally, I'd like to design the path in Blender and be able to adjust the path in Blender.
Steps to reproduce

Create blender file
Create BezierPath, add a few points in Blender file
Save and import to Godot
Observe paths imported as Node and not recognised as a Curve3D

Minimal reproduction project
repro.zip

Can you share the links of those issues you mention? I tested on Godot 3 and I could not reproduce the import of bezier curves.

Actually, it's my fault. I was looking through issues while tired and thought I was in the godot repo when I was actually in the godot-blender-exporter repo. That's my bad.
Regardless, the commit that apparently added this to that particular project is here: https://github.com/godotengine/godot-blender-exporter/commit/3e66e12d7c5bd22cf2644ea2715651bc8121bc72
As I continue thinking about it, the Blender import in Godot manually converts from the blend file to glTF which Godot uses. But glTF (I think) has no mechanism to export curves or paths.
It's not a regression, but still, being able to save bezier paths in Blender, for importing into Godot, would be ideal. Can we reclassify this as a feature request instead?

Actually, according to https://github.com/godotengine/godot-blender-exporter/issues/418#issuecomment-1382147094, it seems like the blender exporter isn't actively maintained and most pipelines have changed to the glTF import/export, or direct use of blend files in Godot itself.
If godot-blender-export is the past, and just using .blend files directly in Godot is the future, I wonder how we can import bezier curves? Even if someone could point me to the bits in Godot that manage the .blend file import, I'd possibly have a run at doing it myself.

The Blender importer uses the GLTF importer behind the scenes, so your best bet is to try to implement it for that one. This is made more complicated by the fact that the GLTF spec doesn't include anything about curves, so you'd have to develop your own GLTF extension, which is something that the spec supports.
The files you will want to take a look at are located in modules/gltf/editor.

Hi, any news on this topic?
i was looking for a faster and easier way to work whit path in Godot 4.2. i tested every export type in blender but no one can handle Bezier curves and when found this https://github.com/godotengine/godot-blender-exporter/pull/380 though was the solution, but is no maintained.


VIH-6265 integration improvements

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/VIH-6265
Change description

Removed need to include Case Admins in request
Added githooks
Added pipelines
Upgraded packages

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

/azp run

/azp run

/azp run

/azp run


Flowsa v1.3.1 release

updates to EIA_MECS_Land and GHGI mapping files that are used in FBS methods in  the flowsa v1.3.1 release

@bl-young any reason to hold off on pulling in these changes?


doc: release-notes: Add documentation release notes for 3.1

This commit adds the documentation release notes for the Zephyr 3.1
release.
Signed-off-by: Stephanos Ioannidis<EMAIL_ADDRESS>Closes #46220

It seems like this is missing a mention of the large reorganization performed in #41154.

Agreed, let's add that before merging. Also, the new Kconfig search engine/display!

@mbolivar-nordic @carlescufi I have updated the release note to mention those two changes.


Write a Kotlin program to find surface area of a sphere

Description
Write a Kotlin program to find surface area of a sphere
Surface area of sphere = 4 × π × Radius^2
Radius : 2

Surface area : 50.26548245743669

How to contribute

Save the solution in program/FindSurfaceAreaOfASphere.kt file
Add FindSurfaceAreaOfASphere.kt file in find-surface-area-of-a-sphere folder

!assign


Add namespace in build.gradle

Description
Edit: Applies to Android Only
Added namespace in module's build.gradle file to avoid "Namespace not specified. Specify a namespace in the module's build file." error. New version of Gradle requires namespace to be specified in build.gradle file.
Below is the error I was getting. But after adding namespace manually in package's build.gradle file, it fixed the issue.

Related Issues
None.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[ ] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

@srichakradhar , Can you please review my PR? Thanks.

Closing as this is has been addressed in https://github.com/googleads/googleads-mobile-flutter/pull/843


How do I add custom images

I was adding image attachments with NSTextAttachment in my custom textView.(Like below)
       let textAttachment = NSTextAttachment()        textAttachment.bounds = CGRect(x: 0, y: (textView.font!.capHeight - image.size.height).rounded() / 2, width:         image.size.width, height: image.size.height)         textAttachment.image = image         let attrStringWithImage = NSAttributedString(attachment: textAttachment)         textView.textStorage.replaceCharacters(in: currentRange, with: attrStringWithImage)
Is there a way to add images(don't care if is it an NSTextAttachment or a suffixedAttachment) on the textView with TwitterTextEditor?
I found I can get hashtags with regex and place an UIImage or UIView after that hashtag. But I can't find a way how to add just UIImage itself like an NSTextAttachment.

Hi, @Topwiz.
This is actually bit difficult on current Twitter Text Editor API design, since it is based on plain text not attributed text.
To use NSTextAttachment to render image within the text view (which is possible in Twitter Text Editor,) but it need to add that attribute to the U+ FFFC  (NSTextAttachment.character) in the plain text, however Twitter Text Editor API is, intentionally separate plain text updating and attribute updating logic, therefore it is bit difficult to use NSTextAttachment.
I understand however such use case may exist, so will explore new API for that.

@Topwiz
I use the TwitterTextEditor layoutManager as the layout backend. And set the image placeholder with space and keep the range. Then replace that space with SuffixedAttachment. It works. Maybe that is what you need.
https://github.com/TwidereProject/ActiveLabel.swift/blob/master/Sources/ActiveLabel/ActiveLabel.swift#L312-L342


Press SELECT to come back to sensor initial settings

That's the idea. Perhaps cycling between a limited number of presets with the same button.

Probably related to #9
Maybe it will also make sense to have different shooting modes where left<->right cycle through different sets of settings.

#26
start+ select resets sensor settings now


western blot assay questions

Hello,
Some questions related to existing Western blot terms:

Why is the term label for OBI:0000854 'western blot analysis' instead of 'western blot assay' when it is a term in the assay branch?
Shouldn't there be a linkage between OBI:0001669 'far-Western blot assay' and 'western blot analysis' ('western blot assay'). It seems that far-Western should be a child of western (inferred child?). Currently OBI:0001669 is a child of 'binding assay' OBI:0001146. And related to this, should OBI:0000854 'western blot analysis (assay)' be linked to 'binding assay' OBI:0001146?
Small note: "western" should not be capitalized in OBI:0001669.

Thanks,
Michelle

Discussed at June 7, 2021 call.
Regarding:

consensus is to change to "assay"
Will connect 'far-western blot assay' to 'western blot assay' via 'far-western bot assay' will have detection_technique as 'western blot assay'
western will always be lower-cased

@cstoeckert Does the above look correct?
(I couldn't capture the notes right after the call as I had back-to-back meetings all day today - so I'm afraid I'm remembering wrong.)
Thanks!

Yes, you captured what we discussed and agreed on. Thanks @mgiglio99 !


It's very easy to forget about .commit_tx()

I already forgot about calling it couple of times, and just found a bug in existing code that also forgot about it.
Maybe we should log a warning message on drop if DatabaseTransaction was not committed? Any other ideas?

I don't know what's the right balance between verbosity and safety here. Not having to worry about aborting txs when leaving a function via a ? operator is nice. We could probably introduce a map_err in front of every one of these that takes a closure which aborts the tx?
Maybe we could make the destructor log an error if a tx was dropped without being aborted?

Maybe we could make the destructor log an error if a tx was dropped without being aborted?

That what I've been thinking too. Possibly a way to mark that the transaction is expected to be dropped uncommited, and then just log a warning. It's not going to change any behavior, just help us spot any mistake.

As discussed on the call, in addition to the above, it will probably be good to create a read-only transaction so that we don't log this warning when its not necessary to commit.

I sent out a PR that implements this. One problem that I ran into is that there are some transactions that are not committed or aborted, they simply go out of scope when there's an error (most times the function returns without the chance to rollback). I added a way to surpress the warning message if that's the case.

Warning message added when write transactions are not committed in this PR

Warning message added when write transactions are not committed in this PR

I just forgot to call .commit_tx() and spent a bunch of time debugging it. A warning is great improvement, but I wonder if we could someday have a "debug mode" in Fedimint where it would just panic if this happened. Would save time in development.


Merge to publish

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/actionable-messages/connectors-dev-dashboard.md
:white_check_mark:Succeeded

docs/rest/webhooks.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Ends of long notes are not properly attached to the rest of the bar with downscroll enabled

Describe your bug here.
Known issue with the extra keys build of Pysch Engine, the 'tail' section of the note doesn't have an updated offset to fix it's position on downscroll.

Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
nay

I'll look into this soon. Thanks for letting me know.


Long Running Query Detection and Mitigation

A way to potentially mitigate database locking and resource issues could to be implement long running query detection and auto termination.  Suggestion: terminate any query that has run for more than 2 minutes and return an error, unless there is an exception that should allow the query to run longer than 2 minutes.

Duplicate -- see #2352


Move provisioning quota calculation methods into MiqTemplate class (pluggable)

PR set:

https://github.com/ManageIQ/manageiq-content/pull/737
https://github.com/ManageIQ/manageiq-automation_engine/pull/532
https://github.com/ManageIQ/manageiq-providers-ibm_cloud/pull/469
https://github.com/ManageIQ/manageiq-providers-ibm_power_hmc/pull/146

Fixes #22641
Move methods making quota calculations for a given request into MiqTemplate base class. They can then be overridden in the ManageIQ::Providers::CloudManager::Template subclass (for "cloud" providers), or even in provider plug-in subclasses.
Allows an override in ManageIQ::Providers::IbmCloud::PowerVirtualServers::CloudManager::Template to fix a bug where it reports 0 cpus for quota.

@miq-bot cross-repo-tests ManageIQ/manageiq-content#737 ManageIQ/manageiq-automation_engine#532

@jaywcarman Sorry, having trouble making out what was changed
Is it possible to change this into 2 (or more) commits?
When it makes sense, separating move operations from change operations:

Move code into MiqTemplate unchanged.
Move code into infra/template and cloud/template.

Is it possible to change this into 2 (or more) commits?

@kbrock I'm happy to do so.

@miq-bot cross-repo-tests https://github.com/ManageIQ/manageiq-content/pull/737 https://github.com/ManageIQ/manageiq-automation_engine/pull/532 https://github.com/ManageIQ/manageiq-providers-ibm_cloud/pull/469 https://github.com/ManageIQ/manageiq-providers-ibm_power_hmc/pull/146


Implement LLM Content Converter node

More than likely part of the Gemini Kit, this node will take any text or stream content and turn it into llm-content object.
For example:

I point core.fetch to a URL that contains a PDF or returns HTML, or a ZIP file
I wire stream output port of core.fetch to the stream input port of the LLM Content Converter node
I wire content output port of LLM Content Converter node to the input port of an output node. This input port has type object and llm-content behavior.

When I run the graph, I see content with parts in the output.

We could also use this node as the foundation for our ELT work, and keep all conversion in one place.

This is so exciting!


Credentials error

This changeset stacks after #52

Addressed the 2 style + grammar stuffz, lemme know what you have in mind for the docstring note.


How to store AesGcmJce

Hi! Please, provide more documentation about storing custom AEAD.
I use AesGcmJce, because I need create key from user entered pin-code, but I really do not understand how I can store my key in Android KeyStore, and use it to decrypt data in future.
Or maybe I should generate same key by pin-code? At this time I do not understand how I can do it. Under hood AesGcmJce generate new IV every time, and keys do not match.

Hi, not sure I understand what you're trying to achieve, can you elaborate?
To access/use Android Keystore with Tink, take a look at code in https://github.com/google/tink/tree/master/java/src/main/java/com/google/crypto/tink/integration/android like https://github.com/google/tink/blob/master/java/src/main/java/com/google/crypto/tink/integration/android/AndroidKeystoreAesGcm.java or https://github.com/google/tink/blob/master/java/src/main/java/com/google/crypto/tink/integration/android/AndroidKeysetManager.java

(please reopen if you have further questions)


Feature Request: Image cards for tags

Hi would it be possible to have image cards, like the lora tab, so that each tag can be associated with a preview image? This would be very useful for artist tags so you can have a preview image of what each artist tag looks like.

Awesome, thank you!


use library to output dot graph

using String.format to create DOT files is getting too unweidly, should switch to a library to do this -- https://github.com/nidi3/graphviz-java looks promising

resolved by https://github.com/apl-cornell/viaduct/commit/0d79dc54cff39d787bb54558b47826d9a382b56f


Jest registerApolloClient is not a function

I've followed the recommendations from the README, but I get this error during tests:
 TypeError: (0 , _experimentalnextjsappsupport.registerApolloClient) is not a function

       9 |
      10 |
    > 11 | const { getClient: graphClient } = registerApolloClient(() => {

Apart from jest the code works fine.
Repo to reproduce:
https://github.com/levchenkod/next-apolo-jest-basic-setup

Jest simulates a browser environment, so it uses the wrong version of Apollo Client for this - registerApolloClient is only available in React Server Components, not in the browser.
You can do
/** @type {import('jest').Config} */
const config = {
  testEnvironment: 'jsdom',
  testEnvironmentOptions: {
    customExportConditions: ['react-server'],
  },
};

in your jest config, which will instead load the "server component" code of @apollo/experimental-nextjs-app-support, but keep in mind that this will change resolution for all your dependencies to "server component" - you'll also get a different build of react, react-dom etc.
If you want to test server components, this is probably a good thing, but I don't know for sure if jest actually works nicely with that.

Jest simulates a browser environment, so it uses the wrong version of Apollo Client for this - registerApolloClient is only available in React Server Components, not in the browser.
You can do
/** @type {import('jest').Config} */
const config = {
  testEnvironment: 'jsdom',
  testEnvironmentOptions: {
    customExportConditions: ['react-server'],
  },
};

in your jest config, which will instead load the "server component" code of @apollo/experimental-nextjs-app-support, but keep in mind that this will change resolution for all your dependencies to "server component" - you'll also get a different build of react, react-dom etc. If you want to test server components, this is probably a good thing, but I don't know for sure if jest actually works nicely with that.

@phryneas I'm getting the same error using Vitest, and I've been trying to replicate the provided Jest config without luck. Any pointers?

Vitest also doesn't simulate a react-server environment by default. This is really a specific runtime environment where libraries load differently than they would in the RSC run or in the browser.
For vitest, you would have to specify
export default defineConfig({
  plugins: [react()],
  resolve: {
    conditions: ["react-server"],
  },
});

Vitest also doesn't simulate a react-server environment by default. This is really a specific runtime environment where libraries load differently than they would in the RSC run or in the browser.
For vitest, you would have to specify
export default defineConfig({
  plugins: [react()],
  resolve: {
    conditions: ["react-server"],
  },
});

Thanks for helping, but adding that line to the config seems to break all tests with the following error:
Error: This entry point is not yet supported outside of experimental channels
 ❯ ../../node_modules/.pnpm/react@18.3.1/node_modules/react/cjs/react.shared-subset.development.js:18:7
 ❯ Object.<anonymous> ../../node_modules/.pnpm/react@18.3.1/node_modules/react/cjs/react.shared-subset.development.js:19:5
 ❯ Object.<anonymous> ../../node_modules/.pnpm/react@18.3.1/node_modules/react/react.shared-subset.js:6:2

Yes, you are running your tests with React 18.3.1, while Next.js is using a Canary build of React. You will have to find out which React build your Next.js installation uses and use that same build for your tests.
Next.js ignores your node_modules and brings it's own dependencies. I know it's insane but that's what we all have to deal with 😢
Look in node_modules/next/dist/compiled/react/cjs/react.development.js for the string ReactVersion, you'll find something like '18.3.0-canary-14898b6a9-20240318'

That is quite insane indeed, I gave the last suggestion a shot but no luck. I think I'll wait with adding tests for the few pages I've migrated to app router until Next 15 to see if they make this more manageable.
Thanks for your help!


Feature/bitfinex metadata fix

Fix for bitfinex currency metadata

@earce Anyone to review? :)

please pull out all huobi changes related to spacing also if you have any remaining huobi changes make them a separate review

Irrelevant differences are reverted. Ready to merge


Printable Colour Chart Would be Really Useful

[Enter feedback here]
A printable version of the colour chart would be fantastic - perhaps as a PDF?

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

ID: aee8f50b-d6f4-0859-9598-d5498f9c4ede
Version Independent ID: 36363d89-51e5-f5aa-de25-f6b56f144e3f
Content: Xamarin.Forms Brushes: Solid colors - Xamarin
Content Source: docs/xamarin-forms/user-interface/brushes/solidcolor.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Microsoft support for Xamarin will end on May 1, 2024 for all Xamarin SDKs including Xamarin.Forms. In preparation for this, all issues and PRs in this repository are being closed.
.NET MAUI is the replacement for Xamarin.Forms, and it's documentation can be found here.


services/content: ignore io.EOF after successful commit

Signed-off-by: Stephen J Day<EMAIL_ADDRESS>

LGTM


Zoom optimisation for Waves and matching implementation for Spectrograms

Zoom optimisation for Waves and matching implementation for Spectrograms

Short description of changes:
My goal was to allow zooming on a spectrogram to be performed faster and with no maximum width. To do this I implemented optimisations in both the wavesurfer and the spectrogram with the intention of making zooming better for users.
Removing the maximum width
I took the multicanvas approach used in the wavesurfer drawer and applied it to the spectrogram so that the maximum size limit would be circumvented. In my approach all canvases are equally sized as I found this to be easier to manage, however the multicanvas drawer remains the same.
Improving Performance
Existing canvases can have their width changed in style without redrawing/recalcuation. This is an incredibly fast way to preview a wave/spectrogram at various zoom levels. I created a zooming() function to be called when the zoom level is changed, and only calling the original zoom() function when the zoom slider is released. This approach preserved the original behavior of zoom for older implementations.
The spectrogram is still a very computationally expensive task and so generating particularly large ones takes a lot of time. I scheduled canvases on a priority so that viewable and near-viewable canvases would be rendered before others. This process can be seen when zooming out quickly after zooming in. This was applied to the wavesurfer too, although it was much less common for long waves to generate the same level of lag as the spectrogram

An example of zooming while the audio is playing:

Breaking in the external API:
None that I know of
Breaking changes in the internal API:
None that I know of
Todos/Notes:
Todos
None
Notes
Some unrelated changes were necessary as a result of the approach taken. Since the drawer width changes with the zoom, I had to remove the check in drawer.js that prevented redrawing the wave if the zoom level remained unchanged.
I changed the example pages for zoom and spectrogram to reflect the new implementation.
This implementation adds/removes no files and requires no additional libraries.
Related Issues and other PRs:
None that I know of

Coverage: 78.995% (-2.4%) from 81.375% when pulling 9d0bdc3dfce89769af757f3b1257d9162ad525b2 on luke-harrison-personal:zoom_optimisation into 4dbd9ecc8f2228e57628f5bf64f612721705a63e on katspaugh:master.

@katspaugh @thijstriemstra @luke-harrison-personal been looking into this as well lately. We can look into adding css image-rendering: pixelated; so it doesn't blur the canvas while it's stretching it. There is also the globalConpositeOperation in canvas we could potentially utilize.
https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/globalCompositeOperation
However there is also the possibility of making these peaks as SVG in realtime as an idea.

That CSS rule is worth trying 👍
SVG, unfortunately, didn't fare well in terms of performance back when we used to have it as a rendering option. Things might’ve changed. In any case, it’s outside the scope of this PR.


"-f ba*" doesn't select best audio

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2<IP_ADDRESS>. (update instructions)
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Description
-f ba* doesn't select best audio that may contain video but best video that contains audio because the sorting field hasvid has the highest priority unless you also use --format-sort-force and something like -S acodec or -S abr.
Examples:

yt-dlp.exe https://www.youtube.com/watch?v=iik25wqIuFo downloads format ID 248+251 (best video and best audio, correct)
yt-dlp.exe https://www.youtube.com/watch?v=iik25wqIuFo -f ba* downloads format ID 22 (best video+audio, wrong)
yt-dlp.exe https://www.youtube.com/watch?v=iik25wqIuFo -f ba* -S acodec --format-sort-force downloads format ID 251 (best audio, correct)

Using only -f ba works in this case, but what if there is a video format with better audio than an audio-only format?
Suggestion: If I want the best audio format, yt-dlp should change the default sorting order to favour better audio formats, independently of video.
I'm not sure if this only relates to Youtube, but I don't know which other site I could test this on.
Verbose log
[debug] Command-line config: ['https://www.youtube.com/watch?v=iik25wqIuFo', '-f', 'ba*', '-vU']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, err utf-8, pref cp1252
[debug] yt-dlp version 2<IP_ADDRESS> [c0c2c57] (win_exe)
[debug] Python version 3.8.10 (CPython 64bit) - Windows-10-10.0.22000-SP0
[debug] exe versions: ffmpeg N-105919-g546afd0d49-20220313 (setts), ffprobe N-105919-g546afd0d49-20220313
[debug] Optional libraries: brotli, Cryptodome, mutagen, sqlite, websockets
[debug] Proxy map: {}
Latest version: 2<IP_ADDRESS>, Current version: 2<IP_ADDRESS>
yt-dlp is up to date (2<IP_ADDRESS>)
[debug] [youtube] Extracting URL: https://www.youtube.com/watch?v=iik25wqIuFo
[youtube] iik25wqIuFo: Downloading webpage
[youtube] iik25wqIuFo: Downloading android player API JSON
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, codec:vp9.2, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), acodec, lang, proto, filesize, fs_approx, tbr, vbr, abr, asr, vext, aext, hasaud, id
[info] iik25wqIuFo: Downloading 1 format(s): 22
[debug] Invoking downloader on "https://rr2---sn-5jvoxu-8pxe.googlevideo.com/videoplayback?expire=1647465486&ei=rv8xYqn2FIPp1gKn_bKIBw&ip=XXX&id=o-ANn_lYxWdx7i5pfnmNMZqe5J7h8SKKB6nvesCom0H-hF&itag=22&source=youtube&requiressl=yes&mh=lR&mm=31%2C29&mn=sn-5jvoxu-8pxe%2Csn-2gb7sn7k&ms=au%2Crdu&mv=m&mvi=2&pl=19&initcwndbps=1132500&vprv=1&mime=video%2Fmp4&ratebypass=yes&dur=7.244&lmt=1641462248093086&mt=1647443362&fvip=2&fexp=24001373%2C24007246&c=ANDROID&txp=5311224&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cvprv%2Cmime%2Cratebypass%2Cdur%2Clmt&sig=AOq0QJ8wRAIgaU9VctCnxz21Qm69vsY5sd4qh8oiyjcTftOwZfVFwlICIFetHaFH5xrnMMBNlddLpdF2BLdTEFEXIsAL-R7WjCVW&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps&lsig=AG3C_xAwRQIhAKyTai83UGb7ZTTxZcghC_fpWxLdCWDJDsv1mZBfnB9xAiBQmOxnu9TMhfVl5CuCeSRW0rtWZzno8PDYLDTq4SdjcQ%3D%3D"
[download] Destination: Rick roll, but with different link [iik25wqIuFo].mp4
[download] 100% of 1.09MiB in 00:00

See https://github.com/yt-dlp/yt-dlp/issues/979#issuecomment-919629354 for details

Well, that's too bad.
Example 1: I just want to download a video. yt-dlp chooses the best audio-only format, the best video-only format and combines them.
Example 2: I want to download the best audio (which may also contain video). But yt-dlp chooses the best video-with-audio-format.
Example 3: I want to download the best audio-only format. yt-dlp chooses the best audio-only format.
I don't get it why there is a difference between example 1 and 2. To me it seems like -f b and -f ba* yield exactly the same result.
I guess I just have to use the "longer" way. Thanks for the answer!

Maybe try using -x? Not sure how it fits into all this.

Maybe try using -x? Not sure how it fits into all this.

Thanks, but -x doesn't change the downloaded format, unfortunately.

Thanks, but -x doesn't change the downloaded format, unfortunately.

Do -x --audio-format "mp3" for that where you can replace "mp3".

Thanks, but -x doesn't change the downloaded format, unfortunately.

Do -x --audio-format "mp3" for that where you can replace "mp3".

It's not about the file I get after the download, but what format ID gets chosen by yt-dlp.

Example 1: I just want to download a video. yt-dlp chooses the best audio-only format, the best video-only format and combines them. Example 2: I want to download the best audio (which may also contain video). But yt-dlp chooses the best video-with-audio-format. Example 3: I want to download the best audio-only format. yt-dlp chooses the best audio-only format.
I don't get it why there is a difference between example 1 and 2. To me it seems like -f b and -f ba* yield exactly the same result.

Python is bad, and so everything written on it rely on its sins. Don't overthink about that, keep yourself sane and have a great life!


Client id length validation

Hi,
I was wondering why the length check here limits the client id to max 23 bytes.
The 3.1.1 spec says you must allow client id's with a length between 1 and 23, but it doesn't say you can't have client id's longer than 23 bytes right? Or am I misunderstanding?

@mrdg you are correct. The spec says "The Server MAY allow ClientId’s that contain more than 23 encoded bytes. The Server MAY allow ClientId’s that contain characters not included in the list given above."
I took the most strict route but see no reason why it can't be more than 23.
Are you using it as client or server?

I'm using only the message package for encoding / decoding  at the moment actually.


NFT module ownerOf on non-existent token fatal error

Reproducible case: https://thirdweb.com/rinkeby/0xe5C11E2d5e930b26CF51AB5155bb88B3654C8b2b/nft-collection/0xf27C2a1c44E6F16Fbcc9FBB582d7799057Dc57a6
Investigation so far:

reported by pratham
happened after a token was burnt via python sdk
error in dev console:

Hunch: Something in the SDK is going through a for loop of token ids and barfs based on one of them not existing => fatal error

Hmm @jnsdls that url you posted returns 404?

Hmm @jnsdls that url you posted returns 404?

updated url

Confirmed that calling ownerOf on a burned token throws an error with message
thirdweb_web3.exceptions.ContractLogicError: execution reverted: ERC721: owner query for nonexistent token

Pushing a PR to the typescript library to wrap the call in a try catch and return null if the token has been burned (thus signaling that the token has been burned)

PR is up #14

Can confirm that this fixes the bug https://thirdweb-www-cpd9lf0ti-thirdweb.vercel.app/rinkeby/0xe5C11E2d5e930b26CF51AB5155bb88B3654C8b2b/nft-collection/0xf27C2a1c44E6F16Fbcc9FBB582d7799057Dc57a6


v0.2.4

Minor adjustments to support to address deprecation warnings in pandas >= 23.0

Coverage decreased (-0.1%) to 94.186% when pulling 3bd06b3100e9708eb4167b80f8b68e3666901ae4 on new-pandas into 985dbaf06fd19ccd8cd2a81179f8100807792a2a on master.


Develop README

Should have a short usage example and a screenshot / gif. We can probably also put the example app on Google Play.

Usage added along with some additional data. Still waiting for a gif and an example app

GIF added


Laboratory work#1, Loreleya Gellertova 23FPL1

There's nothing to watch, I advise you to speed up! I wish you good luck!


Spring Boot: Runtime name change  Spring Boot Tomcat -> Spring Boot

Consensus regarding Runtime name change - remove Tomcat from the name and restore to Spring Boot

relates to #762

PR #845 is merged, closing.


stack view feature can not work correctly on windows 10 os

Describe the bug
I use neovim(release-0.10.2) and cscope-maps(git commit:79452ca) on windows 10 os. And when cross review any items of stack view result, it will display below error:
Error executing vim.schedule lua callback: ...ata/lazy/cscope_maps.nvim/lua/cscope/stack_view/init.lua:173: bad argument #1 to 'lines' (d: No such file or directory)
stack traceback:                                                                                [C]: in function 'lines'                                                                                ...ata/lazy/cscope_maps.nvim/lua/cscope/stack_view/init.lua:173: in function 'read_lines_from_file'                                                                                ...ata/lazy/cscope_maps.nvim/lua/cscope/stack_view/init.lua:187: in function <...ata/lazy/cscope_maps.nvim/lua/cscope/stack_view/init.lua:181>
To Reproduce
Steps to reproduce the behavior:

Use my configuration of cscope_maps,  and build cscope db

Open the stack view for a symbol named container_of

CsStackView open down  container_of

Press "j" to walk next item of  stack view result, it will display this traceback error

Expected behavior
The stack view feature can work correctly on windows 10 , and this feature can work correctly on my ubuntu-20.04.
Screenshots

nvim version (please complete the following information):
nvim -v
NVIM v0.10.2
Build type: Release
LuaJIT 2.1.1713484068
Run "nvim -V1 -v" for more info
cscope-maps:
79452ca (HEAD -> main, origin/main, origin/HEAD) cscope: escape commonly used special chars
D:\code\libuv>cscope --version
cscope: version 15.9
cscope_maps config (please complete the following information):

opts = {
      -- maps related defaults
      disable_maps = false, -- "true" disables default keymaps
      skip_input_prompt = false, -- "true" doesn't ask for input
      prefix = "gq", -- prefix to trigger maps

      -- cscope related defaults
      cscope = {
        -- location of cscope db file
        db_file = "./cscope.out", -- DB or table of DBs
                                  -- NOTE:
                                  --   when table of DBs is provided -
                                  --   first DB is "primary" and others are "secondary"
                                  --   primary DB is used for build and project_rooter
        -- cscope executable
        exec = "cscope", -- "cscope" or "gtags-cscope"
        -- choose your fav picker
        picker = "quickfix", -- "quickfix", "telescope", "fzf-lua" or "mini-pick"
        -- size of quickfix window
        qf_window_size = 10, -- any positive integer
        -- position of quickfix window
        qf_window_pos = "bottom", -- "bottom", "right", "left" or "top"
        -- "true" does not open picker for single result, just JUMP
        skip_picker_for_single_result = true, -- "false" or "true"
        -- these args are directly passed to "cscope -f <db_file> <args>"
        db_build_cmd_args = { "-Rbqkv" },
        -- statusline indicator, default is cscope executable
        statusline_indicator = nil,
        -- try to locate db_file in parent dir(s)
        project_rooter = {
          enable = false, -- "true" or "false"
          -- change cwd to where db_file is located
          change_cwd = false, -- "true" or "false"
        },
      }
}

Additional context
It is maybe the absolute path problem on windows 10, such as below stack view result parttern:
poll_cb [d:/code/libuv/src/fs-poll.c:191]
timer_close_cb [d:/code/libuv/src/fs-poll.c:240]
Thank you to contribute so great tools!

Hey,
Thanks for reporting this. I haven't tested on windows but I think what you pointed out is the issue. We might have to convert the path before reading from the file.

Hi @hansen6878
pls check if windows branch fixes your issue https://github.com/dhananjaylatkar/cscope_maps.nvim/tree/windows
i'll merge if it's all right from your side

@dhananjaylatkar Thank you for the quick fix. I pull the latest code and test on my windows environment. It works perfectly.


Implementing all 4 typical "messages" as in proftpd and other commercial FTP servers (taking over)

Taking over from #422

So @syncplify & @drakkan, what do you think about this?
This seems like a nice feature to add and a good time to create a new release.

I agree. Apologies for mixing in the second change which should have been its own PR. You're right to drop that. I'll do a new and detailed PR once I have time to explore the observation @drakkan made about that. But the primary feature of this PR is highly desirable so I'd be very happy to see it included in your next release. Thanks.

To explain the little pull requests and branches I have pushed...
I have invested little time in it and faced a few issues.

I made a working version and added this PR.
The next day, I changed core parts of the testing code and faced some race conditions
One week later (now) I tried to revert the code but now I have a problem with golangci-lint that won't even valide the same code push... And now I'm not sure how to proceed.

So now I try to understand why we have these differences:

working commit 0aa7a8a
failing commit 0aa7a8a

I suspect it's because of the golangci-lint's cache...


Not return err when pass random str or invalid privateKey to func PrivateKeyFromBase58

I just tried to use the func to validate private key but got some other behavior that func.
https://github.com/gagliardetto/solana-go/blob/main/keys.go#L48
It's correct behavior ?

Also I want to add some notes if pass incorrect value or random str the fucn and call public method PublicKey() get error.
panic: runtime error: slice bounds out of range [x:x]

If pass correct 'privateKey', everything will be fine and return publicKey.

I just tried to use the func to validate private key but got some other behavior that func.
https://github.com/gagliardetto/solana-go/blob/main/keys.go#L48
It's correct behavior ?

Hi @Almazatun , can you explain what is the "some other behaviour"?

Also, I want to add some notes if pass incorrect value or random str the func and call public method PublicKey() or call Sign(pk) not return error argument but call panic. But the methods should return err argument.
panic: runtime error: slice bounds out of range [x:x] | panic: ed25519: bad private key length

If pass correct privateKey, everything will be fine and return publicKey.

Can you give the sample of the code that give that exact error? It will help us to debugging. Thank you

@pikomonde Thank you very much for your reply. The PrivateKeyFromBase58 method returns two values. If I guess that means if pass invalid privateKey should be returned err that does not equal nil. But instead of this behavior, you will get err = nil.
invalidPrivateKey := "6HsFaXKVD7mo43oTbdqyGgAnYFeNNhqY75B3JGJ6K8a227KjjG3uW3v"

_, err := solana.PrivateKeyFromBase58(invalidPk)

fmt.Println(err)

Is this the correct behavior of the method?

Ah, I got your question now. My question is, how do you know that 6HsFaXKVD7mo43oTbdqyGgAnYFeNNhqY75B3JGJ6K8a227KjjG3uW3v is an invalid private key? Is there any docs on Solana that classify that this particular private key is invalid?

@pikomonde You can copy and paste to phantom wallet to check.

I'm not sure if it is the correct behaviour or not (I think we need to compare with solana's official client)
But I think it is invalid because it is not on the a valid "ed25519" pair, and unfortunately the golang's "crypto/ed25519" package not providing a valid validation for it. Need to implement using this: https://security.stackexchange.com/questions/233099/validating-an-ed25519-public-key (haven't check it yet)
So I think there are 2 action items:

Comparing the implementation of solana's official client;
Check whether the implementation of https://security.stackexchange.com/questions/233099/validating-an-ed25519-public-key is correct or not.

Just realized that there is already a function provided by this library:
solana.IsOnCurve("6HsFaXKVD7mo43oTbdqyGgAnYFeNNhqY75B3JGJ6K8a227KjjG3uW3v")


Self-hosted docs

This combines a bit of Bader's work, our existing docs in the Insights repo, and some new changes

Merging so I can send this out. Retroactive comments welcome!


Review Fay Lab Resources chapter

Gavin can please review Fay lab resources chapter.

Merged content into Chapter 12 UMassD Resources.


New DLite Datamodel for SingleFile that contains 'content'

datanode2cuds updated to populate this new version of SingleFile.
The reason for this is that we need to be able to access the data in the datanodes in the next partial pipeline
Missing tests, but I did not find any tests for aiida-cuds to lean on.

@louisponet @CasperWA
Louis and I both have old PRs that should have been merged.
Now that Casper has made an update of execflow to match the newest version of oteapi which uses pydantic2 instead of 1 I wanted to make use of all changes.
Unfortunately trying to merge all branches ended up in a mess for me, so I took only the important parts from my branch, merged with Caspers and then afterwards added all Louis updates (the latter without merge).
I hope this is OK with both of you so that we can proceed. Now all the tests in Execflow run again, and I can run everything that worked before in SS3_wrappers.
This is priabbly not the correct procedure to make such changes, but at the end of the day this was the way I managed.
There are some things that need to be fixed: The critical things to correct prior to merging described in https://github.com/H2020-OpenModel/ExecFlow/pull/22, and fixing of the possibility to define processors etc in the workflow as the original fix did not work.

This all seems fine with me, but then again, it's not my contributions that have been wiped away.
As a suggestion, you could add Co-authored-by: Louis Ponet<EMAIL_ADDRESS>(if that's the correct email address) to the commits that implement his changes to provide him with some acknowledgement of his work?

Shall I close the other PR from you @CasperWA ?


KAFKA-13880: Remove DefaultPartitioner from StreamPartitioner

There are some considerata embedded in this seemingly straight-forward PR that I'd like to explain here. The StreamPartitioner is used to send records to three types of topics:

repartition topics, where key should never be null.
changelog topics, where key should never be null.
sink topics, where only non-windowed key could be null and windowed key should still never be null.

Also, the StreamPartitioner is used as part of the IQ to determine which host contains a certain key, as determined by the case 2) above.
This PR's main goal is to remove the deprecated producer's default partitioner, while with those things in mind such that:

We want to make sure for not-null keys, the default murmur2 hash behavior of the streams' partitioner stays consistent with producer's new built-in partitioner.
For null-keys (which is only possible for non-window default stream partition, and is never used for IQ), we would fix the issue that we may never rotate to a new partitioner by setting the partition as null hence relying on the newly introduced built-in partitioner.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Seems there is some checkstyle error:
> Task :clients:checkstyleMain

[2022-06-16T18:57:40.716Z] [ant:checkstyle] [ERROR] /home/jenkins/jenkins-agent/workspace/Kafka_kafka-pr_PR-12304/clients/src/main/java/org/apache/kafka/clients/producer/internals/DefaultPartitioner.java:21:8: Unused import - org.apache.kafka.common.utils.Utils. [UnusedImports]


Add version 5.1

Comment:
Hi,
Is it possible to add version 5.1? Another recipe has v5.1 in its requirements
possibly this may help
https://conda-forge.org/docs/maintainer/updating_pkgs.html#maintaining-several-versions

Should be resolved by https://github.com/conda-forge/cbor2-feedstock/pull/7


Fix for config file location

With this change the config file should always be in the same directory as the addon file.

Lgtm! Thanks a lot!