smooch.io & rasa.ai integration (+ bonus deployment scripts)

(as I can't publish on the forum, I put this information here)
Addventa is a French AI company specialized in Natural Language Generation and chatbots. We love ChatScript and have developped multiple bots with it. We have contributed to the French language support in ChatScript's code.
We have open sourced 3 repos (under MIT licence):
https://github.com/addventa/ChatScriptSmooch:
Integration of ChatScript with smooch.io.
Smooch.io provides a nice end-user interface (web chat) and can connect to any other channel: facebook messenger, email, SMS etc.
Easy to deploy on heroku or Amazon beanstalk. Works well.
https://github.com/addventa/ChatScriptDeploy:
Installation scripts of ChatScript on a Linux server. Ability to have multiple versions installed.
Lifecycle of a bot on a ChatScript server: scripts to automate the deployment of a new bot and to update a bot.
https://github.com/addventa/ChatScriptRasa:
Integration of ChatScript with rasa.ai for intent classification and entity recognition. Comes with a sample bot that calls rasa.ai.
Have worked on that:

Jean-Baptiste Kerboeuf https://www.chatbots.org/expert/jean_baptiste_kerboeuf/69759/
Corentin Gaillard https://www.chatbots.org/expert/corentin_gaillard/70268/
and myself Ludan Stoecklé https://www.linkedin.com/in/ludanstoeckle/

Hi Ludan!
BTW, the forum login issues are solved, I guess.
Maybe it's better to move there, but Thank you for your shares!
Maybe you can add pull request here adding links in a dedicated paragraphs in this doc:
https://github.com/bwilcox-1234/ChatScript/blob/master/Third Party Tools/README.md
Last but not least, any help in improving wiki documentation here is welcome; I'm available also via mail for possible synchs<EMAIL_ADDRESS>regards
giorgio

Thanks Giorgio!
I agree - pull request created: https://github.com/bwilcox-1234/ChatScript/pull/109
Forum issues are not solved yet, I can't login :( I'll do it later.

Thanks to you
[off-topic]
yes chatbots.org forum login-process is awful.  Nevertheless is a great container and history of Bruce's answers.  Immo a forum dedicated to ChatScript could be better...


[Feature Request]: Able to install via winget

The request
Requesting that WAU can be installed with winget, see this PR: https://github.com/microsoft/winget-pkgs/pull/152510
Is your feature request related to a problem?
No response
Additional information
No response

We are currently working on a MSI installer. I think it will be easier to manage WAU with winget after that.

Not stale.

https://github.com/Romanitho/Winget-AutoUpdate/discussions/582#discussioncomment-10112654

Not stale.

Not stale.

Not stale.

https://github.com/microsoft/winget-pkgs/pull/182735


Add pvc

This PR transform the stateful set claim template to a rendered PVC. This enables reusing existing PVCs so the data can be used between cluster re installs without restoring backups. It also enables estaticly provisioning the volumes (PV and PVC), so there's an escape hatch for the complex configuration required by home-assistant.
The PVC (instead of template) also has been augmented to allow selector and annotations.

Hi, thank you for your contribution. I completely understand the changes you've made. However, I need to address two issues related to your changes:

Backward compatibility: The changes break all current installations because the PVC generated by the StatefulSet has its own suffix related to the replica number. This could cause significant issues for existing setups.

The creation of a single PVC for all replicas could pose a problem in the current default configuration. In scenarios where multiple instances are running, modes such as ReadOnlyMany or ReadWriteMany must be used. This adjustment might not be suitable for all use cases.

I believe that creating a custom PVC can offer benefits in certain specific situations. However, for backup purposes, this might not be the ideal approach since the PVC has a predetermined name, unlike in Deployment mode where a UUID is used in the name. This means that when a new HA deployment is created, the previous PVC with the expected name will be found and reused.
To accommodate these considerations, I have created a new branch. I would suggest making the manual creation of a PVC an optional choice in the values.yaml file. This would provide flexibility and allow users to choose the best configuration for their specific needs.

@pajikos this is my train of thoughts:

Home assistant is not meant to be deployed in HA (pun intended) I mean high availability, I don't think replicas will be eve != 0.
The provided settings allow for dynamically provision PVC, if you don't specify the claim name, it will actually create a new PV. (the behaviour is not obvious).
about the breaking change, completely agree, I think giving a lot of flexibility in the claimSpec could do the trick.

Let me know what you think.

@pajikos  https://github.com/pajikos/home-assistant-helm-chart/pull/48 I think this PR ticks all the boxes.


config: Fix 'optional' -> 'OPTIONAL' for process.terminal

This happened in #574 but was accidentally rolled back in #518.

LGTM

LGTM


Consumer streams terminate on F.raiseError from EnvelopeDecoders

This makes it a big pain to use with a parsed type.
Some options were explored in #151, but not completed.
We will want to provide some means to handle those automatically for users, because for example, json decoding using circe is a common use case, and you cannot prevent a publisher from submitting invalid json, or incorrect structure for your given circe.Decoder
As a workaround so far, I've found this useful:
  /** Convert a decoder producing `A` to a decode that handles failure with `Left` */
  implicit def fallibleDecoder[F[_], A, E](
      implicit decoder: EnvelopeDecoder[F, A],
      F: MonadError[F, E]
  ): EnvelopeDecoder[F, Either[E, A]] =
    decoder.attempt

@gvolpe ^ Is there a way we can configure that bot to exclude certain things?

Added the pinned label, that should be enough


theme.css doesn't work in react-boilerplate

I followed the steps given in the readme, but when I try a simple button <Button primary raised>Welcome to RT</Button>, it doesn't take any styling.

I tried including the generated CSS file assets/react-toolbox/theme.css in react-boilerplate/app/app.js, but I get the following error:

Hello @platonish , having assets folder inside react-boilerplate/app/  I've used this import in app.js and it works:
import '!style-loader!css-loader!./assets/react-toolbox/theme.css';


container layout grid

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


make chat font consistent with vscode UI

For compatibility purposes I didn't remove the original fonts below, seems they are removable. This one is working on my vscode setting, but haven't tested it in a clean install. Please help check, thanks!

looked like it works for me as well, thanks for making Continue look beautiful!


Type 'xxx' already defines a member called 'yyy' with the same parameter compile errors in the generated code.

Actual behavior
Type 'xxx' already defines a member called 'yyy' with the same parameter compile errors in the generated code.
Expected behavior
No compile error in the generated code.
Repro steps

NativeMethods.txt content:

D2D1CreateFactory
ID2D1Factory7
DWriteCreateFactory
IDWriteFactory

Any of your own code that should be shared?

Context

CsWin32 version: 0.1.422-beta
Win32Metadata version (if explicitly set by project): -
Target Framework: net5.0-windows
LangVersion (if explicitly set by project): -

No repro after #270 was merged. Probably fixed in that large change.


JRE 17 LTS: can't open jar files

Please provide a brief summary of the bug
I just installed the latest version of Eclipse Temurin JRE 17LTS and I wanted to install Optifine but I couldnt open the file as it opens a console windows for a millisecond. Nothing happens after that.
I tried to use java -jar file.jar in a console window and it worked. I didnt changed anything from the installer or something.
Please provide steps to reproduce where possible
No response
Expected Results
The file should open as usual and do the things that it should do.
Actual Results
A console window for a millisecond. Nothing happens afterwards.
What Java Version are you using?
openjdk 17.0.8 2023-07-18 OpenJDK Runtime Environment Temurin-17.0.8+7 (build 17.0.8+7) OpenJDK 64-Bit Server VM Temurin-17.0.8+7 (build 17.0.8+7, mixed mode, sharing)
What is your operating system and platform?
Microsoft Windows 10 Pro
Version: 10.0.19044
How did you install Java?
Downloaded the installer package from the official adoptium.net site.
Did it work before?
I just reseted my pc. I've had Oracle Java installed before and everything worked.

Did you test with the latest update version?
It is the latest update.

Did you test with other Java versions?
openjdk 17.0.8 2023-07-18 LTS
OpenJDK Runtime Environment Zulu17.44+15-CA (build 17.0.8+7-LTS)
OpenJDK 64-Bit Server VM Zulu17.44+15-CA (build 17.0.8+7-LTS, mixed mode, sharing)

Also with Redhat:
jdk-17.0.8+7_1
JDK
July 20, 2023

Relevant log output
No response

Used jarfix and the problem was solved.

Awesome.  It also made it much simpler (as it should be imo).


workaround for allocations when broadcasting equations

See https://github.com/trixi-framework/Trixi.jl/pull/1618
Together with #1625, this should hopefully fix the current CI issues.

Let's hope https://github.com/JuliaLang/julia/issues/51118 will be fixed...

I hope so, too, but I'm not very optimistic, to be honest. The issue is solved in Julia v1.10 - the next stable release. Thus, I guess there is not much pressure to fix this specific issue. Of course, for us it's very important since there are much more severe issues with Julia v1.10, e.g., https://github.com/JuliaLang/julia/issues/50985, https://github.com/JuliaLang/julia/issues/50562

I'll merge this now since non-coverage CI passes - except the test fixed in #1625


typo in README

u wrote "chenge" and should be "change" :)

thx for pointing me on this spelling error :]


Disable cypress tests for real

Summary
Missed a job in https://github.com/mattermost/mattermost-plugin-apps/pull/492
Ticket Link
None

@toninis Gentle reminder to review the PR :smiley:

@toninis Good catch :+1:


time: update github.com/rickar/cal to v2 release

Codecov Report

Merging #218 (5cc1093) into master (a83d78f) will decrease coverage by 0.34%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #218      +/-   ##
==========================================
- Coverage   81.03%   80.68%   -0.35%
==========================================
  Files          29       28       -1
  Lines        1028      963      -65
==========================================
- Hits          833      777      -56
- Misses        133      134       +1
+ Partials       62       52      -10

Impacted Files
Coverage Δ

time.go
96.15% <100.00%> (+0.15%)
:arrow_up:

database/migrator.go
50.00% <0.00%> (-12.00%)
:arrow_down:

database/database.go
33.33% <0.00%> (-7.15%)
:arrow_down:

