Records

This branch substitute the input and output ports by only one input and one output using self-generated records. The script takes care of the connections between ports and internal registers, independent of the register type (ReadOnly, Write2Clear, Write2Pulse, etc). The generated vhdl file has no compile errors (tested with GHDL), but I didn't checked that is functionally correct.

Now with the option to use either options (with or without records)

There is a rebase missing first, as several changes and naming conventions were updated. Please, do this first.
Second, one important thing: I like the idea to pack stuff in records, but maybe we would get the best of 2 worlds by allowing several different records while also adding lone ports.

Are you sure? In my forked repo I could merge it with the master branch without any conflicts (also github tells it).
About the "best of 2 worlds", I agree, but I see it is an evolution with lower priority when compared to adding a test bench (my next contribution), a header and a doc generator.

Tafas, let me just understand how can I help here. Your suggestion is to keep the member as package and not libPkg, right? I could change it back and make a new commit with this change.
Can you merge a previous commit inside my branch, or may be cherry pick the changes? Please advise.

Tafas, let me just understand how can I help here. Your suggestion is to keep the member as package and not libPkg, right? I could change it back and make a new commit with this change.
Can you merge a previous commit inside my branch, or may be cherry pick the changes? Please advise.

yes. This is one thing. I advise to revert, as we have the packageBody and packageDeclaration taht together with the libraryObj create package files.
For the several coding styles, new structures and reorganization related but independent to record in/output itself should be a different PR. They are ok, I'd like them on master branch.
I agree that we have more to focus than the record (simulation, for example). I'm still thinking on a more generic way to do the records so for a while, I'll create a record branch and you can push to this branch instead of master. Those willing to use it as it is will be able to do so and I'll rebase it until a more definite solution is set.
Finally, the records. I added the "pkgVHDL" class, it should be used by the regbank to create the pkg containing the records.

I did an independent PR, as you requested in (2). We can drop this one till we get a more mature implementation.


Fix duplicate printing in live captions demo

Fix duplicate printing observed during initial inferences and on script exit.  Formats imports.

Thank you for the review Manjunath.


Get "replies" from a user

Hello friends. I'm running my own instance of Nitter and it seems to be working correctly because I can browse normally, when I visit a user's page I can see the "tweets & replies" but when using ntscraper's get_tweets function I can't read the replies, how can I get the responses that a user has made (and not just their posts)?

I need this too. How can we do it?

get tweets only returns normal tweets and RTs. Actually, it all happens in the replies tab on Twitter. So it would be more accurate to scrape data from there. We expect an urgent solution from the developer. Thanks


Version format migration strategy

I'm migrating some Azure Function endpoints to an ASP.NET Core 6 application. The version format we are using in our Azure Function endpoints is d.d-preview.d for example, 0.1-preview.0, which isn't compatible with what ApiVersion allows as it doesn't allow '.' characters in the Status portion. We have previously shipped clients that call APIs using that format, so I need to keep some compatibility while I migrate to a supported format (which I agree is the right thing to do). Any suggestions? Could the validation rules be relaxed somehow?
Thanks!

Ok. I've resolved this myself. At least for my particular scenario, I was able to extend the QueryStringApiVersionReader (Api Version Reader) to strip the problematic '.' character. Worked like a charm.
On the Version Format, it says "It is possible to customize this behavior for legacy and other non-compliant services, which will be covered in the Advanced Versioning topic." However, I wasn't able to find an Advanced Versioning section or page.

In 1.0-5.x, this was not supported. The status component did not allow .. Starting 6.0, this was rewritten in a way that no longer uses regular expressions and has better performance. One of the side effects is that a . is now allowed. You can see the new implementation here.
Hmm... maybe I goofed and there isn't a section for Advanced Versioning. While it has certainly always been possible (e.g. ApiVersion is not sealed), it has historically be difficult to customize. The primary factors are:

Cannot use an interface because operators are not allowed (ex: new ApiVersion(2.0) >= new ApiVersion(1.0))
Cannot use a struct because they cannot be extended
Parsing as a static method on ApiVersion:
a. You can't override it
b. You can't provide an alternate return type
c. The rest of the framework doesn't know when or where to call your implementation

Starting in 6.0, this has all been refactored. Parsing has now been extracted as IApiVersionParser and ApiVersionParser.Default.Parse retains the old implementation of ApiVersion.Parse. IApiVersionParser is registered via DI. In the places where it would get used, this service is resolved to parse ApiVersion. This means that you can replace it to change the implementation or extend it.
ApiVersion.IsValidStatus stayed a static method because:

It's about the value, not parsing
Makes status have consistent meaning

An ApiVersion is neither System.Version nor a Semantic Version, even though some people try to use them. A status with a ., however, was common enough that I thought was reasonable to support.
We're up to Preview 2 and Preview 3 is just around the corner. If you additional thoughts or options about how to make design and process better (aside from documentation), please. Now is the time for change. 😉

I hope you don't mind me rambling a bit. I love the fact that the library has a strong opinion on the format. It makes sense and you've tied it all back to the Microsoft REST API guidelines, which is clearly stated. Having 6.x support the . makes sense and will certainly make things easier for me ;). I'm planning to ship in the next few months, so if Preview 3 is stable and not to bad to migrate to, i'd certainly love to give it a shot. Significant changes between Preview 2 and Preview 3? If not, maybe I could tinker with Preview 2.
I think some migration strategy could still be useful, but I would totally understand if you said it's not worth it. Once you open the flood gates, you risk devaluing the original goal and stance of the project a bit. But, there is something to be said about supporting services who desire to migrate to the suggested version format to maintain compatibility with their existing clients and to be able to move forward in a standard way. I'm imagining a mechanism to "bless" certain APIs for a legacy "unsupported" version format with the expectation that all other APIs would adhere to the suggested version format. But, i'd expect such a mechanism to be super easy to remove when the time comes and not overly intertwined with the supported configuration. Just a thought.
Either way, i'm a fan. Thanks for the hard work and dedication you've put into the project.

No problem at all. I take all feedback. Some times it changes things. Some times we agree to disagree. Existing and legacy were always on my mind. Many features and concepts started with my own challenges, legacy included. Once the project was out in the wild, there were definitely a lot more tests of effectiveness against existing designs. Incompatibility with existing API version formats have come up before, but not often. It has come up a far amount of times for net new as well. Customization and extensibility was always a consideration, but seeing what it would take by people willing to put in the effort demonstrated it was less than desirable for the reasons listed above. As an example, some people have asked for  3 (1.0.0) or 4 (<IP_ADDRESS>) part API version. I've always that was strange because build and revision numbers are irrelevant to a HTTP client, but - hey - if you want it... 🤷🏽♂
The AssumeDefaultVersionWhenUnspecified was only ever meant to support backward compatibility. If you turn API versioning, then every API is now versions - even if it's implicit. You shouldn't have to touch every piece of API code to deal with that. Similarly, how do you prevent from breaking existing clients. The whole concept wraps around the idea that you had some unstated version (think "Initial" or maybe even "V1"), but now realize that you need versioning. This feature allows all of those original APIs to have whatever defined API version you want from DefaultApiVersion, which defaults to 1.0. Existing clients can chose to specify 1.0 if they know to, but if they don't, then this value will be assumed. There are some other ways this capability can be used, but it's mostly be abused. Clients should always explicitly request an API version when possible. A server should always use the API version the client asks for or fail if it can't process it.
I understand concerns about previews so I won't try to sell you on anything. I have just as many apprehensions about it as everyone else. Here are the things coming in Preview 3:

Refactor for API Versioning for Minimal APIs (this will be a breaking change from Preview 2)
Bug fixes for OData support
Code signing

If you aren't using Minimal APIs, then things should be stable for you. I don't anymore features planned nor any other known issues to fix. OData support is a bit inflight because it was a complete rewrite - again. ☹ After Preview 3, I think things will be close to Release Candidate. The last hurdle is buttoning up code signing. This is taking much longer than I'd like. If that isn't important to you, then you should be fine. I know it's important to some. I would expect in the worse case scenario the only difference between the final RC and release will be signing.
Hopefully that gives you enough information to make an informed decision.

Preview 3 is working great. Thanks!


--ambient is confusing, use --dt instead

So as far as I understand, right now, typings install --ambient [module] has two differences compared to typings install[module]:

when a typing is found in typings/registry, if in typings.json it says "ambient: true" the typing file is ignored without the --ambient option
the --ambient option enables DefinitelyTyped registry lookup

Seeing that we can't have two versions of the same typing in typings/registry, I don't see the logic behind the first one. it only means an extra step when installing typings.
And if the first one is changed, then a better name for the second case is --dt or --definitely-typed.

Nope. default source for --ambient is dt and can be specified in .typingsrc
You can install from different source using typings install <source>!<package> syntax. See typings install -h.

then that means env-node is impossible to install from typings/registry because it's ambient and dt is the default source for ambient typings?

Yes. If you mean typings I node --ambient

isn't typings supposed to completely replace DefinitelyTyped?
I find typings much easier to contribute to but if it's not the default source for env typings then there's no point in maintaining them in typings/registry as no one is going to use them.

Yes. At some point would like to change default to env


Failed to perform add on <Link: PirAnka - PirAnka>

I am getting sporadic errors in the log. Looking at the NetJSON input I can't locate an entry that justifies this error.
the error message is this:

[ERROR 2017-09-22 09:20:14,358] module: contextmanagers, process: 27803, thread: -1213786368
Failed to perform add on <Link: PirAnka - PirAnka>
Traceback (most recent call last):
File "/extra/inet/django-netjsongraph/src/django-netjsongraph/django_netjsongraph/contextmanagers.py", line 10, in log_failure
yield
File "/extra/inet/django-netjsongraph/src/django-netjsongraph/django_netjsongraph/base/topology.py", line 250, in update
link.full_clean()
File "/usr/lib/python3.4/site-packages/django/db/models/base.py", line 1248, in full_clean
raise ValidationError(errors)
django.core.exceptions.ValidationError: {'all': ['source and target must not be the same']}

@acoul would the signature of the object that is failing help you locate the issue?

Let's clarify, what do you think the issue is?

the error message in the log is not good enough hence not helpful
the fact that a validation error is raised if a node has a link to itself doesn't work in your use case

looking @ the NetJSON file I can't locate a link with same target & source. I don;t understand what is triggering this error/behavior. I've made a smaller subset of NetJSON file that causes the same issue.

@acoul I performed some tests and indeed there's something fishy going on.
Even trying to improve the error message won't help.
When this kind of weird bugs pop up, my usual resort is the brute force strategy: the NetJSON subset should be decreased iteratively until the smallest possible subset that triggers the error remains. Can you do this? If you can that would help a lot: I will be able to run very fast tests on the small subset in a semi-automated manner, if a bug is indeed found I could even use that sample in the automated test suite.

