text:
Synthesis failed for java-vision

Hello! Autosynth couldn't regenerate java-vision. :broken_heart:
Here's the output from running synth.py:
va
 M proto-google-cloud-vision-v1p2beta1/src/main/java/com/google/cloud/vision/v1p2beta1/ImageContext.java
 M proto-google-cloud-vision-v1p2beta1/src/main/java/com/google/cloud/vision/v1p2beta1/ImageContextOrBuilder.java
 M proto-google-cloud-vision-v1p2beta1/src/main/proto/google/cloud/vision/v1p2beta1/image_annotator.proto
 M proto-google-cloud-vision-v1p3beta1/src/main/java/com/google/cloud/vision/v1p3beta1/ImageAnnotatorProto.java
 M proto-google-cloud-vision-v1p3beta1/src/main/java/com/google/cloud/vision/v1p3beta1/ImageContext.java
 M proto-google-cloud-vision-v1p3beta1/src/main/java/com/google/cloud/vision/v1p3beta1/ImageContextOrBuilder.java
 M proto-google-cloud-vision-v1p3beta1/src/main/java/com/google/cloud/vision/v1p3beta1/LocationName.java
 M proto-google-cloud-vision-v1p3beta1/src/main/java/com/google/cloud/vision/v1p3beta1/ProductName.java
 M proto-google-cloud-vision-v1p3beta1/src/main/java/com/google/cloud/vision/v1p3beta1/ProductSetName.java
 M proto-google-cloud-vision-v1p3beta1/src/main/java/com/google/cloud/vision/v1p3beta1/ReferenceImageName.java
 M proto-google-cloud-vision-v1p3beta1/src/main/proto/google/cloud/vision/v1p3beta1/image_annotator.proto
 M proto-google-cloud-vision-v1p4beta1/src/main/java/com/google/cloud/vision/v1p4beta1/ImageAnnotatorProto.java
 M proto-google-cloud-vision-v1p4beta1/src/main/java/com/google/cloud/vision/v1p4beta1/ImageContext.java
 M proto-google-cloud-vision-v1p4beta1/src/main/java/com/google/cloud/vision/v1p4beta1/ImageContextOrBuilder.java
 M proto-google-cloud-vision-v1p4beta1/src/main/java/com/google/cloud/vision/v1p4beta1/LocationName.java
 M proto-google-cloud-vision-v1p4beta1/src/main/java/com/google/cloud/vision/v1p4beta1/ProductName.java
 M proto-google-cloud-vision-v1p4beta1/src/main/java/com/google/cloud/vision/v1p4beta1/ProductSetName.java
 M proto-google-cloud-vision-v1p4beta1/src/main/java/com/google/cloud/vision/v1p4beta1/ReferenceImageName.java
 M proto-google-cloud-vision-v1p4beta1/src/main/proto/google/cloud/vision/v1p4beta1/image_annotator.proto
 M synth.metadata
?? proto-google-cloud-vision-v1/src/main/java/com/google/cloud/vision/v1/TextDetectionParams.java
?? proto-google-cloud-vision-v1/src/main/java/com/google/cloud/vision/v1/TextDetectionParamsOrBuilder.java
?? proto-google-cloud-vision-v1p1beta1/src/main/java/com/google/cloud/vision/v1p1beta1/TextDetectionParams.java
?? proto-google-cloud-vision-v1p1beta1/src/main/java/com/google/cloud/vision/v1p1beta1/TextDetectionParamsOrBuilder.java
?? proto-google-cloud-vision-v1p2beta1/src/main/java/com/google/cloud/vision/v1p2beta1/TextDetectionParams.java
?? proto-google-cloud-vision-v1p2beta1/src/main/java/com/google/cloud/vision/v1p2beta1/TextDetectionParamsOrBuilder.java
?? proto-google-cloud-vision-v1p3beta1/src/main/java/com/google/cloud/vision/v1p3beta1/TextDetectionParams.java
?? proto-google-cloud-vision-v1p3beta1/src/main/java/com/google/cloud/vision/v1p3beta1/TextDetectionParamsOrBuilder.java
?? proto-google-cloud-vision-v1p4beta1/src/main/java/com/google/cloud/vision/v1p4beta1/TextDetectionParams.java
?? proto-google-cloud-vision-v1p4beta1/src/main/java/com/google/cloud/vision/v1p4beta1/TextDetectionParamsOrBuilder.java
2020-12-11 03:37:52,081 autosynth [DEBUG] > Running: git log 857f70daef9f4c38f042fb3dfb7b8423ae18fd19 -1 --no-decorate --pretty=%s
2020-12-11 03:37:52,086 autosynth [DEBUG] > Running: git log 857f70daef9f4c38f042fb3dfb7b8423ae18fd19 -1 --no-decorate --pretty=%b%n%nSource-Author: %an <%ae>%nSource-Date: %ad
2020-12-11 03:37:52,091 autosynth [DEBUG] > Running: git add -A
2020-12-11 03:37:52,115 autosynth [DEBUG] > Running: git status --porcelain
2020-12-11 03:37:52,129 autosynth [DEBUG] > Running: git commit -m chore: update gapic-generator-java to 0.0.9

Committer: @miraleung
PiperOrigin-RevId: 346372957

Source-Author: Google APIs <noreply@google.com>
Source-Date: Tue Dec 8 11:37:30 2020 -0800
Source-Repo: googleapis/googleapis
Source-Sha: 857f70daef9f4c38f042fb3dfb7b8423ae18fd19
Source-Link: https://github.com/googleapis/googleapis/commit/857f70daef9f4c38f042fb3dfb7b8423ae18fd19
[autosynth-604 54a72dc] chore: update gapic-generator-java to 0.0.9
 124 files changed, 14584 insertions(+), 10838 deletions(-)
 delete mode 100644 google-cloud-vision/src/test/java/com/google/cloud/vision/v1/ImageAnnotatorSmokeTest.java
 delete mode 100644 google-cloud-vision/src/test/java/com/google/cloud/vision/v1p1beta1/ImageAnnotatorSmokeTest.java
 delete mode 100644 google-cloud-vision/src/test/java/com/google/cloud/vision/v1p2beta1/ImageAnnotatorSmokeTest.java
 delete mode 100644 google-cloud-vision/src/test/java/com/google/cloud/vision/v1p3beta1/ImageAnnotatorSmokeTest.java
 create mode 100644 proto-google-cloud-vision-v1/src/main/java/com/google/cloud/vision/v1/TextDetectionParams.java
 create mode 100644 proto-google-cloud-vision-v1/src/main/java/com/google/cloud/vision/v1/TextDetectionParamsOrBuilder.java
 create mode 100644 proto-google-cloud-vision-v1p1beta1/src/main/java/com/google/cloud/vision/v1p1beta1/TextDetectionParams.java
 create mode 100644 proto-google-cloud-vision-v1p1beta1/src/main/java/com/google/cloud/vision/v1p1beta1/TextDetectionParamsOrBuilder.java
 create mode 100644 proto-google-cloud-vision-v1p2beta1/src/main/java/com/google/cloud/vision/v1p2beta1/TextDetectionParams.java
 create mode 100644 proto-google-cloud-vision-v1p2beta1/src/main/java/com/google/cloud/vision/v1p2beta1/TextDetectionParamsOrBuilder.java
 create mode 100644 proto-google-cloud-vision-v1p3beta1/src/main/java/com/google/cloud/vision/v1p3beta1/TextDetectionParams.java
 create mode 100644 proto-google-cloud-vision-v1p3beta1/src/main/java/com/google/cloud/vision/v1p3beta1/TextDetectionParamsOrBuilder.java
 create mode 100644 proto-google-cloud-vision-v1p4beta1/src/main/java/com/google/cloud/vision/v1p4beta1/TextDetectionParams.java
 create mode 100644 proto-google-cloud-vision-v1p4beta1/src/main/java/com/google/cloud/vision/v1p4beta1/TextDetectionParamsOrBuilder.java
2020-12-11 03:37:52,214 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 54a72dc chore: update gapic-generator-java to 0.0.9
2020-12-11 03:37:52,225 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2020-12-11 03:37:52,240 autosynth [DEBUG] > Running: git diff HEAD..autosynth-604 -- . :(exclude)synth.metadata
2020-12-11 03:37:52,254 autosynth [DEBUG] > Running: git diff HEAD autosynth-604
2020-12-11 03:37:52,270 autosynth [DEBUG] > Running: git apply /tmpfs/tmp/tmpjecg3edw/autosynth-604.patch
2020-12-11 03:37:52,278 autosynth [DEBUG] > Running: git add -A
2020-12-11 03:37:52,292 autosynth [DEBUG] > Running: git status --porcelain
2020-12-11 03:37:52,308 autosynth [DEBUG] > Running: git commit -m chore: update gapic-generator-java to 0.0.9

Committer: @miraleung
PiperOrigin-RevId: 346372957

Source-Author: Google APIs <noreply@google.com>
Source-Date: Tue Dec 8 11:37:30 2020 -0800
Source-Repo: googleapis/googleapis
Source-Sha: 857f70daef9f4c38f042fb3dfb7b8423ae18fd19
Source-Link: https://github.com/googleapis/googleapis/commit/857f70daef9f4c38f042fb3dfb7b8423ae18fd19
[autosynth ae54faa] chore: update gapic-generator-java to 0.0.9
 14 files changed, 155 insertions(+), 75 deletions(-)
2020-12-11 03:37:52,338 autosynth [DEBUG] > Running: git diff autosynth-604..autosynth-606 -- . :(exclude)synth.metadata
2020-12-11 03:37:52,343 autosynth [DEBUG] > Running: git diff autosynth-604..autosynth-606 -- synth.metadata
2020-12-11 03:37:52,349 autosynth [DEBUG] > Running: git diff autosynth-606..autosynth-611 -- . :(exclude)synth.metadata
2020-12-11 03:37:52,353 autosynth [DEBUG] > Running: git diff autosynth-606..autosynth-611 -- synth.metadata
2020-12-11 03:37:52,359 autosynth [DEBUG] > Running: git diff autosynth-611..autosynth-621 -- . :(exclude)synth.metadata
2020-12-11 03:37:52,363 autosynth [DEBUG] > Running: git diff autosynth-611..autosynth-621 -- synth.metadata
2020-12-11 03:37:52,369 autosynth [DEBUG] > Running: git push --force origin autosynth
remote:
remote: Create a pull request for 'autosynth' on GitHub by visiting:
remote:      https://github.com/googleapis/java-vision/pull/new/autosynth
remote:
To https://github.com/googleapis/java-vision.git
 * [new branch]      autosynth -> autosynth
