text:
Explanation of outputs

For a comparative study we are writing we would like to include PGE among the algorithms. We were able to run it successfully but we are not sure how to obtain the results. We noticed a file output/<experiment>/<.yaml file>/clean/<dataset>/out/pge_final.log which probably contains the final model(s). Is that correct? Are all the models in that file members of the final Pareto-front? If not, is it possible to extract it from the list (perheaps using IDs but I don't know)?

To be honest, it's been 4 years since I looked at this project. Might be easier to get on a video share. Is the email in your GitHub profile a good one to use for setting that up?
check out this PR too: https://github.com/verdverm/pypge/pull/9

When you get it working please do a pull request. Thx

It does work, see the latest open PR. When you get your work published for
real, let me know.
I could add an n-ary tree tutorial if you like since it's complex. You
might find one in the SymPy library we both used. If you need a reference
to understand set reduction and why you don't need to prove with data and
benchmarks, I'd be happy to help you find one.
On Tue, Nov 26, 2019, 3:04 PM sohrabtowfighi notifications@github.com
wrote:

When you get it working please do a pull request. Thx
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/verdverm/pypge/issues/12?email_source=notifications&email_token=AAKTQCH7ZFWVQAWDFMX6IHTQVWMO7A5CNFSM4JR2AQN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFHS4BA#issuecomment-558837252,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKTQCBBGL6MMN44MLBLKFTQVWMO7ANCNFSM4JR2AQNQ
.

Go for it. Paper is accepted to SN Applied Sciences. I will review PR after work at the hospital. Thx.

Ah, Korn's style publishing in Springer books lacking real peer review from
those in the field. Congrats!
On Tue, Nov 26, 2019, 3:17 PM sohrabtowfighi notifications@github.com
wrote:

Go for it. Paper is accepted to SN Applied Sciences. I will review PR
after work at the hospital. Thx.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/verdverm/pypge/issues/12?email_source=notifications&email_token=AAKTQCBB7GNY5CID7XSG7X3QVWOBLA5CNFSM4JR2AQN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFHT57Y#issuecomment-558841599,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKTQCHQ5ALH3HPGSP5MG6LQVWOBLANCNFSM4JR2AQNQ
.

GECCO is the place to submit
http://www.wikicfp.com/cfp/program?id=1121
Submissions are due in February
On Tue, Nov 26, 2019, 3:24 PM Tony Worm tony@hofstadter.io wrote:

Ah, Korn's style publishing in Springer books lacking real peer review
from those in the field. Congrats!
On Tue, Nov 26, 2019, 3:17 PM sohrabtowfighi notifications@github.com
wrote:

Go for it. Paper is accepted to SN Applied Sciences. I will review PR
after work at the hospital. Thx.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/verdverm/pypge/issues/12?email_source=notifications&email_token=AAKTQCBB7GNY5CID7XSG7X3QVWOBLA5CNFSM4JR2AQN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFHT57Y#issuecomment-558841599,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKTQCHQ5ALH3HPGSP5MG6LQVWOBLANCNFSM4JR2AQNQ
.

Maybe for my 2nd paper. Why are you still upset with me? I've moved on and so should you. Also idunno what Korn publishing is. Sn applied sciences is peer reviewed journal, not a book.

Korn's is a shitty GP researcher who claims to beat everyone without every
releasing code or data. He only publishes in Springer and not the leading
conferences for the field.
You misrepresented my work and took a few stabs at me in your paper. Would
you be upset if someone did this to you?
Dr. Tony Worm
CEO, Founder
Hofstadter, Inc
https://hofstadter.io
https://meetings.hubspot.com/tony107
On Tue, Nov 26, 2019, 3:29 PM sohrabtowfighi notifications@github.com
wrote:

Maybe for my 2nd paper. Why are you still upset with me? I've moved on and
so should you. Also idunno what Korn publishing is. Sn applied sciences is
peer reviewed journal, not a book.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/verdverm/pypge/issues/12?email_source=notifications&email_token=AAKTQCG7R6X4VRTRMGS4SBLQVWPL5A5CNFSM4JR2AQN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFHU3CY#issuecomment-558845323,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKTQCFWQUDDNPGEDIDSHUDQVWPL5ANCNFSM4JR2AQNQ
.

SN Applied Science is another low quality, citation pumping, money
extracting example of the problems in academic research. That's why a large
number of us went to industry, where real accountability happens.
Dr. Tony Worm
CEO, Founder
Hofstadter, Inc
https://hofstadter.io
https://meetings.hubspot.com/tony107
On Tue, Nov 26, 2019, 3:32 PM Tony Worm tony@hofstadter.io wrote:

Korn's is a shitty GP researcher who claims to beat everyone without every
releasing code or data. He only publishes in Springer and not the leading
conferences for the field.
You misrepresented my work and took a few stabs at me in your paper. Would
you be upset if someone did this to you?
Dr. Tony Worm
CEO, Founder
Hofstadter, Inc
https://hofstadter.io
https://meetings.hubspot.com/tony107
On Tue, Nov 26, 2019, 3:29 PM sohrabtowfighi notifications@github.com
wrote:

Maybe for my 2nd paper. Why are you still upset with me? I've moved on
and so should you. Also idunno what Korn publishing is. Sn applied sciences
is peer reviewed journal, not a book.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/verdverm/pypge/issues/12?email_source=notifications&email_token=AAKTQCG7R6X4VRTRMGS4SBLQVWPL5A5CNFSM4JR2AQN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFHU3CY#issuecomment-558845323,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKTQCFWQUDDNPGEDIDSHUDQVWPL5ANCNFSM4JR2AQNQ
.

I said your code was left in unusable state and I stand by that. This was evident by history of issues in this repo with researchers banging their head against the wall with your package.
Sn applied sciences is a new journal. They are likely low-moderate impact. I paid 0 dollars for publication as paper is not open access.
Congrats on your success in industry. I'm going away now.

authors: sohrabtowfighi verdverm zegkljan

repo: verdverm/pypge


text:
[StorageNodeRegistry] Create contract.

Create a contract : https://github.com/verida/VIPs/pull/4

Let's expand the scope of this issue.

Expand StorageNodeInput to support numberSlots (integer) indicating how many storage slots the node will provide.
The number of tokens required to stake must be defined in a variable (STAKE_PER_SLOT). Only contract owner can change this variable. Initial value is 60 VDA tokens.
When addNode() is called, the requester must provide VDA tokens to stake. The number of staked tokens must be numberSlots * STAKE_PER_SLOT. The staked tokens should be registered against the storage node being registered.
When removeNode() is called, the staked tokens for that storage node should be released to the requester of this call.
Add a new method withdraw() allowing the requester to remove tokens for a given storage node. They must provide a signed request proving they control the private key of the storage node. If the STAKE_PER_SLOT goes down, then the storage node owner can withdraw excess tokens.
Add a new method deposit() allowing a storage node owner to add more tokens to a given storage node. They must provide a signed request proving they control the private key of the storage node. If the STAKE_PER_SLOT goes up, then the storage node owner can deposit additional tokens.

Note: We have not yet handled the scenario where STAKE_PER_SLOT is increased and storage node operators do not have enough tokens staked. This will be handled later. We will implement storage node operators earning a revenue from their nodes. They won't be able to earn revenue if they don't have enough tokens staked.

Add a new method deposit() ...
Here, I think, we don't need the provide the signed request. We can deposit the token amount from any requestor to that didAddress as following:

function depoistToken(address didAddress, uint tokenAmount) external;

Add a new method deposit() ...
Here, I think, we don't need the provide the signed request. We can deposit the token amount from any requestor to that didAddress as following:

function depoistToken(address didAddress, uint tokenAmount) external;

And this deposit() function will work for only the registered DIDs, correct?

Yes, correct.

source: gharchive/issue

repo: verida/blockchain-contracts

license_type: permissive

license_source: github-api


text:
tests: Add test vectors from Paul Miller's noble-curves

Paul Miller's noble-curves project provides different test vectors crysol should test again:

secp256k1 ECDSA signatures vectors
secp256k1 Point validity and de/encoding vectors

Note that .json files should be used, which can be injected either via forge's stdJson library or simple shell script using cast to abi-encode the vectors.

Made the first part with https://github.com/verklegarden/crysol/pull/32 for secp256k1 Point validity and de/encoding vectors.
For ECDSA it will be in an other PR.
From my understanding: to use the verify function from the ECDSA library, one would need to do some processing on vector values as it uses a scalar as a privateKey. Hence, one would need to get the SecretKey from the scalar d. For that it would require to have access to secretKeyFromUint from Secp256k1.

it would require to have access to secretKeyFromUint from Secp256k1.

Feel free to import the Secp256k1 library anywhere if necessary. 👍

After investigation, the encoding of nobles curves test vectors is different from Crysol / Ethereum.
The recovery bit is not serialized into the compact or der format (see small comment in README.md)
We can see that the signature from the test vectors are in compact format which is r and s packed only.
https://github.com/paulmillr/noble-curves/blob/1db569a52474ea94d6ec06fbe5321d17395ca255/test/secp256k1.test.js#L210
Hence:

For valid and invalid case sign, we could compare r and s from nobles cuves VS sk.signRaw but not sure this is relevant as it would only compare forge vs noble curves as the signature is done by the vm in ECDSAOffchain. They should be equal as they both use RFC6979 for deterministic ECDSA signatures.
For invalid case verify, the public key is provided and crysol expose a yparity function so something could be baked to compare results.

-> I will work on a PR for invalid case

Out of 2021 vectors, 3 do not lead the same Signature compared to foundry vm.sign for valid cases of nobles test vectors
// raw parsed signature //
0x7cb38cc5712e9e11a767615f6080dbc111c9cdd613eb98999fd92a86bafd45407923ca1f4d03471d2866f776ef8a6d3cac099b427331aeb245aa9dafeddcf115
  // signed ///
  r = 0x3f8fe493cf305a7f02b2d2c060ba66a8f7bd13a7a64d5200c0655ad069bd85b5
  s = 0x1cf94236c3857e33a1023a5216cbc81b1dc3adcc1c71f4212df1997ffdfb140a
  // expected ///
  r = 0x7cb38cc5712e9e11a767615f6080dbc111c9cdd613eb98999fd92a86bafd4540
  s = 0x7923ca1f4d03471d2866f776ef8a6d3cac099b427331aeb245aa9dafeddcf115

// raw parsed signature //
0xa7f83b5963eaf5332c633327cc967be8f4166d3f1e0b77f9761d8f4e42211e9a58aae31be1eb1e496923bbe8ca5e843cfb89f4d986d61d4edfd7d6fc3c9cf62c
  // signed ///
  r = 0x2d0b04a7560652f419e2542ea7d27f2c4afb0e111bb409cfe9f34b7ff7d33158
  s = 0x50118e90fcfe28abd0635a2e90f00db72bdbfcedbf56dad4049de85798031b38
  // expected ///
  r = 0xa7f83b5963eaf5332c633327cc967be8f4166d3f1e0b77f9761d8f4e42211e9a
  s = 0x58aae31be1eb1e496923bbe8ca5e843cfb89f4d986d61d4edfd7d6fc3c9cf62c

// raw parsed signature //
0x919026f3e239ea52cf530eb6d345dc2b56ef0928f1e9ad20d8f360284dc6504814395e7137e2204f15b69239010f3c34fbb3c858a29b0d106b1fa65bc0047263
  // signed ///
  r = 0xccedf9058419be4bf0d0aaf55b20072bcf6acb16621ac4ab90a3ed20b83a85ce
  s = 0x6c2444f18d6069e828b3ce0e4e5f2f20a2d7e701042bb4bf9361b228f0091ac6
  // expected ///
  r = 0x919026f3e239ea52cf530eb6d345dc2b56ef0928f1e9ad20d8f360284dc65048
  s = 0x14395e7137e2204f15b69239010f3c34fbb3c858a29b0d106b1fa65bc0047263

Number of valid signatures:  2019
Invalid signatures:  3

This should not happen as foundry and nobles curves use RFC6979.
My investigation lead me to into looking at how k is generated for both repo:

nobles-curves:  https://github.com/paulmillr/noble-curves/blob/1db569a52474ea94d6ec06fbe5321d17395ca255/src/abstract/weierstrass.ts#L1064
Foundry depends on ECDSA 0.16.9 which depends on crate RFC6979 0.4.0 :

https://github.com/foundry-rs/foundry/blob/6b0c27ed4ccfdb5a4805e9f53d487cca51c5e116/Cargo.lock#L2887
https://docs.rs/rfc6979/latest/rfc6979/fn.generate_k.html

I am still looking into it as I did not found the root cause yet.
Here the branch with the tests that lead to this
https://github.com/verklegarden/crysol/compare/main...obatirou:crysol:nobles-curves-ecdsa

authors: obatirou pmerkleplant

repo: verklegarden/crysol


text:
How to use secretMounts for passwd and acl in k8s?

I probably doing it wrong, but I'm having trouble using the new secretMounts settings with the helm chart. Here is my secrets file which I converted the contents of both my passwd and acl file to base64:
apiVersion: v1
kind: Secret
metadata:
  name: vernemq-secrets
  namespace: vernemq
data:
  vmq.passwd: #{vmq-passwd}#
  vmq.acl: #{vmq-acl}#
type: Opaque

... and my values.yaml:
...
persistentVolume:
  ## If true, VerneMQ will create/use a Persistent Volume Claim
  ## If false, use local directory
  enabled: false

  ...
  # A list of secrets and their paths to mount inside the pod
  # This is useful for mounting certificates for security (tls)
  secretMounts:
    - name: vernemq-secrets
      secretName: vernemq-secrets
      path: /etc/vernemq
...

I'm sure I'm doing it wrong, but my goal is to have the secrets for both acl and passwd mount and be used by the cluster.

@donfmorrison can you share more information about what isn't working? E.g. some logs. If possible try to do an ls -la /etc/vernemq just to confirm that the files are there (or not) and have the proper permissions.

@dergraf Looks like those secrets aren't being mounted:
kubectl exec vernemq-0 --namespace vernemq -- ls -la /etc/vernemq
lrwxrwxrwx    1 root     root            12 Sep 27 06:19 /etc/vernemq -> /vernemq/etc

kubectl exec vernemq-0 --namespace vernemq -- ls -la /vernemq/etc
total 60
drwxr-xr-x    2 vernemq  vernemq       4096 Oct 23 04:51 .
drwxr-xr-x    1 vernemq  vernemq       4096 Oct 23 04:51 ..
-rw-r--r--    1 vernemq  vernemq      38877 Oct 23 04:51 vernemq.conf
-rw-r--r--    1 vernemq  vernemq        352 Oct 23 04:51 vm.args
-rw-r--r--    1 vernemq  vernemq        217 Oct 23 04:51 vm.args.bak
-rw-r--r--    1 vernemq  vernemq          8 Sep 27 06:08 vmq.acl

Secrets do appear to be present:
kubectl describe secrets/vernemq-secrets --namespace vernemq
Name:         vernemq-secrets
Namespace:    vernemq
Labels:       <none>
Annotations:
Type:         Opaque

Data
====
vmq.acl:     506 bytes
vmq.passwd:  947 bytes

Are there specific logs that would help?

Something comes to mind that I learned just recently. In the Dockerfile we declare a /vernemq/etc as a volume (see https://github.com/vernemq/docker-vernemq/blob/master/Dockerfile#L58), at this point I am not sure if this is the wisest thing to do (@drf, @francois-travais, @codeadict).
As a consequence a volume gets automatically created and survives the deletion of the container. BUT (if I understand it correctly) when the container gets restarted it uses the existing volume automatically and doesn't mount a 'new' volume that may contain new data. Do you think it is possible that this could causing this issue here?

@dergraf - about the volume, I agree it might not the best approach, although it is unlikely to cause that issue you mentioned. Also, removing it would alter a well-known behavior for current users so I'd be extremely reluctant in doing so - it needs proper messaging and an upgrade path.
The first thing that comes to my mind is that, if @donfmorrison pasted his yaml correctly, secretMounts is in the wrong hierarchy (under persistentVolume instead of being top-level), and this basically doesn't make it work.

@drf good catch! I did have the secretMounts section at the wrong level underneath persistentVolume. FIxed that.
Deployments failed using mount path /etc/vernemq so there might be something to your thoughts there. Changing to different mount path resolved all issues.
Secret files mount and setting the path to passwd and acl files via config variables get's everything working as expected.
secretMounts:
  - name: vernemq-auth
    secretName: vernemq-secrets
    path: /vernemq/auth

Thank you!

@dergraf I think this is mostly documentation material

authors: dergraf donfmorrison drf

repo: vernemq/docker-vernemq


text:
README: add libsnappy requirement

I was trying to compile VerneMQ 1.10.2 locally and it failed while compiling eleveldb.
I found the reason in this comment, but since it's a little bit buried (and the error doesn't mention libsnappy-dev) I think it's better to add it to the README.

thanks!

source: gharchive/pull-request

authors: ioolkos rbino

repo: vernemq/vernemq


text:
Empty post body in HTTP server

If a HTTP client posts some String to a vert.x HTTP server the body received by the server seems to be empty although the server registered an BodyHandler.
I have created an reproducer for that issue.

https://github.com/leolux/vertx-body_empty

This is trivial, isn't it?
I wasn't able to find a solution though :baby_chick:

Try:
router.route().handler(BodyHandler.create());
router.route().method(HttpMethod.POST).path("/some/resource").handler(....)
You're overwriting the body handler with the second handler. Routes can only have one handler.
A very similar issue was discussed on the google group not very long ago.
Also....
In your main, you're deploying the Server immediately followed by the client without waiting, so there is no guarantee the server is started before the client sends the request.

When you do this:
router.route().handler(BodyHandler.create()).method(HttpMethod.POST).path("/some/resource")
.handler(otherHandler);
You're creating a single route, then first setting the handler to be a body handler, setting the method and path then setting the handler to be otherHandler (overwriting the bodyHandler).

Yeah, that's it. I must have been blind :-)
Thank you!

authors: leolux purplefox


text:
🛑 Dálkový přístup do KN is down

In 7749454, Dálkový přístup do KN (https://katastr.cuzk.cz/LoginDPWEB/login/Login.do?PAR_DestinateApplication=DalkovyPristup) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Dálkový přístup do KN is back up in c9be13b after 7 minutes.

repo: veselyjiri/uptime

license: MIT


text:
the height of the console input field is so small and can't be changed

This have been modified to 5 lines initial.

authors: jude-zhu nianiaJR

repo: vesoft-inc/nebula-web-docker


text:
Unlimited Access to OpenAI & Claude APIs at Unbeatable Prices - 5$ free trial !

Are you a developer looking to harness the power of cutting-edge AI models without breaking the bank? Look no further! We're excited to introduce our API service that provides unrestricted access to OpenAI and Claude models at incredibly competitive rates.
Key Features:

Unlimited Requests and Tokens: No more worrying about hitting usage limits. Develop and scale your projects with confidence.
Cost-Effective Pricing: Save up to 70% compared to standard pricing. Maximize your budget and minimize expenses.
Access to Top AI Models: Leverage the capabilities of OpenAI and Claude models for your innovative projects.

Why Choose Our Service?
Our mission is to empower developers like you to push the boundaries of AI integration in your projects without financial constraints. By offering unlimited access at reduced costs, we aim to foster innovation and accelerate the development of groundbreaking applications.
Special Offer for GitHub Projects!
To support the open-source community and independent developers, we're offering:

$5 Free Trial Credit: Test our service with OpenAI models at no cost (only OpenAI for free trial, include o1 model)
Free Registration: No upfront fees or commitments.

Don't miss this opportunity to supercharge your AI development while keeping costs under control. Sign up today and experience the future of AI accessibility!
Get free trial now
DM me in telegram: @ericjapper_liogpt

spam

authors: bjormel liogpt

repo: vespa-engine/vespa


text:
Track test-and-set condition not met as success + in new metric

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

@baldersheim PTAL

FYI @yngveaasheim


text:
Limit amount of work in DocumentV1 Q to 4096, or 3s.

Having only a fixed length here does no work well when throughput is low.
@jonmv or @bjorncs PR

Unfortunately it was not enough. You will fill the Q with 4k elements when starting up anyway before there is any pushback from mbus. After discussion with @bjorncs we decided to try without the Q and get direct feedback from mbus, since that already has a dynamic Q.

Revert until all our main clients have been verified.


text:
Latest merge borked post deletions

Attempting to delete a post results in error 500 now.

PHP Fatal error:  Uncaught TypeError: Argument 1 passed to Rails::reportException() must be an instance of Exception, instance of ParseError given, called in /home/lolibooru/myimouto/vendor/railsphp/railsphp/lib/Rails/Rails.php on line 268 and defined in /home/lolibooru/myimouto/vendor/railsphp/railsphp/lib/Rails/Rails.php:295
Stack trace:
#0 /home/lolibooru/myimouto/vendor/railsphp/railsphp/lib/Rails/Rails.php(268): Rails::reportException(Object(ParseError))
#1 [internal function]: Rails::exceptionHandler(Object(ParseError))
#2 {main}
thrown in /home/lolibooru/myimouto/vendor/railsphp/railsphp/lib/Rails/Rails.php on line 295

POST /post/destroy
PHP Warning
array_merge(): Argument #1 is not an array
#0 [internal function]: Rails::errorHandler(2, 'array_merge(): ...', '/home/lolibooru...', 652, Array)
#1 config/default_config.php(652): array_merge(NULL, Array)
#2 app/models/Post/TagMethods.php(193): MyImouto\DefaultConfig->on_commit_tags_hook(Object(Post))
#3 Rails/ActiveRecord/Base.php(636): Post->commit_tags()
#4 Rails/ActiveRecord/Base.php(409): Rails\ActiveRecord\Base->runCallbacks('save', Object(Closure))
#5 Rails/ActiveRecord/Base.php(383): Rails\ActiveRecord\Base->save(Array)
#6 app/models/Post.php(166): Rails\ActiveRecord\Base->updateAttribute('status', 'flagged')
#7 app/models/Post.php(175): Post->flag('Not anime', '2')
#8 app/models/Post.php(186): Post->destroy_with_reason('Not anime', Object(User))
#9 app/controllers/PostController.php(289): Post::static_destroy_with_reason('431194', 'Not anime', Object(User))
#10 Rails/ActionController/Base.php(268): PostController->destroy()
#11 Rails/ActionController/Base.php(238): Rails\ActionController\Base->runAction('destroy')
#12 Rails/Application/Base.php(188): Rails\ActionController\Base->run_request_action()
#13 Rails/Application/Base.php(39): Rails\Application\Base->_run()
#14 public/index.php(3): Rails\Application\Base::dispatchRequest()
#15 {main}
Error context:

Actually was working on that right now. See commit 02cca0efa99dfbf5f2a5f136ab20a7ca51025d43 for fix

It's still borked actually.

Not sure why.
Moving CONFIG()->on_commit_tags_hook($this); to be below
if ($this->isNewRecord() || !$this->new_tags)
            return;

should have fixed it. I can delete posts on mine after that change. Is it still not working? Same error?

I am dumb. I forgot to remove the line above it.


text:
Update maintainers in README.md

Summary
Update the maintainers list and remove the broken link to roadmap.
Implementation Notes :hammer_and_pick:

N/A

External Dependencies :four_leaf_clover:

N/A

Breaking API Changes :warning:

N/A

@JooyoungPark73 please review

repo: vhive-serverless/vHive


text:
Update compositor data for Mir 2.12

It now implements primary-selection-unstable-v1: https://github.com/MirServer/mir/releases/tag/v2.12.0

Looks good, thanks!

authors: JamiKettunen vially

repo: vially/wayland-explorer


text:
chore(main): release 1.5.3

:robot: I have created a release beep boop
1.5.3 (2023-10-13)
Bug Fixes

🔧 修复点击无线模式没有反应的问题 (9d55ef9)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/viarotel-org/escrcpy/releases/tag/v1.5.3 :sunflower:

repo: viarotel-org/escrcpy


text:
chore(main): release 1.4.0

:robot: I have created a release beep boop
1.4.0 (2024-07-11)
🚀 Features

update Debian releases (0de71c2)

🐛 Bugfixes

correct branding color (dbb4ca7)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/vicamo/actions-library/releases/tag/v1.4.0 :sunflower:

repo: vicamo/actions-library


text:
Suggestion kernel.json

First, I like to say it's a really nice kernel you made! It saved me a lot of time! 👍
I am not that experience with Kernels, the comment on the PYTHONPATH really helped me, but I was still struggling. The fix for me was to add this to the json file:
	"env": { 		"PYTHONPATH": "<path of dartkernel.py>" 	}
Maybe other coders will less struggle upon using this.
Sincerely,
Tom

@T0m6502
good suggestion.  Each person's python path can be different.  It's a user specific setting.  i.e., we can't hard-code the setting in the kernel.json file b/c we don't know the location of where the dartkernel.py resides (you could have cloned this anywhere, right?)
I think maybe, adding these details to the README.md might be sufficient.
Let me know if there's anything else that's not working.

Closing out this issue b/c the setting is user specific.


text:
implementation of OpenHashMap.trim( final int n ) seems wrong

In current implementation of public boolean trim(final int n) in OpenHashMap, there is a conflict between method argument n and field member this.n. The argument should be renamed or a this.n should be used to disambiguate.

OMG I don't know how I missed this. Fixed. Can you give me a name for thanking you in the CHANGES file?

authors: CAT-Solstice vigna

repo: vigna/fastutil

license_source: bigquery


text:
Update aws-core, http-client-spi, ... to 2.17.140

Updates

software.amazon.awssdk:aws-core
software.amazon.awssdk:http-client-spi
software.amazon.awssdk:netty-nio-client

from 2.17.104 to 2.17.140.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #77.

repo: vigoo/zio-aws


text:
Miratope can't render 17 or higher dimensional hypercubes/orthoplexes without crashing.

When I set the dimension count to 17 or higher for the hypercube or orthoplex under the generic folder and then click on the hypercube/orthoplex button to render them, it crashes. It doesn't crash like this when I set the dimension count to 17 or more (up to 20) for the simplex analogues. Is it because these hypercubes and orthoplexes have too many facets or that my storage space is full? I am using miratope version v0.0.3.

Hypercubes and orthoplexes have 3^n elements, simplices have 2^n. At those values of n, that fills up the whole RAM and crashes. Not fixable with the way Miratope stores polytopes.

repo: vihdzp/miratope-rs


text:
[improvement] add a cache

Do you plan to add a cache similar to https://github.com/fukatani/stacked_generalization ?

Yes.
In fact, there are plans to restructure the whole project to include features such as Regressors support, caching, lazy-roc definition (...). PR's are welcome.

I will try to look into this. Do you have any idea where the utils package referenced here comes from? I could not install / find a working version on GitHub or for pip https://github.com/fukatani/stacked_generalization/blob/master/stacked_generalization/lib/joblibed.py

@geoHeil https://github.com/fukatani/stacked_generalization/blob/master/stacked_generalization/lib/util.py

@dvro thanks for pointing me there. I overlooked this one after pip complained on installation of not finding such a utils package.

I fixed the utils import bug at that other library, nonetheless their caching system does not seem to work / is causing problems for me. http://heamy.readthedocs.io/ seem to have a cache as well will need to look into that.

Thanks for your project very much!

In fact, there are plans to restructure the whole project to include features such as Regressors support, caching, lazy-roc definition (...).

@dvro @thypad any news on this items?

@dvro won't be able to maintain the project anymore, so it will take a little more for me to complete the restructuring.

authors: dvro geoHeil kuraga thypad

repo: viisar/brew

license: mit


text:
Rename .in to .conf

In its current state, the file containing the input structures is referred to as an input file. The input configuration file is also called input file. To avoid ambiguity, the latter should be called config and use the .conf extension.

This should now have been implemented.

repo: viktorsvahn/asemd


text:
virtualenv shows only for filetype =~ python

this might be a vim-virtualenv extension issue but i am not sure
with the jmcantrell/vim-virtualenv plugin installed and g:airline#extensions#virtualenv#enabled = 1 the statusline correctly shows the virtualenv when it is set - but only for filetypes matching "python".
i would like to configure it to show for other file types - the reason is that i am using python code inside vim (for example for linting and for the taskwiki plugin) and i have the necessary imports installed in a virtualenv so it is useful to see this in the statusline.
(i think) it happens because of this sort of checking in vim-airline/autoload/airline/extensions/virtualenv.vim:
 if &filetype =~# "python"
is there a "nice" way to override this behaviour?   (one that won't be overwritten when the plugin updates)

okay thanks, please try as mentioned in bf5d785 commit message

works perfectly 👍
brilliant.    thank you

repo: vim-airline/vim-airline


text:
Wrong syntax highlighting in perldoc output

nvim --version:

NVIM v0.3.3
Build type: RelWithDebInfo
Lua 5.3
Compilation: /usr/bin/cc -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -Wconversion -Wp,-U_FORTIFY_SOURCE -Wp,-D_FORTIFY_SOURCE=1 -O2 -g -DMIN_LOG_LEVEL=3 -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fdiagnostics-color=auto -Wno-array-bounds -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -I/builddir/build/BUILD/neovim-0.3.3/build/config -I/builddir/build/BUILD/neovim-0.3.3/src -I/usr/include -I/builddir/build/BUILD/neovim-0.3.3/build/src/nvim/auto -I/builddir/build/BUILD/neovim-0.3.3/build/include
Compiled by mockbuild

Features: +acl +iconv -jemalloc +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info

Vim (version: ) - same result too
Operating system/version: Fedora 29
Terminal name/version: Konsole
$TERM: xterm-256color

Steps to reproduce using nvim -u NORC
nvim -u NORC

I just ran perldoc perldata (I have nvi set as default editor and pager (with vimpager plugin))
Actual behaviour

Expected behaviour
Not resetting the color after /x
See https://github.com/neovim/neovim/issues/9544 and https://github.com/vim/vim/issues/3860

This seems to be coming from a file bundled in the vimpager plugin:
https://github.com/rkitover/vimpager/blob/master/syntax/perldoc.vim
It detects perldoc has run and uses this.  As mentioned above, rendered perldoc output just isn't the same as the source input, so I'm not sure that file, which is pretty much an old copy of the perl syntax, would ever look very good.

@merrilymeredith thanks for the information! I will see what I can do, maybe will be able to patch it myself.

authors: XVilka merrilymeredith

repo: vim-perl/vim-perl

license: Vim


text:
make line commands use visual lines in softwrap (enhancement)

For softwrap. Would it be possible to give an option for line commands to use visual lines (that is lines as they appear on screen, rather than wrapped lines). By line commands I mean any commands having to do with lines like D, dd, go to beginning/end of line, etc. This would make life way better for editing.
n fact we already have this with J,K but these are the only commands of this type.
Btw, I cannot imagine any reason why this is not default.

That would be a backward incompatible change. If you really want that, I suggest to use visual mode together with g^, g0 and g$ motions. That would be a nice little vim plugin, perhaps it already exists. I am closing this.

a) How is this an incompatible change if it is an option that could be toggled? I am not saying it should be default, though like I said cannot imagine why it isn't.
What about D, V command, etc? these behave terribly with wrapped text.

On Thu, Oct 13, 2016 at 4:00 PM, yashamon vim-dev-github@256bit.org wrote:

What about D, V command, etc? these behave terribly with wrapped text.

For the D command, just do dg$.  If you don't like typing three characters,
make up a mapping.
-Manny

And the V command? And the A command? Why propose a solution which works half the time, is annoying to implement for the end user, when the current default behavior makes no sense what so ever?

To be clear I am not asking for default behavior to be changed, I am just flabbergasted by it. But I would like an option that could be toggled to make it sane.

authors: chrisbra vim-ml yashamon

repo: vim/vim


text:
Environment variable $TERM is not passed correctly to a job

:help terminal-unix says $TERM is passed to a running job.
But after :let $TERM = 'xterm-256color' | term bash --norc, $TERM in bash is still equal to xterm.

I poked xterm-direct, for unlimited color.  Alas, not yet.

authors: bohrshaw egberts


text:
Syntax for Make assignment

The ::= assignment should be treated the same as :=. It has been adopted by GNU Make already and has been accepted for POSIX Issue 8. Currently, it is not recognized by the syntax highlighting.

On Do, 09 Jan 2020, Bogdan Barbu wrote:

The ::= assignment should be treated the same as :=. It has been adopted by GNU Make already and has been accepted for POSIX Issue 8.

Please contact the syntax file maintainer. Thanks.

I did but he didn't answer.

I did but he didn't answer.

Roland @rohieb was active a month ago,

Yes, there was a fair share of life this week. I've read your mail and will handle it.

closing then.

@Boobies I'm not sure what your request is. Currently we don't highlight the := in assigments at all, so changing this to ::= is a trivial no-op and should already be supported in your version of vim. :)

authors: Boobies bogdan-barbu brammool chrisbra rohieb


text:
Vim9: cannot get listing of matching function names after ":def Pattern"

Describe the bug
On the command-line, we cannot get a listing of the matching function names after :def Pattern.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    def Pattern()
    enddef
    feedkeys(":def Pat\<c-d>", 'nt')
EOF
)

