Fix for error with empty "Unique users" for today/yesterday on Filament v.2

I've same problem (https://github.com/bezhanSalleh/filament-google-analytics/issues/38) with your package on ver. 2.0.0, with Filament v.2, with about to empty GA data, on test environment. We're unable to use package without pass all tests on Test environment (b/c some time it's possible to have 0 as "today unique users" for example at 0:01AM for current day.
We're unable to update to Filament v.3 for some reasons.
Can u please add same fix for your package (2.0.0 ver) b/c 2.0.0 ver last supported version for Filament v.2, or add support for Filament v.2 to 2.0.1 package version if 2.0.1 works with Filament v.2.
vendor/bezhansalleh/filament-google-analytics/src/Traits/Visitors.php
Undefined array key 1 {"userId":1,"exception":"[object] (ErrorException(code: 0): Undefined array key 1 at .../vendor/laravel/framework/src/Illuminate/Collections/Collection.php:1781)

It's require to modify this function
private function visitorsToday(): array
    {
        $analyticsData = Analytics::fetchTotalVisitorsAndPageViews(Period::days(1));

        return [
            'result' => $analyticsData[0]['activeUsers'],
            'previous' => $analyticsData[1]['activeUsers'],
        ];
    }

and here too, to be sure that we are never get 500 if data empty...
    private function visitorsYesterday(): array
    {
        $analyticsData = Analytics::fetchTotalVisitorsAndPageViews(Period::create(Carbon::yesterday()->clone()->subDay(), Carbon::yesterday()));

        return [
            'result' => $analyticsData[0]['activeUsers'],
            'previous' => $analyticsData[1]['activeUsers'],
        ];
    }

Originally posted by @RChutchev in https://github.com/bezhanSalleh/filament-google-analytics/issues/38#issuecomment-2119046697

Something like this should fix the problem with the visitors feature.
Also, looks like, you should replace period with Carbon::today() otherwise we get data for yesterday.
b/c real data is Today: [] , and Yesterday: [{"date":"2024-05-18T01:30:17.000000Z","activeUsers":3,"screenPageViews":79},{"date":"2024-05-17T01:30:17.000000Z","activeUsers":12,"screenPageViews":102}]
in Traits/Visitors.php
[2024-05-19 03:24:29] env.INFO: Today: [{"date":"2024-05-18T01:24:29.000000Z","activeUsers":3,"screenPageViews":79}]

    private function visitorsToday(): array
    {
        $analyticsData = Analytics::fetchTotalVisitorsAndPageViews(Period::create(Carbon::today(), Carbon::today()));

        return [
            'result' => $analyticsData[0]['activeUsers'] ?? 0,
            'previous' => $analyticsData[1]['activeUsers'] ?? 0,
        ];
    }

Same problem may happen with Page Views, if data for yesterday will be 0.
I think better to add '?? 0' here too.
    private function visitorsYesterday(): array
    {
        $analyticsData = Analytics::fetchTotalVisitorsAndPageViews(Period::create(Carbon::yesterday()->clone()->subDay(), Carbon::yesterday()));

        return [
            'result' => $analyticsData[0]['activeUsers'] ?? 0,
            'previous' => $analyticsData[1]['activeUsers'] ?? 0,
        ];
    }

In src/Traits/PageViews.php
Same problem with Today's data, I mean yesterday's data and should be replaced with something like this.
    private function pageViewsToday(): array
    {
        $analyticsData = Analytics::fetchTotalVisitorsAndPageViews(Period::create(Carbon::today(), Carbon::today()));

        return [
            'result' => $analyticsData->last()['screenPageViews'] ?? 0,
            'previous' => $analyticsData->first()['screenPageViews'] ?? 0,
        ];
    }

It's possible that other widgets have the same problem, but I haven't tested that.

Please double check everything, or I can help you with a fix if needed, but inconsistent data is the last thing users like...
And I really appreciate your work.

About data inconsistency, for example page-views widget.
"Today" data

and "yesterday" data

As you can see, real GA data for yesterday marked as today's data with your package.

@bezhanSalleh could you please participate?

for some reason i wasn't watching this repo. apologies for the very late reply.

for some reason i wasn't watching this repo. apologies for the very late reply.

Hi, okay, keep me posted, I'm still waiting for any updates.

Yes, okay, sorry for the misunderstanding.
You are a little bit wrong about that, with Filament 2 I've installed "bezhansalleh/filament-google-analytics": "^2.0.0", exact version is 2.0.0. Yes, composer install your package 2.0.0 with Filament 2 with Laravel 10. That's the reason why I write in the first message v.2 with Filament 2.

Yes, okay, sorry for the misunderstanding. You are a little bit wrong about that, with Filament 2 I've installed "bezhansalleh/filament-google-analytics": "^2.0.0", exact version is 2.0.0. Yes, composer install your package 2.0.0 with Filament 2 with Laravel 10. That's the reason why I write in the first message v.2 with Filament 2.
Also, GitHub Dependabot can update some packages to newly available, anyway, 2.0.0 is compatible with Filament 2, but the next one isn't, and fixes for these errors are not available in 2.0.0. I can't fix it by myself because that's weird to add something to the v.2 branch for the v.1 branch, but if I add this fix to the v.1 branch I didn't get it b/c already use the 2.0.0 version.

ok, so i'm not gonna bore ya with details but i remember now so instead of 2.0.0 lock your version to 1.1.2 and let me know.

About data inconsistency, for example page-views widget.
"Today" data
and "yesterday" data

As you can see, real GA data for yesterday marked as today's data with your package.

@bezhanSalleh, hello, we have downgraded package, yes, it fixed 500 error, but this error still here.

@bezhanSalleh also, looks like something wrong with "Avg. Sessions Duration".
This card show me about 02:00:00 every time, but real value is 33.933530647058824.

This value coming from your SessionDuration trait

@bezhanSalleh, yes, okay, ill check it now, but what about session duration?
GA returns value in seconds, but this value shown incorrectly.
In public function trajectoryValueAsTimeString()
return value should be something like sprintf('%d:%d:%d', $this->value / 3600, floor($this->value / 60) % 60, floor($this->value) % 60), but that's give us a correct value without leading zero

@bezhanSalleh also, we're unable to install 1.1.3, because this package version works only with Filament 3 and require to upgrade Filament to ver. 3
    - bezhansalleh/filament-google-analytics 1.1.3 requires filament/widgets ^3.0 -> satisfiable by filament/widgets[v3.0.0, ..., v3.2.119].

@bezhanSalleh Also, I'm not sure that label is correct
Because the average session duration for today in my GA is 12 min, 7 sec but in your package, the RAW value is 33.933530647058824

that means that the shown value may be "Average engagement time per session" but not an "average session duration"

Is it right?

@bezhanSalleh Moreover, we cannot install 1.1.3, because this package version works only with Filament 3 and requires upgrading Filament to ver. 3
    - bezhansalleh/filament-google-analytics 1.1.3 requires filament/widgets ^3.0 -> satisfiable by filament/widgets[v3.0.0, ..., v3.2.119].

man, i need to sleep... ben up closing to 48hrs now...  was in the wrong branch when made the release 🤦🏻♂
should be fine now, just give it a couple of minutes so it gets updated in packagist.

@bezhanSalleh, yes, okay, I'll check it now, but what about session duration? GA returns the value in seconds, but this value is shown incorrectly.
In public function trajectoryValueAsTimeString()  the return value should be something like
sprintf('%d:%d:%d', $this->value / 3600, floor($this->value / 60) % 60, floor($this->value) % 60)

that gives us a correct value but without leading zero

i know, but the api response for duration is in seconds so instead we use Carbon to properly create the required timestamp and peroperly format it.

@bezhanSalleh Also, the average session duration for today is incorrect, it's yesterday's data.   Because the average session duration for today in my GA is 12 min, 7 sec but in your package, the RAW value is 33.933530647058824, that's yesterday's data.

new releases with fix Filam.v2 => 1.1.4 & Filam.v3 => 2.0.3. cheers!

@bezhanSalleh Also, the average session duration for today is incorrect, it's yesterday's data.   Because the average session duration for today in my GA is 12 min, 7 sec but in your package, the RAW value is 33.933530647058824, that's yesterday's data.

new releases with fix Filam.v2 => 1.1.4 & Filam.v3 => 2.0.3. cheers!

Yes, @bezhanSalleh, I so appreciate your work and only two things that I see as a possible bug.
At least the sessionDurationToday() function has today's data inconsistency.
You are getting today as Period::days(1), which gives us from 22 Oct 2024 to 23 Oct 2024, but that's wrong because today is 23 Oct, which means the date is supposed to be 23 Oct—23 Oct 2024. If you use a Period function, it's required to set Today() as the start and end date Period::create(Carbon::today(), Carbon::today()). Also, the same way to get Today used in some other functions.
The second one is function sessionDurationYesterday(), at least this one gives us yesterday as a period from 2024-10-21 to 2024-10-22, which is not right, because yesterday is 22-10-2024—22-10-2024. And yes, same way to get Yesterday used in some other functions.
I offer to replace today's functions with this way (example)
$results = $this->get('averageSessionDuration', 'date', Period::create(Carbon::today(), Carbon::today()));

And yesterday's functions (example)
$results = $this->get('averageSessionDuration', 'date', Period::create(Carbon::yesterday(), Carbon::yesterday()));

@bezhanSalleh Also, the average session duration for today is incorrect, it's yesterday's data.   Because the average session duration for today in my GA is 12 min, 7 sec but in your package, the RAW value is 33.933530647058824, that's yesterday's data.

new releases with fix Filam.v2 => 1.1.4 & Filam.v3 => 2.0.3. cheers!

Yes, @bezhanSalleh, I so appreciate your work and only two things that I see as a possible bug. At least the sessionDurationToday() function has today's data inconsistency. You are getting today as Period::days(1), which gives us from 22 Oct 2024 to 23 Oct 2024, but that's wrong because today is 23 Oct, which means the date is supposed to be 23 Oct—23 Oct 2024. If you use a Period function, it's required to set Today() as the start and end date Period::create(Carbon::today(), Carbon::today()). Also, the same way to get Today used in some other functions. The second one is function sessionDurationYesterday(), at least this one gives us yesterday as a period from 2024-10-21 to 22-10-2024, which is not right, because yesterday is 22 Oct—22 Oct. And yes, same way to get Yesterday used in some other functions.
This way to get today's and yesterday's dates used for both packages for Filament 2 and Filament 3, IDK why exactly this way is used in your function, but maybe I got something wrong?
I offer to replace today's functions with this way (example)
$results = $this->get('averageSessionDuration', 'date', Period::create(Carbon::today(), Carbon::today()));

And yesterday's functions (example)
$results = $this->get('averageSessionDuration', 'date', Period::create(Carbon::yesterday(), Carbon::yesterday()));

yeah, so after i had some shut eye i reviewed it thoroughly.
we are never getting tomorrows data, for instance for today filter we are getting todays and yesterdays. because we need yesterday's data so we could generate the diff and see if its trending up or down.
anyways, so the issue was in the metric diff and both sessions and average session data were inconsistent, so depending on when you setup your analytics and your analytics timezone we need to do a couple of checks for todays filter to see which is there and adjust the trend and time accordingly.
return match (true) {
    ($results->containsOneItem() && ($results->first()['date'])->isYesterday()) => [
        'previous' => $results->first()['value'],
        'result' => 0,
    ],
    ($results->containsOneItem() && ($results->first()['date'])->isToday()) => [
        'previous' => 0,
        'result' => $results->first()['value'],
    ],
    $results->isEmpty() => [
        'previous' => 0,
        'result' => 0,
    ],
    default => [
        'previous' => $results->last()['value'] ?? 0,
        'result' => $results->first()['value'] ?? 0,
    ]
};

now update your composer to make sure you are on the latest version based on your filament version and hopefully this will be it. so let me know. cheers!

@RChutchev i will have a look over the weekend to make sure the others will have the same fix. cause i know the page views and unique visitors do require the same check.

@bezhanSalleh Also, the average session duration for today is incorrect, it's yesterday's data.   Because the average session duration for today in my GA is 12 min, 7 sec but in your package, the RAW value is 33.933530647058824, that's yesterday's data.

new releases with fix Filam.v2 => 1.1.4 & Filam.v3 => 2.0.3. cheers!

Yes, @bezhanSalleh, I so appreciate your work and only two things that I see as a possible bug. At least the sessionDurationToday() function has today's data inconsistency. You are getting today as Period::days(1), which gives us from 22 Oct 2024 to 23 Oct 2024, but that's wrong because today is 23 Oct, which means the date is supposed to be 23 Oct—23 Oct 2024. If you use a Period function, it's required to set Today() as the start and end date Period::create(Carbon::today(), Carbon::today()). Also, the same way to get Today used in some other functions. The second one is function sessionDurationYesterday(), at least this one gives us yesterday as a period from 2024-10-21 to 22-10-2024, which is not right, because yesterday is 22 Oct—22 Oct. And yes, same way to get Yesterday used in some other functions.
This way to get today's and yesterday's dates used for both packages for Filament 2 and Filament 3, IDK why exactly this way is used in your function, but maybe I got something wrong?
I offer to replace today's functions with this way (example)
$results = $this->get('averageSessionDuration', 'date', Period::create(Carbon::today(), Carbon::today()));

And yesterday's functions (example)
$results = $this->get('averageSessionDuration', 'date', Period::create(Carbon::yesterday(), Carbon::yesterday()));

yeah, so after i had some shut eye i reviewed it thoroughly. we are never getting tomorrows data, for instance for today filter we are getting todays and yesterdays. because we need yesterday's data so we could generate the diff and see if its trending up or down. anyways, so the issue was in the metric diff and both sessions and average session data were inconsistent, so depending on when you setup your analytics and your analytics timezone we need to do a couple of checks for todays filter to see which is there and adjust the trend and time accordingly.
return match (true) {
    ($results->containsOneItem() && ($results->first()['date'])->isYesterday()) => [
        'previous' => $results->first()['value'],
        'result' => 0,
    ],
    ($results->containsOneItem() && ($results->first()['date'])->isToday()) => [
        'previous' => 0,
        'result' => $results->first()['value'],
    ],
    $results->isEmpty() => [
        'previous' => 0,
        'result' => 0,
    ],
    default => [
        'previous' => $results->last()['value'] ?? 0,
        'result' => $results->first()['value'] ?? 0,
    ]
};

now update your composer to make sure you are on the latest version based on your filament version and hopefully this will be it. so let me know. cheers!

Yes, I'll test it now. Thank you so much!
I hope now everything will work well.
Also, I opened a pull request to add a Russian language translation, I hope it will be merged, maybe someone else requires it too

https://github.com/user-attachments/assets/29d5f8ff-9e4f-4c4a-932f-b2a3f9c69070
in the above screenshots, you can see we don't have anything for 24, so now the sessions and avg. session duration will have the correct data. it shows 00:00:00 for today but still gets the result for yesterday 00:08:03 and calculates the diff.
I had a couple of days off, that's why i have been able to respond and check this quickly. but i will merge it when i do the fixes in the next release. cheers!

Screen.Recording.2024-10-24.at.3.03.02.AM.mov
@RChutchev as you can see in the above screenshots, you can see we don't have anything for 24, so now the sessions and avg. session duration will have the correct data. it shows 00:00:00 for today but still gets the result for yesterday 00:08:03 and calculates the diff. I had a couple of days off, that's why i have been able to respond and check this quickly. but i will merge it when i do the fixes in the next release. cheers!

Yes, right, I just updated the package to 1.2.0 for local env, and yes, it now shows me 0 for empty values for sessions and average. session duration, and when some data comes from GA I am sure data will also be shown.
Yes, looks like now diff for the session duration info works well, thanks!
Okay, that's good, thank you so much for the quick fixes.
Okay, thanks, cheers!

@bezhanSalleh, I've tested the last released version, and it looks like the "sessions count" and the "average sessions duration" for today do not work well, and always show 0 as values whatever Google Analytics has value.

That might be the issue with your cache setting, because the base spatie package caches the query result for 24hrs.

That might be the issue with your cache setting, because the base spatie package caches the query result for 24hrs. So you might wanna adjust that according to your needs.

Thanks a lot, yep, I forgot about the Spatie package cache.
Now that works great for me.


Cow: Watch melsa.com.sa

Cow requests the watch of the watch_keyword melsa\.com\.sa. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

melsa\.com\.sa has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by VLAZ in Charcoal HQ


Example of Lazy Implementation

This is an example of lazy implementation, with also an example in the example project.

@fassko could you review this?

@iDevid Can you please explain the need of such feature? Thanks!

@fassko when I use with hidden binding in stack views for example. Without Lazy at startup all the binded views will be showed, then with animation they disappear do tue the data model binding. It is a bit ugly.

To be honest I'm a bit lost. Can you explain once again. An example would help a lot. Thanks!
Can your need be a wrapper around this library. We aim to have this library as lightweight as possible.

If you run the example app, I added an example of that

Can I send you an email with a real app video example? @fassko

@fassko


Request access for Pillow

Hi all, with the ongoing work that's going on for porting pillow to free-threaded Python, it makes sense to us that it uploads nightly wheels as well, since it's a dependency for scikit-image, which is already in the list of projects that do so.
Pillow issue: https://github.com/python-pillow/Pillow/issues/8199
cc @hugovk

Thanks 🙏 I am +1.
You know the drill now is it comes through 😉

Pillow would be great to have!

Great! @hugovk Can you please complete the check list? (taken from the Cython issue)

[ ] Create an account on Anaconda Cloud
[ ] Reply here with the link to your account
[ ] Make a new Anaconda Cloud API token with permissions described in https://scientific-python.org/specs/spec-0004/#process-for-adding-new-projects
[ ] Save the API token as a repo GitHub Actions secret named ANACONDA_ORG_UPLOAD_TOKEN

A set of pillow wheels for the project to be created can be found here.

https://anaconda.org/radarhere

Thanks folks, I will do the creation steps later today and ping you here.

You are all set @hugovk @radarhere 🚀
Thanks @lysnikolaou for the work in the background.
Let us know if you need any support 😃

https://anaconda.org/scientific-python-nightly-wheels/pillow

Thanks @hugovk @lysnikolaou @radarhere and @tupui for moving fast on this!
@hugovk @radarhere If you'd also like to use the scientific/upload-nightly-action GitHub Action please check out the action repo's README. If you need to collect wheels from different CI jobs, consider creating a new GitHub Actions workflow with logic similar to matplotlib's or Awkward's.

Please could you also @aclark4life?
https://anaconda.org/aclark
re: https://github.com/python-pillow/Pillow/pull/8236#issuecomment-2233050364

Please could you also @aclark4life?
https://anaconda.org/aclark
re: python-pillow/Pillow#8236 (comment)

@lysnikolaou Thank you!

Done folks 😃


Spanner connector

Ability to use GSP Spanner as a database
Engine PR: https://github.com/finos/legend-engine/pull/809

Thanks for the work @roasher and sorry about the late response, we weren't so sure the backend change got merged. I'll merge this soon, and will add a test later.


Add UI for the reverse- commands.

Although it's fun to use short-cuts, it's way cooler to use UI, and UI can give you feedback about the running state, which would be nice.

These features has been implemented, therefore closing this issue.


Enabling DDS proxy conflicts with other build options

Describe the bug
Build nanomq with:

-DBUILD_DDS_PROXY=ON -DENABLE_RULE_ENGINE=ON ...
-DBUILD_DDS_PROXY=ON -DBUILD_ZMQ_GATEWAY=ON ...

Expected behavior
Successful build.
Actual Behavior
Build failed with:
       > duplicate symbol '_fatal' in:
       >     nanomq_cli/CMakeFiles/nanomq_cli.dir/dds2mqtt/mqtt_client.c.o
       >     nanomq_cli/CMakeFiles/nanomq_cli.dir/rule_ctrl.c.o

or
       > duplicate symbol '_client_publish' in:
       >     nanomq_cli/CMakeFiles/nanomq_cli.dir/dds2mqtt/mqtt_client.c.o
       >     nanomq_cli/CMakeFiles/nanomq_cli.dir/zmq_gateway.c.o

Environment Details

NanoMQ 0.5.15
NixOS

Could you plz try the updated master branch on NixOS to see if this has been fixed?

Could you plz try the updated master branch on NixOS to see if this has been fixed?

Yes, build is OK now. Thanks! Already merged into nixpkgs.


Improve Custom Tooltip .NET

Now when https://github.com/apexcharts/apexcharts.js/issues/4869 has been implemented we should investigate if we can improve the .Net custom tooltip. With this change we should be able generate the tooltip without relying on the mouse over event to trigger the tooltip generation.

Breaking Change
The .Net Tooltip now uses the apexcharts.js tooltip function.
The syntax  is the same but the tooltip is generated in the apexcharts tooltip container with the apexcharts.js css.
Also we no longer rely on the event 'OnPointEnterEvent' and therefore we don't need to automatically add markers to line charts.
Check https://apexcharts.github.io/Blazor-ApexCharts/features/tooltip-dotnet for samples

fixed in v5.0.0


Fix stderr handling

The stderr stream is not captured in the latest version, resulting in it being printed in tox's output. This is fixed by simply redirecting stderr to os.devnull.

Codecov Report

Merging #21 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master     #21   +/-   ##
======================================
  Coverage    87.8%   87.8%
======================================
  Files           1       1
  Lines          41      41
  Branches        6       6
======================================
  Hits           36      36
  Misses          3       3
  Partials        2       2

Impacted Files
Coverage Δ

src/tox_venv/hooks.py
87.8% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

subprocess.DEVNULL is only available on Python 3.3+, so we need to redirect to STDOUT instead. This is acceptable since we only parse STDOUT if the process doesn't error out.


Added eventtrigger for string implmentation

What kind of change does this PR introduce?

Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?

👷 Deploy Preview for regal-platypus-7fc228 processing.

Name
Link

🔨 Latest commit
ce99a9697f39625e8cba9faaab3f9bd934d1f38d

🔍 Latest deploy log
https://app.netlify.com/sites/regal-platypus-7fc228/deploys/651f10582ff5710008d32b2e


HTTP and WebSockets?

Was HTTP and WebSockets considering when choosing raw TCP/IP for RSMP?
The site would run an http server, responding to commands. A supervisor system could subscribe to data and events using WebSockets. The site would push data when available.
https://en.wikipedia.org/wiki/WebSocket

I don't think so. The raw TCP/IP was chosen back in early 2011 with the release of RSMP 3.0 At that time the RFC for WebSockets was not released yet.


Build fails on Ubuntu 20.04

Bevy requires alsa (provided by libsdl2-dev on Ubuntu) to be compiled
on Linux based platforms as mention by the following error:

Error Log
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: "`\"pkg-config\" \"--libs\" \"--cflags\" \"alsa\"` did not exit successfully: exit code: 1\n--- stderr\nPackage alsa was not found in the pkg-config search path.\nPerhaps you should add the directory containing `alsa.pc\'\nto the PKG_CONFIG_PATH environment variable\nNo package \'alsa\' found\n"', /home/r1walz/.cargo/registry/src/github.com-1ecc6299db9ec823/alsa-sys-0.1.2/build.rs:4:5

But I was unable to find this in the docs or anywhere else. Please, investigate and
provide a list of such dependencies for different platforms.

It's pretty well documented already https://bevyengine.org/learn/book/getting-started/setup/
(there's a link to this page in the readme)

This could probably be made a bit clearer in the README then

I get a similar failure but for libudev. The Linux dependencies document does not include either libudev-dev or libsdl2-dev.

Documented in Linux dependencies now <3 Credit to @MinerSebas.


No windows support?

Hi, great that there is an SDK all done but how can I use my Windows based dev machine to compile code for the Pico?

Of course it does. You read in: https://datasheets.raspberrypi.org/pico/getting_started_with_pico.pdf Chapter 8.1

Of course it does. You read in: https://datasheets.raspberrypi.org/pico/getting_started_with_pico.pdf Chapter 8.1

Cheers! I thought I'd been through it all, wood for the trees, thank you.

Cheers! I thought I'd been through it all, wood for the trees, thank you.


Consider replacing FocusTrapArea

The next version of Flutter removes the FocusTrapArea widget. I'm not sure if flutter team made a replacement for it. In any case consider replacing it with another solution.
Testing Flutter_Pinput with Flutter beta channel crashes the build and produces the following error:
: Error: The method 'FocusTrapArea' isn't defined for the class '_PinputState'.
../…/src/pinput_state.dart:339
- '_PinputState' is from 'package:pinput/src/pinput.dart' ('../../../.pub-cache/hosted/pub.dev/pinput-2.2.21/lib/src/pinput.dart').
Try correcting the name to the name of an existing method, or defining a method named 'FocusTrapArea'.
      child: FocusTrapArea(
             ^^^^^^^^^^^^^

Hey @KristijanZic, that's a well known issue
Here is the patch and you can directly depend on it if you don't want to use Flutter's stable channel.
  pinput:
   git:
    url: https://github.com/Tkko/Flutter_Pinput
    ref: dev

Once Flutter team removes FocusTrapArea from stable I'll merge dev branch to master.

FocusTrapArea has been removed from stable yesterday.

Flutter 3.7.0 • channel stable • https://github.com/flutter/flutter.git
Framework • revision b06b8b2710 (30 hours ago) • 2023-01-23 16:55:55 -0800
Engine • revision b24591ed32
Tools • Dart 2.19.0 • DevTools 2.20.1
I am on the above version of flutter and FocusTrapArea has been removed in the stable so kindly consider replacing it.

Hey guys, the update will be ready in couple of minutes

Thanks for prompt response. Please update as soon as possible.

Hey guys, the update will be ready in couple of minutes

I got this error on ci-azure deploy, but when i build appbundle on my pc, there is no problem. will this be able to be fixed?

Still has issue of FocusTrapArea on pinput version 2.2.21.
But the given patch working fine.
 pinput:
   git:
    url: https://github.com/Tkko/Flutter_Pinput
    ref: dev

Here you go guys, the update is live on pub
Version 2.2.22

I don't know while I have added pinput with git, url and ref
but I'm getting this errors

Hey @AliKarimiENT, this error is't related to this issue, please create a new issue and provide

Error logs
flutter --version
Did you change anything in android/app/build.gradle ?
Did you change anything in  android/build.gradle ?

Because project depends on pinput >=2.2.23 which requires Flutter SDK version >=3.7.0, version solving failed.
I am currently on the beta channel 3.7.0-1.5.pre
Shouldn't it be working there?

Hey @kamami I know it's  bit late but do you have the same issue?


Config changes to reflect the default branch from master to main. Please merge to complete the default branch renaming job.

Auto branch renaming content.

Docs Build status updates of commit ffde207:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

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


use Pm_GetErrorText for errors, export ErrMinBuffer and ErrMaxBuffer, …

… and return errors from Stream factories if stream is unavailable

LGTM, @briansorahan, have you signed a Google CLA before? I cannot find your name in the records. If not, could you please take a look at https://cla.developers.google.com/clas?

Done -_-

Thanks!


pretrained model

Thanks for open source. Some questions:
Should pretrained model in phase 1(Full-Sentence Pre-training) be a finetuned model for phase 2(Simultaneous Translation Fine-Tuning). For example, use a parameter “--restore-file” in fairseq to train the model phrase 2?

Yes, the model of the first state is the begining of the second state


With @WebService(wsdlLocation="foo.wsdl") an autogenerated WSDL is served instead of the foo.wsdl

In https://github.com/quarkiverse/quarkus-cxf/pull/543/files#diff-0cd8e0d8aad8318a25f237e3d52a9a3c48ded4413f1258bb80d14160b1952999R30-R37
I had to add the @Policy annotations pointing at policy XML fragments, because wsdlLocation = "TrustHelloService.wsdl" was not honored and the wsdl() test was failing.
Note that the wsdlLocation attribute works as expected with @WebServiceProvider - see https://github.com/quarkiverse/quarkus-cxf/pull/543/files#diff-6580ccf22a10f9fdfe9c452e5e75c79f4d535711759de0252c044866be04bd9eR35-R48 and the underlying SampleSTS. There the ws-trust-1.4-service.wsdl is served as is.
I wonder whether this behavior is compliant with the spec?

I have added a reproducer in https://github.com/quarkiverse/quarkus-cxf/pull/766/files#diff-142ff1a53c949afbb7d1f95c14c4365e26eabe97c112f8ecd4ee3e6a59b2ec15R48-R71
@ffang do you happen to have any idea whether @WebServiceProvider(wsdlLocation="foo.wsdl") and @WebService(wsdlLocation="foo.wsdl") behaving differently in Quarkus CXF is a bug or if it is the same with stock CXF?
With @WebServiceProvider(wsdlLocation="foo.wsdl") I see my custom WSDL document with <!-- my custom comment --> being served, but with @WebService(wsdlLocation="foo.wsdl") an autogenerated WSDL is served.

The second commit in https://github.com/quarkiverse/quarkus-cxf/pull/1087/commits makes the test pass thanks to
quarkus.cxf.endpoint."/wsdllocation".wsdl = wsdllocation/HelloService.wsdl

in application.properties.
@ffang I still wonder whether the the need to do this for @WebService(wsdlLocation="foo.wsdl") is a feature or a bug, given that no wsdl setting in application.properties is needed for @WebServiceProvider(wsdlLocation="foo.wsdl". Do you happen to have any opinion on that?


Preparation of Attached Deployment Artifacts

Problem Statement
To enable the deployment of attached files, they need to be prepared for deployment.
Issue Dependencies
Depends on: #1
References
OpenTOSCA Tutorial
Expected Behaviour
A TOSCA ServiceTemplate that enables running the attached artifacts must be generated.
Initially, Java and Python3 projects provided as zips shall be supported.
Winery shall be used to generate the deployment model.
Thus, ArtifactTemplates and ServiceTemplates must be generated via Winery's API.
Tasks

[ ] Familiarize yourself with the existing OpenTosca utility code
[ ] Analyze general requirements of Java and Python3 applications (e.g., requirements files, ...)
[ ] Enable automatic generation of a deployable TOSCA Service Template based on the attached artifacts (for now only one Artifact per service task shall be supported):

[ ] Add a drop-down menu to select the artifact type for attached artifacts, e.g., Python3.7 for a zip file containing the Python application or WAR for a packaged Java application
[ ] Retrieve the available artifact types for the drop-down menu from Winery. Use the following endpoint and extract the ids: GET @ http://localhost:8080/winery/artifacttypes/?includeVersions=true Result Example (click to expand)[ { "id" : "AMQP-Driver_Java11-w1", "name" : "AMQP-Driver_Java11-w1", "namespace" : "http://opentosca.org/driverinjection/artifacttypes", "qName" : "{http://opentosca.org/driverinjection/artifacttypes}AMQP-Driver_Java11-w1", "version" : { "componentVersion" : "Java11", "wineryVersion" : 1, "workInProgressVersion" : 0, "currentVersion" : false, "latestVersion" : false, "releasable" : false, "editable" : false } }, { "id" : "AMQP-Driver_Python3.8-w1", "name" : "AMQP-Driver_Python3.8-w1", "namespace" : "http://opentosca.org/driverinjection/artifacttypes", "qName" : "{http://opentosca.org/driverinjection/artifacttypes}AMQP-Driver_Python3.8-w1", "version" : { "componentVersion" : "Python3.8", "wineryVersion" : 1, "workInProgressVersion" : 0, "currentVersion" : false, "latestVersion" : false, "releasable" : false, "editable" : false } } ]
[ ] Add an upload button, which triggers the upload of the attached artifact to Winery
[ ] Derive the required request to create an ArtifactTemplate within Winery based on the artifact type and the retrieved blob POST @ http://localhost:8080/winery/artifacttemplates/
[ ]  Generate a new ServiceTemplate using Winery`s API (POST @ http://localhost:8080/winery/servicetemplates/) using the activity ID, as well as the activity label, as the ID of the ServiceTemplate. Use a separate service template per service task.
[ ] Add a corresponding NodeTemplate representing the artifact within the ServiceTemplate and attach the created ArtifactTemplate as DeploymentArtifact to the NodeTemplate. No Meta Service templates are required, instead add an empty template and add the required node templates. Example Request (click to expand){"documentation":[],"any":[],"otherAttributes":{},"relationshipTemplates":[],"nodeTemplates":[{"documentation":[],"any":[],"otherAttributes":{"{http://www.opentosca.org/winery/extensions/tosca/2013/02/12}x":325,"{http://www.opentosca.org/winery/extensions/tosca/2013/02/12}y":358},"properties":{"propertyType":"KV","kvproperties":{"volume_id":"","snapshot_id":""},"elementName":"properties","namespace":"http://opentosca.org/nodetypes/propertiesdefinition/winery"},"id":"BlockStorage_0","type":"{http://docs.oasis-open.org/tosca/ToscaNormativeTypes/nodetypes}BlockStorage","name":"BlockStorage","minInstances":1,"maxInstances":1,"x":325,"y":358,"capabilities":[],"requirements":[],"deploymentArtifacts":[{"documentation":[],"any":[],"otherAttributes":{},"name":"trest","artifactType":"{http://docs.oasis-open.org/tosca/ns/2011/12/ToscaBaseTypes}ScriptArtifact","artifactRef":"{http://opentosca.org/artifacttemplates}ApacheApp_install-w1"}],"policies":null}]}  The required NodeType can be derived from the type of the artifact, which can be hardcoded as a map in the workflow modeler, e.g., PythonApplication based on the type Python3.7. (Example code)
Example URL derived from generating the ServiceTemplate
[ ] Add URL to service template as property of the activity (Example)

[ ] Add tests verifying the functionality

refined tasks according to questions

Erste Schätzung: 25

Vorherige Schätzung: 13


Good News! gcloud will support interactive shell mode.

To all kube-prompt's users
In public alpha version of gcloud, interactive shell mode is added. This feature provides interactive completion of kubectl's subcommands, not to mention a gcloud's subcommands (See https://cloudplatform.googleblog.com/2018/03/introducing-GCPs-new-interactive-CLI.html
for more details)
Some features still lack but it will be improved in the future (ex: kube-prompt and kube-shell provides feature to complete kubernetes resources such as pods, deployments and so on). It's great news, but it means the worth of kube-prompt will be disappear anymore. Therefore I will not actively develop kube-prompt.
Thanks.

Hi!
It's your project and I totally understand you feeling this way, but just to chime in that not all kubernetes users manage it via GKE, so for some people the Google Cloud SDK is not an option.
This kube-prompt is a really nice project and alternative so perhaps it's worth it to keep it going, even in maintenance/merge pull requests mode.
In any case, thanks!!

First, thanks for the project. As @antoniomo said, not everyone uses google cloud. The team I work on actually have kubernetes deployed on top of AWS so this project is very helpful. Please don't fully abandon.

I've just tried gcloud interactive. Its kubectl support didn't even suggest anything after kubectl get. That's a no-go for me, I'd rather stick to bash completion.

Thanks for replying. I'm pleased you still use kube-prompt.
I also feel this tool is really convenient to operate kubernetes resources, but I don't have enough time to replying issues, checking PRs and updating version of kubernetes/client-go. So I'm looking for co-maintainers. Please check https://github.com/c-bata/kube-prompt/issues/28 for more details.


Create new empty database

Try to create a new empty database, plan is to generate many databases.
But have problems to write a new dbc file. Short testcode
import cantools
db = cantools.db
db.Bus('test', baudrate=500000)
cantools.db.dump_file(db, 'test.dbc')

But this gives the traceback
Traceback (most recent call last):
  File "tmp.py", line 7, in <module>
    cantools.db.dump_file(db, 'test.dbc')
  File "<pythonpath>\site-packages\cantools\database\__init__.py", line 247, in dump_file
    output = database.as_dbc_string(sort_signals=sort_signals)
AttributeError: module 'cantools.database' has no attribute 'as_dbc_string'

Maybe not the correct way to do this, and maybe not ment to create databases with this tool?

import cantools
db = cantools.database.Database()
cantools.database.dump_file(db, 'test.dbc')

should work


feat: bump golang version to 1.17.6 [EE-2350]

Closes https://github.com/portainer/portainer/issues/6342


Add necessary elements to generate the deployment yaml

Issue #, if available:
Description of changes:
Added necessary pieces for building the deployment yaml for tinkerbell and added a basic unit test for it
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


Use Scalacheck for testing pgn parser

@johnynek recommendation

I recommend using scalacheck to generate your AST, convert that to string, and then make sure parsing it back to the AST gives you exactly the right thing.

Can someone please assign me to this!

Do you mind explaining this a little more? Why do we an AST to test PGN parser?

So, The idea is we want to generate valid PGN string and parse it using scalacheck. And the way to do it is generate it's AST a.k. San.
We are already using this technique in some places:
BitboardTest, ByColorTest.
But I'm not sure what is the best way to generate those PGN, like if we use legalMoves to generate those, it can be slow, if not the generated PGN can be illegal (but still valid). And do we really care if generated PGNs are legal or not.

close because We have this: https://github.com/lichess-org/scalachess/blob/master/test-kit/src/test/scala/format/pgn/ParserCheck.scala


Build fails when using jax NGC image

Hello,
Thanks so much for making this project, it looks like really exciting stuff. I'm currently having some trouble installing the library and can't quite figure out what's going wrong. For context I am using an L40 GPU with cuda 12.2 installed and driver version 535.161, and I pulled the following jax NGC image: nvcr.io/nvidia/jax:23.10-py3. When I run:
NVTE_FRAMEWORK=jax
pip install git+https://github.com/NVIDIA/TransformerEngine.git@stable

I get the following output:
Collecting git+https://github.com/NVIDIA/TransformerEngine.git@stable
  Cloning https://github.com/NVIDIA/TransformerEngine.git (to revision stable) to /tmp/pip-req-build-wqpvid2m
  Running command git clone --filter=blob:none --quiet https://github.com/NVIDIA/TransformerEngine.git /tmp/pip-req-build-wqpvid2m
  Running command git checkout -b stable --track origin/stable
  Switched to a new branch 'stable'
  Branch 'stable' set up to track remote branch 'stable' from 'origin'.
  Resolved https://github.com/NVIDIA/TransformerEngine.git to commit 6a9edc38bf9b941b7d369af5103fa8fe0b121d61
  Running command git submodule update --init --recursive -q
  Preparing metadata (setup.py) ... done
Requirement already satisfied: flax>=0.7.1 in /usr/local/lib/python3.10/dist-packages (from transformer-engine==1.5.0+6a9edc3) (0.7.4)
Requirement already satisfied: jax in /usr/local/lib/python3.10/dist-packages (from transformer-engine==1.5.0+6a9edc3) (0.4.17.dev20231020)
Collecting pydantic (from transformer-engine==1.5.0+6a9edc3)
  Using cached pydantic-2.6.4-py3-none-any.whl.metadata (85 kB)
Requirement already satisfied: numpy>=1.12 in /usr/local/lib/python3.10/dist-packages (from flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (1.26.1)
Requirement already satisfied: msgpack in /usr/local/lib/python3.10/dist-packages (from flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (1.0.7)
Requirement already satisfied: optax in /usr/local/lib/python3.10/dist-packages (from flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (0.1.7)
Requirement already satisfied: orbax-checkpoint in /usr/local/lib/python3.10/dist-packages (from flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (0.4.1)
Requirement already satisfied: tensorstore in /usr/local/lib/python3.10/dist-packages (from flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (0.1.46)
Requirement already satisfied: rich>=11.1 in /usr/local/lib/python3.10/dist-packages (from flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (13.6.0)
Requirement already satisfied: typing-extensions>=4.2 in /usr/local/lib/python3.10/dist-packages (from flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (4.8.0)
Requirement already satisfied: PyYAML>=5.4.1 in /usr/lib/python3/dist-packages (from flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (5.4.1)
Requirement already satisfied: ml-dtypes>=0.2.0 in /usr/local/lib/python3.10/dist-packages (from jax->transformer-engine==1.5.0+6a9edc3) (0.3.1)
Requirement already satisfied: opt-einsum in /usr/local/lib/python3.10/dist-packages (from jax->transformer-engine==1.5.0+6a9edc3) (3.3.0)
Requirement already satisfied: scipy>=1.7 in /usr/local/lib/python3.10/dist-packages (from jax->transformer-engine==1.5.0+6a9edc3) (1.11.3)
Collecting annotated-types>=0.4.0 (from pydantic->transformer-engine==1.5.0+6a9edc3)
  Using cached annotated_types-0.6.0-py3-none-any.whl.metadata (12 kB)
Collecting pydantic-core==2.16.3 (from pydantic->transformer-engine==1.5.0+6a9edc3)
  Using cached pydantic_core-2.16.3-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (6.5 kB)
Requirement already satisfied: markdown-it-py>=2.2.0 in /usr/local/lib/python3.10/dist-packages (from rich>=11.1->flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (3.0.0)
Requirement already satisfied: pygments<3.0.0,>=2.13.0 in /usr/local/lib/python3.10/dist-packages (from rich>=11.1->flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (2.16.1)
Requirement already satisfied: absl-py>=0.7.1 in /usr/local/lib/python3.10/dist-packages (from optax->flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (2.0.0)
Requirement already satisfied: chex>=0.1.5 in /usr/local/lib/python3.10/dist-packages (from optax->flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (0.1.84)
Requirement already satisfied: jaxlib>=0.1.37 in /usr/local/lib/python3.10/dist-packages (from optax->flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (0.4.17.dev20231020)
Requirement already satisfied: etils[epath,epy] in /usr/local/lib/python3.10/dist-packages (from orbax-checkpoint->flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (1.5.1)
Requirement already satisfied: nest_asyncio in /usr/local/lib/python3.10/dist-packages (from orbax-checkpoint->flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (1.5.8)
Requirement already satisfied: protobuf in /usr/local/lib/python3.10/dist-packages (from orbax-checkpoint->flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (4.24.4)
Requirement already satisfied: toolz>=0.9.0 in /usr/local/lib/python3.10/dist-packages (from chex>=0.1.5->optax->flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (0.12.0)
Requirement already satisfied: mdurl~=0.1 in /usr/local/lib/python3.10/dist-packages (from markdown-it-py>=2.2.0->rich>=11.1->flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (0.1.2)
Requirement already satisfied: fsspec in /usr/local/lib/python3.10/dist-packages (from etils[epath,epy]->orbax-checkpoint->flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (2023.9.2)
Requirement already satisfied: importlib_resources in /usr/local/lib/python3.10/dist-packages (from etils[epath,epy]->orbax-checkpoint->flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (6.1.0)
Requirement already satisfied: zipp in /usr/local/lib/python3.10/dist-packages (from etils[epath,epy]->orbax-checkpoint->flax>=0.7.1->transformer-engine==1.5.0+6a9edc3) (3.17.0)
Using cached pydantic-2.6.4-py3-none-any.whl (394 kB)
Using cached pydantic_core-2.16.3-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (2.2 MB)
Using cached annotated_types-0.6.0-py3-none-any.whl (12 kB)
Building wheels for collected packages: transformer-engine
  Building wheel for transformer-engine (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [190 lines of output]
      /usr/lib/python3/dist-packages/setuptools/installer.py:27: SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements should be satisfied by a PEP 517 installer.
        warnings.warn(
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build/lib.linux-x86_64-3.10
      creating build/lib.linux-x86_64-3.10/transformer_engine
      copying transformer_engine/__init__.py -> build/lib.linux-x86_64-3.10/transformer_engine
      copying transformer_engine/_version.py -> build/lib.linux-x86_64-3.10/transformer_engine
      creating build/lib.linux-x86_64-3.10/transformer_engine/common
      copying transformer_engine/common/__init__.py -> build/lib.linux-x86_64-3.10/transformer_engine/common
      copying transformer_engine/common/utils.py -> build/lib.linux-x86_64-3.10/transformer_engine/common
      creating build/lib.linux-x86_64-3.10/transformer_engine/jax
      copying transformer_engine/jax/__init__.py -> build/lib.linux-x86_64-3.10/transformer_engine/jax
      copying transformer_engine/jax/dot.py -> build/lib.linux-x86_64-3.10/transformer_engine/jax
      copying transformer_engine/jax/fp8.py -> build/lib.linux-x86_64-3.10/transformer_engine/jax
      copying transformer_engine/jax/layernorm.py -> build/lib.linux-x86_64-3.10/transformer_engine/jax
      copying transformer_engine/jax/mlp.py -> build/lib.linux-x86_64-3.10/transformer_engine/jax
      copying transformer_engine/jax/sharding.py -> build/lib.linux-x86_64-3.10/transformer_engine/jax
      copying transformer_engine/jax/softmax.py -> build/lib.linux-x86_64-3.10/transformer_engine/jax
      copying transformer_engine/jax/cpp_extensions.py -> build/lib.linux-x86_64-3.10/transformer_engine/jax
      copying transformer_engine/jax/fused_attn.py -> build/lib.linux-x86_64-3.10/transformer_engine/jax
      creating build/lib.linux-x86_64-3.10/transformer_engine/paddle
      copying transformer_engine/paddle/__init__.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle
      copying transformer_engine/paddle/constants.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle
      copying transformer_engine/paddle/cpp_extensions.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle
      copying transformer_engine/paddle/distributed.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle
      copying transformer_engine/paddle/fp8.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle
      copying transformer_engine/paddle/fp8_buffer.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle
      copying transformer_engine/paddle/profile.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle
      copying transformer_engine/paddle/recompute.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle
      copying transformer_engine/paddle/utils.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle
      creating build/lib.linux-x86_64-3.10/transformer_engine/pytorch
      copying transformer_engine/pytorch/__init__.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch
      copying transformer_engine/pytorch/constants.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch
      copying transformer_engine/pytorch/cpu_offload.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch
      copying transformer_engine/pytorch/distributed.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch
      copying transformer_engine/pytorch/export.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch
      copying transformer_engine/pytorch/float8_tensor.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch
      copying transformer_engine/pytorch/fp8.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch
      copying transformer_engine/pytorch/jit.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch
      copying transformer_engine/pytorch/numerics_debug.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch
      copying transformer_engine/pytorch/softmax.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch
      copying transformer_engine/pytorch/te_onnx_extensions.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch
      copying transformer_engine/pytorch/utils.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch
      copying transformer_engine/pytorch/attention.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch
      copying transformer_engine/pytorch/transformer.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch
      creating build/lib.linux-x86_64-3.10/transformer_engine/common/recipe
      copying transformer_engine/common/recipe/__init__.py -> build/lib.linux-x86_64-3.10/transformer_engine/common/recipe
      creating build/lib.linux-x86_64-3.10/transformer_engine/jax/flax
      copying transformer_engine/jax/flax/__init__.py -> build/lib.linux-x86_64-3.10/transformer_engine/jax/flax
      copying transformer_engine/jax/flax/module.py -> build/lib.linux-x86_64-3.10/transformer_engine/jax/flax
      copying transformer_engine/jax/flax/transformer.py -> build/lib.linux-x86_64-3.10/transformer_engine/jax/flax
      creating build/lib.linux-x86_64-3.10/transformer_engine/jax/praxis
      copying transformer_engine/jax/praxis/__init__.py -> build/lib.linux-x86_64-3.10/transformer_engine/jax/praxis
      copying transformer_engine/jax/praxis/module.py -> build/lib.linux-x86_64-3.10/transformer_engine/jax/praxis
      copying transformer_engine/jax/praxis/transformer.py -> build/lib.linux-x86_64-3.10/transformer_engine/jax/praxis
      creating build/lib.linux-x86_64-3.10/transformer_engine/paddle/layer
      copying transformer_engine/paddle/layer/__init__.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle/layer
      copying transformer_engine/paddle/layer/attention.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle/layer
      copying transformer_engine/paddle/layer/base.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle/layer
      copying transformer_engine/paddle/layer/layernorm.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle/layer
      copying transformer_engine/paddle/layer/layernorm_linear.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle/layer
      copying transformer_engine/paddle/layer/layernorm_mlp.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle/layer
      copying transformer_engine/paddle/layer/linear.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle/layer
      copying transformer_engine/paddle/layer/rmsnorm.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle/layer
      copying transformer_engine/paddle/layer/softmax.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle/layer
      copying transformer_engine/paddle/layer/transformer.py -> build/lib.linux-x86_64-3.10/transformer_engine/paddle/layer
      creating build/lib.linux-x86_64-3.10/transformer_engine/pytorch/cpp_extensions
      copying transformer_engine/pytorch/cpp_extensions/__init__.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch/cpp_extensions
      copying transformer_engine/pytorch/cpp_extensions/activation.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch/cpp_extensions
      copying transformer_engine/pytorch/cpp_extensions/cast.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch/cpp_extensions
      copying transformer_engine/pytorch/cpp_extensions/fused_attn.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch/cpp_extensions
      copying transformer_engine/pytorch/cpp_extensions/normalization.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch/cpp_extensions
      copying transformer_engine/pytorch/cpp_extensions/transpose.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch/cpp_extensions
      copying transformer_engine/pytorch/cpp_extensions/gemm.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch/cpp_extensions
      creating build/lib.linux-x86_64-3.10/transformer_engine/pytorch/module
      copying transformer_engine/pytorch/module/__init__.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch/module
      copying transformer_engine/pytorch/module/_common.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch/module
      copying transformer_engine/pytorch/module/layernorm.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch/module
      copying transformer_engine/pytorch/module/rmsnorm.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch/module
      copying transformer_engine/pytorch/module/base.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch/module
      copying transformer_engine/pytorch/module/layernorm_linear.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch/module
      copying transformer_engine/pytorch/module/layernorm_mlp.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch/module
      copying transformer_engine/pytorch/module/linear.py -> build/lib.linux-x86_64-3.10/transformer_engine/pytorch/module
      running build_ext
      Building CMake extension transformer_engine
      Running command /usr/bin/cmake -S /tmp/pip-req-build-wqpvid2m/transformer_engine -B /tmp/pip-req-build-wqpvid2m/build/cmake -DPython_EXECUTABLE=/usr/bin/python3 -DPython_INCLUDE_DIR=/usr/include/python3.10 -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/tmp/pip-req-build-wqpvid2m/build/lib.linux-x86_64-3.10 -DENABLE_JAX=ON -Dpybind11_DIR=/tmp/pip-req-build-wqpvid2m/.eggs/pybind11-2.12.0-py3.10.egg/pybind11/share/cmake/pybind11
      -- The CUDA compiler identification is NVIDIA 12.2.91
      -- The CXX compiler identification is GNU 11.4.0
      -- Detecting CUDA compiler ABI info
      -- Detecting CUDA compiler ABI info - done
      -- Check for working CUDA compiler: /usr/local/cuda/bin/nvcc - skipped
      -- Detecting CUDA compile features
      -- Detecting CUDA compile features - done
      -- Detecting CXX compiler ABI info
      -- Detecting CXX compiler ABI info - done
      -- Check for working CXX compiler: /usr/bin/c++ - skipped
      -- Detecting CXX compile features
      -- Detecting CXX compile features - done
      -- Found CUDAToolkit: /usr/local/cuda/include (found version "12.2.91")
      -- Looking for C++ include pthread.h
      -- Looking for C++ include pthread.h - found
      -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
      -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
      -- Found Threads: TRUE
      -- cudnn found at /usr/lib/x86_64-linux-gnu/libcudnn.so.
      CMake Warning (dev) at /usr/share/cmake-3.22/Modules/FindPackageHandleStandardArgs.cmake:438 (message):
        The package name passed to `find_package_handle_standard_args` (LIBRARY)
        does not match the name of the calling package (CUDNN).  This can lead to
        problems in calling code that expects `find_package` result variables
        (e.g., `_FOUND`) to follow a certain pattern.
      Call Stack (most recent call first):
        cmake/FindCUDNN.cmake:44 (find_package_handle_standard_args)
        CMakeLists.txt:24 (find_package)
      This warning is for project developers.  Use -Wno-dev to suppress it.

      -- Found LIBRARY: /usr/include
      -- cuDNN: /usr/lib/x86_64-linux-gnu/libcudnn.so
      -- cuDNN: /usr/include
      -- cudnn_adv_infer found at /usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.
      -- cudnn_adv_train found at /usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.
      -- cudnn_cnn_infer found at /usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.
      -- cudnn_cnn_train found at /usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.
      -- cudnn_ops_infer found at /usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.
      -- cudnn_ops_train found at /usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.
      -- Found Python: /usr/bin/python3 (found version "3.10.12") found components: Interpreter Development.Module
      -- JAX support: ON
      -- Performing Test HAS_FLTO
      -- Performing Test HAS_FLTO - Success
      -- Found pybind11: /tmp/pip-req-build-wqpvid2m/.eggs/pybind11-2.12.0-py3.10.egg/pybind11/include (found version "2.12.0")
      -- Configuring done
      -- Generating done
      -- Build files have been written to: /tmp/pip-req-build-wqpvid2m/build/cmake
      Running command /usr/bin/cmake --build /tmp/pip-req-build-wqpvid2m/build/cmake
      [  2%] Building CXX object common/CMakeFiles/transformer_engine.dir/transformer_engine.cpp.o
      [  5%] Building CUDA object common/CMakeFiles/transformer_engine.dir/transpose/cast_transpose.cu.o
      [  8%] Building CUDA object common/CMakeFiles/transformer_engine.dir/transpose/transpose.cu.o
      [ 11%] Building CUDA object common/CMakeFiles/transformer_engine.dir/transpose/cast_transpose_fusion.cu.o
      [ 13%] Building CUDA object common/CMakeFiles/transformer_engine.dir/transpose/transpose_fusion.cu.o
      [ 16%] Building CUDA object common/CMakeFiles/transformer_engine.dir/transpose/multi_cast_transpose.cu.o
      [ 19%] Building CUDA object common/CMakeFiles/transformer_engine.dir/activation/gelu.cu.o
      [ 22%] Building CUDA object common/CMakeFiles/transformer_engine.dir/fused_attn/fused_attn_f16_max512_seqlen.cu.o
      [ 25%] Building CUDA object common/CMakeFiles/transformer_engine.dir/fused_attn/fused_attn_f16_arbitrary_seqlen.cu.o
      Killed
      gmake[2]: *** [common/CMakeFiles/transformer_engine.dir/build.make:188: common/CMakeFiles/transformer_engine.dir/fused_attn/fused_attn_f16_arbitrary_seqlen.cu.o] Error 255
      gmake[1]: *** [CMakeFiles/Makefile2:116: common/CMakeFiles/transformer_engine.dir/all] Error 2
      gmake: *** [Makefile:136: all] Error 2
      Traceback (most recent call last):
        File "/tmp/pip-req-build-wqpvid2m/setup.py", line 336, in _build_cmake
          subprocess.run(command, cwd=build_dir, check=True)
        File "/usr/lib/python3.10/subprocess.py", line 526, in run
          raise CalledProcessError(retcode, process.args,
      subprocess.CalledProcessError: Command '['/usr/bin/cmake', '--build', '/tmp/pip-req-build-wqpvid2m/build/cmake']' returned non-zero exit status 2.

      During handling of the above exception, another exception occurred:

      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-req-build-wqpvid2m/setup.py", line 611, in <module>
          main()
        File "/tmp/pip-req-build-wqpvid2m/setup.py", line 596, in main
          setuptools.setup(
        File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 153, in setup
          return distutils.core.setup(**attrs)
        File "/usr/lib/python3.10/distutils/core.py", line 148, in setup
          dist.run_commands()
        File "/usr/lib/python3.10/distutils/dist.py", line 966, in run_commands
          self.run_command(cmd)
        File "/usr/lib/python3.10/distutils/dist.py", line 985, in run_command
          cmd_obj.run()
        File "/usr/lib/python3/dist-packages/wheel/bdist_wheel.py", line 299, in run
          self.run_command('build')
        File "/usr/lib/python3.10/distutils/cmd.py", line 313, in run_command
          self.distribution.run_command(command)
        File "/usr/lib/python3.10/distutils/dist.py", line 985, in run_command
          cmd_obj.run()
        File "/usr/lib/python3.10/distutils/command/build.py", line 135, in run
          self.run_command(cmd_name)
        File "/usr/lib/python3.10/distutils/cmd.py", line 313, in run_command
          self.distribution.run_command(command)
        File "/usr/lib/python3.10/distutils/dist.py", line 985, in run_command
          cmd_obj.run()
        File "/tmp/pip-req-build-wqpvid2m/setup.py", line 368, in run
          ext._build_cmake(
        File "/tmp/pip-req-build-wqpvid2m/setup.py", line 338, in _build_cmake
          raise RuntimeError(f"Error when running CMake: {e}")
      RuntimeError: Error when running CMake: Command '['/usr/bin/cmake', '--build', '/tmp/pip-req-build-wqpvid2m/build/cmake']' returned non-zero exit status 2.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for transformer-engine
  Running setup.py clean for transformer-engine
Failed to build transformer-engine
ERROR: Could not build wheels for transformer-engine, which is required to install pyproject.toml-based projects

I also tried to update the jax/jaxlib version and still was not able to successfully build TE. Any insights into how to solve this issue would be much appreciated. If you could direct me to a different image that can build TE for jax that would also solve my problem. Thanks for your time.

@denera @nouiz Could you help here?

@bmac3 Could you try this again with the JAX-Toolbox container at ghcr.io/nvidia/jax:pax?
It would also be helpful to see the verbose output from pip install -v .... for a better trace of the compile failure.

ghcr.io/nvidia/jax:pax worked for me! Thanks so much for the help. I'll mark this as closed now


ClassCastException on wildcard generics in collections

Hello, Trying to figure out the best way around this. I want to populate some JAX-B beans. They have fields like this:
@XmlElementRef(name = "reportedLocation", namespace = "http://api.foo.com/v3", type = JAXBElement.class)     protected List<JAXBElement<? extends ReportedLocation>> reportedLocations;
I get a ClassCastException exception from this:
Caused by: java.lang.ClassCastException: sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl cannot be cast to java.lang.Class 	at io.github.benas.randombeans.CollectionPopulator.getRandomCollection(CollectionPopulator.java:68) 	at io.github.benas.randombeans.FieldPopulator.generateRandomValue(FieldPopulator.java:93) 	at io.github.benas.randombeans.FieldPopulator.populateField(FieldPopulator.java:79) 	at io.github.benas.randombeans.EnhancedRandomImpl.populateField(EnhancedRandomImpl.java:162) 	at io.github.benas.randombeans.EnhancedRandomImpl.populateFields(EnhancedRandomImpl.java:153) 	at io.github.benas.randombeans.EnhancedRandomImpl.doPopulateBean(EnhancedRandomImpl.java:124) 	... 203 more
There are quite a few of these. I have a custom registry for some other abstract classes I have but I'm unsure of the best way around this one.
Another suggestion, it might be nice if the EnhancedRandom were to have a brute force mode where it never ever stops for these kinds of errors and just skips them (and logs an error maybe)
Great library everyone!

Hi,
Thank you for reporting this issue!
We will keep you informed once the fix is published.
Kind regards
Mahmoud

I have the same error and tried this fix. ClassCastException was fixed but collection is empty.
I attached test.
rbeans_param_map.zip

@enedzvetsky Thanks. That the collection is empty is the expected behavior. Trying fill it would require significantly more coding effort.

Hi @ryber ,
We have published the fix in the latest 3.4.0-SNAPSHOT version.
Could you please give it a try? ClassCastException should be fixed now.

Another suggestion, it might be nice if the EnhancedRandom were to have a brute force mode where it never ever stops for these kinds of errors and just skips them (and logs an error maybe)

I see, probably a "silent mode" parameter where errors are logged but the randomization continues.
Or may be the other way, where silent mode is the default and add a "strict mode" parameter that stops randomization on first error. What do you think? Please open a separate issue for this request.
Kind regards
Mahmoud

Hi @ryber @enedzvetsky
v3.4 has been released with the fix.
Please reopen this issue in case of any problem.
Many thanks to @PascalSchumacher for the fix!
Kind regards
Mahmoud


feat: add international women day banner

Description
Add International Women's Day banner and link it to internationalwomensday.com. It also changes the logo to purple.
Preview

Preview here: https://deploy-preview-192--asyncapi-website.netlify.app/


[BUG]Adopt-me button not visible in Light mode

Describe the bug
Adopt-me button not visible in Light mode
To Reproduce

Go to Website
Click on ‘Meet pets’
Click on ‘Light mode’
“Adopt-me” button not visible

Expected behavior
In Light mode the font colour  should be changed to black
Desktop :

OS: Mac OS
Browser:Chrome

Screenshots
Dark/Day mode:

Light/Night mode:

Hey! I can do this immediately, But can you please add the hacktober tag for this issue?

@akshitagupta15june can i be assigned this issue for kwoc?

Hey!! Can you please assign this to me? I am contributing for Codepeak'23.


Webhook payloads

I want to merge this change because it changes way saleor handles webhooks. It will allow us to monitor and retry failed event deliveries.
Clickup list: https://app.clickup.com/2549495/v/l/6-144350552-1
Impact

[x] New migrations
[x] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

please rebase @jakubkuc


Wrap release and unrelease code with ActiveRecord::Base.transaction

The release processes need to be wrapped in a ActiveRecord::Base.transaction block so that if the solr indexing fails the database transaction will rollback.

Related: #550


Update CoreProvider environment variable secret documentation

Implementing rancher-sandbox/rancher-turtles#139 to create a secret containing feature flags as part of the installation of CoreProvider means having two differentiated scenarios that must be documented:

The default behavior of Rancher Turtles if user does not provide secret name cluster-api-operator.cluster-api.configSecret.name or namespace cluster-api-operator.cluster-api.configSecret.namespace, is to create a default secret in the core provider namespace that enables the required features CLUSTER_TOPOLOGY and EXP_CLUSTER_RESOURCE_SET.
If user provides both secret name cluster-api-operator.cluster-api.configSecret.name and namespace cluster-api-operator.cluster-api.configSecret.namespace, this resource must be created and managed by the user and must contain, at least, the required feature flags CLUSTER_TOPOLOGY and EXP_CLUSTER_RESOURCE_SET. This is the existing behavior before fixing rancher-sandbox/rancher-turtles#139.

Solved in #29.


Telemetry Level 0 (Security) should be also applied to the Education edition, not only to LTSC & Enterprise

According to Microsoft's documentation, the Telemetry Level "0" is also supported on the Education SKU, not sure about some others like "Pro Education" or "Pro for Workstations", but the script applies it only to LTSC & Enterprise SKUs, should apply it also to the Education at least.

Yes telemetry level '0' is applicable for Education editions, too. I will add that to the next update.


feat: Rename "register" to "mint"

DOUBT: what should I rename Registration to?

"Pre-Registration, Active Registration, Finished Registration" states in the protocol should NOT change (these registration refer to registration of agent instances in the service).
The idea of changing "Register a Service" etc. is precisely to avoid the confusion between "registering a service in the Autonolas Protocol"   VS   "register agent instances in the service".   The first action is actually "minting an NFT that represents the service", whereas the second action simply associates addresses to an already minted
service.


[Bug]: Cannot compile on macOS with Linux error

Platform
macOS
Project is for iOS, Android, macOS, Windows, Linux
Plugin
connectivity_plus
Version
3.0.0
Flutter SDK
3.3.4
Steps to reproduce

Add package to own project
Try building macOS Version
Error-Message during compile:

../../../../.pub-cache/hosted/pub.dartlang.org/connectivity_plus-3.0.0/lib/src/connectivity_plus_linux.dart:54:33: Error: Member not found: 'vpn'.
      return ConnectivityResult.vpn;

Code Sample
None required

Logs
Compile-Error

Flutter Doctor
[✓] Flutter (Channel stable, 3.3.4, on macOS 12.6 21G115 darwin-arm, locale en-US)
    • Flutter version 3.3.4 on channel stable at /Users/iso/Development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision eb6d86ee27 (13 days ago), 2022-10-04 22:31:45 -0700
    • Engine revision c08d7d5efc
    • Dart version 2.18.2
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/iso/Library/Android/sdk
    • Platform android-33, build-tools 30.0.3
    • Java binary at: /Users/iso/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9014738/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

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

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

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] Android Studio (version 2021.3)
    • Android Studio at /Users/iso/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9014738/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

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

[✓] Connected device (7 available)
    • SM T860 (mobile)   • R52N8175P2E                              • android-arm64  • Android 12 (API 31)
    • SM A536B (mobile)  • RZCT909TEZY                              • android-arm64  • Android 12 (API 31)
    • MiniMe (mobile)    • 00008020-000108D13A41002E                • ios            • iOS 15.7 19H12
    • iPhone X (mobile)  • dd8204853d6bcfce9efecee2fc094c65327e0b1e • ios            • iOS 16.0.3 20A392
    • iPhone 6s (mobile) • ab7504427aab66aece9687552a8a6fc2665f980a • ios            • iOS 15.7 19H12
    • macOS (desktop)    • macos                                    • darwin-arm64   • macOS 12.6 21G115 darwin-arm
    • Chrome (web)       • chrome                                   • web-javascript • Google Chrome 105.0.5195.102
    ! Error: MiniMe is busy: Fetching debug symbols for MiniMe. Xcode will continue when MiniMe is finished. (code -10)
    ! Error: iPhone 6s is busy: Fetching debug symbols for iPhone 6s. Xcode will continue when iPhone 6s is finished. (code -10)

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Checklist before submitting a bug

[X] I Google'd a solution and I couldn't find it
[X] I searched on StackOverflow for a solution and I couldn't find it
[X] I read the README.md file of the plugin
[X] I'm using the latest version of the plugin
[X] All dependencies are up to date with flutter pub upgrade
[X] I did a flutter clean
[X] I tried running the example project

Have same issue while compile into android app bundle for releasing. Please ensure that enum value is valid because there is no ConnectivityResult.vpn found. Thanks a lot for every contributors.

I reverted back to the previous version until this is fixed. Thank you a million for all contributors!

It may be necessary to wait for a new version of connectivity_plus_platform_interface to be released.
@vbuberen When will the new version of connectivity_plus_platform_interface be released? Looking forward to it!

@vbuberen When will the new version of connectivity_plus_platform_interface be released? Looking forward to it!

There were no new features or critical fixes introduced in the 3.0.0 release. Use older version of the plugin and don't tag people multiple times. Release will be when maintainers have time. It is not a commercial project, so nobody is going to promise any deadlines, especially when nobody blocks you from using older version of the plugin.

I am very sorry, my words may not be polite, but it was not my intention.

@vbuberen When will the new version of connectivity_plus_platform_interface be released? Looking forward to it!

There were no new features or critical fixes introduced in the 3.0.0 release. Use older version of the plugin and don't tag people multiple times. Release will be when maintainers have time. It is not a commercial project, so nobody is going to promise any deadlines, especially when nobody blocks you from using older version of the plugin.

No worries at all @zeewell  you have been very polite!
I think is vbuberen that is having a stressful day!

This is weird, because the vpn enum type exists in the file src/enums.dart of the connectivity_plus_platform_interface:
https://github.com/fluttercommunity/plus_plugins/blob/main/packages/connectivity_plus/connectivity_plus_platform_interface/lib/src/enums.dart#L19
And the internal package 1.2.1 has been published: https://pub.dev/packages/connectivity_plus_platform_interface
And also, the project does not complain when opened in the IDE.
However, if I do the following, I can reproduce the issue:

Create a new project with flutter create error_1259
cd error_1259
flutter pub add connectivity_plus
flutter run

I get the same error as the original poster.

Forcing the platform interface package to be "from git" fixes the issue. So I guess there was a bogus release. I will force the publishing of a new version of the platform interface on pub.
dependency_overrides:
  connectivity_plus_platform_interface:
    git:
      url: https://github.com/fluttercommunity/plus_plugins.git
      path: packages/connectivity_plus/connectivity_plus_platform_interface

I published connectivity_plus_platform_interface 1.2.2 and the issue should be fixed now.

Thanks a million.


Persist emitTime from IngestionTrackingContext to the new entity tables and use emitTime during backfill

Context
This is continuation of https://github.com/linkedin/datahub-gma/pull/328
This PR makes 2 changes:

Persist emitTime to the new entity table if IngestionTrackingContext is provided
Use emitTime when checking whether we should backfill the entity
If oldEmitTime is available and smaller than new event's emit time -> backfill
If oldEmitTime is not available and last modified time smaller than new event's emit time -> backfill

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable)

@jsdonn should we also reset isBackfill back to false when emitting MAE?

@jsdonn here's what i meant https://github.com/derekpham/datahub-gma/blob/1bf3ea702e148e9f4bf9f5f605d622ab117ca678/dao-api/src/main/java/com/linkedin/metadata/dao/BaseLocalDAO.java#L580

@derekpham oh yeah that's a good idea. Even though it should be default to false (right?), definitely wouldn't hurt to add it explicitly there during regular MAE emission

@jsdonn It's default is false but for backfill MCE we should explicitly set it back to false?


Improve packaging relative to loggregator

Previously the dea_logging_agent packaging required a number of
symlinks within loggregator proper. This commit removes the need for
those symlinks inside loggregator and pulls in all necessary
dependencies from within dea_logging_agent.
Unfortunately, the dea_logging_agent is still subsumed within the
loggregator release and must refer to its source code files relative to
the loggregator root.
Note this PR goes hand-in-hand with the PR in Loggregator here
/cc @jasonkeene

@enocom This and https://github.com/cloudfoundry/loggregator/pull/207 will need to be reviewed by a pair. I'll let @ahevenor schedule it when he gets back.

@enocom To follow up with this, can this PR be closed? The story doesn't appear to be valid anymore.

@ahevenor Looks like the work included in this PR has already found its way to master. Closing.


Query: What's the quickest way with TSDuck to jump to a specific time in a transport stream?

When you have a long TS capture (say, half a day), I'd like to jump to a certain time in the stream before playback. Same kind of action as dragging the playout bar in Dektec's StreamXpress software.
I've found out it's possible to achieve with the -time --tdt plugin:

-P time --tdt --drop (time in first TDT section) --pass (time to jump to)

I was wondering whether this was the quickest method as it takes a few minutes before playback starts, seems like it's processing every packet before getting to the time to jump to.
Are there any alternative methods to achieve this kind of action that would be quicker?

If the input is a file, a direct access one, not a pipe, you may have a look at input plugin file options such as --byte-offset or --packet-offset. But this is a physical offset in the file, not a time reference. If you want a time reference from the file, then you need to read all packets, to get those references precisely. But if you know the file bitrate, it is relatively trivial to compute the packet offset of a given time offset from the beginning of the file.
If the input is not a file, then all other predefined input plugins handle sequential inputs. So you need to read all packets. If you wan to speed up the processing, you may use the plugin skip right after the input plugin. All packets are read from the input but the first N packets are immediately dropped. But I don't think you really gain anything.

Thanks for the suggestions. It will be file input so I will have a look at the options for the file plugin.
The bitrate is fixed (4Mbps) and I know the duration of the transport stream so sounds like --packet-offset may be the way to go.

You do not even need the TS duration, only the bitrate.
Using bash syntax:
BITRATE=4000000
START_SECOND=10

tsp -I file --packet-offset $(( ($BITRATE * $START_SECOND) / (188 * 8) )) ...

You do not even need the TS duration, only the bitrate.
Using bash syntax:
BITRATE=4000000
START_SECOND=10

tsp -I file --packet-offset $(( ($BITRATE * $START_SECOND) / (188 * 8) )) ...

That's great. I can use this to jump to an approximate position in the stream, then use the -P time --tdt plugin to find the actual TDT time I'm looking to start playout from. Cuts down on parsing time a lot compared with using the time --tdt plugin from the beginning of the stream.
As a quick question before I close this ticket - do you have an idea of what date your next tsduck update will be released? So I'll know when to move over from my locally built tsp.exe to the proper release?

do you have an idea of what date your next tsduck update will be released?

Version 3.19 was released one week ago. So, do not expect version 3.20 before a couple of months. You mention your "locally built tsp.exe". So, I assume that you use Windows and you are able to compile. The safest way is to build you own installer and use the latest TSDuck version from the repo. This is extremely simple. After installing the prerequisites only once, building from scratch a complete set of binary installers is as simple as double-clicking on script Build-Installer.ps1 (you have time to lunch then...)

OK, that's useful information, thanks for the instructions for building an installer.


build: tweak required to build script based on tag github generated

Looks like when a tag is made via github's release UI, the tag isn't
annotated. This required a tweak to the build script to prevent the
following error:
fatal: No annotated tags can describe 'ccfe28dd8b55ca76995b72cd9d028745e2d98d14'.
However, there were unannotated tags: try --tags.

Rather, let's always sign (annotate) tags...
On Oct 21, 2015 14:17, "Derek Gonyeo"<EMAIL_ADDRESS>wrote:

Looks like when a tag is made via github's release UI, the tag isn't
annotated. This required a tweak to the build script to prevent the
following error:
fatal: No annotated tags can describe
'ccfe28dd8b55ca76995b72cd9d028745e2d98d14'.
However, there were unannotated tags: try --tags.
You can view, comment on, or merge this pull request online at:
https://github.com/appc/acbuild/pull/48
Commit Summary

build: tweak required to build script based on tag github generated

File Changes

M build https://github.com/appc/acbuild/pull/48/files#diff-0 (2)

Patch Links:

https://github.com/appc/acbuild/pull/48.patch
https://github.com/appc/acbuild/pull/48.diff

—
Reply to this email directly or view it on GitHub
https://github.com/appc/acbuild/pull/48.


[chan.sankanku.com] Wrong file extension in image links resulting in "File Not Found" errors

Ripme version: v1.5.1
Java version (output of java -version): 1.8.0_131
Operating system: Windows 10
Exact URL you were trying to rip when the problem occurred: https://chan.sankakucomplex.com/?tags=kunaboto
Please include any additional information about how to reproduce the problem: The problem occurs with any chan.sankanku.com link.

Expected Behavior
Get the images links with correct file extensions and download them.
Actual Behavior
All the image links are parsed having ".jpg" extension but some of the images are ".png" or other extensions on the site server, resulting in 404 errors when trying to download them.
Example:
When trying to download the images from the link: https://chan.sankakucomplex.com/?tags=kunaboto
RipMe gets the link:
https://cs.sankakucomplex.com/data/23/90/2390750eb665e15d0393733a31bd0632.jpg?6170028
When it should be:
https://cs.sankakucomplex.com/data/23/90/2390750eb665e15d0393733a31bd0632.png?6170028
Then RipMe cant download the image because the file extension on the link is wrong.
The same happens for all ".png" images.

There doesn't seem to be any way of knowing whether a picture is jpg or png or something else without navigating to each image's page, which we can do, although it will add up to more requests (which means marginally slower ripping and a higher chance of being rate-limited or banned). Still, I think it's better to improve correctness, and worry about those problems later, if they become a problem.

Yeah, had to add a delay, but this seems to be working.
Also testing with [NSFW] https://idol.sankakucomplex.com/?tags=kiriyama_rui

getting some weird errors. i'll pick this up later. work in progress here: https://github.com/metaprime/ripme/tree/sankaku

This is fixed in ripme 1.5.14


Implement v5.1 crawl command

What was wrong?
https://github.com/ethereum/ddht/issues/93 implements $ ddht crawl but only in the v5 protocol.  Now that the beacon chain clients are moving to v5.1 we have a network that can actually be crawled.
How can it be fixed?
Probably ok to do a copy/pasta or something similarly quick since the v5 protocol is going in the trash :wastebasket: soon.
Improvements that can/should be made are to move beyond pure terminal output and be able to dump the crawl contents into a file (or maybe even export them as an ENRDatabaseAPI

done


PHOENIX-7036 Copy the Java version specific profiles for JVM options …

…from HBase

Even if we use the correct options for the JVM version now, only the spark3 connector builds successfully.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
3m 45s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

+0 :ok:
mvndep
11m  8s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
8m 45s
master passed

+1 :green_heart:
compile
1m 17s
master passed

+1 :green_heart:
javadoc
1m  1s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
7m 40s
the patch passed

+1 :green_heart:
compile
1m 20s
the patch passed

-1 :x:
javac
1m 20s
root generated 2 new + 2122 unchanged - 2 fixed = 2124 total (was 2124)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  4s
The patch has no ill-formed XML file.

-1 :x:
javadoc
0m 11s
phoenix5-spark generated 3 new + 153 unchanged - 3 fixed = 156 total (was 156)

-1 :x:
javadoc
0m 27s
root generated 28 new + 2109 unchanged - 28 fixed = 2137 total (was 2137)

_ Other Tests _

-1 :x:
unit
35m 49s
root in the patch failed.

-1 :x:
asflicense
0m 26s
The patch generated 3 ASF License warnings.

73m  0s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix-connectors/pull/107

Optional Tests
dupname asflicense javac javadoc unit xml compile

uname
Linux 209993ba49e7 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-connectors-personality.sh

git revision
master / 97144e1

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

javac
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/1/artifact/yetus-general-check/output/diff-compile-javac-root.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/1/artifact/yetus-general-check/output/diff-javadoc-javadoc-phoenix5-spark.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/1/artifact/yetus-general-check/output/diff-javadoc-javadoc-root.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/1/artifact/yetus-general-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/1/testReport/

asflicense
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/1/artifact/yetus-general-check/output/patch-asflicense-problems.txt

Max. process+thread count
1939 (vs. ulimit of 30000)

modules
C: phoenix5-hive phoenix5-spark phoenix5-spark3-it . U: .

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/1/console

versions
git=2.7.4 maven=3.3.9

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

+0 :ok:
mvndep
10m 57s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
8m 44s
master passed

+1 :green_heart:
compile
1m 19s
master passed

+1 :green_heart:
javadoc
1m  0s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
7m 53s
the patch passed

+1 :green_heart:
compile
1m 19s
the patch passed

-1 :x:
javac
1m 19s
root generated 25 new + 2099 unchanged - 25 fixed = 2124 total (was 2124)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  4s
The patch has no ill-formed XML file.

-1 :x:
javadoc
0m 14s
phoenix5-hive generated 20 new + 1061 unchanged - 20 fixed = 1081 total (was 1081)

-1 :x:
javadoc
0m 11s
phoenix5-spark generated 3 new + 153 unchanged - 3 fixed = 156 total (was 156)

-1 :x:
javadoc
0m 27s
root generated 3 new + 2134 unchanged - 3 fixed = 2137 total (was 2137)

_ Other Tests _

-1 :x:
unit
35m 32s
root in the patch failed.

-1 :x:
asflicense
0m 26s
The patch generated 3 ASF License warnings.

69m 11s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix-connectors/pull/107

Optional Tests
dupname asflicense javac javadoc unit xml compile

uname
Linux ca5e7f8ab68d 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-connectors-personality.sh

git revision
master / 97144e1

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

javac
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/2/artifact/yetus-general-check/output/diff-compile-javac-root.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/2/artifact/yetus-general-check/output/diff-javadoc-javadoc-phoenix5-hive.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/2/artifact/yetus-general-check/output/diff-javadoc-javadoc-phoenix5-spark.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/2/artifact/yetus-general-check/output/diff-javadoc-javadoc-root.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/2/artifact/yetus-general-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/2/testReport/

asflicense
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/2/artifact/yetus-general-check/output/patch-asflicense-problems.txt

Max. process+thread count
1941 (vs. ulimit of 30000)

modules
C: phoenix5-hive phoenix5-spark phoenix5-spark3-it . U: .

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/2/console

versions
git=2.7.4 maven=3.3.9

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

+0 :ok:
mvndep
10m 58s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
8m 40s
master passed

+1 :green_heart:
compile
1m 15s
master passed

+1 :green_heart:
javadoc
1m  2s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
7m 39s
the patch passed

+1 :green_heart:
compile
1m 17s
the patch passed

-1 :x:
javac
1m 17s
root generated 45 new + 2079 unchanged - 45 fixed = 2124 total (was 2124)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  4s
The patch has no ill-formed XML file.

-1 :x:
javadoc
0m 27s
root generated 44 new + 2093 unchanged - 44 fixed = 2137 total (was 2137)

_ Other Tests _

-1 :x:
unit
34m 50s
root in the patch failed.

-1 :x:
asflicense
0m 25s
The patch generated 3 ASF License warnings.

68m  8s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/3/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix-connectors/pull/107

Optional Tests
dupname asflicense javac javadoc unit xml compile

uname
Linux f0ad3cc92765 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-connectors-personality.sh

git revision
master / 97144e1

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

javac
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/3/artifact/yetus-general-check/output/diff-compile-javac-root.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/3/artifact/yetus-general-check/output/diff-javadoc-javadoc-root.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/3/artifact/yetus-general-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/3/testReport/

asflicense
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/3/artifact/yetus-general-check/output/patch-asflicense-problems.txt

Max. process+thread count
2054 (vs. ulimit of 30000)

modules
C: phoenix5-hive phoenix5-spark phoenix5-spark3-it . U: .

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-107/3/console

versions
git=2.7.4 maven=3.3.9

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Update orc.py get_date function

Simply reformats date output to format requested by backend. Requested format was: 'yyyy-mm-dd'

Lines up with meetings we had among multiple parties 🎉


clickable taxon ranks

Right now blue taxon nodes are clickable but green taxon rank nodes are not. Now that Deya is adding properties to the taxon rank concepts, we should make these green nodes clickable so we can display their properties.

This is an easy fix, I would just need to know what to dispaly once a taxon rank is clicked. Right now I have it so that if a taxon rank is clicked nothing happens.

@deyaliao  is adding some properties to the taxon ranks in the Devel graph. There should be "next higher" and "next lower" links, and of course rdfs:label. So treat this like a property display, except it's for a taxon rank instead of a taxon.

I believe the nextHigher and nextLower ranks should be displayed now on the graph, if you click on the taxonRank. Both Nelly and I worked on this.

I do think this issue should be fixed now – I've indicated clickability for rank nodes and got rid of the background rank node.

Yes, it's working correctly now.

I actually noticed another bug; if I use the navigation bar to navigate around the graph, the greyed out taxon ranks located at the concept's 270 degree angle doesn't properly close and open with regards to the navigation––making it still clickable in instances where I don't want it to be clickable. I will fix this tomorrow.

Let's go with the first of the three options and hide the nodes.

I believe it is fixed now.

Looks good.