2020-12-11 03:37:56,413 autosynth [DEBUG] > Running: git log -7 --pretty=%b
2020-12-11 03:37:58,798 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 334, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 92, in synthesize_loop
    synthesize_inner_loop(fork, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 137, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:

repo: googleapis/java-vision


text:
PubSub Subscription randomly stops pulling messages from a topic

For a while now, we noticed that the code just stops pulling new messages so randomly, sometimes it takes few weeks, sometimes days before that happens, and we always had to re-start the service for this to work again.
I have found a similar issue .NET repository, I don't know if that can help.
Environment details

OS: 16.5.0-alpine3.14
Node.js version: 16.5.0
npm version: 7.11.2
@google-cloud/pubsub version: 2.18.3

@gothraven Thanks for the note - do you think it might be related to https://github.com/googleapis/nodejs-pubsub/issues/1135 ?

@feywind It might be related to grpc I have been reading few things about this but it does not happen 15 min after launching, it sometimes takes days, sometimes weeks, but never less than a day (in our case), I'm not sure if that helps !

Any news on this?

This sounds just like https://github.com/googleapis/nodejs-pubsub/issues/1135, maybe we should consolidate the issue?

We have the same problem. Is there any news? not after 15 min. it happens randomly

Yeah, I agree, I'm going to ref it again on #1135 and close this one.

source: gharchive/issue

authors: feywind gothraven mfarhat437 robottheory weyert

repo: googleapis/nodejs-pubsub

license_type: permissive

license_source: bigquery


text:
Is there a way to purge a queue?

I have looked and I saw that i can delete the subscription and create a new one with the same name and configuration.
I see that stackdriver shows getSize of unacked messages for 5 minutes and than it drops to 0.
In the api it says it should be 120 seconds max.
  try {
            const subscriptionMetadataArr = await pubSub.subscription(queue).get();
            const subscription = subscriptionMetadataArr[1]; // configuration
            // remove the subscription and create another one with the same name
            await pubSub.subscription(queue).delete();
            const topic = pubSub.topic(subscription.topic);
            // Create the same subscription with the same name and configuration
            await topic.subscription(subscription.name).create({...subscription});
        } catch (err) {
            throw err;
        }

@slavoroi Which GCP Pub/Sub metric are you referring to from this table?

authors: anguillanneuf slavoroi


text:
DO NOT MERGE: Broken autosynth PR reverting important things 🙃

This PR was generated using Autosynth. :rainbow:
Here's the log from Synthtool:
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/synth.py.
synthtool > Ensuring dependencies.
synthtool > Pulling artman image.
latest: Pulling from googleapis/artman
Digest: sha256:8900f94a81adaab0238965aa8a7b3648791f4f3a95ee65adc6a56cfcc3753101
Status: Image is up to date for googleapis/artman:latest
synthtool > Cloning googleapis.
synthtool > Running generator for google/cloud/securitycenter/artman_securitycenter_v1beta1.yaml.
synthtool > Generated code into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/js/securitycenter-v1beta1.
synthtool > Running generator for google/cloud/securitycenter/artman_securitycenter_v1.yaml.
synthtool > Generated code into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/js/securitycenter-v1.
.eslintignore
.eslintrc.yml
.github/ISSUE_TEMPLATE/bug_report.md
.github/ISSUE_TEMPLATE/feature_request.md
.github/ISSUE_TEMPLATE/support_request.md
.jsdoc.js
.kokoro/common.cfg
.kokoro/continuous/node10/common.cfg
.kokoro/continuous/node10/docs.cfg
.kokoro/continuous/node10/lint.cfg
.kokoro/continuous/node10/samples-test.cfg
.kokoro/continuous/node10/system-test.cfg
.kokoro/continuous/node10/test.cfg
.kokoro/continuous/node11/common.cfg
.kokoro/continuous/node11/test.cfg
.kokoro/continuous/node8/common.cfg
.kokoro/continuous/node8/test.cfg
.kokoro/docs.sh
.kokoro/lint.sh
.kokoro/presubmit/node10/common.cfg
.kokoro/presubmit/node10/docs.cfg
.kokoro/presubmit/node10/lint.cfg
.kokoro/presubmit/node10/samples-test.cfg
.kokoro/presubmit/node10/system-test.cfg
.kokoro/presubmit/node10/test.cfg
.kokoro/presubmit/node11/common.cfg
.kokoro/presubmit/node11/test.cfg
.kokoro/presubmit/node8/common.cfg
.kokoro/presubmit/node8/test.cfg
.kokoro/presubmit/windows/common.cfg
.kokoro/presubmit/windows/test.cfg
.kokoro/publish.sh
.kokoro/release/docs.cfg
.kokoro/release/docs.sh
.kokoro/release/publish.cfg
.kokoro/samples-test.sh
.kokoro/system-test.sh
.kokoro/test.bat
.kokoro/test.sh
.kokoro/trampoline.sh
.nycrc
.prettierignore
.prettierrc
CODE_OF_CONDUCT.md
CONTRIBUTING.md
LICENSE
README.md
codecov.yaml
renovate.json
samples/README.md
synthtool > Replaced '\\[\\\\p\\{L\\}\\\\p\\{N\\}\\]\\(https:\\/\\/cloud\\.google\\.com\\{\\\\p\\{L\\}\\\\p\\{N\\}_- \\]\\{0\\,30\\}\\[\\\\p\\{L\\}\\\\p\\{N\\}\\]\\)\\?' in src/v1beta1/doc/google/cloud/securitycenter/v1beta1/doc_source.js.
synthtool > Replaced '\\[\\\\p\\{L\\}\\\\p\\{N\\}\\]\\(https:\\/\\/cloud\\.google\\.com\\{\\\\p\\{L\\}\\\\p\\{N\\}_- \\]\\{0\\,30\\}\\[\\\\p\\{L\\}\\\\p\\{N\\}\\]\\)\\?' in src/v1/doc/google/cloud/securitycenter/v1/doc_source.js.
synthtool > Replaced '\\/\\*\\*\n \\* @namespace google\n \\*/' in src/index.js.
synthtool > Replaced 'https:\\/\\/cloud\\.google\\.com[\\s\\*]*http:\\/\\/(.*)[\\s\\*]*\\)' in src/v1beta1/doc/google/protobuf/doc_timestamp.js.
synthtool > Replaced 'https:\\/\\/cloud\\.google\\.com[\\s\\*]*http:\\/\\/(.*)[\\s\\*]*\\)' in src/v1/doc/google/protobuf/doc_timestamp.js.
synthtool > No replacements made in **/doc/google/protobuf/doc_timestamp.js for pattern toISOString\], maybe replacement is not longer needed?

> core-js@2.6.9 postinstall /tmpfs/src/git/autosynth/working_repo/node_modules/core-js
> node scripts/postinstall || echo "ignore"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

> protobufjs@6.8.8 postinstall /tmpfs/src/git/autosynth/working_repo/node_modules/protobufjs
> node scripts/postinstall

npm notice created a lockfile as package-lock.json. You should commit this file.
added 624 packages from 867 contributors and audited 1675 packages in 13.833s
found 0 vulnerabilities

> @google-cloud/security-center@1.0.0 fix /tmpfs/src/git/autosynth/working_repo
> eslint --fix '**/*.js'

synthtool > Cleaned up 2 temporary directories.
synthtool > Wrote metadata to synth.metadata.

@bcoe could you take a look at this?

source: gharchive/pull-request

authors: JustinBeckwith yoshi-automation

repo: googleapis/nodejs-security-center


text:
Object prototype may only be an Object or null: undefined at Function.setPrototypeOf appeared between 5.8.2 and 5.8.5

Is this a client library issue or a product issue?
This is the client library.

Did someone already solve this?
I was not able to find any other tickets regarding this error

Environment details

OS: macOS 11.3
Node.js version: 12.22.1
yarn version: 1.22.10
@google-cloud/storage version: 5.8.5

Steps to reproduce

Update from 5.8.2 to 5.8.5

Throws
TypeError: Object prototype may only be an Object or null: undefined
        at Function.setPrototypeOf (<anonymous>)

      at node_modules/graceful-fs/polyfills.js:139:39
      at patch (node_modules/graceful-fs/polyfills.js:141:5)
      at patch (node_modules/graceful-fs/graceful-fs.js:104:3)
      at Object.<anonymous> (node_modules/graceful-fs/graceful-fs.js:96:18)
      at Object.<anonymous> (node_modules/configstore/index.js:4:12)

Hi @cnpatric, thanks for submitting this issue. Do you mind providing details on when exactly this error occurs? It it during npm install?

Also.. what version of typescript are you using?

this happens when we run our tests when we try to test our storage implementations so with yarn test which runs "test": "node_modules/.bin/jest --config jest.config.unit.js", . I can't tell when exactly this appears though it looks like it crashes immediately since no tests in this file are run.
we use typescript 4.3.4

Interesting! This will be hard to reproduce unless I have access to your test files. Can you make sure you environment doesn't have any circular dependencies? These are the changes to package.json between the two versions you mentioned.

Looks like we actually have circular dependencies that use firestore.
I'll fix them and report back if that solved the issue, thanks for your help so far!

No prob @cnpatric. I'll hold off on closing the ticket until I hear back.

Closing this out. Please re-open if issue persists. Thanks @cnpatric!

@danielduhh Sorry just had time for that now, we removed the circular dependency and don't have any other according to madge. So this doesn't seem to be a circular dependency issue.

authors: cnpatric danielduhh

repo: googleapis/nodejs-storage

license_source: github-api


text:
refactor(samples): convert sample tests from ava to mocha

Fixes convert all sample tests from ava to mocha #2865 (it's a good idea to open an issue first for discussion)

[ ] Tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Codecov Report

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

@@          Coverage Diff          @@
##           master   #126   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines           5      5
=====================================
  Hits            5      5

Continue to review full report at Codecov.

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

authors: codecov-io nareshqlogic

repo: googleapis/nodejs-tasks


text:
chore: Migrate access-approval synth.py from artman to bazel

@busunkim96 PTAL

repo: googleapis/python-access-approval


text:
chore: update doc page from googleapis.dev to cloud.google.com

Updating the reference documentation website from googleapis.dev to cloud.google.com for the index pages.

Readme changes need to be made, closing for now.

repo: googleapis/python-assured-workloads


text:
docs: add examples to DataFrameGroupBy and SeriesGroupBy

This change is adding example codes to all methods of DataFrameGroupBy and SeriesGroupBy.

[X] Ensure the tests and linter pass
[X] Code coverage does not decrease (if any source code was changed)
[X] Appropriate docs were updated (if necessary)

Fixes internal bug: 341122015🦕

You can do a staging following: https://g3doc.corp.google.com/devrel/cloud/infra/devrel_services/g3doc/dev/content_automation/cloud_rad/python.md?cl=head#staging-local-changes-from-github-to-devsite to stage docs manually
Example PR:

https://github.com/googleapis/python-bigquery-dataframes/pull/287
https://github.com/googleapis/python-bigquery-dataframes/pull/499

authors: ashleyxuu chelsea-lin

repo: googleapis/python-bigquery-dataframes


repo: googleapis/python-deploy


text:
Correctly handle IAM resource name types

