Hc 279 Remove deprecated HySDS code

https://hysds-core.atlassian.net/browse/HC-279

@mcayanan  havent tested it yet, whats the best way to test it?

On the nisar ci machine, you'll probably need to deploy the container builder update on there and run those commands I linked you to in order to build the PCM container using your changes. When deploying the container builder update on nisar ci, be sure to back up the existing copy that's on there in case there's a bug so you can revert back to it. I don't know if there's an easier way. @pymonger ?

@mcayanan @pymonger was able to test by cloning container-builder in to our CI instance (but changed the name to container-builder-HC-279)
i used branch HC-279 to build
$ pwd
/export/home/###/verdi/ops/container-builder-HC-279
(verdi) [###@nisar-pcm-ci container-builder-HC-279]$ git branch
* HC-279
  master

i also updated the jenkins build script to point to the new container-builder directory
# build image
if [ ! -z "$CONTAINER_REGISTRY" -a ! -z "$CONTAINER_REGISTRY_BUCKET" ]
then
  /export/home/hysdsops/verdi/ops/container-builder-HC-279/build-container.bash \
  ${REPO} ${TAG} ${STORAGE} ${MOZART_REST_URL} ${GRQ_REST_URL} ${SKIP_PUBLISH} ${CONTAINER_REGISTRY} --build-arg GIT_OAUTH_TOKEN=${GIT_OAUTH_TOKEN} --build-arg BRANCH=${TAG} --build-arg PCM_COMMONS_BRANCH=${PCM_COMMONS_BRANCH}
else
  /export/home/hysdsops/verdi/ops/container-builder-HC-279/build-container.bash \
  ${REPO} ${TAG} ${STORAGE} ${MOZART_REST_URL} ${GRQ_REST_URL} ${SKIP_PUBLISH} "" --build-arg GIT_OAUTH_TOKEN=${GIT_OAUTH_TOKEN} --build-arg BRANCH=${TAG} --build-arg PCM_COMMONS_BRANCH=${PCM_COMMONS_BRANCH}
fi

output: https://nisar-pcm-ci.jpl.nasa.gov/job/nisar-dustinlo-3_container-builder_hysds_lightweight-jobs_develop/1/console

Started by user Dustin K Lo
Running as SYSTEM
Building in workspace /var/lib/jenkins/workspace/nisar-dustinlo-3_container-builder_hysds_lightweight-jobs_develop
[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Deferred wipeout is used...
No credentials specified
Cloning the remote Git repository
Cloning repository<EMAIL_ADDRESS> > git init /var/lib/jenkins/workspace/nisar-dustinlo-3_container-builder_hysds_lightweight-jobs_develop # timeout=10
Fetching upstream changes from<EMAIL_ADDRESS> > git --version # timeout=10
 > git --version # 'git version <IP_ADDRESS>'
 > git fetch --tags --progress<EMAIL_ADDRESS>+refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url<EMAIL_ADDRESS># timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url<EMAIL_ADDRESS># timeout=10
Fetching upstream changes from<EMAIL_ADDRESS> > git fetch --tags --progress<EMAIL_ADDRESS>+refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision ac556d7f1bee59b35e46505aea148056b080882a (refs/remotes/origin/develop)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f ac556d7f1bee59b35e46505aea148056b080882a # timeout=10
Commit message: "add purge.sh wrapper and disable python bytecode writing (#22)"
First time build. Skipping changelog.
[nisar-dustinlo-3_container-builder_hysds_lightweight-jobs_develop] $ /bin/bash /tmp/jenkins6187129903951178771.sh
+ '[' '!' -z localhost:5050 -a '!' -z nisar-pcm-registry-bucket ']'
+ /export/home/######/verdi/ops/container-builder-HC-279/build-container.bash hysds_lightweight-jobs develop s3://s3-us-west-2.amazonaws.com/nisar-dev-cc-fwd-dustinlo/ http://###.##.###.###:8888/api/v0.1 http://###.##.###.###:8878/api/v0.1 noskip localhost:5050 --build-arg GIT_OAUTH_TOKEN=######## --build-arg BRANCH=develop --build-arg PCM_COMMONS_BRANCH=develop
[CI] Is checkout a tag: 1 v1.0.5
[CI] Last log: commit ac556d7f1bee59b35e46505aea148056b080882a
Author: Gerald Manipon<EMAIL_ADDRESS>Date:   Tue Oct 6 08:34:49 2020 -0700

    add purge.sh wrapper and disable python bytecode writing (#22)
[CI] Skip image build flag: 0
Validating job-spec for lightweight-echo
Validating hysds-io for lightweight-echo
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-mozart-notify-by-email
Validating hysds-io for lw-mozart-notify-by-email
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-mozart-purge
Validating hysds-io for lw-mozart-purge
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-mozart-reprioritize
Validating hysds-io for lw-mozart-reprioritize
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-mozart-retry
Validating hysds-io for lw-mozart-retry
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-mozart-revoke
Validating hysds-io for lw-mozart-revoke
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-tosca-aws_get
Validating hysds-io for lw-tosca-aws_get
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-tosca-notify-by-email
Validating hysds-io for lw-tosca-notify-by-email
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-tosca-purge
Validating hysds-io for lw-tosca-purge
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-tosca-wget
Validating hysds-io for lw-tosca-wget
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-tosca-wget-email
Validating hysds-io for lw-tosca-wget-email
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-tosca-wget-glob
Validating hysds-io for lw-tosca-wget-glob
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-tosca-wget-product
Validating hysds-io for lw-tosca-wget-product
Checking that the job-spec and hysds-io define the same parameters
All hysds-io and job-specs are valid
[CI] Build for: container-hysds_lightweight-jobs:develop and file hysds_lightweight-jobs
 docker build --rm --force-rm -f docker/Dockerfile -t container-hysds_lightweight-jobs:develop --build-arg GIT_OAUTH_TOKEN=######## --build-arg BRANCH=develop --build-arg PCM_COMMONS_BRANCH=develop .
Sending build context to Docker daemon  392.7kB

Step 1/8 : FROM hysds/pge-base:develop
 ---> bb23b2fe4a88
Step 2/8 : MAINTAINER malarout<EMAIL_ADDRESS> ---> Using cache
 ---> b7ee939ccccb
Step 3/8 : LABEL description="Lightweight System Jobs"
 ---> Using cache
 ---> fc35bcf73cb1
Step 4/8 : USER ops
 ---> Using cache
 ---> 94642a731e02
Step 5/8 : COPY . /home/ops/lightweight-jobs
 ---> e216987d015b
Step 6/8 : ENTRYPOINT ["/entrypoint-pge-with-stats.sh"]
 ---> Running in d5407deaccd9
Removing intermediate container d5407deaccd9
 ---> 75bbced4c1f8
Step 7/8 : WORKDIR /home/ops
 ---> Running in d12870e5aba7
Removing intermediate container d12870e5aba7
 ---> 2020d6a017eb
Step 8/8 : CMD ["/bin/bash", "--login"]
 ---> Running in 9a4ce87f261b
Removing intermediate container 9a4ce87f261b
 ---> 06b35a3fd47d
[Warning] One or more build-args [PCM_COMMONS_BRANCH BRANCH GIT_OAUTH_TOKEN] were not consumed
Successfully built 06b35a3fd47d
Successfully tagged container-hysds_lightweight-jobs:develop
[CI] Pushing docker container container-hysds_lightweight-jobs:develop to localhost:5050
The push refers to repository [localhost:5050/container-hysds_lightweight-jobs]
2c02a5bf78aa: Preparing
8018683c3d46: Preparing
542bfce5c667: Preparing
3f4ca92e2a04: Preparing
fd262f1ffcae: Preparing
0527db030176: Preparing
3388fe6b1854: Preparing
bad99a3c3d04: Preparing
613be09ab3c0: Preparing
bad99a3c3d04: Waiting
0527db030176: Waiting
613be09ab3c0: Waiting
3388fe6b1854: Waiting
3f4ca92e2a04: Layer already exists
8018683c3d46: Layer already exists
542bfce5c667: Layer already exists
fd262f1ffcae: Layer already exists
0527db030176: Layer already exists
bad99a3c3d04: Layer already exists
613be09ab3c0: Layer already exists
3388fe6b1854: Layer already exists
2c02a5bf78aa: Pushed
develop: digest: sha256:9e0c51ebeed46b81b64d93e241cd52abe5444ac0c092abc4d1f2e3c8ba513fff size: 2206
[CI] Build for: job-lightweight-echo:develop and file lightweight-echo
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lightweight-echo develop job-lightweight-echo:develop
[CI] Build for: job-lw-mozart-notify-by-email:develop and file lw-mozart-notify-by-email
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-mozart-notify-by-email develop job-lw-mozart-notify-by-email:develop
[CI] Build for: job-lw-mozart-purge:develop and file lw-mozart-purge
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-mozart-purge develop job-lw-mozart-purge:develop
[CI] Build for: job-lw-mozart-reprioritize:develop and file lw-mozart-reprioritize
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-mozart-reprioritize develop job-lw-mozart-reprioritize:develop
[CI] Build for: job-lw-mozart-retry:develop and file lw-mozart-retry
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-mozart-retry develop job-lw-mozart-retry:develop
[CI] Build for: job-lw-mozart-revoke:develop and file lw-mozart-revoke
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-mozart-revoke develop job-lw-mozart-revoke:develop
[CI] Build for: job-lw-tosca-aws_get:develop and file lw-tosca-aws_get
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-tosca-aws_get develop job-lw-tosca-aws_get:develop
[CI] Build for: job-lw-tosca-notify-by-email:develop and file lw-tosca-notify-by-email
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-tosca-notify-by-email develop job-lw-tosca-notify-by-email:develop
[CI] Build for: job-lw-tosca-purge:develop and file lw-tosca-purge
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-tosca-purge develop job-lw-tosca-purge:develop
[CI] Build for: job-lw-tosca-wget:develop and file lw-tosca-wget
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-tosca-wget develop job-lw-tosca-wget:develop
[CI] Build for: job-lw-tosca-wget-email:develop and file lw-tosca-wget-email
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-tosca-wget-email develop job-lw-tosca-wget-email:develop
[CI] Build for: job-lw-tosca-wget-glob:develop and file lw-tosca-wget-glob
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-tosca-wget-glob develop job-lw-tosca-wget-glob:develop
[CI] Build for: job-lw-tosca-wget-product:develop and file lw-tosca-wget-product
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-tosca-wget-product develop job-lw-tosca-wget-product:develop
[CI] Build for: hysds-io-lightweight-echo:develop and file lightweight-echo
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lightweight-echo develop hysds-io-lightweight-echo:develop
404 Client Error: NOT FOUND for url: http://###.##.###.###:8878/api/v0.1/hysds_io/type
[CI] Build for: hysds-io-lw-mozart-notify-by-email:develop and file lw-mozart-notify-by-email
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-mozart-notify-by-email develop hysds-io-lw-mozart-notify-by-email:develop
404 Client Error: NOT FOUND for url: http://###.##.###.###:8888/api/v0.1/hysds_io/type
[CI] Build for: hysds-io-lw-mozart-purge:develop and file lw-mozart-purge
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-mozart-purge develop hysds-io-lw-mozart-purge:develop
404 Client Error: NOT FOUND for url: http://###.##.###.###:8888/api/v0.1/hysds_io/type
[CI] Build for: hysds-io-lw-mozart-reprioritize:develop and file lw-mozart-reprioritize
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-mozart-reprioritize develop hysds-io-lw-mozart-reprioritize:develop
404 Client Error: NOT FOUND for url: http://###.##.###.###:8888/api/v0.1/hysds_io/type
[CI] Build for: hysds-io-lw-mozart-retry:develop and file lw-mozart-retry
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-mozart-retry develop hysds-io-lw-mozart-retry:develop
404 Client Error: NOT FOUND for url: http://###.##.###.###:8888/api/v0.1/hysds_io/type
[CI] Build for: hysds-io-lw-mozart-revoke:develop and file lw-mozart-revoke
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-mozart-revoke develop hysds-io-lw-mozart-revoke:develop
404 Client Error: NOT FOUND for url: http://###.##.###.###:8888/api/v0.1/hysds_io/type
[CI] Build for: hysds-io-lw-tosca-aws_get:develop and file lw-tosca-aws_get
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-tosca-aws_get develop hysds-io-lw-tosca-aws_get:develop
404 Client Error: NOT FOUND for url: http://###.##.###.###:8878/api/v0.1/hysds_io/type
[CI] Build for: hysds-io-lw-tosca-notify-by-email:develop and file lw-tosca-notify-by-email
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-tosca-notify-by-email develop hysds-io-lw-tosca-notify-by-email:develop
404 Client Error: NOT FOUND for url: http://###.##.###.###:8878/api/v0.1/hysds_io/type
[CI] Build for: hysds-io-lw-tosca-purge:develop and file lw-tosca-purge
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-tosca-purge develop hysds-io-lw-tosca-purge:develop
404 Client Error: NOT FOUND for url: http://###.##.###.###:8878/api/v0.1/hysds_io/type
[CI] Build for: hysds-io-lw-tosca-wget:develop and file lw-tosca-wget
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-tosca-wget develop hysds-io-lw-tosca-wget:develop
404 Client Error: NOT FOUND for url: http://###.##.###.###:8878/api/v0.1/hysds_io/type
[CI] Build for: hysds-io-lw-tosca-wget-email:develop and file lw-tosca-wget-email
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-tosca-wget-email develop hysds-io-lw-tosca-wget-email:develop
404 Client Error: NOT FOUND for url: http://###.##.###.###:8878/api/v0.1/hysds_io/type
[CI] Build for: hysds-io-lw-tosca-wget-glob:develop and file lw-tosca-wget-glob
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-tosca-wget-glob develop hysds-io-lw-tosca-wget-glob:develop
404 Client Error: NOT FOUND for url: http://###.##.###.###:8878/api/v0.1/hysds_io/type
[CI] Build for: hysds-io-lw-tosca-wget-product:develop and file lw-tosca-wget-product
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-tosca-wget-product develop hysds-io-lw-tosca-wget-product:develop
404 Client Error: NOT FOUND for url: http://###.##.###.###:8878/api/v0.1/hysds_io/type
+ '[' -f ./docker/extract_artifacts.sh ']'
Recording test results
None of the test reports contained any result
Finished: SUCCESS

@DustinKLo I might be missing something, but do you know why you were getting those 404 errors when building a job?

@DustinKLo I might be missing something, but do you know why you were getting those 404 errors when building a job?

it's because in io-met.py (add_hysds_io function) it calls the GRQ/Mozart rest API and checks if the hysds-io (with version) document exists
and its returning a 404 because we don't have lightweight-jobs:develop PGEs built into our clusters

@mcayanan  i re-ran the jenkins job and it's not printing a 404 error because the container was already built earlier
Started by user Dustin K Lo
Running as SYSTEM
Building in workspace /var/lib/jenkins/workspace/nisar-######-3_container-builder_hysds_lightweight-jobs_develop
[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Deferred wipeout is used...
[WS-CLEANUP] Done
No credentials specified
Cloning the remote Git repository
Cloning repository<EMAIL_ADDRESS> > git init /var/lib/jenkins/workspace/nisar-######-3_container-builder_hysds_lightweight-jobs_develop # timeout=10
Fetching upstream changes from<EMAIL_ADDRESS> > git --version # timeout=10
 > git --version # 'git version <IP_ADDRESS>'
 > git fetch --tags --progress<EMAIL_ADDRESS>+refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url<EMAIL_ADDRESS># timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url<EMAIL_ADDRESS># timeout=10
Fetching upstream changes from<EMAIL_ADDRESS> > git fetch --tags --progress<EMAIL_ADDRESS>+refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision ac556d7f1bee59b35e46505aea148056b080882a (refs/remotes/origin/develop)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f ac556d7f1bee59b35e46505aea148056b080882a # timeout=10
Commit message: "add purge.sh wrapper and disable python bytecode writing (#22)"
 > git rev-list --no-walk ac556d7f1bee59b35e46505aea148056b080882a # timeout=10
[nisar-######-3_container-builder_hysds_lightweight-jobs_develop] $ /bin/bash /tmp/jenkins1153634780853696808.sh
+ '[' '!' -z localhost:5050 -a '!' -z nisar-pcm-registry-bucket ']'
+ /export/home/#######/verdi/ops/container-builder-HC-279/build-container.bash hysds_lightweight-jobs develop s3://s3-us-west-2.amazonaws.com/nisar-dev-cc-fwd-######/ http://###.##.###.###:8888/api/v0.1 http://###.##.###.###:8878/api/v0.1 noskip localhost:5050 --build-arg GIT_OAUTH_TOKEN=########### --build-arg BRANCH=develop --build-arg PCM_COMMONS_BRANCH=develop
[CI] Is checkout a tag: 1 v1.0.5
[CI] Last log: commit ac556d7f1bee59b35e46505aea148056b080882a
Author: Gerald Manipon<EMAIL_ADDRESS>Date:   Tue Oct 6 08:34:49 2020 -0700

    add purge.sh wrapper and disable python bytecode writing (#22)
[CI] Skip image build flag: 0
Validating job-spec for lightweight-echo
Validating hysds-io for lightweight-echo
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-mozart-notify-by-email
Validating hysds-io for lw-mozart-notify-by-email
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-mozart-purge
Validating hysds-io for lw-mozart-purge
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-mozart-reprioritize
Validating hysds-io for lw-mozart-reprioritize
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-mozart-retry
Validating hysds-io for lw-mozart-retry
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-mozart-revoke
Validating hysds-io for lw-mozart-revoke
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-tosca-aws_get
Validating hysds-io for lw-tosca-aws_get
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-tosca-notify-by-email
Validating hysds-io for lw-tosca-notify-by-email
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-tosca-purge
Validating hysds-io for lw-tosca-purge
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-tosca-wget
Validating hysds-io for lw-tosca-wget
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-tosca-wget-email
Validating hysds-io for lw-tosca-wget-email
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-tosca-wget-glob
Validating hysds-io for lw-tosca-wget-glob
Checking that the job-spec and hysds-io define the same parameters
Validating job-spec for lw-tosca-wget-product
Validating hysds-io for lw-tosca-wget-product
Checking that the job-spec and hysds-io define the same parameters
All hysds-io and job-specs are valid
[CI] Removing current image for container-hysds_lightweight-jobs:develop: 06b35a3fd47d
Total reclaimed space: 0B
Untagged: container-hysds_lightweight-jobs:develop
Untagged: localhost:5050/container-hysds_lightweight-jobs:develop
Untagged: localhost:5050/container-hysds_lightweight-jobs@sha256:9e0c51ebeed46b81b64d93e241cd52abe5444ac0c092abc4d1f2e3c8ba513fff
Deleted: sha256:06b35a3fd47de44aa85ce850841a77d771666d94ba3799019156203b90c765e7
Deleted: sha256:2020d6a017eb0dbaba4f20e0942cc3f9c69e5b55d2732045decdb5640d0e6a79
Deleted: sha256:75bbced4c1f8416c59b5f7a63c3df43ad38d627de3d18ae62a901e1993cf56de
Deleted: sha256:e216987d015bf00f5b46defffcec6b13da7ca7324221bd01724b7d001d7d0e0f
Deleted: sha256:09f7379072e782f187cdaf63856f30e0d3af5143db9fe96aabb0e172f662721b
[CI] Build for: container-hysds_lightweight-jobs:develop and file hysds_lightweight-jobs
 docker build --rm --force-rm -f docker/Dockerfile -t container-hysds_lightweight-jobs:develop --build-arg GIT_OAUTH_TOKEN=########### --build-arg BRANCH=develop --build-arg PCM_COMMONS_BRANCH=develop .
Sending build context to Docker daemon  392.7kB

Step 1/8 : FROM hysds/pge-base:develop
 ---> bb23b2fe4a88
Step 2/8 : MAINTAINER malarout<EMAIL_ADDRESS> ---> Using cache
 ---> b7ee939ccccb
Step 3/8 : LABEL description="Lightweight System Jobs"
 ---> Using cache
 ---> fc35bcf73cb1
Step 4/8 : USER ops
 ---> Using cache
 ---> 94642a731e02
Step 5/8 : COPY . /home/ops/lightweight-jobs
 ---> f0834c8bed85
Step 6/8 : ENTRYPOINT ["/entrypoint-pge-with-stats.sh"]
 ---> Running in 64740b746542
Removing intermediate container 64740b746542
 ---> 52cf8157504c
Step 7/8 : WORKDIR /home/ops
 ---> Running in 7014c9e3341a
Removing intermediate container 7014c9e3341a
 ---> 21b3700453b8
Step 8/8 : CMD ["/bin/bash", "--login"]
 ---> Running in 5d37d5ccef47
Removing intermediate container 5d37d5ccef47
 ---> 25d52297cd53
[Warning] One or more build-args [BRANCH GIT_OAUTH_TOKEN PCM_COMMONS_BRANCH] were not consumed
Successfully built 25d52297cd53
Successfully tagged container-hysds_lightweight-jobs:develop
[CI] Pushing docker container container-hysds_lightweight-jobs:develop to localhost:5050
The push refers to repository [localhost:5050/container-hysds_lightweight-jobs]
d73110d0ca50: Preparing
8018683c3d46: Preparing
542bfce5c667: Preparing
3f4ca92e2a04: Preparing
fd262f1ffcae: Preparing
0527db030176: Preparing
3388fe6b1854: Preparing
bad99a3c3d04: Preparing
613be09ab3c0: Preparing
0527db030176: Waiting
3388fe6b1854: Waiting
bad99a3c3d04: Waiting
613be09ab3c0: Waiting
542bfce5c667: Layer already exists
fd262f1ffcae: Layer already exists
3f4ca92e2a04: Layer already exists
8018683c3d46: Layer already exists
3388fe6b1854: Layer already exists
bad99a3c3d04: Layer already exists
0527db030176: Layer already exists
613be09ab3c0: Layer already exists
d73110d0ca50: Pushed
develop: digest: sha256:d6856449b8458c03509c9167c99fb87021591ab2e459142082772ac0dc73e6b2 size: 2206
[CI] Build for: job-lightweight-echo:develop and file lightweight-echo
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lightweight-echo develop job-lightweight-echo:develop
[CI] Build for: job-lw-mozart-notify-by-email:develop and file lw-mozart-notify-by-email
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-mozart-notify-by-email develop job-lw-mozart-notify-by-email:develop
[CI] Build for: job-lw-mozart-purge:develop and file lw-mozart-purge
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-mozart-purge develop job-lw-mozart-purge:develop
[CI] Build for: job-lw-mozart-reprioritize:develop and file lw-mozart-reprioritize
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-mozart-reprioritize develop job-lw-mozart-reprioritize:develop
[CI] Build for: job-lw-mozart-retry:develop and file lw-mozart-retry
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-mozart-retry develop job-lw-mozart-retry:develop
[CI] Build for: job-lw-mozart-revoke:develop and file lw-mozart-revoke
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-mozart-revoke develop job-lw-mozart-revoke:develop
[CI] Build for: job-lw-tosca-aws_get:develop and file lw-tosca-aws_get
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-tosca-aws_get develop job-lw-tosca-aws_get:develop
[CI] Build for: job-lw-tosca-notify-by-email:develop and file lw-tosca-notify-by-email
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-tosca-notify-by-email develop job-lw-tosca-notify-by-email:develop
[CI] Build for: job-lw-tosca-purge:develop and file lw-tosca-purge
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-tosca-purge develop job-lw-tosca-purge:develop
[CI] Build for: job-lw-tosca-wget:develop and file lw-tosca-wget
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-tosca-wget develop job-lw-tosca-wget:develop
[CI] Build for: job-lw-tosca-wget-email:develop and file lw-tosca-wget-email
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-tosca-wget-email develop job-lw-tosca-wget-email:develop
[CI] Build for: job-lw-tosca-wget-glob:develop and file lw-tosca-wget-glob
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-tosca-wget-glob develop job-lw-tosca-wget-glob:develop
[CI] Build for: job-lw-tosca-wget-product:develop and file lw-tosca-wget-product
Running Job-Met on: container-hysds_lightweight-jobs:develop docker/job-spec.json.lw-tosca-wget-product develop job-lw-tosca-wget-product:develop
[CI] Build for: hysds-io-lightweight-echo:develop and file lightweight-echo
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lightweight-echo develop hysds-io-lightweight-echo:develop
[CI] Build for: hysds-io-lw-mozart-notify-by-email:develop and file lw-mozart-notify-by-email
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-mozart-notify-by-email develop hysds-io-lw-mozart-notify-by-email:develop
[CI] Build for: hysds-io-lw-mozart-purge:develop and file lw-mozart-purge
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-mozart-purge develop hysds-io-lw-mozart-purge:develop
[CI] Build for: hysds-io-lw-mozart-reprioritize:develop and file lw-mozart-reprioritize
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-mozart-reprioritize develop hysds-io-lw-mozart-reprioritize:develop
[CI] Build for: hysds-io-lw-mozart-retry:develop and file lw-mozart-retry
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-mozart-retry develop hysds-io-lw-mozart-retry:develop
[CI] Build for: hysds-io-lw-mozart-revoke:develop and file lw-mozart-revoke
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-mozart-revoke develop hysds-io-lw-mozart-revoke:develop
[CI] Build for: hysds-io-lw-tosca-aws_get:develop and file lw-tosca-aws_get
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-tosca-aws_get develop hysds-io-lw-tosca-aws_get:develop
[CI] Build for: hysds-io-lw-tosca-notify-by-email:develop and file lw-tosca-notify-by-email
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-tosca-notify-by-email develop hysds-io-lw-tosca-notify-by-email:develop
[CI] Build for: hysds-io-lw-tosca-purge:develop and file lw-tosca-purge
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-tosca-purge develop hysds-io-lw-tosca-purge:develop
[CI] Build for: hysds-io-lw-tosca-wget:develop and file lw-tosca-wget
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-tosca-wget develop hysds-io-lw-tosca-wget:develop
[CI] Build for: hysds-io-lw-tosca-wget-email:develop and file lw-tosca-wget-email
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-tosca-wget-email develop hysds-io-lw-tosca-wget-email:develop
[CI] Build for: hysds-io-lw-tosca-wget-glob:develop and file lw-tosca-wget-glob
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-tosca-wget-glob develop hysds-io-lw-tosca-wget-glob:develop
[CI] Build for: hysds-io-lw-tosca-wget-product:develop and file lw-tosca-wget-product
Running IO-Met on: container-hysds_lightweight-jobs:develop docker/hysds-io.json.lw-tosca-wget-product develop hysds-io-lw-tosca-wget-product:develop
+ '[' -f ./docker/extract_artifacts.sh ']'
Recording test results
None of the test reports contained any result
Finished: SUCCESS


Connect more than 2 peers

Our API allows to configure only 1 remote peer, but we want to connect more meshes. However, we must know the identity of the configured peers to determine where an instance of an exported service come from, so we must also extend the Remote struct with the identity that will include trust domain, namespace, and service account. These 3 information are needed to verify SPIFFE ID.
The API should look as follows:
federation:
  meshPeers:
    local:
      ...
    remote:
    - identity:
        trustDomain: cluster.local
        namespace: istio-system
        serviceAccount: federation-controller-west
      addresses:
      - <IP_ADDRESS>
    - identity:
        trustDomain: cluster.local
        namespace: istio-system
        serviceAccount: federation-controller-east
    - addresses:
      - <IP_ADDRESS>

Alternatively, the identity could be a single field containing the SPIFFE ID.
federation:
  meshPeers:
    local:
      ...
    remote:
    - identity: cluster.local/ns/istio-system/sa/federation-controller-east
      addresses:
      - <IP_ADDRESS>
    - identity: cluster.local/ns/istio-system/sa/federation-controller-west
      addresses:
      - <IP_ADDRESS>

The second option is more compact, but an average Istio user does not have to know the SPIFFE ID format, and additionally, the first option allows us to assume default values, e.g. the configuration below could result in the following SPIFFE ID: cluster.local/ns/istio-system/sa/federation-controller-east.
federation:
  meshPeers:
    remote:
    - identity:
        serviceAccount: federation-controller-east

Note that the identities must be unique, so when we connect meshes using the same trust domain, then federation controllers must have unique service account or namespace.
Server can determine the identity from the XFCC header set by the ingress gateway.
Related issues:

Identify source peer (see https://github.com/openshift-service-mesh/federation/issues/62)

Allowing more than 2 peers will require to ensure uniqueness of ServiceEntry and WorkloadEntry names to avoid overwriting imported services, which are exported from more than 1 clusters.


showArea with multiple Line Charts breaking behavior of Tooltip Plugin

Hi
I am working with Line Charts to show to lines with the parameter 'showArea' set to True, and I am using the Tooltip Plugin with it. When my mouse is hovering the highest line everything is working fine but if my mouse hover the line under this one, the tooltip is showed only with the points located on each side of the bar. When I disable 'showArea' everything is fine with the both lines. It seems that the .ct-area of the top Line is covering the other bar and then there is no way the tooltip may work correctly. Here is a screenshot to show you what I'm experiencing:

By the way, thank you for this awesome Chart library, even if it is still in beta it is really powerfull and easy to use! :D

Hi there. For IE11+ and all other browsers you can use this style to fix the issue. Maybe it would be nice to have a fix for this in one of the tooltip plugins.
.ct-area {
  pointer-events: none;
}

This work pretty well, thanks a lot! =)


Add variable to .env file that allows toggle of experiment type

Add variable to .env file that allows us to toggle on/off experiment type. Currently needed for within-subjects experiments

FYI: https://carnegielearning.slack.com/archives/C055CGCRP6Z/p1712780394950259

FYI: https://carnegielearning.slack.com/archives/C055CGCRP6Z/p1712780394950259

@danoswaltCL We cant see this in our PlaypowerLabs workspace, its CL workspace slack link. If this is something we need to know for resolving this ticket, do let us know the details. Thanks.

QA: Dan, passed


Request: Build into a standard docker image stack

I use Portainer on a headless system, and I've had to run all the commands in the .sh manually.
Any chance you can have it auto assemble into a proper container?
It'd help tremendously with updates!

scratch that, it fails with file not found in nginx

Hey, may be I will push all containers in only one image in the future.


will it work on fedora 39?

there is so many things missing on fedora...

It worked great for me on F40. I just had to dnf install python3.10


Add Spark catalog HMS to Fabric notebooks

Adding import/export notebooks to enable an existing hms spark catalog on Fabric Lakehouse.

Could we also consider a README like Dbx2Synapse, including brief introduction and limitations?

@konjac I will add it shortly, in the meanwhile this blog is referencing to the notebooks: https://medium.com/@murggu/migrating-spark-catalog-to-fabric-lakehouse-cc8c14f0f0e1


Error: Request failed with status code 401

Hello
I've got this error message when I want to ask what is Doc about.
"Error: Request failed with status code 401"
What did I do wrong? Please help

API problem solved


TextRenderer Widget throws "Unexpected null value." at using inside a Row or Column

I'm trying to use TextRenderer inside to any Rows and Columns and always throws me error. But, the showed error don't say me what the problem, because, it's throwed a default error.
Any observations:

Flutter version: 2.10
Seo_Renderer lib version: 0.0.5

Example code:
Row(
  mainAxisAlignment: MainAxisAlignment.start,
  children: [
  InkWell(
    onTap: () {
      goToHomePage();
    },
    child: Container(
      width: 500,
      height: 200,
      child: TextRenderer(
        text: "Choose more products",
        style: SeoUtils.getTextRendererStyleByFontSize(14),
        child: Text(
          "Choose more products",
          style: TextStyle(
            fontSize: 14,
            color: const Color(0xFF3B3B3B),
            decoration: TextDecoration.underline,
            decorationColor: const Color(0xFF3B3B3B),
            fontWeight: FontWeight.bold,
          ),
        ),
      ),
    ),
  ),
  Container(child: Icon(Icons.add),),
  ],
  );

Follow below stack errors:
════════ Exception caught by widgets library ═══════════════════════════════════
The following TypeErrorImpl was thrown building TextRenderer(dirty, dependencies: [_ModalScopeStatus], state: _TextRendererState#a019f):
Unexpected null value.

Have you added RobotDetector Widget like this? There are some changes in usage for v0.5.0
runApp(
  RobotDetector(
    debug: true, // you can set true to enable robot mode
    child: MaterialApp(
      home: MyApp(),
      navigatorObservers: [seoRouteObserver],
    ),
  ),
);

caused by :
context.findAncestorStateOfType<_RobotDetectorState>()!._detected;

@iamSahdeep This was the cause. My problem was that RobotDetector it was added in ModularApp and not in MaterialApp, because i used Flutter Modular. Thanks for your help.


Feature/py37

Description

Test addition of Python 3.7
Motivation and Context

Python 3.7 came out and let's see if this code is compatible
Have you tested this? If so, how?

Travis will do it

Codecov Report

Merging #2 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #2   +/-   ##
=======================================
  Coverage   96.94%   96.94%
=======================================
  Files           8        8
  Lines         426      426
=======================================
  Hits          413      413
  Misses         13       13

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 6945b5a...a04d2b9. Read the comment docs.


Add read_write permissions to the boostrap instance

Previously, the boostrap instance did not need to upload to gcs. Now it needs it for the sbom upload.

/cc bkatyl
/cc zmarano


Interface for on-prem and pre-signed urls

We need to have a common set of interface for local(ext4)/NFS/HDFS interfaces. Similarly we should capture all pre-signed-urls as one. However, until we have robust support for Azure, it's probably Ok to have one for azure in cli/common.py.

@xutingl does this work well for you to integrate the pre signed urls?
@HaileyJang and @parasj what do you think about the proposal for the on-prem interface?

@xutingl does this work well for you to integrate the pre signed urls? @HaileyJang and @parasj what do you think about the proposal for the on-prem interface?

Sure! So is the goal to create a class url_interface that is like s3_interface? Are pre signed URLs intended to be used like cp <pre signed URL> <s3://....> ?

Sure! So is the goal to create a class url_interface that is like s3_interface? Are pre signed URLs intended to be used like cp <pre signed URL> <s3://....> ?

Yes, that is the design. So we can have three of them: obj_interface, pre-signed-url, and local/distributed filesystems.

https://arrow.apache.org/docs/python/filesystems.html#filesystem-hdfs


Sorry

Sorry, this applies to FW1.0.0-FW19.0.1, fat32 and exfat

I prefer for the patterns/functions/patches to have names reference what they do/accomplish


from datasets import Dataset is failing

Describe the bug
A clear and concise description of what the bug is.
Steps to reproduce the bug
# Sample code to reproduce the bug
from datasets import Dataset

Expected results
A clear and concise description of the expected results.
Actual results
Specify the actual results or traceback.
/usr/local/lib/python3.7/dist-packages/datasets/utils/file_utils.py in ()
25 import posixpath
26 import requests
---> 27 from tqdm.contrib.concurrent import thread_map
28
29 from .. import version, config, utils
ModuleNotFoundError: No module named 'tqdm.contrib.concurrent'

NOTE: If your import is failing due to a missing package, you can
manually install dependencies using either !pip or !apt.
To view examples of installing some common dependencies, click the
"Open Examples" button below.
Environment info

datasets version: latest version as of 07/21/2021
Platform: Google Colab
Python version: 3.7
PyArrow version:

Hi @kswamy15, thanks for reporting.
We are fixing this critical issue and making an urgent patch release of the datasets library today.


feat(api): Manage context window size by trimming/summarizing content

User Story
As a user
I want LeapfrogAI to gracefully handle overextending context window
So that I don't start getting gibberish when the context window is exceeded.
Additional context
Per @CollectiveUnicorn try trimming the information and passing a summary instead.

We need to have a few pieces in place to get started:

Token counting (#964)
Maximum context size for the currently loaded model


Change Expensify.cash to New Expensify

Details

Change Expensify.cash name to New Expensify.
Change Repo Url to https://github.com/Expensify/App from https://github.com/Expensify/Expensify.cash
Update Readme and Other documentation to show New Expensify.

Fixed Issues

$ Fixes #4213 https://github.com/Expensify/App/issues/4462
Tests | QA Steps

Expensify.cash should not be visible publicly in the App on any platfrom. Instead you should see New Expensify.

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Can't be depicted.

@Jag96 Question:

Mac desktop app is packaged as Expensify.cash. Do you want t change it as well and thus the Download url?

@parasharrajat yes let's update that as well, we can use NewExpensify.dmg for the artifactName and use New Expensify as the title

@Jag96 I have changed almost all instances. Please check carefully and tested the app by making builds on each platform.
There are still a few places that I am confused of

Detox Config in package.json. I am not sure about the case.
Second Expensify.cash.app
https://github.com/Expensify/App/blob/ec38ff9574ff9f1ac997b29b871aaf13afc5d57e/ios/ExpensifyCash.xcodeproj/project.pbxproj#L58

Could you please help me verify all the changes and tell me if I miss somewhere?
Thanks. It would be a great help.

@Jag96 Renaming the folders breaks a lot of paths in info.plist and other files. How can I autocorrect them? I am new to IOS projects& xcode.

No worries, Xcode is a pain when it comes to this stuff. Can you give an example of a path that is messed up or a screenshot of what you're seeing? I think the main things here are:

Make sure you do step 7 in https://github.com/Expensify/App/pull/4408#pullrequestreview-723852704
When renaming the folders in Xcode, it is possible that they aren't being renamed in your files, so you may have to right click a folder in Xcode and choose Add files to NewExpensify and re-import them

Going to tag @AndrewGable on this since he did the renaming last time, just to make sure there isn't another strategy that is easier for this

I believe I followed this stack overflow: https://stackoverflow.com/a/35500038/1858217

Thanks, @AndrewGable I got hands-on on that post just today. I am following that.

@Jag96 All set. It was a hack off the task took around 3 days to carefully change and test everything. Xcode is really bad at managing projects. I have to manually change the path for each source file and rename the old ExpensifyCash to NewExpensify in the Xcode Project metadata.
I have tested the build on all platforms.

There is one BasePackageList.java file that is autogenerated every time I run the android build. I think we should include this in the Code.
Path => /android/app/src/main/java/com/expensify/chat/generated/BasePackageList.java
The content of it is as follows
package com.expensify.chat.generated;

import java.util.Arrays;
import java.util.List;
import org.unimodules.core.interfaces.Package;

public class BasePackageList {
  public List<Package> getPackageList() {
    return Arrays.<Package>asList(
        new expo.modules.haptics.HapticsPackage()
    );
  }
}

Update usages in Timing.js and Session.js a47c15c/src/libs/actions/Session.js#L123 (blame) cc  since this will likely change some dashboards, not sure if they're being used

I have not done this. This will affect backend Dashboards statistics.

There is one BasePackageList.java file that is autogenerated every time I run the android build. I think we should include this in the Code.

I'm seeing that as well, I agree w/ adding it

@Jag96 Done.

Updated the description because this PR should hopefully also fix https://github.com/Expensify/App/issues/4462

Based on the level of effort, Could a bonus be added to this job? Tagging cc: @Beamanator for :eyes: . I have extended the scope of this PR to cover full migration to New Expensify.

It changes the Expensify.cash to New Expensify.
It adds URLs for new.expensify.com and its staging varients.
It migrates the Xcode project.
It Changes the App Name for all platforms.
It changes all references of old GitHub URLs to the new ones.
It updates Package names of builds.
It updates tests to cover the New Expensify.
etc.

In the Xcode project navigator, it looks like there are a few files that are not included in Xcode:

I am not really sure about these. I checked but I am not sure what should be the path for these. Could you please pull the branch and add those references. @Jag96

I wonder if we should rename the app so that the two Expensify apps are kept together in the app launcher for ease of use and to remind customers of the new app? I posted in Slack for others to share their opinions.

Seems Great. But I don't know how to do that. Could you please help me with this?
Other changes are done...

Seems Great. But I don't know how to do that. Could you please help me with this?

@parasharrajat sure

For Android we would just need to change this string to something like 'Expensify New'
For iOS I think you need to find this String under Expensify.cash > Targets > ExpensifyCash > Build Settings > Product Name:

@Julesssss  I have changed these settings already.

If everything is fine. Could someone quickly review and merge this? I have to resolve conflict every 4 hours.

@Julesssss I have changed these settings already.
But are you suggesting changing the name to Expensify New from New Expensify?

Yeah. I thought that you agreed and asked me how to do this?

Seems Great. But I don't know how to do that. Could you please help me with this?

OK. I will change those names. I didn't pay attention to New key placement. But Just out of curiosity. I think changing the name to Expensify New is not good as Brand Name is New Expensify.

@Jag96 Done.

https://github.com/Expensify/App/pull/4274 got merged in between, going to post something internally asking everybody to hold off on merging anything so we can get this through. Also, we can skip waiting for tests on this since its just the version bump that is in the diff.

There's currently cherry-pick testing happening, so we'll have to hold off on updating/merging this until that is done. I'll post back here when we're good to go, and after confirming I'll have everybody hold off on merging until we're done w/ this. Sorry for the back and forth here.

Skipping unnecessary actions to get this merged: https://github.com/Expensify/App/pull/4408#issuecomment-897010587

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @Jag96 in version: 1.0.85-10 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

This PR is failing in iOS https://github.com/Expensify/App/issues/4739

Seeing as #4739 is closed, are we good here @isagoico ?

Yep! We can check it off.

This has been deployed to production and is now subject to a 7-day regression period.
If no regressions arise, payment will be issued on 2021-09-06.  :confetti_ball:


Support the dashed prop in Line abstraction (#103)

This PR adds support for the dashed prop for Drei's Line abstraction, using the advice from the below comment on the Three webgl_lines_fat example.
https://github.com/mrdoob/three.js/blob/22ed6755399fa180ede84bf18ff6cea0ad66f6c0/examples/webgl_lines_fat.html#L236-L239

great! could you make that useeffect a layouteffect?

thinking of it, doesnt this work?
      <primitive dispose={null} object={lineGeometry} attach="geometry" />
        vertexColors={Boolean(vertexColors)}
        resolution={resolution}
        linewidth={lineWidth}
        dashed={dashed}
        defines-USE_DASH={dashed ? "" : undefined}
        {...rest}
      />

Neat - I didn't even know that useLayoutEffect existed.  I'll update the PR.
No, just changing the prop isn't sufficient, because it won't set lineMaterial.needsUpdate to true.  I expect it would work if dashed was constant, but the line material wouldn't update if you changed dashed while the Line was mounted.
(Also, I don't know what's happening inside the shader, but apparently setting lineMaterial.defines.USE_DASH to undefined is not sufficient - it actually needs to be deleted)

oh, ok then lets use uLE. to explain, this effect fires after react has rendered, but before threejs had the chance to paint/render it to the screen. so you get references to all created objects, but you can still change stuff before actual render. only caveat is that it must block render, so not so suitable for expensive calculations etc.


broken link

The "Pricing for Audio Conferencing" link on this page is broken.

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

ID: 6b07cfcf-8f31-91ed-b1de-c7826a1ab91d
Version Independent ID: dfbc4212-8f47-326a-f872-8186a915ae1e
Content: Country/region availability - Audio Conferencing, Calling Plans - Microsoft Teams
Content Source: Teams/country-and-region-availability-for-audio-conferencing-and-calling-plans/country-and-region-availability-for-audio-conferencing-and-calling-plans.md
Service: msteams
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

@aamillerMSFT , is  below link is  suitable or not ?
https://www.microsoft.com/en-in/microsoft-teams/compare-microsoft-teams-options

It should be pointed to here.  https://go.microsoft.com/fwlink/?linkid=799762
Similar to this this section of this site: What are Communications Credits? - Microsoft Teams | Microsoft Docshttps://docs.microsoft.com/en-us/microsoftteams/what-are-communications-credits#want-to-know-about-plans-and-pricing
Want to know about plans and pricing?
You can see the plans and pricing by visiting one of the following links:

   Calling Plans<https://go.microsoft.com/fwlink/?linkid=799761>

   Audio Conferencing<https://go.microsoft.com/fwlink/?linkid=799762>

   Phone System<https://go.microsoft.com/fwlink/?linkid=799763>

From: VARADHARAJAN K @.>
Sent: Thursday, March 11, 2021 4:03 AM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness @.>
Cc: Aaron Miller @.>; Mention @.>
Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] broken link (#6834)
@aamillerMSFThttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FaamillerMSFT&data=04|01|aamiller%40microsoft.com|4c2e9155d3bb4c586fbb08d8e474d2ba|72f988bf86f141af91ab2d7cd011db47|1|0|637510537698712066|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=KhYyGh4h595gWyMd1pALPA4GoL0ANB3EbGZ8ruMcMos%3D&reserved=0 , is below link is suitable or not ?
https://www.microsoft.com/en-in/microsoft-teams/compare-microsoft-teams-optionshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.microsoft.com%2Fen-in%2Fmicrosoft-teams%2Fcompare-microsoft-teams-options&data=04|01|aamiller%40microsoft.com|4c2e9155d3bb4c586fbb08d8e474d2ba|72f988bf86f141af91ab2d7cd011db47|1|0|637510537698722058|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=qpQj8yQMCxB95%2FudXpbs0zvV3h4qH84Rg7N1%2BayWuT0%3D&reserved=0

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-SkypeForBusiness%2Fissues%2F6834%23issuecomment-796618685&data=04|01|aamiller%40microsoft.com|4c2e9155d3bb4c586fbb08d8e474d2ba|72f988bf86f141af91ab2d7cd011db47|1|0|637510537698722058|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=SG1UGXJVSQugW%2FezGzaqSRWaN%2BIPMdSr7ZavFKRXJjk%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMQHVYAGIGWHQRY3L4CLWI3TDCIMNANCNFSM4Y644AIA&data=04|01|aamiller%40microsoft.com|4c2e9155d3bb4c586fbb08d8e474d2ba|72f988bf86f141af91ab2d7cd011db47|1|0|637510537698732052|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=VM9gC3%2BTsAY%2FX8GfOmU5Rh39w08oj59bySJOvwtxBNs%3D&reserved=0.


Failed to run automated scorecard-action@golang-staging test-organization-ls/scorecard-action-private-repo-tests

https://github.com/test-organization-ls/scorecard-action-private-repo-tests/actions/runs/2175340751

e2e is failing for the golang-staging branch

that has to do with cosign API and work @rohankh532 did. @rohankh532 did we set up the COSIGN_EXPERIMENTAL=1 in the code?
@naveensrinivasan can you confirm this result is for the go (not bash entrypoint.sh)?

that has to do with cosign API. @rohankh532 did we set up the COSIGN_EXPERIMENTAL=1 in the code?
@naveensrinivasan can you confirm this result is for the go (not bash entrypoint.sh)?

I think this issue is because id-token isn't set to write in the workflow

Thanks @rohankh532 !

closing, as per https://github.com/ossf/scorecard-action/issues/180#issuecomment-1105508516


Sequence mode: Tooltip of "@" shows only Sugar chemistry structure.

Steps to Reproduce

Switch to the Macro mode

Open KET file with modified nucleotides
ketcher (block).zip

Open Sequence mode

Actual behavior
Tooltip of "@" shows only sugar chemistry structure.

Expected behavior
The entire block is represented with a '@' symbol.
Tooltip of "@" should represent all chemical elements of block.
Related:

https://github.com/epam/ketcher/issues/3734
https://github.com/epam/ketcher/issues/4439

Desktop (please complete the following information):

OS: Windows 10 Pro (version 22H2) x64
Browser: Сhrome
Version: (123.0.6312.86) x64

Version 2.20.0-rc.2
Build at 2024-04-08; 05:30:10
Indigo Toolkit
Version 1.20.0-dev.1.20-gfe00419b-wasm32-wasm-clang-12.0.0

Moved to Refined Backlog since not fixed over 1 release


bug: pennylane job fails with base containers

Describe the bug
We are not able to create successful job when using SV1 device for PennyLane when using Base Containers and were running into import issues like: ImportError: cannot import name 'ObservableReturnTypes' from 'pennylane.operation'
To Reproduce
Steps to reproduce the behavior:

Go to Using_PennyLane_with_Braket_Jobs.ipynb in braket-examples, locally or by spinning up the Braket Notebook Instance.
Instead of using the image_uri = Framework.PL_TENSORFLOW or Framework.PL_PYTORCH, use Framework.BASE` to as image_uri.

Expected behavior
Check the CloudWatch logs in the console account for the submitted job, as the job would fail with described bug.
Screenshots
N/A
System information (please complete the following information as applicable):

Package Versions: amazon-braket-containers==1.6.5 and containers for base image using PennyLane==0.23
Working Environment: [e.g. Local, Braket Notebook Instances] : All
Browser [e.g. chrome, safari]: N/A
Region [e.g. us-west-2]: All regions.

Known workaround (if applicable):

Submit the pennylane jobs using tensorflow or pytorch image uris.
Create custom base image_uri:
a. Checkout this package and add pennylane dependency as pennylane==0.22.0 here: https://github.com/aws/amazon-braket-containers/blob/main/base/jobs/docker/1.0/py3/Dockerfile.cpu#L123
b. Create a custom base image_uri by submitting the container build in your aws_account by following these steps: https://github.com/aws/amazon-braket-containers/blob/main/README.md
c. Use the created custom image_uri from your ECR repository to run the pennylane job with base containers.

Additional context
Add any other context about the problem here.

This issue is fixed with https://github.com/aws/amazon-braket-containers/pull/40, closing this issue.


New Website & Documentation

Description
This PR brings a whole new website + documentation page.
There's still a lot to do, but we're improving it from day to day.
ToDo / Goals

[ ] Landing Page

[ ] Company Logos
[ ] Getting Started

[ ] Documentation

[ ] Port all pages
[ ] Overview
[ ] Live Examples (maybe new PR)
[ ] Anchors (maybe new PR)

[ ] Ecosystem
[x] Social Links
[ ] Responsive
[ ] Accessibility (maybe new PR)
[ ] Use Fela not inline style 😂😂
[ ] Syntax Highlighting

Versioning
Just the meta stuff, we don't have to update anything.
Checklist
Quality Assurance

You can also run yarn run check to run all 4 commands at once.

[x] The code was formatted using Prettier (yarn run format)
[x] The code has no linting errors (yarn run lint)
[x] All tests are passing (yarn run test)
[x] There are no flow-type errors (yarn run flow)

Changes
If one of the following checks doesn't make sense due to the type of PR, just check them.

[x] Tests have been added/updated
[x] Documentation has been added/updated
[x] My changes have proper flow-types

Closing this in favor of a newer approach that might be coming soon.


Bug: Navbar is not responsive

What happened?
Navbar is not responsive and I think the title after logo as "Home" is not required. Logo itself is working as an home link. So, there's no need of logo text.
Add screenshots

What browsers are you seeing the problem on?
No response
Record

[X] I have checked the existing issues
[X] I want to work on this issue

can you please assign me this issue?

thanks @MadhuSaini22 , yes I agree.


Remove integration tests

Since they were transferred to the client, these files are deprecated and no longer kept up-to-date, so they should be removed. It does not help us at all to keep the integration tests in two places.

Besides committee create, they used to be functional alright, and probably still are. Maybe the necessity has lowered since (e)manu(e/a)l testing has grown.
Synergy is better in the client, for you are able to alter html attributes by cypress's needs. As long as you remember to start the whole stack it matters little were the tests are located.

missing tests transferred to the client in https://github.com/OpenSlides/openslides-client/pull/1621. Workflow adjusted to use the tests in the client repo to still have the "full" tests available in this repo.


feat: allow styles when digit has value

adds a prop filledPinCodeContainerStyle for when there is a character present allow a specific set of styles

Your contribution is much appreciated, @EddWills95 !


Update changelog and fix flaky test

Addresses https://github.com/azure/azure-sdk-for-net/issues/13200

/azp run net - servicebus - tests


Intake arm actuates when enabled

The intake arm remembers the last state before "disabled" and then restores it when "enabled". Disable resets all solenoids so the arm will always retract when "disabled". But it should stay there when enabled, for safety reasons. And all the logic should be designed assuming that.

@CaelumCat @trevorgeng  @Moirai01 @INPUTCODE please consider this issue as an opportunity to learn the robot code. Ask questions in the comments when you need help. @Duckfan77 and @LoopedBard3 are not allowed to take on this issue but can answer questions.

Fixed: https://github.com/team3130/Geneva/commit/4f013f424a2dfc215b14aca9562cc36c3b730a0f


Increase auto name length to 255

OpenStack supports names of 255 in (as far as I can tell) all places.
Also update to make use of AutoName members from tfbridge library.

LGTM.


Making a different color value when a new line overlaps the same line path

When clicking on two points that have the same path it creates another line on top of it, causing some issues to tell where is the last used point. Found myself clicking on "delete" multimple times because of this.
I think this could be solved by making overlaping lines a different but subtle color value in the editor when lines are overlaping.
PS: Awesome tool btw! I'm new with Github, where can I create threads for suggestions? I've some ideas

@alarcondgtuc interesting, yes. I think the first improvement is to show where the last point is, and then show overlapping lines on different layers too. Overlapping lines on the same layer could be tricky because there are some "real" use cases for that I believe?

For example to have this in a single layer you would have to backtrack over some of the lines already there, but now that I think more about it maybe that should be in a different layer. I'll think about how to display overlapping lines, thank you for the suggestion.
Also feel free to create new issues for suggestions :D


feat: upgrade mapping-service to v2 workload reconciler

Implements the MappingService controller using the new workload reconciler added in #144.
Generates alpha release v0.13.0-alpha.8

/kind feature
/priority important-soon
/assign

/approve


New package: Rocket_threaded v1.7.2

Registering package: Rocket_threaded
Repository: https://github.com/jakubMitura14/Rocket_threaded.jl
Created by: @jakubMitura14
Version: v1.7.2
Commit: 0c2fe731323d14332c4312543d7e7e1e61a58a37
Reviewed by: @jakubMitura14
Reference: https://github.com/jakubMitura14/Rocket_threaded.jl/commit/0c2fe731323d14332c4312543d7e7e1e61a58a37#commitcomment-131364720
Description: Functional reactive programming extensions library for Julia

“Forked from biaslab/Rocket.jl”. Shouldn’t this be contributed back to Rocket.jl?

Hello @goerz Frankly I want to experiment with some ideas before I will go with PR for contribution - Hovewer I need to check it within my packages. So the problem is I am updating package MedPipe3D  that depends on MedEye3D and MedEye3D depends on Rocket.jl In order to test MedPipe3D I need to load MedEye3D with updated dependencies to my fork of Rocket. Hvewer in order to do this I need to put my dependency on my Fork to Rocket in Project.toml of MedEye3d.
Summarising Can I add to the project.toml of a package in [compat] section a link to github repo of the fork instead of the package version?
I would like to add sth like
[compat]
Rocket_threaded = "https://github.com/jakubMitura14/Rocket_threaded.jl"

to project.toml of MedEye3D
then load MedEye3D by
Pkg.add(url="https://github.com/jakubMitura14/MedEye3d.jl.git")

Then I would not need to register fork as a new package for experimentation - is it possible?

You can use a LocalRegistry.
Alternatively, use Pkg.develop to install your forked version of Rocket into a given environment. You can’t specify that in a Project.toml, but it does get recorded in the Manifest.toml. So as long as you don’t delete that file, even re-instantiating the environment will keep using the local version.

@goerz thanks !

I think you no longer want to register, since the repo went away, but that's not needed. I was curious to watch over your shoulder... And it can also be helpful to others (and you) to have access to unregistered packages. Did you contribute back into Rocket.jl? The main one?

I am still testing the idea - for now I had some data races, channel closed etc. but If it will work I will contribute back, thanks for asking !


Build instructions in README seem obsolete

I just cloned the repo and am trying to build the main branch. The instructions in the README don’t seem to describe the current state of the repo:

"Dependencies (libuv, and mbedTLS) are specified as git submodules” — Nope, there are no submodules in the repo.
"We use Cmake as our build system. Any of the standard generators(makefile, ninja) should be working fine, let us know if you see any issues.” — I did the usual mkdir build && cd build && cmake .. incantation on my macOS system and got the following error:

CMake Error at CMakeLists.txt:75 (find_package):
  Could not find a package configuration file provided by "llhttp" with any
  of the following names:

    llhttpConfig.cmake
    llhttp-config.cmake

  Add the installation prefix of "llhttp" to CMAKE_PREFIX_PATH or set
  "llhttp_DIR" to a directory containing one of the above files.  If "llhttp"
  provides a separate development package or SDK, be sure it has been
  installed.

There’s no mention of llhttp in the README. I can try installing it with homebrew and see if that resolves the issue.

Yeah, lots of changes that aren't relevant anymore for sure! thanks for filing an issue.

I found the llhttp repo but I’m confused — it’s primarily TypeScript. There are instructions in its README for using it in C code with CMake, but it has instructions for what to put in your CMakeLists and it looks nothing like what the diagnostics above say to do.
Sort of frustrating because I don’t really need an HTTP parser; all I want is TLS support for libuv.

I found the llhttp repo but I’m confused — it’s primarily TypeScript. There are instructions in its README for using it in C code with CMake, but it has instructions for what to put in your CMakeLists and it looks nothing like what the diagnostics above say to do.
Sort of frustrating because I don’t really need an HTTP parser; all I want is TLS support for libuv.

I believe llhttp C implementation is generated from Typescript.
After seeing your use case I am considering making HTTP support optional. This will reduce the number of dependencies (llhttp, zlib) for that usage

I too only want TLS for libuv (using mbedtls in my case). I'm using the zig build system, so wrote my own build config for that but I'd a) like to upstream that if it's interesting to the project and b) think llhttp should be made optional, regardless if the build system is zig, cmake or something else :)


Getting timeouts when trying "cf service-access" commands

Command
cf disable-service-access  -o
Disabling access to all plans of service logstash-6 for the org<EMAIL_ADDRESS>as admin...
CLI Version
Error
Error performing request: Get https://api.system.<end_point>/v2/service_plan_visibilities?order-direction=asc&page=244&results-per-page=50: dial tcp: lookup api.system.<end_point>: no such host
When I run the exact same command from the jumphost, it has taken 20mins and finally succeeded.
Customer has 7000 orgs.
In prod environment.
cf service-access
cf enable-service-access
cf disable-service-access
All the 3 commands take like unto an hour to respond and sometimes timeout.
Stack Trace
Platform Details
e.g. Mac OS X 10.11, Windows 8.1 64-bit, Ubuntu 14.04.3 64-bit
Shell
e.g. Terminal, iTerm, Powershell, Cygwin, gnome-terminal, terminator

@SocalNick: I read on slack that this command is known to take an extremely long time due to the number of requests it needs to make (number of service brokers X services per broker X plans per broker X orgs that use said plan). Can you provide us an API that would reduce the number of calls the CLI needs to make?

we have similar issue .. there should be faster specific options for doing this from cf cli

Looking at what we do prior to the enable/disable service request, for whatever reason we are getting a full suite of information about every service X plan available to this organization. This seems extremely unnecessary and heavy weight for what these commands are trying to do.
I think if we re-evaluate how these commands are setup, we may be able to make it faster (eg, not make the n*m number of requests).
The service-access command however will still require the previously quoted "service brokers X services per broker X plans per broker X orgs that use said plan" number of requests. So that will still unfortunately take a long time to return.

@XenoPhex thanks for looking into ways to improve the enable / disable calls. These commands seem like candidates for API endpoints that take the service_guid, plan_guid (optional), and org_guid (optional). Feel free to drop a story.
I don't know how we could improve service-access for deployments with 7000 organizations. I would start by considering whether or not this command provides any useful information at this scale. I would consider not displaying organization information when there are more than X orgs and requiring the command to be bound by a particular broker, service, or org.
Experimenting on A1, I've yet to get the service-access command to return when trying to filter by org.

The issue description lists 3 commands, each supporting multiple arguments affecting the API calls made.
We'll explore the 3 commands separately as follows:

enable-service-access: https://www.pivotaltracker.com/n/projects/892938/stories/118894653
disable-service-access: https://www.pivotaltracker.com/n/projects/892938/stories/119236239
service-access: https://www.pivotaltracker.com/n/projects/892938/stories/117756073

When those investigations are complete, let's revisit and see if and what further work would be required for combinations of specific arguments to these commands.

@svennela We have just pushed an improvement to the commands and are curious to see how they fare on your cloud foundry. Can you please try the corresponding CF CLI binary below and give us feedback?
Linux-64
Windows-64
OSX-64

We have improved the performance of enable-service-access and disable-service-access. Please try with cf CLI 6.19.0, released today.
https://github.com/cloudfoundry/cli#downloads
The service-access performance is in the backlog to be investigated hopefully soon.
Regards,
Dies Koper
CF CLI PM

Once you have too many Orgs cf service access will not work there are few things you can do
Try limiting scope by cf service access -b
If you wanted to add service access then I can send you cf api to do so
Sent from my iPhone

On Jun 8, 2016, at 6:28 PM, Dies Koper<EMAIL_ADDRESS>wrote:
We have improved the performance of enable-service-access and disable-service-access. Please try with cf CLI 6.19.0, released today.
https://github.com/cloudfoundry/cli#downloads
The service-access performance is in the backlog to be investigated hopefully soon.
Regards,
Dies Koper
CF CLI PM
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@dkoper @amulyas We recently faced a lot of issues while running 'cf service-access' on one of our environments. The turnaround time for the command execution is >5mins.
The other recommendation that 'cf service-access -b SERVICE_BROKER_NAME' reduces the turnaround time is also wrong. As the time taken for execution of this command is exactly the same as the former one. It probably just gets the same result for both the commands and simply filters the output as per the flag.
Can you please comment when this issue will be fixed for CF or at-least the 'cf service-access -b' will have a better performance than 'cf service-access'? Alternatively, is there any other way to get the results as returned by the cli command, which has a better turnaround time? May be some sort of api?

@pritishmishra only way I was able to get the information of cf service-access -b is by query the database directly there is no API as relationships are maintained separately and presented only after union of everything

@pritishmishra We still have so many stories to go through until we get to this one. That said, initial explorations (see comments above) indicated that there currently are no APIs to make this faster.
Once we get to this story, I hope we'll have a better idea what APIs to request CAPI for.

Hi @svennela thanks for creating this issue. I'm circling back to see if this command is working for you now; it looks like there was an improvement to the command that was made after your initial comments. We still plan on rewriting this command but I'm reaching out to see if there's been improvement on your side. Thanks.

Hey @svennela Hopefully this issue was resolved a few months ago and so I'm going to close this issue. Please feel free to reopen it if you encounter this again!


Add tracing service to example/platform/esp rpc

Problem
Add trace functionality to esp32 examples
Change overview
Add trace service to RPC services
Testing
Build esp32 all cluster example with RPC turned on and off.

/rebase

/rebase


Mouse can't select text in a multi-line textfield

Steps to Reproduce
Dartpad Example: https://dartpad.dev/c377b45f28f1cd60f23c5ddef9c88524

Run flutter create bug.
Update the files as follows:
main.dart:

import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Center(
          child: MyWidget(),
        ),
      ),
    );
  }
}

class MyWidget extends StatefulWidget {
  createState() => MyWidgetState();
}

class MyWidgetState extends State<MyWidget> {
  TextEditingController _cont1;
  TextEditingController _cont2;

  @override
  initState() {
    _cont1 = TextEditingController();
    _cont2 = TextEditingController();

    _cont1.text = 'Text selection works here';
    _cont2.text = 'Text selection does not work\nwhen text is multi-line.';
    super.initState();
  }

  @override
  Widget build(BuildContext context) {
    return Column(
      children: [
        TextField(controller: _cont1),
        TextField(controller: _cont2, maxLines: null),
      ],
    );
  }
}

On flutter web, I can not select text with the mouse on the multi-line text field.

Expected results:

Actual results:

Logs

for multi-line text field, the issue comes out only when controller initialized with a text. It works fine when you don't provide initial text.

Hi @WG-Studios
the issue occurs in the latest master as well
[✓] Flutter (Channel master, v1.18.0-9.0.pre.14, on Mac OS X 10.15.4 19E287, locale en-EE)
    • Flutter version 1.18.0-9.0.pre.14 at /Users/nevercode/development/flutter_master
    • Framework revision dd88b20435 (34 hours ago), 2020-04-25 19:02:03 -0700
    • Engine revision 2b94311a77
    • Dart version 2.9.0 (build 2.9.0-3.0.dev 94178e920e)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/nevercode/Library/Android/sdk
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.3.1, Build version 11C504
    • CocoaPods version 1.9.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.0.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

[✓] VS Code
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.9.1

[✓] Connected device (4 available)
    • Francesco’s iPhone • 42f545c80499280e43186687e3c51ad278ab2985 • ios            • iOS 12.4.4
    • iPhone 8           • D5F70F31-B488-4454-9539-320B5551D92A     • ios            • com.apple.CoreSimulator.SimRuntime.iOS-13-3 (simulator)
    • Web Server         • web-server                               • web-javascript • Flutter Tools
    • Chrome             • chrome                                   • web-javascript • Google Chrome 81.0.4044.122

• No issues found!

possibly related to cursor issue
see also proposal
Thank you

Hi all
testing gallery for a different issue
I noticed that the issue persist with the latest master
Thank you

I have the same problem when using on the Web. Are there any solutions? Thank you !
[✓] Flutter (Channel master, 1.20.0-1.0.pre.42, on Mac OS X 10.15.2 19C57,
    locale en-US)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 3.5)
[✓] VS Code (version 1.46.0)
[✓] Connected device (2 available)

Same problem here

Having the same issue... In both English and Hebrew.

Having the same issue

Looking at different threads, this problem persists since February and still has no solution
Any application that needs forms, these are all management applications, have this problem
I understand that Flutter web is in beta, but 5 months to fix such an important bug, seems to me a big mistake
I hope you understand those of us who have given Flutter Web a chance in our companies and that we are faced with a problem with our customers that we cannot solve

I have the same problem for spanish this needs a fix ASAP!!! My web app is used for editing descriptions of products, some descriptions come in many lines, this feature is crucial, it makes anything useless.

I HAVE THE SAME PROBLEM, PLEASE ATTENTION HERE!

I'm having the same issue here. Seeing that there's no solution to this problem yet, would writing a JS plugin for a normal-behaved input field and using it instead of the Flutter text field be a viable solution? I'm looking for a temporary solution till this gets fixed.

Same problem here.

What version of flutter downgrade will reverse the mouse positioning problem?   I tried 1.15.18 and it did not solve the problem.   Is there additional steps to reverting back.
git checkout v1.15.18
flutter doctor
flutter build web

I'm having the same issue here. Seeing that there's no solution to this problem yet, would writing a JS plugin for a normal-behaved input field and using it instead of the Flutter text field be a viable solution? I'm looking for a temporary solution till this gets fixed.

I ended up using a HtmlElementView to embed an InputElement (for single line text fields) and a TextAreaElement (for multiline text fields). For this I used platformViewRegistry.registerViewFactory from dart:ui (side note: I had to ignore the undefined_prefixed_name error that the dart analyser throws, because platformViewRegister is not available until compile time). It works just fine and I think it's a viable (temporary) solution that's not so hard to implement.

as stated in the bug, if you use
flutter run -d chrome --release --dart-define=FLUTTER_WEB_USE_SKIA=true
the textformfield work as specified.
Copy the build files after running the command

as stated in the bug, if you use
flutter run -d chrome --release --dart-define=FLUTTER_WEB_USE_SKIA=true
the textformfield work as specified.
Copy the build files after running the command

can we make it work on vs code debug mode? like when pressing f5

Use the command line then copy the build web files
Sent from my iPhone

On Jul 12, 2020, at 7:24 PM, Buildex<EMAIL_ADDRESS>wrote:

as stated in the bug, if you use
flutter run -d chrome --release --dart-define=FLUTTER_WEB_USE_SKIA=true
the textformfield work as specified.
Copy the build files after running the command
can we make it work on vs code debug mode? like when pressing f5
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Same issue here. Wishing for a solution soon

use flutter run -d chrome --release --dart-define=FLUTTER_WEB_USE_SKIA=true as a work around.  It will compile your code for the web.  Don't use flutter build web.   copy the build -> web files

Don't use flutter build web

It should also be okay to use flutter build web (e.g. flutter build web --release --dart-define=FLUTTER_WEB_USE_SKIA=true). Are you seeing an issue?

as stated in the bug, if you use
flutter run -d chrome --release --dart-define=FLUTTER_WEB_USE_SKIA=true
the textformfield work as specified.
when running the command, you will see flutter compile the main.dart code. Yeah
Copy the build files after running the command

but it has more other problem with 'FLUTTER_WEB_USE_SKIA' model

flutter run -d chrome --release --dart-define=FLUTTER_WEB_USE_EXPERIMENTAL_CANVAS_TEXT=true
this can fix it

but it has more other problem with 'FLUTTER_WEB_USE_SKIA' model

Can you provide more information on that?

I have the same issue, I can't select text with the mouse on the multi-line text field

testing the code above with the latest master
logs
[✓] Flutter (Channel master, 1.21.0-6.0.pre.37, on Mac OS X 10.15.5 19F101, locale en-GB)
    • Flutter version 1.21.0-6.0.pre.37 at /Users/nevercode/development/flutter_master
    • Framework revision 35e7005184 (2 days ago), 2020-07-25 09:44:17 -0700
    • Engine revision 626244a72c
    • Dart version 2.9.0 (build 2.9.0-21.0.dev a3815b6590)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/nevercode/Library/Android/sdk
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.12.2

[✓] Connected device (4 available)
    • Pixel 3a (mobile) • 965AY0WP5C • android-arm64  • Android 10 (API 29)
    • macOS (desktop)   • macos      • darwin-x64     • Mac OS X 10.15.5 19F101
    • Web Server (web)  • web-server • web-javascript • Flutter Tools
    • Chrome (web)      • chrome     • web-javascript • Google Chrome 84.0.4147.89

• No issues found!

the issue still persists
thank you

I noticed this is working with TextField, but not EditableText:

Sample
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Center(
          child: MyWidget(),
        ),
      ),
    );
  }
}

class MyWidget extends StatefulWidget {
  createState() => MyWidgetState();
}

class MyWidgetState extends State<MyWidget> {
  TextEditingController _cont1;
  TextEditingController _cont2;
  FocusNode _textFocusNode = FocusNode();

  @override
  initState() {
    _cont1 = TextEditingController();
    _cont2 = TextEditingController();

    _cont1.text = 'Text selection works here';
    _cont2.text = 'Text selection does not work\nwhen text is multi-line.';
    super.initState();
  }

  @override
  Widget build(BuildContext context) {
    return Column(
      children: [
        TextField(controller: _cont1),
        EditableText(
          controller: _cont2,
          focusNode: _textFocusNode,
          style: TextStyle(color: Colors.black, fontFamily: "Roboto Mono"),
          cursorColor: Colors.blue,
          backgroundCursorColor: Colors.grey,
          selectionColor: Colors.lightBlue,
          maxLines: 100,
        ),
      ],
    );
  }
}

@johnpryan EditableText provides very basic selection support. You can't double-tap or drag your mouse to select. It's the same on iOS and Android as well.

One extra detail: with just one extra line I find any text on that second line doesn't always render.
Contrasting:
--release --dart-define=FLUTTER_WEB_USE_SKIA=true
with the other suggestion of:
--release --dart-define=FLUTTER_WEB_USE_EXPERIMENTAL_CANVAS_TEXT=true
The latter is NOT as good. The selection draws with jank, stutters especially as the mouse crosses line divides, also space characters aren't rendered, (and yes, I realise spaces are blank, so perhaps better to write that 'the cursor doesn't move') until a following character (one with shaded pixels) is drawn. So the former suggestion (the one repeatedly proffered in this trail), is much better. I have zero technical understanding of what either mean, I just needed a workaround quickly to tried both.
In case anyone at google reading this, exactly as someone wrote above, we all know web is in beta, but to get our companies to start adoption we have started building web interfaces. In my case they are internal, and a few bugs are fine but this is a pretty vital one, text entry is such a biggy in corporate apps.

@DannyJoinedApps please file an issue describing what you are seeing (screenshots would be nice to have). Also please make sure to upgrade to the latest master version. The issue of the cursor not moving should've been fixed last week.

@mdebbar Hi, sorry, really sorry, I should have checked. You are absolutely right - upgraded and all is fixed. Works perfectly :) Thank you!!


Add optional parameters to claim command (all, outputId, etc.)

Currently the claim command claims all possibly owned outputs without asking. The user have no way to specify for example to accept incoming transfer of a certain native token, etc.
Add optional parameters to the claim command, for examle to claim a given output or outputs.
It would also be good to add a command to display claimable outputs and show some semantic info about it, this is described in #96

I added an option to claim specific outputs. Were you thinking of anything else for this command @lzpap ?


After update ember 3.1.2, inputClass doesn't appear

I just to update to 3.1.2 and strangely the css class passed through inputClass attribute doesn't appear but instead there a white space. Someone knows if it is an error related with the upgrade?
Thanks!

Hey @devCaso,
Let me double check today or tomorrow and reach you back.
Best regards,
Daniel.

@dmuneras thanks you very much because your soon response but it was my fault, I didn't see that I had duplicated the inputClass attribute and the second was inputClass=' ' I'm so sorry :)
By another hand, this mistake didn't overwrite the attribute value in the previous version (3.0), because this was the confusion.
I close this issue, thanks again :)

@devCaso thanks for taking the time to double check. I am glad you solved your problem


Adding surface to group with same name as other one

Steps to reproduce

Create 2 groups with same names.
Add surface to one of them.

Expected result
Surface in one group is created.
Actual result
Surface is created in both groups.

Done, closing.


How is the keypoint detection model used

Hello, can you provide a tutorial for key point detection，thank you.

It seems that every detection can't be used

Hi,
At this point we don't have a tutorial for key point detection.
I think this should be possible, and we could also adapt the object detection tutorials.
Closing this issue.


Re-organize networking code for Trinity

What is wrong?
Currently, all of the networking code lives under evm.p2p.  The long term plan is to split the core DevP2P components from this code into a separate library (probably the existing devp2p python library).  To prepare for this, we should start drawing firmer lines between the different sections of code that currently live in this repository.

Py-EVM code: deals specifically with the EVM
DevP2P code: deals with the generic DevP2P protocol
Trinity code: deals with running an Ethereum node over the DevP2P protocol using the py-evm EVM.

How can it be fixed
Perform the following code re-organization.  This should be done in multiple steps to keep the pull requests smaller.

Everything from evm.p2p to a new root level module devp2p
Move everything from the new devp2p module which is not strictly DevP2P protocol code to trinity.p2p
Find any imports in either of these sections of code which import from evm.utils.* and change them to use their own local utilities, or migrate the utility to eth-utils so it can be shared.

@gsalgado I also think that means we move most of the work you're currently doing over to the trinity branch (or maybe better, go ahead and merge trinity into master and just build from that common base.

When you say DevP2P I guess you mean the base-protocol (https://github.com/ethereum/wiki/wiki/ÐΞVp2p-Wire-Protocol) plus anything related to discovery and sub-protocols as well? If so, I'd prefer to call the new root-level subpackage just p2p.
Also, I think in trinity it'd make more sense to have separate, meaningfully named subpackages for the individual p2p services (e.g. trinity.lightchain, trinity.sync, etc), but it might make sense to start with everything under trinity.p2p

I'd prefer to call the new root-level subpackage just p2p

👍

Also, I think in trinity it'd make more sense to have separate, meaningfully named subpackages

👍
Once we get #379 merged would you like to do that re-org?


Unique IPs IDs

Closes #1210

Coverage remained the same at 82.199% when pulling 25d2b040aa6ae8e7f9ec5a5826ef66e68573277b on na3d:unique-ips-ids into b3eb2801fb49b86a4b8942b5133ed301a6176023 on linode:master.


Internal Server Error 500

Hi,
As my script is going through the process of building a vm, eventually I get this. Is there any logging I can use to debug this?
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed. Also I  don't get the output xml file in history.
Thanks!

Here is the setting in the PHP.INI under [WebPIChanges]
max_execution_time=300
The customization process does take a very long time....

Please also make sure the fastcgi timeout setting is configured accordingly.

Thx I’ll try that!
On Fri, Sep 14, 2018 at 18:03 Jian Liu<EMAIL_ADDRESS>wrote:

[image: image]
https://user-images.githubusercontent.com/7997931/45577098-32cbf080-b82f-11e8-941a-09d8aec13ce7.png
Please also make sure the fastcgi timeout setting is configured
accordingly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vmware/webcommander/issues/202#issuecomment-421496043,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG0n5vSpCKgl7PyxMQUvt4ayzlgJRS2Jks5ubCeWgaJpZM4Wl4K2
.

I made these changes and the issue remained. I did have a lot of write-host messages which I had used for testing the script in PS while waiting for customization, plus a transcript was running which was stopped at the end. After I removed the chatter and stopped the transcript things seemed to work. Thanks for your help.


Add flow BC for Cape Fear River to NC9 mesh

@caseydietrich as discussed in our meeting today, I am starting a thread for adding a flow BC for the Cape Fear River to the NC9 mesh. If you could provide your old SMS tutorial on how to set up ADCIRC BCs, and eventually an in-person walkthrough after I have the chance to try on my own a little bit, that would be much appreciated.

2. Look on the USGS streamflow site for gauges on the Cape Fear River. Ideally, where do we want to apply the river flows?
Per the attached paper, the three main rivers that contribute flow to the Cape Fear River Estuary (with lowest flow and highest non-hurricane flow values in parenthesis) are the 1. Cape Fear River (14 m^3/s - 600 m^3/s) 2. Northeast Cape Fear River - discharges to Cape Fear River Estuary at Wilmington (0.5 m^3/s to 130 m^3/s) and 3. Black River - meets the Cape Fear River NW of Wilmington (0.5 m^3/s to 130 m^3/s)
There are limited flow gauges available for our study area of interest. The only available stream gauges with discharge are located upstream of the confluence of the three rivers the empty into the Cape Fear River Estuary. Gauge locations are shown in the snip below with numbering corresponding to the previous paragraph. While I have not confirmed, I strongly suspect that our mesh does not extend up to the locations of these stream gauges.

The only other other gauge I can find is the area is the Wilmington NOAA gauge, which only provides water levels, not discharges. Additionally, this gauge misses estuary water level contributions from the Brunswick River (circled in red below).

Hydrodynamic_behavior_of_the_C.pdf

1. Look carefully at Brooke's mesh, maybe by overlaying it on NC9, to understand how she cut down the rivers leading into the sounds.
Brooked cut down the mesh around rivers leading to the NC sounds by retaining only the middle-most elements of the river channel, with vertices on either side of the channel serving as the mainland BCs. She placed an unassigned (presumably some river flux) BC at the farthest upstream edge of the cut down river.

Figure 1. An example of a cut down river channel in NC9brooke.

Figure 2. Original NC9 mesh for the same area shown in the shown in Figure 1. Note the slightly darker line that denotes the channel which Brook cut down for her mesh.

@caseydietrich and @anardek per the 2007 thesis attached above, "The Cape Fear Estuary receives most of its freshwater from the Cape Fear River" (Becker, 2007). I also found the following figures which show freshwater inputs to the Cape Fear River Estuary (CFRE) from 1999-2003 (Figure 2.3) and discharges on four different days 1999-2000 (right hand side of Figure 2.4). Based on the figures below, it seems like discharge from the Cape Fear River is on the order of 2-4 times greater than discharge from the Black River and Northeast Cape Fear River. I suggest we start by modeling just the Cape Fear River boundary condition first, then evaluate whether it is necessary to adjust our boundary flow condition or add BCs for the other rivers.

That seems reasonable to me!
On Mon, Sep 19, 2022 at 4:38 PM Thomas Thelen @.***>
wrote:

@caseydietrich https://github.com/caseydietrich and @anardek
https://github.com/anardek per the 2007 thesis attached above, "The
Cape Fear Estuary receives most of its freshwater from the Cape Fear River"
(Becker, 2007). I also found the following figures which show freshwater
inputs to the Cape Fear River Estuary (CFRE) from 1999-2003 (Figure 2.3)
and discharges on four different days 1999-2000 (right hand side of Figure
2.4). Based on the figures below, it seems like discharge from the Cape
Fear River is on the order of 2-4 times greater than discharge from the
Black River and Northeast Cape Fear River. I suggest we start by modeling
just the Cape Fear River boundary condition first, then evaluate whether it
is necessary to adjust our boundary flow condition or add BCs for the other
rivers.
[image: Image]
https://user-images.githubusercontent.com/89156971/191110819-2f80cf58-b544-4672-88d9-d629d0c8cc9f.png
[image: Image]
https://user-images.githubusercontent.com/89156971/191110893-9b713916-852f-42b3-8c93-1416f7608627.png
—
Reply to this email directly, view it on GitHub
https://github.com/NCSU-CHAZ/Sunny-Day-Flooding/issues/15#issuecomment-1251523665,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANXYL55IYWVGILXS4SQY743V7DFLZANCNFSM6AAAAAAQCS6MPQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


⚠ Bofrost.at has degraded performance

In e05725c, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1133 ms

Resolved: Bofrost.at performance has improved in 781e788 after 6 minutes.


Add Global Redirect to clean up redundant paths

https://www.drupal.org/project/globalredirect
For instance, /taxonomy/term/21 should 301 to /volunteer/healthy-relationships, which is globalredirect's job.

@mshmsh5000 is this still a priority?

I wouldn't want to add this to the redirect logic we've been working on. At least, not a priority. We'll open a fresh issue if SEO considerations ever force us into it.


[Bug]: Document Viewer for PDF base64

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When I read the PDF file from s3 with base64 format, the document view always shows the URL / Base64 is invalid.
Steps To Reproduce

connect to s3
read pdf file with base64
bind function result (fileData) to the document viewer
invalid base64

Public Sample App
No response
Version
self-hosted latest version

Thanks for bringing this to our attention @jinglics, we will triage it soon.

Any update on this issue?

Hey @jdglacier not yet, can you please let me know your usecase?

Hey @dilippitchika, I need to be able to read PDF files from S3 (using the built-in S3 'Read file' command) and display the output base64 in the Document Viewer widget.
These files contain confidential data so public access to the S3 bucket must remain blocked (i.e. I can't just use the file URL in the Document Viewer widget).

@jdglacier you can generate a signed URL for the file with an expiry time and use that to display it in the document viewer

@Nikhil-Nandagopal I haven't read much up on it, but I thought that generating signed URLs required the AWS SDK?

@jdglacier no that is an option in the S3 query under the list files operation

@Nikhil-Nandagopal My mistake, I don't know how I missed that. Thanks!

I am not sure if it's the way I am fetching the URL for the document viewer but it seems to complain about a bad URL despite returning a signed-URL from a JS object's function.

@praneetloke 👋
Do you have a base64 URL?
How did you manage to get the signed URL from the JS Object?
Do you see the evaluated value in the document viewer widget?
Are you using a Async JS function to achieve this?
Can you show us a screenshot of the error you are seeing?

Assuming 50% of doc viewer + s3 users face this challenge
Stats

Stat
Values

Reach
100

Effort (months)
0.75


Enrich Resolver interface to enable rule-based Service Discovery

Is your feature request related to a problem? Please describe.
In some scenarios, it will be convenient for developers to conduct tests if the client-side can do service discovery based on some rules (e.g. tag based). Refer to kitex-contrib(#10) for details.
Describe the solution you'd like
Add one method Filter(ctx context.Context, input Result) (output Result, err error) to Resolver that allows user to configure rules to filter the instances.
Design and implementation will be supplemented later.
Describe alternatives you've considered
NA
Additional context
NA

Please check the new extension in kitex-contrib for this feature. https://github.com/kitex-contrib/resolver-rule-based


audio play toggle on android not working

audio is started with $audio.play, but the toggle effect doesn't work, it won't pause playing audio.

Fixed with https://github.com/Jasonette/JASONETTE-Android/commit/4ab474754cf67b3817af9be6e3b771590495b90b
Please try out and let me know if it works, and I'll close it.

works great thanks.