best way to wrap pre-element with div and classes

Hi
I want to wrap the pre-Element with an div. How can i do this?
thanks in advance
Here an example
{columns}

{col}
fooo
{/col}

{col}
fooo
{/col}
{/columns}

You could get something similar by writing:
Header     | Header
---------- | ----------
`Col 1`    | `Col 2`
**Footer** | **Footer**

To give:

Header
Header

Col 1
Col 2

Footer
Footer

Which is rendered as:

Header
Header

Col 1
Col 2

Footer
Footer

If you want the exact result you described you'd need to write an extension to parse this custom table style. It might help to look at how the table demonstrated above is currently implemented, but you'd need to write some custom logic to interpret it in the way you're wanting.
There's some information about writing extensions here: https://github.com/erusev/parsedown/issues/625#issuecomment-386809430


PowerShell support

I tried this in powershell and it didn't work, could you explain how I could get it to work with PowerShell?

Hi @Milo123459, streamhut hasn't been tested on PowerShell so things may not work properly. Happy to integrate any pull requests for Windows/PowerShell support (not sure when I'll have available dev time to look into it)


Add --build-only flag to datasette deploy script.

Overview
Closes #3229 .
We had what appeared to be a transient issue while deploying to fly.io. To test that out, I wanted to try running the Docker build on the fly.io builders, since that was the failing step. flyctl deploy provides this functionality, so I added the --build-only flag to our publish.py to configure that behavior.
Testing
I ran this with the --build-only and checked on https://fly.io/apps/catalyst-coop-pudl/activity for any new releases. No new releases, but I did get a "finished building docker image" log from flyctl. So that seems like it works!
# To-do list
- [ ] Review the PR yourself and call out any questions or issues you have

@jdangerx Ahh, whoops. I didn't actually mean for that to automerge. I think the general version of passing the arguments through would be preferable.


Pass python info to ansible

When running in a virtualenv or if you have multiple valid python paths, ansible's execution will fail.
Pass the necessary details to prevent this failure.

Oops, wrong project.


OTR:definition change for SCAR complex GO:0031209

Current definition: "A heterotetrameric complex that includes orthologues of human PIR121, Nap125 and HSPC300 and regulates actin polymerization and/or depolymerization through small GTPase mediated signal transduction."
It is now known to be a pentameric complex. Suggested new definition:
"A pentameric complex that includes orthologues of human PIR121, Nap1, Abi, SCAR, and HSPC300 and regulates actin polymerization and/or depolymerization through small GTPase mediated signal transduction."
Refs: PMID:24036345, PMID:24630101
Additional synonyms: WAVE regulatory complex, WRC

Done.

You are sooo speedy! thanks.


support routes with None orientation ports

How can we support bundle routes with ports that have orientation=None ?
if __name__ == "__main__":
    import gdsfactory as gf

    c = gf.Component("pads_bundle_steps")
    pt = c << gf.components.pad_array(
        gf.partial(gf.components.pad, size=(30, 30)),
        orientation=None,
        columns=3,
        spacing=(50, 0),
    )
    pb = c << gf.components.pad_array(orientation=None, columns=1, rows=3)
    pt.move((500, 500))

    routes = gf.routing.get_bundle_from_steps_electrical(
        pt.ports,
        pb.ports,
        end_straight_length=60,
        separation=30,
        steps=[{"dy": -50}, {"dx": -100}],
    )

    for route in routes:
        c.add(route.references)

    c.show()

do we support routes with None orientation ports? or neither bundles or routes at the moment? i would think it should just take an extra step of picking the most direct orientation to follow before routing

Not yet
PRs are most welcome:)
@SkandanC

@joamatab
I added a piece of code to add waypoints for None orientation ports as an "initial guess". The problem now is sorting the ports. The routing function fails when the port orientation is None, since the relative orientations of the input and output ports cannot be calculated.

But when I hard code in the port orientations just before sorting, I get this:

Fixed it (this is with None orientation)

Another example:
import gdsfactory as gf

    c = gf.Component("get_route_from_steps_sample")
    w = gf.components.array(
        gf.partial(gf.components.straight, layer=(2, 0)),
        rows=3,
        columns=1,
        spacing=(0, 50),
    )

    left = c << w
    right = c << w
    right.move((200, 100))
    p1 = left.get_ports_list(orientation=None)
    for port in p1:
        port.orientation = None
    p2 = right.get_ports_list(orientation=None)
    for port in p2:
        port.orientation = None
    routes = get_bundle_from_steps(
        p1,
        p2,
        steps=[{"x": 150}, {"y": 100}],
    )

    for route in routes:
        c.add(route.references)

    c
    c.show()

@tvt173 @joamatab

Amazing! Thank you Skandan

fixed in https://github.com/gdsfactory/gdsfactory/pull/702


calling sleep_ms inside an interrupt handler causes lockup

Summary: when you call sleep_ms inside of an interrupt handler, some sort of infinite loop occurs inside of the hardware timer. Specifically, picoprobe/gdb is pointing to the code hanging somewhere in this function: https://github.com/raspberrypi/pico-sdk/blob/26653ea81e340cacee55025d110c3e014a252a87/src/rp2_common/hardware_timer/include/hardware/timer.h#L109
To reproduce: build/flash https://github.com/Lard4/pico-irq-test then when GP22 goes high (gets the interrupt), it turns off the LED then hangs.

Looking at https://github.com/raspberrypi/pico-sdk/blob/master/src/common/pico_time/time.c#L332 it seems sleep_ms calls sleep_us, which in turn calls sleep_until which relies on an alarm-interrupt; so perhaps the problem is interrupts being fired from inside interrupts? :shrug:
If you must use sleep_ms inside an interrupt handler (which seems like an odd thing to do, because you typically want your interrupts to exit as quickly as possible?), it looks like you can set PICO_TIME_DEFAULT_ALARM_POOL_DISABLED to 1, and it'll then do the sleep using busy-waits instead of alarm IRQs?
Ahhh, and I've just noticed that https://raspberrypi.github.io/pico-sdk-doxygen/group__sleep.html says "These functions should not be called from an IRQ handler." :slightly_smiling_face:

Yes, sleep_ functions are interrupt-driven (to save power) and you are using them inside an interrupt. Sleeping in an IRQ is generally unsupported on any platform, and the function description tells you not to do this. Having long delays in an IRQ is also pretty unfriendly to the code being interrupted.
If you do want to insert a long delay in an IRQ, the function to use is busy_wait_us_32() which you will see is also listed as a "see also" under the sleep functions.

I think nonetheless we should downgrade a sleep in an IRQ handler to a busy_wait_us automatically (by default)

I'd recommend leaving sleep disallowed from IRQ context (as is the case in just about every OS out there), and perhaps instead add an assert(irqs-are-enabled) in sleep in debug builds.  The chances of waiting any amount of time in irq context ever being the right thing to do are near zero.

yeah perhaps i was feeling overly generous

merged into develop - sleep in an IRQ handler remains disallowed


SAMZA-2473: gradleVersion and wrapper jar are out-of-sync

Update Gradle wrapper to 5.2.1

Fix built-in wrapper task to read value from gradle.properties
Commit new wrapper scripts and bootstrap jar
$ ./gradlew wrapper to update in the future
Fix maven publish behavior change; see https://docs.gradle.org/5.2.1/userguide/publishing_maven.html#publishing_maven:deferred_configuration

One other thing: Could you please update your pull request description to follow the guidelines at https://cwiki.apache.org/confluence/display/SAMZA/SEP-25%3A+PR+Title+And+Description+Guidelines? It helps us track open source changes.
You shouldn't need to add much more detail than what you already have, but it would be great if you could categorize your bullet points into the corresponding sections listed in that wiki page.

I think this is ready to go, pending CI.


Join my profile 👇👇❤👇Click here

http://gg.gg/Livechatxx18

Can I be assigned this issue 👉👈

Spam


Support synchronous training with parameter servers using Distribution Strategies

System information

TensorFlow version (you are using): TF 2.0
Are you willing to contribute it (Yes/No): Yes

Describe the feature and the current behavior/state.
Right now we have MirroredStrategy and MultiWorkerMirroredStrategy for synchronous training where variables and ops are all replicated and all-reduce is used for gradient aggregation. We also have ParameterServerStrategy where gradient updates from workers are purely asynchronous since SyncReplicasOptimizer is buggy and has been deprecated.
We would like to first collect use cases where synchronous training with MirroredStrategy and MultiWorkerMirroredStrategy is not ideal and synchronous training with parameter servers is necessary.
If this feature is necessary and important enough, we will then use this issue to track the progress of the development of this feature.
We have a separate feature request to support large embeddings with MirroredStrategy and MultiWorkerMirroredStrategy: https://github.com/tensorflow/tensorflow/issues/27726
Will this change the current api? How?
Yes.
Who will benefit with this feature?
Those who use distributed training.
Any Other info.
N/A

What's the progress of this issue?

What's the progress of this issue?

This feature is promising. What's the progress of this issue? @yuefengz

We will send out a RFC for PSStrategy soon.

There is any plan? Thanks @yuefengz

@yuefengz any developments on this ?

hi , Is there some progress with this issue?

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.
Thank you!


Validator considers an empty string unique even when it is a duplicate.

Laravel Version: 5.5.4
PHP Version: 7.2.0RC1
Database Driver & Version: SQLite 3.20.1

Description:
Validator considers an empty string unique even when there's already record with empty string in database.
Steps To Reproduce:

Create a table with unique text column.
Add few records with unique values in that column, including empty string.
Invoke validator with every string from the database and unique rule for that column and check whether it passes. It will fail on every string that's already in the table, except the empty string.

>>> DB::statement('CREATE TABLE test (id INTEGER, value TEXT NOT NULL, PRIMARY KEY(id), UNIQUE
(value))')
=> true
>>> DB::table('test')->insert(['value' => 'one'])
=> true
>>> DB::table('test')->insert(['value' => 'two'])
=> true
>>> DB::table('test')->insert(['value' => 'three'])
=> true
>>> DB::table('test')->insert(['value' => 'three'])
Illuminate\Database\QueryException with message 'SQLSTATE[23000]: Integrity constraint violation: 19 UNIQUE constraint failed: test.value (SQL: insert into "test" ("value") values (three))'
>>> DB::table('test')->insert(['value' => ''])
=> true
>>> DB::table('test')->insert(['value' => ''])
Illuminate\Database\QueryException with message 'SQLSTATE[23000]: Integrity constraint violation: 19 UNIQUE constraint failed: test.value (SQL: insert into "test" ("value") values ())'
>>> DB::table('test')->pluck('value')
=> Illuminate\Support\Collection {#730
     all: [
       "one",
       "two",
       "three",
       "",
     ],
   }
>>> validator(['value' => 'one'], ['value' => 'unique:test'])->passes()
=> false
>>> validator(['value' => 'on1'], ['value' => 'unique:test'])->passes()
=> true
>>> validator(['value' => 'two'], ['value' => 'unique:test'])->passes()
=> false
>>> validator(['value' => 'three'], ['value' => 'unique:test'])->passes()
=> false
>>> validator(['value' => ''], ['value' => 'unique:test'])->passes()
=> true

