Support export * as _ syntax

Description
As a developer, many plugins etc autogenerate files which we have no control over. Some of them use export * as syntax. This plugin does not support that syntax, therefore it's useless in those scenarios.
Suggested solution
Support the export * as __ syntax.
Additional context
Error: [vite:dts] The "export * as ___" syntax is not supported yet; as a workaround, use "import * as ___" with a separate "export { ___ }" declaration

Ran into this using typechain
https://github.com/dethcrypto/TypeChain/issues/900
Validations

[X] Read the FAQ.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

This seems to be a limitation of @microsoft/api-extractor.

This seems to be fixed by https://github.com/microsoft/rushstack/blob/main/apps/api-extractor/CHANGELOG.md#7470

作者为啥不升级呢？这是个很严重的功能问题

Fix by 7a5fe9a55d8503f4af88e935f4b7d3399a4a832e.

@qmhc @JeanBarriere thank you!


Error While resolving toolchains for target bazel_tools//tools/jdk:proguard_whitelister : No matching toolchains found for types bazel_tools//tools/python:toolchain_type.

https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3497#018c231f-7470-4e70-805d-863681b3a38c
Platform : Windows, Ubuntu, MacOS
Logs:
ERROR: /private/var/tmp/_bazel_buildkite/fc9132f32b5702a51ffbcfe66976a1f8/external/bazel_tools/tools/jdk/BUILD:133:10: While resolving toolchains for target @@bazel_tools//tools/jdk:proguard_whitelister (2af9b6f): No matching toolchains found for types @@bazel_tools//tools/python:toolchain_type.
To debug, rerun with --toolchain_resolution_debug='@@bazel_tools//tools/python:toolchain_type'
If platforms or toolchains are a new concept for you, we'd encourage reading https://bazel.build/concepts/platforms-intro.
(03:11:07) ERROR: Analysis of target '//docs:defs' failed; build aborted: Analysis failed

Steps:
git clone https://github.com/bazelbuild/rules_proto.git
git reset f9b0b880d1e10e18daeeb168cef9d0f8316fdcb5 --hard
export USE_BAZEL_VERSION=48eb0236b2f65babf3dd9c314069774a78b629a3
bazel build //...

CC Greenteam @fweikert

Hi @alexeagle, Can you take a look on the above failures. Thanks!


1.1 Schema Support

Resolves #139
This PR adds functionality support for the new command to generate manifests using the 1.1 schema.
Changes:

Addition of a PromptListOfClassType() method that shows a selection menu to allow users to add, edit, or remove items from fields that are a list of objects. (i.e. Agreements, ExpectedReturnCodes).
Creating custom partial class for ReleaseDateString and AgreementContent as a workaround for inconsistencies in the generated model based on the schema.
Added functionality for prompting boolean type fields.
Updating the FieldValidation.ValidateProperty() method to handle long type validation and not just string validation.
Added ResourceStrings for new fields in 1.1 schema.

Microsoft Reviewers: Open in CodeFlow

/azp run


fix: fix case sensitivity on Linux

fix this error:
 ERROR  Failed to compile with 3 errors

These dependencies were not found in node_modules:

* ../views/components/avatarupload
* ../views/components/countto
* components/Charts/lineMarker

thx


Dark mode not sticking on Brave Browser

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[ ] I have tried the npm run clear or yarn clear command.
[ ] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[ ] I have read the console error message carefully (if applicable).

Description
Dark mode is not being "remembered" by Docusaurus when I use Brave Browser upon page refresh.
Reproducible demo
No response
Steps to reproduce
I discovered this while on Pomerium's docusaurus, but it's the same on https://docusaurus.io/docs
Step 1: Toggle dark mode.
Step 2: refresh the page (I use F5)
Step 3: See the page is no longer dark mode.
Expected behavior
It used to retain dark mode unless I completely clear cache/cookies.
Actual behavior
I refresh the page and it's now light mode.
For what it's worth, this seems to be Brave Browser only. I tested on Chrome and that's fine. Additionally, if I set to dark mode and click around documentation, it retains dark mode until refresh (or I enter docs again).
Your environment

Public source code:
Public site URL:
Docusaurus version used: Latest
Environment name and version (e.g. Chrome 89, Node.js 16.4): Brave: Version 1.63.161 Chromium: 122.0.6261.57 (Official Build) (64-bit)
Operating system and version (e.g. Ubuntu 20.04.2 LTS): Microsoft Windows 10 Pro, Version 10.0.19045 Build 19045

Self-service

[ ] I'd be willing to fix this bug myself.

I downloaded Brave on macOS and it works perfectly fine on both our site, and on https://www.pomerium.com/docs
If it doesn't work, it is either a Brave Ubuntu bug (unlikely), or you turned on some privacy/security setting that prevents us from using localStorage, or you use browser extensions that prevent it. If you don't know how to fix it, I'd suggest reinstalling Brave from scratch and disabling all extensions.
Ask a colleague to test under Brave and you'll see it works fine for them.


Added code owners

Adding code owners as mandatory approvers

Dows anyone know why Github says that the file is not correct? Invalid owner on line 1


http包下的示例跑不起来

http/aggregation_svc/main.go
fmt.Println("--- start ---")
err := svc.ProxySvc.CreateSo(c, false)
fmt.Println(err)
fmt.Println("--- end ---")

运行报错：
[GIN-debug] GET    /createSoCommit           --> main.main.func1 (3 handlers)
[GIN-debug] GET    /createSoRollback         --> main.main.func2 (3 handlers)
[GIN-debug] Listening and serving HTTP on :8003
--- start ---
rpc error: code = Unavailable desc = connection closed
--- end ---

ignore me,  follow this project https://github.com/opentrx/seata-golang, run compile and start TC first.


Update github-enterprise-audit-log.md

Feature request

@cwatson-cat The intent of the change in this PR seems to be not to fix the content but to raise an issue. You might want to close this PR and address the issue in a new PR in the private repo.


Import Resource gives TypeError: field() got an unexpected keyword argument 'alias'

I've just installed frictionless with pip on my Mac M2 Os Ventura 13.2.1.
The first exercise I try leads to this error:
Python 3.9.12 (main, Apr  5 2022, 01:52:34)
[Clang 12.0.0 ] :: Anaconda, Inc. on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from frictionless import Resource
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/technical/opt/miniconda3/lib/python3.9/site-packages/frictionless/__init__.py", line 1, in <module>
    from .actions import describe, extract, transform, validate
  File "/Users/technical/opt/miniconda3/lib/python3.9/site-packages/frictionless/actions/__init__.py", line 1, in <module>
    from .describe import describe
  File "/Users/technical/opt/miniconda3/lib/python3.9/site-packages/frictionless/actions/describe.py", line 3, in <module>
    from ..resource import Resource
  File "/Users/technical/opt/miniconda3/lib/python3.9/site-packages/frictionless/resource/__init__.py", line 1, in <module>
    from .resource import Resource
  File "/Users/technical/opt/miniconda3/lib/python3.9/site-packages/frictionless/resource/resource.py", line 39, in <module>
    class Resource(Metadata):
  File "/Users/technical/opt/miniconda3/lib/python3.9/site-packages/frictionless/resource/resource.py", line 194, in Resource
    _dialect: Union[Dialect, str] = attrs.field(factory=Dialect, alias="dialect")
TypeError: field() got an unexpected keyword argument 'alias'
>>>

Any ideas? Thanks!

I am experiencing the same problem on Intel Mac with Anaconda Python 3.10

Ok so it seems frictionless requires the latest attrs 22.2.0 but the version that was previously installed by conda was 22.1.0
Probably frictionless needs to specify the higher version of attrs is required.


Authentication failed

tried with multiple emails and passwords cant get the login to work.  Some passes had ! some had ? also tried passwords with just letters and numbers, also tried emails that ended in .edu and some with .com nothing working

Can set the log level to Trace and log mode to Print and post the logs here?

This was fixed by #2.


Implement Bit Operations (Initial)

Description
In order to have things plumbed into the ALU, we also need the operations on sequences of bits to be implemented. It needs to provide the following:

swap
&
|
~
^
>>
<<
>>>
ror
rol
Count leading zeros
Index of least-significant 1-bit
Parity check
Count 1 bits
Test

This looks good to me!

The above makes sense, but I just want to be clear that we will have to do specific type conversions to get the wrapping behavior we need the specific underlying unsigned integer type.
It may also not make sense to use U256 here. It may be implemented as two felts, which is overhead we do not need when the biggest integers we care about for now are u128, so we can safely convert to and from that as a generic representation.


Reduce total deposited on refund

Summary
Concerning the refund function not decrementing total deposit when called.

A test is definitely missing.


Project level Gerrit settings

Project level Gerrit settings

Plugin settings are now project level.  Seamlessly switch between projects housed on separate Gerrit servers.
Compatibility: Previously existing settings are loaded as the application level default.
When opening a project for the first time, application level default settings are used.
Added buttons for Save as Default Settings and Load Default Settings.

gerrit-intellij-plugin-1.2.6-203.zip
Attaching binary for testing


[SDE-1816] new command upgrade roles from cluster

Related Issues:
https://issues.redhat.com/browse/SDA-6407
https://issues.redhat.com/browse/SDE-1816
What
Setting up a new command to upgrade acc/operator roles/policies
Why
Easier flow for the client to use when roles are linked to a cluster
Steps to check changes
Running under upgrade roles without standard suffix acc roles
./rosa upgrade roles -c gdb-test --mode auto --version=4.10.36
I: Ensuring account role policies compatibility for upgrade
I: Starting to upgrade the policies
? Upgrade the 'sde-1816-6-support' role policy latest version (4.11) ? Yes
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-6-support-policy' to latest version
? Upgrade the 'sde-1816-6-installer' role policy latest version (4.11) ? Yes
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-6-installer-policy' to latest version
? Upgrade the 'sde-1816-6-controlplane' role policy latest version (4.11) ? Yes
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-6-controleplane-policy' to latest version
? Upgrade the 'sde-1816-6-worker' role policy latest version (4.11) ? Yes
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-6-worker-policy' to latest version
I: Starting to upgrade the operator IAM roles and policies
? Upgrade each operator role policy to latest version (4.11)? Yes
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-6-openshift-image-registry-installer-cloud-credentials' to version '4.11'
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-6-openshift-ingress-operator-cloud-credentials' to version '4.11'
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-6-openshift-cluster-csi-drivers-ebs-cloud-credentials' to version '4.11'
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-6-installer-openshift-cloud-network-config-controller-c' to version '4.11'
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-6-openshift-machine-api-aws-cloud-credentials' to version '4.11'
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-6-openshift-cloud-credential-operator-cloud-credential-' to version '4.11'
? Create the 'gdb-test-e3t7-openshift-cloud-network-config-controller-cloud-cr' role? Yes
I: Created role 'gdb-test-e3t7-openshift-cloud-network-config-controller-cloud-cr' with ARN 'arn:aws:iam::765374464689:role/gdb-test-e3t7-openshift-cloud-network-config-controller-cloud-cr'
I: Waiting for operator roles to reconcile

