Support hardware requirements.

Custom Hardware Dependencies
Some packages require custom hardware.

https://github.com/microsoft/winget-pkgs/pull/19373
https://github.com/microsoft/winget-pkgs/pull/25913

Proposed technical implementation details (optional)
Extend schema, and perform validations for hardware requirements

After this, I hope we would be able to add Nvidia GPU Drivers to the repository.

I've added the label "Hardware" and use a query to help find PRs identified as needing this feature.

@denelon Any update on when this feature will be implemented?

@Rolling2405 this is likely to be a "long tail" feature. We've been discussing alternatives to having to go through the process to purchase hardware just for the sake of package validation. One of the concerns is how we deal with systems that may not meet the hardware requirements. We don't have a good way to filter apps out as we don't necessarily know how to probe for the required hardware in advance.
Maybe it could be as simple as a "Warning: This package has been identified as one requiring custom hardware". What are your thoughts on edge cases?

@Rolling2405 this is likely to be a "long tail" feature. We've been discussing alternatives to having to go through the process to purchase hardware just for the sake of package validation. One of the concerns is how we deal with systems that may not meet the hardware requirements. We don't have a good way to filter apps out as we don't necessarily know how to probe for the required hardware in advance.
Maybe it could be as simple as a "Warning: This package has been identified as one requiring custom hardware". What are your thoughts on edge cases?

I think the warning about requiring custom hardware would be a good alternate solution to Microsoft purchasing the hardware to validate packages. Although, if Microsoft is able to purchase the hardware that would be best!

We may add an informational warning for packages with specific hardware requirements if the client isn't extended to check for them as a shorter-term solution. That would at least allow us to begin including hardware specific packages, but we will still need to have access to the specific hardware in order to perform validation.

