text:
[PH] Update library phone numbers for philippines

Dear libphonenumber master,
There are several phone numbers prefix has not been updated for Philippines:

63978
63940
63992
63911
63913
63981
63951
63970
63941
63944
63924
63931
Can kindly update these phone numbers? Thanks!

Complete List:

@melvin-shopee,
Thank you for taking the time to improve libphonenumber!
Please see our guidelines for providing evidence.
We cannot accept screenshots as evidence. In particular, we request a publicly available URL or that you sign the CLA and (after getting whitelisted) share non-public evidence with the mailing list only
readable by core team members.

Hi @kkeshava!
Thanks for replying. I get the lists from here: [http://www.prefix.ph/smart-users/updated-complete-list-mobile-prefixes-philippines-2017/]
Is this enough for the evidence?
Thanks!
Regards,
Melvin Fonda

@melvin-shopee,
We need official evidence like a national numbering plan, announcements from mobile carriers, news articles etc. Please see our guidelines for provide authoritative evidence.

@melvin-shopee
I'm closing as this issue is infeasible for us to fix at this point (we need
more information). Please re-open if you respond so we pick up on it.

authors: kkeshava melvin-shopee penmetsaa


text:
Let defined_characters take a string or a float.

Passing a string instead of a float caused no errors but returned bad
(but not obviously bad) results.  This seemed as reasonable as raising
an error would have.

PTAL

LGTM

source: gharchive/pull-request

authors: dougfelt jamesgk

license_type: permissive

license_source: bigquery


text:
Feature writers API