database/sqlite_cgo.go

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 a83d78f...5cc1093. Read the comment docs.


Upgrade to Ember 2.18 and fix ids on included objects

Fixes errors in app when server side ids were not applied to objects in the included block. Tests seemed to cover the same use case but were passing.

@BryanCrotaz thanks for the PR and all the work. I'll try to push a release out tomorrow.


Added async serialization methods

Solves issue #281

Any thoughts about this comment? #281 (comment)

I've made this change.

@DiscoPYF , I've made all the relevant changes. Will merge once you approve.


[CI/CD] Add Cypress e2e workflow for gantt chart

Description
Add Cypress e2e workflow for gantt chart
Related Issue

Relate  #296

Cypress error matches the expected error I captured on: https://github.com/opensearch-project/dashboards-visualizations/pull/296
The response we got was:
Status: 406 - Not Acceptable
Headers: {
  "content-type": "application/json; charset=utf-8",
  "osd-name": "fv-az985-504",
  "cache-control": "private, no-cache, no-store, must-revalidate",
  "vary": "accept-encoding",
  "content-encoding": "gzip",
  "date": "Wed, 13 Dec 2023 23:40:25 GMT",
  "connection": "keep-alive",
  "keep-alive": "timeout=120",
  "transfer-encoding": "chunked"
}
Body: {
  "error": "Content-Type header [application/x-www-form-urlencoded] is not supported",
  "status": 406
}

Link: https://github.com/opensearch-project/dashboards-visualizations/actions/runs/7202310509/job/19620185810?pr=298#step:20:115
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Let's backport this. During backport we'll have to modify the below lines:
OPENSEARCH_DASHBOARDS_VERSION: 'main'
OPENSEARCH_VERSION: '3.0.0'
OPENSEARCH_PLUGIN_VERSION: '<IP_ADDRESS>'

cypress is expected to fail for now. Synced with @RyanL1997 offline, he will create a backport for this to 2.x


Does it download the LCOW components

So does it automatically download the LCOW minimal linux VM ? or is that already present?
or does it use the Windows Subsystem for Linux
which is a why limited to Win10/2019 ?
And if so, does it automatically install that feature?

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

ID: 51faeed1-77c1-c8c6-c097-6806a3bbdf85
Version Independent ID: 84597429-d2e1-71ed-ee5d-fd2d66dcbff7
Content: Windows and Linux Containers on Windows 10
Content Source: virtualization/windowscontainers/quick-start/quick-start-windows-10-linux.md
Service: windows-containers
Product: windows-containers
GitHub Login: @taylorb-microsoft

edit - does not use WSL (mentioned on overview page)
but still unclear how/when the minimal LinuxKit gets set up under C:\Program Files\Linux Containers. Presumably happens automatically the first time the --platform linux is used

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


test(coverage): enable Babel es2022 tests

Enabled the Babel es2022 tests. Previously they were skipped probably because ES2022 was not yet supported at that time.

Thank you Babel maintainer!


HFilters

Where is HFilters? or even Filter thing?

You can set replacements/block headers in an HConnection instance with these properties:
(Incoming/Outgoing)Blocked
(Incoming/Outgoing)Replaced

Okay.


Add the X-XSS-Protection header

Re-enable XSS protection, even if the user has enabled it https://www.owasp.org/index.php/XSS_(Cross_Site_Scripting)Prevention_Cheat_Sheet#Bonus_Rule.234:_Use_the_X-XSS-Protection_Response_Header
Identified by observatory

I noticed this and a related issue https://github.com/redfin/react-server/issues/638 and I am adding helmet as a custom express middleware in my application. Would having it enabled as a default middleware in the react-server project itself be a good way to go about it?


MSID: 96155 Version: 2 DOI: 10.1101/2<IP_ADDRESS>5463

MSID: 96155
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>5463
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=96155
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>5463

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/96155v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>5463
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/96155/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

error: [journal-ref-article-title] This journal reference (id c7) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c42) has no article-title element.


Vagrant BOX:rockylinux/8 workflow is flaky (broken?): mount.nfs: requested NFS version or transport protocol is not supported

I'm seeing multiple runs across PRs failing with the following output:
mount -o vers=3,udp <IP_ADDRESS>:/tmp/cirrus-ci-build /vagrant
Stdout from the command:
Stderr from the command:
mount.nfs: requested NFS version or transport protocol is not supported

https://github.com/containerd/containerd/pull/7535 (5 failed runs)
https://github.com/containerd/containerd/pull/7534 (failed run)
https://github.com/containerd/containerd/pull/7530 (failed run)
https://github.com/containerd/containerd/pull/7469 (failed run)

It appears this might have started within the past few hours as https://github.com/containerd/containerd/pull/7533 (from 5 hours ago) succeeded.

Past:
==> default: Creating shared folders metadata...
==> default: Starting domain.
==> default: Waiting for domain to get an IP address...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: <IP_ADDRESS>:22
    default: SSH username: vagrant
    default: SSH auth method: private key
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Rsyncing folder: /tmp/cirrus-ci-build/ => /vagrant
==> default: Running provisioner: shell...
    default: Running: /tmp/vagrant-shell20221014-10118-455b5l.sh

Now:
==> default: Creating shared folders metadata...
==> default: Starting domain.
==> default: Waiting for domain to get an IP address...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH username: vagrant
    default: SSH auth method: private key
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Exporting NFS shared folders...
==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
==> default: Mounting NFS shared folders...
==> default: Pruning invalid NFS exports. Administrator privileges will be required...
==> default: Removing domain...
==> default: Deleting the machine folder
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o vers=3,udp <IP_ADDRESS>:/tmp/cirrus-ci-build /vagrant
Stdout from the command:
Stderr from the command:
mount.nfs: requested NFS version or transport protocol is not supported

Looks like the mount driver was silently changed?


Variable setting helpers

Currently, set_variable accepts a buffer.
It would be interesting to have the classical alternatives:

set u64
set uint
set string

etc.
This would make it far easier to set variables.
Potentially, the solution should be to have proper instances to transform the stuff?
Some example of the code I wrote regarding this: https://github.com/nix-community/lanzaboote/pull/166/files#diff-f2cc7d56b3462acd7190e54877874fd277591b33b4f261e03ef17ac242d033e5R154-R175

I think serializing the data should remain up to the application.  Strings are even more complicated of course -- what encoding? UCS-2 is common for UEFI APIs, but there's no requirement that it be used for string data in variables. For example, you could have utf-8 encoded JSON.

I think serializing the data should remain up to the application.  Strings are even more complicated of course -- what encoding? UCS-2 is common for UEFI APIs, but there's no requirement that it be used for string data in variables. For example, you could have utf-8 encoded JSON.

So Rust provides from_le_bytes, from_be_bytes, from_ne_bytes, etc. I wonder if it's scope creep to have similar APIs for that? Only for common usecases, I agree with you you could have anything and the sky is the limit.

We could, but I don't think it's worth it. For example, your current code is:
let _ = runtime_services.set_variable(
    cstr16!("StubFeatures"),
    &SD_LOADER,
    VariableAttributes::from_bits_truncate(0x0),
    &stub_features.bits().to_le_bytes()
);

With the additional API, it would become:
let _ = runtime_services.set_variable_u64_le(
    cstr16!("StubFeatures"),
    &SD_LOADER,
    VariableAttributes::from_bits_truncate(0x0),
    stub_features.bits()
);

That doesn't seem any clearer to me, so I don't think it justifies adding set_variable_* variations.

Agreed, let's close it this then, thank you for the discussion!


[Request] Create in the menu dropdown HELP>ABOUT section

It would be great to be uniform with most software by having a HELP>ABOUT window dropdown so users would know what version of GB Studio their working with.

Good point! This is implemented now in the develop branch 94560f6d373b643a8074d0557a1f1ab3a9609ef4

Thank you!


Heater/crockpot

What issue do you have? Please be as thorough and explicit as possible.
For both the heater and crockpot. I’m no longer able to set a target temperature. Fan speed works.
Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?

Homebridge ui-x

Which version of Homebridge/HOOBS do you have?

1.6.1

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.

Rpi, node 18.17.1

Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?
6.1.2

Which Wemo devices do you have that are causing issues? Please include product models if applicable.

