SyntaxWarning indicating an invalid escape sequence in a regular expression

Issue Description:
The Python interpreter emits a SyntaxWarning indicating an invalid escape sequence in a regular expression. This warning arises because the backslash ('\') in the regular expression pattern is not properly escaped. Specifically, the pattern attempts to match a pipe character ('|') in a context where it should be escaped to ensure correct regex parsing and execution.
File Affected:
c:\Users\**\AppData\Roaming\Python\Python311\site-packages\chocolatey\_chocolatey.py:600
Warning Message:
SyntaxWarning: invalid escape sequence '\|'
Proposed Solution:
To resolve this warning, the backslash character within the regular expression should be escaped properly. This can be achieved by either doubling the backslash ('\\') or by using a raw string (prefixing the string with 'r'). The corrected line of code should either look like this:
out = re.sub("[\\t ]*\\|", "\n", out)

or like this using a raw string:
out = re.sub(r"[\t ]*\|", "\n", out)

Applying this change eliminates the SyntaxWarning and ensures that the regular expression is processed correctly by the Python interpreter.
end fix is:
# pre-parse
out = re.sub(r"[\t ]*\|", "\n", out)
out = re.sub(r"\n[\t ]*Package url[\t ]*\n", "\n Package url: n/a\n", out)

Sorry, but in the current branch (main) the current code looks exctly as you suggest.
Could you please check it?
PS: sorry for the delay (due to my health problems)

Sorry, but in the current branch (main) the current code looks exactly as you suggest.
Could you please check it?
If the error persists, I will reopen this issue.

Sorry, but in the current branch (main) the current code looks exactly as you suggest.
Could you please check it?
If the error persists, I will reopen this issue.


Change the if/else for regex,prefix,postfix to an if statement

Change the if/else for regex,prefix,postfix to an if statement so they may all be used.
I am pulling down the list of new blu-ray releases from
https://www.blu-ray.com/rss/newreleasesfeed.xml
which does not include an image url, so I needed to isolate the movie ID, then do a prefix and postfix to build an img tag to have it shown:

Blue Ray Movie Releases
  - type: custom:list-card
    entity: sensor.blu_ray_releases
    title: Blu-Ray Releases
    columns:
      - title: ''
        field: link
        regex: \d+(?=\/)
        prefix: '<img src="https://images3.static-bluray.com/movies/covers/'
        postfix: '_small.jpg" />'
      - title: Title
        field: title
        add_link: link
        style:
          - white-space: nowrap

Thanks


Zoom factor sweep

Checklist

[x] I've given this PR a concise, self-descriptive, and meaningful title
[x] I've linked relevant issues in the PR body
[x] I've applied the relevant labels to this PR
[x] I've added relevant tests for my contribution
[x] I've updated the documentation and/or added correct docstrings
[x] I've assigned a reviewer
[x] I've consulted ADS's internal developer documentation to ensure my contribution is in line with any relevant design decisions

Description

The goal of this PR is to add a feature to repeatedly segment the same image using different zoom factors within a given range, as discussed in #610. This tool will be useful to evaluate an appropriate zoom factor for optimal segmentation visual aspect.
I added the feature in a new file but the sweep function will be called from the main segment.py CLI. For now, having this feature in a separate file does not make much sense because the code is pretty short but, eventually, when we add a metric to evaluate the masks produced, it will be helpful.
Current parameters:

sweep_range (e.g. [3, 5] for zoom factors between 3 and 5)
sweep_length: number of equidistant zoom factors to sample in sweep_range

Linked issues

#610

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

AxonDeepSeg/zoom_factor_sweep.py
0
15
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-1.2%

Covered Lines:
961

Relevant Lines:
1098

💛  - Coveralls

(Just want to point out that I changed the look of the main segmentation CLI's add_argument() expressions to be a bit more pep8 compliant. Tell me which version you think is better. Personnally, the way it was layed out before hurt my eyes)

Ok this feature now works in the CLI. Before updating the doc and adding tests, I would like some feedback.
The way it works is you specify zoom factor lower/upper bounds with the -r option and the number of points to sample with the -l option. For example, the following:
axondeepseg -t SEM -i image.png -s 0.37 -r 1 2 -l 5

will create a new folder called image_sweep and compute segmentations for 5 equidistant zoom factor values in the range [ 1, 2 [ (i.e. 1.0-1.2-1.4-1.6-1.8).

Wow, excited to see this issue get completed while I was away for ISMRM! Thanks a lot @hermancollin  and @mariehbourget !
Looking at this quickly, the only suggestion I'd have is to write in a check to ensure that the [min, max] zoom range does not exceed the limit set by the patch size (so maybe if we zoom in too much, reset the minimum to that limit. I calculate it elsewhere in the code already, here: https://github.com/axondeepseg/axondeepseg/blob/e7a9373836efa6afedf9393de8fc2109737fcfaa/AxonDeepSeg/segment.py#L269-L291)

Thank you both @mariehbourget @mathieuboudreau for these comments.

Looking at this quickly, the only suggestion I'd have is to write in a check to ensure that the [min, max] zoom range does not exceed the limit set by the patch size (so maybe if we zoom in too much, reset the minimum to that limit.

So IIUC we would check the minimum zoom factor for the given image before starting the zoom sweep processing, and then tell the user if one of the bounds is invalid? This sounds like a good idea.
For the record, if we try to segment with an invalid zoom factor during the sweep, the segment_image function will do the check anyway so there would be some redundance.

So IIUC we would check the minimum zoom factor for the given image before starting the zoom sweep processing, and then tell the user if one of the bounds is invalid? This sounds like a good idea.

Yeah kinda. I would just inform the user and tell them that we internally reset the range so it doesn't go beyond it. Otherwise, there's a risk (unsure if it would happen) that the "optimal zoom value" falls beyond the valid range, and that would be a headache to explain.

For the record, if we try to segment with an invalid zoom factor during the sweep, the segment_image function will do the check you wrote anyway so there would be some redundance, albeit not much resource consumption.

Ah gotcha. It's still better to automatically change the range so that it only contains valid zoom values though I think!


Set up DRAT to weekly scan the ASF full Github

Scan all ASF projects on Github using DRAT stats, and then publish a D3 DRAT viz page with latest scan

Do we have, or can we get an ASF VM for this?

yep we have one, drat.apache.org.
Current projects running there:
http://drat.apache.org/demo/ - Proteus live scan, pre-release 1.0
http://drat.apache.org/asfgit/ - Proteus D3 viz, pre-release 1.0


vRY acronym

The standard acronym for VALORANT rank yoinker is vRY, not Vry.

Fixed .. feel free to close :)


fix(data): Some feilds where not present preventing parsing

Signed-off-by: dark0dave<EMAIL_ADDRESS>

[2022-12-22T00:24:23Z WARN  roux_stream] Error while fetching the latest submissions from r/Augu: error decoding response body: missing field `kind` at line 1 column 58
[2022-12-22T00:24:25Z WARN  roux_stream] Error while fetching the latest comments from r/Augu: error decoding response body: missing field `kind` at line 1 column 58
[2022-12-22T00:24:25Z WARN  roux_stream] Error while fetching the latest comments from r/FunfairTech: error decoding response body: missing field `kind` at line 1 column 59
[2022-12-22T00:24:25Z WARN  roux_stream] Error while fetching the latest submissions from r/RichTogethe: error decoding response body: missing field `domain` at line 1 column 4149
[2022-12-22T00:24:28Z WARN  roux_stream] Error while fetching the latest submissions from r/FunfairTech: error decoding response body: missing field `kind` at line 1 column 59
[2022-12-22T00:24:28Z WARN  roux_stream] Error while fetching the latest submissions from r/Populousplatform: error decoding response body: missing field `kind` at line 1 column 58
[2022-12-22T00:24:28Z WARN  roux_stream] Error while fetching the latest comments from r/Populousplatform: error decoding response body: missing field `kind` at line 1 column 58
[2022-12-22T00:24:29Z WARN  roux_stream] Error while fetching the latest submissions from r/Ardo: error decoding response body: missing field `kind` at line 1 column 58
[2022-12-22T00:24:29Z WARN  roux_stream] Error while fetching the latest submissions from r/Tethe: error decoding response body: missing field `domain` at line 1 column 14798
[2022-12-22T00:24:29Z WARN  roux_stream] Error while fetching the latest comments from r/Ardo: error decoding response body: missing field `kind` at line 1 column 58
[2022-12-22T00:24:31Z WARN  roux_stream] Error while fetching the latest submissions from r/greeninvesto: error decoding response body: missing field `domain` at line 1 column 10084
[2022-12-22T00:24:34Z WARN  roux_stream] Error while fetching the latest submissions from r/CanadianInvesto: error decoding response body: missing field `domain` at line 1 column 4192
[2022-12-22T00:24:39Z WARN  roux_stream] Error while fetching the latest comments from r/Augu: error decoding response body: missing field `kind` at line 1 column 58
[2022-12-22T00:24:41Z WARN  roux_stream] Error while fetching the latest submissions from r/FunfairTech: error decoding response body: missing field `kind` at line 1 column 59
[2022-12-22T00:24:43Z WARN  roux_stream] Error while fetching the latest submissions from r/Augu: error decoding response body: missing field `kind` at line 1 column 58
[2022-12-22T00:24:46Z WARN  roux_stream] Error while fetching the latest comments from r/FunfairTech: error decoding response body: missing field `kind` at line 1 column 59
[2022-12-22T00:24:48Z WARN  roux_stream] Error while fetching the latest comments from r/Ardo: error decoding response body: missing field `kind` at line 1 column 58
[2022-12-22T00:24:49Z WARN  roux_stream] Error while fetching the latest submissions from r/Populousplatform: error decoding response body: missing field `kind` at line 1 column 58
[2022-12-22T00:24:49Z WARN  roux_stream] Error while fetching the latest submissions from r/greeninvesto: error decoding response body: missing field `domain` at line 1 column 10084
[2022-12-22T00:24:51Z WARN  roux_stream] Error while fetching the latest submissions from r/RichTogethe: error decoding response body: missing field `domain` at line 1 column 4149
[2022-12-22T00:24:51Z WARN  roux_stream] Error while fetching the latest submissions from r/Ardo: error decoding response body: missing field `kind` at line 1 column 58
[2022-12-22T00:24:52Z WARN  roux_stream] Error while fetching the latest submissions from r/CanadianInvesto: error decoding response body: missing field `domain` at line 1 column 4192
[2022-12-22T00:24:53Z WARN  roux_stream] Error while fetching the latest comments from r/Populousplatform: error decoding response body: missing field `kind` at line 1 column 58
[2022-12-22T00:24:53Z WARN  roux_stream] Error while fetching the latest submissions from r/Tethe: error decoding response body: missing field `domain` at line 1 column 14798


Cannot refresh save files since getting standard of heroes

I would like to try to tackle this as my first issue if no one else is working on this yet.

This also hit me after doing my first ubers.


Make onPaste also support text of type text/plain

Added support for text/plain when pasting text (from for example notepad++)

ha, interesting one!
thx @maartentenham !

thx @maartentenham , published new version


Removed Sequel Pro (not maintained any more https://github.com/sequel…

Removed Sequel Pro (not maintained any more https://github.com/sequelpro/sequelpro/issues/3705).
Added Sequel Ace

Thank you for helping keep this list updated!


⚠ Spryr has degraded performance

In 5eedd4d, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3038 ms

Resolved: Spryr performance has improved in b48ba29 after 11 minutes.


Missing 'development' Task

[09:18:19] Using gulpfile ~/Desenvolvimento/Github/material/gulpfile.js
[09:18:19] Task 'development' is not in your gulpfile
[09:18:19] Please check the documentation for proper gulpfile formatting

Thank you @gpedro, gulp tasks are still a mess.


Separation of concerns

Hey @homakov,

We talked a bit through twitter yesterday and thought I might as well elaborate a bit more on some of my issues with the project. I'll post each of them separately so they can be fixed and tracked.

Separation of Concerns
Spec and Implementation
My most pressing point is the confusion between specification and implementation. You wrote a medium post about a protocol; but delivered a repo with an implementation. Adding to that confusion is the complete lack of structure within the example implementation.
If SecureLogin is a protocol; I would advice treating it as such and create a clear separation between specification and implementation. Spec should get a repo, and each implementation should get a repo. Changes and discussions to the protocol are relevant for everyone. But someone figuring out why Cordova 6.4 didn't compile doesn't interest someone who runs everything in GO.
Repo and Code
This brings me to my second point; presentation of implementation. In general it benefits everyone if code is consistently structured and follows common programming patterns. In case of a public repo it gets even more important to follow a consistent format.
First, please read up on the best practices for Cordova and Electron. How do you structure the base of your project? What are the distribution channels and how to correctly track dependencies? After that I'd suggest implementing something like Angular, React, Ember or Vue.js for your Cordova app. When you pick a framework, make sure you either follow best practices or document your own practices. This way people can navigate through your project without being familiar with it.
Put SL into modules
Like I said in spec; implementation must be strict but is irrelevant. It follows the same logic no matter what language you use. Because of this I would advice providing modules for popular languages which expose the SL api in the language of choice. If you maintain these modules you limit the effort required for implementing SL and also keep some control over the rollout of feature changes / bug fixes.
Of course each module should get its own repo with bug tracking, documentation and examples
Testing
Please write tests.. You're working on a serious project that requires 100% stability before anything is pushed to master. Imagine users losing the ability to login into existing websites, and at the same time registering new profiles with a wrongly determined password. You'll end up with a scenario where you can't roll back.

Have a nice day

Spec and Implementation

Spec is coming, we finally figured out possible implementation issues and after that ready to finalize it.

First, please read up on the best practices for Cordova and Electron.

Are there any? I thought their job is to work on existing HTML, not enforce their conventions.

How do you structure the base of your project? What are the distribution channels and how to correctly track dependencies?

Will work on it.

After that I'd suggest implementing something like Angular, React, Ember or Vue.js for your Cordova app. When you pick a framework, make sure you either follow best practices or document your own practices. This way people can navigate through your project without being familiar with it.

We don't use framework on purpose:

the app is small and doesn't intend to do anything beyond authentication. So benefits of full blown framework over some DOM manipulations are low

It's easier to audit for anyone not just for a programmer in respective React / Angular etc framework.

We also will refactor code and follow standardjs in near future.

Put SL into modules

Leftpad problem is bothering me, and the fact that we can push code to many apps just modifying a gem is scary. Once protocol is finalized, it's safe to copy-paste the library to your app, instead of adding another dependency. I think anything < 100 LOC and static doesn't deserve it's own package.
One argument for packaging though is https://nacl.cr.yp.to/box.html - we can fork existing implementations of sig verification, slim them down to just verify method and include as part of the package (vs how RbNaCl is a requirement now)

Imagine users losing the ability to login into existing websites, and at the same time registering new profiles with a wrongly determined password

Can you explain how this can be solved by tests? Users type wrong password?
Testing is spot on. We need to add high level tests https://en.wikipedia.org/wiki/System_testing - any recommendations?
And a unit test for scrypt derivation.

I think anything < 100 LOC and static doesn't deserve it's own package.

There are a couple problems with this. One is just simplicity. Being able to just npm install or bower install a package is way easier than going to GitHub and copy-and-pasting a file, especially as SecureLogin grows. In addition, not publishing it to package managers opens up the possibility of someone else publishing code under SecureLogin's name. If you don't publish it to a package manager, someone else will, and there's no guarantee for that code to be safe.

Actually offering both is better. Will try now. Sensitive apps should vendor their dependencies. Others are fine with trysting rubygems or whatever middleman is used.

Started from this https://rubygems.org/gems/securelogin

Are there any? I thought their job is to work on existing HTML, not enforce their conventions.

For both there's documentation and opinion pieces available that describe practices to follow. Of course it isn't enforced on anyone and you're free to develop in a structure that's best suited to your project and needs. What is important is to document your reasoning behind the structure. This helps guiding consistency throughout the project and helps new contributors find code / add new code.

We don't use framework on purpose:
the app is small and doesn't intend to do anything beyond authentication. So benefits of full blown framework over some DOM manipulations are low
It's easier to audit for anyone not just for a programmer in respective React / Angular etc framework.
We also will refactor code and follow standardjs in near future.

I can only agree with and fully support this decision. This does make consistency through formatting and structure so much more important. The efforts from @andrewda in https://github.com/sakurity/securelogin/issues/29 is a great step in the right direction!
I'd also splitting code into modules and templates. Checkout the LIFT principle for that.

Leftpad problem is bothering me, and the fact that we can push code to many apps just modifying a gem is scary. Once protocol is finalized, it's safe to copy-paste the library to your app, instead of adding another dependency. I think anything < 100 LOC and static doesn't deserve it's own package.

I can understand your reasoning on this issue. And your concerns are valid. The angle I'm coming from is sustaining healthy implementation strategy. Critical issues can't be fixed without breaking a majority of the websites / apps. Due to dependency management, hijacks can occur on many levels of the stack. Right now you depend on multiple cordova plugins which could be hijacked or break builds.
I think both concerns are valid. What ever decision is made in this case must be consistent.

Can you explain how this can be solved by tests? Users type wrong password?
Testing is spot on. We need to add high level tests https://en.wikipedia.org/wiki/System_testing - any recommendations?
And a unit test for scrypt derivation.

What you can solve by tests is ensuring that the deterministic scheme will successfully create a profile. From this profile you should test if password generation is working for both valid and invalid passwords. This would become easier if there's a single module used for the SL protocol and all public apis exposed from that module are tested.

What you can solve by tests is ensuring that the deterministic scheme will successfully create a profile.

It's a real problem. In the beginning cordova module gave totally different hash on Samsung phones (now fixed thanks to them). Smoke tests will be added because who knows what cheap android phones do to plugins.

Hey @homakov,
That is because right know you depend on the javascript and webview implementation of those devices.There's a few ways you can fix this:

Embed a fixed WebView component (this drastically app size, decreases portability and doesn't 100% ensure solving the problem.)
Use cordova module that exposes native hashing API's to JS. Not sure if there's a solution for this that supports your case.
Write native SL modules in Swift (IOS) and Java (Android), and hook those into a Cordova module.  (I would suggest this)

That's exactly what 'cordova-plugin-scrypt' does. it just some internal bug that Samsung failed: https://github.com/Crypho/cordova-plugin-scrypt/issues/6
It's quite fast.

Just wanted to edit my comment. Forgot you're already using scrypt natively 👍


Debug mode menu step 1

Issue
https://github.com/gravitee-io/issues/issues/6893
Description
Prepare for next PR to add menu for PS

remove unused PS wrapper in angularjs
change target to es6===es2015

Additional context

🚀 CI was able to deploy the build of this PR, so you can now try it directly here
Notes: The deployed app is linked to the management API of APIM master. (Same login and password as APIM master)

📚  View the storybook of this branch here

There is a weird thing. It works locally but it doesn't seem to work on the :

CI was able to deploy the build of this PR, so you can now try it directly
But I don't know yet if it comes from this PR

:aa: It looks like the snackBar isn't super happy

i've add two new commit to fix your message it's easy so i add it in this PR ;)


HIVE-23894: SubmitDag should not be retried incase of query cancel

Thanks for the review @pgaref
I am afraid we may not be able to simulate the kill query scenario at the specific place using UT. Please let me know ur thought.

Thanks for the review @pgaref
I am afraid we may not be able to simulate the kill query scenario at the specific place using UT. Please let me know ur thought.

Hey @nareshpr  -- np, changes are pretty straightforward so I believe we should push :)


No nfs-utils for creating NFS mounts

If an installation wants to use the Bastion as an NFS server, say to create persistent storage for the cluster, the NFS code needs to be present.  Let's make sure the code is there.

Added the install of nfs-utils to the build process (b5a3a83, in setup-ocp-deployer).


Metadata added to session start, it was removed and broke many applications.

Proposed changes:

...

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

 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.Naresh Dhiman seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for submitting a pull request 🚀 @kalkbrennerei will take a look at it as soon as possible ✨

closing in favor of https://github.com/RasaHQ/rasa/pull/7922 . Thanks for bringing this up and helping us @NareshDen ! 🎉


update on freecodecamp

I added few text to line 23 so newbie can get a feel about freecodecamp

@Sylvester-ABC pls do follow me and star this repo it will be merged

not appropriate conflicts are there


Tabs are added to raw strings

Hi Jan!
Looks like your are using some code beautifier behind the scenes? This has some unwanted aspects on raw strings. Here's an example:
result :=
`This is some text!
It is stored in a file!
Every file needs to have an end.
`
fmt.Println(result)

This produces:
This is some text!
	It is stored in a file!
	Every file needs to have an end.

Any idea how to fix this?

 Everything after %% is moved inside a func main() { ... } with each line indented ...
So short-term solutions:

Remove the %% and create your own func main() {...} for your particular cell. Or move
Or move the statement result := ... to a global variable, if you don't mind it being around for the other cells.

Longer-term solution:

Should we remove the indenting when converting stuff after %%  ? It should be simple enough ... but I wonder ...
Actually parsing and understanding the Go code, and when the line is inside a string, not indenting it: this would be the
optimal solution, but it's complicated, since we would have to actually parse the code ourselves and understand much more about it, which I wanted to avoid, to keep it simple.

Any thoughts ?

Hi Jan!
Since the solution is just about using func main() explicitly that's absolutely fine with me.

I'll leave it as is for now then.


xds failover locality handling

This change is

I need to add more tests, clean the added tests, and clean the code more. But overall this is ready for review. Thanks!

src/core/ext/filters/client_channel/lb_policy/xds/xds.cc, line 2549 at r10 (raw file):
Previously, markdroth (Mark D. Roth) wrote…
@guantaol, if we have a single thread set two timers for exact same time, do we have a guarantee that the callbacks for those timers will run in the order in which the timers were scheduled?  Note that I am asking about what guarantee the C-core timer API provides, regardless of the underlying platform or implementation.

Juanli is the owner of C-core timers, so she may be more authoritative to confirm this.
In my check, we have no such guarantee on the execution order in the timer API.

The reason "Bazel RBE UBSAN C/C++" fails is related with this bug and because this is a bug of libstdc++, solution might be either i) upgrading version of gcc for this to 5.2 or later with the fix or ii) disabling ubsan test on this.

@veblush Thanks! I disabled UBSAN on this test as a workaround.

Interop ALTS Tests (internal CI): https://github.com/grpc/grpc/issues/20384
Interop Cloud-to-Prod Tests (internal CI): https://github.com/grpc/grpc/issues/20395


Create Accordion component

@thomasdigby Should we reinvestigate the need for flexbox to centre these component previews? It wreaks havoc on the accordion.

Yeahhhh kill it. What are you thinking instead?

Updated with a25f0a5 - now extends .wrapper. Yesh?


[DISCUSSION] Update OSB Release Cadence and Method

Is your feature request related to a problem? Please describe
Right now, OSB has been releasing on a monthly cadence. This has been useful for the community as it makes OSB releases predictable and users can plan around OSB's release schedule when contributing changes.
However, the monthly release cadence only gives users a 3 week window (considering how a few days are dedicated to freeze). This is not enough time for users who are working on larger and more impactful changes in OSB.
Describe the solution you'd like
OSB maintainers would like to change two characteristics of the OSB release.
1. Release OSB every 6 weeks instead of on a monthly basis. This would align us with the OpenSearch release cadence and also allow users to have ample time to add changes in before each release.
2. Release from major / minor branches instead of from mainline. Right now, OSB release process starts once a tag is pushed up to mainline and after the release has been completed, maintainers create a major / feature branch and backport new commits when necessary. After our experience with a couple patches in 1.7.0 and 1.3.0, it would be much easier to push tags and release from major / minor branches. This would also remove the need for any freezes and would give users more time to contribute changes up until the release date.
We would like to invite the community's opinion on this matter. Feel free to comment below!

Thanks @IanHoang. As an outcome of this discussion, let's publish a release calendar for OSB. This will provide better visibility for component contributors, aiding them in planning their benchmarking strategy effectively.

Added a forum post for visibility: https://forum.opensearch.org/t/update-opensearch-benchmark-osb-release-cadence/20126

Both suggestions are good ones.  The original reason for the monthly cadence is the spurt of incoming changes the project needed to deal with a few months ago and the need for a quick turnaround that several users wanted at the time.  The rate of updates is now more steady.  If we are aligned with the OpenSearch release cadence, predictability of releases and the ability for users to plan will not be impacted.  The release calendar could technically be the same as the OpenSearch one, but publishing a separate one will give us the ability to diverge when necessary.
Releasing from the eponymous branch is more intuitive for users and eliminates the need for freezes as already mentioned.  It will also simplify the release process.


bump dependencies and lock file

This PR:

Bumps some deps
Let the system find itself the appropriate versioning instead of specifying an exact version

cc @xJonathanLEI

As communicated separately, there seems to be no good reason to tweak version ranges like this.


Create recyclebin_recovery.py

Description
Initial concept for recovery from the recyclebin
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated the docstring for new or existing methods
[ ] I have modified this PR to merge to the develop branch

I'm working to rewrite this to support more config options since the original was really specific to my setup

Bump for the rewrite ?

This looks great! To make it ready for merging into the master branch, it would be helpful to ensure it covers all possible configurations. A bit of additional refinement in that area would make it perfect. :)


Fix typo in README, become contributor

Kudos for this great extension. It makes my greedy kindness desiring to become a deskmate.

Oh I never thought of the CASE. Thanks for your huge contribution!


Is it possible to update the operations editor?

I'll hopefully be able to publish an update in the next few days that includes "Hold until relieved" and the strings from "Sledgehammer". The operation itself is however heavily scripted and thus editing it in the operation editor might not be possible unfortunately.

Operation editor fixed and updated in v0.3.1b


Angular 2 version

Hi ,
Should I use this repo for migration of my angular V1 code for the angular frontend or wait to rebuild a better version?
https://github.com/mgechev/angular2-seed

That seed project is good place to start, I have done some work to that too. I would be very happy if you start to make new frontend application using angular2.

And I would just start with another repository of that ng2 version of boilerplate, the whole idea is to support n different frontends which uses the same backend code.


Fix BLOCKHASH() for numbers bigger than int64

The host application assumes the VM will use arguments of type int64, so we need to check if the number is not bigger.
Fixes #52.

Pushed also to cpp-ethereum.


AdMobRewarded compatibility with wix/react-native-navigation (iOS)

Hi! I'm using react-native-navigation router.
AdMobRewarded works fine, but when I try to call it from a modal window (router's showModal method) it is not displayed although the adOpened event is fired (iOS. Android works well).
Have you experienced something similar or have you tried to use the package with react-native-navigation?

The same problem we encountered.
It looks like the ad should come out but it is blocked by the react-native-navigation modal

+1

@koenpunt @sbugert please help us! thánks


(DNM) Remove prerelease badge from Table resizing

Closes
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:
RSP

For after release


Remapping or removing internal ds-test will break intellisense

Version: forge 0.2.0 (f19fd81 2022-10-06T00:10:55.884113912Z)
OS: Linux
Editor: VS Code with Juan Blanco Solidity Extension
Problem: Remapping or removing internal ds-test will break intellisense
Details:
On a fresh build of foundry, running forge remappings > remappings.txt will give the following:
ds-test/=lib/forge-std/lib/ds-test/src/
forge-std/=lib/forge-std/src/

All good. However, the first line is a bit problematic for VS code users.
If you change or delete the ds-test remapping, the language server cannot resolve the import path in, for example: lib/forge-std/src/Test.sol, this will lead to broken intellsense/autocompletion etc etc. It's a bit of a pain to debug as you don't get any error messages in the editor (although certain compiler configurations refuse to compile).
Possible Solutions:
One option would be to make the import path for ds-test in the forge-std library explicit (lib/forge-std/lib/ds-test/src/). This would avoid the need for remappings so the user cannot break it. The code in the std lib would be slightly less concise, but adds resilience and 'just works'.
Alternatively, update the docs https://book.getfoundry.sh/projects/dependencies to indicate that the ds-test remapping should not be changed. I don't love this as it's basically RTFM, but it would hopefully help a few people

Why do you want to change the ds-test remapping? In general you shouldn't need to touch this, but if you want to open an issue/PR in the book to explicitly mention not to touch it that seems ok to me 🙂

I don't but you can.
They get loaded into the remappings.txt file which is required for VS code to detect aliased imports.
Because there is no warning that the ds-test mappings should not be changed, it's possible to break intellisense in the project purely by accident.
Essentially you have a sharp corner with no obvious warning signs and that is why I'm raising the issue, it's a hit on the otherwise wonderful developer experience.

IMO remappings.txt should be considered deprecated and not used. Remappings can be customized with the remappings key in the config file, and the text file approach was originally for backwards compatibility with dapptools. In general, you shouldn't need to worry about remappings unless you have hybrid foundry-hardhat project and need to point foundry to node_modules
Given that, I'd say the linked section of the book that says "You can customize these remappings by creating a remappings.txt file in the root of your project" should be updated
TBH I've never consistently gotten most intellisense features working in foundry projects, the main reason afaik is because solidity lacks a proper LSP so extensions have to hack these intellisense features together with assumptions, and perhaps "look for remappings in remappings.txt is one of those assumptions". I'd assume there are many other things that can confuse intellisense too
Regardless, I don't think there's anything we need to change in forge-std here (personally not a fan of forcing absolute paths, since all deps you install will have a similar default remapping anyway), but if you want to open an issue/PR in the book to clarify things that's fine with me


Update the Kotlin Gradle plugin

Refer to Maven for the most recen Kotlin Gradle plugin version: https://mvnrepository.com/artifact/org.jetbrains.kotlin/kotlin-gradle-plugin

Updated to 1.3.21.


Icon request: Ripe NCC

URL of the site or app
https://www.ripe.net/
Logo resources for the icon
https://www.ripe.net/about-us/press-centre/ripe-ncc-logos
Anything else?
No response

Don't change title format.

I grabbed the ripe-ncc-logo-white-svg file from the provided logos page and made icons with both primary colors from the RIPE NCC 2015 Brand Guidelines PDF (p. 25, see below).

Blue #131F48
Orange #ff6a00

Blue Icon
Orange Icon

RipeNCC (Blue).zip
RipeNCC (Orange).zip

There are also three (3) secondary colors in the brand guidelines document if the primary colors aren't suitable (p. 26).

#6ebe49
#009ba6
#c4d5ec

Hope this helps.

@CampinCarl You need to create submission issue for these #560

Thanks, I'll do that.

Filled by #580.
Added icon: https://github.com/aegis-icons/aegis-icons/blob/master/SVG/Ripe NCC.svg


[FEATURE] Allow provisioning of a completed workflow with no resources

Is your feature request related to a problem?
Currently, we prevent provisioning a workflow twice.  The intent of this restriction is to avoid duplicating resources.   It's possible to provision a second time if you deprovision first.   However, in the edge case where a workflow does not have any resources, the "deprovision" step is a no-op and should not be required.
What solution would you like?
The FlowFrameworkIndicesHandler currently has a boolean to check whether a workflow is started: https://github.com/opensearch-project/flow-framework/blob/main/src/main/java/org/opensearch/flowframework/indices/FlowFrameworkIndicesHandler.java#L491
This is checked in two REST actions to prevent modification: updating (PUT) a workflow and provisioning a workflow.
In both cases, if the provisioning is complete and there are no resources, there is no reason to prevent editing/provisioining; essentially deprovisioning (no-op) to reset the state.
This method should be updated to allow a COMPLETED provisioning with no resources to be considered the same as "not started".  For performance reasons, the not started check should be done first, as the COMPELTED check requires an additional query of the state index to determine whether resources were provisioned.
What alternatives have you considered?
We may just want to allow a parameter, e.g, ?deprovision=true which would complete the deprovisioning (if any) prior to provisioning a second time.  This would work well with the future "fine grained provisioning" feature where in some cases only a partial deprovisioning is required.
To eliminate the need for a resource check for a COMPLETED provision, we can consider another workflow state that we set when provisioning is complete and we have no resources, or we can rename NOT_STARTED to some neutral term, e.g., PROVISIONABLE, meaning there are no resources.
Do you have any additional context?
With the existing ML configuration steps, we don't expect this edge case often, but with automation steps which do not provision, as envisioned by #522, this may be a common situation.

Given the potential for "fine grained provisioining" in the future, it seems the "alternative you have considered" is the best option.  Allow a parameter like "deprovision=true" to fully or partially deprovision.

Is this a feature or bug-fix?

Is this a feature or bug-fix?

More of a feature as there's not really a bug.  Provisioning a workflow that doesn't create resources is somewhat of an edge case.  It's worth seeing how we fully integrate versioning with the front end before committing to a specific solution.


Defaults in TranspileConfig (now called PassManagerConfig)

While write the release notes for #3004, I realized editing a preset passmanager is a real use-case. That requires a more user-friendly TranspileConfig. For example, it needs good defaults.
If I understand correctly this use-case, a user should be able to instantiate a preset pass manager doing something like this:
from qiskit.transpiler.preset_passmanagers.level0 import level_0_pass_manager
from qiskit.transpiler.transpile_config import TranspileConfig
pass_manager = level_0_pass_manager(TranspileConfig())
pass_manager.draw()

If the level_0_pass_manager parameter is not optional, then TranspileConfig() should be a thing. This PR allows it.

I split transpiler_config from pass_manager_config. This is the structure:
transpile_config = {PassManagerConfig(basis_gates,
                                      coupling_map,
                                      backend_properties,
                                      initial_layout,
                                      seed_transpiler,
                                      callback),
                    optimization_level,
                    pass_manager,
                    output_name,
                    circuit,
                    callback}

After fe54db62572bd095ef85c52e47d48794c8cd235d :
transpile_args = {PassManagerConfig(basis_gates,
                                      coupling_map,
                                      backend_properties,
                                      initial_layout,
                                      seed_transpiler),
                  optimization_level,
                  pass_manager,
                  output_name,
                  circuit,
                  callback}

Closed in favor of https://github.com/Qiskit/qiskit-terra/pull/3290/

Can you add a release note for the info that had been in the changelog?

Can you add a release note for the info that had been in the changelog?

Done in https://github.com/Qiskit/qiskit-terra/pull/3035/commits/6b0b4bec6bb611eec47bcfb1352754016f07ee1b

Since it took me a while to see what's going on, I'll summarize my findings. The release notes should have more details.
The original TranspileConfig contained the following fields:
initial_layout,
basis_gates,
coupling_map,
backend_properties,
seed_transpiler,

optimization_level,
pass_manager,
callback,
output_name

the new PassManagerConfig has just:
initial_layout=None,
basis_gates=None,
coupling_map=None,
backend_properties=None,
seed_transpiler=None,

now with None defaults. This makes it easier to instantiate a preset passmanager:
from qiskit.transpiler.preset_passmanagers.level0 import level_0_pass_manager
from qiskit.transpiler.passmanager_config import PassManagerConfig
pass_manager = level_0_pass_manager(TranspileConfig())

The other attributes are moved to a "transpile_args" dictionary, which I don't really like. They should all just be expanded in the functions that accept them. See comments above.

from qiskit.transpiler.preset_passmanagers.level0 import level_0_pass_manager
from qiskit.transpiler.passmanager_config import PassManagerConfig
pass_manager = level_0_pass_manager(TranspileConfig())

should be
from qiskit.transpiler.preset_passmanagers.level0 import level_0_pass_manager
from qiskit.transpiler.passmanager_config import PassManagerConfig
pass_manager = level_0_pass_manager(PassManagerConfig())

Can you try and see if, using this PR, we can make progress on solving #3118

Can you try and see if, using this PR, we can make progress on solving #3118

I see this PR in the direction of #3118, but solving #3118 will create a lot of changes. I can add it in my backlog for doing next.

I agree with @ajavadia lets make this an early merge for the 0.13.0 cycle. I'm updating the milestone accordingly.

Removing on hold since there was a release.


State of the Julia climate stack & desired additions

In relation to #1 but somewhat distinct, let's discuss the current stack of packages and functionalities
Topics could include:

what exists or seems missing?
how mature are different pieces that you know or contribute to?
what do you use and really like in relation to JuliaClimate?
what do lack and really would want to have / contribute to?
...

In case there is interest in a short introduction to the ESDL.jl API, I would be happy to have a call meeting where we could talk through the concepts in ESDL, comparisons to ClimateTasks.jl etc.

Yes, I would be interested to know more about the details of ESDL and how I can use it for climate analysis. For instance, coming Friday (21st) might be possible for me.
Cheers!

In case there is interest in a short introduction to the ESDL.jl API, I would be happy to have a call meeting where we could talk through the concepts in ESDL, comparisons to ClimateTasks.jl etc.

Sorry for the lag in response -- I am still not running behind on a few things after coming back from OSM20 ...
Would be great to learn more about EDSL. I have been meaning to try it...
Unless the call meeting already happened, maybe next week would be good for all interested?

Not too late to the show @gaelforget. :)

Yes, not too late. Let's try to schedule a telecon on potential use of ESDL, Maybe next week? Which time zones are you in? I am in CET and would be available in general either during the day (8am-5pm) or in the evening (after 8:30pm). When we know which times apply for all of us, we could try to fix a date, otherwise feel free to start a doodle or similar.

I'm in Eastern time: https://www.timeanddate.com/time/zones/et
Now with the COVID-19, here in Québec all schools are closed, probably until mid-May. I have 3 small kids and needs to also work! Hence, not sure I'm gonna be free before a couple of weeks.
If the demo goes ahead, I suggest you try to record it. Might be valuable information/tutorial material.


Will giving the Genre 's "values" make the filtering work?

General
The tutorial is good, but filtering by Genre doesn't work. I don't think the MovieGenre request parameter ever comes through, since the select <option>'s on the page don't have a value.
How can we make the Genre filter work? I think this line:
Genres = new SelectList(await genreQuery.Distinct().ToListAsync());
needs to be modified to give us both text and a value. How can we do that?

@johnbyers Please provide a link to the doc you're looking at.

https://docs.microsoft.com/en-us/aspnet/core/tutorials/razor-pages/search?view=aspnetcore-2.1

I didn't realize this project isn't directly linked to that tutorial page. I will open the issue there, it doesn't make sense here.


Fix/pyvista dependency

@AlejandroFernandezLuces Have you also fixed this on the main branch?

The subjacent error is fixed on main, we can use any pyvista version there. Issue #486 should be closed by this.


Document release procedure

Summary
Document the procedure for software releases and how this will be handled for each instrument.
Parent Requirement

SOC-SDC-L4-63
Software Management
The SDC shall provide tools and procedures for managing all software.
Requirement
All instrument team provided software will be managed at the SDC.
SOC-L3-91
Inspection

I can take the lead on this one.


Add a link to the wiki to make screenshots

On https://watchy.sqfmi.com/docs/create-watchface/, there are a lots of nice explanation, but none on how to make a screenshot of the Watchy.
It took me way too long to find the wiki article explaining how to : https://github.com/sqfmi/Watchy/wiki/Screenshots-of-Watchfaces
So, a link should be added to it on the official site, to make sure it's easily findable.

i would like to work on this issue would u please assign it to me?

Thanks for the feedback! Will add it to the docs


Tomas/sdl 1.0

Regenerated models for DeepImageFeaturizer with new version of Keras
and tensorflow.
Tweaked some tests due to the updated keras api.
Had to decrease numeric precision in several tests.
Traced this issue down to changes in tf. Following simple python
example demonstrates tf getting different result than numy on a simple
expression (tf and numpy matched exactly in tf 1.4):

import tensorflow as tf
tf.version
'1.6.0'
import numpy as np
def simple_graph():
...     g = tf.Graph()
...     with g.as_default():
...        x = tf.placeholder(tf.float32, [1], name = 'x')
...        x /= 127.5
...        x -= 1
...        return (g, x)
...
def make_and_run_simple_graph():
...   g, x = simple_graph()
...   return tf.Session(graph = g).run(x, feed_dict =
{'x:0':np.array([55], dtype = np.float32)})
...
tst = make_and_run_simple_graph()
2018-03-26 14:29:40.269905: I
tensorflow/core/platform/cpu_feature_guard.cc:140] Your CPU supports
instructions that this TensorFlow binary was not compiled to use: AVX2
FMA
a = np.array([55], dtype= np.float32)
b = np.array([127.5], dtype= np.float32)
c = np.array([1], dtype= np.float32)
tst = make_and_run_simple_graph()
tst - (a/b - c)
array([  5.96046448e-08], dtype=float32)