Running under upgrade roles
./rosa create account-roles --mode auto --version=4.9 --prefix=sde-1816-4 -y
I: Logged in as 'gbranco.openshift' on 'https://api.stage.openshift.com'
I: Validating AWS credentials...
I: AWS credentials are valid!
I: Validating AWS quota...
I: AWS quota ok. If cluster installation fails, validate actual AWS resource usage against https://docs.openshift.com/rosa/rosa_getting_started/rosa-required-aws-service-quotas.html
I: Verifying whether OpenShift command-line tool is available...
I: Current OpenShift Client Version: 4.11.2
I: Creating account roles
I: Creating roles using 'arn:aws:iam::765374464689:user/gbranco'
I: Created role 'sde-1816-4-ControlPlane-Role' with ARN 'arn:aws:iam::765374464689:role/sde-1816-4-ControlPlane-Role'
I: Created role 'sde-1816-4-Worker-Role' with ARN 'arn:aws:iam::765374464689:role/sde-1816-4-Worker-Role'
I: Created role 'sde-1816-4-Support-Role' with ARN 'arn:aws:iam::765374464689:role/sde-1816-4-Support-Role'
I: Created role 'sde-1816-4-Installer-Role' with ARN 'arn:aws:iam::765374464689:role/sde-1816-4-Installer-Role'
I: To create a cluster with these roles, run the following command:
rosa create cluster --sts

./rosa create cluster --sts --mode auto --yes
I: Enabling interactive mode
? Cluster name: gdb-49-2
? OpenShift version: 4.9.49
W: More than one Installer role found
? Installer role ARN: arn:aws:iam::765374464689:role/sde-1816-4-Installer-Role
I: Using arn:aws:iam::765374464689:role/sde-1816-4-ControlPlane-Role for the ControlPlane role
I: Using arn:aws:iam::765374464689:role/sde-1816-4-Worker-Role for the Worker role
I: Using arn:aws:iam::765374464689:role/sde-1816-4-Support-Role for the Support role
? External ID (optional):
? Operator roles prefix: gdb-49-2-d8s2
? Multiple availability zones (optional): No
? AWS region: us-east-1
? PrivateLink cluster (optional): No
? Install into an existing VPC (optional): No
? Select availability zones (optional): No
? Enable Customer Managed key (optional): No
? Compute nodes instance type: m5.xlarge
? Enable autoscaling (optional): No
? Compute nodes: 2
? Machine CIDR: <IP_ADDRESS>/16
? Service CIDR: <IP_ADDRESS>/16
? Pod CIDR: <IP_ADDRESS>/14
? Host prefix: 23
? Encrypt etcd data (optional): No
? Disable Workload monitoring (optional): No
I: Creating cluster 'gdb-49-2'
I: To create this cluster again in the future, you can run:
   rosa create cluster --cluster-name gdb-49-2 --sts --mode auto --role-arn arn:aws:iam::765374464689:role/sde-1816-4-Installer-Role --support-role-arn arn:aws:iam::765374464689:role/sde-1816-4-Support-Role --controlplane-iam-role arn:aws:iam::765374464689:role/sde-1816-4-ControlPlane-Role --worker-iam-role arn:aws:iam::765374464689:role/sde-1816-4-Worker-Role --operator-roles-prefix gdb-49-2-d8s2 --region us-east-1 --version 4.9.49 --compute-nodes 2 --compute-machine-type m5.xlarge --machine-cidr <IP_ADDRESS>/16 --service-cidr <IP_ADDRESS>/16 --pod-cidr <IP_ADDRESS>/14 --host-prefix 23
I: To view a list of clusters and their status, run 'rosa list clusters'
I: Cluster 'gdb-49-2' has been created.
I: Once the cluster is installed you will need to add an Identity Provider before you can login into the cluster. See 'rosa create idp --help' for more information.
Name:                       gdb-49-2
ID:                         1vg49g0vh6977voife3eoef3qp0ssa9f
External ID:
Control Plane:              Customer hosted
OpenShift Version:
Channel Group:              stable
DNS:                        gdb-49-2.hgnf.s1.devshift.org
AWS Account:<PHONE_NUMBER>89
API URL:
Console URL:
Region:                     us-east-1
Multi-AZ:                   false
Nodes:
 - Control plane:           3
 - Infra:                   2
 - Compute:                 2
Network:
 - Service CIDR:            <IP_ADDRESS>/16
 - Machine CIDR:            <IP_ADDRESS>/16
 - Pod CIDR:                <IP_ADDRESS>/14
 - Host Prefix:             /23
STS Role ARN:               arn:aws:iam::765374464689:role/sde-1816-4-Installer-Role
Support Role ARN:           arn:aws:iam::765374464689:role/sde-1816-4-Support-Role
Instance IAM Roles:
 - Control plane:           arn:aws:iam::765374464689:role/sde-1816-4-ControlPlane-Role
 - Worker:                  arn:aws:iam::765374464689:role/sde-1816-4-Worker-Role
Operator IAM Roles:
 - arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-machine-api-aws-cloud-credentials
 - arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-cloud-credential-operator-cloud-credenti
 - arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-image-registry-installer-cloud-credentia
 - arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-ingress-operator-cloud-credentials
 - arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-cluster-csi-drivers-ebs-cloud-credential
State:                      waiting (Waiting for OIDC configuration)
Private:                    No
Created:                    Oct 21 2022 12:38:27 UTC
Details Page:               https://qaprodauth.console.redhat.com/openshift/details/s/2GRed5TbwLWiA5UiQGkqeZz1TvH
OIDC Endpoint URL:          https://d3gt1gce2zmg3d.cloudfront.net/1vg49g0vh6977voife3eoef3qp0ssa9f

I: Preparing to create operator roles.
? Permissions boundary ARN (optional):
I: Creating roles using 'arn:aws:iam::765374464689:user/gbranco'
I: Created role 'gdb-49-2-d8s2-openshift-machine-api-aws-cloud-credentials' with ARN 'arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-machine-api-aws-cloud-credentials'
I: Created role 'gdb-49-2-d8s2-openshift-cloud-credential-operator-cloud-credenti' with ARN 'arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-cloud-credential-operator-cloud-credenti'
I: Created role 'gdb-49-2-d8s2-openshift-image-registry-installer-cloud-credentia' with ARN 'arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-image-registry-installer-cloud-credentia'
I: Created role 'gdb-49-2-d8s2-openshift-ingress-operator-cloud-credentials' with ARN 'arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-ingress-operator-cloud-credentials'
I: Created role 'gdb-49-2-d8s2-openshift-cluster-csi-drivers-ebs-cloud-credential' with ARN 'arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-cluster-csi-drivers-ebs-cloud-credential'
I: Preparing to create OIDC Provider.
I: Creating OIDC provider using 'arn:aws:iam::765374464689:user/gbranco'
I: Created OIDC provider with ARN 'arn:aws:iam::765374464689:oidc-provider/d3gt1gce2zmg3d.cloudfront.net/1vg49g0vh6977voife3eoef3qp0ssa9f'
I: To determine when your cluster is Ready, run 'rosa describe cluster -c gdb-49-2'.
I: To watch your cluster installation logs, run 'rosa logs install -c gdb-49-2 --watch'.

./rosa upgrade roles -c gdb-49-2 --mode auto --version=4.10.36
I: Ensuring account role policies compatibility for upgrade
I: Starting to upgrade the policies
? Upgrade the 'sde-1816-4-Installer-Role' role policy latest version ? Yes
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-4-Installer-Role-Policy' to latest version
? Upgrade the 'sde-1816-4-ControlPlane-Role' role policy latest version ? Yes
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-4-ControlPlane-Role-Policy' to latest version
? Upgrade the 'sde-1816-4-Worker-Role' role policy latest version ? Yes
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-4-Worker-Role-Policy' to latest version
? Upgrade the 'sde-1816-4-Support-Role' role policy latest version ? Yes
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-4-Support-Role-Policy' to latest version
I: Starting to upgrade the operator IAM roles and policies
? Upgrade the operator role policy to version 4.11? Yes
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-4-openshift-cloud-network-config-controller-cloud-crede' to version '4.11'
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-4-openshift-machine-api-aws-cloud-credentials' to version '4.11'
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-4-openshift-cloud-credential-operator-cloud-credential-' to version '4.11'
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-4-openshift-image-registry-installer-cloud-credentials' to version '4.11'
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-4-openshift-ingress-operator-cloud-credentials' to version '4.11'
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-4-openshift-cluster-csi-drivers-ebs-cloud-credentials' to version '4.11'
? Create the 'gdb-49-2-d8s2-openshift-cloud-network-config-controller-cloud-cr' role? Yes
I: Created role 'gdb-49-2-d8s2-openshift-cloud-network-config-controller-cloud-cr' with ARN 'arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-cloud-network-config-controller-cloud-cr'
I: Waiting for operator roles to reconcile

./rosa upgrade cluster -c gdb-49-2
? Version: 4.10.36
I: Ensuring account and operator role policies for cluster '1vg49g0vh6977voife3eoef3qp0ssa9f' are compatible with upgrade.
I: Account and operator roles for cluster 'gdb-49-2' are compatible with upgrade
? Are you sure you want to upgrade cluster to version '4.10.36'? Yes
? Please input desired date in format yyyy-mm-dd: 2022-10-21
? Please input desired UTC time in format HH:mm: 13:59
? Node draining: 1 hour
I: Upgrade successfully scheduled for cluster 'gdb-49-2'

./rosa describe cluster -c gdb-49-2
Name:                       gdb-49-2
ID:                         1vg49g0vh6977voife3eoef3qp0ssa9f
External ID:                b39e97c7-d3ea-4b0e-bcae-1928344859ca
Control Plane:              Customer hosted
OpenShift Version:          4.9.49
Channel Group:              stable
DNS:                        gdb-49-2.hgnf.s1.devshift.org
AWS Account:<PHONE_NUMBER>89
API URL:                    https://api.gdb-49-2.hgnf.s1.devshift.org:6443
Console URL:                https://console-openshift-console.apps.gdb-49-2.hgnf.s1.devshift.org
Region:                     us-east-1
Multi-AZ:                   false
Nodes:
 - Control plane:           3
 - Infra:                   2
 - Compute:                 2