Yes empty strings pass all validation rules except rules that imply the field is required, this is intended and it'd be a huge breaking change if we change it.

Using required rule to validate for empty string uniqueness is not a solution, or even workaround, because what if I want to allow for only one occurrence of empty string in table? Like empty Skype number for system superuser?

Sounds like a "required_unless" rule would work great in this scenario.

Laravel considers an empty string as a no value, so validation rules won't run. Your case is a bit weired, why can't multiple rows have an empty column in your database?


changes_xml_default_name

Changed default file name from Changes.xml to changes.xml.
Closes #103.

@mzaninovic555 can you update tests and docs?

@mzaninovic555 can you update tests and docs?

@marwin1991 What should I change regarding tests? Locally they pass fine.


Cannot build due to WARNING: Component "espressif/mdns" not found

Answers checklist.

[X] I have read the documentation ESP-AT Programming Guide and the issue is not addressed there.
[X] I have used the latest released firmware or have updated my ESP-AT branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Hello there, I have NodeMCU v1.1 board (it says: ESP-WROOM-32 on the metal part)

and I was trying to build and load this firmware on it
I have this development enviroment (the latest) on my Windows maschine: https://dl.espressif.com/dl/idf-installer/esp-idf-tools-setup-offline-5.2.1.exe?
and I can compile blink example just fine
I use command line I do not use espressif IDE
I used this instructions to try to compile ESP-AT: https://docs.espressif.com/projects/esp-at/en/latest/esp32/Compile_and_Develop/How_to_clone_project_and_compile_it.html#esp-at-idf-prerequisites
I used the same path as in instructions
after running python build.py install I selected option 1 (ESP-32 on WROOM-32) and again Option 1 to not print any log files
everything went fine until I ran
python build.py menuconfig

Then I get this error: WARNING: Component "espressif/mdns" not found

and it quits
why does this happen, do I use to new enviroment?
What do I do?
Thanks for Anwsering and Best Regards

@veso266 It seems that the relevant components were not successfully downloaded.
Please delete the build sdkconfig and run the following commands again, providing the complete log afterwards.
python build.py install
python build.py menuconfig

thanks, at the end I just installed the version 5 of the toolchain because I read in the readme that this is the version that the software was ported to: https://dl.espressif.com/dl/idf-installer/esp-idf-tools-setup-offline-5.0.exe?
and it worked fine, so I guess the latest version is to new for this to build

Good to know! thanks for the feedback.


Need Static HTML Pages for Indexing the Bio Search

Currently, the old API Docs are appearing in the search results for Swan Lake when searched using the Bio search.

We need to generate the static HTML pages of the new API Docs to index them to appear as search results in the Bio search.

Currently docs are generated using SSR(Server Side Rendering) using NextJS. Hence HTML pages are generated.


DBZ-7785 Add MariaDB REST extension tests

https://issues.redhat.com/browse/DBZ-7785
Depends on https://github.com/debezium/container-images/pull/372

Test failures require the container-images PR to be merged.