this is the follow-up of https://github.com/googlei18n/ufo2ft/pull/156
I would like to merge this to master first before I proceed to work on the dist feature writer (#176), otherwise there's too much stuff on the plate.
the differences from Denis' previous PR are:

the new subpackage is called featureWriters in plural (contains the base class and the writer default implementations);
The interface of feature writer classes was modified, the same writer object can now be reused for multiple fonts. Look at the docstring of BaseFeatureWriter class for more info.
the compile functions take a featureWriters keyword argument that by default is set to None (which means "use ufo2ft default list of writer classes with default options"), or optionally a list of feature writer classes (subscribing to the same interface defined in BaseFeatureWriter) or instances that have been pre-initialized with particular options.
I kept the old kern/mark feature writer modules as aliases that import * from the ones that were moved to the new featureWriters package, and I also kept the existing keyword arguments in the compile funcs, to avoid breaking backward compatibility; a deprecation warning is issued but they will continue to work for a while.

other misc changes:

a temporary file is written with the content of the auto-generated feature so that if there's any syntax error in there, we can inspect that; the temp file is cleaned up on successful compilation
I realized that the current mark feature writer was not writing the rules in a deterministic order in python3, because it was relying on the __iter__ method of defcon Font (for glyph in font) which iterates over the glyph objects in an unsorted order (internally uses dict.keys()). I fixed that by using the glyphOrder (or alphabetic) when looping over the glyphs in the mark feature writer.

@googlebot it's all good.

@anthrotype maybe the featureWriters list could also be loaded from a UFO lib key? What do you think?

Yes I was thinking about something like that, similar to the custom filters.

I'm thinking of adding a new UFO lib element called "com.github.googlei18n.ufo2ft.featureWriters" that is a plist array of strings. Each strings contains the module where the feature writer class is defined, then two colons :: and the the class name; optionally, also a list of keyword arguments (evaluated as python syntax) that is used to instantiate the feature writer (if these are not present, the default options are used). This list is loaded by the FeatureCompiler which will call the writer.write(ufo) method in the order in which the feature writers are listed here:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>lib</key>
	<dict>
		<key>com.github.googlei18n.ufo2ft.featureWriters</key>
		<array>
			<string>ufo2ft.featureWriters::KernFeatureWriter(mode="append", ignoreMarks=False)</string>
			<string>myPrivateTools.featureWriters::MarkFeatureWriter</string>
			<string>myPrivateTools.featureWriters::FooFeatureWriter(bar={1, 2, 3})</string>
		</array>
	</dict>
</dict>
</plist>

I can also add a --feature-writer option to fontmake that takes one of these module_name::class_name(**kwargs) strings on the command line and overrides the ufo2ft defaults (basically replacing the current --kern-writer-module and --mark-writer-module which are too narrow in scope).
wdyt @moyogo ?

Sounds great!
On Thu, 7 Dec 2017, 17:45 Cosimo Lupo, notifications@github.com wrote:

I'm thinking of adding a new UFO lib element called
"com.github.googlei18n.ufo2ft.featureWriters" that is a plist array of
strings. Each strings contains the module where the feature writer class is
defined, then two colons :: and the the class name; optionally, also a
list of keyword arguments (evaluated as python syntax) that is used to
instantiate the feature writer (if these are not present, the default
options are used). This list is loaded by the FeatureCompiler which will
call the writer.write(ufo) method in the order in which the feature
writers are listed here:

lib

com.github.googlei18n.ufo2ft.featureWriters

ufo2ft.featureWriters::KernFeatureWriter(mode="append", ignoreMarks=False)
myPrivateTools.featureWriters::MarkFeatureWriter
myPrivateTools.featureWriters::FooFeatureWriter(bar={1, 2, 3})

I can also add a --feature-writer option to fontmake that takes one of
these module_name::class_name(**kwargs) strings on the command line and
overrides the ufo2ft defaults (basically replacing the current
--kern-writer-module and --mark-writer-module which are too narrow in
scope).
wdyt @moyogo https://github.com/moyogo ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/googlei18n/ufo2ft/pull/178#issuecomment-350042380,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB1ao2DXLIQZumcOQO5GWzkk8DuVBJlBks5s-CQmgaJpZM4Qokvv
.

authors: anthrotype moyogo

license: mit


text:
Unity 5.2.2f / SDK 0.5.2 - Renderproblems distortion / Startglitch / missing Gui Elements

My App starts in portrait mode, let the user browse through menues, vr mode is startet later.
My short setup (similar as in a recent issue from me), which you recommended:

a Cardboard object (just cardboard.cs) in scene
in the inspector for the Cardboard component, VRModeEnabled = off.
the prefab is added later, a prefab without the cardboard component

primary Bugs/Problems (Android):

directly after splash screen there is a frame where the alignment marker and settings button appear = Startglitch
If have enabled the settings button and the back button... but they're not visible. Only sometimes, very randomly.
When I press home and then resume to the app, many bugs appear: random crashes and many distortion problems, sometimes the back and settings button appear suddenly, sometimes not... I append a screenshot with some samples... all taken within 5min in the same app version on a samsung s6.

One note: In editor everything works fine, exept when I switch to other windows and refocus... very seldom I get a null reference from Cardboard.cs line 627 from OnApplicationFocus() - maybe this could be also the reason for some crashes on android... hope this helps.
For all other points I'm looking forward for solutions, advices or maybe I can help to make it more stable.

For picture#1, make sure the main camera's background color has is fully opaque (alpha is turned all the way up).
For the start glitch, try setting the Enable checkboxes for each UI element to false.  Wait till you enable VR mode to turn them on.  This may affect the visibility bug you sometimes see.
I'm not sure that will fix ask the pause/resume issues.  For those, cash you see anything in the adb logcat?

I took the cameras from the prefab, the only settings I changed are the clipping planes to 0.01. And I set the toggle culling mask @ cardboard eye script.
I tried your advice and turn the settings and back button off and after instantiate to on, but this doesn't help. The glitch is still there.
I also changed the cameras to solid black color, the distortion bugs seem to disappear, but difficult to say, they're not constant bugs.
Meanwhile switched to 5.2.2 - I'll also change the title. I still try to figure out from where the crashes come... The app never crashes after first start. When I go to pause (via home button) and then return a crash is very likely, but not always...

First problem might be if you have another camera (which is not related to cardboard) in your scene. Problem with cardboard UI (settings button) i have it too.

I've to correct me: the setup of your scene doesn't matter. The startglitch is always there... it just isn't so obvious, when the settings/alignment/back button stays there, because your app starts with vr mode enabled... even if you just turn off vr mode from one of the prefabs (single cam mode) and so also the gui elements should be not visible, there is also a short frame between loading and your scene... so all in all it just would be cool to have more control or possibilities to divide between menue/app stuff and a vr mode... besides: this is the app I'm talking about: https://play.google.com/store/apps/details?id=com.mikavaa.vrais

Same, startglitch,  checkboxes are unchecked, and  i've also set the : EnableAlignmentMarker = false; and EnableSettingsButton = false; by code, but nothing the glitch remain. I've noted that this appear only on the Android build. On iOS after setting the values to false from  the code  all it's ok .

I have the same problems. App always crashes and no ui elements on the screen. DId you solve your problem?

No, I haven't a solution and even not an idea what else to try... in my eyes, the sdk needs definitly an update. I have another bug sample, which makes everything even more confusing for me. I have two cardboards V2.0... one from Zaak, one from google via a conference (the cardboards have been sponsored by google)... when I configure the viewer I get very different lens distortion... and the one from zaak seem to be correct. I have no idea why and I also remember, that both cardboards had the same correct distortion two weeks ago. These test are from Moto x 2nd. But on a samsung s6 I've seen same problems,,,, for better understanding see image attached below:

The SDK definitely needs an update -- there are several bugs already on the list of what needs to be fixed, including the start glitch.  I'm not allowed to say anything about when new releases are scheduled though :(

So this is good and bad news... good, because I stop thinking about fixing these issues and if they are're caused by me, bad, that I've no idea when I can say to our customers (even more for myself): Now I have an reliable vr mobile workflow with untiy + google sdk... looking forward the update. Is there maybe a source you can tell me/us from where we get the latest news about such update?

We can still try to find a workaround for you with the current SDK too.  Also, I typically come back through these issue posts and say when a new release is available if it has a fix for that issue.

Hey everyone,
I'm fighting the startglitch to. I even commented out the GL rendering code in CardboardPostRender.cs.
Unfortunately even then the alignment marker is appearing in the glitch at the startup and even after that.

As far as i understand this GL is drawn only on devices that don't support native UI. In other way marker and other elements are generated from android plugin.

As simple workaround for missing gui elements, maybe interessting for someone:

disable settings/back button in cardboard.cs
in CardboardPreRender.cs set camera.depth from 100 to 99 for example
use your own gui cam on depth 100 with similar icons/buttons and use anchors for position (in my case ngui, but unity ui should also work)
call Cardboard.SDK,ShowSettingsDialog() and what you want on back button

To prevent some crashes I would like to quit the app, if the user pauses the app. I know, not best pratice, but most crashes (maybe all, and with no debug logcat output) happen after resuming the app. But when I want to use this code for example:

I just wanted to add that we're facing the same startup glitch bug and have tried all suggestions listed here. SDK 0.5.2 Unity 5.2.2p4

OK, sorry for the long absence from this thread.  @HansBernd The GL rendering code in CardboardPostRender.cs is only for when you run the game in the editor.
The "start glitch" is due to the native Java code that creates the UI elements.  It has their visibility set initially to "on", and only after that does the Cardboard SDK get a chance to turn them off.  So you can see a flicker.  As we see, this is a hard problem to work around from the Unity level.

So than isn't it possible that someone, who is able to, change (I assume unityvractivity.jar) the java code and set visibility initially to "off"?
Another important fix would be, that we can quit the app properly as described 3 posts above without timeout... that would make a more or less stable release possible.

Yes, changing the Java code would work.  (I counted Java as "native" code because of the need to marshal calls from .NET)

Any chances of an update? I think there're enough bugs to fix and I wondering, when I see new posts and tweets about google cardboard sdk and unity, how easy it is, but no one talks about the problems... 3 months is a loooooong time for an important update :(

Definitely updates are coming.  We just aren't allowed to give exact dates, I guess because it's better to not make a promise than to make one and have to break it :(

I saw, there's an update. Great! I'll test it and post the result here.

I'll close this issue after the new sdk release 0.6. This solves the

the startglitch
missing Gui Elements

All other problems (crash/timeout) are discussed in a new thread #137

source: gharchive/issue

authors: HansBernd JagaHee Scott-Driscoll hacaro noemis84 ognjenmarcheta smdol

repo: googlesamples/cardboard-unity


text:
ApiException: 8 after app installation

Device: Google Pixel 2XL, Huawei P20 Lite
OS version: 9.0, 8.1
SDK version: 28
[Android] Google Play Services version: play-services-auth:16.0.0

Describe the problem:
ApiException: 8 after calling Task.getResult()
This error happens only first time you try login after app installation. Then, I'm clicking "Sign in button" to execute the code below. I'm choosing my google account and I'm catching ApiException: 8 that means "Internal Error" (https://developers.google.com/android/reference/com/google/android/gms/common/api/CommonStatusCodes). So, I'm clicking "Sign in button" again and it works perfectly since that moment. I can logout and sign in as many times as I want and it will work.
If you clear data of the app, the error will not repeat. Also, it works without error on older devices with android 4.4.2, 5.1, 6, 7.1. Error appears also on emulator with Android version 9.
Steps to reproduce:

Install app
Click "Sign in with Google" button
Catch ApiException: 8
Click "Sign in with Google" button again.
Signed in successfully

Relevant Code:
Task task = GoogleSignIn.getSignedInAccountFromIntent(data);
try {
GoogleSignInAccount account = task.getResult(ApiException.class);
// Signed in successfully, do something with account.
...
} catch (ApiException e) {
e.printStackTrace();
}

any luck with this?
I'm also facing the same issue.
Double checked signing keys in firebase as well as google developer console, and it doesn't seem to be working.

No luck :(
Still the same

Getting the same!

I'm having the same problem

I fix it by adding the following in gso
.requestEmail()
 .requestId()

Me too!

Oh, great: This bug has been open over a year and a half and Google STILL hasn't replied to any of the developers reporting it!

@fractalbob The only workaround that I found was to click sign in button programatically if an exception like this happens!

Or execute recursively in the method that calls the operation:
private void processGmailSignIn(Intent data) {
    Task<GoogleSignInAccount> task = GoogleSignIn.getSignedInAccountFromIntent(data);
    try {
        // Google Sign In was successful, authenticate with Firebase
        GoogleSignInAccount account = task.getResult(ApiException.class);
        firebaseAuthWithGoogle(account);
    } catch (ApiException e) {
        if (e.getStatusCode() == INTERNAL_ERROR) {
            processGmailSignIn(data);
            return;
        }
    }
}

I just realized this exception only happens when I try to do login when I've previously made a login in another device in the same app/project with the same Google account.
Logout the app on the other device to solve the problem.

Or execute recursively in the method that calls the operation, which is what I ended up doing:
private void processGmailSignIn(Intent data) {
    Task<GoogleSignInAccount> task = GoogleSignIn.getSignedInAccountFromIntent(data);
    try {
        // Google Sign In was successful, authenticate with Firebase
        GoogleSignInAccount account = task.getResult(ApiException.class);
        firebaseAuthWithGoogle(account);
    } catch (ApiException e) {
        if (e.getStatusCode() == INTERNAL_ERROR) {
            processGmailSignIn(data);
            return;
        }
    }
}

Above solution not working

I just realized this exception only happens when I try to do login when I've previously made a login in another device in the same app/project with the same Google account.
Logout the app on the other device to solve the problem.

It's been a 2 years already, I don't remember was I logged from another device or not but anyway there're two questions:

Let's assume I was logged in from another device but why this error happens every time I reinstall the app on device that I try to log in.
Shouldn't be there another error with meaningful message instead of just Internal Error?

I just realized this exception only happens when I try to do login when I've previously made a login in another device in the same app/project with the same Google account.
Logout the app on the other device to solve the problem.

It's been a 2 years already, I don't remember was I logged from another device or not but anyway there're two questions:

Let's assume I was logged in from another device but why this error happens every time I reinstall the app on device that I try to log in.
Shouldn't be there another error with meaningful message instead of just Internal Error?

Any luck with this? I am facing the same issue, but I get the message 100% of the attempts, even clicking multiple times on the sign in button...
Support would be appreciated.
+1 on "Internal error" doesn't help.

Are you getting the error on Google sign-in or passwordless email sign-in?
On Fri, Sep 23, 2022, 13:05 Persike @.***> wrote:

Any luck with this? I am facing the same issue, but I get the message 100%
of the attempts, even clicking multiple times on the sign in button...
Support would be appreciated.
+1 on "Internal error" doesn't help.
—
Reply to this email directly, view it on GitHub
https://github.com/googlesamples/google-services/issues/381#issuecomment-1256075692,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALTQDOL5NKG7OJAOU2OFK3V7WFH5ANCNFSM4FTR4LAQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

This problem occurs when:

Succesfully signed in,
Go to Google profile (Apps Access) and remove access for app,
Try to sign-in - should be successfully signed in,
Use service - i.e GDrive -> should be UserRecoverableAuthException
Use intent form UserRecoverableAuthException.getIntent() to startActiviyForResult
In onActivityResult on GoogleSignIn.getSignedInAccountFromIntent(data).getResult(ApiException.class) ApiException with code 8.

Facing the same issue. I've added the google-service.json to my Android project, I'm logged in on the Emulator Device, I've checked all IDs and keys and also added the SHA-1 and SHA-256 to my Firebase project yet I keep getting the exception in getSignedInAccountFromIntent() after running:
private fun signIn() {

    val gso = GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
        .requestIdToken(getString(R.string.default_web_client_id))
        .requestEmail()
        .build()
    val googleSignInClient = GoogleSignIn.getClient(this, gso)
    val signInIntent = googleSignInClient.signInIntent

    val task = GoogleSignIn.getSignedInAccountFromIntent(signInIntent)

    try {
        val auth = Firebase.auth
        // Authenticate with Firebase using Google credentials
        val account = task.getResult(ApiException::class.java)
        val credential = GoogleAuthProvider.getCredential(account?.idToken, null)
        auth.signInWithCredential(credential)
            .addOnCompleteListener(this) { task ->
                if (task.isSuccessful) {
                    // User is logged in, obtain JWT token and return to calling activity
                    val user = auth.currentUser
                    user?.getIdToken(true)?.addOnSuccessListener { result ->
                        val token = result.token
                        val resultIntent = Intent()
                        Timber.i(String.format("Logged in; Token %s", token))
                        resultIntent.putExtra("jwt_token", token)
                        setResult(Activity.RESULT_OK, resultIntent)
                        finish()
                    }
                } else {
                    // Authentication failed, show error message
                    Toast.makeText(this, "Authentication failed.", Toast.LENGTH_SHORT).show()
                }
            }
    } catch (e: ApiException) {
        Timber.e(e);
        // Google Sign-In failed, show error message
        Toast.makeText(this, "Google sign-in failed.", Toast.LENGTH_SHORT).show()
    }
}

authors: LeoPersike Mikkelet Nikoloutsos Nynuzoud cieplakm efraespada falk-stefan fractalbob gopalanrc-nam lnavarrogeodb mhrpatel12

repo: googlesamples/google-services


text:
"Say Cheese" shouldn't be a string?

In the example code the line is:
getActivity().getVoiceInteractor()
.submitRequest(new PickOptionRequest(
"Say Cheese",
new Option[]{option},
null) {
But it seems that it should be:
getActivity().getVoiceInteractor()
.submitRequest(new PickOptionRequest(
new VoiceInteractor.Prompt("Say Cheese"),
new Option[]{option},
null) {
or am I misunderstanding something?

Nope, you are correct. The constructor taking in a String has an @hide annotation in the source, so it's not available for use (without reflection). Anything marked with @hide will also not appear in the docs.

authors: DanFloodTechnologies StephenBrough


text:
🛑 goormIDE is down

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

HTTP code: 403
Response time: 446 ms

Resolved: goormIDE is back up in 51d9a71 after 1 hour, 57 minutes.

repo: goorm-dev/goorm-status

license: MIT

license_source: github-api


text:
🛑 goormIDE is down

In 55b8e6c, goormIDE (https://ide.goorm.io) was down:

HTTP code: 403
Response time: 510 ms

Resolved: goormIDE is back up in e390d7f after 44 minutes.


text:
🛑 goormEDU is down

In 831f5a4, goormEDU (https://edu.goorm.io) was down:

HTTP code: 403
Response time: 780 ms

Resolved: goormEDU is back up in 6781ae3 after 5 minutes.


text:
Update Github workflow script to get info about recently executed functions in smal file

As can be see here - https://github.com/qarmin/Qarminer/actions/runs/1249293607
there are now an artifacts to download, which are produced after each run(even unsuccessful), which provide small file(max 10-20MB, but usually few MB) with info about executed functions with parameters in last run e.g.
######################################## _OS ########################################
	var temp_variable = ClassDB.instance("_OS")
	temp_variable.is_keep_screen_on()
	temp_variable.is_vsync_enabled()
	temp_variable.set_vsync_via_compositor(false)
	temp_variable.set_window_position(Vector2(0.90613, 0.423))
	temp_variable.can_draw()
	temp_variable.set_thread_name(".")
	temp_variable.get_ime_selection()
	temp_variable.set_screen_orientation(-42)
	temp_variable.center_window()

This is how it looks workflow file
https://github.com/qarmin/Qarminer/blob/0dba2d194f0644f32da32b429daa6739b369b7ae/.github/workflows/linux_builds_1.yml#L46-L60

Yeah, this should make it easier to reproduce bugs locally by simply copy-pasting the code, thanks!
In my case result.txt is much smaller because I only run fuzzer for 5 minutes (I've found it sufficient for the number of classes that are tested).
See https://github.com/goostengine/goost-fuzzer/runs/3644425916
Looks like there's a new bug revealed there as well... 😅

authors: Xrayez qarmin

repo: goostengine/goost-fuzzer


text:
Gopass does not consistently respect upper and lowercase in secret names / Git commit fails if secret exists in different case

Summary
Given an existing secret named key. If a new entry KEY is inserted, Gopass internally modifies the encrypted key.gpg instead of creating a new secret file KEY.gpg.
As the case is not handled consistently, even the update of key.gpg fails as Gopass tries to (git) add and commit KEY.gpg instead of the just updated key.gpg.
Steps To Reproduce
➜  ~ gopass list test
test/
└── key

➜  ~ export GIT_TRACE=1; export GOPASS_DEBUG=1

➜  ~ echo "secret-update" | gopass insert -f test/KEY
# ...
2024/03/19 17:06:48.535905 fs/store.go:63	fs.(*Store).Set	Writing KEY.gpg to /Users/MYUSER/.local/share/gopass/stores/test/KEY.gpg
2024/03/19 17:06:48.536004 gitfs/git.go:145	gitfs.(*Git).captureCmd	store.gitAdd: /opt/homebrew/bin/git [git add --all --force KEY.gpg] (/Users/MYUSER/.local/share/gopass/stores/test)
2024/03/19 17:06:48.539757 queue/background.go:106	queue.(*Queue).Add	enqueued task
2024/03/19 17:06:48.539790 gitfs/git.go:145	gitfs.(*Git).captureCmd	store.gitDiffIndex: /opt/homebrew/bin/git [git diff-index --quiet HEAD] (/Users/MYUSER/.local/share/gopass/stores/test)
2024/03/19 17:06:48.543269 gitfs/git.go:155	gitfs.(*Git).Cmd	CMD: gitDiffIndex [diff-index --quiet HEAD]
Error: exit status 1
Output:
  Stdout: ""
  Stderr: "17:06:48.542371 git.c:463               trace: built-in: git diff-index --quiet HEAD\n"
2024/03/19 17:06:48.543293 gitfs/git.go:145	gitfs.(*Git).captureCmd	store.gitCommit: /opt/homebrew/bin/git [git commit --date=1710864408 +00:00 -m Save secret to /KEY: Read secret from STDIN] (/Users/MYUSER/.local/share/gopass/stores/test)
2024/03/19 17:06:48.547371 gitfs/git.go:155	gitfs.(*Git).Cmd	CMD: gitCommit [commit --date=1710864408 +00:00 -m Save secret to /KEY: Read secret from STDIN]
Error: exit status 1
Output:
  Stdout: "On branch main\nYour branch is up to date with 'origin/main'.\n\nChanges not staged for commit:\n  (use \"git add <file>...\" to update what will be committed)\n  (use \"git restore <file>...\" to discard changes in working directory)\n\tmodified:   key.gpg\n\nno changes added to commit (use \"git add\" and/or \"git commit -a\")\n"
  Stderr: "17:06:48.545852 git.c:463               trace: built-in: git commit '--date=1710864408 +00:00' -m 'Save secret to /KEY: Read secret from STDIN'\n"
2024/03/19 17:06:48.547407 queue/background.go:89	queue.(*Queue).run	ERROR: Task failed: failed to commit changes to git: exit status 1: 17:06:48.545852 git.c:463               trace: built-in: git commit '--date=1710864408 +00:00' -m 'Save secret to /KEY: Read secret from STDIN'
❌ Task failed: failed to commit changes to git: exit status 1: 17:06:48.545852 git.c:463               trace: built-in: git commit '--date=1710864408 +00:00' -m 'Save secret to /KEY: Read secret from STDIN'
# ...

➜  ~ cd /Users/MYUSER/.local/share/gopass/stores/test

➜  test git:(main) git status
On branch main
Your branch is up to date with 'origin/main'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   key.gpg

no changes added to commit (use "git add" and/or "git commit -a")

➜  ~ gopass list test
test/
└── key

Expected behavior
Gopass should be case-sensitive and respect upper and lowercase so that it is possible to create both secrets key and KEY.
OR: Gopass is consistently case-insensitive.
Environment

OS: macOS Sonoma 14.4 (23E214)
OS version: Darwin XXXXXXXXX 23.4.0 Darwin Kernel Version 23.4.0: Wed Feb 21 21:44:54 PST 2024; root:xnu-10063.101.15~2/RELEASE_ARM64_T6030 arm64
gopass Version: 1.15.12 go1.22.1 darwin arm64
Installation method: brew

I'm afraid I couldn't reproduce this on MacOS, yet.
Also I didn't find any code that would be case-dependent, yet.
Can you provide additional details? Is it possible that the git repo in the store had unstaged changes before you tried to add test/KEY?

Hi @dominikschulz, thanks for having a look. I reproduced the issue with a fresh repository that I integrated into Gopass. I just gave you permissions to https://github.com/janekbettinger/gopass-test-store .

Is it possible that the git repo in the store had unstaged changes before you tried to add test/KEY?

That "should" not have been the case.
Since you linked a commit after your comment: could you reproduce it in the meanwhile? If not, I might give it another trial and document the init steps as well.

No, I couldn't reproduce it yet. I just found one place where we should handle filenames better - but the changes shouldn't affect casing issues.

authors: dominikschulz janekbettinger

repo: gopasspw/gopass


text:
Cleanup travis config

Signed-off-by: Dominik Schulz dominik.schulz@gauner.org

Codecov Report

Merging #1389 into master will decrease coverage by 0.15%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #1389      +/-   ##
==========================================
- Coverage   57.34%   57.19%   -0.15%
==========================================
  Files         196      190       -6
  Lines       11044    10979      -65
==========================================
- Hits         6333     6279      -54
+ Misses       3898     3894       -4
+ Partials      813      806       -7

Impacted Files
Coverage Δ

commands.go
100.00% <ø> (ø)

internal/action/commands.go
0.00% <0.00%> (ø)

internal/clipboard/clipboard_others.go
77.27% <0.00%> (-9.09%)
:arrow_down:

internal/backend/crypto/gpg/cli/parse_colons.go
93.65% <0.00%> (-3.17%)
:arrow_down:

internal/editor/edit_others.go

pkg/pinentry/pinentry_darwin.go

internal/clipboard/unclip_others.go

internal/backend/crypto/gpg/cli/utils_others.go

pkg/tempfile/mount_darwin.go

internal/notify/notify_darwin.go

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 bdc9bc5...41477c9. Read the comment docs.

authors: codecov-commenter dominikschulz


text:
Enhance: support delete article

Currently, seems there is no way to delete the article even which is posted by me.

We can delete our articles in user page.

Perhaps we could add a delete tips after the delete result is complete.

authors: CarlJi IRONICBo

repo: goplus/community


text:
feat(libreoffice): add singlePageSheets option

Exposes libreoffice's SinglePageSheets option, defaults to false as this is the current behavior.
Normally libreoffice will take each sheet in a spreadsheet and fit into onto 1 or more A4 pages in the output PDF.
When SinglePageSheets is set to true libreoffice will instead render the entire spreadsheet as a single page, with the size of the page being whatever fits the content.
This is useful when the output PDF is to be used digitally and not printed to paper.

Hey @mrbech,
Thanks for this new PR! A stupid question, but I guess it concerns only XLSX etc.?

Hey @mrbech,
Thanks for this new PR! A stupid question, but I guess it concerns only XLSX etc.?

Should be, from my testing it works for xlsx and makes no difference when converting docx documents at least.
The documentation I have been able to find isn't explicit about which formats this works for, but I would guess any formats that normally gets opened by libre office calc.

Thanks again!

authors: gulien mrbech

repo: gotenberg/gotenberg


text:
change win Decoration kill opacity

Hello
first of all thanks for this very good Gtk/Go binding
In order to learn  both Go and  gotk3 I have wrote a naive clock demo
with popup menu I can switch on/off decoration but doing that I lost window opacity
may be I do something wrong ?
if you have some idea,  thanks for your help

Whenever you report such behavioral problems, it'd be nice if you could include a minimal example that shows the behavior that you deem to be incorrect. It should do nothing less and nothing more.

ha ok sorry for the inconvenience
a test code did not seem trivial at first and I thought the demo link code was small enough
I will try to do better next time ;-)
thank you for ignoring this request which, in fact,  is not very important  and may be a problem coming Gtk
Whichever it is, GoTK3 is a great job, thanks for that
cordially

I personally prefer having a small snippet of code that exactly reproduces the problem and does nothing less and nothing more. Sometimes it doesn't even reproduce the problem, indicating that the problem lies somewhere else in your codebase. So I think writing a minimal example is always the best way to go about this, for you and the people that want to help you.

Hello
the smallest I can think of (a key press changes the state)
but not sure you have to spend time on that because it's probably a GTK bug
(tested a lot of case without success,  platform Linux Mint 19)
anyway gotk3 is a great job, thanks for that
test.go.zip

I have to bicker one last time.  If you have a single file with example source code, then you can just post it like this:
```go
func main() {
...
}
```
then nobody has to download a zip file ;)
Anyway it's fine for now, I'll test it later, thanks.

OK I'll do  ;-)
thank's
Le jeu. 25 avr. 2019 à 12:02, Marcel Schramm notifications@github.com a
écrit :

I have to bicker one last time. If you have a single file with example
source code, then you can just post it like this:
func main() {
...
}

then nobody has to download a zip file ;)
Anyway it's fine for now, I'll test it later, thanks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gotk3/gotk3/issues/363#issuecomment-486609565, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABGFC7XNC3UFIDSTUQWUUITPSF6UPANCNFSM4HHLHPEA
.

So, for me this acts completely different. The opacity stays as specified, however, the toggling of the decoration doesn't work at all. After the decoration has been disabled once, it doesn't turn on again.

after lot of search seem there is different Gkt behaviour according the
platforms
so please do not invest time in such a thing, it is not worth it
thanks again
I have enjoyed to play with gotk3
in some future  I will test on Windows
Le jeu. 25 avr. 2019 à 19:30, Marcel Schramm notifications@github.com a
écrit :

So, for me this acts completely different. The opacity stays as specified,
however, the toggling of the decoration doesn't work at all. After the
decoration has been disabled once, it doesn't turn on again.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gotk3/gotk3/issues/363#issuecomment-486766307, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABGFC7W4N3HO74G6T3TDKLLPSHTEVANCNFSM4HHLHPEA
.

Hm, okay. If you think this is not worth investigating any further, just close the issue.

ok
in fact I have same or even more problems with same clock
https://github.com/nodrygo/GoClock test I have done with Racket and Julia

Gtk
but this was just to compare the different environment ;-)
as a language I prefer Julia than Go
as a deployment Racket is the most easy of different platform
for Gtk Binding and for compilation bin size Go is the best :-)

Le jeu. 25 avr. 2019 à 19:57, Marcel Schramm notifications@github.com a
écrit :

Hm, okay. If you think this is not worth investigating any further, just
close the issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gotk3/gotk3/issues/363#issuecomment-486775886, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABGFC7UZBR562UPKS3TXTFTPSHWJ7ANCNFSM4HHLHPEA
.

authors: Bios-Marcel nodrygo

license: isc


text:
Add a basic about page

Fixes #43.
Navbar and footer added in the static file, should perhaps be replaced through template later but it works for now.

The last commit might have had a bit of an unwanted side effect: menu elements being further away from each other while making the menu wider. It might be solved by an additional "Subject" link, otherwise let's pick it up when we do a design review.

@Ainali I have made some structural changes that have some unintentional effects on the design, feel free to have a look in case there is something major otherwise, you can merge this.

@Ainali I have made some structural changes that have some unintentional effects on the design, feel free to have a look in case there is something major otherwise, you can merge this.

Nothing major at all, let's merge this and iterate later.

repo: govdirectory/website


text:
Did somebody see a splash message at startup like this? nothing is wrong but the splash,a little annoying

will disappear quickly, I must record the screen and play it slowly to cut this screen.
MacOS, tmux 3.2 , most recent conf version.

Hello @FinallyFinancialFreedom 👋
This is currently  a tmux limitation. The next version of tmux behaves slightly differently and this won't happen anymore.

thank you , should i update tmux to 3.3-rc?

Your choice.
As you noticed, this <... not ready> "flash" is harmless and happens only briefly when starting tmux with Oh my tmux!

authors: FinallyFinancialFreedom gpakosz


text:
[GPII-3743]: Improve PDs handling in couchdb module

This implements the following:

Adds variable to enable / disable PVCs recovery code and disables it for dev environment.
Adds code to remove disks with gcloud after PVCs deletion to not leave stale resources behind.

I believe this also solves GPII-3742.

LGTM

Any idea why the underlying disks are not getting deleted?

@stepanstipl Unfortunately no – destroying PVCs supposed to release the disks, but in some small number of cases it is not happening. I was unable to find anything related to that event in cluster logs. And that scenario is also very hard to reproduce.

Have a scenario when trying to delete disk that is still mounted, because it was not released by Kube

Deleting corresponding PVC releases the disk.

I'm slightly worried that we're introducing "workaround" to an issue which's cause we don't understand very well

Yeah, it is a good reason to be slightly worried. I have nothing better to offer for now.

I disagree with this - two separate issues. This does not fix recovery process in any way

This PR disables recovery process for dev environments. I thought we agreed that for staging and prod we will follow the process of migrating disks to proper zones manually. But I am fine treating GPII-3742 separately.

@stepanstipl Ok, I addressed some of your concerns: new code does not use gcloud beta anymore, it also repeats disks deletion in a loop until success is achieved.

So that is exactly my point - if the disk is never released and never detached from the VM, this fix won't work

But overall I would still like to see some evidence that this solves the issue.

I run for i in {1..25}; do rake redeploy_module['k8s/gpii/couchdb']; done in my dev cluster and it worked every single time, disks are getting destroyed on 2-3rd attempt in average.
Also, main change here is not PD hard-removal code (it is mostly needed to not leave stale disks behind), but the change that disables PD recovery code for dev environments.

^ I've seen one more fail on recovery code, trying to recover disk that did not exist since then

I've seen one more fail on recovery run, trying to recover disk that did not exist since then

It looks like you set both execute_destroy_pvcs and execute_recover_pvcs into true? I don't think we ever want to do that, and of course there may be situation when recovery code is trying to access disks that are in the process of deletion by Kubernetes.

So I think this is actually dangerous because we're deleting a disk that is managed by Kubernetes, before it has a chance to delete it on its own.

I did not find any side effects of forcefully deleting disks that got their corresponding PVCs and PVs removed and already scheduled for deletion.

Maybe we can get just that change in, without introducing the other bits for now?

I am okay with this, the downside of course would be leaving stale disks behind.

Updated PR description.

lgtm 👍

LGTM!

authors: amatas natarajaya stepanstipl

repo: gpii-ops/gpii-infra


text:
[GPII-3917] Leftovers from the backup-exporter

This PR fixes the issues detected on the https://github.com/gpii-ops/gpii-infra/pull/471

Documentation about the topics that we discussed in the retrospective of the last deployment
Improves the documentation about how to restore external backups
Uses variables to set the zone, networks and subnetwork of the backup-exporter

LGTM

authors: amatas natarajaya


text:
 not included in info.h

Hi,
I just tried to compile the code, and run into this error:
Gpufit-master/Gpufit/info.cpp:122:82: error: ‘::max’ has not been declared; did you mean ‘std::max’?
122 |     std::size_t const highest_size_t_value = std::numeric_limits< std::size_t >::max();
Googling a bit, I found that  was not included in the header file. I think it would be good if you could do that, it seems that it is not included by default. Else, everything worked fine in the compilation - I will now run a few test runs.
Best regards,
Stefan

Hi, I'm facing the same problem. Seems like this is caused by using gcc-11 or higher:
https://gitlab.com/wg1/jpeg-xl/-/issues/84

authors: lukasglandorf stefanhofmeister

repo: gpufit/Gpufit


text:
Incorporate dialogs for user input and structured outputs

https://linux.die.net/man/1/dialog

Once again, I committed a million times to the master branch without opening a feature branch because I'm a n00b

repo: grace-bible/GAM-boarding-scripts


text:
Fixed piano example

Co-authored-by: Mikkel Rasmussen theluja@gmail.com

Ah I didn't catch that. Thank you!


text:
Update README

Fix https://github.com/gradle-nexus/publish-plugin/issues/68

Thanks!

authors: JavierSegoviaCordoba szpak

repo: gradle-nexus/publish-plugin


text:
Proposal: Remove foojay from plugin id as this expose implementation details

Hi guys,
I just read a bit about this plugin, what it does and what it offers etc.
While looking at it, I kept wondering why it's called "foojay".
Well, it makes sense because it uses the foojay api under the hood. Fine.
But thinking a bit further, I think it makes sense to remove this information from the ID as it is not needed. Why should an implementation be exposed to something "generic" like a toolchain vendor?
Just thinking about the future. Imagine you change your API provider. For whatever reason. Will you create a new repository? Will you create a new plugin? Will you keep the foojay name but change the api?
I think to make this plugin more future proof it would make sense to at least remove the foojay information from the plugin id so you can change the jdk provider as you like in the future...
What do you think?

I appreciate your interest in this plugin. However, I must disagree.
This plugin is one of many possible Gradle Toolchain Resolver Plugins, which is specifically based on the DiscoAPI provided by Foojay.
If it would be based on something else, then that would be another such plugin and would be named accordingly.
It's specific, with a specific name.
That doesn't make it non-future-proof.

authors: StefMa jbartok

repo: gradle/foojay-toolchains


text:
Enable selection of JVM implementation for java toolchain

The current java toolchain implementation has hotspot hardcoded as the jvm impl. Since AdoptOpenJDK provides the option to select openj9 instead of hotspot for the JVM Implementation it would be great to configure that in the toolchain.
Expected Behavior
A configuration option to select the jvm_impl for downloading AdoptOpenJDK.
Current Behavior
hotspot is hardcoded in the URL for downloading from AdoptOpenJDK.
Context
I think it should be made clear, that this option only affects downloading the JDK from AdoptOpenJDK and not for selecting locally installed JDKs.
Our plan is to build our application on our CI server with OpenJ9, where gradle downloads the JDK. This way we can use a more general image for our CI build step.

This is actually not only relevant for downloading but also for selecting a toolchain in case you got both installed locally but your build requires a specific one (e.g. j9)

Thanks, @breucode for the request. This is indeed something we plan on doing. I'm closing this one in favor of a more general issue to track this feature: #14802

authors: bmuskalla breucode

repo: gradle/gradle


text:
Configuration-cache safe way to set Gradle properties

It would be nice if there were a configuration-cache safe way to set Gradle properties.
The Gradle properties plugin at https://plugins.gradle.org/plugin/net.saliman.properties provides a very nice functionality where you can have additional Gradle properties files that are evaluated between the checked in Gradle properties file and the Gradle properties file in the user home directory.
This way you can easily have custom values for properties for your local development or even have different values in different worktrees easily.
With one central place (Gradle properties in user home) for all projects and all worktrees this is not really possible or handy, you cannot even easily open the file in your IDE as it is not in the project files.
The plugin up to now works by setting the properties as ext properties on the project or settings.
So if one uses findProperty and alike it magically worked as first the ext properties were searched and then the actual Gradle properties.
If you now try to become configuration cache safe or plugins become configuration cache safe and thus use the provider for the gradle property, this magic does not work any longer, as the provider does not look into the ext properties. So any value set in those additional files will not work anymore.
You could of course use providers.fileContents to make the file an input for the configuration cache and thus invalidate the whole configuration cache when the file changed (which is a bit cannon => sparrow), but even then plugins that use the new provider will not see the value from the additional file as the Gradle property provider will not look into ext properties.
In an optimal world all plugins would probably expose all their configuration options as extensions or task properties, but realistically this will not happen and there will always be plugins that consider some Gradle properties as input.
So to make things like the Gradle properties plugin work as seemlessly blended into Gradle as they are used to, there is the need for some way to set or provide Gradle properties programmatically from a plugin.

This feature request is in the backlog of the relevant team and is prioritized by them.

Unfortunately, we're unlikely to address this in the short-to-medium term. Project properties are already complicated and we're looking at simplifying them. Isolated Projects may bring a better replacement.

authors: Vampire mlopatkin


text:
Improve ExtensionContainer API

Expected Behavior
It should be possible to find more than one extension by type. Currently, ExtensionContainer#findByType assumes that there's a single extension of a specific type, but it's not true: it's perfectly valid to have multiple extensions of the same type. For example the GraalVM plugin configures an extension to configure the native image of an application, and another one for the tests of the application (possibly more).
Therefore, I'd suggest to add variants to be able to configure by type:
project.getExtensions().typed(SomeExtension.class, extensions -> { ... })

Current Behavior
Currently the only solution is to search by name, which is brittle as we need to know all the possible extension names beforehand. Alternatively I can use the extension schema to find all extensions by type in a first iteration, collect the names, then search by name, which is cumbersome:
    private static <T> Set<T> findExtensionsByType(Class<T> type, Project project) {
        Set<T> extensions = new HashSet<>();
        ExtensionContainer container = project.getExtensions();
        container.getExtensionsSchema().forEach(schema -> {
            if (type.isAssignableFrom(schema.getPublicType().getConcreteClass())) {
                //noinspection unchecked
                extensions.add((T) container.findByName(schema.getName()));
            }
        });
        return extensions;
    }

Is this a practice that you'd like to promote, declaring multiple extensions with a single type? I'd be concerned about plugins misusing it, for example, by declaring instances of their extensions for large numbers of variants (which is not that unusual on Android if you happen to have multiple flavors).
I like the consistency of the model of declaring a single extension per plugin (or function), with nested extensions for variants (and using the or configure in Kotlin DSL). The androidComponents extension is a great example of it, and the concept of selectors offers flexible configuration of multiple variants. In your particular example, using a single extension would make the structure of the configuration explicit:
graal {
    native {
        ...
    }

    test {
        ...
    }
}

Which allows you to use the<GraalExtension>().native and the<GraalExtension>().test for acquiring each instance.

Is this a practice that you'd like to promote, declaring multiple extensions with a single type?

Absolutely not. And I agree with the DSL you want to suggest, just need to convince a couple more folks :) This issue is really about the wrong assumption in the ExtensionContainer, which is, IMO, a bug. Nothing more :)

I guess that I worry that introducing an API to access multiple instances of an extension type does promote the practice, indirectly. But I can see how, strictly speaking, it's indeed an artificial limitation :)

ping


text:
IntelliJ Gradle plugin fails to load a project with double included builds on Gradle 7.2

A project has 2 included builds, and one included build also includes another.
+ Sample // includeBuild(platform), includeBuild(product)
-- platform
-- product // includeBuild(platform)

IntelliJ Gradle plugin fails to sync the project using Gradle 7.2.0 but works well with Gradle 7.1.0.
Both Gradle versions works well from the terminal using Gradle wrapper.

Expected Behavior
Project is synced in IntelliJ Idea
Current Behavior
IntelliJ Idea fails to sync the project
No model of type 'TurnOffDefaultTasks' is available in this build.
> No builders are available to build a model of type 'org.jetbrains.plugins.gradle.model.internal.TurnOffDefaultTasks'.

Context
Steps to Reproduce
Open project in Idea
https://github.com/AKhranovskiy/gradle-nested-include-builds/tree/android-studio-sync
Your Environment
Gradle 7.2
Build time:   2021-08-17 09:59:03 UTC
Revision:     a773786b58bb28710e3dc96c4d1a7063628952ad
Gradle 7.1
Build time:   2021-06-14 14:47:26 UTC
Revision:     989ccc9952b140ee6ab88870e8a12f1b2998369e
IntelliJ Gradle plugin 203.7717.56.2031.7678000
IntelliJ Gradle plugin 212.5284.40
IntelliJ Gradle plugin 211.7628.21.2111.7699744
IntelliJ Idea ticket

Thank you for your interest in Gradle!
This is an issue with IntelliJ IDEA’s Gradle integration, which is developed by JetBrains and cannot be addressed in the core of the Gradle Build Tool.
Please open such IntelliJ-related issues on the JetBrains Issue Tracker at https://youtrack.jetbrains.com/

If this also does not work on the command line, please add information to reproduce the CLI problem.

authors: AndreyKhranovsky-TomTom ljacomet


text:
Add an option to disable test fixtures publication

Expected Behavior
It would be great to have an option to disable test fixtures from publishing.
Current Behavior (optional)
Currently, the only way I know is to use internal Gradle APIs to skip specified components from publication:
plugins.withId("org.gradle.java-test-fixtures") {
    val component = JavaPluginHelper.getJavaComponent(project) as DefaultJvmSoftwareComponent
    val feature = component.features.getByName(TestFixturesSupport.TEST_FIXTURES_FEATURE_NAME)
    component.withVariantsFromConfiguration(feature.apiElementsConfiguration) { skip() }
    component.withVariantsFromConfiguration(feature.runtimeElementsConfiguration) { skip() }
}

Context
I need to use test fixtures only internally between my modules, so I don't want to publish them into Maven Central. Here is the project: osipxd/encrypted-datastore (module encrypted-datastore contains test fixtures)

Your issue appears to be a question about how to use Gradle. They should be asked in a different channel, so we will close it. Your question might be answered in Gradle documentation or on our community Slack or forums. Find links to these resources on help.gradle.org.
If you think our analysis is wrong, please provide us with more detailed information explaining why.

This is documented at the end of this section without using internal APIs.

Thank you! My bad, I don't know how I missed that in docs.

authors: ljacomet osipxd


text:
modifying project classpath from init script should either work or fail

I tried to use the following init script:
rootProject {
    buildscript {
        repositories {
            gradlePluginPortal()
        }

        dependencies {
            classpath 'com.github.ben-manes:gradle-versions-plugin:0.20.0'
        }
    }

    apply plugin: 'com.github.ben-manes.versions'
}

The effect it has is Plugin with id 'com.github.ben-manes.versions' not found..
I guess that at the time the closure is applied to the root project it is too late to add to its classpath.
It would be nice if this would either work (or maybe with some other method that can add dependencies to the classpath) or if it would at least error out.
Well, it errors out, but I mean with "you cannot do this here" or something more meaningful, I think you know what I'm talking about. :-)

This is still relevant in 6.8.2.
Actually I made another experiment that surprisingly worked, so it seems you can add to the class path using the original post code, because this works:
my.init.gradle:
rootProject {
    buildscript {
        repositories {
            gradlePluginPortal()
        }

        dependencies {
            classpath 'com.github.ben-manes:gradle-versions-plugin:0.20.0'
        }
    }
}

build.gradle.kts:
apply(plugin = "com.github.ben-manes.versions")

while having the apply in the init script like in the original post still fails with the same error.


text:
Remove CMD_LINE_ARGS in bat script to avoid leaking credentials

The windows startup script leaks CMD_LINE_ARGS into environment variable,
now we remove it.
The windows98/Me handling code is also removed.

@bot-gradle test QF

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

@bot-gradle test QF

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

@big-guy do you still want to take a look?

Cherry-picked to release.

authors: blindpirate bot-gradle donat


text:
Publish 7.4-20220203000213+0000

Publish 7.4-20220203000213+0000

@bot-gradle test and merge

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


text:
Update Sentry Android plugin and use AGP 7.3.0 in samples and Android perf tests

This relates to removal of IncrementalTaskInputs: https://github.com/gradle/gradle/pull/21731.
Sentry plugin was updated for 8.0: https://github.com/getsentry/sentry-android-gradle-plugin/issues/370.
Also, there are some leftovers after upgrading AGP to 7.3.0 in samples and performance tests.
Performance test changes:

https://github.com/gradle/perf-android-large/commit/54eef7cc87e9eb1e89fce0d2de8d12e60c694080
https://github.com/gradle/perf-android-large-2/commit/a67ceb08a7b4e4a71e3c151a3abd72a9abe5d703

@bot-gradle test AST

OK, I've already triggered the following builds for you:

AllSmokeTestsPullRequestFeedback build

@bot-gradle test AST APT

OK, I've already triggered the following builds for you:

AllSmokeTestsPullRequestFeedback build
AllPerformanceTestsReadyForRelease build

@bot-gradle test and merge

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

authors: asodja bot-gradle


text:
Declarative DSL team owns core-configuration/declarative-dsl-*

Also fix a missing change in CODEOWNERS after the move of architecture docs.

The merge queue build has started. Click here to see all failures if any.

authors: bot-gradle eskatos


text:
Add os triggers for stages

This is part of https://github.com/gradle/gradle-bot/issues/119
Developers sometimes want to test only on Linux to speed up. This PR adds OS triggers for PullRequestFeedback/ReadyForNightly/ReadyForRelease stages:

We add a new class in BuildType hierarchy so that we can filter build type by OSes.
+-- BaseGradleBuildType
    +-- OsAwareBaseGradleBuildType
        +-- ...
        +-- ...

I have squashed this PR as 71424d574e70a938507a77ece0267650452de8de

authors: blindpirate bot-gradle


text:
A disabled build option should provide a proper description

For more information see https://github.com/gradle/gradle/issues/3232
The code was there but must have gotten broken in some refactoring step. The disabled build option description wasn't properly tested.

@blindpirate Is this something you are planning to review or should I find someone else?

I'll finish it before your Monday, very sorry for the delay.

No worries, wasn't really on the plan for this sprint. It's definitely OK for me to find someone else to review if you are overloaded.

Still wondering if we could find a better way to represent a description for disabled boolean options. Right now it looks like this:
--scan                    Creates a build scan. Gradle will emit a warning if the build scan plugin has not been applied. (https://gradle.com/build-scans) [incubating]
--no-scan                 Disables option --scan. [incubating]

I think it would be better if the disabled option could have a more descriptive text. I might look into that again.

@blindpirate I improved the error messaging for disabled boolean options by being able to pass in a customized description. Can you please have another look?

LGTM.

authors: blindpirate bmuschko


text:
Render references to code samples in Gradle dist from user guide

Context
Reference self-contained sample projects so that users can directly go to the relevant directory and try it out. The output would something like this:

Note: The code for this example can be found at samples/userguide/dependencyManagement/inspectingDependencies/dependenciesReport in the ‘-all’ distribution of Gradle.

I think this concept only works well if the sample project doesn't cover multiple cases and can run by itself to fulfill a use case. For that very purpose some samples have not been referenced.
Let me know what you think.

I like referencing the sample, but I think it would be preferable to link to GitHub here. I would find having to download a new distribution of Gradle and inspecting it too cumbersome to consider.
I'll be we can use a docbook customization to achieve this.

I like referencing the sample, but I think it would be preferable to link to GitHub here. I would find having to download a new distribution of Gradle and inspecting it too cumbersome to consider.

I can see your point. If we'd reference the sample on GitHub we'd have to make sure that the URL with the right tag for that specific release is used. What I like about the distribution is that you can directly navigate there from the command line and actually run the build.

I am going to close this pull request for now. We may want to approach the functionality in a slightly different way as described above.

authors: bmuschko eriwen


text:
Disable very long tests when not running in embedded mode

Context
This is a poor man's solution to reducing build time, in particular when the
test is using the "no daemon" executer.
See gradle/gradle-private#1207 for details.

LGTM
But please hold on to wait all CI pipeline is green. I'll let you know.

Feel free to merge yourself when you're done, doesn't have to be me :)

No problem!

Merged since I really can't stand with the slow CI tests...

Don't be sorry, it participates to CI stability: it also means less HTTP servers started/shutdown (around 300 if I recall), so reduces port contention ;)

authors: blindpirate melix


text:
Allow Groovy, Kotlin, and Gradle-specific syntax highlighting

This change creates and uses custom xslthl config that allows
Docbook to highlight syntax in a language specific way instead of
just always falling back to java.
Styles for syntax highlighting are adjusted to match IntelliJ
defaults
Context
In order to allow Kotlin DSL samples, we need Kotlin syntax highlighting in our docs.
Instead of undergoing the massive effort of converting the whole pipeline to asciidoctor, including samples testing, I found it much easier to create custom highlighting config.
Examples of better highlighting:

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

I took away Gradle-specific highlighting. Unless there objections, once the CI branch build passes I will merge this.


text:
fix: Ensure HTTP server startup errors are logged (#694)

Bugfixes
PR Description
This commit modifies the go routine that starts the HTTP server to explicitly log any errors encountered during startup, except for http.ErrServerClosed, which is expected during graceful shutdown. This change ensures that issues related to the server's startup, such as the address already being in use, are logged, making it easier to diagnose and fix.
Which issue(s) this PR fixes
Fixes #694
Notes to the Reviewer
PR Checklist

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Mohamad Rashad seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

As this is my first contribution, I welcome all your feedback and advice.

hi @mrashad10, are you still working on this PR? If anything's troubling you, feel free to raise it here!

Hi @hainenber
Sorry but I was busy last 2 weeks, I'm not sure that I will have time to work on it this week too.

authors: CLAassistant hainenber mrashad10

repo: grafana/alloy


text:
JSON API: Bad Gateway

While trying to connect to a WebService exposed from RapidMiner I get the JSON API: Bad Gateway error while configuring the data source.
I have tried with and without user credentials. Copying the headers sent by Postman and the error is the same.
But the error is not helpful to understand what might be wrong.

I'm pasting the error I'm getting I guess the issue is related with the call being done through ip and not by the url of the process.
error="http: proxy error: dial tcp ip:port: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."

@mbarradas Are you still experiencing this issue?

Marcus,
I have a similar issue when attempting to connect to Azure for getting alert status information. First I get an error that API version is required, I add it to the headers section then I get a bad Gateway error. Could an example of a working connection to Azure using this DataSource plugin be provided?  Here is a link to Microsofts DOC on the what I am attempting to perform. https://docs.microsoft.com/en-us/rest/api/monitor/alertsmanagement/alerts/get-all.  Thanks.

I meet the same question with you

I have also experienced the same issue as @AP-XD

Please note that the bad request in the second image is not my issue, it's simply because my endpoint does not return JSON at  the root URL, everything works fine with the datasource in the second image

Hello I just wanted to share that I also faced the similar issue while serving json file using localhost But when I use npoint.io for it it works fine.

Use your IPV4 instead of localhost, it worked for me

Hello I just wanted to share that I also faced the similar issue while serving json file using localhost But when I use npoint.io for it it works fine.

Use your IPV4 instead of localhost, it worked for me

Yeah I also used npoint in the beginning but it was not a good solution for me to use ipv4 because I needed to serve some metrics which was being generated locally.
So actually what I did was create a kubernetes service for hosting the metrics locally which would be accessible by the kubernetes environment and thereby the grafana pod.
I needed it this way because other metrics were also being served to the grafana pod via prometheus which was also in kubernetes environment.

This issue can be closed I think @marcusolsson .
Since being unable to access localhost in environment other than kubernetes is a problem in grafana.
For which they have also provided a config hostNetwork: true in case if you want to access it though.

Thanks for coming back @AP-XD. I'm going to close this then.

Hello I just wanted to share that I also faced the similar issue while serving json file using localhost But when I use npoint.io for it it works fine.

Hello, please I have a similar issue, I am running a Thanos Query Frontend locally and I want to add its URL in the datasource plugin, its giving JSON API: Bad Gateway, please how to I convert the URL:http://localhost:10901/ to npoint if it could work, I have attached images of the Datasource Plugin and Thanos URL

authors: 0128zzc AP-XD Christoper-Lloyd2 DanielA2119 TomiwaAribisala-git VictorZuluaga marcusolsson mbarradas zoltanbedi

repo: grafana/grafana-json-datasource


text:
Could not load file or assembly 'MySql.Data.OpenTelemetry' or one of its dependencies. Strong name signature could not be verified.

Bug Report
A list of Grafana and
OpenTelemetry NuGet packages
used, for example Grafana.OpenTelemetry 0.6.0-beta.1):

Grafana.OpenTelemetry.Base.0.8.1-beta

The .NET runtime version (e.g. net462, net48, netcoreapp3.1, net6.0
etc.). You can find this information in your *.csproj file):

net48, v4.8.1
VisualStudio 2019 or 2022

Symptom
A clear and concise description of what the bug is.
My application does not use MySQL.  Test solution does not have any other packages loaded.
Cannot load required MySql.Data.OpenTelemetry package because the signature could not be verified.
What is the expected behavior?
What did you expect to see?
What is the actual behavior?
What did you see instead?
Could not load file or assembly 'MySql.Data.OpenTelemetry' or one of its dependencies. Strong name signature could not be verified.  The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)
Reproduce
Create a self-contained project using the template of your choice, apply the
minimum required code to result in the issue you're observing.

Create a new project in VisualStudio 2019 using the ASP .NET Web Application (.NET Framework) and add the Grafana.OpenTelemetry.Base.0.8.1-beta NuGet package.
Start the application

Additional Context
`Server Error in '/' Application.
Could not load file or assembly 'MySql.Data.OpenTelemetry' or one of its dependencies. Strong name signature could not be verified.  The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IO.FileLoadException: Could not load file or assembly 'MySql.Data.OpenTelemetry' or one of its dependencies. Strong name signature could not be verified.  The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Assembly Load Trace: The following information can be helpful to determine why the assembly 'MySql.Data.OpenTelemetry' could not be loaded.
=== Pre-bind state information ===
LOG: DisplayName = MySql.Data.OpenTelemetry
(Partial)
WRN: Partial binding information was supplied for an assembly:
WRN: Assembly Name: MySql.Data.OpenTelemetry | Domain ID: 2
WRN: A partial bind occurs when only part of the assembly display name is provided.
WRN: This might result in the binder loading an incorrect assembly.
WRN: It is recommended to provide a fully specified textual identity for the assembly,
WRN: that consists of the simple name, version, culture, and public key token.
WRN: See whitepaper http://go.microsoft.com/fwlink/?LinkId=109270 for more information and common solutions to this issue.
LOG: Appbase = file:///C:/Users/xyz/source/repos/TestGrafanaOpenTelemetry/TestGrafanaOpenTelemetry/
LOG: Initial PrivatePath = C:\Users\xyz\source\repos\TestGrafanaOpenTelemetry\TestGrafanaOpenTelemetry\bin
Calling assembly : (Unknown).
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\Users\xyz\source\repos\TestGrafanaOpenTelemetry\TestGrafanaOpenTelemetry\web.config
LOG: Using host configuration file: C:\Users\xyz\OneDrive - StoneEagle F&I\Documents\IISExpress\config\aspnet.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.
LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
LOG: Attempting download of new URL file:///C:/Users/xyz/AppData/Local/Temp/Temporary ASP.NET Files/vs/f70b5a77/80574c61/MySql.Data.OpenTelemetry.DLL.
LOG: Attempting download of new URL file:///C:/Users/xyz/AppData/Local/Temp/Temporary ASP.NET Files/vs/f70b5a77/80574c61/MySql.Data.OpenTelemetry/MySql.Data.OpenTelemetry.DLL.
LOG: Attempting download of new URL file:///C:/Users/xyz/source/repos/TestGrafanaOpenTelemetry/TestGrafanaOpenTelemetry/bin/MySql.Data.OpenTelemetry.DLL.
LOG: Using application configuration file: C:\Users\xyz\source\repos\TestGrafanaOpenTelemetry\TestGrafanaOpenTelemetry\web.config
LOG: Using host configuration file: C:\Users\xyz\OneDrive - StoneEagle F&I\Documents\IISExpress\config\aspnet.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.
LOG: Post-policy reference: MySql.Data.OpenTelemetry, Version=8.2.0.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d
ERR: Failed to complete setup of assembly (hr = 0x80131045). Probing terminated.
Stack Trace:
[FileLoadException: Could not load file or assembly 'MySql.Data.OpenTelemetry' or one of its dependencies. Strong name signature could not be verified.  The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)]
[FileLoadException: Could not load file or assembly 'MySql.Data.OpenTelemetry, Version=8.2.0.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d' or one of its dependencies. Strong name signature could not be verified.  The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)]
System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) +0
System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) +37
System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) +159
System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection) +80
System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +22
System.Reflection.Assembly.Load(String assemblyString) +29
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +38
[ConfigurationErrorsException: Could not load file or assembly 'MySql.Data.OpenTelemetry, Version=8.2.0.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d' or one of its dependencies. Strong name signature could not be verified.  The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)]
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +721
System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +195
System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +45
System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +172
System.Web.Compilation.BuildManager.GetPreStartInitMethodsFromReferencedAssemblies() +91
System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded) +111
System.Web.Compilation.BuildManager.ExecutePreAppStart() +156
System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException) +692
[HttpException (0x80004005): Could not load file or assembly 'MySql.Data.OpenTelemetry, Version=8.2.0.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d' or one of its dependencies. Strong name signature could not be verified.  The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +660
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +89
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +189
`
Add any other context about the problem here.

@gregprior I've been unable to reproduce this issue using the "ASP.NET Web Application (.NET Framework)" template in Visual Studio 2022. I selected the "Web API" option and have a minimal project where the application starts correctly.
Would you mind providing a sample project that shows this issue?

My application is on .Net Framework using .Net 4.8.
Traces instrumentations  states that MySql.Data is not supported on .NET Framework.
@matt-hensley , here is the sample application that I created: TestGrafanaOpenTelemetry.zip

@matt-hensley, I tried creating a new test package in VisualStudio 2022 and received the same error loading the MySql.Data.Opentelemetry package when trying to run it.

I created a new solution using the "ASP.NET Web Application (.NET Framework)" template
Selected "NET Framework 4.8.1"
Created an empty project. The only thing I changed was unchecking the "Configure for HTTPS"
Added the Grafana.OpenTelemetry.Base.0.8.1-beta NuGet package using the GUI
Clicked the green triangle icon to run the project.

authors: gregprior matt-hensley

repo: grafana/grafana-opentelemetry-dotnet


text:
Docs: Plugin E2E - Panel plugin docs

What this PR does / why we need it:
This PR adds a guide on how to e2e test panel plugins. Feedback on parts that are missing are very much welcome!
I feel like we should say something about the complexity that comes with testing visual components such as lines and curves, and why we discourage screenshot testing. At the same time, I want plugin authors to be free to chose whatever path they think is right. WDYT?
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

I have edited this document in https://github.com/grafana/plugin-tools/pull/852/commits. Please take a look and ensure that no errors have been introduced.

Looks good, thanks Joe!

repo: grafana/plugin-tools


text:
Support of python 3.6

Hi @grahamgower,
I noticed that since new version of demesdraw v0.1.1 Python3.6 is no longer supported. Maybe it is possible to include it back? Some of my projects still use version 3.6 and I would like to use demesdraw there.

Ah, sorry. I released I hadn't actually tested 3.6 (not even in CI), so I just assumed it was broken. I'll add 3.6 to the CI tests and make another release ASAP.

Thank you very much @grahamgower, that was really fast!

authors: grahamgower noscode

repo: grahamgower/demesdraw

license: ISC


text:
Illegal stateexception for suspicious coordinates for node - Europe - GH 4.0 Web Jar

Describe the bug
Graphhopper is not able to import europe latest pbf
What happens at some point:
java.lang.RuntimeException: Couldn't process file europe-latest.osm.pbf, error: Suspicious coordinates for node 60162619: (36.1718877,36.737518) vs. (36.1701893,36.738058,NaN)
Someone already had that problem in June 2021 with graphhopper 3.0 it seems, but the bug report was closed:
https://discuss.graphhopper.com/t/about-illegalstateexception-for-suspicious-coordinates-for-node/6602/2
To Reproduce
Europe latest from about 2 weeks ago and yesterday (16.Nov 2021, aroung 20:00 UTC)
from: https://download.openstreetmap.fr/extracts/
Expected behavior
That it imports without an Error and bulds the graph cache
System Information
graphhopper 4.0 release JAR, Windows 10, OpenJDK 11.0.12
Screenshots & Logs
graphhopper_import_error_2_weeks_old_europe.txt
graphhopper_import_error_16_nov_2021.txt

I'll try to reproduce this for: https://download.openstreetmap.fr/extracts/europe-latest.osm.pbf

The 'suspicious' coordinate seems to be right at the border of the Europe extract, near the border between Turkey and Syria: https://graphhopper.com/maps/?point=36.171888%2C36.737518. That could be part of it.

Can you please also share the config.yml file you used?

Strange thing is:
In both cases it is the Lng/Lat of that point in the Exception message
java.lang.IllegalStateException: Suspicious coordinates for node 59876869: (36.1718877,36.737518) vs. (36.1701893,36.738058,NaN)
java.lang.IllegalStateException: Suspicious coordinates for node 60162619: (36.1718877,36.737518) vs. (36.1701893,36.738058,NaN)
But if we look at the Node IDs:
https://www.openstreetmap.org/node/59876869
https://www.openstreetmap.org/node/60162619
One time on the Falkland Islands on the southern hemisphere and the other time new Hannover/Germany

One time on the Falkland Islands on the southern hemisphere and the other time new Hannover/Germany

Ok this is strange indeed :)

