text:
Cannot transfer discussions (giscus-related?)

I have two public repos set up for giscus. I wanted to transfer existing discussions from one repo to another, but cannot (see https://github.com/github/feedback/discussions/3381). My question: do you know whether it would help if I temporarily disabled giscus access to one or both of the repos? Does giscus's connection even have any effect on the ability to transfer discussions? Or is this simply a GitHub Discussions glitch?
Thanks in advance for any related info you could provide.

I doubt giscus has any effect on this. It only interacts with your repository's discussions when it creates new discussions, comments, replies, and adding/removing reactions. Anything else from the discussions feature itself is untouched.
It's likely there are some issues on GitHub's side when they transfer the discussions. One thing I want to make sure though: is giscus installed on both repositories? If not, try installing it first. Maybe GitHub refuses to transfer the discussions if there are discussions/comments made through giscus but it is not installed on the target repository.
If you have already installed giscus on both repositories, then I can't think of any other causes. There's nothing else we can do other than waiting for GitHub to fix it.

Thanks! And giscus definitely is installed on both repos. So, yes, we'll have to hope GitHub fixes this, soon. Given that these other reports are many months old, I'm not optimistic. :-(

Other possible workaround: convert the discussion into an issue first, then transfer the issue, and then convert the issue into a discussion. Any threads will be flattened though, and it might still fail somewhere along the way, so maybe you want to use a temporary repository to test this first.

I actually did consider the "try it somewhere else" approach, but haven't done it yet because, as you say, I feared it would be stuck there.However, my discussions are small enough that I can risk flattening then with a conversion to issues, so I'll try that. Thanks.

Follow-up: I tried converting two discussions to issues, then transferring them, then converting them back to discussions. Those went through, but as of now it appears the comments got lost in the process (even though the GitHub messages indicated that they would be retained). It was worth a try, though.

Workaround found at https://github.com/github/feedback/discussions/3381#discussioncomment-2655724. Thanks for the report!

And, again, thank you, @laymonage !

authors: brycewray laymonage

repo: giscus/giscus


text:
non github users

i noticed that in the readme, it was mentioned that visitors can comment directly in the forum with giscus app. however when i go to sample hosted website, i see that in the github discussion forum embedded, you have to sign in with github. so does that mean for users to directly post in forum, they have to sign in or make a github account?

https://github.com/giscus/giscus/issues/65

https://github.com/giscus/giscus/issues/65

Alternatively, visitors can comment on the GitHub Discussion directly.

It just means that instead of using giscus, visitors can also open the discussion on GitHub and leave a comment on GitHub directly, instead of via giscus.
Currently GitHub sign-in is required. Closing as duplicate of #65.

source: gharchive/issue

authors: karkir0003 laymonage nschonni

license: MIT

license_type: permissive

license_source: github-api


text:
Importing shapefile failed

geemap version: 0.6.14
Python version: 3.6.9

Description
I try to import a shapfile from a local folder and it failed
What I Did
#recuperer les ecozones de Remi
import os

home_path = os.path.expanduser('~')
ecozone_shp = home_path + '/CIFRAD/ecozones/gez_2010_wgs84.shp'
ecozone = geemap.shp_to_ee(ecozone_shp)
m.addLayer(ecozone, {}, 'ecozone')

and I get the following error

local variable 'part' referenced before assignment
Could not convert the geojson to ee.Geometry()
stat: path should be string, bytes, os.PathLike or integer, not NoneType

Your shapefile might have some invalid geometries. You can try importing the shapefile using the GEE JavaScript Code Editor. See here.

I wasn't able to upload the file on GEE javaScrip Code Editor. I manually change it to a raster to import it. Sorry for bothering

repo: giswqs/geemap


text:
Improve Markdown Rendering when using Webview

Opening Repos with a lot of Markdown content in its Readme.md file crashes the app. Also in a lot of cases even if the Markdown is not huge it is unable to render it completely.
Examples:

https://github.com/transloadit/uppy
https://github.com/mdn/content
https://github.com/openpgpjs/openpgpjs

Thanks for the feedback.
Could you please provide more device info, for example, Android or iOS, System version?

@pd4d10 I am having the same issue, on latest fdroid build 1.11.1.
Device: Google Pixel 4 non-xl, Android 11 Janurary 2021 security update.
The other application, OctoDroid which I was looking to switch from as this integrates other services like Gitlab, also had similar issue was was addressed in an earlier update.

I have the same issue. How about setting the flutter render engine as default before this issue is properly solved?

Yep, it seems that the Android webview widget may have some problems, for example #123 and #194

setting the flutter render engine as default

Makes sense. We could make Flutter render engine as default on Android.

The reason we prefer Webview is that inline HTML is not supported in the Flutter markdown widget.
BTW, this issue could be submitted to the official repo: https://github.com/flutter/flutter/issues?q=is%3Aopen+is%3Aissue+label%3A"p%3A+webview"

repo: git-touch/git-touch


text:
Detect current branch

Does .git actually have a default branch (not a default branch name, but a "main" branch), or is it a GitHub concept

Found an article that says:

Technically, Git has no official concept of the default branch

article: https://usethis.r-lib.org/reference/git-default-branch.html

Note that it says "current" and not "default"

Forgot to update the description, this issue is now more concerned towards detecting the current branch, which #98 addresses.

authors: hojelse joglr

repo: git-visual/git-visual


text:
Typescript support

Hi
I noticed this commit which gives typescript support https://github.com/gitbrent/bootstrap-switch-button-react/commit/0881898ac9d7f19306524b615fc2cbb4178d86cc
Any timeline on the next release? I'm currently working around by using// @ts-ignore

Thanks for the reminder!
Version 1.1.0 has been released.

authors: choweiyuan gitbrent

repo: gitbrent/bootstrap-switch-button-react


text:
🛑 yt.artemislena.eu is down

In 4d976dd, yt.artemislena.eu (https://yt.artemislena.eu/) was down:

HTTP code: 502
Response time: 6967 ms

Resolved: yt.artemislena.eu is back up in 60bde26.

repo: gitetsu/invidious-instances-upptime


text:
🛑 search.mascotboi.xyz is down

In 6a26d8f, search.mascotboi.xyz (https://search.mascotboi.xyz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: search.mascotboi.xyz is back up in 981212b after 17 minutes.

repo: gitetsu/librex-instances-upptime


text:
🛑 search.sethforprivacy.com is down

In a6d2ccd, search.sethforprivacy.com (https://search.sethforprivacy.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: search.sethforprivacy.com is back up in 42782dd after 5 minutes.

repo: gitetsu/whoogle-instances-upptime


text:
🛑 whoogle.dcs0.hu is down

In b1a9bce, whoogle.dcs0.hu (https://whoogle.dcs0.hu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: whoogle.dcs0.hu is back up in c16c1fc.


text:
🛑 DynDNS afraid is down

In 3af5cfd, DynDNS afraid (https://freedns.afraid.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DynDNS afraid is back up in 54eb575 after 10 minutes.

repo: gitgrub/uptest


text:
[GHSA-mpwj-fcr6-x34c] Yarn untrusted search path vulnerability

Updates

Affected products
CWEs
Description
Summary

Comments
The refinement of this security advisory is aimed at providing a clear, concise, and actionable report for stakeholders, enhancing understanding of the vulnerability's implications, and facilitating swift and effective remediation actions. By emphasizing the severity assessment and mitigation strategies, this updated advisory aligns with best practices for security reporting and contributes to the proactive safeguarding of the Node ecosystem against potential threats.

CWE Additions.

Closed without comment. Reopening.

source: gharchive/pull-request

repo: github/advisory-database


text:
Fix typo in docstring

Merge / deployment checklist

[x] Confirm this change is backwards compatible with existing workflows.
[x] Confirm the readme has been updated if necessary.
[x] Confirm the changelog has been updated if necessary.

The failures are not caused by this PR.

CI should be fixed now.

authors: aeisenberg esbena

repo: github/codeql-action


text:
The note refers to January 2024 in the future tense

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository#:~:text=In January 2024%2C GitHub Classroom will change the way student repositories are created from starter code repositories
What part(s) of the article would you like to see updated?
Here is a sentence, "In January 2024, GitHub Classroom will change the way...".
But January 2024 has already passed, so we can't talk about it in the future tense
Additional information
it uses a reusable file - https://github.com/github/docs/blob/main/data/reusables/classroom/note-on-assignment-changes.md

@Denis-GH Apologies, didn't see this new issue until after your previous had been reopened. I'll go ahead and close out this issue given we've reopened https://github.com/github/docs/issues/33078 - thank you for submitting a new issue, though! 💛

repo: github/docs


text:
typo

启 --> 弃

Why:
Closes [issue link]

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for the latest deployment event in your pull request's timeline, then click View deployment).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

Thanks for opening this pull request! Unfortunately, we are not able to accept pull requests for translated content. Our translation process involves an integration with an external service at crowdin.com, where all translation activity happens. We hope to eventually open up the translation process to the open-source community, but we're not there yet.
See https://github.com/github/docs/blob/main/CONTRIBUTING.md#earth_asia-translations for more details.
Someone pointed out this typo a few days ago, so we have an internal issue open for the fix.

authors: janiceilene yuandongx


text:
Update index.md

Why:
Closes [issue link]

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for the latest deployment event in your pull request's timeline, then click View deployment).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

Just a practice to learn pull requests, thaught to make a change in the content, that I think fits the context.
Thank you 👍

Just in a practice of learning pull requests, made a change in the content, that I think fits the contest.
Thank you 👍

Por qué:
Cierra [enlace del problema]
Lo que se está cambiando:
Marque lo siguiente:

[ ] He revisado mis cambios en la puesta en escena (busque el último evento de implementación en la línea de tiempo de su solicitud de extracción y luego haga clic en Ver implementación).
[ ] Para los cambios de contenido, he completado la lista de verificación de auto-revisión.

Impacto del escritor (Esta sección es solo para miembros del personal de GitHub):

[ ] Esta solicitud de extracción afecta a la experiencia de contribución

[ ] He añadido la etiqueta "impacto del escritor"
[ ] He añadido una descripción y/o una demostración en vídeo de los cambios a continuación (por ejemplo, un "vídeo antes y después")

#7958

diff --git a/content/github/setting-up-and-managing-your-github-profile/index.md b/content/github/setting-up-and-managing-your-github-profile/index.md
index 503052faa574..97402939081c 100644
--- a/content/github/setting-up-and-managing-your-github-profile/index.md
+++ b/content/github/setting-up-and-managing-your-github-profile/index.md
@@ -10,6 +10,7 @@ versions:
ghae: '*'
topics:

Profiles

Contribution
children:
/customizing-your-profile
/managing-contribution-graphs-on-your-profile

@LakshmanPalli Thanks so much for opening a PR! I'll get this triaged for review :zap:

@LakshmanPalli I talked to the team and they pointed out that 'contribution' does not come under the allowed topic list. For more information please checkout this docs  ⚡
Take a look at the contributing.md to learn how to contribute in this repo. You can open a discussion if you have any questions or check out issues with the help wanted label. :sparkles:

authors: LakshmanPalli Mexicool ramyaparimi


text:
添加DS_Store

Reasons for making this change:
TODO
Links to documentation supporting these rule changes:
TODO
If this is a new template:

Link to application or project’s homepage: TODO

Thanks, but see Global\macOS.gitignore

repo: github/gitignore

license_source: bigquery


text:
Added .DS_Store for Mac operating system!

Reasons for making this change:
.DS_Store files are useless and annoying so I am preventing them from being committed!

It would be better to setup a global gitignore with macOS.gitignore to ignore all macOS related files all together.


text:
'create' is not a git command

I've installed Hub via Homebrew and am trying to create a new repo by running git create -d 'Notes & implementation of essential design patterns in Javascript' inside my project folder. It's giving me an error:
git: 'create' is not a git command. See 'git --help'.

Did you mean this?
	reset

Running hub version shows it's the latest version:
git version 2.5.4 (Apple Git-61)
hub version 2.2.3

Have you tried run hub create -d 'you-repo-name' instead of using git? Since the create command is provided by hub. Otherwise you can specify git as the alias of hub, that is actually calling hub too.

authors: afang linesh-simplicity

repo: github/hub

license: mit


text:
Add git-patch icon

A common use case is to visual patches so having a patch icon will be a great addition.

@ligaz can you explain a little further the use cases you have in mind?

Hey @jglovier
There are two use cases that I can point to:

Icon for TortoiseGit
Icon for Telerik AppBuilder. We are currently using a couple of the Octicons there.

Per @cameronmcefee's comment in #44, we add icons as they are needed for our own purposes rather than by request, since our goal is a GitHub set rather than a fully featured one like may of the great ones out there already.
Since Git patching isn't a feature currently supported in the GitHub Desktop apps, or the .com workflow, this isn't one we currently have a good reason to add.
Thanks for the suggestion. :heart: I'll reopen if we decide to add it in the future.

authors: jglovier ligaz

repo: github/octicons


text:
Label merge strategy

Prerequisites:
N/A
New Feature
At the moment labels are enforced at this moment.
I would like to have the option to only add/update labels and do not remove any labels that other github actions or developers want to use.
This properly means a merge strategy for labels. Overwrite vs Append

The following labels will help us to estimate the pull request size:

GitHub label
Lines count

size/XS
1 - 10

size/S
11 - 30

size/M
31 - 100

size/L
101 - 500

size/XL
501 - 1000

size/XXL
1001+

@decyjphr This issue would be closed. It was implemented here https://github.com/github/safe-settings/pull/408 and is available from 2.0.21

authors: dgroup jetersen svg153

repo: github/safe-settings

license: ISC


text:
Comment here to be added as a collaborator

Comment below - you can say anything
We will all be using this repository today. Even though it's public, you will not be able to make changes until you're given the correct permissions. We've automated this process via the GitHub API and some fancy chatops. Once you comment, you'll be added as a collaborator.
You'll also start to receive a lot of emails. (:exclamation:) You can slow these down immediately by clicking the 'unsubscribe' button.

Hi

Hello!

dougdiego

GM!

Levey

hello

hello

access pls

Hi

:tada: @garyjzhao, @anayadesign, @dougdiego, @cphalaswal, @senthil33, @lbaskar, and @santhimuthusamy are now  repository collaborators. :balloon:

AP

Amit

hi

Hi

Test comment

add me

hello

:tada: @smummidivarapu1, @sohambhattacharjee, @apanchanathan, @amitdpatel, @sswaminathanart, @vijayayyar, @bharat-patel, and @tyuengithub are now  repository collaborators. :balloon:

Hello

:tada: @govind999 is now a repository collaborator. :balloon:

hello

Hi

Hi

@githubteacher

Hi

:tada: @aramaniart, @asharma-art, and @VenkataKakaraparthy are now  repository collaborators. :balloon:

authors: VenkataKakaraparthy amitdpatel anayadesign apanchanathan aramaniart asharma-art bharat-patel cphalaswal dougdiego garyjzhao githubteacher govind999 lbaskar santhimuthusamy senthil33 smummidivarapu1 sohambhattacharjee sswaminathanart tyuengithub vijayayyar

repo: githubschool/refactored-fiesta


text:
Ignore all comits when .gitleaksignore fingerprint lacks SHA

Description:
This fixes #1155.
Checklist:

[x] Does your PR pass tests?
[x] Have you written new tests for your changes?
[x] Have you lint your code locally prior to submission?

Hi, Is it possible to merge this soon?
Thanks,

It would be great to see this in, is there anything else it needs?  With a large distributed dev team, a merge rather than rebase PR strategy, and a diverse technology set we generally have issues with multiple exceptions being required each time a change is merged to another branch due to the additional merge commit hashes.  I believe that this would make it much easier to ignore once where we cannot use a regex exclusion flag.

authors: BenPhegan C1ph3R-s rgmz

repo: gitleaks/gitleaks


text:
Develop

Authentication with github coded.
@pocman @jacobtardieu Please, review and test. Next time I will branch from develop and pull request into develop instead of master.

J'ai une 404 quand je clique sur http://localhost:9000/authenticate/github

T'as un neo4j qui tourne ?

Peut être pas. :-) mais ça devrait lever une exception.
Le 28 juin 2015 13:43, "Nicolas Joseph" notifications@github.com a écrit :

T'as un neo4j qui tourne ?
—
Reply to this email directly or view it on GitHub
https://github.com/gitlinks/gitrank-web/pull/8#issuecomment-116262723.

@pocman @jacobtardieu Corrected some things

Juste pour information, alt+enter sur le nom d'une méthode permet d'appliquer le type de retour de la méthode ;-)

authors: callicles pocman

repo: gitlinks/gitrank-web


text:
publish release notes

could you publish release notes or a "changeme.md" so we can understand the changes present in each release.

A new CHANGELOG summary has been added to the README on this repo. This log will be used to track ongoing updates across all GitPitch products and services.

authors: gitpitch timveil

repo: gitpitch/gitpitch


text:
v1.3.0 Prep

Next release: v1.3.0 - Monday October 2nd
Note: iPhone is currently in v1.2.0 and Android is currently in v.1.1.0. Going to bump version number to 1.3.0 so that they both match

Today (September 28) - Plan is to close and merge all open PRs that are safe to merge

The next few days, we should focus on fixing any bugs and applying UI fixes to anywhere that needs it. Please tag this issue on those PRs. We'll put a hold to merging large features/updates to the app until after Monday.

Some things that need updating:

[x] ImageZoom component shows a black screen when image is tapped (iPhone + Android)
EDIT - Just seems to be the native module not linking properly. Thanks @machour for pointing this out

[X]  Font on events screen seems too bold on iPhone (only seeing this issue myself, @machour can't reproduce it which is interesting )

[x] Something that I've been thinking, update fonts in app to Nunito

Have been working on a React Native app this past week that uses this font and it really looks crisp. Will be also be perfect to have both platforms use the same font. Will give this a shot :)

[X] Change notifications count badge, make number slightly larger/prominent

Instead of splitting these concerns into separate tickets, I'm okay with having PRs for each but just using this ticket ID. Anything that you can see that we most definitely need to include, don't hesitate to comment it here and we'll add it in the list.
EXCITED TO GET A NEW RELEASE OUT!

After our release, we'll spend some significant amount of time improving a number of things in the app:

Streamlining release flow and CI using Fastlane and Buddybuild or bitrise
Rearchitecting our state to leverage normalizer (progress began here #350)
Moving over to GraphQL incrementally (progress began here #347)
Lay out a more concrete UI guideline flow (similar to how buttons are being mapped here #374)
Keep adding more features! For me the real big wins are things like Enteprise support as well showing pull request review comments for example. But there's still a ton of amazing things left to add

All the above is for future discussion, but just wanted to put that here in case people where were wondering what's next :)

Implement a solid and verbose v3 client implementing all high level api calls (v3.user.getOrgs(), etc.) and use only the high level api in *.actions.js. No more direct calls to v3.get() and other low level methods.

Super excited for this!!
Side note, can we be sure to use the semver terms for releases (v1.3.0) just in case we have to release a patch?

Yep that's a good point, will make sure to use semver from now on 🙌

@lex111 Just noticed two minor things:

[ ] The 99+ icon doesn't show perfectly for iPhone:

[ ] When Mark all Notifications is tapped, it doesn't refresh the pending and all notifications screens:

[ ] Think we can update the Mark All Notifications Button as green maybe to match the merge button?

Please don't feel like you have to get to this right now. Just putting it here so we can address it before our release on Monday :) (more than happy to take care of it myself)

When Mark all Notifications is tapped, it doesn't refresh the pending and all notifications screens:

This I fixed in #371, but need to check so.

The 99+ icon doesn't show perfectly for iPhone:

Ooops, I'll fix it, admit I did not look at iOS :(
By the way, will we change the fonts so that they have the same everywhere?

This I fixed in #371, but need to check so.

Seems to be what's happening on #371 unfortunately. No worries it isn't anything major breaking. I'll merge it in and we'll triage it in master.

Ooops, I'll fix it, admit I did not look at iOS :(

By the way, will we change the fonts so that they have the same everywhere?

Yep exactly so that's why I don't want you to stress over it, I'm going to be applying UI updates with the font change anyway

#371  is not yet merged, so it's better to write it down there :)

Yep was thinking the same thing :)

@housseindjirdeh Ok, for the weekend I think we'll do it, but the font you can do?

@lex111 Yep I can take care of that :) If not today then tomorrow!

⚠ we need to merge https://github.com/gitpoint/git-point-site/pull/10 and change the host in MarkdownWebView before the release.

hey everyone, I was talking with @machour on gitter about #327 as he said, some user normally keeps his finger on the screen while scrolls the app. In issue screen, we added the long press event and for these users, this long press event could be very annoying.
Personally, I have this exact problem when I use facebook app :/
What do you think about to remove it?

Font on events screen seems too bold on iPhone (only seeing this issue myself, @machour can't reproduce it which is interesting 🤔)

I can't reproduce it too 🤔 Descriptions (grey parts) doesn't look bold at all

Something that I've been thinking, update fonts in app to Nunito

I can try to add Nunito instead of AvenirNext and OpenSans and give you some screenshots !
Excited by this new release 😍 🎉

@machour Noted!
@jouderianjr yep personally very okay with removing the long press entirely :)
@Antoine38660 Interesting i have no idea why it's just me lol 🤔 Would love it if you can help out adding Nunito :) Please let me know as soon as you can how it goes!

🐛 Noticing the private box gets squeezed with long repo titles:

@housseindjirdeh I'll try to fix it.

Here's the new Nanuto font :

iOS

Android
TBC...

@Antoine38660 It looks soooo good, running it on my simulator and its sweet :clap:

:warning: The events screen doesn't immediately update with a language change :thinking:

:warning: We'll need to fix any remaining translations (shouldn't be too many)

:bug: Noticing the private box gets squeezed with long repo titles:

I can not fix it :confused: . I thought to put this Text in another Text component, and then everything is fine, but padding and border do not work.

@chinesedfan maybe you can help? How did you put the icon at the end of the title? At us now a problem with that it is incorrectly displayed an notice "Private", it too is in the end.

Here's the gist I linked to @chinesedfan showing how to flex position something to the right. Unfortunately this is going to be a little trickier since there's already an icon positioned to the far right. We'll have to flex position both the icon and private box as a column view within the whole flexed row.
I can help with that in a few hours when I'm back on my machine :raised_hands:

IssueListItem subtitle looks too bold and title doesn't look bold enough. Should look more like this (in terms of boldness):

Issue parent comment isn't padded with the border bottom properly. We could add functionality to only edit the parent comment if the user is the current user but if we're in a rush we can leave that to a future release and just add the bottom padding

Editing issue comment doesn't show the comment by default.

Exploring now :mag:

@housseindjirdeh might be related to api changes

@housseindjirdeh @lex111 Does the private box problem fixed? The screenshot shows wrong height.  I agree that pending it at the end of the repository name is better than the current left-right structure. But it will meet the same space problem as I mentioned in #387.

@chinesedfan in general, yes, but she decided that the name of the repository was reduced, i.e. not really a solution to the problem. It's strange that there is no way to place something at the end of Text component, given that it can be multi-line.

@lex111 You can add View as a child of Text, then it will flow to the end of the text. For example:
<Text>
  <Text>aaaaaaaaaaa</Text> // very long
  <View style={{ width: 10, height: 10 }} /> // without size, it will throw an error
</Text>

The result is:
aaaaaaaaa
aa<View>

without size, it will throw an error

Now I understand why I had a mistake. And it turns out to dynamically determine the real dimensions through onLayout?

I don't know the inner logic, but network articles say it only works with the size is set. I like this layout except for the following problem:
aaaaaaaaa
aa_<View> // we need padding

aaaaaaaaa  // just one line
_<View>    // but starting with padding is annoy

but starting with padding is annoy

And it starts with a new line?

I mean the text and the view flow in multiple lines. If the length of the text happens to be the length of one line, then after wrapped, the second line will start with the view. But the padding is still there, like the 3rd item in the next screenshot.

By the way, maybe we can chat at Gitter.

@housseindjirdeh when is the release?

@lex111 Literally put it up for iOS app review:

Hopefully by tomorrow it'll be approved and rolled out 🙏

@lex111 Running a production build for a final run through for Android and I'm noticing icon issues 😞

Did you mention running link solved the problem?

^ Nvm, running yarn and link again fixed things :o
Next release rolled out for Android!

authors: Antoine38660 andrewda chinesedfan housseindjirdeh jouderianjr lex111 machour

repo: gitpoint/git-point


text:
🛑 ICORER-SITE is down

In aeaa26e, ICORER-SITE (https://icorer.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ICORER-SITE is back up in 6b75a75 after 13 hours, 49 minutes.

repo: gitsrc/upptime


text:
Rework event system - b227bd5 - deprecated '/sys/kbd/' catchall keys

Is there a new equivalent for catch all keyboard input Handle() events?  Documentation shows this as previously being "/sys/kbd", unable to find a working equivalent since the update.
If it's better to have another event capture method for this type of work, let me know.

Just readded this with the <Keyboard> keyword. And also added <Mouse> to handle all mouse events.

Holy smokes! Thanks for the quick resolution.

authors: cjbassi jalder

repo: gizak/termui


text:
🛑 Address Geocoder is down

In 011b6d5, Address Geocoder (https://geocoder.api.gov.bc.ca/addresses.json?addressString=525 Superior Street%2C Victoria%2C BC) was down:

HTTP code: 502
Response time: 331 ms

Resolved: Address Geocoder is back up in 0567214.

repo: gjlawran/apsmon


text:
Implementação método PUT não aderente RFC9110

Seção https://www.rfc-editor.org/rfc/rfc9110#name-put informa que PUT pode retornar 201 (Created) se no corpo da requisição contiver uma representação que não esteja no repositório e possa ser criada. Atualmente, código retorna 404.

Resolvido com commit #9 (8e991a9)

repo: glcamillo/java-sistemabibliotecas


text:
🛑 Schoelcher is down

In a6b337a, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in 403d2dd after 498 days, 8 hours, 21 minutes.

repo: glefait/martinique-public-websites


text:
🛑 Schoelcher is down

In c19a6c5, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in bfe8a0c after 10 minutes.


text:
🛑 Schoelcher is down

In 95e48a0, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in e30c72f after 5 minutes.


text:
🛑 Schoelcher is down

In 22f10fa, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in 20c057d after 5 minutes.


text:
🛑 Schoelcher is down

In 6911baa, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in 924d46f after 5 minutes.


text:
🛑 Préfecture de la Martinique is down

In 28668bc, Préfecture de la Martinique (https://www.martinique.gouv.fr) was down:

HTTP code: 429
Response time: 370 ms

Resolved: Préfecture de la Martinique is back up in 87f3c37 after 39 minutes.


text:
🛑 Saint-Pierre is down

In 8bd934e, Saint-Pierre (https://saintpierre-mq.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Saint-Pierre is back up in d903d60 after 16 minutes.


text:
🛑 Schoelcher is down

In c443161, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in e5d26e2.


text:
🛑 Schoelcher is down

In f4d5416, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in 69c441b.


text:
🛑 Schoelcher is down

In 37a25f8, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in 0b78297.


text:
🛑 Schoelcher is down

In 3c6f64e, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in ce00ce3.


text:
Error on implementing accordion on ionic/react

I've tried your collapsible on earlier and it runs smooth, and when I tried to test accordion on the same code. I got something error Could not find a declaration file for module 'react-responsive-accordion'. 'c:/development/ionic/books/node_modules/react-responsive-accordion/dist/Accordion.js' implicitly has an 'any' type.   Try npm install @types/react-responsive-accordionif it exists or add a new declaration (.d.ts) file containingdeclare module 'react-responsive-accordion';`
npm version 6.14.5
dependencies
"dependencies": {     "@capacitor/core": "2.2.0",     "@ionic/react": "^5.0.7",     "@ionic/react-router": "^5.0.7",     "@testing-library/jest-dom": "^4.2.4",     "@testing-library/react": "^9.4.0",     "@testing-library/user-event": "^8.0.3",     "@types/jest": "^24.0.25",     "@types/node": "^12.12.24",     "@types/react": "^16.9.17",     "@types/react-dom": "^16.9.4",     "@types/react-router": "^5.1.4",     "@types/react-router-dom": "^5.1.3",     "autoprefixer": "^9.8.0",     "ionicons": "^5.0.0",     "react": "^16.13.0",     "react-collapsible": "^2.8.0",     "react-dom": "^16.13.0",     "react-responsive-accordion": "^1.0.0",     "react-router": "^5.1.2",     "react-router-dom": "^5.1.2",     "react-scripts": "3.4.1",     "typescript": "3.8.3"   }

You're using typescript and this library has no typescript definitions. You need to declare you own or stub it out as says
add a new declaration (.d.ts) file containingdeclare module 'react-responsive-accordion';`

authors: glennflanagan kevinpallado


text:
Add remarks to glfw3.h whenever the behaviour differs

This should describe all of the Wayland-specific points, mostly in
three categories:

Missing GLFW features, for example window frame, screensaver
inhibition, clipboard or file drop.
Missing protocols, like setting gamma on a monitor or specifying a
window icon.
Fundamental incompatibilities with Wayland’s concepts, like trying to
handle global positioning of a window in a 2D space, trying to bring
a window to front, or trying to change the monitor’s mode.

If you want and have the time, in this PR or another, there may also be Wayland-specific material to add to docs/compat.dox.

This commit was only about glfw3.h, I will handle the rest of the documentation at some point, and might as well open an issue so I don’t forget. :)

Shortened the subject line to <= 50 characters.

authors: elmindreda linkmauve

repo: glfw/glfw

license: Zlib


text:
Fix Dart Freezed naming for nested objects

Fixes #2660

Available under quicktype-wosherco

repo: glideapps/quicktype


text:
Disable root password to prevent su

Closes #101 #107.

Looks good to me, though you could simplify the tests using any of the existing users:
docker run --user nobody alpine:3.2 su

What is the showstopper here?

This is in the gliderlabs/alpine images now. I'm working through some build script fixes to properly push the official branches and will get a PR open for them in a day or two.

@andyshinn Thank you!

@andyshinn I'm sorry to disturb you again, but have you had a chance to fix the issue for the official Alpine image?

I'm working on fixing up the building and committing of official tarballs before I can properly do that. Follow #94.

Downstream PR https://github.com/docker-library/official-images/pull/1292

@andyshinn Thank you for keeping us up-to-date!

authors: andyshinn frol

repo: gliderlabs/docker-alpine


text:
Add custom linear distance decay function for accessibility measures

The current accessibility method takes the binary approach with hard threshold, which take a rectangular function assuming the value 1 if included in a pre-defined threshold and the value 0 if not (refer here to the code). This method is appropriate for our purpose of indicator aggregation using open data, and passes the suitability analysis in the validation.
But there is also limitation to this approach, since it assumes that if a destination is slightly farther away from the origin (even by only 2 m: 499m vs 501m) it will have a lower attraction. Thus, there could be improvement in our accessibility measures to allow for custom linear distance decay function. From the literature, I found two methods may be applicable to our framework:

Cumulative–Gaussian function: which combines the rectangular function to model the acceptable distance threshold up to a value of perceived closeness, then apply a modified Gaussian function that reflects the influence of distance beyond that acceptable threshold up to the maximum walking distance.

Reference: Vale, D. S., & Pereira, M. (2017). The influence of the impedance function on gravity-based pedestrian accessibility measures: A comparative analysis. Environment and Planning B: Urban Analytics and City Science, 44(4), 740–763. https://doi.org/https://doi.org/10.1177/0265813516641685

Soft threshold approach: which defines a continuous access score for each destination type ranging from 0 to 1

Higgs, C., Badland, H., Simons, K. et al. The Urban Liveability Index: developing a policy-relevant urban liveability composite measure and evaluating associations with transport mode choice. Int J Health Geogr 18, 14 (2019). https://doi.org/10.1186/s12942-019-0178-8)

We discussed the second option before on basecamp, @carlhiggs you may have more thoughts on this since you are the authors of the approach.
I haven't implement these within our framework yet, but want to share the thought process so far, and keen to hear others suggestion on this.

Hi Shirley,
I'll be back off leave from Monday, but just saw your email so thought I'd
give quick jot of thoughts --- in short, I think our parsimonious approach
is justified given our study aims.  I'm writing this from a mobile phone,
sorry if there are predictive text errors!
I think the use of continuous measures is really important in certain
contexts, particularly when accurate measurement of an individual address
is a priority (eg for geocoded survey participants, to evaluate impact of
built environment exposure on some outcome variable, adjusting for
individual sociodemographic covariates).
There were a few reasons we decided not to do this for our study: 1) with
aggregation, hard and soft estimates converge (even at our small area grid
scale, but especially at city scale); 2) it requires measuring some
distance beyond (eg depending on the formula, an access score might
approach 0 around 1600 or more metres; I've previously used 3200m as a
minimum), and in early stage of our study there were concerns about
processing time for both traversal and accounting for network graph buffer;
3) given those reasons (little likely practical difference for the cost to
achieve our aims), the parsimonious approach (500m binary indicators)
seemed justified; 4) policy makers / non quantitative types may find fuzzy
access score hard to interpret (they want clear answers - eg percentage of
people who have access within a policy relevant distance)
To implement a decay like in those images, we'd have to re-measure access
to ensure all addresses were evaluated to some additional minimum distance
eg 1000+ metres.  I don't think it's necessary for this study, although if
another study were to use the method this additional information would be
of value of they were interested in individual not ecological effects.
Having said this, we also calculate a walkability composite measure, and
once indicators are combined in such a measure they less their direct
interpretability and so that advantage of binary indicators is already
lost.  For this reason, in other studies when I have calculated walkability
indices or other composite measures I have used soft threshold scores due
to greater accuracy of reflecting a local context.  Even so, given our
audience of mapping for policy makers and planners, I think the address
complexity is probably not necessary for this study.
Those are my thoughts, and if this was an issue raised by a reviewer that's
how I would respond; I'm happy to discuss further and open to other
viewpoints.
Cheers and enjoy the weekend,
Carl
On Fri, 19 Feb. 2021, 06:10 Shirley Liu, notifications@github.com wrote:

The current accessibility method takes the binary approach with hard
threshold, which take a rectangular function assuming the value 1 if
included in a pre-defined threshold and the value 0 if not (refer here
https://github.com/global-healthy-liveable-cities/global-indicators/blob/5e2c1133cabd7d740a00e4969cc1ddfd5f961701/process/sp.py#L283
to the code). This method is appropriate for our purpose of indicator
aggregation using open data, and passes the suitability analysis in the
validation.
But there is also limitation to this approach, since it assumes that if a
destination is slightly farther away from the origin (even by only 2 m:
499m vs 501m) it will have a lower attraction. Thus, there could be
improvement in our accessibility measures to allow for custom linear
distance decay function. From the literature, I found two methods may be
applicable to our framework:

Cumulative–Gaussian function: which combines the rectangular
function to model the acceptable distance threshold up to a value of
perceived closeness, then apply a modified Gaussian function that reflects
the influence of distance beyond that acceptable threshold up to the
maximum walking distance.

[image: Screen Shot 2021-02-18 at 1 53 48 PM]
https://user-images.githubusercontent.com/46453772/108406800-e3086500-71f0-11eb-84c4-debee1231346.png
Reference: Vale, D. S., & Pereira, M. (2017). The influence of the
impedance function on gravity-based pedestrian accessibility measures: A
comparative analysis. Environment and Planning B: Urban Analytics and City
Science, 44(4), 740–763.
https://doi.org/https://doi.org/10.1177/0265813516641685

Soft threshold approach: which defines a continuous access score
for each destination type ranging from 0 to 1

[image: Screen Shot 2021-02-18 at 1 54 18 PM]
https://user-images.githubusercontent.com/46453772/108406914-08956e80-71f1-11eb-8726-e53b0f76e4c0.png
Higgs, C., Badland, H., Simons, K. et al. The Urban Liveability Index:
developing a policy-relevant urban liveability composite measure and
evaluating associations with transport mode choice. Int J Health Geogr 18,
14 (2019). https://doi.org/10.1186/s12942-019-0178-8)
We discussed the second option before on basecamp, @carlhiggs
https://github.com/carlhiggs you may have more thoughts on this since
you are the authors of the approach.
I haven't implement these within our framework yet, but want to share the
thought process so far, and keen to hear others suggestion on this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/global-healthy-liveable-cities/global-indicators/issues/111,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADDCCMV4W46SI363B5PZEQLS7VQ3PANCNFSM4X23RAMQ
.

@carlhiggs Thanks for the quick reply! I totally agree that we should defend ourselves that binary measure is a preferable method for the study (the case study), based on all the reasons you mentioned. And yes, this is one issue raised by the reviewers asking if we can look into more refined methods like a gravity model or distance decay. My initial thought is, if this is easy to do (also suggested by @gboeing  in the comment), we could create a customized function that allows future users to choose which method is most appropriate for their study. This is thinking from an open-source software standpoint.
So I have been looking up some literature and thinking about which accessibility method would be appropriate to our study and also easy to integrate into our framework within the review timeframe. The Pandana package we used has the accessibility function defined in a way that allows people to retrieve a certain number of nearest points with distance returned, so I am thinking if we could reuse that for the distance decay model (in our current study, we define it in a way that it searches the first nearest point which is appropriate for the binary method). The challenge I have now is as you have mentioned, the later aggregation for the daily living and walkability composite measure. The full_node distance also adds another layer of complexity to this. So any more thoughts on this would be appreciated!
I will also see if I could put some of my thoughts into codes...

Hey Shirley,
I think if we want to implement this for other to use, it shouldn't be too
hard (ie. not an issue for full distance function, composite indicators or
aggregation).
The most straightforward way might be:

user must specify minimum traversal distance appropriate to their
maximum accessibility threshold (if these vary by destination).  This will
depend on the formula used (we could even make this user specified, but
supply an optional default eg like in that ULI paper using a sigmoid
transformation).  They also set a setting to indicate usage of continuous
rather than binary indicators.

distance evaluation works as usual (including full distance fix) using
the larger evaluation distance

accessibility scores are evaluated using the function (default or user
specified), resulting in score from 0 to 1 (instead of binary indicator, 0
or 1)

derived indicators are calculated as usual

aggregation proceeds as usual (and likely will return a similar result
in many cases).  Technical interpretation will shift: eg. percentage
indicators although approximately similar are no longer strictly
percentages --- although the practical interpretation will be essentially
the same.

I think at this point everything else is equivalent, so the only novel bit
beyond configuration is conditional logic determining which function to use
to evaluate access scores (binary, default continuous, or custom continuous)
I'm sure there are many other ways to do this, but that one should be easy
to implement assuming the custom function is straightforward (eg evaluation
of sample point distance against a fixed threshold, with some decay curve).
What do you think?  (I just realised I haven't seen Geoff's comment yet, he
probably has said similar from what you say)
I'll look at reviewer comments etc when formally back at work from Monday.
Carl
On Sat, 20 Feb. 2021, 03:40 Shirley Liu, notifications@github.com wrote:

@carlhiggs https://github.com/carlhiggs Thanks for the quick reply! I
totally agree that we should defend ourselves that binary measure is a
preferable method for the study (the case study), based on all the reasons
you mentioned. And yes, this is one issue raised by the reviewers asking if
we can look into more refined methods like a gravity model or distance
decay. My initial thought is, if this is easy to do (also suggested by
@gboeing https://github.com/gboeing in the comment), we could create a
customized function that allows future users to choose which method is most
appropriate for their study. This is thinking from an open-source software
standpoint.
So I have been looking up some literature and thinking about which
accessibility method would be appropriate to our study and also easy to
integrate into our framework within the review timeframe. The Pandana
package we used has the accessibility function defined in a way that allows
people to retrieve a certain number of nearest points with distance
returned, so I am thinking if we could reuse that for the distance decay
model (in our current study, we define it in a way that it searches the
first nearest point which is appropriate for the binary method). The
challenge I have now is as you have mentioned, the later aggregation for
the daily living and walkability composite measure. The full_node distance
also adds another layer of complexity to this. So any more thoughts on this
would be appreciated!
I will also see if I could put some of my thoughts into codes...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/global-healthy-liveable-cities/global-indicators/issues/111#issuecomment-782191987,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADDCCMU2FQUF4L7MUPM6OPLS72IA7ANCNFSM4X23RAMQ
.

Thanks Carl! I may have overthink some processes. You are correct that changing the method would not affect the aggregation and full distance operation. Below are the three methods I think may be appropriate to use, written in functions, the first is the binary one we used, the second and the third are the two methods I cited at the beginning:

Cumulative opportunities (binary)
1 if d <= access_dist
0 if d > access_dist

def binary_access_score(df, new_name, old_name, access_dist):
    df[new_name] = (df[old_name] <= access_dist).astype("Int64").fillna(0)
    return df[new_name]

Soft threshold access score
1 / (1+ e ^(k *((d-c)/c)))

def soft_access_score(df, new_name, old_name, access_dist, k):
    df[new_name] = 1 / (1+numpy.exp(k * ((df[old_name]-access_dist) / access_dist)))

    df[new_name] = df[new_name].astype(float).fillna(0)
    return df[new_name]

Cumulative-Gaussian
1 if d <= access_dist ;
e ^(-1 *((d^2)/k)) if d > access_dist

def Cumulative_Gaussian_access_score(df, new_name, old_name, access_dist, k):
    df_access = pd.DataFrame()
    for n, d in zip(new_name, old_name): #loop through each colomn
        df[n] = 0 #create column

        df1=df[n].copy()
        df1.loc[df[d] > access_dist] = numpy.exp(-1 * (((df[d]-access_dist)**2) / k))
        df1.loc[df[d] <= access_dist] = 1

        df_access = pd.concat([df_access, df1], axis=1, ignore_index=False)

    df_access = df_access.astype(float).fillna(0)
    return df_access

Then, the simple way would be to change is this line of code  to the binary function. Other users could choose which functions they want to pass for the accessibility scores, with everything else being equivalent.
Let me know what you think.

Hi @shiqin-liu ,
Thanks for taking the lead on this and drafting the functions --- they look good.
I've just had a review of the code, and had a few suggestions.  My comments may have been disjointed there so will respond here.
My main two thoughts on amending these are

we should provide guidance on sensible default values of k for a given access distance threshold (e.g. k=5 is sensible for the soft threshold function, where it seems to me that k=100,000 is required for the cumulative Gaussian function to return similarly equivalent values)
we don't need to specify the new names within the function; by not worrying about this it should make the function definitions simpler (just need to return a dataframe of values, with names endowed in the implementation code)
I think the current definition of cumulative function code modifies the input data frame in the df[n]=0 loop (over writes the input data with zeroes)
we should make sure we amend the variable names and suffixes relating to the word 'binary' in the implementation code; perhaps 'access' is a good generalised alternative prefix?
Geoff also suggested that by doing fillna(0) prior to casting type it should avoid the need of using int64 for a nullable datatype.

Here is an example of refactored functions with the above in mind

import pandas as pd
import numpy

def binary_access_score(df, distances, threshold):
    """
    Calculate accessibiity score using binary measure: 1 if access <= threshold, 0 otherwise
    Parameters
    ----------
    df: DataFrame
        DataFrame with origin-destination distances
    distances: list
         list of distances field names
    threshold: int
        access distance threshold
    Returns
    -------
    DataFrame
    """
    scores = (df[distances] <= threshold).fillna(0).astype(int)
    return scores

def soft_access_score(df, distances, threshold=500, k=5):
    """
    Calculate accessibiity score using soft threshold approach:
    1 / (1+ e ^(k *((dist-threshold)/threshold)))
    Parameters
    ----------
    df: DataFrame
        DataFrame with origin-destination distances
    distances: list
        list of field names for distance records
    threshold: int
        access distance threshold
    k: int
        the slope of decay
    Returns
    -------
    DataFrame
    """
    scores = (1 / (1+numpy.exp(k * ((df[distances]-threshold) / threshold)))).fillna(0)
    return scores

def cumulative_gaussian_access_score(df, distances, threshold=500, k=100000):
    """
    Calculate accessibiity score using Cumulative-Gaussian approach:
    1 if d <= threshold ; otherwise, e ^(-1 *((d^2)/k)) if d > threshold
    Parameters
    ----------
    df: DataFrame
        DataFrame with origin-destination distances
    distances: list
        list of field names for distance records
    threshold: int
        access distance threshold
    k: int
        the slope of decay
    Returns
    -------
    DataFrame
    """
    scores = df[distances].copy()
    scores[scores<=threshold] = 1
    scores[scores>threshold] = numpy.exp(-1 * (((scores[scores>threshold]-threshold)**2) / k))
    scores = scores.fillna(0)
    return scores

Implementing these, it would look something like
#Example dataframe with two columns of distance records
df = pd.DataFrame({'x1':[100,numpy.NaN,300,400,500,600,700,800,900,1000],'x2':[1000,900,800,700,600,500,400,300,200,100]})

# distance record field names
distances = ['x1','x2']

# evaluation threshold
threshold = 500

# compare the three functions
for f in [binary_access_score,soft_access_score,cumulative_gaussian_access_score]:
    prefix =  f.__qualname__[:3].lower()
    df[[f'{prefix}_{x}' for x in distances]] = f(df,distances,threshold)

df

And the output looks like
       x1    x2  bin_x1  bin_x2    sof_x1    sof_x2    cum_x1    cum_x2
0   100.0  1000       1       0  0.982014  0.006693  1.000000  0.082085
1     NaN   900       0       0  0.000000  0.017986  0.000000  0.201897
2   300.0   800       1       0  0.880797  0.047426  1.000000  0.406570
3   400.0   700       1       0  0.731059  0.119203  1.000000  0.670320
4   500.0   600       1       0  0.500000  0.268941  1.000000  0.904837
5   600.0   500       0       1  0.268941  0.500000  0.904837  1.000000
6   700.0   400       0       1  0.119203  0.731059  0.670320  1.000000
7   800.0   300       0       1  0.047426  0.880797  0.406570  1.000000
8   900.0   200       0       1  0.017986  0.952574  0.201897  1.000000
9  1000.0   100       0       1  0.006693  0.982014  0.082085  1.000000

In the script, we imagine that a user has defined their desired function in the set up script, so, if we imagine a variable threshold_function is set in the setup script with the name of the desired function:
# re-initialise example dataframe
df = pd.DataFrame({'x1':[100,numpy.NaN,300,400,500,600,700,800,900,1000],'x2':[1000,900,800,700,600,500,400,300,200,100]})
distances = ['x1','x2']
# define the `threshold_function` variable (presumably accessed via config[`threshold_function`] in the actual code)
threshold_function = binary_access_score
df[[f'access_{x}' for x in distances]] = threshold_function(df,distances,threshold)
df

and the results
       x1    x2  access_x1  access_x2
0   100.0  1000          1          0
1     NaN   900          0          0
2   300.0   800          1          0
3   400.0   700          1          0
4   500.0   600          1          0
5   600.0   500          0          1
6   700.0   400          0          1
7   800.0   300          0          1
8   900.0   200          0          1
9  1000.0   100          0          1

I guess we'll have to take care with the renamed derived variables that these are modified as required elsewhere, eg. in the aggregation scripts etc.
I wasn't sure how best to contribute these ideas to your pull request, so I'll leave them here for now to see what you and @gboeing think.
I like Geoff's suggestion for using an approach like that used by OSMnx for code standardisation; probably important to share common guidelines given multiple contributors.  Perhaps we can talk about how this might work in the meeting on Friday.

authors: carlhiggs shiqin-liu


text:
Update README.md

All modifications have been made.
Close #463

Already fixed

authors: GMVargass elesbom

repo: globocom/database-as-a-service


text:
globus-automate-client doesn't install using pip on python 3.10 or 3.11

Tried to install globus-automate-client in a clean virtual environment using the following commands;
pip install --upgrade pip setuptools wheel
pip install globus-automate-client
This results in a failure. Any ideas?
└─(14:38:58)──> pip install globus-automate-client                                                                                ──(Wed,Jul19)─┘
Collecting globus-automate-client
  Using cached globus_automate_client-0.17.0-py3-none-any.whl (54 kB)
Collecting PyYAML<6.0.0,>=5.3.1 (from globus-automate-client)
  Using cached PyYAML-5.4.1.tar.gz (175 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [62 lines of output]
      /tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg`
      !!

              ********************************************************************************
              The license_file parameter is deprecated, use license_files instead.

              By 2023-Oct-30, you need to update your project and remove deprecated calls
              or your builds will no longer be supported.

              See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
              ********************************************************************************

      !!
        parsed = self.parsers.get(option_name, lambda x: x)(value)
      running egg_info
      writing lib3/PyYAML.egg-info/PKG-INFO
      writing dependency_links to lib3/PyYAML.egg-info/dependency_links.txt
      writing top-level names to lib3/PyYAML.egg-info/top_level.txt
      Traceback (most recent call last):
        File "/home/allsoppj/Repositories/temp/test_loading_globus_automate_client/env/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/home/allsoppj/Repositories/temp/test_loading_globus_automate_client/env/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/home/allsoppj/Repositories/temp/test_loading_globus_automate_client/env/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
          return hook(config_settings)
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 341, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=['wheel'])
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 323, in _get_build_requires
          self.run_setup()
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 338, in run_setup
          exec(code, locals())
        File "<string>", line 271, in <module>
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/__init__.py", line 107, in setup
          return distutils.core.setup(**attrs)
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 185, in setup
          return run_commands(dist)
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
          dist.run_commands()
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
          self.run_command(cmd)
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/dist.py", line 1234, in run_command
          super().run_command(command)
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/command/egg_info.py", line 314, in run
          self.find_sources()
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/command/egg_info.py", line 322, in find_sources
          mm.run()
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/command/egg_info.py", line 551, in run
          self.add_defaults()
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/command/egg_info.py", line 589, in add_defaults
          sdist.add_defaults(self)
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/command/sdist.py", line 104, in add_defaults
          super().add_defaults()
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/_distutils/command/sdist.py", line 251, in add_defaults
          self._add_defaults_ext()
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/_distutils/command/sdist.py", line 336, in _add_defaults_ext
          self.filelist.extend(build_ext.get_source_files())
        File "<string>", line 201, in get_source_files
        File "/tmp/pip-build-env-nvbf18tv/overlay/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 107, in __getattr__
          raise AttributeError(attr)
      AttributeError: cython_sources
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

Hello James! This issue has been showing up across the Python ecosystem due to the latest release of Cython, version 3.0.0, which was released about 48 hours ago and has introduced an issue with PyYAML.
We're actively working to resolve this; PR #194 in this repository is being reviewed now.

Thanks for getting this merged so quickly, do you know when the change will be live on PyPi?

@JamesAllsopp This should be released as v0.17.1 now. :grinning:

authors: JamesAllsopp kurtmckee

repo: globus/globus-automate-client


text:
[Dictionary] support GLUE_OBJECTS

🚧 Draft yet
Goal
gluesql> CREATE TABLE Foo(no int);
gluesql> CRETE INDEX IDX_Foo ON Foo(no);
gluesql> SELECT * FROM GLUE_OBJECTS;

OBJECT_NAME
OBJECT_TYPE
CREATED

Foo
TABLE
2022-10-11 09:24:46.850203088

IDX_Foo
INDEX
2022-10-11 09:24:47.850203088

Todo

[x] implement GLUE_OBJECTS
[x] add created to Schema
[x] implement TABLE created
[x] implement INDEX created
[ ] how to test created without failure?

Pull Request Test Coverage Report for Build 3225692299

100 of 100 (100.0%)  changed or added relevant lines in 9 files are covered.
57 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.08%) to 97.9%

Files with Coverage Reduction
New Missed Lines
%

core/src/executor/execute.rs
2
93.49%

test-suite/src/tester/mod.rs
19
87.5%

core/src/data/value/binary_op/i64.rs
36
96.29%

Totals

Change from base Build 3223898204:
-0.08%

Covered Lines:
38231

Relevant Lines:
39051

💛  - Coveralls

authors: coveralls devgony

repo: gluesql/gluesql


text:
Why is iter used here during training iterations instead of directly using the dataloader?

https://github.com/gmberton/CosPlace/blob/cea7de243abe1a59c69f1087b1b8001d01262c59/train.py#L114

 dataloader = commons.InfiniteDataLoader(groups[current_group_num], num_workers=args.num_workers,
                                            batch_size=args.batch_size, shuffle=True,
                                            pin_memory=(args.device == "cuda"), drop_last=True)

    dataloader_iterator = iter(dataloader)
    model = model.train()

    epoch_losses = np.zeros((0, 1), dtype=np.float32)
    for iteration in tqdm(range(args.iterations_per_epoch), ncols=100):
           images, targets, _ = next(dataloader_iterator)

Why not do it directly like this?

dataloader = commons.InfiniteDataLoader(groups[current_group_num], num_workers=args.num_workers,
                                            batch_size=args.batch_size, shuffle=True,
                                            pin_memory=(args.device == "cuda"), drop_last=True)

       model = model.train()

    epoch_losses = np.zeros((0, 1), dtype=np.float32)
    for images, targets, _ in tqdm(dataloader, ncols=100):

https://github.com/gmberton/CosPlace/blob/804fc8c65871cab81f8efbc2c0cff04f1ab78534/train.py#L106
Why not use torch.utils.data.dataloader directly?

It is also okay to use the standard DataLoader class, but using an InfiniteDataLoader ensures that if there are not enough samples the __iter__ will not raise a StopIteration. This could happen when changing the parameters within the code (e.g. using higher values for parameters --iterations_per_epoch, --batch_size, --L, --N might lead to this issue when using a standard DataLoader)

dataloader_iterator = iter(dataloader)
for iteration in tqdm(range(args.iterations_per_epoch), ncols=100):
       images, targets, _ = next(dataloader_iterator)

What you mean is that with this approach, you can train on a portion of the data in each epoch without having to train on all the data, and only need to go through args.iterations_per_epoch iterations?
https://github.com/gmberton/CosPlace/blob/543eaa5995c64d7e2ddbe2d8a1587ec4b2964728/train.py#L106
dataloader = commons.InfiniteDataLoader(groups[current_group_num], num_workers=args.num_workers,
                                            batch_size=args.batch_size, shuffle=True,
                                            pin_memory=(args.device == "cuda"), drop_last=True)

    dataloader_iterator = iter(dataloader)

When I use the small dataset, it has only one group containing 5,965 classes. If args.batch_size is set to 8, there will be 745 BatchSamplers in the dataloader, meaning the dataloader can iterate 745 times to train on all the data. The statement "images, targets, _ = next(dataloader_iterator)" can only iterate 745 times as well. However, in the training loop, args.iterations_per_epoch is set to 10,000, indicating 10,000 iterations are expected, but in reality, only 745 iterations are possible because the statement "images, targets, _ = next(dataloader_iterator)" cannot iterate further after 745 iterations. If this is the case, your intention to train on only a portion of data in each epoch may not be achieved.

class InfiniteDataLoader(torch.utils.data.DataLoader):
    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self.dataset_iterator = super().__iter__()

    def __iter__(self):
        return self

    def __next__(self):
        try:
            batch = next(self.dataset_iterator)
        except StopIteration:
            self.dataset_iterator = super().__iter__()
            batch = next(self.dataset_iterator)
        return batch

using an InfiniteDataLoader ensures that if there are not enough samples the iter will not raise a StopIteration.
When all samples are used up, the __iter__ will start iterating from the first batch again. Is that correct?
When args.iterations_per_epoch=10,000 and the DataLoader has 800 BatchSamplers, after completing the iteration of the 800th batch, the statement "images, targets, _ = next(dataloader_iterator)" in the for loop will start iterating from the first batch again. In this case, a single for training loop will train on the data multiple times, and eventually, one epoch will complete 10,000 iterations of training.
When args.iterations_per_epoch=10,000 and the DataLoader has 20,000 BatchSamplers, in this case, a single for training loop will only perform 10,000 iterations of training, training only a portion of the data.
This ensures that regardless of whether the number of BatchSamplers is greater than args.iterations_per_epoch, the for training loop in one epoch will always iterate args.iterations_per_epoch times.
Right？

Based on this setup, training on 8 groups of the processed dataset can lead to CosPlace achieving state-of-the-art performance?

All your assumptions are correct, and the answer to all your questions is yes.

Think you  for your help

authors: gmberton wpumain

repo: gmberton/CosPlace


text:
createUser function

I want a createUser function that creates a plain-old javascript object that has all the properties of the Firebase User without any of the methods, and which merges additional properties that I supply.

Will not implement this feature because it is easy to get a plain-old javascript object via user.toJson()

repo: gmcfall/react-firebase-state


text:
Using burst option for servers and peers

The template for ntp.conf enables iburst by default for servers and peers, but there is not a way to enable burst. Are there plans to support it? Any ideas on how you'd like to support it?
I'd happily prep a PR to get the functionality there, but it may require a breaking change to the attribute format to support it depending on the implementation. This is why I raised this issue first.

Nevermind, I am totally a tool and missed it. :stuck_out_tongue:


text:
I broke my finger...

Probably 2-6 weeks before I can start coding again... :(

Oh damn, sorry to hear! Rest up, and I hope the finger knits properly..

coding continues at https://github.com/Bergecraft/Contraptions

Nice! Hit me up if you have questions. Warning, the different gadgets were still getting thought out, so you might want to rework them. But I was really likely the overall structure of code, especially compared to factorymod.....

Oh damn...sorry about the broken finger, man. I didn't realize this was what happened. Hope the recovery went well without complication.

authors: MonsieurWTF ProgrammerDan WildWeazel gmlaxfanatic

repo: gmlaxfanatic/Contraptions


text:
RestrictPaths needs to apply to all OS threads and Goroutines at once

The mapping of Goroutines to system threads is managed by the Go runtime and even at the start of main() you don't get the guarantee that there is only one OS thread active. (In fact, even the GC uses Goroutines, so it's clear to see this is difficult to guarantee.)
The same problem has already been discussed in the context of seccomp(2), which has the same semantics: https://github.com/golang/go/issues/3405 @AndrewGMorgan is pointing to syscall.AllThreadsSyscall() as a way to apply a syscall to all Go-managed OS threads at once.

Note, the syscall.AllThreadsSyscall() is disabled CGo is enabled. For both with and without CGo I have developed the package: psx. If CGO_ENABLED=0 this package redirects to syscall.AllThreadsSyscall(), but if CGO_ENABLED=1 it uses libpsx.

authors: AndrewGMorgan gnoack

repo: gnoack/golandlock


text:
Change baseGas and safeTxGas to strings

Change the types of base_gas and safe_tx_gas in the MultisigExecutionDetails to String
See the backend ticket: https://github.com/gnosis/safe-client-gateway/issues/543

Reopening util the safe-react PR is closed

authors: juampibermani katspaugh

repo: gnosis/safe-react-gateway-sdk


text:
Feature/2517 use string for chain

Using other PR to solve the issue

Closing since i'm using other PR to close this issue

repo: gnosis/safe-react


text:
🛑 Beacon Explorer is down

In a55fff0, Beacon Explorer (https://beacon.chiadochain.net/) was down:

HTTP code: 502
Response time: 19192 ms

Resolved: Beacon Explorer is back up in e9294c1 after 50 minutes.

repo: gnosischain/chiado-uptime


text:
occasional interruption with java.lang.InteruptedException

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
follow all standard steps and run docker in Debian 7. Everthing works fine; but sometimes after a few hours, will disconnect and see the following error:
cta_strategy-ib-gateway-1  | 2023-11-02 08:28:35:471 IBC: detected dialog entitled: DU123456 Trader Workstation Configuration (Simulated Trading); event=Closed
cta_strategy-ib-gateway-1  | Forking :::4000 onto 0.0.0.0:4002
cta_strategy-ib-gateway-1  | remove Client 1
cta_strategy-ib-gateway-1  | remove Client 1
cta_strategy-ib-gateway-1  | 2023-11-02 12:32:03:935 IBC: detected frame entitled: Connecting to server...; event=Opened
cta_strategy-ib-gateway-1  | 2023-11-02 12:32:03:935 IBC: detected frame entitled: Connecting to server...; event=Activated
cta_strategy-ib-gateway-1  | 2023-11-02 12:32:03:936 IBC: detected frame entitled: Connecting to server...; event=Focused
cta_strategy-ib-gateway-1  | java.lang.InterruptedException
cta_strategy-ib-gateway-1  | 	at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:998)
cta_strategy-ib-gateway-1  | 	at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
cta_strategy-ib-gateway-1  | 	at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
cta_strategy-ib-gateway-1  | 	at com.sun.javafx.application.PlatformImpl.waitForStart(PlatformImpl.java:256)
cta_strategy-ib-gateway-1  | 	at com.sun.javafx.application.PlatformImpl.runLater(PlatformImpl.java:277)
cta_strategy-ib-gateway-1  | 	at com.sun.javafx.application.PlatformImpl.runLater(PlatformImpl.java:268)
cta_strategy-ib-gateway-1  | 	at com.sun.javafx.application.PlatformImpl.checkIdle(PlatformImpl.java:392)
cta_strategy-ib-gateway-1  | 	at com.sun.javafx.application.PlatformImpl.setImplicitExit(PlatformImpl.java:346)
cta_strategy-ib-gateway-1  | 	at javafx.application.Platform.setImplicitExit(Platform.java:138)
cta_strategy-ib-gateway-1  | 	at twslaunch.gstat.j.a(j.java:88)
cta_strategy-ib-gateway-1  | 	at twslaunch.gstat.a.d(a.java:215)
cta_strategy-ib-gateway-1  | 	at twslaunch.gstat.a.g(a.java:117)
cta_strategy-ib-gateway-1  | 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
cta_strategy-ib-gateway-1  | 	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
cta_strategy-ib-gateway-1  | 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
cta_strategy-ib-gateway-1  | 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
cta_strategy-ib-gateway-1  | 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
cta_strategy-ib-gateway-1  | 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
cta_strategy-ib-gateway-1  | 	at java.lang.Thread.run(Thread.java:748)
cta_strategy-ib-gateway-1  | 2023-11-02 12:32:37:902 IBC: detected frame entitled: Starting application...; event=Closed

Expected behavior
The connection should stay active; if it is interrupted, it should be able to resume automatically.
Container logs
If applicable, add the container logs docker logs <CONTAINER> or docker-compose logs to help explain your problem.
Versions (please complete the following information):

OS: [e.g. Windows]
Docker version: Docker version 24.0.6
Image Tag (docker --version): [e.g. latest]
Image Digest (docker images --digests): [e.g. sha256:60d9d54009b1b66908bbca1ebf5b8a03a39fe0cb35c2ab4023f6e41b55d17894]

Additional context
Add any other context about the problem here.
Any ideas? Thanks.

It could be related to the daily restart, please share the output of docker compose config. you will want to remove sensitive information like user and pass.
Personally I'm running a container with AUTO_RESTART_TIME=08:59 AM and it runs for a full week without any problem.

Thanks very much for your reply.
My daily restart time is set to 06:05 AM, and it restarts as expected. So it might not be the issue. Anyway, here is my docker-compose.yml:
version: "3.4"

services:
  ib-gateway:
    image: ghcr.io/gnzsnz/ib-gateway:stable
    restart: always
    environment:
      TWS_USERID: ${TWS_USERID}
      TWS_PASSWORD: ${TWS_PASSWORD}
      TRADING_MODE: ${TRADING_MODE:-live}
#      VNC_SERVER_PASSWORD: ${VNC_SERVER_PASSWORD:-}
      READ_ONLY_API: ${READ_ONLY_API:-}
      TWOFA_TIMEOUT_ACTION: ${TWOFA_TIMEOUT_ACTION:-exit}
      AUTO_RESTART_TIME: ${AUTO_RESTART_TIME:-}
      RELOGIN_AFTER_TWOFA_TIMEOUT: ${RELOGIN_AFTER_TWOFA_TIMEOUT:-no}
      TWOFA_EXIT_INTERVAL: ${TWOFA_EXIT_INTERVAL:-60}
      TIME_ZONE: ${TIME_ZONE:-Etc/UTC}
      CUSTOM_CONFIG: ${CUSTOM_CONFIG:-NO}
#    volumes:
#      - ${PWD}/jts.ini:/root/Jts/jts.ini
#      - ${PWD}/config.ini:/root/ibc/config.ini
    ports:
      - "127.0.0.1:4001:4001"
      - "127.0.0.1:4002:4002"
#      - "127.0.0.1:5900:5900"

And here is my .env file (removed sensitive information):
TWS_USERID=XXX
TWS_PASSWORD=XXX
TRADING_MODE=paper
READ_ONLY_API=no
TWOFA_TIMEOUT_ACTION=restart
AUTO_RESTART_TIME=06:05 AM
RELOGIN_AFTER_2FA_TIMEOUT=yes
TIME_ZONE=Asia/Hong_Kong
CUSTOM_CONFIG=

Thanks.

i haven't noticed that error before. looks like something coming from IBC. it's unlikely that can be fixed on this codebase (ex Dockerfile or run.sh), as that's a java exception.
if you find reproduction steps please share them. I'll check my log files to see if I find anything.

hi @josephchenhk
i dug into my log files and indeed I have found the error message that you are reporting. however I can not link it to any actual issue with the functioning of IB Gateway. From my side I can say I have the error on the logs but It does not seems to be causing any issue on my side, or at least I have not noticed it.
have you checked the application logs? ex File>Gateway Logs

Hi @gnzsnz
Thanks for the info. It seems that ib will disconnect for a while and reconnect automatically. If you are not placing an order, it should be fine; but if you are in the middle of placing an order, sometimes it will fail to receive a callback of the order.
can you tell me how to extract the application logs from the docker? Let me get the logs and take a further look. Thanks.

to extract application logs, you need to connet through VNC, and then click File>Gateway Logs
that will save a .txt file named gateway-exported-logs.txt
then you can get it with
docker cp ibgateway:/root/gateway-exported-logs.txt .

ibgateway is the name of your container
regarding this disconnect, I have noticed, but never really caused me an issue. but i read about it in https://groups.io/g/insync I'm sure you will find something usefull there.

thanks a lot for sharing the link, that's useful.
I didn't connect through VNC at the moment; I guess I can not click and save the logs at this time. But I will turn it on next time and download the logs when I see the disconnection.

Hi @gnzsnz,
I'm facing the same issue here.
It seems the java error only occures in case of an reconnect. Whether the connection is closed and restarted during the daily reconnect at 11:45 PM in my case or the connection is closed by peer due to no trading activity.
But, the error does not appear on my API Gateway Logs which I exported via VNC.
It's only side the docker logs.
2023-11-08 23:45:07:133 IBC: Starting Gateway 2023-11-08 23:45:11:612 IBC: Getting config dialog 2023-11-08 23:45:11:613 IBC: Creating config dialog future 2023-11-08 23:45:11:624 IBC: Getting config dialog 2023-11-08 23:45:11:626 IBC: Getting config dialog 2023-11-08 23:45:11:628 IBC: Waiting for config dialog future to complete 2023-11-08 23:45:11:629 IBC: Waiting for config dialog future to complete 2023-11-08 23:45:11:630 IBC: Getting main window 2023-11-08 23:45:11:630 IBC: Creating main window future 2023-11-08 23:45:11:658 IBC: Getting config dialog 2023-11-08 23:45:11:659 IBC: Waiting for config dialog future to complete java.lang.InterruptedException         at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:998)         at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)         at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)         at com.sun.javafx.application.PlatformImpl.waitForStart(PlatformImpl.java:256)         at com.sun.javafx.application.PlatformImpl.runLater(PlatformImpl.java:277)         at com.sun.javafx.application.PlatformImpl.runLater(PlatformImpl.java:268)         at com.sun.javafx.application.PlatformImpl.checkIdle(PlatformImpl.java:392)         at com.sun.javafx.application.PlatformImpl.setImplicitExit(PlatformImpl.java:346)         at javafx.application.Platform.setImplicitExit(Platform.java:138)         at twslaunch.gstat.j.a(j.java:88)         at twslaunch.gstat.a.d(a.java:215)         at twslaunch.gstat.a.g(a.java:117)         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)         at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)         at java.lang.Thread.run(Thread.java:748) 2023-11-08 23:45:18:639 IBC: detected frame entitled: Loading...; event=Opened 2023-11-08 23:45:18:641 IBC: Found Gateway main window 2023-11-08 23:45:18:643 IBC: Got main window from future 2023-11-08 23:45:18:643 IBC: Invoking config dialog menu 2023-11-08 23:45:18:688 IBC: detected frame entitled: Loading...; event=Activated 2023-11-08 23:45:18:689 IBC: detected frame entitled: Loading...; event=Focused 2023-11-08 23:45:18:689 IBC: detected frame entitled: Loading...; event=Lost focus 2023-11-08 23:45:18:690 IBC: detected frame entitled: Loading...; event=Deactivated 2023-11-08 23:45:18:691 IBC: detected frame entitled: IB Gateway; event=Activated 2023-11-08 23:45:18:703 IBC: detected frame entitled: IB Gateway; event=Focused 2023-11-08 23:45:18:703 IBC: detected frame entitled: IB Gateway; event=Opened 2023-11-08 23:45:18:703 IBC: Login dialog WINDOW_OPENED: LoginState is LOGGED_OUT 2023-11-08 23:45:18:931 IBC: detected frame entitled: IB Gateway; event=Lost focus 2023-11-08 23:45:18:932 IBC: detected frame entitled: IB Gateway; event=Deactivated 2023-11-08 23:45:18:932 IBC: detected frame entitled: Authenticating...; event=Activated 2023-11-08 23:45:18:933 IBC: detected frame entitled: Authenticating...; event=Focused 2023-11-08 23:45:18:933 IBC: detected frame entitled: Authenticating...; event=Opened LogModuleConfigurator-Init: Log4j Ver2.x found on classpath LogModuleConfigurator-Init: LogModuleConfigurator initialized with Log4j Verd.x 2023-11-08 23:45:31:171 IBC: detected frame entitled: Starting application...; event=Lost focus 2023-11-08 23:45:31:263 IBC: detected dialog entitled: Trader Workstation Configuration; event=Opened 2023-11-08 23:45:31:264 IBC: detected frame entitled: Starting application...; event=Deactivated 2023-11-08 23:45:31:264 IBC: Got config dialog from future 2023-11-08 23:45:31:264 IBC: Got config dialog from future 2023-11-08 23:45:31:265 IBC: Got config dialog from future 2023-11-08 23:45:31:264 IBC: Got config dialog from future 2023-11-08 23:45:31:264 IBC: detected dialog entitled: Trader Workstation Configuration; event=Activated 2023-11-08 23:45:31:269 IBC: detected dialog entitled: Trader Workstation Configuration; event=Focused 2023-11-08 23:45:31:373 IBC: detected dialog entitled: Trader Workstation Configuration; event=Lost focus 2023-11-08 23:45:31:379 IBC: detected frame entitled: Starting application...; event=Closed 2023-11-08 23:45:31:380 IBC: Login has completed 2023-11-08 23:45:31:382 IBC: detected dialog entitled: Trader Workstation Configuration; event=Focused 2023-11-08 23:45:31:382 IBC: Setting Auto restart time 2023-11-08 23:45:31:514 IBC: Auto restart time already set to 11:45 PM 2023-11-08 23:45:31:515 IBC: Setting ReadOnlyApi 2023-11-08 23:45:31:903 IBC: Read-Only API checkbox is already set to: false 2023-11-08 23:45:31:903 IBC: Performing port configuration 2023-11-08 23:45:31:904 IBC: TWS API socket port is already set to 4000 2023-11-08 23:45:31:904 IBC: Performing master client ID configuration 2023-11-08 23:45:31:904 IBC: TWS Master Client ID is already set to 0 2023-11-08 23:45:32:096 IBC: Configuration tasks completed 2023-11-08 23:45:32:096 IBC: Click button: OK 2023-11-08 23:45:32:236 IBC: detected dialog entitled: Pending Tasks; event=Closed 2023-11-08 23:45:32:237 IBC: detected dialog entitled: Trader Workstation Configuration; event=Lost focus 2023-11-08 23:45:32:238 IBC: detected dialog entitled: Trader Workstation Configuration; event=Deactivated 2023-11-08 23:45:32:238 IBC: detected dialog entitled: Trader Workstation Configuration; event=Closed addLogConsole Client 2147483647 addLogConsole Client 0 addLogConsole Client 5 addLogConsole Client 5 addLogConsole Client 2147483647 addLogConsole Client 0 2023-11-09 06:14:07:847 IBC: detected frame entitled: Connecting to server...; event=Opened 2023-11-09 06:14:07:849 IBC: detected frame entitled: Connecting to server...; event=Activated 2023-11-09 06:14:07:850 IBC: detected frame entitled: Connecting to server...; event=Focused addLogConsole Client 5 addLogConsole Client 0 java.lang.InterruptedException         at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:998)         at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)         at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)         at com.sun.javafx.application.PlatformImpl.waitForStart(PlatformImpl.java:256)         at com.sun.javafx.application.PlatformImpl.runLater(PlatformImpl.java:277)         at com.sun.javafx.application.PlatformImpl.runLater(PlatformImpl.java:268)         at com.sun.javafx.application.PlatformImpl.checkIdle(PlatformImpl.java:392)         at com.sun.javafx.application.PlatformImpl.setImplicitExit(PlatformImpl.java:346)         at javafx.application.Platform.setImplicitExit(Platform.java:138)         at twslaunch.gstat.j.a(j.java:88)         at twslaunch.gstat.a.d(a.java:215)         at twslaunch.gstat.a.g(a.java:117)         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)         at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)         at java.lang.Thread.run(Thread.java:748) 2023-11-09 06:15:44:289 IBC: detected frame entitled: Starting application...; event=Lost focus 2023-11-09 06:15:44:289 IBC: detected frame entitled: Starting application...; event=Deactivated 2023-11-09 06:15:44:290 IBC: detected frame entitled: Starting application...; event=Closed addLogConsole Client 0 addLogConsole Client 2147483647 addLogConsole Client 5 addLogConsole Client 9 2023-11-09 06:59:32:893 IBC: detected frame entitled: IB Gateway; event=Activated
Do you have any thoughts on this issue?
Thanks in advance.