@Naros I pushed the mariaDB example image into regitry but I accidentally merged this PR without re-running it to make sure the tests are passing :-(.
Could yo please keep an eye on the main build to make sure there is no failure. I am sorry for the mess :-(


Update CBMC version to 5.95.1

Update CBMC version to 5.95.1
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

Leaving as draft until the version is available in brew.


What about making the tight belt reducing the normal warp instead of the temp warp

From the source code I guess the tight belt can only reduce the TEMP warp while emitting flux.
But the Sanitizing Soap can easily clean the TEMP warp in one time, and the Soul Brazier in Thaumic Exploration can storage the PERM warp. And there's no way to reduce NORMAL warp quickly and easily.
So why not make the tight belt reducing the NORMAL warp so that it will be both useful and irreplacable ; )

Reducing warp is not a purpose of tight belt, it's a cost of applying thaumic sickness.
Vomited flux is intended to use in pair with Taint Animation Focus (see its enchantments)


The lastest webrtc  can't work with jitsi-videobridge

WebRTC.framework can't contains x86 code when submit to appstore.
I used the latest webrtc(commitid:144475b3286f4de5059e0333044a72faf5d0171c) source to compile my webrtc.framework(only contains arm code)
but it can't work with jitsi-videobridge
my fork is https://github.com/richmonkey/react-native-webrtc

jitsi videobridge commit id:c65f68acd7046b1a517a985d2dc0a75186bb855b

jicofo commit id:0676b569277fec9d05fc14e386bf83026a1c67ab

This has nothing to do with the Jitsi Video Bridge. This plugin has always had x86 in it, for the Simulator to work.
You can follow the instructions here to remove non-arm architectures when submitting to the store. Or use lipo by hand, whatever suits you.
If you make your own builds you should make them from the same commits we do (see commit logs).


Generate SDK for 0.4 release

What this PR does / why we need it:
Generate SDK for 0.4 release
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:

Fixed a path issue for update-openapigen.sh after KFServing migrated to use GO Module

Release note:

@yuzisun Would you please also update the author_email to correct Ellis Email and add yours if you are willing to do it? Thanks.
https://github.com/kubeflow/kfserving/blob/2e3cfe048e7bcda94b5069c3c3d6dc5efbbf5102/python/kfserving/setup.py#L30

/lgtm

/approve


Add static override to change assisted installer namespace

Issue: https://github.com/stolostron/backlog/issues/21016
Signed-off-by: Jakob Gray<EMAIL_ADDRESS>

/lgtm


Can't Control Mouse In GNOME Desktop Mode With Deck Trackpads

I think this has something to do with the new GNOME version. I rebased to the 39 branch early, and I noticed it prompted me to allow "Remote Control" whenever I would touch the trackpad for the first time in desktop mode (only after Steam launched).  Now that I have rebased on latest and updated, it no longer prompts me for that, but the functionality of actually using the mouse cursor from Deck is lost without an external mouse.

Fixed as of the latest commit.


package owner sentry not redirecting to getsentry anymore

sentry/sentry-laravel is no longer redirecting to getsentry/sentry-laravel package when trying to install.
You may want to update the readme.

I must have overlooked a PR where we changed behavior here (or this is working as expected). The package name is 'sentry/sentry-laravel', while the repository name is 'getsentry/sentry-laravel'.

You mean using https://github.com/sentry/sentry-laravel to go to this repository? AFAIK this has never worked, it has always been sentry/sentry-laravel on packagist and getsentry/sentry-laravel here.

https://packagist.org/packages/sentry/sentry
https://packagist.org/packages/sentry/sentry-laravel

Are you adding the git repository yourself in the composer.json?

Maybe i added it manually in my composer.json, that was like more than a year, but it was working and I am doing composer update around once per week. The repository is in my vendor directory in local and was online too (it was installed through composer install), but when trying to composer update yesterday in my online version it broke my project because it couldnt find sentry/sentry-laravel anymore.

Well I have just tried to install it locally from a fresh composer.json and it worked. I will have to try online again and see if it work again, maybe it was just a temporary glitch in the matrix. Ill keep you posted if the glitch persist, thanks !

Thanks, will close this for now (hoping it was just a glitch) otherwise feel free to reopen 👍


Support jvm_thread metrics

Please answer these questions before submitting pull request

Why submit this pull request?

[ ] Bug fix

[x] New feature provided

[ ] Improve performance

Related issues
https://github.com/apache/skywalking/issues/5098

New feature or improvement

Describe the details and related test reports.
Support jvm_thread metrics

PTAL @ascrutae

https://github.com/apache/skywalking-data-collect-protocol/blob/24788cf41807048dcbe8dba0958688aaaf630d73/language-agent/JVMMetric.proto

How do I update this file? I can't update it with Git
https://github.com/apache/skywalking-data-collect-protocol/blob/24788cf41807048dcbe8dba0958688aaaf630d73/language-agent/JVMMetric.proto

Read the doc about git submodule.

Take a look at ui-initialized-templates.yml, you should add new components on the instance page, then export the new dashboard configurations, and update this file.
This file managed the default UI layout since 8.0.0. You should have used it, right?

ok, I missed it here

How can I solve this problem?

I think this is only related to your local git submodule issue. If you are not familiar with the commands, try Sourcetree, it is very friendly to the git submodule with providing a GUI.

I think this is only related to your local git submodule issue. If you are not familiar with the commands, try Sourcetree, it is very friendly to the git submodule with providing a GUI.

thanks,


Policy regarding changes to the content and translations

If I (or whoever) wish to propose a change to some text on the English version of the website, such as by writing a patch and filing a pull request, am I required to provide corresponding changes for all the translations of the website as well? CONTRIBUTING.md does not seem to provide guidance on this matter, and I would like to suggest that such guidance be added.

You're not required to. We should change CONTRIBUTING to mention this, yeah.


Reuse evaluations when computing proofs

Reuse precomputed evaluations instead of evaluation polynomial for each proof

Did it make a difference in terms of efficiency?

I still need to measure it. But it should. The question is if is it enough.


Add a Beep Tone on Each Registered Lap

would be nice to have lap voice call by pilot with the ability to turn this feature on or off ..

Added voice announcements,  currently in the 'feature-voice' branch if you would like to test.


Fully atomic state changes

Coverage decreased (-0.3%) to 90.779% when pulling 9e36722819e8361a05ba4c32b3e0cf18a9d4be96 on fully_atomic_state_transition into 71b6bd19c027e7b2099f2f173238cc1bdee3a05b on master.

Coverage decreased (-0.3%) to 90.779% when pulling b897fba928f2504b2a9d8b4f962c45a434b8483f on fully_atomic_state_transition into 71b6bd19c027e7b2099f2f173238cc1bdee3a05b on master.


[build] android_building.md Flamingo Android Studio Java instructions

Made a fresh install of Ubuntu 22.04.2 LTS
Installed Android Studio using "software" in Ubuntu
Android Studio Flamingo | 2022.2.1 Patch 1
According to Building instruction you should set
JAVA_HOME=/Applications/Android\
Studio.app/Contents/jbr/Contents/Home/
Java was not found using that path
./scripts/build/build_examples.py --target android-arm64-chip-tool build
2023-07-07 10:20:09 INFO    Building targets: android-arm64-chip-tool
2023-07-07 10:20:09 INFO    Preparing builder 'android-arm64-chip-tool'
2023-07-07 10:20:09 INFO    Generating /home/willy/matter/connectedhomeip/out/android-arm64-chip-tool
2023-07-07 10:20:09 INFO    Setting up Android deps through Gradle
2023-07-07 10:20:09 WARNING
2023-07-07 10:20:09 WARNING ERROR: JAVA_HOME is set to an invalid directory: /Applications/Android Studio.app/Contents/jbr/Contents/Home/
2023-07-07 10:20:09 WARNING
2023-07-07 10:20:09 WARNING Please set the JAVA_HOME variable in your environment to match the
2023-07-07 10:20:09 WARNING location of your Java installation.
In Android Studio Flamingo I found default Java
JAVA_HOME=/snap/android-studio/126/android-studio/jbr
When I check version it appears to be version 17.0.06 however
/snap/android-studio/126/android-studio/jbr/bin/java --version
openjdk 17.0.6 2023-01-17
OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
OpenJDK 64-Bit Server VM (build 17.0.6+0-17.0.6b802.4-9586694, mixed mode)
So unsure how to set JAVA_HOME correctly using Flamingo
Building from scripts worked without JAVA_HOME using
sudo apt install openjdk-11-jdk-headless
sudo snap install --classic kotlin
/scripts/build/build_examples.py --target android-arm64-chip-tool build
The resulting APK runs fine on an Android Phone

I think the JAVA_HOME value is relevant to Mac OSX, not Linux.

could you consider to use docker to complete android chip-tool
docker run -it -v ~/workspace/connectedhomeip:/connectedhomeip ghcr.io/project-chip/chip-build-android:1
git config --global --add safe.directory /connectedhomeip
git config --global --add safe.directory /connectedhomeip/third_party/pigweed/repo
source scripts/bootstrap.sh
./scripts/build/build_examples.py --target android-arm64-chip-tool build


Any plans to support Swift 3?

Hey @alexpyoung, we'll be working on it 😄 You can follow #432 for updates.


Use in MPV

Hello, is it possible to use these shaders in MPV instead of the glsl ones ? I am having performance issues on MPV on Apple Silicon because it simply uses OpenGL and isn't optimised at all for it.

Did you test this version and verified it's actually faster than OpenGL version?
I doubt if MPV supports any metal shaders. But in any case this is out of scope of this project. I suggest that you create a feature request in MPV.

Yes I understand that isn't what the project is for, just wondering if it was ever done. Nice work !

I am having performance issues on MPV on Apple Silicon

Which version of Apple Silicon are you using: M1, M2, Pro, Max, or Ultra? Are you running the native mpv build or the Intel version? Additionally, are you using shaders optimized for higher or lower-end GPUs? I personally found that the standard M1 and M2 versions hit their limit, so I stuck with the lower-end GPU, which has been working great for me.

I am having performance issues on MPV on Apple Silicon

Which version of Apple Silicon are you using: M1, M2, Pro, Max, or Ultra? Are you running the native mpv build or the Intel version? Additionally, are you using shaders optimized for higher or lower-end GPUs? I personally found that the standard M1 and M2 versions hit their limit, so I stuck with the lower-end GPU, which has been working great for me.

Using a M2 Pro right now, going with the low end cpu shaders worked so I'm sticking with that

I did not have an M2 Pro chip to test with when I was writing the instructions for Mac, but I assume it also had performance issue with the higher-end GPUs? I will go back to review and update the instructions. Based on my experience with the normal M2 chip, I could only use the Medium shaders. If you have an M2 Pro, you might be able to try using the Large (L) shaders instead. So it's possible that they could work on an M2 Pro as the shader optimized for higher-end GPUs starts with the Very Large (VL) shaders.

I did not have an M2 Pro chip to test with when I was writing the instructions for Mac, but I assume it also had performance issue with the higher-end GPUs? I will go back to review and update the instructions. Based on my experience with the normal M2 chip, I could only use the Medium shaders. If you have an M2 Pro, you might be able to try using the Large (L) shaders instead. So it's possible that they could work on an M2 Pro as the shader optimized for higher-end GPUs starts with the Very Large (VL) shaders.

I will try the Large ones then, VL didn't work. Also, i haven't tried the metal shaders, just the basic anime4k ones.
Did you observe a difference of performance between metal and non metal ?

I will try the Large ones then, VL didn't work. Also, i haven't tried the metal shaders, just the basic anime4k ones.

Give it a try! Apparently, the author of this project, Anime4KMetal, was able to get VL metal shaders working on their M1 Ultra.

Did you observe a difference of performance between metal and non metal ?

My results varied slightly, you can take a look here, if you’re interested.

I have added support for chaining multiple shaders as well as all presets as defined in official Anime4K instructions. Feel free to check out this repo or download pre-built binaries from v0.0.2 release. Screenshots can be found in README.md.
From my testing all presets (Fast, HQ) work well on my 48-core M1 Ultra without dropping frames. The results from presets are way better than using individual shaders. Note that no preset is using shaders larger than VL size.


[Bugfix] Add continuous render on resize

Adds an EventFilter which will call any arbitrary Caml callback on Resize
Binds the render function to be called on resize

This is ready to be merged!


User view presentation

From 20/SEP/23 Lasair-Adler meeting

18/OCT/23

presentation given at 18/OCT/23 Adler-Lasair meeting
Waiting for slides

Slides posted


initial version of bdd.yml file

Created bdd.yml

Hopefully, I have fixed this

This one does not seem to have a story associated?

This one does not seem to have a story associated?

@yitao-zhou I just connected this issue to the story, #40 Create GitHub Actions Workflow File for BDD


dm: continuous data validation

Is your feature request related to a problem?
no
Describe the feature you'd like
support continuous data validation during sync.
subtasks

[x] #4459
[x] #4770
[x] #4716
[x] #4488
[x] #4490

[x] #4889
[x] #5091
[x] #5164
[x] #5305

[x] #5152
[x] ~validator start add --remove-meta?~ not needed for now
[x] #5253
[x] ~check locks, fix potential data race~(done in #5330)
[x] #5330
[x] #5392
[x] #5449
[ ] #5368
[x] #5632
[ ] make major dm integration test and chaos test which uses sync-diff, use validator too @buchuitoudegou
[ ] #5634 @buchuitoudegou
[ ] subtask config maybe updated during task pause, some fields in syncer maybe reinitialized, need to make sure validator read the right value @D3Hunter
[ ] error operation command should give a message on non-exist error-id, not success silently. @D3Hunter

features/enhancements may added later.

[ ] make sure show-error/operate error can see and operate non-flushed errors

new error rows stays in memory before flush, user can view it in validation status, but in show-error cannot see and operate them. but checkpoint flush every minute, i think it's ok for now.

[ ] #4427
[ ] for error row, show which col failed to validate.
[ ] may have a command to generate fix sql from error row.
[ ] support validation for binary/json data types
[ ] when validator worker met retryable error on validate, validator routine should stop send events to worker to avoid pending row size or count exceed the max allow size or count, cause validator stop automatically, since we don't know how long this retryable error will last.
[ ] stopped task fail over, processed row status and table status is not loaded into memory, so they're zero/empty. but we can see errors, since it's loaded from db all the time
[ ] only start/stop support -s right now, other commands may report error if only some subtask enables validator, maybe other commands support them too.
[ ] update document of validator monitor

bugs/problems introduced in merged pr:

[x] subtask.Run may recreate syncer, validator need to know

when subtask.Run, then the subtask is new created or have called closed, the validator is null(after #4770 merged) then, so it's ok

[x]  #5184
[x] methods in data_validator used by dmctl command should use its own context and set timeout. also need to handle this case https://github.com/pingcap/tiflow/pull/5306#discussion_r860778625 @buchuitoudegou
[x] #5359
[x] ~https://github.com/pingcap/tiflow/pull/5534#discussion_r883231371 some error messages don't conform to English grammar~, moved into #5143

Describe alternatives you've considered
No response
Teachability, Documentation, Adoption, Migration Strategy
No response

it's a new feature, not affects 5.4

validator will automatically stop itself when encountering some network errors (e.g. failing to persist checkpoint to downstream).

[2022/06/09 16:15:42.045 +08:00] [INFO] [checkpoint_flush_worker.go:68] ["about to sync flush checkpoint snapshot"] [task=test] [unit="binlog replication"] [snapshot_id=8]
[2022/06/09 16:15:42.112 +08:00] [INFO] [checkpoint_flush_worker.go:109] ["sync flush checkpoint snapshot successfully"] [task=test] [unit="binlog replication"] [snapshot_id=8] [pos="position: (mysql-bin.000007, 856099799), gtid-set: "]
[2022/06/09 16:15:42.113 +08:00] [INFO] [syncer.go:1255] ["after sync flushed checkpoint, gc all causality keys"] [task=test] [unit="binlog replication"]
[2022/06/09 16:15:56.502 +08:00] [INFO] [validator_checkpoint.go:626] ["error count loaded"] [task=test] [unit="continuous validator"] [counts={}]
[2022/06/09 16:15:56.503 +08:00] [INFO] [data_validator.go:412] ["validator status"] [task=test] [unit="continuous validator"] ["processed(i, u, d)"="[188081,309328,154816]"] ["pending(i, u, d)"="[7095,7573,0]"] ["new error rows(not flushed)"=0] ["binlog process speed"="0.58 MB/s"]
[2022/06/09 16:15:56.944 +08:00] [INFO] [status.go:126] ["binlog replication progress"] [task=test] [unit="binlog replication"] ["total binlog size"=768887649] ["last binlog size"=646532312] ["cost time"=30] [bytes/Second=4078511] ["unsynced binlog size"=472461562] ["estimate time to catch up"=115]
[2022/06/09 16:15:56.945 +08:00] [INFO] [status.go:147] ["binlog replication status"] [task=test] [unit="binlog replication"] [total_events=1821563] [total_tps=7751] [tps=9744] [master_position="(mysql-bin.000008, 322468679)"] [master_gtid=e530ae5c-e7bb-11ec-a664-0242ac110002:1-3377534] [checkpoint="location(position: (mysql-bin.000007, 923761787), gtid-set: )(flushed location(position: (mysql-bin.000007, 856099799), gtid-set: ))"]
[2022/06/09 16:15:56.951 +08:00] [INFO] [validator_checkpoint.go:626] ["error count loaded"] [task=test] [unit="continuous validator"] [counts={}]
[2022/06/09 16:16:01.088 +08:00] [INFO] [server.go:742] [request=QueryStatus] [payload="name:"test" "]
[2022/06/09 16:16:01.099 +08:00] [INFO] [status.go:126] ["binlog replication progress"] [task=test] [unit="binlog replication"] ["total binlog size"=785765817] ["last binlog size"=768887649] ["cost time"=5] [bytes/Second=3375633] ["unsynced binlog size"=486429876] ["estimate time to catch up"=144]
[2022/06/09 16:16:01.099 +08:00] [INFO] [status.go:147] ["binlog replication status"] [task=test] [unit="binlog replication"] [total_events=1862332] [total_tps=7759] [tps=8153] [master_position="(mysql-bin.000008, 353294878)"] [master_gtid=e530ae5c-e7bb-11ec-a664-0242ac110002:1-3396265] [checkpoint="location(position: (mysql-bin.000007, 940635997), gtid-set: )(flushed location(position: (mysql-bin.000007, 856099799), gtid-set: ))"]
[2022/06/09 16:16:01.108 +08:00] [INFO] [validator_checkpoint.go:626] ["error count loaded"] [task=test] [unit="continuous validator"] [counts={}]
[2022/06/09 16:16:10.048 +08:00] [WARN] [validator_checkpoint.go:79] ["met error"] [task=test] [unit="continuous validator"] [error="context deadline exceeded"]
[2022/06/09 16:16:10.048 +08:00] [WARN] [strategy.go:94] ["retry stratey takes effect"] [error="context deadline exceeded"] [retry_times=0] [retry_count=3]
[2022/06/09 16:16:10.049 +08:00] [WARN] [data_validator.go:957] ["failed to flush checkpoint: "] [task=test] [unit="continuous validator"] [error="context deadline exceeded"]
[2022/06/09 16:16:10.049 +08:00] [ERROR] [data_validator.go:443] ["error during validation"] [task=test] [unit="continuous validator"] [error="[code=43002:class=validator:scope=internal:level=high], Message: failed to persist checkpoint and data, RawCause: context deadline exceeded"] [errorVerbose="[code=43002:class=validator:scope=internal:level=high], Message: failed to persist checkpoint and data, RawCause: context deadline exceeded\ngithub.com/pingcap/tiflow/dm/pkg/terror.(*Error).Delegate\n\tgithub.com/pingcap/tiflow/dm/pkg/terror/terror.go:315\ngithub.com/pingcap/tiflow/dm/syncer.(*DataValidator).doValidate\n\tgithub.com/pingcap/tiflow/dm/syncer/data_validator.go:714\ngithub.com/pingcap/tiflow/dm/syncer.(*DataValidator).routineWrapper\n\tgithub.com/pingcap/tiflow/dm/syncer/data_validator.go:326\nruntime.goexit\n\truntime/asm_amd64.s:1571"]
[2022/06/09 16:16:10.049 +08:00] [INFO] [data_validator.go:754] [stopping] [task=test] [unit="continuous validator"]
[2022/06/09 16:16:10.053 +08:00] [INFO] [data_validator.go:769] [stopped] [task=test] [unit="continuous validator"]
[2022/06/09 16:16:12.071 +08:00] [INFO] [syncer.go:3619] ["flush all jobs"] [task=test] [unit="binlog replication"] ["global checkpoint"="location(position: (mysql-bin.000007, 983927538), gtid-set: )(flushed location(position: (mysql-bin.000007, 856099799), gtid-set: ))"] ["flush job seq"=8]

The validator has 4 workers by default while the syncer has 16 ones, which results in validator has huge lag with the syncer (it not severely affects the functionality but the validator is more likely to fail when running too long)

ail to get syncer's log file index

should print the error out in updateValidatorBinlogMetric and updateValidatorBinlogLag

https://github.com/pingcap/tiflow/blob/d8afd07f45f5f38be1d89ccb3447b4aa70b44177/dm/syncer/data_validator.go#L982-L985
It's okay to return error here because the validator won't be stopped but simply log a warning.
FYI:
https://github.com/pingcap/tiflow/blob/7974dd31256db1d5cad1199dc36cd4aa79fa7541/dm/syncer/data_validator.go#L957-L958
If this persist, initializing the validator, failed, the validator should be stopped @D3Hunter
https://github.com/pingcap/tiflow/blob/7974dd31256db1d5cad1199dc36cd4aa79fa7541/dm/syncer/data_validator.go#L586-L607


bazel run error

I am trying to run the code from this tutorial: http://tensorflow.org/tutorials/seq2seq/index.md
When I try to run this command:
bazel run -c opt tensorflow/models/rnn/translate/translate.py -- -- data_dir ../data/translate/
I get the following error:
...................
ERROR: Cannot run target //tensorflow/models/rnn/translate:translate.py: Not   executable.
INFO: Elapsed time: 1.537s
ERROR: Build failed. Not running target.

Any ideas how to resolve?

bazel run -c opt tensorflow/models/rnn/translate:translate
in bazel you have to build / run the target as defined in the BUILD file, rather than the source file.

Maybe update the tutorial with the right command then?

Good call -- sent out the fix internally and we'll push the change out soon.  Thanks!

Great thanks!


java.net.ProtocolException: expected 0 bytes but received 8192

Hello. Long story short:
    val url = "https://www.ozon.ru/"
    val requestBuilder = Request.Builder().url(url)
    requestBuilder.header("User-Agent", "Mozilla/5.0 (Linux; Android 13) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5112.97 Mobile Safari/537.36")
    val response = OkHttpClient.Builder().build().newCall(requestBuilder.get().build()).execute()
    println(response.protocol)
    println(response.header("Content-Length"))
    println(response.headers)
    println(response.body!!.contentLength())
    println(response.body!!.contentType())
    val body = response.body
    val string = body!!.string()
    body.close()
    println(string)

h2
null
0
null
Exception in thread "main" java.net.ProtocolException: expected 0 bytes but received 8192
at okhttp3.internal.connection.Exchange$ResponseBodySource.read(Exchange.kt:290)
at okio.RealBufferedSource.select(RealBufferedSource.kt:229)
at okhttp3.internal.Util.readBomAsCharset(Util.kt:265)
at okhttp3.ResponseBody.string(ResponseBody.kt:187)
at a.b.c.main(Hello.kt:377)

This site works when force Protocol.HTTP_1_1 in OkHttpClient builder, also works perfectly in browser with http2 (either from real device or from PC browser devtools with mobile UA).

To reproduce this error, you can use any mobile user-agent (I tried 3 different).
Tried on OkHttp 4.10.0 / 5.0.0-alpha.10

Thanks, should be relatively easy to repro with a test server.

So it's sending an early hints (103).
Issue: https://github.com/square/okhttp/issues/3671
and a PR https://github.com/square/okhttp/pull/7196

Closing as a duplicate of https://github.com/square/okhttp/issues/3671


Self-registration is not working

This is the link sent to the user
https://localhost:8182/action/1b092b67-9355-4ece-ae01-bc3d34e84229/confirm
localhost:8182 instead should point to the public hostname.
DONE:

[ ] functional self-registration test in CI is present

Quick fix on nuv.la and BB : bypass Clojure proxy.
Fix available here:
https://github.com/slipstream/SlipStreamServer/commit/17df7bcc6df31cf2dcc924947ec9da13ed0fd222


Deprecate this repo

Now that tldr is in Homebrew, this tap can be deprecated.

:tada: bca560db8732f0f3c2f7a5542104e6eeeb039925


[1.319] Rigidbody component must be on parent prefab...

Hello.. K I've discovered today that any prefabs made with Realtime CSG must have Rigidbody attached or the attached script throws error on each prefab I remove it from when runtime. Normally no problem but it Fracs up my triggers inside the models that I need my own Rigidbody for trigger. Is there any way to disable this problem without painfully removing all the scripts from each prefab?
 This way I can still remodel any time needed :)

I'm not entirely sure if I understand .. are you saying you don't want CSG models to have any rigidbodies, because you have a parent object that already has a rigidbody?

Most of my prefabs are Static (12m x 12m x 12m) Maze blocks... I only use rigidbody mainly if I have a trigger (box collider) to trigger an event. So, if there's already a rigidbody from Realtime CSG on parent than it conflicts with the child (zone trigger).. Luckily most of my zone triggers are seperate in it's own _Trigger folder..

However, if there's a Rigidbody on all my 100 Maze blocks? Imagine the extra physics overhead this would create.. Although they are set "Is Kinematic" by Realtime CSG, there was some weird conflicts everytime my player ran into a trigger zone.. Anyhow, I'd like to see a way if.... we could keep the models just as you've got them but the script throws an error if we remove the rigidbody from the prefab (when we hit run in editor).. Hope this clarifies somewhat.. Great work on the improvements; features. :D

All seems fine... Looks like I missed a few settings that we're enabled by "Default" on the "CSG Model" script..
Now should be good. Thanks! :D

Ok cool :)
So if I understand correctly it was a setting on the model that wasn't set correctly?
Do you think there's something I could improve to make things clearer?

I thought everything was ok but I get the odd:
MissingComponentException: There is no 'Rigidbody' attached to the "Test" game object, but a script is trying to access it.
You probably need to add a Rigidbody to the game object "Test". Or your script needs to check if the component is attached before using it.
InternalRealtimeCSG.MeshInstanceManager.OnBuild () (at Assets/Plugins/RealtimeCSG/Editor/Scripts/Managers/MeshInstanceManager.cs:1039)
This is only if I uncheck:
All 3 settings under Physics: the "CSG Model" script. Oh the settings you have are very easy to find, I didn't really realize how important they were..

Fixed in 1.319 which you can find on the update site https://prenominal.nl/updates/ !
I'll close this ticket when this version is available on the asset store

Kewl ! Thanks for the Fixx.. :)
I'll try this out tonight..