Like the example config but with following changes:
profiles:
- name: motorcycle_fastest
vehicle: car
weighting: fastest
- name: motorcycle_shortest
  vehicle: car
  weighting: shortest

- name: motorcycle_curvature
  vehicle: motorcycle
  weighting: curvature

profiles_ch:
- profile: motorcycle_fastest
- profile: motorcycle_shortest
- profile: motorcycle_curvature

ok just finished my test with the original config from:
https://github.com/graphhopper/graphhopper/blob/master/config-example.yml
With the Europe file form yesterday
Again: Exception
Log:
original_config_exception_europe_16_nov_2021.txt

I can reproduce this, but only for the extract from openstreetmap.fr. Using the extract from Geofabrik everything seems fine.

One time on the Falkland Islands on the southern hemisphere and the other time new Hannover/Germany

No, wait. These are internal GH node IDs, not OSM node IDs. The information that is actually relevant is this:
Couldn't properly add edge with osm ids:[1005030478, 4170133500, 1005030422, 4170133499, 8484835379, 1387855317, 7410227416, 7410227427, 186618975, 1005030419, 3170650878, 9126391916, 186618977, 6579545603, 186618979, 1005030376, 9126308678, 186618980, 6579545796, 6579545795, 1005030390, 186618983, 186618984, 6579545781, 6579545810, 6579545769, 7410148598, 6579545764, 1005030470, 6579545733, 3170650958, 6579545837, 1005030371, 186618985, 4170099792, 8111781662, 186618986, 8111781663, 2018655435, 5346676488, 1005030441, 186618987, 4170099870, 186618988, 4170099871, 186618989, 8111841551, 8111841552, 1286376293, 186618992, 4065449517]