C-d does not cause the pager to display the functions whose name start with Pat; instead it is inserted literally on the command-line.
Expected behavior
C-d causes the pager to display the name of the Pattern() function:
:def Pat
<SNR>1_Pattern
^------------^

Environment

Vim version: 8.2 Included patches: 1-1287
OS: Ubuntu 16.04.6 LTS
Terminal: XTerm(356)

Additional context
The issue does not come from the fact that the pattern was not prefixed by s:; the issue persists even with the latter:
vim9script
def Pattern()
enddef
feedkeys(":def s:Pat\<c-d>", 'nt')

The issue disappears if we use :fu instead of :def on the command-line:
vim9script
def Pattern()
enddef
feedkeys(":fu s:Pat\<c-d>", 'nt')

Is it working as intended?  Shouldn't :fu only be able to access the names of legacy functions, and :def only the names of Vim9 functions?

I've also noticed that :delfu is able to delete a :def function in a legacy script:
def Func()
enddef
delfu Func

Again, is it working as intended?  Or should we instead use a new :deldef command?

Also, :fu is able to give the definition of a :def function
vim9script
def g:Func()
    echo 'test'
enddef
fu Func

:fu Func
    def Func()
 1          echo 'test'
    enddef

So, all in all, it seems that :fu and :delfu can operate of :def functions, just like regular legacy functions.