Support TLS 1.3 on Mac

Describe the feature
Original bug opened on aws-iot-device-sdk-python-v2:

Describe the bug
If you enable AWS IoT security policy TLS13_1_3_2022_10 which requires one of the following cipher suites:

TLS_AES_128_GCM_SHA256
TLS_AES_256_GCM_SHA384
TLS_CHACHA20_POLY1305_SHA256

Then running the basic_connect fails with with: awscrt.exceptions.AwsCrtError: AWS_IO_TLS_ERROR_NEGOTIATION_FAILURE: TLS (SSL) negotiation failed.
After doing a packet capture, I noticed the above cipher suites were missing from the Client Hello.
The issue only affects  V2 of this SDK. I dont have issues with V1, curl, or any other mqtt library. I was able to replicate this on Windows, Mac, and an Amazon Linux 3 image. If I downgrade to TLS13_1_2_2022_10, it works.
Expected Behavior
Sample basic_connect.py to connect
Current Behavior
Does not connect, TLS (SSL) negotiation failed
Reproduction Steps

AWS IoT > Connect > Domain configurations
Select the data-ats endpoint
Under security policy select TLS13_1_3_2022_10.
Save
Install aws python sdk v2: python3 -m pip install awsiotsdk
Download latest python sdk package with samples: git clone https://github.com/aws/aws-iot-device-sdk-python-v2.git
Add Iot certs to known location on client
Run

python3 ./aws-iot-device-sdk-python-v2/samples/basic_connect.py
--endpoint [endpoint]
--cert [path to client cert]
--key [path to client key]
--ca_file AmazonRootCA1.pem
SDK version used
1.22.0
Environment details (OS name and version, etc.)
Mac Sequoai 15.1.1

Use Case
Use TSL 1.3 on Mac with the aws-iot-device-sdk-python-v2
Proposed Solution
No response
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

Note, this does not only affect MAC, it is reproducible on Windows, Mac, and using the Amazon Linux 2 and 3 image.

@GeoSnipes This should not effect Linux. Please create a new issue if you are having problems. For Windows, we have a separate issue https://github.com/awslabs/aws-c-io/issues/609 where we are tracking this.


new fst releases available

this pull request is automated and triggered by new fst releases

This failed CI but... GitHub doesn't know about it? https://travis-ci.org/github/UAlbertaALTLab/cree-intelligent-dictionary/jobs/668826305

@Madoshakalaka, could you please check out this PR and see what the new FST broke?

@eddieantonio Sure

@eddieantonio I just realized there's a loophole in how we're doing this. The pr does update the latest fst files. However, the test database is NOT rebuilt with the newest fst, thus it may fail some tests unexpected.
All in all, the automatic pr is an incomplete automation. What needs to be done is to also build the test database.

@eddieantonio I just realized there's a loophole in how we're doing this. The pr does update the latest fst files. However, the test database is NOT rebuilt with the newest fst, thus it may fail some tests unexpected.
All in all, the automatic pr is an incomplete automation. What needs to be done is to also build the test database.

Ah, I see! This will be tough since it'd be weird to upload the test XMLs... or is it?

