Avoid use of the term "shebang"

The Mozilla documentation section
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar#The_Hashbang_Grammer

describes Hashbang Grammar. The Mozilla documentation section mostly uses the ECMAScript term 'Hashbang'. However, below the example, the Mozilla documentation section introduces the alternate term 'shebang'.
ECMAScript has chosen 'hashbang'
https://bit.ly/2OPkevy

as its term of choice. Mozilla appears to be wisely aiming to mirror the ECMAScript proposal. In keeping with the ECMAScript terminology, I would not mention 'shebang' in the Mozilla documentation.
I would change the paragraph after the example to
Hashbang comments in JavaScript mimic hashbang comments in Unix.
A hashbang comment in JavaScript specifies the JavaScript interpreter
that should run the script. If you aren't trying to specify a JavaScript
interpreter, steer clear of the #! comment. Use a // comment instead.

The link to the Wikipedia page on shebangs is still a good idea. In my revised paragraph, I would make
hashbang comments in Unix

the text linking to the Wikipedia URL.

@vouser I have given the hashbang page text a copy edit, and incorporated your comments:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar#Hashbang_comments
Let me know if this works for you now.


Missing Files

Your repo is missing a slew of files required to get this up and running. They should be included.

Do you mean the composer dependencies? Those should be downloaded and installed with composer.


Instructions for building Docker image instructions

These instructions allow the 'docker build' command to be run in the project's root directory.
#65

Works for me...

cloned the PR code base into a new project
build the project $ mvn clean package
ran the docker build as follows:

grantf$ docker build -f application/Dockerfile --build-arg JAR_FILE=application-*.jar -t my-org/ehrbase:latest .
Sending build context to Docker daemon  157.7MB
Step 1/6 : FROM openjdk:8-jdk-alpine
 ---> a3562aa0b991
Step 2/6 : ARG JAR_FILE
 ---> Using cache
 ---> b4df4e2be098
Step 3/6 : COPY application/target/${JAR_FILE} app.jar
 ---><PHONE_NUMBER>4e
Step 4/6 : RUN mkdir -p file_repo/knowledge/archetypes &&  mkdir -p file_repo/knowledge/operational_templates && mkdir -p file_repo/knowledge/templates
 ---> Running in 6b92a6e1db27
Removing intermediate container 6b92a6e1db27
 ---> 00d5efd8dbf5
Step 5/6 : EXPOSE 8080
 ---> Running in fcc7a1b5abbd
Removing intermediate container fcc7a1b5abbd
 ---> 5dd7ee8b7bd4
Step 6/6 : ENTRYPOINT ["java","-Dspring.profiles.active=docker","-jar","/app.jar"]
 ---> Running in 3c3c2603adc5
Removing intermediate container 3c3c2603adc5
 ---> 711c05e19c11
Successfully built 711c05e19c11
Successfully tagged my-org/ehrbase:latest

Environment:
MacOS v10.14 (Mojave), Docker  v19.03.5
Looking at the output from the COPY command in your Docker output, perhaps you have different application JARs in the target directory matching  application-*.jar?  COPY seems to have matched multiple source files?


Support for ESP32-S3

since it is already supported in Arduino ESP32 git branch https://github.com/espressif/arduino-esp32/tree/esp32-s3-support
and a official release for will be soon done.

Adding it should be similar to how we added C3 support in #26.
Also looks like upstream already supports it https://github.com/adafruit/Adafruit_WebSerial_ESPTool/tree/main/stubs

@balloob  Thx!
Can you publish to NPM? It seems the github action for did not run


Make it possible to load drone from a suburl

Creating this issue to keep it tracked, already started at https://github.com/drone/drone/pull/1238

let's track as https://github.com/drone/drone/issues/475


[WIP] handle housenumbers that look like postcodes

new libpostal is good at this and doesn't make these mistakes anymore.

libpostal still occasionally gets the number/postcode flipped.  I'm going thru Orange County, CA right now and found the following examples where house number is parsed as postcode:

21161 HILLSDALE HUNTINGTON BEACH CA
24241 PORTO NUOVO DANA POINT CA
24855 CROWN ROYALE LAGUNA NIGUEL CA

It might be a good idea to keep this logic around.

These cases are slightly different in that there aren't both a housenumber and a postalcode, but rather only the housenumber. In this case we can't assume libpostal got it wrong because it may not have. We might actually need to send queries with both and return anything that matches. Most likely sending both will reveal the clear winner.

In the US we might be able to work some magic since each state is allotted a range for postal codes:
https://en.wikipedia.org/wiki/ZIP_Code#/media/File:ZIP_Code_zones.svg
If libpostal returns a state, it wouldn't be hard to determine whether a zip code is likely a house number instead.

add unit tests and acceptance tests and merge

@dianashk please add code comments before merging.

move this over to API now that text-analyzer is no longer being used.

Looks like this is still an issue and the fix should be merged.
21161 HILLSDALE HUNTINGTON BEACH CA
      {
        "controller:libpostal": {
          "parsed_text": {
            "postalcode": "21161",
            "neighbourhood": "hillsdale",
            "city": "huntington beach",
            "state": "ca"
          }
        }
      },


can't optain rabbitmq stats