Codecov Report

Merging #110 into master will decrease coverage by 9.61%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #110      +/-   ##
==========================================
- Coverage   82.84%   73.22%   -9.62%
==========================================
  Files          34       10      -24
  Lines        1999      493    -1506
  Branches       44       44
==========================================
- Hits         1656      361    -1295
+ Misses        343      132     -211

Impacted Files
Coverage Δ

python/sparkdl/param/image_params.py

python/sparkdl/transformers/keras_tensor.py

.../scala/org/apache/spark/ml/image/HadoopUtils.scala

src/main/scala/org/tensorframes/impl/SqlOps.scala

python/sparkdl/image/image.py

python/sparkdl/param/shared_params.py

python/sparkdl/graph/input.py

python/sparkdl/__init__.py

python/sparkdl/graph/builder.py

python/sparkdl/param/converters.py

... and 33 more

Continue to review full report at Codecov.

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


Fix clash with rspec-rails

This PR fix clash with rspec-rails

Coverage decreased (-0.8%) to 95.971% when pulling 214d5d5eed07ff777f3d5d3d66d2b283c0bc928b on pavel-jurasek-bcgdv-com:develop into e9f2256f780a50d1d593f36c6c91c96fce6d5aa6 on philostler:develop.

Coverage decreased (-0.8%) to 96.0% when pulling c023ad71749d05852252f0b327b02b7b1e11a08d on pavel-jurasek-bcgdv-com:develop into e9f2256f780a50d1d593f36c6c91c96fce6d5aa6 on philostler:develop.