@eddieantonio I just finished updating the test. I don't think this specific test failed due to an not updated test database. The failures were due to our test examples depending too much on the fst output for pisin. The linguists changed it a lot. See my comments in the diffs.
But I can imagine the test database update issue to cause legitemate test failures later. For now I guess what we can do manual updates to the test database after FST releases.
For now I'll change the automated comment:

this pull request is automated and triggered by new fst releases

- this pull request is automated and triggered by new fst releases
+ this pull request is automated and triggered by new fst releases, please rebuild the test database on this branch

Please feel free to come up with automated approach to securely distribute the latest XML files.

@eddieantonio See #383 where I edited some prompts


DCOS-46294 - COPS-4205: No tasks show for a service

update @dcos/mesos-client to 0.2.6
update @dcos/http-service to 1.1.0

Closes DCOS-46294, See COPS-4205
Testing

npm i
make sure that /mesos/api/v1 endpoints have timestamp part _ts=<number>

rebased and force pushed in an attempt to retrigger CI (seems like it worked)

@brandonc could you re-approve? Nothing changed 😇

thanks @DanielMSchmidt  🤞 for ✅ in Jenkins

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


OLH-1593: Include hint text in emails for One Login Home

Proposed changes

What changed
Include hint text in emails for One Login Home.
This does hard code the client IDs for the Home frontend, but we have all the rest of the content duplicated here anyway so I didn't think that was too bad.
I'm using Notify's Optional content feature to show / hide the hint text line for events about One Login Home.
This relies on a template update which I've made in the Test Notify service. Once the PR is merged I'll apply the same template update to the live service
Why did it change
To explain to users what 'Your GOV.UK One Login Home' means
Related links
Checklists

Environment variables or secrets

[x] No environment variables or secrets were added or changed

Testing
I've deployed this to dev and triggered an email. I've also checked that the hint text doesn't show up when the variable is set to false.

Ah no, that's a separate optional block that adds a newline in the inset text block if the hint text is present to make the spacing better


Platform ZP not found

Did you install homebridge-lib?

I installed directly from config-ui-x search bar. Maybe there was no dependency for homebridge-lib?

Managed to work after installing homebridge-lib. May you can add that to install directly from ui-x when installing sonos-zp

And as you wrote in readme speaker serive
Dont work in home app. Maybe you can implement it now as this type https://developer.apple.com/documentation/homekit/hmservicetypespeaker?language=objc


Add back missing TraceException

As TraceException is defined in trace_event_impl and in the else-part, the module is not found, TraceException is of course undefined here. Add a dummy definition.

We use codereview for contributions. Please follow steps in https://github.com/google/trace-viewer/wiki/Contributing

Got it. My first time fixing code in GitHub. Will follow the steps.
2015-05-16 1:26 GMT+08:00 Nat Duca<EMAIL_ADDRESS>
We use codereview for contributions. Please follow steps in
https://github.com/google/trace-viewer/wiki/Contributing
—
Reply to this email directly or view it on GitHub
https://github.com/natduca/py_trace_event/pull/3#issuecomment-102463735.

Close it and use https://codereview.appspot.com/239950043/ for code review instead.


Comparison with "JNCC data from ESAS"

There is one dataset on OBIS that seems to contain ESAS data: https://obis.org/dataset/8426d16e-cb66-4b6e-8d3c-d8e8b977fc79 published from this IPT.
It should be investigated in what sense the dataset overlaps with the now official ESAS dataset published via this GitHub repository.

Comparison:

year
jncc
esas
diff

1979
2,469
2,708
239

1980
77,340
77,966
626

1981
87,299
88,412
1,113

1982
89,683
90,348
665

1983
88,865
89,222
357

1984
63,779
66,105
2,326

1985
45,216
49,930
4,714

1986
65,552
71,956
6,404

1987
79,309
149,014
69,705

1988
34,581
103,227
68,646

1989
18,140
63,590
45,450

1990
24,630
54,791
30,161

1991
36,077
89,714
53,637

1992
49,595
94,112
44,517

1993
20,622
92,997
72,375

1994
58,765
132,416
73,651

1995
91,698
141,317
49,619

1996
44,407
71,658
27,251

1997
57,089
161,434
104,345

1998
67,908
131,269
63,361

1999
7,157
56,099
48,942

2000
12,705
62,919
50,214

2001

106,842
106,842

2002

109,174
109,174

2003

121,998
121,998

2004

64,419
64,419

2005

102,004
102,004

2006

67,479
67,479

2007

112,353
112,353

2008

153,260
153,260

2009

89,407
89,407

2010

85,125
85,125

2011

110,178
110,178

2012

108,852
108,852

2013

66,856
66,856

2014

82,639
82,639

2015

64,179
64,179

2016

132,428
132,428

2017

13,128
13,128

2018

10,112
10,112

2019

8,762
8,762

2020

3,495
3,495

2021

4,974
4,974

Total
1,122,886
3,558,868
2,435,982


play function not return 1 in macOS

int result = await audioPlayer.play(url)
in macOS  result = 0

Play returns void. So it's probably 0. Nothing wrong here.


v2.5.1

Summary by CodeRabbit

New Features

Introduced new configuration options for logging and retry behavior.
Added callback functionality to download operations.
Enhanced documentation on customizing logging and defining directory naming rules.

Bug Fixes

Fixed method naming inconsistency in image decryption and saving process.
Updated URL protocol in exception message for improved security.

Documentation

Expanded tutorials on logging customization and directory naming conventions.

Refactor

Improved readability and clarity in option handling and plugin invocation.
Streamlined return values in entity creation and indexing methods.

Style

Standardized function and variable naming for better clarity and consistency.

@coderabbitai review


zoro streaming links

Bro are you taking episode streaming links part from consumet cuz i was previously using their api their zoro streaming links are not working but yours are whats the difference
I am specifically taking about this file https://github.com/ghoshRitesh12/aniwatch-api/blob/main/src/extractors/rapidcloud.ts
because before this the code is same.

@Shuvadip-Ghosh
Well, yes I have taken consumet's extractor. I try to keep the extractors updated as their's, so there shouldn't be any difference at all.

bro i tested both just now the links i get from your api is working but the links from consumet package is not working there has to be some difference please bro I need it !!!

@ghoshRitesh12 bro i tested both just now the links i get from your api is working but the links from consumet package is not working there has to be some difference please bro I need it !!!

@Shuvadip-Ghosh
It's the same extractor, I just checked. They may have some proxy issues.

bro the vidcloud streaming link are not working what to do ?? the decoded m3u8 links are not working what to do ??

Aniwatch doesn't have a server named vidcloud.
Need more clarification.


[feat]: Ask user before stopping docker

Is your feature request related to a problem? Please describe.
When using the sandbox the CLOSE button at the top corner closes the workspace and stops docker.
The feedback from the users if they would like to have a confirmation prompt to ask whether docker should be stopped.
Describe the solution you'd like
Add a prompt and ask for confirmation before stopping docker

@digiserg no - we wont do this. Users can manage that themselves and there is a lot of complexity around how the spawned processes work in relation to windows and mac. We are not changing this now.


feat: #1239 adding business to bceid references

Adding "Business" to all BCeID references.

Hi Nick, since we started to work on the accessibility, it's better to update the ids related to "bceid" to "business bceid" as well. Please our code and make sure those are updated as well, thanks!!

Also in the table, the user domain is still showing "BCEID", and by checking the data, it's getting directly from the api return. So please create a new ticket to update the description of "BCEID" in the user_type_code table in our database.


False "Code is unreachable" warning when using not isinstance()

When using not isinstance() to check if a variable is of the required type/s, Pylance incorrectly reports the indented code block as unreachable.
 Environment data

Language Server version: 2024.7.1
OS and version: linux x64
Python version (and distribution if applicable, e.g. Anaconda): 3.12
python.analysis.indexing: true
python.analysis.typeCheckingMode: off

 Code Snippet
def my_func(var: int | str) -> None:
    if not isinstance(var, (int, str)):
        print('not ok')  # <-- Pylance: Code is unreachable
    else:
        print('ok')

Thanks for the issue. This is by design. The type for var is (int | str), it cannot be anything else as far as Pylance is concerned. If you call my_func with something else (and you enable typeCheckingMode=basic), Pylance should give you an error.

See this issue for more information:
https://github.com/microsoft/pylance-release/issues/6131

There's been a lot of recent discussion about this behavior from the perspective of package authors. See https://github.com/microsoft/pylance-release/issues/5647 for example.
Are you a package author? Our prerelease build from today (2024.7.102) includes a new config setting that allows you to disable the tagged hints which cause the if block's code to be dimmed in your scenario. You can set python.analysis.disableTaggedHints to true if you'd like to disable this feature.

Thank you both for the prompt replies. I'm not a package author and I actually do find the hints useable.
Reading #5647, I have to agree with @sztomi regarding this behaviour: marking the indented code as unreachable when it is clearly not the case in any way, shape, or form, is a terrible "by design" choice IMO. It is both logically incorrect and simply misleading.
The fact that Pylance "thinks" this is the case solely based on Pyright's logic, indicates to me that these two tools are way over-coupled with each other to the point where Pylance's ability to work correctly is severely hindered. This isn't the first Pylance bug I encountered where it turned out an obviously incorrect behaviour was due to how Pyright operates and "nothing could be done".
I appreciate Pylance's team hard work and dedication and recognize that users complaining about tools they got for free is the epitome of ungratefulness. However, please take this to heart: if Pylance's approach to solving such a trivial issue is hiding the incorrect warning instead of actually addressing the underlying faulty logic that causes it, VS code will cease to be a useful Python development tool and will soon fall behind PyCharm/Zed/Lapce and others.
Thanks again for your time.

This isn't the first Pylance bug I encountered where it turned out an obviously incorrect behaviour was due to how Pyright operates and "nothing could be done".

What would be the wanted behavior? A warning on the type specification for var? That int | str isn't actually the possible types?

I wonder if maybe the warning we give should mention
"Given that the type of 'var' is declared 'int | str', this code path is unreachable. You may want to further specify the type of 'var'"

@valorien, the scenario in #5647 was a public API which external users could call with incorrect types. In that case a package author would, understandably, want to validate the types of the function's parameters and raise errors for invalid types. And it's strange from the package author's perspective that that intentional validation code is flagged as unreachable.
But it sounds like that's not the case for you? This is a function that is only called from within your code base? If that's the case, why do you want to add extra code to detect invalid parameter types? As Rich pointed out above, assuming you have python.analysis.typeCheckingMode set to something other than "off", any calls you make to my_func with an argument that is neither an int nor a str will be flagged with a reportArgumentType diagnostic.

@rchiodo I know I'm stating the obvious here, but type annotations are meaningless when it comes to Python's logic.
The fact that var is of type int | str does in no way make the conditional code in my example "unreachable".
What would be the wanted behaviour? Don't warn this block is unreachable when that's clearly not the case.
I can use type annotations to inform users of my code that var is of type some_type, and yet still decide I want to make sure (or raise a TypeError exception) when an unsupported type of variable is passed.
That is a completely valid and acceptable behaviour in Python and it does not make the code unreachable. A simple run immediately proves that, which only makes Pylance's "warning" even more questionable.