and this corresponds to this way: https://www.openstreetmap.org/way/113319111, so it is in Syria (very close to the extract borders) indeed. Is there a smaller extract that covers this area? For example Turkey? I could not find one here: https://download.openstreetmap.fr/extracts/

Geofabrik europe import went through successfully over the night. Thanks for the help.

I also tried importing the openstreetmap.fr extract using the current master. This also works. So there seems to be some issue that only shows up for this specific extract that was fixed between the 4.0 release and now...

I've had this kind of error two days in a row now for two consecutive PBFs for Ukraine.  GH 4.0, Geofabrik download for Ukraine: https://download.geofabrik.de/europe/ukraine-latest.osm.pbf
The issue occurs with this way: https://www.openstreetmap.org/way/846903409 around 47.813205,29.8186892
The gh error happened just after some user edited the way in OSM two days ago.
Error:
com.graphhopper.reader.osm.OSMReader     : Couldn't properly add edge with osm ids:[2212875445, 9514052350, 2212875467, 9514052351, 9514052622, 2212875505, 2212875518, 9514052352, 2212875527, 2212875540, 9514052354, 2212875557, 2212875568, 9514052353, 2212875599, 2212875612, 2212875618, 2212875635, 7049294558, 2212875646, 2212875667, 2212875726, 7049294559, 7049294561, 7049294560, 7049294566, 9514053097, 9514053096, 7049294564, 7049294563, 7049294562, 7049294565, 2212875741, 7010865446, 2212875748, 2212875759, 2212875765, 2212875775, 9514053502, 2212875781, 2212875785, 2212875799, 9514053501, 2212875807, 9514053500, 2212875805, 2212875809, 2212875816, 2212875823, 2212875838, 2212875852, 2212875859, 2212875861, 9514180881, 2212875886, 9514180883, 2212875903, 9514180882, 2212875907, 2212875892, 9514180884, 2212875890, 9514053377, 2212875877, 2212875873, 2212875865, 2212875863, 2212875867, 9514053378, 2212875875, 9514180885, 2212875911, 2212875920, 9514053362, 9514053346, 2212875934, 2212875944, 2212875946, 2212875950, 2212875959, 2212875969, 2212875986, 2212876011, 2212876016, 2212876026, 2212876032, 7051535395, 2212876039, 9514180741, 2212876037, 2212876035, 2212876028, 2212876022, 2212876020, 2212876015, 9514373967, 9514373990, 2212875996, 2212876000, 7051535394, 2212875998, 2212875988, 2212875970, 2212875967, 2212875965, 2212875961, 7051535391, 9514374014, 2212875955, 7051535393, 2212875957, 7051535392, 2212875997, 9514377317, 2212876030, 9514377318, 2212876045, 2212876049, 9514377319, 2212876053, 2212876055, 8091548008, 2212876060, 7051535390, 2212876149, 7051535389, 2212876172, 2212876187, 2212876267, 2212876282, 2212876322, 8159113891, 2212876352, 2212876361, 2212876373, 9514377632, 2212876394, 2212876401, 2212876415, 2212876435, 2212876486, 2212876502, 2212876527, 9514377610, 2212876533, 2212876555, 2212876579, 2212876633, 5415957630, 2212876664, 2212876711, 2212876779, 2212876812, 2212876818, 2212876831, 2212876833, 2212876835, 2850392159, 2212876837, 2212876839, 2212876847, 8060497997, 8060497998, 4743246351, 8060498000, 2212876851, 8060497999, 4743246349]

