Support for .NET Core?

Do you any plans to support your library running on .NET Core in the near future?

Nope.
Why -> I feel like this library should be put into Maintenance Mode as there are heaps better options IMO now to do minification/bundling.

Thanks. Can you clarify on these better options from your point-of-view?
I'm using your awesome library in a WinForms desktop application (a german CMS) and never found an alternative way to compress JavaScript and CSS other than your library.
So I'm very keen on knowing what you see as the alternatives.

Oh wow. I never thought that this library would be used in a desktop application. Um .. er ... I don't really have an honest answer, actually :blush:
I was thinking this library would only be used with ASP.NET websites .. which most people are using grunt/gulp/webpack, etc to do all their minification and bundling these days.

What an interesting application for it - just goes to show how you should never make assumptions about how your library will be used :)
@UweKeim Are you using it as a library or using the msbuild tasks?
Also have you considered having a crack at porting to .NET Core yourself?
Or, as @PureKrome says, you could look at gulp or web pack as the cool kid on the block now to do your minification....

@freeranger As a library.
The user of can activate a checkbox and let all his CSS and JavaScript files getting compressed before uploading to their FTP server.
Probably I can include Nodejs into my application and use some library out there to compress.

What an interesting application for it - just goes to show how you should never make assumptions about how your library will be used :)

:point_up: this!

Hmm... I just ran the portability analyser: https://visualstudiogallery.msdn.microsoft.com/1177943e-cfb7-4822-a8a6-e56c7905292b
and according to it, our codebase is highly compatible, so it would be fairly trivial to port:


Option + Left/Right/Delete don't work in the terminal window

The terminal window is great. However, the navigation shortcuts to navigate one word forward or back don't appear to work. Instead of jumping forward and back one word, they print the following characters:

Option + Left: ;5D
Option + Right: ;5C

Option + Delete also doesn't delete a word at a time, and instead just behaves as a regular Delete, deleting one character at a time.
These shortcuts work normally in regular text boxes (e.g. here on GitHub) or in macOS Terminal when "Use Option as Meta key" is enabled.
Environment:

VSCode Version: 1.7.2
OS Version: macOS 10.12.1

Duplicate https://github.com/sourcelair/xterm.js/issues/225

@Tyriar - Thanks for the pointer to the upstream issue.
Technically, this is not a duplicate since this is an issue affecting VS Code, even though the root issue is upstream.
After the upstream issue is fixed, how will users know when that fix is included in VS Code? Would this issue not be the correct place to communicate that?
Don't mean to nitpick on issue management; I'm just curious as to how things are supposed to work.

@nchammas good question :smile:
I've been using a sort of hybrid approach for managing issues around the terminal to date, sometimes having the issue in the vscode repo if it's important, and not if it's not so important. It turns out this is a huge pain to manage all these different issue so I've decided to move to a system where if the issue will be fixed upstream and all that needs to be done is upgrade the dependency then I close it in vscode. If there will be additional integration work necessary to get the fix I keep it open in vscode.
The reason I'm moving to a system like this is because I spend a big chunk of my time contributing to xterm.js, so much so that it's linked as a dependency to vscode by pinning a commit, not using the stable version. I do this because of my familiarity with it, to dogfood recent changes and because I have commit access on xterm.js as well so I can freely manage the issues over there.
Due to this change I've started going through the commits for xterm.js for each release and pulling in notable fixes/features that came through upstream in the release notes. I also think it's beneficial to more centralize the discussion upstream and to also give the other owners of that xterm.js more insight into how many people are experiencing that particular issue (by count of closed issue links).

Makes sense. Thanks for elaborating. 👍


Typo

Coverage increased (+4.7%) to 78.923% when pulling 8c01c908d0b7108b5a05494db15126b76dfcac5c on ligurio:patch-2 into 674bef063ac6d0d50659ae73868bcfba7309cb89 on ajvb:master.

@ligurio Thank you for this! Need to merge master in to your branch before I can merge it in.


removed rabbitmq specs that arent required anymore. The log_level and…

… log file permissions are already checked in the serverspec.

LGTM.


Bug: mux-uploader-retry not shown on upload error + retry not reseting mux-uploader-progress

Is there an existing issue for this?

[X] I have searched the existing issues

Which Mux Elements/Packages does this apply to? Select all that apply
mux-uploader
Which browsers are you using?
Edge ("Edgeium")
Which operating systems are you using?
Windows
Description
I am reporting two bugs in one issue.
Reduced test case
https://gist.github.com/theazgra/2c88938a3198540b6e6ecb9324e47d3c
Steps to reproduce

Provide invalid endpoint url to trigger upload-error
Try to upload video/audio
Upload fails

Current Behavior
Upload fails. Correct status message (error message) is shown. But retry button (<mux-uploader-retry>) is not shown.

Also when i modify HTML in inspector, showing the <mux-uploader-retry> button, clicking in doesn't reset <mux-uploader-progress> element state. This is screenshot after click the button:

Expected Behavior

<mux-uploader-retry> is shown, when upload fails. Allowing user to click the button.
state of <mux-uploader-progress> is reseted after reseting uploader state (progress bar and percentage are hidden)

Errors
No response
What version of the package are you using?
1.0.0-beta.6

Thanks for filing the detailed issue and the handy screenshots. Our team's a bit stacked in our priority queue right now, but I'll be sure to keep you posted if/when we're able to make progress on this!

Hey @theazgra I'm hoping to be able to pick this up soon. Do you happen to know if this issue was unique to Windows+Edge, or does it show up on other browsers as well (windows or otherwise)?


Error with some manga - RuntimeError: Bad password

Comix works with most titles however there seems to be problems with manga published by Kodansha?. Both "Hozuki's Coolheadedness" and "Kino's Journey" cannot be saved.
# python3 comix.py 871492
871492 : Kino's Journey - v06
Downloading page 000 . . .Traceback (most recent call last):
  File "/home/user/Downloads/comix-main/comix.py", line 138, in <module>
    cmx.download()
  File "/home/user/Downloads/comix-main/comix.py", line 114, in download
    zf.extractall(content_folder, pwd=image_key)
  File "/usr/local/lib/python3.9/dist-packages/pyzipper/zipfile.py", line 2106, in extractall
    self._extract_member(zipinfo, path, pwd)
  File "/usr/local/lib/python3.9/dist-packages/pyzipper/zipfile.py", line 2159, in _extract_member
    with self.open(member, pwd=pwd) as source, \
  File "/usr/local/lib/python3.9/dist-packages/pyzipper/zipfile.py", line 2013, in open
    return self._open_to_read(mode, zinfo, pwd)
  File "/usr/local/lib/python3.9/dist-packages/pyzipper/zipfile.py", line 2024, in _open_to_read
    raise e
  File "/usr/local/lib/python3.9/dist-packages/pyzipper/zipfile.py", line 2021, in _open_to_read
    return self.zipextfile_cls(zef_file, mode, zinfo, True, pwd)
  File "/usr/local/lib/python3.9/dist-packages/pyzipper/zipfile.py", line 1203, in __init__
    self.read_init()
  File "/usr/local/lib/python3.9/dist-packages/pyzipper/zipfile.py", line 1218, in read_init
    self._decrypter = self.get_decrypter()
  File "/usr/local/lib/python3.9/dist-packages/pyzipper/zipfile.py", line 1306, in get_decrypter
    decrypter = self._decrypter_cls(
  File "/usr/local/lib/python3.9/dist-packages/pyzipper/zipfile_aes.py", line 61, in __init__
    raise RuntimeError("Bad password for file %r" % zinfo.filename)
RuntimeError: Bad password for file 'COMIXOLOGY_BOOK_ENCRYPTED_HD_0001.jpg'

I don't have this issue with volumes from other publishers so far.

The password derivation fails since Kodansha's imprints, Vertical and Digital-First have unique publisher IDs delivered in the protobufs but the passwords are still generated with Kodansha's publisher ID. Fixed it in f93f0d7e32b014e2e6de5530ec8ae6ddad4bc8f3 with a hack for now.

@athrowaway2021 thanks for the fix. But I had to replace publisher_id with self.publisher_id, then it works.
I guess it should be like this:
        if self.publisher_id == "274" or self.publisher_id == "281":
            self.publisher_id = "6670"


Handle invalid connection

Thanks for the package - very useful.
Currently, the server throws and exits when it can't connect to the server. I think it would be better for proxy to continue operation when it can't connect to the server, since it's a very common case. Sometimes the other server is still booting up - may be temporarily down - or you forgot to turn it on. It currently throws:
internal/streams/legacy.js:61
      throw er; // Unhandled stream error in pipe.
      ^

Error: connect ECONNREFUSED <IP_ADDRESS>:8080
  at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16) {
  errno: -61,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 8080
}
lcp --proxyUrl http://localhost:8080 exited with code 1

