text:
[Snyk] Upgrade com.fasterxml.jackson.datatype:jackson-datatype-jsr310 from 2.15.3 to 2.16.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade com.fasterxml.jackson.datatype:jackson-datatype-jsr310 from 2.15.3 to 2.16.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 3 versions ahead of your current version.
The recommended version was released 2 months ago, on 2023-12-24.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Closing this, as it falls into the same category of convergency errors mentioned here, and the decision here.

source: gharchive/pull-request

authors: Artur- taefi

repo: vaadin/hilla

license_type: permissive

license_source: github-api


text:
Improve UX of week numbers

Currently the date picker week numbers have some UX issue. They are equally close from two weeks. It’s not clear which week do they correspond to.

I’ll provide an updated design mockup.

We actually had this designed already by Tuomas. Some parts of the design have changed since, but you can use the week number design from this mockup: https://drive.google.com/file/d/0BzkWbWvgmkIxUlBlWDZRNHF1OWs/view

source: gharchive/issue

authors: jouni platosha

repo: vaadin/vaadin-date-picker

license_source: bigquery


text:
Fix typo

This change is

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

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

Comments from Reviewable

authors: Artur- CLAassistant limonte

repo: vaadin/vaadin-text-field


text:
RLN: Poseidon hash

Problem
Add poseidon hash with functionality according to spec.
Create an identity structure with identity commitment that can be inserted into a merkle tree.
From spec (https://github.com/vacp2p/rfc/blob/670816fa01f84fbde12a44f72f30e9b9458aaf5a/content/docs/rfcs/32/README.md):
[](https://github.com/vacp2p/rfc/blob/670816fa01f84fbde12a44f72f30e9b9458aaf5a/content/docs/rfcs/32/README.md#hash-function)Hash function

Canonical [Poseidon hash implementation](https://eprint.iacr.org/2019/458.pdf) is used, as implemented in the [circomlib library](https://github.com/iden3/circomlib/blob/master/circuits/poseidon.circom), according to the Poseidon paper. This Poseidon hash version (canonical implementation) uses the following parameters:

    t: 3
    RF: 8
    RP: 57

See:

https://github.com/iden3/circomlibjs/blob/main/src/poseidon.js
https://github.com/kilic/rln/blob/7ac74183f8b69b399e3bc96c1ae8ab61c026dc43/src/circuit/poseidon.rs
https://github.com/arnaucube/poseidon-rs

Acceptance criteria
Posedion hash function added and with correct parameters.

Easiest here is probably to use poseidon-rs

Done


text:
Error on Vagrant up in Windows

Hello, I've been using Vagrantpress for all of the sites I develop. But I've recently come to a project where I have to put the local environment on a Windows PC. (Windows 7)
Vagrant installed with no errors.
VirtualBox installed with no errors.
Hostupdater is installed, BUT i had the define the plugin home directory. Following this answer: (http://stackoverflow.com/questions/26102156/unable-to-install-plugin-hostmanager-in-vagrant-in-windows-8-1)
Downloaded the directory, ran vagrant up, and then I'm hitting an error when downloading the actual box.
default: Downloading: http://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box`
default:
An error occurred while downloading the remote file. The error message, if any, is reproduced below. Please fix this error and try again.
Theres no actual error message after. Has anyone encountered anything like this before? Are there any specific steps I need to take for a Windows enviroment?

Resolved: I needed to download the Microsoft C++ 2010 redistributable
link: https://www.microsoft.com/en-us/download/details.aspx?id=8328

repo: vagrantpress/vagrantpress

license: mit


text:
Improved route.go test coverage

Related to #32
Improved test coverage of route.go to 87.3%

Signed-off-by: Bennie van der Walt barendjohannes.vdwalt@gmail.com

Only a pleasure @vaguecoder 👋

repo: vaguecoder/gorilla-mux


text:
Task 10,11,22,23,24

Task 10,11,22,23,24 are done

SourceCode/2023/Sep2023/Basics/Chandupriya/Task_10/project.json
This comment is related to the 'Main.xaml' file:
Looks like there's an issue with the 'InputDialog' activity that's preventing your project from being analyzed. It seems UiPath can't identify this activity, likely due to a lack of its corresponding package in your project. To fix it:

Open your project in UiPath Studio.
In the Activities panel, search for 'InputDialog'.
Check its package details. Make sure it's correctly installed via the Package Manager.
If not, install/upgrade it and try again.

Remember to make sure all your activities are correctly installed and maintained to avoid this kind of issue in the future.

SourceCode/2023/Sep2023/Basics/Chandupriya/Task_11/project.json

Hey mate, there are a few things going off here.

This workflow seems to have a few errors. Tip: double-check your flow, so the project can be accurately analysed. Don’t wanna miss anything, right?

Looks like there's an issue with loading a file (C:\VSTS_BA1\_work\1\s\SourceCode\2023\Sep2023\Basics\Chandupriya\Task_11\Main.xaml). It's having trouble with 'InputDialog'. This could mean the software does not recognise that component. Ensure everything’s in place and in the right version, and retry. Remember, if you ever have issues, always ensure components are correctly installed and updated.

Let's get these sorted and move onwards, warrior. Don't forget to follow the code- check, correct, commit, and then we conquer!

SourceCode/2023/Sep2023/Basics/Chandupriya/Task_22/project.json
Hey there,
Hold up, seems like there's an issue with the Main.xaml file in your PR. Here's what could be going wrong:

You're trying to use the BuildDataTable activity, but UiPath doesn't seem to recognize it. Make sure you've installed all the necessary packages. Going to Manage Packages and installing UiPath.System.Activities should solve this.

There might be some errors in your workflows preventing the project from being analysed. You might want to go through each .xaml file, check the error list and fix them.

Keep it tight, eliminate the bugs, and let's roll over this issue.
Remember, preparation is key.

SourceCode/2023/Sep2023/Basics/Chandupriya/Task_23/project.json
The "Main.xaml" file seems to have an issue. {http://schemas.uipath.com/workflow/activities}MessageBox is not recognized. You might have a deprecated or invalid usage of MessageBox. Kindly check your usage and replace or fix it accordingly.
Also, the project cannot be analyzed because this file has errors. Please make sure error is fixed for analysis to proceed. Fixing the MessageBox call should resolve this.

@ChandupriyaY
Task-10
Code verified.
Task-11
Code verified.
Task-22
Code verified.
Task-23
Code verified.
Task-24
Code verified.

authors: ChandupriyaY krish952-creator vajrang-b

license: MIT


text:
First Shimmer effect start slowly

Hi, I use library very well.
Issue
In generally, API respond about 1 ~ 2seconds. but ShimmerEffect animation wait 1.5seconds below
animationSpec = infiniteRepeatable(
    animation = tween(
        800,
        easing = LinearEasing,
        delayMillis = 1_500, // I can't change `delayMillis`. it is interval time.
    ),
    repeatMode = RepeatMode.Restart,
),

because of this, animation effect doesn't show at first time.
I hope to change start delay of first animation.
Thanks.

Thanks! Fixed it with 1.3.0
That was something that annoyed me as well. I changed the defaultShimmerTheme to use a custom animation spec instead, which is based on a KeyframesSpec.
Instead of adding the delay to the beginning of the animation, it will now be added end, if you use the newly introduced shimmerSpec or the existing default theme.

authors: laco-dev valentinilk

repo: valentinilk/compose-shimmer


text:
🛑 PMANG is down

In b34c29c, PMANG (https://www.pmang.jp) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PMANG is back up in 7961e29 after 4 hours, 43 minutes.

repo: valofe/upptime


text:
Unable to remove tab when heading contains emoji

Whenever the heading for a tab contains an emoji such as 😄, that tab cannot be removed. Everything else seems to be working fine.

Never mind, it's actually a Chrome issue.


text:
Is it supported?

looks like it is not support, may be some answers from maintainers?

This library has more issues than entire frameworks.  Someone may need to fork.

Yeah was looking at the amount of issues and last updates. Not feeling very confident with this solution.

Hi. I am continue to develop in the fork:
https://github.com/optimistex/ngx-select-ex
There is solved a lot of issues. If are you found new big then just make an issue in my fork.

authors: murraybauer optimistex perrosen talgautb


text:
Upgrade to Typescript v4.x

Description
We are one major version behind on Typescript (we are still using v3.8.3) so it is time to upgrade. This will improve static typechecking and help us to detect bugs more quickly. Of note, the catch error type as any behaviour has been updated in Typescript v4 which would help us to write more robust error handling. (https://devblogs.microsoft.com/typescript/announcing-typescript-4-4/#using-unknown-in-catch-variables)
Acceptance Criteria

Upgrade to newest Typescript version
Fix type errors that arise
Ensure CI still passes
Ensure app still runs

completed in https://github.com/valora-inc/wallet/pull/2132

repo: valora-inc/wallet


text:
Add enriched wallet info endpoint

Proposed changes
Add enriched wallet info endpoint with owners per safe and related booleans addresed to frontend.
Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

nice!

authors: jmoreira-valory truemiller

repo: valory-xyz/olas-operate-app


text:
Added Aviator

Aviator -  Easy-to-use GUI for encoding with SVT-AV1-PSY & libopus
Python, GTK4, libadwaita
https://github.com/gianni-rosato/aviator
See also: https://thisweek.gnome.org/posts/2024/11/twig-172/
This time only one entry per PR :-)

Aviator is already present in the list but I guess we can move it to the "Media Encoders" category as you did.

Closed with #245.

repo: valpackett/awesome-gtk

license: Unlicense


text:
New Software Release 1.513.1975

Hi you'all!
After the last issue with updating Karoo 2 software, this new one version released yesterday also destroy every 3rd party app on the K2?
Just let me know.
Thanks!

I haven't fully tested every feature, but so far everything seems to be working fine. Feel free to upgrade your Karoo.

authors: Mputxeta valterc


text:
[FEAT] Common warning points

Is your feature request related to a problem? Please describe.
I want to define breaking points for data not related to any repository like that for reviewers.
Describe the solution you'd like
A page where I can define my  warning points.
I need to define values like:

Max Pending PRs for a reviewer
Max Sum of time PRs are waiting for a review from the reviewer

I will do this

repo: valueadd-poland/pimp-my-pr


text:
Can't install on local host

Hi There is any chance to update this to the new version of all dependencies
When i try to execue yarn start command i get an issue like below

Hello,
It seems the version of the node.js is the issue here, but I don't have the time to dig deeper. You can still run it locally if you switch to node.js 16.
Here's how to do it with nvm (https://github.com/nvm-sh/nvm):

Delete the node_modules folder if present
If you don't have node.js 16 install run nvm install 16
Switch to node.js 16: nvm use 16
Run: yarn install
Run :yarn start

Thanks! It works :)

repo: vangelov/calories-in


text:
fix qemu persistent mode for 32-bit target on 64-bit host

When running persistent qemu-mode with CPU_TARGET=i386 on x86_64 host like this:
AFL_DEBUG_CHILD_OUTPUT=1 AFL_QEMU_PERSISTENT_ADDR=$function_start_addr afl-fuzz -Q -i in -o out -- ./test @@

afl aborts with message:
/AFLplusplus/qemu_mode/qemu-3.1.1/tcg/tcg-op.c:2646: tcg fatal error
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
This patch fixes the error

thank you!

repo: vanhauser-thc/AFLplusplus


text:
Feature request : Retry on "Failed to Connect"

Due to the lag on device connect/disconnect it would be great to have a retry on a failure to connect to ensure the next command goes through.
Failed to connect to: 58:93:D8:3E:D2:DB Disconnected from: 58:93:D8:3E:D2:DB Traceback (most recent call last):   File "/home/ian/Downloads/melnor-bluetooth/turnoff1.py", line 16, in <module>     asyncio.run(main())   File "/home/ian/anaconda3/lib/python3.9/asyncio/runners.py", line 44, in run     return loop.run_until_complete(main)   File "/home/ian/anaconda3/lib/python3.9/asyncio/base_events.py", line 647, in run_until_complete     return future.result()   File "/home/ian/Downloads/melnor-bluetooth/turnoff1.py", line 13, in main     await device.push_state();   File "/home/ian/Downloads/melnor-bluetooth/melnor_bluetooth/device.py", line 240, in push_state     on_off.handle, AttributeError: 'NoneType' object has no attribute 'handle'

I'll be reworking the library fairly significantly to better support the new bluetooth hooks in Home Assistant. I'll see if/where this makes sense to land during that work.

Commands now guard against disconnected states and will attempt to reconnect if there's an issue

authors: blackshoals vanstinator

repo: vanstinator/melnor-bluetooth


text:
'Try a built demo' button is broken

The 'Try a built demo' button on the home page of the wiki leads to a 'Not Found' site.

btw thanks @ItsAnysek for beeing around here

I'm glad to help :)

authors: ItsAnysek vaporvee

repo: vaporvee/discord-sdk-godot


text:
Space 间隔 靠右属性 无效

Bug report 🐞
pc浏览器模拟h5有效，但微信内无效。

建议参数justify 增加可选值 flex-end
Version & Environment
0.1.5
微信开发者工具、微信pc客户端、部分安卓浏览器

感谢反馈，已修复该问题，将在下个小版本中体现

谢谢

authors: jjjjjmmmmm qytayh


text:
docs: rewrite docs and example in menu

Checklist

[ ] Fix linting errors
[ ] Tests have been added / updated (or snapshots)

Change information

Codecov Report

Merging #704 (4f73399) into dev (66e9745) will increase coverage by 0.07%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev     #704      +/-   ##
==========================================
+ Coverage   95.39%   95.46%   +0.07%
==========================================
  Files         217      217
  Lines        5338     5338
  Branches     1009      977      -32
==========================================
+ Hits         5092     5096       +4
- Misses        236      242       +6
+ Partials       10        0      -10

Impacted Files
Coverage Δ

packages/varlet-ui/src/tabs/Tabs.vue
76.25% <0.00%> (ø)

packages/varlet-ui/src/back-top/BackTop.vue
91.89% <0.00%> (ø)

packages/varlet-ui/src/collapse/Collapse.vue
86.36% <0.00%> (ø)

...varlet-ui/src/date-picker/src/day-picker-panel.vue
98.36% <0.00%> (ø)

...rlet-ui/src/bottom-navigation/BottomNavigation.vue
89.53% <0.00%> (ø)

...rlet-ui/src/date-picker/src/month-picker-panel.vue
93.54% <0.00%> (ø)

...kages/varlet-ui/src/collapse-item/CollapseItem.vue
98.18% <0.00%> (+7.27%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

authors: codecov-commenter wangKBweb

repo: varletjs/varlet


text:
Style guide

This PR explores adding a style guide.

[x] Merge #9 and rebase
[x] Ability to render markdown files
[x] Ability to render markdown files with erb
[x] Page route
[x] Add page navigation
[x] Add a way to render examples

[x] Print the rendered component in an iframe
[x] Print the code for rendering the component with syntax highlighting
[x] Make the iframe the correct size for the component. The width should be 100% and the height should have a maximum height, but otherwise adjust based on the height of the content. For components that are 100% wide themselves, it would be useful to be able to pass a width to the example.

[x] Make a home page for the style guide
[x] Make the component generator generate a style guide page
[x] Make an install generator to set up the style guide
[x] Decide what should be generated by default
[ ] Make it pretty
[ ] There's an issue with including component css, only the first component gets included
[ ] There seems to be an issue with the height of the iframe getting set to 150 even for small components

There are currently issues with both redcarpet and rouge, with them spitting out a lot of warnings. Hopefully new releases of both gems will fix those. There are also alternatives such as kramdown and coderay available.

Original idea
When it comes to printing the code for rendering the component, my current idea is to do something like this:
class ExampleComponent
  has_many :examples do
    attribute :source
  end

  # override this method...
  def examples(value = nil, attributes = nil, &block)
    if block
      # i suppose this will be the value variable in fact, but still...
      attributes[:source] = block.source # capture the content of the block somehow...
    end
    super
  end
end

Might need a gem to get the source of the block: https://github.com/banister/method_source. It's possible to do with #source_location as well but that means parsing the file, which seems a bit silly. Yet another solution would be to pass it as a string or something and then eval it but that sounds like a worse solution!
Update: Unfortunately the gems available can't extract the source of an erb block, only pure Ruby blocks.. Another issue is that you can't print erb markdown blocks without them getting evaluated.

The way examples are implemented is through markdown, similar to https://www.catalog.style. That is:
# Alert

Provide contextual feedback messages for typical user actions with the handful of available and flexible alert messages.

```example
<%= component "alert", message: "Something went right!", context: "success" %>
```

```example
<%= component "alert", message: "Something went wrong!", context: "danger" %>
```

That would a) render the component and b) render the erb source code. In order to do this, I think reversing the processing order should do the trick. That is, first process the template using markdown, then erb.
To test this PR, check out the repo, run bin/rails server and navigate to http://localhost:3000/styleguide.

@jimmynordlund Cool! I pushed some more markdown examples, I think one additional subheader and a blockquote. They're all on the style guide home page now. Some other feedback:

Should there be a max width for the page, or perhaps at least for the example wrapper? They get really wide on a big screen.
I think the iframe should be left adjusted instead of centered, for the same reason. It looks a bit weird on a big monitor, and ends up far away from the code sample.
The navigation should support at least one more level, but preferably more. Is it possible to redo it and have that work even without sass? Do you think it should be more clear what is clickable and what is not? I added another level to the test guide so should be easy to see it now at least.
I don't know about this for sure, but maybe the style guide should go in gray scale, so as not to interfere with the colors of the components? If there was a component with almost the same color as the navigation perhaps that would be annoying :P

@jensljungblad Pushed some updated styling with a new, more muted colour scheme and and a nav that supports deeper nesting and clearly differentiates between what’s clickable and what’s not. There’s also a max-width on the main container now. Feels much better.
The only thing I’m not entirely sold on is the left alignment of the component preview in the iframe. I like it centred. I feel like the “misalignment” is a plus, that it’s its own thing, a preview of something that lives somewhere else and therefore should break the “flow” and just be aligned against its own container. It’s also not as jarring now that the max-width of the main container is capped. But, all in all, minor detail. I’m fine with either really.

@jimmynordlund Cool! Feels better with the max width, agreed. I fixed an issue with how the example code was being generated that made the padding a bit weird, and also added a markdown code example to the dummy home page. I tweaked some paddings and stuff in the css, and also moved the font declarations from the pre to the code tag, didn't seem to work on the pre.
I also changed my mind about the Google Font dependency for now :P I have to think a bit if it's a good idea or not.. I added the native-stack from Bootstrap instead for now.
Perhaps it's good enough to test with the real style guide now, and then we can make further tweaks once we see how that looks!

authors: jensljungblad jimmynordlund

repo: varvet/components


text:
Day370

Completed the problem, however, the given test cases seem to be incorrect.

Resolves #954 .

Pull Request Test Coverage Report for Build 1766

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1770:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls

authors: coveralls vaskoz

repo: vaskoz/dailycodingproblem-go


text:
Release version 0.4

Prepare py4vasp for a public release with several updates to the documentation

@martin-schlipf, are there plans to open the Issues tracker now that py4vasp is public? It would be great to be able to contribute to this both via PRs and flagging issues as they arise.

Thanks @arosen93 for your interest in py4vasp. I hadn't opened the issue tracker, because we used to track issues in a separate private repository, but I agree that this is the best way to notify us of any problems with the code.
I've opened the issue tracker now.

Exciting!! Thank you!


text:
Runtime Error xmlpullparser

I get the below Error when i try to login using release version. The error does not appear during debug.  Any pointers how to resolve.
E/AndroidRuntime(22968): java.lang.ExceptionInInitializerError E/AndroidRuntime(22968):        at l.b.a.m.i(Unknown Source:0) E/AndroidRuntime(22968):        at l.b.a.d.<clinit>(Unknown Source:0) E/AndroidRuntime(22968):        at l.b.a.k0.d.y(Unknown Source:0) E/AndroidRuntime(22968):        at org.xrstudio.xmpp.flutter_xmpp.Connection.a.f(Unknown Source:4) E/AndroidRuntime(22968):        at org.xrstudio.xmpp.flutter_xmpp.Connection.FlutterXmppConnectionService.e(Unknown Source:36) E/AndroidRuntime(22968):        at org.xrstudio.xmpp.flutter_xmpp.Connection.FlutterXmppConnectionService.b(Unknown Source:0) E/AndroidRuntime(22968):        at org.xrstudio.xmpp.flutter_xmpp.Connection.FlutterXmppConnectionService$a.run(Unknown Source:15) E/AndroidRuntime(22968):        at java.lang.Thread.run(Thread.java:784) E/AndroidRuntime(22968): Caused by: java.lang.IllegalStateException: Could not parse Smack configuration file E/AndroidRuntime(22968):        at l.b.a.p.<clinit>(Unknown Source:197) E/AndroidRuntime(22968):        ... 8 more E/AndroidRuntime(22968): Caused by: org.xmlpull.v1.a: caused by: org.xmlpull.v1.a: resource not found: /META-INF/services/org.xmlpull.v1.XmlPullParserFactory make sure that parser implementing XmlPull API is available E/AndroidRuntime(22968):        at org.xmlpull.v1.b.b(Unknown Source:214) E/AndroidRuntime(22968):        at org.xmlpull.v1.b.a(Unknown Source:1) E/AndroidRuntime(22968):        at l.b.a.p.d(Unknown Source:0) E/AndroidRuntime(22968):        at l.b.a.p.c(Unknown Source:6) E/AndroidRuntime(22968):        at l.b.a.p.<clinit>(Unknown Source:98) E/AndroidRuntime(22968):        ... 8 more

You need to add the proguard rules while releasing for android or either disable the minify. @mugambikimathi

authors: mugambikimathi vavadiyahiren


text:
Removed suspicious/ambiguous API factory methods

Fixes #2003

Codecov Report

Merging #2024 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #2024      +/-   ##
============================================
- Coverage     97.62%   97.62%   -0.01%
+ Complexity     5168     5163       -5
============================================
  Files            91       91
  Lines         11835    11830       -5
  Branches       1568     1568
============================================
- Hits          11554    11549       -5
  Misses          134      134
  Partials        147      147

Impacted Files
Coverage Δ
Complexity Δ

vavr/src-gen/main/java/io/vavr/API.java
92.79% <ø> (+0.11%)
193 <0> (-4)
:arrow_down:

vavr/src/main/java/io/vavr/collection/TreeMap.java
97.4% <0%> (-0.44%)
151% <0%> (-1%)

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 4558730...5225fe2. Read the comment docs.

authors: codecov-io danieldietrich

repo: vavr-io/vavr


text:
Bug: docs build error

Version
Vben Admin V5
Describe the bug?
打包文档的时候就会报错，似乎是预览组件DemoPreview的路径没有被正确解析，缺了/？移除所有使用DemoPreview的地方后打包成功。
Reproduction

System Info
OS: Win11
Node: v20.17.0

Relevant log output
No response
Validations

[X] Read the docs
[X] Ensure the code is up to date. (Some issues have been fixed in the latest version)
[X] I have searched the existing issues and checked that my issue does not duplicate any existing issues.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

报错信息
@vben/docs:build:  ERROR  x Build failed in 4.09s
@vben/docs:build:
@vben/docs:build: ✖ building client + server bundles...
@vben/docs:build:
@vben/docs:build:  ERROR  build error:
@vben/docs:build: [vite-plugin-pwa:build] [vite]: Rollup failed to resolve import "D:Github
ue-vben-admindocssrcdemos
ben-draweasic/index.vue" from "D:/Github/vue-vben-admin/docs/src/components/common-ui/vben-drawer.md".
@vben/docs:build: This is most likely unintended because it can break your application at runtime.
@vben/docs:build: If you do want to externalize this module explicitly add it to
@vben/docs:build: `build.rollupOptions.external`
@vben/docs:build: [vite-plugin-pwa:build] [vite]: Rollup failed to resolve import "D:Github
ue-vben-admindocssrcdemos
ben-draweasic/index.vue" from "D:/Github/vue-vben-admin/docs/src/components/common-ui/vben-drawer.md".
@vben/docs:build: This is most likely unintended because it can break your application at runtime.
@vben/docs:build: If you do want to externalize this module explicitly add it to
@vben/docs:build: `build.rollupOptions.external`
@vben/docs:build:     at viteWarn (file:///D:/Github/vue-vben-admin/node_modules/.pnpm/vite@5.4.3_@types+node@22.5.4_less@4.2.0_sass@1.78.0_terser@5.32.0/node_modules/vite/dist/node/chunks/dep-BaOMuo4I.js:65511:17)
@vben/docs:build:     at onRollupWarning (file:///D:/Github/vue-vben-admin/node_modules/.pnpm/vite@5.4.3_@types+node@22.5.4_less@4.2.0_sass@1.78.0_terser@5.32.0/node_modules/vite/dist/node/chunks/dep-BaOMuo4I.js:65543:5)
@vben/docs:build:     at onwarn (file:///D:/Github/vue-vben-admin/node_modules/.pnpm/vite@5.4.3_@types+node@22.5.4_less@4.2.0_sass@1.78.0_terser@5.32.0/node_modules/vite/dist/node/chunks/dep-BaOMuo4I.js:65206:7)
@vben/docs:build:     at file:///D:/Github/vue-vben-admin/node_modules/.pnpm/rollup@4.21.2/node_modules/rollup/dist/es/shared/node-entry.js:18668:13
@vben/docs:build:     at Object.logger [as onLog] (file:///D:/Github/vue-vben-admin/node_modules/.pnpm/rollup@4.21.2/node_modules/rollup/dist/es/shared/node-entry.js:20306:9)
@vben/docs:build:     at ModuleLoader.handleInvalidResolvedId (file:///D:/Github/vue-vben-admin/node_modules/.pnpm/rollup@4.21.2/node_modules/rollup/dist/es/shared/node-entry.js:19257:26)
@vben/docs:build:     at file:///D:/Github/vue-vben-admin/node_modules/.pnpm/rollup@4.21.2/node_modules/rollup/dist/es/shared/node-entry.js:19215:26
@vben/docs:build:
@vben/docs:build:  ELIFECYCLE  Command failed with exit code 1.
@vben/docs:build: ERROR: command finished with error: command (D:\Github\vue-vben-admin\docs) C:\Users\admin\AppData\Roaming\npm\pnpm.cmd run build exited (1)
@vben/docs#build: command (D:\Github\vue-vben-admin\docs) C:\Users\admin\AppData\Roaming\npm\pnpm.cmd run build exited (1)

@yymjku18 试一下最新的

@yymjku18 试一下最新的

打包成功，非常感谢

repo: vbenjs/vue-vben-admin


text:
Can I just evaluate the results on the test set but not submit them to the leaderboard?

Hi, it is a good benchmark for image matching community, but some times,  I would like to just use it to improve our method rather than participate in the challenge directly.

In that case you can use the validation sets, or whatever split you desire. It should be an easy fix. We won’t be able to release the test sets, since we intend to keep the challenge going for at lease a few years.
Thanks
Message written with iPhone.
Please excuse any brievity and typos.
—
Kwang Moo YI
Assistant Professor
Dept. of Computer Science
University of Victoria
+1 (250) 475 5837

On Jun 9, 2020, at 20:52, Jizhou Ma notifications@github.com wrote:

Hi, it is a good benchmark for image matching community, but some times, I would like to just use it to improve our method rather than participate in the challenge directly.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thank you for your answer

authors: Jizma kmyid

repo: vcg-uvic/image-matching-benchmark


text:
Question about async create index interface

Thanks for the great project.
I noticed that vearch need to be indexed after insert data using '_forcemerge' interface.
However, I found that is an async interface. So, when I get success code from this url, I get low recall result with HNSW and empty result with gpu IVF-PQ / cpu IVF-Flat.
I try to look for something about this in documents, but I failed.
How can I do to know when the indexing is successfully done?

Agree. I spend a day to figure out the '_forcemerge' is async.
I am using vearch v3.1.0. This might work:
response = requests.get("http://" + ip_db + "/_cluster/stats")
index_status = json.loads(response.text)[0]["spaces"][0]["partitions"][0]["index_status"]

when indexing is over. index_status==2.

Thank you. I will have a try.
However, I think an interface about that maybe better.

repo: vearch/vearch


text:
parameterizes basic_cup for easy import

This results in the same render but passes all the values through from the top level basic_cup allowing other projects to import the objects with use and call the basic_cup method with all or none of their own parameters.

Superseded by #12


text:
Hardware architecture

Hi. I have a NVIDIA NX board, which is based on ARM architecture. I encountered the following problems when compiling on the NX board.

Can this package run under arm architecture? Is this error related to the architecture? How to solve this issue?

Hi @HomieRegina -- yes, this was something we also saw during our internal tests on a Raspberry Pi (also ARM). ARM-based boards apparently do not have the cpuid.h system header file.
We've released a patch in v1.4.1 which should fix this.

Hi @HomieRegina -- yes, this was something we also saw during our internal tests on a Raspberry Pi (also ARM). ARM-based boards apparently do not have the cpuid.h system header file.
We've released a patch in v1.4.1 which should fix this.

Thanks for your great work. We will test it soon.

authors: HomieRegina kennyjchen


text:
Define maximum number of items or number of pages

Is it possible to not just limit the number of items per page but limit the total number of items or the number pages. For example, i only want for some cases to display 3 items and stop the pagination no matter how many items are left in the collection. Is this behavior possible?
Thank you.

Hello, I had the same question.  Looking forward for an answer.


text:
[WIP] PHP84 : Add spec compliance

Q
A

Type
improvement

BC Break
yes

Fixed issues
#72

Summary
A playground for the new spec-compliance RFC:

https://wiki.php.net/rfc/opt_in_dom_spec_compliance
https://wiki.php.net/rfc/domdocument_html5_parser
https://wiki.php.net/rfc/improve_callbacks_dom_and_xsl

WIP: Extended DOM

https://github.com/nielsdos/php-src/pull/93

Current stats:
 ...............................................................  63 / 607 ( 10%)
............................................................... 126 / 607 ( 20%)
............................................................... 189 / 607 ( 31%)
............................................................... 252 / 607 ( 41%)
............................................................... 315 / 607 ( 51%)
............................................................... 378 / 607 ( 62%)
............................................................... 441 / 607 ( 72%)
............................................................... 504 / 607 ( 83%)
............................................................... 567 / 607 ( 93%)
........................................                        607 / 607 (100%)

Time: 00:00.183, Memory: 34.43 MB

OK (607 tests, 1047 assertions)

TODO:

Infection
Static analysis

Just letting you know that while waiting for the reviews, I spent some time today implementing the missing APIs in a separate branch. (Can be found at https://github.com/nielsdos/php-src/pull/93)
In particular:

DOM\Element::$substitutedNodeValue (I might add the same one for DOM\Attr too, not sure yet)
DOM\Element::getInScopeNamespaces(): array
DOM\Element::rename(?string $namespaceURI, string $qualifiedName): void and also for DOM\Attr.
As expected, these were rather easy to implement.

Just wanted to give you a small update @nielsdos  :

The new entity substitution works flawlessly
Renaming nodes works in general, but I have a feeling there are a few cases not working properly (will come back to this when later, I now covered about half of the test-suite but I need to dive into the specifics so that I can give you more detailed information)
Removing namespaces works as described above (one case still failing - need to dive into the specifics as well)
The getInScopeNamespaces works theoretically, but I expect it to work a bit different. I've mentioned in your PR :  https://github.com/nielsdos/php-src/pull/93#discussion_r1511227671

Tests: 608, Assertions: 1022, Errors: 20, Failures: 21.

Getting closer to the end goal :)

Thanks for the update! Nice to see ^^
I'll try to have a look soon-ish at how to deal with the getInScopeNamespaces() discrepancy.
As for the other issues: if you're stuck debugging them, I could always try to have a look at your code with a debug PHP build, if I know what test case to look for :)

@nielsdos All unit tests are succeeding, which is nice.
Next up - static analysis:

64 errors found

I'm using the stubs that are included in your PR which are not able to infer specific types in specific situations. What would be the best way forward there? Is it a matter of just fixing the provided stub files? Or should some kind of effort be needed in psalm ad well? How do you see the path forward there?
(I know it' still very early for adding PHP 8.4 support - but I'm just asking to figure out what the next steps would be in that space.)

Psalm has stubs built in, which they also further annotate with version information, e.g. https://github.com/vimeo/psalm/blob/5.x/stubs/extensions/dom.phpstub
So when 8.4 support comes they'll have to copy over the new stuff from our own stubs and add the PHP 8.4 version annotation for the new stuff.
Can you share an example of a type inference error?

Can you share an example of a type inference error?

I'm just gonna paste the full list of errors here so that you can skim around it - but that doesnt mean I expect answers for them ;)
I still need to go through the list and eliminate my own mistakes and will try to narrow down the list by altering the stub file from my end. Maybe it can be shared with spalm when I'm done with it.

Reveal the errrors
ERROR: MissingDependency - src/Xml/Dom/Assert/assert_dom_node_list.php:15:45 - DOM\NodeList depends on class or interface dom\iteratoraggregate that does not exist (see https://psalm.dev/157)
function assert_dom_node_list(mixed $node): \DOM\NodeList

ERROR: MoreSpecificReturnType - src/Xml/Dom/Assert/assert_dom_node_list.php:15:45 - The declared return type 'DOM\NodeList' for VeeWee\Xml\Dom\Assert\assert_dom_node_list is more specific than the inferred return type 'object' (see https://psalm.dev/070)
function assert_dom_node_list(mixed $node): \DOM\NodeList

ERROR: LessSpecificReturnStatement - src/Xml/Dom/Assert/assert_dom_node_list.php:17:12 - The type 'object' is more general than the declared return type 'DOM\NodeList' for VeeWee\Xml\Dom\Assert\assert_dom_node_list (see https://psalm.dev/129)
    return instance_of(\DOM\NodeList::class)->assert($node);

ERROR: MissingDependency - src/Xml/Dom/Assert/assert_dom_node_list.php:17:24 - DOM\NodeList depends on class or interface dom\iteratoraggregate that does not exist (see https://psalm.dev/157)
    return instance_of(\DOM\NodeList::class)->assert($node);

ERROR: MixedArgument - src/Xml/Dom/Assert/assert_dom_node_list.php:17:24 - Argument 1 of Psl\Type\instance_of cannot be mixed, expecting class-string (see https://psalm.dev/030)
    return instance_of(\DOM\NodeList::class)->assert($node);

ERROR: MissingDependency - src/Xml/Dom/Collection/NodeList.php:63:15 - DOM\HTMLCollection depends on class or interface dom\iteratoraggregate that does not exist (see https://psalm.dev/157)
     * @param \DOM\HTMLCollection $list

ERROR: MixedInferredReturnType - src/Xml/Dom/Collection/NodeList.php:64:16 - Could not verify return type 'VeeWee\Xml\Dom\Collection\NodeList<DOM\Element>' for VeeWee\Xml\Dom\Collection\NodeList::fromDOMHTMLCollection (see https://psalm.dev/047)
     * @return NodeList<\DOM\Element>

ERROR: MissingDependency - src/Xml/Dom/Collection/NodeList.php:73:15 - DOM\NodeList depends on class or interface dom\iteratoraggregate that does not exist (see https://psalm.dev/157)
     * @param DOMNodeList<X> $list

ERROR: MixedInferredReturnType - src/Xml/Dom/Collection/NodeList.php:74:16 - Could not verify return type 'VeeWee\Xml\Dom\Collection\NodeList<X>' for VeeWee\Xml\Dom\Collection\NodeList::fromDOMNodeList (see https://psalm.dev/047)
     * @return NodeList<X>

ERROR: InvalidClass - src/Xml/Dom/Collection/NodeList.php:196:15 - Class, interface or enum DOMXpath has wrong casing (see https://psalm.dev/007)
     * @param list<callable(DOMXpath): DOMXpath> $configurators

ERROR: InvalidArgument - src/Xml/Dom/Collection/NodeList.php:208:52 - Argument 2 of VeeWee\Xml\Dom\Xpath::fromUnsafeNode expects callable(DOM\XPath):DOM\XPath, but callable(DOMXpath):DOMXpath provided (see https://psalm.dev/004)
                => Xpath::fromUnsafeNode($node, ...$configurators)->query($xpath, $node)

ERROR: InvalidClass - src/Xml/Dom/Collection/NodeList.php:214:15 - Class, interface or enum DOMXpath has wrong casing (see https://psalm.dev/007)
     * @param list<callable(DOMXpath): DOMXpath> $configurators

ERROR: InvalidArgument - src/Xml/Dom/Collection/NodeList.php:222:52 - Argument 2 of VeeWee\Xml\Dom\Xpath::fromUnsafeNode expects callable(DOM\XPath):DOM\XPath, but callable(DOMXpath):DOMXpath provided (see https://psalm.dev/004)
                => Xpath::fromUnsafeNode($node, ...$configurators)->evaluate($expression, $type, $node)

ERROR: InaccessibleProperty - src/Xml/Dom/Configurator/document_uri.php:17:9 - DOM\XMLDocument::$documentURI is marked readonly (see https://psalm.dev/054)
        $document->documentURI = $documentUri;

ERROR: MixedReturnTypeCoercion - src/Xml/Dom/Locator/Attribute/attributes_list.php:14:12 - The declared return type 'VeeWee\Xml\Dom\Collection\NodeList<DOM\Attr>' for VeeWee\Xml\Dom\Locator\Attribute\attributes_list is more specific than the inferred return type 'VeeWee\Xml\Dom\Collection\NodeList<mixed>|VeeWee\Xml\Dom\Collection\NodeList<never>' (see https://psalm.dev/197)
 * @return NodeList<\DOM\Attr>

ERROR: InvalidArgument - src/Xml/Dom/Locator/Attribute/attributes_list.php:22:26 - Argument 1 of Psl\Vec\values expects iterable<mixed, mixed>, but DOM\NamedNodeMap provided (see https://psalm.dev/004)
    $attributes = values($node->attributes);

ERROR: MixedReturnTypeCoercion - src/Xml/Dom/Locator/Attribute/attributes_list.php:24:12 - The type 'VeeWee\Xml\Dom\Collection\NodeList<mixed>' is more general than the declared return type 'VeeWee\Xml\Dom\Collection\NodeList<DOM\Attr>' for VeeWee\Xml\Dom\Locator\Attribute\attributes_list (see https://psalm.dev/197)
    return new NodeList(...$attributes);

ERROR: MixedArgument - src/Xml/Dom/Locator/Attribute/attributes_list.php:24:28 - Argument 1 of VeeWee\Xml\Dom\Collection\NodeList::__construct cannot be mixed, expecting DOM\Node (see https://psalm.dev/030)
    return new NodeList(...$attributes);

ERROR: InvalidArgument - src/Xml/Dom/Locator/Element/children.php:20:9 - Argument 1 of Psl\Vec\filter expects iterable<mixed, mixed>, but DOM\NodeList provided (see https://psalm.dev/004)
        $node->childNodes,

ERROR: MissingDependency - src/Xml/Dom/Locator/Element/siblings.php:20:9 - DOM\NodeList depends on class or interface dom\iteratoraggregate that does not exist (see https://psalm.dev/157)
        $node->parentNode?->childNodes?->getIterator() ?? [],

ERROR: MixedArgument - src/Xml/Dom/Locator/Element/siblings.php:20:9 - Argument 1 of Psl\Vec\filter cannot be array<never, never>|mixed, expecting iterable<mixed, mixed> (see https://psalm.dev/030)
        $node->parentNode?->childNodes?->getIterator() ?? [],

ERROR: MoreSpecificReturnType - src/Xml/Dom/Locator/Node/detect_document.php:17:44 - The declared return type 'DOM\XMLDocument' for VeeWee\Xml\Dom\Locator\Node\detect_document is more specific than the inferred return type 'DOM\Document|null' (see https://psalm.dev/070)
function detect_document(\DOM\Node $node): \DOM\XMLDocument

ERROR: LessSpecificReturnStatement - src/Xml/Dom/Locator/Node/detect_document.php:19:12 - The type 'DOM\Document|DOM\XMLDocument|null' is more general than the declared return type 'DOM\XMLDocument' for VeeWee\Xml\Dom\Locator\Node\detect_document (see https://psalm.dev/129)
    return is_document($node) ? $node : $node->ownerDocument;

ERROR: NullableReturnStatement - src/Xml/Dom/Locator/Node/detect_document.php:19:12 - The declared return type 'DOM\XMLDocument' for VeeWee\Xml\Dom\Locator\Node\detect_document is not nullable, but the function returns 'DOM\Document|null' (see https://psalm.dev/139)
    return is_document($node) ? $node : $node->ownerDocument;

ERROR: PossiblyNullPropertyFetch - src/Xml/Dom/Locator/Xsd/locate_namespaced_xsd_schemas.php:20:19 - Cannot get property on possibly null variable $document->documentElement of type DOM\Element|null (see https://psalm.dev/082)
    $attributes = $document->documentElement->attributes;

ERROR: MixedAssignment - src/Xml/Dom/Locator/Xsd/locate_namespaced_xsd_schemas.php:23:10 - Unable to determine the type that $schemaLocation is being assigned to (see https://psalm.dev/032)
    if (!$schemaLocation = $attributes->getNamedItemNS($schemaNs, 'schemaLocation')) {

ERROR: MissingDependency - src/Xml/Dom/Locator/Xsd/locate_namespaced_xsd_schemas.php:23:28 - DOM\NamedNodeMap depends on class or interface dom\iteratoraggregate that does not exist (see https://psalm.dev/157)
    if (!$schemaLocation = $attributes->getNamedItemNS($schemaNs, 'schemaLocation')) {

ERROR: PossiblyNullReference - src/Xml/Dom/Locator/Xsd/locate_namespaced_xsd_schemas.php:23:41 - Cannot call method getNamedItemNS on possibly null value (see https://psalm.dev/083)
    if (!$schemaLocation = $attributes->getNamedItemNS($schemaNs, 'schemaLocation')) {

ERROR: MixedPropertyFetch - src/Xml/Dom/Locator/Xsd/locate_namespaced_xsd_schemas.php:28:25 - Cannot fetch property on mixed var $schemaLocation (see https://psalm.dev/034)
    $parts = split(trim($schemaLocation->textContent), '/\s+/');

ERROR: MixedArgument - src/Xml/Dom/Locator/Xsd/locate_namespaced_xsd_schemas.php:28:25 - Argument 1 of trim cannot be mixed, expecting string (see https://psalm.dev/030)
    $parts = split(trim($schemaLocation->textContent), '/\s+/');

ERROR: PossiblyNullPropertyFetch - src/Xml/Dom/Locator/Xsd/locate_no_namespaced_xsd_schemas.php:21:19 - Cannot get property on possibly null variable $document->documentElement of type DOM\Element|null (see https://psalm.dev/082)
    $attributes = $document->documentElement->attributes;

ERROR: MixedAssignment - src/Xml/Dom/Locator/Xsd/locate_no_namespaced_xsd_schemas.php:22:10 - Unable to determine the type that $schemaLocNoNamespace is being assigned to (see https://psalm.dev/032)
    if (!$schemaLocNoNamespace = $attributes->getNamedItemNS($schemaNs, 'noNamespaceSchemaLocation')) {

ERROR: MissingDependency - src/Xml/Dom/Locator/Xsd/locate_no_namespaced_xsd_schemas.php:22:34 - DOM\NamedNodeMap depends on class or interface dom\iteratoraggregate that does not exist (see https://psalm.dev/157)
    if (!$schemaLocNoNamespace = $attributes->getNamedItemNS($schemaNs, 'noNamespaceSchemaLocation')) {

ERROR: PossiblyNullReference - src/Xml/Dom/Locator/Xsd/locate_no_namespaced_xsd_schemas.php:22:47 - Cannot call method getNamedItemNS on possibly null value (see https://psalm.dev/083)
    if (!$schemaLocNoNamespace = $attributes->getNamedItemNS($schemaNs, 'noNamespaceSchemaLocation')) {

ERROR: MixedPropertyFetch - src/Xml/Dom/Locator/Xsd/locate_no_namespaced_xsd_schemas.php:27:25 - Cannot fetch property on mixed var $schemaLocNoNamespace (see https://psalm.dev/034)
    $parts = split(trim($schemaLocNoNamespace->textContent), '/\s+/');

ERROR: MixedArgument - src/Xml/Dom/Locator/Xsd/locate_no_namespaced_xsd_schemas.php:27:25 - Argument 1 of trim cannot be mixed, expecting string (see https://psalm.dev/030)
    $parts = split(trim($schemaLocNoNamespace->textContent), '/\s+/');

ERROR: InvalidNullableReturnType - src/Xml/Dom/Locator/document_element.php:16:52 - The declared return type 'DOM\Element' for /users/verweto/projects/github/veewee/xml/src/xml/dom/locator/document_element.php:16:231:-:closure is not nullable, but 'DOM\Element|null' contains null (see https://psalm.dev/144)
    return static fn (\DOM\XMLDocument $document): \DOM\Element => $document->documentElement;

ERROR: NullableReturnStatement - src/Xml/Dom/Locator/document_element.php:16:68 - The declared return type 'DOM\Element' for /users/verweto/projects/github/veewee/xml/src/xml/dom/locator/document_element.php:16:231:-:closure is not nullable, but the function returns 'DOM\Element|null' (see https://psalm.dev/139)
    return static fn (\DOM\XMLDocument $document): \DOM\Element => $document->documentElement;

ERROR: PossiblyNullArgument - src/Xml/Dom/Locator/elements_with_namespaced_tagname.php:23:46 - Argument 1 of VeeWee\Xml\Dom\Locator\Element\locate_by_namespaced_tag_name cannot be null, possibly null value provided (see https://psalm.dev/078)
            => locate_by_namespaced_tag_name($document->documentElement, $namespace, $localTagName);

ERROR: PossiblyNullArgument - src/Xml/Dom/Locator/elements_with_tagname.php:23:35 - Argument 1 of VeeWee\Xml\Dom\Locator\Element\locate_by_tag_name cannot be null, possibly null value provided (see https://psalm.dev/078)
            => locate_by_tag_name($document->documentElement, $tagName);

ERROR: PossiblyNullPropertyFetch - src/Xml/Dom/Locator/root_namespace.php:15:63 - Cannot get property on possibly null variable $document->documentElement of type DOM\Element|null (see https://psalm.dev/082)
    return static fn (\DOM\XMLDocument $document): ?string => $document->documentElement->namespaceURI;

ERROR: MixedInferredReturnType - src/Xml/Dom/Manipulator/Attribute/rename.php:19:42 - Could not verify return type 'DOM\Attr' for /users/verweto/projects/github/veewee/xml/src/xml/dom/manipulator/attribute/rename.php:19:522:-:closure (see https://psalm.dev/047)
    return disallow_issues(static fn (): \DOM\Attr => match(true) {

ERROR: MixedReturnStatement - src/Xml/Dom/Manipulator/Attribute/rename.php:19:55 - Possibly-mixed return value (see https://psalm.dev/138)
    return disallow_issues(static fn (): \DOM\Attr => match(true) {
        is_xmlns_attribute($target) => rename_xmlns_attribute($target, $newQName),
        default => tap(fn () => $target->rename($newNamespaceURI, $newQName))($target)
    });

ERROR: MixedReturnStatement - src/Xml/Dom/Manipulator/Attribute/rename.php:19:55 - Could not infer a return type (see https://psalm.dev/138)
    return disallow_issues(static fn (): \DOM\Attr => match(true) {
        is_xmlns_attribute($target) => rename_xmlns_attribute($target, $newQName),
        default => tap(fn () => $target->rename($newNamespaceURI, $newQName))($target)
    });

ERROR: PossiblyNullArgument - src/Xml/Dom/Manipulator/Document/optimize_namespaces.php:23:37 - Argument 1 of VeeWee\Xml\Dom\Locator\Xmlns\recursive_linked_namespaces cannot be null, possibly null value provided (see https://psalm.dev/078)
        recursive_linked_namespaces($documentElement),

ERROR: InvalidNullableReturnType - src/Xml/Dom/Manipulator/Document/optimize_namespaces.php:24:47 - The declared return type 'string' for /users/verweto/projects/github/veewee/xml/src/xml/dom/manipulator/document/optimize_namespaces.php:24:711:-:closure is not nullable, but 'null|string' contains null (see https://psalm.dev/144)
        static fn (\DOM\NamespaceInfo $info): string => $info->namespaceURI

ERROR: NullableReturnStatement - src/Xml/Dom/Manipulator/Document/optimize_namespaces.php:24:57 - The declared return type 'string' for /users/verweto/projects/github/veewee/xml/src/xml/dom/manipulator/document/optimize_namespaces.php:24:711:-:closure is not nullable, but the function returns 'null|string' (see https://psalm.dev/139)
        static fn (\DOM\NamespaceInfo $info): string => $info->namespaceURI

ERROR: RiskyTruthyFalsyComparison - src/Xml/Dom/Manipulator/Element/copy_named_xmlns_attributes.php:17:13 - Operand of type null|string contains type string, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
        if ($xmlns->prefix && !$target->hasAttribute($xmlns->nodeName)) {

ERROR: PossiblyNullOperand - src/Xml/Dom/Manipulator/Element/rename.php:27:88 - Cannot concatenate with a possibly null null|string (see https://psalm.dev/080)
    if ($newPrefix && $newPrefix !== $target->prefix && $target->hasAttribute('xmlns:'.$target->prefix)) {

ERROR: PossiblyNullOperand - src/Xml/Dom/Manipulator/Element/rename.php:28:43 - Cannot concatenate with a possibly null null|string (see https://psalm.dev/080)
        $target->removeAttribute('xmlns:'.$target->prefix);

ERROR: InvalidPropertyAssignmentValue - src/Xml/Dom/Traverser/Visitor/RemoveNamespaces.php:26:25 - $this->filter with declared type 'callable(DOM\Attr|DOM\Element):bool|null' cannot be assigned type 'callable(DOM\Attr):bool|null' (see https://psalm.dev/145)
        $this->filter = $filter;

ERROR: UndefinedPropertyFetch - src/Xml/Dom/Traverser/Visitor/RemoveNamespaces.php:84:38 - Instance property DOM\Node::$localName is not defined (see https://psalm.dev/039)
        return new Action\RenameNode($node->localName, null);

ERROR: MixedArgument - src/Xml/Dom/Traverser/Visitor/RemoveNamespaces.php:84:38 - Argument 1 of VeeWee\Xml\Dom\Traverser\Action\RenameNode::__construct cannot be mixed, expecting string (see https://psalm.dev/030)
        return new Action\RenameNode($node->localName, null);

ERROR: MissingDependency - src/Xml/Dom/Xpath/Locator/query.php:24:27 - DOM\NodeList depends on class or interface dom\iteratoraggregate that does not exist (see https://psalm.dev/157)
            static fn (): DOMNodeList => assert_dom_node_list(

ERROR: MixedInferredReturnType - src/Xml/Dom/Xpath/Locator/query_single.php:28:66 - Could not verify return type 'DOM\Node' for /users/verweto/projects/github/veewee/xml/src/xml/dom/xpath/locator/query_single.php:28:695:-:closure (see https://psalm.dev/047)
        static function (\DOM\XPath $xpath) use ($query, $node): \DOM\Node {

ERROR: MissingDependency - src/Xml/Dom/Xpath/Locator/query_single.php:31:31 - DOM\NodeList depends on class or interface dom\iteratoraggregate that does not exist (see https://psalm.dev/157)
                static fn (): \DOM\NodeList => assert_dom_node_list(

ERROR: InvalidArgument - src/Xml/Dom/Xpath/Locator/query_single.php:40:17 - Argument 1 of Webmozart\Assert\Assert::count expects Countable|array<array-key, mixed>, but DOM\NodeList provided (see https://psalm.dev/004)
                $list,

ERROR: InvalidArgument - src/Xml/Dom/Xpath/Locator/query_single.php:42:96 - Argument 1 of count expects Countable|array<array-key, mixed>, but DOM\NodeList provided (see https://psalm.dev/004)
                format('Expected to find only one node that matches %s. Got %s', $query, count($list))

ERROR: MissingDependency - src/Xml/Dom/Xpath/Locator/query_single.php:45:20 - DOM\NodeList depends on class or interface dom\iteratoraggregate that does not exist (see https://psalm.dev/157)
            return $list->item(0);

ERROR: MixedReturnStatement - src/Xml/Dom/Xpath/Locator/query_single.php:45:20 - Could not infer a return type (see https://psalm.dev/138)
            return $list->item(0);

ERROR: InvalidReturnType - src/Xml/Encoding/Internal/Decoder/Builder/element.php:14:12 - The declared return type 'array<string, array<array-key, mixed>|string>' for VeeWee\Xml\Encoding\Internal\Decoder\Builder\element is incorrect, got 'non-empty-array<string, array<array-key, mixed>|null|string>' (see https://psalm.dev/011)
 * @return array<string, string|array>

ERROR: InvalidReturnStatement - src/Xml/Encoding/Internal/Decoder/Builder/element.php:25:16 - The inferred type 'non-empty-array<string, null|string>' does not match the declared return type 'array<string, array<array-key, mixed>|string>' for VeeWee\Xml\Encoding\Internal\Decoder\Builder\element (see https://psalm.dev/128)
        return [$name => $element->textContent];

ERROR: RiskyTruthyFalsyComparison - src/Xml/Encoding/Internal/Decoder/Builder/namespaces.php:25:26 - Operand of type null|string contains type string, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
                        ($node->prefix ? $node->localName : '') => $node->value

ERROR: InvalidArgument - src/Xml/Xslt/Transformer/document_to_string.php:22:44 - Argument 1 of XSLTProcessor::transformToXml expects DOMDocument, but DOM\XMLDocument provided (see https://psalm.dev/004)
                $processor->transformToXML($document->toUnsafeDocument()),

At least some errors are legit, e.g. Class, interface or enum DOMXpath has wrong casing (see https://psalm.dev/007)
Some others, e.g. Instance property DOM\Node::$localName is not defined (see https://psalm.dev/039), are because localName is now only defined on DOM\Attr and DOM\Element.
Some others are about nullability.
So all in all, quite a few seem to be because of type changes.

DOM\HTMLCollection depends on class or interface dom\iteratoraggregate

This one is a "mistake" in the stub and you can fix it by copying the stub from the master branch. This was found already by one of the Symfony developers and fixed in master. What's going on here is that I didn't put a backslash before IteratorAggregate so it first searches in the DOM namespaces and only after that fails in the global namespace. I put "mistake" in quotes because technically it works due to how namespace lookup works in PHP, but looks like psalm is very strict.

Stubs issues:
This is a WIP: gonna fill it up as I go....

✅  Collections don't contain more detailed iterable<Tk, Tv> information : manually adding to the stub files.

❌ Document::documentURI:

ERROR: InaccessibleProperty - src/Xml/Dom/Configurator/document_uri.php:17:9 - DOM\XMLDocument::$documentURI is marked readonly (see https://psalm.dev/054)
        $document->documentURI = $documentUri;

documentURI is marked as readonly in the stubs but is not readonly:
See tests/Xml/Dom/Configurator/DocumentUriTest.php. This feature is being used for inline XSD schema parsing in WSDLs from my end and I suppose should be left writeable?

✅ Collections don't contain more detailed iterable<Tk, Tv> information : manually adding to the stub files from my side. This should probably be ported to psalm.

Yeah this information should be put into psalm eventually.

documentURI is marked as readonly in the stubs but is not readonly:

Fixed in https://github.com/php/php-src/pull/13982, good catch

❌ Node::$ownerDocument is null|Document? I would expect it to never be null? What is the case for null here?

This is, unfortunately, the right type. $ownerDocument is only NULL for document nodes, and the owner document for other nodes. See spec: https://dom.spec.whatwg.org/#dom-node-ownerdocument

❌ Document::$documentElement is null|Document? I would expect it to never be null? What is the case for null here?

This is also unfortunately possible. I.e.: https://3v4l.org/bsF7g/rfc#vgit.master

In other news, I've been wrapping up the implementation work for the remaining features I wanted to add to ext-dom in PHP 8.4.
One thing I'm having some difficulties with is the API design of Element::rename function proposed earlier.
The problem is as follows:
In one of the feature additions I'm proposing for 8.4, I'm adding Document::$body. This has the type HTMLElement. HTMLElement is a class that extends Element, and the idea here is that if an element is in the HTML namespace, getting an element should return an instance of HTMLElement instead of Element. (For example if firstElementChild is in the HTML namespace, it returns an HTMLElement)
This clashes with Element::rename. Let's say we start with an element in the namespace "urn:x" and we use Element::rename to change the namespace to the HTML namespace. Suddenly our Element instance should actually be an HTMLElement object, but that's not possible because we can't change the object type of an instance. Similarly, the opposite problems happens when we go from the HTML namespace to a non-HTML namespace.
I haven't been able to come up with a good solution. Here are some things I thought about:

Ignore the problem. The easy solution, but might also be weird because suddenly you can't assign it to properties that have the HTMLElement type, even if you changed the element to the HTML namespace.
Return a new instance from rename(). This would work but is kind of awkward for developers I think. Also when the element is already stored somewhere this is a recipe for disaster as the existing instance of the element is stale.
Leave rename() out. Also an easy solution but would be annoying for developers...

I'm not sure how to go about it. Maybe you have some ideas.

@nielsdos
If I understand the problem correctly, then it's about some kind of transition from HTMLElement to regular Element and the other way around?
I'm a bit confused by the sentence:

and the idea here is that if an element is in the HTML namespace, getting an element should return an instance of HTMLElement instead of Element.

This means that wether it returns a HTMLElement is based on a namespace URI like http://www.w3.org/1999/xhtml?
There are some ways to look at this:

Would renaming an HTML element be something someone wants to do in PHP context? I guess it will probably be a rather limited approach. Renaming the namespace there would most likely be many bridges too far.
Renaming an XML element into a HTML element would most likely also be an operation that would hardly ever happen. I can imagine a scenario where you want to add something that looks like HTML to XML, but it won't really be HTML compliant I suppose.

Let's take a look at the provided solutions:

Ignore the problem. The easy solution, but might also be weird because suddenly you can't assign it to properties that have the HTMLElement type, even if you changed the element to the HTML namespace.

I'm not sure what properties you are talking about here - but I would say that switching type of node is not something you want to do here. So to me this is a no-go.

Return a new instance from rename(). This would work but is kind of awkward for developers I think. Also when the element is already stored somewhere this is a recipe for disaster as the existing instance of the element is stale.

This is indeed not a good idea either. However I do like the idea of making it return the node you are renaming so that it can be chained. That's another discussion I suppose.

Leave rename() out. Also an easy solution but would be annoying for developers...

You mean leave it out of the HTMLElement class? This might be confusing since you are extending the regular Element and it would be there and throw an exception. It is still needed in regular Element though for various operations you can find in this repository, so not having it would be kinda blocking.
Maybe some other ideas:

Add a hard block on renaming cross node-types by throwing an exception? It can be done by checking the source and target namespace I suppose. Since this is an operation that wouldn't or shouldnt happen in many scenarios, it might be a sensible thing to do?

Limiting the rename() method on the HTMLElement so that you cannot change namespaces. This would still lead to the issue from XML to HTML namespace. I'm not sure this would have a lot of impact, cause it inherits from a regular element.

In other news, I've been wrapping up the implementation work for the remaining features I wanted to add to ext-dom in PHP 8.4.

Cool, great work. I'm sure your work here will be viable in the long run!
I do have some last thing I am thinking on and off about for some while now, maybe I'dd just ask here:
Why do both XMLReader and XMLWriter don't support a regular resource stream (like fopen) as input / output target? It's kind off annoying that you need to e.g. write an xml resource stream to a file first before opening it or write to a file first and then do something with it. Would that be something that would be easy to add to e.g. PHP 8.4? (Maybe disputable since they are trying to move away from resources for the past years)
To be clear, I don't want to add more work for you to the table since you are already doing so much. Let me know if I can help with anything.

@nielsdos Thanks for the review on the static analysis part. I was able to get it all covered now.

Awesome! :tada:

If I understand the problem correctly, then it's about some kind of transition from HTMLElement to regular Element and the other way around?

Indeed

This means that wether it returns a HTMLElement is based on a namespace URI like http://www.w3.org/1999/xhtml?

Yes

There are some ways to look at this:
Would renaming an HTML element be something someone wants to do in PHP context? I guess it will probably be a rather limited approach. Renaming the namespace there would most likely be many bridges too far.
Renaming an XML element into a HTML element would most likely also be an operation that would hardly ever happen. I can imagine a scenario where you want to add something that looks like HTML to XML, but it won't really be HTML compliant I suppose.

You are right about both these things: these are strange things to do. However, users have always managed to surprise me :-)
I agree with your conclusions about the provided workarounds.

Leave rename() out. Also an easy solution but would be annoying for developers...

You mean leave it out of the HTMLElement class? This might be confusing since you are extending the regular Element and it would be there and throw an exception. It is still needed in regular Element though for various operations you can find in this repository, so not having it would be kinda blocking.

Yes, leave it out for HTMLElement for example. I think you're right this is strange though.
Or leave the rename method out entirely... What also crossed my mind is that rename is also incompatible if we ever want to make something like the registerNodeClass function such that you could register custom Element classes (e.g. being able to do registerElementClass('xhtml namespace', 'body', MyBodyElement::class).

Maybe some other ideas:
Add a hard block on renaming cross node-types by throwing an exception? It can be done by checking the source and target namespace I suppose. Since this is an operation that wouldn't or shouldnt happen in many scenarios, it might be a sensible thing to do?
Limiting the rename() method on the HTMLElement so that you cannot change namespaces. This would still lead to the issue from XML to HTML namespace. I'm not sure this would have a lot of impact, cause it inherits from a regular element.

These seem like sensible solutions, I'm not sure though on how well this generalises and how well this would work for potential future DOM APIs (e.g. the registerElementClass example from earlier).

Why do both XMLReader and XMLWriter don't support a regular resource stream (like fopen) as input / output target?

I don't know, ask my predecessors :-) It should not be hard to add though. I found two feature requests about this: https://bugs.php.net/bug.php?id=46146 and https://bugs.php.net/bug.php?id=63506

It's kind off annoying that you need to e.g. write an xml resource stream to a file first before opening it or write to a file first and then do something with it. Would that be something that would be easy to add to e.g. PHP 8.4?

I easily see the use case for XMLWriter, it's often the case that XML is embedded into something, and with XMLWriter being stream-oriented it makes perfect sense to have an openStream method. I'll look into this, stay tuned ;)
As for XMLReader, I find it harder to see the use case. You can use XMLReader::open and read from any uri (even from custom stream wrappers). Can you give me a concrete use case for XMLReader? A concrete use case can also help if I need to draft an RFC text.

(Maybe disputable since they are trying to move away from resources for the past years)

Well, using existing resource types is fine, introducing new resource types is not. The stream resource will stay with us for a some time anyway.

Yes, leave it out for HTMLElement for example. I think you're right this is strange though. Or leave the rename method out entirely... What also crossed my mind is that rename is also incompatible if we ever want to make something like the registerNodeClass function such that you could register custom Element classes (e.g. being able to do registerElementClass('xhtml namespace', 'body', MyBodyElement::class).

What would be the benifit of having a registerElementClass? As-in : what does it solve? It makes things complexer and I can't think of a good reason to do so.

I was thinking about hypothetical future additions that could cause problems. registerElementClass was once suggested on the mailing list so that's why I brought it up. But you may be right that this is thinking about problems that don't exist.
I'm just a bit scared of implementing APIs that will bite me in my ass later on when implementing other features.

There are 2-3 ways to go in this case :
* Either accept that the node-type can change when performing these operations based on the XMl / HTML rules or the customly registered classes.

* Or Don't allow cross-node renames (which is basically what I proposed earlier)

* Don't to renaming at all (which is kind off a blocker)

The first two bullet points are the most sensible in my opinion. I'll have another think about it. I'll also discuss this internally a bit more.
I don't want to get rid of renaming because it's a handy feature.

I easily see the use case for XMLWriter, it's often the case that XML is embedded into something, and with XMLWriter being stream-oriented it makes perfect sense to have an openStream method. I'll look into this, stay tuned ;)

Nice :)

Please see https://github.com/nielsdos/php-src/pull/106
This implements a new method XMLWriter::openStream(resource $stream). It takes an open stream and writes its data to it.
When implementing this I dug into the libxml APIs and found that the underlying API allows setting a character encoding. So it's possible to extend the function signature to this: XMLWriter::openStream(resource $stream, ?string $encoding) where you could set a particular character encoding via the optional $encoding argument. I think it's sensible to add that encoding argument, and maybe even for the other 2 open methods (i.e. openUri and openMemory) too? Please let me know what you think.

As for XMLReader, I find it harder to see the use case. You can use XMLReader::open and read from any uri (even from custom stream wrappers). Can you give me a concrete use case for XMLReader? A concrete use case can also help if I need to draft an RFC text.

For example XML responses in HTTP Responses: An HTTP response you receive over an already opened up resource stream contains XML. Now you first need to write this stream to a file before you can use XMLReade from a file. Afterwards you need to make sure to remove that file. Those are some steps too far to me, not to mention the I/O overhead.
Even in PSR-7, you could use a StreamWrapper to make sure you don't have to write to a file before reading this stream.
It would be nice if one could just XMLReader::openStream($httpResponseStream);

Yeah okay that makes perfect sense, thanks.
I'd model it after https://www.php.net/manual/en/xmlreader.open.php though, so XMLReader::openStream(resource $stream, ?string $encoding = null, int $flags = 0). Let me know what you think.

Please see nielsdos/php-src#106 This implements a new method XMLWriter::openStream(resource $stream). It takes an open stream and writes its data to it.

Wow that was fast 😮

When implementing this I dug into the libxml APIs and found that the underlying API allows setting a character encoding. So it's possible to extend the function signature to this: XMLWriter::openStream(resource $stream, ?string $encoding) where you could set a particular character encoding via the optional $encoding argument. I think it's sensible to add that encoding argument, and maybe even for the other 2 open methods (i.e. openUri and openMemory) too? Please let me know what you think.

Sure makes sense to add it. There is no option to do so at this moment, so makes sense!

Yeah okay that makes perfect sense, thanks. I'd model it after https://www.php.net/manual/en/xmlreader.open.php though, so XMLReader::openStream(resource $stream, ?string $encoding = null, int $flags = 0). Let me know what you think.

That would indeed be a good API. I notice from my library, I did not implement encoding and flags - so might need to do that here as well. Maybe I'll also create some kind of libxml flag builder someday, cause those are confusing me everytime I look at them :)

FWIW, after discussion internally about rename we decided the best option would be to disallow cross-node renames, which is what you suggested earlier. I.e. if (namespaceURI is the HTML namespace || node is in the HTML namespace) { the namespace must be the HTML namespace for both namespaceURI and the node, otherwise we throw }
For XMLReader & XMLWriter, I can do a short RFC for this. I'll work on adding the encoding parameter too, it makes me wonder what the encoding is it uses right now actually or if it does some kind of autodetect... Of course the libxml docs aren't really helping here...

Maybe I'll also create some kind of libxml flag builder someday, cause those are confusing me everytime I look at them :)

The options aren't always amazingly named. E.g. LIBXML_NOENT is my "favourite" one because people often think it stands for "NO ENtity substitution", but it does the opposite :-(

FWIW, I made a draft RFC for the XMLReader&Writer openStream function: https://wiki.php.net/rfc/xmlreader_writer_streams. I'm sharing this with a few people and if nothing comes up I'll post it to the mailing list tomorrow evening or on Tuesday or so, I'll see.
In the end I decided to keep the signatures for XMLWriter the same and not add the $encoding argument to openStream() because XMLWriter::startDocument() already has an encoding argument and it is handled nicely there.

@nielsdos nice! Let's hope for a smooth acceptance path then :)

authors: nielsdos veewee

repo: veewee/xml


text:
Dedicated transfer page

Story
As a user
I want a simplified dedicated transfer page
So that I can easily be linked to transfers from other apps
Acceptance Criteria

[x] I can transfer on /transfer
[x] I can transfer with a preselected asset at /transfer?assetId=xyz

Tasks

[x] UX (if needed)
[x] Design (if needed)
[ ] Team and stakeholder review
[x] Specs reviewed and created or adjusted
[x] Implementation
[x] Testing (unit and/or e2e)
[x] Code review
[x] QA review

Sketch
Additional details / background info

@macqbat Can we make the asset box to match vega key and amount when no asset has been selected?

@macqbat, @mattrussell36 Can we make the asset box to match vega key and amount when no asset has been selected?

this has been done in the last commit

@macqbat All looks good to me.
Is this going through a team review or can we move to closed?

authors: bwallacee macqbat mattrussell36

repo: vegaprotocol/frontend-monorepo


text:
sortable headers break filters in FF & edge

sortable headers break filters in FF & edge

fixed in local copy

repo: vegarringdal/aureliaGrid


text:
Modify MicArray Application to use keyboard input to adjust beamforming

Modify Mic Array Beamforming application to use Left and Right arrow keys to adjust the pickup angle of the beamforming algorithm.
DoD: Pressing the left arrow will steer the beamforming angle to the left, pressing right arrow key will steer beamforming angle to the right. Can be controlled with keyboard with terminal printing teh DOA.

Mic Application:
https://github.com/velascorhwee/final-project-assignment-micarray/tree/sprint-2-issue-10and11
Implemented a rough delay sum algorithm that can be controlled with the keyboard using the 'a' and 'd' keys.
The 'w' and 's' keys control the gain.


text:
JSON格式识别不出来

Description
JSON字符串 格式识别不出来
[{"enquiryorderdetailid":17233,"name":"柴油滤清器","list":[{"quotationdetailid":11174,"mid":2228,"refiorder":17233,"refdecode":0,"prodid":3569244,"code":"1000335797","name":"柴油滤清器","brandname":"板東","defaultimage":"","finalprice":12.000000,"qty":1.000000,"fqtys":0.0,"customremark":"","fitcarname":"AC Schnitzer X5 2011款 3.0T AT ACS5 35i(N55B30,8AT)","addressname":"NGK","spec":"","featurecodes":"","oenumber":"","drawingno":"4F0254800G","typename":"","prodkey":"4986625F84290FE1"}]},{"enquiryorderdetailid":17234,"name":"滤清器","list":[{"quotationdetailid":11175,"mid":2228,"refiorder":17234,"refdecode":0,"prodid":3569244,"code":"1000335797","name":"柴油滤清器","brandname":"板東","defaultimage":"","finalprice":12.000000,"qty":1.000000,"fqtys":0.0,"customremark":"","fitcarname":"AC Schnitzer X5 2011款 3.0T AT ACS5 35i(N55B30,8AT)","addressname":"NGK","spec":"","featurecodes":"","oenumber":"","drawingno":"4F0254800G","typename":"","prodkey":"4986625F84290FE1"}]}]
Steps To Reproduce

Expected behavior
[
{
"enquiryorderdetailid":17233,
"name":"柴油滤清器",
"list":[
{
"quotationdetailid":11174,
"mid":2228,
"refiorder":17233,
"refdecode":0,
"prodid":3569244,
"code":"1000335797",
"name":"柴油滤清器",
"brandname":"板東",
"defaultimage":"",
"finalprice":12,
"qty":1,
"fqtys":0,
"customremark":"",
"fitcarname":"AC Schnitzer X5 2011款 3.0T AT ACS5 35i(N55B30,8AT)",
"addressname":"NGK",
"spec":"",
"featurecodes":"",
"oenumber":"",
"drawingno":"4F0254800G",
"typename":"",
"prodkey":"4986625F84290FE1"
}
]
},
{
"enquiryorderdetailid":17234,
"name":"滤清器",
"list":[
{
"quotationdetailid":11175,
"mid":2228,
"refiorder":17234,
"refdecode":0,
"prodid":3569244,
"code":"1000335797",
"name":"柴油滤清器",
"brandname":"板東",
"defaultimage":"",
"finalprice":12,
"qty":1,
"fqtys":0,
"customremark":"",
"fitcarname":"AC Schnitzer X5 2011款 3.0T AT ACS5 35i(N55B30,8AT)",
"addressname":"NGK",
"spec":"",
"featurecodes":"",
"oenumber":"",
"drawingno":"4F0254800G",
"typename":"",
"prodkey":"4986625F84290FE1"
}
]
}
]
DevToys Version
版本 1.0.9.0 | X64 | RELEASE | 8bcfa60 | 8bcfa60
Relevant Assets/Logs
Error reading JObject from JsonReader. Current JsonReader item is not an object: StartArray. Path '', line 1, position 1.

已经解决了，更新到1.0.10.0

authors: hinnuryuu xinhaiyang

repo: veler/DevToys


text:
kotlin当中不显示。

我写了Java和Kotlin两个版本
使用相同的数据和相同的adapte
但是kotlin的版本不显示数据
代码和截图如下
`class CUQuickEditPopup(mContext: Context) : Dialog(mContext) {
init {
    val builder = AlertDialog.Builder(context)
    val view = layoutInflater.inflate(R.layout.pop_up_wheel_view, null)
    val iconWheelView = WheelView<Pair<String, Pair<Int, Int>>>(context)
    iconWheelView.setWheelAdapter(ArrayWheelIconAdapter(context))
    iconWheelView.skin = WheelView.Skin.Holo
    iconWheelView.setWheelData(iconItems)
    val timeWheelView = WheelView<String>(context)
    timeWheelView.setWheelAdapter(ArrayWheelTimeAdapter(context))
    timeWheelView.skin = WheelView.Skin.Holo
    timeWheelView.setWheelData(timeItems)
    val typeWheelView = WheelView<Pair<String, Int>>(context)
    typeWheelView.setWheelAdapter(ArrayWheelTypeAdapter(context))
    typeWheelView.skin = WheelView.Skin.Holo
    typeWheelView.setWheelData(typeItems)
    builder.setView(view)
    builder.create().show()
}

companion object {
    @JvmStatic
    val typeItems = arrayListOf("call allowed" to com.hyphenate.easeui.R.string.call_allowed,
            "text allowed" to com.hyphenate.easeui.R.string.text_allowed,
            "do not disturb" to com.hyphenate.easeui.R.string.do_not_disturb)

    @JvmStatic
    val timeItems = arrayListOf("0.5 ", "1 ", "1.5 ", "2 ", "2.5 ", "3 ")

    @JvmStatic
    val iconItems = arrayListOf(
            "meeting" to Pair(R.string.meeting, R.drawable.ease_blue_add),
            "work" to Pair(R.string.work, R.drawable.ease_blue_add),
            "study" to Pair(R.string.study, R.drawable.ease_blue_add),
            "social" to Pair(R.string.social, R.drawable.ease_blue_add),
            "meal" to Pair(R.string.meal, R.drawable.ease_blue_add),
            "entertainment" to Pair(R.string.entertainment, R.drawable.ease_blue_add))
}

}
`
`public class CUQuickEditPopupJava extends Dialog {
public CUQuickEditPopupJava(@NonNull Context context) {
    super(context);
    AlertDialog.Builder builder = new AlertDialog.Builder(context);
    View view = getLayoutInflater().inflate(R.layout.pop_up_wheel_view, null);

    WheelView iconWheelView = view.findViewById(R.id.iconWheelView);
    iconWheelView.setWheelAdapter(new ArrayWheelIconAdapter(context));
    iconWheelView.setWheelData(CUQuickEditPopup.getIconItems());

    WheelView timeWheelView = view.findViewById(R.id.timeWheelView);
    timeWheelView.setWheelAdapter(new ArrayWheelTimeAdapter(context));
    timeWheelView.setWheelData(CUQuickEditPopup.getTimeItems());

    WheelView typeWheelView = view.findViewById(R.id.typeWheelView);
    typeWheelView.setWheelAdapter(new ArrayWheelTypeAdapter(context));
    typeWheelView.setWheelData(CUQuickEditPopup.getTypeItems());

    builder.setView(view);
    builder.create().show();
}

}
`

不显示

Java版本

这一块抽出来想用kotlin写，发现不显示。
调试发现adapter的getview方法没有调用。bindview也就没法填充布局了。
用Java写的就没这个问题。

repo: venshine/WheelView


text:
ClassLoaderUtil.getResourceAsStream(String, Class<?>) 方法可以删除

ClassLoaderUtil.getResourceAsStream(String, Class<?>) 方法可以删除

暂时保留着吧
目前修改 调用了 #481

repo: venusdrogon/feilong-core


text:
Hello, could you release a subscription package based on Appwrite with Next.js and Stripe?

I find that Appwrite is more outstanding and flexible in terms of self-hosting compared to Supabase.
thank you !

Not sure about that....I think the local/remote Supabase integration in this repo is very easy to manage either locally or using a remote Supabase instance. What makes Appwrite more outstanding or flexible? I don't see any benchmarks or outputs to suggest the latter.

repo: vercel/nextjs-subscription-payments


text:
[turborepo] [eslint-plugin-turbo] eslint-pugin-turbo can't read jsonc turbo.json

What version of Turborepo are you using?
v1.8.2
What package manager are you using / does the bug impact?
npm
What operating system are you using?
Mac
Describe the Bug
As per https://github.com/vercel/turbo/pull/3812, turbo.json can contain comments.
However, eslint-pugin-turbo has a rule turbo/no-undeclared-env-vars which attempts to find and read a turbo.json (to find env vars Turbo is aware of) with JSON.parse, which breaks with comments.
Expected Behavior
eslint-plugin-turbo can handle turbo.json files with comments.
To Reproduce
Follow turbo setup instructions
Add a comment to your turbo.json, e.g.
// this is a comment
{
  "$schema": "https://turbo.build/schema.json",
  "pipeline": {
  },
}

Run npx turbo lint
Reproduction Repo
No response

Looking through the source code to try to fix this, it seems like @tknickman has already made the necessary code changes in https://github.com/vercel/turbo/pull/3846/files#diff-5e060cf84306ac1371af2dda2a506b709e04c0a4b6a11f43df6399b0fceee5cfR62
Looks like it might need a release of eslint-plugin-turbo to get this completed though.

Hey @domdomegg, thanks for the repot. I'm taking a look at this, we should def support reading with jsonc in the plugin

authors: domdomegg tknickman

repo: vercel/turbo


text:
Target via synthesized task

What if we implemented targets by doing it as a synthesized volatile task which inserts itself as a dependency in the correct places?

Can we implement this without putting it into the UI as a task (graph, dry run, etc.) and without needing to add the concept of volatile tasks?

authors: gsoltis nathanhammond


text:
dev script of ui package in example with rollup

By running the dev script "pnpm run build -- --watch", it failed with error message of "RollupError: Could not resolve entry module "--watch". ". Replaced the script with "pnpm build --watch"
Description
I ran npx create-turbo@latest -e with-rollup and when I wanted to run pnpm dev, faced the error RollupError: Could not resolve entry module "--watch". .
The error was fixed by replacing pnpm run build -- --watch by  pnpm build --watch
Testing Instructions
To test the changes, making changes in @repo/ui should be watched and result in building the package, and also running pnpm dev should work without any errors.

Allow CI Workflow Run

[ ] approve CI run for commit: f4f66255fd368f4f36f0ad475c8d17bccc406f38

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer


text:
Macbook Pro 2014 - Synchronizing with network takes Forever.

Hey Guys,
I am new to use the Verge wallet. Before i realized that the wallet is not synchronizing, I told a friend of mine to send my verge coins to the address that was provided in the wallet. My first guestion is, why does it take forever for the walet to synchronize with the network and how can I solve the problem? Secondly, will i get my coins once the wallet will be synchronized or I lost them? Please help me out.
Thank you very much!

I've been synchronizing for 2 weeks and I'm only 6% done through tor takes forever
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: sahh97 notifications@github.com Date: 10/12/18  1:48 AM  (GMT-05:00) To: vergecurrency/VERGE VERGE@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [vergecurrency/VERGE] Macbook Pro 2014 - Synchronizing with network takes Forever. (#813)
Hey Guys,
I am new to use the Verge wallet. Before i realized that the wallet is not synchronizing, I told a friend of mine to send my verge coins to the address that was provided in the wallet. My first guestion is, why does it take forever for the walet to synchronize with the network and how can I solve the problem? Secondly, will i get my coins once the wallet will be synchronized or I lost them? Please help me out.
Thank you very much!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/vergecurrency/VERGE","title":"vergecurrency/VERGE","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/vergecurrency/VERGE"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Macbook Pro 2014 - Synchronizing with network takes Forever. (#813)"}],"action":{"name":"View Issue","url":"https://github.com/vergecurrency/VERGE/issues/813"}}}
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/vergecurrency/VERGE/issues/813",
"url": "https://github.com/vergecurrency/VERGE/issues/813",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
},
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "Macbook Pro 2014 - Synchronizing with network takes Forever. (#813)",
"sections": [
{
"text": "",
"activityTitle": "sahh97",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@sahh97",
"facts": [
{
"name": "Repository: ",
"value": "vergecurrency/VERGE"
},
{
"name": "Issue #: ",
"value": 813
}
]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "IssueComment",\n"repositoryFullName": "vergecurrency/VERGE",\n"issueId": 813,\n"IssueComment": "{{IssueComment.value}}"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "IssueClose",\n"repositoryFullName": "vergecurrency/VERGE",\n"issueId": 813\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/vergecurrency/VERGE/issues/813"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "MuteNotification",\n"threadId": 392384894\n}"
}
],
"themeColor": "26292E"
}
]

@sahh97 shouldnt take more than a day or two, but you can download the blockchain instead. and yes, your coins will show up when its complete

Leaving this as a future reference: https://verge.zendesk.com/hc/en-us/articles/360015942312-Syncing-is-slow-stuck-will-take-forever

repo: vergecurrency/VERGE


text:
[VIP-1] Upcoming fork brainstorming

upcoming fork shall include:

#904 new halving schedule including 7 new periods
~#969 Difficulty and Proof of Work check adjustments~

further ideas:

Maybe removing old mining signatures of blocks
... feel free to add more topics for cleaning up the old v4 base ...

Halving will be done soon - closing for now :)


text:
Add travis and small cleanups

Fixes #1.

Disables the -W flags on the bison generated files which cause warnings on newer versions of GCC / clang.
Add very simple Travis build.

@kmurray If this makes sense, I will also send the same type of pull request for libsdfparse and libblifparse libraries too.

@mithro, @kmurray  : sorry, wasn't watching for PRs on this repo.  Is the -W on bison generated still needed or has that been dealt with elsewhere?

authors: mithro vaughnbetz

repo: verilog-to-routing/libsdcparse


text:
[Bug] 无论redir-host还是fake-ip模式，开启后本地网络手机的多个翻墙软件节点不通，请教...

Verify Steps

[X] Tracker 我已经在 Issue Tracker 中找过我要提出的问题
[X] Latest 我已经使用最新 Dev 版本测试过，问题依旧存在
[X] Core 这是 OpenClash 存在的问题，并非我所使用的 Clash 或 Meta 等内核的特定问题
[X] Meaningful 我提交的不是无意义的 催促更新或修复 请求

OpenClash Version
v0.45.129-beta
Bug on Environment
Official OpenWrt
Bug on Platform
Linux-amd64(x86-64)
To Reproduce
无论redir-host还是fake-ip模式，开启openclash后本地网络手机v2rayNG、Clash meat、Clash全部节点不通，关闭路由openclash节点正常使用。日志太长上传了几个设置界面截图供参考。
Describe the Bug
单设备主路由，AD接管dnsmasq，上游dns留唯一地址指向openclash7874端口，生效后无论使用edir-host还是fake-ip模式，局域网手机v2rayNG测试真连接延迟全部节点均显示-1ms不通，手机更换clash meta和原版clash，节点均不通；关闭opclash，adg上游dns填任意服务器地址，开机手机软件各节点正常；尝试排除法换路由使用passwall，手机节点正常。隐约感觉是dns的问题，但不知修改哪个选项来解决，烦请热心人帮助，谢谢！提交issue较少，如有不规范请谅解。
OpenClash Log

OpenClash Config
No response
Expected Behavior
无。
Screenshots
No response

不通是测试节点连通性不通，可能走了两次代理，你可以设置绕过手机ip或者让手机连接路由器时停用自身代理软件

不通是测试节点连通性不通，可能走了两次代理，你可以设置绕过手机ip或者让手机连接路由器时停用自身代理软件

由于使用习惯的问题,通常在家庭局域网中也习惯不关手机代理软件,是因为opclash的短间隔更新订阅功能,想要换过来用一下; 所以关闭手机代理的情况下应当是可以的因为节点在路由的opwrt代理组件内正常... 只是不明白为什么别passwall运行时手机代理也正常使用且设备优先而opclash运行时手机上的节点就不通了，所以求助看是哪里设置问题

跟规则有关系的，那些代理地址设置成直连应该就可以了

repo: vernesong/OpenClash


text:
OpenClash v0.39.6-beta 和 Clash 1.0.0 版本 IPv6 配置适配问题

新版本增加了一个配置项 ipv6，和之前的 dns.ipv6 有差别。新配置结构如下：
ipv6: false

dns:
  ipv6: false

目前 OpenClash 好像会把两个等同一个，没有分开做开关。全局设置里关掉 IPv6 DNS，ipv6 和 dns.ipv6 都会设置为 false。

分开来不好理解，统一管理

按照我的文档的理解，这两个配置应该是控制不同行为的：
ipv6 是控制 clash dial 的时候是不是同时发起 ipv4 和 ipv6 的请求。在 Fake IP 模式下应该可以支持直连访问 ipv6 资源和 ipv6 的节点。
dns.ipv6 是控制 clash redir-host 模式下是否返回 AAAA 的解析结果。
我的目标是使用 Fake IP 模式访问只有 IPv6 单栈的资源，不知道能否实现。目前如果打开 ipv6，同时使用 redir-host 模式（DHCPv6 开启，内网所有设备均有公网 IPv6 地址），访问内外网络都会有点慢，Chrome 还会偶有访问失败再刷新正常和 Github issue 页头像部分不显示的问题。
如理解有误，敬请指教，谢谢。

@jakeslee 同样想要 1 的效果，如果有方法了麻烦告诉我，非常感谢！

看不懂，更新OC时路过，过来拜访一下大佬

authors: jakeslee qq775818258-01-jakeslee-is-fool smallst vernesong


text:
MultiMap is overriding my entries

The fact that the index is calculated like this (in CaseInsensitiveHeaders), it overrides my entries.
private static int index(int hash) {
        return hash % 17;
}

It is intended to not allow you to have more than 17 entries and override them?
If so, could you please let me know what can I use instead?

@TatianaBuica did you find a bug ? do you have a reproducer ?

When I am trying to make the following insert into a MultiMap, keys doorsUser and encryptionAlgorithm are always fighting for index 4.
MultiMap form = MultiMap.caseInsensitiveMultiMap();
form.add("doorsUser", "aa");
form.add("encryptionAlgorithm", "");

The fact that the index is calculated as I mentioned above, it is a bit confusing and I am not sure if this is a bug.

is there a bug ? i.e is data overwritten when you use the MultiMap ?
it's expected to have collision inside the implementation, that's how hash tables work https://en.wikipedia.org/wiki/Hash_table#Collision_resolution

I ran the code you provided:
  public static void main(String[] args) {
    MultiMap form = MultiMap.caseInsensitiveMultiMap();
    form.add("doorsUser", "aa");
    form.add("encryptionAlgorithm", "");
    for (Object o : form) {
      System.out.println("o = " + o);
    }
    System.out.println("doorsUser=" + form.get("doorsUser"));
    System.out.println("encryptionAlgorithm=" + form.get("encryptionAlgorithm"));
  }

and I got
o = doorsUser=aa
o = encryptionAlgorithm=
doorsUser=aa
encryptionAlgorithm=

authors: TatianaBuica vietj


text:
no transaction found on vtc network

I made a transaction from electrum wallet to ledger nano s, but my transaction has not been confirmed and the vtc network does not see it. I tried to deduce 12.94 vtc with the commission of 0.005vtc. help with this transaction: 24b25f5122b09fa07b5c53a3e7da81682275a3daef5ddba4501fa5687b65dbe4

This is a problem with Ledger, not Vertcoin. You will need to contact them to figure out what went wrong on their end with the transaction.

repo: vertcoin/electrum-vtc


text:
anyone get ApexCharts to render in PDF? i get blank

Anyone get ApexCharts to render in PDF? In a regular view, the chart renders fine, but in a PDF I get blank.
Thanks.

Separately, narrowed down an issue that had me going at first.
Blade template tags in the view seem to cause issues. Using for example {{ asset('js/app.js') }} causes an error. Even though it's a bare bones view.
Error:
TimeoutError: Navigation timeout of 30000 ms exceeded

Can confirm. Issue is still present. Even a simple css {{ asset('css/app.css') }} will lead to timeout.

Ok. Played around with things a bit and had the same issue of timeout of 30000 ms when try to convert a view on Localhost. I was running it via php artisan serve. After playing around on a new Laravel project I narrowed it down to the use of a specific blade command.
 <link href="{{ asset('css/app.css') }}" rel="stylesheet">
The issue seems to be that puppeteer is not handling local network requests. For now I have gotten it to work as follows:
@env('local')
      @php
            echo '<style>' . file_get_contents(realpath(public_path('css/app.css'))) . '</style>';
      @endphp
@endenv
@env(['staging', 'production'])
    <link href="{{ asset('css/app.css') }}" rel="stylesheet">
@endenv

The above works without a hitch. So something is up with localhost uri resources in puppeteer.

repo: verumconsilium/laravel-browsershot


text:
Cross-compiling ring v0.17.8 dependency fails

verus-analyzer (on the upcoming infra branch) uses verusfmt as a library.  When the (very complex) GitHub action runs to generate a release of verus-analyzer, one of the commands executed is:
$ cargo build --manifest-path ./crates/rust-analyzer/Cargo.toml --bin rust-analyzer --target aarch64-unknown-linux-gnu --release

This eventually fails with:
   Compiling ring v0.17.8
   Compiling ra-ap-rustc_index_macros v0.53.0
   Compiling futures-core v0.3.30
   Compiling profile v0.0.0 (/home/runner/work/verus-analyzer/verus-analyzer/crates/profile)
   Compiling chalk-derive v0.97.0
   Compiling ra-ap-rustc_index v0.53.0
The following warnings were emitted during compilation:

warning: ring@0.17.8: In file included from crypto/curve25519/curve25519.c:22:
warning: ring@0.17.8: In file included from include/ring-core/mem.h:60:
warning: ring@0.17.8: In file included from include/ring-core/base.h:64:
warning: ring@0.17.8: In file included from /usr/lib/llvm-11/lib/clang/11.0.0/include/stdint.h:52:
warning: ring@0.17.8: /usr/include/stdint.h:26:10: fatal error: 'bits/libc-header-start.h' file not found
warning: ring@0.17.8: #include <bits/libc-header-start.h>
warning: ring@0.17.8:          ^~~~~~~~~~~~~~~~~~~~~~~~~~
warning: ring@0.17.8: 1 error generated.

error: failed to run custom build command for `ring v0.17.8`

Running cargo tree seems to point the finger at verusfmt, in so far as it's the only package that uses ring.  Here's a simplified version of the relevant output (with arrows added for emphasis):
│   └── verusfmt v0.4.0
│       ├── axoupdater v0.6.9
│       │   ├── axoasset v1.0.0
│       │   │   ├── reqwest v0.12.5
│       │   │   │   ├── hyper-rustls v0.27.2
│       │   │   │   │   ├── futures-util v0.3.30 (*)
│       │   │   │   │   ├── http v1.1.0 (*)
│       │   │   │   │   ├── rustls v0.23.12
│       │   │   │   │   │   ├── once_cell v1.19.0
│       │   │   │   │   │   ├── ring v0.17.8                             <----
│       │   │   │   │   │   │   ├── cfg-if v1.0.0
│       │   │   │   │   │   │   ├── getrandom v0.2.15 (*)
│       │   │   │   │   │   │   ├── spin v0.9.8
│       │   │   │   │   │   │   └── untrusted v0.9.0
│       │   │   │   │   │   │   [build-dependencies]
│       │   │   │   │   │   │   └── cc v1.0.97
│       │   │   │   │   │   ├── rustls-pki-types v1.7.0
│       │   │   │   │   │   ├── rustls-webpki v0.102.6
│       │   │   │   │   │   │   ├── ring v0.17.8 (*)                     <----
│       │   │   │   │   │   │   ├── rustls-pki-types v1.7.0
│       │   │   │   │   │   │   └── untrusted v0.9.0
│       │   │   │   │   │   ├── subtle v2.6.1
│       │   │   │   │   │   └── zeroize v1.8.1

Can we address this by bumping a version on one of these packages?  Or by updating Cargo.toml, so that the library version doesn't depend on axoupdater (which seems unnecessary for the library)?

This can likely be fixed by adding the correct apt install libc6-arm64-cross or similar to the GH action, but I do agree that axoupdater is only necessary for the binary, and not the library, thus #109, allowing one to disable it out.  I don't think the solutions in the above "updating Cargo.toml link are ideal for our use case, so I've opted to simply make it into an optional dependency that can be disabled.
You should be able to test it temporarily using a git dependency, by specifying a branch to test and ensure that #109 works for this, before accepting the PR to be merged.

authors: jaybosamiya parno

repo: verus-lang/verusfmt