Improve Docker support

This PR improves Docker support. As a result, build time decreases a lot, it's easier to use Docker for development, and less network traffic.

use local clone for building the image (instead of cloning remote repository)
use local Dockerfile to build Helpy instead of pulling remote helpy/helpy in docker-compose to make development much easier
copy only necessary parts in early steps of the build to improve build speed, and only in the end copy rest of the content
merge multiple configurations to docker/.env{,.sample} to make configuration easier
move PostgreSQL data directory to temporary volume
update documentation to match current status
etc.

Thanks for this work @ypcs 👍  One question... I saw you moved the location of the postgres database - is this still retained between updates when running in production?  How will this affect production installations that are already running Postgres in the prior location?

Data is retained between updates after switching to this new volume, it's just stored in Docker volume directory instead of $(pwd)/postgres. You can list current Docker volumes with docker volume ls. Default name seems to be <name of current directory>_postgres, ie. for me this looks like
$ docker volume ls
DRIVER              VOLUME NAME
local               helpy_postgres
local               helpy_rails-assets

And if I'm interested in more details, docker volume inspect <volume> comes to help,
$ docker volume inspect helpy_postgres
[
    {
        "CreatedAt": "2018-10-22T20:18:17+03:00",
        "Driver": "local",
        "Labels": null,
        "Mountpoint": "/var/lib/docker/volumes/helpy_postgres/_data",
        "Name": "helpy_postgres",
        "Options": null,
        "Scope": "local"
    }
]

These volumes persist, until removed by user, eg. by running docker-compose rm. Tested by running
# do the initial build & run container
docker-compose build
docker-compose up -d

# make changes to helpy code
echo "#mychange" >>README.md

# rebuild the image & relaunch
docker-compose build
docker-compose up -d

# now running updated code, and contents in postgres volume were kept
# also by looking data via `docker volume inspect <volume>` timestamps weren't changed