And also a nice error message would be good too something like "Cannot connect to http://localhost:8080"

Going to close this issue - let me know if you need it back up again.


Refreshing page many times makes tasks unavailable

After repeatedly refreshing the page, all the tasks become unavailable. The start page says, for example, "5 tehtävää saatavilla" but when cliking on a task to start it, it tells me "Uusia tehtäviä ei löytynyt."

This happens, because each time a page is refreshed / user is given a new task, the task is marked as that users property. One user can hold N (=8) simultaneous tasks. After a short while these tasks expire and user can get more tasks. This is a feature in the original repo.


Add Custom Font to labelStyle is Not working

when is user custom font in react native is working fine , but is not working in react-navigation DrawerItems
please any advice ?

Closing because you haven't followed the issue template; please open a new one that follows the template.
Without that, it's nearly impossible to understand & investigate the issue. I suggest you also try (in the new issue) to answer/explain in a way that fits these questions:

have you tried updating to the latest release?
does it happen only on Android/iOS?
does it happen on both Debug and Release modes?
does it happen with Debugger On or Off? Both?
Can you provide a GIF or a repo or a snack to reproduce this issue?

Maybe related to https://github.com/react-community/react-navigation/issues/374


waypoint-style-the-html-body-element completed before correct code entered

Challenge http://www.freecodecamp.com/challenges/waypoint-style-the-html-body-element has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
This waypoint was completed before correct code completely entered.
<style>
  body {
    background-color: black;

</style>

The closing bracket is missing.
Thank You

Thanks @AEA2002 for pointing this out!

I tested this waypoint and the issue is not fixed:


Revert "Use protoversion for containerd version"

This reverts commit d2e319523d15bab57432969688b5f419ec76bc54.
We decided to trim deps as possible at first.

LGTM


NIFI-6546 - Add JsonPath set value support

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables ability to set JsonPath values.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

I'll try to add this to my todo list.

@tpalfy - I've updated the code based on your review.
@tpalfy @MikeThomsen - Let me know if you any additional advice for me.
Thanks for your feedback.
Mans

@mans2singh you need to rebase off of master because you have a merge conflict.

@MikeThomsen -
I've rebased to master.
Please let me know if you have any additional advice/recommendations.
Thanks

@MikeThomsen -
I've updated the code based on your review.
Please let me know if you have any additional comments.
Thanks


qml: LimeWindow.qml

It would make sense to separate out the wxndow specific bits into a separate qml file.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1379647-qml-limewindow-qml?utm_campaign=plugin&utm_content=tracker%2F282001&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F282001&utm_medium=issues&utm_source=github).

Migrated to limetext/lime-qml#12.


[QUESTION] Is their a way to get the VIO offline using prerecorded stereo images and imu data?

Dear,
Is it possible to use the spectacularAI SDK to calculate VIO with the oakd-pro camera (with BMI270 IMU), when the rectified stereo images and the imu have been prerecorded with a certain timestamp?
If so what information would all be required to do this?
Kind regards,
YD

Yes, it is possible with the publicly available SDK if you record the data through our Python recording tool https://github.com/SpectacularAI/sdk-examples/blob/main/python/oak/vio_record.py . Replay API example here https://github.com/SpectacularAI/sdk-examples/blob/main/python/oak/vio_replay.py.
If the data is recorded in another format, you need to use our core SDK, which is available as a paid product (through sales: https://www.spectacularai.com/#contact)


Use net instead of link

Hi,
Is it possible use net instead of link in Phundament to let container comunicate in docker-compose? I've read that link will be deprecated soon, maybe it will change the way the container are linked to each others?

Yes, I plan to update this.
Here's an example how a Phundament app works with networking and without links (needs to be adjusted a bit for phundament/app)

Ok, so I can consider this issue closed. Thank you!

See the commit above for a first draft, but we're having some issues with it (https://github.com/docker/docker/issues/21168).
Would be great if you could give feedback, if you're also having this problem or not.


Error loading wasm-bindgen-minimal example

I tried running the wasm-bindgen-minimal example and got this error:
Error loading Rust wasm module 'wasm_bindgen_minimal': TypeError: Import module '__wbindgen_placeholder__' is invalid

0: Import module '__wbindgen_placeholder__' is invalid
wasm-bindgen-minimal.js (46,20)

Compiled on Windows 10
Rust: nightly-2020-04-06-x86_64-pc-windows-msvc
Cargo web: 0.6.26
Browser: Firefox 75.0

I followed these steps:
cargo install cargo-web

gh repo clone koute/stdweb

cd stdweb

cd examples

cd canvas

cargo web start --target=wasm32-unknown-unknown

Terminal read warning: 47 warnings emitted - but I still tried to see the final result in the browser.
I got this error in browser's console for localhost:8000:
canvas.js:631 Encountered a panic!

__cargo_web_snippet_dc2fd915bd92f9e9c6a3bd15174f1414eee3dbaf @ canvas.js:631
canvas.js:583 Panic location: /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/mem/mod.rs:659

I tried the todomvc example and got the same errrors in terminal and console. Could not interact with page for the todomvc example, but the canvas example just showed a blank screen.


⚠ ClamAV has degraded performance

In 05733d6, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 445 ms

Resolved: ClamAV performance has improved in 02a7cf9.


Add parth.ninja to webring

Hi!!!! I added the webring icon to the footer, so it will be on all pages at the bottom. There are a various pages that talk about my hobbies and work, and there is also a contact page at /hello. There are blog posts and other stuff as well.
Thank you and also thanks for maintaining this really fun webring!

Hey Parth!
Your website is absolutely gorgeous :) Glad to be adding it to the webring, I love that the about page leads to all these different subsections :) Looking forward to following it grow!


add guidance for URN page

Description of change
Add guidance copy to URN page
Link to relevant ticket
https://dsdmoj.atlassian.net/jira/software/projects/CRIMAP/boards/897?selectedIssue=CRIMAP-206
Screenshots of changes (if applicable)

Just needing a rebase - I merged ahead of you, didn't realise!

Just needing a rebase - I merged ahead of you, didn't realise!

Oh no worries. We should be able to merge in any order and updating the branch before it gets merged is rightly the responsibility of whoever submitted the PR.


Added snake as a showcase

Please checkout the provided sample at https://github.com/programmeramera/snake-in-tetra and if it is good enough, feel free to included it in the showcase.
Any comments are welcome!

Looks great, thank you for reminding me how terrible I am at Snake 😄 The code looks good too, nice to have another good single-file example!

I've also cherry picked this commit onto the release branch so that it'll show up on the website immediately (need to rethink this branching strategy, I think...)


Properly trace cloud events

Pretty print was being called and concatenated regardless the logger is enable or not. Due to the massive amount of events that we might potentially received there, this might well explain why some test were timing out. In any case, it is a mistake that should be fixed.
Update:
Since the failure was still there, I tried invoking the operation after event registration, to rule out process publishing event too soon

PR job #1 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-runtimes -u https://github.com/apache/incubator-kie-kogito-runtimes/pull/3271 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3271/1/display/redirect
Test results:

PASSED: 3257
FAILED: 1

Those are the test failures:

org.kie.kogito.quarkus.workflows.PojoServiceIT.testPojo
Expecting value to be true but was false

PR job #2 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-runtimes -u https://github.com/apache/incubator-kie-kogito-runtimes/pull/3271 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3271/2/display/redirect
Test results:

PASSED: 3106
FAILED: 1

