SSProve

We'd like to add
https://github.com/SSProve/ssprove
to platform. Is there anything we'd need to do?

Related to:
https://github.com/coq/platform/issues/61

@spitters : the first step would be to discuss with the authors if they plan to long term maintain this project and if they want it to be included in the Coq Platform in agreement with the charter. It would help if you could initiate and conduct this discussion here. It definitely looks like a very interesting development, but with only two journal publication related tags it is unclear to me what the long term prospect is.
Also I couldn't find an opam package, which makes dependency analysis and initial tests difficult.

Yes, we plan to maintain it for the long term.
@haselwarter , @TheoWinterhalter and myself will be likely maintainers.
Will create an opam package.

Ah I didn't realize you are one of the authors.

@spitters : did you create the opam package as discussed? I somehow still can't find it. If the opam package is there by Wednesday I can still consider it for the 2022.03 release, otherwise I need t postpone it.

@MSoegtropIMC we have an opam file at https://github.com/SSProve/ssprove/blob/main/ssprove.opam , is that what you had in mind?

@haselwarter No, the opam file should be submitted to the opam-coq-archive (for specific releases).

@haselwarter : a description field in opam would be nice - we generate the readme from it. It can have a few lines (some have a few 10 lines). Please note that you can unfold the package sections by clicking on the tiangles.

@spitters @haselwarter : I would need the tag and the published opam package by tomorrow evening for inclusion in Coq Platform 2022.03.

@spitters @haselwarter : I wanted to ask what the status of the opam packages is. I can delay the release a few days, say until Tuesday next week (that is packages are there on Monday) if you say a few days would help.

It's probably better to not rush things and maybe aim for a later release of the platform. So no need for you to wait for us. Thanks.