HOWEVER current installations (created with volume ./postgres:...) will not switch to use this new path without manual step, like. sudo cp -a postgres/* /var/lib/docker/volumes/helpy_postgres/_data/.
I'm fine if that single commit (6f86519) gets dropped, workflow will be enhanced anyways.

@scott is the behaviour described above OK, or should I remove changes to Postgres data directory? (And perhaps create separate PR from it.)

@ypcs I think breaking that into its own PR would make sense, since it does represent a breaking change for anyone using the current compose layout.

I dropped commit containing changes to Postgres data directory. Will create separate pull request from it.

Having a solid Dockerfile in the project is important for attracting new contributors. It is so much simpler to test and develop Helpy if a simple git clone+ docker build + docker run is enough to get a dev environment running. This PR is an important step towards that. Please @scott consider merging this soon. Thanks!

hey @ypcs this PR is generating a bunch of errors, which the previous one did not.  Can you take a look so I can get it merged in?

It seems that renaming scss-lint to scss_lint (as suggested by output from bundle install) broke the tests, so I removed that change. It was anyways out-of-scope for this PR.


Journal not sync in masters

Alluxio Version:
2.6.1
Describe the bug
The journal between masters cannot be synchronized. When the leader loses contact, another master is elected as the leader. This situation will cause journal data inconsistencies.
To Reproduce

Start alluxio cluster with 3 masters.
Start sync one path (use alluxio fs startSync /xxxx).
Observe the size of journals of different masters. We can find that the leader's journal grows very fast, but the follwer master's journal hardly grows.
kill leader.  Another master will be elected as the leader. New Leader will write journal.
Start the killed master node.  It will be re-elected as the leader.

@jffree can you check if snapshots are taken successfully on the followers? and if there are any log entries indicating errors in the journal system?


Add Metafield Resource

Adds the general Metafield resource (e.g. client.Metafield.List(...))
Adds metafields to Product resource (e.g. client.Product.ListMetafields(...))

Codecov Report

Merging #90 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #90   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          17     18    +1
  Lines         513    572   +59
=====================================
+ Hits          513    572   +59

Impacted Files
Coverage Δ

oauth.go
100% <ø> (ø)
:arrow_up:

metafield.go
100% <100%> (ø)

util.go
100% <100%> (ø)
:arrow_up:

product.go
100% <100%> (ø)
:arrow_up:

goshopify.go
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Can't generate letsencrypt certs with dns-01 challenge

Describe the bug:
When adding certificates to my cluster, the certificate is never generated. The certificate describe last entry is something along the lines of
Events:
  Type    Reason        Age   From          Message
  ----    ------        ----  ----          -------
  Normal  GeneratedKey  2m9s  cert-manager  Generated a new private key
  Normal  Requested     2m8s  cert-manager  Created new CertificateRequest resource "mydomain-com-364056456"

Expected behaviour:
Certificate is generated from letsencrypt and Status of k8s certificate moves from 'False' to 'True'
Steps to reproduce the bug:
Deployment of cert-manager was done as follows:
kubectl apply --validate=false -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.11/deploy/manifests/00-crds.yaml
kubectl create namespace cert-manager
kubectl label namespace cert-manager certmanager.k8s.io/disable-validation=true
helm install cert-manager --namespace cert-manager --version v0.11.0 jetstack/cert-manager --set 'extraArgs={--dns01-recursive-nameservers=<IP_ADDRESS>:53,<IP_ADDRESS>:53}'

I'm using the following manifests to setup cert manager
cloudflare dns secret
apiVersion: v1
kind: Secret
metadata:
  name: cloudflare-dns
type: Opaque
data:
  api-key: base64mumble=

clusterissuer.yaml
apiVersion: cert-manager.io/v1alpha2
kind: ClusterIssuer
metadata:
  name: letsencrypt
spec:
  acme:
    server: https://acme-v02.api.letsencrypt.com/directory
    email<EMAIL_ADDRESS>    privateKeySecretRef:
      name: letsencrypt
    dns01:
      providers:
      - name: cf-dns
        cloudflare:
          email<EMAIL_ADDRESS>          apiKeySecretRef:
            name: cloudflare-dns
            key: api-key

certificate.yaml
apiVersion: cert-manager.io/v1alpha2
kind: Certificate
metadata:
  name: mydomain-com
  namespace: default
spec:
  secretName: mydomain-com-tls
  issuerRef:
    name: letsencrypt
  commonName: '*.mydomain.com'
  dnsNames:
  - mydomain.com
  acme:
    config:
    - dns01:
        provider: cf-dns
      domains:
      - '*.mydomain.com'
      - mydomain.com

After creating the certificate, I see the following in the certmanager kube logs:
I1122 22:21:31.284246       1 controller.go:129] cert-manager/controller/certificates "level"=0 "msg"="syncing item" "key"="default/mydomain-com"
I1122 22:21:31.291444       1 sync.go:361] cert-manager/controller/certificates "level"=0 "msg"="no existing CertificateRequest resource exists, creating new request..." "related_resource_kind"="Secret" "related_resource_name"="mydomain-com-tls" "related_resource_namespace"="default" "resource_kind"="Certificate" "resource_name"="mydomain-com" "resource_namespace"="default"
I1122 22:21:31.325576       1 controller.go:129] cert-manager/controller/certificaterequests-issuer-venafi "level"=0 "msg"="syncing item" "key"="default/mydomain-com-364056456"
I1122 22:21:31.332266       1 conditions.go:200] Setting lastTransitionTime for CertificateRequest "mydomain-com-364056456" condition "Ready" to 2019-11-22 22:21:31.332219555 +0000 UTC m=+433.383971845
I1122 22:21:31.334680       1 controller.go:129] cert-manager/controller/certificaterequests-issuer-acme "level"=0 "msg"="syncing item" "key"="default/mydomain-com-364056456"
I1122 22:21:31.336981       1 conditions.go:200] Setting lastTransitionTime for CertificateRequest "mydomain-com-364056456" condition "Ready" to 2019-11-22 22:21:31.33696944 +0000 UTC m=+433.388721718
I1122 22:21:31.337452       1 controller.go:129] cert-manager/controller/certificaterequests-issuer-ca "level"=0 "msg"="syncing item" "key"="default/mydomain-com-364056456"
I1122 22:21:31.337517       1 conditions.go:200] Setting lastTransitionTime for CertificateRequest "mydomain-com-364056456" condition "Ready" to 2019-11-22 22:21:31.337512577 +0000 UTC m=+433.389264855
I1122 22:21:31.337688       1 controller.go:129] cert-manager/controller/certificaterequests-issuer-selfsigned "level"=0 "msg"="syncing item" "key"="default/mydomain-com-364056456"
I1122 22:21:31.337740       1 conditions.go:200] Setting lastTransitionTime for CertificateRequest "mydomain-com-364056456" condition "Ready" to 2019-11-22 22:21:31.337736623 +0000 UTC m=+433.389488901
I1122 22:21:31.337903       1 controller.go:129] cert-manager/controller/certificaterequests-issuer-vault "level"=0 "msg"="syncing item" "key"="default/mydomain-com-364056456"
I1122 22:21:31.337946       1 conditions.go:200] Setting lastTransitionTime for CertificateRequest "mydomain-com-364056456" condition "Ready" to 2019-11-22 22:21:31.337942539 +0000 UTC m=+433.389694819
I1122 22:21:31.348491       1 sync.go:373] cert-manager/controller/certificates "level"=0 "msg"="created certificate request" "related_resource_kind"="Secret" "related_resource_name"="mydomain-com-tls" "related_resource_namespace"="default" "resource_kind"="Certificate" "resource_name"="mydomain-com" "resource_namespace"="default" "request_name"="mydomain-com-364056456"
E1122 22:21:31.349326       1 pki.go:128] cert-manager/controller/certificates "msg"="error decoding x509 certificate" "error"="error decoding cert PEM block" "related_resource_kind"="Secret" "related_resource_name"="mydomain-com-tls" "related_resource_namespace"="default" "resource_kind"="Certificate" "resource_name"="mydomain-com" "resource_namespace"="default" "secret_key"="tls.crt"
I1122 22:21:31.349693       1 conditions.go:155] Setting lastTransitionTime for Certificate "mydomain-com" condition "Ready" to 2019-11-22 22:21:31.349682206 +0000 UTC m=+433.401434528
E1122 22:21:31.387649       1 controller.go:131] cert-manager/controller/certificaterequests-issuer-acme "msg"="re-queuing item  due to error processing" "error"="Operation cannot be fulfilled on certificaterequests.cert-manager.io \"mydomain-com-364056456\": the object has been modified; please apply your changes to the latest version and try again" "key"="default/mydomain-com-364056456"
I1122 22:21:31.387719       1 controller.go:129] cert-manager/controller/certificaterequests-issuer-acme "level"=0 "msg"="syncing item" "key"="default/mydomain-com-364056456"
I1122 22:21:31.387846       1 controller.go:135] cert-manager/controller/certificaterequests-issuer-acme "level"=0 "msg"="finished processing work item" "key"="default/mydomain-com-364056456"
I1122 22:21:31.389680       1 controller.go:135] cert-manager/controller/certificaterequests-issuer-venafi "level"=0 "msg"="finished processing work item" "key"="default/mydomain-com-364056456"
I1122 22:21:31.389728       1 controller.go:129] cert-manager/controller/certificaterequests-issuer-venafi "level"=0 "msg"="syncing item" "key"="default/mydomain-com-364056456"
I1122 22:21:31.389904       1 controller.go:135] cert-manager/controller/certificaterequests-issuer-venafi "level"=0 "msg"="finished processing work item" "key"="default/mydomain-com-364056456"
E1122 22:21:31.443118       1 controller.go:131] cert-manager/controller/certificaterequests-issuer-vault "msg"="re-queuing item  due to error processing" "error"="Operation cannot be fulfilled on certificaterequests.cert-manager.io \"mydomain-com-364056456\": the object has been modified; please apply your changes to the latest version and try again" "key"="default/mydomain-com-364056456"
I1122 22:21:31.443937       1 controller.go:129] cert-manager/controller/certificaterequests-issuer-vault "level"=0 "msg"="syncing item" "key"="default/mydomain-com-364056456"
I1122 22:21:31.445985       1 controller.go:135] cert-manager/controller/certificaterequests-issuer-vault "level"=0 "msg"="finished processing work item" "key"="default/mydomain-com-364056456"
E1122 22:21:31.446597       1 controller.go:131] cert-manager/controller/certificaterequests-issuer-selfsigned "msg"="re-queuing item  due to error processing" "error"="Operation cannot be fulfilled on certificaterequests.cert-manager.io \"mydomain-com-364056456\": the object has been modified; please apply your changes to the latest version and try again" "key"="default/mydomain-com-364056456"
I1122 22:21:31.446906       1 controller.go:129] cert-manager/controller/certificaterequests-issuer-selfsigned "level"=0 "msg"="syncing item" "key"="default/mydomain-com-364056456"
I1122 22:21:31.447279       1 controller.go:135] cert-manager/controller/certificaterequests-issuer-selfsigned "level"=0 "msg"="finished processing work item" "key"="default/mydomain-com-364056456"
E1122 22:21:31.447780       1 controller.go:131] cert-manager/controller/certificaterequests-issuer-ca "msg"="re-queuing item  due to error processing" "error"="Operation cannot be fulfilled on certificaterequests.cert-manager.io \"mydomain-com-364056456\": the object has been modified; please apply your changes to the latest version and try again" "key"="default/mydomain-com-364056456
"
I1122 22:21:31.449332       1 controller.go:129] cert-manager/controller/certificaterequests-issuer-ca "level"=0 "msg"="syncing item" "key"="default/mydomain-com-364056456"
I1122 22:21:31.449878       1 controller.go:135] cert-manager/controller/certificaterequests-issuer-ca "level"=0 "msg"="finished processing work item" "key"="default/mydomain-com-364056456"
I1122 22:21:31.458493       1 controller.go:135] cert-manager/controller/certificates "level"=0 "msg"="finished processing work item" "key"="default/mydomain-com"
I1122 22:21:31.458546       1 controller.go:129] cert-manager/controller/certificates "level"=0 "msg"="syncing item" "key"="default/mydomain-com"
I1122 22:21:31.459628       1 sync.go:379] cert-manager/controller/certificates "level"=0 "msg"="validating existing CSR data" "related_resource_kind"="CertificateRequest" "related_resource_name"="mydomain-com-364056456" "related_resource_namespace"="default" "resource_kind"="Certificate" "resource_name"="mydomain-com" "resource_namespace"="default"

Anything else we need to know?:
I've deleted all of the following and tried again:

certificate
clusterissuer
cloudflare secret
tls secret (mydomain-com-tls)

Traefik and other acme certbots in my env work, so I'm sure my cloudflare config is correct.
However, I am base64 encoding my api key, so not sure if that's a factor?
Environment details::

Kubernetes version (e.g. v1.10.2): 1.16.2
Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): Rancher
cert-manager version (e.g. v0.4.0): v0.11.0
Install method (e.g. helm or static manifests): helm

/kind bug

I second that, DNS01 challenge doesn't work for me on clean 0.11 install.
always treats the cert as it would be processed by CA solver..

This works in 0.12.0. Will close.


Investigate Sonar improvments

To try and split out FE and BE reporting by specifying we are a "monorepo". https://docs.sonarsource.com/sonarcloud/advanced-setup/monorepo-support/#convert-a-standard-project
Talk to Joseph Anderson if you have questions around why/what it should look like.

I created a test branch and made an isolated commit that affected back-end only.  The findings did not overwrite -- they accumulated in Sonar:

I think this is a non-issue because as @snesm mentioned "the SonarCloud functionality has been moved to a separate workflow so that it no longer directly impacts the frontend and backend builds".


Fix Failing Unit Tests, Add Integration Tests and update to HQRM

We're wanting to use this module in configs, but at the moment the unit tests are failing and so this would introduce too much risk for us if used in the current state.
After looking through the code it looks like this module could use some TLC to bring it up to current standards and reduce the tech debt.
I'll look at reworking this resource to meet HQRM guidelines over the next few weeks - @kwirkykat  - is this OK with you?
The following tasks need to be performed (IMHO):

[ ] Fix Unit Tests
[ ] Update unit tests to use standard templates
[ ] Add Integration Tests
[ ] Update documentation to meet minimum standards
[ ] Change references to OneGet to PSGet (?)
[ ] Convert Localization strings handling to standard folder structure

There will be other tasks required, but these are the basic ones I have identified.

Testing failures are caused by NuGet provider regression bug which fails to find-packages from local share.

@PlagueHO This module actually isn't currently part of the DSC Resource Kit (though I would be willing to add it). I think the PowerShell Get/Gallery sister team has ownership over this repository.
The improvements suggested here would be invaluable regardless of whether it's in the res kit or not.

Oh right!  I had no idea. I guess that explains why it doesn't meet the naming conventions.
TBH our teams use this module extensively. However we do have a guideline that we don't use resources outside the reskit or the Powershell.org ones due to the risk that comes with not having good test coverage or support.
What are the chances of bringing this resource under your umbrella? I'm happy to help out as this is much better than reverting to using xScript. :) and this resource is so awesome! !

how about bring it into windows inbox as a part of PackageManagement(OneGet), what do you think?

@jianyunt - I'm definitely OK with it being under PS PackageManagement. My main goal is to make sure there is adequate unit and integration test coverage to control risk. So, whatever is the best plan to enable that. As I said, I'm always happy to commit code if it helps (especially tests :grin:)

@PlagueHO, we absolutely appreciate contributions from the Community.
BTW, I am fixing these tests in WIP branch. Will PR to master today.

@jianyunt - Awesome! I know the HQRM guidelines the DSC team have created don't apply to this resource module, but they do result reducing risk using a DSC resource. If I were to work on changes to bring this module up to HQRM quality standards at some point, is this something that your team would be interested in?
This wouldn't be for a while yet as I have a significant back log of work on other DSC resources to get through first.

@PlagueHO, you are welcome to make the module higher quality. Feel free to send us your PR.  thank you!

This issue was moved to OneGet/oneget#253

test is fixed.


Unexpected Exception: KeyError 'uuid'

I noticed in the examples of the README.md that the classes have a uuid.  However, my model does not:
class hprItem(BaseModel):     s_id: str     start_time: str     end_time: str     recurring: str     c_id: int     s_id: int     t_id: str
When I try to add an instance of the above class to the database, it throws a keyerror.
Is there a requirement that your pydantic models have to have a uuid?

Hello,
I am using sqlite-utils.Database and this need a primary key "pk" as identifier. So you need an identifierin your models. I am using a uuid for this. If you want to use anything other than uuid as p key you can set it with the param pk when adding a model.
https://github.com/Phil997/pydantic-sqlite/blob/d52d0f42045c90b47a8e6987ec60dd071444f427/pydantic_sqlite/_core.py#L83
I hope it helps.


added dependency for pcdfilter_pa (parameter_pa) on indigo

@peterweissig Package dependencies are captured in the package.xml rather than the distribution file. The recommended way to introduce documentation dependency is to use package format2 (schema, REP and migration guide ) and to declare your dependency using the <doc_depend> tag

Adding dependencies for doc jobs is valid. See REP 141 for this.
The value needs to be a list though and can't be a single name. Please format your patch as in this example: https://github.com/ros/rosdistro/blob/59ee1c91559850af0a38e828b51371449ce56261/kinetic/distribution.yaml#L3990-L3991

Adding dependencies for doc jobs is valid. See REP 141 for this.

Oh I look at the wrong REP, thanks for pointing it out. And please discard my previous comment then


Fixes interface for failing nomad tests

This should fix the failing tests here: https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/jobs/2181921
@sanbrock I'm not entirely sure if I should just use the first element of the list or use a for-loop. But in the failing tests this were always one-element lists so I thought it may be fine like this. But please let me know if we should solve this differently.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage remained the same at 53.801%

Files with Coverage Reduction
New Missed Lines
%

pynxtools/nyaml2nxdl/nyaml2nxdl_forward_tools.py
1
79.04%

pynxtools/nexus/nexus.py
3
73.78%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5096

Relevant Lines:
9472

💛  - Coveralls


bumped alpine version to 3.15.4 to fix CVE-2022-28391

Root Cause : Trivy scanner shows the following security vulnerabilities
nexentastor-csi-driver-block:master (alpine 3.15.0)
Total: 6 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 4, CRITICAL: 2)
Proposed Fix : Bump dependant image version to those that have the issues fixed
Testing Done : trivy image nexentastor-csi-driver-block:master

after update:
nexentastor-csi-driver-block:master (alpine 3.15.4)
Total: 0 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0)
nexentastor-csi-driver-block/nexentastor-csi-driver-block
Total: 3 (UNKNOWN: 1, LOW: 1, MEDIUM: 1, HIGH: 0, CRITICAL: 0)


Guide to securing a ClickHouse installation?

Sorry for this "meta" issue but I'm trying to enable TLS and generally reduce the attack surface of a ClickHouse deployment and I cannot find any related documentation or issue. Here's what I'm trying to achieve at the moment (there's probably more to it in the long run but that's a start):

Enable TLS with a robust configuration using TLSv1.3 only
Disable protocols that are unused, namely:
a. MySQL (port 9004)
b. PostgreSQL (port 9005)
c. gRPC (port 9100)
d. tcp_with_proxy_port (I don't even know that this one is), ie port 9011
If possible, also disable non-TLS enabled protocols, ie:
a. HTTP (port 8123)
b. interserver HTTP (port 9009)
c. client (port 9000)

EDIT: related Hardening Guide
1. Enable TLS with a robust configuration using TLSv1.3 only
I have the following in spec.configuration.clusters[0].settings (should hostTemplate be used instead?):
      tcp_port_secure: 9440
      https_port: 8443
      interserver_https_port: 9010
      openSSL/server/certificateFile: "/etc/clickhouse-server/certs/server.crt"
      openSSL/server/privateKeyFile: "/etc/clickhouse-server/certs/server.key"
      openSSL/server/caConfig: "/etc/clickhouse-server/certs/ca.crt"
      openSSL/server/loadDefaultCAFile: false
      openSSL/server/verificationMode: "relaxed"
      openSSL/server/disableProtocols: "sslv2,sslv3,tlsv1,tlsv1_1,tlsv1_2"
      openSSL/server/preferServerCiphers: false
      openSSL/server/requireTLSv1: false
      openSSL/server/requireTLSv1_1: false
      openSSL/server/requireTLSv1_2: false
      openSSL/server/requireTLSv1_3: true
      openSSL/server/cacheSessions: false
      openSSL/client/caConfig: "/etc/clickhouse-server/certs/ca.crt"
      openSSL/client/loadDefaultCAFile: false
      openSSL/client/verificationMode: "relaxed"
      openSSL/client/disableProtocols: "sslv2,sslv3,tlsv1,tlsv1_1,tlsv1_2"
      openSSL/client/preferServerCiphers: false
      openSSL/client/requireTLSv1: false
      openSSL/client/requireTLSv1_1: false
      openSSL/client/requireTLSv1_2: false
      openSSL/client/requireTLSv1_3: true
      openSSL/client/cacheSessions: false

How can I get the certificate files mounted from secrets? I've only seen advice to use the files directive which is a no-go in a GitOps environment as the certificate key cannot be in the charts.
2. Disable protocols that are unused
I have no idea how to get started as when no port is specified, it gets interpreted as if the default port is desired.
3. Disable non-TLS enabled protocols
This is more of a question about feasibility as I don't even know if this would work because I think that the HTTP /ping endpoint is used for liveness probes, etc.

@rolinh , looks like we need to write a comprehensive security guide.
ClickHouse settings should got to spec.configuration.settings. Usually you run one cluster per ClickHouse installation (in fact, we recommend doing that), so no need to go to cluster level settings.

https://github.com/Altinity/clickhouse-operator/blob/master/docs/security_hardening.md
cc @bkuschel @rolinh


Update to Unicode 14.0 Beta

Closes #12.
Let's try...

First-time contributors need a maintainer to approve running workflows

:smile:

Can I make a PR for Contour with updated version of this library? :)

oh yes, please. Many thanks :)


Incompatible

Are you ending support for Android 8.0.0?

Yes, support has ended, and 8.1 support will be dropped soon as well.


Add support for subpath imports and subpath patterns

Following up from #87, subpath imports and subpath patterns should get some love too.

With v2 released I think we can close this issue :)


Need to add "enableNoPublicIp" as true in the properties, clearly says not to

This is misleading: "Add the parameter (not as a property) to one of the following templates" - it is meant to go under the "properties" attribute

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

ID: 958bd4e0-a052-a55e-7a37-1cbcdbf2dbbe
Version Independent ID: 1b74b0d1-c984-4fd0-899f-72ae6437c286
Content: Secure cluster connectivity - Azure Databricks
Content Source: databricks/security/secure-cluster-connectivity.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@hariAtCba - Thanks for posting the inputs. Below is sample ARM template section and "not as a property" refers to not property under "properties" attribute and it should be added as parameter inside it.
It appears clear from the documentation, please suggest if you think otherwise.
{             'type': 'Microsoft.Databricks/workspaces',             'apiVersion': '2018-04-01',             'name': '[parameters('workspaceName')]',             'location': '[parameters('location')]',             'dependsOn': [],             'tags': {                 'data platform': 'warehouse'             },             'sku': {                 'name': 'standard'             },             'properties': {                 'ManagedResourceGroupId': '[variables('managedResourceGroupId')]',                 'parameters': {                     'enableNoPublicIp': {                         'value': true                     }                 }             }         }

@hariAtCba - I will proceed to close the issue now. Please feel free to post for any further queries.

I get it now, it just initially reads a bit different because I initially didn’t even look in the properties object for the parameters attribute, initially thought to just add it outside of the properties object altogether.
From: HarithaMaddi-MSFT<EMAIL_ADDRESS>Sent: Tuesday, 3 November 2020 5:18 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Hari Veerakumar<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Need to add "enableNoPublicIp" as true in the properties, clearly says not to (#65435)
@hariAtCbahttps://github.com/hariAtCba - Thanks for posting the inputs. Below is sample ARM template section and "not as a property" refers to not property under "properties" attribute and it should be added as parameter inside it.
It appears clear from the documentation, please suggest if you think otherwise.
{ 'type': 'Microsoft.Databricks/workspaces', 'apiVersion': '2018-04-01', 'name': '[parameters('workspaceName')]', 'location': '[parameters('location')]', 'dependsOn': [], 'tags': { 'data platform': 'warehouse' }, 'sku': { 'name': 'standard' }, 'properties': { 'ManagedResourceGroupId': '[variables('managedResourceGroupId')]', 'parameters': { 'enableNoPublicIp': { 'value': true } } } }
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/65435#issuecomment-720926927, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQHOLUFIIEZD5L5HVA2CWBTSN6OCTANCNFSM4TIIWBGA.
************** IMPORTANT MESSAGE *****************************
This e-mail message is intended only for the addressee(s) and contains information which may be
confidential.
If you are not the intended recipient please advise the sender by return email, do not use or
disclose the contents, and delete the message and any attachments from your system. Unless
specifically indicated, this email does not constitute formal advice or commitment by the sender
or the Commonwealth Bank of Australia (ABN 48 123 123 124 AFSL and Australian credit licence 234945)
or its subsidiaries.
We can be contacted through our web site: commbank.com.au.
If you no longer wish to receive commercial electronic messages from us, please reply to this
e-mail by typing Unsubscribe in the subject line.


customInput remounts on every render

Hi, I think there's a performance issue when using customInput option with react-datepicker. The provided custom input gets created/mounted on every render of the parent.
The problem can be seen in this sandbox:

Here I was testing it together with react-hook-form, but I commented the integration to prove the problem is on the datepicker. I followed the example here -> https://reactdatepicker.com/#example-custom-input.
I added local state (open) to force parent rendering, and useEffect to log the element remounting.
This may not seem like a big problem, but this is a simple example. On my project I'm using a heavier custom element and the performance hit is pretty obvious.
I don't know if the solution is fixable here or I'm gonna have to use some kind of hook/memoization. Any clues?
Thanks and keep up the good work !

OS: Ubuntu on WLS
Browser Chrome
Version 86

Oh, and seems forwardRef is also necessary, as commented by @Psvensso on this other issue https://github.com/Hacker0x01/react-datepicker/issues/2397#issuecomment-707048538

Same here. This is even more visible when you pass onChange handler, and try to manually type the date. You will lose focus on each render.
In my case, adding useMemo hook solve the issue
const CustomInput = React.useMemo(
  () => forwardRef((props, ref) => <input {...props} ref={ref} />),
  [],
);

Same here. This is even more visible when you pass onChange handler, and try to manually type the date. You will lose focus on each render.
In my case, adding useMemo hook solve the issue
const CustomInput = React.useMemo(
  () => forwardRef((props, ref) => <input {...props} ref={ref} />),
  [],
);

Could you post a full example of this? Thanks!

If anyone is looking for full example here it is with custom tailwind component
const DatePicker = ({
  value,
  onChange,
  label,
  showError,
  placeholder,
}: IDatePicker): JSX.Element => {
  const ref = createRef<HTMLInputElement>();

  const CustomInput = useMemo(
    () =>
      forwardRef<HTMLInputElement, unknown>(({ ...rest }) => (

          {label && {label}}
          <input
            ref={ref}
            {...rest}
            className={!value && showError ? 'input-error' : ''}
            type="text"
            autoComplete="bday"
          />
          <Icon
            className={`absolute text-gray-500 right-4 ${
              label ? '' : '-translate-y-1/2'
            } top-1/2 transform stroke-current`}
            name="calendar"
          />

      )),
    []
  );

  return (
    <ReactDatePicker
      customInput={<CustomInput ref={ref} />}
      selected={value}
      locale={ru}
      dateFormat="dd.MM.yyyy"
      portalId="root"
      onChange={onChange}
      placeholderText={placeholder}
    />
  );
};

If anyone is looking for full example here it is with custom tailwind component
const DatePicker = ({
  value,
  onChange,
  label,
  showError,
  placeholder,
}: IDatePicker): JSX.Element => {
  const ref = createRef<HTMLInputElement>();

  const CustomInput = useMemo(
    () =>
      forwardRef<HTMLInputElement, unknown>(({ ...rest }) => (

          {label && {label}}
          <input
            ref={ref}
            {...rest}
            className={!value && showError ? 'input-error' : ''}
            type="text"
            autoComplete="bday"
          />
          <Icon
            className={`absolute text-gray-500 right-4 ${
              label ? '' : '-translate-y-1/2'
            } top-1/2 transform stroke-current`}
            name="calendar"
          />

      )),
    []
  );

  return (
    <ReactDatePicker
      customInput={<CustomInput ref={ref} />}
      selected={value}
      locale={ru}
      dateFormat="dd.MM.yyyy"
      portalId="root"
      onChange={onChange}
      placeholderText={placeholder}
    />
  );
};

Cheers! Did you also manage to make this component responsive on phones when including time?


Add cmd line arguments

Hello,
I find it frustrating that one of the best terminals does not offer us the possibility to add command line arguments for port forwarding and save those to a connection.
Something like: -L 5444:localhost:5432
Thank you

I find it frustrating that everybody thinks that every single SSH client is a thin wrapper around OpenSSH.
Duplicate of #2395


[I18N] update (IT) and (hi) strings.xml

useful for #1909 and #1918
Some more updates to strings.xml and #1918 would be good to go for🚀

@GOVINDDIXIT Did you translate it by your own or used some service to do it?

I have translated (hi)strings.xml on my own and used google translator for (it)

@GOVINDDIXIT Can you remove the Italian translations from Google Translate from the PR? There's another PR opened from a native speaker. Thank you! 👍

@rafaelks  Sure. I also think that native speaker will be a far better option than google translate 😃


Fix buffer overflow in input handling

kpress function in x.c previously relied on the wrong understanding
of XmbLookupString behavior. When the composed string is longer
than the available buffer, the buffer is not initialized and the
actual length of the data available to read is returned, not
the amount of data written. When that amount is later used to
process the contents of this buffer, not only will the random
contents of the uninitialized buffer be sent directly to the
terminal and whichever application is now running in it, but
possibly also whatever is in the memory after that buffer,
leading to undefined behavior and possible random command execution.

This is a pull request for issue #341


[T3A2][F09-A?]GuoShiMin

Ready for review.

Accepting this PR without a review because another of your PRs for this tutorial was reviewed in detail.


Manifest merger failed with multiple errors, see logs

while upgrading ,implementation 'com.theartofdev.edmodo:android-image-cropper:2.7.0' into
api 'com.theartofdev.edmodo:android-image-cropper:2.8.0' ,Manifest merger failed with multiple errors, see logs issue occurs

bumpity bump

following solution worked for me:
In build.gradle (Module: app)
replace this: api 'com.theartofdev.edmodo:android-image-cropper:2.8.+'
with this: api 'com.theartofdev.edmodo:android-image-cropper:2.7.0'
It may give you warning but works for me.

Thanks its works good now
On Thu 28 Feb, 2019, 1:25 AM BilalRabbani<EMAIL_ADDRESS>wrote:

following solution worked for me:
In build.gradle (Module: app)
replace this: api 'com.theartofdev.edmodo:android-image-cropper:2.8.+'
with this: api 'com.theartofdev.edmodo:android-image-cropper:2.7.0'
It may give you warning but works for me.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ArthurHub/Android-Image-Cropper/issues/654#issuecomment-468006729,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Add2MouqWwCpVE2aBEbZ_BNcVMYTFjCNks5vRuK2gaJpZM4anCP7
.

Migrate to androidX, it's automated from the IDE. It's the way forward now.


fix: check visibility as well to show another login message

Details
Check visibility as well to check if should show another login message
Fixed Issues
$ https://github.com/Expensify/App/issues/34567
PROPOSAL: https://github.com/Expensify/App/issues/34567#issuecomment-1895335442
Tests

Open ND and log out if logged in
[WEB ONLY] Enter email or phone number and tap Continue to go to the magic code page
[WEB ONLY] Open a new tab and navigate to the magic link with wrong magic code and correct domain
[WEB ONLY] Verify that the magic code expired page is displayed
[WEB ONLY] Navigate to the original tab
[WEB ONLY] Verify that the magic code page is opened without any flickering

[x] Verify that no errors appear in the JS console

Offline tests
This should be tested in online mode
QA Steps

Open ND and log out if logged in
[WEB ONLY] Enter email or phone number and tap Continue to go to the magic code page
[WEB ONLY] Open a new tab and navigate to the magic link with wrong magic code and correct domain
[WEB ONLY] Verify that the magic code expired page is displayed
[WEB ONLY] Navigate to the original tab
[WEB ONLY] Verify that the magic code page is opened without any flickering

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/126839717/14873524-8c52-4d78-8c29-f35afe125cad

Android: mWeb Chrome
https://github.com/Expensify/App/assets/126839717/0368d46e-6e71-48ba-a946-b6f06394eac5

iOS: Native
https://github.com/Expensify/App/assets/126839717/22e42aa2-aee3-43fc-ad81-d8fead35701e

iOS: mWeb Safari
https://github.com/Expensify/App/assets/126839717/a54d4dcb-3110-45a6-b10f-8091e765b887

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/126839717/7e216309-98af-4537-9fed-6255981b635d

MacOS: Desktop
https://github.com/Expensify/App/assets/126839717/cc73c6ee-2dac-4f26-a3cb-2f89c9400e74

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

[WEB ONLY] Open a new tab and navigate to the magic link with wrong magic code and correct domain

@s-alves10 Could you tweak this to be something more like "...edit the magic link to make the code invalid, e.g. change the last few digits"? I find it a bit unclear otherwise.

@s-alves10 As mentioned in the issue, I'm not able to reproduce this anymore on staging or main. I also get some weird issues when testing on your PR, e.g. after logging in on the original (leader) tab I get an LHN with only one chat (even though I'm in "Most Recent" mode).

@s-alves10 Could you tweak this to be something more like "...edit the magic link to make the code invalid, e.g. change the last few digits"? I find it a bit unclear otherwise.

Updated

@s-alves10 As mentioned in the issue, I'm not able to reproduce this anymore on staging or main. I also get some weird issues when testing on your PR, e.g. after logging in on the original (leader) tab I get an LHN with only one chat (even though I'm in "Most Recent" mode).

I'm not sure what this means. Can you please test once more? I wasn't able to reproduce what you mentioned. Also the code changes isn't related to LHN at all

Can you please test once more? I wasn't able to reproduce what you mentioned.

Never mind, I managed to repro the same issue on staging!

🚀 Deployed to staging by https://github.com/mountiny in version: 1.4.33-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
cancelled 🔪

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/francoisl in version: 1.4.33-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


add user-defined content to menu items via the params field.

https://gohugo.io/content-management/menus/#params
https://gohugo.io/templates/menu-templates/#using-params-in-menus

resolved and add docs


Error while training DiffusionPrior

I am trying to train a DALL-E-2 diffusion prior, but I get the following error message: ```
RuntimeError                              Traceback (most recent call last)
 in
13 )
14
---> 15 loss = diffusion_prior(text, images)
16 loss.backward()
4 frames
/usr/local/lib/python3.8/dist-packages/clip/model.py in encode_text(self, text)
340         x = self.token_embedding(text).type(self.dtype)  # [batch_size, n_ctx, d_model]
341
--> 342         x = x + self.positional_embedding.type(self.dtype)
343         x = x.permute(1, 0, 2)  # NLD -> LND
344         x = self.transformer(x)
RuntimeError: The size of tensor a (13) must match the size of tensor b (77) at non-singleton dimension 1
I am using a Google Colab notebook and was unable to identify the problem. How do I fix it?

@sr5434 hey Samir, do you want to try the latest version and see if this resolves your issue
@rom1504 was gracious enough to update the depending package

@sr5434 just so you know though, the new SOTA is now OpenClip
highly recommend using their model instead!

The bug still occurs, but with a slightly different error message:
RuntimeError                              Traceback (most recent call last)
[<ipython-input-21-2c767efa316d>](https://localhost:8080/#) in <module>
     13 )
     14
---> 15 loss = diffusion_prior(text, images)
     16 loss.backward()

7 frames
[/usr/local/lib/python3.8/dist-packages/torchvision/transforms/functional_tensor.py](https://localhost:8080/#) in normalize(tensor, mean, std, inplace)
    938     if std.ndim == 1:
    939         std = std.view(-1, 1, 1)
--> 940     return tensor.sub_(mean).div_(std)
    941
    942

RuntimeError: The size of tensor a (30) must match the size of tensor b (3) at non-singleton dimension 0

@lucidrains how do I fix the aforementioned issue?


Mesh not working

Not throwing any errors, but not showing the image that is being displaced, older version seem to work, here's a sample using your demo code but tweaked for the new version (Container instead DisplayObjectContainer, requestAnimationFrame instead of requestAnimFrame, Stage as Container instead of Stage):
I ended up pulling the .js from your demo and it works, but using the latest .js from the site does not show the mesh.
http://staging34.com/pixiTests/demo-sample.html

Yes this is a bug in v3.0.5 and was fixed in the latest dev. I will be doing a release today that includes the fixes.

Just released 3.0.6, this should be fixed now!


Issue: User Model Problems

I've noticed a few issues with the current implementation of the User model in Mongoose that need to be addressed. Here's a breakdown of the problems I've identified:
1. Inconsistent Error Message Style

The error messages for username, email, password, verifyCode, and verifyCodeExpiry fields are inconsistent in terms of tone and structure.

Example: "Email is required" vs "Please use a valid email"

2. Indexing for Unique Fields

username and email are marked as unique, but Mongoose does not create an actual index unless it's explicitly defined. This could lead to issues with enforcing uniqueness at the database level.

3. Handling verifyCode and verifyCodeExpiry

There is no logic in place for validating the verification code's expiration or handling invalid/expired verification codes.

4. Default for createdAt in MessageSchema

The current createdAt field uses default: Date.now, which executes when the model is compiled rather than when the document is created. This could lead to incorrect timestamps.

5. Subdocument vs Reference for messages Field

The messages array in the UserSchema uses the Message schema directly, creating subdocuments instead of references to separate Message documents.

6. Security Concern: Plain-Text Password Storage

Passwords are currently stored in plain text, which is a security risk. The password should be hashed before being saved to the database.

7. Message Type in User Interface

The messages field in the User interface is typed as Message[]. If messages are stored as references (ObjectIds), this type should be updated to reflect that.

@BaibhavTiwari go for it


add playbook to migrate systemd unit to podman

this commit adds a new playbook to force systemd units for containers to
use podman instead of docker.
This is needed in the rhel8 upgrade context so after the base OS is upgraded containers can be started using podman.
Signed-off-by: Guillaume Abrioux<EMAIL_ADDRESS>

wip

jenkins test dev-centos-container-podman

@guits found the issue. I think you removed a taks during the iscsi containerized/systemd refact.
There's a task to create the log directories which isn't present in this PR.
https://github.com/ceph/ceph-ansible/commit/91bef94b6c1ee159173a64cbca36385c67a186de#diff-8543c5196317a6a1ae0edd3392ba0f23R2
Without this task, the rbd-target-{api,gw} services don't start.

@guits I've rebased this PR to include the missing code

jenkins test pipeline

jenkins test dev-centos-non_container-all_daemons


Sign up is two words

pls

I know this is mad easy to fix but I'm working on the report no h8 pls :^)


Searched Seeds Counter

I don't quite understand how the SEARCHED SEEDS counter works, it seems to be a lot higher than actual seeds searched?
The found seed numbers that match the search criteria always go up in numerical order.
So why is the searched seed counter at 200 million, while the next found seed number only goes up by 35 million for example? (went from seed 134,545,678 to seed 170,246,436 while the search seed counter was already over 200 million)
Is the counter just broken or am I misinterpreting something?

Thanks for the report! This is indeed a bug.
The counting code is was working fine for one thread, but for multiple cores the logic doesn't work. The value is basically off by some factor around the number of cores you have in your system.

nice, thanks for the fast fix :)


Update release-notes-azure-cli.md

Docs Build status updates of commit 2465676:
:clock10: Pending: waiting for processors (53 builds ahead of you)
:warning: Docs Build is busy, currently there are 53 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 2465676:
:clock10: Full build: the average full build time is 12 min(s) 32 sec(s), this is based on the last 15 build(s) for this repository.
:warning: This is a FULL build due to the incremental build being disabled in configuration file (.openpublishing.publish.config.json in 'live' branch). For more detailed info, please click here.

Docs Build status updates of commit 2465676:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/release-notes-azure-cli.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 3ce717f:
:clock10: Full build: the average full build time is 10 min(s) 8 sec(s), this is based on the last 16 build(s) for this repository.
:warning: This is a FULL build due to the incremental build being disabled in configuration file (.openpublishing.publish.config.json in 'live' branch). For more detailed info, please click here.

Docs Build status updates of commit 3ce717f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/includes/current-version.md
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid) View (azure-cli-latest)

docs-ref-conceptual/release-notes-azure-cli.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 807e0f6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/includes/current-version.md
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid) View (azure-cli-latest)

docs-ref-conceptual/release-notes-azure-cli.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Documentation regarding registering for notifications

Is there documentation pertaining to registering for push notifications in React Native?
There should be two methods:

with initWithLaunchOptions autoRegister:true|false
[oneSignal registerForPushNotifications];

https://documentation.onesignal.com/docs/ios-sdk-api#registerForPushNotifications

Looks like the functionality exists for sure:

https://github.com/geektimecoil/react-native-onesignal/blob/master/ios/RCTOneSignal/RCTOneSignal.m#L44
https://github.com/geektimecoil/react-native-onesignal/blob/master/ios/RCTOneSignal/RCTOneSignal.m#L79


Hide KUBECONFIG when not in use

what

Hide KUBECONFIG when not in use
Combine service role IAM policies into single managed policy
Add service_ipv4_cidr option

why

When not intending to use KUBECONFIG, values from it were being used anyway, causing problems, particularly for "exec auth".
Fixes #135 (introduced in #132). Supersedes and closes #136.
Closes #130

/test all

/test all


Vite Plugin not re-generating routes with a non-standard Vite root configured

Describe the bug
I've provided minimal example project that demonstrates a potential bug with the TanStack Router Vite Plugin not detecting and generating when using a non-standard vite root configuration. In this example, the vite root config is set to app in the vite.config.ts file. With this configuration, TanStack Router does not detect tsr.config.json in the project root, but will detect it if the file is moved to the app directory. Once moved to the app directory, the TanStack Router Vite plugin will successfully generate the routes on vite dev boot, but will not detect and re-generate based on adding and removing files in the app/routes directory.
Your Example Website or App
https://github.com/a-maas/ts-router-ex
Steps to Reproduce the Bug or Issue

Clone this repository
Run npm install
Run npm run dev
Observe that the routes are generated on boot.
Add a test.tsx file to the app/routes directory.
Observe that the routes are not re-generated.

Expected behavior
As a user, I expect the TanStack Router Vite plugin to re-generate routes when I add and remove files from the configured routes directory, even when Vite is configured with a non-standard root.
Screenshots or Videos
No response
Platform

OS: macOS 14.4
Browser: N/A
Editor: VSCode

Additional context
No response

this PR seems to be related: https://github.com/TanStack/router/pull/1259
do you want to provide a PR to fix this issue?

Thanks for the link, I didn't find that when searching for this issue before submitting. Yes, that PR and related issue look like a very similar issue to what I described above, though, the issue still persists.
I will take some time and try to work out a fix PR. Any guidance would be appreciated since I'm still pretty new to Vite and TSR.

@schiller-manuel it seems like there are two options to fix this. The problem stems from initially setting ROOT to process.cwd(), but later redefining ROOT as vite's configured root. This leads to a mismatch if you have vite's root set to anything other than the process.cwd().
Option 1: To be consistent, use process.cwd() everywhere, which would mean only changing this line to process.cwd() instead of config.root. I'm not sure if this would cause confusion or future issues for people using vite.root.
Option 2: Use vite.root, if set, everywhere, with a process.cwd() fallback. This would have a few consequences:

tsr.config.json would need to be placed at vite.root, not project root, if they were different. In my case, it would need to be placed in ./app instead of project root.
File paths defined in tsr.config.json, like routesDirectory would need to be based on the vite.root, instead of project root, if they are different.

Seems like in the prior PR, you were weighing both of these options, and ended up going with Option 1, but Option 2 may be more desirable.

would option 2 be a breaking change?


Support Lagrange-basis KZG polynomial commitments

Motivation
Commit to z_a, z_b, and w in lagrange basis. For circuits with a lot of boolean constraints, this should reduce the time in the MSM.
Test Plan

(Write your test plan here)
Related PRs

(Link your related PRs here)

LGTM, resampling parameters now

Oh wait, I should have marked this as draft. I'm still some bugs.

No problem!

Ok tests are passing locally, so this is ready for review and then merging. @howardwu, could you benchmark the speed diff between master and this PR?

After regenerating the parameters, tests pass locally, so not sure what's up.

@Pratyush @howardwu  Hello，I've a question to ask you.
I use arkworks-rs/marlin and AleoHQ/snarkVM to study Marlin.
I want to know their performace，so I tried to run benches/bench.rs for  arkworks-rs/marlin  and algorithms/benches/snark/marlin.rs.
I set the same input parameters:
for circuit
num_constraints = 65536 num_variables = 10
for max_degree
num_constraints = 65536 num_variables = 65536 num_non_zero = 3 * 65536
But the result was confusing. I found that “Constructing lagrange_bases” took a long time in AleoHQ/snarkVM.
My profiling:
AleoHQ/snarkVM:
········Start:   Trimming public parameters ··········Start:   Constructing shifted_powers_of_beta_gof size 65535 ··········End:     Constructingshifted_powers_of_beta_gof size 65535 ...........62.926ms ··········Start:   Constructinglagrange_basesof size 65536 ··········End:     Constructinglagrange_bases of size 65536 .....................81.317s ········End:     Trimming public parameters ........................................81.446s
arkworks-rs/marlin:
··Start:   Trimming public parameters
····Start:   Constructing shifted_powers of size 262143
····End:     Constructing shifted_powers of size 262143 ..........................4.351ms
····Start:   Constructing neg_powers_of_h of size 2
····End:     Constructing neg_powers_of_h of size 2 ..............................2.796µs
··End:     Trimming public parameters ..............................................14.008ms
Looking forward to your reply! Thanks!


Remove drat from readme

The drat is no longer up to date and I think as written using the description will pull the cran version of covidregionaldata with no issue. If wanting the development version (maybe to get data fixs?) Should change to the universe and specify that as a repository in the description.

Quick search indicates covidregionaldata is no longer used so I have removed. Looking at the scripts may be a few missing dependencies. In particular Sophie's NHS package though unclear of that is being used either.


Confirm dialog when user deletes favorite

Sorry if I spam you with pull requests 😅
This one is just adding a confirmation message if you try to delete a favorite. I already deleted a couple of my favorites by mistake, without having a second chance to regret it.
This PR also needs to be complemented with Chinese translation.

I will put it to config, let user to choose.

Sounds fair, thanks!


[Q] How can I set retry wait interval of _retry parameter?

I want to retry after 1 hours.
How can I set this?
If this feature is not included, would it be possible to add in next release?

Hello, @jo8937  exponential backoff introduced in v0.9.30
Could you try it?  If it works well, please close this case.
http://docs.digdag.io/workflow_definition.html#retrying-failed-tasks-automatically

@hiroyuki-sato LGTM! Thank you. It is better than what I want. I've tried it and it works fine. I'll close this issue.


Prevent users from moving instanced children

This implements one possible fix for #14648 (the second alternative discussed in the issue).
It discards instancing of modified subscenes without explicitly telling the user about it.
Fixes #14648

But so far you can modify subscenes and keep the instancing information,
not sure why you would want this..
On Thu, Dec 14, 2017 at 7:52 AM, Matthias Hölzl<EMAIL_ADDRESS>wrote:

This implements one possible fix for #14648
https://github.com/godotengine/godot/issues/14648 (the second
alternative discussed in the issue).
It discards instancing of modified subscenes without explicitly telling
the user about it.
Fixes #14648 https://github.com/godotengine/godot/issues/14648
You can view, comment on, or merge this pull request online at:
https://github.com/godotengine/godot/pull/14652
Commit Summary

Discard scene instancing when a child node is moved

File Changes

M editor/scene_tree_dock.cpp
https://github.com/godotengine/godot/pull/14652/files#diff-0 (15)

Patch Links:

https://github.com/godotengine/godot/pull/14652.patch
https://github.com/godotengine/godot/pull/14652.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/14652, or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z26cd4P6gI3V0zB2o1BZuDPtsmL6lks5tAP3hgaJpZM4RB4Ig
.

Ah I see the problem. I think the solution is to simply disallow moving nodes from instanced subscenes. You should only be able to move your own.

I'm happy with any solution that makes it less likely that users end up with a scene file that doesn't reflect what they thought they were doing in the editor. Is something like the latest commit more in line with what you wanted?

Is it still possible to delete nodes inside an instanced subscene?

No, that results in a popup "Can't operate on nodes from a foreign scene!"
The same is true for most of the other operations although "Change Type" changes the type of the node. I guess that should be disallowed as well.


Test the design & implementation split concept together with new properties panel + Camunda Modeler

What should we do?
We want to test the concept of design & implementation split (cf. https://github.com/camunda/camunda-modeler-design/issues/8, Q2 scope). Therefore the new properties panel shall be integrated into the Camunda Modeler in a testing manner.
That includes (tbd):

decide about the properties provider

design:

equals BPMN?
we agreed that we don't have input / output in design for now (due to technical limitations / missing technical concept)

implementation:

equals Zeebe?

add properties-panel-next to Camunda Modeler
focus: only show one BPMN file type (?)
on create: enable Design Properties Provider only (design)
enable implementation in status bar
enable implementation in "fake" group "Execution Properties" in Properties Panel
on enable: add Implementation Properties Provider

Why should we do it?
The new properties panel makes it easier to integrate a split between different modes. We want to find out whether we want to have fully integrated as part of the next implementation steps.
Child of https://github.com/bpmn-io/internal-docs/issues/256

Technical preparation is done (cf. learnings above). Let's focus the test planning inside https://github.com/camunda/camunda-modeler-design/issues/20.
Once we have detailed learnings what we want to implement / improve, let's create another issues for that.


Crashing push on XCode 14 beta

Crashing push on NavigationController extension, XCode 14 beta 5, is complaining that the method must be made on main thread.

@hugovanderlei can you confirm that trigger is called from the main thread in this case?

I tested it in both xcodes, and it always worked on XCode 13, where the method was called on the main thread. However, when I use XCode 14, the method is not called on the main thread, as shown in the images.

@pauljohanneskraft  Same problem here, any news?

Same problem. Any news?

I was able to resolve it on my project. On XCode 14, I observed that even when an async trigger method is called by another method with @MainActor, the trigger method is no longer on the main thread.
I believe adding @MainActor to the async trigger might work.

In my project, I had to use MainActor.run to call the trigger.
            router.trigger(.checkAuthentication)
        }```

This forces the trigger method to be executed on the main thread.

In my case it only happened on async methods

Any news?

any news?

any news?

any news?

Sorry for the long wait. I will try to figure out the root cause to this - can anyone confirm or deny that this only affects the async extensions and not the regular trigger methods?

I pushed a potential fix to https://github.com/QuickBirdEng/XCoordinator/pull/239 - Can anyone confirm that this solves the issue?

Hi @pauljohanneskraft, I have tried your fix in all the afflicted sections in my app and everything is fixed. Thank you. My team is looking forward to the new version. well done!

Thank you very much for the feedback - I will try to release it in about a week, hope that's fine. Until then, feel free to specify that branch for now as a temporary workaround.

The fix has just been merged and will be released shortly.


Also when deploying a new Cockpit via the Deployer Chatbot all uppercases are ignored

Example: You have a cloud space ready, named "WhattIconsume", and in the conversation with the Deployer Chatbot you specify that you want the Cockpit be deployed there, you'll end up with a new cloud space, named "watticonsume" - see  screenshot

Is related to the same wrong behaviour when deploying via AYS: https://github.com/Jumpscale/jscockpit/issues/62

See https://github.com/Jumpscale/jscockpit/issues/62#issuecomment-233181454


Improve support of eslint-plugin-import

Hi there!
First of all, I would like to say thank you for your amazing work!
I came across to your project from this tweet, and while I was reading the docs, there was something that grab my attention, and is basically that you suggest to disable eslint-plugin-import... So at that moment I thought "it must be some other way to deal with this", and I guess there is one:

eslint-plugin-import resolvers

If you have some time, don't you mind to have a look to it? I was thinking that maybe we could provide a custom resolver, so it would be just a matter to include it from babel-root-import/eslint-plugin-import-resolver, what do you think?
Thanks!

@mgtitimoli any luck on this? I am trying to get eslint-plugin-import to work as well and I'm having issues.

Thanks for pointing me to the right direction @mgtitimoli , I've implemented a fairly compatible resolver as gist: https://gist.github.com/layerssss/68eb1db9a43a5cf3325fbe25d62bad12 @adrianmcli

Hi, I've tried the eslint plugin mentioned in the readme. However, my eslint still shows an error for imports.

@divyanshu013 I'm not sure if is your case, but I had problems with my eslint, and after config the rootPathPrefix and rootPathSuffix in my .eslintrc, it fixed for me:
{
  "extends": "airbnb",
  "rules": {},
  "settings": {
    "import/resolver": {
      "babel-plugin-root-import": {
        "rootPathPrefix": "~",
        "rootPathSuffix": "src"
      }
    }
  }
}


Page grammar mistake

I found a grammar mistake in this documentation Page.
In this command, I think there is an extra "g" at the end of this sentence.
echo "spark.authenticate true" >> $spark_defaults_confg
It should not exist.

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

ID: 5ff50d07-e0de-ebc3-7161-86abba8a84b5
Version Independent ID: e756df59-ceeb-abe2-c3f2-9c5089028cab
Content: Encrypt traffic between cluster worker nodes - Azure Databricks
Content Source: databricks/security/encrypt-otw.md
Service: azure-databricks
GitHub Login: @mamccrea
Microsoft Alias: mamccrea

@HarryUlysses Thanks for bringing this to our notice. We are investigating into the issue and will update as appropriate.

Thanks @HarryUlysses! I've updated the doc. The changes should be live tomorrow.
#please-close

OK, it is no problem. It is my pleasure to provide feedback to you.


Check boot corruption

PR Overview:

Add sync after changing boot count
Run fsck against writeable partitions during boot

Documentation:

No documentation changes are needed

Integration Tests:

 Force partition corruption and test recovery


updating to new tns

closes https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/8104

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@dstrome PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

@tiburd Can you help me getting this merged?

@tiburd Can you help me getting this merged?


Terraform module added

main.tf, variables.tf, outputs.tf added, README.md updated

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


Tuning recipe

Type of Change

Feature
No API

Description
detail description
JIRA ticket: ILITV-2606
How has this PR been tested?
Pre-CI
Dependency Change?
No

/Azurepipeline run Model-Test


Allow a few more commands for chat-commands.js

What is the issue, e.g. map voting, you would like to solve?
Currently only supports "command", and not "command2", "command3" for example.
How would you like us to solve this issue?
To make this work like this (example words "version" and "website". Project Reality servers also support those commands iirc)

Additional Info
It currently outright ignores command2 and command3 variables.

If not I can attempt to push one for you. All we ask is not to modify flags as they are tied to GitHub actions.

If not I can attempt to push one for you. All we ask is not to modify flags as they are tied to GitHub actions.

Please do thank you!

Haven’t forgotten still plan on doing this. Going to make a branch here for it.


CI: Extend config file check to devel files

Those files are easy to break when a change happens in Agora.
Although they are in devel (and hence, subject to laxer rules),
we can easily avoid any breakage by adding this check to the CI,
as the check is extremely cheap.

As discussed with @hewison-chris yesterday.

It is already helping:-
devel/config-fullnode.yaml(37:4): registry.validators.email: Key is not a valid member of this section. There are 3 valid keys: authoritative, primary, soa


Compiling a contract with import_remappings fails

py-solc Version: 2.1.0
solc Version: 0.4.17
Python Version: 3.5.2
OS: Ubuntu 16.04, 4.4.0-104-generic

What was wrong?
I tried to compile a contract, say like this one:
pragma solidity 0.4.17;

contract Blah {
    uint public a;

    function Blah(uint _a) public {
        a = _a;
    }

    function getA() public view returns(uint) {
        return a;
    }
}

The python compilation code is as follows:
class Chain:
    ...
    @classmethod
    def compileContract(cls, filename):
	with open(filename,'r') as f:
            contract_source_code = f.read()
        compiled_sol = compile_source(contract_source_code, import_remappings=['='])
        return compiled_sol ['<stdin>:Blah']
    ...

Executing this function returns an error:
Traceback (most recent call last):
  File "compile.py", line 71, in <module>
    compiled = Chain.compileContract(sys.argv[1])
  File "compile.py", line 24, in compileContract
    compiled_sol = compile_source(contract_source_code, import_remappings=["="])
  File "/usr/local/lib/python3.5/dist-packages/solc/main.py", line 106, in compile_source
    stdoutdata, stderrdata, command, proc = solc_wrapper(**compiler_kwargs)
  File "/usr/local/lib/python3.5/dist-packages/solc/utils/string.py", line 85, in inner
    return force_obj_to_text(fn(*args, **kwargs))
  File "/usr/local/lib/python3.5/dist-packages/solc/wrapper.py", line 165, in solc_wrapper
    stderr_data=stderrdata,
solc.exceptions.SolcError: An error occurred during execution
> command: `solc --combined-json abi,asm,ast,bin,bin-runtime,clone-bin,devdoc,interface,opcodes,userdoc =`
> return code: `1`
> stderr:

> stdout:

Notes:

It fails whatever value I assign to import_remapings.
Executing with import_remappings removed works fine (it's not needed in this example, but I have another case where I'm importing other contracts and I need to use it).
Executing solc --combined-json abi,asm,ast,bin,bin-runtime,clone-bin,devdoc,interface,opcodes,userdoc = blah.sol directly from the command line works fine too (no errors, no warnings).
I tried also running with solc 0.4.19 in docker but problem persisted.
All files I have in one directory and all commands were executed inside this directory.

Cute Animal Picture

Any advance on this?
I can't understand the workaround

My workaround is just a function which reads a json passed in a command line argument, which is a compiled contract. Compilation itself is done in memory with solc, not with py-solc. It just allows for having the contract data stored the same way as it would be using py-solc without affecting other parts of code, and does not require compiling it in advance and storing in a file.
Which part of it don't you understand exactly?

For anyone else facing this issue, a simple solution is to send an extra dash at the end of the command:
compiled_sol = compile_source(contract_source_code, import_remappings=['=/', '-'])
The problem seems to be related to the way the solc compiler cli behaves when sending the source code via stdin AND sending the remapping arguments. The following command does not work if you try to send the source code via stdin (it returns immediately without waiting for input):
 $ solc --combined-json abi,asm,ast,bin,bin-runtime,clone-bin,devdoc,interface,opcodes,userdoc =/
However the following does work:
 $ solc --combined-json abi,asm,ast,bin,bin-runtime,clone-bin,devdoc,interface,opcodes,userdoc =/ -
So the simplest solution is to send an extra dash at the end of the command, and the import_remappings arguments provides an easy way to do so :)

I'm also running into this issue.  The solutions proposed did not work for me.
`
contract_source_code = '''
pragma solidity ^0.4.13;
contract Escrow {
address public owner;
uint public fee;
//Balances temporarily made public for testing; to be removed
mapping (address =>  mapping (address => uint)) public balances;
function Escrow() public {
owner = msg.sender;
}
modifier onlyOwner() {
require(msg.sender == owner);
_;
}
//Fee should be set in PPM
function setFee(uint price) onlyOwner external {
fee = price;
}
function start(address payee) payable external {
balances[msg.sender][payee] = balances[msg.sender][payee] + msg.value;
}
function end(address payer, address payee) onlyOwner external returns(bool){
uint value = balances[payer][payee];
uint paidFee = value / (1000000 / fee);
uint payment = value - paidFee;
balances[payer][payee] = 0;
payee.transfer(payment);
owner.transfer(paidFee);
return true;
}
function refund(address payer, address payee) onlyOwner external returns(bool){
uint value = balances[payer][payee];
balances[payer][payee] = 0;
payer.transfer(value);
return true;
}
}
'''
provider = HTTPProvider('https://ropsten.infura.io/')
w3 = Web3(provider)
assert w3.isConnected()
abi = compile_source(contract_source_code, import_remappings=['=/', '-'])
`
I've tried first encoding the contract_source_code with json.dumps, but same issue.

import_remappings will fix this error
compiled_sol = compile_source(contract_source_code, import_remappings=['=./pathDirectory', '-'])
Compiled source code

How does the above change apply when I do compile_files(....)


Modified notebook sdk_automl_tabular_forecasting_batch.ipynb

Modified notebook sdk_automl_tabular_forecasting_batch.ipynb

[X] Use the notebook template as a starting point.
[X] Follow the style and grammar rules outlined in the above notebook template.
[X] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[X] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
[ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[X] This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
[X] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

Please describe changes in the PR summary.

This PR message is not acceptable. Please be more description on why and what was changed.

@sudarshan-SpringML can you attach (or paste) the regression test error so we can see what was fixed? Thanks.


[QUESTION]

Submit your question
Microsoft help source URLs and cookie consents for users in v5?
What is the context of your question

[ ] Installation
[ ] Learning Pathways Content
[x ] SharePoint Success Content
[ ] Administration
[ ] Custom Content
[ ] Viewer Web Part

What is your question
With the help content included from Microsoft, is there always a cookie consent window for each user when reading embedded content, like on Microsoft's websites?
Which Microsoft help source URLs are included?
Thanks for your help!

@marcoschmucker I am not sure what the question is here? The content for all the Learning Pathways content is included via an IFrame. We have no control over the content (cookie consent or other content) for the pages and just pull them into the webpart. Is there something more you are asking?

Closed due to inactivity. If this is still an issue please create a new issue and reference this one. In addition, please answer the question in the previous comment.

@marcoschmucker the webpart is embedded in SharePoint so it is not responsible for showing a cookie message just like the news webpart isn't required to put out a cookie menu. The pages that Learning Pathways pulls in via an Iframe are responsible for their own content and we have no control over those. I hope that answers your question.

@dcashpeterson Thanks a lot. This is true!


Update lunchy to 0.1.6

Thank you for the contribution. It was merged directly as 54945a22b8ed4fa4318c1e38d0bcf12ab8e96d15 to keep commit history cleaner. Your contribution is still credited to you.

Wow, that was fast! :rocket:


Python 3 Support

The Scikits.Talkbox module seems to only work on Python 2.7.
Is there a way that I can use this software on Python 3.3 and above?

Hi. The whole library has only been tested in Python 2.7
On Wed, 23 Mar 2016 at 19:21 Connor Byron<EMAIL_ADDRESS>wrote:

The Scikits.Talkbox module seems to only work on Python 2.7.
Is there a way that I can use this software on Python 3.3 and above?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/tyiannak/pyAudioAnalysis/issues/7

Perhaps this should be left open as a feature request? Also would be useful to note that Python 2.7 is supported on the README.md. Thanks!

Hope to provide python3 version, thanks

i could change the code to work with python3. However, i assume it is not backwards compatible to Python 2.7.  But this is not a crucial task, i think the author could do this as he do not accepts pull requests.


Fix Raven.captureException example in docs

Raven.captureException cannot be passed as a function reference; it needs to be bound to Raven (either via bind or by being wrapped in a function).

Thanks for the fix, I saw this while using it and I forgot to update the readme.


WIP Delayed exit

With old exit function, anybody could leave without any repercussions. E.x. a bad actor does something bad on the whitelist and decides to exit before being challenged and they are transferred back their original unstaked deposit. By increasing the time in which one is required to finalize an exit, we can mitigate this.

Split up exit function into two, initExit() and finalizeExit().

Add two parameters to Parameterizer: exitTimeDelay and exitTimeExpiry. exitTimeDelay represents the first time that the user is allowed to finalize their exit while exitTimeExpiry represents the latest time.

Add tests. Refactor a few tests to contain less state.

Will rebase against develop before final review.

See PR #72, it has commits that are squashed from this PR.


25 correct clippy

Description

Updating the code to follow the Clippy good practices. Used the command cargo clippy --all-targets --all-features

Fixes part of #25
Type of change

[X] Refactor

@Samyak2 @psiayn sorry, can't ask review directly. If/when possible, please review!

@Samyak2 done!

Looks like 6a75349ff403537ce122b27d88230d314144450b also fixed formatting (a part of #23), but that's ok


Sorry, someAction does not appear to be a valid operation on this API.

Actual Error
Error: Sorry, `getVouchersApi` does not appear to be a valid operation on this API.
    at Proxy.<anonymous> (/mnt/c/Users/Bruce/Documents/workspace/CoinPlanet/xoxoday_server/node_modules/api/dist/index.js:179:47)
    at step (/mnt/c/Users/Bruce/Documents/workspace/CoinPlanet/xoxoday_server/node_modules/api/dist/index.js:33:23)
    at Object.next (/mnt/c/Users/Bruce/Documents/workspace/CoinPlanet/xoxoday_server/node_modules/api/dist/index.js:14:53)
    at fulfilled (/mnt/c/Users/Bruce/Documents/workspace/CoinPlanet/xoxoday_server/node_modules/api/dist/index.js:5:58)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

I am referring the docs mentioned here https://helpcenter.xoxoday.com/reference/get-vouchers-api. Although it is working in the docs (on providing my access token) when i perform the same action in my localhost server it is not working.
The above error is being shown. The version is also exactly the same. Even the example is the same.
It is working in the docs but not in my localhost server.
const { pool} = require("../../server");
const sdk = require("api")("@xoxoday/v1.0#d550oavlgo466vx");

// =========== TEST =============

// Retrieve all from the database.
exports.testController = async (req, res) => {
  try {
    const query = {
      text: 'SELECT COUNT(*) FROM "Users"',
    };

    const users = await pool.query(query);
    console.log(users);

    sdk.auth(".........my_access_token..........");
    sdk
      .getVouchersApi({
        query: "plumProAPI.mutation.getVouchers",
        tag: "plumProAPI",
        variables: {
          data: {
            limit: 10,
            page: 1,
            exchangeRate: 1,
            sort: { field: "name", order: "ASC" },
          },
        },
      })
      .then(({ data }) => console.log(data))
      .catch((err) => console.error(err));

    return res.status(200).json({
      usersCount: users.rows,
      // vouchers: vouchers,
    });
  } catch (error) {
    console.log(error);
  }
};

Hi! It looks like the API Registry entry for that API has been a bit corrupted and doesn't have any documented endpoints.

This is unfortunately a known rare quirk in our registry system and something we're working towards resolving but we sadly don't have a workaround for you for this right now. 😞

Hi, Can you suggest a workaround bcz I have paid a lot of money to use this API. Sorry, but will downgrading or using some other version will it work?

It works on the docs because those docs aren't using the api library to make request in the browser, and thereby don't use this API Registry system. Unfortunately cannot be fixed from their site but we're slowly working on fixes it's just a tough problem to solve with how rare it happens.
You can still use their API, just not through the api library. On https://helpcenter.xoxoday.com/reference/get-vouchers-api you can click on this little arrow to see other code snippets for Node HTTP libraries:

Thank You @erunion . I thought using it via api library was the only way


Make CIS-2 token lookup more lenient

Purpose
Make CIS-2 token lookup more lenient
Changes

Redo getTokens so that metadataURL and balances are fetched individually.
Log errors from token lookup, don't show them in UI.
Don't fail "Choose Contract" unless all tokens are missing either metadata or balance.
fetchTokensConfigure now keeps looking until 1 valid token is found (/or all tokens in the contract have been checked)

Checklist

[x] My code follows the style of this project.
[x] The code compiles without warnings.
[x] I have performed a self-review of the changes.
[x] I have documented my code, in particular the intent of the
hard-to-understand areas.
[x] (If necessary) I have updated the CHANGELOG.

The balance shows incorrectly when adding a token (it shows as 0 even if I have tokens).

The balance shows incorrectly when adding a token (it shows as 0 even if I have tokens).

I'm unable to reproduce this? :thinking:


Tests and modification to test environment

Is your feature request related to a problem? Please describe.

[x]  1. Update regex for config verb hadler
[ ]  2. Add functional tests for dynamic server config change
[x]  3. Add environment variable "testingMode" in the docker container that contains the secondary server used in functional tests.
[x]  4. Add environment variable "testingMode" and set it to true in the GitHub workflow environment.
[x]  5. Fix issue - functional tests part of git workflow in set-verb branch cannot connect to the secondary server
[x]  6. Fix Bug - _getBoolEnvVar method in AtSecondaryConfig does not return env variables.

Describe the solution you'd like
3&4 - Dynamic server config is a new feature that allows for modifications to certain server configurations without having to restart the secondary server. This feature can be used through the config verb handler which now accepts new commands. The server needs to have a config parameter "testingMode" to be set to true for this feature to work which can be either set in the server config.yaml. Since setting it to true on production secondaries can open up vulnerabilities set the parameter to false by default and instead pass it as an environment variable for functional_tests to verify this feature as part of git actions.
5 - Functional tests for dynamic server config change cannot reach secondary. The tests retry connecting for 5 mins and then terminate causing tests to fail. Investigate and resolve issue.
6 -  _getBoolEnvVar method in AtSecondaryConfig does not return env variables even when env variables are present. Investigate and resolve this bug.

Resolved (1) as part of https://github.com/atsign-foundation/at_tools/pull/191
Resolved (3, 4, 5, 6) as part of https://github.com/atsign-foundation/at_server/pull/724

Task 5
This issue was being caused by a getter in AtSecondaryConfig which was trying to access a parameter from environment variables which was throwing an exception causing secondary to shutdown. Hence secondary unreachable messages are repetitively logged. This was solved my using try-catch block to use an alternative method to fetch config when env var is not present. Also added a log to which describes the cause for secondary being unreachable.

Task 6
This bug was being caused due to a missing return statement in _getBoolEnvVar in the if-clause when an env variable is present.