Network:
 - Service CIDR:            <IP_ADDRESS>/16
 - Machine CIDR:            <IP_ADDRESS>/16
 - Pod CIDR:                <IP_ADDRESS>/14
 - Host Prefix:             /23
STS Role ARN:               arn:aws:iam::765374464689:role/sde-1816-4-Installer-Role
Support Role ARN:           arn:aws:iam::765374464689:role/sde-1816-4-Support-Role
Instance IAM Roles:
 - Control plane:           arn:aws:iam::765374464689:role/sde-1816-4-ControlPlane-Role
 - Worker:                  arn:aws:iam::765374464689:role/sde-1816-4-Worker-Role
Operator IAM Roles:
 - arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-machine-api-aws-cloud-credentials
 - arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-cloud-credential-operator-cloud-credenti
 - arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-image-registry-installer-cloud-credentia
 - arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-ingress-operator-cloud-credentials
 - arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-cluster-csi-drivers-ebs-cloud-credential
 - arn:aws:iam::765374464689:role/gdb-49-2-d8s2-openshift-cloud-network-config-controller-cloud-cr
State:                      ready
Private:                    No
Created:                    Oct 21 2022 12:38:27 UTC
Details Page:               https://qaprodauth.console.redhat.com/openshift/details/s/2GRed5TbwLWiA5UiQGkqeZz1TvH
OIDC Endpoint URL:          https://d3gt1gce2zmg3d.cloudfront.net/1vg49g0vh6977voife3eoef3qp0ssa9f
Scheduled Upgrade:          scheduled 4.10.36 on 2022-10-21 13:59 UTC

Running under upgrade cluster
./rosa create account-roles --mode auto --version=4.9 --prefix=sde-1816-5 -y
I: Logged in as 'gbranco.openshift' on 'https://api.stage.openshift.com'
I: Validating AWS credentials...
I: AWS credentials are valid!
I: Validating AWS quota...
I: AWS quota ok. If cluster installation fails, validate actual AWS resource usage against https://docs.openshift.com/rosa/rosa_getting_started/rosa-required-aws-service-quotas.html
I: Verifying whether OpenShift command-line tool is available...
I: Current OpenShift Client Version: 4.11.2
I: Creating account roles
I: Creating roles using 'arn:aws:iam::765374464689:user/gbranco'
I: Created role 'sde-1816-5-Installer-Role' with ARN 'arn:aws:iam::765374464689:role/sde-1816-5-Installer-Role'
I: Created role 'sde-1816-5-ControlPlane-Role' with ARN 'arn:aws:iam::765374464689:role/sde-1816-5-ControlPlane-Role'
I: Created role 'sde-1816-5-Worker-Role' with ARN 'arn:aws:iam::765374464689:role/sde-1816-5-Worker-Role'
I: Created role 'sde-1816-5-Support-Role' with ARN 'arn:aws:iam::765374464689:role/sde-1816-5-Support-Role'
I: To create a cluster with these roles, run the following command:
rosa create cluster --sts

./rosa create cluster --sts --mode auto --yes
I: Enabling interactive mode
? Cluster name: gdb-49-3
? OpenShift version: 4.9.49
W: More than one Installer role found
? Installer role ARN: arn:aws:iam::765374464689:role/sde-1816-5-Installer-Role
I: Using arn:aws:iam::765374464689:role/sde-1816-5-ControlPlane-Role for the ControlPlane role
I: Using arn:aws:iam::765374464689:role/sde-1816-5-Worker-Role for the Worker role
I: Using arn:aws:iam::765374464689:role/sde-1816-5-Support-Role for the Support role
? External ID (optional):
? Operator roles prefix: gdb-49-3-w6m1
? Multiple availability zones (optional): No
? AWS region: us-east-1
? PrivateLink cluster (optional): No
? Install into an existing VPC (optional): No
? Select availability zones (optional): No
? Enable Customer Managed key (optional): No
? Compute nodes instance type: m5.xlarge
? Enable autoscaling (optional): No
? Compute nodes: 2
? Machine CIDR: <IP_ADDRESS>/16
? Service CIDR: <IP_ADDRESS>/16
? Pod CIDR: <IP_ADDRESS>/14
? Host prefix: 23
? Encrypt etcd data (optional): No
? Disable Workload monitoring (optional): No
I: Creating cluster 'gdb-49-3'
I: To create this cluster again in the future, you can run:
   rosa create cluster --cluster-name gdb-49-3 --sts --mode auto --role-arn arn:aws:iam::765374464689:role/sde-1816-5-Installer-Role --support-role-arn arn:aws:iam::765374464689:role/sde-1816-5-Support-Role --controlplane-iam-role arn:aws:iam::765374464689:role/sde-1816-5-ControlPlane-Role --worker-iam-role arn:aws:iam::765374464689:role/sde-1816-5-Worker-Role --operator-roles-prefix gdb-49-3-w6m1 --region us-east-1 --version 4.9.49 --compute-nodes 2 --compute-machine-type m5.xlarge --machine-cidr <IP_ADDRESS>/16 --service-cidr <IP_ADDRESS>/16 --pod-cidr <IP_ADDRESS>/14 --host-prefix 23
I: To view a list of clusters and their status, run 'rosa list clusters'
I: Cluster 'gdb-49-3' has been created.
I: Once the cluster is installed you will need to add an Identity Provider before you can login into the cluster. See 'rosa create idp --help' for more information.
Name:                       gdb-49-3
ID:                         1vg4mr8eh6gb6tlemh4vjcj5jt0i6nja
External ID:
Control Plane:              Customer hosted
OpenShift Version:
Channel Group:              stable
DNS:                        gdb-49-3.3um5.s1.devshift.org
AWS Account:<PHONE_NUMBER>89
API URL:
Console URL:
Region:                     us-east-1
Multi-AZ:                   false
Nodes:
 - Control plane:           3
 - Infra:                   2
 - Compute:                 2
Network:
 - Service CIDR:            <IP_ADDRESS>/16
 - Machine CIDR:            <IP_ADDRESS>/16
 - Pod CIDR:                <IP_ADDRESS>/14
 - Host Prefix:             /23
STS Role ARN:               arn:aws:iam::765374464689:role/sde-1816-5-Installer-Role
Support Role ARN:           arn:aws:iam::765374464689:role/sde-1816-5-Support-Role
Instance IAM Roles:
 - Control plane:           arn:aws:iam::765374464689:role/sde-1816-5-ControlPlane-Role
 - Worker:                  arn:aws:iam::765374464689:role/sde-1816-5-Worker-Role
Operator IAM Roles:
 - arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-cluster-csi-drivers-ebs-cloud-credential
 - arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-machine-api-aws-cloud-credentials
 - arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-cloud-credential-operator-cloud-credenti
 - arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-image-registry-installer-cloud-credentia
 - arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-ingress-operator-cloud-credentials
State:                      waiting (Waiting for OIDC configuration)
Private:                    No
Created:                    Oct 21 2022 13:06:56 UTC
Details Page:               https://qaprodauth.console.redhat.com/openshift/details/s/2GRi5oVgBh5KUzAlBdhtsg5ffSI
OIDC Endpoint URL:          https://d3gt1gce2zmg3d.cloudfront.net/1vg4mr8eh6gb6tlemh4vjcj5jt0i6nja

I: Preparing to create operator roles.
? Permissions boundary ARN (optional):
I: Creating roles using 'arn:aws:iam::765374464689:user/gbranco'
I: Created role 'gdb-49-3-w6m1-openshift-cloud-credential-operator-cloud-credenti' with ARN 'arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-cloud-credential-operator-cloud-credenti'
I: Created role 'gdb-49-3-w6m1-openshift-image-registry-installer-cloud-credentia' with ARN 'arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-image-registry-installer-cloud-credentia'
I: Created role 'gdb-49-3-w6m1-openshift-ingress-operator-cloud-credentials' with ARN 'arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-ingress-operator-cloud-credentials'
I: Created role 'gdb-49-3-w6m1-openshift-cluster-csi-drivers-ebs-cloud-credential' with ARN 'arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-cluster-csi-drivers-ebs-cloud-credential'
I: Created role 'gdb-49-3-w6m1-openshift-machine-api-aws-cloud-credentials' with ARN 'arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-machine-api-aws-cloud-credentials'
I: Preparing to create OIDC Provider.
I: Creating OIDC provider using 'arn:aws:iam::765374464689:user/gbranco'
I: Created OIDC provider with ARN 'arn:aws:iam::765374464689:oidc-provider/d3gt1gce2zmg3d.cloudfront.net/1vg4mr8eh6gb6tlemh4vjcj5jt0i6nja'
I: To determine when your cluster is Ready, run 'rosa describe cluster -c gdb-49-3'.
I: To watch your cluster installation logs, run 'rosa logs install -c gdb-49-3 --watch'.

./rosa upgrade cluster -c gdb-49-3 --mode auto
? Version: 4.10.36
I: Ensuring account and operator role policies for cluster '1vg4mr8eh6gb6tlemh4vjcj5jt0i6nja' are compatible with upgrade.
I: Starting to upgrade the policies
? Upgrade the 'sde-1816-5-Installer-Role' role policy latest version (4.11) ? Yes
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-5-Installer-Role-Policy' to latest version
? Upgrade the 'sde-1816-5-ControlPlane-Role' role policy latest version (4.11) ? Yes
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-5-ControlPlane-Role-Policy' to latest version
? Upgrade the 'sde-1816-5-Worker-Role' role policy latest version (4.11) ? Yes
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-5-Worker-Role-Policy' to latest version
? Upgrade the 'sde-1816-5-Support-Role' role policy latest version (4.11) ? Yes
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-5-Support-Role-Policy' to latest version
I: Starting to upgrade the operator IAM roles and policies
? Upgrade each operator role policy to latest version (4.11)? Yes
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-5-openshift-ingress-operator-cloud-credentials' to version '4.11'
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-5-openshift-cluster-csi-drivers-ebs-cloud-credentials' to version '4.11'
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-5-openshift-cloud-network-config-controller-cloud-crede' to version '4.11'
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-5-openshift-machine-api-aws-cloud-credentials' to version '4.11'
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-5-openshift-cloud-credential-operator-cloud-credential-' to version '4.11'
I: Upgraded policy with ARN 'arn:aws:iam::765374464689:policy/sde-1816-5-openshift-image-registry-installer-cloud-credentials' to version '4.11'
? Create the 'gdb-49-3-w6m1-openshift-cloud-network-config-controller-cloud-cr' role? Yes
I: Created role 'gdb-49-3-w6m1-openshift-cloud-network-config-controller-cloud-cr' with ARN 'arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-cloud-network-config-controller-cloud-cr'
I: Waiting for operator roles to reconcile
I: Account and operator roles for cluster 'gdb-49-3' are compatible with upgrade
? Are you sure you want to upgrade cluster to version '4.10.36'? Yes
? Please input desired date in format yyyy-mm-dd: 2022-10-21
? Please input desired UTC time in format HH:mm: 14:03
? Node draining: 1 hour
I: Upgrade successfully scheduled for cluster 'gdb-49-3'