Hi @pavel-jurasek-bcgdv-com , is this in addition to #84 or an improved version of?

Add ability to match symbols
Fix matcher with combination with ActiveJob

Thanks @pavel-jurasek-bcgdv-com . Merged!

Can we get a backport of that in rspec-sidekiq 2.x? Or is 3.0 coming in the foreseeable future? Happy to provide a patch

https://github.com/philostler/rspec-sidekiq/pull/108


Refinements of Wasserstoff-Kernnetz

[x] check overlap of Kernnetz with IPCEI projects (I think there is code from Ammar)
[ ] Implement that those pipelines from Kernnetz marked as retrofitted gas pipelines remove corresponding gas pipeline capacity
[ ] consider build_year when adding capacities: custom_pipes.query("build_year <= @investment_year", inplace=True)
[ ] until 2030: only assume that pipelines from Kernnetz are built (p_nom_extendable=False, via p_nom taking into account build years (i.e. less in 2025 than in 2030)). Pipelines outside of Germany should be extendable because we don't have data.
[ ] after 2030: Set also H2 pipelines in Germany to p_nom_extendable=True but with Kernnetz capacities as p_nom_min (as implemented now).

The overlap with the ipcei pipelines lokks good:
IPCEI:

Model:

Two questions concerning the implementation of the reduction of the corresponding gas pipeline capacity if it is retrofitted for H2: If I see it correctly, the gas pipelines are implemented such that they are partially bidirectional and partially unidirectional. The kernnetz is implemented completely bidirectional.
1: So I would remove the capacity from the sum of the uni- and bidirectional gas pipes capacity and not from every existing pipeline?
2: How comes that, the reversed pipelines can have a smaller p_nom that the corresponding bidirectional pipeline?

