various problems with pc to andoid conection

[ x] I have read the FAQ.
[ x] I have searched in existing issues.

Environment

OS: [Windows]
scrcpy version: [1.19.1]
installation method: [Windows release 1.19.1]
device model: Galaxy S9

Describe the bug
There was a lot of problems but i coud fix them with your help i just whant to recommend to add in the installation guide to use a USB 3 insted of a USB 2 port.
In my case i had issues with the conection it freezes sometimes the connection itself was unstable if it even start to connect and didnt just drop out.
For example i have to aktivate and deaktivate the usb settings everytime i try to start scrcpy.
Another one is that the connection was refuesed or if it was acceptet i cant click anything.
Best regards and thanks for this awesome code

Just updated ethernally script which facilitates wireless mirroring
https://github.com/fusionneur/ethernally
Let me know if you encounter any issue. Thank you


LazyMapTo with URL's chunk like parameter

Hello:
We are using a domain name for the adobe author instance (i.e. dom1), and we have another domain for the publish instance and angular application (call dom2).
We're using the lazymapto function, to load our components in runtime, just when it needed. The domain dom2, publish and angular application, works fine.
But the author instance in the editor mode, when it try to get the chunks for the application, raise an 404 error from the navigator, because the chunks files dont exists in the author instance (dom1), the chunks files exists in dom2. So the components don't  are visibles in the editor mode.
We would like a new version for lazyMapTo function that considers a new URL parameter. This parameter will indicate the origin from AEM must to load the chunk component. This solution will help too for manage multiple environments (i.e dev,stage,prod)
We have used the urlDeploy parameter for the build instruction in package.json.

@pescobar77 Thanks for raising this enhancement request.
Feel free to contribute a PR for the same :D


Definition of loss in pre-train phase

Hi, thanks for your great work. I'm just wondering if there is misalignment between the definition of loss in pre-train phase (here) and the Equation 2 in the manuscript? I think there should be a KL loss that author missed. Currently, MSE loss is used only.

Hi, thank you for your question.
In all experiments, we set the KL regularization coefficient $\lambda=0$ in pertaining. Because we have tested various $\lambda$ values and found $\lambda=0$ leads to the best performance. We hypothesize that this is because cell latent representations do not necessarily follow the prior normal distribution so that the KL penalty may introduce biases in the latent representation learning. This explanation has now been added to Supplementary Section 5.
Overall, the VAE pretraining should contain KL. However, we found that using only MSE in our datasets produces better results in our datasets. I think this is data-dependent. I will add the KL term back and update the codes.


fix: read deckfile "." location fixed

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 5 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 63.382%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

getdeck/utils.py
0
5
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
1132

Relevant Lines:
1786

💛  - Coveralls

LGTM


fix bug in rm -fa parallel deletes

Signed-off-by: baude<EMAIL_ADDRESS>

/approve

LGTM

LGTM

/lgtm


[Develop] Adding Middleware to Route Groups

Come to find out that the process for adding middleware to route groups is different than adding them to routes.
What I expected:
$app->group('/', function () { })->add('\Security:check');
Current
$app->group('/', \Security:check, function () { });
Where \Security:check must return a callable which is the middleware wrapped in a function.
So I would suggest 2 things.

We change the middleware to be added like route middleware which is a ->add at the end
We also add the resolveCallable onto that so that things get resolved properly.

:+1:

:thumbsup:

I was always a little uncomfortable with how routes and groups were done, so I wrote something to play with that made a new class of RouteGroup alongside Route.
I'll dig out the code and try to marge it back in to Slim3 (it was a while ago, and many things have changed).
What the code did was made routes and groups essentially the same thing (so things like middleware were handled exactly the same way), but one could have children. It followed the same principal for dispatching, but that part has to be updated due to the PSR-7 work in Slim since I wrote it.

@designermonkey any news about it?

Sorry guys, responsibilities have taken over again.

@designermonkey is the code available anywhere on Github or can it be available for us to take a look at?

Yeah, by all means. This component is never going to get used, so feel free to pull it apart. It was based on Slim anyway.
https://github.com/usebeagle/routes

Implemented.


1.3.0, 1.3.1 releases are incompatible with Ember Fastboot