./rosa describe cluster -c gdb-49-3
Name:                       gdb-49-3
ID:                         1vg4mr8eh6gb6tlemh4vjcj5jt0i6nja
External ID:                61aea6e8-0f42-4922-844d-3675062cf78c
Control Plane:              Customer hosted
OpenShift Version:
Channel Group:              stable
DNS:                        gdb-49-3.3um5.s1.devshift.org
AWS Account:<PHONE_NUMBER>89
API URL:                    https://api.gdb-49-3.3um5.s1.devshift.org:6443
Console URL:                https://console-openshift-console.apps.gdb-49-3.3um5.s1.devshift.org
Region:                     us-east-1
Multi-AZ:                   false
Nodes:
 - Control plane:           3
 - Infra:                   2
 - Compute:                 2
Network:
 - Service CIDR:            <IP_ADDRESS>/16
 - Machine CIDR:            <IP_ADDRESS>/16
 - Pod CIDR:                <IP_ADDRESS>/14
 - Host Prefix:             /23
STS Role ARN:               arn:aws:iam::765374464689:role/sde-1816-5-Installer-Role
Support Role ARN:           arn:aws:iam::765374464689:role/sde-1816-5-Support-Role
Instance IAM Roles:
 - Control plane:           arn:aws:iam::765374464689:role/sde-1816-5-ControlPlane-Role
 - Worker:                  arn:aws:iam::765374464689:role/sde-1816-5-Worker-Role
Operator IAM Roles:
 - arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-cluster-csi-drivers-ebs-cloud-credential
 - arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-machine-api-aws-cloud-credentials
 - arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-cloud-credential-operator-cloud-credenti
 - arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-image-registry-installer-cloud-credentia
 - arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-ingress-operator-cloud-credentials
 - arn:aws:iam::765374464689:role/gdb-49-3-w6m1-openshift-cloud-network-config-controller-cloud-cr
State:                      ready
Private:                    No
Created:                    Oct 21 2022 13:06:56 UTC
Details Page:               https://qaprodauth.console.redhat.com/openshift/details/s/2GRi5oVgBh5KUzAlBdhtsg5ffSI
OIDC Endpoint URL:          https://d3gt1gce2zmg3d.cloudfront.net/1vg4mr8eh6gb6tlemh4vjcj5jt0i6nja
Scheduled Upgrade:          scheduled 4.10.36 on 2022-10-21 14:03 UTC

This does not include changes in regards to breaking installer policies, so we still need to refactor and check how the structure for that will be to have a more unified flow

LGTM

/lgtm


Implement generic EventHandler class

http://forums.bridge.net/forum/community/help/326-system-eventargs?p=338#post338

Duplicate of #326.

Similar to #326. Just add the generic  member too.

Yes, my mistake. Was trying to keep one issue per forum thread but they are really different things I overlooked while reviewing this.

Pushed the fix in branch 328-eventHandlerSupport. Will merge its implementation is what we need.


Fix syntax error. Missing semicolon.

This kind of errors can be busted pretty easily using a script like this
#!/bin/sh

PHP_EXECUTABLE=`which php`

if [ -x "${PHP_EXECUTABLE}" ]; then
	find . -type f -name "*.inc" -exec "${PHP_EXECUTABLE}" -n -l {} \; | grep -v "No syntax errors detected"
	find . -type f -name "*.php" -exec "${PHP_EXECUTABLE}" -n -l {} \; | grep -v "No syntax errors detected"
else
	echo "PHP executable not found!"
fi

Feel free to add something like this to a test-suite or something ;)

Already fixed. I have a git hook that usually flags such things but it must have broken since it didn't warn me.


Replace requires with custom error messages

I too am an enjoyer of custom errors

Cool didn't know about custom errors in solidity


Strange log entry after updating to 0.7.0

This is the entry that appeared in the log after updating to the latest version. This didn't happen before the update.
/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_sensor.py:161: RuntimeWarning: coroutine 'ASensor.publish' was never awaited
  self.publish(val)
RuntimeWarning: Enable tracemalloc to get the object allocation traceback

config
DRIVER: umodbus
INVERTERS:
  - SERIAL_NR: "ххх"
    HA_PREFIX: DEYE
    MODBUS_ID: 1
    PORT: tcp://<IP_ADDRESS>:502
SENSOR_DEFINITIONS: single-phase

Can you try 0.7.1?

Can you try 0.7.1?