My "can't optain rabbitmq stats trigger" is not functioning
Zabbix 4.2.1
RabbitMQ 3.7.18
48163:20190920:124552.920 item "<IP_ADDRESS>:rabbitmq.stats[{$ZABBIX_SERVER_IP},{$RABBITMQ_MGMT_ADDRESS},{$RABBITMQ_USER},{$RABBITMQ_PASSWORD},{$RABBITMQ_CA_PATH},{HOST.HOST}]" became not supported: special characters ", ', ", `, *, ?, [, ], {, }, ~, $, !, &, ;, (, ), <, >, |, #, @, 0x0a" are not allowed in the parameters
Any idea whats going wrong ?

and without that, I don't get data, If I run the command manually on the box, I get 1 set of data

set the macro {$ZABBIX_SERVER_IP} manually, and now it works!
I though this was a builtin key from zabbix.
(not mentioned in your instructions)


Installing as Brew Package?

Would you consider offering this (and maybe launchpad) as a brew plugin? I like the " 'tween the easy to bootstrap &  developer springboard" philosophy of these, but all of my macos and debian new machine install scripts use brew now. zinit has a brew package, but feels far too complex.

I’ll do it if someone pays me for it. 😉
Otherwise, please see my answer to the same question over here: https://github.com/marlonrichert/zsh-autocomplete/issues/379#issuecomment-986000768


Denom metadata changes must land in wasm crate

We recently added DenomMetadata to Transactions #2310, but recently the Zpoken team mentioned they don't have access to that info. We suspect we forgot to update the wasm crate to use the new setup. Common mistake: we've been depending on Zpoken to update the WASM ad-hoc, but we should aim to update that crate in tandem with other changes.

Aiming to land this in Testnet 57.

Closed by #2787


🧑💻: UI improvement for Home page

We are not getting anything while clicking on home page.

@sanskritisahu21 go ahead

ok! Thankyou I will join.


Fixes #13 in final form, and adds support for tag 21065

Codecov Report

Merging #16 (7a901ff) into main (da780f0) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #16   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           14        14
  Lines         2181      2202   +21
  Branches       357       358    +1
=========================================
+ Hits          2181      2202   +21

Files Changed
Coverage Δ

src/constants.ts
100.00% <100.00%> (ø)

src/types.ts
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


i get  Permission denied in setup container

Problem description
i get  Permission denied in setup container

Extra information
Stack configuration

Docker setup

$ docker version

Docker version 23.0.1

$ docker-compose version

Docker Compose version 2.17.2

Container logs

$ docker-compose logs

[FATAL tini (7)] exec /entrypoint.sh failed: Permission denied

Closing due to inactivity and missing information.


can not edit job and flow on line

azkaban now can not add job and edit flow on line
like

also we can drag and drop job on flow

i have a idea. when we add job on line,insert project_properties table.
when modify or add flow, Operate project_flows table.


Revert "abb: 1.1.8-0 in 'indigo/distribution.yaml' [bloom]"

Reverts ros/rosdistro#7804
There are no indigo tags again.

@wjwwood @Levi-Armstrong I'm not sure what's going on but every sourcedeb build is failing.

@shaun-edwards  The only times I've seen this have been this and the previous abb indigo release. They're very obvious as they completely swamp the farm until the jobs are manually disabled.
What arguments are you calling bloom with? You can try running bloom without submitting the pull-request and see if the tags are produced. It should say something like: Creating tag: debian/ros-jade-shape-msgs_1.12.2-1_trusty for each debian package during the run, as well as for each rpm. Then will prompt you to push all and push tags.
At that point you can use another terminal to check the prompt Tip: Check to ensure that the debian tags created have the same version as the upstream version you are releasing.
You can find the repo at the top of the logs where it will say something like: Cloning into '/tmp/tmpmcv3bk'...

I forked your repo and tried running it myself, and there are missing dependencies preventing bloom from running on indigo. How did you run bloom?
bloom-release -t indigo -r indigo abb
Specified repository 'abb' is not in the distribution file located at 'https://raw.githubusercontent.com/ros/rosdistro/master/indigo/distribution.yaml'
Could not determine release repository url for repository 'abb' of distro 'indigo'
You can continue the release process by manually specifying the location of the RELEASE repository.
To be clear this is the url of the RELEASE repository not the upstream repository.
For release repositories on GitHub, you should provide the `https://` url which should end in `.git`.
Here is the url for a typical release repository on GitHub: https://github.com/ros-gbp/rviz-release.git
==> Looking for a release of this repository in a different distribution...
A previous distribution, 'hydro', released this repository.
Release repository url [https://github.com/ros-industrial-release/abb-release.git]: https://github.com/tfoote/abb-release.git
==> Fetching 'abb' repository from 'https://github.com/tfoote/abb-release.git'
Cloning into '/tmp/tmpeIAclc'...
remote: Counting objects: 6743, done.
remote: Compressing objects: 100% (123/123), done.
remote: Total 6743 (delta 33), reused 0 (delta 0), pack-reused 6593
Receiving objects: 100% (6743/6743), 5.64 MiB | 4.96 MiB/s, done.
Resolving deltas: 100% (2382/2382), done.
Checking connectivity... done.
==> Setting release repository remote url to 'git@github.com:tfoote/abb-release.git'
==> git remote set-url origin git@github.com:tfoote/abb-release.git
==> Testing for push permission on release repository
==> git remote -v
origin	git@github.com:tfoote/abb-release.git (fetch)
origin	git@github.com:tfoote/abb-release.git (push)
==> git push --dry-run
Everything up-to-date
==> Releasing 'abb' using release track 'indigo'
==> git-bloom-release indigo
Processing release track settings for 'indigo'
Checking upstream devel branch for package.xml(s)
Cloning into '/tmp/tmpqwDXmK/upstream'...
remote: Counting objects: 1619, done.
remote: Compressing objects: 100% (49/49), done.
remote: Total 1619 (delta 27), reused 0 (delta 0), pack-reused 1570
Receiving objects: 100% (1619/1619), 5.49 MiB | 4.78 MiB/s, done.
Resolving deltas: 100% (1017/1017), done.
Checking connectivity... done.
Looking for packages in 'indigo' branch... found 9 packages.
Detected version '1.1.8' from package(s): ['abb_irb5400_support', 'abb', 'abb_driver', 'abb_moveit_plugins', 'abb_irb6640_moveit_config', 'abb_irb2400_moveit_plugins', 'abb_irb6600_support', 'abb_irb2400_support', 'abb_irb2400_moveit_config']

Executing release track 'indigo'
==> bloom-export-upstream /tmp/tmpqwDXmK/upstream git --tag 1.1.8 --display-uri https://github.com/ros-industrial/abb.git --name upstream --output-dir /tmp/tmp3anrW0
Checking out repository at 'https://github.com/ros-industrial/abb.git' to reference '1.1.8'.
Exporting to archive: '/tmp/tmp3anrW0/upstream-1.1.8.tar.gz'
md5: db53144f6b37e3331dedfd80b4dfa539

==> git-bloom-import-upstream /tmp/tmp3anrW0/upstream-1.1.8.tar.gz  --release-version 1.1.8 --replace
The latest upstream tag in the release repository is 'upstream/1.1.8'.
Removing tag: 'upstream/1.1.8'
Importing archive into upstream branch...
Creating tag: 'upstream/1.1.8'
I'm happy.  You should be too.

==> git-bloom-generate -y rosrelease indigo --source upstream -i 1
Releasing packages: ['abb_irb5400_support', 'abb', 'abb_driver', 'abb_moveit_plugins', 'abb_irb6640_moveit_config', 'abb_irb2400_moveit_plugins', 'abb_irb6600_support', 'abb_irb2400_support', 'abb_irb2400_moveit_config']
Releasing package 'abb_irb5400_support' for 'indigo' to: 'release/indigo/abb_irb5400_support'
Releasing package 'abb' for 'indigo' to: 'release/indigo/abb'
Releasing package 'abb_driver' for 'indigo' to: 'release/indigo/abb_driver'
Releasing package 'abb_moveit_plugins' for 'indigo' to: 'release/indigo/abb_moveit_plugins'
Releasing package 'abb_irb6640_moveit_config' for 'indigo' to: 'release/indigo/abb_irb6640_moveit_config'
Releasing package 'abb_irb2400_moveit_plugins' for 'indigo' to: 'release/indigo/abb_irb2400_moveit_plugins'
Releasing package 'abb_irb6600_support' for 'indigo' to: 'release/indigo/abb_irb6600_support'
Releasing package 'abb_irb2400_support' for 'indigo' to: 'release/indigo/abb_irb2400_support'
Releasing package 'abb_irb2400_moveit_config' for 'indigo' to: 'release/indigo/abb_irb2400_moveit_config'

==> git-bloom-generate -y rosdebian --prefix release/indigo indigo -i 1
Generating source debs for the packages: ['abb_irb6600_support', 'abb_irb5400_support', 'abb', 'abb_driver', 'abb_irb2400_support', 'abb_irb2400_moveit_config', 'abb_irb2400_moveit_plugins', 'abb_irb6640_moveit_config', 'abb_moveit_plugins']
Debian Incremental Version: 1
Debian Distributions: ['saucy', 'trusty']
Releasing for rosdistro: indigo

Pre-verifying Debian dependency keys...
Running 'rosdep update'...
Could not resolve rosdep key 'abb_common'
Failed to resolve abb_common on ubuntu:saucy with: Error running generator: Failed to resolve rosdep key 'abb_common', aborting.
abb_common is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'abb_common'
Failed to resolve abb_common on ubuntu:trusty with: Error running generator: Failed to resolve rosdep key 'abb_common', aborting.
abb_common is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_2400_moveit_config'
Failed to resolve irb_2400_moveit_config on ubuntu:saucy with: Error running generator: Failed to resolve rosdep key 'irb_2400_moveit_config', aborting.
irb_2400_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_2400_moveit_config'
Failed to resolve irb_2400_moveit_config on ubuntu:trusty with: Error running generator: Failed to resolve rosdep key 'irb_2400_moveit_config', aborting.
irb_2400_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_6640_moveit_config'
Failed to resolve irb_6640_moveit_config on ubuntu:saucy with: Error running generator: Failed to resolve rosdep key 'irb_6640_moveit_config', aborting.
irb_6640_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_6640_moveit_config'
Failed to resolve irb_6640_moveit_config on ubuntu:trusty with: Error running generator: Failed to resolve rosdep key 'irb_6640_moveit_config', aborting.
irb_6640_moveit_config is depended on by these packages: ['abb']
<== Failed
Some of the dependencies for packages in this repository could not be resolved by rosdep.
You can try to address the issues which appear above and try again if you wish.
Would you like to try again? [Y/n]?
Running 'rosdep update'...
Could not resolve rosdep key 'abb_common'
Failed to resolve abb_common on ubuntu:saucy with: Error running generator: Failed to resolve rosdep key 'abb_common', aborting.
abb_common is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'abb_common'
Failed to resolve abb_common on ubuntu:trusty with: Error running generator: Failed to resolve rosdep key 'abb_common', aborting.
abb_common is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_2400_moveit_config'
Failed to resolve irb_2400_moveit_config on ubuntu:saucy with: Error running generator: Failed to resolve rosdep key 'irb_2400_moveit_config', aborting.
irb_2400_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_2400_moveit_config'
Failed to resolve irb_2400_moveit_config on ubuntu:trusty with: Error running generator: Failed to resolve rosdep key 'irb_2400_moveit_config', aborting.
irb_2400_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_6640_moveit_config'
Failed to resolve irb_6640_moveit_config on ubuntu:saucy with: Error running generator: Failed to resolve rosdep key 'irb_6640_moveit_config', aborting.
irb_6640_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_6640_moveit_config'
Failed to resolve irb_6640_moveit_config on ubuntu:trusty with: Error running generator: Failed to resolve rosdep key 'irb_6640_moveit_config', aborting.
irb_6640_moveit_config is depended on by these packages: ['abb']
<== Failed
Some of the dependencies for packages in this repository could not be resolved by rosdep.
You can try to address the issues which appear above and try again if you wish.
Would you like to try again? [Y/n]? n
User aborted after rosdep keys were not resolved.
<== The following generator action reported that it is missing one or more
    rosdep keys, but that the key exists in other platforms:
'['/usr/bin/git-bloom-generate', '-y', 'rosdebian', '--prefix', 'release/indigo', 'indigo', '-i', '1']'

If you are absolutely sure that this key is unavailable for the platform in
question, the generator can be skipped and you can proceed with the release.
Skip generator action and continue with release [y/N]? y

Action skipped, continuing with release.

==> git-bloom-generate -y rosrpm --prefix release/indigo indigo -i 1
Generating source RPMs for the packages: ['abb_irb6600_support', 'abb_irb5400_support', 'abb', 'abb_driver', 'abb_irb2400_support', 'abb_irb2400_moveit_config', 'abb_irb2400_moveit_plugins', 'abb_irb6640_moveit_config', 'abb_moveit_plugins']
RPM Incremental Version: 1
RPM Distributions: ['21', 'heisenbug']
Releasing for rosdistro: indigo

Pre-verifying RPM dependency keys...
Running 'rosdep update'...
Could not resolve rosdep key 'abb_common'
Failed to resolve abb_common on fedora:21 with: Error running generator: Failed to resolve rosdep key 'abb_common', aborting.
abb_common is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'abb_common'
Failed to resolve abb_common on fedora:heisenbug with: Error running generator: Failed to resolve rosdep key 'abb_common', aborting.
abb_common is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_2400_moveit_config'
Failed to resolve irb_2400_moveit_config on fedora:21 with: Error running generator: Failed to resolve rosdep key 'irb_2400_moveit_config', aborting.
irb_2400_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_2400_moveit_config'
Failed to resolve irb_2400_moveit_config on fedora:heisenbug with: Error running generator: Failed to resolve rosdep key 'irb_2400_moveit_config', aborting.
irb_2400_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_6640_moveit_config'
Failed to resolve irb_6640_moveit_config on fedora:21 with: Error running generator: Failed to resolve rosdep key 'irb_6640_moveit_config', aborting.
irb_6640_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_6640_moveit_config'
Failed to resolve irb_6640_moveit_config on fedora:heisenbug with: Error running generator: Failed to resolve rosdep key 'irb_6640_moveit_config', aborting.
irb_6640_moveit_config is depended on by these packages: ['abb']
<== Failed
Some of the dependencies for packages in this repository could not be resolved by rosdep.
You can try to address the issues which appear above and try again if you wish.
Would you like to try again? [Y/n]? n
User aborted after rosdep keys were not resolved.
<== The following generator action reported that it is missing one or more
    rosdep keys, but that the key exists in other platforms:
'['/usr/bin/git-bloom-generate', '-y', 'rosrpm', '--prefix', 'release/indigo', 'indigo', '-i', '1']'

If you are absolutely sure that this key is unavailable for the platform in
question, the generator can be skipped and you can proceed with the release.
Skip generator action and continue with release [y/N]? y

Action skipped, continuing with release.

Tip: Check to ensure that the debian tags created have the same version as the upstream version you are releasing.
Everything went as expected, you should check that the new tags match your expectations, and then push to the release repo with:
  git push --all && git push --tags  # You might have to add --force to the second command if you are over-writing existing tags
<== Released 'abb' using release track 'indigo' successfully
==> git remote -v
origin	git@github.com:tfoote/abb-release.git (fetch)
origin	git@github.com:tfoote/abb-release.git (push)
Releasing complete, push to release repository?
Continue [Y/n]? n
User answered no to continue prompt, aborting.

If you skip the rosdebian generator it will not generate the debian tags and from there the debians will fail to build.

The full output for bloom-release is below but here is the output for the
tag, it says it was pushed successfully to the release repository.
==> Pushing tags to release repository for 'abb'
==> git push --tags
Username for 'https://github.com': Levi-Armstrong
Password for<EMAIL_ADDRESS>Total 0 (delta 0), reused 0 (delta 0)
To https://github.com/ros-industrial-release/abb-release.git

[new tag]         release/indigo/abb/1.1.8-0 ->
release/indigo/abb/1.1.8-0
[new tag]         release/indigo/abb_driver/1.1.8-0 ->
release/indigo/abb_driver/1.1.8-0
[new tag]         release/indigo/abb_irb2400_moveit_config/1.1.8-0 ->
release/indigo/abb_irb2400_moveit_config/1.1.8-0
[new tag]         release/indigo/abb_irb2400_moveit_plugins/1.1.8-0 ->
release/indigo/abb_irb2400_moveit_plugins/1.1.8-0
[new tag]         release/indigo/abb_irb2400_support/1.1.8-0 ->
release/indigo/abb_irb2400_support/1.1.8-0
[new tag]         release/indigo/abb_irb5400_support/1.1.8-0 ->
release/indigo/abb_irb5400_support/1.1.8-0
[new tag]         release/indigo/abb_irb6600_support/1.1.8-0 ->
release/indigo/abb_irb6600_support/1.1.8-0
[new tag]         release/indigo/abb_irb6640_moveit_config/1.1.8-0 ->
release/indigo/abb_irb6640_moveit_config/1.1.8-0
[new tag]         release/indigo/abb_moveit_plugins/1.1.8-0 ->
release/indigo/abb_moveit_plugins/1.1.8-0
[new tag]         upstream/1.1.8 -> upstream/1.1.8
<== Pushed tags successfully

Here is the output from the bloom-release
larmstrong@lha-vm:~/catkin_ws/src/abb$ bloom-release abb --track indigo
--rosdistro indigo
Specified repository 'abb' is not in the distribution file located at '
https://raw.githubusercontent.com/ros/rosdistro/master/indigo/distribution.yaml
'
Could not determine release repository url for repository 'abb' of distro
'indigo'
You can continue the release process by manually specifying the location of
the RELEASE repository.
To be clear this is the url of the RELEASE repository not the upstream
repository.
For release repositories on GitHub, you should provide the https:// url
which should end in .git.
Here is the url for a typical release repository on GitHub:
https://github.com/ros-gbp/rviz-release.git
==> Looking for a release of this repository in a different distribution...
A previous distribution, 'hydro', released this repository.
Release repository url [
https://github.com/ros-industrial-release/abb-release.git]:
==> Fetching 'abb' repository from '
https://github.com/ros-industrial-release/abb-release.git'
Cloning into '/tmp/tmp0UyIde'...
remote: Counting objects: 6593, done.
remote: Total 6593 (delta 0), reused 0 (delta 0), pack-reused 6593
Receiving objects: 100% (6593/6593), 5.62 MiB | 7.66 MiB/s, done.
Resolving deltas: 100% (2349/2349), done.
Checking connectivity... done.
==> Testing for push permission on release repository
==> git remote -v
origin https://github.com/ros-industrial-release/abb-release.git (fetch)
origin https://github.com/ros-industrial-release/abb-release.git (push)
==> git push --dry-run
warning: push.default is unset; its implicit value is changing in
Git 2.0 from 'matching' to 'simple'. To squelch this message
and maintain the current behavior after the default changes, use:
git config --global push.default matching
To squelch this message and adopt the new behavior now, use:
git config --global push.default simple
When push.default is set to 'matching', git will push local branches
to the remote branches that already exist with the same name.
In Git 2.0, Git will default to the more conservative 'simple'
behavior, which only pushes the current branch to the corresponding
remote branch that 'git pull' uses to update the current branch.
See 'git help config' and search for 'push.default' for further information.
(the 'simple' mode was introduced in Git 1.7.11. Use the similar mode
'current' instead of 'simple' if you sometimes use older versions of Git)
Username for 'https://github.com': Levi-Armstrong
Password for<EMAIL_ADDRESS>Everything up-to-date
==> Releasing 'abb' using release track 'indigo'
==> git-bloom-release indigo
Processing release track settings for 'indigo'
Checking upstream devel branch for package.xml(s)
Cloning into '/tmp/tmpw_0wdP/upstream'...
remote: Counting objects: 1619, done.
remote: Compressing objects: 100% (49/49), done.
remote: Total 1619 (delta 27), reused 0 (delta 0), pack-reused 1570
Receiving objects: 100% (1619/1619), 5.49 MiB | 10.90 MiB/s, done.
Resolving deltas: 100% (1017/1017), done.
Checking connectivity... done.
Looking for packages in 'indigo' branch... found 9 packages.
Detected version '1.1.8' from package(s): ['abb_irb5400_support', 'abb',
'abb_driver', 'abb_moveit_plugins', 'abb_irb6640_moveit_config',
'abb_irb2400_moveit_plugins', 'abb_irb6600_support', 'abb_irb2400_support',
'abb_irb2400_moveit_config']
Executing release track 'indigo'
==> bloom-export-upstream /tmp/tmpw_0wdP/upstream git --tag 1.1.8
--display-uri https://github.com/ros-industrial/abb.git --name upstream
--output-dir /tmp/tmpXeEfHD
Checking out repository at 'https://github.com/ros-industrial/abb.git' to
reference '1.1.8'.
Exporting to archive: '/tmp/tmpXeEfHD/upstream-1.1.8.tar.gz'
md5: 63112005bd7ff39902e4672ac38ca403
==> git-bloom-import-upstream /tmp/tmpXeEfHD/upstream-1.1.8.tar.gz
--release-version 1.1.8 --replace
The latest upstream tag in the release repository is 'upstream/1.1.7'.
Importing archive into upstream branch...
Creating tag: 'upstream/1.1.8'
I'm happy.  You should be too.
==> git-bloom-generate -y rosrelease indigo --source upstream -i 0
Releasing packages: ['abb_irb5400_support', 'abb', 'abb_driver',
'abb_moveit_plugins', 'abb_irb6640_moveit_config',
'abb_irb2400_moveit_plugins', 'abb_irb6600_support', 'abb_irb2400_support',
'abb_irb2400_moveit_config']
Releasing package 'abb_irb5400_support' for 'indigo' to:
'release/indigo/abb_irb5400_support'
Releasing package 'abb' for 'indigo' to: 'release/indigo/abb'
Releasing package 'abb_driver' for 'indigo' to: 'release/indigo/abb_driver'
Releasing package 'abb_moveit_plugins' for 'indigo' to:
'release/indigo/abb_moveit_plugins'
Releasing package 'abb_irb6640_moveit_config' for 'indigo' to:
'release/indigo/abb_irb6640_moveit_config'
Releasing package 'abb_irb2400_moveit_plugins' for 'indigo' to:
'release/indigo/abb_irb2400_moveit_plugins'
Releasing package 'abb_irb6600_support' for 'indigo' to:
'release/indigo/abb_irb6600_support'
Releasing package 'abb_irb2400_support' for 'indigo' to:
'release/indigo/abb_irb2400_support'
Releasing package 'abb_irb2400_moveit_config' for 'indigo' to:
'release/indigo/abb_irb2400_moveit_config'
==> git-bloom-generate -y rosdebian --prefix release/indigo indigo -i 0
Generating source debs for the packages: ['abb_irb6600_support',
'abb_irb5400_support', 'abb', 'abb_driver', 'abb_irb2400_support',
'abb_irb2400_moveit_config', 'abb_irb2400_moveit_plugins',
'abb_irb6640_moveit_config', 'abb_moveit_plugins']
Debian Incremental Version: 0
Debian Distributions: ['saucy', 'trusty']
Releasing for rosdistro: indigo
Pre-verifying Debian dependency keys...
Running 'rosdep update'...
Could not resolve rosdep key 'abb_common'
Failed to resolve abb_common on ubuntu:saucy with: Error running generator:
Failed to resolve rosdep key 'abb_common', aborting.
abb_common is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'abb_common'
Failed to resolve abb_common on ubuntu:trusty with: Error running
generator: Failed to resolve rosdep key 'abb_common', aborting.
abb_common is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_2400_moveit_config'
Failed to resolve irb_2400_moveit_config on ubuntu:saucy with: Error
running generator: Failed to resolve rosdep key 'irb_2400_moveit_config',
aborting.
irb_2400_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_2400_moveit_config'
Failed to resolve irb_2400_moveit_config on ubuntu:trusty with: Error
running generator: Failed to resolve rosdep key 'irb_2400_moveit_config',
aborting.
irb_2400_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_6640_moveit_config'
Failed to resolve irb_6640_moveit_config on ubuntu:saucy with: Error
running generator: Failed to resolve rosdep key 'irb_6640_moveit_config',
aborting.
irb_6640_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_6640_moveit_config'
Failed to resolve irb_6640_moveit_config on ubuntu:trusty with: Error
running generator: Failed to resolve rosdep key 'irb_6640_moveit_config',
aborting.
irb_6640_moveit_config is depended on by these packages: ['abb']
<== Failed
Some of the dependencies for packages in this repository could not be
resolved by rosdep.
You can try to address the issues which appear above and try again if you
wish.
Would you like to try again? [Y/n]? n
User aborted after rosdep keys were not resolved.
<== The following generator action reported that it is missing one or more
rosdep keys, but that the key exists in other platforms:
'['/usr/bin/git-bloom-generate', '-y', 'rosdebian', '--prefix',
'release/indigo', 'indigo', '-i', '0']'
If you are absolutely sure that this key is unavailable for the platform in
question, the generator can be skipped and you can proceed with the release.
Skip generator action and continue with release [y/N]? y
Action skipped, continuing with release.
==> git-bloom-generate -y rosrpm --prefix release/indigo indigo -i 0
Generating source RPMs for the packages: ['abb_irb6600_support',
'abb_irb5400_support', 'abb', 'abb_driver', 'abb_irb2400_support',
'abb_irb2400_moveit_config', 'abb_irb2400_moveit_plugins',
'abb_irb6640_moveit_config', 'abb_moveit_plugins']
RPM Incremental Version: 0
RPM Distributions: ['21', 'heisenbug']
Releasing for rosdistro: indigo
Pre-verifying RPM dependency keys...
Running 'rosdep update'...
Could not resolve rosdep key 'abb_common'
Failed to resolve abb_common on fedora:21 with: Error running generator:
Failed to resolve rosdep key 'abb_common', aborting.
abb_common is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'abb_common'
Failed to resolve abb_common on fedora:heisenbug with: Error running
generator: Failed to resolve rosdep key 'abb_common', aborting.
abb_common is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_2400_moveit_config'
Failed to resolve irb_2400_moveit_config on fedora:21 with: Error running
generator: Failed to resolve rosdep key 'irb_2400_moveit_config', aborting.
irb_2400_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_2400_moveit_config'
Failed to resolve irb_2400_moveit_config on fedora:heisenbug with: Error
running generator: Failed to resolve rosdep key 'irb_2400_moveit_config',
aborting.
irb_2400_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_6640_moveit_config'
Failed to resolve irb_6640_moveit_config on fedora:21 with: Error running
generator: Failed to resolve rosdep key 'irb_6640_moveit_config', aborting.
irb_6640_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_6640_moveit_config'
Failed to resolve irb_6640_moveit_config on fedora:heisenbug with: Error
running generator: Failed to resolve rosdep key 'irb_6640_moveit_config',
aborting.
irb_6640_moveit_config is depended on by these packages: ['abb']
<== Failed
Some of the dependencies for packages in this repository could not be
resolved by rosdep.
You can try to address the issues which appear above and try again if you
wish.
Would you like to try again? [Y/n]? n
User aborted after rosdep keys were not resolved.
<== The following generator action reported that it is missing one or more
rosdep keys, but that the key exists in other platforms:
'['/usr/bin/git-bloom-generate', '-y', 'rosrpm', '--prefix',
'release/indigo', 'indigo', '-i', '0']'
If you are absolutely sure that this key is unavailable for the platform in
question, the generator can be skipped and you can proceed with the release.
Skip generator action and continue with release [y/N]? y
Action skipped, continuing with release.
Tip: Check to ensure that the debian tags created have the same version as
the upstream version you are releasing.
Everything went as expected, you should check that the new tags match your
expectations, and then push to the release repo with:
git push --all && git push --tags  # You might have to add --force to the
second command if you are over-writing existing tags
<== Released 'abb' using release track 'indigo' successfully
==> git remote -v
origin https://github.com/ros-industrial-release/abb-release.git (fetch)
origin https://github.com/ros-industrial-release/abb-release.git (push)
Releasing complete, push to release repository?
Continue [Y/n]? Y
==> Pushing changes to release repository for 'abb'
==> git push --all
Username for 'https://github.com': Levi-Armstrong
Password for<EMAIL_ADDRESS>Counting objects: 169, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (117/117), done.
Writing objects: 100% (144/144), 22.56 KiB | 0 bytes/s, done.
Total 144 (delta 31), reused 0 (delta 0)
To https://github.com/ros-industrial-release/abb-release.git
5d64422..e0327e8  master -> master
4043d2d..3d9d3e6  patches/release/indigo/abb ->
patches/release/indigo/abb
a4ac60c..391cb82  patches/release/indigo/abb_driver ->
patches/release/indigo/abb_driver
b4c8730..71d7a7c  patches/release/indigo/abb_irb2400_moveit_config ->
patches/release/indigo/abb_irb2400_moveit_config
38b3043..ea70cc6  patches/release/indigo/abb_irb2400_moveit_plugins ->
patches/release/indigo/abb_irb2400_moveit_plugins
fa68159..fdb89f9  patches/release/indigo/abb_irb2400_support ->
patches/release/indigo/abb_irb2400_support
e7c5b5d..83d84b2  patches/release/indigo/abb_irb5400_support ->
patches/release/indigo/abb_irb5400_support
2fbcda4..55ccc8c  patches/release/indigo/abb_irb6600_support ->
patches/release/indigo/abb_irb6600_support
d454874..30d7447  patches/release/indigo/abb_irb6640_moveit_config ->
patches/release/indigo/abb_irb6640_moveit_config
1a17fc4..d19a827  patches/release/indigo/abb_moveit_plugins ->
patches/release/indigo/abb_moveit_plugins
2f1c491..35a690f  release/indigo/abb -> release/indigo/abb
1601d5c..c127b19  release/indigo/abb_driver -> release/indigo/abb_driver
25897b5..b25d0d7  release/indigo/abb_irb2400_moveit_config ->
release/indigo/abb_irb2400_moveit_config
7f8b30b..6832151  release/indigo/abb_irb2400_moveit_plugins ->
release/indigo/abb_irb2400_moveit_plugins
07cb35c..f9f4e92  release/indigo/abb_irb2400_support ->
release/indigo/abb_irb2400_support
c75a5cd..1f6c372  release/indigo/abb_irb5400_support ->
release/indigo/abb_irb5400_support
beaa183..6ef6832  release/indigo/abb_irb6600_support ->
release/indigo/abb_irb6600_support
6d2bc44..6d1172d  release/indigo/abb_irb6640_moveit_config ->
release/indigo/abb_irb6640_moveit_config
1029bb7..b0875d4  release/indigo/abb_moveit_plugins ->
release/indigo/abb_moveit_plugins
62e047c..3457f90  upstream -> upstream
<== Pushed changes successfully
==> Pushing tags to release repository for 'abb'
==> git push --tags
Username for 'https://github.com': Levi-Armstrong
Password for<EMAIL_ADDRESS>Total 0 (delta 0), reused 0 (delta 0)
To https://github.com/ros-industrial-release/abb-release.git