Tasks of refinement are build in:

If kernnetz pipeline is build in period, the corresponding gas pipeline capacity is removed if it exists
build_year is considered
until 2030 H2 pipes in Germany are not extendable, however kernnetz exists
from 2030 all H2 pipelines are extedable, The kernnetz capacities are not implemented as p_nom_min, but as additional lines which is not extendable.

What I checked:
checklist

kernnetz: check with
2020: no kernnetz
2030: correctly builds 20 pipes (with reversed)
2040: correctly builds 10 additional pipes (with reversed)
2050: no mor pipes (already completely build)
code: n.links[n.links.index.str.contains("kernnetz")]

reduction of gas network:
2020: no difference in gas pipelines between prenetworks brownfield and prenetworks-final
2030: 614 GW removed of 639 GW possible removed
2040: 65 GW removed from possible 175 GW
2050: no more removal
code: n_bf.links.loc[(n_bf.links.carrier == "gas pipeline"), :].p_nom.sum() - n_f.links.loc[(n_f.links.carrier == "gas pipeline"), :].p_nom.sum()

p_nom max of prenetworks-final is roughly such an amount lower as the wkn in the period:
2020: p_nom max is 282 GW lower in final, whole reduction would have been 489 GW if you account for bidirectional pipes (reason for difference is that there is no retrofitting potential is some pipes of the gas network where it should be)
2030: same as year before
2040: same
2050: same