Yes, :def functions are also functions.  You can also call them like functions defined with :function.  So there doesn't seem to be a reason for the need of :deldef.
If you delete a :def function and call it you will get "E933: Function was deleted"
About completion: The script-local function cannot be called from the command line without knowing the script ID.  I don't see why you would want to call it anyway.
In case you just want to find the function, use ":filter Pattern func".

About completion: The script-local function cannot be called from the command line without knowing the script ID.  I don't see why you would want to call it anyway.

It's just a matter of consistency; if :fu and :def can both access the same functions, and if :fu is able to expand s: (which is the case), then I would expect :def to also be able to expand s: (which is not the case).
Other than consistency, I regularly want to create a breakpoint in a script-local function.  It only works if I provide the script ID:
:breakadd func <SNR>123_myfunc

To get this command, I type this:
:func s:myfunc

Then, I press Tab, and Vim expands the command-line into:
:func <SNR>123_myfunc

Then, I press C-b to jump at the start of the command-line.  Finally, I type :breakadd  and press Enter.
It's not a big issue anyway, I'll keep using :fu both for legacy functions and Vim9 functions.

In case you just want to find the function, use ":filter Pattern func".

:filter would print the full function name on the command-line, but I would still need to copy it; outside tmux, I'm not sure how to do it (I guess with the mouse, but I don't like the mouse).  With the previous method, I don't need to copy anything, because the expansion is not printed; it's inserted.

