text:
[WIP] Adding bounding boxes and fixing notebooks

fixing notebook zoom code
adding code to manipulate bounding boxes in cornerstone
fixes #25

Codecov Report

Merging #25 into master will increase coverage by 1%.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #25   +/-   ##
=======================================
+ Coverage   63.28%   64.28%   +1%
=======================================
  Files           4        4
  Lines         463      476   +13
=======================================
+ Hits          293      306   +13
  Misses        170      170

Impacted Files
Coverage Δ

cornerstone_widget/utils.py
96.77% <100%> (+0.69%)
:arrow_up:

cornerstone_widget/cs_widget.py
90% <100%> (+0.15%)
:arrow_up:

cornerstone_widget/_version.py
44.4% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@betatim I've added the basic functionality, but the bounding boxes do not show up for some reason. The demo.ipynb is probably the best starting point for experimenting

authors: codecov-io kmader


text:
WIP: TracWiki links and formatting (#4)

Scope
There are TracWiki markup links which need to be converted. Here are examples of files (taken from https://github.com/chevah/trac-to-github/issues/2#issuecomment-764700864_ ):

TracWiki markup - https://trac.chevah.com/wiki/WikiStart?action=edit
RST markup with Trac directives - https://trac.chevah.com/wiki/Development/Python?action=edit
Mixed of RST with TracWiki macros (see bottom) - https://trac.chevah.com/wiki/Administrative?action=edit

At first, we can use this ticket to convert RST Trac links directives.
Later we should look at converting whole TracWiki pages.
Changes
TracWiki links should now work. I have added a new match case to _trac_rst_wiki_to_github_links, as well as new methods that handle TracWiki link syntax (with or without link text different from the article).
Also Trac tickets should work. There were only 3 of them, but it was easy enough to automate.
Only one malformed :trac: reference remains, which will be addressed manually.
TracWiki syntax: the script handles the following:

title/heading syntax: heading (===) and subheading (---)
lists: it unindents single-space-quoted lists, and adds an empty line before the first list element. The majority of files looks good; but nesting conversion is not proper.

What is not done
About lists: I did not properly implement nesting. I started to, but it turned out to be too difficult for me, considering the diminishing returns. An exhaustive (as of 2021-01-27) list of failures:

Architecture/Agent/General section "Remote file", under "steps"
Development/GetToKnow section "Products documentation and download pages".
Infrastructure/OutOfOrderMachines Mosna under "network cards"
Infrastructure/Services/VPN under "Overton"
Requirements/Vision, last two list items on page
Support/General section "Initial Assessment"
Support/CustomerDataBase/Template.rst and some files created from that template.

In addition, {{{ }}} code blocks need to be converted manually, by searching for {{{ in a commit before stripping the {{{#!rst }}} armor.
How to try and test the changes
reviewers: @adiroiban
First, copy the config.py.sample to config.py, because the Trac URL is specified as a config option.
Then, continue testing like PR #3:

Run tests using unittest from the project directory:
python3.8 -m unittest
Checking output
I did not find an easy way to verify the GitHub link behavior. The only way to properly test is to run the conversion, then push and check the wiki.
There are some things you can still check locally:

run the script, and then look at the diff using gitk, with the "Ignore space change" checkbox checked.

check what :trac: markers are left

This is ready for review.
I have some questions:

Is there any way to further deduplicate all the _trac[...] methods? They seem to rhyme to me, but could not quite extract another method from sections that repeat.
Are the tiny methods overkill? (_underline, _matches, _sub)? To me they look okay.

This is ready for review.
I have some questions:

Is there any way to further deduplicate all the _trac[...] methods? They seem to rhyme to me, but could not quite extract another method from sections that repeat.
Are the tiny methods overkill? (_underline, _matches, _sub)? To me they look okay.

needs-review

needs-review

source: gharchive/pull-request

repo: chevah/trac-to-github

license: MIT

license_type: permissive

license_source: github-api


text:
Microphone errors - InputStream

Getting errors with selecting any of the Microphone options.
Running on a Windows 11 machine. Buzz 0.9.0
Microphone: Microsoft Sound Mapper - Input
An error occurred while starting a new recording:Error opening InputStream:
Unanticipated host error [PaErrorCode -9999]: 'Undefined external error.' [MME
error 1]. Please check your audio devices or check the application logs for more
information.
Microphone: Microphone Array (Intel@ Smart
An error occurred while starting a new recording:Error opening InputStream:
Unanticipated host error [PaErrorCode -9999]: 'Undefined external error.' [MME
error 1]. Please check your audio devices or check the application logs for more
information.
Microphone: Primary Sound Capture Driver
An error occurred while starting a new recording:Error opening InputStream:
Unanticipated host error [PaErrorCode -9999]: 'DirectSound error' [Windows
DirectSound error -2147467259]. Please check your audio devices or check the
application logs for more information.
Microphone: PC Speaker (Realtek HD Audio output with SST)
An error occurred while starting a new recording:Error opening InputStream:
Invalid device [PaErrorCode -9996]. Please check your audio devices or check the
application logs for more information.
Microphone: Stereo Mix (Realtek HD Audio Stereo input)
An error occurred while starting a new recording:Error opening InputStream:
Invalid device [PaErrorCode -9996]. Please check your audio devices or check the
application logs for more information.
Microphone: Microphone (Realtek HD Audio Mic input)
An error occurred while starting a new recording:Error opening InputStream:
Invalid device [PaErrorCode -9996]. Please check your audio devices or check the
application logs for more information.
Microphone: Microphone Array 1 ()
An error occurred while starting a new recording:Error opening InputStream:
Invalid device [PaErrorCode -9996]. Please check your audio devices or check the
application logs for more information.

An error occurred while starting a new recording:Error opening InputStream: Unanticipated host error [PaErrorCode -9999]: 'Input/output error' [ALSA error -5]. Please check your audio devices or check the application logs for more information
Facing same error on ubuntu 22.04, any fix?
Suggestions would be much appreciated

Cause of issue on Ubuntu is known, we are working to fix it. To fix this for you, please connect necessary snap interfaces:
sudo snap connect buzz:audio-record
sudo snap connect buzz:password-manager-service
sudo snap connect buzz:pulseaudio
sudo snap connect buzz:removable-media

This will grant Buzz access to the microphone for sound recording, password manager service so it can store OpenAI API key and also removable media, so you can select files for transcription from removable media.
Issue with Windows is not clear yet. Does the microphones work in other apps?

For Windows case, please, see if this is relevant https://support.microsoft.com/en-gb/topic/error-message-error-initializing-direct-sound-occurs-when-starting-directx-c892d63a-ac48-51c4-8c25-3653448703ed
IMO, googling for errors around DirectSound error' [Windows DirectSound error -2147467259] has the most potential to get to some solution, PaErrors seem relatively generic.

If it is Windows, please see if Buzz has permission to use the microphone in Settings -> Privacy -> Microphone
See method 1 in this video https://www.youtube.com/watch?v=eRcCYgOuSYQ
For method 2 there is no need to uninstall the antivirus, but see if you can temporarily disable it or if there are settings to allow Buzz use the microphone or make it a trusted application.

source: gharchive/issue

authors: Jaykumaran raivisdejus shazwozza

repo: chidiwilliams/buzz


text:
chore: Update example/.gitignore

Flutter automatically removes one line from the .gitignore when
running flutter build web.

Current dependencies on/for this PR:

main

PR #49   👈

PR #50

This stack of pull requests is managed by Graphite.

Merge activity

Jan 10, 10:09 AM: @Mr-Pepe merged this pull request with Graphite.

repo: chill-chinese/stroke-order-animator


text:
feat: ability to change proxy options for any request

Description
Ability to change proxy options for any request.
One example: dynamic agent addition
Motivation and Context

How has this been tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

I have dynamic agent need.
any method to do it?

I also want to change agent on demand. Is there any idea or suggestion?

same

authors: IORazutkin alanhg cumt-robin twinkle77

repo: chimurai/http-proxy-middleware

license: mit

license_source: bigquery


text:
Possible problem when subclassing QThread

Greetings!
I noticed that class Thread referred a StackOverflow post, while a recent comment to it mentioned that subclassing QThread is always the wrong thing to do, because the QThread object lives in the parent thread; ergo, slots signaled on this object run in the parent thread rather than the actual thread encapsulated by the QThread object. Signal-slot connections are the entire basis for thread synchronization in Qt. Ergo, subclassing QThread obstructs synchronization. .
I'm trying to learn the usefulness of such small updates on StackOverflow. Would this comment help improve your code? I understand that such defect might not happen in real life situation. In that case, do you think this comment can help prevent future bugs (for example, when the code were reused somewhere else)?
I'll really appreciate it if you could kindly give me some feedback or suggestions. Thank you very much for your time.
Have a nice day!

Greetings!
If I understand you correctly, you're not asking about the code but whether your comment makes a difference and helps me (and other users) to avoid bugs and write better code?
The answer is: YES! Thanks a lot for your suggestion, the code you're referring to is several years old and my coding skills at that time were even more limited than they are now. But I will need Threading in my main project (pyfda) in the very near future which makes your input especially valuable for me - perfect timing! Please do comment on other people's code, that's the essence of StackOverflow.
I think I will start with cleaning up and updating this repo before I transfer some of the code to pyfda.

authors: OshinoMoumou chipmuenk


text:
WORKSPACE collision

I (and maybe others) already have WORKSPACE defined. (In my case it's for Perforce). Can this be renamed to (something like) CALIPTRA_WORKSPACE?

Please take a look at PR #21, with a fix for this issue.

authors: calebofearth steven-bellock

repo: chipsalliance/caliptra-rtl


text:
Failed to deassert the reset of uc using JTAG for HVM

According to the section "Provisioning IDevID during manufacturing" in the Caliptra Main Spec, one should be able to use JTAG to set the CPTRA_DBG_MANUF_SERVICE_REG and CPTRA_DBG_MANUF_SERVICE_REG in soc_ifc and deassert the reset of the uc. In our test, we failed to do so. We found that when BootFSMBrk is set to one and Fuse_Done is high, the boot_fsm_ps is stuck in the BOOT_WAIT state. Thus, fw_update_rst_window is tied to 1.
always_comb fw_update_rst_window = boot_fsm_ps inside {BOOT_FW_RST, BOOT_WAIT};

The fw_update_rst_window signal further disables the gated clock used in the dmi_jtag_to_core_sync module. As a result reg_en and reg_wr_en enable signals are tied to zero  disables the JTAG access to the soc_ifc.
There is a mismatch between the spec and the code. Can you confirm if this is the design intent?

dmi_jtag_to_core_sync reset should be powergood, and not be impacted by fw_update_rst_window.
fw_update_rst_window is used to force the ahb bus idle during uC resets to protect from metastability on the bus due to RDC.
I'm going to need some more information to try to reproduce this.
You are in debug or manufacturing mode and reach BOOT_WAIT state, and powergood is asserted, and you are not able to access JTAG?

You are in debug or manufacturing mode and reach BOOT_WAIT state, and powergood is asserted, and you are not able to access JTAG?
@Nitsirks Yes,  that is correct. Powergood is asserted. The reset of dmi_jtag_to_core_sync is released already, but the input clock to the synchronizer is gated and tied to ground.

I understand the issue now. Looking into how our JTAG validation missed this.
Is it possible for you to see if changing this line resolves the issue for you? In the mean time I'll validate this as well.
always_comb fw_update_rst_window = (boot_fsm_ps == BOOT_FW_RST) |
                                   ((boot_fsm_ps == BOOT_WAIT) & (wait_count != 0));

Is it possible for you to see if changing this line resolves the issue for you? In the mean time I'll validate this as well.

The change to the code works
telnet 127.0.0.1 4444
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
Open On-Chip Debugger
> riscv.tap.0 riscv dmi_read 0x60
0x0
> riscv.tap.0 riscv dmi_write 0x60 1
> riscv.tap.0 riscv dmi_read 0x60
0x1
> riscv.tap.0 riscv dmi_read 0x61
0x0
> riscv.tap.0 riscv dmi_write 0x61 1
> riscv.tap.0 riscv dmi_read 0x61
0x1

an old RDC change introduced this bug...PR is done, regressions ran, will be released into 1.1 and 1.0.2

authors: Nitsirks bharatpillilli blueblue0124


text:
Change name of our json-package at the right place.

I didnn't realize that the name of our json package is not coming from the nlohmann json source tar, but from our own Bazel file we made ourself. So changing the name is much simpler there than providing a patch :)
Remove the patch from #2120 again and just change the name there.
For the work in #2121 though this means, that it would probably better to use our bazel file (as it uses the single-header version as well as does proper settings for exceptions)

@lromor this is for you to review

repo: chipsalliance/verible


text:
Add starlark jcxxgen

-> Relevant submit in this stacked change <-

Move code jcxxgen code generation into *bzl file.
This makes it more readable in the BUILD file.
jcxxgen(
    name = "lsp-protocol",
    src = "lsp-protocol.yaml",
    out = "lsp-protocol.h",
    namespace = "verible::lsp",
)

Codecov Report

Merging #980 (a951340) into master (43375d7) will increase coverage by 0.01%.
The diff coverage is 96.96%.

@@            Coverage Diff             @@
##           master     #980      +/-   ##
==========================================
+ Coverage   92.79%   92.81%   +0.01%
==========================================
  Files         322      324       +2
  Lines       20974    21072      +98
==========================================
+ Hits        19463    19558      +95
- Misses       1511     1514       +3

Impacted Files
Coverage Δ

common/lsp/json-rpc-dispatcher.h
100.00% <ø> (ø)

common/lsp/message-stream-splitter.cc
100.00% <ø> (ø)

common/lsp/message-stream-splitter.h
100.00% <ø> (ø)

common/lsp/file-event-dispatcher.cc
95.23% <95.23%> (ø)

common/lsp/dummy-ls.cc
97.22% <97.22%> (ø)

common/lsp/json-rpc-dispatcher.cc
100.00% <100.00%> (ø)

common/lsp/lsp-text-buffer.cc
100.00% <100.00%> (ø)

common/lsp/lsp-text-buffer.h
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

authors: codecov-commenter hzeller


text:
not listing bought items for sale but still updating profit

autobuyer is purchasing players but isnt listing them up for sale. since the update with profit total and search bars.
have tried the simple fixes ie restart app, delete and reistall etc
is there any way to run an older version of the bot?

You can find all the versions of bot here -https://github.com/chithakumar13/FUT-Auto-Buyer/releases

license: ISC


text:
Remove arrow2

Fixes #179

Reconsider removing arrow2 as the maintenance burden is minimal.


text:
(itunes) Uninstalling doesn't remove Bonjour

Chocolatey Version
Other (note in the comments)
Chocolatey License
None
Package Version
12.12.6.1
Current Behaviour
choco uninstall itunes does not remove Bonjour. You have to remove it through Programs and Features.
Expected Behaviour
choco uninstall itunes should remove Bonjour, since choco install itunes installs Bonjour.
Steps To Reproduce

In an environment where Chocolatey reports that the package itunes is not installed, and where Programs and Features does not list any of, "Apple Mobile Device Support," "Bonjour," or, "iTunes," as installed programs…
Run choco install itunes
Check Programs and Features. It should now list the three programs mentioned above.
Run choco uninstall itunes
Check Programs and Features again (refresh if you left it open). "Bonjour" will still be listed.

Environment
- Operating System: 10.0.19045.0
- PowerShell Version: 5.1.19041.1682
- Shell: PowerShell

Chocolatey Log
https://gist.github.com/awebeer256/34bc58c849774be5c59a97a870995386

Anything else?
Chocolatey version 1.2.0

Add not much you can do except only uninstall Bonjour yourself because there are many conditions where Bonjour is installed : Skype, iChat, and iPhoto install Bonjour too, so we need to check if one of these is not installed before. Other thing, sometimes, you want to keep Bonjour... Bets way to solve your problem is probably by creating a package Bonjour, add it to dependency of iTunes, and tell the user that he add to remove Bonjour if he want...

Okay, that's fair. I didn't know that Bonjour was a dependency of multiple things, including those beyond the bounds of Apple.
I'd still like this issue to remain open, to hopefully encourage someone to do this:

creating the package Bonjour, add it to the iTunes dependencies

…but I'd no longer consider it urgent.

The bonjour package already exists.

I'd argue that this doesn't deserve to be closed until the itunes package is modified to not include installing Bonjour, but to instead have the bonjour package as a dependency.

@awebeer256 To be clear, this is not what this issue was about. It was about Bonjour not being uninstalled and was marked as a bug.
If want to add Bonjour as a dependency and not have the iTunes installer install Bonjour, then that is something entirely different. To get buy in to do that, please raise a discussion.

authors: Starmania awebeer256 pauby


text:
Add additional security features to server (optional)

These tasks were split out from #9, and include:

Secure Nexus repo with credential
Turn on CCM Client & Service Salts
Generate Register-InternetEndpoint.ps1 script to pair with a ClientSetup.ps1 script

On further discussion with @steviecoaster, we've agreed to leave some of this work out of the first release. We are striving to keep this simple, and weaving in the -InternetEnabled bits will add complexity at this point. We may revisit this later, possibly when revising the "distributed" approach with a new version of Organizational Deployment Guide.
@steviecoaster, I'll leave this open just for this one piece, if that's OK:

Generate Register-Endpoint.ps1 script to pair with a ClientSetup.ps1 script, and output this script to choco-setup\files.

For the first release, to meet our internally-defined security requirements and maintain parity with QDE, we have decided to include the ability to define your own SSL Certificate.. This should cover the use cases of users bringing their own Domain cert, or purchasing a third-party cert. This is our minimum requirement if the user intends to expose this server to external endpoints on the Internet.
This will involve the following:

Update Set-SSLSecurity.ps1 with logic to:

Accept external cert
Copy to appropriate cert store
Reassign services and bindings
Import cert into Java Key Store for Nexus
Update firewall rule for Nexus to 8443

Update Jenkins job templates in the scripts folder to reflect change of port for repo URI
Move order of Jenkins script to the end again, as we need the CN to update repo URI

repo: chocolatey/choco-quickstart-scripts


text:
Flash Packages Update to Latest Version

Do to a 'error' in the processing of the update.ps1 file at this time. The following packages didn't get updated to the Latest Version(s). This will bring the packages up to date.
@AdmiringWorm

This is automatic package and as such its AU updater should be fixed, packages should not get manually updated. See here:
https://gist.github.com/gep13/bd2eaa76f2a9ab739ca0544c502dca6e#errors

I see that you already did some work on AU, what is wrong with submitting only update.ps1 changes ?

repo: chocolatey/chocolatey-coreteampackages


text:
(GH-113) Fix incorrect format for title element

The format for the title element is incorrect, merging this PR fixes that.
This will also close #113

@mkevenaar your changes have been merged, thanks for your contribution 👍

@mkevenaar your changes have been merged, thanks for your contribution 👍

repo: chocolatey/docs


text:
hsc2hs generates output with invalid path on Windows

I'm working on getting this package to build on Windows (see https://github.com/rcook/clang-pure/commit/42ca11c2c9ddc2723b71b8ebef7a82ff277dd7a9). Currently, there is a problem related to hsc2hs: running stack build generates an output file srcLanguageCClangInternalFFI.c in the root directory corresponding to the source file src/Language/C/Clang/Internal/FFI.hsc.
When I get some more time I'll investigate and figure out if there is a straightforward fix for this.

I think it's somehow related to Language.C.Inline.Unsafe.

Update: I have isolated this as either a bug in hsc2hs or inline-c with a minimal repro independent of this project. I've filed a bug against inline-c: https://github.com/fpco/inline-c/issues/50

Also: https://ghc.haskell.org/trac/ghc/ticket/12504 - just in case this is a bug in hsc2hs and not inline-c.

repo: chpatrick/clang-pure


text:
DeprecationWarning: Tapable.plugin is deprecated. Use new API on .hooks instead

Hi,
This warning is causing, due to upgradation on Webpack 4 because they are still using the old plugin API, they need to be upgraded to the latest version.
I am getting the below error:
(node:10740) DeprecationWarning: Tapable.plugin is deprecated. Use new API on .hooks instead
[ERROR]     at VisualizerPlugin.apply (C:\Users\Hp\Desktop\New folder (2)\gateway_upgrade\node_modules\webpack-visualizer-plugin\lib\plugin.js:44:22)
[ERROR]     at webpack (C:\Users\Hp\Desktop\New folder (2)\gateway_upgrade\node_modules\webpack\lib\webpack.js:37:12)
[ERROR]     at processOptions (C:\Users\Hp\Desktop\New folder (2)\gateway_upgrade\node_modules\webpack-cli\bin\webpack.js:437:16)
[ERROR]     at yargs.parse (C:\Users\Hp\Desktop\New folder (2)\gateway_upgrade\node_modules\webpack-cli\bin\webpack.js:513:3)
[ERROR]     at Object.parse (C:\Users\Hp\Desktop\New folder (2)\gateway_upgrade\node_modules\webpack-cli\node_modules\yargs\yargs.js:552:18)
[ERROR]     at C:\Users\Hp\Desktop\New folder (2)\gateway_upgrade\node_modules\webpack-cli\bin\webpack.js:218:8
[ERROR]     at Object. (C:\Users\Hp\Desktop\New folder (2)\gateway_upgrade\node_modules\webpack-cli\bin\webpack.js:515:3)
[ERROR]     at Module._compile (module.js:652:30)
[ERROR]     at Object.Module._extensions..js (module.js:663:10)
[ERROR]     at Module.load (module.js:565:32)
[ERROR]     at tryModuleLoad (module.js:505:12)
[ERROR]     at Function.Module._load (module.js:497:3)
[ERROR]     at Module.require (module.js:596:17)
[ERROR]     at require (internal/module.js:11:18)
[ERROR]     at Object. (C:\Users\Hp\Desktop\New folder (2)\gateway_upgrade\node_modules\webpack\bin\webpack.js:80:2)
[ERROR]     at Module._compile (module.js:652:30)
[ERROR]     at Object.Module._extensions..js (module.js:663:10)
[ERROR]     at Module.load (module.js:565:32)
[ERROR]     at tryModuleLoad (module.js:505:12)
[ERROR]     at Function.Module._load (module.js:497:3)
[ERROR]     at Function.Module.runMain (module.js:693:10)
[ERROR]     at startup (bootstrap_node.js:191:16)
[ERROR]     at bootstrap_node.js:612:3

any update?

@chrisbateman Why are there no updates on this? It has been months that it has been an issue...

update?

This workaround has worked for me
File: node_modules/webpack-visualizer-plugin/lib/plugin.js
Line: 44
change
compiler.plugin('emit', function (compilation, callback) {
by
compiler.hooks.done.tap('emit', function (compilation, callback) {

I am getting this issue when upgrading from Webpack3 to Webpack4
error details
DeprecationWarning: Tapable.plugin is deprecated. Use new API on .hooks instead
at VisualizerPlugin.apply (node_modules\webpack-visualizer-plugin\lib\plugin.js:44:22)
at webpack (node_modules\webpack\lib\webpack.js:47:13)
Can any one let me know which version of webpack i need to use after 4 and i will not modify in node modules.

repo: chrisbateman/webpack-visualizer


text:
chore(dev): release 0.16.4

:robot: I have created a release beep boop
0.16.4 (2024-11-22)
Bug Fixes

copy image uploads instead of rename, because we cant be sure of fs layout (8af83e7)
pass correct pix_fmt to scale_cuda filter (#980) (d6448e2)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.16.4
:sunflower:

repo: chrisbenincasa/tunarr

license: Zlib


text:
Contribution: Use Heading Level Indicator as the fold toggle

Type of Contribution
CSS Class(es)
Description
body.no-heading-level-in-lp .is-live-preview .HyperMD-header .cm-fold-indicator .collapse-icon {
    align-items: flex-end;
    color: var(--text-muted);
    display: flex;
    opacity: 1 !important;
    padding-bottom: 1.5px;
}
body.no-heading-level-in-lp .is-live-preview .HyperMD-header .cm-fold-indicator.is-collapsed .collapse-icon {
    color: var(--text-accent);
}
body.no-heading-level-in-lp .is-live-preview .HyperMD-header .cm-fold-indicator .collapse-icon:hover {
    color: var(--hover-accent-2);
}
body.no-heading-level-in-lp .is-live-preview .HyperMD-header .cm-fold-indicator .collapse-icon::before {
    color: currentColor;
    font-family: var(--font-monospace);
    font-size: .8rem;
    font-style: normal;
    line-height: 1.15em;
    opacity: 1 !important;
    position: relative;
    white-space: nowrap;
}
body.no-heading-level-in-lp .is-live-preview .HyperMD-header-1 .cm-fold-indicator .collapse-icon::before {
    content: "H1";
}
body.no-heading-level-in-lp .is-live-preview .HyperMD-header-2 .cm-fold-indicator .collapse-icon::before {
    content: "H2";
}
body.no-heading-level-in-lp .is-live-preview .HyperMD-header-3 .cm-fold-indicator .collapse-icon::before {
    content: "H3";
}
body.no-heading-level-in-lp .is-live-preview .HyperMD-header-4 .cm-fold-indicator .collapse-icon::before {
    content: "H4";
}
body.no-heading-level-in-lp .is-live-preview .HyperMD-header-5 .cm-fold-indicator .collapse-icon::before {
    content: "H5";
}
body.no-heading-level-in-lp .is-live-preview .HyperMD-header-6 .cm-fold-indicator .collapse-icon::before {
    content: "H6";
}
body.no-heading-level-in-lp .is-live-preview .HyperMD-header .cm-fold-indicator .collapse-icon svg {
    display: none;
}
body.no-heading-level-in-lp .is-live-preview .HyperMD-header .cm-foldPlaceholder {
    display: none;
}

Screenshot
https://user-images.githubusercontent.com/134939/164535060-d3e353f1-816b-46ad-8338-dda2095c642a.mp4

oh that's a small but really cool idea.
(Just so you know, I am not ignoring these two or the older contribution – I just want to finish the big 2.0 update of the theme before I take a more detailed look how to add your contributions.)

Okay, this idea is super cool, but I hesitate a bit with adding it, since it would be a bit unintuitive to some users, that in some places of the theme, the fold triangles cause a fold, while in this area of the theme, the level indicator causes a fold.
The idea itself is really cool though, so even though I am not adding it, you should definitely post it in the forum and/or Discord for others to see!

authors: chrisgrieser pryley

repo: chrisgrieser/shimmering-focus


text:
[Bug:low priority]: Broken Ligatures

Bug Description
caveat I'm unsure if this is a bug or not as it appears to be intentional (which is okay).
Ligatures used to work but were recently disabled.
I git bisect'd to this commit
/* make html comments readable by disabling ligatures in edit mode
 (only in effect when using a font different from iA Writer Quattro)  */
 .markdown-preview-view,
 .cm-s-obsidian {
 	font-variant-ligatures: none;
 }

Easily fixable with a snippet, so no worries.  It might be nice to enable or disable via style settings.
Relevant Screenshot
N/A
To Reproduce
N/A
Obsidian Version
0.15.3
Installer Version
0.14.15
Font Size
16
Which editor are you using?

[X] New Editor
[ ] Legacy Editor

In which mode(s) does the problem occur? (if applicable)

[X] Source (Edit)
[X] Reading (Preview)
[X] Live Preview

Which operating system?

[X] macOS
[ ] Linux
[ ] Windows
[ ] iOS
[ ] Android

Plugin-Specific Problems

[X] I took note of the specific instructions regarding those plugins.

Checklist

[X] I updated to the latest version of the theme (Settings → Appearance → Themes - Manage → Update).
[X] I made sure that the issue is related to this theme by checking that the problem does not occur with the default theme.
[X] In case I am missing an UI element, I have checked that it cannot be re-enabled with the Style Settings plugin.
[X] If the bug occured after updating the theme, I read the last couple of entries in the changelog to make sure the bug is not an intentional change. (In that case, there will most likely be a style setting to turn it off again.)

oh sorry, that was simply a mistake where I forgot to change something back a while ago 🙈
it was meant to be
.cm-s-obsidian .cm-comment {
  font-variant-ligatures: none;
}

fixed in latest release. Thanks for pointing it out

Thanks!!
On June 24, 2022, GitHub @.***> wrote:

oh sorry, that was simply a mistake where I forgot to change something
back a while ago 🙈
it was meant to be
.cm-s-obsidian .cm-comment { font-variant-ligatures: none; }
fixed in latest release. Thanks for pointing it out

—
Reply to this email directly, view it on GitHub
<https://github.com/chrisgrieser/shimmering-
focus/issues/176#issuecomment-1165846671>, or unsubscribe
<https://github.com/notifications/unsubscribe-
auth/AADOXTCLPE2AUNVY45FOVGTVQX77FANCNFSM5ZYUS4FQ>.
You are receiving this because you authored the thread.Message ID:
@.***>

authors: chrisgrieser pmbauer


text:
Is it possible to install on Raspberry Pi 3?

I tried installing it on Raspberry Pi 3. But MongoDB has failed many times. How can I install it correctly?

@mstfcan
Hey, I tried on RPi3 and he is not happy to run. So try to use RPi4, which I tested.

authors: chrisleekr mstfcan

repo: chrisleekr/binance-trading-bot


text:
Error: Way too much request weight used; IP banned until ....

Version

Description

Hi,
I'm using v0.0.73 (a7d650b) and got this error.
Job: Trailing Trade Indicator Code: -1003 Message: Way too much request weight used; IP banned until 1627635599203. Please use the websocket for live updates to avoid bans.
I'm currently only monitoring 6 symbols with a buying signal (15m).
What i can do to reduce the interval and avoid using too much weight in a short time?
Thank you!

Another question.
Is there a reason why websocket is not used for live updates?
Might give a go to implement if it's just time/effort on your end.

Hi @claytonnarcis
I am also monitoring 6 symbols with 15m/30.

Is there a reason why websocket is not used for live updates?

FYI, WebSocket is used to retrieve the current price.
Let me confirm with you few things:

Can you show me your symbol configuration?
Did you have many open orders?

1.) Here you go.

2.) None. All waiting to execute.
Prior to this ban alert. This error popup.
Execution failed (08:34:59.588) Job: Trailing Trade Indicator Code: -1003 Message: Too much request weight used; current limit is 1200 request weight per 1 MINUTE. Please use the websocket for live updates to avoid polling the API.

Really? There were no open orders?
Hmm, something else is going on.
Can you see the bottom of the frontend which will show the usage of API like below:

Can you check what was the maximum used weight?

Here are some screenshots from Slack.

Can you run following command in your server and provide me the log?
docker logs binance-bot -f | bunyan -c 'this.job === "trailingTradeIndicator"' > test.log
In the log, it will display apiLimit that was used, so we can calculate how much the request used the API.

Before the alert that 1269 weight is used, were there any orders placed?
I know you mentioned there was no open order, just want to make sure.

hang on, let me double check.

my bad, there were two open orders and then i got ban.
Refresh my IP, trade was executed.

Let me know if you need the order history and trades history screenshot from the binance app

Running bunyan threw errors like this
(node:46) UnhandledPromiseRejectionWarning: LockError: Exceeded 1 attempts to lock the resource "redlock:trailing-trade-symbols:ETHUPUSDT-symbol-info".  at /srv/node_modules/redlock/redlock.js:431:20  at tryCatcher (/srv/node_modules/bluebird/js/release/util.js:16:23)  at Promise.errorAdapter [as _rejectionHandler0] (/srv/node_modules/bluebird/js/release/nodeify.js:35:34)  at Promise._settlePromise (/srv/node_modules/bluebird/js/release/promise.js:601:21)  at Promise._settlePromise0 (/srv/node_modules/bluebird/js/release/promise.js:649:10)  at Promise._settlePromises (/srv/node_modules/bluebird/js/release/promise.js:725:18)  at _drainQueueStep (/srv/node_modules/bluebird/js/release/async.js:93:12)  at _drainQueue (/srv/node_modules/bluebird/js/release/async.js:86:9)  at Async._drainQueues (/srv/node_modules/bluebird/js/release/async.js:102:5)  at Immediate.Async.drainQueues [as _onImmediate] (/srv/node_modules/bluebird/js/release/async.js:15:14)  at processImmediate (internal/timers.js:464:21)
trailing-indicator-cn.log

The trailingTradeIndicator processes following steps:

https://github.com/chrisleekr/binance-trading-bot/blob/master/app/cronjob/trailingTradeIndicator.js#L64

Get symbol configuration - does not use API
Get override action - does not use API
Execute dust transfer - if you execute dust transfer, it uses 1 API weight
Get account info - uses 10 API weights per second = maximum 600 API limits per min
Get indicators - uses 2 API weights per second = maximum 120 API weights per min.
Get open orders - uses 3 API weights per second = maximum 180 API weights per min.
Save data to cache - does not use API.

So in maximum with trailing trade indicators, it should use 900 API weights, but usually less than 900 because the trailingTradeIndicator takes more than 1 sec.

my bad, there were two open orders and then i got ban.
Refresh my IP, trade was executed.

The trailingTrade cronjob without orders does not use API; however, when there are open orders, it checks the order status based on the checkOrderExecutePeriod specified in the config.
Since you had some open orders, which still does not make sense because it was only 2 open orders.
My suspicion is the symbol ETHDOWNUSDT was down dramatically and cancel/place lots of orders within a min.
But still does not make sense because each order should have 20 seconds cool time temporaryDisableActionAfterConfirmingOrder and 10 seconds of checking order status checkOrderExecutePeriod.
https://github.com/chrisleekr/binance-trading-bot/blob/master/config/default.json#L92
Have you changed the config?

I cannot find any issue with your configuration.
Hey, can you see at the bottom of the frontend how much is maximum API used weight per min?
Mine is typically about 550~600.

will monitor, it's 16 right now. No open buy orders.

Let me know, it could be a bug that I didn't find.
Another suggestion I can make is increasing checkOrderExecutePeriod to 20 or something.

https://github.com/chrisleekr/binance-trading-bot/blob/master/config/default.json#L97

You can configure BINANCE_JOBS_TRAILING_TRADE_SYSTEM_CHECK_ORDER_EXECUTE_PERIOD=20 in the .env file.

Sure thing, will delay the check order.
Triggered by the grid trade.

Good, let me know. If the issue is not occurring again, please close the issue.

Hi Chris. A friend was having the same issues at my fork. Then he pulled your master version, erased docker data and got the bot up. He was instantly banned by IP, he monitored +-12 symbols.
After he had those problems, I went further and tried to change how the bot works, and I possibly found a way to keep the weight low while having various coins and not hurting much the bot update values performance.
I think the changes I did was:

Add a seconds verify at every API call. This makes sure the same coin won't trigger the same steps over and over again.

As I needed a different way to setup a last buy price, I did a 'order verification' code at ensure-order-placed.js that now tells the bot if the order was filled or not (I used the ensure-manual-buy-order.js code).

If I'm not wrong, the coin won't be stuck too at the same step, before my changes it seems the bot could actually stuck at a step and then will trigger that step eternally, increasing API usage possibly.

There was more changes, but I'm just writing them to give you a notion.
It was your master version 0.72 btw that he received the ban.

@pedrohusky

After those steps I can monitor almost 20 coins without even reaching 800 weight.

The bot itself is designed to monitor as many coins as configured. It supposes to not over 900 API weight limits per min.
I am sure you already know by looking at the code. API requests are mostly done in the trailing trade indicators cronjob.
And in the trailing trade cronjob is only doing create/query/cancel orders. Those calls cost only 1 API weight per call.
@claytonnarcis
A few weeks ago, I had received the API limit exceeded and found refreshing account information costing 20 API limit, not 10 API limit - https://binance-docs.github.io/apidocs/spot/en/#account-information-user_data
It should've cost only 10 API limit per call. After a few hours later, it's back to 10 API weight.
Hence, I added this configuration to reduce the call for refreshing account information, which is currently set as 1.
If it happens again, you can try increasing this as well.
"refreshAccountInfoPeriod": {
  "__name": "BINANCE_JOBS_TRAILING_TRADE_SYSTEM_REFRESH_ACCOUNT_INFO_PERIOD",
  "__description": "Set the seconds for the period of checking the account info.",
  "__format": "number"
}

Anyway, if the issue is not occurring continuously, please close the issue.

Just wanna say thanks for this fix.
I am using a 40 pairs configuration with BUSD and a 6 grid trade config. for buying and when market went down I had more than 12 orders created by the bot and a lot of this API weight error msg. showing up on Slack.
After changing by config. according to this issue, everything seems to be good.
I've just added the folowing lines into the .env config. file and restarted the bot.

# See https://github.com/chrisleekr/binance-trading-bot/issues/251
BINANCE_JOBS_TRAILING_TRADE_SYSTEM_CHECK_ORDER_EXECUTE_PERIOD=20
BINANCE_JOBS_TRAILING_TRADE_SYSTEM_REFRESH_ACCOUNT_INFO_PERIOD=2

Thanks guys.

authors: chopeta chrisleekr claytonnarcis pedrohusky


text:
Dust not included in Open Trades asset indicator

Version

v0.0.96
Description

After the sell order is executed there is always some dust left. It should be counted even if no trade is open as this dust will be included in next trade.
To Reproduce

Make some trades which left dust on you balance
When no trade is open the dust is not counted into value of asset

Expected Behaviours

Dust should be counted to see real value of asset even if no trade is open.
Screenshots

Additional context

Oh, nice catch.

authors: chrisleekr uhliksk


text:
update from 1.44 to 1.84, old data disappear

config：3master、3filer、5volumes、1mount、1s3
volume -max=256
1.44:
[root@cpu-001 ~]# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdg1       440G   16G  402G   4% /
devtmpfs         63G     0   63G   0% /dev
tmpfs            63G     0   63G   0% /dev/shm
tmpfs            63G  4.2G   59G   7% /run
tmpfs            63G     0   63G   0% /sys/fs/cgroup
/dev/sda        3.5T  9.3G  3.3T   1% /data1
/dev/sdb        3.5T  976G  2.4T  30% /data2
/dev/sdc        3.5T  660G  2.7T  20% /data3
/dev/sdd        3.5T  621G  2.7T  19% /data4
/dev/sde        3.5T  588G  2.7T  18% /data5
/dev/sdf        3.5T  798G  2.5T  24% /data6
tmpfs            13G     0   13G   0% /run/user/1001
tmpfs            13G     0   13G   0% /run/user/1237
tmpfs            13G     0   13G   0% /run/user/0
SeaweedFS       607G  567G   40G  94% /data1/seaweedfs/data/mount
1,84:
[root@cpu-001 ~]# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdg1       440G   16G  402G   4% /
devtmpfs         63G     0   63G   0% /dev
tmpfs            63G     0   63G   0% /dev/shm
tmpfs            63G  4.2G   59G   7% /run
tmpfs            63G     0   63G   0% /sys/fs/cgroup
/dev/sda        3.5T  9.3G  3.3T   1% /data1
/dev/sdb        3.5T  976G  2.4T  30% /data2
/dev/sdc        3.5T  660G  2.7T  20% /data3
/dev/sdd        3.5T  621G  2.7T  19% /data4
/dev/sde        3.5T  588G  2.7T  18% /data5
/dev/sdf        3.5T  798G  2.5T  24% /data6
tmpfs            13G     0   13G   0% /run/user/1001
tmpfs            13G     0   13G   0% /run/user/1237
tmpfs            13G     0   13G   0% /run/user/0
10.18.1.28:9333/       110T  17M   110T  0% /data1/seaweedfs/data/mount
567G data not exist，and another question：why 110T，we have 6 disk，unable to 110T，how to set it to real max space。
i just replace weed and restart all services。am i wrong ?

Please follow issue template.

256 x 30 GB = 110 TB

authors: WYmindsky chrislusf

repo: chrislusf/seaweedfs


text:
Screen Glitch with Instant Fade Transition

Description:
When using the instant fade transition in GBStudio, the screen glitches and does not display correctly. This issue occurs consistently regardless of the project size or number of scenes. The bug has been observed across all versions of 4.x.
Steps to Reproduce:

Create or open a project in GBStudio (version 4.x).
Add at least 2 scenes to the project.
Set up a scene transition with the "instant" fade option.
Execute the transition in-game.
Observe the screen glitch.

Expected Behavior:
The screen should transition instantly without any graphical glitches.
Observed Behavior:
The screen shows graphical glitches and does not transition correctly.
Affected Versions:

GBStudio 4.x (all versions tested so far)

Additional Context:
This issue appears consistently across projects of all sizes, with no minimum number of scenes required to trigger the glitch.

That's how the GB hardware works - the fade is needed to hide the loading of the scene tiles into RAM, otherwise you see glitches. You can get an 'instant' effect only in V4 onwards if you use the common tileset functionality.
It's in the documentation - https://www.gbstudio.dev/docs/project-editor/scenes#common-tilesets

Closing as @chunkysteveo says unfortunately this is just how the hardware works and the common tilesets feature was added as way to allow instant transitions without seeing the tile loading

authors: chrismaltby chunkysteveo kill99999-dev

repo: chrismaltby/gb-studio


text:
[Feature] Actor Invoke

This PR implements a new event, Actor Invoke.
This event lets you invoke another Actor from inside your script, like a method call.
When that invocation is completed, it returns to where it was invoked, and continues as normal.
This also allows for recursion, which might be used for a lot of interesting purposes.
As of now, I have hardcoded the call stack depth to 8. I don't know how much would be viable to have, as I was concerned about memory usage. With a depth of 8, it should take about 16 bytes of memory.

Thanks Thomas, I merged the Scene State pull request but this one has conflicts now, it seems to partially include the Scene State code again but with different function names.
On a side note I'm thinking of changing compileEntityEvents.js a little so instead of hard coding the command code as a hex number, to instead just use the index in that array. That way we should have less merge conflicts as you wouldn't need to explicitly say 0x47 is StackPop you'd just need to make sure that the order of the commands in that array matches the order in the corresponding array in ScriptRunner.c

@chrismaltby I have now fixed the conflicts

authors: chrismaltby thomas-alrek


text:
Add .env files to build process in frontend

The build is breaking on production because it doesn't care about the .env file on the box. Use a repo secret to fix this.

The above commit fixed the .env file but I still need to get it to restart pm2.


text:
dynamic insertion of commands

Hi Christian,
I am looking dynamic insertion/deletion of commands in execbeat.yml file. That is when I add execbeat.yml in initial build it may not have exhaustive list of commands. But when needed i should be able to add/delete a new set of commands to execbeat.yml.
Is it possible as of now?
With Best wishes,
Veera

Hi Veera,
I'm not sure if I understand your request as you speak of "building" and adding commands. There are pre-build binaries available under "releases" and you don't need to rebuild Execbuild after adding new commands but just restarting one of the pre-build binaries is sufficient.

Hi Christian,
Thanks for your reply.
My question is different. Rephrasing it.
I wanted to add or remove commands into execbeat.yml file at run time.
That mean, for ex: today i am running x set of logging commands, maybe some day i need execbeat to run y set of logging commands. So is there a possibility to add/remove commands to execbeat.yml.
Current workaround i am doing is: have 2 .yml files (one for each x & y set) . based on need just kill current running execbeat & restart execbeat with different .yml & so on.
But it may not work if set changes dynamically, as per the user request.
With Best Regards,
Veera

Hi Veera,
Thanks for the clarification. Currently this is not possible. As a workaround You can start the Execbeat with different configurations in parallel. The beat infrastructure has an option to automatically reload the configuration, but I haven't implemented that for Execbeat. I'm currently traveling but will look into it when back. Of course I'm also happy for any pull request :)

The automatic reloading of the configuration is still in beta. Therefore I would like to wait with the implementation until it becomes a stable feature

Hi Christian,
Thanks for your inputs.
I am new to GoLang, let me see if i could add this feature to execbeat. Currently i am using the workaround of restarting the execbeat with new configuration file.
Again thanks for your inputs.
Veera

Hi @veeragadag , @christiangalsterer
Have submitted a pull request #20 to support this requirement. Do have a check and let me know your suggestions.
Thank You

authors: christiangalsterer manjurajv veeragadag

repo: christiangalsterer/execbeat


text:
Self-contained Dockerfiles

One piece that will help producing the final artifacts is to remove the need to have a local packaging (off container build) with multi stage builds:
https://github.com/christophd/kn-connectors/blob/a919efe7b528594b6126f24d48a993e9c3d81432/timer-source/src/main/docker/Dockerfile.jvm#L21-L27

/close
moved to actual repo: knative-extensions/eventing-integrations

authors: matzew pierDipi

repo: christophd/kn-connectors


text:
[BUG]: Correct package name in Sentence Transformer installation error

The Python package for Sentence Transformer is sentence-transformers (kebab-case), not sentence_transformers (snake_case). Update the error message to use the correct package name.
See https://pypi.org/project/sentence-transformers
Description of changes
Just the name of the package in the error message.

Hey @S1M0N38, thank you for this. Why do you think the snake case will cause an error? Have you seen such instances? My understanding of PEP-8 and PEP-0423 is that pip would allow you to use both dashes or underscore.  So, my conclusion is that this is not a bug.

Yesterday I tried to install sentence_transformers by adding it to the requirements.txt file and then running pip install -r requirements.txt. However, it complained that sentence_transforms could not be found. Then I changed it to sentence-transformers and this time the installation proceeded flawlessly.
I then looked at the Sentence Transformers docs where they show the installation using the kebab-case convention, so I thought pip install sentence_transforms was a bug.
However, now I'm trying to reproduce this issue but pip install sentence_transforms works! It's highly probable that I had misspelled the package name when writing to requirements.txt (but I had double-checked a couple of times before opening this PR).
@tazarov, I also think this is not a bug. Sorry for wasting your time.

repo: chroma-core/chroma


text:
Is it support download file from url?

Hi,
I would like to ask is it current feature support the browser download file behavior?

There is built-in support for download yet, but that's a good feature request

authors: armonia-tech gsouf

repo: chrome-php/headless-chromium-php


text:
Websocket context Timeout

Hi, We are facing the error "websocket url timeout reached" when we reach request limit of 200
Here is the code example:
ctx, cancel := context.WithTimeout(context.TODO(), 30*time.Second)
defer cancel()
secondCtx, cancel := chromedp.NewContext(ctx)

Could you please help me out..

A browser instance consumes many resources and a system has limited resources. You should try to limit the number of browser instances/tabs. Usually, you can use a channel to do that. See https://go.dev/doc/effective_go#channels.
And usually, it's better to use a single browser instance. See https://github.com/chromedp/chromedp/issues/752#issuecomment-1668838777.

Thank you, that did solve my problem.
I do have one more question. How to we limit the system resource while converting html to pdf using PrintToPdf for a single instance.
I can see that resources are used by the following:

Renderer
Utility
Zygote --no-zygote-sandbox
Zygote --no-sandbox
gpu-process

Are all this process are required to convert. If not, can we discard any of it. If yes, how?
Please help with this.

The behavior of the browser is controlled by the switches. You can find a full list of the switches here: https://peter.sh/experiments/chromium-command-line-switches/.
I don't know which combination of the switches will make it consume less resources. Generally, chromedp/headless-shell consumes less resources. You can give it a try.

authors: KThrishul ZekeLu

repo: chromedp/chromedp


text:
Feature Request: GIF animation

I'd love to have this implemented, because I'm not content with staring at a still image when it should be animated.

Please see: https://github.com/chtaylo2/Roku-GooglePhotos/issues/58


text:
OnItemLongClick method is not working in ListView

I have tried to match setOnClickListener and setOnLongClickListener with my adapter class to main fragment through listener. As, I'll perform an action for a long click then onClick event is called default. Because, i have set the return value to "false" to perform listener event in my main Fragment. If I'll set return as "true" in longClick event then listener is not performed.
How can i solve this problem?

Apply the click listener on main child for now.

authors: sagarsabhadiya shahzeb-whizpool


text:
About problems of  coco train

Thanks for your job!
you first trained the model on MS-COCO and then fine-tuned on VOC0712, are you using coco2017 or coco2014?   SSD author  gives the method of making coco2014 data set,  that need other json file-instances_minival2014.json and instances_valminusminival2014.json.
but I don't find  instances_minival2017.json and instances_valminusminival2017.json，
can you tell me the links of these file?
thanks

I have these json files.

authors: dlyldxwl ujsyehao


text:
Add best practices

Fill out best practices badge for project:
https://bestpractices.coreinfrastructure.org/en

#47

authors: awzhgw caniszczyk

repo: chubaofs/chubaofs


text:
How the scalability problem is (not yet) solved

What can the community do to help this service stay up and operational? Whether technical contributions--some measure of caching, advocacy (or funding) for more capacity, or a deeper exploration of the deployment?

How [may we] attempt to solve the scalability problem?

Secondary question: When does the capacity timer reset? (It's 4am UTC as I post this, so hopefully not midnight UTC, which would imply max daily requests was reached in 4 hours)

The capacity timer resets at 0:00:00 UTC.
This is a generic message, and it is sometimes displayed when some other problems occur (in rare cases, but it is possible).
Probably it was exactly the case on 24 Feb.
At the moment, the data capacity is though on the limit, but almost always (except some days with peak loads) it suffices to handle the requests.
Thank you for reaching me out, and ping me again if the service will not available :+1:

authors: chubin mcint


text:
Add nushell agent

Nushell is the shell with built-in HTTP client, identified by nushell user-agent string:
https://github.com/nushell/nushell/blob/19d732f313c4def195ce11474b165d75657e96cb/crates/nu-command/src/network/http/client.rs#L38C22-L38C29

@weirdan Bruce, please update your branch from master, and let's merge it.

@chubin done. The changes from cmd/srv.go were moved to internal/processor/processor.go

authors: chubin weirdan


text:
🛑 Ali Inspector 2 is down

In 0da1bbb, Ali Inspector 2 (https://aliinspector.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 衣联 is back up in ed4becc after .

repo: chwang-team/status-hao


text:
8.8.7 - release note tracking

Template Fixes:
N/A
Specification Changes:

Field
Change

presampling_activity
NEW PICKLIST IDs: Certified humane animal husbandry practices [GENEPIO:0100894], Conventional farming practices [GENEPIO:0100895]

specimen_processing
NEW PICKLIST Definition: Samples pooled [OBI:0600016]

geo_loc_name (state/province/region)
NEW PICKLIST IDs: Atlantic region (Canada) [wikidata:Q246972], Central region (Canada) [wikidata:Q1048064], Northern region (Canada) [wikidata:Q764146], Pacific region (Canada) [wikidata:Q122953299], Prairie region (Canada) [wikidata:Q1364746]

environmental_site
NEW PICKLIST IDs: Pigsty [ENVO:03501413], Dairy farm [ENVO:03501416]

animal_or_plant_population
NEW PICKLIST IDs/Definitions: Wildlife [FOODON:00004503], Wild bird [FOODON:00004505]; NEW PICKLIST ID: Seabird [FOODON:00004504]

environmental_material
NEW PICKLIST IDs/Definitions: Dead haul trailer [GENEPIO:0100896], Live haul trailer [GENEPIO:0100897]; NEW PICKLIST IDs: Bulk tank [ENVO:03501379], Nest [ENVO:03501432]

body_product
NEW PICKLIST IDs: Digestive tract substance [GENEPIO:0100898], Caecal content [GENEPIO:0100899], Intestinal content [GENEPIO:0100900], Stomach content [GENEPIO:0100901]

anatomical_part
NEW PICKLIST ID: Fish vent [GENEPIO:0100902]

food_product
NEW PICKLIST ID: Potato [FOODON:03315354]

food_product_properties
NEW PICKLIST IDs: Meat (with bone) [FOODON:02010116], Meat (with skin) [FOODON:02010111]

food_product_production_stream
NEW FIELD changes: production_stream label changed to food_product_production_stream; slight adjustments to definition; updated example; REMOVED PICKLIST VALUES: Food animal production stream [FOODON:03000450], Food product production stream [FOODON:03000457]; NEW PICKLIST IDs: Beef cattle production stream [FOODON:03000452], Broiler chicken production stream [FOODON:03000455], Dairy cattle production stream [FOODON:03000453], Layer chicken production stream [FOODON:03000456], Egg production stream [FOODON:03000458], Meat production stream [FOODON:03000460], Veal meat production stream [FOODON:03000461], Milk production stream [FOODON:03000459]

host (common name)
NEW PICKLIST ID: Seabird [FOODON:00004504]

Version Tracking:
Excel Template, Reference Guides, Curation SOP
x = 8 = Field relabeled
y = 8 = New value/picklist IDs
z = 7 = New definitions
New Term SOP N/A unless indicated.
Template To-Dos

[ ] Update IDs

[ ] Excel Template
[x] DH Template

[ ] Update production_stream -> food_product_production_stream field label

[ ] Excel Template
[x] DH Template

Update issue request protocol
Approved in workgroup meeting 2023-10-17.

[ ] Convert issue templates to issue forms

[x] Specification - Change Field Request
[ ] Specification - Change Term Request
[ ] Specification - New Term Request (Bulk)
[ ] Specification - New Term Request

[ ] Update protocol document images and text to accommodate changes.


text:
Connection issues when using VIPs

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
We are running Typhoon on bare metal. Since a couple of weeks cilium is the default CNI provider. We saw significant performance gains since we switched from calico.
But there seems to be an issue, when using VIPs. We are running keepalived and when we access services over VIPs, the connection is very slow. Sometimes we get no response. But then again it works without issues for a couple of minutes. At the same time accessing the services using node IP works always very fast and without issues.
cilium monitor shows a lot of TCP RST:
-> overlay flow 0x70a70309 , identity remote-node->unknown state new ifindex cilium_vxlan orig-ip 0.0.0.0: 10.10.224.27:41802 -> 10.2.0.50:3000 tcp SYN
-> overlay flow 0x70a70309 , identity remote-node->unknown state new ifindex cilium_vxlan orig-ip 0.0.0.0: 10.10.224.27:41802 -> 10.2.0.50:3000 tcp ACK
-> overlay flow 0x70a70309 , identity remote-node->unknown state new ifindex cilium_vxlan orig-ip 0.0.0.0: 10.10.224.27:41802 -> 10.2.0.50:3000 tcp ACK
-> overlay flow 0x0 , identity remote-node->unknown state new ifindex cilium_vxlan orig-ip 0.0.0.0: 10.10.224.27:41802 -> 10.2.0.50:60564 tcp RST
-> overlay flow 0x0 , identity remote-node->unknown state new ifindex cilium_vxlan orig-ip 0.0.0.0: 10.10.224.27:41802 -> 10.2.0.50:60564 tcp RST
-> overlay flow 0x0 , identity remote-node->unknown state new ifindex cilium_vxlan orig-ip 0.0.0.0: 10.10.224.27:41802 -> 10.2.0.50:60564 tcp RST
-> overlay flow 0x70a70309 , identity remote-node->unknown state new ifindex cilium_vxlan orig-ip 0.0.0.0: 10.10.224.27:41802 -> 10.2.0.50:3000 tcp ACK
-> overlay flow 0x0 , identity remote-node->unknown state new ifindex cilium_vxlan orig-ip 0.0.0.0: 10.10.224.27:41802 -> 10.2.0.50:60564 tcp RST

10.10.224.27 is the keepalived MASTER
10.2.0.50 is the cluster IP of the service
10.10.224.8 is the VIP (in the tcpdump file)

In the tcpdump taken on the client side, we see a lot of TCP retransmissions:
10.10.224.8.pcap.zip
Cilium Version
Client: 1.11.2 17b0dbd 2022-02-23T13:09:05-08:00 go version go1.17.7 linux/amd64
Daemon: 1.11.2 17b0dbd 2022-02-23T13:09:05-08:00 go version go1.17.7 linux/amd64

Kernel Version
Linux 5.15.17-200.fc35.x86_64 #1 SMP Thu Jan 27 16:29:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Kubernetes Version
v1.23.4

Sysdump
No response
Relevant log output
No response
Anything else?
cilium status
KVStore:                Ok   Disabled
Kubernetes:             Ok   1.23 (v1.23.4) [linux/amd64]
Kubernetes APIs:        ["cilium/v2::CiliumClusterwideNetworkPolicy", "cilium/v2::CiliumEndpoint", "cilium/v2::CiliumNetworkPolicy", "cilium/v2::CiliumNode", "core/v1::Namespace", "core/v1::Node", "core/v1::Pods", "core/v1::Service", "discovery/v1::EndpointSlice", "networking.k8s.io/v1::NetworkPolicy"]
KubeProxyReplacement:   Probe   [team0 10.10.224.27 (Direct Routing)]
Host firewall:          Disabled
Cilium:                 Ok   1.11.2 (v1.11.2-17b0dbd)
NodeMonitor:            Listening for events on 32 CPUs with 64x4096 of shared memory
Cilium health daemon:   Ok
IPAM:                   IPv4: 11/254 allocated from 10.2.11.0/24,
BandwidthManager:       Disabled
Host Routing:           BPF
Masquerading:           BPF   [team0]   10.2.11.0/24 [IPv4: Enabled, IPv6: Disabled]
Controller Status:      65/65 healthy
Proxy Status:           OK, ip 10.2.11.175, 0 redirects active on ports 10000-20000
Hubble:                 Disabled
Encryption:             Disabled
Cluster health:         14/14 reachable   (2022-03-18T18:19:27Z)

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@wkruse can you get a tcpdump and a sysdump of both source and destination nodes? thanks

10.10.224.27 is the keepalived MASTER
10.10.224.8 is the VIP, that is claimed by the keepalived MASTER
The HTTPS request to https://10.10.224.8:30901 was made (the first 2x times the connection could not be established, after that it worked 1x)

(ip.addr == 10.10.224.8 or ip.addr == 10.2.0.50) and tcp
10.10.224.27-filtered.pcap.zip

10.10.224.24 is the node IP of the service
10.2.0.50 is the cluster IP of the service

ip.addr == 10.2.0.50 and tcp
10.10.224.24-filtered.pcap.zip
I've filtered the dumps, as it is difficult to anonymize.

10.2.11.175 is the Cilium IP on the node 10.10.224.27
10.2.0.193 is the Cilium IP on the node 10.10.224.24

Running cilium monitor --type drop on the node 10.10.224.27 we see regularly:
xx drop (Unsupported protocol for NAT masquerade) flow 0x0 to endpoint 0, , identity unknown->unknown: 10.2.11.175 -> 10.2.0.193 Redirect(Host)

An additional info, we have on each node two active NICs and use teaming with active backup.
id=team0
type=team
interface-name=team0

[team]
config={"hwaddr": "xxx","runner": {"name": "activebackup"}, "link_watch": {"name": "ethtool"}}

[ipv4]
method=manual
addresses=10.10.224.27/24
gateway=10.10.224.254
dns=xxx

ip addr show team0
6: team0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether xxx brd ff:ff:ff:ff:ff:ff
    inet 10.10.224.27/24 brd 10.10.224.255 scope global noprefixroute team0
       valid_lft forever preferred_lft forever
    inet 10.10.224.6/32 scope global team0
       valid_lft forever preferred_lft forever
    inet 10.10.224.7/32 scope global team0
       valid_lft forever preferred_lft forever
    inet 10.10.224.8/32 scope global team0
       valid_lft forever preferred_lft forever
    inet 10.10.224.9/32 scope global team0
       valid_lft forever preferred_lft forever
    inet 10.10.224.214/32 scope global team0
       valid_lft forever preferred_lft forever
    inet6 fe80::62a5:516a:32e6:fefd/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

Besides the 10.10.224.27 all the others are VIPs.

We are running Fedora Linux 35.20220116.3.0 (CoreOS) (https://getfedora.org/en/coreos) which doesn't have sysdump. What kind of information, that sysdump provides, would be helpful?

Cilium config used in Typhoon: https://github.com/poseidon/terraform-render-bootstrap/tree/master/resources/cilium

@aanm: We have upgraded to 1.11.4 and executed cilium bpf ct flush global and cilium bpf nat flush on every node. The issue still persists. We have also provisioned a new test cluster, where we also see the issue. The connections are stuttering (every a couple of minutes it works and when again very slow or connection refused), when using VIPs. Direct connections (using node IPs) work without problems. When the connections are stuttering, we see a lot of TCP RST from the node with VIP to the service.
I was able to run pwru on the keepalived MASTER.
The new cluster IP of the service is 10.2.10.98 (was 10.2.0.50).
pwru --filter-dst-ip=10.2.10.98 --filter-proto=tcp --output-tuple > pwru-10.2.10.98.txt

pwru-10.2.10.98.txt.zip

ote-node->unknown state new ifindex cilium_vxlan orig-ip 0.0.0.0: 10.10.224.27:41802 -> 10.2.0.50:3000 tcp SYN
-> overlay flow 0x70a70309 , identity remote-node->unknown state new ifindex cilium_vxlan orig-ip 0.0.0.0: 10.10.224.27:41802 -> 10.2.0.50:3000 tcp ACK
-> overlay flow 0x70a70309 , identity remote-node->unknown state new ifindex cilium_vxlan orig-ip 0.0.0.0: 10.10.224.27:41802 -> 10.2.0.50:3000 tcp ACK
-> overlay flow 0x0 , identity remote-node->unknown state new ifindex cilium_vxlan orig-ip 0.0.0.0: 10.10.224.27:41802 -> 10.2.0.50:60564 tcp RST

TCP RSTs are coming from the keepalived master. Anything stands out in the logs? In any case, cilium datpath doesn't initiate any RSTs.

10.2.11.175 is the Cilium IP on the node 10.10.224.27
10.2.0.193 is the Cilium IP on the node 10.10.224.24

Running cilium monitor --type drop on the node 10.10.224.27 we see regularly:

What do you mean Cilium IP? Is it the IP address assigned to cilium_host device? Also, I'm a bit confused about the network path. Client is connecting to a Kubernetes service with clusterIP via a VIP?

@aditighag: Maybe I am missing something, but I do not see anything, that stands out in the logs.
This is running journalctl -f --no-hostname on the keepalived master during stuttering connection:
Apr 25 20:35:10 audit: PROCTITLE proctitle=69707461626C65732D726573746F7265002D770035002D5700313030303030002D2D6E6F666C757368002D2D636F756E74657273
Apr 25 20:35:10 audit[2370403]: NETFILTER_CFG table=filter family=2 entries=37 op=xt_replace pid=2370403 subj=system_u:system_r:spc_t:s0 comm="iptables-restor"
Apr 25 20:35:10 kernel: audit: type=1327 audit(1650911710.083:701333): proctitle=69707461626C65732D726573746F7265002D770035002D5700313030303030002D2D6E6F666C757368002D2D636F756E74657273
Apr 25 20:35:10 kernel: audit: type=1325 audit(1650911710.084:701334): table=filter family=2 entries=37 op=xt_replace pid=2370403 subj=system_u:system_r:spc_t:s0 comm="iptables-restor"
Apr 25 20:35:10 audit[2370403]: SYSCALL arch=c000003e syscall=54 success=yes exit=0 a0=4 a1=0 a2=40 a3=55a7d44955d0 items=0 ppid=11266 pid=2370403 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables-restor" exe="/usr/sbin/xtables-legacy-multi" subj=system_u:system_r:spc_t:s0 key=(null)
Apr 25 20:35:10 kernel: audit: type=1300 audit(1650911710.084:701334): arch=c000003e syscall=54 success=yes exit=0 a0=4 a1=0 a2=40 a3=55a7d44955d0 items=0 ppid=11266 pid=2370403 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables-restor" exe="/usr/sbin/xtables-legacy-multi" subj=system_u:system_r:spc_t:s0 key=(null)
Apr 25 20:35:10 audit: PROCTITLE proctitle=69707461626C65732D726573746F7265002D770035002D5700313030303030002D2D6E6F666C757368002D2D636F756E74657273
Apr 25 20:35:10 kernel: audit: type=1327 audit(1650911710.084:701334): proctitle=69707461626C65732D726573746F7265002D770035002D5700313030303030002D2D6E6F666C757368002D2D636F756E74657273
Apr 25 20:35:19 audit[2370740]: NETFILTER_CFG table=nat family=10 entries=29 op=xt_replace pid=2370740 subj=system_u:system_r:spc_t:s0 comm="ip6tables-resto"
Apr 25 20:35:19 kernel: audit: type=1325 audit(1650911719.233:701335): table=nat family=10 entries=29 op=xt_replace pid=2370740 subj=system_u:system_r:spc_t:s0 comm="ip6tables-resto"
Apr 25 20:35:19 kernel: audit: type=1300 audit(1650911719.233:701335): arch=c000003e syscall=54 success=yes exit=0 a0=4 a1=29 a2=40 a3=55a0299d6d60 items=0 ppid=11266 pid=2370740 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="ip6tables-resto" exe="/usr/sbin/xtables-legacy-multi" subj=system_u:system_r:spc_t:s0 key=(null)
Apr 25 20:35:19 audit[2370740]: SYSCALL arch=c000003e syscall=54 success=yes exit=0 a0=4 a1=29 a2=40 a3=55a0299d6d60 items=0 ppid=11266 pid=2370740 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="ip6tables-resto" exe="/usr/sbin/xtables-legacy-multi" subj=system_u:system_r:spc_t:s0 key=(null)
Apr 25 20:35:19 audit: PROCTITLE proctitle=6970367461626C65732D726573746F7265002D770035002D5700313030303030002D2D6E6F666C757368002D2D636F756E74657273
Apr 25 20:35:19 kernel: audit: type=1327 audit(1650911719.233:701335): proctitle=6970367461626C65732D726573746F7265002D770035002D5700313030303030002D2D6E6F666C757368002D2D636F756E74657273
Apr 25 20:35:19 kernel: audit: type=1325 audit(1650911719.233:701336): table=filter family=10 entries=13 op=xt_replace pid=2370740 subj=system_u:system_r:spc_t:s0 comm="ip6tables-resto"
Apr 25 20:35:19 audit[2370740]: NETFILTER_CFG table=filter family=10 entries=13 op=xt_replace pid=2370740 subj=system_u:system_r:spc_t:s0 comm="ip6tables-resto"
Apr 25 20:35:19 audit[2370740]: SYSCALL arch=c000003e syscall=54 success=yes exit=0 a0=4 a1=29 a2=40 a3=55a0299d8ef0 items=0 ppid=11266 pid=2370740 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="ip6tables-resto" exe="/usr/sbin/xtables-legacy-multi" subj=system_u:system_r:spc_t:s0 key=(null)
Apr 25 20:35:19 kernel: audit: type=1300 audit(1650911719.233:701336): arch=c000003e syscall=54 success=yes exit=0 a0=4 a1=29 a2=40 a3=55a0299d8ef0 items=0 ppid=11266 pid=2370740 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="ip6tables-resto" exe="/usr/sbin/xtables-legacy-multi" subj=system_u:system_r:spc_t:s0 key=(null)
Apr 25 20:35:19 audit: PROCTITLE proctitle=6970367461626C65732D726573746F7265002D770035002D5700313030303030002D2D6E6F666C757368002D2D636F756E74657273
Apr 25 20:35:19 kernel: audit: type=1327 audit(1650911719.233:701336): proctitle=6970367461626C65732D726573746F7265002D770035002D5700313030303030002D2D6E6F666C757368002D2D636F756E74657273

The service (Grafana) was was logging (probably due to TCP RST):
server.go:3160: http: TLS handshake error from 10.10.224.27:32813: read tcp 10.2.10.98:3000->10.10.224.27:32813: read: connection reset by peer
server.go:3160: http: TLS handshake error from 10.10.224.27:61956: read tcp 10.2.10.98:3000->10.10.224.27:61956: read: connection reset by peer
server.go:3160: http: TLS handshake error from 10.10.224.27:36087: read tcp 10.2.10.98:3000->10.10.224.27:36087: read: connection reset by peer

When running the same setup with Calico, we don't see any issues.

What do you mean Cilium IP? Is it the IP address assigned to cilium_host device?

Exactly, the IP from the annotation io.cilium.network.ipv4-cilium-host.

Client is connecting to a Kubernetes service with clusterIP via a VIP?

Correct. We have a couple of services, that are exposed outside of the Kubernetes cluster. The corresponding DNS entries resolve to the VIPs. The Kubernetes services are using NodePort. The client is connecting to the well-known port.

SELinux was a red herring. When keepalived master and the service are on the same node, we have no issues. When there is a network hop in-between, we have the stuttering connection.

After upgrading to Fedora CoreOS 35.20220424.3.0 with kernel 5.17.4, we cannot reproduce it anymore. We still don't know the root cause, but at least the VIPs are working without stuttering anymore.

authors: aanm aditighag wkruse

repo: cilium/cilium


text:
Geneve DSR load balancer mode does not work

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I just made a new Node IPAM load balancer using Geneve in DSR mode as advertised in the documentation. I noticed that if I have externalTrafficPolicy: Local, then I won't have any incoming traffic at all, although I think this would be a separate issue.
If I change it to externalTrafficPolicy: Cluster, there is a connection, but the whole connection stuck without any I/O until connection reset.
I'm running Cilium behind a Wireguard connection because my homelab does not have a public IP that can be listened to. So, I made a Wireguard network to my VPS and then I used the CiliumLoadBalancerIPPool to expose the mail server as a load balancer using that public IP from the VPS (plus the Egress policy set to use that VPS to have complete traffic relay), I have even set it up this way correctly:
apiVersion: cilium.io/v2alpha1
kind: CiliumLoadBalancerIPPool
metadata:
  name: vps-ip
spec:
  blocks:
    - cidr: 206.XXX.YYY.ZZZ/32

And if the load balancer is in SNAT mode, I can access 206.XXX.YYY.ZZZ to my mail server, but obviously I won't get the correct client IP address rendering the email server in an open relay setup (since it is resolved as internal IP). I'm not sure what to do now.
Cilium Version
1.15.6
Kernel Version
Talos Linux 1.6.5
Kubernetes Version
v1.30.0
Regression
No response
Sysdump
No response
Relevant log output
No response
Anything else?
Helm config
kubeProxyReplacement: true
bandwidthManager:
  bbr: true
  enabled: true
bpf:
  masquerade: true
  tproxy: true
cluster:
  name: kubehyper
egressGateway:
  enabled: true
gatewayAPI:
  enabled: false
hubble:
  relay:
    enabled: true
  ui:
    enabled: true
ingressController:
  enabled: false
ipMasqAgent:
  enabled: true
ipv6:
  enabled: false
nodeIPAM:
  enabled: true
sctp:
  enabled: true
tunnelProtocol: geneve
k8sServiceHost: localhost
k8sServicePort: 7445
loadBalancer:
  algorithm: maglev
  dsrDispatch: geneve
  mode: snat # depends, okay with snat, fails with dsr
routingMode: tunnel
operator:
  replicas: 3
securityContext:
  capabilities:
    ciliumAgent: [CHOWN, KILL, NET_ADMIN, NET_RAW, IPC_LOCK, SYS_ADMIN, SYS_RESOURCE, DAC_OVERRIDE, FOWNER, SETGID, SETUID]
    cleanCiliumState: [NET_ADMIN, SYS_ADMIN, SYS_RESOURCE]
cgroup:
  autoMount:
    enabled: false
  hostRoot: /sys/fs/cgroup

Cilium Users Document

[X] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

[X] I agree to follow this project's Code of Conduct

My game server experiment shows that all my servers based on UDP won't have this issue, and the client source IP address is correctly resolved under Geneve DSR mode. It is TCP mode however having the connection stuck for some reason.

"daemon creation failed: BPF masquerading to route source (--enable-masquerade-to-route-source="true") currently not supported with BPF-based masquerading (--enable-bpf-masquerade="true")"
Huh...

I did an IRL check with WireShark, here's the request to LB with DSR

Here's the request to LB with SNAT

SNAT
tcpdump of cilium_geneve on the node that hosted the mail server pod:
18:09:19.369576 IP (tos 0x0, ttl 118, id 44016, offset 0, flags [DF], proto TCP (6), length 52)
    10.243.139.190.62327 > 10.240.9.152.submissions: Flags [S], cksum 0xa96d (correct), seq 1720110851, win 62258, options [mss 536,nop,wscale 8,nop,nop,sackOK], length 0
18:09:19.369628 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52)
    10.240.9.152.submissions > 10.243.139.190.62327: Flags [S.], cksum 0xab5f (incorrect -> 0xc4e0), seq 645902441, ack 1720110852, win 64860, options [mss 1410,nop,nop,sackOK,nop,wscale 7], length 0
18:09:19.387951 IP (tos 0x0, ttl 118, id 44017, offset 0, flags [DF], proto TCP (6), length 40)
    10.243.139.190.62327 > 10.240.9.152.submissions: Flags [.], cksum 0xfedc (correct), seq 1, ack 1, win 1025, length 0
18:09:19.388594 IP (tos 0x0, ttl 118, id 44018, offset 0, flags [DF], proto TCP (6), length 122)
    10.243.139.190.62327 > 10.240.9.152.submissions: Flags [P.], cksum 0xdbf7 (correct), seq 1:83, ack 1, win 1025, length 82
18:09:19.388628 IP (tos 0x0, ttl 64, id 17689, offset 0, flags [DF], proto TCP (6), length 40)
    10.240.9.152.submissions > 10.243.139.190.62327: Flags [.], cksum 0xab53 (incorrect -> 0x0091), seq 1, ack 83, win 507, length 0
18:09:19.400408 IP (tos 0x0, ttl 64, id 17690, offset 0, flags [DF], proto TCP (6), length 40)
    10.240.9.152.submissions > 10.243.139.190.62327: Flags [F.], cksum 0xab53 (incorrect -> 0x0090), seq 1, ack 83, win 507, length 0
18:09:19.414582 IP (tos 0x0, ttl 118, id 44019, offset 0, flags [DF], proto TCP (6), length 40)
    10.243.139.190.62327 > 10.240.9.152.submissions: Flags [.], cksum 0xfe89 (correct), seq 83, ack 2, win 1025, length 0
18:09:19.416129 IP (tos 0x0, ttl 118, id 44020, offset 0, flags [DF], proto TCP (6), length 40)
    10.243.139.190.62327 > 10.240.9.152.submissions: Flags [F.], cksum 0xfe88 (correct), seq 83, ack 2, win 1025, length 0
18:09:19.416171 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 40)
    10.240.9.152.submissions > 10.243.139.190.62327: Flags [.], cksum 0x008f (correct), seq 2, ack 84, win 507, length 0

tcpdump of cilium_geneve on the node that the load balancer is hosted that connects to the target pod:
reading from file -, link-type EN10MB (Ethernet), snapshot length 4096
18:11:27.740698 IP (tos 0x0, ttl 118, id 44021, offset 0, flags [DF], proto TCP (6), length 52)
    10.243.139.190.62787 > 10.240.9.152.submissions: Flags [S], cksum 0x103f (correct), seq 2353545380, win 62258, options [mss 536,nop,wscale 8,nop,nop,sackOK], length 0
18:11:27.746795 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52)
    10.240.9.152.submissions > 10.243.139.190.62787: Flags [S.], cksum 0xa81f (correct), seq 1827794313, ack 2353545381, win 64860, options [mss 1410,nop,nop,sackOK,nop,wscale 7], length 0
18:11:27.752287 IP (tos 0x0, ttl 118, id 44022, offset 0, flags [DF], proto TCP (6), length 40)
    10.243.139.190.62787 > 10.240.9.152.submissions: Flags [.], cksum 0xe21b (correct), seq 1, ack 1, win 1025, length 0
18:11:27.753682 IP (tos 0x0, ttl 118, id 44023, offset 0, flags [DF], proto TCP (6), length 122)
    10.243.139.190.62787 > 10.240.9.152.submissions: Flags [P.], cksum 0xbf36 (correct), seq 1:83, ack 1, win 1025, length 82
18:11:27.759755 IP (tos 0x0, ttl 64, id 39092, offset 0, flags [DF], proto TCP (6), length 40)
    10.240.9.152.submissions > 10.243.139.190.62787: Flags [.], cksum 0xe3cf (correct), seq 1, ack 83, win 507, length 0
18:11:27.773097 IP (tos 0x0, ttl 64, id 39093, offset 0, flags [DF], proto TCP (6), length 40)
    10.240.9.152.submissions > 10.243.139.190.62787: Flags [F.], cksum 0xe3ce (correct), seq 1, ack 83, win 507, length 0
18:11:27.778314 IP (tos 0x0, ttl 118, id 44024, offset 0, flags [DF], proto TCP (6), length 40)
    10.243.139.190.62787 > 10.240.9.152.submissions: Flags [.], cksum 0xe1c8 (correct), seq 83, ack 2, win 1025, length 0
18:11:27.779591 IP (tos 0x0, ttl 118, id 44025, offset 0, flags [DF], proto TCP (6), length 40)
    10.243.139.190.62787 > 10.240.9.152.submissions: Flags [F.], cksum 0xe1c7 (correct), seq 83, ack 2, win 1025, length 0
18:11:27.787552 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 40)
    10.240.9.152.submissions > 10.243.139.190.62787: Flags [.], cksum 0xe3cd (correct), seq 2, ack 84, win 507, length 0

Geneve DSR
tcpdump of cilium_geneve on the node that hosted the mail server pod:
reading from file -, link-type EN10MB (Ethernet), snapshot length 4096
18:18:49.788674 IP (tos 0x0, ttl 119, id 44112, offset 0, flags [DF], proto TCP (6), length 52)
    <MY OWN ISP IP>.ctinets.com.61579 > 10.240.9.152.submissions: Flags [S], cksum 0xf8dd (correct), seq 3162704892, win 62258, options [mss 536,nop,wscale 8,nop,nop,sackOK], length 0

tcpdump of cilium_geneve on the node that the load balancer is hosted that connects to the target pod:
reading from file -, link-type EN10MB (Ethernet), snapshot length 4096
18:18:49.755979 IP (tos 0x0, ttl 119, id 44112, offset 0, flags [DF], proto TCP (6), length 52)
    <MY OWN ISP IP>.ctinets.com.61579 > 10.240.9.152.submissions: Flags [S], cksum 0xf8dd (correct), seq 3162704892, win 62258, options [mss 536,nop,wscale 8,nop,nop,sackOK], length 0

Looks like there is no respond...?

Is the MTU really correct for TCP though...

There's more, I have checked on the host interface of the node that hosted the pod (this time a game server on port 25565), here's what I got:
reading from file -, link-type EN10MB (Ethernet), snapshot length 4096
19:17:58.928626 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.58468: Flags [S.], cksum 0x28da (correct), seq 440089612, ack 4104243680, win 64308, options [mss 1410,sackOK,TS val 110442570 ecr 1520752668,nop,wscale 7], length 0
19:18:02.796539 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 48)
    <Load Balancer Server IP>.25565 > 51.75.66.201.1001: Flags [S.], cksum 0x9925 (correct), seq 2743871116, ack 2717961258, win 64860, options [mss 1410,nop,nop,sackOK], length 0
19:18:07.010743 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.58468: Flags [S.], cksum 0x0948 (correct), seq 440089612, ack 4104243680, win 64308, options [mss 1410,sackOK,TS val 110450652 ecr 1520752668,nop,wscale 7], length 0
19:18:08.908628 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 48)
    <Load Balancer Server IP>.25565 > 51.75.66.201.1001: Flags [S.], cksum 0x9925 (correct), seq 2743871116, ack 2717961258, win 64860, options [mss 1410,nop,nop,sackOK], length 0
19:18:13.218923 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.38992: Flags [S.], cksum 0xcc56 (correct), seq 708622976, ack 4013035055, win 64308, options [mss 1410,sackOK,TS val 110456860 ecr 1520794508,nop,wscale 7], length 0
19:18:14.224595 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.38992: Flags [S.], cksum 0xc868 (correct), seq 708622976, ack 4013035055, win 64308, options [mss 1410,sackOK,TS val 110457866 ecr 1520794508,nop,wscale 7], length 0
19:18:16.294105 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.38992: Flags [S.], cksum 0xc053 (correct), seq 708622976, ack 4013035055, win 64308, options [mss 1410,sackOK,TS val 110459935 ecr 1520794508,nop,wscale 7], length 0
19:18:17.100594 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 48)
    <Load Balancer Server IP>.25565 > 51.75.66.201.1001: Flags [S.], cksum 0x9925 (correct), seq 2743871116, ack 2717961258, win 64860, options [mss 1410,nop,nop,sackOK], length 0
19:18:17.313813 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.38992: Flags [S.], cksum 0xbc57 (correct), seq 708622976, ack 4013035055, win 64308, options [mss 1410,sackOK,TS val 110460955 ecr 1520794508,nop,wscale 7], length 0
19:18:18.337976 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.38992: Flags [S.], cksum 0xb857 (correct), seq 708622976, ack 4013035055, win 64308, options [mss 1410,sackOK,TS val 110461979 ecr 1520794508,nop,wscale 7], length 0
19:18:20.353849 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.38992: Flags [S.], cksum 0xb077 (correct), seq 708622976, ack 4013035055, win 64308, options [mss 1410,sackOK,TS val 110463995 ecr 1520794508,nop,wscale 7], length 0
19:18:22.380556 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.38992: Flags [S.], cksum 0xa88c (correct), seq 708622976, ack 4013035055, win 64308, options [mss 1410,sackOK,TS val 110466022 ecr 1520794508,nop,wscale 7], length 0
19:18:23.244612 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.58468: Flags [S.], cksum 0xc9dd (correct), seq 440089612, ack 4104243680, win 64308, options [mss 1410,sackOK,TS val 110466886 ecr 1520752668,nop,wscale 7], length 0
19:18:24.418069 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.38992: Flags [S.], cksum 0xa097 (correct), seq 708622976, ack 4013035055, win 64308, options [mss 1410,sackOK,TS val 110468059 ecr 1520794508,nop,wscale 7], length 0

This is pcaped from the load balancer server:
reading from file -, link-type EN10MB (Ethernet), snapshot length 4096
19:18:01.783870 IP (tos 0x0, ttl 46, id 1, offset 0, flags [DF], proto TCP (6), length 48)
    51.75.66.201.1001 > <Load Balancer Server IP>.25565: Flags [S], cksum 0xe079 (correct), seq 2717961257, win 32768, options [mss 1460,nop,nop,sackOK], length 0
19:18:07.007615 IP (tos 0x0, ttl 55, id 42618, offset 0, flags [DF], proto TCP (6), length 60)
    <Third Party Client IP>.58468 > <Load Balancer Server IP>.25565: Flags [S], cksum 0x32f3 (correct), seq 4104243679, win 64240, options [mss 1460,sackOK,TS val 1520788300 ecr 0,nop,wscale 7], length 0
19:18:14.238911 IP (tos 0x0, ttl 55, id 5520, offset 0, flags [DF], proto TCP (6), length 60)
    <Third Party Client IP>.38992 > <Load Balancer Server IP>.25565: Flags [S], cksum 0x23e8 (correct), seq 4013035054, win 64240, options [mss 1460,sackOK,TS val 1520795532 ecr 0,nop,wscale 7], length 0
19:18:17.310808 IP (tos 0x0, ttl 55, id 5523, offset 0, flags [DF], proto TCP (6), length 60)
    <Third Party Client IP>.38992 > <Load Balancer Server IP>.25565: Flags [S], cksum 0x17e8 (correct), seq 4013035054, win 64240, options [mss 1460,sackOK,TS val 1520798604 ecr 0,nop,wscale 7], length 0
19:18:18.334903 IP (tos 0x0, ttl 55, id 5524, offset 0, flags [DF], proto TCP (6), length 60)
    <Third Party Client IP>.38992 > <Load Balancer Server IP>.25565: Flags [S], cksum 0x13e8 (correct), seq 4013035054, win 64240, options [mss 1460,sackOK,TS val 1520799628 ecr 0,nop,wscale 7], length 0
19:18:24.414988 IP (tos 0x0, ttl 55, id 5526, offset 0, flags [DF], proto TCP (6), length 60)
    <Third Party Client IP>.38992 > <Load Balancer Server IP>.25565: Flags [S], cksum 0xfc27 (correct), seq 4013035054, win 64240, options [mss 1460,sackOK,TS val 1520805708 ecr 0,nop,wscale 7], length 0
19:18:32.607119 IP (tos 0x0, ttl 55, id 5527, offset 0, flags [DF], proto TCP (6), length 60)
    <Third Party Client IP>.38992 > <Load Balancer Server IP>.25565: Flags [S], cksum 0xdc27 (correct), seq 4013035054, win 64240, options [mss 1460,sackOK,TS val 1520813900 ecr 0,nop,wscale 7], length 0

I ran curl <Load Balancer IP>:25565 -v on the third-party client that has direct IP rather than masqueraded behind a home router.
Please ignore 51.75.66.201

This is looking sus:
root@backup:~# tcpdump -vvvnnn '(src <Homelab Network IP> or dst <Homelab Network IP> or src <Load Balancer Server IP> or dst <Load Balancer Server IP>) and not (port 22 or port 8007 or port 3260)'
tcpdump: listening on enp1s0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
20:10:16.352980 IP (tos 0x0, ttl 64, id 25731, offset 0, flags [DF], proto TCP (6), length 60)
    <Third Party Client IP>.59984 > <Load Balancer Server IP>.25565: Flags [S], cksum 0x5405 (incorrect -> 0x8d20), seq 1162860748, win 64240, options [mss 1460,sackOK,TS val 746509135 ecr 0,nop,wscale 7], length 0
20:10:17.313553 IP (tos 0x0, ttl 64, id 55941, offset 0, flags [DF], proto TCP (6), length 60)
    <Third Party Client IP>.33338 > <Load Balancer Server IP>.25565: Flags [S], cksum 0x5405 (incorrect -> 0xf130), seq 1755166148, win 64240, options [mss 1460,sackOK,TS val 746510095 ecr 0,nop,wscale 7], length 0
20:10:18.336970 IP (tos 0x0, ttl 64, id 55942, offset 0, flags [DF], proto TCP (6), length 60)
    <Third Party Client IP>.33338 > <Load Balancer Server IP>.25565: Flags [S], cksum 0x5405 (incorrect -> 0xed30), seq 1755166148, win 64240, options [mss 1460,sackOK,TS val 746511119 ecr 0,nop,wscale 7], length 0
20:10:19.360961 IP (tos 0x0, ttl 64, id 55943, offset 0, flags [DF], proto TCP (6), length 60)
    <Third Party Client IP>.33338 > <Load Balancer Server IP>.25565: Flags [S], cksum 0x5405 (incorrect -> 0xe930), seq 1755166148, win 64240, options [mss 1460,sackOK,TS val 746512143 ecr 0,nop,wscale 7], length 0
20:10:20.384963 IP (tos 0x0, ttl 64, id 55944, offset 0, flags [DF], proto TCP (6), length 60)
    <Third Party Client IP>.33338 > <Load Balancer Server IP>.25565: Flags [S], cksum 0x5405 (incorrect -> 0xe530), seq 1755166148, win 64240, options [mss 1460,sackOK,TS val 746513167 ecr 0,nop,wscale 7], length 0
20:10:21.408969 IP (tos 0x0, ttl 64, id 55945, offset 0, flags [DF], proto TCP (6), length 60)
    <Third Party Client IP>.33338 > <Load Balancer Server IP>.25565: Flags [S], cksum 0x5405 (incorrect -> 0xe130), seq 1755166148, win 64240, options [mss 1460,sackOK,TS val 746514191 ecr 0,nop,wscale 7], length 0
20:10:22.432967 IP (tos 0x0, ttl 64, id 55946, offset 0, flags [DF], proto TCP (6), length 60)
    <Third Party Client IP>.33338 > <Load Balancer Server IP>.25565: Flags [S], cksum 0x5405 (incorrect -> 0xdd30), seq 1755166148, win 64240, options [mss 1460,sackOK,TS val 746515215 ecr 0,nop,wscale 7], length 0
20:10:24.448970 IP (tos 0x0, ttl 64, id 55947, offset 0, flags [DF], proto TCP (6), length 60)
    <Third Party Client IP>.33338 > <Load Balancer Server IP>.25565: Flags [S], cksum 0x5405 (incorrect -> 0xd550), seq 1755166148, win 64240, options [mss 1460,sackOK,TS val 746517231 ecr 0,nop,wscale 7], length 0
20:10:28.640965 IP (tos 0x0, ttl 64, id 55948, offset 0, flags [DF], proto TCP (6), length 60)
    <Third Party Client IP>.33338 > <Load Balancer Server IP>.25565: Flags [S], cksum 0x5405 (incorrect -> 0xc4f0), seq 1755166148, win 64240, options [mss 1460,sackOK,TS val 746521423 ecr 0,nop,wscale 7], length 0
20:10:36.832978 IP (tos 0x0, ttl 64, id 55949, offset 0, flags [DF], proto TCP (6), length 60)
    <Third Party Client IP>.33338 > <Load Balancer Server IP>.25565: Flags [S], cksum 0x5405 (incorrect -> 0xa4f0), seq 1755166148, win 64240, options [mss 1460,sackOK,TS val 746529615 ecr 0,nop,wscale 7], length 0

This is on my home router:
20:10:17.319418 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.33338: Flags [S.], cksum 0x23b0 (correct), seq 2412780328, ack 1755166149, win 64308, options [mss 1410,sackOK,TS val 113580960 ecr 746510095,nop,wscale 7], length 0
20:10:18.342334 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.33338: Flags [S.], cksum 0x1fb1 (correct), seq 2412780328, ack 1755166149, win 64308, options [mss 1410,sackOK,TS val 113581983 ecr 746510095,nop,wscale 7], length 0
20:10:19.366294 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.33338: Flags [S.], cksum 0x1bb1 (correct), seq 2412780328, ack 1755166149, win 64308, options [mss 1410,sackOK,TS val 113583007 ecr 746510095,nop,wscale 7], length 0
20:10:20.393482 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.33338: Flags [S.], cksum 0x17ae (correct), seq 2412780328, ack 1755166149, win 64308, options [mss 1410,sackOK,TS val 113584034 ecr 746510095,nop,wscale 7], length 0
20:10:21.414591 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.33338: Flags [S.], cksum 0x13b1 (correct), seq 2412780328, ack 1755166149, win 64308, options [mss 1410,sackOK,TS val 113585055 ecr 746510095,nop,wscale 7], length 0
20:10:22.438581 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.33338: Flags [S.], cksum 0x0fb0 (correct), seq 2412780328, ack 1755166149, win 64308, options [mss 1410,sackOK,TS val 113586080 ecr 746510095,nop,wscale 7], length 0
20:10:23.472810 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <Load Balancer Server IP>.25565 > <Third Party Client IP>.33338: Flags [S.], cksum 0x0ba6 (correct), seq 2412780328, ack 1755166149, win 64308, options [mss 1410,sackOK,TS val 113587114 ecr 746510095,nop,wscale 7], length 0

But I probably think I got the reason why I'm seeing this, but I'm not closing this issue until it is confirmed...

I would like to keep this open since DSR does work with UDP but not TCP which sounds quite strange on a deeper level, since DSR should not work if either case with my homelab setup.
To summarize:

Tunneled Geneve DSR does not work with TCP, since the three-way handshake is not observed to complete at all
Tunneled Geneve DSR does work with UDP, but that's because UDP employs a fire-and-forgot model without handshake. So anyone can send data to the source client IP:port without problem.
Something might be wrong in eBPF datapath for load balancer handling TCP stuff
SNAT obviously works since the endpoint has to go back to the load balancer source, rather than going to the client directly.
It is also possible that your real server IP behind the load balancer, would leak on IP level if you use DSR.
LB in Geneve DSR mode probably works with native routing (?) It shouldn't be working though

https://github.com/cilium/cilium/blob/b0a69f3cbcb1b05bf3eca677b4cabee55b260ec4/bpf/lib/nodeport.h#L2311-L2340
I'm not sure how to attach a breakpoint here...

no stale

No stale