thanks for sharing this @ValentinBaier
As far as I can tell, this is just a warning on the logs. I don't have any impact, at least on my side.
last night it happened like 3-4 times with no activity at all, and this morning everything works fine. it happened before and after the daily restart. I just got some fresh historical data and all works fine.
In any case, there is nothing that i can do to fix it. it's coming from IBC, if there is anything to fix it should be fixed upstream. I will re-label this as wontfix, as this is not a bug related to ib-gateway-docker.

I manage to identify this issue while I was connected throgh VNC

with error message in logs
quant-ibgateway-1     | 2023-11-18T14:15:10.952037425+01:00 2023-11-18 14:15:10:951 IBC: detected dialog entitled: Existing session detected; event=Opened
quant-ibgateway-1     | 2023-11-18T14:15:10.952171156+01:00 2023-11-18 14:15:10:952 IBC: Continue this session and let the other session exit (scenario 5)
quant-ibgateway-1     | 2023-11-18T14:15:10.952304026+01:00 2023-11-18 14:15:10:952 IBC: Click button: Reconnect This Session
quant-ibgateway-1     | 2023-11-18T14:15:11.027317665+01:00 2023-11-18 14:15:11:027 IBC: detected frame entitled: Attempt 3: Authenticating (trying for another 15 seconds)...; event=Lost focus
quant-ibgateway-1     | 2023-11-18T14:15:11.027722907+01:00 2023-11-18 14:15:11:027 IBC: detected frame entitled: Attempt 3: Authenticating (trying for another 15 seconds)...; event=Deactivated
quant-ibgateway-1     | 2023-11-18T14:15:11.028028511+01:00 2023-11-18 14:15:11:027 IBC: detected dialog entitled: Existing session detected; event=Activated
quant-ibgateway-1     | 2023-11-18T14:15:11.029156290+01:00 2023-11-18 14:15:11:029 IBC: detected dialog entitled: Existing session detected; event=Focused
quant-ibgateway-1     | 2023-11-18T14:15:11.030148796+01:00 2023-11-18 14:15:11:030 IBC: detected dialog entitled: Existing session detected; event=Lost focus
quant-ibgateway-1     | 2023-11-18T14:15:11.030853691+01:00 2023-11-18 14:15:11:030 IBC: detected dialog entitled: Existing session detected; event=Deactivated
quant-ibgateway-1     | 2023-11-18T14:15:11.031682689+01:00 2023-11-18 14:15:11:031 IBC: detected dialog entitled: Existing session detected; event=Closed
quant-ibgateway-1     | 2023-11-18T14:15:11.031818264+01:00 2023-11-18 14:15:11:031 IBC: detected frame entitled: Attempt 3: Authenticating (trying for another 15 seconds)...; event=Activated
quant-ibgateway-1     | 2023-11-18T14:15:11.032368338+01:00 2023-11-18 14:15:11:032 IBC: detected frame entitled: Attempt 3: Authenticating (trying for another 15 seconds)...; event=Focused
quant-ibgateway-1     | 2023-11-18T14:15:11.523906339+01:00 java.lang.InterruptedException
quant-ibgateway-1     | 2023-11-18T14:15:11.523976831+01:00     at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:998)
quant-ibgateway-1     | 2023-11-18T14:15:11.523993472+01:00     at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
quant-ibgateway-1     | 2023-11-18T14:15:11.524006236+01:00     at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
quant-ibgateway-1     | 2023-11-18T14:15:11.524018048+01:00     at com.sun.javafx.application.PlatformImpl.waitForStart(PlatformImpl.java:256)
quant-ibgateway-1     | 2023-11-18T14:15:11.524233233+01:00     at com.sun.javafx.application.PlatformImpl.runLater(PlatformImpl.java:277)
quant-ibgateway-1     | 2023-11-18T14:15:11.524272156+01:00     at com.sun.javafx.application.PlatformImpl.runLater(PlatformImpl.java:268)
quant-ibgateway-1     | 2023-11-18T14:15:11.524287795+01:00     at com.sun.javafx.application.PlatformImpl.checkIdle(PlatformImpl.java:392)
quant-ibgateway-1     | 2023-11-18T14:15:11.524301561+01:00     at com.sun.javafx.application.PlatformImpl.setImplicitExit(PlatformImpl.java:346)
quant-ibgateway-1     | 2023-11-18T14:15:11.524308945+01:00     at javafx.application.Platform.setImplicitExit(Platform.java:138)
quant-ibgateway-1     | 2023-11-18T14:15:11.524314997+01:00     at twslaunch.gstat.j.a(j.java:88)
quant-ibgateway-1     | 2023-11-18T14:15:11.524321809+01:00     at twslaunch.gstat.a.d(a.java:215)
quant-ibgateway-1     | 2023-11-18T14:15:11.524328792+01:00     at twslaunch.gstat.a.g(a.java:117)
quant-ibgateway-1     | 2023-11-18T14:15:11.524335946+01:00     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
quant-ibgateway-1     | 2023-11-18T14:15:11.524346055+01:00     at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
quant-ibgateway-1     | 2023-11-18T14:15:11.524359340+01:00     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
quant-ibgateway-1     | 2023-11-18T14:15:11.524375110+01:00     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
quant-ibgateway-1     | 2023-11-18T14:15:11.524392632+01:00     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
quant-ibgateway-1     | 2023-11-18T14:15:11.524404284+01:00     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
quant-ibgateway-1     | 2023-11-18T14:15:11.524415125+01:00     at java.lang.Thread.run(Thread.java:748)
quant-ibgateway-1     | 2023-11-18T14:15:11.566467618+01:00 2023-11-18 14:15:11:566 IBC: detected frame entitled: Starting application...; event=Lost focus
quant-ibgateway-1     | 2023-11-18T14:15:11.566516870+01:00 2023-11-18 14:15:11:566 IBC: detected frame entitled: Starting application...; event=Deactivated
quant-ibgateway-1     | 2023-11-18T14:15:11.566756821+01:00 2023-11-18 14:15:11:566 IBC: detected frame entitled: Starting application...; event=Closed

this is caused by a disconnection with IBKR API servers and data servers (not shown on the screenshot)
This confirms that this is not an issue with ib-gateway-docker but an issue comming from IBKR server farm.

@gnzsnz Thanks for your further info.
So if you place an order during this disconnection, can the order be executed normally? If not, what can we do to make sure the order executed as expected? From your log, I can see the interruption started at 2023-11-18 14:15:11:032, and it tried to resume at 2023-11-18 14:15:11:566. Does it mean the interruption only last for half the second? OR it will last for longer since it still take more time for IBC to finish login after detecting the frames. Thanks.

i'm my case it was constantly trying to reconnect, that's how I had time to take the screenshot.
I don't know about the specific case of open orders during a disconnect, maybe https://groups.io/g/insync can help.
Ib-gateway & IBC are doing their job, they try to reconnect.

Got it. Thanks very much. Will post here if I have any further findings.

authors: ValentinBaier gnzsnz josephchenhk

repo: gnzsnz/ib-gateway-docker