java.lang.IllegalStateException: Suspicious coordinates for node 2009748: (47.813205,29.8186892) vs. (47.8135259,29.818154,NaN)

After some research here is the method that fails:
private void checkCoordinates(int nodeIndex, GHPoint point) {
        final double tolerance = 1.e-6;
        if (Math.abs(nodeAccess.getLat(nodeIndex) - point.getLat()) > tolerance || Math.abs(nodeAccess.getLon(nodeIndex) - point.getLon()) > tolerance)
            throw new IllegalStateException("Suspicious coordinates for node " + nodeIndex + ": (" + nodeAccess.getLat(nodeIndex) + "," + nodeAccess.getLon(nodeIndex) + ") vs. (" + point + ")");
    }

Osm way id that fails: 846903409

Did you try using master?

In my software I use GH4.0 dependency from maven.
Here is another smaller file with the same error (34Mb) : https://s3.eu-central-1.amazonaws.com/akcent.pub/osm/odessa_oblast-latest.osm.pbf
The problem in gh4.0 occurs for the way https://www.openstreetmap.org/way/1012228399
I tried to run tests with this file for master - everything imported fine. But master is already 5.0-snapshot and I'm not sure it is production ready.
Is there a possibility to get fix for current GH4.0 version?
Besides I didn't manage to run tests for 650Mb Ukraine file due to constant OOM error even with 24Gb heap. Not sure if it should be another issue or just me.