I'm closing the issue, because I don't think it's very important anyway, since we can use :fu or :def interchangeably on the command-line.

Ah, you first use completion and then go back and change the command.  Should have completion on ":breakadd func", isn't that working?  Apparently not.
Completion normally uses the typed text as the lead.  In this case the script number would be needed, which you generally don't know.  Expanding "s:FuncName" to include the script number is a bit weird, bit useful anyway.  When typing the "s:" is not meaningful, since there is no script context, thus interpreting this as "any script" makes sense.

Thank you for adding a todo item to add completion for :breakadd:

Implement completion for "breakadd".  Should expand the second argument, e.g.
"func", and then function names after ":breakadd func".  Including
script-local functions.

The same issue applies to :profile.

authors: brammool lacygoill


text:
Update colorschemes

Add missing 8c support
Bring back bolds as in originals

@romainl, fyi

I will include it and send out a runtime files update soon.  Thanks!

authors: brammool habamax


text:
xssproxy receives dbus messages for disabling screensaver but the screen still goes blank/start screensaver

Hi,
I installed xssproxy on ubuntu, using it with verbose options I get some logs while firefox is playing a video like:
Inhibit request app=':1.2349' name='firefox' reason='audio-playing'
Disabling screensaver
Inhibit request app=':1.2349' name='firefox' reason='video-playing

That seems OK, but looking at xset q I still see DPMS is Enabled and the screen goes in standby after some time.
I tried with xscreensaver  installed and running but still the screen goes blank or the screensaver is started.
I am using xssproxy version 1.0.0.
I am using i3 as window manager.

xssproxy calls XSuspendScreenSaver which stops the timer. This is not visible in xset q. I am unable to reproduce. mpv does the same thing, can you run it with -v and check if it works for it? You should have the following line:
[vo/gpu/x11] Disabling screensaver.

It also has code to disable DPMS, but it should not be used if the first method succeeds. It will display "Setting DPMS" if it uses this code.

Hi!
sorry for the late reply in this time I tested xssproxy and I can say that it works most of the times, few times it didn't work but it's ok I was not able to investigate about this.
What I changed is that now I start xssproxy when my wm start (i3 in its config).
When I opened the ticket I used to run it as for test via console for verbose option but I don't think this change its behaviour.
As a feature request, if possible, I would like to use xssproxy as a "client" too to query if the suspend was activated/deactivadted, to have a status like.
This could be useful imho as for test or to integrate it in status bar software like i3blocks.
Thanks, as for me the ticket can be closed.

authors: fedxyz vincentbernat

repo: vincentbernat/xssproxy


text:
Why is miner showing constant blocks mined

Hi
If this is a private network why any of the miners alice/bob/lily constantly keep printing these lines

INFO [10-01|00:24:18] Successfully sealed new block            number=313 hash=dc5479…7cc629
DEBUG[10-01|00:24:18] Trie cache stats after commit            misses=15 unloads=3
INFO [10-01|00:24:18] 🔗 block reached canonical chain          number=308 hash=2d8368…8d3cfe
INFO [10-01|00:24:18] 🔨 mined potential block                  number=313 hash=dc5479…7cc629
INFO [10-01|00:24:18] Commit new mining work                   number=314 txs=0 uncles=0 elapsed=271.092µs

Each node that is mining will print these lines out as new blocks are mined on the private network. These lines are the same ones that are printed if you were mining on the main Ethereum network.

Yeah but I am not doing any transactions. I thought mining happens when transactions are processed. Is it still supposed to be mining? The block numbers go up too constantly. I am probably wrong with my concepts here, my apologies for asking you wrong question.

The miners will continuously mine blocks (and be rewarded for doing so) even if there are no transactions to be processed. In a way, the reward for mining blocks provides an incentive for miners to provide an infrastructure which is "always on" and available for processing transactions. Miners will also get rewards for processing transactions (the "gas" that is spent on transactions and smart contracts goes to them).

Hi, vincentchu, do you mean, miners are mining all the time, even empty blocks? And if true, makes it sense?

authors: faizann lm2a vincentchu

repo: vincentchu/eth-private-net


text:
modelnet40_ply_hdf5_2048.zip not available anymore

Hello there!
Unfortunately I cannot test your work beacuse the weights are not available anymore under this link:
https://shapenet.cs.stanford.edu/media/modelnet40_ply_hdf5_2048.zip
I've also searched mirrors but did not found anyone currently.
May I ask you to create a mirror and share it with us here or provide an alternative link maybe?
Thank you very much in advance!

The page is online again.
Just in case it will be unavailable again here is a mirror:
https://drive.google.com/file/d/14Gao2KbJeOCyaU67TgH2iKOJNpzzeKHt/view?usp=sharing


text:
Adding TSTP to the list of signals sent to clients

Starting with Sidekiq version 5, TSTP, not USR1 is the signal that needs to be sent to the children to notify them about impeding shutdown.
Also adding .idea/ folder used by RubyMine to the list of git-ignored files.

Thanks! Released 1.7.3 version.

authors: kigster laurynas

repo: vinted/sidekiq-pool


text:
Add style inheritance for text style attributes

Attributes which affect text styles (color, font size, etc.) should be inherited from the parent element.

Turns out this is really hard to do efficiently.

repo: viridia/quill


text:
Does viro support to get asset from the WEB?

Does viro support to get assets such as 3D object, pano-pic, pano-video from the web?
Or we must store all the assets in local storage?

Hi @johnzhou1,
Yep, Viro does support using assets from the web, you do not need to store all your assets locally.  I've listed some of examples of how do this for various asset types below.
3DObject example using a web asset:
<Viro3DObject source={{uri:"https://s3-us-west-2.amazonaws.com/viro/heart.obj"}}
         position={[-1.7 , -4.3 , -4.65]}
         rotation={[0,0,0]}
         scale={[1.8 , 1.8  , 1.8]} />

Image example using web asset:
 <ViroImage  position={[0, 1, -3]}
            source={{uri:"https://s3-us-west-2.amazonaws.com/viro/Explorer/360_horseshoe.jpg"}} />

Video using web asset:
 <Viro360Video
          source={{uri:"https://example.com/myvideo.mp4"}}  />

Hope that helps!

That's great! Thanks a lot.

FYI, the docs might need to be updated, as it states here that:

3D models must be loaded from the application bundle.