Dell.command monitor 10.9.1 4 a10 b4 de567824 (PR #113067), Requires physical system to install and run, as VM does not have a WMI-ACPI compliant BIOS.
Is it possible to enable hardware support for winget validation?

@Rolling2405 this is likely to be a "long tail" feature. We've been discussing alternatives to having to go through the process to purchase hardware just for the sake of package validation. One of the concerns is how we deal with systems that may not meet the hardware requirements. We don't have a good way to filter apps out as we don't necessarily know how to probe for the required hardware in advance.
Maybe it could be as simple as a "Warning: This package has been identified as one requiring custom hardware". What are your thoughts on edge cases?

Honestly, it should either check for specific devices in the system, or if not possible, ask the user to connect X device, use X vendor/device, etc.

One of the concerns is how we deal with systems that may not meet the hardware requirements. We don't have a good way to filter apps out as we don't necessarily know how to probe for the required hardware in advance.

Potentially silly question:
Why not make the user responsible for meeting the hardware requirements for any software they install until a solution is found?
So it would be my own fault if I tried to install something for which I don't have the necessary hardware. Or is there a deeper technical problem with simply allowing this?

Don't most installers for specific hardware or driver already have built-in checks? What if the user wants to install software for a device they haven't plugged in? As mentioned by @S1rDan the user should be responsible.


Searching for CJK works only with keywords that put inside quotation marks

Describe the bug
Searching for CJK works only with keywords that put inside quotation marks
Steps To Reproduce
I added some text in CJK like '一部販売店がHGST製品に対して Seagate の同等製品',

tried to search for 'HGST' -> No matches
tried to search for '"HGST"' -> 1 match
tried to search for 'Seagate' -> 1 match
tried to search for '販売店' ->  No matches
tried to search for '"販売店"' -> 1 match

Expected behavior
To match the keywords without quotation marks.
Your Configuration (please complete the following information):

BookStack v21.04.5
MariaDB　10.4.19
Apache/2.4.47 (Win64)
PHP/8.0.6

I checked the source code in BookStack/app/Entities/Tools/SearchRunner.php and I find the code near line 152
$query->orWhere('term', 'like', $inputTerm .'%');
the '%' is not in pairs. I fixed this code, and all keyword can be matched.
$query->orWhere('term', 'like', '%'. $inputTerm .'%');

Thanks for raising @dgwxx.
This is a known issue and already open under issues #1037 and #778 so I'm therefore going to close this off as a duplicate.


feat: Golang ssh

I've kept the old SSH functionality, henceforth known as "binary SSH", in nvrh. In fact it's still the default

--ssh-path binary will use the included OpenSSH on Windows, and ssh anywhere else
--ssh-path internal will use golang's SSH stuff added in this PR
--ssh-path /some/path/to/ssh will use binary SSH, calling out to /some/path/to/ssh

These PR has changes that will be more annoying for people that use password auth + binary ssh mode. nvrh now runs more commands after you end the session for cleanup. I really recommend:

looking into an SSH agent
looking into ControlMaster
looking into internal ssh mode

~Mostly putting this up to get it off my mind. It's nowhere near feature complete, and the amount of things we have to worry about is staggering (and really makes me appreciate just shelling out to things):~

[x] parsing ssh config
[x] host aliases
[x] username from config
[x] default user name
[x] ports from config
[x] ports on the command line
[x] password entering
[x] password auth
[x] passphrase entering
[x] passphrase auth
[x] ssh agent auth
[x] parsing known_hosts
[x] validation via known_hosts
[x] updating known_hosts

~And that's just to build a config to even begin connecting via SSH. On top of that we've got to pass a client around, and do port / socket tunnelling.~
Closes #24

Alright, I've let this cook for a month. I've been using it and it seems to work everywhere (and more importantly, doesn't have any regressions when not using the internal SSH path).
I'm not psyched on how much code it is, and don't know how willing I am to maintain it, but it's got some other refactors that I think are worth it, and it shouldn't be to hard to strip out the internal SSH path if maintenance becomes a burden.


Materialize import breaks webpack (angular-cli)

I'm curious as to why the materialize-css package is installed as materialize.
Here: https://github.com/InfomediaLtd/angular2-materialize/blob/master/package.json#L99
This causes an error with Webpack:
ERROR in ./~/angular2-materialize/dist/index.js
Module not found: Error: Can't resolve 'materialize' in '.../node_modules/angular2-materialize/dist'
 @ ./~/angular2-materialize/dist/index.js 2:0-22

The only way to get this to work is to create an alias in the build process (webpack, systemjs, etc.), but this is currently not available with the latest angular-cli, and also seems a little unnecessary.
Are you able to install the materialize-css package as is, and then just import "materialize-css" here: https://github.com/InfomediaLtd/angular2-materialize/blob/master/src/index.ts#L1
Thanks!

@rubyboy Are you accepting PR-s?

@Sixthdim thanks for the feedback. You can find more details in a similar issue here: https://github.com/InfomediaLtd/angular2-materialize/issues/54
@MarkusPint most definitely! See my comments in https://github.com/InfomediaLtd/angular2-materialize/issues/54. Maybe two deployment targets, one with and one without materialize-css, would be a good option. This way if someone wants to just import angular-materialize and let it bring all required dependencies (it does need materialize-css) they would use the current deployment. Then, create another entry point without that dependency for other people who want to bring it materialize-css any other way they want.
Thanks for offering to contribute.

This is affecting me too. I'm still not clear on why this affects angular-cli webpack and not the standard seed project? Is there a workaround we can use for the moment to get around this issue?

@pchristou This mainly affects angular-cli@webpack because it doesn't (yet) support a webpack config file, so there is no way to setup an alias for "materialize" -> "materialize-css", and "materialize" doesn't exist in node_modules. The way it's setup in this project only works with JSPM. I'll see if I can get a PR up today.

Thanks for the explanation @Sixthdim.

PR Created: https://github.com/InfomediaLtd/angular2-materialize/pull/84

OK, PR merged and a new version has been released to npm. I haven't tested it, so please give it a whirl and I hope it will work.
Thanks @Sixthdim for picking this issue up and contributing!

@rubyboy @Sixthdim Thank you both for your work. I recreated a project, imported the MaterializeDirective and that change seems to have done the trick..


Why @babel/highlight?

I'm exploring merging @babel/highlight in @babel/code-frame, and I noticed lavamoat in the dependents:
https://github.com/LavaMoat/LavaMoat/blob/df54b37bba49351a10093194d28fd488d098056a/packages/lavamoat-node/src/parseForPolicy.js#L8
Out of curiosity, why don't you just use @babel/code-frame directly, given that you are passing the highlighted code to it anyway?

cc @kumavis

I don't see a strong reason to not use code-frame directly. We could refactor.


Add enterprise to homepage and update community section

Deploy preview for calico ready!
Built with commit 7cc7a5651740732a164083ea8e6377766c532118
https://deploy-preview-3733--calico.netlify.app


Incorrect TRRS schematic symbol resulting in incorrect PCB footprint

Incorrect TRRS schematic symbol resulting in incorrect PCB footprint
The pins on the TRRS jack schematic symbol are incorrectly numbered, which results in incorrect wiring in the PCB. See incorrect writing PCB image below:

I was able to confirm that the wiring is indeed incorrect on a physical BFO-9000 PCB using a multimeter.
See below a screenshot of incorrect and correct schematics:

Extent of the effect
I looked into other places where this issue could come up.
I tested the symbols in the following Keebio Components library and the pins were correct, so that's good:
https://github.com/keebio/keebio-components
I did however, find the same issue in the following places:

Quefrency Rev. 1 Keyboard PCB
Various schematics PDF files in Keebio Docs

Suggested fix
Suggested steps for fix:

Update the symbols in the affected schematics to match what's on the PCBs.
Version the PCBs (e.g. BFO-9000 v1.0) so that it's possible to identify which type of board you have if the PCBs end up changing.
Update the symbols so that in the resulting PCB the VCC line is connected to the Tip of the TRRS jack and bump the PCB version (e.g. BFO-9000 v1.1 or v2.0).

I think just updating the schematics would be great, and I completely understand that people should not be pulling out or plugging in the TRRS cables when the keyboard's main MCU is connected.

Note
I wrote this up so that others don't have to go through the same troubleshooting steps that I did and hopefully this Github Issue will be of use for those in the same boat as me, until the affected places get updated.

Yeah, the original symbol for the TRRS used for the BFO-9000 and a couple of other boards was incorrect, and later boards used the corrected symbol. These files are being provided as-is without any further modifications on my end, so if someone else wants to fix this issue, they are free to do so and can submit a PR for it.


NIFI-1107 - Integrate Multipart uploads into the PutS3Object processor.

Add nifi-ssl-context-service-nar to nifi-aws-nar pom.
Add nifi-ssl-context-service-api to nifi-aws-processors pom.
Add SSL context service and endpoint override properties to AbstractAWSProcessor to support non-Amazon S3-compatible endpoints.
Added Multipart upload API support, multipart threshold and size properties, state tracking for multipart upload, and expanded flow file attributes to PutS3Object.
Updated annotations and property list for FetchS3Object and DeleteS3Object.
Added region to bucket in AbstractS3Test to minimize AWS propogation issues during testing.
Expanded tests in TestPutS3Object to validate new multipart logic.

My major concern is with the persistence file. I would think scrubbing the file periodically, removing older stale entries would be a must, otherwise the file will begin accumulating cruft as more and more files don't complete the multipart lifecycle.

Another, major secondary concern is what to do with failed partial multipart puts and maybe having to do bucket cleanup.

I'm closing this pull request since the general S3 changes have been incorporated by @trkurc.  The remaining Multipart Upload functionality will be incorporated into a new pull request in conjunction with S3 bucket and local state cleanup functionality.

Changes Unknown when pulling 52fd4180c7e929cbbdd3647d1b7aad68174b2f9c on jskora:NIFI-1107 into ** on apache:master**.


ERROR:make docker GOOS=linux

USE Mac os
when make docker GOOS=linux
docker build -f iothub/nginx-mqtt/Dockerfile .
Sending build context to Docker daemon  476.6MB
Step 1/9 : FROM centos
---> 2d194b392dd1
Step 2/9 : COPY iotgateway/nginx-mqtt/nginx.repo /etc/yum.repos.d/
COPY failed: stat /var/lib/docker/tmp/docker-builder696979447/iotgateway/nginx-mqtt/nginx.repo: no such file or directory
make: *** [docker] Error 1
Don`t have iotgateway,I guess it is iothub？

Please pull again, the files had been updated. Thanks


Combine sequels into a single title

Describe your suggested feature
Hello, I haven't seen this feature being mentioned anywhere and I think it would be pretty useful.
A lot of websites do not put different chapters of the same story under the same URL but rather upload each separate, making the act of reading them one after the other pretty anmoying (e-hentai being the perfect example).
So my idea is just lets us select a bunch of titles that we already added, select "combine" and just put the chapters one after the other (letting us choose the order).
Kinda like this:

So instead of 4 titles with 1 chapter each, we end with 1 title with all 4 chapters inside.
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 1.10.5.
[X] I will fill out all of the requested information in this form.

The order could probably be determined by the release dates.

The order could probably be determined by the release dates.

This would not be reliable as too many of these releases are translated out of order, by separate grouos, or have v2 releases.

I remember using a workaround with MergedSource.
Funilly enough, I used it with the same hentai as you.

Basically, the idea is to you use Merge feature and then search for other chapters.

The only problem is that Merge automatically chooses the closest match. So to be able to find vol.2 instead of a copy of vol.1 you have to rename it to some random string first (so that it won't be matched with any other entry). Only then the manual search appears.
But doing it that way was too bothersome to use on a daily basis.
I think combining your idea of selecting entries from library view and using Merge feature should allow for implementing it quite easily.
It doesn't allow reordering, but most of those have chapter/volume number in title, so default ordering works good enough. (still, it would be useful to have it too)

If we go with that, then #1094 is connected to this issue as it requests manually selecting manga to merge as well


chore(package): update multi-path-matcher to version 2.0.9

:tada: This PR is included in version 10.0.7 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Function clone in helper.js ( TypeError: obj is undefined )

Hi, I have found this problem on helper.js
var clone = exports.clone = function (obj) {
if (obj === null) {   <== THIS FAIL IF obj IS UNDEFINED
return null;
} else if (obj.constructor === Array) {
return obj.map(clone);
} else if (typeof obj === 'object') {
...
...
Please fix. Thanks

Thanks for the report!


Add @cosenary's license

Please keep the original license within the repository as specified in the BDS license file.

Sorry inconvenience.

No problem at all. https://github.com/cosenary/Instagram-PHP-API/issues/139#issuecomment-102258427


ENH: Upload COG-UK data with raw data upload so that ingest (without fetch) can get it

With the debug_subsample PR, we download COG_UK data (metadata&accessions) from s3 as well.
So we should add COG-UK data to raw data upload to be able to make everything work off s3 directly in ingest (without fetch)

Resolved in https://github.com/nextstrain/ncov-ingest/pull/365


[SPARK-21298][spark core]Don't need to modified name when it's added the same ids

What changes were proposed in this pull request?
It's not need to replace name when the key has exsited.
I have a stage,named freedom and id is 0,  then adding a stage that named nofreedom and id is 0. In this case, i think it's not need to modified the stage name. returns existing values only.
How was this patch tested?
Unit test

Can one of the admins verify this patch?

Since this is not a bug, could you please close this? @Geek-He Thank you!

ok


Remove dist and uglification config

And add Travis badge.
To comply with https://github.com/Palindrom/JSON-Patch-OT/issues/5#issuecomment-285670232

I don't know what the commit 2.0.0 is doing in this branch, but anyway the PR looks GTM :)

@warpech now that I think about it, this is a non-breaking change, and we didn't change the name. Should I bump to 1.0.2 instead of 2.0.0? I did this because we agreed to bump major to all repo name changes. But this one's name didn't change.
Would appreciate your advice.

Sorry, I have missed the question. Seems that you have already decided 12 days ago: https://github.com/Palindrom/JSON-Patch-OT/releases/tag/2.0.0

@warpech no issue at all. I released because I initially thought it's the same situation is this.


ENG-1886 Add a Docker step in the blueprint CI

To merge after https://github.com/entando/entando-blueprint/pull/128 and a rebase (this branch has been created from the Cypress one).


Driver api refactor

Refactored the driver api so that is aligns well with the design
of endpoint lifecycle becoming decoupled from the container lifecycle.
Introduced go interfaces to obtain address information during CreateEndpoint.
Go interfaces are also used to get data from driver during join.
This sort of deisgn hides the libnetwork specific type details from drivers.
Another adjustment is to provide a list of interfaces during CreateEndpoint. The
goal of this is many-fold:
* To indicate to the driver that IP address has been assigned by some other
entity (like a user wanting to use their own static IP for an endpoint/container)
and asking the driver to honor this. Driver may reject this configuration
and return an error but it may not try to allocate an IP address and override
the passed one.
* To indicate to the driver that IP address has already been allocated once
for this endpoint by an instance of the same driver in some docker host
in the cluster and this is merely a notification about that endpoint and the
allocated resources.
* In case the list of interfaces is empty the driver is required to allocate and
assign IP addresses for this endpoint.
Signed-off-by: Jana Radhakrishnan<EMAIL_ADDRESS>

LGTM

LGTM. Thanks.


Suggestion:

Make item effect items able to attach to inventory or hotbar for effect

Hello, thanks for opening this suggestion! A developer will assign to this issue and is going to keep you up to date! We don't know yet if this feature is already in the next version because in the next days there is an update planned. Of course we try to implement it as fast as possible!
If you have any question feel free to comment down below.

In the next update is will not be possible to use the items which you can currently create in any inv slot/hotbar!
BUT: There will be a new feature released too - Feature 1.2.0. You can run any commands for example a potion command and give it to a player this way.
Of course we try to implement you suggetion with the legacy items that were created with itemeffects. But there is a lot of work to do. I'll keep you updated in this thread.

Hello. please add "item-effects" that work in all slots regardless of what is in hand


Fix FlatMapTuple typehint bug

(fixes https://github.com/apache/beam/issues/33014)
FlatMapTuple throws false positive type hint errors in certain situations, e.g.
 def identity(x: Tuple[str, int]) -> Tuple[str, int]:
    return x
  with beam.Pipeline() as p:
    with beam.Pipeline() as p:
      A = (p
                | "Generate input" >> beam.Create([('P1', [2])])
                | "Flat" >> beam.FlatMapTuple(lambda k, vs: [(k, v) for v in vs])
                | "Identity" >> beam.Map(identity))

raises the following exception:
E         apache_beam.typehints.decorators.TypeCheckError: The transform 'Identity' requires PCollections of type 'Tuple[<class 'str'>, <class 'int'>]' but was applied to a PCollection of type 'Tuple[<class 'type'>, <class 'int'>]' (produced by the transform 'Flat').

This is a downstream effect of a bug in the trivial_inference.py code. I couldn't really figure out the underlying bug but we can work around it by adding a tuple coercion before unpacking in FlatMapTuple.
I've created a spinoff issue for the underlying inference issue: https://github.com/apache/beam/issues/33308

R: @jrmccluskey

I can't seem to get this isorted correctly. It's not a part of the pre-commit hook and the isort version isn't compatible with my py3.11. @jrmccluskey would you mind doing it before merging if it's easy for you env?

Have you tried to manually change the import orders?
2024-12-06T18:03:21.6023142Z ERROR: /runner/_work/beam/beam/sdks/python/test-suites/tox/pycommon/build/srcs/sdks/python/apache_beam/typehints/trivial_inference_test.py Imports are incorrectly sorted.
2024-12-06T18:03:21.6025546Z Command exited with non-zero status 1
2024-12-06T18:03:21.6026715Z 613.13user 32.61system 1:24.90elapsed 760%CPU (0avgtext+0avgdata 874112maxresident)k
2024-12-06T18:03:21.6028325Z 10928inputs+1120outputs (8major+2025317minor)pagefaults 0swaps
2024-12-06T18:03:21.6030229Z --- /runner/_work/beam/beam/sdks/python/test-suites/tox/pycommon/build/srcs/sdks/python/apache_beam/typehints/trivial_inference_test.py:before	2024-12-06 17:57:32.050442
2024-12-06T18:03:21.6033655Z +++ /runner/_work/beam/beam/sdks/python/test-suites/tox/pycommon/build/srcs/sdks/python/apache_beam/typehints/trivial_inference_test.py:after	2024-12-06 18:03:19.361962
2024-12-06T18:03:21.6035359Z @@ -21,8 +21,8 @@
2024-12-06T18:03:21.6035826Z
2024-12-06T18:03:21.6036256Z  import types
2024-12-06T18:03:21.6036738Z  import unittest
2024-12-06T18:03:21.6037179Z +
2024-12-06T18:03:21.6037906Z  import apache_beam as beam
2024-12-06T18:03:21.6038613Z -
2024-12-06T18:03:21.6039092Z  from apache_beam.typehints import row_type
2024-12-06T18:03:21.6039735Z  from apache_beam.typehints import trivial_inference
2024-12-06T18:03:21.6040397Z  from apache_beam.typehints import typehints
2024-12-06T18:03:21.6041736Z ERROR: /runner/_work/beam/beam/sdks/python/test-suites/tox/pycommon/build/srcs/sdks/python/apache_beam/typehints/typed_pipeline_test.py Imports are incorrectly sorted.
2024-12-06T18:03:21.6043773Z --- /runner/_work/beam/beam/sdks/python/test-suites/tox/pycommon/build/srcs/sdks/python/apache_beam/typehints/typed_pipeline_test.py:before	2024-12-06 17:57:32.054441
2024-12-06T18:03:21.6045808Z +++ /runner/_work/beam/beam/sdks/python/test-suites/tox/pycommon/build/srcs/sdks/python/apache_beam/typehints/typed_pipeline_test.py:after	2024-12-06 18:03:19.484289
2024-12-06T18:03:21.6047036Z @@ -22,8 +22,8 @@
2024-12-06T18:03:21.6047434Z  import typing
2024-12-06T18:03:21.6047893Z  import unittest
2024-12-06T18:03:21.6048591Z  from typing import Tuple
2024-12-06T18:03:21.6049002Z +
2024-12-06T18:03:21.6049370Z  import apache_beam as beam
2024-12-06T18:03:21.6049765Z -
2024-12-06T18:03:21.6050178Z  from apache_beam import pvalue
2024-12-06T18:03:21.6050718Z  from apache_beam import typehints
2024-12-06T18:03:21.6051435Z  from apache_beam.options.pipeline_options import OptionsContext
2024-12-06T18:03:21.6053182Z lint: exit 1 (84.91 seconds) /runner/_work/beam/beam/sdks/python/test-suites/tox/pycommon/build/srcs/sdks/python> time /runner/_work/beam/beam/sdks/python/test-suites/tox/pycommon/build/srcs/sdks/python/scripts/run_pylint.sh pid=1228
2024-12-06T18:03:21.6055705Z lint: commands_post[0]> bash /runner/_work/beam/beam/sdks/python/test-suites/tox/pycommon/build/srcs/sdks/python/scripts/run_tox_cleanup.sh


SCRIPT ERROR

As soon as you spawn the K9 through the Menu, I get this error. Thanks!

Fixed in 857849d


Remove stray please

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix-please" git@github.com:tnws/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

LGTM - @thaJeztah @moxiegirl

Heh, yes LGTM


Error parsing DS_Store file

Hi, I'm having errors parsing a DS_Store
I'm using your code:
package main

import (
	"fmt"
	"os"
	"flag"
	"github.com/gehaxelt/ds_store"
	"io/ioutil"
)

func main() {

	var fileName string

	flag.StringVar(&fileName, "i", "", "DS_Store input file")
	flag.Parse()

	if fileName == "" {
		panic("FileName (-i): Must be specified")
	} else if _, err := os.Stat(fileName); os.IsNotExist(err) {
		panic("FileName (-i): File does not exist:" + fileName)
	}

	dat, err := ioutil.ReadFile(fileName)

	if err != nil {
		panic(err)
	}

	a, err := ds_store.NewAllocator(dat)

	filenames, err := a.TraverseFromRootNode()
	if err != nil {
		panic(err)
	}

	for _,f := range filenames {
		fmt.Printf("File: %s \n", f)
	}
}

I've compiled it:
go build ds.go

After executing:
[/tmp]> ./ds -i DS_Store
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x10a3b76]

goroutine 1 [running]:
github.com/gehaxelt/ds_store.(*Allocator).TraverseFromRootNode(0x0, 0x1803, 0x1a03, 0x0, 0x10f0f60, 0xc00004e240)
	/Users/jbono/go/src/github.com/gehaxelt/ds_store/ds_store.go:188 +0x26
main.main()
	/tmp/ds.go:32 +0x13a

It's crashing in this function
Attached the DS_Store file as DS_Store.zip since GitHub doesn't allows DS_Store to be uploaded.
DS_Store.zip

Hi @joanbono
thanks for your analysis. I had the same issue of some .DS_Store files not being parsable.
If you compare your screenshots you can see that the top one has one 0x00 byte to few.
I'm not sure if that's something I can/could/should fix or not? Unfortunately there is no official documentation on the file format, so we can only guess what's wrong here.

Yeah, you are right.
Here the only thing which can be done maybe is to avoid the panic and print something like Error parsing the DS_Store file  and not that detailed and long message. But I think it is still "useless" somehow, so I'll close this 😄
Thanks a lot for your answer and for your library!


mssql: Invalid usage of the option NEXT in the FETCH statement

When executing First or Limit + Find with mssql, a sql server error is generated
Error

mssql: Invalid usage of the option NEXT in the FETCH statement.

In these cases sql query being executed is invalid
Query

SELECT * FROM "users"  WHERE "users".deleted_at IS NULL AND (("users"."id" = '1')) ORDER BY "users"."id" ASC FETCH NEXT 1 ROWS ONLY

Basically the query needs to have "OFFSET 0 ROWS FETCH NEXT 1 ROW ONLY", or the FETCH statement should be removed all together.
Environment: Windows 10, MS Sql Server Express 2016
Here is the sample code:
package main

import (
    "log"

    "github.com/jinzhu/gorm"

    _ "github.com/jinzhu/gorm/dialects/mssql"
)

type User struct {
    gorm.Model
    Email     string
    Firstname string
    Lastname  string
}

func main() {
    // db connection code goes here
    db, err := gorm.Open("mssql", /*conn string*/)
    if err != nil {
        log.Panic(err)
        return
    }
    defer db.Close()

    db.LogMode(true)

    id := 1
    var e1 User
    db.First(&e1, id) // generates error
    log.Println("user id: ", e1.ID)

    var e2 User
    db.Offset(0).Limit(1).Find(&e2, id) // genertes error
    log.Println("user id: ", e2.ID)
}

I'm getting the same exact issue. It would be great to have this fixed.

As a workaround, this works
id := 1
var e1 User
db.Find(&e1, id)

Cheers.
A bit off topic, but I have a question about the MSSQL driver in general. Is it stable? Because I've tried using a simple Has One example and I just can't get that working either.
I'm going to do some more tests and probably file an issue if I can confirm something is acting strange.

IMO, mssql dialect does seem buggy at multiple places. However gorm provides some basic working functionality which should be enough for most of the cases.

The fix is very simple, LimitAndOffsetSQL function should be replaced with below. That should take care of errors generated by multiple functions.
func (mssql) LimitAndOffsetSQL(limit, offset interface{}) (sql string) {
	if offset != nil && limit != nil {
		if parsedOffset, err := strconv.ParseInt(fmt.Sprint(offset), 0, 0); err == nil && parsedOffset > 0 {
			sql += fmt.Sprintf(" OFFSET %d ROWS", parsedOffset)
		}
		if parsedLimit, err := strconv.ParseInt(fmt.Sprint(limit), 0, 0); err == nil && parsedLimit > 0 {
			sql += fmt.Sprintf(" FETCH NEXT %d ROWS ONLY", parsedLimit)
		}
	}
	return
}

Below updated function should take care of syntax error when offset is zero
func (mssql) LimitAndOffsetSQL(limit, offset interface{}) (sql string) {
	if offset != nil {
		if parsedOffset, err := strconv.ParseInt(fmt.Sprint(offset), 0, 0); err == nil && parsedOffset > 0 {
			sql += fmt.Sprintf(" OFFSET %d ROWS", parsedOffset)
		}
	}
	if limit != nil {
		if parsedLimit, err := strconv.ParseInt(fmt.Sprint(limit), 0, 0); err == nil && parsedLimit > 0 {
			if sql == "" {
				// add default zero offset
				sql += " OFFSET 0 ROWS"
			}
			sql += fmt.Sprintf(" FETCH NEXT %d ROWS ONLY", parsedLimit)
		}
	}
	return
}

Add a merge request to this @dipbhi

Still not work with SQLServer 2008 R2

Still not working. 2019/12/01.
error message is:
"mssql: Invalid usage of the option NEXT in the FETCH statement."

Same issue. How can this basic function left broken for 3 years+ ? Why did I make myself the work yesterday using sqlite, thinking I can swap easily to sqlserver (as advertised by gorm) and now it's not "simply" working.

The issue for me was that I was missing AUTO_INCREMENT;PRIMARY_KEY after my Id column in my model


GPU memory limitation

hi，there
I want to ask why I have reduced the number of layers of the decoder, and the number of attention heads , but the gpu memory has not decreased significantly. Which part occupies more gpu memory in the process of inference？

The multi-scale encoder is heavy.


Something to consider

The cost of something like this can be pretty high for smaller collections:
Array of 20

and gives mixed results as the array length increases.
Array of 100:

I dig what you're trying to do, however it may be better accomplished through method compilation. For example checkout heya/pipe.

The fundamental advantage of the library is the increase in the number of no-ops for equivalent computations.


Protocol for Passing Arguments to the "data" field of the Drone's Infer function.

I am presently attempting to write a "simplified" version of the existing Mountain Car example - for eventual instantiation as an RxEnvironments simulation. To that end, I am shamelessly stealing some of the Drone example's code.
My question is about the drone's infer wrapper: move_to_target, which I have reproduced below:
function move_to_target(drone::Drone, env::Environment, start::State, target, horizon, dt)

    results = infer(
        model = drone_model(
            drone = drone,
            environment = env,
            horizon = horizon,
            dt = dt
        ),
        data  = (
            initial_state = collect(get_state(start)),
            goal = [target[1], target[2], 0, 0, 0, 0],
        ),
        meta  = drone_meta(),
        returnvars = (s = KeepLast(), u = KeepLast())
    )

    return results

end

It is my understanding that fields belonging to the @drone_model should be passed to infer via infer's data field. Indeed that is done here, however some of the @drone_model's fields are passed directly into the call to drone_model while the others are passed to the data field.
I can't account for why this should be the case. Should we always pass all model arguments to infer's data field? clearly it is not a "necessity", since the drone example works as intended. In that case, what is the protocol for partitioning the model's arguments between its constructor as opposed to infer's data field?
Any thoughts are appreciated!

Thoughts @wouterwln?

In RxInfer, there is a difference between data and parameters. For data, we create a delta factor node in the factor graph and make sure we can attach factor nodes to this data. For parameters, this isn't necessarily the case. Consider the following (wacky) model:
@model function recursive_model(n, y)
    if n == 1
        x ~ NormalMeanVariance(0, 1)
    else
        x ~ recursive_model(n = n-1)
    end
    y ~ NormalMeanVariance(x, 1)
end

Now in this model, we have an interface n that we don't actually want to create a factor node for (the same as the env or horizon parameters in your drone_model. However, for y, which is actually data, we want to pass it as data. So inference in this model would be done by calling:
infer(model=recursive_model(n=10), data = (y = 1,))

I think that's the difference you're after, right?

Aha, thanks @wouterwln.
So it seems that the data field is used to pass all arguments for which we want to create factor nodes - or perhaps just any node in the factor graph. Direct invocations of model parameters in the model function simply act to specify more abstract "meta-information" about the model's structure: the recursion depth in your above example. Have I understood that correctly?
A basic schema would then be: "data = graph nodes of some kind" and: "parameters = some graph metadata".
Indeed, that was the distinction I was after, thanks again.

Sure, but note that you can also pass stuff you want to make factor nodes of in the parameters.
@model function something(a, b, y)
    x ~ Normal(mean = a, variance = b)
    y ~ Normal(mean = x, variance = 1)
end

can also be invoked with:
infer(model = something(a = 1, b = 1), data = (y = 0.0,))

The only thing is that you cannot pass parameters as data. Strictly speaking, a and b serve as "parameters" in a sense that they parameterize a prior distribution, but there is no functional difference between passing a and b as data in this setting.

Ahh ok. That does clear up my query. Thanks @wouterwln.


iOS: ensure that all completion handlers have been called

Summary
This PR makes sure that all completion handlers have been called before webView navigates to other url. There is a possibility that sendAlertResult or sendConfirmResult are going to be called too late which can result in NSInternalInconsistencyException.

LGTM


main.py does not handle multiple instances properly

My bad.. I thought that StreamDeck spun up multiple processes to handle multiple instances, but it does not, I'll have to change the storage to a dictionary keyed off of the instance_context

Resolved by #2


Error 404 when running store.app

Operating System: Ubuntu 18.04 x64
Node version: v8.10.0
app-play-scraper version: v0.16.3

Description:
I am using this Library on node-js with a discord bot. It's hosted on a VPS. The bot checks for details of various apps regularly, with a gap of 10 seconds between each time store.app is ran. Recently, (starting yesterday), Error 404 responses are randomly returned when the iTunes Lookup API is used. Around 5 - 10% of the requests fail. I know that there is nothing the dev can do about it, I'm just looking to learn what could be the possible cause and if there is any fix.
 My experience is that if fails quite randomly so I was thinking about add max_attempts=1 parameter to be able to do it multiple times if 404 is encountered (so some timing will be required as well).

@TheArmKing is API responding to your query always with 404? My experience is that if fails quite randomly so I was thinking about add max_attempts=1 parameter to be able to do it multiple times if 404 is encountered (so some timing will be required as well).

Oops, seems like I forgot to mention its quite randomly returning 404 messages. I have a loop going through the same app list, and each time there are different apps that return 404. (Around 10 to 12 out of 140 returned 404). What is the default value of max_attempts?  I think it would be better to try a run a request 2 more times if it returns 404, because in some cases the app is deleted and the 404 is actually true.

@TheArmKing I have very similar issue, it is independent of the specific API call (hopefully, it means that we will have proper API one day :)). The idea with max_attempts (with default value set to 1) is mine and it should be able to fix these kind of bugs. @facundoolano what do you think about such additional parameter?

I was able to emulate something like 'max_attempts', retrying search for an app thrice with 5 second gaps (so as to not trigger the API Rate Limit). It seems to be working well, the error rate has reduced to < 1%

@TheArmKing are you going to write a PR or should I? imho the right place might be doRequest() function so it is common functionality for all interaction but I can take a deeper look at it (hopefully) in the night.

I won't be making a PR, I didn't modify any files of the library, I just made some changes in my bot's js file.

#144 has many merge conflicts and there is no reply here from the maintainer. What is the status? Will this get merged? It's been more than a year ...


Update freddierice/go-losetup

Non-trivial change as this will need a new package in debian.
See https://github.com/freddierice/go-losetup/issues/5

wrong project; oops


Small API update

Hello, I updated the API a little bit:

Keypair.public field is now private and the public key can be accessed using Keypair.public() function. Now the user can't accidentally modify public field.
You can save keys to a file and next time read it and use it using Keypair::from_bytes() function.
More secure rng can be used using Keypair::random(rng) function.

I forgot to check if there are other pull requests... Damn it


Razor Pages Tutorials: Verify if SQLite package still must be pre-loaded before EF scaffolding MacOS

Verify SQLite package still must be preloaded before running the scaffolding and if not, update the model.md tutorial to remove the pre-load by command line instruction.
Background:
For .NET 7 for the macOS instruction, the SQLite package had to be preloaded before running scaffolding.  This was a workaround added to the tutorial since the scaffolding would load the SQLite package and add it to the .csproj, but then the tooling would not find it as it started to generate the new files.
A good time to check back on this behavior would be with the GA of .NET 8, unless the dev team gives a specific fix date.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 6719f08e-3bd7-dc1a-71df-f2ef9fbca9d8
Version Independent ID: 7096fdb3-612e-9e00-bd0b-8ea4886a09ce
Content: Part 2, add a model
Content Source: aspnetcore/tutorials/razor-pages/model.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @wadepickett
Microsoft Alias: wpickett

Visual Studio for Mac preview17.6.1 build 452 released July 11th 2023 now works with .NET 8 previews, requiring the .NET 8 SDK be installed separately.  So this might be a good candidate for the next sprint.


Use BFS for shortest paths if unit weight is used

In shortest paths algorithm, detect if unit weight (i.e., all edges have weight equal to 1) is used and use simple BFS algorithm if so. Unit edge weights are represented by Unit type. For unit weights the overhead of Dijkstra's algorithm is unnecessary and thus using a straightforward BFS implementation will be more efficient.
Somewhat tricky part is how to deduce that the edge weight getter represents unit weight. We can't use std::any API, because we don't want to constrain the edge weight getter to be 'static. One possible way that I can think of now is to add a new static method to GetEdgeWeight trait called is_unit() -> bool with the default implementation returning false. The Unit type would then be the only type that would return true. This is not perfect as it can't recognize user functions that also represent a unit weight, but using such functions should be discouraged.
Do not expose BFS as a new algorithm option in Algo enum, as this should be solely an implementation detail, which covers only a niche use case.

Deducing that the weight getter represents a constant weight can be done with getter.get_const().is_some(), where get_const is an extension of GetWeight trait mentioned in #31.

Having a bfs() method on the algorithm builder that would force the BFS algorithm should be probably allowed, because using a specific algorithm is needed in cases where the type constraints of the common entrypoint are too strict. In shortest paths example, it is completely valid to run the algorithm on an implicit graph, and dijkstra() already allows that. BFS should be possible too. Calling this bfs() would only be allowed if the edge weight type is Unit.


Hopper removes modules from LaserIO Node

LaserIO version
1.2
Minecraft Version
1.18.2
Forge Version
40.1.47
Modpack & Version
Direwolf20 1.18.2 v1.5.1
Do you have optifine installed?
No
Describe the issue
A hopper under a laser node will remove the modules
Steps to reproduce
place hopper in world
place laser node above hopper
place item module in laser node
wait...
The module will be pulled out of the laser node and put into the hopper.
Expected behaviour
I expect the modules would not be removed by the hopper.
Screenshots
none
Log files
none
Additional information
I did test this in a multiplayer and single player and received the same results.

Currently LaserIO nodes are an inventory like any other - so hoppers and other pipe system can interact with them. On one hand, this adds some cool effects :). On the other, it can cause this.  At this time I don't want to remove it, but its possible I will someday.


Allow programmatically creating nested refs

Codecov Report

Merging #375 (9389a57) into master (ff892ce) will increase coverage by 0.20%.
The diff coverage is 95.83%.

@@            Coverage Diff             @@
##           master     #375      +/-   ##
==========================================
+ Coverage   66.90%   67.10%   +0.20%
==========================================
  Files          72       72
  Lines        7887     7905      +18
==========================================
+ Hits         5277     5305      +28
+ Misses       2610     2600      -10

Impacted Files
Coverage Δ

lumen/base.py
83.11% <90.90%> (+3.38%)
:arrow_up:

lumen/tests/test_pipeline.py
100.00% <100.00%> (ø)

lumen/variables/base.py
79.89% <0.00%> (+0.54%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Adjusted top bar button hover to be more noticable

I've adjusted the top bar buttons in light mode to be more noticeable when you hover over them:
Here's what hovering over the Apps button currently looks like:

And here is what it looks like with this change:

The top buttons seem to have been changed with the dark mode update. They used to only show the oval highlight when hovering:

I think the dark mode change of always showing the ovals makes sense as it lets users know that those things are clickable.


Move requires inside functions which will use the new classes

Been having issues with the CP mac app related to some of the system imports that gh_inspector brings in https://github.com/CocoaPods/CocoaPods-app/issues/376
This moves those imports to only happen during the code that needs them.

Why not use autoload instead?

Hmmmmmm, I do not know what this is (goes off to learn)

Ah, I see, I can replace require with autoload and it will only load those symbols when the first one is accessed. This makes sense, and should fix my issue.


nvidia.com/gpu: 1

If my pod is not configured with nvidia.com/gpu: 1, specific indicator values cannot be collected。 The pod must be configured with nvidia.com/gpu: 1？

Yes, Kubernetes makes certain labels available only when the pod is configured with "nvidia.com/gpu".

If the pod is configured with nvidia.com/gpu, the gpu resources are exclusively occupied by the pod (only one gpu card), and the statistics of different pods indicators for each gpu card cannot be reached

Yes, Kubernetes makes certain labels available only when the pod is configured with "nvidia.com/gpu".

The dcgm exporter can collect the memory size of each process and the gpu utilization rate of each process? I feel that I can only collect the memory size and gpu utilization of this card

Correct, dcgm exporter does not report process utilization but gpu and pod utilization.

Correct, dcgm exporter does not report process utilization but gpu and pod utilization.

Is there a good way that a GPU card can run multiple pods and collect indicators

We are looking into enhancements to better enable dcgm exporter reporting with gpu time slicing but that is still in the planning stages.


per-buffer configuration

The editorconfig project uses file-path based rules to manage editor settings, but atom only has language-scoped settings. So, editorconfig can't manage settings like trim_trailing_whitespace or insert_final_newline.

+1

+1

:+1: Per-buffer config is supported in Sublime btw.

:+1:  for per-buffer settings

Nothing has happened?

This is already solved with the atom-editorconfig package.


Request: Instagram support?

Shot in the dark, but I'll ask it: Any possible chance of either extending this (or possibly a separate project) to getting this to work with Instagram?

I want to at some point but right now I don't have the time to invest in it

Facebook video support would be nice as well

I've looked into this for one of my own projects and it's not practical. Despite facebook pushing to standardize the use of open-graph tags, they refuse to use them on their own site and make you go through their private api which requires approval. It's a pain for both instagram and facebook and im unsure if robin willing to put in the time to get approved and such

Hi, I'm currently working on this https://github.com/Wikidepia/InstaFix.
It should work but you will need an account to use it, I'm planning to host it soon™


Update debian and alpine to 9.6.7

Building a debian image with 9.6.6 doesn't work since apt repository has be updated (see http://apt.postgresql.org/pub/repos/apt/dists/jessie-pgdg/9.6/binary-amd64/)

Looks like the bot got this update in, https://github.com/docker-library/postgres/commit/165ffaab649aea0797ad61739cb5c9ac69466929 and https://github.com/docker-library/postgres/commit/7da010d82077944ce39211cc610ce58c11366360.

Yes but 6 min after me ...


Update nixpkgs input

@alejandrosame please take a look at b7a92d4. I undid your specialization. This is how I intended the function to be used.

Since these are @alejandrosame's changes (with a small tweak and PR opened not from a fork but the main repo), I'll to ahead and "self merge" once CI succeeds.


[hotfix] Update to 1.13

Will manually backport this to 2.5 until we solve the issues w/ mergify and the repo structure noted here: https://github.com/ververica/ververica-platform-playground/pull/62


Bugfix/cs1025

Addresses #1025 (RCS-358).

@tburghart Once you got all r_t modules running I'd like you to review this, as this includes a minimal S3 client implementation in Erlang.
When it comes to contradiction of proxy and SSL, I expressed my idea in the comment of 4d9b923 .

Go see #1305.


voyager_astc_8x8_unorm.ktx is missing from the asset pack

When I try to run 'multisampling' with the latest code, I get an error about a missing asset:

Could not load texture from data/models/voyager/voyager_astc_8x8_unorm.ktx

I recently reworked the mesh sample and forgot about this one. Will fix this.

Thanks. Looks good now.


Jitter based Node Synchronization algorithm is missing.

Hi,
There are couple of issues in the Node Synchronization part. They need to be addressed to make it working.
Please add support for the following:

Calculation of Jitter at PNF.
Handling of Timing Info at VNF.
vnf_handle_timing_info().

Hello Sharmar7,
Firstly thanks for the feedback. Yes you are a correct that jitter calculations and their input to the node synchronization is not implementation.  Thanks for raising the issue. The support for the jitter calculations (i.e. timestamps in the 'downlink' messages) was only added in the last review cycle of the nFAPI specification by the addition of the transmit time stamp in the P7 header in February this year, after I had make the first open-nFAPI release. Instead the initial opensource release of open-nFAPI node synchronization works with just the ul_node_sync message, which is sufficient for the simulators running on a 'controlled' network. I agree that the jitter should be added to support networks which a high level of jitter.
The support on the PNF side would mean implementing the jitter calculations from RFC 3550 which is straight forward. The complexity comes in how best to use that information on the VNF side. Any input you have or suggestions would be appreciated.
If you wish to add this functionality you have my full support.
Thank you very much for your interest. If you have any other suggestions or improvements please post them on the git hub. I would be very happy to discuss.
Thanks
Hobei


fix: allow setting the tenant when creating new periodic task

This makes it possible to add a new PeriodicTask while on a Tenant-level
admin and set the Tenant on the PeriodicTaskTenantLink correctly.
Previously, you couldn't set the Tenant because it is readonly, which then
meant that once you saved the PeriodicTask, it was on the public schema,
and therefore wouldn't show up on the Tenant's admin.

I think it would be useful to have a util something like the below, as it's used twice in the admin file and I'm sure it would be useful elsewhere too
def is_public(request):
    return request.tenant.schema_name == get_public_schema_name()


How to use the brand new models?

Hello, always thank you for all your hard work. I would like to ask how to use a VLM like Qwen2 VL-72B(Not LLM) or Nvidia/NVLM-D-72B in Ollama. When I attempt to customize the model, it fails due to an unsupported backbone. Could you advise on what steps are needed to enable support for these newer models? Thank you.

https://github.com/ollama/ollama/issues/7162
https://github.com/ollama/ollama/issues/7080

Neither Qwen2 VL, nor NVLM are supported yet. Sorry! I'll close this as a dupe.


Bump version to 1.0.0 final

Should we wait for this to land in 1-0-stable first: https://github.com/projecthydra-labs/hyrax/pull/1027 ?
cc: @jrochkind


Make driver reusable.

Move driver into tree directory.
Remove DeviceSplitCandidate.

Now GradStats is used in some places.  Will post benchmark later.

Codecov Report

Merging #6061 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6061   +/-   ##
=======================================
  Coverage   79.10%   79.10%
=======================================
  Files          12       12
  Lines        3044     3044
=======================================
  Hits         2408     2408
  Misses        636      636

Continue to review full report at Codecov.

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

Stalled.  I will approach it in a different PR.

Stalled.  I will approach it in a different PR.


cannot find module "ajv"

Describe the bug
To Reproduce
Steps to reproduce the behavior:

npm -g update @open-rpc/generator-client
pen-rpc-generator-client --version 1.0.28

open-rpc-generator-client \
  -s https://raw.githubusercontent.com/open-rpc/examples/master/service-descriptions/petstore-openrpc.json \
  PetStore
Error: added 67 packages from 417 contributors and audited 101 packages in 2.583s
found 0 vulnerabilities

><EMAIL_ADDRESS>build /Users/stev/PetStore
> tsc && typedoc --out docs

index.ts(3,17): error TS2307: Cannot find module 'ajv'.

    at exec (/Users/stev/.nodenv/versions/10.15.0/lib/node_modules/@open-rpc/generator-client/src/bootstrapGeneratedPackage.js:10:14)
    at ChildProcess.exithandler (child_process.js:301:5)
    at ChildProcess.emit (events.js:182:13)
    at maybeClose (internal/child_process.js:962:16)
    at Socket.stream.socket.on (internal/child_process.js:381:11)
    at Socket.emit (events.js:182:13)
    at Pipe._handle.close (net.js:610:12)

Expected behavior
I expected it to generator an open-rpc client.

fixed in #44


Custom Pluralize

Hello,
One of my types is "faculty". In english, I would consider the singular to be "a faculty member" so I am using faculty as both singular and plural.
I have looked into the inflection library, but there isn't a way to push strings into their "uncountable" array as it is hidden behind a closure.
How should I tell Fortune that the plural of "faculty" is "faculty", not "faculties"?

Belongs here: https://github.com/fortunejs/fortune-json-api
You want to turn off inflectType, see the readme.


Install command line issue

Hey there!
When I execute the install commande line ember install ember-states, I get the following error:
No compatible version found: ember-states@'*'
Valid install targets:
["1.13.0-beta"]

I've managed to install it anyway with this line: ember install<EMAIL_ADDRESS>But then I can't import it into an ember-cli app.
When I try to use the following import statement
`import State from 'ember-states'`

I get this error in the browser javascript console:
Could not find module `ember-states/index` imported from `ember-states`

And I can't import it with an app.import since it's located in the node_modules folder.
Is there anything I do wrong?

For those who might have the same issue, I've managed to integrate it into an ember-cli app by adding an index.js file into the addon directory of ember-states, with this content:
import StateManager from './state-manager';
import State from './state';

export default StateManager;
export {StateManager, State};

I'm then able to use that import statement from my app:
`import StateManager from 'ember-states'`
`import {State} from 'ember-states'`

I don't know if it's a right way to do this, so any comment is welcome.

+1 for resolution


[libconfig] CMake support

Is your feature request related to a problem? Please describe.
vcpkg install libconfig does not set up any CMake targets. Instead, it outputs a suggestion to add --head to get CMake support.
vcpkg install libconfig --head sets up CMake targets that don't work. It suggests to use target_link_libraries(main PRIVATE libconfig::config libconfig::config++), which would probably be correct - except that the included CMake configuration only sets up one of those two library targets, and trying to use the only one that gets set up results in unresolved references at link time.
Proposed solution
Ensure that CMake import targets get created for both libraries included in the build.
Describe alternatives you've considered
No response
Additional context
Using triplet x64-mingw-static

libconfig provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(libconfig CONFIG REQUIRED)
    target_link_libraries(main PRIVATE libconfig::libconfig libconfig::libconfig++

Could  you please provide a simple cmake example to verify if the usage is correctly linked to these two libraries: libconfig, libconfig++.

Example CMakeLists.txt - note that the linker order is reversed from vcpkg's suggestion, which seems to be required for successful static linking:
cmake_minimum_required(VERSION 3.26.3)

project(configTest LANGUAGES CXX)

# use config mode to prefer vcpkg versions
find_package(libconfig CONFIG REQUIRED)

add_executable(${PROJECT_NAME}
  main.cpp
)
target_link_libraries(${PROJECT_NAME} PRIVATE libconfig::libconfig++ libconfig::libconfig)

Example main.cpp:
#include <libconfig.h++>

int main(int argc, char* argv[])
{
  libconfig::Config cfg;

  return 0;
}

Current output from my working MSYS MinGW + VSCode + cmake-tools + vcpkg environment on Windows 11:
[main] Building folder: libconfigTest
[main] Configuring project: libconfigTest
[proc] Executing command: C:\msys64\mingw64\bin\cmake.EXE --no-warn-unused-cli -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_INSTALL_PREFIX:STRING=C:/msys64/home/bensh/projects/rustLaunchSite/install -DCMAKE_C_COMPILER:FILEPATH=C:/msys64/mingw64/bin/gcc.exe -DCMAKE_CXX_COMPILER:FILEPATH=C:/msys64/mingw64/bin/g++.exe -DCMAKE_TOOLCHAIN_FILE:FILEPATH=C:/msys64/opt/vcpkg/scripts/buildsystems/vcpkg.cmake -SC:/msys64/home/bensh/projects/libconfigTest -Bc:/msys64/home/bensh/projects/libconfigTest/build -G "MinGW Makefiles"
[cmake] Not searching for unused variables given on the command line.
[cmake] CMake Error at C:/msys64/opt/vcpkg/scripts/buildsystems/vcpkg.cmake:854 (_find_package):
[cmake]   Could not find a package configuration file provided by "libconfig" with
[cmake]   any of the following names:
[cmake]
[cmake]     libconfigConfig.cmake
[cmake]     libconfig-config.cmake
[cmake]
[cmake]   Add the installation prefix of "libconfig" to CMAKE_PREFIX_PATH or set
[cmake]   "libconfig_DIR" to a directory containing one of the above files.  If
[cmake]   "libconfig" provides a separate development package or SDK, be sure it has
[cmake]   been installed.
[cmake] Call Stack (most recent call first):
[cmake]   CMakeLists.txt:6 (find_package)
[cmake]
[cmake]
[cmake] -- Configuring incomplete, errors occurred!
[proc] The command: C:\msys64\mingw64\bin\cmake.EXE --no-warn-unused-cli -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_INSTALL_PREFIX:STRING=C:/msys64/home/bensh/projects/rustLaunchSite/install -DCMAKE_C_COMPILER:FILEPATH=C:/msys64/mingw64/bin/gcc.exe -DCMAKE_CXX_COMPILER:FILEPATH=C:/msys64/mingw64/bin/g++.exe -DCMAKE_TOOLCHAIN_FILE:FILEPATH=C:/msys64/opt/vcpkg/scripts/buildsystems/vcpkg.cmake -SC:/msys64/home/bensh/projects/libconfigTest -Bc:/msys64/home/bensh/projects/libconfigTest/build -G "MinGW Makefiles" exited with code: 1

I've searched my vcpkg install tree, and found that there are simply no *.cmake files installed for my x64-mingw-dynamic or x64-mingw-static libconfig installs, so I'm not sure why the vcpkg install process is even suggesting it:
$ vcpkg list
curl:x64-mingw-dynamic                            8.0.1               A library for transferring data with URLs
curl:x64-mingw-static                             8.0.1               A library for transferring data with URLs
curl[non-http]:x64-mingw-dynamic                                      Enables protocols beyond HTTP/HTTPS/HTTP2
curl[non-http]:x64-mingw-static                                       Enables protocols beyond HTTP/HTTPS/HTTP2
curl[schannel]:x64-mingw-dynamic                                      SSL support (Secure Channel)
curl[schannel]:x64-mingw-static                                       SSL support (Secure Channel)
curl[ssl]:x64-mingw-dynamic                                           Default SSL backend
curl[ssl]:x64-mingw-static                                            Default SSL backend
curl[sspi]:x64-mingw-dynamic                                          SSPI support
curl[sspi]:x64-mingw-static                                           SSPI support
egl-registry:x64-mingw-dynamic                    2022-09-20          the EGL API and Extension Registry
glad:x64-mingw-dynamic                            0.1.36              Multi-Language Vulkan/GL/GLES/EGL/GLX/WGL Loader...
glad[loader]:x64-mingw-dynamic                                        Generate loader logic.
ixwebsocket:x64-mingw-dynamic                     11.4.3              Lightweight WebSocket Client and Server + HTTP C...
ixwebsocket:x64-mingw-static                      11.4.3              Lightweight WebSocket Client and Server + HTTP C...
ixwebsocket[mbedtls]:x64-mingw-dynamic                                SSL support (mbedTLS)
ixwebsocket[mbedtls]:x64-mingw-static                                 SSL support (mbedTLS)
ixwebsocket[ssl]:x64-mingw-dynamic                                    Default SSL backend
ixwebsocket[ssl]:x64-mingw-static                                     Default SSL backend
libconfig:x64-mingw-dynamic                       1.7.3#2             C/C++ library for processing configuration files
libconfig:x64-mingw-static                        1.7.3#2             C/C++ library for processing configuration files
libtcod:x64-mingw-dynamic                         1.23.1              Common algorithms and tools for roguelikes.
libtcod[png]:x64-mingw-dynamic                                        Support for reading and writing PNG files. Requi...
libtcod[sdl]:x64-mingw-dynamic                                        Support for SDL2 windows and events with the lib...
libtcod[unicode]:x64-mingw-dynamic                                    Support for non-ASCII characters. Required for t...
libtcod[zlib]:x64-mingw-dynamic                                       Support for REXPaint files and TCODZip archives.
lodepng-c:x64-mingw-dynamic                       deprecated          Legacy port. Use port lodepng instead.
lodepng:x64-mingw-dynamic                         2021-12-04#1        PNG encoder and decoder in C++
mbedtls:x64-mingw-dynamic                         2.28.1              An open source, portable, easy to use, readable ...
mbedtls:x64-mingw-static                          2.28.1              An open source, portable, easy to use, readable ...
nlohmann-json:x64-mingw-dynamic                   3.11.2              JSON for Modern C++
nlohmann-json:x64-mingw-static                    3.11.2              JSON for Modern C++
opengl-registry:x64-mingw-dynamic                 2022-09-29#1        the API and Extension registries for the OpenGL ...
pugixml:x64-mingw-static                          1.13.0              Light-weight, simple and fast XML parser for C++...
reproc:x64-mingw-dynamic                          14.2.4#1            Cross-platform (C99/C++11) process library
reproc:x64-mingw-static                           14.2.4#1            Cross-platform (C99/C++11) process library
sdl2:x64-mingw-dynamic                            2.26.5              Simple DirectMedia Layer is a cross-platform dev...
sdl2[base]:x64-mingw-dynamic                                          Base functionality for SDL
stb:x64-mingw-dynamic                             2023-04-11#1        public domain header-only libraries
tiny-process-library:x64-mingw-dynamic            2.0.4#2             A small platform independent library to create a...
tiny-process-library:x64-mingw-static             2.0.4#2             A small platform independent library to create a...
utf8proc:x64-mingw-dynamic                        2.7.0#1             Clean C library for processing UTF-8 Unicode data.
vcpkg-cmake-config:x64-mingw-dynamic              2022-02-06#1
vcpkg-cmake-config:x64-mingw-static               2022-02-06#1
vcpkg-cmake:x64-mingw-dynamic                     2022-12-22
vcpkg-cmake:x64-mingw-static                      2022-12-22
yaml-cpp:x64-mingw-dynamic                        0.7.0#1             yaml-cpp is a YAML parser and emitter in C++ mat...
zlib:x64-mingw-dynamic                            1.2.13              A compression library
zlib:x64-mingw-static                             1.2.13              A compression library

$ find /opt/vcpkg/installed -name '*.cmake'
/opt/vcpkg/installed/x64-mingw-dynamic/share/curl/CURLConfig.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/curl/CURLConfigComponents.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/curl/CURLConfigVersion.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/curl/CURLTargets-debug.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/curl/CURLTargets-release.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/curl/CURLTargets.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/curl/vcpkg-cmake-wrapper.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/glad/gladConfig.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/glad/gladConfigVersion.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/glad/gladTargets-debug.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/glad/gladTargets-release.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/glad/gladTargets.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/ixwebsocket/ixwebsocket-config.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/ixwebsocket/ixwebsocket-targets-debug.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/ixwebsocket/ixwebsocket-targets-release.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/ixwebsocket/ixwebsocket-targets.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/libtcod/libtcodConfig.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/libtcod/libtcodConfigVersion.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/libtcod/libtcodTargets-debug.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/libtcod/libtcodTargets-release.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/libtcod/libtcodTargets.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/lodepng/lodepng-config.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/lodepng/lodepng-targets-debug.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/lodepng/lodepng-targets-release.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/lodepng/lodepng-targets.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/lodepng-c/lodepng-c-config.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/lodepng-c/lodepng-c-targets-debug.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/lodepng-c/lodepng-c-targets-release.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/lodepng-c/lodepng-c-targets.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/nlohmann_json/nlohmann_jsonConfig.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/nlohmann_json/nlohmann_jsonConfigVersion.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/nlohmann_json/nlohmann_jsonTargets.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/reproc/reproc-config-version.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/reproc/reproc-config.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/reproc/reproc-targets-debug.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/reproc/reproc-targets-release.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/reproc/reproc-targets.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/reproc++/reproc++-config-version.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/reproc++/reproc++-config.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/reproc++/reproc++-targets-debug.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/reproc++/reproc++-targets-release.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/reproc++/reproc++-targets.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/sdl2/SDL2Config.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/sdl2/SDL2ConfigVersion.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/sdl2/SDL2mainTargets-debug.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/sdl2/SDL2mainTargets-release.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/sdl2/SDL2mainTargets.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/sdl2/SDL2Targets-debug.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/sdl2/SDL2Targets-release.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/sdl2/SDL2Targets.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/stb/FindStb.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/stb/vcpkg-cmake-wrapper.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/tiny-process-library/tiny-process-library-config-debug.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/tiny-process-library/tiny-process-library-config-release.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/tiny-process-library/tiny-process-library-config.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/unofficial-utf8proc/unofficial-utf8proc-config-debug.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/unofficial-utf8proc/unofficial-utf8proc-config-release.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/unofficial-utf8proc/unofficial-utf8proc-config.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/vcpkg-cmake/vcpkg-port-config.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/vcpkg-cmake/vcpkg_cmake_build.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/vcpkg-cmake/vcpkg_cmake_configure.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/vcpkg-cmake/vcpkg_cmake_install.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/vcpkg-cmake-config/vcpkg-port-config.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/vcpkg-cmake-config/vcpkg_cmake_config_fixup.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/yaml-cpp/yaml-cpp-config-version.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/yaml-cpp/yaml-cpp-config.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/yaml-cpp/yaml-cpp-targets-debug.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/yaml-cpp/yaml-cpp-targets-release.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/yaml-cpp/yaml-cpp-targets.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/zlib/vcpkg-cmake-wrapper.cmake
/opt/vcpkg/installed/x64-mingw-static/share/curl/CURLConfig.cmake
/opt/vcpkg/installed/x64-mingw-static/share/curl/CURLConfigComponents.cmake
/opt/vcpkg/installed/x64-mingw-static/share/curl/CURLConfigVersion.cmake
/opt/vcpkg/installed/x64-mingw-static/share/curl/CURLTargets-debug.cmake
/opt/vcpkg/installed/x64-mingw-static/share/curl/CURLTargets-release.cmake
/opt/vcpkg/installed/x64-mingw-static/share/curl/CURLTargets.cmake
/opt/vcpkg/installed/x64-mingw-static/share/curl/vcpkg-cmake-wrapper.cmake
/opt/vcpkg/installed/x64-mingw-static/share/ixwebsocket/ixwebsocket-config.cmake
/opt/vcpkg/installed/x64-mingw-static/share/ixwebsocket/ixwebsocket-targets-debug.cmake
/opt/vcpkg/installed/x64-mingw-static/share/ixwebsocket/ixwebsocket-targets-release.cmake
/opt/vcpkg/installed/x64-mingw-static/share/ixwebsocket/ixwebsocket-targets.cmake
/opt/vcpkg/installed/x64-mingw-static/share/nlohmann_json/nlohmann_jsonConfig.cmake
/opt/vcpkg/installed/x64-mingw-static/share/nlohmann_json/nlohmann_jsonConfigVersion.cmake
/opt/vcpkg/installed/x64-mingw-static/share/nlohmann_json/nlohmann_jsonTargets.cmake
/opt/vcpkg/installed/x64-mingw-static/share/pugixml/pugixml-config-version.cmake
/opt/vcpkg/installed/x64-mingw-static/share/pugixml/pugixml-config.cmake
/opt/vcpkg/installed/x64-mingw-static/share/pugixml/pugixml-targets-debug.cmake
/opt/vcpkg/installed/x64-mingw-static/share/pugixml/pugixml-targets-release.cmake
/opt/vcpkg/installed/x64-mingw-static/share/pugixml/pugixml-targets.cmake
/opt/vcpkg/installed/x64-mingw-static/share/reproc/reproc-config-version.cmake
/opt/vcpkg/installed/x64-mingw-static/share/reproc/reproc-config.cmake
/opt/vcpkg/installed/x64-mingw-static/share/reproc/reproc-targets-debug.cmake
/opt/vcpkg/installed/x64-mingw-static/share/reproc/reproc-targets-release.cmake
/opt/vcpkg/installed/x64-mingw-static/share/reproc/reproc-targets.cmake
/opt/vcpkg/installed/x64-mingw-static/share/reproc++/reproc++-config-version.cmake
/opt/vcpkg/installed/x64-mingw-static/share/reproc++/reproc++-config.cmake
/opt/vcpkg/installed/x64-mingw-static/share/reproc++/reproc++-targets-debug.cmake
/opt/vcpkg/installed/x64-mingw-static/share/reproc++/reproc++-targets-release.cmake
/opt/vcpkg/installed/x64-mingw-static/share/reproc++/reproc++-targets.cmake
/opt/vcpkg/installed/x64-mingw-static/share/tiny-process-library/tiny-process-library-config-debug.cmake
/opt/vcpkg/installed/x64-mingw-static/share/tiny-process-library/tiny-process-library-config-release.cmake
/opt/vcpkg/installed/x64-mingw-static/share/tiny-process-library/tiny-process-library-config.cmake
/opt/vcpkg/installed/x64-mingw-static/share/vcpkg-cmake/vcpkg-port-config.cmake
/opt/vcpkg/installed/x64-mingw-static/share/vcpkg-cmake/vcpkg_cmake_build.cmake
/opt/vcpkg/installed/x64-mingw-static/share/vcpkg-cmake/vcpkg_cmake_configure.cmake
/opt/vcpkg/installed/x64-mingw-static/share/vcpkg-cmake/vcpkg_cmake_install.cmake
/opt/vcpkg/installed/x64-mingw-static/share/vcpkg-cmake-config/vcpkg-port-config.cmake
/opt/vcpkg/installed/x64-mingw-static/share/vcpkg-cmake-config/vcpkg_cmake_config_fixup.cmake
/opt/vcpkg/installed/x64-mingw-static/share/zlib/vcpkg-cmake-wrapper.cmake

As a workaround, I currently use this large pile of goop in my CMakeLists.txt to manually set up import targets for both dynamic and static flavors:
find_library(LIBCONFIG_LIB libconfig REQUIRED)
find_library(LIBCONFIG_IMPLIB "liblibconfig.dll.a")
find_library(LIBCONFIGPP_LIB libconfig++ REQUIRED)
find_library(LIBCONFIGPP_IMPLIB "liblibconfig++.dll.a")
if(VCPKG_TARGET_TRIPLET MATCHES ".*static.*")
  message("RLS: Configuring for static linking")
  add_library(libconfig STATIC IMPORTED)
  add_library(libconfig++ STATIC IMPORTED)
else()
  message("RLS: Configuring for dynamic linking")
  add_library(libconfig SHARED IMPORTED)
  if(DEFINED LIBCONFIG_IMPLIB)
    set_property(TARGET libconfig PROPERTY IMPORTED_IMPLIB "${LIBCONFIG_IMPLIB}")
  endif()
  add_library(libconfig++ SHARED IMPORTED)
  if(DEFINED LIBCONFIGPP_IMPLIB)
    set_property(TARGET libconfig++ PROPERTY IMPORTED_IMPLIB "${LIBCONFIGPP_IMPLIB}")
  endif()
endif()
set_property(TARGET libconfig PROPERTY IMPORTED_LOCATION "${LIBCONFIG_LIB}")
set_property(TARGET libconfig++ PROPERTY IMPORTED_LOCATION "${LIBCONFIGPP_LIB}")

From the logs you provided, it can be seen that vcpkg does not provide the cmake config file libconfigConfig.cmake for libconfig. Therefore, find_package(libconfig CONFIG REQUIRED) cannot be used.

Hold on: You yourself demonstrated that vcpkg says "libconfig provides
CMake targets", but now you're suggesting that it's okay that it then does
not.
Either vcpkg should provide CMake support for this library, or it should
avoid falsely stating that it does.
Clearly something is broken here, and that's what I'm trying to get support
with.
On Tue, Apr 18, 2023, 1:14 AM Frank @.***> wrote:

From the logs you provided, it can be seen that vcpkg does not provide
the cmake config file libconfigConfig.cmake for libconfig. Therefore, find_package(libconfig
CONFIG REQUIRED) cannot be used.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vcpkg/issues/30906#issuecomment-1512654876,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA2TC24WBQ3GCOQTVUAWKTXBZEPBANCNFSM6AAAAAAXAJKVCU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Okay, there are a number of things going on here.
First, I forgot to switch back to the --head version (not even sure what that's about honestly).
Second, I got the CMake target name wrong for the C flavor of the library - it's libconfig::config. Note a couple of weird things:

The target name does not match the package name.
The target name does not match what you posted in your install output.
The target names in my install output do not match those in your install output (did something change in the last day?):

libconfig provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(libconfig CONFIG REQUIRED)
    target_link_libraries(main PRIVATE libconfig::config libconfig::config++)

Now that leaves us with one issue: vcpkg does install libconfig++ CMake config files for the C++ flavor of the library, but they don't work.
Here's my find result, which clearly shows libconfig++Config*.cmake files:
$ find /opt/vcpkg/installed/ -iname '*libconfig*.cmake'
/opt/vcpkg/installed/x64-mingw-dynamic/share/libconfig/libconfig++Config-debug.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/libconfig/libconfig++Config-release.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/libconfig/libconfig++Config.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/libconfig/libconfig++ConfigVersion.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/libconfig/libconfigConfig-debug.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/libconfig/libconfigConfig-release.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/libconfig/libconfigConfig.cmake
/opt/vcpkg/installed/x64-mingw-dynamic/share/libconfig/libconfigConfigVersion.cmake
/opt/vcpkg/installed/x64-mingw-static/share/libconfig/libconfig++Config-debug.cmake
/opt/vcpkg/installed/x64-mingw-static/share/libconfig/libconfig++Config-release.cmake
/opt/vcpkg/installed/x64-mingw-static/share/libconfig/libconfig++Config.cmake
/opt/vcpkg/installed/x64-mingw-static/share/libconfig/libconfig++ConfigVersion.cmake
/opt/vcpkg/installed/x64-mingw-static/share/libconfig/libconfigConfig-debug.cmake
/opt/vcpkg/installed/x64-mingw-static/share/libconfig/libconfigConfig-release.cmake
/opt/vcpkg/installed/x64-mingw-static/share/libconfig/libconfigConfig.cmake
/opt/vcpkg/installed/x64-mingw-static/share/libconfig/libconfigConfigVersion.cmake

Here's what happens if I add find_package(libconfig++ CONFIG REQUIRED)  to my CMakeLists.txt:
[cmake] -- find_package(libconfig++ CONFIG REQUIRED)
[cmake] CMake Error at C:/msys64/opt/vcpkg/scripts/buildsystems/vcpkg.cmake:852 (_find_package):
[cmake]   Could not find a package configuration file provided by "libconfig++" with
[cmake]   any of the following names:
[cmake]
[cmake]     libconfig++Config.cmake
[cmake]     libconfig++-config.cmake
[cmake]
[cmake]   Add the installation prefix of "libconfig++" to CMAKE_PREFIX_PATH or set
[cmake]   "libconfig++_DIR" to a directory containing one of the above files.  If
[cmake]   "libconfig++" provides a separate development package or SDK, be sure it
[cmake]   has been installed.
[cmake] Call Stack (most recent call first):
[cmake]   CMakeLists.txt:9 (find_package)
[cmake]
[cmake]
[cmake] -- Configuring incomplete, errors occurred!

[cmake] -- find_package(libconfig++ CONFIG REQUIRED)
[cmake] CMake Error at C:/msys64/opt/vcpkg/scripts/buildsystems/vcpkg.cmake:852 (_find_package):
[cmake]   Could not find a package configuration file provided by "libconfig++" with
[cmake]   any of the following names:
[cmake]
[cmake]     libconfig++Config.cmake
[cmake]     libconfig++-config.cmake
[cmake]
[cmake]   Add the installation prefix of "libconfig++" to CMAKE_PREFIX_PATH or set
[cmake]   "libconfig++_DIR" to a directory containing one of the above files.  If
[cmake]   "libconfig++" provides a separate development package or SDK, be sure it
[cmake]   has been installed.
[cmake] Call Stack (most recent call first):
[cmake]   CMakeLists.txt:9 (find_package)
[cmake]
[cmake]
[cmake] -- Configuring incomplete, errors occurred!
Note that CMake calls out libconfig++Config.cmake, which exists in the find output above!
...also, if I were to trust the vcpkg install output and just find_package(libconfig CONFIG REQUIRED) and assume that it defines both targets, I get this:
[cmake] -- find_package(libconfig CONFIG REQUIRED)
[cmake] -- Configuring done (0.1s)
[cmake] CMake Error at CMakeLists.txt:14 (target_link_libraries):
[cmake]   Target "configTest" links to:
[cmake]
[cmake]     libconfig::config++
[cmake]
[cmake]   but the target was not found.  Possible reasons include:
[cmake]
[cmake]     * There is a typo in the target name.
[cmake]     * A find_package call is missing for an IMPORTED target.
[cmake]     * An ALIAS target is missing.
[cmake]
[cmake]
[cmake]
[cmake] -- Generating done (0.0s)
[cmake] CMake Generate step failed.  Build files cannot be regenerated correctly.

Something is broken here. Why is vcpkg installing libconfig++ CMake files that don't work?

@HunterZ
I have tried it locally, and it seems that the upstream has exported two sets of cmake config files for libconfig and libconfig++, but the namespace of the targets is incorrect. I will fix this today and submit a PR to the upstream. :)
CMakeLists.txt:
cmake_minimum_required(VERSION 3.0)
project(test)
add_executable(main main.cpp)
find_package(libconfig CONFIG REQUIRED)
target_link_libraries(main PRIVATE libconfig::libconfig libconfig::libconfig++)

Error:
CMake Error at CMakeLists.txt:5 (target_link_libraries):
  Target "main" links to:

    libconfig::libconfig++

  but the target was not found.  Possible reasons include:

    * There is a typo in the target name.
    * A find_package call is missing for an IMPORTED target.
    * An ALIAS target is missing.

https://github.com/hyperrealm/libconfig/blob/4f13b7f5152427b5e511a09617ca2d9ff63f7800/lib/CMakeLists.txt#L150

but the namespace of the targets is incorrect.

How is it incorrect?
Did anybody try with CMAKE_FIND_DEBUG_MODE enabled?

Maybe this is just due to the limitations of the usage heuristics?
AFAIU CMake config is installed correctly, but not reported correctly. Usage should be
libconfig provides CMake targets:

    # C API
    find_package(libconfig CONFIG REQUIRED)
    target_link_libraries(main PRIVATE libconfig::libconfig)

    # C++ API
    find_package(libconfig++ CONFIG REQUIRED)
    target_link_libraries(main PRIVATE libconfig::libconfig++)

with no other fixes needed.
i.e. you must call find_package(libconfig++) if you want to use the C++ API.

with no other fixes needed. i.e. you must call find_package(libconfig++) if you want to use the C++ API.

Please refer to my last comment, where I stated the following and demonstrated how it also fails:

Here's what happens if I add find_package(libconfig++ CONFIG REQUIRED) to my CMakeLists.txt:

Yes, I realized that already in https://github.com/microsoft/vcpkg/pull/30980#issuecomment-1515815295.

Stale bots are extremely user hostile. I am going to unsubscribe from this issue because I strongly dislike the undue burden that this places on issue reporters to keep issues in front of developers.

@HunterZ The reminder also goes to subscribed maintainers and contributors. The bot pinging twice a year seems a fair frequence.

vcpkg install libconfig does not set up any CMake targets. Instead, it outputs a suggestion to add --head to get CMake support.
vcpkg install libconfig --head sets up CMake targets that don't work. It suggests to use target_link_libraries(main PRIVATE libconfig::config libconfig::config++), which would probably be correct - except that the included CMake configuration only sets up one of those two library targets, and trying to use the only one that gets set up results in unresolved references at link time.

This is strange. Upstream does install cmake config for 1.7.3. The port update to that version just didn't properly cleanup the legacy vendored CMake build.
Nevertheless, there is a problem with the libconfig++ config, and upstream isn't responsive.

@FrankXie05 : I'm getting compile errors in my project using x64-windows-static version of libconfig++ since port version 4, when everything worked fine in version 3 :

Do you want me to create a specific issue regarding this problem ?

@rtoumazet
It's better to open a new issue. :)


[request] No breaking changes between minor version bumps

Hey @willmcgugan, thanks for the hard work on this library!
I have wow'd my co-workers with it.
I'd like to request that breaking changes produce a major version bump.
The specific regression I ran into was introduced in release v1.2.0 when __console__ was replaced with __rich_console__.
Thanks again!

I'll adhere to semver in future. Sorry about that, I had assumed nobody was yet using the console protocol. Glad somebody is reading the docs!


Basestring

Hi,
I get the error message: " Base string is not defined". I don't know how I should define it, can someone help me please?

Python 3 doesn't have basesting, replace it using str(Maybe, you can check)


Documentation refactor

This commit includes new documentation
for newcomers.

thanks for the Carlos,
the way to extend topsail will change soon when I merge https://github.com/openshift-psap/topsail/pull/114 and the similar PRs that will come, I think we should delay this PR until the refactoring is done, or at least stabilized

thanks @ccamacho , I merge this PR, I will work on top of it


Hub: Move hash-wasm into vendor (emscripten)

Resolves #221
In this PR, I moved source code of hash-wasm into vendor directory (c source code), also add compile script using emscripten. As a bonus, SIMD is also enabled, which should allow better performance.
I also added sha256-wrapper.ts as a thin wrapper for the compiled wasm module.

createSHA256 create the wasm module, works just like before.
createSHA256WorkerCode this function use Function.toString() trick to copy the module code into worker. This trick is already used in one of my project, wllama, so it should work on Firefox/Chrome/Safari (but feel free to test it further)

I published the package with tag wasm: npm add @hugginface/hub@wasm
I added some E2Es with Svelte and vite-build, which work great.
But then I tried including the file directly from a CDN: https://huggingface.co/spaces/coyotte508/hub-sha256

When loading the unbundled dist file from https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>, I get a different sha 256
When loading the bundled file from https://esm.sh/<EMAIL_ADDRESS>or https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>, I get an error when accessing a minified variable

Reference links:

https://huggingface.co/spaces/coyotte508/push-model-from-web/blob/main/index.html#L9 import map
https://huggingface.co/spaces/coyotte508/hub-sha256/blob/main/app.js test of different modules

That said, I'm very happy with this PR :)

When loading the unbundled dist file from https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>, I get a different sha 256

After having a deeper look, turns out I made a silly mistake: Signature of TypedArray.subarray should be (start, end), but I thought it was (offset, length), see: https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Global_Objects/TypedArray/subarray
It should be fixed in the last commit.

Just for fun, I also do a benchmark. Seems like we're gaining 20% performance: https://gist.github.com/ngxson/dfb4735e2f43b1b8b5d0c16113e84145

Function
Time milisecs

hashBrowser
839.6666666666666

hashWasmOld
3146

hashWasmNew
2661.3333333333335

Seems problems are fixed :)

Nice, thanks again for your help - that motivates me a lot. Feel free to merge (or to further test it) if you want. Bon weekend !


Update optim

Closes #194
The changes are:

The function now includes a progress bar
The function now avoids including the model state into the compiled functions

@GianmarcoCallegher yesterday, I found some more issues, so I converted the PR back to a draft and fixed them. It is now ready for review. The issues concerned:

The implementation of early stopping contained a thinko. I had compared the current loss to the best loss within the patience periord. Now I compared the oldest loss in the patience period to the best loss within the patience period.
The iteration counter and index handling was off by one. Now, iteration 0 refers to the initial values. Previously it referred to the values after the first update.

@jobrachem I saw new commits. Is it ready for the review?

@GianmarcoCallegher Yes :)

Well done 😄


MinMaxIndex::read may throw exception  if index_file_size  is 1048592

https://github.com/pingcap/tiflash/blob/c7510734bf6b57a072e3c67ee602c183440aa990/dbms/src/Storages/DeltaMerge/File/DMFilePackFilter.h#L257
frame_total_size should be ChecksumFrameLength + header_size. If index_file_size  is 1048592 (16 + 1048576, 1048576 is the frame length), MinMaxIndex::read will throw exception because bytes_read != bytes_limit.

Another related issue: https://github.com/pingcap/tiflash/issues/4778


allow enableRaytracing UI toggle and config option

This commit allows the enableRaytracing toggle and configuration option to be exposed regardless of build setting. This follows on a internal discussion about comparisons. Please also see the linked issue #213 regarding this change, as a debugOptimized build will need further optimizations to remain truly "optimized" for general use, especially for the vulkan validation layers setting. it looks like meson may also need to be updated to reflect a debugoptimized build selection.

This change is fine in principle, however we need a mechanism to disable the UI toggle for specific games based on a (separate) config entry.
Modders may want to do engine-side changes to suit the game to Remix, whether config tweaks, e.g., disabling culling altogether, or engine-side changes if source is available. Some of these may break the non-RT mode or make it largely unusable. We'd like to let modders ship a config file with their mod that removes this option from the UI if it's known to be broken on that specific mod, to avoid noise/bug reports around that.
@watbulb would you like to make that change?

@nsubtil I can take a look at making said change next week. I've been away for work and haven't been too up to date on progress, but I'd be happy to dip my toes back in next week as I have some downtime.
I agree it should be configurable, I think I will brainstorm a couple ways to provide the config file, format, and how it will be parsed as part of the module.
Thanks for commenting <3

Thanks!
Note that we already have functionality to add a setting that is read from the config file. You should be able to declare a new setting using the RTX_OPTION macro (or one of the other variants if applicable) and the config file parser will pick it up.

REMIX-1878 for tracking.


@iwsio/json-csv-core/types does not exist

Getting this error when transpiling with tsc
node_modules/@iwsio/json-csv-node/dist/exporter.d.cts:3:36 - error TS2307: Cannot find module '@iwsio/json-csv-core/types' or its corresponding type declarations.

import type { ExportOptions } from '@iwsio/json-csv-core/types';
                                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

It seems like installing @iwsio/json-csv-core does not work either

Looks like the path should be
import type { ExportOptions } from '@iwsio/json-csv-core/dist/types

Just seeing this. I'll check it out! Thanks @khuynhepi

@khuynhepi I see what's going on. This is due to your tsconfig.json likely using moduleResolution: 'Node' instead of Node16 or NodeNext. The difference between Node and the others is that Node16 and newer will use the package.json exports prop to map subpaths to modules on disk. The type import pattern is by convention too, so when you import @iwsio/json-csv-core/exporter, Typescript will resolve the module at the path: ./dist/exporter.js and its matching type definitions ./dist/exporter.d.ts.
TL'DR: If you're using moduleResolution: "Node", you need to use the relative path from the root of the module.  If you're using Node16 or NodeNext, it supports sub-path exports.
Options:

Switching to Node16 should get you most of the module resolution behavior you're used to and support for the sub-path export.
Keeping Node just means you have to import the disk module. Typescript should see types adjacent to it on disk.

More info at https://www.typescriptlang.org/tsconfig/#moduleResolution

Also, just FYI, there were some weird resolution issues between ESlint and Typescript. I'm shoring up the config in the next PR. #61

thanks @nathanb. I was able to successfully transpile. However, I am still unsure on the eslint issue you are talking about.
  8:31  error  Unable to resolve path to module '@iwsio/json-csv-core/types'  import/no-unresolved

ahh seems like adding
  "settings": {
    "import/resolver": {
      "typescript": {}
    }
  }

did it

Awesome! Great work!


ExternalSourceAspect.scope should be RelatedElement | undefined

Describe the bug
In ExternalSourceAspect class scope is always defined, but real iModels sometimes external source aspects may have it as undefined
Expected behavior
ExternalSourceAspect.scope should have type of RelatedElement | undefined

@simsta6, whats the severity of this issue? Do you need a fix for this now, or is this something that can wait until 5.0. Due to this being a breaking change, if this were to be done now it would require implementing a new scope property and deprecating the old one (or something similar), but I cannot directly change scope to optional in 4.x.x


Support for Hitachi RAS-35YHA (RAC-35YHA), RAS-25YHA (RAC-25YHA)

Support for Hitachi RAS-35YHA, RAS-25YHA (and possibly others in same series).
These Hitachi models have 4 fan speeds plus Auto.
These Hitachi models are reverse cycle, inverters with Heat, Cool, Dry, Fan Only and a "Auto Comfort Mode"
Operational Temp for Heat and Cool is 16 degrees to 32 degrees Celsius.
Note: Although the other Hitachi files do also work with these models, they do not contain all the features (extra fan speeds and extra modes).
This code file allows operation of the following:
Operational Modes:

Heat
Cool
Dry
Fan Only

Fan Modes:

High
Med
Low
Quiet
Auto

Caveats:

Auto mode is not included as this is a "Comfort Feel" setting with no temperature setting
Dry Mode only has two fan speeds, Quiet and Low, on the original remote.  I have copied the
"Quiet" setting to Quiet and Low speeds, with "Low" setting on Med, High and Auto so as to
allow operation in any mode
Fan Only: This does not support Auto Fan in Fan Only and no codes are in the "Auto" section
for Fan Only mode.

Edit: Codes were captured from Original remote control and tested in real life use.
HitRAS35.json.txt

Amazing job. Thanks


[request] CEX.io Live Trading and Backtest importing support.

Note: for support questions, please join our Discord server

I'm submitting a ...
[ ] bug report
[x] feature request
[ ] question about the decisions made in the repository

Action taken (what you did)

Looked at Supported Exchanges list and found CEX.io only listed with live monitoring support.

Expected result (what you hoped would happen)

Since CEX.io seems to be the only exchange with 0% maker fee, it seems only logical to add live trading and importing for backtesting.

Actual result (unexpected outcome)

CEX.io have no Live trading or importing for backing testing support.

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)

https://cex.io/cex-api

Very open to a PR! I won't have time for this.


fixed broken link

Description of the change: fixed broken link to docs page

Hello @StrikerRUS,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Resource specified colors are removed

There are some cases where resource specified colors like @color\foo are removed from color properties.

I was inspecting processed files with shapeshifter and didn't see color. It didn't occur to me that shapeshifter doesn't know of other resources.


Refactor shader node setup

Preferably using a blend file shipped with sollumz and each shader node layout and nodes already setup using custom node groups

Some ongoing work in dev/shader-expressions branch. The aim is to define shaders by building a kind of AST through normal python expressions and function calls that somewhat resemble a shading language. Then this AST can be "compiled" to a shader node tree. This should simplify editing existing shaders and creating new ones as we would not have to care about manually creating nodes and linking them, which takes a lot of code for what is in reality very simple shader code.
Another benefit is that the shader definitions would stay as plain-text code, simple to version control compared to a binary .blend file.

dev/shader-expressions is merged now. Most materials still don't use it but we will be slowly migrating them (#1007, 124350d3a632258a8336370bfa5dd3aa85790898, dev/ynv-qol branch, etc.). Any new material generation code should be using shader expressions from now on.