heaterA & crockpot
It worked before, but I haven’t used the heater since it’s been warm. (And not since I’ve upgraded to the new architecture)
In the Wemo app it works, and the log reflects the changes in the Wemo app. But in HomeKit I’m unable to set a target temperature, (doesn’t show the temperature wheel/slider, fan speed can be set.
I tired a couple versions of the Wemo plugin, and a couple versions of node 18. Also I tried adding the child bridge to an old device running the old architecture of HomeKit.
Also I’ve tried adding it to home assistant.
It seems to work on the old architecture,  not on the new or on homeassistant
Please paste any relevant logs below.
22/10/2023, 12:19:41] [Homebridge UI] Homebridge log truncated by admin.
[22/10/2023, 12:19:54] [Wemo] [HeaterA] sending update {"Mode":4,"SetTemperature":75}.
[22/10/2023, 12:19:56] [Wemo] [HeaterA] current mode [eco].
[22/10/2023, 12:19:57] [Wemo] [HeaterA] sending update {"Mode":1,"SetTemperature":75}.
[22/10/2023, 12:19:58] [Wemo] [HeaterA] current mode [eco].
[22/10/2023, 12:19:58] [Wemo] [HeaterA] current mode [frost-protect].
[22/10/2023, 12:20:06] [Wemo] [HeaterA] sending update {"SetTemperature":81}.
[22/10/2023, 12:20:06] [Wemo] [HeaterA] target temperature [27°C].
[22/10/2023, 12:20:07] [Wemo] [HeaterA] sending update {"SetTemperature":83}.
[22/10/2023, 12:20:07] [Wemo] [HeaterA] target temperature [28°C].
[22/10/2023, 12:20:08] [Wemo] [HeaterA] sending update {"SetTemperature":84}.
[22/10/2023, 12:20:08] [Wemo] [HeaterA] target temperature [29°C].
[22/10/2023, 12:20:12] [Wemo] [HeaterA] sending update {"SetTemperature":79}.
[22/10/2023, 12:20:12] [Wemo] [HeaterA] target temperature [26°C].
[22/10/2023, 12:20:14] [Wemo] [HeaterA] sending update {"SetTemperature":75}.
[22/10/2023, 12:20:14] [Wemo] [HeaterA] target temperature [24°C].
[22/10/2023, 12:20:15] [Wemo] [HeaterA] target temperature [26°C].
[22/10/2023, 12:20:16] [Wemo] [HeaterA] target temperature [24°C].
[22/10/2023, 12:20:17] [Wemo] [HeaterA] sending update {"SetTemperature":66}.
[22/10/2023, 12:20:17] [Wemo] [HeaterA] target temperature [19°C].
[22/10/2023, 12:20:28] [Wemo] [HeaterA] sending update {"SetTemperature":81}.
[22/10/2023, 12:20:28] [Wemo] [HeaterA] target temperature [27°C].
[22/10/2023, 12:20:42] [Wemo] [HeaterA] sending update {"Mode":4,"SetTemperature":81}.
[22/10/2023, 12:20:42] [Wemo] [HeaterA] current mode [eco].
[22/10/2023, 12:20:44] [Wemo] [HeaterA] current mode [eco].
[22/10/2023, 12:20:45] [homebridge-doorbird] frontdoor: Motion detected.
[22/10/2023, 12:20:47] [Wemo] [HeaterA] sending update {"Mode":3,"SetTemperature":81}.
[22/10/2023, 12:20:47] [Wemo] [HeaterA] current mode [low].
[22/10/2023, 12:20:48] [Wemo] [HeaterA] current mode [low].
[22/10/2023, 12:21:16] [homebridge-doorbird] frontdoor: Motion detected.
[22/10/2023, 12:21:18] [Wemo] [HeaterA] sending update {"Mode":1,"SetTemperature":81}.
[22/10/2023, 12:21:18] [Wemo] [HeaterA] current mode [frost-protect].
[22/10/2023, 12:21:31] [Wemo] [HeaterA] sending update {"Mode":3,"SetTemperature":81}.
[22/10/2023, 12:21:31] [Wemo] [HeaterA] current mode [low].
[22/10/2023, 12:21:33] [Wemo] [HeaterA] current mode [low].
[22/10/2023, 12:21:47] [Wemo] [HeaterA] sending update {"Mode":2,"SetTemperature":81}.
[22/10/2023, 12:21:48] [Wemo] [HeaterA] current mode [high].
[22/10/2023, 12:21:49] [Wemo] [HeaterA] current mode [high].
[22/10/2023, 12:21:57] [homebridge-doorbird] frontdoor: Motion detected.
[22/10/2023, 12:22:03] [Wemo] [HeaterA] sending update {"Mode":3,"SetTemperature":81}.
[22/10/2023, 12:22:03] [Wemo] [HeaterA] current mode [low].
[22/10/2023, 12:22:04] [Wemo] [HeaterA] current mode [low].
[22/10/2023, 12:22:07] [Wemo] [HeaterA] sending update {"Mode":2,"SetTemperature":81}.
[22/10/2023, 12:22:07] [Wemo] [HeaterA] current mode [high].
[22/10/2023, 12:22:08] [Wemo] [HeaterA] current mode [high].
[22/10/2023, 12:22:11] [Wemo] [HeaterA] sending update {"Mode":4,"SetTemperature":81}.
[22/10/2023, 12:22:12] [Wemo] [HeaterA] current mode [eco].
[22/10/2023, 12:22:12] [Wemo] [HeaterA] sending update {"Mode":1,"SetTemperature":81}.
[22/10/2023, 12:22:12] [Wemo] [HeaterA] current mode [frost-protect].
[22/10/2023, 12:22:19] [Wemo] [HeaterA] sending update {"Mode":4,"SetTemperature":81}.
[22/10/2023, 12:22:19] [Wemo] [HeaterA] current mode [eco].
[22/10/2023, 12:22:21] [Wemo] [HeaterA] current mode [eco].
[22/10/2023, 12:22:27] [homebridge-doorbird] frontdoor: Motion detected.
[22/10/2023, 12:22:30] [Wemo] [HeaterA] sending update {"SetTemperature":84}.
[22/10/2023, 12:22:30] [Wemo] [HeaterA] target temperature [29°C].
[22/10/2023, 12:22:36] [Wemo] [HeaterA] sending update {"SetTemperature":68}.
[22/10/2023, 12:22:36] [Wemo] [HeaterA] target temperature [20°C].
[22/10/2023, 12:22:55] [Wemo] [HeaterA] target temperature [26°C].
[22/10/2023, 12:23:15] [Wemo] [HeaterA] target temperature [25°C].
[22/10/2023, 12:23:29] [homebridge-doorbird] frontdoor: Motion detected.
[22/10/2023, 12:23:39] [Wemo] [HeaterA] sending update {"Mode":1,"SetTemperature":77}.
[22/10/2023, 12:23:39] [Wemo] [HeaterA] current mode [frost-protect].
[22/10/2023, 12:23:42] [Wemo] [HeaterA] sending update {"Mode":4,"SetTemperature":77}.
[22/10/2023, 12:23:42] [Wemo] [HeaterA] current mode [eco].
[22/10/2023, 12:23:44] [Wemo] [HeaterA] current mode [eco].
[22/10/2023, 12:23:47] [Wemo] [HeaterA] sending update {"SetTemperature":66}.
[22/10/2023, 12:23:47] [Wemo] [HeaterA] target temperature [19°C].

I'm having the same issue with this plugin. I used to be able to control my heater from Homebridge, but no longer.

same issue, shows as 0.0 and No Response

same issue with heater! has anyone managed to get it to work with one of the beta versions of this plugin?


Native validation doesn't dismiss errors as the user corrects them

Provide a general summary of the issue here
React ARIA's "native" validation doesn't work like HTML5 native validation works in most browsers, which results in a significantly worse user experience.
🤔 Expected Behavior?
In most modern browsers, when an HTML5 validation error is already showing, the validation error will update in real time until the user has fixed it, and then the error will immediately go away without the user blurring the field.
😯 Current Behavior
When validationBehavior is set to "native" and a validation error is showing, the error will never go away until the user blurs the field. The error message also won't update if the native validation issue changes until the user blurs the field.
💁 Possible Solution
I think the useFormValidation component should have two modes:

A "lazy" mode which is initially active - in this mode it would only call state.commitValidation() in the change event handler
An "eager" mode which becomes active while a native validation error is showing - in this mode if would call state.commitValidation() in an input event handler

🔦 Context
No response
🖥 Steps to Reproduce
https://codesandbox.io/s/quirky-meitner-jl79fh?file=/src/App.js
Version
latest
What browsers are you seeing the problem on?
Firefox, Chrome, Safari
If other, please specify.
No response
What operating system are you using?
macOS Sonoma 14.3
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

The behavior of validating on blur for "native" validation is intentional since we thought it might be distracting to the user to display errors as they were entering their updated input value. Does implementing realtime validation like as shown here suffice instead?

Yep, I tested the native form in both Firefox and Chrome. After an error, the field switches to real-time validation and updates the error as the user types. Would love to see the same behavior with react-aria-component's Forms.

The goal isn't to match what browsers do by default - for that you don't even need React Aria at all, you can just use native inputs. Our goal is to improve the UX. Showing errors while the user is typing and has not completed their input yet is very distracting and can be misleading. An error might appear and disappear multiple times, for example while entering an email address, which could be very confusing for users. That's why by default we show errors only on "complete" input, which we determine from the blur event.
If you want different behavior, there is support for completely controlling the live error message using props, or using a library like react-hook-form.

The goal isn't to match what browsers do by default - for that you don't even need React Aria at all, you can just use native inputs

I'd agree that strictly matching the browser's behavior just for the sake of it isn't good. But I think the standard browser behavior in this case is just really nice.
To clarify, errors are only re-validated in real-time after a submit attempt that triggers a validation error (you can check the code sandbox above). When typing for the first time, no error messages will be displayed until the user submits the form.

An error might appear and disappear multiple times

With the native form behavior, the field stops re-validating in real time after valid input is typed in. So once the error disappears, it will not show up again until the user attempts to submit (or blur). IMO this behavior is super reasonable and very user-friendly.

Looks like all browsers implement this differently. Here's another example.

In Safari, errors clear immediately as soon as the user edits the value, even if the new value is still invalid. Revalidation only occurs when the user resubmits. This is a bit misleading since the value is still invalid even though it looks like it isn't. For example, if the error is "Please enter at least 8 characters" and there are two characters in the field, entering a third character hides the error even though it is still invalid.
In Chrome, the error message updates as you type after an error. If you type just "devon" into the email field and hit submit, you'll get an error: "Please include an @ in the email address". Then typing the "@" immediately changes the error to "Please enter a part following '@'". This is annoying because I'm not done typing yet.
In Firefox, the error doesn't disappear until the field becomes valid, but the error message does not update as you type. For example, typing one character into the min length field errors with "Please use at least 8 characters (you are currently using 1 characters)". Adding another character doesn't update the message.

None of these are ideal in my opinion. I think Safari's behavior is the least annoying, but still misleading. Firefox's behavior would be better if the error message was less specific (e.g. not including the current character count). We can't control that though (the default error messages come from the browser).
I think I'd want to continue revalidating on blur rather than only on re-submit, and not updating the error message live. Not sure whether it's better to hide the previous error immediately like Safari and potentially re-display it on blur, or just wait until the user is done editing to update it like we do today.

I agree that showing outdated error messages is not ideal. It's just a question of when exactly to hide/update the error. As I showed above, there isn't a clear standard across browsers for this. Each option has pros and cons.
I could see potentially implementing Safari's behavior of hiding the error message as soon as the user edits the value, but as I said before it's still not ideal if the value is actually still invalid and the error re-appears on blur. It could also cause additional layout shifts while typing.
If the error messages were less specific (e.g. "Please enter an email address" instead of "Please include an @ in the email address") then we could potentially wait until the input is valid to hide the message since it wouldn't change as you type, but we can't guarantee this since the messages depend on the browser.
Updating the error message live has a number of downsides:

As mentioned in the articles you linked, it's annoying to see error messages about incomplete input.
For screen reader users, hearing a potentially irrelevant error message after typing each character rather than the character you entered could be very confusing.
If the error message changes length, it could cause a lot of layout shifts when not shown as a floating overlay.

Another thing to consider is what to do with errors that come from server side validation. For example, say you enter an email address in a signup form and submit, and then the server says there is already an account with that email. There's not really a way to know when to hide that error except by re-submitting the form. Perhaps that's another reason to go with Safari's behavior of hiding as soon as the value changes. We currently clear server errors on blur. Would be nice if errors from client side and server side validation behaved somewhat consistently.

Following along here..is there a current suggested solution for showing validation errors in real time only once a field has been committed with an invalid value? Switching all fields/error messages to controlled does not seem like a tenable solution.
It seems that switching to validationBehavior="aria" allows for the desired ux except that it does not block form submissions when there is an invalid field.
Where does this leave us? Are we stuck choosing between one of these (imo) poor user experiences or re-implementing the whole of form validation ourselves?
My ideal requirements:

I can use uncontrolled form components, optionally defining constraints via validate().
Support for server validation
Submits are prevented when the form is invalid


Updated Readme.md

Remade Readme.md with some small changes ...

@sparsh-99 i commited some changes as you asked for graphs and defination.

yeah..
On Thu, Oct 1, 2020 at 12:26 PM Sparsh Garg<EMAIL_ADDRESS>wrote:

Merged #8 https://github.com/sparsh-99/Python-Package/pull/8 into
master.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/sparsh-99/Python-Package/pull/8#event-3827823919, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APVJABDB6GKGADZS5MHMFJ3SIQRYLANCNFSM4R722VIQ
.


add Sidekiq web UI to admin section; go max-Sidekiq with jobs

Description of changes
This adds the Sidekiq web UI to the admin section under /admin/sidekiq for some better insight into the job queues. It also turns all the ActiveJob job classes into Sidekiq::Worker classes.
My recommendation is to commit to Sidekiq as the backend's background job processor. Some benefits of making backend's jobs full-fledged Sidekiq::Worker classes:

more refined controls over when and how a job is executed
easier test configuration to prevent the actual scheduling of jobs during a test run into a development environment
increased visibility into the state of jobs through the Sidekiq administrative web UI

Issue Resolved

Fixes #405

Not done yet is adding any sort of visible link to the Sidekiq web UI. An admin would have to log in to the admin interface face and then type .../admin/sidekiq to get to it.

I figured out adding a link to ActiveAdmin! RTFM: Sometimes It Helps™
This now adds a "Background Jobs" link to the default ActiveAdmin menu which will open /admin/sidekiq in a new tab/window (because there are not links back to the OC web site from the Sidekiq web UI).


haveno: add package

fix https://github.com/NixOS/nixpkgs/issues/293842
based on https://github.com/NixOS/nixpkgs/pull/311314
based on https://github.com/tadfisher/gradle2nix/pull/62
draft in haveno/default.nix
nix-shell -p nur.repos.milahu.haveno

haveno is not working
the desktop app is working, but it fails to connect to seednodes
i dont know whether this is a problem with the client or a problem with the haveno network
the gui statusbar says: no seed nodes available
the seednode seems offline:
bugc27z7lqjgpwmhbuu3kuwoq2bhailj573r32jm5ydwrcqrwjtblnid.onion:1002
$ torsocks nc bugc27z7lqjgpwmhbuu3kuwoq2bhailj573r32jm5ydwrcqrwjtblnid.onion 1002
1720959904 ERROR torsocks[402405]: Host unreachable (in socks5_recv_connect_reply() at socks5.c:539)

$ curl --proxy socks5h://user$RANDOM@<IP_ADDRESS>:9050 http://bugc27z7lqjgpwmhbuu3kuwoq2bhailj573r32jm5ydwrcqrwjtblnid.onion:1002
curl: (97) Can't complete SOCKS5 connection to bugc27z7lqjgpwmhbuu3kuwoq2bhailj573r32jm5ydwrcqrwjtblnid.onion. (4)

the main version of haveno is broken by design
because the authors want to separate development from deployment
so im using the haveno-reto fork
which has seednodes and different keys
but otherwise its exactly the same code
is haveno a scam
it is possible that haveno is a scam, a waste of time
https://old.reddit.com/r/Monero/comments/1cqf02p/haveno_mainnet_documentation_released/

its already running on mainnet however not usable because there's no mods.

how do you propose to run a mainnet network from the official repository without being exposed to significant legal risk?

https://old.reddit.com/r/Monero/comments/1e60nc8/haveno_instances_experience/

Haveno Reto is the only running Haveno network that everybody knows about

https://github.com/haveno-dex/haveno/issues/1142

im building haveno from source, but i guess it requires more patching
maybe there are some more libs or bins hidden in jars
which dont run on nixos by default and cause silent errors
but i rather invest my time in basicswap

having a list of N seednodes is not "decentralized"
haveno is a pipe dream similar to openbazaar

haveno/readme.txt
future work
i already spent too much time on this...
if someone wants to get their hands dirty on this
i would recommend to first try a binary release of haveno-reto
maybe with steam-run, maybe with buildFHSEnv
maybe on a different linux distro like arch linux
to verify that haveno-reto is actually working
then i would modify gradle2nix so that my mkOverride function is applied to all jar files
maybe there are still some libs or bins that need to be patched
otherwise haveno silently fails... but that is an optimistic view
ping @Kreyren @linsui @emmanuelrosa @chayleaf @surfaceflinger @TanvirOnGH @shortwavesurfer2009 @nahuhh

Why don't you submit the code as merge request in nixpkgs? Makes it easier to review

Because they are banned.

I have my merge request submitted you can submit changes to my fork branch for me to merge them and submit them to nixpkgs for example.

i won't review

ok, good luck : )
i had the impression that the people i pinged
have an interest in getting haveno run on nixos
i have spent enough time on haveno already
only to see that it breaks on runtime...

interest in haveno running without issues and implemented in a sane and controlled way

Why the long unpack way? Should be handled via https://github.com/NixOS/nixpkgs/pull/272380

Why the long and hacky unpack phase

you mean mkOverride?
that is a missing feature of gradle2nix, see https://github.com/tadfisher/gradle2nix/pull/62#issuecomment-2218670780
i dont remember whether this works with gradle2nix v1
my version is based on gradle2nix v2 with better dependency resolution
but thats implementation detail
some of the jar files contain libraries and executables (libs and bins)
which require patching with patchelf
like i said, before spending more time on this
i would recommend to verify if haveno-reto is actually working
for example on arch linux

screw gradle2nix you should be using the provided gradle setup hook

oh man, im so happy that i "left" nixpkgs...
these discussions are so braindead
its a matter of taste which is better
nixpkgs prefers one derivation for all dependencies
i prefer one derivation per dependency
but thats implementation detail...
if haveno is broken, "the provided gradle setup hook" wont save you

or a problem with the haveno network

correct
wait a few days and try again with new version

yeah, i prefer to do my subjective shit
instead of wasting my time debating matters of taste
but hey, good luck porting reto to nixpkgs

haveno is not working
the desktop app is working, but it fails to connect to seednodes i dont know whether this is a problem with the client or a problem with the haveno network
the gui statusbar says: no seed nodes available
the seednode seems offline: bugc27z7lqjgpwmhbuu3kuwoq2bhailj573r32jm5ydwrcqrwjtblnid.onion:1002
$ torsocks nc bugc27z7lqjgpwmhbuu3kuwoq2bhailj573r32jm5ydwrcqrwjtblnid.onion 1002
1720959904 ERROR torsocks[402405]: Host unreachable (in socks5_recv_connect_reply() at socks5.c:539)

Your adjustments up to this point were correct, you should have just left the app running.
The seed nodes are under DoS. Your messages are normal. Just let the app run for 20-30 minutes.

the main version of haveno is broken by design
It's not broken, it's been running live on the Monero testnet (Stagenet) for 1.5 years and will always be there. It's all documented.

is haveno a scam
it is possible that haveno is a scam, a waste of time

Haveno-reto is not a scam. I have made over 30 trades there.

its already running on mainnet however not usable because there's no mods.

Mods are in the SimpleX chat or as arbs in the client if there are problems.
http://haveno-reto.com/
Haveno Reto is LIVE

any progress with haveno on nixos?

apparently the seed node is offline

currently i can reach 2 of 8 seed nodes

haveno-ping.sh

#!/usr/bin/env bash

# https://github.com/retoaccess1/haveno-reto/raw/master/core/src/main/resources/xmr_mainnet.seednodes

seednodes="$(cat <<'EOF'
z47tltuwytd5icqq4hni2ammvlugp6pcwqboeu7ngawruualxjjuu3ad.onion:9992(@anon3)
xephvvzd3orepnny7lbia4nkwie5t7wjivlvvz5lhbsck7ubavystead.onion:9992(@anon3)
c66xsfwbequrnytwlp7cz7oirs6q4grxmqyny7afuvc6r4e3cn2ynoqd.onion:1003(@anon1)
bugc27z7lqjgpwmhbuu3kuwoq2bhailj573r32jm5ydwrcqrwjtblnid.onion:1002(@anon2)
u6wwec5ddxswwyrz7rgzuiwowf33llab57y3xzmwwxvsofq2w4m6ihad.onion:1002(@anon4)
syslvhws23bczuabxtd6ekaprbc4pkel7yrrj7iq5awd5fhkjfzkcaqd.onion:1002(@anon5)
znoonk3vlow2ishmgnucjzuejwzabdfg2zcvg55ok63viohjohuw4cad.onion:1002(@anon6)
h7skqvtehrnhmsfnk3vgpej7nrn5qepla7a3ls27h7ctve7qr525baad.onion:1002(@anon7)
EOF
)"

# netselect is not working with torsocks
#torsocks netselect $(echo "$seednodes" | sed -E 's/\(@anon[0-9]+\)$//')
#torsocks netselect $(echo "$seednodes" | sed -E 's/\(@anon[0-9]+\)$//')

# ping is not working with torsocks
#torsocks ping $(echo "$seednodes" | sed -E 's/\(@anon[0-9]+\)$//')