So what you're saying detecting this unreachability is useless because it's obviously for the exceptional case when the user passes in the wrong value. You did this on purpose, it's not a coding mistake and in fact you don't want to specify the arguments to allow for this code to be reachable because that gives the wrong impression to callers.

@debonte, thank you for elaborating on #5647.
It actually is the same case in my logic, though I'm building an internal tool where reading/configuration errors my occur, which is why type checks are needed. Again, the point is that this code is completely valid and is not unreachable.
The issue here is not whether Pylance's type checking will prevent me from calling a function with an incorrect type of argument, it is that while developing the function itself, Pylance is misleading me as a developer by telling me a block of code is unreachable.
There are cases where code blocks should be marked as unreachable. This is clearly not one of them and never will be since that code is easily reachable.

So what you're saying detecting this unreachability is useless because it's obviously for the exceptional case when the user passes in the wrong value. You did this on purpose, it's not a coding mistake and in fact you don't want to specify the arguments to allow for this code to be reachable because that gives the wrong impression to callers.

@rchiodo No, what I'm saying is that calling this code "unreachable" is simply incorrect and misleading. It is perfectly reachable, and this behaviour might also confuse developers further as they would assume actual cases of unreachable code can be ignored just like this one should. Pylance is bending the term "unreachable" here to mean something completely unrelated. It's worse than useless since it's simply not true.
I don't know on what basis you've decided users passing in wrong values is an exceptional case, but even if that was the case, marking this code block as unreachable would still be wrong. The fact that I did this on purpose for my testing doesn't mean it can't happen - and even then that code block would still not be considered "unreachable".
Please also take into account that not all users use VS code or an IDE, many have never heard or care about type annotations, and it's completely reasonable and valid for me as someone who writes a function to raise a TypeError with a friendly message when an unsupported type is passed.

problem is this is runtime type check
    if not isinstance(var, (int, str)):
        print('not ok')  # <-- Pylance: Code is unreachable

and the warning is design time (static analysis) type check.
and it sounds like you want us to understand runtime type not design time type. and that's not possible for us. we don't run code to know what the runtime type is. we only know the static time type which is int | str.
I don't believe any of static analysis tool will know what the runtime type will be. if you want that, you would need something like notebook that actually run the code.
"python.analysis.disableTaggedHints": false might be what you want.

Most of pylance's features (including semantic highlighting, completion suggestions, signature help, refactoring, etc.) are based on static type analysis. Static type analysis is intrinsically tied to reachability analysis. If a block is considered unreachable by a static type checker, it will have no effect on downstream types. If it is reachable, the static type analyzer must take into consideration any changes it makes to local state.
When pyright detects that code is unreachable by static analysis, it never generates an error condition (i.e. the condition never appears in VS Code's "problems" panel, and red squiggles never appear). Rather, pyright uses tagged hints to instruct the editor to display the text using a subtle grayed-out color. As a developer, you can then decide whether this is something you expect or not. Sometimes unreachable code is indicative of a bug, but sometimes it's not.
It sounds like you would prefer not to be notified of code that is statically determined to be unreachable. If that's the case, the python.analysis.disableTaggedHints will provide you with a way to disable these tagged hints, and you will not see any of the grayed-out blocks of code in your editor.
You are correct that there may be differences between runtime behavior and behaviors determined through static analysis. This is especially true in a language as dynamic as Python. A static analyzer needs to make certain assumptions. One of those assumptions is that if the developer has taken the time to add type annotations in their code, these annotations correctly describe the intended behavior at runtime. In your case, it sounds like you're using type annotations in a "looser" (as in, "less strict") manner.

from what you are saying, It seems you only consider syntactically unreachable code as unreachable code and doesn't consider type-wise unreachable code as unreachable code since in python, you can't force function parameters to be certain type.
so, is your asking us to split unreachable to be syntactically unreachable and type-wise unreachable ?

This is going deep beyond my understanding of the subject matter, so allow me to bow out.
But before I go, here's the same code snippet when it is written in PyCharm:

As you can see, PyCharm does not warn the user that this perfectly reachable code is "unreachable".
Also note that it is only not isinstance() that causes Pylance to issue this warning, while isinstance() by itself does not.
Thank you all for your time and I appreciate the feedback provided.

Also note that it is only not isinstance() that causes Pylance to issue this warning, while isinstance() by itself does not.

I'm not seeing that behavior in 2024.7.1 or our most recent prerelease build. Can you provide a code sample to explain what you mean?
def my_func(var: int | str) -> None:
    if not isinstance(var, (int, str)):
        print('not ok')  # <-- Pylance: Code is unreachable
    else:
        print('ok')

def my_func_reversed(var: int | str) -> None:
    if isinstance(var, (int, str)):
        print('ok')
    else:
        print('not ok')  # <-- Pylance: Code is unreachable

@valorien I just tried pycharm. and I don't think they provide unreachability check based on type like pylance. it only provides unreachability based on syntax
ex)
def foo():
    print(10)
    return
    print(10) <= pycharm only works for something like this.

but not for this.
class A:
    pass

def foo():
    a: A = A()
    if isinstance(a, A):
        print(1)
    else:
        print(2)

@debonte, the code you provided is exactly my point. Only the not isinstance() or else (when logically flipped and else == not isinstance()) are marked as unreachable. Why would any type check be "reachable" in this case? utterly confusing.
@heejaechang, thank you very much for checking. PyCharm may not provide unreachability warnings based on types, but it also doesn't issue completely false unreachability warnings like the one issued by Pylance that started this discussion.
You haven't indicated where the warning in your 2'nd code sample is so I'm not sure what to look for.

there is no warning in pycharm for the 2nd code since it seems not check reachability based on type
..
not sure what you meant by

Only the not isinstance() or else (when logically flipped and else == not isinstance()) are marked as unreachable. Why would any type check be "reachable" in this case? utterly confusing.

the code example flips condition and it shows expected behavior.

I see your point regarding PyCharm in this use case, and you're correct. I also understand your point regarding the flipped logic and why it's treated differently.
However, my point stands: marking if not isinstance(obj, types...) sanity checks as "unreachable", when they are absolutely perfectly reachable and necessary when users provide incorrect arguments to a called function, is a bug and not a feature.
PyCharm may not detect reachability based on type, but it also doesn't falsely flag reachable and perfectly functional code as unreachable, like Pylance does.

we recently added an option to disable type based reachability check. it will be released soon, (not in this prerelease though). it will be off by default if type checking mode is off and will be on by default if type checking mode is enabled.
when it is off, we will only show unreachable code if we can determine it without involving type such as
   return
   print(a) <= here


[master] Update Shell /vars command output

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues.

Fixes #36319 to master branch
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

This fix is already available in the master which was added by a sync PR related to 2201.2.x. branch.


Excessive quoting with line_width: -1

Recent versions of YAML quote excessively with line_width -1.
For example:
> puts Psych.dump({'b' => 'c'}, {line_width: -1})
---
"b": >-
  c

If you are bisecting this, the bug is not in 2.0.8 but is in 2.0.13, so it's somewhere in between. A cursory look show this as a likely suspect: https://github.com/tenderlove/psych/commit/2edf642b82ae88ed93ec5f6ed7ae699771c04fc6.

Yep, this seems like a bug.  What would you expect -1 to do?  My initial reaction is that it should raise an ArgumentError, since a negative line width seems like a result of a bug.  How are you encountering this?

Not as a result of a bug: I have been recommending the users of my gem to use -1 to remove max line width for years. ^^'
Throwing an ArgumentError for -1 could be OK if we document that 0 is the one true value to use to disable max width. It seems unlikely that this value is set dynamically in the user's code though, so perhaps we could just make values <= 0 work again?
If we throw an ArgumentError, the major version should probably be bumped.

Turns out line_width: 0 is broken as well.

Actually, -1 is documented as unlimited in the C API here:
https://github.com/tenderlove/psych/blob/master/ext/psych/yaml/yaml.h#L1864

@tenderlove I've given it a go in #255.
However, I discovered another issue: if line_width is not passed, best_width in yaml.h:1609 is actually garbage (uninitialised memory). Because it's garbage, sometimes it's greater or equal than zero, in which case it defaults to 80 here, but at other times it's negative and it defaults to MAX_INT here.


[Enhancement]: Change text color in config

What happened?
The text is always white, but with some backgrounds that's not the best looking color. It would be great to be able to set a text color the same way you can with background_color
Card Version
1.0.6
HomeAssistant Version
2022.11.5
Relevant javascript log output
No response

You could try customize the theme or the card itself using custom-ui.

Color is the same of ha-picture-card-text-color, it can be customized via a theme


Better formatting of the PowerShell code

Updated the formatting of the PowerShell code. On the website the New keyword was removed from the New-AzureADUser cmdlet.

Hi - is ```powershell the better way to mark a section to be displayed as  ?

@RobdeJong no, that is just for letting your editor know the preferred syntax highlighting.
The initial problem is something else, here is a screenshot of the issues:

In the first block of code, everything is on one line. So I changed that to a code block.
The second block with the New-AzureADUser cmdlet was defined just after the three backticks, so the editor thinks that New is the actual code language. By adding a linebreak that problem is resolved.

@estruyf Excellent response, thanks! I have been struggling with the MD formatting of articles a bit - it seems that using a 4 spaces or a single backtick to indicate  doesn't work well here. Do we have some documentation of the MD formatting we can use here?

@RobdeJong single tick-back is just for highlighting it in the current line. Code blocks are written with three tick-backs: https://help.github.com/articles/creating-and-highlighting-code-blocks/
Here is a useful doc page: https://help.github.com/articles/basic-writing-and-formatting-syntax/

@estruyf An example cannot have more than one code block. Powershell engine doesn't accept it. The build was failing so I had to change to single tick.

Hi - I was reading the doc links that @estruyf included, it doesn't mention anything about the PowerShell help engine MD syntax and requirements. Do we have these documented anywhere? What does ```powershell\ do exactly?

@RobdeJong  followed by PowerShell indicates that the code in the block is PowerShell and should be formatted as such.  For example if the code block was to contain Java - it would bejavascript - then the code.

Thanks, @TaraMeyer . How is the formatting of a PowerShell block different from the generic <Code> formatting?