But master is already 5.0-snapshot and I'm not sure it is production ready. Is there a possibility to get fix for current GH4.0 version?

master can usually be considered stable, but I just released 5.0-pre1 as well.

Besides I didn't manage to run tests for 650Mb Ukraine file due to constant OOM error even with 24Gb heap. Not sure if it should be another issue or just me.

I just ran the OSM import for ukraine-220219.osm.pbf from Geofabrik (one profile: car/fastest) without errors using -Xmx20g -Xms20g.

Using ukraine-220219.osm.pbf from Geofabrik with a car/fastest profile I get this error:
java.lang.IllegalStateException: Suspicious distance for edge: 934005 2277655-2277656 145.892 vs. 355.78495746511203, difference: -209.89295746511203

using GH 3.2 and this error:
java.lang.IllegalStateException: Suspicious distance for edge: 925560 2269210-2269211 145.892 vs. 355.78810307356486, difference: -209.89610307356486

using GH 4.0. I do not get an error using ukraine-220101.osm.pbf.

For Ukraine I ended up splitting that way 846903409 into several segments yesterday and now the problem during import is gone for geofabrik pbf. So for current snapshot I think there is no problems with suspicious coordinates.
But this https://s3.eu-central-1.amazonaws.com/akcent.pub/osm/odessa_oblast-latest.osm.pbf - still has this problem for gh4.0