total=$(echo "$seednodes" | wc -l)

timeout=30

while true; do
  res="$(
    pids=()
    while IFS=: read host port; do
      #echo $host $port
      echo asdf | timeout $timeout torsocks nc -v $host $port 2>&1 | grep -v 'ERROR torsocks' &
      pids+=($!)
    done < <(echo "$seednodes" | sed -E 's/\(@anon[0-9]+\)$//' | shuf)
    wait ${pids[@]}
  )"
  # Connection to $host (127.xxx.xxx.xxx) $port port [tcp/...] succeeded!
  #good=$(echo "$res" | grep ^Connection | wc -l)
  good=$(echo "$res" | grep -E '^Connection .* succeeded!$' | wc -l)
  # nc: connect to $host (127.xxx.xxx.xxx) port $port (tcp) failed: No route to host
  #bad=$(echo "$res" | grep ^nc | wc -l)
  echo $(date +%Y-%m-%dT%H:%M:%S%z) reachable seednodes: $good of $total
done

$ ./haveno-ping.sh
2024-07-30T20:47:21+0200 reachable seednodes: 0 of 8
2024-07-30T20:47:51+0200 reachable seednodes: 0 of 8
2024-07-30T20:48:22+0200 reachable seednodes: 0 of 8
2024-07-30T20:48:52+0200 reachable seednodes: 1 of 8
2024-07-30T20:49:23+0200 reachable seednodes: 1 of 8
2024-07-30T20:49:53+0200 reachable seednodes: 2 of 8
2024-07-30T20:50:24+0200 reachable seednodes: 2 of 8
2024-07-30T20:50:54+0200 reachable seednodes: 1 of 8

any progress with haveno on nixos?

No, why I think you are working on it.
Haveno is a Java package that runs on all major OS. IDK why NIXOS can't do that.

apparently the seed node is offline

Some seeds are gone or under DOS, but new ones are coming with v1.0.10, because everyone has to generate new .onion addresses for externalTor.

currently i can reach 2 of 8 seed nodes

The client won't connect to more than 2. After bootstrap you no longer need seed nodes. The network is P2P.

No, why I think you are working on it.

no. i stopped working on haveno.nix
because i found nanswap and changenow
which "just work" for small amounts
so i made this issue to share my progress

IDK why NIXOS can't do that.

because nixos has no FHS paths like /lib/ld-linux.so.2
so precompiled bins and libs must be patched with patchelf
see mkOverride in my haveno.nix

precompiled bins and libs

but generally, using precompiled files is a security risk
so ideally, more jar files should be built from source
or constructed from other nix packages (tor, monero, ...)
my haveno.nix kind-of works
but 2 weeks ago, it failed to connect to seed nodes
maybe i should have had more patience
maybe its a silent failure in haveno
somebody will find out... ; )


Cleanup openssl 1.1.1 workarounds

They were added in https://github.com/conda-forge/staged-recipes/pull/20432#issuecomment-1274243030, but now openssl 3 migration should have progressed enough so that they are not necessary anymore.
Checklist

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

@conda-forge-admin, please rerender

Tests are failing due to:
export PREFIX=/home/conda/feedstock_root/build_artifacts/bipedal-locomotion-framework_1670329826819/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho
export SRC_DIR=/home/conda/feedstock_root/build_artifacts/bipedal-locomotion-framework_1670329826819/test_tmp
import: 'bipedal_locomotion_framework'
Traceback (most recent call last):
  File "/home/conda/feedstock_root/build_artifacts/bipedal-locomotion-framework_1670329826819/test_tmp/run_test.py", line 2, in <module>
    import bipedal_locomotion_framework
  File "/home/conda/feedstock_root/build_artifacts/bipedal-locomotion-framework_1670329826819/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/lib/python3.10/site-packages/bipedal_locomotion_framework/__init__.py", line 1, in <module>
    from .bindings import *
ImportError: arg(): could not convert default argument 'mixed_velocity: manif::SE3Tangent<double>' in method '<class 'bipedal_locomotion_framework.bindings.ik.SE3Task'>.set_set_point' into a Python object (type not registered yet?)
Tests failed for bipedal-locomotion-framework-python-0.10.0-py310h83a6ccd_3.conda - moving package to /home/conda/feedstock_root/build_artifacts/broken
WARNING:conda_build.build:Tests failed for bipedal-locomotion-framework-python-0.10.0-py310h83a6ccd_3.conda - moving package to /home/conda/feedstock_root/build_artifacts/broken
TESTS FAILED: bipedal-locomotion-framework-python-0.10.0-py310h83a6ccd_3.conda

Probably this is a problem of the overconstraining the compiler version by pybind11, see https://github.com/ami-iit/bipedal-locomotion-framework/issues/386 .


Add user photo instead of user menu icon/1823

In this pull request:

Created new component AccountIcon (in the folder navigation-icons)(there was no posibility to add this element to exisisting file with NavigationIcons.constants)
Added tests to this implementation
Removed previous MUI element from NavigationIcons.constants
Fixed tests for NavBar and UserIcons component
Added immediate reload of the page after clicking on 'Update profile' button for changin the Avatar without user intervention

https://github.com/ita-social-projects/SpaceToStudy-Client/assets/127191734/d4bafa9f-65b4-4d32-a305-9ee8dacd10d9

As for me, font size should be a bit smaller for better displayment. What do you think?

As for me, font size should be a bit smaller for better displayment. What do you think?

Fixed) Thank you!


Implement chain registry rpc discovery

I suggest implementing the chain registry to find information regarding bitsong and find the available rpc nodes to which to make requests

We can add the registry as new package @bitsongjs/registry
var chain_info = registry.getChain('bitsong')
chain_info.getRandomRPC()

its important to add a kind of ping before returning the endpoint

its important to add a kind of ping before returning the endpoint

Yes, that's why I created #10

I thought about it, I think it is better not to directly integrate the chain-registry, it is only redundant, we will recommend using it and we will describe it in the documentation

Ok we can do it in a separate lib outside bitsongjs. I use the same concept with golang and it is very useful


Add hacky-patching target and make it easier to disable coreos-installer

Rather than including the temporary hacks for single-node clusters in the bootstrap-in-place-poc installer branch - which will then diverge from the bootstrap-in-place branch used for the openshift/installer#4482 PR - let's just do it with a Makefile target that patches and builds the installer.

This new version has a make installer target that patches and then builds the installer
Again - the goal is to get everyone working from the same installer branch

This new version has a make installer target that patches and then builds the installer
Again - the goal is to get everyone working from the same installer branch


parameter --image doesn't work

version: 1.0.2
IS:
calling wifi-password with -i or --image shows the password in the terminal.
SHOULD:
show the qr code as an image
SUGGESTION:
let the user specify a name and/or a path including the file extension(.jpeg, .png, etc.). If no extension is give or the extension is invalid, fall back to a default extension.
[janst@jan-pc wifi-password]$ wifi-password -i
ERROR: You need to run '/usr/bin/wifi-password' as root

[janst@jan-pc wifi-password]$ wifi-password --image
ERROR: You need to run '/usr/bin/wifi-password' as root

[janst@jan-pc wifi-password]$ sudo wifi-password -i
<shows password, erased for privacy reasons>