This version does not work.
log:
19:56:30 INFO    ############################################################
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/__main__.py", line 79, in <module>
    main()
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/__main__.py", line 74, in main
    loop.run_until_complete(main_loop(loop))
  File "/usr/local/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/__main__.py", line 40, in main_loop
    await ist.hass_discover_sensors()
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_inverter.py", line 165, in hass_discover_sensors
    ents = [
           ^
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_inverter.py", line 166, in <listcomp>
    s.create_entity(dev, ist=self) for s in self.ss.values() if not s.hidden
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_sensor.py", line 217, in create_entity
    self.entity = RWEntity(**ent, on_change=on_change)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: RWEntity.__init__() missing 1 required positional argument: 'device'
[19:56:30] WARNING: Halt add-on with exit code 1
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun sunsynk (no readiness notification)
s6-rc: info: service legacy-services successfully started
20:01:11 INFO    Loading configuration: /data/options.json
20:01:11 INFO    sunsynk library version: 0.6.4
20:01:11 INFO    Schedules:
+---------------------+-----+------+--------+-----------+----------+------------+
|         Key         | src | Read | Report | Change by | Change % | Change any |
+---------------------+-----+------+--------+-----------+----------+------------+
|      date_time      |  *  | 3600 |  3600  |           |          |            |
|          rw         |  *  |  5   |  300   |           |          |     1      |
|         enum        |     |  5   |  300   |           |          |    True    |
|          w          |  *  |  5   |   60   |           |          |     1      |
|         kwh         |  *  |  60  |  300   |           |          |     1      |
|       any_unit      |  *  |  5   |  300   |           |          |     1      |
|       no_unit       |  *  |  5   |  300   |           |          |     1      |
|      aux_power      |  +  |  1   |   60   |           |          |     1      |
|      load_power     |  +  |  1   |   60   |           |          |     1      |
|    grid_ct_power    |  +  |  1   |   60   |           |          |     1      |
|  generator_voltage  |  +  |  1   |   60   |           |          |     1      |
| generator_frequency |  +  |  1   |   60   |           |          |     1      |
|    grid_connected   |  +  |  1   |  300   |           |          |     1      |
+---------------------+-----+------+--------+-----------+----------+------------+
20:01:11 INFO    Using Single phase sensor definitions.
20:01:11 INFO    Importing /share/hass-addon-sunsynk/mysensors.py...
20:01:11 INFO      custom sensors: gen_starting_capacity, day_gen_power, day_gen_time, generator_voltage, generator_status, generator_frequency, gen_max_operating_time, gen_cooling_time, gen_charge_battery_current, grid_restore_time, gen_charge_enabled, gen_signal, gen_force, grid_charge_battery_current, battery_max_charge_current
20:01:11 INFO    Added hidden sensors as other sensors depend on it: Rated power, Serial
20:01:11 INFO    Connecting to tcp://<IP_ADDRESS>:502
20:01:11 INFO    Reading startup sensors Prog6 Time, Prog5 Time, Battery Shutdown Capacity, Battery Low Capacity, Prog1 Time, Serial, Rated power, Prog3 Time, Prog4 Time, Prog2 Time
20:01:12 INFO    ############################################################
20:01:12 INFO                 Inverter serial number '****6178'
20:01:12 INFO    ############################################################
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/__main__.py", line 79, in <module>
    main()
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/__main__.py", line 74, in main
    loop.run_until_complete(main_loop(loop))
  File "/usr/local/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/__main__.py", line 40, in main_loop
    await ist.hass_discover_sensors()
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_inverter.py", line 165, in hass_discover_sensors
    ents = [
           ^
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_inverter.py", line 166, in <listcomp>
    s.create_entity(dev, ist=self) for s in self.ss.values() if not s.hidden
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_sensor.py", line 217, in create_entity
    self.entity = RWEntity(**ent, on_change=on_change)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: RWEntity.__init__() missing 1 required positional argument: 'device'
[20:01:12] WARNING: Halt add-on with exit code 1
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

0.7.3 might be better!

I have just updated to 0.7.3 and am getting similar errors
22:07:37 INFO    ############################################################
22:07:37 INFO                 Inverter serial number '***XXXX'
22:07:37 INFO    ############################################################
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/main.py", line 79, in
main()
File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/main.py", line 74, in main
loop.run_until_complete(main_loop(loop))
File "/usr/local/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/main.py", line 40, in main_loop
await ist.hass_discover_sensors()
File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_inverter.py", line 165, in hass_discover_sensors
ents = [
^
File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_inverter.py", line 166, in
s.create_entity(dev, ist=self) for s in self.ss.values() if not s.hidden
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_sensor.py", line 212, in create_entity
self.entity = RWEntity(
^^^^^^^^^
TypeError: mqtt_entity.entities.RWEntity() got multiple values for keyword argument 'entity_category'
[22:07:37] WARNING: Halt add-on with exit code 1

Just upgraded to 0.7.3. Add on won't start getting these errors
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/main.py", line 79, in
main()
File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/main.py", line 74, in main
loop.run_until_complete(main_loop(loop))
File "/usr/local/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/main.py", line 40, in main_loop
await ist.hass_discover_sensors()
File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_inverter.py", line 165, in hass_discover_sensors
ents = [
^
File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_inverter.py", line 166, in
s.create_entity(dev, ist=self) for s in self.ss.values() if not s.hidden
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_sensor.py", line 212, in create_entity
self.entity = RWEntity(
^^^^^^^^^
TypeError: mqtt_entity.entities.RWEntity() got multiple values for keyword argument 'entity_category'
[22:41:04] WARNING: Halt add-on with exit code 1
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Also just updated to 0.7.3
Wont start and getting error:
05:31:53 INFO    Loading configuration: /data/options.json
05:31:53 INFO    sunsynk library version: 0.6.4
05:31:53 INFO    Schedules:
+-------------+-----+------+--------+-----------+----------+------------+
|     Key     | src | Read | Report | Change by | Change % | Change any |
+-------------+-----+------+--------+-----------+----------+------------+
|  date_time  |     |  60  |   60   |           |          |    True    |
|      rw     |     |  5   |  300   |           |          |    True    |
|     enum    |     |  5   |  300   |           |          |    True    |
|      w      |  *  |  2   |   5    |           |          |     1      |
|     kwh     |     | 300  |  300   |           |          |            |
|   any_unit  |     |  15  |  300   |           |          |            |
|   no_unit   |     |  15  |  300   |           |          |    True    |
| rated_power |  +  | 300  |  300   |           |          |            |
+-------------+-----+------+--------+-----------+----------+------------+
05:31:53 INFO    Using Single phase sensor definitions.
05:31:53 INFO    Importing /share/hass-addon-sunsynk/mysensors.py...
05:31:53 INFO      custom sensors: inverter_current
05:31:53 INFO    Added hidden sensors as other sensors depend on it: Rated power, Serial
05:31:53 INFO    Connecting to tcp://x.x.x.x:502
05:31:53 INFO    Reading startup sensors Prog4 Time, Battery Low Capacity, Battery Shutdown Capacity, Prog1 Time, Rated power, Battery Low voltage, Serial, Prog2 Time, Battery Float voltage, Prog3 Time, Prog6 Time, Prog5 Time
05:31:54 INFO    ############################################################
05:31:54 INFO                 Inverter serial number '****2330'
05:31:54 INFO    ############################################################
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/__main__.py", line 79, in <module>
    main()
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/__main__.py", line 74, in main
    loop.run_until_complete(main_loop(loop))
  File "/usr/local/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/__main__.py", line 40, in main_loop
    await ist.hass_discover_sensors()
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_inverter.py", line 165, in hass_discover_sensors
    ents = [
           ^
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_inverter.py", line 166, in <listcomp>
    s.create_entity(dev, ist=self) for s in self.ss.values() if not s.hidden
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_sensor.py", line 212, in create_entity
    self.entity = RWEntity(
                  ^^^^^^^^^
TypeError: mqtt_entity.entities.RWEntity() got multiple values for keyword argument 'entity_category'
[05:31:54] WARNING: Halt add-on with exit code 1

Try 0.7.4. likely this is text based sensors

Fixed for me. Thanks @kellerza for quick update

0.7.4 is running OK for me too - many thanks


the response of qt wallet under windows is very slow

Find the root cause for this.

i'm trying to port to Qt WebEngine, hope that it will give a better performance


Fix #161 - add SessionRequest::remote_address

Fixes #161
Testing
cargo build works. I didn't test it, per se.

Thank you


Add Black auto formatter

Problem Statement
Currently we don't have an auto formatter, so code style can be inconsistent.
Describe the solution you'd like
We like Black at Cadre and think we should adopt this to eliminate the need for stylistic comments in code reviews.
Describe alternatives you've considered
yapf is another good formatter, but takes longer and uses a heuristic so may not be deterministic.

Can I work on this ?


MSPSDS-472: Improve technical setup

The code changes comprise:

De-verbalising logs via Lograge
Adding timeouts Slowpoke
Adding db admin dashboard pgHero
NOT adding the secure_headers gem as this is already covered by rails (see https://github.com/twitter/secure_headers/issues/394)
Preventing host header injection (following this piece of advice

Pull Request Test Coverage Report for Build 1122

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 93.237%

Totals

Change from base Build 1120:
0.02%

Covered Lines:
1999

Relevant Lines:
2144

💛  - Coveralls

Damn it, I've written a whole host of comments before putting into review that I've accidentally deleted now :P

@broder as discussed, I'll want to push this through and leave enabling pghero historical stats to a separate PR


feat: Added the adapter and tests for it

I will next add the documentation and rockspec for this.

Also added the setup doc and rockspec.


Iptt filter panel 120

All filters now working.
Changes from bootstrap4 branch merged in.
Multi-select on filters now working.
@jennyhavah if you can run a local server and have a look at it.

Closing it as incomplete


allow selection of specific battery power

[ ] allow selection of specific battery charge/discharge power in kW/KWh
[ ] 0.1 to 2 with default 0.5

Fixed this issue, but unexpected values resulted.


[macOS] Add Xcode 12.1 GM seed

Description
Adding announced Xcode 12.1 GM seed
Related issue: n\a
Check list

[n\a] Related issue / work item is attached
[n\a] Tests are written (if applicable)
[n\a] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run macos1015, macos110

/azp run macos1015

/azp run macos1015


disable escape key behaviour

Is there a way to avoid closing the search input when I press escape key?
I can't figure out a workaround to disable this behaviour.

There isn't a way to disable this at the moment. Is there a good reason to disable this behavior? Seems like appropriate UX to me, but maybe I'm missing something.

I'm customizing the search behaviour for my app and the escape key breaks it.
So I wanted to know if there is a way (workaround) to disable it.
I think it may be a appropriate UX in the general case but not necessarily in a customized scenario.
Anyway, thanks for your answer :)

Sure, no problem. It's possible that such an option can be incorporated here https://github.com/gregnb/mui-datatables/pull/771. I will think on it.

Thanks :)


How to upgrade OpenSSL to 1.0.2f or above?

Hi,
Is there any way to upgrade OpenSSL to 1.0.2f or above? Google Play Console is scanning this part now, thanks.

OpenSSL library is not provided by this project, it uses openssl available in the environment.
So I see no way, how I could help you with such matters


Fix loading crash on mc 1.18.2 with fabric 0.13.3

Fix for #58 by updating to new mining levels api
Also includes fixes for deprecation of ItemTags.getTagGroup() and BlockTags.getTagGroup().

Thank you!
I was kind of dreading going through the huge tagging process.
I had been trying to do it with data-generators like I did with the Forge version but it looks like that might  be specific to that modloader and not built in to Fabric. If that's the case, there's probably an API to do it with. I think I prefer that approach if possible for the sake of future-proofing. I'll worry about that later, though.
The only edit I might make is to remove the "b" in the new version number because that's how I've been formatting it. That or I'll replace it with a "c" for consistency with the Forge version, since this change already happened in it. I've been having that dilemma ever since I ported the mod to Fabric.


Fix a few minor typos

Just a few wording/spelling things I noticed while reading this case study.  Thanks for the excellent docs!

Thanks @elnjensen!!


[WIP] Automate Method Dialog Parser testing outside engine

The Automate Method Dialog Parser can be tested outside the
Automate Engine. It uses a Mock Service to replace the Drb calls
and allows for testing the methods outside of the engine.

@tinaafitz @gmcculloug
Please Review

Implemented this when doing Ansible Tower methods


How do I use function parameters in citekey?

Hi. I'm trying to get my citekeys into this format:
If one author: surname-2022
If two authors: surname-and-surname-2022
If three authors: surname-surname-and-surname-2022
If more than three authors: surname-etal-2022

I've found the bit of the docs I think I need:
$author, +<joinchar>: Author/editor information. Parameters are: - creator: author or editor, - initials: whether to add initials or to only use initials, - letters: pick this many letters from the name, defaults to 0 = all, - select: select these authors, number or range (inclusive); negative numbers mean “from the end”, default = 0 = all, - given: use given name instead of family name, - etal: use this term to replace authors after etalafter authors have been named, - etalafter: add the etal if there are more authors selected that - joiner: use this character to join authors

But I'm struggling to understand the syntax. I have this [authors+-]-[year] outputting Szabo-Burns-Lantrip-2022. I'm now trying to add etal and etalafter=3. I've tried:[authors:etal:etaafter=3]-[year], [authors:etal,etalafter=3]-[year], [authors+-etal,etalafter=3]-[year] and various other combinations of +/:/-/., but I clearly don't know what I'm doing because the "Citation key format" box goes orange and doesn't let me save it!
Thanks for your help.
Support log ID: 72WF67SG-refs-euc

The docs are out of sync alas - I have a change lined up that will what you want possible, but I expect to take a few more days to get it ready for release.

The docs are out of sync alas - I have a change lined up that will what you want possible, but I expect to take a few more days to get it ready for release.

Oo that's wonderful, thank you :). I'm in no rush. I've been playing around with different ideas and decided I'd like the title in it too, in the format every-word-with-hypens - is that possible too? So in total it would be:
If one author: surname-2022-every-word-of-the-title-no-caps-hypens-not-spaces-but-stripped-of-punctuation
If two authors: surname-and-surname-2022-every-word-of-the-title-no-caps-hypens-not-spaces-but-stripped-of-punctuation
If three authors: surname-surname-and-surname-2022-every-word-of-the-title-no-caps-hypens-not-spaces-but-stripped-of-punctuation
If more than three authors: surname-etal-2022-every-word-of-the-title-no-caps-hypens-not-spaces-but-stripped-of-punctuation

Might seem a bit odd. But my rationale is that in Obsidian I can use that as the title of the note, and put the human-readable version in the display text, for example:
`[[surname-2022-every-word-of-the-title-no-caps-hypens-not-spaces|Surname et al. 2022]]
Then I can do Scan Markdown file for references in Zotero and it'll still be able to match it. Does that seem sensible? I'm only on day three of using Zotero, so happy to be told I'm barking up the wrong tree (as we say in the UK!)

I've been tinkering some more, and realised that I can keep most of the name of my Obsidian notes in human-readable format and just put the citekey at the end. So I realise I actually want the shortest citekey possible really!
So I've now got my citekey as:
bratmanetal2015
And this as my note name:
Bratman et al. (2015) ‘Nature experience reduces rumination and subgenual prefrontal cortex activation’ (@bratmanetal2015)
So thanks very much for looking at this, but I've realised I don't need what I asked how to do in the first place. All a learning curve, hey! Thanks for a great plugin :)

Awesome bot!

That's the first time I heard that! 😄

That's the first time I heard that! smile

Haha! It hassles politely :-D. Can I set the citekey as the Zotero key? In other words, PFFCF6SB from zotero://select/library/items/PFFCF6SB?

Not currently.

The other way around does work BTW; zotero://select/library/items/@citekey

The other way around does work BTW; zotero://select/library/items/@citekey

Oo that's good to know, thanks. I've settled on using the DOI or ISBN as the citekey where those exist (slash converted to hyphen), and I'm really happy with that. Thanks for all your work on the plugin!

FYI on my setup<EMAIL_ADDRESS>and zotero://select/library/items/doi-10.1073-pnas.1510459112 both select everything in my library, not just the one item!

I see that happening too, but this seems to be a Zotero behavior; I don't do anything with the second link, so that's definately Zotero, and for the first, when I cannot find the citekey, I pass back to Zotero, and you get the same behavior as with the 2nd URL. I could perhaps generate an error when I see an @ but cannot find the key.

Sorry I'm not quite with you. Are you saying the version without the @ should work? Neither work for me!

Sorry, I'm not quite with you. Are you saying you get the same behaviour I got with the one without the @?

Zotero has changed the behavior of select links. zotero://select/library/items/<something> will now select group <something> if it is present, and the user library if not. That is the behavior you're seeing. The only route BBT can patch in Zotero is now zotero://select/items/, and that should select the single item pointed to by , which can be an @citekey` when BBT is installed.

Will you take it up with Zotero? This is really not something BBT does.

This is not something I can do anything about.


[BugFix] Fix DoubleToFloat when keys is None

Description
Describe your changes in detail.
Motivation and Context
close #1437

[x] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes
What types of changes does your code introduce? Remove all that do not apply:

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds core functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update in the documentation)
[ ] Example (update in the folder of examples)

Checklist
Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

[x] I have read the CONTRIBUTION guide (required)
[ ] My change requires a change to the documentation.
[ ] I have updated the tests accordingly (required for a bug fix or a new feature).
[ ] I have updated the documentation accordingly.

Closed by #1442


Add iPhone 7 and iPhone 7 Plus

They are already supported, which version are you using?

My bad you are right.
I just forgot to do an update at that moment.
Closed.


Fail fast on .NET Full Framework and log exceptions in hostfxr utility

To check if the application is full framework, I check for the existence of APPNAME.runtimeconfig.json.
@pan-wang I passed in the EventLog handle to each of these functions as it is part of CommonLib. We want to keep hostfxr_utility in CommonLib in the case where we need to parse configuration in the request handler.
For https://github.com/aspnet/AspNetCoreModule/issues/255

@pan-wang updated.


ldeep: 1.0.49 -> 1.0.51

Diff: https://github.com/franc-pentest/ldeep/compare/refs/tags/1.0.49...1.0.51
Changelog: https://github.com/franc-pentest/ldeep/releases/tag/1.0.51
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 275495 run on x86_64-linux 1

2 packages built:

ldeep
ldeep.dist


Can't get it to work in Godot 3.5

Hello, I tried the plugin out but I can't get it to work, I enabled the plugin but whenever I select a tilemap in my scene tree it shows a bunch of errors in the console, I'll add a screenshot so you can see them.

Note that the "invalid get index pressed on nil" errors happen when dragging the cursor along the scene viewer, and the ones before those happen when selecting or unselecting a tilemap on the scene tree.
And when I open the project it says this:

What do you think could be the problem?
Thanks.

Thanks for the report, @strellydev! Probably something has been changed in recent updates to version 3.5, and the editor cannot find some of Godot's internal objects. He needs this in order to integrate in instead of the regular editor.
I'll try to debug it on the latest release of Godot 3.5 in the next day or two.

It looks like it can't find the CanvasItemEditor in the EditorViewport node. But this problem doesn't reproduce on my machine.
Please provide the exact version of your Godot engine and the hash of the commit you got the tile map editor from.

Hi, thanks for the quick answer, the Godot version is v3.5.stable.official [991bb6ac7] and the commit for the plugin is #5fcf557, which should be the latest one, I just downloaded it today from the main page.

With 3.5.2 (the latest you can download from godotengine.org) the Tile Map tab appears, but it still doesn't work, with new errors appearning. Here's a screenshot.

I figured out what the problem is. In the plugin settings, the parameter "palette_zoom_step_factor" is set to 0.
(Project Settings -> General -> Enchanced Tile Map Editor -> Palette Zoom Step Factor -> float value where 1.0 is for no zooming)
Godot sometimes incorrectly shows the location of the error. If a class has a parent class and the error occurred in it, it will show the script path of the child class, not the parent class. And the line number will be for the parent class.
I made a hotfix that will prevent zero from reaching the division operation, but please set the scaling factor to whatever you feel comfortable with.

The setting wasn't set to 0 but I downloaded the hotfix and it worked fine, thank you!


Failed to connect to ESP8266: Invalid head of packet (0x62)

I was having a go at putting micropython on the board, however mistakenly attempted to upload the "esp8266-20190125-v1.10.bin" micropython file via the OTA method rather than USB.
I'm now trying to install the default badgy.bin file via Arduino to start again however get the following exception:
Sketch uses 333532 bytes (31%) of program storage space. Maximum is 1044464 bytes.
Global variables use 37136 bytes (45%) of dynamic memory, leaving 44784 bytes for local variables. Maximum is 81920 bytes.
esptool.py v2.6
2.6
esptool.py v2.6
Serial port COM4
Connecting........_____....._____....._____....._____....._____....._____.....____Traceback (most recent call last):
  File "C:\...\Arduino15\packages\esp8266\hardware\esp8266\2.5.2/tools/upload.py", line 25, in <module>
    esptool.main(fakeargs)
  File "C:/.../Arduino15/packages/esp8266/hardware/esp8266/2.5.2/tools/esptool\esptool.py", line 2653, in main
    esp.connect(args.before)
  File "C:/.../Arduino15/packages/esp8266/hardware/esp8266/2.5.2/tools/esptool\esptool.py", line 468, in connect
    raise FatalError('Failed to connect to %s: %s' % (self.CHIP_NAME, last_error))
esptool.FatalError: Failed to connect to ESP8266: Invalid head of packet (0x6C)
esptool.FatalError: Failed to connect to ESP8266: Invalid head of packet (0x6C)

Would this be due to uploading the micropython .bin file via OTA?  Can I reset Badgy or still put micropython on it?

Try using the esptool and erasing the flash. You may also have to toggle the on/off switch at the right time if you are unable to get it into upload mode.

Thanks for the reply.  Regarding toggling the on/off switch at the right time to force into upload mode - is there a specific time to do this?  E.g. a few seconds after plugging the USB in?

Thanks for the reply.  Regarding toggling the on/off switch at the right time to force into upload mode - is there a specific time to do this?  E.g. a few seconds after plugging in the USB?

It all depends on the sketch. The on/off switch won't put it into upload mode - but most of the badgy sketched use the deepsleep, so once it's booted and done "whatever task" it will shut down. I found a little more reliable is to hold the joystick button down on boot. This (usually - again, depends on the sketch) will put it into OTA Upload mode and not set it to go to sleep. It will be sat waiting for a HTTP upload, but more importantly will be up and running and able to accept Tx Rx signals from the USB chip.

Success!  Using esptool to erase the flash did the job.  In case anyone finds themselves in the same situation as me, here's the steps I took to erase the flash and put micropython on the board:

Plug the board in with the On/Off switched to Off
Run $ esptool.py --port /dev/tty.SLAB_USBtoUART erase_flash (Your port may vary)
You'll see a Connecting........_____ message
During this message, hold down the joystick button and turn the switch to On.  Then release the joystick button.  Doing this near the beginning of the "Connecting" message worked for me.

Full output:
$ esptool.py --port /dev/tty.SLAB_USBtoUART erase_flash
esptool.py v2.6
Serial port /dev/tty.SLAB_USBtoUART
Connecting........_
Detecting chip type... ESP8266
Chip is ESP8266EX
Features: WiFi
MAC: 84:f3:eb:84:63:66
Uploading stub...
Running stub...
Stub running...
Erasing flash (this may take a while)...
Chip erase completed successfully in 7.1s
Hard resetting via RTS pin...

Installing micropython was then a similar process:
$ esptool.py --port /dev/tty.SLAB_USBtoUART --baud 460800 write_flash --flash_size=detect 0 esp8266-20190529-v1.11.bin
esptool.py v2.6
Serial port /dev/tty.SLAB_USBtoUART
Connecting........_____....._
Detecting chip type... ESP8266
Chip is ESP8266EX
Features: WiFi
MAC: 84:f3:eb:84:63:66
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Auto-detected Flash size: 4MB
Flash params set to 0x0040
Compressed 617880 bytes to 402086...
Wrote 617880 bytes (402086 compressed) at 0x00000000 in 9.6 seconds (effective 517.5 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

Badgy now broadcasts the Micropython AP successfully.  Thanks very much for your help!

Awesome, glad the little joystick hack worked for you!


MLOpsZoomCamp ressource request

Title
Ressource request MLOPsZoomCamp
Is this a new project?
yes
People involved
@likeajumprope
Project Description
Both for the purpose of checking out the platform and because I am participating in the MlOpsZoomCamp, (https://github.com/DataTalksClub/mlops-zoomcamp) I'd like to request some ressources (see below). Also trying to figure out whether this might be a good way to teach people the usage of the cloud
Link to project repository/sources
https://github.com/likeajumprope/mlops-zoomcamp
What resources do you require?
Virtual Machines, Object Storage
Anything else?
I guess I COULD just create this project myself as admin, but thought I'd better go the traditional way..

Yes, but still important to have a record :) create the project and let me know if you need any help.

This project is now closed and all resources on the Oracle Cloud will be deleted within the next few days.


Better NPC dialogues

Extracted from #72
Dialogs should be hierarchical.
I have the code when you talk to the NPC.
But I'm not sure how it should look on the admin side.
I will think about it.

First draft for the editor:

It is ugly because I'm bad at user interface. Maybe @Phosphorus-M has an idea on how to make it look good...

Actually changed, it was too ugly.

For now it looks like this.

When you are a player, if a text has children (text under), then it will be clickable
if it doesn't have children, it will be simple text, not clickable.

it would be nice to make dialogues as a fallout or arkanum or elderscrolls online. where your choice determines the next stage of the quest.it would also be nice to make the appearance of certain replicas depending on the requirements (stats or level or completed quest). for example, to cross the river, you need to speak to the NPC. further choice - persuade (you need the necessary stats, belonging to the faction), bribe (money, object), kill npc.

Very complex. Maybe later...

I made buttons into buttons for now.

look nice

I have committed the first version. I will work some more on it.

LOL oops sorry sorry my mistake
Also as I have explained somewhere else.
I have started moving AD&R to Integramod.

oh, this is nice

@winzombie From the text -- Are you czech? In prague?

@vendethiel nope, im from Ukraine

Oh, funny enough then — the text you posted also makes sense in Czech.

Also, it took way longer than expected, but now AD&R is part of Integramod.


Off-by-one error when indexing individual pins of a bus

Steps to reproduce the issue
Verilog source:
module Top(
           output [3:0] LED,
           inout [10:1] JA
           );

   wire [3:0]           ROWS = JA[10:7];
   wire [3:0]           COLS = 4'b1110;

   assign LED = ROWS;
   assign JA[4:1] = COLS;

endmodule

I have a keypad connected to the JA port, so some of the bits in the JA bus are output (to select the scanned columns) and some are input (to read in the currently selected column from all rows).
Expected behavior
The state of the selected (0-th) column should show up on the LEDs.
Actual behavior
If we look at the Yosys synthesis result, we can see that COLS gets assigned to JA[3:0] instead of JA[4:1]. Similarly, the pins read from JA are off by one, so instead of 10:7, ROWS (and consequently, LED) gets assigned from 9:6:
$ echo 'read_verilog Top.v; synth; show;' | yosys

This is not an actual error, it's just idiosyncracy of show command (it always uses internal yosys bit numbering, which is from 0 LSB).
When written to JSON or other output format, the relevant wire should have the right annotations to be handled correctly

This is not an actual error, it's just idiosyncracy of show command (it always uses internal yosys bit numbering, which is from 0 LSB).
When written to JSON or other output format, the relevant wire should have the right annotations to be handled correctly

I'm not convinced. When I synthesize the whole circuit end-to-end, targeting a Xilinx 7 dev board, the only way I can get it to work is if I shift the definition of COLS by one, i.e. if I set COLS = 4'b1101, and then I can observe the 0th column (!) being scanned. Similarly, the input as read from ROWS is then shown off-by-one on the LEDs.

Then please give an instruction for how to reproduce the problem end-to-end

Sure, here it is: https://github.com/gergoerdi/yosys-issue-3078/tree/1eb7b9a88b678087e7ace0e3ade7c45e13e39c34
Build with make, then upload to a Nexys A7-50T development board with make upload. Connect a Digilent 4x4 keypad to the JA user port, and then observe the LED behaviour.

I have a much simplified version at https://github.com/gergoerdi/yosys-issue-3078/tree/1eb7b9a88b678087e7ace0e3ade7c45e13e39c34 that doesn't require any external peripherals:
module Top(
           output [5:2] LED
           );

   assign LED[5:2] = 4'b1101;
endmodule

With Vivado this lights up LEDs 2, 4 and 5; with Symbiflow using Yosys, it lights up only LED 2.
$ echo 'read_verilog Top.v; synth_xilinx; show;' | yosys

I've got no idea what all the Symbiflow bits are doing, but running yosys -p "synth_xilinx -top Top -blif /dev/stdout" Top.v produces:
.model Top
.inputs
.outputs LED[2] LED[3] LED[4] LED[5]
.names $false
.names $true
1
.names $undef
.subckt OBUF I=$true O=LED[2]
.subckt OBUF I=$false O=LED[3]
.subckt OBUF I=$true O=LED[4]
.subckt OBUF I=$true O=LED[5]
.end

which looks like correct BLIF output to me

Thanks, I've reported this to the Symbiflow project as well.

I'd be curious what the eblif file from symbiflow_synth looks like if you could post it here (I don't have all their wrappers set up)

I'd be curious what the eblif file from symbiflow_synth looks like if you could post it here

# Generated by Yosys 0.9+4270 (git sha1 539d4ee9, x86_64-conda_cos6-linux-gnu-gcc <IP_ADDRESS>_b0863d8_dirty -fvisibility-inlines-hidden -fmessage-length=0 -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O2 -ffunction-sections -fdebug-prefix-map=/home/runner/work/conda-eda/conda-eda/workdir/conda-env/conda-bld/yosys_1628927583200/work=/usr/local/src/conda/yosys-0.9_5567_g539d4ee9 -fdebug-prefix-map=/home/cactus/.conda/envs/xc7=/usr/local/src/conda-prefix -fPIC -Os -fno-merge-constants)

.model Top
.inputs
.outputs LED[2] LED[3] LED[4] LED[5]
.subckt GND GND=$false
.subckt VCC VCC=$true
.subckt VCC VCC=$undef
.subckt T_INV TI=$true TO=$iopadmap$Top.LED.t
.cname $iopadmap$Top.LED.genblk1.t_inv
.attr module_not_derived<PHONE_NUMBER>0000000000000000000001
.attr src "/home/cactus/prog/fpga/symbiflow/symbiflow-examples/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v:1921.5-1925.4|/home/cactus/prog/fpga/symbiflow/symbiflow-examples/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v:1950.11-1953.6"
.subckt OBUFT_VPR I=$true O=LED[2] T=$iopadmap$Top.LED.t
.cname $iopadmap$Top.LED.obuft
.attr module_not_derived<PHONE_NUMBER>0000000000000000000001
.attr src "/home/cactus/prog/fpga/symbiflow/symbiflow-examples/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v:1921.5-1925.4|/home/cactus/prog/fpga/symbiflow/symbiflow-examples/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v:2064.5-2068.4"
.param DRIVE<PHONE_NUMBER>0000000000000000001100
.param IOSTANDARD "LVCMOS33"
.param IO_LOC_PAIRS "NONE"
.param LVCMOS12_DRIVE_I12 0
.param LVCMOS12_DRIVE_I4 0
.param LVCMOS12_LVCMOS15_LVCMOS18_LVCMOS25_LVCMOS33_LVTTL_SLEW_FAST 0
.param LVCMOS12_LVCMOS15_LVCMOS18_LVCMOS25_LVCMOS33_LVTTL_SSTL135_SSTL15_SLEW_SLOW 1
.param LVCMOS12_LVCMOS15_LVCMOS18_SSTL135_SSTL15_STEPDOWN 0
.param LVCMOS12_LVCMOS25_DRIVE_I8 0
.param LVCMOS15_DRIVE_I12 0
.param LVCMOS15_DRIVE_I8 0
.param LVCMOS15_LVCMOS18_LVCMOS25_DRIVE_I4 0
.param LVCMOS15_SSTL15_DRIVE_I16_I_FIXED 0
.param LVCMOS18_DRIVE_I12_I8 0
.param LVCMOS18_DRIVE_I16 0
.param LVCMOS18_DRIVE_I24 0
.param LVCMOS25_DRIVE_I12 0
.param LVCMOS25_DRIVE_I16 0
.param LVCMOS33_DRIVE_I16 0
.param LVCMOS33_LVTTL_DRIVE_I12_I16 1
.param LVCMOS33_LVTTL_DRIVE_I12_I8 0
.param LVCMOS33_LVTTL_DRIVE_I4 0
.param LVTTL_DRIVE_I24 0
.param PULLTYPE "NONE"
.param PULLTYPE_KEEPER 0
.param PULLTYPE_NONE 1
.param PULLTYPE_PULLDOWN 0
.param PULLTYPE_PULLUP 0
.param SLEW "SLOW"
.param SSTL135_DRIVE_I_FIXED 0
.param SSTL135_SSTL15_SLEW_FAST 0
.subckt T_INV TI=$true TO=$iopadmap$Top.LED_1.t
.cname $iopadmap$Top.LED_1.genblk1.t_inv
.attr module_not_derived<PHONE_NUMBER>0000000000000000000001
.attr src "/home/cactus/prog/fpga/symbiflow/symbiflow-examples/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v:1921.5-1925.4|/home/cactus/prog/fpga/symbiflow/symbiflow-examples/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v:1950.11-1953.6"
.subckt OBUFT_VPR I=$false O=LED[3] T=$iopadmap$Top.LED_1.t
.cname $iopadmap$Top.LED_1.obuft
.attr module_not_derived<PHONE_NUMBER>0000000000000000000001
.attr src "/home/cactus/prog/fpga/symbiflow/symbiflow-examples/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v:1921.5-1925.4|/home/cactus/prog/fpga/symbiflow/symbiflow-examples/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v:2064.5-2068.4"
.param DRIVE<PHONE_NUMBER>0000000000000000001100
.param IOSTANDARD "LVCMOS33"
.param IO_LOC_PAIRS "NONE"
.param LVCMOS12_DRIVE_I12 0
.param LVCMOS12_DRIVE_I4 0
.param LVCMOS12_LVCMOS15_LVCMOS18_LVCMOS25_LVCMOS33_LVTTL_SLEW_FAST 0
.param LVCMOS12_LVCMOS15_LVCMOS18_LVCMOS25_LVCMOS33_LVTTL_SSTL135_SSTL15_SLEW_SLOW 1
.param LVCMOS12_LVCMOS15_LVCMOS18_SSTL135_SSTL15_STEPDOWN 0
.param LVCMOS12_LVCMOS25_DRIVE_I8 0
.param LVCMOS15_DRIVE_I12 0
.param LVCMOS15_DRIVE_I8 0
.param LVCMOS15_LVCMOS18_LVCMOS25_DRIVE_I4 0
.param LVCMOS15_SSTL15_DRIVE_I16_I_FIXED 0
.param LVCMOS18_DRIVE_I12_I8 0
.param LVCMOS18_DRIVE_I16 0
.param LVCMOS18_DRIVE_I24 0
.param LVCMOS25_DRIVE_I12 0
.param LVCMOS25_DRIVE_I16 0
.param LVCMOS33_DRIVE_I16 0
.param LVCMOS33_LVTTL_DRIVE_I12_I16 1
.param LVCMOS33_LVTTL_DRIVE_I12_I8 0
.param LVCMOS33_LVTTL_DRIVE_I4 0
.param LVTTL_DRIVE_I24 0
.param PULLTYPE "NONE"
.param PULLTYPE_KEEPER 0
.param PULLTYPE_NONE 1
.param PULLTYPE_PULLDOWN 0
.param PULLTYPE_PULLUP 0
.param SLEW "SLOW"
.param SSTL135_DRIVE_I_FIXED 0
.param SSTL135_SSTL15_SLEW_FAST 0
.subckt T_INV TI=$true TO=$iopadmap$Top.LED_2.t
.cname $iopadmap$Top.LED_2.genblk1.t_inv
.attr module_not_derived<PHONE_NUMBER>0000000000000000000001
.attr src "/home/cactus/prog/fpga/symbiflow/symbiflow-examples/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v:1921.5-1925.4|/home/cactus/prog/fpga/symbiflow/symbiflow-examples/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v:1950.11-1953.6"
.subckt OBUFT_VPR I=$true O=LED[4] T=$iopadmap$Top.LED_2.t
.cname $iopadmap$Top.LED_2.obuft
.attr module_not_derived<PHONE_NUMBER>0000000000000000000001
.attr src "/home/cactus/prog/fpga/symbiflow/symbiflow-examples/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v:1921.5-1925.4|/home/cactus/prog/fpga/symbiflow/symbiflow-examples/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v:2064.5-2068.4"
.param DRIVE<PHONE_NUMBER>0000000000000000001100
.param IOSTANDARD "LVCMOS33"
.param IO_LOC_PAIRS "LED[2]:J13"
.param LVCMOS12_DRIVE_I12 0
.param LVCMOS12_DRIVE_I4 0
.param LVCMOS12_LVCMOS15_LVCMOS18_LVCMOS25_LVCMOS33_LVTTL_SLEW_FAST 0
.param LVCMOS12_LVCMOS15_LVCMOS18_LVCMOS25_LVCMOS33_LVTTL_SSTL135_SSTL15_SLEW_SLOW 1
.param LVCMOS12_LVCMOS15_LVCMOS18_SSTL135_SSTL15_STEPDOWN 0
.param LVCMOS12_LVCMOS25_DRIVE_I8 0
.param LVCMOS15_DRIVE_I12 0
.param LVCMOS15_DRIVE_I8 0
.param LVCMOS15_LVCMOS18_LVCMOS25_DRIVE_I4 0
.param LVCMOS15_SSTL15_DRIVE_I16_I_FIXED 0
.param LVCMOS18_DRIVE_I12_I8 0
.param LVCMOS18_DRIVE_I16 0
.param LVCMOS18_DRIVE_I24 0
.param LVCMOS25_DRIVE_I12 0
.param LVCMOS25_DRIVE_I16 0
.param LVCMOS33_DRIVE_I16 0
.param LVCMOS33_LVTTL_DRIVE_I12_I16 1
.param LVCMOS33_LVTTL_DRIVE_I12_I8 0
.param LVCMOS33_LVTTL_DRIVE_I4 0
.param LVTTL_DRIVE_I24 0
.param PULLTYPE "NONE"
.param PULLTYPE_KEEPER 0
.param PULLTYPE_NONE 1
.param PULLTYPE_PULLDOWN 0
.param PULLTYPE_PULLUP 0
.param SLEW "SLOW"
.param SSTL135_DRIVE_I_FIXED 0
.param SSTL135_SSTL15_SLEW_FAST 0
.subckt T_INV TI=$true TO=$iopadmap$Top.LED_3.t
.cname $iopadmap$Top.LED_3.genblk1.t_inv
.attr module_not_derived<PHONE_NUMBER>0000000000000000000001
.attr src "/home/cactus/prog/fpga/symbiflow/symbiflow-examples/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v:1921.5-1925.4|/home/cactus/prog/fpga/symbiflow/symbiflow-examples/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v:1950.11-1953.6"
.subckt OBUFT_VPR I=$true O=LED[5] T=$iopadmap$Top.LED_3.t
.cname $iopadmap$Top.LED_3.obuft
.attr module_not_derived<PHONE_NUMBER>0000000000000000000001
.attr src "/home/cactus/prog/fpga/symbiflow/symbiflow-examples/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v:1921.5-1925.4|/home/cactus/prog/fpga/symbiflow/symbiflow-examples/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v:2064.5-2068.4"
.param DRIVE<PHONE_NUMBER>0000000000000000001100
.param IOSTANDARD "LVCMOS33"
.param IO_LOC_PAIRS "LED[3]:N14"
.param LVCMOS12_DRIVE_I12 0
.param LVCMOS12_DRIVE_I4 0
.param LVCMOS12_LVCMOS15_LVCMOS18_LVCMOS25_LVCMOS33_LVTTL_SLEW_FAST 0
.param LVCMOS12_LVCMOS15_LVCMOS18_LVCMOS25_LVCMOS33_LVTTL_SSTL135_SSTL15_SLEW_SLOW 1
.param LVCMOS12_LVCMOS15_LVCMOS18_SSTL135_SSTL15_STEPDOWN 0
.param LVCMOS12_LVCMOS25_DRIVE_I8 0
.param LVCMOS15_DRIVE_I12 0
.param LVCMOS15_DRIVE_I8 0
.param LVCMOS15_LVCMOS18_LVCMOS25_DRIVE_I4 0
.param LVCMOS15_SSTL15_DRIVE_I16_I_FIXED 0
.param LVCMOS18_DRIVE_I12_I8 0
.param LVCMOS18_DRIVE_I16 0
.param LVCMOS18_DRIVE_I24 0
.param LVCMOS25_DRIVE_I12 0
.param LVCMOS25_DRIVE_I16 0
.param LVCMOS33_DRIVE_I16 0
.param LVCMOS33_LVTTL_DRIVE_I12_I16 1
.param LVCMOS33_LVTTL_DRIVE_I12_I8 0
.param LVCMOS33_LVTTL_DRIVE_I4 0
.param LVTTL_DRIVE_I24 0
.param PULLTYPE "NONE"
.param PULLTYPE_KEEPER 0
.param PULLTYPE_NONE 1
.param PULLTYPE_PULLDOWN 0
.param PULLTYPE_PULLUP 0
.param SLEW "SLOW"
.param SSTL135_DRIVE_I_FIXED 0
.param SSTL135_SSTL15_SLEW_FAST 0
.end

I'll take care of the show issue; otherwise, this is a symbiflow bug


QEMU MicroVM: why such bad results and why not in the Firecracker paper?

Dear Firecracker paper authors,
While looking at some other paper (https://github.com/rellermeyer/container_benchmarks/issues/1), I noticed the unexplainably bad results of QEMU's MicroVM in your GitHub repo.
Here is the QEMU MicroVM command line: https://github.com/firecracker-microvm/nsdi2020-data/blob/cf1b30f674523ee44363f74e16bcb301ffb10598/scripts/util_start_qemu_uvm.sh
Here is the commit that added QEMU MicroVM data: https://github.com/firecracker-microvm/nsdi2020-data/commit/b35147fbc1e51754757c6aaad04dcd219b1f45df
You also updated all the plots, some of them include QEMU MicroVM perf, especially this one: https://github.com/firecracker-microvm/nsdi2020-data/blob/master/data/m5d.metal/boot-serial-all.pdf
If I'm reading the plot correctly, and if I'm not confusing two shades of "light blue", then QEMU MicroVM exhibits extremely bad boot time (~600ms, about 2.5x worse than normal QEMU).
I also notice that your final paper https://www.usenix.org/system/files/nsdi20-paper-agache.pdf doesn't mention QEMU MicroVM at all (this may be just timing issues, since your GitHub updates are dated with 9. February and the NSDI conference was on 25. February).
So I have two questions:

Do you have any explanations on QEMU MicroVM boot times? Did you maybe expand on this in some follow-up paper, video, blog, etc?
How can you explain the fact that QEMU's MicroVM behaves worse than normal QEMU ( with normal machine type)?
Why didn't you include any mentions of QEMU's MicroVM in the final paper?

Hi Dmitrii. Let us take a look here, and we'll get back to you in a few days. Thanks, Radu


useAsyncFn: keeping the previous state when start running the async function

Description
useAsyncFn - keeping the previous state when start running the async function [#934]
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as before)

Checklist

[x] Read the Contributing Guide
[x] Perform a code self-review
[x] Comment the code, particularly in hard-to-understand areas
[x] Add documentation
[x] Add hook's story at Storybook
[x] Cover changes with tests
[x] Ensure the test suite passes (yarn test)
[x] Provide 100% tests coverage
[x] Make sure code lints (yarn lint). Fix it with yarn lint:fix in case of failure.
[x] Make sure types are fine (yarn lint:types).

Thanks!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Please, add Spanish translation (es)

Greetings.
First of all, thank you so much for this fantastic app!
On the other hand, would you mind providing a Spanish translation, please?
Thank you again for your work and your time!

Done in this action build: https://github.com/aj3423/SpamBlocker/actions/runs/9489868059

Done in this action build: https://github.com/aj3423/SpamBlocker/actions/runs/9489868059

Quite decent.
Thanks!

It shows "Copy" when the text in the inputbox is exactly the same as the current json configuration(including the language), because importing a same configuration would be unnecessary.
When the language is changed, the current configuration becomes different, then it shows "Import".
To force import a configuration, you can add a space somewhere to make the text different, or export/import as compressed format.

Oh, that makes sense.
Thanks, and sorry for wasting your time!
Have a nice weekend.


1.1.7

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Overview of Changes

Include a bulleted list of high level changes here.

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Additional Notes
Please add any additional notes regarding this pull request here.

You did it @dinakarmeda!
Thank you for signing the Anthem Opensource Software CLA.


not_a_PNG_(too_short) 035A4301_17.png

Some errors (not_a_PNG_(too_short) ) occur when running the script preprocess_comp1k_dataset.py. Please see below logs.
python preprocess_comp1k_dataset.py data/adobe_composition-1k data/coco data/VOCdevkit --composite
preparing training data...
[                                                  ] 16/43100, 0.6 task/s, elapsed: 27s, ETA: 72203sOS2K ERR 08 read Success Success not_a_PNG_(too_short) 035A4301_17.png
[                                                  ] 27/43100, 0.6 task/s, elapsed: 46s, ETA: 72869sOS2K ERR 08 read Success Success not_a_PNG_(too_short) 035A4301_28.png
[                                                  ] 28/43100, 0.6 task/s, elapsed: 46s, ETA: 70922sOS2K ERR 08 read Success Success not_a_PNG_(too_short) 035A4301_28.png
[                                                  ] 32/43100, 0.6 task/s, elapsed: 52s, ETA: 70576sOS2K ERR 08 read Success Success not_a_PNG_(too_short) 035A4301_34.png
[                                                  ] 34/43100, 0.6 task/s, elapsed: 57s, ETA: 71997sOS2K ERR 08 read Success Success not_a_PNG_(too_short) 035A4301_35.png
[                                                  ] 36/43100, 0.6 task/s, elapsed: 58s, ETA: 69967sOS2K ERR 08 read Success Success not_a_PNG_(too_short) 035A4301_37.png

You can safely ignore the warning. Once there was a note on doc

We may consider adding it back

Note that we also run pngfix after the processing. Please do report back if the generated files are not usable.

There are indeed some dad png files generated as they have zero byte. Please see below logs:
[>>>>>>>>>>>>>>>>                                  ] 322/1000, 1.6 task/s, elapsed: 202s, ETA:   425sOS2K ERR 08 read Success Success not_a_PNG_(too_short) girl-1219339_1920_3.png

Does this occur constantly?

Does this occur constantly?

It seems that the error info occurs differently each time. In other words, the .png file with zero byte have different filename each time I run the script. Therefore, I've replaced those zero byte files with correct .png resulted by the last running. Although, it is not authentic solution, it works. Hopes anyone can share the reason why generating .png with zero byte ?

I'm not sure about the reason yet... My last attempt was successful. Lets wait and see if others met the same problem

Closing due to inactivity, please reopen if there are any further problems.