Looks like changes made in #217 and released as 1.3.0 reference document which effectively breaks this library for projects also using ember fastboot.
ReferenceError: document is not defined
    at getScrollBarWidth (/var/folders/pw/kjxgyxss2wz0kj8lmfnd_vdm0000gn/T/broccoli-41877Iv5L0goPohmi/out-454-broccoli_persistent_filter_autoprefixer_filter/assets/addon-tree-output/ember-router-scroll/utils/scrollbar-width.js:11:1

@snewcomer it does not. There are still two references to document at the top of addon/index.js

🤦♂ 1.3.2?

@snewcomer that seems to have restored Fastboot compatibility on our project. Thanks for the quick turn around.


change sails.lift to sails.load

because sails.lift init http server … …and now port value "-1" is forbidden.
For now it throw

Fatal error: "port" argument must be >= 0 and < 65536

Merge, please

Okay; finally had some time to test the patch. Looks good. Thanks!

Published in v1.3.2.


Initial commit of webhook listener capability.

Coverage increased (+0.6%) to 57.303% when pulling 63dd0485820723464524fabbbf2f59859963c6b2 on webhook into 46dc6fea194b53538b6a3b7a7bda7d96979f96c7 on master.

Coverage increased (+0.6%) to 57.303% when pulling 63dd0485820723464524fabbbf2f59859963c6b2 on webhook into 46dc6fea194b53538b6a3b7a7bda7d96979f96c7 on master.


custom_components.ariston error HA 2024.4.1

Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/ariston/ariston_api.py", line 493, in async_connect
response = await self._async_post(
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/ariston/ariston_api.py", line 918, in _async_post
return await self.__async_request("POST", path, None, body)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/ariston/ariston_api.py", line 904, in __async_request
return await self.__async_request(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/ariston/ariston_api.py", line 907, in __async_request
raise Exception(response.status)
Exception: 403
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/config/custom_components/ariston/init.py", line 74, in async_setup_entry
reponse = await ariston.async_connect(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/ariston/init.py", line 49, in async_connect
return await self.api.async_connect()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/ariston/ariston_api.py", line 506, in async_connect
raise ConnectionException() from error
ariston.ariston_api.ConnectionException
Is anyone else getting this error after updating?

Same for me.

Same here.

same here :computer:

Same here.

Same on HA 2024.3.3

Same on 2024.3.1.

Same here

Hi gents,
same for me.
Made a quick test, seems to me that URL string is not found.
If you try to configure it from scratch seems that they removed temporarily the page:
https://www.ariston-net.remotethermo.com/api/v2/
Guess that they will publish again API web page again later or on another URL string.

Same here HA 2024.4.1

Same here, ariston server issue?
HA 2024.4.1

Ok I found the issue. Ariston blocked the python client. I don't know why.
Dear Ariston,
Please send me an email if you have a problem with this integration.
Thanks!
Sorry, but I have a workaround.

Ok I found the issue. Ariston blocked the python client. I don't know why.
Dear Ariston, Please send me an email if you have a problem with this integration. Thanks!
Sorry, but I have a workaround.

Hi,
What is workaround?
Thank you

Hi @fustom,
Would it be possible to do local integration to avoid blocking?  I guess it must require reverse engineering.  I'm not a developer but I can help with testing.

Fixed.

How do you fix it?
It is not working for me.

Hi @fustom,
Would it be possible to do local integration to avoid blocking? I guess it must require reverse engineering. I'm not a developer but I can help with testing.

Hi @dtalens
Check https://github.com/fustom/ariston-remotethermo-home-assistant-v3/issues/272

fixed, thx!

Fixed.

Working. Thank you

Working again, thx!

It works again but I have identified that power on/off is not working.

It doesn't matter what I do the action is not actually applied.

What is the solution?

Great! Thank you!

Hi @fustom,
Would it be possible to do local integration to avoid blocking? I guess it must require reverse engineering. I'm not a developer but I can help with testing.

Hi @dtalens
Check https://github.com/fustom/ariston-remotethermo-home-assistant-v3/issues/272

Link is not working

Fixed.

😊


ENG-578: IT (Part 1) - Manifest

Creates a fendermint_testing_materializer create, currently with just a Manifest type with some example JSON/YAML/TOML files and random generation, to circulate as an idea for how we could define a testnet.
The properties I added are just a baseline, we can add stuff as we go, like block intervals, checkpoint intervals, etc.
The idea is that there will be a Testnet type that parses and validates a Manifest, and then subsequently is able to generate a set of steps that can be executed by a Materializer to provision the thing. The Testnet will have types like nodes, relayers, whatever we need to talk to. The Materializer will have a log that it can use to figure out where it deployed things and how it can execute commands on the resources in the testnet. In the Testnet everything will have a unique resource name.
I added TOML and JSON examples but I think YAML is the most readable and it also supports comments, which might be handy in a manifest. The generated TOML is of course not the only way to do it, you could craft one manually and indent it, but why bother when we have YAML (as long as there is no hard-to-spot indent problems with yaml :confounded:)
TODO:

[x] Add nodes
[x] Add relayers
[x] TOML support

The Manifest is really shaping up as a TopologyDescriptor. I wonder if the Materializer should take a TopologyDescriptor and return a Manifest?

Thanks for these suggestions. The naming was influenced by CometBFT, but there are significant differences at the moment:

The CometBFT Manifest is the static description of a testnet that you'd either author by hand, or generate randomly
The CometBFT Testnet parses the manifest and chooses further random (but deterministic) values for the fields which aren't part of the manifest or are left empty. This is for repeatability in tests. It generates values for IP addresses and ports as well, which then the infrastructure has to allocate accordingly.

Our Manifest is the same as theirs, but the testnet is completely different, it delegates everything about resource allocation to the Materializer and doesn't have any randomness in it, it just drives the process of the order of calling the operations.
My intention with the Materializer is that one should be able to implement it concentrating on smaller actions, no procedure, just one thing at a time, such as allocating a node, creating a key, joining a subnet - the only thing they should ensure is repeated executions being idempotent, so some kind of persistent run log.
This could be implemented in the Materializer trait; at the moment it's in the Testnet but it rhymes with "take a topology and return a Manifest Testnet".


Enh/improve aniso bspline

Hello @eilidhmacnicol! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file nirodents/workflows/brainextraction.py:

Line 461:27: E231 missing whitespace after ','

Merging after testing locally...


Fix gsl file that has an internal "timeout" error for an hour

Example:
timeout
Bad eval: 1 at ./get_model_file.pl line 9.

This was found in the wild in ppg.report.


[luaruntime_channelMessagesList] can't display last chat message if chat message is larger than 1

fix just 2 char

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


Unsuccessful geometry transformation should error, not return untransformed geometry

Due to software being complicated, it is easy for people to end up with a mess of GDAL and PROJ and what-not paths not matching. If that happens, coordinate transformations will fail due to gdal(?) throwing errors like
ERROR 4: Unable to open EPSG support file gcs.csv.  Try setting the GDAL_DATA environment variable to point to the directory containing EPSG csv files.
ERROR 6: No translation for an empty SRS to PROJ.4 format is known.

Fiona does not treat those errors as more than messages (I assume they are printed by gdal, not Fiona). It will not fail and raise an exception but return the original geometry instead.
In [1]: from fiona.crs import from_epsg

In [2]: from fiona.transform import transform_geom

In [3]: p = {'type': 'Point', 'coordinates': (10, 53.5)}

In [4]: transform_geom(from_epsg(4326), from_epsg(25832), p)
ERROR 4: Unable to open EPSG support file gcs.csv.  Try setting the GDAL_DATA environment variable to point to the directory containing EPSG csv files.
ERROR 4: Unable to open EPSG support file gcs.csv.  Try setting the GDAL_DATA environment variable to point to the directory containing EPSG csv files.
ERROR 6: No translation for an empty SRS to PROJ.4 format is known.
Out[7]: {'type': 'Point', 'coordinates': (10.0, 53.5)}

In a notebook this might look like this:
from fiona.crs import from_epsg
from fiona.transform import transform_geom
p = {'type': 'Point', 'coordinates': (10, 53.5)}
transformed_p = transform_geom(from_epsg(4326), from_epsg(25832), p)
print(transformed_p)

printing

{'type': 'Point', 'coordinates': (10.0, 53.5)}

This is very bad and bound to lead to silent bugs since the error messages might not even be visible to the user (e.g. in a Jupyter Notebook they print to the shell where the notebook was launched).
If there is any way for Fiona to know about the issue, please raise an Exception!

No idea how Github handles notification but I submitted the issue too early and only added the content now. Posting this comment to notify about that. ;)

@kannes I've been able to reproduce this by setting GDAL_DATA to a bogus value:
$ GDAL_DATA=/tmp/foo python
Python 3.6.4 (v3.6.4:d48ecebad5, Dec 18 2017, 21:07:28)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from fiona.crs import from_epsg
>>> from fiona.transform import transform_geom
>>> p = {'type': 'Point', 'coordinates': (10, 53.5)}
>>> transform_geom(from_epsg(4326), from_epsg(25832), p)
ERROR 4: Unable to open EPSG support file gcs.csv.  Try setting the GDAL_DATA environment variable to point to the directory containing EPSG csv files.
ERROR 4: Unable to open EPSG support file gcs.csv.  Try setting the GDAL_DATA environment variable to point to the directory containing EPSG csv files.
ERROR 6: No translation for an empty SRS to PROJ.4 format is known.
{'type': 'Point', 'coordinates': (10.0, 53.5)}

The reason why GDAL error messages are escaping to the terminal is that you don't have any GDAL error handlers set up. This is done by configuring Python's logger and running your code within a with fiona.Env(): block.
>>> import logging
>>> logging.basicConfig()
>>> with fiona.Env():
...     transform_geom(from_epsg(4326), from_epsg(25832), p)
...
ERROR:fiona._env:Unable to open EPSG support file gcs.csv.  Try setting the GDAL_DATA environment variable to point to the directory containing EPSG csv files.
ERROR:fiona._env:Unable to open EPSG support file gcs.csv.  Try setting the GDAL_DATA environment variable to point to the directory containing EPSG csv files.
ERROR:fiona._env:No translation for an empty SRS to PROJ.4 format is known.
{'type': 'Point', 'coordinates': (10.0, 53.5)}

The tricky thing is that OGR doesn't necessarily consider the lack of a known transformation an error and by default will go on without it. I've talked to Even about this and he feels that once the user gets the support files configured, all these problems are solved. I mostly agree.
Mainly, the thing to do is get accustomed to executing Fiona's methods within an Env. Then you'll see something in Jupyter (which configures the logger) about support files not being found.


Custom format of builds

Hi and thanks for your package! (Saved me quite some time)
Using it in a standard NextJS/Prismic setup and saw/found out that I needed to change the format flag in the package.json build-all part to cjs:
"esbuild-esm": "esbuild src/main.ts --format=cjs --target=es6 --bundle --sourcemap=external --outfile=dist/esbuild/main.esm.js",
Not sure what's the best course of action, as in if it's possible to pick up the required format automatically from the project that's using this package 🤷
Anyway, just though I'd let you know 😄

you can do, const CanvasScrollClip = require('canvas-scroll-clip').default, should work. Decided to stick with esm setup as it had broader usage, at least that what my research showed when I was building the package.
The best case scenario would be an UMD, but esbuild doesn't support that.


[FLINK-3674] Add an interface for Time aware User Functions

This moves the event-time/processing-time trigger code from
WindowOperator behind a well defined interface that can be used by
operators (and user functions).
InternalTimerService is the new interface that has the same
functionality that WindowOperator used to have. TimerService is the user
facing interface that does not allow dealing with namespaces/payloads
and also does not allow deleting timers. There is a default
implementation in HeapInternalTimerService that can checkpoint timers to
a stream and also restore from a stream. Right now, this is managed in
AbstractStreamOperator and operators can ask for an
InternalTimerService.
This also adds tests for HeapInternalTimerService.
This adds two new user functions:

TimelyFlatMapFunction: an extension of FlatMapFunction that also
allows querying time and setting timers
TimelyCoFlatMapFunction: the same, but for CoFlatMapFunction

There are two new StreamOperator implementations for these that use the
InternalTimerService interface.
This also adds tests for the two new operators.
This also adds the new interface KeyContext that is used for
setting/querying the current key context for state and timers. Timers
are always scoped to a key, for now.
Also, this moves the handling of watermarks for both one-input and
two-input operators to AbstractStreamOperators so that we have a central
ground-truth.
There was also a bunch of small changes that I had to do to make the proper change more clean. I would like to keep these as separate commits because they clearly document what was going on.
Note for Reviewers
You should probably start from the tests, i.e. HeapInternalTimerServiceTest, TimelyFlatMapTest and TimelyCoFlatMapTest. Then, the other interesting bits are AbstractStreamOperator that now deals with watermarks and checkpointing the timers and the HeapInternalTimerService as well. Keep in mind that this is just moving the code from WindowOperator to HeapInternalTimerService with some generalizations. I didn't try to optimize any of the data structures that are used.
R: @StephanEwen @StefanRRichter @kl0u for review, please 😃

This PR disables RescalingITCase because the timers are checkpointed using the legacy/deprecated StreamCheckpointedOperator interface. (AbstractStreamOperator implements the interface because it keeps the timers.) The tests can be reactivated once @kl0u gets in his work on making the timers key-group aware.

R: @StefanRRichter @kl0u could you please review again, I pushed some changes and rebased on top of master.
Each commit can stand on its own and the purpose of each commit is documented in the commit message so you should probably review this commit by commit.

Thanks a lot for the review, @StefanRRichter! I addressed most comments by writing code, for some I only gave an answer that describes the rational.

Thanks for your comments @StefanRRichter and @kl0u. I incorporated most of them by now.

I updated this on top of the latest master with @StefanRRichter's state changes.
Please take another look, @StefanRRichter.

Rebased version looks good to me.


.Net: Transition to Polly.Core

Needs to be done after #3079.
The Polly package supports both v7 and v8 API's. The new Polly.Core package only supports v8 and is recommended for new projects (see getting started and migration guide).

The reliability support in SK has been replaced by relying on standard DI mechanisms, eg you can now use Microsoft.Extensions.Http.Resilience with SK, and it supports the latest versions of polly.


deployment error

Hi,
I get deployment error. The API names of the lwc components are invalid.
Please check.

Not able to duplicate.


h2o security implementation

Article checklist
ATTENTION: In your PR - add the ISSUE (topic form) # that this PR corresponds to. You can do this by also adding a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
If you have not already please go over our Resources Page for more tips and tricks on how to improve our overall technical writing.
Preliminary Checks - Formatting and Structure

[x] Does your article follow any of the suggested structure formats? - see example formats
[x] Is your article properly formatted in Markdown? - see Github Markdown guide
[x] Have you used the correct folder and file structure? - see Contribution Guidelines
[x] Is your article over 750 words? - Tool: Wordcounter.net
[x] Have you used our preferred heading structure? - H3 (###) and up
[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images
[x] In your PR - add a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid -  Grammarly
[x] Please place your article through a 3rd party plagiarism checker? We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide

Contribution guidelines
For first-time contributors and for more details, see Contributing Guidelines
This fixes #2291.

@pkalynan
Going over this and reading up on H20, I realize that you actually don't implement H20 security at any one point in this tutorial.
Correct me if I'm wrong but, I would expect you to show us how to setup an instance of H20 or point us to an article that does that. Then using this as a basis take us through implementing security for it.
Instead, you briefly touch on the security aspect, point us to the home page of H20's documentation and then move on to other ways of securing data that feel unrelated to H20.
To move forward, I need you to do one of two things:

Help me understand how the article covers the intended topic; "H20 security implementation"

or

Rewrite the article to cover the intended topic.

Kindly reply with the way you wish to move forward with this.

@adrianmurage
I would like to move forward with:

Help me understand how the article covers the intended topic; "H20 security implementation".

Instead of restating what is already on official documentation which is what @hectorkambow advises not to do, I added a link to the tutorial as a reminder. I could redirect the reader to a specific section of the installation and start-up of h2o.
The initial steps resolve internal security within the h2o instance, so that is a type of security attempt. This is something that is not an option in other modules, and it is unique.
H2o is a module that deals with data and to increase security within h2o; data files should be secure as well. Permissions is a topic already covered in other articles, so it was just there as a reminder.
Another is extremely backend solution if someone connected h2o to a Java database, where a basic Java If-then statement is an attempt to prevent SQL injection attacks. This is to help secure data from user input if an attack was targeting the database connected to h2o. Java is not too irrelevant since databases can be written in Java. Majority of data files came from a database at one point in the data analysis cycle which is why database was included.
I could change the title to become more appropriate. Options could include, "Data protection", or "H2O Data Protection". I could also explain in more detail what h2o is used for in this tutorial which is to perform data analyses.

@pkalynan
I agree with your approach.
Directing the reader to the specific sections in the documentation would be really helpful.
I think you should consider giving some information about H20 from the perspective of the 5W and H
(What, Why, Where, When, What, How).
Like the idea that H20 is unique(and why its unique) is a good example of such an elaboration.
I like the idea to align the Title with the content you intend to write about.
All in all, yes I now think I have an understanding of what your intention was.
Kindly @ me when you've updated the document.
Great job with the explanation to me. I appreciate it.

@adrianmurage
I made some changes as per your recommendations.
If you could let me know a title you would prefer, I can change the hero image and index.md file accordingly.
Thank you in advance.

plagiarism check done

@adrianmurage
I made some changes as per your recommendations.
If you could let me know a title you would prefer, I can change the hero image and index.md file accordingly.
Thank you in advance.

A heading that mentions the aspect of securing the data like: "Securing data with h2o" would be appropriate.
This is just a suggestion, feel free to tweak it as you see fit.

@pkalynan
I am done with the review.
Great job on this one! Looking forward to seeing more of your work.
Kindly finalize with the title of the article to enable me to update the front matter and label this ready for final review
@ me when you're done.

@adrianmurage,
Title changed in response to your helpful suggestion.
Thank you.

@pkalynan
I am done with the review.
Great job on this one! Looking forward to seeing more of your work.
Kindly finalize with the title of the article to enable me to update the front matter and label this ready for final review
@ me when you're done.

@adrianmurage,
Title changed in response to your helpful suggestion.
Thank you.

The PR has two index.md files.
Kindly make sure you delete the old index.md file and its directory h2o-security-implementation

@pkalynan
Great job with this article!
I'll make final changes then mark it for final review
Looking forward to more of your work

great work @pkalynan
Very easy to follow along
cc @adrianmurage  🚀


Mod compat issue: Lack of Deadly worldgen in some biome types

Relayed from: https://github.com/NillerMedDild/Enigmatica6/issues/2103

Apotheosis-1.16.4-4.5.2

This issue does not appear with just Apotheosis, so this is more of a PSA than anything.

Certain biomes, or perhaps biome groups, wont generate Apotheosis structures.
For example, in desert-type biomes, it seems to be impossible to locate boss chambers/dungeons and rogue spawners (the ones with blocks above them and vines surrounding them)
The best way to figure out if a biome is generating them, is to go into spectator mode, and give yourself night vision. When flying around the caves, you should be able to spot them fairly quickly if they generate in the biome your currently in.
The biomes that I've had issues locating structures in so far are:
-Jungle type biomes
-Desert type biomes
-Ice type biomes
I'll add more to this list as I find them. I should also mention the world type I have tested this on is the default option. I haven't checked other world types yet, as I usually use default. This doesn't appear to be an issue with Apotheosis directly, as a testing modpack I have with a few other mods, seems to generate structures from Apotheosis just fine.

Maybe related to #380 ?  I guess see if it persists with 4.6.0

It does I'm afraid.

is there perhaps a consistent set of biomes where it occurs?  And anything that they have in common?

The biometypes where this happens are
-Jungle type biomes
-Desert type biomes
-Ice type biomes
I'm not sure what they have in common though.

This is including vanilla biomes as well?  I swear I've seen stuff in deserts

It includes vanilla biomes as well, but remember this issue is not present with only Apotheosis and dependencies, so you probably have seen stuff in deserts.

From discussion on discord and CF, this appeared to be caused by YUNG's Better Dungeons   An issue was opened over there, but no response was ever received.
#502


add(components): Windstrap

Name
Link

Windstrap
https://windstrap.netlify.app

Windstrap is a set of Bootstrap Components CSS for TailwindCSS, so that it will work with Bootstrap JS.
https://windstrap.netlify.app
https://github.com/praveenjuge/windstrap

[x] My item is in the right category
[x] My item is logically grouped below similar items
[x] My item's name and description respects the conventions of the list
[x] My item is awesome
[x] I have read and followed the contribution guidelines

Thank you!


[Turbopack] Use hmr_to_commit data in HMR benchmark

Which project is this feature idea for?
Turbopack
Describe the feature you'd like to request
When running the next-dev benchmarks, I noticed that the hmr_to_eval and hmr_to_commit metrics are reporting the same numbers for Vite (~101ms)*, while for Turbopack it shows significant difference (~15ms vs ~54ms).
Since the eval-to-commit cost is shown to be significant in the Turbopack case, the hmr_to_eval benchmark for Vite seem to be flawed. I am not sure about the exact cause - this could be due to different HMR mechanisms, but there is definitely something wrong: the eval time and commit time should not be the same.
Given this, comparisons / claims based on the hmr_to_eval metrics should also be considered flawed. If there is no satisfactory solution to fix hmr_to_eval for Vite, then my suggestion is to use hmr_to_commit for comparisons instead. It is IMO also the more reasonable metrics to focus on since it better reflects HMR performance perceived by the user.
* The stats are gathered on M1 mbp with this PR to use SWC for Vite applied.
Describe the solution you'd like

Use hmr_to_commit as the metrics for comparing HMR performance, or at least include it alongside hmr_to_eval for reference.

Update public benchmarks accordingly.

Describe alternatives you've considered
Identify why hmr_to_eval and hmr_to_commit are showing identical numbers for Vite.
PACK-2501

Closing since Turbopack is no longer in this repo.

Closing since Turbopack is no longer in this repo.

Then please move it to the correct repo to preserve votes, subscribers, and history!


chore Fix compilation errors reported by GCC-13

Proposed changes
Issue Number: close #21214
Add missing headers to fix the compilation errors reported by GCC-13.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 41.96 seconds
stream load tsv:          462 seconds loaded<PHONE_NUMBER>9 Bytes, about 154 MB/s
stream load json:         22 seconds loaded<PHONE_NUMBER> Bytes, about 102 MB/s
stream load orc:          57 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          28 seconds loaded 861443392 Bytes, about 29 MB/s
insert into select:          68.6 seconds inserted 10000000 Rows, about 145K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230627063523_clickbench_pr_168516.html


Update for rules_swift 2.x

This fixes a missing _swift_vfs.yaml error related to the changes in: https://github.com/bazelbuild/rules_swift/pull/1191

When testing this we should ensure bazel clean --expunge is run because the vfs rule is not hermetic.
The current changes help get the missing vfs file added but then leads to:
error: cannot load underlying module <Module>

Should be fixed now! @brentleyjones tested on their project.
@thiagohmcruz mind testing that this works for you as well in rules_swift 1.x and ideally also in 2.x? 🙏🏼
Going to test in cash soon

Per Slack, this has BwtB issues still.

I updated the extended_module_map rule to forward CcInfo with the generated files, hoping that fixes any BwtB issues (we don't use that feature yet so cant really test).
I did verify this builds for us using bazel clean --expunge && bazel build //... --disk_cache= --remote_cache= to ensure no left over build artifacts.
If CI goes green I'm going to merge to unblock using rules_swift 2.0 and we can follow up with any other improvements if we run into them.


Automatically adjust .gitignore on local:init

In GitLab by @robertlemke on Dec 12, 2018, 09:38
Local Beach should check and adjust the .gitignore so that:

.LocalBeach is not checked in
Configuration/ is checked in, so that the database configuration in Configuration/Development/Beach/Settings.yaml is part of the project

.LocalBeach could just be appended to .gitignore
For the configuration it's a bit more complicated (there might be some rules already set up…) so we could just force-add the created Settings.yaml. That way the developer clearly sees it's there and should be versioned and can adjust things on her own as needed…


What's not getting copied?

With the temporary logging I added for #2, I get this for “Indiana Jones and the Fate of Atlantis”:

(Blocks copied: 9,948 of 9,951; 3 remain)

and this for Mac OS 9.0:

(Blocks copied: 50,883 of 50,885; 2 remain)

Either there's still some file or files that haven't been fully copied, or one or more blocks are undercounted in the numerator or overcounted in the denominator.

I added code to ImpHFSVolume that creates a mutable copy of the volume bitmap, and to the innermost reading method to uncheck bits as the corresponding blocks are read from. I also added a method that reports on the contents of that bit vector, and a call to that method at the end of the converter.
(Blocks copied: 50,883 of 50,885; 2 remain)
100%: Updating catalog…
Of the 50982 blocks that are marked as allocated, 0 have not been read from
(minus 97 blocks for the extents overflow file, not copied)

50982 - 97 = 50885, so that much checks out.
So why does this method undercount the number of blocks copied by (on this volume) two blocks?

It looks like this is because ImpHFSVolume (intentionally) does not read blocks that aren't needed to satisfy the remaining logical length. This CD-ROM has a couple of files whose physical extents are bigger than needed for their logical lengths. If the remaining logical length is less than the total size in bytes of the extent, the reading method rounds the remaining logical length up to the block size and just reads that.
If I change the code that marks off blocks as read to use that number of blocks instead of the number from the extent, then the report correctly identifies two blocks as having not been read:
0%: Copying file “Desktop DF”…
2023-02-21 19:43:02.080807-0800 impluse-hfs[84545:18456638] Underrun alert! Data is not big enough to hold this extent. Only reading 18 blocks out of this extent's 20 blocks
This file's lengths are DF 580034 bytes, RF 0 bytes. Physical sizes 56 blocks + 0 blocks = 56 blocks. Copied 54 blocks + 0 blocks = 54 blocks
⋮
Blocks that have not been accessed: 54219 through 54220
Of the 50982 blocks that are marked as allocated, 2 have not been read from

This file has two extents, covering 36 and 20 blocks. The logical length is 0x8d9c2 bytes and the block size is 0x2a00 bytes.
36 blocks is 0x5e800 bytes, which leaves 0x2f1c2 bytes remaining to be read. 20 blocks is 0x34800 bytes; inversely, 0x2f1c2 is just under 18 blocks.
So yeah, this file is shorter than its physical allocation.
I'm unsure what to do with this. Technically, this is correct, but it's unsettling. In theory, this could be a symptom of an underread, though it appears to not be.
I guess I could add a new argument to the reader block indicating how many a-blocks were skipped because they weren't needed? Then the converter can add those blocks to the count of blocks copied as a sort of acknowledgment.
Another option would be to stop auto-truncating the data at the volume read level. Read the whole extent, no matter what, and let the client (the converter) truncate it to the logical length. Then it's a little more accurate to say that those blocks were read.
I also have to wonder if there are any applications that are relying somehow on having files bigger than their logical length, concealing data past the end of the file.

Incidentally, DiskWarrior prunes extents that are longer than needed for the logical length. Huh.


Increase code coverage to at least 80%

Increase the code coverage for critical pieces of the application to at least 80%.

Remainder of coverage moved to #13


don't feed non valid laser data to stereo tracker and skip

I noticed this problem when running lpslam_node requesting the laser data to be SystemDefaultsQoS (reliable) and having the laser data published in SensorDataQoS (best effort).
QoS incompatibility resulted in having an empty laser data which caused a crash in lpslam_node. When the laser data is empty or not valid, it shouldn't be fed to the tracker and no map can be created in this case.

From this patch it looks like when you have no laser scanner, you never will be able to do OpenVSLAM tracking. Is it as intended?
Does the crash appear in OpenVSLAM? If so, I suppose this could be untracked laser scan validity in occupancy_map_exporter::map_export() when calling get_laser_rays_in_world().
So, the problem of lost laserscan data is better to be resolved on OpenVSLAM side, maybe starting to look into get_laser_rays_in_world() routine:
diff --git a/src/openvslam/laser/laser_scanner_2d.cc b/src/openvslam/laser/laser_scanner_2d.cc
index 935650d..14c118c 100644
--- a/src/openvslam/laser/laser_scanner_2d.cc
+++ b/src/openvslam/laser/laser_scanner_2d.cc
@@ -61,6 +61,10 @@ std::vector<std::pair<Vec3_t, Vec3_t>> laser_scanner_2d::get_laser_rays_in_world
     std::vector<std::pair<Vec3_t, Vec3_t>> pts;
     pts.reserve(data.get_ranges().size());

+    if (!data.size()) {
+        return nullptr;
+    }
+
     internal_in_world(data, cam_pose_cw, [&pts](Vec3_t cam, Vec3_t target ) {
         pts.push_back({cam, target});
     });

Here are just my thoughts on it, @ItsJas looking forward for your respond.

@AlexeyMerzlyakov The context of crash is having empty laser data, It happened to me because of QoS incompatibility. I originally did it that way as a fast fix to avoid the crash.
In the meantime I was willing to look at it a bit more and discuss the behavior that we want to have in this case.
I totally agree that it would be better to still have the tracking going on and treat it more low level like not try to create the occupancy grid which is the part causing the crash or handle the empty laser data case in it (working on it).
But it's important to think of scenarios where the laser data is not valid or temporarily empty/unavailable and how to handle the situation and if it's possible to recover after it.
And also to keep in mind that originally the node is supposed to get stereo images and laser data to provide an occupancy grid map. So if that's not possible, what should it do instead?
@Trilion99 What do you think?

As far as I understand, currently for OpenVSLAM (LP-version) is using stereo-camera plus odometry data for tracking. Laser data is being used only for plotting OccupancyGrid maps. Please correct me, if I wrong. In this case, laser data is not so important as camera or odometry source, since even if the laser data is being lost for some time, tracking will still be stable, and the robot pose will be defined in any period of time. I think, the right solution here - is to skip these invalid laser frames and do not paint them on map, until laser scanner won't be available again. The tracking shouldn't be suffer.
Looking into code base of LP-OpenVSLAM shows that laser scanner data is being stored in laser_landmark class. All calls to laser_2d_ field are already safe (being checked for validity), except one: laser_landmark::get_laser_rays_in_world(). This directly calls laser_scanner conversion methods, which might cause an issue. So, it looks like (almost?) all protection for invalid laser scanner frames is already made. And in this case I would like to propose to start from something like this change:
--- a/src/openvslam/data/laser_landmark.cc
+++ b/src/openvslam/data/laser_landmark.cc
@@ -24,8 +24,12 @@ std::vector<Vec3_t> laser_landmark::get_points_in_world() const {
 }

 std::vector<std::pair<Vec3_t, Vec3_t>> laser_landmark::get_laser_rays_in_world() const {
+    if (laser_scanner_ == nullptr || !laser2d_.is_valid()) {
+        return {};
+    }
+
     return laser_scanner_->get_laser_rays_in_world(laser2d_, ref_keyfrm_->get_cam_pose());
 }

However, that may not be enough. Yesterday, I've looking more into laser_landmark::get_laser_rays_in_world() and found that even if laser2d_ is invalid, get_laser_rays_in_world() will return empty vector of data, that already do patch from above. So this is probably not the real case of this problem (and its fix). That is why I've asked to share the backtrace in a message before.

@AlexeyMerzlyakov I totally agree with you. The tracking should still happen as long as we have stereo images and odometry.
The patch looks PGTM. The crash is indeed happening in laser_landmark::get_laser_rays_in_world(). I tested the fix and it prevented the crash as expected.
As for the backtrace, it's pretty much the segmentation fault that I mentioned previously in this issue.
Thinking back at it, other than the QoS mismatch this could've happened in some cases where the laser Gazebo  plugin is not loaded properly for some reason.

Indeed, the patch from above should work. As I've mentioned, the problem was not only in non-valid laser2d structure, but also is that if this structure is not set, initializer or keyframe_inserter won't connect laser_landmark with a keyframe in some cases. This leads to laser_landmark is being created with default constructor where ref_keyfrm_ = nullptr; and laser_scanner_ = nullptr;. Later in the code zero-pointer dereferencing causes segfaults. So, actually the first part of check from that patch laser_scanner_ == nullptr is crucial for that issue.

Closing this since it wasn't the right fix for the issue.
Going to proceed with fixing it OpenVSLAM side as suggested by Alexey.


Add dill serialization support

@Flood1993 If you agree, I will add this PR and #125 before next release.

@Flood1993 As you can see the new serializer is covered by old tests:
https://codecov.io/gh/opensistemas-hub/osbrain/commit/d25313e852fe72b49bfe649c7af82681b400761a
Do you think there are still missing tests anyway? If so, I'll add them before merging, but right now I can't think of a test that is missing for this change.


[Improve] Dynamic parameters changed to properties

Currently, flink job in streampark can specify properties. The current name is "Dynamic parameters", In order to reduce user confusion, It needs to be exactly the same as the name of this parameter in flink.
Relevant description information in flink official website:
Allows specifying multiple generic configuration
options. The available options can be found at
https://nightlies.apache.org/flink/flink-docs-stable/
ops/config.html
Contribution Checklist

If this is your first time, please read our contributor guidelines: Submit Code.

Make sure that the pull request corresponds to a GITHUB issue.

Name the pull request in the form "[Feature] Title of the pull request", where Feature can be replaced by Hotfix, Bug, etc.

Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review.

If the PR is unfinished, add [WIP] in your PR title, e.g., [WIP][Feature] Title of the pull request.

-->
What changes were proposed in this pull request
Issue Number: close #1885

Brief change log

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): no

LGTM


SAK-42836 Enhance the gb submission messager tool

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 3

Complexity increasing per file
==============================
- webcomponents/tool/src/main/frontend/sakai-submission-messager.js  4
- gradebookng/tool/src/java/org/sakaiproject/gradebookng/rest/GradebookNgEntityProvider.java  7

See the complete overview on Codacy


Allow specifying training epochs when calling run_cli

The number of training epochs seems to be hardcoded to 24 and isn't overwritten anywhere(maybe I'm missing something?), this PR adds a new input argument extra_trainer_config_args to run_cli, I think it's better than directly adding epochs as input because it's more flexible and can be used to specify other trainer args in the future.
The default behavior is unchanged.

Thanks for your contribution!


Client Allocation Request for: kim

Client Allocation Questions
Core Information

Name: kim
Website / Social Media: https://www.instagram.com/kyooungbin/
Region: Greater China
DataCap Requested: 16GiB
Addresses to be Notarized: f1qlc4n3fjtwn7ckk7w2gden7zg5gfl6wg3aj7jfq
Notary Requested: dannyob

@kyoungbinkim Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

See #1561


undefined method `stringify_keys' for #Array:0xb2490950 with Rails 3

When I edit a form relating a model with 'has_magic_columns' I get this error:
undefined method `stringify_keys' for #Array:0xb2490950
NoMethodError in ContactsController#update
undefined method `stringify_keys' for #Array:0xb2490950
Rails.root: /home/riccardo/git/cloud-assets
Application Trace | Framework Trace | Full Trace
app/controllers/contacts_controller.rb:66:in update' app/controllers/contacts_controller.rb:65:in update'
Request
Parameters:
{"commit"=>"Update Contact",
"contact"=>{"job_start(1i)"=>"2011",
"job_start(2i)"=>"9",
"job_start(3i)"=>"30",
"unix_name"=>"jdell",
"picture_url"=>"/images/contacts/anonymous.jpg",
"initials"=>"CC",
"tags"=>"",
"male"=>"1",
"mobile"=>"",
"phone_ext"=>"",
"dell_id"=>"999999998",
"birth(1i)"=>"1940",
"birth(2i)"=>"9",
"personal_email"=>"",
"team_id"=>"1",
"active"=>"1",
"birth(3i)"=>"27",
"givenname"=>"Xxxxx"},
"authenticity_token"=>"MYUYzl4yVaeDNz2E+4B6WXJHpjHtf8PaQ3aYpt9KQ20=",
"_method"=>"put",
"utf8"=>"✓",
"id"=>"22"}

I'd have to see the controller code to tell you for sure but it looks like your controller is calling update_attributes with an Array instead of a Hash. Post the code for your action and your Rails version.

Closing due to lack of activity. If you still need help, please post the followup information I requested and I'll re-open the issue.


Fix indent for defaultDeployment

IMHO the indent of the resources block is to large in die default Template.
Not really important, but I think it would be nice to stay consistent with the rest of the yamls (which have a 2 space indent).
For comparison:
Old:
        resources:
            limits:
              cpu: 100m
              memory: 128Mi
            requests:
              cpu: 100m
              memory: 128Mi

New
        resources:
          limits:
            cpu: 100m
            memory: 128Mi
          requests:
            cpu: 100m
            memory: 128Mi

Thanks!


dbeaver/dbeaver#546 Notification settings

I think it's better to keep values selector right near the label

Did we really have popup and sound for filter saving, UUID copying and finishing transformation from source code to sql? It doesn't look like a long operations. Do we need them here?

Notification sound doesn't play if Show popup is disabled

Verified


MovingWorld crash

In an attempt to use "Archimedes Ships Plus" its support library appears to have triggered a null-pointer dereference in CCTweaks.
To me it appears as though MovingWorld attempts to set the "ship" into motion and this causes a connection issue with the network cables and/or modems while CCTweaks is running its "onServerTick" handler.
To be honest I'm not sure if the crash belongs here or should be reported to ComputerCrafts issue tracker directly, so I am going to do both.
Forgot this, initially:
Forge Version: <IP_ADDRESS>4
Minecraft: 1.7.10
ComputerCraft: 1.75
CCTweaks: 3.3.7
Crash log from the server follows:
[21:22:25] [Server thread/ERROR]: Encountered an unexpected exception
java.lang.NullPointerException
at dan200.computercraft.shared.peripheral.common.TilePeripheralBase.getPeripheralType(TilePeripheralBase.java:103) ~[TilePeripheralBase.class:?]
at dan200.computercraft.shared.peripheral.modem.TileCable$2.canConnect(TileCable_Patch.java:109) ~[TileCable$2.class:?]
at org.squiddev.cctweaks.core.network.NetworkHelpers.getAdjacentNodes(NetworkHelpers.java:45) ~[NetworkHelpers.class:?]
at org.squiddev.cctweaks.core.network.NetworkHelpers.getAdjacentNodes(NetworkHelpers.java:35) ~[NetworkHelpers.class:?]
at org.squiddev.cctweaks.core.network.AbstractWorldNode.getConnectedNodes(AbstractWorldNode.java:30) ~[AbstractWorldNode.class:?]
at org.squiddev.cctweaks.core.network.cable.SingleModemCable.getConnectedNodes(SingleModemCable.java:25) ~[SingleModemCable.class:?]
at org.squiddev.cctweaks.core.network.AbstractWorldNode.connect(AbstractWorldNode.java:37) ~[AbstractWorldNode.class:?]
at org.squiddev.cctweaks.core.network.cable.BasicCable.connect(BasicCable.java:68) ~[BasicCable.class:?]
at org.squiddev.cctweaks.core.network.cable.SingleModemCable.connect(SingleModemCable.java:19) ~[SingleModemCable.class:?]
at dan200.computercraft.shared.peripheral.modem.TileCable$3.run(TileCable_Patch.java:143) ~[TileCable$3.class:?]
at org.squiddev.cctweaks.core.FmlEvents.onServerTick(FmlEvents.java:48) ~[FmlEvents.class:?]
at cpw.mods.fml.common.eventhandler.ASMEventHandler_184_FmlEvents_onServerTick_ServerTickEvent.invoke(.dynamic) ~[?:?]
at cpw.mods.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:54) ~[ASMEventHandler.class:?]
at cpw.mods.fml.common.eventhandler.EventBus.post(EventBus.java:140) ~[EventBus.class:?]
at cpw.mods.fml.common.FMLCommonHandler.onPreServerTick(FMLCommonHandler.java:260) ~[FMLCommonHandler.class:?]
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:536) ~[MinecraftServer.class:?]
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:396) [MinecraftServer.class:?]
at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:685) [li.class:?]

This isn't fixed, but I'm closing it as I can't do any more. The above commit should prevent similar issues with other mods/scenarios.

I'd have attempted to find a fix myself, but I am woefully unprepared for
Java after spending many long years learning the tricks of C and C++ and
transitioning to Perl and Python.
DRH
On Mon, May 23, 2016 at 3:45 PM, SquidDev<EMAIL_ADDRESS>wrote:

This isn't fixed, but I'm closing it as I can't do any more. The above
commit should prevent similar issues with other mods/scenarios.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/SquidDev-CC/CCTweaks/issues/100#issuecomment-221074853


Patched a potential segfault when appending simulations

I had some problems when calling the ``append_simulations` method. In a Jupyter Notebook, it would kill the kernel every time without further notice. In a script, one can see this is due to a segmentation fault.
After some debugging, I spotted the problem when checking the Z-score of the data. In my case, the result of the simulation was two vstacked time series (external input and simulated time series; the tensor shape was (batch_size, 2, n_data)). For testing purposes, I was training the SBI only with a single realization of the external input, thus leading to 0 variance among all batches.
Despite this not being a very common use case, the fact that it kills the Python kernel makes the problem difficult to track for the user: there is no error message and the debugger does not work properly (it will just crash, not going inside the SBI code). Even print statements inside the function append_simulations would not print out in a notebook, being visible only when used on a script.
For this reason, I added a small extra check in the code. If this edge case arises, the computation of the Z-score is skipped, and now the user is adequately warned about the problem so it can be fixed when needed. From what I have seen code would run afterwards without problems.

Hi @VictorSeven, thanks for making this PR and sorry for the delayed response.
I am not sure I understand the use-case of training with only a single training-data point. But I agree that this edge case should not result in a segmentation fault and should be documented with a warning.
I suggest to just check whether num_unique == 1 in line 35.
If yes, raise the warning, if no perform the z-scoring and the original check implemented in the function.
Do you see what I mean?
At the moment the tests are failing at the black formatting check. You can fix this by running black filename (as well as isort and pyright) locally before committing.
Best regards, and thanks again for looking into this
Jan

Hello, sorry for the delay -was a bit sick last weeks.
I have updated the change as suggested to use num_unique instead. I run black and so on as indicated so I hope now everything should be correct. Let me know if there is any additional problem.
About use case: I understand the confusion about the use case of training with a single data point. In my case, my dynamical system was always subject to a single external input, which I was not passing to SBI, because it was always the same. Then, I wanted to train SBI to recognise several different external inputs. As a test, I rewrote the code where now SBI was aware of the external input, and I was to check if giving it only 1 would yield the same results as I had before. I understand it was maybe not intended usage and this led to an error, but the main problem was that the Python kernel would just silently crash, making it difficult to debug the problem.

Codecov Report

Merging #803 (88f88e3) into main (2a114f4) will increase coverage by 0.08%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #803      +/-   ##
==========================================
+ Coverage   74.76%   74.85%   +0.08%
==========================================
  Files          80       80
  Lines        6190     6199       +9
==========================================
+ Hits         4628     4640      +12
+ Misses       1562     1559       -3

Flag
Coverage Δ

unittests
74.85% <100.00%> (+0.08%)
:arrow_up:

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

Impacted Files
Coverage Δ

sbi/utils/sbiutils.py
80.22% <100.00%> (+0.46%)
:arrow_up:

... and 22 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Dangerfile should use failure instead of fail

On the repo, ensure that Dangerfile matches https://github.com/sous-chefs/repo-management/blob/master/Dangerfile

@tas50 should this now be raise? I've seen it in a few prs

Rubocop is going to want raise. If that's not going to work with Danger and CI then we should get that pushed out in .rubocop.yml files

@Xorima 👆

Ok I will add this to my todo list today

Closing now as every single cookbook repo is done, every single issue is now closed.


Experiencing Error in Script Execution.

Greetings,
Firstly, I would like to thank you for providing this open-source tool. I am new to programming and was trying to run the package you provided. I am consistently experiencing error. Please refer to screenshot of error message below. Please do advise me on how to troubleshoot.
Regards,
Ben

Hi,
As it is specified in the readme of this repository (section "Installation"), falcon should be run on Linux or OSX but not Windows (as explained by @bittremieux  in issue #9). Many Linux distributions are freely available and can be installed on a computer (possibly in dual boot with windows) or executed within a virtual machine (see VirtualBox).
Best regards,
Kilian

The error you see is because the input directory has not been specified correctly. In the example on the main page the directory with peak files is peak/, in your case this would be E:\MS_RAW_Files\..., so without the peak/ prefix.
However, even when specifying the input peak files correctly, falcon indeed only runs on Linux or OS X, not on Windows. Possibly the Windows Subsystem for Linux could be used to run falcon in your Windows environment without needing a dual-boot system, but this functionality has not been tested.


Can't assign NonEmpty to SortedMap when using map.set(k,v) - typescript compilation errors on ts5.5.2 & rimbu 2.0.2

Fails this very simple test code on typescript 5.5.2:
import { SortedMap } from "@rimbu/core";
const empty_map: SortedMap<number, number> = SortedMap.empty<number, number>();
let m1: SortedMap<number, number> = empty_map.set(1, 1);

src/temp_ts.ts:3:5 - error TS2322: Type 'NonEmpty<number, number>' is not assignable to type 'SortedMap<number, number>'.
  Types of property 'nonEmpty' are incompatible.
    Type '() => true' is not assignable to type '() => this is NonEmpty<number, number>'.
      Signature '(): true' must be a type predicate.

3 let m1: SortedMap<number, number> = empty_map.set(1, 1);
      ~~

Found 1 error in src/temp_ts.ts:3

tsc --version
Version 5.5.2

The js code runs correctly, only typings are problematic.
Can't provide links to sandbox as your sandbox is obsolete (have very old version of rimbu and ts)

Another/simpler way to reproduce:

Download main from this repo (2.0.2)
yarn add typescript@latest
yarn build

It will fail with the following error:
   ×  @rimbu/collection-types:build
       _cjs_prepare/map-custom/interface/index.cts(245,20): error TS2430: Interface 'NonEmpty<K, V, Tp>' incorrectly extends interface 'VariantMapBase<K, V, Tp>'.
         Types of property 'nonEmpty' are incompatible.
           Type '() => true' is not assignable to type '() => this is WithKeyValue<Tp, K, V>["nonEmpty"]'.
             Signature '(): true' must be a type predicate.
       _cjs_prepare/map-custom/interface/index.cts(449,20): error TS2430: Interface 'NonEmpty<K, V, Tp>' incorrectly extends interface 'Omit<RMapBase<K, V, Tp>, keyof NonEmpty<any, any, any>>'.
         The types returned by 'addEntries(...)' are incompatible between these types.
           Type 'Tp["nonEmpty"]' is not assignable to type 'Tp["normal"]'.
             Type '"nonEmpty"' is not assignable to type '"normal"'.
       _cjs_prepare/map-custom/interface/index.cts(1010,33): error TS2322: Type 'StreamSource<readonly [K, V]> & WithKeyValue<Tp, K, V>["nonEmpty"]' is not assignable to type 'Tp["normal"]'.
         'Tp["normal"]' could be instantiated with an arbitrary type which could be unrelated to 'StreamSource<readonly [K, V]> & WithKeyValue<Tp, K, V>["nonEmpty"]'.
       _cjs_prepare/set-custom/interface/base.cts(193,20): error TS2430: Interface 'NonEmpty<T, Tp>' incorrectly extends interface 'VariantSetBase<T, Tp>'.
         Types of property 'nonEmpty' are incompatible.
           Type '() => true' is not assignable to type '() => this is WithElem<Tp, T>["nonEmpty"]'.
             Signature '(): true' must be a type predicate.
       _cjs_prepare/set-custom/interface/base.cts(319,20): error TS2430: Interface 'NonEmpty<T, Tp>' incorrectly extends interface 'Omit<RSetBase<T, Tp>, keyof NonEmpty<any, any>>'.
         The types returned by 'addAll(...)' are incompatible between these types.
           Type 'Tp["nonEmpty"]' is not assignable to type 'Tp["normal"]'.
             Type '"nonEmpty"' is not assignable to type '"normal"'.
       _cjs_prepare/set-custom/interface/base.cts(618,33): error TS2322: Type 'StreamSource<T> & WithElem<Tp, T>["nonEmpty"]' is not assignable to type 'Tp["normal"]'.
         'Tp["normal"]' could be instantiated with an arbitrary type which could be unrelated to 'StreamSource<T> & WithElem<Tp, T>["nonEmpty"]'.

It builds with older typescript version.

Thanks for reporting, must be something that changed with the type inference mechanism in TS5.5.2. I'll check the changelogs and see if there is an easy fix. You are also correct about the obsolete sandbox. I was looking for a good alternative but did not find the best solution yet. Also, my time has become a bit more fragmented lately but I'll try to get it fixed.

The TS team have made Type Predicate rules a bit more strict. I think I found a way to fix it, I hope to finish and release it in the coming days.

Fix has been released, let me know if you still run into issues


zkapps grafana dashboard terraform integration

Explain your changes:

This PR integrates a new zkApps grafana dashboard into our existing terraform network deployments.
This PR makes use of the new zkapps-dashboard Helm package that was merged in https://github.com/MinaProtocol/mina/pull/12689
This code updates the kubernetes terraform package to include a new helm installation of the dashboard, alongside the other Mina nodes that are deployed. This method reuses the existing configs and workflows for testnets.
Within the Helm package, an image file has been removed. This fixes an issue with the package size exceeding the limit imposed by Terraform.
Because this is updating the existing module, it should be noted that any testnet deployments that use the existing kubernetes terraform module will be installing the zkapp dashboard (similar to how the "watchdog" is always installed).
This update only applies to the develop branch because it is specific to zkapp support.
 Specifically, the dashboard exposes a postgres port (port 5432), but has null credentials that block external access unless a credential is set at the time of deployment. There is a pending to-do to configure this with certificate-based authentication or other authentication method once support is available from Mina Foundation.
This PR also fixes a regression by returning mina_archive_schema and mina_archive_schema_aux_files variables to the testnet configurations. In the current state, testnet deploys return an error that these vars are references but not defined.
Finally, updates have been applied to the Berkeley testnet README to explain fixes for common terraform errors.

Explain how you tested your changes:

The Helm package that is being integrated has been tested in isolation as part of https://github.com/MinaProtocol/mina/pull/12689.
The integration that pulls the package into testnet deployment has been tested manually by completing isolated testnet deployments using terraform in a dedicated namespace (berk-dash-test for example).

Checklist:

[x] Modified the current draft of release notes with details on what is completed or incomplete within this project
[x] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[NA] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[NA] Serialized types are in stable-versioned modules
[x] Does this close issues? List them

Closes #12108

!ci-build-me

!ci-build-me


Drop +x bit of test file.

Hi.  Is there any reason for this?  It looks a bit weird to have a executable test file in the git repository.

Thank you!  No, it was just a warning in the Debian package, it can wait until next release, please dont't move the tag.  Btw, I've done some testing of this tag by rebuilding all reverse dependencies of it in Debian and all of them worked fine:
https://salsa.debian.org/jas/golang-github-secure-systems-lab-go-securesystemslib/-/pipelines/779095
(the podman and singularity-container fail due to other problems, not related to securesystemslib.
Thanks again for quick release and merge.


feat(linter): allow lint rules with the same name

Apologies @Boshen for the stupidly large diff.
I've done the following:

RuleEnum's members are now prefixed with the plugin name. e.g. NoDebugger has become EslintNoDebugger
updated tester.rs to accept the rule's NAME, CATEGORY to allow us to test rules with the same name (diff category)
updates declare_all_lint_rules satisfy the first above change.

#7496  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Nov 26, 11:24 PM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.

cc @Sysix this may break oxlint plugin.


Expose a "constructor" for EditableStyledDocumentImpl in its interface

Slightly related to #278, but could we add a static method to EditableStyledDocument that returns back an instance of EditableStyledDocumentImpl?
In my project, I'm creating the model first and then passing that to the view to display. My view has multiple components to it, one of which is a StyledTextArea. Since I don't have my own custom implementation of EditableStyledDocument, I currently have to create a fake StyledTextArea just to get an instance of the implementation class via StyledTextArea#getContent. Once the model has been fully constructed, I then pass it to the view which creates one or more areas that share that document.

Being able to create an EditableStyledDocument without creating a StyledTextArea sounds reasonable. Maybe I would even make the class public, but rename it to e.g. SimpleEditableStyledDocument.

Why make it public though? You seemed to be against that beforehand.

I think I was mainly against it serving as a base class for custom EditableStyledDocument implementations that users would inherit from. I still hold that position, and the class is indeed final.

Resolved by #309


Make e2e tests' docker images more stable

This PR allows running e2e tests in docker containers multiple times without having to rebuild the image.

A few E2E tests were failing due to https://github.com/iTwin/imodel-native/issues/586 - skipped until the issue is fixed on the backend.


Using the/v1/chat/completion API, the end data "data: [DONE]" was not received

method: POST
url: http://<IP_ADDRESS>:8080/v1/chat/completions
headers: [Accept: text/event-stream], [Authorization: Bearer e4nnF...XU]
body: {
"model": "gpt-3.5-turbo",
"messages": [
{
"role": "user",
"content": "who are you?"
}
],
"temperature": 0.7,
"stream": true
}

@squallliu the ending event of /v1/chat/completions doesn't return data:[DONE], but /v1/completions did.

@thxCode see https://platform.openai.com/docs/api-reference/chat/create#chat-create-stream

it is fixed in HEAD. thanks.

close as fixed


Locally accepted baselines not carried over when switching branch

From AP-4356
How is the user affected? And what is the expected behavior?
Locally accepted snapshots are supposed to be promoted to project-wide baselines when the local author pushes a commit that runs a CI build. However, when the local builds ran on a different branch, those accepted changes don't carry over and need to be reviewed again.
How many and/or what class of users does this impact?
Users that make local changes, accept VTA builds and then switch branch before committing.
Is there a workaround?
Switch branch before running any local VTA builds.
What are the steps for reproducing the issue?
On main, make some visual changes, run some builds and accept the changes locally. Create a new branch and commit your work. Push the changes to trigger a CI build. This build will resurface all changes that were previously accepted on the local build.

This is related to, but not the same as #259.


mechanical power-loops with no wind/water wheel

Please see below method for creating a mechanical power-loop that can have the power source removed and still continue providing power.

the wind mill/water wheel then can be added next to the gearbox (must be directly adjacent with no axles in-between)

Once power has fully propagated around the loop, the wind mill/water wheel can be removed with power remaining.

Syllei'Anor

Also to quickly add to this, if you use the water wheel sized one (only 1 set of axles long instead of 2) then the loop is small enough that 3/4 buckets of water can get the water wheel moving for long enough for it to power the full loop, and then not need the wheel any more


colab run

https://colab.research.google.com/drive/1LHwX6yVWc1XZaOvOB_coQjLFf77xykVX?usp=sharing <<< please see

Thanks 👍🏻🙏 Adding Colab 🚀

as Install Nerfstudio and Dependencies (~10 min) , we can move inside google drive instead then regularly installing in each in every colab session, so, if we run inside google drive then we can continue our training even we leave in the middle of the session run.


Tron skin not working

I'm trying out the plugin, but it seems like the Tron skin isn't working for me. It simply shows the 'default' look.
Is this a known issue? And anyone any idea how i could fix  this problem?

@chinookproject, @aterrien  Me too can't get it to work. Can you show us a solution of how you did that? I am using this but can't get it to work. Neither can I get the units to work.
	<script>
		$(function() {
			$('.dial').knob({
				thickness: 0.2,
				lineCap: "round",
				readOnly: true,
				fgColor: "#D07321",
				inputColor: "#3e4040"
			});
		});
	</script>


Performance improvement: Reduce time spent reading settings file, variant 2

I profiled using StyleCopTester and noticed that a lot of time was spent reading the settings file. Previously a SourceTextValueProvider was used to cache the parsed json data, but that was no longer used. Updating SettingsHelper to again use a SourceTextValueProvider improved the time needed to retrieve the diagnostics in StyleCopTester by around 15% on my machine, when running on StyleCop.Analyzers.sln
This attempt uses RegisterCompilationStart in AnalysisContext to retrieve the settings file content early in the analysis process. Moved json file specific code from SettingsHelper to SettingsJsonHelper, to try to make the code easier to understand.

Ready for review @sharwell. Let's see if this approach is better than #3519.

Closing since this is a mess and has conflicts


Add methods to erase time history for design optimization of transient physics

There are containers in the base physics class, e.g. time steps and checkpointed states, that need to be emptied in between design iterations. In the smith meeting on 12/14/23 possible solutions were discussed including adding reset methods for each individual entity that needs to be cleared, or added a "global" reset method that would return the base physics class to the "state" the module is in immediately following construction.

Closed by #1183


Mermaid is not rendering on Firefox, Brave and Vivaldi

Describe the bug
The mermaid graph is not rendering correctly on Firefox, Brave, Vivaldi.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://luiscachog.io/using-the-ansible-stat-module-on-a-loop/'
See that the page is showing 'graph TD; A(Stat over file) --> B{Does the file exists?}; B -->|Yes| C[state: file]; B -->|No| D[state: touch]; ' instead of the rendered graph.
If you visit the same URL, using Chrome or Safari it works.

Expected behavior
Render the graph correctly.
Technical details:

Academic Version: 4.8.0
Hugo Version: 0.66.0
Browser/OS: Firefox, Brave, Vivaldi

If applicable, add screenshots to help explain the issue.

Try using the shortcode diagram instead ?
{{< diagram >}}
mermaid stuff
{{< /diagram >}}

That fixed!
Thank you @Bertbk


HSDP Support

What does this PR do?
Adds HSDP. Manually tested

lgtm, but can this be tested? maybe its not possible with our current CI infra?

Manually tested! I don't think with current CI infra


Helm chart ignores ingress: true, traefik: false

Ingress annotations and routes are ignored (because the ingress is never created) if using a non-traefik ingress.
Using chart version 0.8.1

Closed, as I can't reproduce.


[Asset-Sync] Enable backups

Whether this is tag by tag, or as an entire repo.
The result of this should include

nightly/hourly automation
a restore from backup process (at the very least documented)

Closing as dup of #4298 which has more detail.


parameterize implicit acknowlegdements

see https://github.com/apache/mesos/commit/e1aeec052cf9c8cec1cf14f4c72c83e2d6b68f02

Motivation for this in this JIRA - https://issues.apache.org/jira/browse/MESOS-2347


select filters not working when the option value is 0.

when you try to filter the grid with something like this my_filter=0&my_other_filter=2
then the filters that are = 0 are not considered.
This is a bug when working with mysql boolean fields (0,1) - you can only filter for 1, not for 0

actually when passing 0 as a filter it's ignored for any type of field.

Now  issue fixed.
I use array_filter() to remove empty inputs and it remove string "0", which i didn't noticed.
Really thank you for find this.

Did you push this fix already?

Sorry, I pushed it just now.

Thanks! Suggestion of improvement
in AbstractFilter::condition() method you have to replace
    if (empty($value)) {
        return null;
    }

// because empty(0) is true
    if ( ! isset($value)) {
        return null;
    }


[Header] Header should have the same width as main container

Reproducible: always
Build found: last commit from https://github.com/ita-social-projects/GreenCityClient/tree/dev
Preconditions

Site https://zero-waste-staging.onrender.com/uk is opened.
Go to http://localhost:3000/en/calculator

Steps to reproduce

Go to http://localhost:3000/en/calculator

Actual result

Expected result
Header should have the same width as main container
Labels to be added
"Bug", Priority ("pri: "hight), Severity ("severity:"medium)

Done


Error starting tiflash on Ubuntu 22.04.2 LTS (Jammy Jellyfish) due to GLIBC version mismatch

Bug Report
I am trying to start tiflash on Ubuntu 22.04.2 LTS (Jammy Jellyfish), but I am getting the following error:
/root/.tiup/components/tiflash/v6.5.0/tiflash/tiflash: /lib/aarch64-linux-gnu/libpthread.so.0: version `GLIBC_PRIVATE' not found (required by /root/.tiup/components/tiflash/v6.5.0/tiflash/tiflash)

cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
...

1.  What did you expect to see? (Required)
I expected the tiflash-server process to start successfully.
3. What did you see instead (Required)
I encountered the following error:

/root/.tiup/components/tiflash/v6.5.0/tiflash/tiflash: /lib/aarch64-linux-gnu/libpthread.so.0: version `GLIBC_PRIVATE' not found (required by /root/.tiup/components/tiflash/v6.5.0/tiflash/tiflash)

This error is preventing me from starting tiflash, and I am not sure how to resolve it. Any help or suggestions would be greatly appreciated.
Thank you.
4. What is your TiFlash version? (Required)
v6.5.0

Have fixed by https://github.com/pingcap/tiflash/pull/6572, but not merged in release-6.5. Please use nightly instead.

openEuler 22.03 LTS SP1 also suffer from this issue. And we verified it is fixed since v6.6.0
# cat /etc/system-release
openEuler release 22.03 (LTS-SP1)

# /root/.tiup/bin/tiup tiflash:v6.5.4 version
Starting component `tiflash`: /root/.tiup/components/tiflash/v6.5.4/tiflash/tiflash version
/root/.tiup/components/tiflash/v6.5.4/tiflash/tiflash: /usr/lib64/libpthread.so.0: version `GLIBC_PRIVATE' not found (required by /root/.tiup/components/tiflash/v6.5.4/tiflash/tiflash)

# /root/.tiup/bin/tiup tiflash:v6.6.0 version
Starting component `tiflash`: /root/.tiup/components/tiflash/v6.6.0/tiflash/tiflash version
TiFlash
Release Version: v6.6.0
Edition:         Community
Git Commit Hash: 77c4d0f7ca15b6d77e0d82b9ad5cbf0d7925cc91
Git Branch:      heads/refs/tags/v6.6.0
UTC Build Time:  2023-02-09 16:32:20
Enable Features: jemalloc sm4(GmSSL) asimd unwind thinlto
Profile:         RELWITHDEBINFO

Raft Proxy
Git Commit Hash:   6444536dc45ccf50949ac47f10ced164578ddf55
Git Commit Branch: HEAD
UTC Build Time:    2023-02-09 16:38:52
Rust Version:      rustc 1.67.0-nightly (96ddd32c4 2022-11-14)
Storage Engine:    tiflash
Prometheus Prefix: tiflash_proxy_
Profile:           release


Support localization(i18n) in the App

Is your feature request related to a problem? Please describe.
Currently strings are either hard-coded in each file , which is not good for support of localization.
Describe the solution you'd like

use i18n-js & react-native-localize package in App
Follow similar project structure as in ignite-bowser boilerplate
Remove all hard coded strings
Reference all strings from i18n folder

Additional context
I have implemented it in magecart, here is the code, do you want this feature, I could work on it.

@alexakasanjeev go ahead if you want to work on it.


Consider providing instructions on how to build this project

As a developer interested in this project, I would like to have a list of requisite tools, their corresponding versions and the relevant processes (e.g., shell commands) needed to build this project so that I can get started understanding how to contribute.
I ask this because I am new to Yarn and I am unsure if I need a specific version or how to invoke Yarn to reproduce a specific version of ng-hal.

@fdutton Hi, does #44 give you enough infos?
It includes at least the basics. More details are work-in-progress and may (or may not) change. E.g., the testing strategy: the karma tests are really unit tests. i thought about integration tests also w/ jasmine/karma but it falsifies code coverage. So I will likely move integration tests to the demo app but there is still no common code pattern.

This is perfect. Thank you.


34-create-filters-storage

Closes #34

Started doing in branch with the camera, but merged later in the new branch


refactor(gc): drop umoci's gc and implement our own

With recent dist-spec changes, best if we roll our own gc.

What type of PR is this?

Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:

Automation added to e2e:

Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@peusebiu
Things to do:

Wire GC path into the changes in this PR
Wire S3 into this PR
Drop umoci from go.mod
regclient CI should work
Conformance should work with GC

Superseded by https://github.com/project-zot/zot/pull/1656


Teamlist Tuple

I could make my team lists into a Tuple bec it should be unchangeable

https://github.com/DarthMaxwell/F1Fantasy2022/compare/b21118cb0585...0a60498606f4


Clarify docs relating to the use of wildcard certs

Clarify use of wildcard in Subject property
Add info regarding use of multiple domain names

Learn Build status updates of commit a4e0714:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/database-engine/configure-windows/enable-encrypted-connections-to-the-database-engine.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@vanmsft
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Learn Build status updates of commit 52e0543:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/database-engine/configure-windows/enable-encrypted-connections-to-the-database-engine.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit ccf525f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/database-engine/configure-windows/enable-encrypted-connections-to-the-database-engine.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Thanks, @premradhakrishnan - Approving this after making small changes.
#sign-off

Learn Build status updates of commit 50d341d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/database-engine/configure-windows/enable-encrypted-connections-to-the-database-engine.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 20d5c5b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/database-engine/configure-windows/enable-encrypted-connections-to-the-database-engine.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Hi @VanMSFT - Thank you for approving the changes.
Hi @Court72 - VanMSFT has approved and added #signoff in the comment. Is there anything else to be done before the merge?
Thanks


Refs #24833 - Renamed vars in solve_lookup_type to be more consistent

LGTM.

Does it make sense to also add the test from https://github.com/django/django/pull/4794 in this commit?

Also forwardported test & release note. Merged in 286d0e6ab1e54906007fda86b6cb6deb26c6deb2, thanks!


LIHEDP Notebooks

Jupyter Notebooks from a course on Laser Plasma Interaction and High Energy Density Plasma

Note:
I am interested in pushing some of the content of these notebooks on PlasmaPy.
I believe the core functions would need to be extracted and implemented in separate .py files.
Hopefully, some of this is of interest to you:

For example, the notebook "critical_density.ipynb" aims to implement issue #26.
The "assignment_answers.ipynb" notebook uses a recent Inertial Confinement Fusion experiment at NIF,(https://doi.org/10.1038/s41566-021-00890-z) which made a lot of noise in the Fusion community, to illustrate several of the functions implemented in the other files. This may be a good example for issue #61.

I have a question about the difference between Pull Request and Drafts:
Can you see Drafts and comment on them?
Is it annoying for you if the Pull Request contains code that is quite rough?

@cmoissar drafts just have a note so we know they aren't ready to review. Absolutely no problem opening a PR even when rough - it allows us to easily see what you're working on and give suggestions.
I think adding some functions for LP HEDP and an example notebook that features them would be great! I would do at as 1 PR per function and then 1 PR for the notebook. If you're still interested, you should open those PRs on the main PlasmaPy package.

Hey @cmoissar, do you mind if I take a stab at implementing the plasma critical density formulary as my first commit?

Hey @cmoissar, do you mind if I take a stab at implementing the plasma critical density formulary as my first commit?

Of course not, have at it!

@cmoissar drafts just have a note so we know they aren't ready to review. Absolutely no problem opening a PR even when rough - it allows us to easily see what you're working on and give suggestions.
I think adding some functions for LP HEDP and an example notebook that features them would be great! I would do at as 1 PR per function and then 1 PR for the notebook. If you're still interested, you should open those PRs on the main PlasmaPy package.

Thanks for your reply.
I'll (slowly) work on that after my summer break!


add leap.nvim

I appreciate the PR, however I would like to not include leap.nvim into Neve. I've tried it before but eventually removed it as I don't want to replace neovim's default s and S mappings.

Maybe override something like CTRL + s?

Maybe override something like CTRL + s?

I'm using CTRL + s to save the file already :cry:


Doesn't appear to be a way to enable tracing with the pomerium-ingress manifest install

What happened?
The pomerium crd doesn't provide any config options for tracing, which is enabled in both the regular configs and the deprecated helm charts.

we will likely add it as runtime options in one of the upcoming releases together with updating docs.
is there a performance issue you're experiencing and trying to debug right now?

No performance issues, I would just like the ingress to generate trace tagging for my upstream services.


Improve documentation

Summary of Changes

Update documentation
Update examples

Motivation
Improving documentation is a continuous process.
Implementation
The quickstarts are the primary focus of these edits:

inference: this is focused on a user who is just making inferences. It doesn't cover anything about starting the server. For now, since the Python library is not publicly distributed, it relies on using the development container for making inferences.
deployment: this now shows a model repository deployment approach which omits the need to explicitly load models and also makes a migration to KServe simpler. There are concrete examples for setting up ResNet50.
development: more platform-specific code snippets are added

To enable users to run examples without also loading the server, I added a new --endpoint flag which doesn't attempt to load a new worker.
Notes
The inference quickstart should be simplified once the Python library is public so it doesn't rely on the development container.

Build successful!


Error from mypy when using converters in a list

When I use multiple callables with the converter argument in field, I get an error from mypy.
Here is a simple example of what I'm trying to do.
# main.py
import numpy as np
import numpy.typing as npt
from attrs import field, define

@define
class Foo:
    x: npt.NDArray[np.float64] = field(converter=[np.array, np.float64])

foo = Foo(x=[1,2,3])

print(type(foo.x), foo.x.dtype)

$ python main.py
<class 'numpy.ndarray'> float64

But mypy (version 1.9.0) gives me an error:
$ mypy main.py
main.py:8: error: No overload variant of "field" matches argument type "list[object]"  [call-overload]
main.py:8: note: Possible overload variants:
main.py:8: note:     def field(*, default: None = ..., validator: None = ..., repr: bool | Callable[[Any], str] = ..., hash: bool | None = ..., init: bool = ..., metadata: Mapping[Any, Any] | None = ..., converter: None = ..., factory: None = ..., kw_only: bool = ..., eq: bool | None = ..., order: bool | None = ..., on_setattr: Callable[[Any, Attribute[Any], Any], Any] | list[Callable[[Any, Attribute[Any], Any], Any]] | _NoOpType | None = ...,
alias: str | None = ..., type: type | None = ...) -> Any
main.py:8: note:     def [_T] field(*, default: None = ..., validator: Callable[[Any, Attribute[_T], _T], Any] | Sequence[Callable[[Any, Attribute[_T], _T], Any]] | None = ..., repr: bool | Callable[[Any], str] = ..., hash:
bool | None = ..., init: bool = ..., metadata: Mapping[Any, Any] | None = ..., converter: Callable[[Any], Any] | None = ..., factory: Callable[[], _T] | None = ..., kw_only: bool = ..., eq: bool | Callable[[Any], Any] | None = ..., order: bool | Callable[[Any], Any] | None = ..., on_setattr: Callable[[Any, Attribute[Any], Any], Any] | list[Callable[[Any, Attribute[Any], Any], Any]] | _NoOpType | None = ..., alias: str | None = ..., type: type | None = ...) -> _T
main.py:8: note:     def [_T] field(*, default: _T, validator: Callable[[Any, Attribute[_T], _T], Any] | Sequence[Callable[[Any, Attribute[_T], _T], Any]] | None = ..., repr: bool | Callable[[Any], str] = ..., hash: bool | None = ..., init: bool = ..., metadata: Mapping[Any, Any] | None = ..., converter: Callable[[Any], Any] | None = ..., factory: Callable[[], _T] | None = ..., kw_only: bool = ..., eq: bool | Callable[[Any], Any] | None = ...,
order: bool | Callable[[Any], Any] | None = ..., on_setattr: Callable[[Any, Attribute[Any], Any], Any] | list[Callable[[Any, Attribute[Any], Any], Any]] | _NoOpType | None = ..., alias: str | None = ..., type: type | None =
...) -> _T
main.py:8: note:     def [_T] field(*, default: _T | None = ..., validator: Callable[[Any, Attribute[_T], _T], Any] | Sequence[Callable[[Any, Attribute[_T], _T], Any]] | None = ..., repr: bool | Callable[[Any], str] = ..., hash: bool | None = ..., init: bool = ..., metadata: Mapping[Any, Any] | None = ..., converter: Callable[[Any], Any] | None = ..., factory: Callable[[], _T] | None = ..., kw_only: bool = ..., eq: bool | Callable[[Any], Any] | None = ..., order: bool | Callable[[Any], Any] | None = ..., on_setattr: Callable[[Any, Attribute[Any], Any], Any] | list[Callable[[Any, Attribute[Any], Any], Any]] | _NoOpType | None = ..., alias: str | None = ..., type: type | None = ...) -> Any
main.py:8: error: Unsupported converter, only named functions, types and lambdas are currently supported  [misc]
Found 2 errors in 1 file (checked 1 source file)

Not sure why or if this is fixable.

I will look into it and try my best to troubleshoot and debug this code :)

The [misc] error may be related to this discussion - https://github.com/python/mypy/issues/6172

Yes this is most likely due to Mypy‘s limitations unfortunately.

Should I report the bug on Mypy's github?

I’m pretty sure there’s a ticket there and/or here but I’m too swamped rn to do the research. Unfortunately, it’s a rather recurring topic.

Closing it now; if it turns out to be a new problem, feel free to re-open with a rationale.


Support for json messages in mqtt switches and sensors

I am currently working on connecting a Homematic CCU2 to Home Assistant via MQTT. I am using hm2mqtt (https://github.com/owagner/hm2mqtt/) for this on the CCU2 side.
However, the way that is implemented, it sends a json string in the state topic (e.g. hm/status/mydevice/STATE) that looks like the following

{"val":0,"ts":"1448049600608","lc":"1448049600608","hm_addr":"LEQXXXXXXX:1"}

What I needed for HA was only the val, so I implemented a generic mechanism to access parts of a json message in a message by adding a new key "state_format" to the config where you can specify the type of message (json:) followed by a parsing rule (jsonpath in the json case, based on jsonpath_rw).

Any hints why coveralls says coverage dropped? I thought it was because of the extra line break I had introduced previously, but that seems not to be the case.

Coveralls can be confusing. It is lower because the dev branch currently dropped because of the new lock component that still needs testing. Don't worry about it :+1:


CI: remove xvfb-run from linux headless E2E tests

Only headful needs it.
This is to try to fix recent observed flakiness in the CI, which happens only for this action. A typical failure looks like the following:
tests/test_log_events.py ....node:internal/errors:705
  const ex = new Error(msg);
	     ^

Error: socket hang up
    at connResetException (node:internal/errors:705:14)
    at Socket.socketOnEnd (node:_http_client:518:23)
    at Socket.emit (node:events:525:35)
    at endReadableNT (node:internal/streams/readable:1358:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  code: 'ECONNRESET'
}
❌ [server-headless] Service exited unexpectedly

E.g. failure: https://github.com/GoogleChromeLabs/chromium-bidi/actions/runs/4790216621/jobs/8519039667?pr=638
I am hoping this won't be reproduced with this change, let's see.


Force LF line endings for .ql, .qll, .qlref, and .dbscheme

Added a .gitattributes file to specify that *.ql, *.qll, *.qlref, and *.dbscheme files should have their line endings normalized to LF in the database, and to keep the LF line endings in the working tree even on Windows. Instructions for how to renormalize files after future changes are in a comment .gitattributes.
Renormalized the existing such files in the repo. This consisted of a few .qlref files in C#, three test .ql files that @rdmarsh2 recently modified in JavaScript, and essentially every file that @dave-bartolomeo has ever edited:) I don't expect any of these files to cause merge conflicts with anything currently in flight.
I didn't know which other file extensions we want to force this for. I'm fine with forcing it for all text files, assuming that doesn't break anything.

Added WIP to prevent merge until all three languages sign off.

I don't think you want to do this to the *.dbscheme files -- you'd trigger the need for upgrade scripts, as their content hash matters.

I don't think you want to do this to the *.dbscheme files -- you'd trigger the need for upgrade scripts, as their content hash matters.

@pavgust All of the dbscheme files are already LF in the database. I've always had to be careful when I made dbscheme changes to avoid introducing rogue CRLFs. With this change, they'll remain LF in the database and in the working tree. Also, I just added a .editorconfig file to this PR, so that anyone using a supported editor will be much less likely to introduce a CRLF. Finally, we hash the dbscheme with git hash-object, which takes .gitattributes into account even for files not yet committed, so even if someone does add a CRLF to a dbscheme file, the computed hash will be the same as if it were normalized to LF.

Ah, good -- apologies, I should have checked whether any dbscheme files actually changed. If not, then forcing their line endings to LF is indeed the right thing to do.

Finally, we hash the dbscheme with git hash-object, which takes .gitattributes into account even for files not yet committed, so even if someone does add a CRLF to a dbscheme file, the computed hash will be the same as if it were normalized to LF.

There are at least some code paths that has the dbscheme in an equivalent way, but without access to the repo (and hence without reference to .gitattributes). Still, +1 on this PR.

I've added .qhelp files to the LF-only list. There were only two that had CRLFs.
I don't think we should do this for .expected files. We compare these using binary comparison. If someone adds CRLFs in their working tree, and the binary comparison succeeds, then the comparison would fail for everyone else. I'd rather the failure happen on the machine where the CRLF was introduced.
For other source file extensions, I'd like to hold off until we can discuss further. I'd be fine with LF for all the .js/.cs/.cpp/.html files, but I don't know if there are any of them that chose their current line endings for specific testing purposes. Also, most of these files aren't part of the distribution that end customers see, so it's less important (although still good) to have consistent line endings.

I'd be fine with LF for all the .js/.cs/.cpp/.html files, but I don't know if there are any of them that chose their current line endings for specific testing purposes.

Some of the alert suppression tests have CRLF line endings to test that suppression works on Windows, so indeed we'd have to be careful about enforcing LF line endings for tests.
Apparently the plugin.xml files also have CRLF line endings, but we can fix those up later if desired.