[janst@jan-pc wifi-password]$ sudo wifi-password --image
<shows password, erased for privacy reasons>```

if args.qrcode:
    args.no_password = True
    generate_qr_code(args.ssid, password, image=args.image)
    return

Problem seems to be here. the -i switch will only be checked and the image var set if the -q switch is also selected. If you pass both -q and -i it should write the file.

if args.qrcode:
    args.no_password = True
    generate_qr_code(args.ssid, password, image=args.image)
    return

Problem seems to be here. the -i switch will only be checked and the image var set if the -q switch is also selected. If you pass both -q and -i it should write the file.

I am also getting an error when I pass both flags ` wifi-password -i -q                                                                                1 ↵ n3rdly@private
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/qrcode-6.1-py3.9.egg/qrcode/image/pil.py", line 6, in
from PIL import Image, ImageDraw
ModuleNotFoundError: No module named 'PIL'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/bin/wifi-password", line 33, in
sys.exit(load_entry_point('wifi-password==1.0.3', 'console_scripts', 'wifi-password')())
File "/usr/local/lib/python3.9/site-packages/wifi_password-1.0.3-py3.9.egg/wifi_password/wifi_password.py", line 108, in main
File "/usr/local/lib/python3.9/site-packages/wifi_password-1.0.3-py3.9.egg/wifi_password/wifi_password.py", line 85, in generate_qr_code
File "/usr/local/lib/python3.9/site-packages/qrcode-6.1-py3.9.egg/qrcode/main.py", line 289, in make_image
from qrcode.image.pil import PilImage
File "/usr/local/lib/python3.9/site-packages/qrcode-6.1-py3.9.egg/qrcode/image/pil.py", line 8, in
import Image
ModuleNotFoundError: No module named 'Image'`

I am also getting an error when I pass both flags ` wifi-password -i -q                                                                                1 ↵ n3rdly@private
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/qrcode-6.1-py3.9.egg/qrcode/image/pil.py", line 6, in
from PIL import Image, ImageDraw
ModuleNotFoundError: No module named 'PIL'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/bin/wifi-password", line 33, in
sys.exit(load_entry_point('wifi-password==1.0.3', 'console_scripts', 'wifi-password')())
File "/usr/local/lib/python3.9/site-packages/wifi_password-1.0.3-py3.9.egg/wifi_password/wifi_password.py", line 108, in main
File "/usr/local/lib/python3.9/site-packages/wifi_password-1.0.3-py3.9.egg/wifi_password/wifi_password.py", line 85, in generate_qr_code
File "/usr/local/lib/python3.9/site-packages/qrcode-6.1-py3.9.egg/qrcode/main.py", line 289, in make_image
from qrcode.image.pil import PilImage
File "/usr/local/lib/python3.9/site-packages/qrcode-6.1-py3.9.egg/qrcode/image/pil.py", line 8, in
import Image
ModuleNotFoundError: No module named 'Image'`

@n3rdly same thing happened to me. Seems like the image module isn't bundled with the program. But you can just run pip3 install image and it fixes it.

@n3rdly same thing happened to me. Seems like the image module isn't bundled with the program. But you can just run pip3 install image and it fixes it.


React 16

Coverage increased (+100.0%) to 100.0% when pulling 821faf2bd66fb0e73ef0675b8cf34c9cd4dfe395 on react-16 into b1a325da216b72026abea211c72a999dd66ae1e8 on master.


Replace the border color in the LanguageSelect

Problem

The language select uses the shade scale instead of the opacity scale of the dark charcoal colors.
Description

The VSelectField border should be dark charcoal with 20% opacity. This allows us to simplify the code because both variants (yellow and not yellow) have the same border color.
https://github.com/WordPress/openverse-frontend/blob/5dacba4a40907885aed2b25678ec140736c9f159/src/components/VSelectField/VSelectField.vue#L5
This line can be removed, and replaced with border-dark-charcoal border-opacity-20.
Additional context

For more context and screenshots, look at the comments here: https://github.com/WordPress/openverse-frontend/pull/1936#issuecomment-1313861604
Implementation

[ ] 🙋 I would be interested in implementing this feature.

Can i work on the issue?

Sure, @Mayank-Jain-1! I'm assigning the issue to you.

I think, as after the change the class would not be changing it should be removed from :class and should be added to the class

In :class

<div
    class="relative m-0.5px box-content block w-fit overflow-hidden rounded-sm border text-sm focus-within:m-0 focus-within:border-1.5 focus-within:border-pink hover:border-dark-charcoal focus-within:hover:border-pink"
    :class="
      'border-dark-charcoal border-opacity-20'
    "
>

In class

<div
    class="relative m-0.5px box-content block w-fit overflow-hidden rounded-sm border text-sm focus-within:m-0 focus-within:border-1.5 focus-within:border-pink hover:border-dark-charcoal focus-within:hover:border-pink border-dark-charcoal border-opacity-20"
  >

Can you please review these pull requests and update me?


Bootstrap pod does not install plugins from the general spec, fails if plugin specific settings are configured in opensearch.yml

Description
If I want to provide an S3 API backed repository for opensearch snapshots, but not use S3 itself, I need to provide the s3.client.default.endpoint configuration. However this causes the bootstrap pod to fail as it doesn't have the plugin installed and does not recognise the setting.
Steps to reproduce

Install the latest version of the operator.
Deploy the following YAML:

apiVersion: opensearch.opster.io/v1
kind: OpenSearchCluster
metadata:
  name: my-first-cluster
spec:
  security:
    tls:
       http:
         generate: true
       transport:
         generate: true
         perNode: true
  general:
    httpPort: 9200
    serviceName: my-first-cluster
    version: 2.3.0
    pluginsList: ["repository-s3"]
    drainDataNodes: true
    additionalConfig:
      s3.client.default.endpoint: "example.s3.com"
  dashboards:
    tls:
      enable: true
      generate: true
    version: 2.3.0
    enable: true
    replicas: 1
    resources:
      requests:
         memory: "512Mi"
         cpu: "200m"
      limits:
         memory: "512Mi"
         cpu: "200m"
  nodePools:
    - component: masters
      replicas: 3
      resources:
         requests:
            memory: "4Gi"
            cpu: "1000m"
         limits:
            memory: "4Gi"
            cpu: "1000m"
      roles:
        - "data"
        - "cluster_manager"
      persistence:
         emptyDir: {}

Expected Outcome
I expect the bootstrap pod to also install all required plugins so that it can verify the additional config settings.
Actual outcome
Bootstrap pod fails with the following error:
[2023-02-12T11:27:04,774][ERROR][o.o.b.OpenSearchUncaughtExceptionHandler] [development-bootstrap-0] uncaught exception in thread [main]
org.opensearch.bootstrap.StartupException: java.lang.IllegalArgumentException: unknown setting [s3.client.default.endpoint] please check that any required plugins are installed, or check the breaking changes documentation for removed settings
        at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:184) ~[opensearch-2.5.0.jar:2.5.0]
        at org.opensearch.bootstrap.OpenSearch.execute(OpenSearch.java:171) ~[opensearch-2.5.0.jar:2.5.0]
        at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:104) ~[opensearch-2.5.0.jar:2.5.0]
        at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:138) ~[opensearch-cli-2.5.0.jar:2.5.0]
        at org.opensearch.cli.Command.main(Command.java:101) ~[opensearch-cli-2.5.0.jar:2.5.0]
        at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:137) ~[opensearch-2.5.0.jar:2.5.0]
        at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:103) ~[opensearch-2.5.0.jar:2.5.0]
Caused by: java.lang.IllegalArgumentException: unknown setting [s3.client.default.endpoint] please check that any required plugins are installed, or check the breaking changes documentation for removed settings
        at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:608) ~[opensearch-2.5.0.jar:2.5.0]
        at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:549) ~[opensearch-2.5.0.jar:2.5.0]
uncaught exception in thread [main]
        at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:519) ~[opensearch-2.5.0.jar:2.5.0]
        at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:489) ~[opensearch-2.5.0.jar:2.5.0]
        at org.opensearch.common.settings.SettingsModule.<init>(SettingsModule.java:170) ~[opensearch-2.5.0.jar:2.5.0]
        at org.opensearch.node.Node.<init>(Node.java:506) ~[opensearch-2.5.0.jar:2.5.0]
        at org.opensearch.node.Node.<init>(Node.java:356) ~[opensearch-2.5.0.jar:2.5.0]
        at org.opensearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:242) ~[opensearch-2.5.0.jar:2.5.0]
        at org.opensearch.bootstrap.Bootstrap.setup(Bootstrap.java:242) ~[opensearch-2.5.0.jar:2.5.0]
        at org.opensearch.bootstrap.Bootstrap.init(Bootstrap.java:404) ~[opensearch-2.5.0.jar:2.5.0]
        at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:180) ~[opensearch-2.5.0.jar:2.5.0]
        ... 6 more
java.lang.IllegalArgumentException: unknown setting [s3.client.default.endpoint] please check that any required plugins are installed, or check the breaking changes documentation for removed settings
        at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:608)
        at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:549)
        at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:519)
        at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:489)
        at org.opensearch.common.settings.SettingsModule.<init>(SettingsModule.java:170)
        at org.opensearch.node.Node.<init>(Node.java:506)
        at org.opensearch.node.Node.<init>(Node.java:356)
        at org.opensearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:242)
        at org.opensearch.bootstrap.Bootstrap.setup(Bootstrap.java:242)
        at org.opensearch.bootstrap.Bootstrap.init(Bootstrap.java:404)
        at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:180)
        at org.opensearch.bootstrap.OpenSearch.execute(OpenSearch.java:171)
        at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:104)
        at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:138)
        at org.opensearch.cli.Command.main(Command.java:101)
        at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:137)
        at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:103)```

Hi @dobharweim. You are correct that currently the operator does not install any plugins on the bootstrap pod. We may need to do that in the future. Or we could also look into not giving the bootstrap pod the additionalConfig.
As a workaround: Can you try to set spec.bootstrap.additionalConfig to set some dummy configuration? That should prevent the general additionalConfig from being added to the bootstrap pod.

@swoehrl-mw nice workaround.
I simply set bootstrap.additionalConfig."network.bind_host"="<IP_ADDRESS>" and that prevented passing the plugin settings to the bootstrap container :+1:

I also faced this issue and used the workaround mentioned in https://github.com/opensearch-project/opensearch-k8s-operator/issues/430#issuecomment-1525298903. When can we expect the Helm Chart release for the fix?


Downgrade Node.js

Readiness checklist

[ ] I added/updated tests.
[x] I ensured that the PR title is good enough for the changelog.
[x] I labeled the PR.

Description
Publishing is completely broken under Node.js 23. Linked issue is closed, but fix not yet published.

@sebbi08 stalker!


Fix Windows CI

To fix #299.

Personally I don't want to get in to the business of interpreting paths too much since it's already tricky enough. Stripping a leading // already feels quite dubious. Is there perhaps a way to fix the test or otherwise test for a different result on Windows? Or use different Path APIs on Windows?

Are you open to use a crate for UnixPath?

I'm not personally familiar with any such crates, is there no way to do this using the standard library?

I think using UnixPath is the cleanest way.
See https://github.com/rust-lang/rust/issues/100833.

Simplified a bit without using a crate; please review.


fixed typo in readme

There is a typo in the readme.

Thanks. :)

Looks like CI is failing. That is certainly unrelated but GitHub won't let me merge this PR until CI is green... sorry. :/
We can leave this PR open, maybe someone finds the time to fix our CI (or maybe I do, but that could take a while).

I will take a look at the nightly build too.

Instead of adding a merge commit, could you please rebase on top of current master?

did it

Thanks. :)
bors r+


Hosted Heroku link not working

Hosted Heroku link not working
Screenshots

Desktop:

OS: [Windows]
Browser [chrome]

have you uploaded database to server

getting the same error today...

heroku logs --tail --app your_app_name  run this command in git and check do you get any errors in deploy if yes then deploy it again with a correct manner

hey abhi, I'm using the api for this repository in one of my readme.md's. how would I go about doing what you just told me in my case? Thanks in advance.

that does not matter in you git cd to the root folder of your project and run the command to check logs of Heroku. if you find out error in logs. if you use any string in API which store in .env file then you need to add environment variables in heroku app also

the api used to work in my private repository README's before, but this week due to some reason it suddenly stopped working. I don't think I have heroku installed on my end so this is what I get when I try to run
heroku logs --tail --cam_sys-22
(my repo is named cam_sys-22).

go to youtube and watch a tutorial for this try deployment
again from start

Since we are using a free quota, every month we have a downtime of 1/1.5 day for which it won't be available.
I hope that clarifies system unavailability of the utility for some time every month

why not host it on some other provider then which is free? like netlify maybe
@shravan20

Can anyone pick this up for deployment in any of the service of your own?

Why not shift the code to render.com?

Why not shift the code to render.com?

This has been moved to GCP now, you can continue using it.

That's the reason why your IP for the URL for the project. However, the site doesn't works on handheld devices.
Also, from the website to README file, the forwarding URL is mentioned of heroku. I think that needs a change.