plots of kernnetz:

2020: no kernnetz

2030:

2040:

2050: same as 2040

code :

n_f.links.bus0 = n_f.links.bus0.str[:-3]
n_f.links.bus1 = n_f.links.bus1.str[:-3]

# 2030
import cartopy.crs as ccrs
import pandas as pd

fig, ax = plt.subplots(1, 1, figsize=(20,20), subplot_kw={"projection":ccrs.PlateCarree()})
n_f.links = n_f.links.loc[(n_f.links.carrier == "H2 pipeline") & (n_f.links.index.str.contains("kernnetz")), :]

n_f.plot(ax=ax, line_widths=0, link_widths=n_f.links.p_nom/5e3)

the reduction of retrofitted and gas pipeline capacity is applied don the right lines
To run the model with H2 retrofit those fixes have to be made to pypsa-eur submoduls branch:
https://github.com/daniel-rdt/pypsa-eur/blame/44d9337b2e826aaa25b285784b3efa960bdb96e1/scripts/plot_network.py#L325-L337
https://github.com/daniel-rdt/pypsa-eur/blame/44d9337b2e826aaa25b285784b3efa960bdb96e1/scripts/plot_network.py#L263-L268


Enhance Copy/Update action in Settings editor

Current copy/update action has following issues

[ ] Display the edit icon in settings with a small delay
[ ] dropdown decorator only works for first setting with multiple settings on a single line
[ ] action decoration in settings file makes it hard to put cursor at end of line
[ ] Settings: Edit icon off by a few pixels
[ ] Clicking edit icon in editable settings.json scrolls horizontally
[ ] New settings "copy to settings" drop down is clunky
[ ] "edit" button for settings not discoverable
[ ] "Copy to Settings" overwrites existing value

@bgashler1 Listed in the description are the issues with Edit icon in Settings editor. Most of them are usability issues. Hence, I have done following changes to the edit icon

Moved and placed edit icon to the Glyph margin just like Light bulb. This will make action to be consistent.
Icon is visible when the cursor is in setting or when mouse is hovered on setting (includes description, value)
Used line highlights when
a. Hovering on icon
b. On copying the setting
When there are more than one setting in a line, used sub context menu.

Looks like there is no UX call today hence showing the video here

Feedback is welcome.
Thanks

@sandy081 this is great 👍 nice work!  I love the consistency parallel you introduced.  I can't wait to try it out.
One other thing that would be cool to have is that if you scroll down the search box could become fixed at the top (but first letting you scroll passed the header/description above it).
.
What do you think?


[WIP] update tabular fit docs

Removed "rl" searcher option from tabular_prediction.fit() as it has issue: https://github.com/awslabs/autogluon/issues/317

extra tabular_prediction fit() example to demonstrate how to maximize predictive accuracy

Job PR-330-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-330/1/index.html

LGTM. Thanks!

@zhanghang1989 should I also go ahead and remove this 'rl' option from the ImageClassification + other tasks' docs?

Image classification works fine with RLScheduler and RLSearcher, as it is handled differently.
https://github.com/awslabs/autogluon/blob/master/autogluon/task/base/base_task.py#L15-L21


chore: adding devcontainer with create aztec app

Please read contributing guidelines and remove this line.

#5960  👈
master

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

Join @signorecello and the rest of your teammates on  Graphite

I see this when clicking the button when I am logged in with a github account that is not part of AztecProtocol

Interesting, I'll check this out. Indeed I made the boxes with 8gb RAM, that can explain it

Docs Preview
Hey there! 👋 You can check your preview at https://6632410fb5bd62e2a61fe5dc--aztec-docs-dev.netlify.app


Suppress Error and Event Logging with the C# wrapper