Edit: Ukraine had this error only during several days: 17-19 Feb I think. I have saved pbf for 19 Feb to replicate the problem in case you need it.

Ok thanks, but I just took it from here: https://download.geofabrik.de/europe/ukraine-220219.osm.pbf

But this https://s3.eu-central-1.amazonaws.com/akcent.pub/osm/odessa_oblast-latest.osm.pbf - still has this problem for gh4.0

Can you just use GraphHopper 5.0-pre1? It's here: https://repo.maven.apache.org/maven2/com/graphhopper/graphhopper-parent/5.0-pre1/

I guess I have to refactor a bit in order to use 5.0 but sure, I'll give it a try
Thanks.

I don't get the error for moldova-latest.osm.pbf from Geofabrik. Do you get the error for any most recent OSM area? If so we should try to grab a mini-extract that reproduces the error via the 'Export' feature on openstreetmap.org for example.

The problem is a bit strange. For Ukraine it's gone now as I've modified the problematic way.
But when I pinpointed the location of the problem yesterday, I tried to extract just that area to be able to debug more easily. And to my surprise when I extracted just area with the full way using https://download.bbbike.org/ - I couldn't reproduce the problem.
Then I decided to extract the whole Odessa region - to which that problematic way belongs - I've downloaded it from http://download.openstreetmap.fr/extracts/europe/ukraine/ - and I had the same error but this time in Moldova for way 1012228399 in Ucrainca  town. Because Odessa area contains some border areas of Moldova.
So I tried to export just Ucrainca area using https://download.bbbike.org/ and again - the problem was gone for that pbf. But I've just downloaded http://download.openstreetmap.fr/extracts/europe/ukraine/odessa_oblast-latest.osm.pbf a few minutes ago, and the problem still exists during import on GF4.0:
Suspicious coordinates for node 114341: (46.4298027,29.2784187) vs. (46.4300336,29.2783441,NaN)