@ashishk1331 : I am able to access the website in mobile devices. Do you want to pick this issue up to update the documents with images instead of those URL so as to save unwanted API additional calls?
Or we can make it cacheable calls too, I think this is a better idea. Would you like to pick this up?

Yes sir. I would love to pick it up.
Also, I'm a bit confused about replacing API calls with images. So, Instead of displaying API endpoint you want to display pre-saved images for the same?
I can update the API url to match the current url.

@ashishk1331:
This part of the code is responsible for not caching the response in the github content and dynamically generating new quotes that is shown on the github readme. This part of the code explicitly set response header to expire the reponse within 0 seconds even if it has been cached, forcing it to invalidated.
You can introduce a field to skip this caching and completely skip the below header being set. This would ensure github cache not being invalidated.
res.header(
        "Cache-Control",
        "no-cache,max-age=0,no-store,s-maxage=0,proxy-revalidate"
        );
     res.header("Pragma", "no-cache");
     res.header("Expires", "-1");

I implemented public caching for 1 hour. However, time can be changed by modifying the hours variable before the header.
However, I think until and unless there is a change made by the user, we can cache the response for a year. Because README remains still for years.

Let's keep it optional, only if you pass a value in query params

Okay. So the query parameters namely cache and expire_after can do the trick,
cache = true | false
expire_after = 1 (hours)

Would generate the cache header with max age of 1 hour.
Something like this?

Folks we have moved it to vercel, closing this issue. Please do check the latest documentation changes.

Marking this as closed as it is fixed, by migrating the application to vercel


Version bump in version.hpp

Looks like TOML11_VERSION_PATCH in version.hpp should be updated from 0 to 1?

You are right. I updated the version.hpp and CMakeLists.txt. Thank you!


MDI focus

The MDI box isn't keeping focus and I keep accidentaly jogging with the arrow keys vs using the command history.  I almost think entering focus on the MDI box should be fully modal so you can't do anything else by accident.  I don't think this was a problem in my initial fix.  Happy to take a look myself if you've done something unintentionally here.

Note that focus is taken away from the MDI on tab changes or on pressing the Send button, has always been like that. The first is coded for, the second is default Windows behaviour? AFAICT your initial fix did not handle this differently.

would you be open to making it full modal?

Can look into that yes, not sure if it possible/easy to do for all possible scenarioes. Clicking on a button taking away focus is IIRC a property of the button as clicking on the override buttons does not take it away from the MDI - so fixing those should be easy. Perhaps tab change and DRO input will be easy as welll but for those I guess I need to save away the currently focused element if it is the MDI in order to refocus later.

I have added a test branch if you want to compile yourself.
MDI will no longer lose focus on a tab change or by pressing Send. When editing DRO values focus is not given back as this will be harder to change, hope this is ok.
Pressing the reset button will also result in the DRO loosing focus - it is not enough to set the button as not focusable, there is a lot going on behind the scenes when a reset is detected.

New release now up that includes the change in the test branch.


[Toopltip] Add disabled prop

[x] I have followed (at least) the PR section of the contributing guide.

Closes #21204

So this would also work with a Boolean? Like if I use something like
<Tooltip disabled={false} />

It will still show, until I change it to true, right?
Thanks for this PR :)

@DaniGuardiola Agree. The pull request doesn't solve the original problem in its form.

Oh thank you @DaniGuardiola , I didn't think in this case. But I already made some changes with useEffect and now, when the disabled prop change, is being verified the prop, if is true we close the tooltip.

@edumoreira1506 What do you think about forcing the closed state at the open state level? Basically providing an alternative to <Tooltip open={false} /> without the controlled and uncontrolled mix concern/warning.

I didn't understand @oliviertassinari . Could you explain better?

@oliviertassinari what you are describing sounds to me exactly like what the disabled prop is for, I'm not sure I understood what you meant.

I meant this:
index d21812392..569bdc705 100644
--- a/packages/material-ui/src/Tooltip/Tooltip.js
+++ b/packages/material-ui/src/Tooltip/Tooltip.js
@@ -207,7 +207,7 @@ const Tooltip = React.forwardRef(function Tooltip(props, ref) {
     state: 'open',
   });