I created a very small NetJSON subset that recreates this issue. The NetJSON is been generated by this simple set of ASs:

17101 19332
17101 19479
17101 20802
17101 21042
18569 18606
18569 19835
18569 21194
18570 19835
44038 9895
44038 19835
44038 22239

hope this helps

@acoul trying with that dataset I get a similar error:
Failed to perform add on <Link: SV1CIM-SOFIKO-SV1GSD - SV1CIM-SOFIKO-SV1GSD>: ValidationError

Is this the same error you are getting with the same dataset? If yes I can proceed with some more testing.

[ERROR 2017-09-27 18:56:19,273] module: contextmanagers, process: 7641, thread: -1213450496
Failed to perform add on <Link: SV1CIM-SOFIKO-SV1GSD - SV1CIM-SOFIKO-SV1GSD>
Traceback (most recent call last):
File "/extra/inet/django-netjsongraph/src/django-netjsongraph/django_netjsongraph/contextmanagers.py", line 10, in log_failure
yield
File "/extra/inet/django-netjsongraph/src/django-netjsongraph/django_netjsongraph/base/topology.py", line 250, in update
link.full_clean()
File "/usr/lib/python3.4/site-packages/django/db/models/base.py", line 1248, in full_clean
raise ValidationError(errors)
django.core.exceptions.ValidationError: {'all': ['source and target must not be the same']}

yes ACK. this is the error I am getting too.

@acoul I prepared a patch in pull request #58 (branch issues/58).
Before merging it in master I would like us to test it a bit. Be sure to update your django-netjsongraph code with the code on that branch and apply the data migration with ./manage.py migrate.
While working on this issue I realized a better long term solution is needed and opened issue #61.

I am still getting the same error. Here are the steps I followed:

cd django-netjsongraph; git pull; git checkout issues/58; pip install ./ --user; cd ~web/nmsbgp; ./manage.py makemigrations; ./manage.py migrate

I just added the "./manage.py makemigrations" step as I was instructed by the following message:

Your models have changes that are not yet reflected in a migration, and so won't be applied.
Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.

here is the error message:

[ERROR 2017-10-03 13:05:45,093] module: contextmanagers, process: 14240, thread: -1214155008
Failed to perform add on <Link: SV1CIM-SOFIKO-SV1GSD - SV1CIM-SOFIKO-SV1GSD>
Traceback (most recent call last):
File "/extra/inet/django-netjsongraph/src/django-netjsongraph/django_netjsongraph/contextmanagers.py", line 10, in log_failure
yield
File "/extra/inet/django-netjsongraph/src/django-netjsongraph/django_netjsongraph/base/topology.py", line 250, in update
link.full_clean()
File "/usr/lib/python3.4/site-packages/django/db/models/base.py", line 1248, in full_clean
raise ValidationError(errors)
django.core.exceptions.ValidationError: {'all': ['source and target must not be the same']}

I decided to delete and recreate the database & the sub categories. The error persist with some additional nodes:

[ERROR] Failed to perform add on <Link: PirAnka - PirAnka>
Traceback (most recent call last):
File "/extra/inet/django-netjsongraph/src/django-netjsongraph/django_netjsongraph/contextmanagers.py", line 10, in log_failure
yield
File "/extra/inet/django-netjsongraph/src/django-netjsongraph/django_netjsongraph/base/topology.py", line 250, in update
link.full_clean()
File "/usr/lib/python3.4/site-packages/django/db/models/base.py", line 1248, in full_clean
raise ValidationError(errors)
django.core.exceptions.ValidationError: {'all': ['source and target must not be the same']}
Failed to perform add on <Link: PirAnka - PirAnka>: ValidationError
See error log for more information

[ERROR] Failed to perform add on <Link: Benz_Kalloni - Benz_Kalloni>
Traceback (most recent call last):
File "/extra/inet/django-netjsongraph/src/django-netjsongraph/django_netjsongraph/contextmanagers.py", line 10, in log_failure
yield
File "/extra/inet/django-netjsongraph/src/django-netjsongraph/django_netjsongraph/base/topology.py", line 250, in update
link.full_clean()
File "/usr/lib/python3.4/site-packages/django/db/models/base.py", line 1248, in full_clean
raise ValidationError(errors)
django.core.exceptions.ValidationError: {'all': ['source and target must not be the same']}
Failed to perform add on <Link: Benz_Kalloni - Benz_Kalloni>: ValidationError
See error log for more information

[ERROR] Failed to perform add on <Link: SV1CIM-SOFIKO-SV1GSD - SV1CIM-SOFIKO-SV1GSD>
Traceback (most recent call last):
File "/extra/inet/django-netjsongraph/src/django-netjsongraph/django_netjsongraph/contextmanagers.py", line 10, in log_failure
yield
File "/extra/inet/django-netjsongraph/src/django-netjsongraph/django_netjsongraph/base/topology.py", line 250, in update
link.full_clean()
File "/usr/lib/python3.4/site-packages/django/db/models/base.py", line 1248, in full_clean
raise ValidationError(errors)
django.core.exceptions.ValidationError: {'all': ['source and target must not be the same']}
Failed to perform add on <Link: SV1CIM-SOFIKO-SV1GSD - SV1CIM-SOFIKO-SV1GSD>: ValidationError
See error log for more information

also the orphan node does appear again as orphan in the new graph as reported on https://github.com/netjson/django-netjsongraph/issues/59