Thanks! If you need any help preparing this, please let me know.
FYI: the next official release will be in about 5..6 months, 4..8 weeks after the 8.16.0 release (see https://coq.discourse.group/t/coq-8-16-release-schedule/1598). There will be an 8.16 preview releases short after the 8.16.0 release - that is July or early August) where I would also include it.

@TheoWinterhalter : I started to prepare the next release (2022.09). The first preview will happen soon.
As far as I can tell there is still no opam package in the Coq Opam repo.
It should be there latest in 4 weeks.

Sorry for this, we have been busy with other things so I don't think we will be ready either for the next release.
Thanks for checking with us!

Are there issues besides the opam package?

Nothing comes to mind, but we are going to update our dependencies soon so we probably should wait for this.
I hope this doesn't create too much workload overhead for you to wait on us like this.

Fine with me. For the 2022.09 release there is still some time - mid of August would be good but I can also live with end of August. Beyond that it starts to produce substantial extra work, so I might postpone it then.

Since there was no progress and the 2022.09 beta is due I delayed this to 2023.03.
@TheoWinterhalter : if you have something by tomorrow, I might reconsider.

Hi, I think this issue is adding unnecessary workload for you, it might be best to close it and reopen it when we are ready to propose something. Unless @spitters or @haselwarter disagree?

Let's leave it open then, at least until we evaluate how to merge our work
on Jasmin back into main, upstream compatibility permitting.
On Wed, 14 Sept 2022 at 09:34, MSoegtropIMC @.***>
wrote:

I am fine to leave it open to not forget it - the traffic will be about
2...3 pings per release of Coq Platform (6 months).
—
Reply to this email directly, view it on GitHub
https://github.com/coq/platform/issues/177#issuecomment-1246363683, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGO4GROXX3MZ55RFRVTAS3V6F5ZBANCNFSM5IGZDYHA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Allow use of gpt-4-32k model

Currently, specifying that in model doesn't work.  Allow this option to be used in conjunction with max tokens to be set to 32,768.

You could try going and editing the plugin's own code to remove the places where the max_tokens parameter is. This parameter is no longer mandatory - if you don't need to limit the AI, I think not using max_tokens will solve this problem.


Frontend: Use static assets instead of fetching json from github

[!NOTE]
We are meticulous when it comes to merging code into the main branch, so please understand that we may reject pull requests that do not meet the project's standards. It's never personal. Also, game-related scripts have a lower chance of being merged.

Description

Adds json files as static assets to frontend by creating a symbolic link /json -> /frontend/public/json
Reads json files from static assets instead of fetching them from github
Update sort_order in metadata.json and use it instead of overriding in frontend
Ran linting which also changed some unrelated files

Tested that the website works on my fork github pages
Some benefits:

(very) Small performance increase
Better for development since frontend will use local json files
Fixes github rate limit exceeded error

Fixes https://github.com/community-scripts/ProxmoxVE/issues/155
Type of change
Please check the relevant option(s):

[x] Bug fix (non-breaking change that resolves an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (a fix or feature that would cause existing functionality to change unexpectedly)
[ ] New script (a fully functional and thoroughly tested script or set of scripts.)

Prerequisites
The following efforts must be made for the PR to be considered. Please check when completed:

[x] Self-review performed (I have reviewed my code, ensuring it follows established patterns and conventions)
[x] Testing performed (I have tested my changes, ensuring everything works as expected)
[x] Documentation updated (I have updated any relevant documentation)

Additional Information (optional)
Provide any additional context or screenshots about the feature or fix here.
Related Pull Requests / Discussions
If there are other pull requests or discussions related to this change, please link them here:

Related PR #

LGTM, but @BramSuurdje is the pro for this 😅

LGTM

Ah, I was running into this issue and I couldn't understand why I was making too many request to github.io. Thanks for resolving.


Parses CHANGES.txt to identify contributors

This script can be used to list contributors as indicated in CHANGES.txt so that we can easily thank them in our release notes.
I tested it on 9.6 and I'm happy with the results!  Added them to: https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote9_6_0
Ideally we incorporate this into the Release Wizard.

Unlike a Git log, CHANGES.txt has cleaner data and can be edited if we see a formatting or spelling glitch.  For better or worse (?), it doesn't have more trivial changes that were not worthy of CHANGES.txt.

If you make an effort to get it into wizard, I can try help if you get stuck..


New Feature

Implementing Memory Game

wrong branch , please re-working and change branch: mini-apps


Show gaps in graphs on expression browser.

Addresses #345
@Conorbro
Console templates also need changing.

I've extended this to cover console templates, and made it more resilient.


File Scope Attribute documentation makes reference to non-existent scope

Spotted while browsing here: https://open-cmsis-pack.github.io/Open-CMSIS-Pack-Spec/main/html/pdsc_components_pg.html#FileScopeAttributeType
"Applies only to file elements of category include and category header; ignored otherwise. A private include path is added to the command line for building any module of the component for the specified language. A hidden header file is indicating an internal header file which must not be explicitly included by modules outside of the scope of the component."
I can't find this "hidden" scope anywhere in the schema (though I would actually like to use it). Was this removed or is this intended to be added at a later time?
https://github.com/Open-CMSIS-Pack/Open-CMSIS-Pack-Spec/blob/a6d49e51f619dacc89a3763e44e3105561b75169/doxygen/src/components_schema.txt#L1100-L1101

Good catch. Thanks for raising this. This was overlooked when we aligned the naming for header and include paths to private and public.

Thanks for getting back to me so quickly @jkrech. So private has the same effect as hidden then in that it's a component internal header file that isn't exposed to the compiler's include path?

Yes. In addition private header files must not be suggested by tools for addition to a module. Background: there is IDEs suggesting the user to add "#include ..." statement to files in the editor. E.g. if you have selected the CMSIS RTOS2 component the IDE will then suggest to add the header for the RTOS2 component #include "cmsis_os2.h" This must not be done for header files that have the attribute "private" set.


s3 backend: copy for large files

The s3 backend's Copy() should work for files larger than 5gb.

implemented as part of #83.


[API] Add updateLoss method

This patch newly adds updateLoss method into FullyConnectedLayer class
to remove redundant code.
Signed-off-by: Sangjung Woo<EMAIL_ADDRESS>Self evaluation:

Build test:	 [X]Passed [ ]Failed [ ]Skipped
Run test:	 [X]Passed [ ]Failed [ ]Skipped

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #93. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ec2-54-180-96-14.ap-northeast-2.compute.amazonaws.com/.

@jijoongmoon
Question. There is no weight decay code in COST_MSR case of FullyConnectedLayer::forwarding() method. Is your intention or just omitted?

@jijoongmoon
Question. There is no weight decay code in COST_MSR case of FullyConnectedLayer::forwarding() method. Is your intention or just omitted?

Oh. this should be added. Could you include the code?

@jijoongmoon I have already done it. Thanks.


Feature/ipv6 test

Issue #, if available:
Description of changes:
Running IPv6 with Calico requires a Ubuntu 22.04

/approve
/lgtm

/approve


How to change the language, the current language obtained by device language?

Currently I can change the language but only with ios and datetime mode. How do I change the language of both ios and android?please help me!Thank

Hi!
Please see #162


Building and using the AS node with Autoware

Status
PRODUCTION / DEVELOPMENT
Description
Readme file to use the AS node with Autoware.

@francisvac
Thank you for your support!


Inversion of Array (Using Merge Sort)

💥 Proposal
Greetings sir/Mam,
I would like to contribute the code for this issue in C++/CPP.
The code is ready. I have added the code , along with proper explanation of the algorithm , test cases , time complexity and space complexity of the same, as per the guidelines.
Kindly assign it to me.
This is regarding GSSOC'21.
Regards,
Hitain Kakkar

/assign


ISPN-6629 Enable Netty Epoll support by default in the Hot Rod server

https://issues.jboss.org/browse/ISPN-6629

Pushed to master, thanks


HiDPI text editor: wrong span positions?

Code:
"Set up"
AeFontManager resetGlobalInstance.
AeDownloadedFont ensureAllDownloadedAt: AeFilesystemResources downloadedFontsDirectory.
AeFontManager globalInstance
	scanDirectory: AeFilesystemResources fontsDirectory;
	scanDefaultDirectories.

"Doesn't work! symbols should be replaced"
text := 'a := A->B->>C <= c|=>d~~>e.' asRopedText
	fontName: 'Cascadia Code'; fontSize: 30;
	yourself.
text onAlbum openInOblSpace.

Steps to reproduce in a MacBook (maybe in any HiDPI screen):

Select "SDL2 Alexandrie" Bloc host in System settings
Evaluate the code above

When the host is "Morphic Alexandrie", it looks nice.

strange that it works fine with Morphia-Alexandrie...
I've noticed the the measured advance seems wrong for some letters as C, c, a ... (ok for A)

I wanted to test it on Windows but Alexandrie don't load on windows.

Probably there was an error on the postLoad action of the
BaselineOfAlexandrie, because it logs in the terminal the version of
Harfbuzz, among others, and it doesn't find it.
I plan to try it on windows and linux today. For the moment we can get the
harfbuzz DLL the same as Esteban's gtk bindings, from this zip:
http://files.pharo.org/vm/pharo-spur64-headless/win/latest-win64-GTK.zip
Martín
On Sun, Oct 16, 2022 at 1:07 PM Alain Plantec @.***>
wrote:

I wanted to test it on Windows but Alexandrie don't load on windows.
—
Reply to this email directly, view it on GitHub
https://github.com/plantec/Album/issues/25#issuecomment-1279999287, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXHHKK4HM355SHPTYAHXBTWDQR4ZANCNFSM6AAAAAAREHPF3U
.
You are receiving this because you authored the thread.Message ID:
@.***>

On Mon, Oct 17, 2022 at 10:45 AM Martin Dias @.***> wrote:

Probably there was an error on the postLoad action of the
BaselineOfAlexandrie, because it logs in the terminal the version of
Harfbuzz, among others, and it doesn't find it.
I plan to try it on windows and linux today. For the moment we can get the
harfbuzz DLL the same as Esteban's gtk bindings, from this zip:
http://files.pharo.org/vm/pharo-spur64-headless/win/latest-win64-GTK.zip
I tried and failed to add harfbuzz DLL on my windows 10.
But it is disabled by default, so I only removed what was raising the
error: a log in the BaselineOfAlexandrie.
Maybe it now works on Windows. I'll try tomorrow.

Cheers,
Martín

Martín
On Sun, Oct 16, 2022 at 1:07 PM Alain Plantec @.***>
wrote:

I wanted to test it on Windows but Alexandrie don't load on windows.
—
Reply to this email directly, view it on GitHub
https://github.com/plantec/Album/issues/25#issuecomment-1279999287, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXHHKK4HM355SHPTYAHXBTWDQR4ZANCNFSM6AAAAAAREHPF3U
.
You are receiving this because you authored the thread.Message ID:
@.***>

On Tue, Oct 18, 2022 at 12:09 AM Martin Dias @.***> wrote:

On Mon, Oct 17, 2022 at 10:45 AM Martin Dias @.***> wrote:

Probably there was an error on the postLoad action of the
BaselineOfAlexandrie, because it logs in the terminal the version of
Harfbuzz, among others, and it doesn't find it.
I plan to try it on windows and linux today. For the moment we can get
the harfbuzz DLL the same as Esteban's gtk bindings, from this zip:
http://files.pharo.org/vm/pharo-spur64-headless/win/latest-win64-GTK.zip
I tried and failed to add harfbuzz DLL on my windows 10.
But it is disabled by default, so I only removed what was raising the
error: a log in the BaselineOfAlexandrie.
Maybe it now works on Windows. I'll try tomorrow.

It works when installing a recent harfbuzz + dependencies.
Unzip this into the pharo-vm directory (replacing some dlls) made it work:
https://github.com/harfbuzz/harfbuzz/releases/download/5.2.0/harfbuzz-win64-5.2.0.zip

Cheers,
Martín

Martín
On Sun, Oct 16, 2022 at 1:07 PM Alain Plantec @.***>
wrote:

I wanted to test it on Windows but Alexandrie don't load on windows.
—
Reply to this email directly, view it on GitHub
https://github.com/plantec/Album/issues/25#issuecomment-1279999287,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXHHKK4HM355SHPTYAHXBTWDQR4ZANCNFSM6AAAAAAREHPF3U
.
You are receiving this because you authored the thread.Message ID:
@.***>

On Wed, Oct 19, 2022 at 5:07 AM Martin Dias @.***> wrote:

On Tue, Oct 18, 2022 at 12:09 AM Martin Dias @.***> wrote:

On Mon, Oct 17, 2022 at 10:45 AM Martin Dias @.***>
wrote:

Probably there was an error on the postLoad action of the
BaselineOfAlexandrie, because it logs in the terminal the version of
Harfbuzz, among others, and it doesn't find it.
I plan to try it on windows and linux today. For the moment we can get
the harfbuzz DLL the same as Esteban's gtk bindings, from this zip:
http://files.pharo.org/vm/pharo-spur64-headless/win/latest-win64-GTK.zip
I tried and failed to add harfbuzz DLL on my windows 10.
But it is disabled by default, so I only removed what was raising the
error: a log in the BaselineOfAlexandrie.
Maybe it now works on Windows. I'll try tomorrow.

It works when installing a recent harfbuzz + dependencies.
Unzip this into the pharo-vm directory (replacing some dlls) made it work:
https://github.com/harfbuzz/harfbuzz/releases/download/5.2.0/harfbuzz-win64-5.2.0.zip

Bah, the dlls can be located on the same directory as the image, too.

Cheers,
Martín

Martín
On Sun, Oct 16, 2022 at 1:07 PM Alain Plantec @.***>
wrote:

I wanted to test it on Windows but Alexandrie don't load on windows.
—
Reply to this email directly, view it on GitHub
https://github.com/plantec/Album/issues/25#issuecomment-1279999287,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXHHKK4HM355SHPTYAHXBTWDQR4ZANCNFSM6AAAAAAREHPF3U
.
You are receiving this because you authored the thread.Message ID:
@.***>

This is fixed, I guess.

This is too old


Missing -generate-genesis-proof flag throws an ugly error

Crash_log
{"OS_type":"Unix","Release":"5.4.0-1037-gcp","Machine":"x86_64","Sys_name":"Linux","Exception":{"commit_id":"fd3980820fb82c7355af49462ffefe6718800b77","sexp":["monitor.ml.Error","No genesis proof file was found and not allowed to generate a new genesis proof",["Raised at file "src/error.ml" (inlined), line 9, characters 14-30","Called from file "src/app/cli/src/mina.ml", line 653, characters 12-27","Called from file "src/deferred1.ml", line 17, characters 40-45","Called from file "src/job_queue.ml" (inlined), line 131, characters 2-5","Called from file "src/job_queue.ml", line 171, characters 6-47","Caught by monitor coda"]],"backtrace":["Raised at file "src/error.ml" (inlined), line 9, characters 14-30","Called from file "src/app/cli/src/mina.ml", line 653, characters 12-27","Called from file "src/deferred1.ml", line 17, characters 40-45","Called from file "src/job_queue.ml" (inlined), line 131, characters 2-5","Called from file "src/job_queue.ml", line 171, characters 6-47"]},"Command":"Command: (mina daemon)","Coda_branch":"master","Coda_commit":"fd3980820fb82c7355af49462ffefe6718800b77"}
~

@Julian-dev28 looks like you haven't passed the --generate-genesis-proof true flag, can you try again using that?

Hello mrmr1993
Thank you for the solution and sorry for the late reply. The CLI is throwing the error: -generate-genesis-proof: command not found

Closing this issue as it is stale for a long time.


Requested Feature - Automated app screenshots

Automated app screenshots
It would be awesome if we could build a mechanism to automate collecting screenshots for various devices.
I came across this lib and it looks promising: https://github.com/gre/react-native-view-shot
I'm thinking that we would need some way of triggering events inside the app, so likely will need to use deep-linking.
Also, some kind of scripting mechanism like cypress or mocha might work.
If we expose the navigation object to the calling script, it can go where it needs to in the app, and then call captureScreen.
So Airfoil would first boot up the app on the specified device sizes, and then run the collect-screenshots script, then boot up the next device, etc.

Some more possibly helpful links (thanks @makozlo ):
https://lickability.com/blog/automating-app-store-screenshots-with-fastlane-and-swiftui/


Possible to use ffmpegs advanced-options?

Hi,
I would like to use advanced options like -copyts (See: https://ffmpeg.org/ffmpeg.html#Advanced-options). Looks like this is not possible at all.
I tried it this way but this seems to be wrong just from looking at it :D :
(
    ffmpeg
    .input(input, ss=timestamp, "copyts")
    .filter_('subtitles', subtitle)
    .output(output, vframes=1)
    .overwrite_output()
    .run()
)

or "-re", something important for real-time streaming! :-(

@Johndirr I haven't tried -copyts but it might be possible that you can use it adding copyts=None as an argument.
@briveira I am using -re succesfully the same way, i.e:
ffmpeg.input('file.mp4', re=None)


Too grey

Describe the issue
The new color scheme for the Datatracker header is dark, so there is not enough contrast between the new background and the text. Please lighten it greatly.

Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

This should be already fixed by #6166

As of right now, it is not, and I get the same screen shot as above. The page I'm on reports "Version 11.8.0 (release - b3a057d)"

You can preview the next release at dt-main.dev.ietf.org.

The pink is better, but why have any background at all? Any background color makes the text harder to read for someone. And, yes, I'm a bit bah-humbug-y about design changes...

I appreciate the color change, but I am now reopening this because now the "Report a bug" text is unreadable:


GitBook Access

@icebob or @lionel-bijaoui do either of you have access to the GitBooks account?
I'd like to start looking into cleaning up the documentation hosted there as it's pretty far behind at the moment.
I've setup a new GitBooks organization called "vue-generators" and was planning to migrate all of the existing documentation over to that, and making the documentation public via a GitHub repo (ie; vue-generators/vfg-docs) so it can be updated by the community more easily, as well as made available offline.

What is your gitbook username?

Same as GitHub, should be zoul0813 (signed up with GitHub SSO)

Btw, the book is on https://legacy.gitbook.com

higginsd at zoulcreations dot com is the email

Done.

thanks


new packages strategy breaks plugin

Search Terms
legacy-packages
legacypackages
Problem
I have a plugin that considers a multi-package project as a whole, basically.  It expects a couple specific packages to exist, and creates new reflections in other packages based on the reflections found in those required packages.  The new packages mode seems to run in isolation, so my plugin cannot make the connections.
I'm also receiving warnings about use of typedoc.entryPoint in package.json when run w/ legacy-packages, which mention it will be ignored--but I'm not aware of any alternative.  Because of this, TypeDoc complains that it cannot find entry points.  I would rather not require my users to know the specific entry point of the required package(s).
Suggested Solution
Do not eliminate legacy-packages and/or support typedoc.entryPoint and/or suggest a workaround.

Yes, the whole point of 0.24's packages mode is to run in isolation and then merge the project together when done, see #2197 for details on that.
Your plugin should probably be listening to Application.EVENT_PROJECT_REVIVE. When that fires, it will be passed a ProjectReflection which contains everything.
In packages mode, TypeDoc effectively makes a completely separate run in each child package, so each of those packages should configure their entryPoints option as if docs were to be built for only that package. Gerrit0/typedoc-packages-example has a setup using this.

I'm also receiving warnings about use of typedoc.entryPoint in package.json when run w/ legacy-packages

That shouldn't happen... a minimal repro would be great.

Thanks, I'll give this a try tomorrow and get that MCVE if it's still a problem.


Audio finished not firing

A few changes that were required to get the audio player to fire the finished playing event.

This was published to npm as 0.3.1. Thanks!


Eww gets stuck when :onclick runs a command that closes an eww window. On hypland 0.34.0 [BUG]

Checklist before submitting an issue

[X] I have searched through the existing closed and open issues for eww and made sure this is not a duplicate
[X] I have specifically verified that this bug is not a common user error
[X] I am providing as much relevant information as I am able to in this bug report (Minimal config to reproduce the issue for example, if applicable)

Description of the bug
I don't know why this is happening. I have been programming in eww for past month and all of a sudden I'm having this issue.
 The issue
I have made a bash script that keeps gets called to open other eww windows. when this script gets called it closes all other open secondary eww windows. and then opens the desired eww window.
The scripts does more in my config but I have simplified it here.
 The bug
When a button gets pressed which closes an eww window. eww will get stuck on that button. You will only be able to interact with that button. If you click on any other eww instance it will click on the initial button.
I have only noticed this when eww successfully closes a window from a button press.
 My environment
I am on arch linux, Wayland. With the hyprland compositor.
I have only noticed this issue on the day of writing this bug report. After I Updated all of arch's packages. (was 1 week behind)
I have completely reinstalled eww and it hasn't changed. I have tested minimal setups and it hasn't changed.
I do not have access to another similar system so I couldn't test this.
Reproducing the issue
A button that closes an open eww window. Better visualised with hover effects.
The below configuration demonstrates it in multiple ways
eww.yuck:
(defwindow bartop
  :monitor 0
  :geometry (geometry :x "0%"
                      :y "0px"
                      :width "100%"
                      :height "30px"
                      :anchor "top center")
  :stacking "fg"
  :exclusive true
  :wm-ignore false
  (bar)
  )

(defwidget bar []
  (box :style "background-color: gray;" :space-evenly false
       (button :onclick "./windowManager close"
               "close all")
       (button :onclick "./windowManager open blue"
               "open blue")
       (button :onclick "./windowManager open red"
               "open red")
       (button :onclick "./windowManager open yellow"
               "open yellow")
       (button :onclick "eww close yellow"
               "close yellow")
       )
  )

(defwidget other [?color ?text]
  (box :style "background-color: ${color};"
       "${text}"
       ))

(defwindow blue
  :monitor 0
  :geometry (geometry :x "0"
                      :y "0px"
                      :width "100px"
                      :height "100px"
                      :anchor "top left")
  :stacking "overlay"
  :exclusive false
  :wm-ignore false
  (other :color "blue" :text "blue Window")
  )
(defwindow red
  :monitor 0
  :geometry (geometry :x "100px"
                      :y "0px"
                      :width "100px"
                      :height "100px"
                      :anchor "top left")
  :stacking "overlay"
  :exclusive false
  :wm-ignore false
  (other :color "red" :text "red Window")
  )
(defwindow yellow
  :monitor 0
  :geometry (geometry :x "200px"
                      :y "0px"
                      :width "100px"
                      :height "100px"
                      :anchor "top left")
  :stacking "overlay"
  :exclusive false
  :wm-ignore false
  (other :color "yellow" :text "yellow Window")
  )

eww.scss:

button {
    border: solid 2px black;
    background-color: white;
    color: black;
}
button:hover {
    background-color: black;
    color: white;
}

windowManager bash script:
#! /usr/bin/bash

commandIn="$1"
inputIn="$2"

closeWindow () {
    # closes everything except "bartop"
    eww close $(eww windows | grep "*" | tr -d "*" | grep -iv bartop | tr "\n" " ") > "/dev/null" 2> "/dev/null"
    echo "" > "$openWindowPath"
}

openWindow () {
    #closeWindow #This is removed to better visualise it in the config. normally it would always close all windows
    eww open "$1" > "/dev/null" 2> "/dev/null"
}

#check mode
if test "$commandIn" == "close"; then
    closeWindow
elif test "$commandIn" == "open"; then
    openWindow "$inputIn"
fi

Expected behaviour
What I would expect to happen is it to close the eww window and not get stuck on the button. I didn't used to do this until recenly breaking my configuration.
Additional context
Displays the issue on the config provided.
https://github.com/elkowar/eww/assets/51342815/3c6514ed-d7a7-463a-972e-30a6d7fd53ab
When I pressed the "close yellow button" eww was somehow locked on this button. pressing anything on eww would trigger the same button again. In order to be freed from this state I have to click on an eww element and the onclick effect must not close a window or it will lock me in the same button again.
As you have seen the close all button sometimes locks me in and other times works successfully. I am not sure for what causes this.

I have discovered that this issue only appears when I have a window open on the screen. So it may be a problem with hyprland or wayland. Since this issue started after upgrading. I will be checking the changes for them.

I have downgraded to just before the latest hyprland release (0.33.1), and am not running into the same issue. everything is working as expected. I am confident the problem appears on hyprland release 0.34.0

I have upgraded only hyprland to 0.34.0 and I am getting the same issue again. I dont know what my best course of actions should be at this point.

I am having this issue too, maybe you should submit a issue in Hyprland repo.

having the same issue here, downgrading hyprland fixes it

I am having this issue too, maybe you should submit a issue in Hyprland repo.

I'm not sure if this would qualify as an issue due to a bug in hyprland. I feel like its more of a bug in eww due to changes in hyprland.

I am having this issue too.
Hyprland 0.34.0
eww 0.4.0 65d622c81f2e753f462d23121fa1939b0a84a3e0

I can confirm this is a working solution.
Waiting for 0.1 seconds between closing and opening a window fixes the issue.
I will keep this issue open but this will do for now.

Just to add to this. After playing around with this a bit it looks to me eww somehow "refreshes" when a window is closes. The button then loses focus and never registers the mouse was released. Even with the workaround of having 0.1s sleep in the scripts, if I don't release the mouse during the 0.1s timeframe, the button remains stuck.

This seems to be have the same causes as #1022, please see my comment there to have potential workarounds


[Bug]: ng add @o3r/design does not work

Package name
design
Package version
10.2.1
Reproduction steps
npm create @o3r my-workspace
cd my-workspace
ng g app webapp
ng add @o3r/design --project-name webapp

Current result
In angular.json

"useOtterDesignToken": true, is added for all projects. Shouldn't it be only for webapp?
generate-css builder is not added
Also, no template files are added to the project (design-token.custom.json and theme.scss)

Expected result
In angular.json

"useOtterDesignToken": true, is added only for webapp?
generate-css builder is added for webapp
Template files are added to the project (design-token.custom.json and theme.scss)

Additional comments
No response

Integration tests should be enhanced to verify everything works well for the ng add


Add Vue School top banner

This PR updates uncomments and updates the script of the Vue School top banner.
Feel free to check the deploy preview to see the banner in action.
For more information, please visit: https://vueschool.io/affiliates/banner

Thank you. BTW, I noticed this:

Thanks for the heads up @posva, changing

Ready @posva, now all images are using https (check the code here https://vueschool.io/banner.js?affiliate=vuerouter&type=top). Thanks!


New version: schollz.croc version 10.04

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

Queued — Contributor License Agreement is not agreed yet.

I made a discussion for this, because I do not understand the Contributor License Agreement: https://github.com/microsoft/winget-pkgs/discussions/155182

Queued — Contributor License Agreement is not agreed yet.

I made a discussion for this, because I do not understand the Contributor License Agreement: #155182

Please let us know (@ me) when you're happy for this PR to be merged. Feel free to mark it as draft, to better communicate that it's queued.

@microsoft-github-policy-service agree

@stephengillie thanks, I'm ready to move forward. Thanks for your help.


Feature Request: Allow to define default value

Would it be possible to write a template file like this?
something = {{ Env.FOO, "bar" }}

which will populate the placeholder with bar if the env variable FOO does not exist

works, thank you!


itunes tagged vs untagged import

Take an MKV >4 gigabytes.  Use manual.py to auto convert, tag and move it to the auto-add iTunes directory, and iTunes will refuse to import it.  Quicktime will choke on it with an error -2041: an invalid sample description was found in the movie filename goes here.
  Winds up in 'home movies' of course.  Then proceed to either a) use manual.py to tag and move the MP4 file, and iTunes resucks it in just fine, or b) use manual.py -nm to tag in in place, then in iTunes right-click and get info, and iTunes repopulates and moves it to the appropriate movies/tv shows/whatever just fine.

same here. tried an 1080p mkv file with subtitle using manual.py resulting file seems fine but itunes wont import.

Yeah at this point it seems iTunes doesn't like to import certain files with embedded subtitles. Not sure exactly what it doesn't like about the subs though


hevc_qsv encoder into ffmpeg, controlling options

Hi, I managed to build ffmpeg with MediaSDK support on my LMDE4 distro (it is Debian based) and when I ask for encoder options (in this case hevc_qsv) I get:
topolinik@debbieb1:~$ ~/ffmpeg -h encoder=hevc_qsv
ffmpeg version n4.2.2-6-gd1e8be3411 Copyright (c) 2000-2019 the FFmpeg developers
  built with gcc 8 (Debian 8.3.0-6)
  configuration: --prefix=/home/topolinik/svn/mpv-build/build_libs --enable-static --disable-shared --enable-gpl --disable-debug --disable-doc --enable-pic --enable-pic --disable-debug --enable-postproc --enable-gpl --enable-libdrm --enable-libtheora --enable-libxvid --enable-libx264 --enable-libvpx --enable-libmfx --extra-cflags=-I/opt/intel/mediasdk/include/ --extra-cxxflags=-I/opt/intel/mediasdk/include/ --extra-ldflags=-L/opt/intel/mediasdk/lib/ --enable-nonfree --enable-openssl
  libavutil      56. 31.100 / 56. 31.100
  libavcodec     58. 54.100 / 58. 54.100
  libavformat    58. 29.100 / 58. 29.100
  libavdevice    58.  8.100 / 58.  8.100
  libavfilter     7. 57.100 /  7. 57.100
  libswscale      5.  5.100 /  5.  5.100
  libswresample   3.  5.100 /  3.  5.100
  libpostproc    55.  5.100 / 55.  5.100
Encoder hevc_qsv [HEVC (Intel Quick Sync Video acceleration)]:
    General capabilities: delay hybrid
    Threading capabilities: none
    Supported pixel formats: nv12 p010le qsv
hevc_qsv encoder AVOptions:
  -async_depth       <int>        E..V..... Maximum processing parallelism (from 1 to INT_MAX) (default 4)
  -avbr_accuracy     <int>        E..V..... Accuracy of the AVBR ratecontrol (from 0 to INT_MAX) (default 0)
  -avbr_convergence  <int>        E..V..... Convergence of the AVBR ratecontrol (from 0 to INT_MAX) (default 0)
  -preset            <int>        E..V..... (from 1 to 7) (default medium)
     veryfast                     E..V.....
     faster                       E..V.....
     fast                         E..V.....
     medium                       E..V.....
     slow                         E..V.....
     slower                       E..V.....
     veryslow                     E..V.....
  -rdo               <int>        E..V..... Enable rate distortion optimization (from -1 to 1) (default -1)
  -max_frame_size    <int>        E..V..... Maximum encoded frame size in bytes (from -1 to 65535) (default -1)
  -max_slice_size    <int>        E..V..... Maximum encoded slice size in bytes (from -1 to 65535) (default -1)
  -bitrate_limit     <int>        E..V..... Toggle bitrate limitations (from -1 to 1) (default -1)
  -mbbrc             <int>        E..V..... MB level bitrate control (from -1 to 1) (default -1)
  -extbrc            <int>        E..V..... Extended bitrate control (from -1 to 1) (default -1)
  -adaptive_i        <int>        E..V..... Adaptive I-frame placement (from -1 to 1) (default -1)
  -adaptive_b        <int>        E..V..... Adaptive B-frame placement (from -1 to 1) (default -1)
  -b_strategy        <int>        E..V..... Strategy to choose between I/P/B-frames (from -1 to 1) (default -1)
  -forced_idr        <boolean>    E..V..... Forcing I frames as IDR frames (default false)
  -low_power         <boolean>    E..V..... enable low power mode(experimental: many limitations by mfx version, BRC modes, etc.) (default false)
  -idr_interval      <int>        E..V..... Distance (in I-frames) between IDR frames (from -1 to INT_MAX) (default 0)
     begin_only                   E..V..... Output an IDR-frame only at the beginning of the stream
  -load_plugin       <int>        E..V..... A user plugin to load in an internal session (from 0 to 2) (default hevc_hw)
     none                         E..V.....
     hevc_sw                      E..V.....
     hevc_hw                      E..V.....
  -load_plugins      <string>     E..V..... A :-separate list of hexadecimal plugin UIDs to load in an internal session (default "")
  -profile           <int>        E..V..... (from 0 to INT_MAX) (default unknown)
     unknown                      E..V.....
     main                         E..V.....
     main10                       E..V.....
     mainsp                       E..V.....
  -gpb               <boolean>    E..V..... 1: GPB (generalized P/B frame); 0: regular P frame (default true)

Where can I get more details about them?
What I would like is more knowledge of what they do and how I can tune in order to get my personal balance for encoding time, visual quality and final file size but I need to understand them better.
Sorry if this is not the right place to ask for this.

Hi @eblanca ,
Detailed reply to your question requires a separate wiki page. Actually we've already considered such page but didn't start writing it.
Right here, I can give you only some hints. I hope it will be enough. If not, please tell what exact option(s) you're interested in.
First of all, all parameters above are from MediaSDK API. You can find their description in the manual.
Let me describe just few (most important):

-low_power - it enables a special type of HW encoders which use only fixed functions HW blocks (programmable hw execution units are not involved).  Can influence both performance and quality.
-preset - it's for performance vs quality balancing. Pretty straightforward.
-b_strategy - B frames gives higher quality but lower performance.
-async_depth - it influences performance, async_depth!=1 gives higher performance but means internal buffering (might be bad for low latency cases).

Hello Dmitry, thanks for your hints.
While as a user I appreciate the idea of the wiki page, as a programmer I love that manual!
I am currently digging into ffmpeg source code and that manual has a lot of answers, great!
Gosh, I should have found it weeks ago!
I already had a brief view of the entire manual and some questions arose:

what's the difference in use case for the function classes MFXVideoENCODE and MFXVideoENC? (ffmpeg uses MFXVideoENCODE only)

in ffmpeg implementation, a call to MFXVideoENCODE_Init is issued passing the whole block of the user specified options, then before encoding starts, a call to MFXVideoENCODE_GetVideoParam passing an identical data block but empty. This is because this function returns the actual encoding parameter set due to the particular hardware/software (CPU/MSDK) configuration, is my understanding right?

the manual doesn't clarify this, but are any options usable only with particular codecs? For example, I see ffmpeg implementation provides lookahead options (lookahead, lookahead_depth and lookaheadDS) only for h264_qsv encoding engine, is this right (after reading the manual, I think it isn't) ?

Thank you.

Hello @eblanca ,

what's the difference in use case for the function classes MFXVideoENCODE and MFXVideoENC? (ffmpeg uses MFXVideoENCODE only)

Most likely you don't need MFXVideoENC . MFXVideoENC is a special interface for encoder users who needs low level access to tune encoders quality. I'd advise to look at https://github.com/Intel-Media-SDK/MediaSDK/blob/master/doc/mediasdkfei-man.md. It's a FEI manual. FEI implements ENC/PAK interfaces.  This document explains idea of ENC and PAK (especially https://github.com/Intel-Media-SDK/MediaSDK/blob/master/doc/mediasdkfei-man.md#usage-models).

This is because this function returns the actual encoding parameter set due to the particular hardware/software (CPU/MSDK) configuration, is my understanding right?

Exactly. Encoder implementation can internally initialize with slightly modified (e.g in case of some incompatibilities) version of mfxVideoParams passed at Init from application. So a user can check actual parameters by GetVideoParam.

the manual doesn't clarify this, but are any options usable only with particular codecs?

Yes. The manual is written in a lawyered language to some extend to be abstract from specific HW versions and a type of codec.
Generally Query() API interface is provided to say if some API option is supported or not.

For example, I see ffmpeg implementation provides lookahead options (lookahead, lookahead_depth and lookaheadDS) only for h264_qsv encoding engine, is this right (after reading the manual, I think it isn't)

In a nutshell, currently - yes, ffmpeg supports LookAhead only for AVC.
From MediaSDK perspective Lookahead can be also implemented for HEVC as well. We've recently proved it by https://github.com/Intel-Media-SDK/MediaSDK/pull/2034. Now the ball on ffmpeg side to enable such support for HEVC.
Regards,
Dmitry


Problem with dangling veth

On a k8s cluster, when the k8s-api-server container moves from one host to another, it leaves behind a dangling veth on the host. Due to this, any container running on the host where the past k8s-api-server container was running will have problems connecting with the api server.
To confirm the issue, install "arping" and run arping kubernetes.kubernetes.rancher.internal to see the duplicate ARP replies.
CC: @aemneina @wlan0 @ibuildthecloud

Fixed in Network Services v0.2.2, network-manager:v0.7.3.

Tested with rancher-server version - v1.6.3-rc1 using Network Services v0.2.2, network-manager:v0.7.3.
Set up - rancher-server with 3 Rhel 7.3 hosts.
Deploy "pinger" from https://github.com/leodotcloud/pinger-catalog-item.git catalog.
Deploy "dokuwiki" stack from community catalog. This service has a sidekick  with start_once set to true.
Deploy "janitor"  stack from community catalog. This would result in cleaning up the sidekick instance of "dokuwiki-server " that is in stopped state, resulting in service reconcile kicking in and resulting in new instance of "dokuwiki-server " and its sidekick being created in new host.
After keeping this setup around for over night , there was no dangling veth on the hosts.
There were few instances when the Network manager was able to detect dangling veths and clean them up.
time="2017-06-21T23:35:51Z" level=debug msg="vethsync/utils: checking for dangling veths"
time="2017-06-21T23:35:51Z" level=debug msg="vethsync/utils: dangling veth found: &{{20 1500 0 vethr8e6cecd3f0 c2:03:d0:5e:4f:4b up|broadcast|multicast 69699 3 4 <nil>  0xc4202420e0 0 <nil> ether} }"
time="2017-06-21T23:35:51Z" level=debug msg="vethsync: dangling: map[20:0xc4202a8ec0]"
time="2017-06-21T23:35:51Z" level=debug msg="vethsync/utils: cleaning up dangling veths"

Link: https://github.com/moby/moby/issues/31937


Updated XIAO M0 dependencies and examples

Summary
I updated XIAO M0 dependencies and examples with latest crates.
I tested blink and ssd1306 examples but all examples do compile so it should be good.
Feel free to use the modifications for other boards, especially usb device changes for string descriptors.
Checklist

[x] CHANGELOG.md for the BSP or HAL updated
[pass] All new or modified code is well documented, especially public items
[x] No new warnings or clippy suggestions have been introduced - CI will deny clippy warnings by default! You may #[allow] certain lints where reasonable, but ideally justify those with a short comment.

If Adding a new Board

[pass] Board CI added to crates.json
[pass] Board is properly following "Tier 2" conventions, unless otherwise decided to be "Tier 1"

If Adding a new cargo feature to the HAL

[pass] Feature is added to the test matrix for applicable boards / PACs in crates.json

Thanks @TheRolfFR! Please just make sure the formatting check passes, and I can merge this.


[backport] Show versions of cub and cutensor on cupy.show_config

Backport of #3271

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 99a37ed72cb3966da848ddd8f621c5d5a0536a9f, target branch v7) succeeded!


Possibly broken with 2022.5

I get the following error:
Logger: homeassistant.setup
Source: setup.py:298
First occurred: 10:13:34 PM (1 occurrences)
Last logged: 10:13:34 PM
Unable to prepare setup for platform tibber_custom.camera: Platform not found (numpy.core.multiarray failed to import).
While I haven’t changed any of my configs. Just updated to 2022.5.
Is it working for anyone else on this version?

Same problem for me since upgrading

Yup the exact same thing happened to me too.

Same here.

Same issue and error message here

Works for me again with 2022.5.2.

Same! Guess this can be closed

Yep. It works with the latest update.

yep, works now


Change Vertical Offset to Y Offset

Since I'm using a modified 3D Printer, "Vertical Offset" is confusing. I changed it to "Y Offset" to match "Invert Y Axis".

Added additional commits to laser.py for review

I reset the default footer to None because the svg_to_gcode library already turns off the laser by default.


OpenROAD.IOPlacement options

Description
io_layer_variables https://github.com/efabless/openlane2/blob/12c6d69ce9d08f0c524fdc6aef179f7632b9fa30/openlane/steps/common_variables.py#L19 used in OpenROAD.IOPlacement have no validation. Layout would be generated with geometry related issues such as overlapping pins and pins that violate spacing rules. Back in the day, these variables were added to ensure maximum routability for macro integration. In a recent (will find the link) discussion with OpenROAD it was questioned whether these options are really needed and should be removed. We didn't get back to OpenROAD if we value these options.
Proposal
Study the feasibility and value of these options and decide on either removing them or keeping them and have some sort of validation for these variables

Do you have a link to the issue where they asked for us to re-investigate our need for those options?

Do you have a link to the issue where they asked for us to re-investigate our need for those options?

I will look for it

https://github.com/The-OpenROAD-Project/OpenROAD/issues/3372

@mo-hosni, weigh in?


Applying cel upgrade to release 1.5

We (Intuit) would like to use these string functions for our logging via Mixer (until we move away from mixer-telemetry), and would like to be able to leverage them in 1.5. (Ref: https://istio.slack.com/archives/C382V8Q92/p1585682045040300)

Hi @josephpeacock. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@googlebot I fixed it.

Hey @josephpeacock , thanks for your contribution.
Our normal "flow" is to commit to master and cherrypick to the release branch. Is this PR a manual cherrypick of #22110 ?

Hi @fpesce, not sure if my methodology was right, but that was the goal. @kyessenov tried to automatically do so (/cherrypick release-1.5) on the original PR, which failed with a conflict. So I created a patch of my commit and applied it to the release-1.5 branch, and created this PR. Let me know if I should re-do this in some other way.


Issues with nested tags, this.tags, and this.parent

I been talking about issues I have run across in issue #300 but there has been no comment and really is becoming a more general issue that keeps flopping around between versions.
Same code, just different versions of riot:
2.0.10 -> http://jsfiddle.net/6ep4agLw/3/
2.0.11 -> http://jsfiddle.net/6ep4agLw/2/
2.0.12 -> http://jsfiddle.net/6ep4agLw/
2.0.13 -> http://jsfiddle.net/6ep4agLw/1/
Just between these versions it flops back and forth on processing and or skipping/missing nested tags. Yes I know the this.tags were not in past versions, so ignore that part in those past version examples.
On the versions that are not dropping the nesting tags, and this one might just be an opinion or point of view thing, have their parent as the outer most defined tag and not what they are nested under. This has flopped around too in even prior versions. I believe the parent should be what you are really nested under, and if you need to access a different level you can pass it. Yes having the highest most is nice for pulling nodes inside for inner content, but this seems to be the only good for initial logic as that parent is really invalid in many cases after that point. There really are many different points of view on what should be your parent when you start and when you settle.
With this.tags I saw that when you have unnamed tags, instead of making an array of these in this.tags, the this.tags.sometag takes on the value of the last tag of that type encountered that is unnamed. Also from the examples what I believe is expected in this container is not. Again the outer most defined tag gets all of the tags in its this.tags but the nested tags do not have anything that is under them in theirs.

I think your mistake is here:
riot.mount('*');

Riot mounts automatically all the nested tags, but if you try to mount all of them at same time it will fail. What if you just mount starting from the outer tag?

riot.mount(...) will only automatically mount nested tags if those nested tags are declared in a tag definition (i.e. a <script type="riot/tag">...</script>) and not those living in the HTML body nested under other riot tags.
http://jsfiddle.net/6ep4agLw/4/ (2.0.12)

@sheastreet this should be fixed (we have refactored a bit the riot code and now you can use the yield tag to create nested dependencies) can we close this bug?


template: pass active to avoid AttributeError

Another try to fix #283 :)

Current coverage is 85.16% (diff: 100%)

Merging #287 into master will not change coverage

@@             master       #287   diff @@
==========================================
  Files            56         56
  Lines          1827       1827
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1556       1556
  Misses          271        271
  Partials          0          0

Powered by Codecov. Last update e7ae452...fbd6fff

Ah, I like this one. Future includes can just look at existing usages to realise they should pass this variable. Cool.


[RFC]: refactor blas/ext/base/dapxsumors to follow current project conventions

Description
This RFC proposes refactoring @stdlib/blas/ext/base/dapxsumors to follow current project conventions.
These conventions are outlined in more detail in https://github.com/stdlib-js/stdlib/issues/788. Namely, we want to migrate from C++ add-on interfaces to C add-on interfaces and then make various style and simplification changes.
Some example commits which perform most, if not all, of the requested changes include https://github.com/stdlib-js/stdlib/commit/d66d80cfcbab1da95cb5ae8cfae4a1fc4c5129d1 (saxpy),  https://github.com/stdlib-js/stdlib/commit/3c82fe7b6c0f9fd6ef02c86d6e2024d708ac8c14 (cswap), and https://github.com/stdlib-js/stdlib/commit/5b15c9675be434c0e11b1ec1e1f78d7b089abbcd (dasum).
Related Issues
Related issues #788, #1152.
Questions
No.
Other
No.
Checklist

[X] I have read and understood the Code of Conduct.
[X] Searched for existing issues and pull requests.
[X] The issue name begins with RFC:.

@Planeshifter  I would Like to work upon this issue. Please assign it to me.

@ShivamAhir Done. Looking forward to the PR!


TypeError: Cannot read properties of undefined (reading 'call')

TypeError: Cannot read properties of undefined (reading 'call')
at item.set (validator.js:75:80)
at validator.js:317:25
at Array.forEach ()
at Validator.import (validator.js:310:68)
{
    "items": [
        {
            "field": "name",
            "message": "This field is required!",
            "valid": false
        },
        {
            "field": "email",
            "message": "This field is required!",
            "valid": false
        }
    ]
}

The error occurs because the validator attempts to set new values from the provided object into the object being validated, but the method responsible for retrieving the object is returning undefined. This leads to the failure when trying to update the values.
Solution
To fix this issue, you need to call the .init() method on the validator. The .init() method should be used to pass a function that will return the object you want to validate. This is especially important when you intend to import validation results from another validator or application.
Example Code
import { BshValidationError, v } from "@bshg/validation";

v.configure({
  validatorOptions: {
    dev: true
  }
});

type User = {
  email: string;
  name: string;
};

const validator1 = v.validator<User>({
  id: "user-1-validator",
  items: {
    email: v.string().required().email(),
    name: v.string().required()
  }
});

const validator2 = v.validator<User>({
  id: "user-2-validator",
  items: {
    email: v.string().required().email(),
    name: v.string().required()
  }
})
  .init(() => ({
    email: "",
    name: ""
  }));

validator1.validateThrowAsync({
  email: "email",
  name: "1234"
})
  .then(() => console.log("pass"))
  .catch(v => {
    const error = v as BshValidationError;
    validator2.import(error.results); // This will works now
  });

.init() Method: This method is crucial when you want to import the validation results into another validator, especially if you need to update the validated object's values with new values. This situation often arises when validation results are retrieved from an external source, such as a backend application. If you don't call .init() with the appropriate function, the validator may ignore the new values, potentially causing data loss.

With the latest updates, you may encounter a warning like this:
if the value of 'email' was changed, the new value will be ignored! to avoid this behavior, please use the '.init()' method to pass the object to set the changes to.


ir:feat - add support for file imports

ir:feat - add support for file imports
This commit add a support to handle file imports on IR.
To support file imports a new interface Member was created. This
interface basically represents a object member that can be created or
declared inside a file; for now this Member could be a Function or a
Import, but in the future this member could be class declarations,
constants and global variable declarations.
A new struct ExternalMember was created that implements Member
interface. This struct is a generic member that represents imports, your
fields holds information about the path of import, the name of import
and a optional alias. These information's is used to construct a concrete
Member like a function or a variable.
A new struct File was also created that holds all members declared on
some file. This struct represents an ast.File converted to IR
representation.
Signed-off-by: Matheus Alcantara<EMAIL_ADDRESS>

This PR requires #74 to be merged first.


Adapt to using the circuit arithmetics library

Summary
Qiskit/qiskit-terra#4062 moved the arithmetic operations we had in qiskit/aqua/circuits to circuit arithmetics library and converted them to circuit objects. This PR changes the circuit factory objects in Aqua to use the library objects and deprecates them.
Probably we should leave the tests we had in for now to make sure everything still works and then remove then in a follow-up PR. Or can we already remove them in this one?

We should leave the tests to ensures the components still continue to work even though they are deprecated. In the tests make sure they filter out the deprecation warning i.e. warnings.filterwarnings("ignore", category=DeprecationWarning)
Can you also change any components that continue to use these such as european_call_delta and others. (Search for any imports of qiskit.aqua.circuits in the main code and/or look at the build output here as recently we added logic to collate deprecated warnings emitted by the build to ensure Aqua does not use deprecated function - outside of and tests that need to test it, hence the filter).
Also can you create a changelog entry noting that these have become part of new circuit library in Terra etc.

Ok, the tests are still there 👍 I added the deprecation warnings filter to the tests and replaced the places where the previous circuit factory types were used by the circuit library objects (European Call Delta etc.).
Is the note in the changelog sufficient?


Not an issue, just question on kindly provided example.

if (MainFormsPlc != null) { var value = MainFormsPlc.Read("DB9.DBD2"); }
tell me please for what do you check if MainFormsPlc is not equal 'null'?
I'm asking because I have in my code following:
private Plc plc = null; And it's working.
P.S. I'm not much familiar with such kind of sites based on pretty odd forum engines. Especially highly recommended Stackoverflow.

Ah, I see...
Before showing SubForm the Plc instance is passed to the newly created SubForm. While executing button_Click in the SubForm you might not want to have a NullReferenceException before doing PLC actions.
I prefer to catch such issues before they actually get a problem (Exception), in this case it is a user that clicks the button. I don't know when the user clicks it, maybe in some mid-action while the Form (Form1) is still initializing. This might not happen in this simple example but may in some advanced setups.

@Mallowan
I find it neat to have versioning support built-in, so GitHub reflects all changes. I am also still learning to utilize GitHub correctly. There are many features but this applies to most other platforms as well.

Where do you have private Plc plc = null; in your project?
If it is in your MainForm and you use it (Open(), Read() or Write()) you don't need to Open() in SubForm again. MyPlc (or your plc) points just to the same instance as MainFormsPlc in the SubForm.

MainForm, some pieces of code.
 public partial class MainForm : Form
    {
        private Plc plc = null;
        private ErrorCode errCode;
        public bool? CPUisConnected; //By certain reasons this variable must be nullable, so it's "bool?".
                                     //Because normal boolean variable is always true by default. So while application starting it causes fail " PLC connection is broken".
                                     //The connection itself is in process of establishing in that moment, though.

 #region PLC connection and errors handling

            //////////////////////////////////-PLC connection and errors handling-//////////////////////////////////

            try
            {
                plc = new Plc(CpuType.S71500, "<IP_ADDRESS>", 0, 1);

                if (!plc.IsAvailable) throw new Exception("Plc not responding to ping");

                errCode = plc.Open();

                if (errCode != ErrorCode.NoError) throw new Exception(plc.LastErrorString);

            }

            catch (Exception ex)
            {
                //MessageBox.Show(ex.Message, "Attention!",MessageBoxButtons.OK,MessageBoxIcon.Error);
                Form_ErrorBox.Show(ex.Message, "Attention!", "OK");

            }

            #endregion

Also I would like ask about following:
I noticed that for app there's no matter if I put '0' or '1' in Rack value in the line

plc = new Plc(CpuType.S71500, "<IP_ADDRESS>", 0, 0);
in real hardware configuration i have rack =1. look at the pic attached.  However it's working with '0' as well.

I assume the region PLC is in Form's construct so plc will be instanciated when you open a SubForm. That should be fine, it can be private.
Second, Slot is irrelevant on 1500, I have seen this in NetToPlcSim also. Unsure if Rack is working, don't have a suitable setup ATM.

Feel free to re-open.


Adds a neededfossils command

Resolves #70

Codecov Report

Merging #71 into master will decrease coverage by 0.56%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##           master      #71      +/-   ##
==========================================
- Coverage   98.57%   98.00%   -0.57%
==========================================
  Files           1        1
  Lines         633      653      +20
  Branches      117      123       +6
==========================================
+ Hits          624      640      +16
- Misses          0        2       +2
- Partials        9       11       +2

Impacted Files
Coverage Δ

turbot/__init__.py
98.00% <80.00%> (-0.57%)
:arrow_down:

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 c460570...d340de4. Read the comment docs.

Dang that's a big red image for a decrease of coverage by 0.56% lol


Fix ListView Component

The list view component was using the createMockComponent, even though there was a mock component written for the list view.
This PR activates this component, and fixes the problems in it.
Should fix #12

there's some more work to be done on the listview, but I think this will unblock some people so :+1:


Typeclass derivation for ordering not working

The typeclass derivation example for ordering (shown here: http://dotty.epfl.ch/docs/reference/contextual/derivation.html) is not compiling.
It seems that the Ordering companion object does not define the derived method.
scala> enum Tree[T] derives Eql, Ordering, Pickling {
     |   case Branch(left: Tree[T], right: Tree[T])
     |   case Leaf(elem: T)
     | }
1 |enum Tree[T] derives Eql, Ordering, Pickling {
  |                                    ^^^^^^^^
  |                                    Not found: type Pickling
1 |enum Tree[T] derives Eql, Ordering, Pickling {
  |                          ^
  |               value derived is not a member of object scala.math.Ordering

In the documentation Ordering is just an example (Commonly used examples are...) and does not refer to scala.math.Ordering. With a user defined Ordering typeclass and the appropriate typeclass derivation infrastructure in its companion object this should work as intended!

but that is a terrible thing to do. very misleading doc. it should be explained in advanced

I agree that the doc is subpar. I had to learn the impl recently for checkUnused. It's just a convention but the doc sounds like magic.


OpenAPI Java POJO Does Not Support Array Parameters

Currently the the schema.java class used by parameters in the OpenAPI java POJO does not contain a field for items when the parameter is of type "array"
There currently is no way to support this style of parameter with a POJO
 parameters:
      - name: foo
        in: query
        schema:
          type: array
          items:
            type: string

This is causing major issues for us as we serve a swagger page from these POJOs.
Please add an optional items field to the Schema.java class that is used by the Parameter.java class

I've long been searching (the past 9 months) for an answer. Turns out there's an array subtype, and a swagger parser. This solves all my life problems.

@rickerju any chance can you share some example code ?


v0.3.3

v0.3.3
🚀 Features

Add custom header and footer include files @CodeSandwich (#334)

🐛 Bug Fixes

Limit the effect of nav_exclude to the main navigation @pdmosses (#443)
Update normalize.scss @pdmosses (#444)
Update code.scss @pdmosses (#445)
Fix list alignment @pdmosses (#446)

🧰 Maintenance

Bump stylelint-config-primer from 9.0.0 to 9.2.1 @dependabot-preview (#451)
Bump stylelint from 13.6.1 to 13.7.2 @dependabot-preview (#440)
Bump @primer/css from 15.1.0 to 15.2.0 @dependabot-preview (#436)
Bump prettier from 2.1.1 to 2.1.2 @dependabot-preview (#429)

@pdmosses this looks good to me, but could use another 👀 before 🚢 🚢

@pmarsceill thanks for approving and merging the PRs. I'll review the changes in v0.3.3 and report back ASAP.

@pmarsceill it looks good to me. Apart from viewing the changes, I've also downloaded the code and checked the regression tests locally using Jekyll v3.8.5. 🎉

BTW, when v0.3.3 has been released, I'll need to update my remaining PRs. Is it best for me just to merge the new master into the feature branches of my fork, or should I rebase first?

```

v0.3.3
🚀 Features

Add custom header and footer include files @CodeSandwich (#334)

🐛 Bug Fixes

Limit the effect of nav_exclude to the main navigation @pdmosses (#443)
Update normalize.scss @pdmosses (#444)
Update code.scss @pdmosses (#445)
Fix list alignment @pdmosses (#446)

🧰 Maintenance

Bump stylelint-config-primer from 9.0.0 to 9.2.1 @dependabot-preview (#451)
Bump stylelint from 13.6.1 to 13.7.2 @dependabot-preview (#440)
Bump @primer/css from 15.1.0 to 15.2.0 @dependabot-preview (#436)
Bump prettier from 2.1.1 to 2.1.2 @dependabot-preview (#429)

v0.3.3
🚀 Features

Add custom header and footer include files @CodeSandwich (#334)

🐛 Bug Fixes

Limit the effect of nav_exclude to the main navigation @pdmosses (#443)
Update normalize.scss @pdmosses (#444)
Update code.scss @pdmosses (#445)
Fix list alignment @pdmosses (#446)

🧰 Maintenance

Bump stylelint-config-primer from 9.0.0 to 9.2.1 @dependabot-preview (#451)
Bump stylelint from 13.6.1 to 13.7.2 @dependabot-preview (#440)
Bump @primer/css from 15.1.0 to 15.2.0 @dependabot-preview (#436)
Bump prettier from 2.1.1 to 2.1.2 @dependabot-preview (#429)


Detangle circular requirements for migrations

This PR improves the detangling of circular requirements (python-ligo-lw) to better support migrations.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Optional dependencies

Made neo4j-cypher-dsl an optional. Changed the template.mf files so that packages from optional dependencies are also optionally imported in OSGi.
Defined postConstruct as the initMethod of the Neo4jTemplate bean.

Cypherdsl cannot be optional, because it's used in the AbstractGraphRepository.


Add all ruby version to travis.yml

Should we drop support for 2.1 and below?
https://www.ruby-lang.org/en/news/2017/04/01/support-of-ruby-2-1-has-ended/

I think we should drop it only if necessary.


JDA getter hierarchy abstraction

Pull Request Etiquette

[x] I have checked the PRs for upcoming features/bug fixes.
[x] I have read the contributing guidelines.

Changes

[x] Internal code
[x] Library interface (affecting end-user code)
[x] Documentation
[ ] Other: _____

Closes Issue: NaN
Description
Summary
Adds a unifying superinterface for the common JDA getter.
Reasoning
There were 54 cases of "JDA getJDA()" getters. That has been reduced to 34, 32 of which were direct default/non-abstract implementations of it, and the other 2 of which were still abstract and were left because their documentation left extra details about its specific sub-implementations, i.e. it could throw an exception. Almost all of the previous abstract implementations had inconsistent variations of exactly the same documentation, which has now been unified. This change would remove a lot of duplicate code and documentation and lets developers not have to write the same documentation and/or change it slightly for this method, opting to just implement the FromJDA interface instead. This will very unlikely affect any end-user code. And, this project is not foreign to this pattern, with its ISnowflake interface already.
Notes
This could also be applied to the common Guild getter, which had 81 uses, 25 being abstract. getChannel and getUser/getAuthor had too few use cases to do a similar thing.

Would personally name the interface "JdaContainer"
"FromJda" sounds like a method fromJda, gives me the impression I can create the entity, from JDA.

@Tais993 Yes, maintainers feel free to change it to whatever name makes sense :). I actually wasn't too sure on the one I picked, it was supposed to be as if it was already created "from that jda" instance you can get. JdaContainer probably works better.

I'm not a huge fan of introducing interfaces for a single method. This is really kind of strange to do and results in very complicated type definitions. Inconsistent wording in the documentation isn't really a problem either, since they all mean the same thing at the end of the day.


Should add return a Result?

When the arena is at capacity, further adds will panic (if debug assertions are enabled) or overwrite the first element, which is probably unwanted.
add should probably return a Result<Idx*, CapacityExceeded>. Or we leave add as is (or better, always panic) and introduce a new try_add method, but I'm not happy to make the better solution the longer one.
Perhaps:

add returns Result
checked_add panics
wrapping_add overwrites

When the arena is at capacity, further adds will ... or overwrite the first element, which is probably unwanted.

It's not true. I added more tests, see https://github.com/llogiq/compact_arena/pull/4
The problem is:
const NANO_ARENA_ITEMS: usize = 255;

pub struct TinyArena<T, B> {
    ...
    data: [T; TINY_ARENA_ITEMS],
}

assert!((i as usize) < NANO_ARENA_ITEMS);
self.data[i as usize] = item;
self.len += 1;

You cast i to usize and try to assign an item to [T; 255]  with idx=255, which will obviously fail because of out-of-range index. Max index should be 255 and the size of nano arena should be 255+1 to enable wrapping addition for u8.
But that's not all. There is a different behavior in permutation of debug/release and no-default-features/uninit which gives us the following bug:
cargo test --release --features uninit

---- add_256_objects stdout ----
thread 'add_256_objects' panicked at 'index out of bounds: the len is 255 but the index is 255', /home/humbug/compact_arena/src/lib.rs:503:13
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
note: Panic did not include expected string 'assertion failed: (i as usize) < NANO_ARENA_ITEMS'

failures:
    add_256_objects

Or we leave add as is

It's up to you, but there is a big flow: there is no len() method, so the user can not manually implement try_add.

I'm working on adding try_add to all arenas. add then becomes self.try_add(item).unwrap().

How about 255 -> 256 for nano arena issue?

We now have try_add on all arenas, so closing this.


Splink install failing due to splink_datasets PermissionError

Another colleague in ONS and I have been struggling to import splink into a dataproc serverless instance. We're both essentially using the basic google recommended container image from a dockerfile and just adding Splink to the list of dependencies to install.
The problem doesn't seem to occur with Splink version 2.x but does with 3.x and 4, and there isn't a problem using Splink on a single VM inside Google Cloud Platform.
The error that returns is:
File "/opt/miniconda3/lib/python3.12/site-packages/splink/__init__.py", line 5, in <module> from splink.internals.datasets import splink_datasets
File "/opt/miniconda3/lib/python3.12/site-packages/splink/internals/datasets/__init__.py", line 270, in <module> class _SplinkDataSets(metaclass=_SplinkDataSetsMeta, datasets=_datasets):
File "/opt/miniconda3/lib/python3.12/site-packages/splink/internals/datasets/__init__.py", line 152, in __new__ cls.cache_dir.mkdir(exist_ok=True)
File "/opt/miniconda3/lib/python3.12/pathlib.py", line 1311, in mkdir os.mkdir(self, mode)
PermissionError: [Errno 13] Permission denied: '/opt/miniconda3/lib/python3.12/site packages/splink/internals/datasets/__splinkdata_cache__'

Originally posted by @WillHoylesONS in https://github.com/moj-analytical-services/splink/discussions/2340

Closed by #2357, but see also #2369.


CHEBI:15642, the name is wrong, and KEGG x-ref invalid

Hi,
This compound, CHEBI:15642, (6R)-6-(L-erythro-1,2-dihydroxypropyl)-5,6,7,8-tetrahydro-4a-hydroxypterin, is in fact D-erythro. KEGG has deleted its original structure C06486. Instead the have created C15522 that is wrongly cited in CHEBI:15374.
I have just submitted the correct structure, CHEBI:136571 and have add a cross reference to KEGG C15522
Cheers,
Kristian

Hi Kristian,
As CHEBI:15642 seemed to have the right names but the wrong structure, I have merged it with your submission - the primary ID is CHEBI:15642.
Is there any evidence for the stereochemistry for the stereobond (shown in Kegg C15522) to the hydroxy group at the ring junction? I am slightly puzzled by the terminology "4alpha-hydroxy..... - the position would normally be termed 4a rather than 4alpha  -  with terms such as 4alpha, 3beta, etc., the greek letter would normally refer to the stereochemistry rather than position (as with steroids) - so I wonder whether it should be "4a-hydroxy..." rather than "4alpha-hydroxy..." ?
Cheers,
Gareth

Hi Gareth,
I took the name from MetaCyc without considering it much. I asked Ron if they had a special reason for it, and as they have not, please change back to 4a
Cheers,
Kristian

Thanks, Kristian.
I have added a MetaCyc link (CPD-5881) to CHEBI:15642 and to the 'unspecified stereochemistry' version, CHEBI:15374 - structure-wise, it isn't a perfect match for either ChEBI entry, but one or more of the synonyms from both ChEBI entries matches with the MetaCyc entry.
Cheers,
Gareth


Improve Psalm annotations

This contribution adds annotations similar to the runtime checks to
allow users of static analysis tools to catch those errors.
All the new annotations have been added under the @psalm- vendor
prefix to make sure IDEs does not encounter annotations they do not
known how to parse.
No changes at runtime is expected by this contribution.

PIE will fix the Psalm annotations in the next minor patch.


Retry on SSL Connect Error.

I have been getting a bunch of spurious [35] SSL connect errors on Azure Pipelines, so these should be treated as spurious errors.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ehuss (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

@bors: r+
Thanks!

:pushpin: Commit f7724aef59ac14188ed79bd2b58e45375d33e58c has been approved by alexcrichton

:hourglass: Testing commit f7724aef59ac14188ed79bd2b58e45375d33e58c with merge 531c4bff7f0ecb036b60bc0d4421ff50fae148d8...

:sunny: Test successful - checks-azure
Approved by: alexcrichton
Pushing 531c4bff7f0ecb036b60bc0d4421ff50fae148d8 to master...