-  let open = openState;
+  let open = disabled ? false : openState;

   if (process.env.NODE_ENV !== 'production') {
     // eslint-disable-next-line react-hooks/rules-of-hooks

I meant this in #21217 (comment):
index d21812392..569bdc705 100644
--- a/packages/material-ui/src/Tooltip/Tooltip.js
+++ b/packages/material-ui/src/Tooltip/Tooltip.js
@@ -207,7 +207,7 @@ const Tooltip = React.forwardRef(function Tooltip(props, ref) {
     state: 'open',
   });

-  let open = openState;
+  let open = disabled ? false : openState;

   if (process.env.NODE_ENV !== 'production') {
     // eslint-disable-next-line react-hooks/rules-of-hooks

Oh, that makes sense indeed.

We are giving up on the problem, for now. We have added the "Waiting for upvotes label"

so, how to disable a tooltip?

@Grawl see my last comment on the linked issue for a workaround


Vienna 3.6.1 doesn't open any window and shows no content

Today I opened Vienna 3.6.1, which I updated yesterday (or the day before) and was met with silence. The icon opened in the dock bar, but nothing was being shown. Using the options in the menu bar on top I was able to open windows one by one from the Window menu, but even when opened manually the only indicator of content I saw was the title bar indicating 514 items were unread.

I opened the gihub release page, downloaded 3.6.0 and was able to open the program normally and showing the content:

In case it helps, here is a log of the console filtering for the word vienna opening the bad 3.6.1 version, and here is the same kind of log using version 3.6.0.

Which macOS version are you running?
The only two lines I see are these:
Unknown class NSSearchToolbarItem in Interface Builder file at path /Users/gradha/Applications/Vienna 3.6.1 bad.app/Contents/Resources/Base.lproj/MainWindowController.nib.
<NSBackgroundActivityScheduler: 0x600003248990>: Invalid value for interval (0.000000). The value must be >= 1.

Mojave 10.14.6 (18G6042).

I have done a quick test. I can confirm the problem and it appears to be caused by the background activity scheduler, when the automatic refresh is set to “manual”.

I can also confirm that the other line mentioned above (Unknown class NSSearchToolbarItem in Interface Builder file) appears to have no functional impact as far as I can tell. The search toolbar items works on El Capitan as it is supposed to.


Staking: allow nomination mirroring

A simple solution to allow application such as https://forum.polkadot.network/t/nomination-pool-controlled-by-a-smart-contract/2436/2 would be to tweak Nomination::targets to be, instead of a plain Vec<AccountId>:
enum NominationTargets {
    /// Directly nominating thyself.
    Direct(Vec<AccountId>),
    /// Mirroring the nomination preference of another `AccountId`.
    Mirror(AccountId)
}

This will possible increase the weight of the election snapshot, but given that we already read most nominators' data anyway, it is mostly going to be overlay overhead, not actual IO read.
Chaining should probably not be allowed.
If you are Mirror(Alice) and Alice is anything but Direct(_), then you are not taken into account and are basically in an "inactive" state.
This sounds not too hard, and enables a bunch of things, but going back to the original issue, the real solution is keep direct nominations raw and simple, and build such functionalities into pools.

This issue has been mentioned on Polkadot Forum. There might be relevant details there:
https://forum.polkadot.network/t/nomination-pool-controlled-by-a-smart-contract/2436/4

And what triggers the smart contract?

Either an on-chain scheduler or a system where anyone can post a transaction to trigger the update, paying the (small) gas for that.

Either an on-chain scheduler or a system where anyone can post a transaction to trigger the update, paying the (small) gas for that.

Indeed, but this brings up the topic of smart-contracts on the relay chain? We discussed this internally and concluded to not pursue it any further. Once staking lives in its own parachain, something like this can easily be done via contracts.


DX: Fix SCA with PHPMD

I found the SCA workflow here using PHPMD very useful and applied it in one of my projects. However, I noted that the actual fixing part with PHPMD is never run. I checked with the actions runs here and it seems the same is true. So after a lot of trial and error fixing the syntax, I found a solution at least working for me and wished to share here.
The problems are:

The results of git diff with grep is never saved to $GITHUB_ENV, even though there are changed PHP files. This is maybe because of the || true part.
Check - phpmd step has a condition to run if: ${{ github.env.CHANGED_PHP_FILES }}. The problem here is that the github context does not have the env property. Rather, the env is a context of its own. See https://docs.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#env-context

thanks for the research :+1:
lets see what happens when we run the checks :)

Coverage remained the same at 91.561% when pulling 2eec39a7bcebc61f8f0db0c1fdd518e351564f23 on paulbalandan:phpmd-sca into d7c45649d0590c5345d188faf0706106dfbf539d on FriendsOfPHP:2.19.

The 2nd commit shows that phpmd is now being called whenever there are changed PHP files, so the added sample file can now be deleted.

can you re-add the test file again to show how phpmd is kicking off now?

I think the failing CI is unrelated, or not?

i think we are ready to merge @paulbalandan ? if so, pls drop the test file and if CI still green, let's merge

Thank you @paulbalandan.


AttributeError: 'Version' object has no attribute 'major'

there doesn't seem to be a valid attribute major from packaging.
https://github.com/microsoft/DeepSpeed/blob/1ba3e8e3364049ecfc647aae4715ec9441676c51/deepspeed/__init__.py#L36
Was able to install it from source after commenting line #41 of deepspeed/init.py
this is also an issue with the pip version.

The authors didn't specify the version requirement for the packaging package. In my case I was able to fix the issue by pip install packaging --upgrade, which installed the version 21.0 of packaging.

this is when compiling master. Perhaps packaging version should be mentioned.


Allow "Insert Cursor" keybinding to be configurable

VSCode Version: 1.7.1
OS Version: OSX Sierra

It does not appear that the Insert Cursor keybinding can be configurable. I would like to map it to the Sublimetext equivalent which is cmd+click
Thanks.

AFAIK, we don't have Click support in keybindings.

Let's track in #3130


Bug: Selection changes incorrectly when focus is before anchor across two text nodes with different font colors when setting a font color

Lexical version: 0.7.5
Steps To Reproduce

Create two text nodes.
Set the color of the second node to a color
Then select right to left and select the entire second node and half of the first node.
then select a new color on the color picker

The current behavior
https://user-images.githubusercontent.com/69976884/215290831-23e783b6-3881-49f3-90cc-597744c758de.mov
The expected behavior
The selection should remain consistent and not change when the color changes.

@thegreatercurve Hey I'm new to open source, and would love to work on this issue. I hope you can assign it to me.

Since the bug is still not resolved I will try to solve it

sure 👍


We can only get the four coordinates of the convex hull, how to judge the direction of the QR code

Hi there, I have the same problem. The older implementations where [0]-Element was tied to "upper" left QR-Code corner.

Ok, #39 has a fix. I manually applied it and now it works (2 lines of code).


Save coordinates on Service Requests created through Open311

@amirozer done in https://github.com/govflow/govflow/commit/fb8cf67ad8eea3d46065ad093eaf044e666a7449
Please see the code and the tests to ensure it covers what you need. You can grab a version of this in release 0.0.16-alpha on npm.


Missing folders: /public/api/pokemon and /public/assets/lib/semantic

For the later one since its just semantic you can download it and put it in place, but for /api/pokemon that is something that should be included here, and without it i don't think that this can work

the semantic entry in the bower.json is missing

"/public/api/pokemon" is not a missing folder - its the api of this app - will show you an error if the inventory.json is missing

/api/pokemon is just an api endpoint, so that shouldn't require an update, but @eratio08 is correct. The semantic-ui entry was missing from the bower.json and has been added in v0.0.2. I'm closing this, but create another issue if the /public/api endpoint continues to be an issue.

The Api error results from the missing inventory.json - not a real error

Perfect. We'll just assume that's solved, then.


Fixing misuse of the standard math library (performance audit)

Please refer there for context: https://github.com/PX4/Firmware/pull/6829#issuecomment-286920967.
The root of the problem is an improper use of the math library. The templated classes were implicitly making assumptions about the scalar type. For example, in many places the library used to make references to ::sinf or ::sqrt, essentially assuming that the scalar type is float or double, respectively.
Normally, this problem would be really easy to fix; consider the following two of the most obvious approaches:

Replace all references to the C standard library with alternative references to the C++ standard library by adding std:: where necessary. This approach is pretty straightorward, but lacks in two ways:

A lot of code modifications.
No proof against re-occurrence of the same problem in the future. This one could be solved by means of advanced static analysis though, but it would be slightly outside of the scope right now.

Shadow the C math functions with C++ alternatives using the using directive. This approach requires minimal changes to the codebase and is absolutely resilient to re-occurrence of the problem in the future: in order to break things again, a developer would have to explicitly specify the desired scope of the referred definition, e.g. ::sin, which people normally don't do.

N.B.: high integrity coding standards, such as MISRA C++ or HIC++, consistently prohibit the use of the C standard library. This specific case is a good anecdote in support of that recommendation.
The second solution from the above have been implemented here and tested against the unit tests (they all pass). Sadly, my attempt to test it with NuttX was unsuccessful due to the sad state of its C++ standard library. It turned out that instead of providing correct overloads in adherence to the C++ specification, it simply imports the C definitions into the std namespace. Consider fabs:
  using ::fabs;

That's it. This is what should have been there according to the standard:
float       fabs(float);
double      fabs(double);
long double fabs(long double);

The problem I described in the PX4 performance audit thread cannot be fixed right now without the loss of generality in the Matrix library. There are two solutions:

Partially fix the NuttX C++ standard library. This is not something people do overnight.
Implement the missing math functions manually in the Matrix library. Here's an idea how we can do that:

inline float       fabs(float x)       { return ::fabsf(x); }
inline double      fabs(double x)      { return ::fabs(x); }
inline long double fabs(long double x) { return ::fabsl(x); }

And so on. The list of missing functions is not large, I believe we only need about 10 or so.

Coverage remained the same at 100.0% when pulling 14e9465587b088b4d9a49a8945c7ee1c1963c21a on performance_audit into cf924956d7d62ce18bfc4f8441e9177ddb69c0dc on master.

Coverage remained the same at 100.0% when pulling 8ef25276769127595c8cf27c2ee026a2954173cc on performance_audit into cf924956d7d62ce18bfc4f8441e9177ddb69c0dc on master.

I have applied the second workaround described above, now it works well with NuttX.

Coverage remained the same at 100.0% when pulling 41fe2cd2a6d1c00c39e1e06e6326beb3da450373 on performance_audit into cf924956d7d62ce18bfc4f8441e9177ddb69c0dc on master.

Thanks for the thorough explanation Pavel. What about situations where the return is assigned to a float, but the input is a double. Wouldn't it be better to explicitly call the float version?

Not always. Use of double suggests that a higher precision is needed than what float can provide, so converting to float before the computation may have adverse effects on numerical precision.

Just waiting on feedback from @davids5 , then I think we are good to merge.

@jgoppert LTGM

@pavel-kirienko do you know any tools that would help us work towards MISRA C++ or HIC++? I haven't looked recently, but the MISRA options I've seen so far have been quite expensive.

@dagar there is SciTools Understand, it's free for open source, but it tends to produce heaps of false positive. A bit unfriendly but usable.


Instantiable tuple labels

closes https://github.com/microsoft/TypeScript/issues/44939
A somewhat big drawback of this feature is that an instantiated label is only usable if it instantiates to a string literal type. This means that instantiations that end up being template literal types and even unions of strings are just discarded. I'm open to discussing other possible designs.
I think it's a reasonable tradeoff since this feature is primarily an editor experience improvement. Labels don't have any effect on type checking itself.

@typescript-bot pack this

@typescript-bot pack this

@DanielRosenwasser this is still a draft that I put out since I wanted to share this with some people who asked for this feature.
Since then I tested this more and it's not working correctly yet for some recursive cases etc. I have some work in progress locally that fixes some of those issues. While investigating them I learned a bunch of new things about how type references, mappers, etc are implemented under the hood 😉
Those learnings make it harder to implement this feature - or to rephrase: I've hoped for a simpler implementation but at the end of the day I can't avoid instantiating those labels sooner. This raises some data structure/internal API questions. Since those things are also consumed programmatically I'd like to ensure that an implementation design won't be too disruptive for those consumers. I have some ideas/some open questions related to that. If the team would be open to discussing those concerns before I sit down to implement an enhanced proof of concept - I would highly appreciate it. It would be also quite nice if the team could comment on general level of your interest in this feature :)

Yeah, I think that's why I packed it - I want to gauge appetite/interest. Of course, even if we're interested, a big part of this will hinge on the complexity/maintainability/limitations of the implementation.

Actually, I'm having a hard time imagining a reasonable implementation of InsertTupleNames. I think you have some very basic first-order types that are being used as labels, but I still don't quite get the motivation - what people want to write, how feasible/practical it is, and whether it's worth it.

I can't truly comment on InsertTupleNames right now - would have to read that issue more carefully. The motivating example that I'd like to make work is close to something like this (TS playground):
type ToNamedTuple<
  TAbiParameters extends readonly { name: string; type: unknown }[],
  Results extends any[] = [],
> = TAbiParameters extends readonly [
  infer Head extends { name: string; type: unknown },
  ...infer Tail extends readonly { name: string; type: unknown }[],
]
  ? ToNamedTuple<
      Tail,
      [...Results, `${Head['name']}`: Head['type']]
    >
  : Results

type Result = ToNamedTuple<
  [
    { name: 'foo'; type: string },
    { name: 'bar'; type: bigint },
    { name: 'baz'; type: number },
  ]
>

This is definitely implementable, just a matter of juggling type parameters and things.
In the beginning, I thought that .mapper would always be there and that it would be able to resolve all type parameters. That would allow me to have those labels pretty lazily evaluated. That's not how it works though.
Then I tried to store a global mapping between the types and mappers but that didn't pan out because it turned out that types are heavily cached backed on their type arguments. So that made the labels to "leak" between tuple instantiations with the same element types.
There is no good caching unit that would allow me to keep labels/mappers around - other than the type itself. Currently labels of tuples are Nodes (well, Identifiers). Changing that labeledElementDeclarations' type to (Node | Type)[] would be bizarre and I discarded this option right away.
Types created based on template literal types at labels positions should be somehow included in the type's ID. This way new types could be created based on different label instantiations and things would "just work". This has an obvious drawback of creating more tuple types with the same element types. I don't think that's a big issue from the memory PoV but the checker should learn how to compare such tuple tupes effectively - labels are purely decorative and they shouldn't affect the assignability rules between same element tuples.
Alternatively, wrapper types could be introduced with .target that would reference the underlying tuple type that would hold the actual element types and the wrapper would only be used to store the instantiated labels. I'm not yet sure how I feel about it. On one level it feels like a complication but it has some potential of making the implementation simpler at the expense of having one extra type of a type to care about. Note that I already found a potential use case for an alternative "tuple type" in the past - currently reversed mapped tuple types have subtle differences from reverse mapped object types since they are instantiated at different times. Introducing a ReversedTupleType (or something akin to that) could potentially fix this by making it possible to defer their instantiations so they could behave in the same way as object ones.

Got some other motivating examples for you (potentially). I ran into a similar issue where I think I could benefit from the changes in this PR and from something such as InsertTupleNames - as I understand it.
Here are the examples:

Retyping the parameters of a function. I think I have an immediate use case for this here.
type Result = RetypeParameters<[a: string, b: number], [number, string]> // [a: number, b: string]

Named tuple to Object Type. Kind of the reverse of your example.
type Result = ToObject<[a: string, b: number]> // { a: string, b: number }

Using infer over named tuples. (Not sure if this will be addressed by your PR, but my thinking is this would allow for the above two to be easy to implement?)
type InferNames<NamedTuple extends any[]> =
    NamedTuple extends [infer Name: any, ...infer Rest] ?
    [Name, ...InferNames<Rest>] : never

What do you think?

Apologies if this is not the right avenue to post any of these. Happy to move over to a new issue, or to the original issue your PR is solving. Thanks for driving this forward!

Looking forward to this feature