Those are the test failures:

org.kie.kogito.quarkus.workflows.PojoServiceIT.testFilterPojo
Expected size: 1 but was: 2 in:{"age"=666, "name"="javieritoPerson"}

@fjtirado this belongs to unstable test due to kafka streams no reset among tests. you can merge this if you want.


CAMEL-11860: camel-olingo4- Upgrade to olingo 4.4

Fix for issue: https://issues.apache.org/jira/browse/CAMEL-11860
Do we really need to set any baseUri here ? It works fine with 'null' as well, but i would avoid doing that. Guys, do we need to set some specific baseUri for this ? Let me know.

Good point! I will try implementing the suggested changes. However, there's already a 'serviceUri', we set.  So, if i am understanding this right, are you suggesting this can be used as the baseUri ?  Maybe we can have something like this ?
private String serviceUri = "/".

Do we know what exactly is the meaning of the baseUri? And the difference it has to serviceUrl. eg can we find more details in the dropbox api / documentation about these?

I think it's suitable to pass null as baseUri, but from source code point of view https://github.com/apache/olingo-odata4/blob/38f77daa5c555af2012449e1f090a0395bd7a883/lib/server-core/src/main/java/org/apache/olingo/server/core/uri/parser/Parser.java#L173 this is a full service URI starting with http and finishing with query parameters. It's would be good to pass serviceUri variable as baseUri parameter to the parseUri method.

Hi Dmitry,
Thank you for the pointers.  I actually went through that code (or similar) while trying to make the changes and then wasn't sure if passing simply a 'null'  would be fine. It looked ERROR prone.
You make a good point on 'serviceUri', so, probably as i understand, we can directly have the setServiceUri as the 'baseUri'. But, as Claus suggested, i would still like to do more research on the 'serviceUri' and 'baseUri' differences in the Api's or code and see what is the difference.

Hi Claus,
As per Dmitry's suggestions, i have pushed the commit with changes. I believe we can also include this on 2.20 than wait for next one. Let me know.

Adding to it, i also do not see any issues with spring-boot & karaf iTests.

Hi Dmitry,
Okay,  so i will need to check further. But i did set the serviceUri as the baseUri.  I probably can't think of more flaws presently. What exactly can be the problem here ? It is affected because we defined a static serviceUri ?

Yes, it's related to static changes.

Hi Dmitry,
I have pushed commit with latest changes. As to what i can understand from the code and some docs, there isn't a clear mentioning on what the baseUri is introduced for or does it replace the serviceUri. To me, it looks the serviceUri is the baseUri.
Do you see any issues with the latest code i pushed ?

Hi Viral!
Looks good. I think the baseUri introduced for the some exotic cases, which can be occurred very rearly.

Thanks Dmitry for checking this.
@davsclaus , can we merge this ? if there are no further changes required ?

@vrlgohel yeah +1

I'm gonna merge this

@vrlgohel Thanks, the PR has been merged. Can you close this?

Thanks a lot Andrea!


Improve report

Codecov Report

Merging #318 into master will decrease coverage by 52.45%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #318       +/-   ##
============================================
- Coverage     58.56%   6.11%   -52.46%
- Complexity     2789    2793        +4
============================================
  Files           337     337
  Lines          7093    7102        +9
============================================
- Hits           4154     434     -3720
- Misses         2939    6668     +3729

Impacted Files
Coverage Δ
Complexity Δ

src/Service/ImageService.php
0.00% <0.00%> (-25.83%)
73.00 <0.00> (ø)

src/Service/Report/Legacy/PdfSizes.php
0.00% <0.00%> (ø)
33.00 <8.00> (+4.00)

src/Service/Report/Legacy/Report.php
0.00% <0.00%> (ø)
44.00 <15.00> (ø)

src/Service/ReportService.php
0.00% <0.00%> (ø)
86.00 <0.00> (ø)

src/Api/Entity/Base/Map.php
0.00% <0.00%> (-100.00%)
2.00% <0.00%> (ø%)

src/Api/Entity/Edit/Map.php
0.00% <0.00%> (-100.00%)
14.00% <0.00%> (ø%)

src/Api/Entity/Base/Note.php
0.00% <0.00%> (-100.00%)
8.00% <0.00%> (ø%)

src/Api/Entity/Feed/Feed.php
0.00% <0.00%> (-100.00%)
2.00% <0.00%> (ø%)

src/Api/Entity/Base/Issue.php
0.00% <0.00%> (-100.00%)
4.00% <0.00%> (ø%)

src/Feed/Entity/FeedEntry.php
0.00% <0.00%> (-100.00%)
10.00% <0.00%> (ø%)

... and 230 more

Continue to review full report at Codecov.

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


symengine: 0.11.2 -> 0.12.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/symengine/symengine/releases.
meta.description for symengine is: A fast symbolic manipulation library
meta.homepage for symengine is: https://github.com/symengine/symengine
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.12.0 in filename of file in /nix/store/sarg79axc3nhg8wgfcv4ndycy1ksznig-symengine-0.12.0

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

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

haskellPackages.symengine-hs
python311Packages.symengine
python312Packages.symengine
symengine

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/d33016aecc71f8e6514aab87412aba7e406acf1f#symengine

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

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

5 packages built:

python311Packages.symengine
python311Packages.symengine.dist
python312Packages.symengine
python312Packages.symengine.dist
symengine

Maintainer pings
cc @costrouc for testing.

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

7 packages built:

haskellPackages.symengine-hs
haskellPackages.symengine-hs.doc
python311Packages.symengine
python311Packages.symengine.dist
python312Packages.symengine
python312Packages.symengine.dist
symengine


[WIP] TS-4875: Hoist SSL index creation into library initialization.

The SSL index used for server certificate validation can only be
created once, so we need to do it in the library initialization,
not the client context initialization. Following the SSL utilities
conventions, wrap a helper API around the raw SSL data index accesses.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/822/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/718/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/826/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/722/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/723/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/827/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/837/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/733/ for details.


DateTime format in EpcisEvent for callbacks