This would have been a dealbreaker for me, so I'm pleased to see that it is not the case :)
(And it's also missing that glTF is now supported I guess)

Thanks for the call out. Docs have been updated.

Hi this sounds relevant to our project can you show us an example using other remote assets to go with the OBJ (mtl, png) we have unable to get these working, we get a white object but using the same files locally in res directory works fine.
Thanks in advance

Did you find some solution?, Im getting same issue

Hello. Since glTF files specifies it's asset relative path within the file, how are we supposed to get them referenced when downloading from the server? Should we make a local copy of all of them or there is a more dynamic way of doing this?

authors: VikAdvani dam00n georgecirilo johnzhou1 masierraf silvainSayduck

repo: viromedia/viro


text:
Unable to resolve module ./res/emoji_smile/emoji_smile.vrx

Developing an sample app by following this (https://docs.viromedia.com/docs/tutorial-ar) tutorial and its working fine only if this Viro3DObject piece of code is not included
        <Viro3DObject
            source={require('./res/emoji_smile/emoji_smile.vrx')}
            position={[-.5, .5, -1]}
            scale={[.2, .2, .2]}
            type="VRX" />

and if this code is included then its throwing this error
  Loading dependency graph, done.
  error: bundling failed: Error: Unable to resolve module `./res/emoji_smile/emoji_smile.vrx` from     `C:\Path\Projects\ARSample\js\HelloWorldSceneAR.js`: The module `./res/emoji_smile/emoji_smile.vrx` could not be found from `C:\Path\Projects\ARSample\js\HelloWorldSceneAR.js`. Indeed, none of these files exist:
    `C:\Path\Projects\ARSample\js\res\emoji_smile\emoji_smile.vrx(.native||.android.js|.native.js|.js|.android.json|.native.json|.json)`
 `C:\Path\Projects\ARSample\js\res\emoji_smile\emoji_smile.vrx\index(.native||.android.js|.native.js|.js|.android.json|.native.json|.json)`
at ModuleResolver.resolveDependency (C:\Path\Projects\ARSample\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:161:851)
at ResolutionRequest.resolveDependency (C:\Path\Projects\ARSample\node_modules\metro\src\node-haste\DependencyGraph\ResolutionRequest.js:91:16)
at DependencyGraph.resolveDependency (C:\Path\Projects\ARSample\node_modules\metro\src\node-haste\DependencyGraph.js:272:4579)
at dependencies.map.relativePath (C:\Path\Projects\ARSample\node_modules\metro\src\DeltaBundler\traverseDependencies.js:376:19)
at Array.map (<anonymous>)
at resolveDependencies (C:\Path\Projects\ARSample\node_modules\metro\src\DeltaBundler\traverseDependencies.js:374:16)    at C:\Path\Projects\ARSample\node_modules\metro\src\DeltaBundler\traverseDependencies.js:212:33
at Generator.next (<anonymous>)
at step (C:\Path\Projects\ARSample\node_modules\metro\src\DeltaBundler\traverseDependencies.js:297:313)
at C:\Path\Projects\ARSample\node_modules\metro\src\DeltaBundler\traverseDependencies.js:297:473

Please help since i have tried a lot to solve this. Thanks in advace

Hi @saad-ansari, it the emoji_smile.vrx file places in the file path -> [Your Workspace Folder]/res/emoji_smile/emoji_smile.vrx
It looks like the asset might not be in the correct file path. You can either move the asset to that path or rename the path

Yes i forgot to mention that the file path is correct with correct name. Issue is only with VRX or OBJ objects like if i'm using any image from the same path it works
 <ViroARScene onTrackingUpdated={this._onInitialized} >
    <ViroText text={this.state.text} scale={[.5, .5, .5]} position={[0, 0, -1]} style={styles.helloWorldTextStyle} />
    <ViroBox position={[0, -.5, -1]} scale={[.3, .3, .1]} materials={["grid"]} animation={{name: "rotate", run: true, loop: true}}/>
    <ViroAmbientLight color={"#aaaaaa"} />
    <ViroSpotLight innerAngle={5} outerAngle={90} direction={[0,-1,-.2]}
      position={[0, 3, 1]} color="#ffffff" castsShadow={true} />
    <ViroNode position={[0,-1,0]} dragType="FixedToWorld" onDrag={()=>{}} >
      <Viro3DObject
        source={require('./res/emoji_smile/emoji_smile.vrx')}
        position={[-.5, .5, -1]}
        scale={[.2, .2, .2]}
        type="VRX" />
    </ViroNode>
  </ViroARScene>

@dam00n i have tried to move res folder to root of the project but still the same error. Please check and save my time since i have been stuck to this issue from last week. Thanks in advance

Can you make sure your rn-cli.config.js has all the correct extensions.
    return ["obj", "mtl", "JPG", "vrx", "fbx", "hdr"];
  },```

You should have something like this depending on the files you use.

https://docs.viromedia.com/docs/importing-assets#adding-asset-types

Thank you @dam00n  it works now actually the file was missing :/

@dam00n RN 0.57.0 is using a new version of metro bundler which relies on a new config format (see here).
Any idea how to make this work with RN 0.57.0?

Okay, fixed it by using a rn-cli.config.js like this:
/**
 * Copyright (c) 2015-present, Facebook, Inc.
 * All rights reserved.
 *
 * This source code is licensed under the BSD-style license found in the
 * LICENSE file in the root directory of this source tree. An additional grant
 * of patent rights can be found in the PATENTS file in the same directory.
 *
 * React Native CLI configuration file
 */
'use strict'

const { getDefaultConfig } = require('metro-config')

module.exports = (async () => {
  const {
    resolver: { sourceExts },
  } = await getDefaultConfig()

  return {
    resolver: {
      sourceExts: [...sourceExts, 'obj', 'mtl', 'JPG', 'vrx', 'fbx', 'hdr'],
    },
  }
})()

Unfortunately I still get errors with RN 0.57.0 but those errors are not related to this topic anymore ;-) related to the assets import (see)

I've used @flavordaaave's solution, but the extensions were added in the assetExts entry instead of the sourceExts:
const { getDefaultConfig } = require('metro-config')

module.exports = (async () => {
  const {
    resolver: { assetExts },
  } = await getDefaultConfig()

  return {
    resolver: {
      assetExts: [...assetExts, 'obj', 'mtl', 'JPG', 'vrx', 'fbx', 'hdr'],
    },
  }
})();

Dears,
I have same problem.
i do all "https://github.com/viromedia/ViroARSampleApp"
and recheck all of above. but problem stay.
what is my fault?
thanks

Hi!! I have the same issue, but i'm using RN 0.59 / Viro 2.17, I don't have rn-cli.config.js  file
Im trying to solve using metro.config.js file
If I put in this way:
module.exports = {
  transformer: {
    getAssetExts() { return ["obj", "mtl", "JPG", "vrx", "hdr", "gltf", "glb", "bin", "arobject", "gif"];
    },

    getTransformOptions: async () => ({
      transform: { experimentalImportSupport: false, inlineRequires: false,
      },
    }),
  },
};

Show me this error:
error: bundling failed: Error: Unable to resolve module ./res/emoji_smile/emoji_smile.vrx

If I put this other way:
module.exports = {
  resolver: {
    assetExts: [ 'obj', 'mtl','jpg','vrx','hdr','gltf','glb','bin', 'arobject','png', ],
  },
  transformer: {
    getTransformOptions: async () => ({
      transform: { experimentalImportSupport: false,
        inlineRequires: false, },
    }),
  },
};

Show me this error:
error: bundling failed: Error: Unable to resolve module osfromC:\Users\XXX\Test1\node_modules\metro-config\src\defaults\index.js: Module osdoes not exist in the Haste module map

Hi!! I have the same issue, but i'm using RN 0.59 / Viro 2.17, I don't have rn-cli.config.js  file
Im trying to solve using metro.config.js file
If I put in this way:
module.exports = {
  transformer: {
    getAssetExts() { return ["obj", "mtl", "JPG", "vrx", "hdr", "gltf", "glb", "bin", "arobject", "gif"];
    },

    getTransformOptions: async () => ({
      transform: { experimentalImportSupport: false, inlineRequires: false,
      },
    }),
  },
};

Show me this error:
error: bundling failed: Error: Unable to resolve module ./res/emoji_smile/emoji_smile.vrx
If I put this other way:
module.exports = {
  resolver: {
    assetExts: [ 'obj', 'mtl','jpg','vrx','hdr','gltf','glb','bin', 'arobject','png', ],
  },
  transformer: {
    getTransformOptions: async () => ({
      transform: { experimentalImportSupport: false,
        inlineRequires: false, },
    }),
  },
};

Show me this error:
error: bundling failed: Error: Unable to resolve module osfromC:\Users\XXX\Test1\node_modules\metro-config\src\defaults\index.js: Module osdoes not exist in the Haste module map

Using the resolved worked for me, I was able to load the .vrx file on RN 0.64.2

authors: DianaCruz16 JulioC andrewasfa dam00n flavordaaave omidtecnikcm saad-ansari


text:
Network Transform System

Copied scripts from my repo to mirror, Will remove extra asmdef and move tests later on
resolves: https://github.com/vis2k/Mirror/issues/2500
How to test

Add NetworkTransformSystem to NetworkManager
Add NetworkTransformBehaviour to Player/NetworkObject
Change settings in inspector for System and Behaviour is needed
Play :)

TODO

[x] Add rotation
[ ] Add scale? (does movement syncing need scale?)
[ ] Add parent? (needs discussing internally)
[x] Find way to avoid singleton/static state
[ ] Custom editor to avoid Serialized debug fields
[x] Decide if settings should be per Behaviour instead of for System

Im fine with scale off by default, or completely removed, theres probably only 1 out of 1000 games that want to continuously sync scale.
Users in most scenarios can send change of scale via cmd/rpc, syncvar/hooks, only when required, i think the majority of others will/should do same.

closing in favor of the other one :)

closing in favor of the other one :)

authors: James-Frowen JesusLuvsYooh vis2k


text:
Update FAQ with changing transport guide.

Update faq page with a guide about changing transports.

@erikastaroza  Whilst your editing the FAQ, can you change this line:
Only host / server can check this_, below is an example of how to sync this number to all players_.
Makes no sense now the code examples got removed 😔

@erikastaroza  Whilst your editing the FAQ, can you change this line:
Only host / server can check this_, below is an example of how to sync this number to all players_.
Makes no sense now the code examples got removed 😔

Maybe change the line about forwarding? Not every transport requires port forwarding. Maybe state that some transports require port forwarding.

Maybe change the line about forwarding? Not every transport requires port forwarding. Maybe state that some transports require port forwarding.

Updated :)

Updated :)

Updated :)

Updated :)

authors: FakeByte JesusLuvsYooh erikastaroza


text:
[Bug] hover not tooltip response in viser-vue

https://viserjs.github.io/demo.html#/pie/multi-level-pie

I use the same example by vue-viser as same as Official Website Demo， but child case hoverd without  tooltip response, meanwhile console hasn't been throwing error

<template>

    <v-chart :force-fit="true" :height="height" :data="data" :data-pre="dataPre" :scale="scale">
      <v-tooltip :show-title="false" :item-tpl="itemTpl" />
      <v-coord :type="'theta'" :radius="0.5" />
      <v-pie :position="'percent'" :color="'type'" :label="label" :select="false" :style="style" :tooltip="tooltip" />
      <v-view :view-id="2" :data-pre="viewDataPre" :scale="scale">
        <v-coord :type="'theta'" :radius="0.75" :inner-radius="0.5 / 0.75" />
        <v-pie :position="'percent'" :color="color" :label="'name'" :select="false" :style="style" :tooltip="tooltip" />
      </v-view>
    </v-chart>

</template>

"vue": "^2.5.3"
"@antv/g2": "^3.0.2-beta.1"
"viser-vue": "^1.2.0"

Could you give me your Official Website Demo viser & viser-vue version?

The Official Website Demo use viser-vue 1.3.1 with vue 2.5.11. In fact, according to package.json, We set package up to viser-vue ^1.2.0 and vue ^2.5.9. Would you like to try a new version vue?

If you totally copy the viser-vue demo from official website, it should work fine.

ok，I'll try it asap ，then get back to you. thx

repo: viserjs/viser


text:
could you release 0.3.2

could you release 0.3.2

@maxbear1988 Done.


text:
Unify handling of color

Is your feature request related to a problem?
We have what appears to be a free for all in the way different classes handle/manage color as briefly touched on here, https://github.com/visit-dav/visit/pull/5205#issuecomment-720763011.
This should probably be cleaned up to use the same, consistent representation and storage for color everywhere. I would recommend that internally in VisIt, we represent colors as double[5] where first 3 are RGB, 4th is Alpha and 5th, when needed, is position (as in color control point) and where all values are in the range [0...1]. We should leave that model only to interact with the outside world (VTK, GL, Qt, etc.). This design would have downsides only in cases where we'd expect to handle very large (e.g. millions of entries) arrays of colors. Even in the most elaborate color tables, I can't myself imagine any cases with more than a few thousand colors. So, I don't think this would ever be an issue.

@biagas you mentioned something about unifying the way we handle colors and it reminded me we have this issue about that.

repo: visit-dav/visit


text:
Flexible spacing between levels in hierarchica layout

For context, the use case is the same as describe here.
What I find annoying is that, when the lineno has a large range, and nodes are relatively sparse, the fixed distance between levels would make the graph unnecessarily tail...

I'm wondering, can we add an option to enable flexible spacing between levels? So that there's a minimal space between two adjacent levels that have nodes, while the layout system can decide the actual space, presumably minimizing space.

Hi @laike9m,
two issues. One is that I don't think what you have there is a formal hierarchy, in other words you may be misusing hierarchical layout and trying to force it to do something it wasn't designed to do. The other one is that you force the rendering of a tonne of empty levels and then complain that it renders a tonne of empty levels. Just number the levels 1, 2, 3… and your problem will disappear or if you do have formal hierarchy (the only thing hierarchical layout is supposed to handle), just omit the levels, they'll be inferred from the structure.

Re-numbering the level is something I planned to do. There's some hidden complexity as the numbers of level could change as user interacts with the graph, but that' doable for sure.
I'm not sure if there's a better choice than hierarchical layout. For my use case I need to put nodes that have the same lineno on the same height, so hierarchical layout + level seems to be the only choice? I could be wrong.

kindly ping..😢

Remapped lineno to level and now looks fine. Closing this issue.

repo: visjs/vis-network


text:
Problem after updating to 0.16.0

Hello,
I'm sorry if my report is not complete but I'm a bit out of time now.
Today I did upgrade all outdated libraries in my project, including vue-svg-loader (from 0.15.0 to 0.16.0).
After the update, the build completed with a warning for each one of the vue components generated by the loader, here is the webpack output for one of them:
WARNING in ./src/frontend/components/Medal.vue?vue&type=script&lang=js& (./node_modules/babel-loader/lib??ref--2-0!./node_modules/vuetify-loader/lib/loader.js??ref--13
-0!./node_modules/vue-loader/lib??vue-loader-options!./src/frontend/components/Medal.vue?vue&type=script&lang=js&) 13:12-18
"export 'default' (imported as 'Medal1') was not found in '@Components/medal_icons/medal-1.svg'

Even if this is only a warning, when I load my vue application, then I receive this message in the console:
TypeError: "exports" is read-only
I wasn't sure if that was releated to vue-svg-loader or other libraries update (or both).
Anyway, after downgrading to previous version, warnings disappeared and the application loaded correctly.
Thanks for this library ;)

Maybe related to https://github.com/visualfanatic/svg-to-vue/issues/19

Yes, I can confirm that: downgrading svg-to-vue from 0.7.0 to 0.6.0 resolved all warnings, and made the application work again.
I missed some posts, sorry :)

Maybe this should be re-opened? I think I just got the same error.
During compilation:
WARNING  Compiled with 1 warnings                                                                                7:00:10 PM

 warning  in ./static/js/cite-grid/main.vue?vue&type=script&lang=js&

"export 'default' (imported as 'USMap') was not found in '../../../capweb/templates/includes/usa_territories_white.svg'

During page display:
usa_territories_white.svg?376f:2 Uncaught TypeError: Cannot assign to read only property 'exports' of object '#<Object>'
    at Module.eval (usa_territories_white.svg?376f:2)
    at eval (usa_territories_white.svg:620)
    at Module../capweb/templates/includes/usa_territories_white.svg (cite-grid.js:4868)
    at __webpack_require__ (cite-grid.js:782)
    at fn (cite-grid.js:150)
    at eval (cjs.js?!../node_modules/babel-loader/lib/index.js!../node_modules/cache-loader/dist/cjs.js?!../node_modules/vue-loader/lib/index.js?!./static/js/cite-grid/main.vue?vue&type=script&lang=js&:18)
    at Module.../node_modules/cache-loader/dist/cjs.js?!../node_modules/babel-loader/lib/index.js!../node_modules/cache-loader/dist/cjs.js?!../node_modules/vue-loader/lib/index.js?!./static/js/cite-grid/main.vue?vue&type=script&lang=js& (cite-grid.js:4418)
    at __webpack_require__ (cite-grid.js:782)
    at fn (cite-grid.js:150)
    at eval (main.vue?8074:1)

As a workaround, forcing yarn to use an earlier version of svg-to-vue avoided the issue:
  "resolutions": {
    "vue-svg-loader/svg-to-vue": "0.6.0"
  },

authors: f-ricchiuto fadafez jcushman simllll

repo: visualfanatic/vue-svg-loader


text:
Tablas/datos

Don @palamago,
¿En sus clases, hasta ahora, ha existido un data set o tabla que haya sido de interés para los alumnos? Esto con el fin de hacer ejemplos con datos que ya conozcan y no hacer una introducción a los mismos :sweat_smile: .

Usé uno muy pequeño sobre el top 5 de películas ganadores del Óscar, nada serio. 😄

authors: jbkunst palamago

repo: visualizacion-uc/introduccion-datos


text:
폴더 오타 수정

/examples/parcle-bundler-js-onfile => /examples/parcel-bundler-js-onfile

Thank you for your participation.

authors: ChoSeyoung visualkhh

repo: visualkhh/simple-boot-front


text:
Question: trying to figure out how I use beforeAll & afterAll following the examples provided

Hi
I'm having issues running custom fixtures in berforeAll / afterAll
i'll use the example of berforeAll  which collects some data to be used in cucumber multi reporter
I have created a custom fixture
`import { Page } from '@playwright/test';
import { Fixture} from 'playwright-bdd/decorators'

export
@Fixture("reportBeforeDataHook")
class ReportBeforeDataHook {
    private page: Page;

    constructor(page: Page) {
        this.page = page;
    }

async getReportDataBeforeAll() {
    console.log(`BEFORE HOOK RUNNING`);
    startTimeDate = new Date();
    startTime = performance.now();
    await this.page.goto(``);
    const buildNumberElement = await this.page.locator(`//span[@class='ms-2']`).first();
    buildNumber = await buildNumberElement.textContent() ?? '';
    const getUA = await this.page.evaluate(() => navigator.userAgent);
    userAgentInfo = uaParser(getUA);
    browserName = userAgentInfo.browser.name;
    browserVersion = userAgentInfo.browser.version;
    console.log('browser name:', browserName, 'browser version:', browserVersion);
    osName = userAgentInfo.os.name;
    osVersion = userAgentInfo.os.version;
    console.log('os name:', osName, 'os version:', osVersion);
    await this.page.close();
}`

Then in fixtures.ts
`import fs from 'fs';
import path from 'path';

import { test as base } from 'playwright-bdd';
import {ReportBeforeDataHook } from './Hooks/reportBeforeDataHook';
import {ReportAfterDataHook} from "./Hooks/reportAfterDataHook";

export const test = base.extend<{
  reportBeforeDataHook: ReportBeforeDataHook
  reportAfterDataHook: ReportAfterDataHook
  slowTest: void

}>( {

  reportAfterDataHook: async ( { page }, use ) => use( new ReportAfterDataHook( page)  ),
  reportBeforeDataHook:async ( { page }, use ) =>  use( new ReportBeforeDataHook( page ) ),
),

  //checks all features and  updates time out
  slowTest: [ async ( { $tags }, use, test ) => {
    if ( $tags.includes( '@slow' ) ) {
      const slowms = 300000;
      const slowtimeout = test.setTimeout( slowms );

      // test.slow()
      console.log( `slow test found extending time out to ${ slowms }  ` )
      await use( slowtimeout );

    }
    else {
      const fastms = 180000;
      const fasttimeout = test.setTimeout( fastms );
      console.log( `slow test not found using time out ${ fastms }  ` )
      await use( fasttimeout );

    }
  }, { auto: true } ],

  });

`
then when I try to use the fixture in beforeAll
`import { createBdd } from 'playwright-bdd';
import { test } from '../../steps/fixtures';

const { BeforeAll, AfterAll } = createBdd(test);

BeforeAll(async function ({ reportBeforeDataHook }) {

});`

I get error
Property 'reportBeforeDataHook' does not exist on type 'PlaywrightWorkerArgs & PlaywrightWorkerOptions & BddFixturesWorker & { $workerInfo: WorkerInfo; }'.ts(2339)
when i try to add the worker scope matching the syntax in the example
reportBeforeDataHook:[async ( { page }, use ) =>  use( new ReportBeforeDataHook( page ) ),{scope: 'worker'}]}),
I get error
   Type at position 1 in source is not compatible with type at position 1 in target.         The types of 'scope' are incompatible between these types.           Type '"worker"' is not assignable to type '"test"'.ts(2322)
I am bit confused on what I need to to do to get my custom fixtures working in the hooks

Hi @odeatomas
Worker scoped fixtures should be defined as a second generic argument in test.extend. E.g.:
export const test = base.extend<{ /* test-scoped fixtures */ }, {
  reportBeforeDataHook: ReportBeforeDataHook
  reportAfterDataHook: ReportAfterDataHook
}>( ... )

thanks for the quick response @vitalets
updated the worker scoped fixtures as a second generic argument in test.extend
 reportBeforeDataHook: [async ({  }, use) => {     await use(  new ReportBeforeDataHook() );   }, { scope: 'worker' }],
but get error
Property 'page' does not exist on type '{ reportBeforeDataHook: ReportBeforeDataHook; reportAfterDataHook: ReportAfterDataHook; } & PlaywrightWorkerArgs & PlaywrightWorkerOptions & BddFixturesWorker'.

thanks for the quick reply.
sorted now

authors: odeatomas vitalets

repo: vitalets/playwright-bdd


text:
X-Editable & PHP & MySql

Hello,
I used X-Editable plug-in and couldn't connect to database to update it. I think I must pust some code into javascript code.
Any one help me?
Thanks in advance.
Database info;
Table name is customer
column name that I wanna update is customer_name
HTML code is;
a href="#" id="customer_name" name="customer_name" data-type="text" data-placement="top" data-title="Enter New Customer Name" class="editable editable-click" data-pk="" data-url="../includes/php/update.php"></a
Javascript code is;
$(document).ready(function() {
$.fn.editable.defaults.mode = 'popup';
$('#customer_name').editable();
And update.php code is;
$customer_name = $_POST['name'];
$ID = $_POST['pk'];
$value = $_POST['value'];
mysql_query('UPDATE customer SET ' . $customer_name . '=' . $value . ' WHERE ID = ' . $ID);

i have some problam with x-editable, i get the value from sql but how to update the in sql
html code

JavaScript code
$('#username').editable({
url: '/post',
type: 'text',
pk: 1,
name: 'username',
title: 'First Name',
validate: function (value) {
if ($.trim(value) == '') return 'This field is required';
}
    });

authors: Narender-Sharma PecadoX

repo: vitalets/x-editable


text:
In docker container

I have shared the host network and full privileges to the docker container and still the chromecast api can't find any chromecasts (it works outside of the container).
I know this is a docker question moreso, but my question for you is:
How does the chromecast discovery API search and find chromecasts?
Do you know of something that the chromecast API does that wouldn't work in a docker container even though the network is shared with the host (same network) and the container has root privileges?

How does the chromecast discovery API search and find chromecasts?

It is using Multicast DNS for discovery. I suppose it is sending some request to the networks' multicast address and then waits for response. Maybe you have to configure Docker's networking settings to let the multicast packets pass through to the outer network.

https://stackoverflow.com/questions/37214608/docker-receiving-multicast-traffic
That sounds like the solution. Thanks for the insight.
I will test and report back; if you can leave this open I will make sure to post the solution, could be helpful to users of the repo.
Thanks again.

It seems like this may be quite hard (impossible?) to do in a docker container. Can I connect directly to a chromecast via local ip? That might work much easier

ChromeCast chromecast = new ChromeCast("192.168.10.36");
Found this, trying

Yeah, so for reference, just use the ip when trying to use ChromeCast in a docker container. Discovery is much more difficult to get working due to multicast having issues in the container.
So:
ChromeCast chromecast = new ChromeCast("192.168.10.36");
Thanks for the help!

Thank you very much for an update.

authors: kamenomagic vitalidze


text:
move to pnpm7

pnpm7 has a few breaking changes and a new lockfile version.
Right now our ci uses pnpm@6 and that causes errors when running on ecosystem projects already on 7.
The same can be true if we switch to pnpm7 and projects are still on 6.
Once vite main branch is on pnpm7 make that move here too. Once moved, disable projects still on pnpm6 until they also migrated.

this has been done already

repo: vitejs/vite-ecosystem-ci


text:
Duplicated modules under optimizeDeps

Describe the bug
Hi everyone,
as this is my first issue here i'd like to thank you for this great tool ❤.
I am having an issue with vite's optimization of dependencies during development: under some (admittingly very specific, but in my opinion legitimate) circumstances, vite will instantiate a module from node_modules twice.
This in turn leads to side effects happening multiple times, confused object identities and instanceof checks failing, which can be very hard to debug. When the depsOptimizer is not present (e.g. during vite build), everything works as expected.
I'll do my best describing the issue. I have also attached a repository with as minimal of a reproduction as i could manage.
The problem
At my company, we are using a vite/rollup plugin to add some reflection capabilities to an application.
Essentially, from a single import in the application's code to a virtual module, the apps entire dependency graph may be scanned. All transitive node dependencies are visited and for certain packages code is generated, including imports to modules or objects within those packages.
The reproduction repository uses a simplified system that produces the same problem. A single import "virtual:init-all-packages"; triggers analysis of the dependency graph, visits all referenced packages (just via dependencies), and if their package.json contains a "customAutoInit": "..." declaration, that init module will be imported to trigger the initialization code within that module.
The import "virtual:init-all-packages"; is thus turned into:
import "RESOLVED_LOCATION/dep1/init1.js";
import "RESOLVED_LOCATION/dep2/init2.js";
// ...

Note that this virtual module cannot use bare imports (e.g. import "dep1/init1.js") because transitive dependencies may not be reachable from the virtual modules "location" (nested node_modules etc. should be taken into account). This is why the plugin resolves the module ids passing some importer from where the import is possible. This results in an absolute path like /@fs/.../dep1/init1.js?v=d7007810, which will then be ignored by the depsOptimizer.
The problem here arises when the unoptimized modules mentioned above use node modules that are also used by the application directly (and are thus optimized in node_modules/.vite/...). There will be two copies of any modules used in this way: raw files in node_modules and a copy bundled by esbuild in .vite, with different parts of the application observing one or the other. In the reproduction repository, the module shared/inner is duplicated.
I don't think excluding certain packages from optimization would really help here, since only a static set of packages can be configured and dependencies may add additional imports whenever they feel like it, making any such solution very hard to maintain. Also optimization is a great feature in principle and i would like to make it work correctly in this case.
Additional observations
I have dug around vite's code a bit.
All problems would be avoided if the resolve(...) call in our plugin would receive an optimized module id instead of the raw location.
The implementation of resolve even has this capability, adding a missing import and then re-triggering optimization, but that branch is skipped in these specific circumstances because the (virtual) importer is in node_modules.
However, i cannot use a location outside of node_modules because the module id in question might not be reachable from elsewhere.
I have verified locally that removing the (importer && isInNodeModules(importer)) check from the linked condition would fix the issue in this case. However that line is probably there for a good reason (?). The check was introduced by Evan in this commit, but I couldn't find any additional context.
An additional option for resolve, or an improved skip condition (although i can't think of one) or any other kind of workaround with would be greatly appreciated. However, because the optimizer can alter the observable behaviour of the app in a significant matter, I believe a fix should be internal.
Reproduction
https://github.com/mbeckem/vite-duplicated-modules-repro
Steps to reproduce
Run pnpm install followed by pnpm vite dev and then open the browser, for more details see the linked repository's README.
System Info
System:
    OS: Linux 5.15 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 7 PRO 4750U with Radeon Graphics
    Memory: 17.12 GB / 30.59 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 18.13.0 - ~/.nvm/versions/node/v18.13.0/bin/node
    npm: 8.19.3 - ~/.nvm/versions/node/v18.13.0/bin/npm
  Browsers:
    Chrome: 114.0.5735.133
    Firefox: 114.0.1
  npmPackages:
    vite: ^4.3.9 => 4.3.9

Used Package Manager
pnpm
Logs

Click to expand!
$ pnpm vite dev --debug
  vite:config bundled config file loaded in 50.16ms +0ms
  vite:config using resolved config: {
  vite:config   root: '/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/src',
  vite:config   plugins: [
  vite:config     'vite:optimized-deps',
  vite:config     'vite:watch-package-data',
  vite:config     'vite:pre-alias',
  vite:config     'alias',
  vite:config     'vite:modulepreload-polyfill',
  vite:config     'vite:resolve',
  vite:config     'vite:html-inline-proxy',
  vite:config     'vite:css',
  vite:config     'vite:esbuild',
  vite:config     'vite:json',
  vite:config     'vite:wasm-helper',
  vite:config     'vite:worker',
  vite:config     'vite:asset',
  vite:config     'auto-init',
  vite:config     'vite:wasm-fallback',
  vite:config     'vite:define',
  vite:config     'vite:css-post',
  vite:config     'vite:worker-import-meta-url',
  vite:config     'vite:asset-import-meta-url',
  vite:config     'vite:dynamic-import-vars',
  vite:config     'vite:import-glob',
  vite:config     'vite:client-inject',
  vite:config     'vite:import-analysis'
  vite:config   ],
  vite:config   optimizeDeps: {
  vite:config     disabled: 'build',
  vite:config     force: undefined,
  vite:config     esbuildOptions: { preserveSymlinks: false }
  vite:config   },
  vite:config   server: {
  vite:config     preTransformRequests: true,
  vite:config     sourcemapIgnoreList: [Function: isInNodeModules],
  vite:config     middlewareMode: false,
  vite:config     fs: { strict: true, allow: [Array], deny: [Array] }
  vite:config   },
  vite:config   configFile: '/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/vite.config.ts',
  vite:config   configFileDependencies: [
  vite:config     '/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/vite.config.ts'
  vite:config   ],
  vite:config   inlineConfig: {
  vite:config     root: undefined,
  vite:config     base: undefined,
  vite:config     mode: undefined,
  vite:config     configFile: undefined,
  vite:config     logLevel: undefined,
  vite:config     clearScreen: undefined,
  vite:config     optimizeDeps: { force: undefined },
  vite:config     server: {}
  vite:config   },
  vite:config   base: '/',
  vite:config   rawBase: '/',
  vite:config   resolve: {
  vite:config     mainFields: [ 'module', 'jsnext:main', 'jsnext' ],
  vite:config     browserField: true,
  vite:config     conditions: [],
  vite:config     extensions: [
  vite:config       '.mjs',  '.js',
  vite:config       '.mts',  '.ts',
  vite:config       '.jsx',  '.tsx',
  vite:config       '.json'
  vite:config     ],
  vite:config     dedupe: [],
  vite:config     preserveSymlinks: false,
  vite:config     alias: [ [Object], [Object] ]
  vite:config   },
  vite:config   publicDir: '/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/src/public',
  vite:config   cacheDir: '/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/node_modules/.vite',
  vite:config   command: 'serve',
  vite:config   mode: 'development',
  vite:config   ssr: {
  vite:config     format: 'esm',
  vite:config     target: 'node',
  vite:config     optimizeDeps: { disabled: true, esbuildOptions: [Object] }
  vite:config   },
  vite:config   isWorker: false,
  vite:config   mainConfig: null,
  vite:config   isProduction: false,
  vite:config   esbuild: { jsxDev: true },
  vite:config   build: {
  vite:config     target: [ 'es2020', 'edge88', 'firefox78', 'chrome87', 'safari14' ],
  vite:config     cssTarget: [ 'es2020', 'edge88', 'firefox78', 'chrome87', 'safari14' ],
  vite:config     outDir: 'dist',
  vite:config     assetsDir: 'assets',
  vite:config     assetsInlineLimit: 4096,
  vite:config     cssCodeSplit: true,
  vite:config     sourcemap: false,
  vite:config     rollupOptions: {},
  vite:config     minify: 'esbuild',
  vite:config     terserOptions: {},
  vite:config     write: true,
  vite:config     emptyOutDir: null,
  vite:config     copyPublicDir: true,
  vite:config     manifest: false,
  vite:config     lib: false,
  vite:config     ssr: false,
  vite:config     ssrManifest: false,
  vite:config     ssrEmitAssets: false,
  vite:config     reportCompressedSize: true,
  vite:config     chunkSizeWarningLimit: 500,
  vite:config     watch: null,
  vite:config     commonjsOptions: { include: [Array], extensions: [Array] },
  vite:config     dynamicImportVarsOptions: { warnOnError: true, exclude: [Array] },
  vite:config     modulePreload: { polyfill: true },
  vite:config     cssMinify: true
  vite:config   },
  vite:config   preview: {
  vite:config     port: undefined,
  vite:config     strictPort: undefined,
  vite:config     host: undefined,
  vite:config     https: undefined,
  vite:config     open: undefined,
  vite:config     proxy: undefined,
  vite:config     cors: undefined,
  vite:config     headers: undefined
  vite:config   },
  vite:config   envDir: '/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/src',
  vite:config   env: { BASE_URL: '/', MODE: 'development', DEV: true, PROD: false },
  vite:config   assetsInclude: [Function: assetsInclude],
  vite:config   logger: {
  vite:config     hasWarned: false,
  vite:config     info: [Function: info],
  vite:config     warn: [Function: warn],
  vite:config     warnOnce: [Function: warnOnce],
  vite:config     error: [Function: error],
  vite:config     clearScreen: [Function: clearScreen],
  vite:config     hasErrorLogged: [Function: hasErrorLogged]
  vite:config   },
  vite:config   packageCache: Map(2) {
  vite:config     'fnpd_/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules' => {
  vite:config       dir: '/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules',
  vite:config       data: [Object],
  vite:config       hasSideEffects: [Function: hasSideEffects],
  vite:config       webResolvedImports: {},
  vite:config       nodeResolvedImports: {},
  vite:config       setResolvedCache: [Function: setResolvedCache],
  vite:config       getResolvedCache: [Function: getResolvedCache]
  vite:config     },
  vite:config     'fnpd_/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/src' => {
  vite:config       dir: '/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules',
  vite:config       data: [Object],
  vite:config       hasSideEffects: [Function: hasSideEffects],
  vite:config       webResolvedImports: {},
  vite:config       nodeResolvedImports: {},
  vite:config       setResolvedCache: [Function: setResolvedCache],
  vite:config       getResolvedCache: [Function: getResolvedCache]
  vite:config     },
  vite:config     set: [Function (anonymous)]
  vite:config   },
  vite:config   createResolver: [Function: createResolver],
  vite:config   worker: {
  vite:config     format: 'iife',
  vite:config     plugins: [
  vite:config       'vite:optimized-deps',
  vite:config       'vite:watch-package-data',
  vite:config       'vite:pre-alias',
  vite:config       'alias',
  vite:config       'vite:modulepreload-polyfill',
  vite:config       'vite:resolve',
  vite:config       'vite:html-inline-proxy',
  vite:config       'vite:css',
  vite:config       'vite:esbuild',
  vite:config       'vite:json',
  vite:config       'vite:wasm-helper',
  vite:config       'vite:worker',
  vite:config       'vite:asset',
  vite:config       'vite:wasm-fallback',
  vite:config       'vite:define',
  vite:config       'vite:css-post',
  vite:config       'vite:worker-import-meta-url',
  vite:config       'vite:asset-import-meta-url',
  vite:config       'vite:dynamic-import-vars',
  vite:config       'vite:import-glob',
  vite:config       'vite:client-inject',
  vite:config       'vite:import-analysis'
  vite:config     ],
  vite:config     rollupOptions: {},
  vite:config     getSortedPlugins: [Function: getSortedPlugins],
  vite:config     getSortedPluginHooks: [Function: getSortedPluginHooks]
  vite:config   },
  vite:config   appType: 'spa',
  vite:config   experimental: { importGlobRestoreExtension: false, hmrPartialAccept: false },
  vite:config   getSortedPlugins: [Function: getSortedPlugins],
  vite:config   getSortedPluginHooks: [Function: getSortedPluginHooks]
  vite:config } +11ms
  vite:esbuild 31.21ms tsconfck init /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules +0ms
  vite:deps scanning for dependencies... +0ms

  VITE v4.3.9  ready in 221 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose
  ➜  press h to show help
  vite:deps Crawling dependencies using entries:
  vite:deps   /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/src/index.html +0ms
  vite:resolve 0.34ms ./app/index.js -> /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/src/app/index.js +0ms
  vite:resolve 0.80ms virtual:init-all-packages -> auto-init?from=/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/src/app/package.json&noext +4ms
  vite:resolve 0.75ms shared -> /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/external/node_modules/shared/index.js +3ms
  vite:deps Scan completed in 39.70ms:
  vite:deps   shared -> /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/external/node_modules/shared/index.js +26ms
  vite:deps Dependencies bundled in 7.41ms +0ms
  vite:html-fallback Rewriting GET / to /index.html +0ms
  vite:time 37.45ms /index.html +0ms
  vite:resolve 0.91ms /@vite/client -> /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/node_modules/.pnpm/vite@4.3.9_@types+node@16.18.36/node_modules/vite/dist/client/client.mjs +0ms
  vite:resolve 0.21ms /app/index.js -> /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/src/app/index.js +4ms
  vite:load 3.59ms [fs] /@vite/client +0ms
  vite:load 1.73ms [fs] /app/index.js +1ms
  vite:resolve 0.33ms shared -> /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/node_modules/.vite/deps/shared.js?v=b189d285 +7ms
  vite:resolve 0.56ms virtual:init-all-packages -> auto-init?from=/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/src/app/package.json&noext +0ms
  vite:import-analysis 4.26ms [2 imports rewritten] app/index.js +0ms
  vite:transform 7.34ms /app/index.js +0ms
  vite:time 11.76ms /app/index.js +486ms
  vite:resolve 3.00ms dep1/package.json -> /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/external/node_modules/dep1/package.json +6ms
  vite:resolve 0.65ms dep1/init1.js -> /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/external/node_modules/dep1/init1.js?v=077357fd +1ms
  vite:resolve 0.47ms dep2/package.json -> /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/external/node_modules/dep2/package.json +0ms
  vite:resolve 0.61ms dep2/initExport -> /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/external/node_modules/dep2/init2.js?v=077357fd +1ms
  vite:resolve 0.26ms shared/package.json -> /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/external/node_modules/shared/package.json +0ms
  vite:load 7.29ms [plugin] auto-init?from=/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/src/app/package.json&noext +14ms
  vite:import-analysis 0.96ms [2 imports rewritten] auto-init?from=/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/src/app/package.json&noext +7ms
  vite:transform 1.46ms auto-init?from=/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/src/app/package.json&noext +8ms
  vite:resolve 0.12ms @vite/env -> /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/node_modules/.pnpm/vite@4.3.9_@types+node@16.18.36/node_modules/vite/dist/client/env.mjs +10ms
  vite:import-analysis 3.27ms [1 imports rewritten] /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/node_modules/.pnpm/vite@4.3.9_@types+node@16.18.36/node_modules/vite/dist/client/client.mjs +9ms
  vite:transform 4.02ms /@vite/client +8ms
  vite:time 32.49ms /@vite/client +15ms
  vite:cache [memory] auto-init?from=/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/src/app/package.json&noext +0ms
  vite:time 0.34ms /@id/__x00__auto-init?from=/home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/src/app/package.json&noext +2ms
  vite:load 11.68ms [fs] ../external/node_modules/dep2/init2.js?v=077357fd +13ms
  vite:resolve 0.77ms shared/inner -> /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/external/node_modules/shared/inner.js?v=077357fd +8ms
  vite:import-analysis 3.53ms [1 imports rewritten] /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/external/node_modules/dep2/init2.js?v=077357fd +8ms
  vite:transform 4.27ms ../external/node_modules/dep2/init2.js?v=077357fd +8ms
  vite:load 17.28ms [fs] ../external/node_modules/dep1/init1.js?v=077357fd +5ms
  vite:import-analysis 0.03ms [no imports] /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/external/node_modules/dep1/init1.js?v=077357fd +2ms
  vite:transform 0.88ms ../external/node_modules/dep1/init1.js?v=077357fd +2ms
  vite:load 11.27ms [fs] ../node_modules/.pnpm/vite@4.3.9_@types+node@16.18.36/node_modules/vite/dist/client/env.mjs +3ms
  vite:load 3.35ms [fs] ../external/node_modules/shared/inner.js?v=077357fd +0ms
  vite:import-analysis 0.09ms [no imports] /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/external/node_modules/shared/inner.js?v=077357fd +2ms
  vite:transform 0.38ms ../external/node_modules/shared/inner.js?v=077357fd +2ms
  vite:cache [memory] ../external/node_modules/dep1/init1.js?v=077357fd +11ms
  vite:time 0.44ms ../external/node_modules/dep1/init1.js?v=077357fd +11ms
  vite:cache [memory] ../external/node_modules/dep2/init2.js?v=077357fd +1ms
  vite:time 0.47ms ../external/node_modules/dep2/init2.js?v=077357fd +1ms
  vite:import-analysis 0.07ms [no imports] /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/node_modules/.pnpm/vite@4.3.9_@types+node@16.18.36/node_modules/vite/dist/client/env.mjs +4ms
  vite:transform 0.49ms ../node_modules/.pnpm/vite@4.3.9_@types+node@16.18.36/node_modules/vite/dist/client/env.mjs +4ms
  vite:cache [304] ../node_modules/.pnpm/vite@4.3.9_@types+node@16.18.36/node_modules/vite/dist/client/env.mjs +0ms
  vite:time 0.40ms ../node_modules/.pnpm/vite@4.3.9_@types+node@16.18.36/node_modules/vite/dist/client/env.mjs +7ms
  vite:cache [memory] ../external/node_modules/shared/inner.js?v=077357fd +20ms
  vite:time 0.74ms ../external/node_modules/shared/inner.js?v=077357fd +13ms
  vite:deps ✨ static imports crawl ended +16s
  vite:deps ✨ using post-scan optimizer result, the scanner found every used dependency +0ms
  vite:optimize-deps load /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/node_modules/.vite/deps/shared.js +0ms
  vite:deps ✨ dependencies optimized +2ms
  vite:load 86.71ms [plugin] ../node_modules/.vite/deps/shared.js?v=b189d285 +59ms
  vite:import-analysis 0.03ms [no imports] /home/michael/projects/pioneer/repro-depsoptimize-duplicated-modules/node_modules/.vite/deps/shared.js?v=b189d285 +54ms
  vite:transform 0.26ms ../node_modules/.vite/deps/shared.js?v=b189d285 +54ms
  vite:time 60.24ms ../node_modules/.vite/deps/shared.js?v=b189d285 +37ms

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[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.

possible duplicated of https://github.com/vitejs/vite/issues/9171 ?

I can't say this with absolute certainty, but I think that this is a different problem (with similar error symptoms, though). #9171 describes duplicated modules within the chunks generated by the optimizer (chunk-xyz.js). This issue is related two duplicate modules where one copy is generated by the optimizer and the other one is not.
Essentially, there are two "import paths" that are not merged into the same module copy, hence the module existing twice. Additonally, this problem only occurs during development, whereas #9171 can also happen during build.

I don't know much about Vite, so I'm not sure this is related, but I am getting duplicate modules breaking my app, and using resolve.alias is not helping and only causes module not found errors.
With this config,
import {defineConfig} from 'vite'
import path from 'path'

// https://vitejs.dev/config/
export default defineConfig({
	optimizeDeps: {
		noDiscovery: true,
		include: [],
	},
	assetsInclude: ['**/*.glb'],
	build: {
		target: 'esnext',
		// FIXME ^ why do private fields get compiled to __pricateAdd(), __privateGet(), etc, although we use esnext?
		minify: false,
	},
	esbuild: {
		minify: false,
		jsx: 'automatic',
		jsxImportSource: 'preact',
		target: 'esnext',
		// FIXME ^ why do private fields get compiled to __pricateAdd(), __privateGet(), etc, although we use esnext?
	},
	resolve: {
		alias: {
			'solid-js': path.resolve('./node_modules/solid-js/dist/solid.js'),
			'solid-js/store': path.resolve('./node_modules/solid-js/store/dist/store.js'),
			'solid-js/web': path.resolve('./node_modules/solid-js/web/dist/web.js'),
			'solid-js/html': path.resolve('./node_modules/solid-js/html/dist/html.js'),
		},
	},
})

I get errors like these:
Failed to resolve import "solid-js/web" from "node_modules/lume/dist/index.js". Does the file exist?

I have verified that paths like path.resolve('./node_modules/solid-js/dist/solid.js') do actually exist.
Without the resolve.alias, I do not get the missing module errors, but then the app ends up having duplicate libraries (that makes other problems).
I do have an optimizeDeps config. Is it related?

Maybe my issue is not optimizeDeps-related. Changing my alias config to following no longer has a missing module error, and duplicates are prevented:
		alias: {
			'solid-js': path.resolve('./node_modules/solid-js'),
		},

Dunno if this is related, but I just ran into an issue where running vite build produced two different sized results depending on if the packages were installed with npm ci vs pnpm i --frozen-lockfile.
I narrowed it down to the use of shared-workspace-lockfile = false in my .npmrc file. Removing, or setting this to true removed the duplication of bundled assets and the filesizes are the same/closer.

For context... This happened for me in a monorepo using "npm workspaces". We mainly use npm, but "npm workspaces" are a bit of nightmare for building and isolating/ejecting backend Node applications for production. Because of this, in CI we opted to use pnpm instead to at least pnpm install --frozen-lockfile the packages at the start, and then pnpm deploy at the end to export an isolated package that we can prep for dist.
This preparation looks a little like:
# Generate PNPM Workspace and Settings
cat 'package.json' | yq eval '{"packages": .workspaces}' -P - > 'pnpm-workspace.yaml'
echo 'link-workspace-packages = true' > '.npmrc'
echo 'shared-workspace-lockfile = false' >> '.npmrc'   # <---- this was causing the duplication
echo 'shamefully-hoist = true' >> '.npmrc'

# Generate PNPM Lockfile
pnpm import

# Install Dependencies
pnpm install --frozen-lockfile

The deployment/ejection looks like:
# Create isolated/deployable application
pnpm deploy --filter="$project_name" --prod /usr/src/deploy

In between those stages we would build and test etc... Using either npm or pnpm to do so, i.e... npm run build or pnpm run build, or npm run build --workspace="$project_name" or pnpm run --filter="$project_name" build.
This is where we noticed that the resulting assets for one of our very-small frontend packages was slightly larger than expected.
Running npm ci in the root of the repo to remove the pnpm installed deps and replace with npm installed ones, then re-running the build fixed the issue. So we determined it was something about how pnpm was structuring the node_modules/. After playing with the pnpm settings, we determined it was the shared-workspace-lockfile causing the problem for us.
Annoyingly, that option is kind of important for backend applications (as it seems to ensure deps with binaries are correctly exported when deploying), but for frontend applications/assets having it is causing this bundling bloat. I was hoping I could create an .npmrc in each package to tailor what we need where, but it doesn't look like these get inherited. The good news is that the setting can be added and removed just before/after pnpm deploy at least and its seems to work out. But that gymnastics is not going to be fun.
Anyways.... in my case at least, this issue seems to be related more to pnpm and not vite necessarily.

authors: dardino is-jonreeves mbeckem trusktr

repo: vitejs/vite