Is your feature request related to a problem? Please describe.
There's no way (as far as I can tell) to suppress error messages using the C# wrapper. Error messages print out even when the exception is caught in a try-catch.
Describe the solution you'd like
Expose the ability to silence error and event logging through the C# wrapper
Describe alternatives you've considered
Catching the exception (didn't work).
Setting the environment variable K4A_ENABLE_LOG_TO_STDOUT to 0 (didn't work)
Ignoring the issue (doesn't solve...).
Additional context
try
{
    kinect = Device.Open();
}
catch (AzureKinectOpenDeviceException)
{
     return false;
}

still results in
[2019-10-29 08:51:39.234] [critical] [t=13652] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\usbcommand\usbcommand.c (360): find_libusb_device(). libusb device(s) are all unavalable. Is the device being used by another application?

[2019-10-29 08:51:39.236] [error] [t=13652] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\depth_mcu\depth_mcu.c (68): usb_cmd_create(USB_DEVICE_DEPTH_PROCESSOR, device_index, NULL, &depthmcu->usb_cmd) returned failure in depthmcu_create()

[2019-10-29 08:51:39.236] [error] [t=13652] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\sdk\k4a.c (133): depthmcu_create(index, &device->depthmcu) returned failure in k4a_device_open()

How are you setting the environment variable? I am seeing the error messages, but if I set the environment variable in the command line before launching my app it is suppressed. Are you attempting to suppress the logging from within in your program?

I set the environment variable via Control Panel > System > Advanced System Settings > Environment Variables. I couldn't find a way to suppress messages from my program.

If you update the environment variable via the Advanced System Settings -> Environment Variables, you need to restart the process that you are launching your program from.  For example, restarting the Command Prompt or Visual Studio.
An easy way to check if it is set correctly is to add Console.WriteLine("K4A_ENABLE_LOG_TO_STDOUT = {0}", Environment.GetEnvironmentVariable("K4A_ENABLE_LOG_TO_STDOUT")); to your code before you make any K4A calls.  One note here is that calling SetEnvironmentVariable in C# won’t update the C runtime cache and therefore K4A won’t honor that setting.
Probably the easiest way to ensure that you don’t have the extra logging is to just run the executable from a batch script that first sets the environment variable before executing your program.
The original design was that by setting the debug message handling the console logging wouldn’t be initialized.  We are looking into fixing that.  However, because of the way the C# code was written, it always registers a handler, so fixing the issue would result in the opposite behavior you have now, if you want the logging you would have to set the environment variable to log to the console before launching the application.
Let me know if restarting the application lets you pick up the environment variable correctly.

It works now. Restarting Visual Studio fixed the issue. Thanks for the additional information.


ERROR in The Angular Compiler requires TypeScript >=3.6.4 and <3.8.0 but 3.8.3 was found instead.

Description
I just upgraded to Angular 9 using ng update --all --force -C. No other options worked.
Now when I run ng serve, I get an error, ERROR in The Angular Compiler requires TypeScript >=3.6.4 and <3.8.0 but 3.8.3 was found instead.
Why did Angular update me to Typescript 3.8.3 if it's not supported?

@bryanrideshark You can manually update the typescript version (say, to 3.7.5) after "ng update".
In general, I run into this type of issues with virtually every angular version upgrade. This question is really for the Angular Team, but is there a reason why the maximum typescript version should be set for each Angular release? For example, in this particular case, is there a reason why we should presume that Angular 9 will not work with future versions of typescript (or, even with 3.8.x), say, instead of following the semantic versioning convention?

TypeScript does not strictly follow semantic versioning.  Breaking changes are present in minor releases.  Since the Angular compiler leverages TypeScript, each minor version needs to be validated before it can be officially supported.
The combination of the --all and --force flags are why TypeScript 3.8 was installed.  If using just the -all flag, the following will be reported:
Package "@angular-devkit/build-angular" has an incompatible peer dependency to "typescript" (requires ">=3.6 < 3.8", would install "3.8.3")
Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=3.6 <3.8", would install "3.8.3")

The --all flag will attempt to update every package mentioned in the workspace's package.json to the latest version.
For information regarding recommended update procedures, please see https://update.angular.io/#8.0:9.0

I found an older TypeScript GitHub issue that supports what @clydin is stating. Sigh.
https://github.com/microsoft/TypeScript/issues/14116

npm i<EMAIL_ADDRESS><3.8.0"


Correct enum indentation in vimscript

Specially handle commas within an enum block to correct indentation issue in #16289.
And improved test for indentation.

Don't forget to update runtime/indent/testdir/vim.{in,ok}
tests to test your changes.  You can peek at my changeset to
figure out what additional changes are required for CI (also
see this README.txt).
Then, test it locally as follows:
cd runtime/indent
make clean test

I would also consider adding a more complicated test, e.g.:
" START_INDENT
enum Digits
INVALID(v:numbermax),  # The null value.
ZERO(0 * v:numbermin), ONE(2 - 1),
TWO(1 + 1), THREE(9 / 3), FOUR(1 * 4),
FIVE(1 + 2 + 2), SIX(36 / 3 / 2), SEVEN(7), EIGHT(2 * 2 * 2),
NINE(3 + 3 + 3)
const value: number
def new(this.value)
enddef
endenum
" END_INDENT

The proposed changes work for reformatting the whole enum
block and as long as the indent cache is valid.  As before,
typing in enum values and keeping them aligned requires one
i_Ctrl-d stroke after entering the second value followed by
a comma.

The proposed changes work for reformatting the whole enum
block and as long as the indent cache is valid. As before,
typing in enum values and keeping them aligned requires one
i_Ctrl-d stroke after entering the second value followed by
a comma.

That's indeed a problem, I'll take some time finding a better solution.

I believe this is a simple solution to the issue. However, since it is limited to enum blocks and partially overlaps with the logic for indenting bracket blocks, further refactoring may be needed in the future to improve the code.

The latest patch version correctly aligns enum values when
they are typed and when they are formatted.  Thank you.
It would be nice if some future patch tried a bit harder at
recovering indentation for value arguments split across two
or more lines when they are typed.  For example:
vim9script

enum RGB
    RED(
        0xff0000,
        0),
    GREEN(
        0x008000,
        0),
    BLUE(
        0x0000ff,
        0)

    const value: number
    var other: any

    def new(value: number, other: any)
        this.value = value
        this.other = other
    enddef
endenum

thanks!


Button height, length & width irregularities and padding around button text

Some buttons feature less padding than others, and inconsistent use of padding, height and
width. The specified height is minimum 10mm, with 15px padding around the button, but there is
no mention of a maximum height and padding between text within a button and its perimeter.
(https://gctools-outilsgc.gitbook.io/-gcdigital-design-system/buttons). For the UI Kit file, it would be
preferable if all buttons were the same height and an established range of widths (3 variations),
so external users are absolutely certain that the assets they are composing an experience with
are fundamentally consistent.

Recommend re-establishing consistent padding between button text and button perimeter
for all buttons. Build a default button and re-use (see tutorial)
Recommend using either px or mm for dimension specifications throughout the UI Kit. Currently a combination of mm & px dimensions are used creating some leeway for
misinterpretation
Recommend converting button to text shape where button text is centred, This allows the
button perimeter to scale consistently & proportionately in accordance with changes to
the text content. A step-by-step tutorial can be provided. The technique can also prevent ‘eyeballing’ of text within a shape.
Tutorial on GitHub: https://github.com/gctools-outilsgc/designsystem/blob/master/ui_kit_visual_review/Scalable_Bttns_v01.mp4

See page 4 of UI kit report

Define small, normal and large button classes.


fix(store): replace pg_advisory_xact_lock by unique index

:tada: This PR is included in version 1.0.0-alpha.2 :tada:
The release is available on:

GitHub release
v1.0.0-alpha.2

Your semantic-release bot :package::rocket:


TODO ISSUE

Setup Azure Space, Blobs, Authentication, and Model Endpoint
Scrape YouTube for Transcripts
Train Model on Andrew Huberman's Voice

Need to also reformat/find solutions to store the dataframe that was scraped. Excel has a max cell length of 32,760 characters so the current excel file has incomplete transcripts. Need to also reformat the transcript format to make it easier for model training


feature: extract the most relevant parts using NetworkX in repo-map

Feature request
Use NetworkX to extract repo-map to reduce token usage
Motivation
No response
Other
No response

After considering the problem further, @aarnphm was likely right. Something like ColBERT would be the best approach to retrieve definitions that are important to the prompt when requesting an action from the LLM.
Initially, I thought that including the structure of the code would be more important than the semantics of the definitions. However, after further consideration, I've come to the conclusion that semantic relevance of definitions is crucial to include for context.
Let's consider a scenario where we're developers making a hypothetical change to lua/avante/repo_map.lua, and we've added lua/avante/colbert.lua.
We prompt the LLM:
"Change the get_repo_map() method to retrieve n number of tokens passed in as a parameter of the method via ColBERT."
If we were developing this ourselves, we would likely use tools like ripgrep to search for colbert or read colbert.lua to get an understanding of it. When doing this we are focusing on semantic content rather than the structural hierarchy of the codebase.
That being said, I'm not sure that using NetworkX for ranking is the right approach. Does anyone else have thoughts on this?


feat(all): apply rollup for build distributions files.

Issue
#239
It reduces library size.
Details
Apply tree-shaking using webpack4
Ref https://github.com/naver/egjs-view360/issues/229#issuecomment-438105395
apply rollup

target
before size (kb)
after size(kb)

view360.pkgd.min.js
184
129

PanoViewer.pkgd.min.js
178
125

SpinViewer.pkgd.min.js
69
39

Coverage decreased (-0.008%) to 93.692% when pulling 513fef0fde825786545c5035aa36a8f56e33175f on jongmoon:rollup#239 into 5f854987ccedcd8cb94f2f77af46a361bb34fec7 on naver:master.


Command 'Diff: File' resulted in an error (Running the contributed command: 'diff.file' failed.)

My Diff extension stopped working today. Showing me this error
Command 'Diff: File' resulted in an error (Running the contributed command: 'diff.file' failed.)

@arvinyorro Can you reproduce this issue reliably?

Closing for lack of additional information.


Influence of BlCrvAC and BlSwpAC on AeroDyn outputs -- comparison standalone and OpenFAST

Hi,
While validating a coupling of AeroDyn, I came through a comparison between OpenFAST and AeroDyn standalone (OpenFAST master branch v2.3.0). The OpenFAST test cases were as simple as possible to compare with AeroDyn (Elastodyn with motion DOFs unactivated, InflowWind with constant uniform wind, AeroDyn). In other words, it defines a rigid onshore wind turbine with prescribed rotation of the rotor and no control. I expected the results output by AeroDyn/standalone to be similar to those from AeroDyn/OpenFAST. Am I wrong ?
In fact, I observed two different behaviors, linked to the parameters BlCrvAC and BlSwpAC in AeroDyn's blade file:

When BlCrvAC=BlSwpAC=0m for each aerodynamic node, both simulations provide the exact same results.
Otherwise, differences show up from the very beginning of the simulation. As soon as BlCrvAC and BlSwpAC are non-zero on a given aerodynamic node, the evaluation of the local aerodynamic outputs at this node differ.

To illustrate the issue, I ran a test case using the NREL 5MW turbine, for which BlCrvAC and BlSwpAC are non-zero. The following figure presents the local AoA at a given node for 4 different configurations:

Blue : OpenFAST with regular 5MW blade
Orange : AeroDyn standalone with regular 5MW blade
Green : OpenFAST with modified 5MW blade (BlCrvAC=BlSwpAC=0m). Curve superposed with red one
Red : AeroDyn with modified 5MW blade (BlCrvAC=BlSwpAC=0m). Curve superposed with green one
Interestingly, at t=0s, the offset between Blue and Red/Green is twice the one between Orange and Red/Green. This is true for several local parameters, and this is independent from the values of BlCrvAC and BlSwpAC.

I investigated a bit, and I feel like the translation velocity evaluated at blade nodes AD%u%BladeMotion(k)%TranslationVel may generate this difference. For a simulation with the 5MW blade, I compared at t=0s the position of blade aerodynamic nodes u%BladeMotion(1)%position and the translation velocity AD%u%BladeMotion(1)%TranslationVel in AD_CalcOutput, for a simulation with AeroDyn/standalone and another with OpenFAST. While minor differences exist for the position, the translation velocity varies a lot. The differences in position and translation velocity can be found in the file attached (in meters).
AD_vs_OF_Blade1_position_translationvel.txt
I'm a bit confused by the computation of this translation velocity in those 2 test cases.

AeroDyn's driver computes it from a prescribed rotation of the rotor and the position of aerodynamic nodes. This directly takes into account the bending parameters BlCrvAC and BlSwpAC.
From what I understand, during an OpenFAST simulation, the rotation is performed within Elastodyn's routines. ElastoDyn's blade mesh is used to compute the translation velocity, which is then interpolated back onto the aerodynamic nodes. I don't get how the correct velocity fields can be obtained, as ElastoDyn has no idea of what BlCrvAC or BlSwpAC may be.

Sorry for the looong question, I tried to keep it precise and to expose clearly what I went through. I joined a test case to reproduce the problem, see below.
Have a nice day,
Louis Douteau
To Reproduce
All the results presented here have been obtained from the test case attached.
5MW_Land_DLL_WTurb_compAD.zip
Steps to reproduce the behavior:
1- update in the Makefile OF_FOLDER_PATH = path to OpenFAST repo
2- choose the AeroDyn blade file (NRELOffshrBsline5MW_AeroDyn_blade.dat or NRELOffshrBsline5MW_AeroDyn_blade.dat.noCrvSwp)
3- "make run" to run both OpenFAST and AeroDyn
4- "make plot" to compare outputs (comparative plots written to comp*.png)

Hi @ldouteau,
Thank you for your thorough description of the problem.
My theory is that the difference in velocity at the aerodynamic analysis nodes that you are seeing is related to interpolation in the Line2-to-Line2 mesh-to-mesh mapping in the coupled ElastoDyn-AeroDyn solution of OpenFAST versus the analytically exact calculation used in the AeroDyn driver.  If my theory is correct, then I would expect to see the effect of interpolation go to zero as the number of structural analysis nodes in ElastoDyn (BldNodes) increases, bringing the coupled ElastoDyn-AeroDyn solution of OpenFAST closer (and eventually match) the solution from the AeroDyn driver.  Can you run this test and report the results?
If increasing BldNodes in ElastoDyn does not improve the results, I would guess that there is a bug somewhere in the kinematics math--either in the AeroDyn driver or the Line2-to-Line2 mesh-to-mesh mapping, but this would surprise me as this math has been checked many times before.
Best regards,

Hi @jjonkman ,
Thank you for your reactivity !
I went through your suggestions, first trying to increase the number of nodes in ElastoDyn, but the results remained unchanged. See the upcoming plots ran on the same test case as yesterday:

Blue and Orange respectively OpenFAST and AeroDyn with 18 ED nodes
Green and Red respectively OpenFAST and AeroDyn with 118 ED nodes. Green and Blue (resp. Red and Orange) data sets superpose perfectly.

I agree to your point that the interpolation is probably the cause of the differences observed. I agree too that either the Line2-to-Line2 function or the AeroDyn implementation are probably not bugged, I guess this issue would have came out earlier then. My interpretation would be that, as soon as prebending parameters are non-zero, the aerodynamic nodes are displaced, moved away from the structural nodes. The interpolation would then loose precision.
To clarify this I attached two files to illustrate this point, which compare the positions of aerodynamic and structural nodes (evaluated at the Line2_to_Line2 call) :

for the modified 5MW blade, with BlCrvAC=BlSwpAC=0m at each aerodynamic node. ElastoDyn and AeroDyn nodes almost coincide, the interpolation is straightforward, and ultimately AeroDyn/standalone and OpenFAST compare well.
ED_AD_interpolation_5MW_noCrvSwp.txt
for the actual 5MW blade, withBlCrvAC and BlSwpAC non-zero. An important deflection is observed along the y-axis between both samplings, which I assumed from the previous situation to use the same coordinate system. The interpolation realized would be less relevant, and may thus explain the differences with AeroDyn/standalone where the motion is computed at the exact position of aerodynamic nodes.
ED_AD_interpolation_5MW.txt

I also tried to compare the evolution of the offset with BlCrvAC alone on a single node. I just went with BlSwpAC=0m on a given aerodynamic node, varied BlCrvAC and examined the evolution of the relative velocity (could have been another local parameter). The upcoming plot exposes Vrel(BlCrvAC,t=0s)-Vrel(BlCrvAC=0m,t=0s) for both AeroDyn/standalone (AD) and OpenFAST (OF). The datasets are perfectly linearly fitted (R²=1), with the 0.01 offset due to the format of outputs. The evolution of Vrel with BlCrvAC is twice faster when simulating with OpenFAST, I don't know if it can help finding the source of the error.

What is your opinion about these observations ? Let me know if you need me to perform other checks.
Have a nice day,
Louis

Hi @ldouteau,
OK, I tracked down the bug, which was in the rotational velocity field of the ElastoDyn blade output mesh, where the rotational speed was accidentally doubled.  This bug would effect any coupled AeroDyn-ElastoDyn solution with curvature or sweep offsets set in AeroDyn.  The bug should be fixed in PR #453.
Best regards,

Hi @jjonkman,
Your correction solved the problem. Thank you for the efficient follow-up !
Best regards,
Louis


--target-cov failing

Based on the latest version from Master, it appears that the --target-cov option is not currently working with mmseqs cluster. Specifically, something like:
mmseqs cluster DB DB_clu tmp --min-seq-id 0.4 --target-cov 0.8 --cluster-mode 2
returns a number of errors. I think what's happening is that internally, the options -c 0 and --target-cov 0.8 are being based passed to other commands (e.g. linclust), and they're failing because they're not expecting both options at once. Note that I am not passing -c 0 to the main command, but internally it's generated and passed to other commands.

Hi Mohammed,
I think I know whats happening and I can fix it tomorrow.
As a short-term workaround until then: If you explicitly pass MMseqs a sensitivity, it won't automatically try to use the cascaded workflow, where this issue is (most likely) happening. You want the cascaded clustering for a larger database though.
Best regards,
Milot

Thanks for the tip Milot. Yes you're right, specifying a sensitivity does make it run. It's a bit strange because cascaded clustering is off by default (at least according to the help), so I'm not sure why it's using it without me explicitly asking for it. At any rate, I look forward to the fix!

Hi Mohammed,
I removed the --target-cov parameter and replaced it with a new parameter --cov-mode 1.
The documentation was also updated:
https://github.com/soedinglab/MMseqs2/wiki#how-to-set-the-right-alignment-coverage-to-cluster
Why its automatically choosing the cascaded clustering:
We implemented some heuristics to automatically choose the best parameters originally for the clustering. Maybe we have to rethink that decision and remove those.
Best regards,
Milot

Thank you Milot! It appears to be working now.


Tweak the columns to show the Succeeded condition, reason, start, and end times.

$ kubectl get builds
NAME                                          SUCCEEDED   REASON         STARTTIME   COMPLETIONTIME
test-build-with-more-steps                    True                       18m         16m
test-build-with-serviceaccount-docker-basic   True                       18m         17m
test-build-with-serviceaccount-git-ssh        True                       18m         17m
test-build-with-serviceaccount-pull-secrets   True                       18m         17m
test-build-with-step-status                   True                       19m         16m
test-configmap                                True                       19m         17m
test-custom-env-vars                          True                       18m         16m
test-custom-source                            True                       18m         17m
test-custom-source-cluster                    True                       18m         16m
test-custom-volume                            True                       18m         17m
test-failure                                  False                      18m         17m
test-gcs-archive                              True                       18m         16m
test-git-branch                               True                       18m         17m
test-git-revision                             True                       18m         17m
test-git-tag                                  True                       19m         18m
test-git-volume                               True                       19m         16m
test-home-is-set                              True                       18m         17m
test-home-volume                              True                       19m         16m
test-panic                                    False                      18m         17m
test-reuse-git-init                           True                       18m         16m
test-secret-env                               True                       18m         17m
test-secret-volume                            True                       18m         16m
test-subdir-exists                            True                       19m         16m
test-subdir-nofile                            False                      18m         17m
test-subdir-notexists                         False                      19m         17m
test-template-args                            True                       18m         16m
test-template-env-merge                       True                       18m         17m
test-template-volume                          True                       18m         17m
test-unnamed-steps                            True                       18m         16m
test-with-high-timeout                        True                       19m         18m
test-with-low-timeout                         False       BuildTimeout   18m         17m
test-workingdir                               True                       19m         17m
test-workspace-volume                         True                       19m         16m

cc @greghaynes (this follows my feedback from knative/serving, thanks for the trick to access the specific condition!)

It is notable that this requires 1.11, but is harmless on 1.10

TBH, I think this is a better UX than columns.txt, but there's a lot of overlap.
I agree on the relative times, this was unexpected for type: date.  I will experiment with format: date and format: date-time to see what comes out.

No luck with date and date-time :(

/lgtm
/approve


Platform error sensor.openweathermaphistory - Exception importing custom_components.openweathermaphistory.sensor

Hi,
since a few days the following error message is displayed when I want to restart HA (Developer Tools -> YAML -> Restart):
The system cannot restart because the configuration is not valid: Platform error sensor.openweathermaphistory - Exception importing custom_components.openweathermaphistory.sensor
Furthermore, the following error messages are displayed in the HA log:
_Logger: homeassistant.components.websocket_api.http.connection
Source: components/hassio/init.py:707
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 10:50:43 (1 occurrences)
Last logged: 10:50:43
[547577543456] The system cannot restart because the configuration is not valid: Platform error sensor.openweathermaphistory - Exception importing custom_components.openweathermaphistory.sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 200, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1744, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1781, in execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/usr/src/homeassistant/homeassistant/components/hassio/init.py", line 707, in async_handle_core_service
raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: The system cannot restart because the configuration is not valid: Platform error sensor.openweathermaphistory - Exception importing custom_components.openweathermaphistory.sensor

_Logger: homeassistant.components.hassio
Source: components/hassio/init.py:696
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 10:50:43 (1 occurrences)
Last logged: 10:50:43
The system cannot restart because the configuration is not valid: Platform error sensor.openweathermaphistory - Exception importing custom_components.openweathermaphistory.sensor_

_Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: homeassistant.loader
Source: custom_components/openweathermaphistory/sensor.py:55
Integration: openweathermaphistory (documentation, issues)
First occurred: 09:58:03 (2 occurrences)
Last logged: 10:50:43
Unexpected exception importing platform custom_components.openweathermaphistory.sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 728, in get_platform
cache[full_name] = self._import_platform(platform_name)
File "/usr/src/homeassistant/homeassistant/loader.py", line 745, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
File "/usr/local/lib/python3.10/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1006, in _find_and_load_unlocked
File "", line 688, in _load_unlocked
File "", line 883, in exec_module
File "", line 241, in call_with_frames_removed
File "/config/custom_components/openweathermaphistory/sensor.py", line 55, in
vol.Optional(CONF_UNIT_SYSTEM, default=CONF_UNIT_SYSTEM_METRIC): cv.unit_system,
AttributeError: module 'homeassistant.helpers.config_validation' has no attribute 'unit_system'

Unfortunately, I can not remember when the problem started.
Current configuration:
Home Assistant 2022.11.2
Supervisor 2022.10.2
Operating System 9.3
Frontend 20221108.0 - latest
WeatherFlow integration v1.0.8
I am quite inexperienced with HA, should you need any further information, please let me know.
BR
Dirk

Hi Dirk,
Sorry you have this issue, but it is not related to the WeatherFlow integration. If you look at the logfile you will find lines like this /config/custom_components/openweathermaphistory/sensor.py" so your errors are related to an integration called openweathermaphistory. Please post your error there.

Oh, sorry about that. I mixed up the error messages with Weatherflow.
Sorry for the unnecessary request.


[wagtail] Update release info

Updated with information from https://github.com/wagtail/wagtail/wiki/Release-schedule, restructured recent versions to have sensible date orders in the YAML.

Could you rebase your branch against the latest commit here please? It's running quite behind and failing builds as a result.

Superseded by #1588 -> close


Hard-coded version number

https://github.com/DCAN-Labs/dcan_bold_processing/blob/2ef154c6bc70dc3029d4b5941d1bf51f65db7334/dcan_bold_proc.py#L4
Does this need to be hard-coded?  If so, could explanation be added to the code, including other modules where it might need to be changed?

It actually does need to be hard coded. We should be updating it when we release a new tagged version. I'm not sure how difficult it would be to go back and edit this field in the previous tags. I think we just need to make sure that we updated this field in new releases from now on.
Thank you for bringing this to our attention Paul.

@perronea @paul-reiners @madisoth @arueter1 @ericfeczko I should warn you that the historical reason we didn't update this hard-coding was because it goes into file names which are taken as outputs and Kathy and I were afraid if we updated that string there it would break post-processing scripts/analyses that expected those filenames.  So, I guess that's just a word of warning.  I agree it should update with each version, but it's a risky change for downstream stuff.

That's a great point @ericearl. Maybe it should be removed all together and tracked in a separate metadata file within each subject's DBP directory just like the matlab config.

@perronea I think that would be a better change, yeah. But certainly be careful about filename overlaps and downstream tools expecting the original version string.

I'm closing this issue - as Anders explained, this does need to be hard-coded


SetParametersAndRender will breaks with .NET 8

Describe the bug
The extension function SetParametersAndRender throws a NullPointerException since the ComponentState.SetDirectParameters methods vilisbility is changed to internal in .NET 8.0 Preview 4.
The exception is raised here:
https://github.com/bUnit-dev/bUnit/blob/e654d6d21b269e1e7a15a812968532a17795caff/src/bunit.core/Rendering/TestRenderer.cs#L211-L213
Example:
Testing this component:

    @Test

@code {
    [Parameter]
    public string? Test { get; set; }
}

With this test:
        // Arrange
        var test = "Hello";
        var nextTest = "World";

        // Act
        var cut = RenderComponent<ExampleComponent>(p => p.Add(x => x.Test, test));
        cut.SetParametersAndRender(p => p.Add(x => x.Test, nextTest));

        // Assert
        cut.MarkupMatches($"
{nextTest}
");

Results in this output:
Message:
System.NullReferenceException : Object reference not set to an instance of an object.

  Stack Trace:
<>c__DisplayClass32_0.<SetDirectParameters>b__0() line 213
<>c.<InvokeAsync>b__8_0(Object state)
--- End of stack trace from previous location ---
TestRenderer.AssertNoUnhandledExceptions() line 582
TestRenderer.SetDirectParameters(IRenderedFragmentBase renderedComponent, ParameterView parameters) line 232
RenderedComponentRenderExtensions.SetParametersAndRender[TComponent](IRenderedComponentBase`1 renderedComponent, ParameterView parameters) line 33
RenderedComponentRenderExtensions.SetParametersAndRender[TComponent](IRenderedComponentBase`1 renderedComponent, Action`1 parameterBuilder) line 68
Tests.UpdatesCorrectly() line 39
RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)

Version info:

bUnit version: 1.22.19
.NET Runtime and Blazor version: 8.0.0-preview.6.23329.11

Additional context:
Related changes in dotnet/aspnetcore:

Commit: #ff2241b
Pull Request: 47555

Hey @a2er,
Yes that is definitely a regression we did not catch as we only run the test up til net7.0.
@egil as v2 is not ready, we should enable v1 for net8.0. At least to a degree where users can still use v1 without any issue on the newest .net version.

@egil: I have a PR ready when I get back from the holidays (tomorrow evening).
I have a new laptop and my ssh settings and stuff are not ported - therefore I want to set this up tomorrow for signed commits and stuff

FYI: In net 8 some of the things we need reflection for are now available without.

Thanks for the quick respone!
FYI: I was running the unit tests with .net 8. There are other issues:

(Fails related to this issue are not shown.)
Let me know if you want me to do further investigations on those.

Thanks for the heads up. Yes there are other things for net8.0. Mainly the renderer has a new method that the bUnit one has to implement. And there is a new test double we have to provide.

There should be a prerelease on NuGet soon.
Would be nice to get some feedback on this one

SetParametersAndRender is working as expected.
I will continue playing around with .NET 8 Blazor (but WASM only) you may hear from me.
Thanks for the quick fix guys!


IGAPP-564: Send signal on feedback

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword IGAPP.

Not sure if it is supposed to be like this, but no information is send where the feedback was send (offers, categories, search.. ) but we send signals for every page opened so it should be oke, i guess?


[ᚬmaster] Rc/v0.26.4

Codecov Report

Merging #417 into master will decrease coverage by 0.01%.
The diff coverage is 90.9%.

@@            Coverage Diff             @@
##           master     #417      +/-   ##
==========================================
- Coverage   90.14%   90.13%   -0.02%
==========================================
  Files          26       26
  Lines        1137     1145       +8
  Branches      265      268       +3
==========================================
+ Hits         1025     1032       +7
- Misses        111      112       +1
  Partials        1        1

Impacted Files
Coverage Δ

packages/ckb-sdk-rpc/src/defaultRPC.ts
100% <ø> (ø)
:arrow_up:

packages/ckb-sdk-utils/src/ecpair.ts
97.5% <100%> (+0.27%)
:arrow_up:

packages/ckb-sdk-utils/src/index.ts
100% <100%> (ø)
:arrow_up:

packages/ckb-sdk-rpc/src/resultFormatter.ts
99.11% <75%> (-0.89%)
:arrow_down:


ATT error: 0x0e (unlikely) after write

When I try to write the "text/string" characteristic in the unmodified standalone.cpp / Server.cpp I get the error 0x0e (unlikely). When using gatt-python this error shows as  'Operation failed with ATT error: 0x0e' and with nRF Connect I get Write operation failed: BLE_GATT_STATUS_ATTERR_UNLIKELY_ERROR (0x010E).
I have tested with bluez 5.48 and 5.45 on Ubuntu 18.04 and I don't see useful debug information in the logs, the error is not mentioned neither by bluetoothd nor gobbledegook. btmon shows me the error is sent:
Bluetooth monitor ver 5.48
= Note: Linux version 4.15.0-42-generic (x86_64)                                             0.728855
= Note: Bluetooth subsystem version 2.22                                                     0.728857
= New Index: BA:27:EB:BB:B3:40 (Primary,USB,hci0)                                     [hci0] 0.728857
= Open Index: BA:27:EB:BB:B3:40                                                       [hci0] 0.728858
= Index Info: BA:27:EB:BB:B3:40 (Cambridge Silicon Radio)                             [hci0] 0.728858
@ MGMT Open: standalone (privileged) version 1.14                                   {0x0003} 0.728859
@ MGMT Open: bluetoothd (privileged) version 1.14                                   {0x0002} 0.728859
@ MGMT Open: bluetoothd (privileged) version 1.14                                   {0x0001} 0.728859
@ MGMT Open: btmon (privileged) version 1.14                                        {0x0004} 0.728939
> ACL Data RX: Handle 68 flags 0x02 dlen 12                                        #1 [hci0] 9.186933
      ATT: Write Request (0x12) len 7
        Handle: 0x0037
          Data:<PHONE_NUMBER>
< ACL Data TX: Handle 68 flags 0x00 dlen 9                                        #2 [hci0] 14.192821
      ATT: Error Response (0x01) len 4
        Write Request (0x12)
        Handle: 0x0037
        Error: Unlikely Error (0x0e)
> HCI Event: Number of Completed Packets (0x13) plen 5                            #3 [hci0] 14.272507
        Num handles: 1
        Handle: 68
        Count: 1

I suppose it may be related to the write response mentioned in #6, as, when I run the example-gatt-server from bluez my test application receives a write response and all is OK.
Also when I change the characteristic to "write-without-response" it works OK - but without write responses...
.gattCharacteristicBegin("string", "00000002-1E3C-FAD4-74E2-97A033F1BFAA", {"read", "write-without-response", "notify"})

Hi @br101, it looks like this can be linked to my (closed) issue #9.
I'm still have the same problem, not fixed yet. So as soon as you find the solution, please, share it.
Thanks.

Yes I've seen your #9 ... my fix for now is to use "write-without response" as mentioned, but that can not be the real solution...


Add network metrics endpoint

https://github.com/iotaledger/iota.go/pull/703

Closed by https://github.com/iotaledger/iota-sdk/pull/2143


Deploy app

Sorry one more time :(

You can contact github support and ask them to remove the fork "attribute" from your repository
or just delete the repo, create a new one, and push all your stuff :)

Thanks :)


Remove unnecessary const return qualifiers

This can actually prevent move semantics from being used (which doesn't matter for trivial types, but it can with std::string, etc). I don't know if this was intentional in design, but I figured I'd make a pull request anyway.

How does const interfere with move semantics?

Didn't notice this until now, but const rvalues cannot bind to non-const rvalues (T&&, which is required in a move assignment/constructor)

Closing PRs out of scope of this project now.


DropOut seems to be broken

Inserting a DropOut layer with a drop probability arbitrarily close to 1 (i.e. 0.999...) does not disturb training. I would expect DropOut to stop the neural net from training at these high values.
Experimenting with the code attached below, I see that the results are hardly different regardless of whether dropout is set to 0.5 or 0.999999 in the settings section. Despite seeding the random number generator, the results are slightly different, implying that something is happening.
(I have tested this with real data containing actual patterns, too)
#!/usr/bin/env python
# -*- coding: utf-8 -*-

import numpy as np
# NOTE: This is the only simple way to get reproducable results in Keras.
np.random.seed(1)

from keras.models import Sequential
from keras.layers.core import Dense, Dropout, Activation
from keras.optimizers import SGD

##############
#  Settings  #
##############

n_features = 10
n_outcomes = 5
n_samples = 5000
fraction_train = 0.7

hidden_layer_size = 8
hidden_activation = 'relu'

dropout = 0.999999
# dropout = 0.5

#########################
#  Make synthetic data  #
#########################

X = np.random.normal(size=[n_samples,n_features])
Y = np.random.randint(2, size=[n_samples,n_outcomes])

X_train = X[n_samples*fraction_train:]
X_test = X[:n_samples*fraction_train]

Y_train = Y[n_samples*fraction_train:]
Y_test = Y[:n_samples*fraction_train]

###############
#  Create NN  #
###############

keras_nn = Sequential()

keras_nn.add(Dense(
    hidden_layer_size,
    input_dim=n_features,
    activation=hidden_activation)
)

keras_nn.add(Dropout(dropout))

keras_nn.add(Dense(
    n_outcomes,
    activation='softmax')
)

optimiser = SGD()

keras_nn.compile(loss='categorical_crossentropy', class_mode='binary', optimizer=optimiser)

##############
#  Train NN  #
##############

history = keras_nn.fit(X_train, Y_train, nb_epoch=1)

keras_proba = keras_nn.predict_proba(X_test, verbose=0)

print keras_proba

My configuration:
Ubuntu 14.04.3 LTS
Python 2.7 with bleeding-edge Keras and Theano. I've also tried recent stable releases.
No GPU use that I know of.

Ugh, no.