Hello,
In the EPCIS repository the EventTime is stored as a DateTime. It is always stored in Zulu time (UTC), even if another time zone was specified for that time. The EventTimeZoneOffset field represents the timezone of the original capture.
In the EPCIS subscription callbacks the eventTime field is DateTimeOffset instead of a DateTime. However, this does not seem to represent the local time equivalent of the stored database field.
Thus, capture Event contains:
{   ...
"eventTime": "2019-06-12T06:31:32-04:00",
"eventTimeZoneOffset": "-04:00",
....
}
Database contains (as expected)
EventTime	                                EventTimeZoneOffset
2019-06-12 10:31:32.0000000	-240
However, when sending that EPCIS event in the callback we get:
EventTime  = {12/06/2019 10:31:32 +02:00}
Instead of
12/06/2019 10:31:32 +00:00
It seems that the database field is interpreted as being in local time instead of UTC for the callback!
According to MSDN for Json.Text deserializer, when no time zone info is present (and there isn't in the database) the time will be interpreted as local time, not as UTC.
I have solved this using this code in the JsonCallbackParser
  // Added yvdh: DateTime default to local, while the db is UTC!!!!
  if (property.PropertyType == typeof(DateTimeOffset))
  {
  // This date time has no idea of timezone ...
   var utcAsWrongLocalTime  = DateTime.SpecifyKind(((DateTimeOffset)    jsonValue.Value.Deserialize(property.PropertyType)).DateTime, DateTimeKind.Utc );
    value = new DateTimeOffset(utcAsWrongLocalTime);
  }

This does not take care of arrays of time ...
Cheers
Yves

Hi @yvdh,
Thanks for raising this issue.
The date should be parsed correctly if the timezone is correctly specified, so it seems that the issue is in the EPCIS repository itself and not in this parsing library.
By looking at the JsonEventFormatter, it appears that the JSON formatter doesn't include the timezone by default. I created a PR for it in the EPCIS repository project. I did a few tests with that change and everything looks correct, at least for expected DateTime fields in the events.
For custom fields everything should be correct as the repository should return the text value that it received.
Can you explain what you mean with:

This does not take care of arrays of time ...

Do these arrays come from custom data (extension/ILMD)? If so, could it be possible for you to share an example to verify the fix in the repo is correct?
Thanks and regards,

Hello Louis-Axel.
thnx for the PR, I will check it out.
Regarding arrays, I just meant I think that the code I modified does not do anything for DateTime arrays/lists/collections in the parser. I don't think there are such properties currently in EPCIS, and I have none myself, but there could theoretically be in extensions at some point in the future.
I did not do any tests other than check that it worked for my specific case ..
Cheers,
Yves

Hello,
I checked out the code, but as far as I can tell this solves the problem for the main EPCIS hosting solution, but not for the EPCIS subscription callback client in your other project .  This would simply also require inclusion of the EpcisDateFormatConverter : JsonConverter for its json serialization.
Truth be told I should have posted this issue in that project, my bad.
Cheers,
Yves

I checked out what DateTimeStyles.AdjustToUniversal does, and I don't think it does what we need!
If I give it a string without timezone info (as from the database) it will subtract the current server time zone offset from it:
"2019-06-12T10:31:32" => "2019-06-12T08:31:32+02:00"
As the date times in the database are supposedly always UTC and are to be interpreted as absolute times this should become either:

"2019-06-12T12:31:32+02:00" as local time in a +2 zone
"2019-06-12T10:31:32Z" as UTC time.

So, AdjustToUniversal still assumes times without any timezone are local times, which they are not!
This snippet will always interpret times without timezone as UTC.
var utcTime = DateTime.SpecifyKind(((DateTimeOffset)jsonValue.Value.Deserialize(property.PropertyType)).DateTime, DateTimeKind.Utc);
value = new DateTimeOffset(utcTime);
Also,  I have integrated the new date formatter into the EPCIS host, but dates are still written to the database without timezone info (no 'Z'), which is what I think we ultimately need (correct me if I am wrong).
All in all, this time stuff is quite messy in .NET ...

That's right, AdjustToUniversal will always assume that the original format is Local if it's not specified.. A combination of DateTimeStyles.AssumeUniversaland DateTimeStyles.AdjustToUniversal might return the expected result as a datetime without timezone would be treated as UTC, and if a timezone is specified it would be converted to UTC.
Very quick tests returned the expected values, i.e. "2019-06-12T10:31:32" is converted to "2019-06-12T10:31:32Z", and "2019-06-12T12:31:32+02:00" to "2019-06-12T10:31:32Z" as well.
Also as the formatted values are always formatted in UTC there's probably no need to update the callback library.
This will require a change in all the dates fields in both XML and JSON parsers, I'll try to update it as soon as possible in the EPCIS repository.
Thanks for all your time invested on this issue, that'll be a great improvement!

Hi @yvdh
The branch fix/json-formatting is updated to always use UTC timezone for the dates.
It'd be really appreciated if you could test it to see if it fully matches your expectations.
Thanks!

Hello,
I quickly setup a separate project with your fix branch and ran it. Here are my findings:

It assumes UTC if no timezone is present in a capture: 2019-06-12T06:31:32 => 2019-06-12 06:31:32.0000000 in DB
It uses the provided timezone if present in a capture: 2019-06-12T06:31:32-04:00  => 2019-06-12 10:31:32.0000000 in DB.
It returns the wrong event time when querying: 2019-06-12 06:31:32.0000000 in DB => 2024-04-22T05:31:54.459Z in response
The recordTime in a record response is wrong: 2024-05-22 10:22:48.1927291 in DB => 2024-04-22T12:44:56.921Z

My 2 cents: assuming UTC when no time zone is present is a step forward but I think just adding timezone info in the database is a safer solution (especially with the ambiguity in the .NET date/time coding). It really means we are using absolute time that leaves no room for interpretation. The callback library should then also still work out of the box I think.
Available for discussion in Whatsapp if you want ...
Cheers
Yves

I  checked a few things and I understand that my suggestion requires any DateTime2 type column to become a DateTimeOffset column in the database. Mmm, that's quite disruptive ...
So your idea is probably a softer approach to the problem ...
Yves


Polish pipeline and selectors API

After adding a few new selectors in addition to the most basic Shared one, it became apparent that reorganization of the code would be beneficial. There are quite a few improvements that are desirable, ultimately they could be summarized into the following areas:

[ ] Move selectors to a separate module (rather than keeping them in skada.base).
[x] The code for branching the execution flow (i.e. splitting/merging) is scattered, duplicated across different methods and, mostly, purely tested. It would be nice to come with more generic concepts/blocks, requires proper design work (thankfully we have quite a few examples of the functionality now).
[ ] Make sure that all methods are covered with a proper docstrings.
[ ] There are multiple scenarios that we want to test against all available selectors. Would be nice to find a way to organize tests accordingly to this.
[ ] Documentation and examples to explain the inner workings of the pipeline/selectors.
[ ] In the beginning of the work we made a few shortcuts for naming conventions and parametrization to avoid Shared selector being 'visible' in the pipeline. It's time to re-evaluate those choice in the light of new functionality introduced.

Note that this was partially covered in #184


View Components install problem

Steps to reproduce:

Create a package with Spatie Package Tools, like below.
Add a view package, and use hasViewPackage() method.

use Spatie\LaravelPackageTools\PackageServiceProvider;
use Spatie\LaravelPackageTools\Package;

class AwesomePackageServiceProvider extends PackageServiceProvider
{
  public function configurePackage(Package $package): void
    $package
      ->hasViewComponent('nitrogen', Menu::class)
  ...

If you put the View Component's PHP part to src/View/Components, then the publish command will not run, it will say, the PHP file is missing from src/Components. If you move the folder, and the file to this location, publish will not run, but Laravel will say, View Component is missing from View/Components folder. So the quick and dirty solution is using PHP file in both location, but it's not okay, double to maintain.

The issue is here, the word 'View' is missing from the path. If I put the word "View" there, the publish command will work without any issue, and of course Laravel too...
// \vendor\spatie\laravel-package-tools\src\PackageServiceProvider.php:138

        if (count($this->package->viewComponents)) {
            $this->publishes([
                $this->package->basePath('/     View      /Components') => base_path("app/View/Components/vendor/{$this->package->shortName()}"),
            ], "{$this->package->name}-components");
        }

Github missed the link: https://github.com/spatie/laravel-package-tools/blob/f613d221ccc6d245db50a38d21539ad20e550823/src/PackageServiceProvider.php#L140


Add readthedocs config

Description
Adds support for using readthedocs for the Python client. To use the service a maintainer needs to import the project on readthedocs.io, and possibly also set up webhooks.
Note: it's possible to move the config to a subdirectory (e.g. clients/python), although that's a beta feature.
How Has This Been Tested?

Pushed the documentation as a test on my fork: https://test-model-registry.readthedocs.io/en/latest/index.html
Merge criteria:

[x] The commits and have meaningful messages; the author will squash them after approval or will ask to merge with squash.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

@tarilabs should we remove docs build from the CI tests? It should only be helpful to know if a build failed.

I'll update for using poetry. The webhook setup seems to be the best way to fetch updates from GitHub, at least according to the RTD docs. We can set up automations rules via the platform, e.g. https://docs.readthedocs.io/en/stable/automation-rules.html#examples. But it doesn't seem to make sense to have a docs build GHA, because readthedocs always builds on their end (automation only helps it recognize the target). When importing the project from GitHub they already set up webhooks automagically, the same way they ask for the manual setup to be executed.
We can however call in the Generic API integration from GHA.
FYI they have a GHA for previewing docs on PRs, which could also be useful, although it shouldn't work using the generic endpoint approach: https://github.com/readthedocs/actions/tree/v1/preview
There's also a way to set up webhooks for build failure notifications


Enable test coverage

This PR enables test coverage for forest and adds a badge to the README.md.
@andrewgryan Akin to travis-ci, you will require to turn-on coveralls for the informatics-lab/forest repo. Happy to talk you through this.

Nice work!


Compile time error using Plugin.BLE  beta 5

Hi,
We are currently using Plugin.BLE bet3 in our project, which works fine. When we update the Plugin.BLE nuget package to beta 5, we are not able to succesfully compile the project. It gives "MT2002" error.
Is it because the xamarin environment? if so, what is the version of Xamarin.iOS or Xamarin required?
Can you please help me solve the mentioned problem?
Thanks in advance
Leela

We used the latest stable Xamarin version to compile it. Did you update Xamarin to the latest stable release? Perhaps you can try cloning the repository and build the solution.

@leelatoo do you have this issue with 1.0.0 stable, too?

No activity since Jul 28. Will consider this closed


TypeError: axe.run arguments are invalid

Stencil.js uses JSX like React. I'm using ordinary Jest unit tests with it. It always throws the error above.
But even when I use jest-axe exactly like in your first usage example, I get the same error. Even if I just call it like expect(await axe('<img src="#"/>')).toHaveNoViolations(), although this certainly is a string.
I'm using typescript, but I did install @types/jest-axe and added the type jest-axe in tsconfig.json.
Any help is appreciated.

Ah, I think I found it. It's a bug in axe-core, there is a function isContext() with switches, and it doesn't use "break";


Add test to check data and index types compatibility

PR adds integration test (disabled by default) that checks compatibility between combinations of:

data type - INT, LONG, FLOAT, DOUBLE, BIG_DECIMAL, BOOLEAN, TIMESTAMP, STRING, JSON, BYTES, MAP (all variants)
cardinality - single value, multiple values
encoding - raw or dictionary
index types - timestamp, bloom, fst, geo, inverted, json, native_text, text, range, vector
and reports the outcome .

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 55.37%. Comparing base (59551e4) to head (fc767ca).
Report is 1358 commits behind head on master.

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (fc767ca). Click for more details.
HEAD has 53 uploads less than BASE

Flag
BASE (59551e4)
HEAD (fc767ca)

integration
7
0

integration2
3
0

temurin
12
1

java-21
7
1

skip-bytebuffers-true
3
1

skip-bytebuffers-false
7
0

unittests
5
1

unittests1
2
1

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@             Coverage Diff              @@
##             master   #14493      +/-   ##
============================================
- Coverage     61.75%   55.37%   -6.38%
- Complexity      207      698     +491
============================================
  Files          2436     2100     -336
  Lines        133233   110660   -22573
  Branches      20636    17582    -3054
============================================
- Hits          82274    61276   -20998
+ Misses        44911    44486     -425
+ Partials       6048     4898    -1150

Flag
Coverage Δ

custom-integration1
?

integration
?

integration1
?

integration2
?

java-11
?

java-21
55.37% <ø> (-6.26%)
:arrow_down:

skip-bytebuffers-false
?

skip-bytebuffers-true
55.37% <ø> (+27.64%)
:arrow_up:

temurin
55.37% <ø> (-6.38%)
:arrow_down:

unittests
55.37% <ø> (-6.38%)
:arrow_down:

unittests1
55.37% <ø> (+8.48%)
:arrow_up:

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles

Why disable by default? this would be a good thing to have running to catch combination regressions?

Nice! This can give us big confidence!
How long does it take to run the test? Both in your local environment and in Github Actions?


Memory leak issue

Hi,
I've run into a critical memory leak when integrating Turbo with my Shopify store. This seems to be a deeper conflict between Turbo and Shopify’s architecture, not limited to a specific theme. After each Turbo-driven navigation, the heap size increases exponentially due to thousands of detached DOM nodes being retained, leading to eventual browser crashes.
Setup: Shopify theme with Turbo loaded via CDN in theme.liquid. Basic setup with  wrapping the primary content. Removed all custom JS to isolate, but issue still persists across both paid and free themes.
Memory leak occurs only with Turbo—heap snapshots show entire DOM trees from previous pages are retained. Switching to PJAX completely resolves it, indicating Turbo’s handling of Shopify’s dynamic element updates is the issue.
The issue occurs even in a stripped-down theme, suggesting it’s related to Turbo’s core caching or preservation logic conflicting with Shopify’s dynamic section rendering.
Tried disabling Turbo Frames, manual node replacements, using data-turbo-permanent to preserve elements, different script loading strategies (async, defer, dynamic imports), and more. All failed to resolve the issue.
Is there a known issue with Turbo and Shopify’s dynamic DOM structure? Could Turbo’s element preservation or caching be mishandling the updates? Any suggestions for debugging this?
Appreciate any guidance—I'd really like to leverage Turbo’s benefits if I can get past this issue.
Thanks!

Please anyone

Which library is retaining references to the detached DOM nodes?
Turbo or Shopify?


Last Epoch: Terrible gpu utilization and performance hit on Linux (DXVK) vs playing on Windows OS. This is not happening in other games for me, only Last Epoch

Playing the game on Linux (proton-DXVK) results in terrible performance hit. See attached comparison screenshot, For example in character selection screen I get 144 FPS on Windows (GPU utilization ~50%) while on Linux (DXVK) I get 60 FPS while gpu utilization is maxed out, which is not normal as there is not much for the gpu to do in this screen. In game it is a "greek tragedy". I get 250 FPS on Windows vs 100 FPS on linux. During combat with many enemies I get 120-150 FPS on Windows vs 40-50 FPS on Linux (DXVK). There is something that hitting the GPU hard and makes it under-perform.

Software information
LAST EPOCH. 1080p, fullscreen (tried all settings from low to ultra high).
System information

GPU: Sapphire Radeon RX5600XT

Driver: Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
vendor: Sapphire driver: amdgpu v: kernel bus-ID: 09:00.0
Display: x11 server: X.Org v: <IP_ADDRESS> driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu resolution: 1920x1080
OpenGL: renderer: AMD Radeon RX 5600 XT (navi10 LLVM 15.0.7 DRM 3.52
6.4.3-060403-generic)
v: 4.6 Mesa 23.2.0-devel (git-96cf453 2023-06-08 jammy-oibaf-ppa)
direct render: Yes

Wine version: Wine 8.12 (tried other versions also)

DXVK version: v2.2-119-g6be1f6d7bd5f832

Log files
Proton log:
steam-899770.log.zip
References
Opened issue in proton/valve github

Looking at your screenshots and poking at the game myself on Linux and Windows i think your issue points towards vram exhaustion. On Windows this is handled much better than on Linux usually. dxvk also isn't the greatest in this area and can maybe also make the usage go up.
Could you try as a test making a file called dxvk.conf next to the games exe and inserting dxvk.maxChunkSize = 16
This game seems to have quite alot of memory fragmentation. At least with dxvk

Looking at your screenshots and poking at the game myself on Linux and Windows i think your issue points towards vram exhaustion. On Windows this is handled much better than on Linux usually. dxvk also isn't the greatest in this area and can maybe also make the usage go up a bunch in some situations.
Could you try as a test making a file called dxvk.conf next to the games exe and inserting dxvk.maxChunkSize = 16 This game seems to have quite alot of memory fragmentation. At least with dxvk

I played with dxvk.info trying to solve this problem, poking around with dxgi.maxDeviceMemory variable in order to fool the game and not use all vram, to no positive result.
Regarding your suggestion I just did the test:
Tried dxvk.maxChunkSize = 16 / 32 / 64 / 128 / 256 etc, With any value lower thn 128 I get more severe performance hit (20 FPS). With values 256 and greater I get the FPS I currently have.
Do you think there is any other dxvk setting I could try ?

Do you think there is any other dxvk setting I could try ?

Sadly no.
I see the game pretty much straight up uses 8GB vram at main menu, so it just loads in everything even when it might not be relevant. This is both at medium, high, very high and ultra where the used vram doesn't really change much. The amount actually allocated by chunks add up to around 8.5 so here the fragmentation isn't as terrible but you will go above your vram limit which can be pretty bad on Linux as said.
At low preset the used amount drops to around 4.2 and allocated chunks 6.6, so here dxvk inefficiencies starts to play a role. At very low it's around 3.1 used and 6.3 allocated. These are numbers with dxvk on Windows so Linux might be slightly different.

Do you think there is any other dxvk setting I could try ?

Sadly no.
I see the game pretty much straight up uses 8GB vram at main menu, so it just loads in everything even when it might not be relevant. This is both at medium, high, very high and ultra where the used vram doesn't really change much (at main menu and start of game). The amount actually allocated by chunks add up to around 8.5 so here the fragmentation isn't as terrible but you will go above your vram limit which can be pretty bad on Linux as said. At low preset the used amount drops to around 4.2 and allocated chunks 6.6, so here dxvk inefficiencies starts to play a role. At very low it's around 3.1 used and 6.3 allocated. These are numbers with dxvk on Windows so Linux might be slightly different.
Edit: note i'm using a 7900xtx which has 24GB vram.

PS. Also tried with another pc which has a Radeon 6600XT(8 GB). The performance was somewhat better, but still the whole 8GB vram were utilized and there was a huge difference in FPS between windows and Linux (proton-dxvk)

What is the difference with that card compared to Windows? Also what is your CPU

My CPU is Ryzen 5800X3D

I don't have easy access right now to the machine with 6600XT (8GB) which has a Ryzen 3800X. I remember that when I run the game there I hit 144 fps in login screen (like windows) and about 150-170 FPS outside of combat (I didn't test combat). On this PC however, GPU was throttling because of the low IPC of CPU (3800X). I did reach to the conclusion that the higher VRAM was helping.

May I ask what FPS you are hitting on Linux vs Windows with your GPU ? Not that I can afford this card, just curious.

Also I would like to add that using PROTON_USE_WINED3D=1 (which tells proton to translate to OpenGL) gives me 100% of the performance I get on windows. However this introduces various graphical glitches that are related to this game coding (same glitches I have when running the game native openGL linux client). This means that the problemisn't necessary related to how linux is handling vram but proves that it is a DXVK performance issue handling the vram in this game.

May I ask what FPS you are hitting on Linux vs Windows with your GPU ? Not that I can afford this card, just curious.

At 1080p just standing still when you start the actual game.
Ultra dxvk Linux around 280 (radv)
Ultra dxvk Windows around 350
Ultra native Windows around 340

Very low dxvk Linux around 330 (radv)
Very low dxvk Windows around 400
Very low native Windows around 390

On Linux/Proton (not exactly sure where the issues is) i start hitting another problem that cause a perf hit with high core count CPU's especially in some Unity games. So if i restrict the game to say 6 logical cores it looks better again. WINE_CPU_TOPOLOGY=6:0,1,2,3,4,5
Ultra dxvk Linux around 380 (radv)
Very low dxvk Linux around 430 (radv)

Also I would like to add that using PROTON_USE_WINED3D=1 (which tells proton to translate to OpenGL) gives me almost 100% of the performance I get on windows.

With wined3d vram is probably alot less of a issue so imo it still points towards that. Note i'm not actually a dev and just help out testing and i don't have much technical insight. So don't take my word as gospel
I'm impressed wined3d manages so well perf wise. Kodus and good work to the wined3d devs :beers:

Difference between dxvk and wined3d in low vram cases might also be due to differences between radv and radeonsi, since radv added GTT domain for everything it behaves even worse in some vram constrained cases (context: https://gitlab.freedesktop.org/mesa/mesa/-/issues/8763, https://gitlab.freedesktop.org/mesa/mesa/-/issues/8107)

That is to say, trying amdvlk or reverting the GTT commit in radv might be interesting as well, but it's still unlikely to work as well as on windows.

OMG OMG OMG!!!
I just took I timeshift snapshot (so I could revert back easily if things go south) and installed amdvlk (from here) and WOW!!!!
My character selection screen jumped from 60 to 144 FPS (like windows!!!!!!!)
However, in game (outside of combat) I get ~170 FPS, which is still worse than Windows' 250FPS, but much better than 120FPS I had up to know.
I can't believe it. And everyone says that mesa's radv is better than amdvlk and recommend not to install amdvlk.... I don't know what just happened!

I can't believe it. And everyone says that mesa's radv is better than amdvlk and recommend not to install amdvlk

That is still the correct recommendation in 99% of cases.

So, could this be a mesa radv's vulkan implementation issue?

My guess is still that it's because RADV always sets the GTT domain for allocations, which amdvlk doesn't do and which makes it perform worse in some cases when VRAM is running out. You could try to confirm that by building radv with https://gitlab.freedesktop.org/mesa/mesa/-/commit/862b6a9a97ad9c47c14dbc76ea892293573c746f reverted.

I can't believe it. And everyone says that mesa's radv is better than amdvlk and recommend not to install amdvlk

That is still the correct recommendation in 99% of cases.

So, could this be a mesa radv's vulkan implementation issue?

My guess is still that it's because RADV always sets the GTT domain for allocations, which amdvlk doesn't do and which makes it perform worse in some cases when VRAM is running out. You could try to confirm that by building radv with https://gitlab.freedesktop.org/mesa/mesa/-/commit/862b6a9a97ad9c47c14dbc76ea892293573c746f reverted.

Could you please explain to me, now that I have installed amdvlk, radv was overwritten? Or they both exist? And how games know which one to choose? I see no difference in my inxi report....

You can have both installed and choose on a per-game basis using VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/SOME_DRIVER_ICD.json (path might differ per distro, don't know what you did to install amdvlk, ...), although amdvlk makes itself the default automatically when installed.

You can have both installed and choose on a per-game basis using VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/SOME_DRIVER_ICD.json (path might differ per distro, don't know what you did to install amdvlk, ...), although amdvlk makes itself the default automatically when installed.

I used the deb file. I have linux mint 21.1

UPDATE:
OK, I played for about an hour using amdvlk and the good news are that the game never drops below 60-70 FPS (using radv the FPS were dropping at ~40 FPS during combat with many enemies). The bad news are that when a new map loads there is stuttering for a while probably until all shaders/textures load properly to VRAM. This stuttering does NOT happen with the radv. On windows os, during heavy combat the FPS never drop below 110-120 FPS + there is no stuttering. I wish I could afford a 7900XTX like @Blisto91 but I can't.... (and even if I could, the KWh cost where I live is very very expensive, so I couldn't afford the power consumption of 7900xtx either....

Hopefully the vram situation will improve with time the whole way through the stack. dxvk, radv and if necessary amdgpu.

The bad news are that when a new map loads there is stuttering for a while probably until all shaders/textures load properly to VRAM. This stuttering does NOT happen with the radv.

Ye amdvlk doesn't support VK_EXT_graphics_pipeline_library yet which is what allows dxvk to compile shaders upfront (main menu or loading screen) if the game does the same on Windows. So it will instead compile at draw time which gives stutters until you've seen everything.

Hopefully the vram situation will improve with time the whole way through the stack. dxvk, radv (and amds drivers needed) and if necessary amdgpu.

The bad news are that when a new map loads there is stuttering for a while probably until all shaders/textures load properly to VRAM. This stuttering does NOT happen with the radv.

Ye amdvlk doesn't support VK_EXT_graphics_pipeline_library yet which is what allows dxvk to compile shaders upfront (main menu or loading screen) if the game does the same on Windows. So it will instead compile at draw time which gives stutters until you've seen everything.

Do you think we could have a "best of both worlds" solution in the short future? Both compiling shaders upfront + handling vram exhaustion better at the same time?

Do you think we could have a "best of both worlds" solution in the short future? Both compiling shaders upfront + handling vram exhaustion better at the same time?

You can probably get amdvlk's out of vram behavior by just reverting https://gitlab.freedesktop.org/mesa/mesa/-/commit/862b6a9a97ad9c47c14dbc76ea892293573c746f and compiling mesa, although that is still far from really good low vram management, even if it's good enough in this case. VRAM management has been bad on both vendors for years and years on linux, I doubt there will be a solution in the near future.

You can probably get amdvlk's out of vram behavior by just reverting https://gitlab.freedesktop.org/mesa/mesa/-/commit/862b6a9a97ad9c47c14dbc76ea892293573c746f  and compiling mesa

I think this is complicated for my technical skills atm and to tell you the truth I don't want to invest time on it.

VRAM management has been bad on both vendors for years and years on linux, I doubt there will be a solution in the near future.

Then I think it is time to either buy at least a 12GB gpu or play Last epoch on windows. I like neither of those two solutions....

UPDATE:
After a couple of computer restarts, steam downloaded some updates (not game clients updates, something to do with shaders) and  now the game is playable with almost no stuttering with amdvlk! Or maybe I played long enough and somehow the system "understood" what is needed to be in vram and there is no more stuttering..... I'll keep testing.

UPDATE:
Since I don't know if there is anything that can be done by dxvk devs to improve the performance in max vram saturation scenarios, I opened a issue in mesa forums, hoping that devs can see it and improve radv. Feel free to contribute there also.

The issue is known. See also https://gitlab.freedesktop.org/mesa/mesa/-/issues/8763

You can have both installed and choose on a per-game basis using VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/SOME_DRIVER_ICD.json (path might differ per distro, don't know what you did to install amdvlk, ...), although amdvlk makes itself the default automatically when installed.

I found out that is easier to simply use AMD_VULKAN_ICD=RADV when you want to play a game with RADV (instead of looking for paths). You can also use AMD_VULKAN_ICD=AMDVLK, for amdvlk, but there is no need for that since, after installation, amdvlk becomes the default.

Probably works fine most of the time but note at for some it might not work 100% correctly https://github.com/GPUOpen-Drivers/AMDVLK/issues/331

@tethragon Can you give this another go with dxvk master? Vram usage should have improved a bunch in some scenarios


Stuck at It works!

Expected Behavior
expecting the creation of token.pickle.
Actual Behavior
The web page shows it works and console get stuck and nothing happened after that
Steps to Reproduce the Problem

Download the sample
Install the libraries
Run the quickstart via python quickstart.py

Specifications

Python version (python --version) - 3.6
OS (Mac/Linux/Windows) - Mac

Are any errors reported on the command line?

No errors. But not redirecting to a window. Any suggestions ?

If you see the "It works!" text then it did redirect correctly. I'm not able to reproduce the problem, and without more information I can't further troubleshoot.


Ambassador CrashLoopBackOff while using with Knative

Describe the bug
I have configured ambassador to use Knative. We have around 150 services in Knative. Suddenly ambassador started to restart 1000 of times and shows CrashLoopBackOff. Some of the Knative is not registered in ambassador as well.
kubectl get pods -n ambassador
ambassador-8cbdb64dd-68c2g   0/1     Running            986        23d
ambassador-8cbdb64dd-wnktv   0/1     Running            1742       23d
ambassador-8cbdb64dd-xcwvj   0/1     CrashLoopBackOff   2919       23d

Knative service shows Status as False ans reason as RevisionMissing
sc7a7b5f1-3919-420d-913a-f533d17e17b7-knative-deployment   http://sc7a7b5f1-xxxx-420d-913a-f533dxxxxx-knative-deployment.xxxxxx.com   sc7a7b5f1-3919-42xxx-xxxx-f533d17e17b7-knative-deployment-65c2v            False   RevisionMissing

When i check the logs of ambassdor, there is no error logs.
Ambassador CrashLoopBackOff events,
Events:
  Type     Reason     Age                      From                                          Message
  ----     ------     ----                     ----                                          -------
  Warning  Unhealthy  45m (x1122 over 14d)     kubelet, xxx-appnodepool-17318896-vmss000001  Readiness probe failed: Get http://xxxxxx:8877/ambassador/v0/check_ready: dial tcp xxxx:8877: connect: connection refused
  Warning  Unhealthy  36m (x14953 over 14d)    kubelet, xxx-appnodepool-17318896-vmss000001  Liveness probe failed: HTTP probe failed with statuscode: 503
  Warning  Unhealthy  5m50s (x16737 over 14d)  kubelet, xxx-appnodepool-17318896-vmss000001  Readiness probe failed: HTTP probe failed with statuscode: 503
  Warning  BackOff    60s (x12659 over 9d)     kubelet, xxx-appnodepool-17318896-vmss000001  Back-off restarting failed container

Versions (please complete the following information):

Ambassador: 1.3.1
Kubernetes environment Azure AKS
Version 1.15.6

Whole my cluster services will be down. For us its very important to have stable Ambassador, else our application is down. Requesting to please.

Do i need to increase Liveness probe and Readiness probe initial delay time? Because of more than 150 services, default 30seconds is not enough?
Please suggest.

Getting Kubestatus timeout error.
KubeStatus DONE 127: result se60bf65b-e132-47bd-a956-b6574d9da82b-knative-deployment.recobo-ml-api-deploy-ns: timed out
Increased Readiness and Liveness probe initialDelay to 10min, but it shows timeout for all knative services.
We are running only 31 Knative service currently. I tried upgrading ambassador to 1.4.1 also, the error remains the same.

After debugging for couple of hours, we saw below behavior.
Working flow:

Ambassador is up and running with Knative env
Create Knative service with zero scaling enabled
Ambassador creates mapping for the same
I can access knative service using ambssador URL

Error Flow:

Same as above
Restart ambssador by either upgrading to newer version or delete pods
Now you will see Kubestatus timeout error. Because as knative service is scaled to zero, Kubestatus can't validate service
It will keep on trying still all services are up.
Because of readiness and liveness probe, it will restart
When it loops and check for service status, CPU usage will be 2CPU.

As we are using Knative because of scale zero feature and our most of our services are not used so frequently.
How can we solve this issue @concaf @richarddli

I believe that this is actually fixed in current versions of Ambassador -- there's been a lot of work around Knative. Can you try this with Ambassador 1.10? Thanks!

I believe that this is actually fixed in current versions of Ambassador -- there's been a lot of work around Knative. Can you try this with Ambassador 1.10? Thanks!


tf.lite file issue

Quick question; I reset the openMV cam because it was doing some off things that I have not seen. We finally got the Boron working as it was having a major DeviceOS issue. Now that I have reset the camera, I am uploading the main.py and trying to put the tf.lite file back into the OpenMV hard drive. It keeps saying this file is too big even though I have done this before and never got this issue. I tried zipping it too.
Any recommendations?
There is an SD card and I tried copying/pasting

@ebgoldstein Looks like its the openmv. Used a different computer, same issue. Tried the other openMV and it read the full SD .

there we go... can you use the other openmv board?

@ebgoldstein yes I am! I am still experiencing green flashing when I plug it in. Based on some forums it is the bootloader running. This may be normal but all last semester I did not see this occur.
I am looking more into this to make sure my next step does not cause any issues. I am wondering if you have experienced this at all?

@ebgoldstein After the code runs I have a LED red turn on and off which is successfully occuring once.
I understand that while the camera is connected to the IDE the camera waits for you to press run which means it will only run once, however, it is only running once when connected/powered by the Boron which is new.
I have tried to power it from USB to the wall but still nothing.

@BentleySettin , see the new openmv code i just committted.. this one worked on my device.. the old version did not.. Can you please try it and LMK?
(@anardek & @SUPScientist - maybe ignore my email, this version of the code seems to work on my machine and I was able to reproduce the issues that @BentleySettin was having... this code shoudl work :crossed_fingers: )

@ebgoldstein it works! Thank you Evan!


What is this behavior?

Notice: Hi, I've been doing React for ~1 week now.
I have some behavior in my code which I don't know is specific to this package or not. I'd like some help to understand it.
I would like to extend the current raised button for which I have done this
const Button = (props) => {
  const parent = MKButton.button()
  const textStyle = parent.textStyle
  console.log('first')
  console.log(parent.textStyle)
  console.log(textStyle)

  return (
    <MKButton
      {...parent.toProps()}
      onPress={props.onPress}>
      {console.log('second')}
      {console.log(parent.textStyle)}
      {console.log(textStyle)}
      <Text style={{
        ...parent.textStyle,
        color: 'green'
      }}>
        {props.text}
      </Text>
    </MKButton>
  )
}

And this is the output from my console

Why does the second parent.textStyle return an array instead of an object?
I assumed I could do
style={{
        ...parent.textStyle,
        color: 'green'
      }}

But this gives me some errors because I'm spreading an array which makes the keys in the form of 0 1 2...
This is the error-less way
style={{
        ...textStyle,
        color: 'green'
      }}

Could you provide me any insights? Thanks

This is the behavior of ReactNative's StyleSheet, it's immutable, it returns the id of the styles, but not the object. You can provide additional styles to override/extend the old one, for example:
style={[ baseStyle, style1, {
    color: 'green'
  }]}

Thank you!


Add Expr support to OpenQASM 3 exporter

Summary
This adds support for Expr nodes in condition fields and SwitchCaseOp.target.  The general c_if condition checking is lifted into an Expr node as part of the OQ3 export, so the form of them automatically becomes like the new-style outputs, depending on how expr.lift_legacy_condition chooses to raise them to Expr nodes.
As part of the refactor of the Expression subtree of the temporary AST, I removed SubroutineCall.  Its definition was severely out-of-date (a form from before even the initial arXiv draft), where it was statement-like instead of expression-like.  There is currently no support in Qiskit for representing these sorts of subroutines properly, and the OQ3 exporter would produce invalid OQ3 if it encountered something that it thought should be a a subroutine call.  This commit fixes that bug, correctly raising an exception that non-unitary instructions are not yet supported for export.
This commit also removes the special casing from the CXGate into the exporter itself; it was more convenient in the new structure of some internal components, and it's a data model we don't want to support anyway.
Details and comments
Close #10225.  Depends on #10249 and #10358.  Further changelog in #10331.
I haven't verified the exact output formats from this against what the QSS stack supports yet, but will do early next week and make whatever tweaks are required.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

664 of 713 (93.13%)  changed or added relevant lines in 21 files are covered.
15 unchanged lines in 7 files lost coverage.
Overall coverage increased (+0.03%) to 86.01%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/circuit/classical/types/ordering.py
36
37
97.3%

qiskit/circuit/controlflow/switch_case.py
8
9
88.89%

qiskit/dagcircuit/dagcircuit.py
9
11
81.82%

qiskit/qasm3/ast.py
68
71
95.77%

qiskit/circuit/classical/types/types.py
44
48
91.67%

qiskit/qasm3/printer.py
38
43
88.37%

qiskit/circuit/classical/expr/expr.py
102
111
91.89%

qiskit/qasm3/exporter.py
93
104
89.42%

qiskit/circuit/classical/expr/constructors.py
142
155
91.61%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/expr.rs
1
93.76%

qiskit/circuit/controlflow/switch_case.py
1
94.08%

qiskit/qasm3/exporter.py
1
94.87%

qiskit/transpiler/passes/synthesis/unitary_synthesis.py
1
90.18%

crates/qasm2/src/lex.rs
3
91.14%

qiskit/qasm3/ast.py
3
95.62%

qiskit/qasm3/printer.py
5
88.45%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
72056

Relevant Lines:
83776

💛  - Coveralls

Now rebased over main.

I've added the test case I was worried about now, so this PR is totally ready.


Make staking inflation curve configurable.

Context:
currently the curve used to compute the reward of the validators and nominators is fixed in srml-staking. This PR makes it configurable at the runtime (node-runtime) level.
Done:

Definition of the curve has changed to just a list of points: (Perbill, Perbill), this allows to define any function from [0, 1] to [0, 1] even the curve is very steep. (The limitation for [0, 1] -> [0, 1] is to avoid difficulties with overflows)
definition of PiecewiseLinear is moved to sr-primitives, it uses its own function multiply_by_rational_saturating. Maybe we want to make this latter function available publicly.
to declare a curve easily a proc-macro crate is introduced at srml-staking-reward-curve.
this crate generate a test for the precision alongside the declaration.
the generation of the curve has changed for efficiency reason because the time to compile is important.
new algorithm just divide into variable segment with some maximum size.

Awesome :)
Will need a polkadot update PR but looking very good otherwise.

Some refactor suggestions but overall seems to deliver what it intended to do --make the curve configurable-- perfectly :) LGTM

(just saw the label being in-progress -- ^^ given that it is actually done.)


My blocks "return" block

I have a small question about this extension, can we edit it so that a block can also return booleans.
I know that a can use "Couplers" to transform a string into a boolean but in would be nice if the vm did it by itself.
It (the vm) can tell if a "return" block is in the definition of a block definition to change the shape. Maybe the vm could transform the output block into a boolean if, for exemple, the content of every return block is true or false.

consider this:


Implementation for BiomeVolumeFactory

Is this request specific to one implementation of Sponge?
No
Sponge Version
1.16.5-8.0.0-RC1061
What are you requesting?
Implementantion for BiomeVolumeFactory is missing (I assume it was missed since BlockVolumeFactory is present)

It sounds like an important feature for Volumes API


Fetch logs of particular steps

There's a log table already, but it fetches logs of all steps in a job. This is often too much to handle in a single page.
Instead, it would be useful to try to fetch logs for particular steps in a job, after identifying failing steps. This is not documented, but the URL is: {owner}/{repo}/commit/{sha}/checks/{jobId}/logs/{stepNumber}. This could map to a table called step_logs and would have to support predicate pushdown for all params in that URL.

Note this will most likely require #40 to be useful, since steps will usually be joined with the jobs table.

There's no API for this. We'd have to split logs based on the block comments.
I guess I'll just try to finish fetching job logs, that is add splitting them into parts to avoid reaching the internal Trino page limit.


Add sched_get/setscheduler for NetBSD

NetBSD supports sched_getscheduler() and sched_setscheduler() with the same signature as FreeBSD-like operating systems.

r? @Amanieu
(rust-highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit 10eff9941f3002f31e18a2befe4bfcb86868140e has been approved by Amanieu

:hourglass: Testing commit 10eff9941f3002f31e18a2befe4bfcb86868140e with merge 402f84a2edf84d45457d3da76a69daa9e42a8e67...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: Amanieu
Pushing 402f84a2edf84d45457d3da76a69daa9e42a8e67 to master...


fix strip prefix bug in SaveOp

if strip_prefix_ not found in blob name, strip_prefix_.size() characters of blob name will be stripped.

Thanks for the fix!


Request for dropbox or radio options

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here

Current behavior

Can't select one from multiple options.
Expected behavior

Request for Dropbox or radio options
Reproduction of the problem

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Table version: 0.7.x

Angular version: 2.0.x

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [all | TypeScript X.X | ES6/7 | ES5]

What are you wanting to select from multiple options? You haven't really provided any context to this issue. Why can't this be solved with a header or a cell template? Radio buttons and drop downs are best left to external component libraries because the next complain will be "how do I make this function/appear as my other radio buttons/drop downs?"

I just find out that I can do it using template, sorry I haven't updated this issue, I will close it!
Thanks!


Fix error in notifies reload for delete action.

Description
This change fixes a syntax error inside of the delete resource.
Issues Resolved
Check List

[x] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[x] New functionality includes testing.
[x] New functionality has been documented in the README if applicable
[x] The CLA has been signed. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

/cc @tas50

Oops. Thanks for noticing that


Feat: Filtering Problem List using local files.

Hey, just wanted to add this feature, which is basically able to filter the problem list using both text and JSON files.
For example:
list.json
# My LeetCode Study List
two-sum
4sum|arrays,hash-table
longest-palindromic-substring|dynamic-programming

list.txt
{
  "dynamic-programming": [
    "longest-palindromic-substring",
    "coin-change"
  ],
  "arrays": [
    "two-sum",
    "4sum"
  ]
}

Basic Use:
:Leet custom file=my_list.txt

With additional Filters
:Leet custom file=my_list.txt filter=difficulty difficulty=medium
:Leet custom file=my_list.txt filter=status status=notac

Proof that is works.
Screencast from 2024-11-20 22-10-27.webm
(copilot summary below)
New functionality for custom list filtering:

lua/leetcode/cache/problemlist.lua: Added parse_custom_list function to parse custom list files and filter_by_custom_list function to filter problems based on the custom list. Also added Problemlist.filter_by_file method to integrate these functions.

Command structure updates:

lua/leetcode/command/arguments.lua: Added arguments.list_custom to define the structure for custom list command arguments, including file and filter options.
lua/leetcode/command/init.lua: Added cmd.custom_list function to handle the new custom list command and integrated it into the command list with cmd.commands.custom. [1] [2]

Here is neetcode 150 if you want to test it yourself.
neetcode.txt