We need to handle resource name types on IAM methods. These should probably accept generic ResourceName objects, as IAM methods will usually accept many resource name formats. Toolkit needs to support specifying ResourceName objects as flattened method parameters without interferring with the string format functions used by other languages.

I think this is now completely done, isn't it? Suggest closing.

Yes, this is complete.

authors: jskeet michaelbausor

repo: googleapis/toolkit


text:
Stuck when trying to launch cartographer with RPLidar

Hey i have this issue when running the command
`roslaunch cartographer_ros backpack_2d.launch´
The process starts but gets stuck like in the picture below

I am fully able to run the deutsche museum demo, provided by Cartographer, but i can't get it to work with my own lidar (RPLidar a1).
Also the lidar is perfectly connected (i get data from /scan) and i am running hector SLAM just fine.
roscore and rviz are also both up and running beforehand.
Any suggestions to get it working with cartographer?

I guess you need check the configuration file(.lua). you should set num_laser_scans = 1 and num_multi_echo_laser_scans = 0

I guess you need check the configuration file(.lua). you should set num_laser_scans = 1 and num_multi_echo_laser_scans = 0

Thanks for your reply, but I already did that, still same issue :/
here are my .lua and .launch files
backback_2d.lua:  https://pastebin.com/FXA4Du0D
backback_2d.launch:  https://pastebin.com/trzJDZ7Z

I set the base_frame is laser and the topic is 'scan'. Attached to the file I have changed.
At 2019-03-21 16:47:49, "joyde3382" notifications@github.com wrote:
I guess you need check the configuration file(.lua). you should set num_laser_scans = 1 and num_multi_echo_laser_scans = 0
Thanks for your reply, but I already did that, still same issue :/
here are my .lua and .launch files
backback_2d.lua: https://pastebin.com/FXA4Du0D
backback_2d.launch: https://pastebin.com/trzJDZ7Z
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Hmm, not quite sure what you're getting at. I managed to link the lidar node with the cartographer node
by replacing the following lines:
tracking_frame = "base_link",
published_frame = "base_link",
with
tracking_frame = "rplidarNode",
published_frame = "rplidarNode",

However i am still stuck at the same place..

@joyde3382 Did you figure out how to set it up?
I am running into the same issue.
Thanks.

repo: googlecartographer/cartographer


text:
Added a fake file writer (writes to string instead of file)

Added fake filer writer which writes the output to a string instead of a file.
This will help writing tests for classes that use the file writer interface to write data.

This is related to #1069.

Thanks @wohe  and @pifon2a for the feedback. @pifon2a I reverted back to the initial solution which doesn't use inheritance for better readability, sorry about that.
The std::shared_ptrstd::string on_close_output in FakeFileWriter will be used in a mock FileWriterFactory for #1069.
Can one of you have a look again?

@wohe, can you have a look again?

authors: schwoere wohe


text:
Video from webcam not showing

I am unable to see the video from my webcam...i tried index file for step01 folder bt still am unable to see a video ..

@gurbaaj could you provide more details on how you are running this?
Are you running this from a server or localhost (this only works in https / localhost)? Any errors in console? What browser and operating system are you using?

I'll close this now, but feel free to open an issue if you're still experiencing problems.

authors: gurbaaj nitobuendia samdutton

repo: googlecodelabs/webrtc-web


text:
[normalizer] Consider lookup flags when merging rules

This was causing normalizer to be non-deterministic in some cases; because we were merging rules without considering the lookup flags, we would preserve the flag of the first rule we encountered, which would depend on the iteration order of the hashmap.
This fixes the underlying issue, by not merging any rules that do not have identical lookup flags.

I think this also contributes to (fixes?) https://github.com/googlefonts/fontc/issues/643?

authors: cmyr rsheeter

repo: googlefonts/fontc


text:
GF Latin Plus includes ₧ (peseta), a mostly unused symbol for an historical currency. Should it?

The Spanish peseta has been out of use for at least 20 years (since the introduction of the Euro). Additionally, the ₧ (P plus bar) symbol potentially doesn’t seem to be used as much as the "Pts" version of the glyph.
Should it really be in the GF Latin Plus glyph set? If so, is there a reason?
Related: https://github.com/googlefonts/glyphsets/issues/37
Thanks!

As @RosaWagner said in #37,

This is planned in https://github.com/googlefonts/glyphsets/pull/36/files#diff-deb67e1abe331b32c4d92df0424d086fa76c2861e0b1a7337ba935e70eaaa8d7

repo: googlefonts/glyphsets


text:
Update explanation of difference in "individual heterozygosity" query

@deflaux
The difference between the query and vcftools is smaller now as a result of earlier fixes to the query (https://github.com/googlegenomics/codelabs/commits/master/R/PlatinumGenomes-QC/sql/homozygous-variants.sql). Updated the explanation as a result.

Signed CLA for my gmail account as well (asha.rostamianfar@gmail.com).

Excellent - thank you @arostamianfar

authors: arostamianfar deflaux

repo: googlegenomics/codelabs


text:
Number parsing issue : Poland

I am using a parse method of PhoneNumberUtil with a Poland phone number e.g.(+48 (0) 22 512 XXXX). here, i got result as "Country Code: 48 National Number: 22512XXX Leading Zero(s): true" whereas i am assuming Zero will be truncated from the result.
When i try the same use case with UK phone number e.g.(+44 (0) 22 512 XXXX), it truncates the Zero from it and gives result as expected like "Country Code: 44 National Number: 22512XXXX".
After debugging the lipphonenumber sdk, i found that internally these values are coming from a resource file(PhoneNumberMetadataProto_**) which is an encrypted file.
So, my understanding is that number parsing logic must be same for all countries,

Why it is different for poland and UK?
Does this require any fix from my end, as i am expecting result without leading the zero value?

Thanks for the clarification.
However, phone number that we get are beyond our control and would like to fix this for our customers in Poland. Can you please suggest what is the best way to override this xml configuration for Poland in our project?

You can't easily, because we don't consider this a valid use-case.
If a number is bad, you want to reflect that. This number is not diallable and doesn't work. Why do you want to try and fix it? Parsing it will retain the number you gave it, which is what it's designed to do.
This isn't a bug with the library. Please consider joining the discussion group if you'd like to discuss this further.

authors: lararennie sangamaggarwal


text:
google colab - deep-stabilization-master

Hello, I'm trying to run the program in google colab but it doesn't work in the section of "!bash install.sh" in the FlowNet2 section. The error that says colab is
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
can you help me?
thanks!

hello did you find a solution to your problem pleas ?, am facing the same problem.

hi! I don't have a solution. The owner never answered. If you find something, place tell me!

Hope this will help. https://github.com/NVIDIA/flownet2-pytorch/pull/271

hello, I used the google colab in this link to genrate the flowNet https://github.com/Gauravv97/flownet2-Colab

When I meet these problems above mentioned, I will open the install.sh, and install the contents one by one step, usually it works.

authors: cyfedu1024 hibaKhechai pilitro zhmeishi

repo: googleinterns/deep-stabilization


text:
Style my commits button in Explore

Changes

Styled My Commits button in Explore page to look like the UI Mock

The icon after "My Commits" looks like a placeholder of profile photo? Are we going to show user profile photo here?

@ifhuang

The icon after "My Commits" looks like a placeholder of profile photo? Are we going to show user profile photo here?

Haha nope it's actually just meant to be an icon 😅

authors: hzxcaryn ifhuang

repo: googleinterns/gpay-group-buy


text:
Exception building library

Hello there,
I'm trying to build a "library" or "library-v3" through Gradle Task "build", but script fails with the following message:
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring project ':library-v3'.
> groovy.lang.GroovyRuntimeException: Cannot set the value of read-only property 'executionData' for task ':library-v3:jacocoTestDebugUnitTestReport' of type org.gradle.testing.jacoco.tasks.JacocoReport.

Is there a way to overcome the problem?
I'm using Android Studio 4.0.2.
Thank you.
Max

Solution here:
https://proandroiddev.com/how-i-resolved-jacoco-plugin-error-after-upgrading-gradle-to-6-1-1-d85c0086d66a

I'm able to see library and library-v3 build on master. The issue you ran into is most likely related to using the Android Gradle Plugin 4.x.x which both libraries are not yet upgraded to. When we do upgrade, the fix as you pointed out is to use the fork of jacoco-android-gradle-plugin.

PR open at https://github.com/googlemaps/android-maps-utils/pull/799

authors: arriolac barbeau mdicosimo

repo: googlemaps/android-maps-utils


text:
pittpatt "inconsistent image dimensions" errors on some devices

On certain devices, face tracking fails with errors
E/pittpatt: online_face_detector.cc:236] inconsistent image dimensions E/pittpatt: detector.cc:220] inconsistent image dimensions
Has been observed on

Samsung Galaxy Note 4
Samsung Galaxy J2
with apparently fairly normal front camera preview sizes of e.g.
960x540, 720x480, 640x480

One workaround is to force to 800x480, which enables face tracking to work
with front camera on both these devices (even though 800x480 not even listed
in available preview sizes on J2)

The face tracker assumes that each image frame received is consistently the same dimensions.  As far as I can tell, it looks like it is receiving a new image frame that is has different dimensions that the previous image frame.
Can you give more details on how you initialized the face detector and how you are passing in images?

Thank you for responding so quickly.
Our detector is very simple, just via
new FaceDetector.Builder().build()
with 4 of the usual flags (setLandmarkType(FaceDetector.NO_LANDMARKS) etc)
Frame created via new Frame.Builder().build(), using setImageData() with a byteBuffer and our preview width and height (which will be constant until camera switched front/rear)

When the camera is switched or rotated, the face detector should be rebuilt so that it can reinitialize for images of a different dimension.

Yes -- the second I saw your original response I started looking at this, think the bug is in our code...mea culpa

repo: googlesamples/android-vision


text:
🛑 goormEDU is down

In 8c32ca1, goormEDU (https://edu.goorm.io) was down:

HTTP code: 403
Response time: 685 ms

Resolved: goormEDU is back up in 1c7b509 after 6 minutes.

repo: goorm-dev/goorm-status

license: MIT


text:
🛑 goormIDE is down

In 2fa2a58, goormIDE (https://ide.goorm.io) was down:

HTTP code: 403
Response time: 601 ms

Resolved: goormIDE is back up in 490ae99 after 1 hour, 47 minutes.


text:
🛑 goormIDE is down

In 8fb051a, goormIDE (https://ide.goorm.io) was down:

HTTP code: 403
Response time: 455 ms

Resolved: goormIDE is back up in 71b4b0c after 5 minutes.


text:
🛑 goormEDU is down

In 103cca2, goormEDU (https://edu.goorm.io) was down:

HTTP code: 403
Response time: 740 ms

Resolved: goormEDU is back up in 6fe9d89 after 5 minutes.


text:
🛑 goormEDU is down

In 3a718db, goormEDU (https://edu.goorm.io) was down:

HTTP code: 403
Response time: 771 ms

Resolved: goormEDU is back up in cfe13ec after 10 minutes.


text:
Login route bug

If you go to /login while logged in, the application hangs

Where is this fixed?

Give me a moment. I ran into an issue with the push.

Pushed.

authors: MorganPeterson bkj

repo: gophronesis/penny-sae


text:
Selecionar a Rede Social no perfil do usuário issue #183

Criada uma tabela que guarda os tipos das redes sociais. Mostrar esse tipos na tela de editar perfil do usuário. Assim como mostrar as redes sociais cadastradas no show do usuário.

Coverage decreased (-0.2%) to 12.156% when pulling 19c2e3629bd8da972df84d10aa8beb1f2078075c on benhur10cp:master into 4f03ca263fc87ba80022899e9fd04f42ff33627d on gorails:master.

repo: gorails/gorails

license: mit


text:
Add a postman collection to our API docs

What we need
Add "Download our postman collection." on the home page of the API docs, with a link to the file below.
Postman collection
Then add: "Make sure you replace the {account_name}, and add your email along with your API key in the Basic Auth fields."

https://www.getpostman.com/docs/postman_for_publishers/run_button/creating_run_button

authors: RomainLapeyre xarg

repo: gorgias/gorgias-docs


text:
Fixed some typos

Just fixing more some typos.
README.md:
abstrations -> abstractions
tensor/example_dense_cmp_test.go:
Simliarly -> Similarly

Coverage increased (+0.02%) to 72.807% when pulling c8cfa985e178148922b9c8d511b0cc169f25bcac on tiagorlampert:master into d78b17f3e9857e0b755070a011d200176b7baa75 on gorgonia:master.

Coverage increased (+0.02%) to 72.807% when pulling c8cfa985e178148922b9c8d511b0cc169f25bcac on tiagorlampert:master into d78b17f3e9857e0b755070a011d200176b7baa75 on gorgonia:master.

Thank you so much @tiagorlampert

authors: chewxy coveralls tiagorlampert

repo: gorgonia/tensor


text:
Upstream: Pull in changes from Hugo v0.75.0

Closes: #85

Why is the branch name hugo-v0.75.0-1?

authors: chayev felicianotech

repo: gothamhq/gotham


text:
Writing GUI Tests

Hey everyone,
I would like to test my GUI application. Therefore I would like to create my own gdk.Event structs (as if a key-press-event would happen for example) - how do I do that? I didn't find any structs for events in your code.
Thanks in Advance.

Hey, while we have structures for events, those are meant to be read only and don't expose the underlying properties. You could however use something like https://github.com/go-vgo/robotgo in order to actually simulate a user. Sorry for the late answer.

authors: Bios-Marcel Bresenham

license: isc


text:
Update to Esprima 2.0 (refs #141).

See http://blog.jquery.com/2015/02/06/esprima-2-0-released/. This sets the step for Istanbul to start instrumenting and tracking the coverage of ES6 syntax.
No feature or performance regression was observed.

Coverage remained the same at 97.57% when pulling 5ca2268c51252380d1017f381279dad53a783c83 on ariya:esprima-2.0 into bc1cbdeeacf83343955b8bf473dbd7b60cdcde10 on gotwarlost:master.

@gotwarlost Ping. Let me know if you need more information!

@gotwarlost Any plans on getting this merged? io.js supports many ES6 features and istanbul is not usable with a codebase that makes use of these features right now.

I'll merge the pull request but note that the merge of this PR is of no direct benefit to anyone as it stands. That is because the ES6 features for which I have instrumentation and the ES6 features that are present in Esprima 2.0 are completely orthogonal :(

@gotwarlost Thanks!
The plan is for Esprima 2.1, 2.2, and so, to include more and more ES6 features.

authors: ariya arthurschreiber coveralls gotwarlost

repo: gotwarlost/istanbul


text:
ie8 examples are missing

This seems to be a non issue.
I tested this and after some patience the iframe loads in. Seems like IE is struggling a little bit but then it works. Can't really blame IE8 for that 😬

authors: TrebBrennan alex-page

repo: govau/GOLD


text:
🛑 Crawler APIs is down

In 91d7612, Crawler APIs (https://crawler.ritamdigital.org/services/ritam/api/posts/top-headlines/tag/top-stories/editor) was down:

HTTP code: 500
Response time: 1053 ms

Resolved: Crawler APIs is back up in e92d17e after 6 minutes.

repo: govindbhardwaj/monitor-ritam


text:
Error inflating class com.gordonwong.materialsheetfab.sample.Fab

Hi @gowong
Thanks for the amazing library.
I tried to use your library in your project.
(Initially i tried to copy-paste the sample app files to test the library)
But i'm getting this error
11-19 17:31:48.186 11272-11272/com.roshu.testing123 E/AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.roshu.testing123/com.roshu.testing123.MainActivity}: android.view.InflateException: Binary XML file line #44: Error inflating class com.gordonwong.materialsheetfab.sample.Fab
This is my XML file (I took it directly from sample app):

<android.support.v4.widget.DrawerLayout
android:id="@+id/drawer_layout"
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
android:layout_width="match_parent"
android:layout_height="match_parent">
<RelativeLayout
    android:layout_width="match_parent"
    android:layout_height="match_parent">

    <android.support.design.widget.CoordinatorLayout
        android:layout_width="match_parent"
        android:layout_height="match_parent">

        <android.support.design.widget.AppBarLayout
            android:id="@+id/appbar"
            android:layout_width="match_parent"
            android:layout_height="wrap_content">

            <!-- Toolbar -->
            <android.support.v7.widget.Toolbar
                android:id="@+id/toolbar"
                style="@style/Widget.MaterialSheetFab.ToolBar" />

            <!-- Tabs -->
            <android.support.design.widget.TabLayout
                android:id="@+id/tabs"
                style="@style/Widget.MaterialSheetFab.TabLayout" />
        </android.support.design.widget.AppBarLayout>

        <!-- View pager -->
        <android.support.v4.view.ViewPager
            android:id="@+id/viewpager"
            android:layout_width="match_parent"
            android:layout_height="match_parent"
            android:layout_below="@+id/appbar"
            app:layout_behavior="@string/appbar_scrolling_view_behavior" />

    </android.support.design.widget.CoordinatorLayout>

    <!-- Your FAB implementation -->
    <com.gordonwong.materialsheetfab.sample.Fab
        android:id="@+id/fab"
        style="@style/Widget.MaterialSheetFab.Fab"
        android:layout_alignParentBottom="true"
        android:layout_alignParentEnd="true"
        android:layout_alignParentRight="true" />

    <!-- Overlay that dims the screen -->
    <com.gordonwong.materialsheetfab.DimOverlayFrameLayout
        android:id="@+id/overlay"
        android:layout_width="match_parent"
        android:layout_height="match_parent" />

    <!-- Circular reveal container for the sheet -->
    <io.codetail.widget.RevealLinearLayout
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        android:gravity="end|bottom"
        android:orientation="vertical">

        <!-- Sheet that contains your items -->
        <android.support.v7.widget.CardView
            android:id="@+id/fab_sheet"
            style="@style/Widget.MaterialSheetFab.Sheet">

            <!-- Sheet items -->
            <LinearLayout
                android:layout_width="wrap_content"
                android:layout_height="wrap_content"
                android:orientation="vertical">

                <!-- Recording -->
                <TextView
                    android:id="@+id/fab_sheet_item_recording"
                    style="@style/TextAppearance.MaterialSheetFab.Sheet.Item"
                    android:drawableLeft="@drawable/ic_mic_grey600_24dp"
                    android:drawableStart="@drawable/ic_mic_grey600_24dp"
                    android:text="@string/recording" />

                <!-- Reminder -->
                <TextView
                    android:id="@+id/fab_sheet_item_reminder"
                    style="@style/TextAppearance.MaterialSheetFab.Sheet.Item"
                    android:drawableLeft="@drawable/ic_access_alarms_grey600_24dp"
                    android:drawableStart="@drawable/ic_access_alarms_grey600_24dp"
                    android:text="@string/reminder" />

                <!-- Photo -->
                <TextView
                    android:id="@+id/fab_sheet_item_photo"
                    style="@style/TextAppearance.MaterialSheetFab.Sheet.Item"
                    android:drawableLeft="@drawable/ic_photo_camera_grey600_24dp"
                    android:drawableStart="@drawable/ic_photo_camera_grey600_24dp"
                    android:text="@string/photo" />

                <!-- Note -->
                <LinearLayout
                    android:layout_width="match_parent"
                    android:layout_height="wrap_content"
                    android:background="@color/theme_accent">

                    <TextView
                        android:id="@+id/fab_sheet_item_note"
                        style="@style/TextAppearance.MaterialSheetFab.Sheet.Item"
                        android:drawableLeft="@drawable/ic_create_grey600_24dp"
                        android:drawableStart="@drawable/ic_create_grey600_24dp"
                        android:text="@string/createnote" />
                </LinearLayout>

            </LinearLayout>

        </android.support.v7.widget.CardView>

    </io.codetail.widget.RevealLinearLayout>

    <!-- Snackbar -->
    <LinearLayout
        android:id="@+id/snackbar"
        style="@style/Widget.MaterialSheetFab.Snackbar"
        android:layout_alignParentBottom="true">

        <TextView
            style="@style/TextAppearance.MaterialSheetFab.Snackbar.Message"
            android:text="@string/snackbar_shared_msg" />

        <TextView
            style="@style/TextAppearance.MaterialSheetFab.Snackbar.Action"
            android:text="@string/view" />
    </LinearLayout>
</RelativeLayout>

<!--<android.support.design.widget.NavigationView
    android:id="@+id/navigation_view"
    android:layout_width="wrap_content"
    android:layout_height="match_parent"
    android:layout_gravity="start"
    app:headerLayout="@layout/layout_drawer_header" />-->

</android.support.v4.widget.DrawerLayout>
Thanks for any help :)
Edit:
i imported library using build.gradle file.
(i didn't actually copied the library to studio)

The com.gordonwong.materialsheetfab.sample.Fab class needs to be implemented. Please see the readme for details on how to do that.

@gowong Thanks.
It solved my problem :100:
can you please address #18
It's not bug with library. I'm new to android.
when you have sometime please have a look into it :)

@roshu10 I'd be glad to help out with any questions or issues related to this library, but I think it'd be better for you to post on stackoverflow any questions you have about Android.

@gowong
I tried to implement onClick on notes using few questions from stackoverflow.
But couldn't find solution
I did some changes.
my question is also here (https://plus.google.com/u/0/110290076138677327721/posts/4z2gAM93f9T)
This is the only issue stopping me from using this amazing library

repo: gowong/material-sheet-fab


text:
Support vision language models in llama-box backend

Is your enhancement related to a problem? Please describe.
Now llama-box supports VLMs like Qwen2-VL. However, GPUStack does not handle the multimodal projector file. Users need to download it and set it via backend parameters.
Describe the solution you'd like
Make the UX as simple as other LLMs.

Verified in main 37cc489

authors: Finenyaco gitlawr

repo: gpustack/gpustack


text:
Open to new collaborators

If you want to collaborate in the project you are more than welcome, feel free to join the Discord https://discord.com/invite/U967mp5qbQ and tell us what you are interested in doing and we will help you to be able to help on it 🎉 👍

Would it be helpful to start copying the old issues from gqless into this repo? Perhaps a chance to reevaluate the state and mark which issues are good first issues?

My idea was to simply start fixing them in the gqty repo and then simply notifying that the fix was released in gqty instead of gqless, there are some issues that were already fixed and did exactly that, if you feel like some issues should be copied before, no problem 👍

I think there shouldn't be two repositories for the same library. Makes things complicated to track.

It's something out of our control, we don't have ownership rights over the gqless org / repo, which is why this "fork" was made

Got it!
Could you please point me to a document explaining the reason for this fork?

Got it!
Could you please point me to a document/article/issue explaining the reason for this fork, if there is such a thing?

There isn't one, I just made a quick announcement in the old discord

It would be nice to have some information as to why there's a split, and why should or shouldn't one switch from GQless to GQTY.
I think it would be great if you could please write an explanation at the top of the readme file so that people would know why the change and how we should proceed.
Thanks!

I'm thinking that some kind of roadmap or what's missing can be helpful for new collaborators. If someone wants some feature which can be found on a roadmap - it's easier to start collaboration. I'm big fan of comparison that URQL client has made. Maybe we can decide what of those features are needed or nice to have

authors: PabloSzx huczk nemonemi trevordilley

repo: gqty-dev/gqty


text:
New roadmap

🍰 Pullrequest

Issues

None

Todo

[X] None

@clauspeterhuebner There seems to be a discrepancy between the public and the developer roadmap. I left our meeting early and you might have explained that, but thats what I recognized.

correct some differences between the internal roadmap_V2 and the roadmap_publicity.
summarized the where only some very small formal differences. The roadmap for publicity will only be used informative to create or write a webpage or newsletter.

authors: clauspeterhuebner ulfgebhardt

repo: gradido/gradido


text:
Configure pre-releases as draft to avoid unnecessary notifications

The current GitHub workflow development-release.yml overwrites any current GitHub pre-release on every commit, which is advertised by email/notification while this is actually not really a pre-release per say. Would you be open to test making it a draft pre-release to see if it prevents the notifications for each commit on the main branch?
This would allow us to actually be able to follow "real" releases, and not be notified for each commit.
I'm not sure if this will work, but it is worth a try.
Thanks

Hi, @SimonMarquis! Thank you for the issue and PR. We will discuss this internally.

authors: SimonMarquis erichaagdev


text:
Gradle 7.0.2 no longer will deploy to S3 buckets with a dot and digit and throws NPE

Context
Our organization has been using gradle through the years to build a Java/Scala project. We have proprietary build scripts and staging S3 buckets we use for deploying maven artifacts.
We recently attempted to deploy a release using gradle to an s3 bucket that would follow the pattern ${BUCKET_NAME}-${VERSION_WITH_DOTS}
This was working up till 7.0.2 (Before we were using 6.8.1). It is throwing an NPE exception (version 7.0.2's is bellow):
13:03:59  Caused by: java.lang.NullPointerException
13:03:59  	at org.gradle.internal.resource.transport.aws.s3.S3RegionalResource.getBucketName(S3RegionalResource.java:84)
13:03:59  	at org.gradle.internal.resource.transport.aws.s3.S3RegionalResource.configure(S3RegionalResource.java:73)
13:03:59  	at org.gradle.internal.resource.transport.aws.s3.S3RegionalResource.<init>(S3RegionalResource.java:39)
13:03:59  	at org.gradle.internal.resource.transport.aws.s3.S3Client.putSingleObject(S3Client.java:132)
13:03:59  	at org.gradle.internal.resource.transport.aws.s3.S3Client.put(S3Client.java:124)
13:03:59  	at org.gradle.internal.resource.transport.aws.s3.S3ResourceConnector.upload(S3ResourceConnector.java:85)
13:03:59  	at org.gradle.internal.resource.transfer.ProgressLoggingExternalResourceUploader.upload(ProgressLoggingExternalResourceUploader.java:39)
13:03:59  	at org.gradle.internal.resource.transfer.AccessorBackedExternalResource.put(AccessorBackedExternalResource.java:182)
13:03:59  	at org.gradle.internal.resource.BuildOperationFiringExternalResourceDecorator$3.call(BuildOperationFiringExternalResourceDecorator.java:100)
13:03:59  	at org.gradle.internal.resource.BuildOperationFiringExternalResourceDecorator$3.call(BuildOperationFiringExternalResourceDecorator.java:97)
13:03:59  	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
13:03:59  	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
13:03:59  	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
13:03:59  	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
13:03:59  	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
13:03:59  	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
13:03:59  	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
13:03:59  	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
13:03:59  	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
13:03:59  	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
13:03:59  	at org.gradle.internal.resource.BuildOperationFiringExternalResourceDecorator.put(BuildOperationFiringExternalResourceDecorator.java:97)
13:03:59  	at org.gradle.api.publish.maven.internal.publisher.AbstractMavenPublisher$ModuleArtifactPublisher$1.run(AbstractMavenPublisher.java:272)
13:03:59  	at org.gradle.api.internal.artifacts.repositories.transport.NetworkOperationBackOffAndRetry.withBackoffAndRetry(NetworkOperationBackOffAndRetry.java:50)
13:03:59  	at org.gradle.api.publish.maven.internal.publisher.AbstractMavenPublisher$ModuleArtifactPublisher.putResource(AbstractMavenPublisher.java:269)
13:03:59  	at org.gradle.api.publish.maven.internal.publisher.AbstractMavenPublisher$ModuleArtifactPublisher.publish(AbstractMavenPublisher.java:230)
13:03:59  	at org.gradle.api.publish.maven.internal.publisher.AbstractMavenPublisher$ModuleArtifactPublisher.publish(AbstractMavenPublisher.java:223)
13:03:59  	at org.gradle.api.publish.maven.internal.publisher.AbstractMavenPublisher.publish(AbstractMavenPublisher.java:81)
13:03:59  	at org.gradle.api.publish.maven.internal.publisher.MavenRemotePublisher.publish(MavenRemotePublisher.java:61)
13:03:59  	at org.gradle.api.publish.maven.internal.publisher.ValidatingMavenPublisher.publish(ValidatingMavenPublisher.java:50)
13:03:59  	at org.gradle.api.publish.maven.tasks.PublishToMavenRepository$1.publish(PublishToMavenRepository.java:109)
13:03:59  	at org.gradle.api.publish.internal.PublishOperation.run(PublishOperation.java:43)
13:03:59  	... 121 more

I can provide a larger stack trace, but I don't think its needed as this seems to be a behavior from java.net.URI, which is coming from here: https://github.com/gradle/gradle/blob/v7.0.2/subprojects/resources-s3/src/main/java/org/gradle/internal/resource/transport/aws/s3/S3RegionalResource.java#L73
Expected Behavior
Gradle bellow version 7.0.2 was working with buckets URLs with values s3://my-awesome-bucket-7.0.0/maven, this seems to be a problem now when parsed through java.net.URI.  So this would be classified as a regression of behavior.
Steps to Reproduce
Rather simple java program:
import java.net.URI;
import java.net.URISyntaxException;

class S3URI {
    public static void main(String[] args) {
        try {
            URI uri1 = new URI("s3://my-awesome-bucket-7-0-0/maven");
            System.out.println("Parses Correctly: " + uri1.getHost());
            URI uri2 = new URI("s3://my-awesome-bucket-7.biz/maven");
            System.out.println("Still parses: " + uri2.getHost());
            URI uri3 = new URI("s3://my-awesome-bucket-7.0.0/maven");
            System.out.println("No longer parses: " + uri3.getHost());
        } catch(URISyntaxException e) {
            System.out.println("ERROR" + e.toString());
        }
    }
}

javac S3URI.java && java S3URI
Parses Correctly: my-awesome-bucket-7-0-0
Still parses: my-awesome-bucket-7.biz
No longer parses: null

What do I hope to achieve?
I'm putting in a workaround on my end [1], this is just to log an issue/regression.
[Edit]
Ideally this scenario is checked for (Check if URI.getHost() returns null) and raise a more informative error message such as "invalid bucket name" (even though S3 would accept it as a valid name)
[/Edit]
[1] It was high time we stopped including . in our bucket names which throws off AWS S3's SSL Cert when accessing objects through the DNS endpoint (ie: https://my-bucket.s3.us-west-2.amazonaws.com/my/key)

@andrewegel , I have looked into this and I can confirm the problem you describe. Will work on fixing it.
What is unclear to me is why it has worked for you before, because I can reproduce the same exact NPE with any Gradle and JDK version I try. As far as I can tell, those basket names with dotted versions in them should have never worked... Could you maybe put together a reproducer? Or any ideas on what might be different in your setup?

As far as I can tell, those basket names with dotted versions in them should have never worked... Could you maybe put together a reproducer? Or any ideas on what might be different in your setup?

I had to dig into some crufty code and found something - I think it was working "before" because we were using the org.springframework.build:aws-maven:5.0.0.RELEASE plugin to do the deployment to S3, so in re-reviewing my assumptions here, this isn't a bug in Gradle, because we were never using Gradle's libraries to deploy, and were instead relying on an external maven plugin to do the work, where I guess S3 buckets with dots in the name do work.
I appreciate you putting in a fix for this anyways, but I understand with this new information if you wanted to pull it back out.

@andrewegel thank you for sorting it out. The issue in Gradle is genuine in that it wasn't working as expected, so I think the fix will remain and is useful. A win-win I guess ;)

authors: andrewegel jbartok

repo: gradle/gradle


text:
Gradle 4.1-rc1 fails with Could not initialize class sun.security.ssl.SSLContextImpl$TLSContext

./gradlew test --refresh-dependencies
Parallel execution is an incubating feature.

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'fievel'.
> Could not resolve all files for configuration ':classpath'.
   > Could not resolve gradle.plugin.com.kageiit:jacobo-plugin:2.0.5.
     Required by:
         project :
      > Could not resolve gradle.plugin.com.kageiit:jacobo-plugin:2.0.5.
         > java.lang.NoClassDefFoundError: Could not initialize class sun.security.ssl.SSLContextImpl$TLSContext

Once I can ./gradlew --stop, the command succeeded on the next try

This might be the same issue as described on the forum.
Is this only happening with 4.1-rc1 or does it also occur with older versions of Gradle? Where is the plugin hosted you are trying to download?

I only tried on 4.1-rc1 . Hard to repo now as it happened once and not again after the daemon was stopped.
The plugin is hosted on the Gradle plugins repository

Same bug for me in gradle 4.2.1 with newly installed Java 9. Any solutions ?
------------------------------------------------------------
Gradle 4.2.1
------------------------------------------------------------

Build time:   2017-10-02 15:36:21 UTC
Revision:     a88ebd6be7840c2e59ae4782eb0f27fbe3405ddf

Groovy:       2.4.12
Ant:          Apache Ant(TM) version 1.9.6 compiled on June 29 2015
JVM:          9-Ubuntu (Oracle Corporation 9-Ubuntu+0-9b161-1)
OS:           Linux 4.10.0-35-generic amd64

Is this still happening with Gradle 4.3.1?

@kageiit Does this still happen with the latest version of Gradle?

Have not seen it on 4.3.1 so far

Thanks for the feedback. I am going to close the issue for now. Please let us know if should you see the issue with newer Gradle versions going forward.

I faced the similar issue as well with the Gradle version 4.5.1. It is mentioned below
Could not resolve joda-time:joda-time:2.9.9.

java.lang.NoClassDefFoundError: Could not initialize class sun.security.ssl.SSLContextImpl$TLSContext

I've faced the same issue when building Web Applications using Gradle v4.6.
java.lang.NoClassDefFoundError: Could not initialize class sun.security.ssl.SSLContextImpl$TLSContext
java.base/java.lang.Class.forName0(Native Method)
java.base/java.lang.Class.forName(Class.java:292)

authors: NilsRenaud aloktech bmuschko kageiit legendtang


text:
Building Kotlin Applications Sample is not up to date

Issue type
Missing information
Problem description
In section:
https://docs.gradle.org/current/samples/sample_building_kotlin_applications.html#run_the_init_task
The console output shown (basic Groovy project with Groovy DSL) does not match the newest Gradle version and don't match the code shown later on the page (Kotlin Application with Kotlin DSL)
Context (optional)
I wanted to go through the tutorial and had trouble figuring out whether what I'm doing is correct or not.
Page with the problem
https://docs.gradle.org/current/samples/sample_building_kotlin_applications.html

This is a valid documentation issue.
We welcome documentation contributions. See our contributing documentation guide for more information.

The current doc is outdated. It shows:
$ gradle init

Select type of project to generate:
  1: basic
  2: application
  3: library
  4: Gradle plugin
Enter selection (default: basic) [1..4] 1

Select implementation language:
  1: C++
  2: Groovy
  3: Java
  4: Kotlin
  5: Scala
  6: Swift
Enter selection (default: Java) [1..6] 2

Select build script DSL:
  1: Groovy
  2: Kotlin
Enter selection (default: Groovy) [1..2] 1

Project name (default: demo):
Source package (default: demo):

BUILD SUCCESSFUL
2 actionable tasks: 2 executed

The actual output:
gradle init

Select type of build to generate:
  1: Application
  2: Library
  3: Gradle plugin
  4: Basic (build structure only)
Enter selection (default: Application) [1..4] 1

Select implementation language:
  1: Java
  2: Kotlin
  3: Groovy
  4: Scala
  5: C++
  6: Swift
Enter selection (default: Java) [1..6] 2

Enter target Java version (min: 7, default: 21):

Project name (default: test):

Select application structure:
  1: Single application project
  2: Application and library project
Enter selection (default: Single application project) [1..2]

Select build script DSL:
  1: Kotlin
  2: Groovy
Enter selection (default: Kotlin) [1..2]

Generate build using new APIs and behavior (some features may change in the next minor release)? (default: no) [yes, no]

> Task :init
To learn more about Gradle by exploring our Samples at https://docs.gradle.org/8.7/samples/sample_building_kotlin_applications.html

BUILD SUCCESSFUL in 3m 7s
1 actionable task: 1 executed

@Herudaio, we are currently not maintaining these samples and I am planning on removing them in Gradle 8.10.
The long-term game plan is that I will maintain a repository of selective but fully working sample projects.

Re-opening until PR is merged.

authors: Herudaio lkasso ov7a


text:
Incorrect cache behavior when file name contains special characters

Expected Behavior

Current Behavior
I've turned on caching for some tasks that generate dirnames with special characters, and it seems that the gradle cache is escaping the characters (perhaps using URL encoder?)
Steps to Reproduce (for bugs)
Create the following files:

build.gradle
task badCacheTask(type: Exec) {
  inputs.file('foo.sh')
  outputs.dir("output")
  outputs.cacheIf { true }
  commandLine = ['bash', 'foo.sh']
}

foo.sh (creates a bunch of files with special chars)
bad_dir='output/dir/#/special$char'
bad_file='f!ile .txt'
mkdir -p "${bad_dir}"
echo "foo" > "${bad_dir}/${bad_file}"

run the following:
gradle badCacheTask
mv output good-cache
gradle badCacheTask
tree output good-cache

The output of the above command looks like:
 output
 └── dir
     └── %23
         └── special$char
             └── f!ile%20.txt
 good-cache
 └── dir
     └── #
         └── special$char
             └── f!ile\ .txt

As can be seen in the output above. The actual state of the output dir after cache restoration is not the same as expected.

The cache file contents from the cache key 5a1a4e7a01d4080c60ba674aac2cfd8a are as follows:$ tar -ztvf ~/.gradle/caches/build-cache-1/5a1a4e7a01d4080c60ba674aac2cfd8a
-rw-r--r-- 0/0             342 2017-09-27 21:35 METADATA
drwxr-xr-x 0/0               0 2017-09-27 21:35 property-$1/
drwxr-xr-x 0/0               0 2017-09-27 21:35 property-$1/dir//
drwxr-xr-x 0/0               0 2017-09-27 21:35 property-$1/dir/%23//
drwxr-xr-x 0/0               0 2017-09-27 21:35 property-$1/dir/%23/special$char//
-rw-r--r-- 0/0               4 2017-09-27 21:35 property-$1/dir/%23/special$char/f!ile%20.txt

Your Environment

Build scan URL: https://scans.gradle.com/s/2eytczf3jj74q

Thanks for reporting. Looks like we have a problem handling spaces in cached file names since 4.2.

Looks like we have a problem handling spaces in cached file names since 4.2

I don't believe this is limited to just spaces — in my case the pound character # is also escaped. I don't know if there are other chars are escaped as well.

Indeed, the problem seems to be caused by any character that is escaped in URIs: spaces, percent signs etc.

PR merged.

authors: ketan lptr


text:
Graduate PluginDeclaration.getTags to stable

Expected Behavior
PluginDeclaration.getTags has been incubating since 7.6 and has not changed since. It would be great if it could be used without suppressing incubation warnings.
Current Behavior (optional)
No response
Context
We are using this to publish our Gradle plugin to Gradle plugin portal.

The issue is in the backlog of the relevant team and is prioritized by them.


text:
3.2-rc-2 build fails for multi-level project dependencies

Expected Behavior

./gradlew build should be successful.
Current Behavior

Build fails with unresolved reference compilation error.
It looks to affect at least Kotlin projects using Gradle 3.2-rc-2 with 2 levels of project dependencies, i.e., project-a -> project-b -> project-c. The same project works fine with Gradle 3.2-rc-1.
I did try with the project converted to Java and that worked fine with both Gradle 3.2-rc-1 and 3.2-rc-2.
Context

I have been trying out Kotlin as a language to develop in. At the same time, I started looking at using Gradle Script Kotlin for my build scripts. I was hoping to upgrade from Gradle 3.1 to 3.2 as soon as possible as I know it will include a fix for Gradle Script Kotlin on Windows.
Steps to Reproduce (for bugs)

Example project: https://github.com/jonathan-yan/example-broken-gradle-3.2-rc-2-multi-project
Run ./gradlew build

Your Environment

Windows 10 (64-bit)
Oracle JDK 8u112 (64-bit)

@jonathan-yan Thanks for reporting the issue. We are currently looking into it.

The offending commit is ad1a7fbed7e6088a88845c7da4a4e396e6826f29. The new logic is somehow interacting badly with the task configuration created by KotlinPlugin.

Do we have a stacktrace of the failure? I will start looking into it now.

@lacasseio In case you were still waiting for the stacktrace (though you probably have already got it by running the example that I provided):
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':project-a:compileKotlin'.         at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:84)         at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:55)         at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:61)         at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)         at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:88)         at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:45)         at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:51)         at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)         at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)         at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)         at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:233)         at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:215)         at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:74)         at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:55)         at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor.process(DefaultTaskPlanExecutor.java:32)         at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter.execute(DefaultTaskGraphExecuter.java:113)         at org.gradle.execution.SelectedTaskExecutionAction.execute(SelectedTaskExecutionAction.java:37)         at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:37)         at org.gradle.execution.DefaultBuildExecuter.access$000(DefaultBuildExecuter.java:23)         at org.gradle.execution.DefaultBuildExecuter$1.proceed(DefaultBuildExecuter.java:43)         at org.gradle.execution.DryRunBuildExecutionAction.execute(DryRunBuildExecutionAction.java:32)         at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:37)         at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:30)         at org.gradle.initialization.DefaultGradleLauncher$4.run(DefaultGradleLauncher.java:197)         at org.gradle.internal.Factories$1.create(Factories.java:25)         at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)         at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:53)         at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:194)         at org.gradle.initialization.DefaultGradleLauncher.access$200(DefaultGradleLauncher.java:36)         at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:118)         at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:112)         at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)         at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:63)         at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:112)         at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:98)         at org.gradle.launcher.exec.GradleBuildController.run(GradleBuildController.java:66)         at org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28)         at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)         at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:41)         at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:26)         at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:75)         at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:49)         at org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute(ServicesSetupBuildActionExecuter.java:44)         at org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute(ServicesSetupBuildActionExecuter.java:29)         at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:51)         at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:173)         at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:244)         at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:217)         at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:33)         at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)         at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)         at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)         at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:210)         at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:174)         at org.gradle.launcher.Main.doAction(Main.java:33)         at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)         at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:60)         at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:37)         at org.gradle.launcher.GradleMain.main(GradleMain.java:23)         at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:31)         at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:108)         at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61) Caused by: org.gradle.api.GradleException: Compilation error. See log for more details         at org.jetbrains.kotlin.gradle.tasks.KotlinCompile$callCompiler$10.invoke(Tasks.kt:406)         at org.jetbrains.kotlin.gradle.tasks.KotlinCompile.callCompiler(Tasks.kt:419)         at org.jetbrains.kotlin.gradle.tasks.KotlinCompile.callCompiler(Tasks.kt:151)         at org.jetbrains.kotlin.gradle.tasks.AbstractKotlinCompile.execute(Tasks.kt:117)         at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73)         at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$IncrementalTaskAction.doExecute(DefaultTaskClassInfoStore.java:163)         at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:134)         at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:123)         at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:95)         at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:76)         ... 61 more

Thanks @jonathan-yan, I was able to reproduce. Currently debugging.

This issue was fixed and code review in master and release. It will be included in Gradle 3.2-rc-3.

Just tried with Gradle 3.2-rc-3 and it works like a charm. Thanks.

authors: bamboo bmuschko jonathan-yan lacasseio


text:
Return same SnapshotHierarchy when nothing was invalidated

So we can rely on SnapshotHierarchy being the same instance when nothing changes. We use this currently when printing the warning at the end of the build whether we dropped unsupported file systems.

@bot-gradle test QF

OK, I've already triggered QuickFeedback build for you.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

OK, I've already triggered a build for you.

authors: bot-gradle wolfs


text:
Bump version for removing validation warnings to 9.0

We changed all warnings for 8.0 into errors already, the warnings from the 8.x line should be turned into errors in 9.0.
Fixes #21648.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


text:
Support @Option with task properties of type ListProperty and SetProperty

Fixes #10517

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test and merge

I've triggered a build for you. Click here to see all failures if there's any.

Pre-tested commit build failed. Click here to see all build failures.

@bot-gradle test and merge

I've triggered a build for you. Click here to see all failures if there's any.

authors: FrauBoes bot-gradle


text:
Set implementation version in the manifest to the base version

This is one step to improving cacheability of the Gradle build. Note that I had to create a separate task to configure the jar manifest in launcher since the build failed using a cached version without the right Class-Path attribute in the Manifest causing the distribution to be broken (build scan).
That is one of the parts of #754.

LGTM

authors: big-guy wolfs


text:
Configure metrics exporter for loadbalancing when possible

PR Description
Metrics support was turned off in otelcol.exporter.loadbalancing for two reasons:

metrics support is considered development upstream
the metrics exporter crashed when configured with the default routing_key = traceID

Solve both issues by supporting metrics only if the specified routing_key supports it and stability level is set to experimental
Which issue(s) this PR fixes

Notes to the Reviewer
PR Checklist

[x] CHANGELOG.md updated
[ ] Documentation added
[ ] Tests updated
[ ] Config converters updated

Does this need a doc update in https://grafana.com/docs/alloy/latest/reference/components/otelcol/otelcol.exporter.loadbalancing/ ?

Does this need a doc update in https://grafana.com/docs/alloy/latest/reference/components/otelcol/otelcol.exporter.loadbalancing/ ?

I have now added a doc update to the PR

authors: clayton-cornell madaraszg-tulip

repo: grafana/alloy


text:
Small typo in the documentation

What happened:
Hi,
First of all, thanks for your work great on this Datasource plugin. I'm starting to using and it's really powerful !
I'm opening this ticket because there is a small typo in the documentation (https://grafana.com/grafana/plugins/grafana-athena-datasource/) :
$__rawtimeFrom() => $__rawTimeFrom()

I lost a lot of time to understand why it was not working so it can maybe prevent other people to do the same. And I found the solution thanks to this ticket: https://github.com/grafana/athena-datasource/issues/149
What you expected to happen:
$__rawtimeFrom() => $__rawTimeFrom()

in the documentation
How to reproduce it (as minimally and precisely as possible):

Screenshots

Anything else we need to know?:
Environment:
Useless information I think

Grafana version:
Plugin version:
OS Grafana is installed on:
User OS & Browser:
Others:

thanks for reporting this @CharlesBlonde! maybe you can open a quick PR updating the docs?

Please review for any changes :)

Thanks for the fix and it has been fixed to quickly by @PrajwalBorkar  I wasn't able to do the PR :)
Nevertheless, I didn't realized the typo root source was README.md...
I was personally  using this page as documentation and not the Github README. I guess it will be updated with the next release ?

I was personally using this page as documentation and not the Github README. I guess it will be updated with the next release ?

That's correct :+1:

authors: CharlesBlonde PrajwalBorkar andresmgot

repo: grafana/athena-datasource


text:
Add support for Azure Monitor Log Analytics

[x] Integrate the Monaco editor
[x] Integrate the KustoDB Language Service to get intellisense
[x] Add a new option for Log Analytics and integrate the Log Analytics API
[x] Support parsing the data into time series format
[x] Support parsing the data into table format
[x] Documentation
[x] Support switching Workspace in the query editor
[x] Have Run button like the analytics portal has
[x] Show the raw query after executing
[x] Slim down the Monaco editor js file by removing unneeded features (currently 8MB uncompressed)
[x] Use the /metadata endpoint to get the schema (/query/schema will be deprecated) and for multiple databases/solutions put into one virtual database for the intellisense schema.
[x] Investigate which AAD role is needed and document it.
[x] Improve Intellisense for Grafana macros - getting double entries in the list sometimes.
[x] Template variable support
[x] Annotation support
[x] Handle Esc button when in monaco editor.
[ ] Support for Azure Gov
[x] Monaco Code Editor refactoring
[ ] Add throttling support when autorefreshing (use the API to find out when requests are throttled and wait for the retry-after period)
[x] Add message that it requires Grafana 5.3.

This is done except for:

Going to test it with multiple workspaces
Documentation for template variables and annotations.

can you tell me if log analytics support in grafana is currently available or only azure monitor resources and application insights? any estimate when is going to be ready?

@cfarre log analytics support is not available yet - I am waiting for the green light from Microsoft's legal department on an open source License for a Kusto component (Kusto is the database used by log analytics).
So I have no idea how long that will take but hopefully soon as they are starting to test a preview version with some customers this week.

Hello, thank you very much for Grafana! Let me please ask: can we use log analytics queries directly to define the chart legends in terms of resource tags for example? is there an alternate way to achieve this?

Is this live ?

@cconrado hopefully this week - the license issue is now resolved.

Any update on when this will be publicly available?

This is now published with the Azure Log Analytics support marked as being in preview.

@daniellee
we are doing a project based on log analytics and grafana. do you know when this will be publicly available?

@cfarre it is already publicly available. Support is included in the latest release.

@daniellee can you send me install instructions. I cannot find any doc from MS. I followed manual instructions in https://github.com/grafana/azure-monitor-datasource/blob/master/README.md we tested this release and are having performance issues, plus other function problems.

@daniellee this is the problem I am facing. Any query I am running it hangs the UI in grafana to the point is unresponsive. The queries run correctly on azure portal
this is the simple query we are testing going back 30 minutes. what is the best channel to discuss those issues? is there something we are doing incorrectly?
SparkMetric_CL
| where name_s contains "driver.DAGScheduler.job.allJobs"

@daniellee this is the problem I am facing. Any query I am running it hangs the UI in grafana to the point is unresponsive. The queries run correctly on azure portal
this is the simple query we are testing going back 30 minutes. what is the best channel to discuss those issues? is there something we are doing incorrectly?
SparkMetric_CL
| where name_s contains "driver.DAGScheduler.job.allJobs"

You may need a filter on timestamp.
| where $__timeFilter()
will use the time range selected in grafana

@cfarre the portal automatically adds a time filter clause to any query which Grafana does not so @JamesHealey94 is correct you should always add a time filter.

@daniellee @JamesHealey94
Ok I fixed this issue. now I have another question. we have multi variables template and we are trying to use $__escapeMulti($myVar) or $__contains(colName, $myVar) but the macros do not work on our grafana

@cfarre could you provide some more information?
What does the raw query look like? And what does your template variable definition look like?

@cfarre - don't know if it's your issue, but I've got a problem with $__contains macro, which I've raised in #84

@daniellee
we have developed a dashboard to monitor spark clusters. Below is one of our queries. Is it possible to parameterize the SparkListenerEvent_CL? additionally can you point me to deployment automation of grafana and dasboards? I would like to automate a deployment script that installs grafana, sets up the datasource and installs the dashboards.
SparkListenerEvent_CL
| where $__timeFilter(TimeGenerated)
| where Event_s contains "queryprogressevent"
| extend sname=strcat(progress_name_s,"-","triggerexecution")
| summarize percentile(progress_durationMs_triggerExecution_d,90)  by bin(progress_timestamp_t, 1m), sname
| order by  progress_timestamp_t  asc  nulls last

authors: JamesHealey94 cconrado cfarre daniellee fernandrez samhodgkinson tjmoore

repo: grafana/azure-monitor-datasource


text:
Richer diff when running cortextool diff|sync

Right now, when you use the diff command it will only tell you which groups are going to be changed, but does not tell you which individual rules/alerts are changing.
I would be good to have an idea of what exactly is changing when you run this or the sync command.

To expand on this, it seems that running sync/diff after syncing will also result in updates - I would have expected this to no-op.

take a look at this line: https://github.com/grafana/cortex-tools/blob/35691e0471880e9eb20562207976c5861df26455/pkg/rules/compare.go#L215

trying to figure out how to increase verbosity with a flag

@gotjosh it is forced to false always: https://github.com/grafana/cortex-tools/blob/35691e0471880e9eb20562207976c5861df26455/pkg/commands/rules.go#L491

@gotjosh putting an pull request soon. sorry for spamming your @

authors: gotjosh justinTM

repo: grafana/cortex-tools


text:
Add 'indent' option, output arguments instead of command

The compile_commands.json file supports an 'arguments' list instead of a single 'command' string. The forms both valid, but arguments is preferred since it reduces problems with string escaping and can be easier to parse. It should also be a little faster since it avoids unnecessary string concatenation.
For users that may want a human readable file, I've added an 'indent' option which adds line breaks and standard indentation to the json output, making it more legible.

This project is being archived. Apologies I did not get to this PR sooner.
Thank you for your interest and contribution.

authors: siddharthab yeswalrus

repo: grailbio/bazel-compilation-database


text:
Connection Error (api project)

Hi
I am running a latest neo4j 4.x.x database in docker container.  I can connect from neo4j browser without any issues(create, delete, fetch etc... all works) with bolt driver but not able connect to from the node js grandstack api project.
NOTE: It was working fine with the older version and I have upgraded the database and downloaded the latest API code from this repo.
ERROR #1:  Please ensure that your database is listening on the correct host and port and that you have compatible encryption settings both on Neo4j server and driver. Note that the default encryption setting has changed in Neo4j 4.0. Caused by: connect EADDRNOTAVAIL 255.255.255.255:7687
Another issue: After default installation of the GRAND stack(out of the box) on windows OS, npm start is giving me an error as below. I had to split the commands( in windows bash (build separately then copy..)  and run to make it to work (work around)
ERROR #2:
: Successfully compiled 6 files with Babel.
The system cannot find the path specified.
':' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! grand-stack-starter-api@0.0.1 build: babel src --out-dir build && shx cp .env build 2>/dev/null || : && shx cp src/schema.graphql build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the grand-stack-starter-api@0.0.1 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Shashikanth.r\AppData\Roaming\npm-cache_logs\2020-06-13T23_38_32_349Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! grand-stack-starter-api@0.0.1 start: npm run build && node build/index.js "run"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the grand-stack-starter-api@0.0.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Shashikanth.r\AppData\Roaming\npm-cache_logs\2020-06-13T23_38_32_427Z-debug.log

It was my mistake....After checking the DB logs in the containers, I found that APOC  plugins were missing. Its all working fine. I am closing this.  Thanks

repo: grand-stack/grand-stack-starter


text:
If CH vehicle profile is not the first the access limits are not considered

It seems that a CH profile which is on the second rank of a profile list or later does not take access limits into account. Disabling CH helps and also moving it to the first rank of the profile list. This problems is independent of the used graph.bytesForFlags
Hmmh, cannot reproduce this in a test environment, seems to be something different ...

Ok, strange. This is something specific to a custom encoder. It does not look like the same problems happen for e.g. car. Hmmh, still we need to improve the API to avoid this for custom encoders.

Arg, it is a duplicate of #490 and the reason is the 'contains' ... e.g. think about the names 'car' vs. 'electric_car' ...

repo: graphhopper/graphhopper


text:
Avoid Pattern compilation

The old code would need to compile two Pattern instance for each call of simpleXMLEscape() as String.replaceAll() requires that a Pattern is compiled on each call. The PR switches one of the replaceAll() calls to a simple replace() as it doesn't require regex functionality. The other one is compiled once and gets reused.

Did you have a problem in production due to this?

The PR switches one of the replaceAll() calls to a simple replace() as it doesn't require regex functionality.

:+1:

Just Sonarlint screaming on top of its lungs :smile:

Any objections?

Thanks

authors: easbar karussell otbutz


text:
Installing graphite-carbon unattended

I'm trying to create an automation script that install Graphite on Ubuntu 14.04 without user interaction (unattended).
I try with the following command:
sudo apt-get -q -y --force-yes install graphite-carbon=0.9.12-3

During the installation, I will be asked whether I want Carbon to remove the database files.
Do you know if there is a way to run an installation without these kind of UI? I have only this problem with Graphite-carbon.
I have also tried using
export DEBIAN_FRONTEND=noninteractive

without success.
What is the best way to install graphite-carbon without user interaction?

And there's always:
echo "graphite-carbon graphite-carbon/postrm_remove_databases boolean false" | sudo debconf-set-selections

repo: graphite-project/carbon


text:
Release 1.0.2

IMO it's time to release 1.0.2 to the public.
Maybe you know some patches or bugfixes which should be backported from master to 1.0.x before baking 1.0.2?
For whisper I'm going to check @piotr1212 commits for some fixes beside python3 support (I think we need to release py3 a bit later, in 1.1.0)
For carbon - the same. Should we include DYNAMIC_ROUTER support to 1.0.2 ?
/cc @iksaif @DanCech @cbowman0 @drawks
@graphite-project/committers

Nop, I would not include DYNAMIC_ROUTER in 1.0.2 :)

Release is done, release documentation also updated - https://github.com/graphite-project/graphite-summit/wiki

:+1:

authors: deniszh iksaif

repo: graphite-project/graphite-web


text:
go-carbon stopping to pull metrics and showing below erroe

go-carbon stopped to show metrics and showing below error everytime I need to restart go-carbon service to work fine can u please help regarding this @deniszh
Jul 28 01:06:03 ip-10-0-250-82 sh[16094]:     os.rename(self.baseFilename, dfn)
Jul 28 01:06:03 ip-10-0-250-82 sh[16094]: OSError: [Errno 2] No such file or directory
Jul 28 01:06:03 ip-10-0-250-82 sh[16094]: Logged from file logger.py, line 88
Jul 28 01:56:37 ip-10-0-250-82 sh[16094]: Traceback (most recent call last):
Jul 28 01:56:37 ip-10-0-250-82 sh[16094]:   File "/usr/lib/python2.7/logging/handlers.py", line 77, in emit
Jul 28 01:56:37 ip-10-0-250-82 sh[16094]:     self.doRollover()
Jul 28 01:56:37 ip-10-0-250-82 sh[16094]:   File "/usr/lib/python2.7/logging/handlers.py", line 350, in doRollover
Jul 28 01:56:37 ip-10-0-250-82 sh[16094]:     os.rename(self.baseFilename, dfn)
Jul 28 01:56:37 ip-10-0-250-82 sh[16094]: OSError: [Errno 2] No such file or directory
Jul 28 01:56:37 ip-10-0-250-82 sh[16094]: Logged from file logger.py, line 88

please help @deniszh its production server

s


text:
Warn about BigDecimal limitations

The documentation currently states that BigDecimal has arbitrary precision, but it does not.
For example, trying to represent the value 2 ** 256 - 1 in a BigDecimal as follows:
const value = BigDecimal.fromString('115792089237316195423570985008687907853269984665640564039457584007913129639935');

will result in the following value being stored:
115792089237316195423570985008687900000000000000000000000000000000000000000000

Only the most significant 34 digits have been preserved, and it turns out that this is due to BigDecimals internally being stored in IEEE-754 decimal128 floating-point format, which supports 34 decimal digits of significand.
This makes BigDecimal unsuitable for representing fixed-point types that can span wider than 34 digits, such as a Solidity ufixed256x18 or equivalent.
I think this could catch smart-contract developers unawares.
At first I was thinking of trying to fix, but after tracing the issue down to the Rust level, I decided to settle on a warning in the docs :slightly_smiling_face:

Thanks!

repo: graphprotocol/docs


text:
Continue of discussion re issue 140

Please check my comment at https://github.com/graphql-java-generator/graphql-maven-plugin-project/issues/140

Follow up for issue #140:
Based on this schema:
type Query {
    foo: Foo
}

interface IBar {
    name: String
}

interface I2Bar implements IBar {
    name: String
}

type Bar implements I2Bar & IBar {
    name: String
}

interface IFoo {
    bar: IBar
}

interface I2Foo implements IFoo {
    bar: I2Bar
}

type Foo implements I2Foo & IFoo {
    bar: Bar
}

The plugin generates:
	public interface IFoo {
		public void setBar(IBar bar);
	}

	public interface I2Foo extends IFoo {
		public void setBar(I2Bar bar);
	}

Once this is generated,  Java class that inherits from I2Foo must implements both setters, like this:
	public class Foo implements I2Foo, IFoo {
		@Override
		public void setBar(IBar bar) {
			// TODO Auto-generated method stub
		}

		@Override
		public void setBar(I2Bar bar) {
			// TODO Auto-generated method stub
		}
	}

This is a java constraint.
In your proposal, the Foo class should have only the setBar(IBar bar).
I can not accept this: this setter allows invalid data to be created (if setBar is called with a non-I2Bar instance). My strong opinion is that the generated code must stick to the GraphQL schema. So, if only one setter exists, it must be the setBar(I2Bar bar).
And, as you've making me thinking about it, I found a way to avoid it: having a default implementation for the setBar(IBar bar) method in the generated I2Foo interface:
	public interface IBar {
		public void setName(String name);
	}

	public interface I2Bar extends IBar {
		@Override
		public void setName(String name);
	}

	public class Bar implements I2Bar {
		@Override
		public void setName(String name) {
			// TODO Auto-generated method stub
		}
	}

	public interface IFoo {
		public void setBar(IBar bar);
	}

	public interface I2Foo extends IFoo {
		@Override
		default public void setBar(IBar bar) {
			if (bar == null || bar instanceof I2Bar) {
				setBar((I2Bar) bar);
			}
			throw new IllegalArgumentException(
					"The 'bar' parameter should be an instance of 'I2Bar', but is an instance of '"
							+ bar.getClass().getName() + "'");
		}

		public void setBar(I2Bar bar);
	}

	public class Foo implements I2Foo, IFoo {
		@Override
		public void setBar(I2Bar bar) {
			// TODO Auto-generated method stub
		}
	}

I'll see to integrate it in a next release.
Etienne

Not sure how much I agree with the issue of allowing invalid data to be created as there is a validation within the setter implementation re the type of the value being set same as done in the generated code now, also, nothing prevents from the programmer to invoke wrong setter in currently generated code as well.
Furthermore, while I do agree generated code should reflect the schema as much as possible, I don't think setters in the interfaces are required to achieve it but only getters are enough because schema defines what fields of (interface) type you can get(!) and the setters can be generated only on the real type...
In a more complex structure, when one want a more grained control of the types, if one chooses to implement interfaces with his own types (instead of using the generated pojos), setters might be totally redundant for him in case the type holds some more complex data structure (not necessarily reflected in schema at all) and getters can return some aggregated / computed data on top of the data in the pojo, consider the following (simplified) example:
	public interface IBar {
		// redundant
		public void setName(String name);

		// this is the only thing really defined in the gql schema
		public String getName()
	}

	public interface I2Bar extends IBar {
		// redundant
		@Override
		public void setName(String name);

		// this is the only thing really defined in the gql schema
		public String getName()
	}

	public class MyCustomNotGeneratedBar implements I2Bar {
		String firstName;
		String lastName;

		// redundant because firstName & lastName was somehow populated with pojo creation
		@Override
		public void setName(String name) {
			// TODO Auto-generated method stub
		}

		public String getName() {
			return firstName + " " + lastName;
		}
	}

I disagree here.
The issue is not just to mark that the interface possesses one attribute. It's also to allow standard use cases.
And the setter is one of the two standard methods for a property. The generated code must have it.
For instance, with this star wars schema:
interface characters {
  id: String!
  name: String!
}

query {
  characters: [Character]
}

mutation {
  updateCharacters(c: Character): Character
  updateCharacter(c: [Character!]!): Character
}

A normal use is to retrieve the character's list, update the name (or whatever other property), then update them back on the server.

authors: DimaSol etienne-sf


text:
improve: remove resolver shorthands

closes #582
As discussed. In most cases resolver shorthands are not a serious use of the API.
I probably missed areas of the codebase that can be simplified as a result. In particular the parts in the builder module that need to do runtime checks. Also maybe something about typegen?
TODO

[ ] Update docs

Just noticed the tests are failing 😅 will fix

@tgriesser could you point me to the builder code. I actually couldn't find it the first time around when trying to remove runtime support for it.

@jasonkuhrt here https://github.com/graphql-nexus/schema/blob/9bfdf2cdc55d962ba89422f14ec4ecb11ec2bfa2/src/definitions/definitionBlocks.ts#L154-L170

@Weakky or @tgriesser any idea what's up with the failing tests? Not from this PR looks like. Trying to fix anyways.

Hey @Weakky and @tgriesser ready for re-review I think!

@jasonkuhrt I think the CI errors are related to @tgriesser's last commit, but I can't fix it either. Even after updating the snapshots, the errors persist :(

@Weakky ok we'll deal with it later, the tests were passing locally before so let's assume that's enough here.

authors: Weakky jasonkuhrt

repo: graphql-nexus/schema


text:
Add a rename_all macro attribute

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
I find the serde macro #[serde(rename_all = "camelCase")] really useful on a day to day basis. I think it would be nice to have the same thing in juniper.
Describe alternatives you've considered
Wiriting #[graphql(name = "fieldName")] on evry single field
Additional context
serde reference https://serde.rs/attr-rename.html
I'm not that much an advanced rust user, I can try send a PR but I'm not very confident with
proc_macros code.

Looks like on master all fields are automatically converted to camelCase now.
I guess we can close this?

repo: graphql-rust/juniper