So, it looks like the problem depends on area that is exported, and only in some cases this glitch occurs.

I managed to reproduce the error for this mini OSM file (a small extract around the 'suspicious coordinate' taken from your odessa_oblast file):
https://gist.github.com/easbar/c7d9bd99208ed1f39aa8536e122d4d33

I am pretty sure this is somehow related to OSM ways containing missing nodes. This happens we extract an area such that some ways are only partly included. Dealing with this was quite a headache before #2448 so not sure if it is worth fixing this for GH <=4.0.

I've been using graphopper about 5 years, and this error happened only once to me, so I guess it's pretty safe just to ignore this issue for now.
Thanks for feedback on this error.

authors: akamuza easbar landliebe

repo: graphhopper/graphhopper


text:
Can jar packages specify multiple pbf files to run?

I want to load map data for multiple continents, but the pbf file downloaded from openstreemap is separate for each continent, so Can jar packages specify multiple pbf files to run?  so I don't have to merge the pbf files

Please use our forum for usage related questions like these.


text:
Documentation links are broken

The links here still point to the wiki:
https://github.com/graphhopper/jsprit/blob/master/docs/Classical-Problems-Examples.md
There are a few more that you can find out via
grep wiki docs/*

Hi! @karussell
Is this broken link from the repository?
If I'm correct the please review the PR.

It has been solved .Need to close this issue
#350

authors: jsroyal karussell

repo: graphhopper/jsprit


text:
Added docs for evm and non-evm (firehose) chain integrations

We only have documentation on new chain integrations under the Firehose section, and we don't mention how new EVM chains may already be Graph Node compliant. In addition, the general notes on integrations through Firehose do not cover the Graph Node and graph tooling integration part, even though we have some valuable docs in Graph Node's repo.
This PR introduces:

a new high-level page, under Indexing, which states how new chains may be integrated with Graph Node
detailed documentation for EVM-based chains (how to connect to Graph Node and do a simple integration test)
references other existing Firehose documentation, targeting integrators

I am not too sure about the proposed Integrating New Networks title. Even though we typically refer to "new chains", we do say networks when referring to supported chains on the hosted service and the networks. An alternative could be on-chain data sources but probably not SEO-friendly. Happy to tweak it and organize it differently.
@graphprotocol/docs-reviewers , let me know what you think! 👍

I've realized some inconsistencies around chains and networks. Do we have a preference?

I think this looks reasonable as a starting point, but I think there are still some open questions on the extent to which we want to promote direct integrations, vs. integrations via substreams, and I expect there will be some things which will trip up external teams.

Agree. I can revise this later once we have better internal alignment.

repo: graphprotocol/docs