@RobdeJong - the major difference is how it renders.  with the three ` followed by PowerShell - the text in the code block following the back ticks will "look" like the text would in a PowerShell console via the engine.  You'll find this mainly in the examples section of the MDs we support.  So the difference between the two is how each renders.


Custom app login screen with identityserver4

I am new to IdentityServer4. We have an existing Web app and now we are planning to write an API for 3rd party apps to connect. We want to use IdentityServer4 for the authentication. I have the IdentityServer server running but I want the user to be directed to our Web login page to login rather than the IdentityServer login. I can achieve this by setting the UserInteractionOptions.LoginUrl. After the login I redirect the user to the return Url that was passed in but the identity server redirects back to our web app and the keeps cycling. How can I tell the IdentityServer that the user has been authenticated? So that the IdentityServer shows the consent screen

have you read the docs?
http://docs.identityserver.io/en/release/topics/signin.html#login-workflow

Yes I have and that link does not explain how to achieve my scenario.

Well, your external app would somehow need to issue a cookie at your IdentityServer. How that's done is up to you. We do have customers doing that successfully.

Hey @amiteshs - have you solved your problem?


Need ur contact to discuss about future updates

send me ur discord or something, so i can communicate about this project

Sure. Username is lonewof2007. Discord, ofc.

i cant find it, so add me
natsumeaoi

All good. Check the DMs.


[BUG] refresh another uses cases were not resolved yet

The first two use cases are resolved :

refresh when reset cell content
refresh when renaming column name

But the last two use cases are not :

refresh when changing the select option color in column setting
refresh when changing select option and column is sorted

Originally posted by @imeed166 in https://github.com/RafaelGB/obsidian-db-folder/issues/300#issuecomment-1233915687

I also include refresh when the column is sorted


Create doesn't return the created object

Sails version: 1.0.0-46
Node version: 9.5.0
NPM version: 5.6.0
DB adapter name: connect-mongo
DB adapter version: 2.0.1
Operating system: MacOS Sierra V 10.12.6

When creating a new object, the new object is not returned.
Console.log output: undefined
Order.create({customerName: "test"}).exec(function (err, newOrder) {
            if (err) {
                res.send(500, {
                    error: 'Database Error'
                });
            }
            console.log(JSON.stringify(newOrder));
            res.json(newOrder);
        });

Hi @RJiryes -- in Sails 1.0, records are not automatically returned from create, createEach, update or destroy (for optimization reasons).  To get the created record, chain .fetch() onto your .create() call:
Order.create({customerName: "test"}).fetch().exec(function (err, newOrder) { ... }

See the Sails v1 upgrade guide for more info.

Thanks a lot @sgress454 👍 👍


OpenDSSDirect uses progress bar in daily solution mode

These two DLLs have version <IP_ADDRESS> to avoid confusion in i2x.  However, EPRI will be requested separately to update the OpenDSS version number in SVN, because there are other settings in the dproj files that I didn't want to affect.
You'll have to test the x86 DLL because I only have 64-bit Python.
Please deploy this to PyPi.org when finished.

Hi Tom, I will update it to PyPI this week. I need to change the variant part of the capacitor since Davis changed how we read and write pointers (https://sourceforge.net/p/electricdss/code/3608/).
I have unit tests, and I use TOX to test different Python versions, including 64 and 32 bites.
Thanks so much for your contribution.


Create UI for Payments in Profile

To contain a tab containing a list of payments and an option to cancel reoccurring payments. Payment types to be styled differently.

Need to add download receipt link.

Added receipt into branch feature-ui-payments-profile. Needs to be strapped up with data. #300

Possibility to automate email confirmation on donation:
Customized Email

users name
mailing address/email
If in memory of
If during campaign

Donations and Events need separate tabs.


[CUR-325] fix: removed nested div from p

Description

Removed nested div inside of a P tag

Issue(s)

Getting a React hydration error with mismatching JSX

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


✨ Add min and max values for INTEGER and NUMBER types

https://discord.com/developers/docs/interactions/application-commands#application-command-object-application-command-option-structure

This should be done after #227


Smartparking folder visible in the GitRepository

Repported by @TG-JC

Confirmed as a bug. The folder is created in parallel to the folder you specify, after you added a repository from the Main Mashup UI, before you even click Pull.

I believe this was a hidden small issue present for a long time.
-In the AddNewRepo service, I'm creating the Thing, doing Enable and Restart, and after that I'm setting the configuration which includes the proper folder.
-in the Java template, I'm using one of the lifecycle methods, "initializeThing", to prepare some things - like initializing the git repository on the disk. That method is executed during the very first enable/restart, before the correct configuration was set, and initializes the repository with the default value of the path - smartparking.
Since this is not really a bug, just a minor annoyance, I'll close this thread with won't fix.
If anybody needs to have this fixed, please reopen this issue in future.


[Python] Add a pyarrow.Table.aggregate function to compute aggregates against the whole table

Describe the enhancement requested
The implementation would be almost identical to pyarrow.TableGroupBy.aggregate except the keys list would be empty.  Currently this does not appear to be possible using an empty array of keys:
>>> tab.group_by([]).aggregate([("x", "sum")])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "pyarrow/table.pxi", line 5325, in pyarrow.lib.TableGroupBy.aggregate
  File "pyarrow/_compute.pyx", line 2145, in pyarrow._compute._group_by
  File "pyarrow/error.pxi", line 144, in pyarrow.lib.pyarrow_internal_check_status
  File "pyarrow/error.pxi", line 100, in pyarrow.lib.check_status
pyarrow.lib.ArrowInvalid: Cannot infer ExecBatch length without at least one value

Even if it were possible, I don't think it would be obvious to obtain the result in this way.
Component(s)
Python

Note, we may want to wait until #14867 merges as the corresponding C++ functionality will be more obvious (and tested)

Also related to #33832. Because if it's worth doing for tables, it would be even more valuable on datasets or scanners, for out-of-core aggregation.


maxOccurs=1 lead to List

my xsd appear as in attached file , then is ROOT  1-->1 Header   but when I build project , the hyperjaxb3 create
`@ManyToOne(targetEntity = HeaderType.class, cascade = {
CascadeType.ALL
})
@JoinColumn(name = "HEADER_IRIDE_HJID")
public HeaderType getHeader() {

    return header;
}`

it's my mistake or a bug ? I expect a OneToOne annotation because xsd tell ROOT can have only 1 header !

Hi @kronos72it
Hyperjaxb3 has been merged in jaxb-tools repository.
I guess you already asked this in SO (since it's reminding me something) but for reference :
It's normal behaviour since XSD only provide one-way relationship between your ROOT object and the HEADER objects, saying that one Root Object has only one Header Object.
But you don't have any information about the reverse link between Header and Root object.
Does one Header belongs to only one Root Object ? Or can you have the same Header object into 2 differents Root Objects ?
Since plugin can't decide, it creates the default relationship which is a @ManyToOne relationship (one header can be used by multiples Root objects)
You can find the documentation in wiki's page here : https://github.com/highsource/jaxb-tools/wiki/HyperJAXB3-Reference-Single-Page#mapping-as-one-to-one


feat(load.go): add warning on requirements.lock

What this PR does / why we need it:
Adds a warning when requirements.lock is used and the API version is not v1.
Partial fix for: #12853 (full fix to come when this functionality is hopefully removed in v4)
Special notes for your reviewer:
FYI @gjenkins8
If applicable:

[ ] this PR contains documentation
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

@gjenkins8 Are you still interested in this PR?


Can't find .gitmessage file

Looks like this bug still exists :(

#28

Fixed in 807509556f59fed267ca8e28f65deb6b1e64c5ac


clarify remove encryption for different OME ver

@KCCross  please review this

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@KCCross Please merge this PR. Thanks.

Samson, we need to talk about this. I'm pretty sure we covered this elsewhere in several other ways.


Report live value of d parameter in decentralizationLevel.

Context
Task #1692 will have added a skeletal decentralizationLevel parameter to the ApiNetworkParameters object.
Decision
Adjust the code so that this parameter reflects the true value of the d parameter, as reported by the network.
Acceptance Criteria

The GetNetworkParameters API endpoint must return a decentralization level percentage that reflects the true value of the d parameter, as reported by the network.

Development

[x] (https://github.com/input-output-hk/cardano-wallet/pull/1700)
Introduce ProtocolParameters type to hold (a subset of) the protocol parameters defined in a Formal Specification of the Cardano Ledger.
data ProtocolParameters = ProtocolParameters
    { decentralizationLevel
        :: Quantity "percent" Percentage
    , txParameters
        :: TxParameters
    }

[x] (https://github.com/input-output-hk/cardano-wallet/pull/1700)
Rewrite the GenesisBlockParameters type to include a ProtocolParameters value (whose type is defined above):
- data GenesisBlockParameters = GenesisBlockParameters
-     { staticParameters :: BlockchainParameters
-     ,     txParameters ::         TxParameters
-     }
+ data NetworkParameters = NetworkParameters
+     {  genesisParameters ::  GenesisParameters
+     , protocolParameters :: ProtocolParameters
+     }

[x] (https://github.com/input-output-hk/cardano-wallet/pull/1700)
Change the type of toApiNetworkParameters to:
- toApiNetworkParameters :: BlockchainParameters -> ApiNetworkParameters
+ toApiNetworkParameters ::    NetworkParameters -> ApiNetworkParameters

[x] (https://github.com/input-output-hk/cardano-wallet/pull/1715)
Revise documentation comments for the following types:

[x] NetworkParameters
[x] GenesisParameters
[x] ProtocolParameters

[x] (https://github.com/input-output-hk/cardano-wallet/pull/1725)
Generalize the wallet, network, and database layers to use ProtocolParameters instead of TxParameters. (ProtocolParameters includes TxParameters).

[x] (https://github.com/input-output-hk/cardano-wallet/pull/1725)
Adjust the chain-following code to retrieve the current value of the d parameter, in the same way we already do for transaction parameters.

[x] (https://github.com/input-output-hk/cardano-wallet/pull/1725)
Introduce a DecentralizationLevel type (based on the Percentage type).
Greater values should indicate greater levels of decentralization, as follows:

Value
Meaning

0%
Network is completely federalized

100%
Network is completely decentralized

[x] (https://github.com/input-output-hk/cardano-wallet/pull/1725)
Add a function to convert from d parameter values to values of type DecentralizationLevel, performing the following mapping:
{1 → 0%, 0.9 → 10%, 0.8 → 20%, ..., 0 → 100%}

QA

[x] Create unit and property tests to check that we correctly convert from values of d (provided by cardano-node) to values of DecentralizationLevel.
[x] Add unit test to lib/byron/test/unit/Cardano/Wallet/Byron/NetworkSpec.hs to see that decentralization parameter is updated ⇒ #1736.
[x] Add integration test  NETWORK_PARAMS - Able to fetch network parameters to check that decentralization parameter is correct (this is not checking parameter updates however) ⇒ #1736.

@rvl wrote:

I suspect that you will hook in to the same place that TxParameters are updated (fromPParams), and possibly rename/embed TxParameters to something more general.

lgtm.


Doesn't handle SvelteKit w/ changed base path

Describe the bug
When setting up the project as described in the Readme (onto a SvelteKit app), the application will not execute if the svelte config specifies an alternate base path:
svelte.config.js:
import adapter from '@sveltejs/adapter-auto';

/** @type {import('@sveltejs/kit').Config} */
const config = {
	kit: {
		adapter: adapter(),
		paths: {
			base: '/subfolder'
		}
	}
};

export default config;

To Reproduce
Steps to reproduce the behavior:

Create new SvelteKit project via 'npm create svelte@latest '
Modify svelte.config.js as shown above (just set a base path).
Follow steps as descibed in Readme to setup vite-plugin-rsw and create the default crate
Start dev server with 'npm run dev'

Expected behavior
The dev server should correctly resolve the WASM module to its actual location; not adjusted by base path.
Screenshots
Not a screen shot, but here's the error I'm getting:
[1] Failed to load url /rsw-hello/pkg/rsw_hello.js (resolved id: D:/Git/demo-wasm/rsw-hello/pkg/rsw_hello.js). Does the file exist?
[1] Failed to load url /rsw-hello/pkg/rsw_hello.js (resolved id: D:/Git/demo-wasm/rsw-hello/pkg/rsw_hello.js). Does the file exist?
[1] Error: Not found: /subfolder/rsw-hello/pkg/rsw_hello.js
[1]     at resolve (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:395:13)
[1]     at resolve (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:236:5)
[1]     at #options.hooks.handle (/@fs/D:/Git/demo-wasm/node_modules/@sveltejs/kit/src/runtime/server/index.js:41:55)
[1]     at Module.respond (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:233:40)
[1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Note that the two URLs at the top (D:/Git/demo-wasm/rsw-hello/pkg/rsw_hello.js) are actually correct, and I've confirmed that the files actually are there.
Desktop (please complete the following information):

Windows 10
Firefox
vite-plugin-rsw: 2.0.11, vite: 4.04, @sveltejs/kit: 1.3.1

Please configure [[crates]] -> root and try again. https://github.com/rwasm/rsw-rs#options

Process won't even start:
[0] [🦀 rsw::crate] rsw-hello The system cannot find the path specified. (os error 3)
[0] rsw watch exited with code 1

Even attempted moving the crate into a folder called 'subfolder' afterwards:
[1] Failed to load url /subfolder/rsw-hello/pkg/rsw_hello.js (resolved id: D:/Git/demo-wasm/subfolder/rsw-hello/pkg/rsw_hello.js). Does the file exist?
[1] Error: Not found: /subfolder/subfolder/rsw-hello/pkg/rsw_hello.js
[1]     at resolve (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:395:13)
[1]     at resolve (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:236:5)
[1]     at #options.hooks.handle (/@fs/D:/Git/demo-wasm/node_modules/@sveltejs/kit/src/runtime/server/index.js:41:55)
[1]     at Module.respond (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:233:40)
[1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

You need to install rsw and run rsw watch in a terminal, then open a new terminal and run yarn dev:
cargo install rsw

How is your rsw.toml set up?

How is your rsw.toml set up?

As I said in the OP, the rsw.toml file is exactly as it was described following the instructions in the Readme. However, here is a dump:
name = "rsw"
version = "0.1.0"

#! time interval for file changes to trigger wasm-pack build, default `50` milliseconds
interval = 50

#! link
#! npm link @see https://docs.npmjs.com/cli/v8/commands/npm-link
#! yarn link @see https://classic.yarnpkg.com/en/docs/cli/link
#! pnpm link @see https://pnpm.io/cli/link
#! The link command will only be executed if `[[crates]] link = true`
#! cli: `npm` | `yarn` | `pnpm`, default is `npm`
cli = "npm"

#! ---------------------------

#! rsw new <name>
[new]
#! @see https://rustwasm.github.io/docs/wasm-pack/commands/new.html
#! using: `wasm-pack` | `rsw` | `user`, default is `wasm-pack`
#! 1. wasm-pack: `rsw new <name> --template <template> --mode <normal|noinstall|force>`
#! 2. rsw: `rsw new <name>`, built-in templates
#! 3. user: `rsw new <name>`, if `dir` is not configured, use `wasm-pack new <name>` to initialize the project
using = "wasm-pack"
#! this field needs to be configured when `using = "user"`
#! `using = "wasm-pack"` or `using = "rsw"`, this field will be ignored
#! copy all files in this directory
dir = "my-template"

[[crates]]
name = "rsw-hello"
link = true

#! ################# NPM Package #################

#! When there is only `name`, other fields will use the default configuration

#! 📦 -------- package: rsw-hello --------
# [[crates]]
# #! npm package name (path: $ROOT/rsw-hello)
# name = "rsw-hello"
# #! run `npm link`: `true` | `false`, default is `false`
# link = false

#! 📦 -------- package: @rsw/utils --------
# [[crates]]
# #! npm package name (path: $ROOT/utils)
# name = "utils"
# # #! scope: npm org
# scope = "rsw"
# #! run `npm link`: `true` | `false`, default is `false`
# link = false

#! 📦 -------- package: @rsw/hello --------
# [[crates]]
# #! npm package name (path: $ROOT/@rsw/hello)
# name = "@rsw/hello"
# #! default is `.`
# root = "."
# #! default is `pkg`
# out-dir = "pkg"
# #! target: bundler | nodejs | web | no-modules, default is `web`
# target = "web"
# #! run `npm link`: `true` | `false`, default is `false`
# link = false
# #! rsw watch
# [crates.watch]
# #! default is `true`
# run = true
# #! profile: `dev` | `profiling`, default is `dev`
# profile = "dev"
# #! rsw build
# [crates.build]
# #! default is `true`
# run = true
# #! profile: `release` | `profiling`, default is `release`
# profile = "release"

As for the 'rsw watch' command, it was added to the 'dev' script as described be the Readme, so it runs everytime the dev server is started. It is also the source of the error messages I've been pasting.

Is the rsw-hello directory initialized under the project root path?

Is the rsw-hello directory initialized under the project root path?

Yes

You can execute the rsw watch command separately and see if the rsw-hello/pkg/rsw_hello.js file is generated.

As I said before, the file is begin generated, it's just not being found. However, I did run these commands as you indicated and got the same output as before:
Failed to load url /rsw-hello/pkg/rsw_hello.js (resolved id: D:/Git/demo-wasm/rsw-hello/pkg/rsw_hello.js). Does the file exist?
Error: Not found: /subfolder/rsw-hello/pkg/rsw_hello.js
    at resolve (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:395:13)
    at resolve (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:236:5)
    at #options.hooks.handle (/@fs/D:/Git/demo-wasm/node_modules/@sveltejs/kit/src/runtime/server/index.js:41:55)
    at Module.respond (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:233:40)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Your description doesn't help me locate the problem. Please submit the code to the github repository, including the files in rsw-hello.

Public repo: https://github.com/SenojLuap/demo-wasm

Failed to load url /rsw-hello/pkg/rsw_hello.js (resolved id: /Users/lencx/github/demo-wasm/rsw-hello/pkg/rsw_hello.js). Does the file exist?
Error: Not found: /rsw-hello/pkg/rsw_hello.js
    at resolve (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:395:13)
    at resolve (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:236:5)
    at #options.hooks.handle (/node_modules/@sveltejs/kit/src/runtime/server/index.js:41:55)
    at Module.respond (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:233:40)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
The request url "/Users/lencx/github/demo-wasm/rsw-hello/pkg/rsw_hello.js" is outside of Vite serving allow list.

- /Users/lencx/github/demo-wasm/src/lib
- /Users/lencx/github/demo-wasm/src/routes
- /Users/lencx/github/demo-wasm/.svelte-kit
- /Users/lencx/github/demo-wasm/src
- /Users/lencx/github/demo-wasm/node_modules

Refer to docs https://vitejs.dev/config/server-options.html#server-fs-allow for configurations and more details.

svelte config changed, restarting vite dev-server. changed file: /Users/lencx/github/demo-wasm/svelte.config.js

The resource you are accessing is not allowed, you can check the documentation and just do the configuration below. https://vitejs.dev/config/server-options.html#server-fs-allow
import { sveltekit } from '@sveltejs/kit/vite';
import { ViteRsw } from 'vite-plugin-rsw';

const config = {
	plugins: [sveltekit(), ViteRsw()],
	server: {
	    fs: {
	      // Allow serving files from one level up to the project root
	      allow: ['..'],
	    },
  	}
};

export default config;

How did you get that additional output? That would have made the problem much easier to understand


[Feature][数据开发] hive作业 不能上线问题

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description

Use case
hive作业正常上线，dolphinscheduler 可以成功调度
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

what's your  version of hive datasource jdbc

use Dinky 1.0.


[vde_switch] No buffer space available

Lima Version: 0.6
For creating a local k8s cluster I started two instance with --vmnet-mode=bridged specified for networking. After the initialization (by Kubeadm) of control-plane, node instance was expected to join the cluster.
Howerver, node instance kept stuck into NoReady status and I found the console of vde_switch kept printing "vde_switch: send_sockaddr port 3: No buffer space available".
I tried to increase wmem_max using:
echo 83886080 | sudo tee /proc/sys/net/core/wmem_max

But nothing resolved.
I wonder if this is a bug?
$ sudo vde_vmnet --vmnet-mode=bridged --vmnet-interface=en0 /tmp/vde.ctl
Initializing vmnet.framework (mode 1002)
Using network interface "en0"
* vmnet_mtu: 1500
* vmnet_interface_id: CD65D0DC-6BC7-4E0F-9F31-FD8A255DDD3E
* vmnet_max_packet_size: 1514
* vmnet_mac_address: 72:7e:fd:a5:36:a7

$ vde_switch
vde_switch: send_sockaddr port 3: No buffer space available
vde_switch: send_sockaddr port 3: No buffer space available
vde_switch: send_sockaddr port 3: No buffer space available
vde_switch: send_sockaddr port 3: No buffer space available

"Switchless mode" may work as a workaround
https://github.com/lima-vm/vde_vmnet/tree/v0.4.0#ptp-mode-switchless-mode

"Switchless mode" may work as a workaround
https://github.com/lima-vm/vde_vmnet/tree/v0.4.0#ptp-mode-switchless-mode
https://github.com/lima-vm/lima/blob/v0.6.0/pkg/limayaml/default.yaml#L133

$ sudo vde_vmnet /tmp/vde.ptp[]
zsh: no matches found: /tmp/vde.ptp[]

Am I missed anything?

Did I missed anything?

I don't know about zsh, but you'll probably have to escape the brackets

Also, I notice that readme said the ptp mode doesn't support multi vm

That description is for shared mode.
Should work for multi-VM with bridged mode (untested).


[Bug]: CanvasPointerField disappears in Repeater

What happened?
Hi,
now I am implementing the creation of a field inside the Repeater layout, and when creating a new Repeater item, the field appears in the newly created one, and disappears in the previous items. Do you have any ideas how to implement working with the Repeater layout?
How to reproduce the bug
When I add a CanvasPointerField inside the Repeater and click AddItemButton, the CanvasPointerField in the previous Repeater item disappears
https://github.com/user-attachments/assets/f0a880d1-5fb9-4104-8ffb-e79001d7d9f4
Forms\Components\Repeater::make('body')
    ->columnSpanFull()
    ->schema([
        CanvasPointerField::make('points')
            ->pointRadius(15) // default is 5
            ->imageUrl('https://avatars.githubusercontent.com/u/97165289')
            ->width(200) // required
            ->height(200) // required
            ->label('Select body parts that are in pain')
            ->columnSpanFull(),
    ]),

Package Version
1.0.3
PHP Version
8.3
Laravel Version
11
Which operating systems does with happen with?
macOS, Windows, Linux
Notes
No response

We are having problems recording the marked locations to the database. Can you provide information about this issue?

Actually, disappears in almost all dynamic elements that are not visible when the page is loaded. Same issue with Form Steps: if CanvasPointerField is NOT in the first step that's visible on page load, it won't be visible at all

This is due to the Livewire updates and rebuilds the DOM that canvas is attached to. Please see my PR for details:
https://github.com/ruelluna/canvas-pointer/pull/6