[new tag]         release/indigo/abb/1.1.8-0 ->
release/indigo/abb/1.1.8-0
[new tag]         release/indigo/abb_driver/1.1.8-0 ->
release/indigo/abb_driver/1.1.8-0
[new tag]         release/indigo/abb_irb2400_moveit_config/1.1.8-0 ->
release/indigo/abb_irb2400_moveit_config/1.1.8-0
[new tag]         release/indigo/abb_irb2400_moveit_plugins/1.1.8-0 ->
release/indigo/abb_irb2400_moveit_plugins/1.1.8-0
[new tag]         release/indigo/abb_irb2400_support/1.1.8-0 ->
release/indigo/abb_irb2400_support/1.1.8-0
[new tag]         release/indigo/abb_irb5400_support/1.1.8-0 ->
release/indigo/abb_irb5400_support/1.1.8-0
[new tag]         release/indigo/abb_irb6600_support/1.1.8-0 ->
release/indigo/abb_irb6600_support/1.1.8-0
[new tag]         release/indigo/abb_irb6640_moveit_config/1.1.8-0 ->
release/indigo/abb_irb6640_moveit_config/1.1.8-0
[new tag]         release/indigo/abb_moveit_plugins/1.1.8-0 ->
release/indigo/abb_moveit_plugins/1.1.8-0
[new tag]         upstream/1.1.8 -> upstream/1.1.8
<== Pushed tags successfully
==> Generating pull request to distro file located at '
https://raw.githubusercontent.com/ros/rosdistro/master/indigo/distribution.yaml
'
Would you like to add documentation information for this repository? [Y/n]?
Y
==> Looking for a doc entry for this repository in a different
distribution...
Using defaults from the doc entry of distribution 'hydro'.
Please enter your repository information for the doc generation job.
This information should point to the repository from which documentation
should be generated.
VCS Type must be one of git, svn, hg, or bzr.
VCS type [git]:
VCS url [https://github.com/ros-industrial/abb.git]:
VCS version must be a branch, tag, or commit, e.g. master or 0.1.0
VCS version [hydro]: indigo
Would you like to add source information for this repository? [Y/n]? Y
==> Looking for a source entry for this repository in a different
distribution...
Using defaults from the source entry of distribution 'hydro'.
Please enter information which points to the active development branch for
this repository.
This information is used to run continuous integration jobs and for
developers to checkout from.
VCS Type must be one of git, svn, hg, or bzr.
VCS type [git]:
VCS url [https://github.com/ros-industrial/abb.git]:
VCS version must be a branch, tag, or commit, e.g. master or 0.1.0
VCS version [hydro]: indigo
Would you like to add a maintenance status for this repository? [Y/n]? Y
Please enter a maintenance status.
Valid maintenance statuses:

developed: active development is in progress
maintained: no new development, but bug fixes and pull requests are
addressed
end-of-life: should not be used, will disappear at some point
Status: developed
You can also enter a status description.
This is usually reserved for giving a reason when a status is 'end-of-life'.
Status Description [press Enter for no change]:
Unified diff for the ROS distro file located at
'/tmp/tmp8XHW57/abb-1.1.8-0.patch':
--- ../indigo/distribution.yaml
+++ ../indigo/distribution.yaml
@@ -10,6 +10,31 @@

saucy
trusty
repositories:

abb:
doc:

 type: git

 url: https://github.com/ros-industrial/abb.git

 version: indigo

release:

 packages:

 - abb

 - abb_driver

 - abb_irb2400_moveit_config

 - abb_irb2400_moveit_plugins

 - abb_irb2400_support

 - abb_irb5400_support

 - abb_irb6600_support

 - abb_irb6640_moveit_config

 - abb_moveit_plugins

 tags:

   release: release/indigo/{package}/{version}

 url: https://github.com/ros-industrial-release/abb-release.git

 version: 1.1.8-0

source:

 type: git

 url: https://github.com/ros-industrial/abb.git

 version: indigo

status: developed
acado:
doc:
type: git
==> Checking on GitHub for a fork to make the pull request from...
==> Using this fork to make a pull request from: Levi-Armstrong/rosdistro
==> Cloning Levi-Armstrong/rosdistro...
==> mkdir -p rosdistro
==> git init
Initialized empty Git repository in /tmp/BLg3Vg/rosdistro/.git/
Pull Request Title: abb: 1.1.8-0 in 'indigo/distribution.yaml' [bloom]
Pull Request Body :
Increasing version of package(s) in repository abb to 1.1.8-0:

upstream repository: https://github.com/ros-industrial/abb.git
release repository:
https://github.com/ros-industrial-release/abb-release.git
distro file: indigo/distribution.yaml
bloom version: 0.5.19
previous version for package: null

abb
* No changes

abb_driver
* No changes

abb_irb2400_moveit_config
* No changes

abb_irb2400_moveit_plugins
* No changes

abb_irb2400_support
* No changes

abb_irb5400_support
* No changes

abb_irb6600_support
* No changes

abb_irb6640_moveit_config
* No changes

abb_moveit_plugins
* No changes

Open a pull request from 'rosdistro/rosdistro:bloom-abb-3' into
'ros/rosdistro:master'?
Continue [Y/n]? Y
==> git checkout -b bloom-abb-3
Switched to a new branch 'bloom-abb-3'
==> Pulling latest rosdistro branch
remote: Counting objects: 57525, done.
remote: Compressing objects: 100% (49/49), done.
remote: Total 57525 (delta 31), reused 0 (delta 0), pack-reused 57476
Receiving objects: 100% (57525/57525), 15.14 MiB | 7.68 MiB/s, done.
Resolving deltas: 100% (35436/35436), done.
From https://github.com/ros/rosdistro

branch            master     -> FETCH_HEAD
==> Writing new distribution file: indigo/distribution.yaml
==> git add indigo/distribution.yaml
==> git commit -m "abb: 1.1.8-0 in 'indigo/distribution.yaml' [bloom]"
[bloom-abb-3 0d77d69] abb: 1.1.8-0 in 'indigo/distribution.yaml' [bloom]
1 file changed, 25 insertions(+)
==> Pushing changes to fork
Counting objects: 349, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (159/159), done.
Writing objects: 100% (331/331), 89.03 KiB | 0 bytes/s, done.
Total 331 (delta 237), reused 263 (delta 172)
To
<EMAIL_ADDRESS>[new branch]      bloom-abb-3 -> bloom-abb-3
<== Pull request opened at: https://github.com/ros/rosdistro/pull/7804

On Tue, Apr 7, 2015 at 5:54 PM, Tully Foote<EMAIL_ADDRESS>wrote:

I forked your repo and tried running it myself, and there are missing
dependencies preventing bloom from running on indigo. How did you run
bloom?
bloom-release -t indigo -r indigo abb
Specified repository 'abb' is not in the distribution file located at 'https://raw.githubusercontent.com/ros/rosdistro/master/indigo/distribution.yaml'
Could not determine release repository url for repository 'abb' of distro 'indigo'
You can continue the release process by manually specifying the location of the RELEASE repository.
To be clear this is the url of the RELEASE repository not the upstream repository.
For release repositories on GitHub, you should provide the https:// url which should end in .git.
Here is the url for a typical release repository on GitHub: https://github.com/ros-gbp/rviz-release.git
==> Looking for a release of this repository in a different distribution...
A previous distribution, 'hydro', released this repository.
Release repository url [https://github.com/ros-industrial-release/abb-release.git]: https://github.com/tfoote/abb-release.git
==> Fetching 'abb' repository from 'https://github.com/tfoote/abb-release.git'
Cloning into '/tmp/tmpeIAclc'...
remote: Counting objects: 6743, done.
remote: Compressing objects: 100% (123/123), done.
remote: Total 6743 (delta 33), reused 0 (delta 0), pack-reused 6593
Receiving objects: 100% (6743/6743), 5.64 MiB | 4.96 MiB/s, done.
Resolving deltas: 100% (2382/2382), done.
Checking connectivity... done.
==> Setting release repository remote url to 'git@github.com:tfoote/abb-release.git'
==> git remote set-url origin git@github.com:tfoote/abb-release.git
==> Testing for push permission on release repository
==> git remote -v
origin  git@github.com:tfoote/abb-release.git (fetch)
origin  git@github.com:tfoote/abb-release.git (push)
==> git push --dry-run
Everything up-to-date
==> Releasing 'abb' using release track 'indigo'
==> git-bloom-release indigo
Processing release track settings for 'indigo'
Checking upstream devel branch for package.xml(s)
Cloning into '/tmp/tmpqwDXmK/upstream'...
remote: Counting objects: 1619, done.
remote: Compressing objects: 100% (49/49), done.
remote: Total 1619 (delta 27), reused 0 (delta 0), pack-reused 1570
Receiving objects: 100% (1619/1619), 5.49 MiB | 4.78 MiB/s, done.
Resolving deltas: 100% (1017/1017), done.
Checking connectivity... done.
Looking for packages in 'indigo' branch... found 9 packages.
Detected version '1.1.8' from package(s): ['abb_irb5400_support', 'abb', 'abb_driver', 'abb_moveit_plugins', 'abb_irb6640_moveit_config', 'abb_irb2400_moveit_plugins', 'abb_irb6600_support', 'abb_irb2400_support', 'abb_irb2400_moveit_config']
Executing release track 'indigo'
==> bloom-export-upstream /tmp/tmpqwDXmK/upstream git --tag 1.1.8 --display-uri https://github.com/ros-industrial/abb.git --name upstream --output-dir /tmp/tmp3anrW0
Checking out repository at 'https://github.com/ros-industrial/abb.git' to reference '1.1.8'.
Exporting to archive: '/tmp/tmp3anrW0/upstream-1.1.8.tar.gz'
md5: db53144f6b37e3331dedfd80b4dfa539
==> git-bloom-import-upstream /tmp/tmp3anrW0/upstream-1.1.8.tar.gz  --release-version 1.1.8 --replace
The latest upstream tag in the release repository is 'upstream/1.1.8'.
Removing tag: 'upstream/1.1.8'
Importing archive into upstream branch...
Creating tag: 'upstream/1.1.8'
I'm happy.  You should be too.
==> git-bloom-generate -y rosrelease indigo --source upstream -i 1
Releasing packages: ['abb_irb5400_support', 'abb', 'abb_driver', 'abb_moveit_plugins', 'abb_irb6640_moveit_config', 'abb_irb2400_moveit_plugins', 'abb_irb6600_support', 'abb_irb2400_support', 'abb_irb2400_moveit_config']
Releasing package 'abb_irb5400_support' for 'indigo' to: 'release/indigo/abb_irb5400_support'
Releasing package 'abb' for 'indigo' to: 'release/indigo/abb'
Releasing package 'abb_driver' for 'indigo' to: 'release/indigo/abb_driver'
Releasing package 'abb_moveit_plugins' for 'indigo' to: 'release/indigo/abb_moveit_plugins'
Releasing package 'abb_irb6640_moveit_config' for 'indigo' to: 'release/indigo/abb_irb6640_moveit_config'
Releasing package 'abb_irb2400_moveit_plugins' for 'indigo' to: 'release/indigo/abb_irb2400_moveit_plugins'
Releasing package 'abb_irb6600_support' for 'indigo' to: 'release/indigo/abb_irb6600_support'
Releasing package 'abb_irb2400_support' for 'indigo' to: 'release/indigo/abb_irb2400_support'
Releasing package 'abb_irb2400_moveit_config' for 'indigo' to: 'release/indigo/abb_irb2400_moveit_config'
==> git-bloom-generate -y rosdebian --prefix release/indigo indigo -i 1
Generating source debs for the packages: ['abb_irb6600_support', 'abb_irb5400_support', 'abb', 'abb_driver', 'abb_irb2400_support', 'abb_irb2400_moveit_config', 'abb_irb2400_moveit_plugins', 'abb_irb6640_moveit_config', 'abb_moveit_plugins']
Debian Incremental Version: 1
Debian Distributions: ['saucy', 'trusty']
Releasing for rosdistro: indigo
Pre-verifying Debian dependency keys...
Running 'rosdep update'...
Could not resolve rosdep key 'abb_common'
Failed to resolve abb_common on ubuntu:saucy with: Error running generator: Failed to resolve rosdep key 'abb_common', aborting.
abb_common is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'abb_common'
Failed to resolve abb_common on ubuntu:trusty with: Error running generator: Failed to resolve rosdep key 'abb_common', aborting.
abb_common is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_2400_moveit_config'
Failed to resolve irb_2400_moveit_config on ubuntu:saucy with: Error running generator: Failed to resolve rosdep key 'irb_2400_moveit_config', aborting.
irb_2400_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_2400_moveit_config'
Failed to resolve irb_2400_moveit_config on ubuntu:trusty with: Error running generator: Failed to resolve rosdep key 'irb_2400_moveit_config', aborting.
irb_2400_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_6640_moveit_config'
Failed to resolve irb_6640_moveit_config on ubuntu:saucy with: Error running generator: Failed to resolve rosdep key 'irb_6640_moveit_config', aborting.
irb_6640_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_6640_moveit_config'
Failed to resolve irb_6640_moveit_config on ubuntu:trusty with: Error running generator: Failed to resolve rosdep key 'irb_6640_moveit_config', aborting.
irb_6640_moveit_config is depended on by these packages: ['abb']
<== Failed
Some of the dependencies for packages in this repository could not be resolved by rosdep.
You can try to address the issues which appear above and try again if you wish.
Would you like to try again? [Y/n]?
Running 'rosdep update'...
Could not resolve rosdep key 'abb_common'
Failed to resolve abb_common on ubuntu:saucy with: Error running generator: Failed to resolve rosdep key 'abb_common', aborting.
abb_common is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'abb_common'
Failed to resolve abb_common on ubuntu:trusty with: Error running generator: Failed to resolve rosdep key 'abb_common', aborting.
abb_common is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_2400_moveit_config'
Failed to resolve irb_2400_moveit_config on ubuntu:saucy with: Error running generator: Failed to resolve rosdep key 'irb_2400_moveit_config', aborting.
irb_2400_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_2400_moveit_config'
Failed to resolve irb_2400_moveit_config on ubuntu:trusty with: Error running generator: Failed to resolve rosdep key 'irb_2400_moveit_config', aborting.
irb_2400_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_6640_moveit_config'
Failed to resolve irb_6640_moveit_config on ubuntu:saucy with: Error running generator: Failed to resolve rosdep key 'irb_6640_moveit_config', aborting.
irb_6640_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_6640_moveit_config'
Failed to resolve irb_6640_moveit_config on ubuntu:trusty with: Error running generator: Failed to resolve rosdep key 'irb_6640_moveit_config', aborting.
irb_6640_moveit_config is depended on by these packages: ['abb']
<== Failed
Some of the dependencies for packages in this repository could not be resolved by rosdep.
You can try to address the issues which appear above and try again if you wish.
Would you like to try again? [Y/n]? n
User aborted after rosdep keys were not resolved.
<== The following generator action reported that it is missing one or more
rosdep keys, but that the key exists in other platforms:
'['/usr/bin/git-bloom-generate', '-y', 'rosdebian', '--prefix', 'release/indigo', 'indigo', '-i', '1']'
If you are absolutely sure that this key is unavailable for the platform in
question, the generator can be skipped and you can proceed with the release.
Skip generator action and continue with release [y/N]? y
Action skipped, continuing with release.
==> git-bloom-generate -y rosrpm --prefix release/indigo indigo -i 1
Generating source RPMs for the packages: ['abb_irb6600_support', 'abb_irb5400_support', 'abb', 'abb_driver', 'abb_irb2400_support', 'abb_irb2400_moveit_config', 'abb_irb2400_moveit_plugins', 'abb_irb6640_moveit_config', 'abb_moveit_plugins']
RPM Incremental Version: 1
RPM Distributions: ['21', 'heisenbug']
Releasing for rosdistro: indigo
Pre-verifying RPM dependency keys...
Running 'rosdep update'...
Could not resolve rosdep key 'abb_common'
Failed to resolve abb_common on fedora:21 with: Error running generator: Failed to resolve rosdep key 'abb_common', aborting.
abb_common is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'abb_common'
Failed to resolve abb_common on fedora:heisenbug with: Error running generator: Failed to resolve rosdep key 'abb_common', aborting.
abb_common is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_2400_moveit_config'
Failed to resolve irb_2400_moveit_config on fedora:21 with: Error running generator: Failed to resolve rosdep key 'irb_2400_moveit_config', aborting.
irb_2400_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_2400_moveit_config'
Failed to resolve irb_2400_moveit_config on fedora:heisenbug with: Error running generator: Failed to resolve rosdep key 'irb_2400_moveit_config', aborting.
irb_2400_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_6640_moveit_config'
Failed to resolve irb_6640_moveit_config on fedora:21 with: Error running generator: Failed to resolve rosdep key 'irb_6640_moveit_config', aborting.
irb_6640_moveit_config is depended on by these packages: ['abb']
<== Failed
Could not resolve rosdep key 'irb_6640_moveit_config'
Failed to resolve irb_6640_moveit_config on fedora:heisenbug with: Error running generator: Failed to resolve rosdep key 'irb_6640_moveit_config', aborting.
irb_6640_moveit_config is depended on by these packages: ['abb']
<== Failed
Some of the dependencies for packages in this repository could not be resolved by rosdep.
You can try to address the issues which appear above and try again if you wish.
Would you like to try again? [Y/n]? n
User aborted after rosdep keys were not resolved.
<== The following generator action reported that it is missing one or more
rosdep keys, but that the key exists in other platforms:
'['/usr/bin/git-bloom-generate', '-y', 'rosrpm', '--prefix', 'release/indigo', 'indigo', '-i', '1']'
If you are absolutely sure that this key is unavailable for the platform in
question, the generator can be skipped and you can proceed with the release.
Skip generator action and continue with release [y/N]? y
Action skipped, continuing with release.
Tip: Check to ensure that the debian tags created have the same version as the upstream version you are releasing.
Everything went as expected, you should check that the new tags match your expectations, and then push to the release repo with:
git push --all && git push --tags  # You might have to add --force to the second command if you are over-writing existing tags
<== Released 'abb' using release track 'indigo' successfully
==> git remote -v
origin  git@github.com:tfoote/abb-release.git (fetch)
origin  git@github.com:tfoote/abb-release.git (push)
Releasing complete, push to release repository?
Continue [Y/n]? n
User answered no to continue prompt, aborting.
If you skip the rosdebian generator it will not generate the debian tags
and from there the debians will fail to build.
—
Reply to this email directly or view it on GitHub
https://github.com/ros/rosdistro/pull/7840#issuecomment-90752997.

--
Levi Armstrong

Yes, it pushed the tags it generated successfully. However you told it earlier to skip running the ros debian generator which means there are no debian tags. And thus the debian packages cannot be built.
If you are absolutely sure that this key is unavailable for the platform in
question, the generator can be skipped and you can proceed with the release.
Skip generator action and continue with release [y/N]? y

This defaults to No for a reason. If you answer yes here it disables the debian generator and no debian tags get generated. You cannot make a successful release skipping the generators.
Yes bloom lets you continue because there are use cases where you might not want to generate debian packages. Such as our collaborators generating Fedora packages in a custom repo. But that is not what you want to do.
You need to fix your dependency issues then bloom will run fine.


Exception thrown when trying to check if index exists

NEST/Elasticsearch.Net version:
7.13.0
Elasticsearch version:
7.13.1
Description of the problem including expected versus actual behavior:
We have 3 clusters. 2 in Elastic Cloud and one running locally in docker. When trying to determine if an index exists, using ExistsAsync(), we get a BadResponse:
# FailureReason: BadResponse while attempting HEAD on https://elastic:SdHPdB7XrHnNh4hMZNZAdpoa@8a4d49ea484146418345bf750e01b415.eu-west-1.aws.found.io:9243/_alias/indexer_rigel_pickuppoints_coolrunnerdaohome-alias?pretty=true&error_trace=true
# Audit trail of this API call:
 - [1] BadResponse: Node: https://elastic:redacted@8a4d49ea484146418345bf750e01b415.eu-west-1.aws.found.io:9243/ Took: 00:00:00.0782374
# OriginalException: Elasticsearch.Net.ElasticsearchClientException: Request failed to execute. Call: Status code 200 from: HEAD /_alias/indexer_rigel_pickuppoints_coolrunnerdaohome-alias?pretty=true&error_trace=true
   at Elasticsearch.Net.Transport`1.HandleElasticsearchClientException(RequestData data, Exception clientException, IElasticsearchResponse response)
   at Elasticsearch.Net.Transport`1.FinalizeResponse[TResponse](RequestData requestData, IRequestPipeline pipeline, List`1 seenExceptions, TResponse response)
   at Elasticsearch.Net.Transport`1.RequestAsync[TResponse](HttpMethod method, String path, CancellationToken cancellationToken, PostData data, IRequestParameters requestParameters)
   at Reshopper.BusinessLogic.Infrastructure.Elasticsearch.ElasticsearchHelper.<>c__DisplayClass5_0.<<GetWhichIndexNamesAliasPointsToAsync>b__0>d.MoveNext() in C:\Source\Reshopper\backend\src\Reshopper.BusinessLogic\Infrastructure\Elasticsearch\ElasticsearchHelper.cs:line 74
# Request:
<Request stream not captured or already read to completion by serializer. Set DisableDirectStreaming() on ConnectionSettings to force it to be set on the response.>
# Response:

# TCP states:
  Established: 163
  TimeWait: 11
  CloseWait: 2

# ThreadPool statistics:
  Worker:
    Busy: 2
    Free: 32765
    Min: 8
    Max: 32767
  IOCP:
    Busy: 1
    Free: 999
    Min: 8
    Max: 1000

# Exception:
Elasticsearch.Net.ElasticsearchClientException: Request failed to execute. Call: Status code 200 from: HEAD /_alias/indexer_rigel_pickuppoints_coolrunnerdaohome-alias?pretty=true&error_trace=true
   at Elasticsearch.Net.Transport`1.HandleElasticsearchClientException(RequestData data, Exception clientException, IElasticsearchResponse response)
   at Elasticsearch.Net.Transport`1.FinalizeResponse[TResponse](RequestData requestData, IRequestPipeline pipeline, List`1 seenExceptions, TResponse response)
   at Elasticsearch.Net.Transport`1.RequestAsync[TResponse](HttpMethod method, String path, CancellationToken cancellationToken, PostData data, IRequestParameters requestParameters)
   at Reshopper.BusinessLogic.Infrastructure.Elasticsearch.ElasticsearchHelper.<>c__DisplayClass5_0.<<GetWhichIndexNamesAliasPointsToAsync>b__0>d.MoveNext() in C:\Source\Reshopper\backend\src\Reshopper.BusinessLogic\Infrastructure\Elasticsearch\ElasticsearchHelper.cs:line 74

We have also tried with a missing index and get a 404 as expected, but it still throws the exception and the "Exists" property is not present on the exception.
This only happens on one of the cloud clusters, the other 2 clusters works as expected with the "Exists" property available even when a 404 is returned.
When doing the exact same calls using postman, it returns the status codes as it should.
It seems one of our clusters triggers something in the client which makes it throw an exception instead of handling the 404 and 200 the expected way.
The same thing happens when trying to check if an alias exists using AliasExistsAsync(). Exact same behavior
Steps to reproduce:
No clue, Only happens on one cluster out of 3.
Expected behavior
No exceptions throw and the possibility to check the exists variable in the answer from the cluster, instead of a thrown exception.

Hi, @oliv0533. Thanks for reporting this. I have reproduced the issue and I'm looking at a client-side fix around response validation. Could you also please let me know which cloud provider and region both cloud deployments are in and which one succeeds and which fails?

@oliv0533 - We isolated this to a change in 7.13.0 which affects these requests against Elastic Cloud deployments. I have released 7.13.1 which includes a fix for this issue from #5735.

@stevejgordon  Thanks for the swift action.


Filter backtrace originating from evm_spec_helper

EvmSpecHelper.clear_caches yields to a block in which an example is
run. Should that example fail the backtrace reported by RSpec will
include the appropriate line in spec/support/evm_spec_helper, and the
line in spec/spec_helper from which it is called twice. This adds some
noise to the backtrace, making it harder to read. Adding these files to
RSpec's backtrace exclusion patterns alleviates the problem.
Before:
     1.2) Failure/Error: expect(response).to have_http_status(:ok)
            expected the response to have status code :ok (200) but it was :internal_server_error (500)
          # ./spec/requests/api/blueprints_spec.rb:39:in `block (3 levels) in <top (required)>'
          # ./spec/spec_helper.rb:105:in `block (3 levels) in <top (required)>'
          # ./spec/support/evm_spec_helper.rb:28:in `clear_caches'
          # ./spec/spec_helper.rb:105:in `block (2 levels) in <top (required)>'

After:
     1.2) Failure/Error: expect(response).to have_http_status(:ok)
            expected the response to have status code :ok (200) but it was :internal_server_error (500)
          # ./spec/requests/api/blueprints_spec.rb:39:in `block (3 levels) in <top (required)>'

@miq-bot add-label test
@miq-bot assign @Fryguy
/cc @jrafanie

Do we ever want to see failures with these files in the backtrace?  Currently, we don't have any expects in them but there are a few allows here.  I'm good with this until it's a problem.

@jrafanie yeah, I'd prefer not to do this, but think the benefit outweighs the cost of some possible obscurity there


Clarify preStop hooks in Termination of Pods

Update docs to note containers instead of pods (and containers stopping independent of one another).

I signed it

I signed it

/lgtm

@cody-clark do you mind taking a look?

Absolutely! This looks great, @bpownow; thanks!
/approve


Classes returning new instance

Hi,
I came by this repo on the LaTeX subreddit. I have fumbled a lot with 3D tikz in the past as well, with some success here and there, but mostly headaches.
Combining LaTeX and Python is great. I know my way around the former, but am not super knowledgeable in Python, so bear that in mind.
One of the things I noticed was that class methods return a new instance of their own class, e.g.
class Vector3:
    def __init__(self, x, y, z):
        self.x = x
        self.y = y
        self.z = z

    def scale(a, s):
        return Vector3(a.x * s, a.y * s, a.z * s)

These methods should probably return the class itself (hint, hint), not a wholly new instance, which quickly gets out of hand.
See for example:
class Vector3:
    def __init__(self, x, y, z):
        self.x = x
        self.y = y
        self.z = z

    def scale(a, s):
        return Vector3(a.x * s, a.y * s, a.z * s)

    def scale_self(self, s):
        self.x *= s
        self.y *= s
        self.z *= s
        return self

The behaviour is now:
 ~/3dpp/master/python$
Python 3.8.1 (default, Jan 22 2020, 06:38:00)
[GCC 9.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from lib.geometry import Vector3
>>> x = Vector3(1, 2, 3)
>>> x
(1, 2, 3)
>>> y = x.scale(2)
>>> y
(2, 4, 6)
>>> x is y
False
>>> z = x.scale_self(2)
>>> z
(2, 4, 6)
>>> z is x
True
>>> zz = x.scale_self(2).scale_self(2)
>>> zz
(8, 16, 24)

So the methods can now be chained, but more importantly, no new object is retained. A vector should stay the same vector (object). This can be checked with id() or as above, is.
I haven't even tried your software yet, I hope to do so soon and maybe get to do a full pull request.

Hi,
First of all, thanks so much for taking an interest.
As for your issue, I'm refraining from mutating the vector objects because I want to reuse them.
This is especially useful when declaring operators between vectors. Take for example this:
>>> u = Vector3(1, 1, 1)
>>> v = Vector3(1, 0, 2)
>>> w = Vector3(2, 1, 1)
>>> q = (u - v) ^ (u + w) # '^' is the cross product operator

Since I'm using u twice, mutating it would just make the expression impossible. Moreover, I would lose the value of u for later computations.
Granted, I could make copies of it, but it would just obscure the logic.
The sacrifice in performance/memory is so negligible, that the gain in conciseness and cleaner code is much more significant.
In theory I could have written it in C and use static allocations for everything, but I'm not writing a game, it's just a tools that supposed to be useful and extensible :)

Okay, cool! Thanks for the insight.
Of course, the impact is absolutely not noticeable here, I was more worried about style.


update to work with latest master

Changes

Replaced MacExpr(depreciated) with MacEager
Updated to use isize/usize instead of int/uint
Fixed checking if literal is valid

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

Thanks!


rewrite tests to use intern

fixes #489...sorta
I changed the testing to use intern's QUnit's interface. It will still need to have a browserstack API (tested locally with mine, and it works).
For this to be actually useful, something akin to https://github.com/twbs/savage would need to be added for PRs. In addition, for the actual ask of #489 to be fulfilled, some kind of box that auto downloads the latest versions of browsers and runs this against them. Travis wouldn't work well for this, since its essentially linux only (there is os x support, but its invite only and really only meant for iphone apps). AppVeyor could work, since it runs on windows, but it would be an fairly non standard env. So a mac mini or custom windows hosting somewhere where chrome canary, firefox nightly, webkit nightly, and edge could be installed would probably be best (imo, at least).

@patrickkettner
Thx for your work. I had no time yet to go through, but picturefill has the need to be a named module (https://github.com/patrickkettner/picturefill/commit/8f5782ec06c725f93d4ca396621d5dc0e0068575#diff-e3cc12fee32d40e95863f7b6bee3e282L1419). We can't change this. Is there another way to integrate intern tests with picturefill as a named amd module?

Hiya!
There are other ways to get it to work, using an explicit name is sort of a
requirejs antipattern (
https://github.com/jrburke/requirejs/wiki/Updating-existing-libraries#anon),
so I removed it.
I believe adding an empty dependency array to to and signature will make it
work with a name, though
On Fri, Jul 24, 2015, 4:05 AM Alexander Farkas<EMAIL_ADDRESS>wrote:

@patrickkettner https://github.com/patrickkettner
Thx for your work. I had no time yet to go through, but picturefill has
the need to be a named module (patrickkettner@8f5782e
#diff-e3cc12fee32d40e95863f7b6bee3e282L1419
https://github.com/patrickkettner/picturefill/commit/8f5782ec06c725f93d4ca396621d5dc0e0068575#diff-e3cc12fee32d40e95863f7b6bee3e282L1419).
We can't change this. Is there another way to integrate intern tests with
picturefill as a named amd module?
—
Reply to this email directly or view it on GitHub
https://github.com/scottjehl/picturefill/pull/555#issuecomment-124415996
.

@patrickkettner

using an explicit name is sort of a requirejs antipattern

We are aware of this. But we recommend to add picturefill async in the head, often separated from the rest of the JS (similar to Modernizr). This can produce errors, if requireJS is in the page and the module is unnamed.
I already checked today more of your work and found some errors and there are still some open questions. But I need to clarify some parts and need to play around first. I would suggest, that I'm trying to fix those in your forked branch so we can then pull everything in at once, if and as soon as the picturefill team decides to do so.
Will start with this at Sunday/Monday.

I would suggest, that I'm trying to fix those in your forked branch... Will start with this at Sunday/Monday

I can work on any issue today and saturday, so any issue you can mention before then would be appreciated.

In general: I have added a new index.html into the tests director:
<!DOCTYPE html>
<title>Wait a minute, I'll redirect you</title>
<meta http-equiv="refresh" content="0; url=../node_modules/intern/client.html?config=tests/intern&reporters=Html&reporters=Console">

Open this in current Safari
Here are things I saw (not everything an issue)

making it worked with named module
picture has to be created first: https://github.com/patrickkettner/picturefill/blob/new_tests/tests/tests.js#L117-L122
I think we should keep qunit for tests-functional.html (https://github.com/patrickkettner/picturefill/commit/8f5782ec06c725f93d4ca396621d5dc0e0068575#diff-595bf3fa2348192244b0319be33066b8L62 https://github.com/patrickkettner/picturefill/commit/8f5782ec06c725f93d4ca396621d5dc0e0068575#diff-b9cfc7f2cdf78a7f4b91a753d10865a2L34).
I don't understand why removing this: https://github.com/patrickkettner/picturefill/commit/8f5782ec06c725f93d4ca396621d5dc0e0068575#diff-2a8a5fef3397df87ab538f028a5c6b50L68 works.

Sorry for being soo short. I have no time. Thank you!!! Really great.

I think we should keep qunit for tests-functional.html

Any reason you don't want to use intern for functional tests as well?

@aFarkas I believe I updated all of your concerns


Make inc/dec take an int

Also add doc comments for succ/pred. Supersedes #79.

You should add tests for a.inc(int32.high+1), a.inc(int64.high), and same for dec and int64.low, int32.low-1.

@dlesnoff done.
The CI failure is caused by #88 (unrelated to this PR). See #89 for a (temporary) fix.


[UI] Refreshing on Connections page causes Adapter connection prompt

Current Behavior
While on http://localhost:9081/management/connections, when the page is refreshed, this happens:
https://github.com/meshery/meshery/assets/7570704/a5f2ba3e-63d6-48cd-8f17-e5a346ade96a

Contributor Guides and Handbook

🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🖥 Contributing to Meshery UI
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

@senali-d @aabidsofi19 routing issue..

would like to work on this. Please assign it to me.

This issue has been resolved @LakshyaSatpal , lets get you some issues


ui: Add table dividers

And add some  hyphens while we're here.

There is https://django-softhyphen.readthedocs.io/en/latest/, but that says

(Warning! Because of its overhead, the filter is not recommended in production if it needs to run each time the page loads.)

how badly do you need those hyphens at the moment. Could you back out that part of the change for now and we can investigate just how bad the performance overhead of django-softhyphen really is?

I'll take them out. They do make the layout on narrower screens break, since the table flows past the leftmenu, but that is minor.

Note that https://github.com/datadesk/django-softhyphen is archived and hasn't seen a commit in seven years...

Thanks.
If we can't find a library someone else is supporting I would rather set up our own dict in utils for the words we want to soft-hyphenate and a template filter that would transform words using that dict than to manually, explicitly, soft-hyphenate each word each time it occurs. The latter raises the readability concern I already pointed to, and would likely lead to things like making programs scanning for spelling errors literals break.


Vertical line check sometimes randomly equal to horizontal line check.

This is probably a control structure discrepancy.

Resolved.


Disable portal nexus swap when holding shift modifier

Add shift modifier to the portal nexus to disable the swap

I'm not a fan of this, as I'd expect that if this new behavior was added to handle Shift being pressed, I would also expect the reverse behavior to work. (config disabled with shift pressed would swap "Teleport menu" to left-click) At the very least, I would expect this to be explained in the config description, but even that would not make this behavior obvious.


New check: Overlapping components that don't have to be

I heard about an issue with the Google Sans tt ligature glyph rendering on Android, where there is an expected perfect pixel alignment of the crossbar, and yet it doesn't render that way:

Looking at the roman TTFs in https://www.axis-praxis.org/samsa/ I see:

The crossbar of the ligature is made of 2 overlapping components, and this creates some double-printing fringe effect, somehow.
Yet, since it is possible to 'transform' components, I propose removing one rectangle and stretching the other to have the same area and position as the previous combination. This should produce zero change in ink in most scenarios, and remove the fringe.
And that situation seems like something it should be possible to write a generic checker for - where components overlap and where a single component could do instead :) @simoncozens do you see a straightforward way to do this? :)

I think this isn't going to happen. In this case, the crossbars are not made up of two overlapping components - the two crossbars are made up of different contours from each of two different component glyphs. And so it would not be possible to stretch either component to make a long crossbar, without distorting the t forms.
And even if it were possible, in general, searching through all the components to find a transformation matrix of one which creates the same visual appearance of two components overlapped would be... well, it would be easier to fix the rasteriser.


SELECT DISTINCT and ORDER BY not working

Hi good day.
I have the following problem using the following statement alasql
var sql = 'select DISTINCT FROM Period? ORDER BY ASC RequestDate '
var res = alasql (sql, [result]);
With version 0.3 (used in the example), it does not work correctly the DISTINCT, but if the ORDER BY.
With version 0.2.1 (which I use in my project, it works well but not the DISTINCT ORDER BY.
There is a report on DISTINCT malfunction in version 3.
Thank you so much.
NOTE: The sample data are online
<!DOCTYPE html>

    Query result:

Sorry, the correct query is:
var sql = 'select DISTINCT Period FROM  ? ORDER BY ASC RequestDate '
var res = alasql (sql, [result]);

Hi @cbugari - Sorry long response time.
Thank you so much for a very well described bug.
Its really terrible we have introduced an error - but even worse that our regression tests did not include this scenario.
Small questions - if we have data corresponding to
{
		"RequestDate": "2015-09-17",
		"Period": "Sep-15"
	},
	{
		"RequestDate": "2015-09-18",
		"Period": "Sep-15"
	},
	{
		"RequestDate": "2015-09-17",
		"Period": "Jul-16"
	},
	{
		"RequestDate": "2015-09-18",
		"Period": "Jul-16"
	}

will you the expect jul-16 or sep-16 to come first?
This is really


How to get 2D NavMesh(Occupancy Grid)

Hello,
I have quick question. How to get the map in below on ROS side? Did you use camera view or direclty get from UNity and use other ROS tool to visualise like this?

Thanks

Hey, could you successfuly implement this git?
My map is loading, but still some errors


Remove default finger image for notes in PDF

I think this is ready to go, unless there are concerns?
FWIW I considered doing this as an option, but this is one place where (from what I've heard anyway) nobody likes the current behavior. So it seems like adding an option "Turn on the finger image", which is off by default, might be overkill. We could go that way though if anybody prefers?

Since an image to signal or augment notes is by no means absolutely correct or only way, I see no reason to add a toggle. If someone wants to add the old finger image, it's pretty easy to do it.
The finger images themselves could be removed in 3.0.


Fastest, but with memory leaks.

While benchmarking using leapfrog, I found that its performance is indeed the fastest among a dozen third-party libraries. However, due to the repetitive nature of the tests, I noticed some implementations suffer from memory leaks. Unfortunately, leapfrog::LeapMap is also one of them, exhibiting leaks on both Windows 10 and Ubuntu 24.04. To verify this leakage, I crafted a dedicated test program. Here's my code:
cargo.toml:
[dependencies]
leapfrog = "0.3.0"
sysinfo = "0.30.13"

main.rs:
use sysinfo::{ System, Pid };

fn main() {
    println!("Process ID: {}", std::process::id());
    let pid = Pid::from_u32(std::process::id() as u32);

    let get_memory_usage = |pid| {
        let system_info = System::new_all();
        let current_process = system_info.process(pid).expect("Process not found");
        current_process.memory()
    };
    println!("Initial memory usage: {} bytes", get_memory_usage(pid));

    const NUM_ROUNDS: usize = 10;
    const INSERTIONS_PER_ROUND: usize = 10_000_000;

    let start_time = std::time::Instant::now();
    for round in 1..=NUM_ROUNDS {
        let map = leapfrog::LeapMap::new();
        for index in 0..INSERTIONS_PER_ROUND {
            map.insert(index, index);
        }
        let memory_before_drop = get_memory_usage(pid);
        drop(map); // Explicitly drop to free resources.
        let memory_after_drop = get_memory_usage(pid);
        let elapsed_time = start_time.elapsed();
        println!(
            "Round: {round}, Time elapsed: {:?}, Memory before drop: {} bytes, after drop: {} bytes",
            elapsed_time, memory_before_drop, memory_after_drop
        );
    }
}

The test output is as follows:
Initial memory usage: 11919360 bytes
Round: 1, Time elapsed: 1.8845246s, Memory before drop: 886329344 bytes, after drop: 232243200 bytes
Round: 2, Time elapsed: 3.826265s, Memory before drop:<PHONE_NUMBER> bytes, after drop: 450646016 bytes
Round: 3, Time elapsed: 5.6983455s, Memory before drop:<PHONE_NUMBER> bytes, after drop: 669356032 bytes
Round: 4, Time elapsed: 7.5641729s, Memory before drop:<PHONE_NUMBER> bytes, after drop: 887300096 bytes
Round: 5, Time elapsed: 9.4544339s, Memory before drop:<PHONE_NUMBER> bytes, after drop:<PHONE_NUMBER> bytes
Round: 6, Time elapsed: 11.3552829s, Memory before drop:<PHONE_NUMBER> bytes, after drop:<PHONE_NUMBER> bytes
Round: 7, Time elapsed: 13.2239042s, Memory before drop:<PHONE_NUMBER> bytes, after drop:<PHONE_NUMBER> bytes
Round: 8, Time elapsed: 15.0954465s, Memory before drop:<PHONE_NUMBER> bytes, after drop:<PHONE_NUMBER> bytes
Round: 9, Time elapsed: 16.9596344s, Memory before drop:<PHONE_NUMBER> bytes, after drop:<PHONE_NUMBER> bytes
Round: 10, Time elapsed: 18.8209026s, Memory before drop:<PHONE_NUMBER> bytes, after drop:<PHONE_NUMBER> bytes

Under Windows 10 (rust 1.81.0-nightly), by increasing the number of creation-deletion cycles, my system memory can be filled up in just a few minutes.

Hey,
Thank you for this, it is definitely something that I need to loop into. I will try and reproduce and fix as soon as I get a chance.


Informs when Side Menu start presenting menu and end presenting menu

Hi, do you think it is possible to add in a delegate, to inform the view controllers about when it will start presenting the side menu, and also when the side menu has been completely presented? Same goes to when closing the side menu. It would be help if that's added. Many thanks.

Do you have a specific scenario that cannot be solved by the standard
present/dismiss view controller calls? Since this control uses custom
transitions it does not have any special calls for display and dismiss,
therefor you can use the normal system calls.
On Sat, Apr 30, 2016 at 2:05 AM MunFai<EMAIL_ADDRESS>wrote:

Hi, do you think it is possible to add in a delegate, to inform the view
controllers about when it will start presenting the side menu, and also
when the side menu has been completely presented? Same goes to when closing
the side menu. It would be help if that's added. Many thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/jonkykong/SideMenu/issues/23

I was wondering, when the side menu has been presented, then now when I would like to dismiss the side menu, via a pan gesture towards to the left, or simply tap on the origin view's area, would my view controller be informed on the events? Since the pan and tap are handled by Side Menu.

@munfai I'm still not understand the scenario of why you would need to do that. You may be able to accomplish this by overriding viewWillAppear, viewDidAppear, viewWillDisappear, and viewDidDisappear in the view controller you use as your menu. That won't give you dynamic progress of how much the transition has appeared, but will let you know start and end.
I also encourage people to contribute to this control. If you create a pull request, I can take your changes to the library to support this.


[shardformer]import transformers implicitly

As Hugging Face Transformers is not our dependency, we should not import from transformers at the top of our files. We should only import them inside the function when needed.

Fixed by #4101


Round Robin

Hi, this page is showing Round Robin style for the distribution method but we cannot find this method anywhere in our Call Queue configuration.  Is this feature coming soon or is it already there?  Thank you!

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

ID: b755d9ae-13ac-019f-f5f4-a95b1eee2989
Version Independent ID: f7afd8ad-e6e0-6c79-aed1-4ee87d48ba12
Content: Create a call queue
Content Source: Teams/create-a-phone-system-call-queue.md
Service: msteams
GitHub Login: @jambirk
Microsoft Alias: jambirk

@waseemhashem  can you comment here? I thought that was already at GA.

I did look at a Production build and they are available. @waseemhashem - we will need to look further into this and why his organization doesn't see the options.

Its coming our with the service update we are rolling out, we started the roll out couple of days ago, we expect it to be available to all customers in 2 weeks

Thank you very much!!  We will look for it soon! :)

@officedocsbot assign @scanum

In both of our customer's tenants we cannot see Microsoft Teams admin center, Voice > Call queues, the only options are Direct routing and Call park, but nothing about voice or phone number, still waiting for this featuer.

@waseemhashem - any updates? Thanks.

The roll-out is still going, we came across couple of issues and paused the expansion for couple of days but now we're on track again. Apologies for the delays, auto attendant and call queues are business critical applications and we want to make sure expansion speed does not compromise the service quality.

@ibachus Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

@officedocsbot close

The feature is there now in our org.  Thank you everyone. :)


Expanded ComponentType to allow any props type

Fixes #19

@MattSchiller can confirm, existing cases still get the required props!
If we find more edge cases in the future we can always tackle them, though I'm starting to reach the end of my rope for wanting to spend more time on these types...

@MattSchiller can confirm, existing cases still get the required props!
If we find more edge cases in the future we can always tackle them, though I'm starting to reach the end of my rope for wanting to spend more time on these types...

Totally & sounds good 👍


Add default dashboards for combinations of data sources, with multiple single-source reports

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1866
Originally created by @DouweM on 2020-03-13 19:02:52

View 7 previous comments from the original issue on GitLab


Upgrade Azure.AI.OpenAI dependency

Current:
<PackageVersion Include="Azure.AI.OpenAI" Version="1.0.0-beta.9" />

Request: 1.0.0-beta.10 released  on 12/6, or whatever the last is.
See also: https://github.com/microsoft/kernel-memory/issues/190
Thanks

https://github.com/microsoft/semantic-kernel/pull/4089

dupe of https://github.com/microsoft/semantic-kernel/issues/3972


Testing the accessibility and performance of the application

[x] Use google forms to audit the accessibility and performance of the app
[x] If it scores well then keep the back-end and front-end design
[x] Put the result into the documentation

This issue has been completed and linked to a pull request.


how to block zoom when mousewheeling on treemap

Version
5.0.2
Steps to reproduce
let option = {
dataZoom: {
start: 80,
type: "slider",
zoomOnMouseWheel: false
},
tooltip: {
formatter:  ....
}
},
series: [{
type: 'treemap',
label: {
show: true,
formatter: '{b}'
},
upperLabel: {
show: true,
height: 30
},
itemStyle: {
borderColor: '#fff'
},
data: Object.values(chartData),
levels: getLevelOption()
}]
        };
        e.setOption(option);

What is expected?
when applying dataZoom.zoomOnMouseWheel = false, zoom event is not occur.
What is actually happening?
It doesn't work and zoom still occur.

treemap.zoom: false

Thank you It's been resolved


MOABSharp project (with documented process of C# binding generation and tweak)

Brief Description
moabsharp is a realistic example of with documented process of C# binding generation by CppSharp,  with some notes on tweak and fix uncompilable code.
There are some maybe useful dotnet core project setup xml file and some notes, I hope to share with the community, since the project is driven csproj xml instead of lua build script.
Currently, there are some bit C# code does not compile, must be manually fixed, such as

options.UsePropertyDetectionHeuristics = false; does not help to stop delete_mesh() C++ API been generated as property in C# which is not correct.
some class has missing constructor on windows (seems for class without public default ctor, but with public ctor with some parameter), but on Linux it is fine.
see details in fix error

I am planning to use Roslyn C# API to postprocessing the generated code fixing process, because I did not know how to remove and replace some problemetic C# generation in CppSharp.
And thank the developers for making moabsharp possible.
OS: Windows / OS X / Linux (include version and/or distro)
Used headers
Used settings
Target: MSVC/GCC/Clang
Other settings
Stack trace or incompilable generated code

@qingfengxia thank you for your kind words. We'll be happy to fix these errors so that you don't have to do anything by hand. I've been working on a major feature (which might help with the missing constructors) in my limited time but I'd definitely find some if I had some isolated bug reports.

Great! thank you. At the meantime, I will show how to further tweak the generated binding using Roslyn API on C# side.

Here is my postprocessing fix, now almost manual fix can be avoided
https://bitbucket.org/qingfengxia/moabsharp/src/dev/MOABSharpFix/Program.cs
perhaps we can close this information thread.

@qingfengxia when we've isolated the errors you're forced to fix in separate reports, then we'll close this one.


View controller in navigation view is not popped even though binding is set accordingly

Describe the bug
The NavigationLink for the "Navigate" button doesn't pop the ChildStateView when contained inside a List, after tapping the "Done!" button.
I was able to distill the example such that the misbehaviour is shown when the following is true:

There must be a second NavigationLink
All of that must be enclosed in a List

To Reproduce
https://github.com/hanneskaeufler/tca-bug-repro
I have created the above sample repository, where I have tried to distill this down.
If you run this app (here's a screenrecording https://github.com/hanneskaeufler/tca-bug-repro/blob/main/bug.mp4) you will see that the ChildStateView doesn`t pop back, as it should (and does in the second part of the video).
You can comment/uncomment here in order to see the working and non-working states.
https://github.com/hanneskaeufler/tca-bug-repro/blob/main/popBugRepro/ContentView.swift#L75
Expected behavior
View controller is popped when isActive binding is set to false
Screenshots
https://github.com/hanneskaeufler/tca-bug-repro/blob/main/bug.mp4
Environment

Xcode [Version 12.2 beta 4 (12B5044c), but same in app store release version]
Swift [e.g. 5.2.2]
OS (if applicable): [e.g. iOS 14.2]

Caveat: I realize this might just as well be a SwiftUI bug or something unrelated to TCA, but my "production" app is using TCA so I guess it might also be related. Any help would be appreciated!

I didn't look at your project but I had the same issue. I definitely think this is a bug into SwiftUI. Here is what I use to fix this when used with TCA:
`extension ViewStore {
public func navigation(
get: @escaping (State) -> Bool,
action: Action
) -> Binding {
var previous: Bool? = nil
return .init(
get: { get(self.state) },
set: { newValue, transaction in
guard newValue != previous else { return }
previous = newValue
guard !newValue else { return }
withAnimation(transaction.disablesAnimations ? nil : transaction.animation) {
self.send(action)
}
}
)
}
public func navigation<S>(
	get: @escaping (State) -> S?,
	action: Action
) -> Binding<Bool> {
	var previous: Bool? = nil
	return .init(
		get: { get(self.state) != nil },
		set: { newValue, transaction in
			guard newValue != previous else { return }
			previous = newValue
			guard !newValue else { return }
			withAnimation(transaction.disablesAnimations ? nil : transaction.animation) {
				self.send(action)
			}
		}
	)
}

}
`
It basically skip back event that weren't supposed to fire.

@hanneskaeufler I'm going to close this since it's a SwiftUI bug. If you filed a feedback please do share the number here!


Publish to OpenVSX

Thanks for this lovely extension !
We are quite a few using VSCodium, a release of VSCode which isn't proprietary and doesn't bundle Microsoft telemetry, and doing so it doesn't use Microsoft's marketplace for their extensions.
They use Open VSX, which is basically the same but they don't have obscure policies preventing custom clients to download their VSX packages.
Publishing on there is quite easy and I think it would be cool when you have time, meanwhile for those like me using VSCodium we can download the extension manually from the Microsoft marketplace website for now.

Hi @Miaourt
Thanks for the suggestion.
I actually work for Microsoft, so I wouldn't feel comfortable going out of my way to publish it onto another platform without fully understanding the implications.
The workaround to download it manually, or to build the extension locally seems ok for now. This project is MIT licensed.
A note that you can disable any telemetry https://code.visualstudio.com/docs/getstarted/telemetry
If you do have any specific concerns about privacy, I work closely with the product teams in VS code so I can bring this up directly.
Sorry I can't be of more help here, hope you understand


changes have not yet been reflected in the deployment

Deployed The CI Cd was not connected to this repo


Could you provide a method to construct the mesh and display it?

After test, how can I display the constructed mesh?

Check out pygel3d

Sorry for the late reply. You could use either GUI-based software (e.g. MeshLab), or 3D packages (e.g. pygel3d, open3d) to display mesh models.


Bring the users into product addition from scan card if either category, ingredients, nutrition is missing

Why

The latest discussion with my little sister

What

Let's be radical, and prevent from accessing the product page unless we have the info we need
Bring the users into product addition from scan card if either category, ingredients or nutrition is missing

In those cases, we can send them with the app global user, it won't overwrite data

Option - Weasel - Back and forth to editing/subknowledge panels

Option - Nuclear - Get them into product addition

Like in "Operation Sleepy Weasel"?
Actually I also said to myself today: the "I don't know anything about this product" carousel card is very boring, everything is grey (and you guys know how passionate I can be when we're talking about UI).
As you get 80% of the interesting results just with category, ingredients and nutrition, I would go medieval on incomplete products:

in the carousel card, display on top the "edit" buttons of each of the big 3 that is not answered yet
do the same on top of the product page, if ever the user managed to cross the bridge of death without answering the 3 questions

And then, "l'appétit vient en mangeant", and the users might find interesting to add some more data to products as they see the impact with computed scores.

on Top of the existing ? Or like in option 1 ?
"in the carousel card, display on top the "edit" buttons of each of the big 3 that is not answered yet"

A bit like option 1, but with more enthusiasm.

Option 1 seems more credible with 1 button=1 score, WDYT?

Option 1 seems more credible with 1 button=1 score, WDYT?

We need to test.

I drafted this option as well, but I loathe the back and forth implied.

@teolemon The thing is that we land on different places when we scan a new barcode or when we type in a new barcode.
My suggestions:

if we scan an existing barcode, we do the same as now - we display the product card
if we scan a new barcode, we display an unknown card (as now), but we open the "add new product page" directly
in the "add new product page", we start with nutriscore, ecoscore, nova, and only then the pictures
we display "bonus points" for each operation (typically the big 3)

That said, the impact would predominantly be for NEW products, not on INCOMPLETE products...
An idea would be to say: for new products or highly incomplete products, we always display the 3 questions in a dialog on top of whatever is displayed. Something like

title: Incomplete product!
text: Help us complete this product by answering those 3 questions!

ugly new barcode scanned
new barcode typed in
add new product page

@teolemon Looks very much like what you suggested:

What exactly would trigger the display of that dialog?

Let's try drastic. If no ingredients or no category or no nutrition.
There should be a way to access the product anyway.

We really need the word "add a".
It's not comprehensible otherwise

Instead of "tap for more info", we could - for incomplete products - display a big fat red "Incomplete product: please help us!" message, that would open a bottom sheet with the already mentioned "add category", "add ingredients" and "add nutrition facts" buttons, with an additional "go to the incomplete product anyway" button?

Slight variation: tapping on the "incomplete product" scan card would open the product page, that - if incomplete - opens the bottom sheet dialog at init.

Perhaps getting rid of the score labels when in the scan card. I'm sure that after 1 minute the users may be able to understand the difference between A green and E red, especially if they're given a tooltip in the scan card and the full label in the product page (that is next).
That would also help us put more "scores" in the scan card, assuming that logos are good enough for a scan card, as more details are accessible in the next page.

@teolemon This is my latest suggestion: an explicit warning card just after the product name, with all the needed actions.

as a scan card
as a product page

I'll PR probably tomorrow.
I don't say that it's the most beautiful thing on earth, but

it's intrusive - the user eyes cannot avoid to see the red block
it's not that intrusive - the user can ignore the red block and scroll away
it's less intrusive than a dialog or a bottom sheet

scan
product

I don't think we can realistically ship this, Red is very anxiety inducing.
What about having two prompts related to the scores ?

Compute the Eco-Score
Compute the Nutri-Score

I don't think we can realistically ship this, Red is very anxiety inducing.

It could be whatever color. I'll try with app primary and secondary colors instead.

What about having two prompts related to the scores ?

Compute the Eco-Score
Compute the Nutri-Score

Not a big fan of prompts (e.g. when to open them, when to reopen them, extra action to close them) and we would need a 3rd one for Nova. 3 different prompts for 3 fields in the end.
Regardless of the final implementation, we would probably be better off with a single label (prompt or button), but a very promising one (e.g. "Answer 3 questions now to compute Nutriscore, Ecoscore and Nova!")

@teolemon Latest suggestion...

scan card
product page

Let's try that way 👍

"Hey ! Answer 3 questions NOW to compute Nutri-Score, Eco-Score & Ultra-processing (NOVA) !"
Idea: We could even tweak that dynamically based on settings  "Hey ! Answer 3 questions NOW to compute Nutri-Score, Eco-Score & Mustard status !"