in case this may help, it seems there is a relationship between the names of the Nodes that get the above errors. searching with grep on the json file I came up with the following:
},
{
"source": "ANKA",
"cost": 1.0,
"target": "ANKA2",
"cost_text": "",
"properties": {}
},
{
"source": "ANKA",
"cost": 1.0,
"target": "PirAnka",
"cost_text": "",
"properties": {}
},
{
"source": "Kalloni",
"cost": 1.0,
"target": "Benz_Kalloni_2",
"cost_text": "",
"properties": {}
},
{
"source": "Kalloni",
"cost": 1.0,
"target": "Benz_Kalloni",
"cost_text": "",
"properties": {}
},
{
"source": "SV1CIM-SOFIKO-SV1GSD",
"cost": 1.0,
"target": "Sv1gyk-Sofiko",
"cost_text": "",
"properties": {}
},
{
"source": "sv1gsd_2",
"cost": 1.0,
"target": "SV1CIM-SOFIKO-SV1GSD",
"cost_text": "",
"properties": {}
},
{
"source": "sv1gsd",
"cost": 1.0,
"target": "SV1CIM-SOFIKO-SV1GSD",
"cost_text": "",
"properties": {}

@acoul yes it's a problem related to the NetJSON id and local_address fields.
The shortcut I initially used to implement this was a bad choice (issue #61).
The bug is not in the parser but in the methods that look for existing links and nodes.
I thought the patched solved the problem but evidently I did not have enough data to test, I will try another patch as soon as possible and let you know.

Closed by #79


Bug: placeholder should not be shown for single DecoratorNode

Lexical version: 0.9

It seems that DecoratorNode is not checked:
https://github.com/facebook/lexical/blob/5445f2ce45496a5305a1bd6c9df2bc8d7dfc737b/packages/lexical-text/src/index.ts#L114-L137

Hey @vilic! I'm having trouble recreating this. Could you give some instructions on what you did?

Sure, two changes to the playground:

Comment out those to insert image at root:

https://github.com/facebook/lexical/blob/5445f2ce45496a5305a1bd6c9df2bc8d7dfc737b/packages/lexical-playground/src/plugins/ImagesPlugin/index.tsx#L225-L227

Make ImageNode non-inline by adding:

isInline(): boolean {
  return false;
}

Then in the playground:

Insert a sample image.
Delete the leading empty paragraph.


camera doesn't move with the ego vehicle

I met the problem when I tried to spawn multiple clients and carla servers in a multi-processing way. I found that the camera created by carla server didn't move with the ego vehicle while the camera created by me worked well. However, if I tried to spawn multiple clients and carla servers seperately, this problem disappeared.
Does anyone know how to solve this?

From what I understand, the camera that normally follows the ego vehicle (which let's the user see it from a bird's eye view), is not moving? If that's the case, the camera is moved at leaderboard/scenarios/scenario_manager.py:
spectator = CarlaDataProvider.get_world().get_spectator()
ego_trans = self.ego_vehicles[0].get_transform()
spectator.set_transform(carla.Transform(ego_trans.location + carla.Location(z=50), carla.Rotation(pitch=-90)))

Maybe you can debug that part see if there is an issue there? or did I missunderstood your problem altogether :slightly_smiling_face:?
Also, what do you mean by "while the camera created by me worked well"?


Support Basic Auth

To be used safely over WAN requires a minimum of authentication.

😁  Hurry up

@rfyiamcool haha, just a moment please :-D


⚠ Processors has degraded performance

In 26e1e4e, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 96 ms

Resolved: Processors performance has improved in 18ceb49.


Add set mode service

Add set mode service with full GUI support. Some cleanup in services.py also.

This code is probably correct. However, the Miele API is reporting wrong values and does not react properly.
Waiting for response from Miele.

Still no response from Miele. The service useless if the current state is not reported in the API.


Invalid search result range Error

On some tweets reply button is not showing by default. This breaks the code and gives an error Invalid search result range

Do you have an example to demonstrate this bug?

Closing due to lack of reproduction. Happy to reopen once provided.


Uncaught (in promise) ReferenceError: $state is not defined

Im getting Uncaught (in promise) ReferenceError: $state is not defined
in console using it on nuxt

I'm so sorry I missed this issue, is this problem still exists?


modernize layout and installation

Follow instructions per https://packaging.python.org/en/latest/tutorials/packaging-projects/

Feature is available in the 2.0.0 release


Plugins Not Working

Describe the bug
After enabling plugins (tried with Klarna Shopping and my previously working custom plugin), and typing in the chat, chat will show this error
Unable to generate bot response. Details: Error: 500: Microsoft.OpenApi.Readers.Exceptions.OpenApiUnsupportedSpecVersionException: OpenAPI specification version '' is not supported. at Microsoft.OpenApi.Readers.ParsingContext.Parse(YamlDocument yamlDocument) at Microsoft.OpenApi.Readers.OpenApiYamlDocumentReader.ReadAsync(YamlDocument input, CancellationToken cancellationToken) at Microsoft.OpenApi.Readers.OpenApiTextReaderReader.ReadAsync(TextReader input, CancellationToken cancellationToken) at Microsoft.OpenApi.Readers.OpenApiStreamReader.ReadAsync(Stream input, CancellationToken cancellationToken) at Microsoft.SemanticKernel.Functions.OpenAPI.OpenApi.OpenApiDocumentParser.ParseAsync(Stream stream, Boolean ignoreNonCompliantErrors, CancellationToken cancellationToken) at Microsoft.SemanticKernel.Functions.OpenAPI.Extensions.KernelOpenApiPluginExtensions.RegisterOpenApiPluginAsync(IKernel kernel, String pluginName, OpenApiFunctionExecutionParameters executionP...

Note: This works in a previous version that I still have deployed.
To Reproduce
Steps to reproduce the behavior:

Go to Plugins
Enable Klarna Shopping
Type message I'm looking for shoes, size 10.
See error

Platform

OS: Windows
IDE: VS Code
Language: C#
Source: Latest code as of this issue creation date.

Additional context
Running locally, with ./start.ps1

can confirm that bug.

I'm getting the same error enabling the websearch pluging and using the Azure infrastructure provided by copilot development team

thanks @raffertyuy  When you say latest code, are you referring to the latest release, or the latest commit on main?  Can you please point me to the exact commit you are using?

thanks @raffertyuy  When you say latest code, are you referring to the latest release, or the latest commit on main?  Can you please point me to the exact commit you are using?

Hi @momuno, it's the latest commit on the chain as of yesterday.
Should be this one: https://github.com/microsoft/chat-copilot/commit/ccf79dcd194464dc82014221845a2ea05122ccce

Thank you @raffertyuy.  We were able to reproduce and are working on reverting the version bump. (Tested that plugins do work on commit prior to the version bump).  We will then look into what caused the problem.

It seems that SK now expects json with camel casing and CC follows OpenAi’s documentation, snake case.
When I removed the attributes forcing snake case in websearch plugin, SK could deserialize and import, but CC breaks because it’s expecting the previous format.

Thank you for bringing this issue up.
This should now be fixed with PR #624

Confirmed working on my custom plugin. Klarna shopping isn't working still though, but different "Oops..." error.

Another fix is coming for Klarna. It will be in when this PR is merged: #626


BLE Sample notify is not working

Hi Neil,
i have two issues with ble sample notify. First one is easy to solve. In line https://github.com/nkolban/esp32-snippets/blob/master/cpp_utils/tests/BLETests/SampleNotify.cpp#L95 is created new BLE2902 descriptor, but by default notification i turned off in it (easy to fix).
But after fixing it there is another issue:
E (3358) BT: btc_gatts_arg_deep_copy 8 no mem
and i cant find solution. And i think so at the end service and/or characteristic does not start.

Howdy ... it is my understanding that the flag which says that notifications are enabled should NOT be initially set.   Instead, a client that wants notifications should make a request to set the flag on.  The server then looks at the value of the flag before actually sending a notification and then uses this as the indication of whether or not to send the notification.  Thus the server does not send notifications unless a client has actively expressed an interest in receiving them.
Have you increased the amount of memory for the Blue Tooth stack in the makemenu config settings.
See the following:
https://github.com/nkolban/esp32-snippets/blob/master/Documentation/BLE C%2B%2B Guide.pdf

Hi,
just a different approach. In my case notify is ready when esp32 starts and is waiting ble client to connect, then starts to sent notifications.
Yes, i did increase BLE stack to 10000 but still same error. Most likely its esp-idf error, but i dont know how to debug it.

Do you have a sample application that demonstrates the issue?  Have you been able to switch on BLE C++ library debugging/trace to examine what is going on at the API level?

Basically its sample code with 1 change:
   BLE2902* p2902Descriptor = new BLE2902();     p2902Descriptor->setNotifications(true);
in line 95
	pCharacteristic->addDescriptor(p2902Descriptor);

The weirdest thing is when i revoke esp-idf to commit 27574a3 then i cant compile the code cause for some reason files in components directory are not included and  i got this message:
F:/esp32/programs/workspace/bletest/main/SampleNotify.cpp:26:23: fatal error: BLEDevice.h: No such file or directory compilation terminated.
but with latest esp-idf i can compile and flash but with issue described above.

What is esp-idf commit 27574a3?   Do you have a link?  What is your thinking?  Are you trying to run with release of ESP-IDF v2.1?
For the compilation issue, try deleting the F:/esp32/programs/workspace/bletest/build directory and then try re-building.   The BLEDevice.h header should be found in F:/esp32/programs/workspace/bletest/cpp_utils

Ive found this post of yours https://github.com/espressif/esp-idf/issues/857, and this is mentioned commit https://github.com/espressif/esp-idf/commit/27574a31e7c41f6e22e10e9b9d7713c6d49f795d, its esp-idf v2.1 release.
When i change esp-idf to new commit with fetch or checkout i always do make clean and then recompile code. This dont help this time.

If desired, we can always do live chat and/or screen shares as needed.  You can always find me when I am around on IRC in channel #ESP32.

I will make it working somehow, cause your library is great, nice and clean to read and to work with.
Thank you for all your hard work.


[ISSUE #411] Fixed ClassCastException when get the instance of the store

What is the purpose of the change
Avoid  ClassCastException when get the instance of the store
Brief changelog
Judge the type of store before cast
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-0.1%) to 42.487% when pulling df321f7e0996bdb4bec3a75dcbad1d9792bc0ab3 on Hellojungle:fixIssue411 into 901e06afa259ed16be53b1d812c38c48f0f347dc on apache:develop.


README: fix link to irc channel

I don't think this ever meant to point to freenode since the channel
there is almost empty, don't seem to be related to Way-Cooler or
Awesome, and doesn't have Timidger :)

Ah thanks, that is what I meant


uv pip install --prefix should search package in prefix path

❯ uv pip install --break-system-packages --prefix ~/.local hyuga
Using Python 3.12.7 environment at /nix/store/rmcswikkmjlp0rp5302dx8ydbqpgd14y-python3-3.12.7-env
Resolved 10 packages in 2.92s
error: Failed to prepare distributions
  Caused by: Failed to download and build `hyrule==0.7.0`
  Caused by: Build backend failed to determine requirements with `build_wheel()` (exit status: 1)

[stderr]
Traceback (most recent call last):
  File "<string>", line 8, in <module>
ModuleNotFoundError: No module named 'setuptools'
❯ uv pip install --break-system-packages --prefix ~/.local setuptools
Using Python 3.12.7 environment at /nix/store/rmcswikkmjlp0rp5302dx8ydbqpgd14y-python3-3.12.7-env
Resolved 1 package in 2ms
Installed 1 package in 8ms
 + setuptools==75.6.0
❯ uv pip install --break-system-packages --prefix ~/.local hyuga
Using Python 3.12.7 environment at /nix/store/rmcswikkmjlp0rp5302dx8ydbqpgd14y-python3-3.12.7-env
Resolved 10 packages in 3ms
error: Failed to prepare distributions
  Caused by: Failed to download and build `hy==1.0.0`
  Caused by: Build backend failed to determine requirements with `build_wheel()` (exit status: 1)

[stderr]
Traceback (most recent call last):
  File "<string>", line 8, in <module>
ModuleNotFoundError: No module named 'setuptools'

pip install will not have this bug.

This looks like expected behavior from build isolation https://docs.astral.sh/uv/pip/compatibility/#pep-517-build-isolation

Oh, I note --no-build-isolation


Adjust timer & remove close message

Great work, please keep the PR's small in the future

Looks good, second member can merge.
Sidenote: many insertions, much size. Wow.


no such file discord-ipc-0

I'm guessing the ipc file isn't in the usual place, you'll want to customize discord-emacs-ipc-dir and discord-emacs-ipc-name to match up with the correct location.


Validation improvements

Implement measurements of recall (fraction of signals recovered) vs. background and glitch datasets separately. Closes #41 , closes #170 .
For background, outputs are pooled across adjustable windows at an adjustable stride to simulate test-time clustering, and recall is measured using thresholds from the top k background "events".
For glitches, recall is measured using thresholds from adjustable specificity levels (fraction of glitches correctly classified at a given threshold).
Monitoring (for early stopping and model selection) can be performed against any threshold for either metric. Checkpointing at a specified cadence has been added as well.

[ ] Add Recorder and Validator parameters to train:main function definition
[ ] Add tests
[ ] Fix sample_rate used for background pooling to be 1 / stride

Ok I have screwed something up royally with the commit ordering here, I may need to rework this


Link to CRISPR Screens documentation from AOTF is incorrect

Describe the bug
Clicking on the documentation icon for CRISPR Screens on the AOTF page should point to https://platform-docs.opentargets.org/evidence#crispr-screens
Observed behaviour
It currently points to
https://platform-docs.opentargets.org/evidence#project-score
To Reproduce
Steps to reproduce the behaviour:

Go to an associations page e.g. https://platform.opentargets.org/disease/MONDO_0016063/associations
Click on the documentation icon which appears when you hover over CRISPR Screens
See error

Same issue for PROGENy — it currently points to SLAPenrich

Thanks @HelenaCornu! Can you help me to update them here and create a PR?


Extend new Tab Bar menu to include a Wrapped Tabs option

This would set "workbench.editor.showTabs": "multiple" and "workbench.editor.wrapTabs": true
For consistency the existing Multiple Tabs option would set "workbench.editor.showTabs": "multiple" and "workbench.editor.wrapTabs": false
Doing this would increase the visibility of the tab-wrapping feature.

As an alternative to having some of the menu options affect two settings, the existing workbench.editor.wrapTabs boolean could be migrated to a new value of the new setting, e.g. "workbench.editor.showTabs": "wrapped"

I still think the tab wrapping feature deserves greater visibility.
Related, info at https://code.visualstudio.com/docs/getstarted/userinterface#_tabs still treats the showTabs setting as a boolean.

Closing as not planning to add wrap tab options to Tab Bar Submenu.
Thanks for letting me about the docs being out of date, changed it


Remove U2F support

Completely remove U2F support from 1.18.0, 1.17.0 will be the last release that U2F is somewhat supported. Users who used U2F would already be warned about using U2F for a while now and should hopefully already be migrated to webauthn. But starting 1.18 definitely remove it.

Note, there are other // FIXME: DEPRECATED for other related settings. But separating them so it become apparent in the changelog for 1.18.0 that support is removed.


Task works incorrect in case default and active databases aren't the same

System information:

Operating system (distribution) and version win 10 x64
DBeaver version 6.3.3

Connection specification:

Database name and version postgresql

Describe the problem you're observing:
Error like "ERROR: relation "actor" does not exist" appears when trying to execute export in case default and active database aren't the same
log.txt

We need to save active database and active schema in task configuration.

Fixed.

verified


Change default size for bootstrap.resample

~Pretty straightforward fix here. Minor nitpicky detail: I'm calling the bootstrap samples replicates however I noticed you call them replicas. In my experience the former is more common, but in any event I think it'd be good the use the same term consistently in the documentation so maybe we pick one.~
Closes https://github.com/dsaxton/resample/issues/51

I would prefer if the size argument was removed from bootstrap.bootstrap, and the default value in bootstrap.resample reduced from 1000 to 100.

@HDembinski going to just merge this in as it's a small / simple fix


Heading Attributes fall in sequential order

#Heading attributes fall in sequential order
#User Story
AS A marketing agency
I WANT a codebase that follows accessibility standards
SO THAT our own site is optimized for search engines
#Acceptance criteria
GIVEN a deployed website
WHEN I use the website
Then I can navigate Headings in a logical sequence

Sub titles in sidebar changed from H3 to H2 and font size adjusted
Footer adjusted to an aside tag rather than a heading tag


Waiting for promise resolution on post without timing out?

I have deployed a lambda serving a graphql endpoint with aws-serverless-express. The application is working fine including serving the /graphiql and /playground apps and querying is returning content as expected from RDS.
The issue comes when posting content, I use Sequelize to perform the DB insertion inside my mutation that correctly returns a promise. For my testing I use cURL and in non-lambda mode the connection remains open until the transaction is committed, when posting against lambda the connection times out it seems as soon as the content is posted which is only a few seconds even though I have configured the lambda timeout for 5 minutes.
Additionally, even though the timeout has happened the full commit does complete and the content is persisted which is somewhat good news.
Is there some configuration for aws-serverless-express that is required to prevent this I might be missing?

See discussion in #32 with workaround.


Missing BMM deps

Add pillow, openpyxl, lmfit.

lmfit should come from collection -> analysis -> scikit-beam:
https://github.com/NSLS-II/lightsource2-recipes/blob/69889343b789c0d7d84f92a0c223347b131fd6bb/recipes-tag/scikit-beam/meta.yaml#L33
Not sure why it's not installed.
pillow should be installed as a dependency of scikit-image.
Not sure about the third one.

There is a noarch package for openpyxl in https://anaconda.org/anaconda/openpyxl/files.

Everything is in one large metapackage now. See https://github.com/nsls-ii-forge/analysis-feedstock/blob/master/recipe/meta.yaml.


Null Safety

Please Migrate Package to Null Safety

The issue is resolved now

Not migrated to null safety , but added additional null check conditions so that you wont run into any Null Pointer Exception , still you can use this plugin with unsound null safety without any exception


Update deployment options doc

Addresses https://cockroachlabs.atlassian.net/browse/DOC-8861

private clusters

As per the Slack convo, we don't need to call out Private Clusters on this page. Let me know if you disagree. cc @jramos-crl


[Connector API] Add missing 8.14 changes

Changes
Adding missing Connector API features that were shipped in 8.14 after #2367 was merged.
2 new endpoints:

validate draft filtering
activate draft filtering

2 endpoint changes

update filtering endpoint takes now rules and advanced_snippet as optional params, filtering is now optional (still present for backward compatibility)
delete connector endpoint accepts delete_sync_jobs url param

filtering-related timestamps (rules and advanced_snippet) were made optional in ES backend in 8.14

From the other PR: FilteringConfig -> active and draft should be optional, domain should be removed, it seems like an internal parameter

From the other PR: FilteringConfig -> active and draft should be optional

@l-trotta  I'm not sure if they should become optional, they are always required in the Filtering config representation in the server implementation

domain should be removed, it seems like an internal parameter

Yes, domain is not part of the request payload for any endpoint, but we do populate it in the index and return in the response when getting/listing connectors (the response is Connector or Connectors[]). We still need to populate it (even with the default value) as this is required by the Connector Protocol.
If I remove this from the FilteringConfig could it impact e.g. the get connector response from clients? (as Connector type references filtering: FilteringConfig[])
I'm unsure how to handle that case correctly in clients

Sorry for the confusion, I didn't understand how the filtering field was outputted differently if used in the context of SyncJobs. The correct fix is to replace FilteringConfig with FilteringRules in SyncJobConnectorReference. Server code

`features' in Connector should be nullable

The correct fix is to replace FilteringConfig with FilteringRules in SyncJobConnectorReference

Thank you for catching this! 👍

💚 All backports created successfully

Status
Branch
Result

✅
8.14

Questions ?
Please refer to the Backport tool documentation


Code cleanup

Summary

Removed useless comments
Fixed indentation for better readability
Fixed annoying temp1 variable name

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@rpetrusha we need to resolve the merge conflicts here and perhaps we should make changes to the VB code ourselves? Thanks!

This should be ready to merge once the build completes.


[Feature]: Add api errors

Description
In order to get more information about the failure flow at the api calls we need to return an error object with the information parsed to app
Current Behavior
The api client returns nulls with no information about the error itself.
How
Since Godot is not static typed we can use it to return an response ( like an 'ok' for timeouts) or an object error (VSTError?) with the following params:

errorCode:int - Usefull to track errors and pick out easly
errorDescription:String - A human readeable description in english

In the other hand if we took this aproach every response from the api must be casted to response or the error class. I think that add a lot of overhead so we can:

Parse all the responses to objects that will inherit from another one called VSTError and only check the errorCode ( much faster and ligther )
Refactor a little bit the api script to add in every call 2 Callables one to be called when the api call was success and the other when the call was a failure ( Example -> "func add_vip(user_to_vip_id: String, on_success_callback:Callable = null, on_failure_callback:Callable = null)")
Make a big refactor and make a "ApiRequest" class and using Builder pattern to add all the data and the callbacks.

I think this should be our first priorioty right now. We don't control any API call and it's a problem if the supposed flow fails. Let's work on this right now


bam_util (sort, filter, mark and remove duplicates)

How do you get snakemake to alternate between star.smk and utils.smk. I'm working on bwa_mem and it seems like it doesn't order the rules properly due to ambiguity in the rules.

@rdmorin you marked this "Done", should this issue be closed?


⚠ Bofrost.lu has degraded performance

In a38f1ab, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1739 ms

Resolved: Bofrost.lu performance has improved in 9a698fe after 9 minutes.


fix code smells; fix typos; performance refine(trying to)

Hi.
I implemented a lastIndexOf in the last commit.
Maybe we should open another pr for it but...anyway.
if it is acceptable, then I will make the indexOf.
if not, then I will rebase it out.

I'd find it reasonable to consider your changes in batches of, say, ten apiece. (That would make it possible to carefully inspect one by one.) But that many in one go? Definitely no.

I'd find it reasonable to consider your changes in batches of, say, ten apiece. (That would make it possible to carefully inspect one by one.) But that many in one go? Definitely no.

do you mean I should split them into several prs？

the performance refines I said has being splited to [LANG-1548] and [LANG-1549]

Coverage decreased (-0.004%) to 95.036% when pulling 62f744a7f25bc456354f23fb3e1b7455a4c53f7a on XenoAmess:fix_code_smells into 3d4ed4a8ac63db1e51601ffc31fed44dccbb276c on apache:master.

I'd find it reasonable to consider your changes in batches of, say, ten apiece. (That would make it possible to carefully inspect one by one.) But that many in one go? Definitely no.

@XenoAmess it's quite hard to review this PR. It has several commits, and several changes. Committers will have to read and understand your changes, and then be confident that these changes can go in the next release without causing regressions.
As @jochenw pointed out, instead if you could prepare one pull request for a change, and either include your other changes in another PR, or wait for a review/merge to submit more, that would be much easier to review; at the same time, your PR would be reviewed much faster.
Bruno

I'd find it reasonable to consider your changes in batches of, say, ten apiece. (That would make it possible to carefully inspect one by one.) But that many in one go? Definitely no.

@XenoAmess it's quite hard to review this PR. It has several commits, and several changes. Committers will have to read and understand your changes, and then be confident that these changes can go in the next release without causing regressions.
As @jochenw pointed out, instead if you could prepare one pull request for a change, and either include your other changes in another PR, or wait for a review/merge to submit more, that would be much easier to review; at the same time, your PR would be reviewed much faster.
Bruno

OK, you're right, then I will split it into more prs.

@jochenw  @kinow
Hi.
This pr is already splited into several prs.
Most of them are small enough that not need to have a jira (IMO).
So I will close this pr.
Thanks for your help.


Fix several html issues for the web interface

This fixes all issues reported by the W3C validator.
Signed-off-by: Stefan Weil<EMAIL_ADDRESS>

See buggy and fixed version.

(I don't see any bug which is solved by this.)

Nor do I. At least Firefox accepts the buggy HTML (nearly) without complaining. You can see some bugs marked red when looking at the HTML source in Firefox. The full list of bugs is shown by the W3C validator (see links in my previous comment).

Thank you @stweil !


Bug where pushdown of Struct types included in UNION types did not work properly.

What is the necessity of this update? What is updated?
An array of names is passed to the projection pushdown setting.
In the case of Struct and Array, it is possible to track child columns by name.
On the other hand, when it comes to UNION types, you must explicitly track them from the Struct and Array types.
This fix makes it possible to track UNION Struct types.
UNION Arrays have already been handled.
How did you do the test? (Not required for updating documents)
Added unit tests and compared the behavior.

Before

$ ./bin/yosegi.sh cat -p "[[\"union_struct\",\"c1\"]]" -i a.yosegi  -o -
{"union_struct":null}
{"union_struct":null}

$ ./bin/yosegi.sh cat -p "[[\"union_struct\",\"SPREAD\",\"c1\"]]" -i a.yosegi  -o -
{"union_struct":{"c1":10}}
{"union_struct":{"c1":null}}

After

$ ./bin/yosegi.sh cat -p "[[\"union_struct\",\"c1\"]]" -i a.yosegi
 -o -
{"union_struct":{"c1":10}}
{"union_struct":{"c1":null}}

$ ./bin/yosegi.sh cat -p "[[\"union_struct\",\"SPREAD\",\"c1\"]]" -i a.yosegi  -o -
{"union_struct":{"c1":10}}
{"union_struct":{"c1":null}}

LGTM


Compatibility with signac 2.0

Description

Merge after #152 is merged.
Motivation and Context

Resolves #132
Checklist:

[x] I am familiar with the Contributing Guidelines.
[x] I agree with the terms of the Contributor Agreement.
[x] The changes introduced by this pull request are covered by existing or newly introduced tests.
[x] The package documentation and framework documentation in signac-docs are up to date with these changes.
[x] I have updated the changelog and added any related issue and pull request numbers for future reference.

@cbkerr We can’t merge this until signac 2.0 is released, right? If not, I’d like to keep this in draft until then.

@cbkerr Maybe we can refactor this to focus on 1.8+ compatibility and require signac>=1.8.0 like this PR: https://github.com/glotzerlab/signac-flow/pull/693


Authorization header not sent via the Swagger UI

When using the Swagger UI generated , the Authorization header is never sent.

closed by #94

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Upgraded to latest pod, now delegates not firing

The title says it all. I just upgraded to the latest pod from an ancient version, and now my UIWebView delegate methods aren't firing.
In my header file:
@interface MyViewController : UIViewController <UITextFieldDelegate,RestConnectionDelegate,UIWebViewDelegate>

@property WebViewJavascriptBridge* bridge;

In my implementation file:
    NSLog(@"Setting up JavaScript bridge...");
    [WebViewJavascriptBridge enableLogging];

    _bridge = [WebViewJavascriptBridge bridgeForWebView:_register_web_view webViewDelegate:self handler:^(id data, WVJBResponseCallback responseCallback) {
        // yadda yadda
    }];

    NSLog(@"webView delegate is %@", _register_web_view.delegate.description);
    [_register_web_view loadRequest:requestObj];

That NSLog on the second-to-last line shows that the delegate is set properly:
webView delegate is <WebViewJavascriptBridge: 0x17409e7d0>
I have implemented all of UIWebView's delegate methods and included NSLog statements in each to confirm that the methods are not being fired.
In short, I've covered all my bases and I don't know what's going on. Any suggestions would be appreciated.

Closing. Changing _bridge to self.bridge in the assignment fixed it.


Query tab doesn't worrk once connected to the PostgreSQL

I am using the PostgreSQL connector in Falcon SQL Client. Once introduced the credentials in CONNECTION tab I see the screen and "CONNECTED" status, however, I cannot access the query tab when clicking.
My db has different schemas, so not sure but it can be related to this issue #518
Anyone any idea?

Same issue here.

Same problem here with sqlite. The whole falcon window goes blank after clicking on the query tab. In the console, I can see this error repeated multiple times:
Uncaught Error: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object%20with%20keys%20%7Btype%2C%20data%7D&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at ca (web-bundle.min.js:82831)
    at t (web-bundle.min.js:82832)
    at ag (web-bundle.min.js:82959)
    at web-bundle.min.js:82969
    at P (web-bundle.min.js:82972)
    at yg (web-bundle.min.js:82989)
    at fh (web-bundle.min.js:83022)
    at gh (web-bundle.min.js:83023)
    at Jh (web-bundle.min.js:83038)
    at Kh (web-bundle.min.js:83037)

Following the that link, the full error message is:
Objects are not valid as a React child (found: object with keys {type, data}).
Does anyone knows how to fix it?

Catalina 10.15.3 here. Connecting to MariaDB running in a docker container and queries tab gives a blank screen.

Since it's an Electron container, I figured I could check on what the error messages are. This one comes in like a lot. It refers to this URL:

https://reactjs.org/docs/error-decoder.html/?invariant=31&args[]=object with keys {type%2C data}&args[]=

Objects are not valid as a React child (found: object with keys {type, data}).

I've got no clues as to what it means and how it is working for everyone else, but not us.

@chriddyp could you help?

Same issue here, Catalina 10.15.3.
After successfully connecting, clicking on the Query tab does nothing.

Same issue, but for connecting to mssql from linux. Tested PostgreSQL DB connection/queries and that appears to work.


Generic Super / Command mods key binding

It would be nice to be able to share the config between OS X and Linux/Windows computers so a generic name for Command / Super which would do the right thing™ in the configuration would be awesome.
I'm also all for not adding anything but just that Super would be equal to Command on OS X and that Command on Linux / Windows would be equal to Super.

This should already be the case. Have you tested this out and confirmed that it does not work?

I have not! I suspected as much because I couldn't find Super or Command
in glutin but then again I couldn't find it in alacritty either (but I'm
just bad at searching I guess).
I'll try it!
On Mon, 2019-08-26 at 00:59:33 -0700, Christian Duerr wrote:

This should already be the case. Have you tested this out and confirmed that it does not work?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/jwilm/alacritty/issues/2754#issuecomment-524760135

I'd assume this works fine then. Using either Command or Super should be identical.


 Along with also fixing some broken code which used fancy quotes for string literals (” instead of ").

Many thanks for taking the time to check this out.


FileSystemProvider/FileSystem Loading Issues

I am wondering where to start looking for solving the following issue I am seeing:
SpringBoot application using ( full gradle build attached)

  springBootVersion = '1.4.0.RELEASE'

  springCloudVersion = 'Brixton.RELEASE'

Application has a CommandLineRunner implementation that "starts" a class on application startup.
The "start" method uses java.nio.file classes to "guarantee" the file system provider is available based on configured file ( file:///, s3:///, etc..) based on the application yml.
I use a 3rd party java.nio..FileSystemProvider implementation (for S3) when running in "mycloud" profile.
I use the native java nio file system provider ( file:///) when running in "default" profile (no eureka and no config server)
When running in default profile and with the application configured to use "file:///....." to store a file all works well using the java.nio.file library.
When I run in profile "mycloud" , I configure the application to use "s3:///bucket/..." ( via an application yml in the config server) and now the code throws the following even though the JAR for the s3 provider is located in the FAT jar for the application
Caused by: java.nio.file.ProviderNotFoundException: Provider "s3" not found
Code uses the following calls to verify and get the file system:  Where schema is based on configured file location ( file:///, s3:///, .....)
this.fs = FileSystems.getFileSystem(new URI(scheme+":///"));
this.fs = FileSystems.newFileSystem(new URI(scheme+":///"), new HashMap<String,Object>(), Thread.currentThread().getContextClassLoader());
I add a bit of code to insure the 3rd party FileSystemProvider is loaded in a static{} block in a class that is loaded via the Spring Context, and the application now finds the 3rd party FileSystemProvider when the class is "started" from a CommandLineRunner implementation.  All's good..
I now run the application in "default" profile ( no Eureka, no ConfigServer and using a file system of file:///.....)  and the application fails to start with the following.  The application can not find the native "file" FileSystemProvider
Caused by: java.nio.file.ProviderNotFoundException: Provider "file" not found
There are definitely behavior differences in the application when running standalone vs running with Eureka and ConfigServer in the mix.
Any thoughts on where to start looking?
gradle.txt

So it works with eureka and config server, but not otherwise? Not sure that we can offer much help without seeing a sample project.

Aplogies,
I have been able to replicate the issue minus eureka and config server all
together.  Must be an issue of loading a custom FileSystemProvider
implementation from a jar inside of the FAT jar.
Please close this issue.
Regards.
Mark Ulmer
On Fri, Sep 30, 2016 at 1:19 PM, Spencer Gibb<EMAIL_ADDRESS>wrote:

So it works with eureka and config server, but not otherwise? Not sure
that we can offer much help without seeing a sample project.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spring-cloud/spring-cloud-commons/issues/136#issuecomment-250815837,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADVJnehJZMuZ9pLl1BgOsdx2Vu8SUZetks5qvVKvgaJpZM4KLToF
.


Update Zynq Ultrascale port for V4.x and Clean up

Description
This pull request introduces the V4.x port for the Xilinx Ultrascale, which basically merges the previous implementation, the Zynq7000 port and the suggestion by @pete-pjb here #1172
Key Changes:

V4.x Port: A combination of previous work, the Zynq7000 port, and the proposal in by @pete-pjb here #1172
Interrupt Mapping: A new header file, x_emac_map.h, has been introduced to handle interrupt IDs. Since there is no canonical definition for EMAC interrupt IDs, the header maps interrupt IDs based on the EMAC base address.
LLMNR Update: The LLMNR implementation now leverages the multicast MAC hash table rather than using a dedicated MAC entry.
Removal of Zynq7000 (GEM V2) Code: Zynq7000-related code has been removed, as the ports for the Zynq7000 and Ultrascale are quite distinct. Keeping the Zynq7000 code IMHO no longer adds value and was redundant.
Micrel PHY support is also from the .zip provided by @pete-pjb. However, this has not been tested and may require further validation.

I will provide inline comments on specific sections where I'm uncertain or need feedback.
Test Steps
I could only test a single interface with IPv4 so far. Junbo Frames and LLMNR also work fine.
I plan to test multiple interfaces on a Kria board I have at my hand soon.
Checklist:

[ ] I have tested my changes. No regression in existing tests.
[ ] I have modified and/or added unit-tests to cover the code changes in this Pull Request.

Related Issue
#1172
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Every Ethernet peripheral, or most of them, has two ways of setting a MAC-address:

Up to four standard MAC-addresses. Need 100% match
A hash table with like 64 entries. Each entry is actually a bit.

Hash: when you add a MAC address whose calculated hash value is 12, then bit 12 in the hash table will get set.
( no news for most of you ).
Emil Popov and me came up with this idea:

First add primary MAC-addresses, i.e. the hardware addresses of the endpoint.
Secondly, add the MAC-addresses of the multicast addresses used (e.g. mDNS, LLMNR).

The first 4 (GMACSA_NUMBER) addresses will go to the table in the peripheral.
All subsequent addresses will be hashed.
MAC-addresses can be unhashed too: there will be 64 usage counters. When the counter reaches zero again, the hash value will be cleared.
You find an implementation in DriverSAM. Maybe we should put it in Common, so all drivers can use it.
For the Ultrascale port, I am thinking of using the same method.

Ah youre'right the Zynq7000 port uses XEMACPS_NWCFG_MCASTHASHEN_MASK directly instead of using the API function.
I added the discussed multicast fixes to the Zynq7000 port.
I noticed the promiscuous mode in the Zynq7000 port which is somewhat questionable as a default:
    /* As 'MCASTHASHEN' doesn't seem to work, use the promiscuous mode so that IPv6 multicast packets are received. */
    /* Allow promiscuous mode. */
    ulValue |= XEMACPS_NWCFG_COPYALLEN_MASK;

But I cannot test it.

By enabling and playing with mDNS?

I meant I do not have a Zynq7000 at  hand. I did test mDNS now for the Ultrascale.
I do like the idea of sharing the MAC related code in Common, however I do not have the time to do it at the moment.
My testing is complete for now here is what I did and what I think should still be tested:

[x] IPv4 including LLMNR, mDNS, Jumbo Frames
[x] Two endpoints (Virtual interfaces) on the same physical interface
[ ] IPv6
[ ] More than one physical interface
[ ] Zynq7000 changes

@StefanBalt
Thanks for taking time to contribute to FreeRTOS+TCP.
Can you help in fixing the CI checks:

To fix the spell checks these words [those listed in the logs Run spellings check] needs to be added to this file.
To fix the formatting please apply this patch.

Please let us know if you have questions or want us to take care of the CI.

@StefanBalt
Since the multicast PR needs more time to be merged, can you please help in fixing the following proposals from @htibosch so that we can go ahead with merging the branch:

LLMNR
MDNS

Please feel free to let us know if you prefer us to make the suggested changes.
Thank you.

Sure, I will push a fix (probably today).

I don't have the time to test it, I hope you did.

As mentioned earlier, I tested some of the features but not all (i.e. IPv6, DHCP and more than one physical interface missing).


The original data set can't be found.

I want to get the dataset and create a team as the instructions illustrated, but no one ever approved my team. Kindly provide me if you have it...

There has been some discussion about this issue. issue #1


v1.0.0 Release

PR's key points
…
How to review this PR?
…

          1 Warning

:warning:
Big PR, try to keep changes smaller if you can 😜

  Generated by :no_entry_sign: Danger


wiki plugin - Allow other plugins to register custom editor extensions

For example the Camel plugin to register its wiki based editor.
Today the dozer plugin is still in hawtio-wiki as its tied to the wiki plugin. But ideally all that is fully pluggable and independent.
We had to remove the Camel wiki editor for now. But will look at adding it back later when we focus on a good Camel web editor.

See also #13


parallax-background srcset

Hi Eren,
Would it be possible to use srcset with paralax-background? And if so how do I implement it in this code with jQuery LazySizes where I use jpg and webp?
<picture>                   <source media="(max-width: 3500px)"                   type="image/webp"                   data-sizes="auto"                   srcset="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw=="                   data-srcset="                   /Responsive-Images/Voeren/Header-home/piano-player_c_scale%2Cw_600.webp 600w,                   /Responsive-Images/Voeren/Header-home/piano-player_c_scale%2Cw_1356.webp 1356w,                   /Responsive-Images/Voeren/Header-home/piano-player_c_scale%2Cw_1920.webp 1920w" class="lazyload img-responsive">                   <img                   data-sizes="auto"                   data-src="/Responsive-Images/Voeren/Header-home/piano-player_c_scale%2Cw_600.jpg"                   srcset="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw=="                   data-srcset="                   /Responsive-Images/Voeren/Header-home/piano-player_c_scale%2Cw_600.jpg 600w,                   /Responsive-Images/Voeren/Header-home/piano-player_c_scale%2Cw_1356.jpg 1356w,                   /Responsive-Images/Voeren/Header-home/piano-player_c_scale%2Cw_1920.jpg 1920w"                   src="/Responsive-Images/Voeren/Header-home/piano-player_c_scale%2Cw_600.jpg" class="lazyload img-responsive"                   alt="ein paar Hände hautnah spielen Klavier">                 </picture>
Regards & Thanks,
David

Hi David,
I've never used "srcset" before. So I will give it a try. If I come up with a solution I will let you know.
Best regards.

Hi Eren,
Thanks very much!!
Regards,
David


Consider removing patternMatch method from Functor

visit is a much more practical option on each cyclops-react type.

Merged in https://github.com/aol/cyclops-react/pull/451


fix admin verb to set unspawned ballisic ammo count

About the PR

Fixed #26362
Why / Balance

Technical details

I made the UpdateBallisticAppearance function public, I can't think of any reason that's a bad idea.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:ADMIN:

fix: setting ballistic ammo counts for a magazine should no longer be able to crash your game.

Thanks!


Packrat support

Packrat is, in my opinion, a necessary component in R projects these days, especially if there are multiple developers and/or multiple servers running your project's code.
While I could write my init.R to specify the exact package versions to install, it would be great if this buildpack could use Packrat to install dependencies since we're using it anyway.
When I deploy my code to a VPS for the first time (or when I add a dependency), it's just a matter of running packrat::restore() inside the project folder. If you're not familiar with the package, there's a local .Rprofile file that sources packrat/init.R. The restore function parses packrat/packrat.lock, which is like the Gemfile.lock file in a Ruby project, and runs install.packages for each specific package version. Tarballs for the dependencies are already in packrat/src/ (since they're checked in to git) and the dependencies are installed into packrat/lib/x86_64-apple-darwin15.6.0/3.4.3 (which is gitignored). So no need to go out to CRAN and download them, which is nice.
In my buildpack's init.R (not the packrat/init.R), I figured you could do something this:
my_packages = c("packrat")
install_if_missing = <snip>
invisible(sapply(my_packages, install_if_missing))

setwd("/app")
source(".Rprofile") # which just sources packrat/init.R
packrat::restore()

This doesn't work, though, since I'm apparently not in the app directory. If I replace the last three lines with
list.files("/app")
setwd("/app")
print(getwd())
print(list.files(getwd()))

then git push heroku master prints
remote: -----> Executing init.r script
remote:        [1] "data.R"                "environment.example.R" "init.R"
remote:        [4] "packrat"               "README.md"             "run.R"
remote:        [7] "server.R"              "ui.R"                  "wrapper.R"
remote:        [1] "/tmp/build_50bdef0edfab8ae27abbeb3a2c074a7c"
remote:        character(0)

So /app symlinks to a temp directory, which contains my app files. But when I try to enter that directory, the files disappear. Any idea what's going on? Thanks!

I'll investigating adding support for packrat.

I guess there are two ways of addressing this.
Firstly, for the least impact in the short term, taking your approach, using the init.R file to install the packrat package and running the package restore.
Secondly, in the medium term, to add "native support" by including packrat by default, changing the detection logic to look for a packrat directory (and/or packrat.lock file) in the root (possibly removing the need for the init.R file) to determine whether the R buildpack applies, and then to run the restore.
I'll try and get the first option working in the meantime.

Thanks for looking into this. My workaround for the time being is to parse the packrat.lock file myself in init.R and install the packages from the tarballs already contained in packrat/src:
pkgs <- as.data.frame(read.dcf("/app/packrat/packrat.lock")[-1, , drop = FALSE])

for (i in 1:nrow(pkgs)) {
  pkg <- pkgs[i, ]

  message("Trying to install ", pkg$Package)

  if (pkg$Package %in% rownames(installed.packages())) {
    message(pkg$Package, " is already installed")
  } else if (pkg$Source == "CRAN") {
    f <- file.path("/app/packrat/src", pkg$Package, paste0(pkg$Package, "_", pkg$Version, ".tar.gz"))
    message("...from ", f)

    install.packages(
      f,
      type = "source",
      INSTALL_opts = "--no-docs --no-help --no-demo"
    )
  } else if (pkg$Source == "github") {
    f <- file.path("/app/packrat/src", pkg$Package, paste0(pkg$GithubSha1, ".tar.gz"))
    message("...from ", f)

    install.packages(
      f,
      type = "source",
      INSTALL_opts = "--no-docs --no-help --no-demo"
    )
  }
}

Packrat supports more sources than just CRAN and GitHub, but this is good enough for my purposes right now.
Note: I also had to add .Rprofile to .slugignore so that that source("packrat/init.R") line isn't evaluated during compilation.

Yes, I found the issue with execution of the .Rprofile file during slug compilation. I tweaked the compile script by adding the --no-init-file switch to the command in my test, since .slugignore would cause the file not to be included at runtime, which wouldn't be desirable.
I've experimented with the first approach I suggested above, but without much luck. The main issue is that since the /app is symlinked into the fake chroot, under /app/.root/app, this causes issues when packrat tries to restore the packages. I tried copying the files instead of symlinking them, but then ran into other issues.
I have reached out to the Heroku team to see whether they have any ideas for a better way to package R given it's unique requirements and the restrictions imposed during slug compilation, which is why I had to resort to using a fake chroot.

See the heroku-buildpack-r-packrat-test project. You will see that packrat::restore() succeeds, however without the /app symlink and the project packages installed under /app/packrat/lib*, the slug size exceeds the limit of 500MB.
Also since /app is copied instead of being symlinked, if you have a multi-buildpack scenario, the files may become out of sync.

Hey @virtualstaticvoid, did the Heroku team have any ideas?

Hi @ankane
Yes, their feedback was to use the container stack together with a build manifest (heroku.yml).
I went ahead an implemented a compatible solution which will work for most cases, but will require rework if multiple buildpacks were used.
Currently I am working on implementing "native support" for packrat in the buildpack. See heroku-16-packrat branch. Note that this is still work in progress.

Thanks @virtualstaticvoid, I'll check out that branch. The general issue I've seen with container only solutions is it doesn't allow for the same fine-grained caching as buildpacks (like package-level caching). Even as containers gain popularity, I still think buildpacks are needed for fast deploys (Dokku does a great job combining both technologies).

+1
I definitely need packrat support in my project but I also need to run R along with Ruby, so it looks like the container approach is the way to go

Fixed by #123 .


Install Fails

attempting to install in latest dotnet cli (2.1.3) fails and displays following errors
PS C:\pscore\test> dotnet new -i "FiftyProtons.Templates.PSCore::*"
  Restoring packages for C:\Users\Chris\.templateengine\dotnetcli\v2.1.3\scratch\restore.csproj...
C:\Users\Chris\.templateengine\dotnetcli\v2.1.3\scratch\restore.csproj : error NU1103: Unable to find a stable package FiftyProtons.Templates.PSCore with version
C:\Users\Chris\.templateengine\dotnetcli\v2.1.3\scratch\restore.csproj : error NU1103:   - Found 2 version(s) in nuget.org [ Nearest version: 0.1.0-alpha1 ]
C:\Users\Chris\.templateengine\dotnetcli\v2.1.3\scratch\restore.csproj : error NU1103:   - Found 0 version(s) in Microsoft Visual Studio Offline Packages
C:\Users\Chris\.templateengine\dotnetcli\v2.1.3\scratch\restore.csproj : error NU1103:   - Found 0 version(s) in C:\Program Files\dotnet\sdk\NuGetFallbackFolder
  Generating MSBuild file C:\Users\Chris\.templateengine\dotnetcli\v2.1.3\scratch\obj\restore.csproj.nuget.g.props.
  Generating MSBuild file C:\Users\Chris\.templateengine\dotnetcli\v2.1.3\scratch\obj\restore.csproj.nuget.g.targets.
  Restore failed in 196.46 ms for C:\Users\Chris\.templateengine\dotnetcli\v2.1.3\scratch\restore.csproj.

Hmm - sorry about that; I'm at the airport right now but I'll give this a look as soon as I can.

I'm on a very low bandwidth connection at the moment, so I can't test this myself yet, but I believe the syntax has changed slightly - you should be able to use dotnet new -i FiftyProtons.Templates.PSCore (leave off the ::*).
Would you mind giving that a try and letting me know if it works for you, @clmcgrath?

Ah - I think I understand the issue. There are 2 problems. One is that there is no stable package (I'll publish one when I get back to civilisation) and the other is that no version was specified.
This worked for me (although it still complains about there not being a stable version):
dotnet new -i 'FiftyProtons.Templates.PSCore::0.1.0-alpha1'

dotnet new -i FiftyProtons.Templates.PSCore didn't work for me have the same errors as before,  but the dotnet new -i 'FiftyProtons.Templates.PSCore::0.1.0-alpha1' seems to be working

Ok, thanks - I'll update the instructions in the README until I can get a stable package published.

BTW, I've had a look at the latest version of PowerShell Core and things have moved around a little (for one thing, modules need to target netcoreapp2.0. I'll get the template updated :)

In the meanwhile, this is the basic project file you'll need:
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>netcoreapp2.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.PowerShell.SDK" Version="6.0.0-rc.2"/>
  </ItemGroup>
</Project>

ya i noticed that you were still targetting 1.6 after i generated a project from the template

Just tried updated template with PSCore RC2 and everything seems to work, so will publish a new package as soon as I have decent bandwidth.

Sorry for the delay, @clmcgrath - I completely forgot about this while I was travelling! Have published v0.2.2 (package should show up on NuGet in 20 mins or so) and I believe the issue will then be resolved :)


Install geoip by default.

Feature Request

Please install geoip (http://pecl.php.net/package/geoip) by default.

Will do.

Done. Can you please test it?

Works for me!


Unable to install on Ubuntu 16.10

Hi, when running the installation commands you provide, I get the following error message:
docker run --interactive --tty --rm --volume "/usr/local/bin:/silo_install_path" grpn/ansible-silo:2.1.0 --install
Installing from ansible-silo 2.1.0:

ansible will be created
cp: can't create symlink '/silo_install_path/ansible': Read-only file system
ansible-config will be created
cp: can't create symlink '/silo_install_path/ansible-config': Read-only file system
ansible-console will be created
cp: can't create symlink '/silo_install_path/ansible-console': Read-only file system
ansible-doc will be created
cp: can't create symlink '/silo_install_path/ansible-doc': Read-only file system
ansible-galaxy will be created
cp: can't create symlink '/silo_install_path/ansible-galaxy': Read-only file system
ansible-lint will be created
cp: can't create symlink '/silo_install_path/ansible-lint': Read-only file system
ansible-playbook will be created
cp: can't create symlink '/silo_install_path/ansible-playbook': Read-only file system
ansible-pull will be created
cp: can't create symlink '/silo_install_path/ansible-pull': Read-only file system
ansible-silo will be created
/silo/silo_functions.sh: line 447: /silo_install_path/ansible-silo: Read-only file system
chmod: /silo_install_path/ansible-silo: No such file or directory
ansible-vault will be created
cp: can't create symlink '/silo_install_path/ansible-vault': Read-only file system
Done

Do you have an idea what I'm missing? Is the problem my read/write access to "/usr/local/bin:/silo_install_path" ?

Sorry @jochenparm for the delay. Yes it probably is due to write permissions to /usr/local/bin.
You should be able to do it like that:
docker run --interactive --tty --rm --volume "/tmp/bin:/silo_install_path" grpn/ansible-silo:2.1.0 --install
sudo mv /tmp/bin/* /usr/local/bin

Let me know if that works for you or not.
This should probably be mentioned in the docs.

+1 for not abusing --privileged and leaving it to the user to have sudo rights to perform the move. That would allow prompting from mv in the future if the file existed already and the user was going to overwrite it.


Add native line bookmarking

VSCode Version: 1.20.1
OS Version: macOS 10.13

This is more of a feature request in order to add bookmarking of lines in to VSCode, so that you don't have to add an extension

We currently have no plans to add this as a core functionality.


Update translation

@abdelmjid-saber thanks for your contribution.
there are some notes you must do to accept this request.
1- the request is about translations, we are using JSON to translate the echo system so please use the same method.
2- you remove the default date from install script and that's make a conflict with blueprint of tomato-plugins so please update it back


Fix ic uninitialized warning in release build

Change logs

Fix ic uninitialized warning in release

Why are the changes needed?

Block the release build

Does this PR introduce any user-facing change?

nil

How was this patch tested?

no spec

Contributor's Checklist
Here are some reminders and checklists before/when submitting your pull request, please check them:

[ ] Make sure your Pull Request has a clear title and commit message. You can take git-commit template as a reference.
[ ] Sign the Contributor License Agreement as prompted for your first-time contribution.
[ ] List your communication in the GitHub Issues or Discussions (if has or needed).
[ ] Document changes.
[ ] Add tests for the change
[ ] Pass make installcheck
[ ] Pass make -C src/test installcheck-cbdb-parallel
[ ] Feel free to @cloudberrydb/dev team for review and approval when your PR is ready🥳

@my-ship-it after sign CLA, the CLA bot become reviewer ? so weird about this action 😆

Hi, @jiaqizho: it should happen like this and not affect your PR review. Two reviewers with write access are still required for your PR approval.


mysql 5.7 now use socket connect as default (not password)

mysql 5.7 new feature default use socket connect (not password)
I install mysql var apt in Ubuntu 18.04, but not asks for a password. and can not connect to mysql without password.
user@user:~$ mysql -u root
ERROR 1698 (28000): Access denied for user 'root'@'localhost'
user@user:~$ mysql -u root
ERROR 1698 (28000): Access denied for user 'root'@'localhost'

Solution
add a sudo and it works. fxxk.
user@user:~$ sudo mysql -u root
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 13
Server version: 5.7.22 MySQL Community Server (GPL)

Copyright (c) 2000, 2018, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql>

DO NOT WANT CODING ANY MORE, NO CODE IS THE BEST CODE.
Thanks to https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1752215/comments/3

ok.
Now I got no code https://twitter.com/fihtml/status/995858999344971776 . I lost all my code :-D

@imfht Good! That's the idea.

@lhcgoncalves  I think this repository has magical powers.


Profile during normal usage

As this will be running all the time on my laptop system, I would like it to be as efficient as possible. This ticket tracks doing some non-scientific profiling under average-ish conditions to see how it compares to my previous setup (QTile).
It'd be interesting to use this in order to measure improvements from #16 and #18.

#17 could also have an impact on CPU utilisation/wakeups, but I doubt it will have a big impact as most non-focused windows won't change their title.

I think I want to come up with some scripts that can be run under Xephyr which simulate:
No activity
Normal usage: occasionally switching groups, changing window title for active window (as if you're changing chrome tabs)
Heavy usage: constantly switching groups and changing window titles
For each of these scenarios, measure the amount of time spent on-cpu and off-cpu. (Possibly measure the number of wakeups/context switches as well?)
Then having some perf/flamegraph scripts that allow us to analyse the on-cpu time before/after our changes.

I did some very non-scientific tests using perf stat under no acitvity/heavy usage scenarios. My proposed changes for #16 and #18 do reduce the on-cpu time by about 50%, which I think is pretty good!
However, we're not actually using very much CPU at all (for heavy usage, about 0.009% vs. 0.004% with the changes) so I am going to resist coming up with any fancy scripts that we can run regularly to check for regressions. I think the biggest thing we can do is to minimise polling/wake-ups, so I think addressing #17 and #18 are both very worthwhile.


show server icon besides server name in server selection

suppose I have 2 servers with the same name but different icons, this helps differentiate between them.
plus, I think it looks better than just a simple wrench
I have tested this on a selfhost and it seems to work fine 😃

+1 on this, I can see it adding a better experience with server navigation (I sometimes happen to misclick the server, an icon could help)

Has this been tested on mobile?

Seems to work as intended on mobile, tested with Firefox mobile on a selfhosted YAG instance.

^, works fine on mobile

Do you think it would be a better idea to show the question mark image instead of the wrench if a server has no icon?

Would leave it as wrench to be fair, people are used to that now.
A question mark may confuse users into thinking that their server is unavailable or something along the line of that.


rubyfmt: avoid failing upon warning

Description of changes
Fixes https://github.com/NixOS/nixpkgs/issues/320722
The build was failing because there were unused variables. These were introduced by upgraded dependencies. We don't want to be bothered by such warnings in the future, so this removes the #![deny(warnings, missing_copy_implementations)] annotation.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

 It will not be installed.
        /private/tmp/nix-build-rubyfmt-0.10.0.drv-0/source/librubyfmt/ruby_checkout/ext/fiddle/extconf.rb:73: missing libffi. Please install libffi or use --with-libffi-source-dir with libffi sou>
        Check ext/fiddle/mkmf.log for more details.
  openssl:
        Could not be configured. It will not be installed.
        /private/tmp/nix-build-rubyfmt-0.10.0.drv-0/source/librubyfmt/ruby_checkout/ext/openssl/extconf.rb:101: OpenSSL library could not be found. You might want to use --with-openssl-dir=<dir> >
        Check ext/openssl/mkmf.log for more details.
  *** Fix the problems, then remove these directories and try again if you want.
  make[1]: Leaving directory '/private/tmp/nix-build-rubyfmt-0.10.0.drv-0/source/librubyfmt/ruby_checkout'

  --- stderr
  + cp enc/jis/props.h.blt enc/jis/props.h
  parse.c:9130:9: warning: variable 'yynerrs' set but not used [-Wunused-but-set-variable]
      int yynerrs = 0;
          ^
  1 warning generated.
  bigdecimal.c:7161:18: warning: variable 'prec' set but not used [-Wunused-but-set-variable]
      SIGNED_VALUE prec;
                   ^
  ripper.c:10310:9: warning: variable 'yynerrs' set but not used [-Wunused-but-set-variable]
      int yynerrs = 0;
          ^
  1 warning generated.
  1 warning generated.
  thread 'main' panicked at librubyfmt/build.rs:90:5:
  could not extract arch from rbconfig.rb
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

@bobvanderlinden do you think you could fix the build on darwin ?

do you think you could fix the build on darwin ?
Sorry, I already worked on a possible solution, but I couldn't find a good way to test it for darwin and got distracted :sweat_smile::disappointed: I have pushed the change. Could you give it a try?

Sorry, I already worked on a possible solution, but I couldn't find a good way to test it for darwin and got distracted 😅😞 I have pushed the change. Could you give it a try?

No worry !
Unfortunately I see no improvement:
  make[2]: Leaving directory '/private/tmp/nix-build-rubyfmt-0.10.0.drv-0/source/librubyfmt/ruby_checkout/ext/ripper'
  make[2]: Entering directory '/private/tmp/nix-build-rubyfmt-0.10.0.drv-0/source/librubyfmt/ruby_checkout'
  revision.h unchanged
  config.status: creating ruby-runner.h
  linking ruby
  make[2]: Leaving directory '/private/tmp/nix-build-rubyfmt-0.10.0.drv-0/source/librubyfmt/ruby_checkout'
  make[1]: Leaving directory '/private/tmp/nix-build-rubyfmt-0.10.0.drv-0/source/librubyfmt/ruby_checkout'
  make[1]: Entering directory '/private/tmp/nix-build-rubyfmt-0.10.0.drv-0/source/librubyfmt/ruby_checkout'
  *** Following extensions are not compiled:
  fiddle:
        Could not be configured. It will not be installed.
        /private/tmp/nix-build-rubyfmt-0.10.0.drv-0/source/librubyfmt/ruby_checkout/ext/fiddle/extconf.rb:73: missing libffi. Please install libffi or use --with-libffi-source-dir w>
        Check ext/fiddle/mkmf.log for more details.
  openssl:
        Could not be configured. It will not be installed.
        /private/tmp/nix-build-rubyfmt-0.10.0.drv-0/source/librubyfmt/ruby_checkout/ext/openssl/extconf.rb:101: OpenSSL library could not be found. You might want to use --with-open>
        Check ext/openssl/mkmf.log for more details.
  *** Fix the problems, then remove these directories and try again if you want.
  make[1]: Leaving directory '/private/tmp/nix-build-rubyfmt-0.10.0.drv-0/source/librubyfmt/ruby_checkout'

  --- stderr
  + cp enc/jis/props.h.blt enc/jis/props.h
  parse.c:9130:9: warning: variable 'yynerrs' set but not used [-Wunused-but-set-variable]
      int yynerrs = 0;
          ^
  1 warning generated.
  bigdecimal.c:7161:18: warning: variable 'prec' set but not used [-Wunused-but-set-variable]
      SIGNED_VALUE prec;
                   ^
  ripper.c:10310:9: warning: variable 'yynerrs' set but not used [-Wunused-but-set-variable]
      int yynerrs = 0;
          ^
  1 warning generated.
  1 warning generated.
  thread 'main' panicked at librubyfmt/build.rs:90:5:
  could not extract arch from rbconfig.rb

Lets first fix linux. We can fix darwin in another PR.


BLD: Meson __config__ generation

Changes
Add functionality to autogenerate build information from Meson information
In order to add new information, do the following:

Add the information as an argument in scipy/meson.build
Modify __config__.py.in to accept the new argument

New __config__.py:

 'print' mode

In [2]: scipy.show_config()
Build Dependencies:
  blas:
    detection method: pkgconfig
    found: 'True'
    include directory: /usr/include/x86_64-linux-gnu/openblas-pthread/
    lib directory: /usr/lib/x86_64-linux-gnu/openblas-pthread/
    name: openblas
    openblas configuration: USE_64BITINT= DYNAMIC_ARCH=1 DYNAMIC_OLDER=1 NO_CBLAS=
      NO_LAPACK= NO_LAPACKE=1 NO_AFFINITY=1 USE_OPENMP=0 generic MAX_THREADS=64
    pc file directory: /usr/lib/x86_64-linux-gnu/pkgconfig
    version: 0.3.20
  lapack:
    detection method: pkgconfig
    found: 'True'
    include directory: /usr/include/x86_64-linux-gnu/openblas-pthread/
    lib directory: /usr/lib/x86_64-linux-gnu/openblas-pthread/
    name: openblas
    openblas configuration: USE_64BITINT= DYNAMIC_ARCH=1 DYNAMIC_OLDER=1 NO_CBLAS=
      NO_LAPACK= NO_LAPACKE=1 NO_AFFINITY=1 USE_OPENMP=0 generic MAX_THREADS=64
    pc file directory: /usr/lib/x86_64-linux-gnu/pkgconfig
    version: 0.3.20
Compilers:
  c:
    commands: ccache, cc
    linker: ld.bfd
    name: gcc
    version: 11.3.0
  c++:
    commands: ccache, c++
    linker: ld.bfd
    name: gcc
    version: 11.3.0
  cython:
    commands: cython
    linker: cython
    name: cython
    version: 0.29.32
Machine Information:
  build:
    cpu: x86_64
    endian: little
    family: x86_64
    system: linux
  cross-compiled: 'False'
  host:
    cpu: x86_64
    endian: little
    family: x86_64
    system: linux
Python Information:
  path: /home/ganesh/os/sci/bin/python
  version: '3.10'

 'json' mode

{'Compilers': {'c': {'name': 'gcc',
   'linker': 'ld.bfd',
   'version': '11.3.0',
   'commands': 'ccache, cc'},
  'cython': {'name': 'cython',
   'linker': 'cython',
   'version': '0.29.32',
   'commands': 'cython'},
  'c++': {'name': 'gcc',
   'linker': 'ld.bfd',
   'version': '11.3.0',
   'commands': 'ccache, c++'}},
 'Machine Information': {'host': {'cpu': 'x86_64',
   'family': 'x86_64',
   'endian': 'little',
   'system': 'linux'},
  'build': {'cpu': 'x86_64',
   'family': 'x86_64',
   'endian': 'little',
   'system': 'linux'},
  'cross-compiled': 'False'},
 'Build Dependencies': {'blas': {'name': 'openblas',
   'found': 'True',
   'version': '0.3.20',
   'detection method': 'pkgconfig',
   'include directory': '/usr/include/x86_64-linux-gnu/openblas-pthread/',
   'lib directory': '/usr/lib/x86_64-linux-gnu/openblas-pthread/',
   'openblas configuration': 'USE_64BITINT= DYNAMIC_ARCH=1 DYNAMIC_OLDER=1 NO_CBLAS= NO_LAPACK= NO_LAPACKE=1 NO_AFFINITY=1 USE_OPENMP=0 generic MAX_THREADS=64',
   'pc file directory': '/usr/lib/x86_64-linux-gnu/pkgconfig'},
  'lapack': {'name': 'openblas',
   'found': 'True',
   'version': '0.3.20',
   'detection method': 'pkgconfig',
   'include directory': '/usr/include/x86_64-linux-gnu/openblas-pthread/',
   'lib directory': '/usr/lib/x86_64-linux-gnu/openblas-pthread/',
   'openblas configuration': 'USE_64BITINT= DYNAMIC_ARCH=1 DYNAMIC_OLDER=1 NO_CBLAS= NO_LAPACK= NO_LAPACKE=1 NO_AFFINITY=1 USE_OPENMP=0 generic MAX_THREADS=64',
   'pc file directory': '/usr/lib/x86_64-linux-gnu/pkgconfig'}},
 'Python Information': {'path': '/home/ganesh/os/sci/bin/python',
  'version': '3.10'}}

TODO

[ ] Add tests
[ ] Add release notes
[ ] Add docs

related: https://github.com/numpy/numpy/pull/20939#issuecomment-1336666340 | https://github.com/scipy/scipy/issues/16803 | https://github.com/numpy/numpy/pull/22769

Thanks @ganesh-k13, looks like a good start. Regarding the TODOs:

don't worry about release notes. We keep those on the wiki, I have already added an entry for this at https://github.com/scipy/scipy/wiki/Release-Note-Entries-for-SciPy-1.10.0#build-system-related-changes
A basic test would be nice
I see show_config is not present in our API docs right now. And there's no page at all on the main namespace - you could add it under http://scipy.github.io/devdocs/reference/index.html#api-definition. It needs only two entries: show_config and LowLevelCallable.

Ah nice, thanks for the info! I'll add them. Are the keys sufficient for SciPy? I removed SIMD and retained the rest.

I had a few doubts:

It needs only two entries: show_config and LowLevelCallable

Where and what to add for LowLevelCallable?

Fortran compiler and Pythran to the compilers section? And pybind11 to the dependencies section?

Fortran, was straightforward, but pythran was not a compiler, so let me explore. Same with pybind11 not being a proper dependency like blas, will take a look at this as well.

Where and what to add for LowLevelCallable?

Actually, it's already all wired up, but the scipy/__init__.py needs a cleanup and then we need a new reST file with .. automodule:: scipy. Let's do that in a separate PR, I can take care of that. That will make the show_config docstring show up too.

Fortran, was straightforward, but pythran was not a compiler, so let me explore. Same with pybind11 not being a proper dependency like blas, will take a look at this as well.

Ah good point. We do some custom checking and that doesn't include a version number. So let's forget about these for now. pybind11 should become a builtin Meson dependency later on, and then that will be easy. Maybe just add code comments for now to add these dependencies in the future?

@ganesh-k13 the macOS arm64 failure is relevant: dep.get_variable() doesn't work when the dependency is detected with CMake. It's possible to fish other variable names out of CMake (see https://mesonbuild.com/Reference-manual_returned_dep.html#depget_variable), but given that that's a fallback mechanism, it is probably more robust to just add a default value of 'unknown' to avoid Meson raising an error.

it is probably more robust to just add a default value of 'unknown' to avoid Meson raising an error.

I have added it in 4620153
Now, this should be an issue in NumPy as well yeah? Should I port this change there?

Now, this should be an issue in NumPy as well yeah? Should I port this change there?

Yes, it's a problem there too. Let's finish up this PR, and then it'd be great if you could sync the changes back to NumPy.

Sure, will do! Few minor changes in the cleanup portion also, will be nice to keep them in-sync.


Error by install jsPdf jspdf

I have a new computer and would like to install my project there.
npm install  aborts.
111 error path git
112 error code ENOENT
113 error errno ENOENT
114 error syscall spawn git
115 error enoent Error while executing:
115 error enoent undefined ls-remote -h -t<EMAIL_ADDRESS>115 error enoent
115 error enoent
115 error enoent spawn git ENOENT
116 error enoent This is related to npm not being able to find a file.
what can I do for use the jspdf ?
regards Ingo

The problem is with<EMAIL_ADDRESS>- either rollback jsPDF to  a version that references a different version of file-saver or yo could use NPM Shrinkwrap and manually specify<EMAIL_ADDRESS>THIS IS JUST AN EXAMPLE, NOT TESTED:
{     "dependencies": {         "jsPDF": {             "version": "1.5.3",             "from"<EMAIL_ADDRESS>            "dependencies": {                 "file-saver": {                     "version": "2.0.2",                     "from"<EMAIL_ADDRESS>               }             }         }     } }

Thank you just its run fine.
regards Ingo

@MrRio Please update dependency