text:
🛑 tt is down

In fbe0092, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 3900 ms

Resolved: tt is back up in 2571c94 after 10 minutes.

repo: chenhaonanniubi/upptime


text:
🛑 tt is down

In 222812a, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 3131 ms

Resolved: tt is back up in 8e75a6f.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 tt is down

In 67e95cd, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 3180 ms

Resolved: tt is back up in 70bfbc2 after 12 minutes.


text:
无法解析链接

不知道是哪里出了问题，别人分享的下载链接。
2.0.0版本的也无法解析，显示这个。

3.0.3版本的也无法解析，点击解析没有反应。

链接提供一下

另外，请确保链接在浏览器上是可以正常打开的

这好像是会员链接，我适配一下

浏览器可以打开 https://xiyoufuman.lanzouf.com/b0172ka8j 提取码：9hxn

同道中人啊，可以用这个当备用，https://www.lanzouf.com/b02c4d88d 密码:zfg
我刚发现的，粗糙但蛮好用的

不知道是哪里出了问题，别人分享的下载链接。
2.0.0版本的也无法解析，显示这个。
3.0.3版本的也无法解析，点击解析没有反应。

搞好了，可以试一下

好了耶( •̀ ω •́ )y    大佬辛苦啦❤b(￣▽￣)d    晚安(￣o￣) . z Z


text:
Too many config files

Including configs for things like flow, vscode, and travis adds a lot of mess to clean up for people who don't use those things. Since this is the react electron repo, I feel like it should be stripped down a little.

Which configs should we get rid of?

Just registering another opinion... I think the flow configs are good because they provide an opinionated best practice, which is what boilerplate is for.
I think the editor-specific configs could either be removed (because everybody uses a different editor, and your choise editor isn't necessarily related to the project ecosystem), or it should be an explicit policy that other editor configs are welcomed and maybe put them in editor_configs/ with a README file in that directory explaining the policy. I use Emacs, but VS Code seems to be an emerging norm in the JS community so it's probably helpful to have a config laying around.
Also, wouldn't removing yarn.lock make it pretty difficult to debug issues people are having with the project? yarn.lock in projects I've worked on is always committed to make sure that people are using the same dependencies without having to continually ask everybody to list which version they have installed locally.
In general my opinion is:

It's not that hard to remove config files, and they rarely get in the way. You're going to have to customize this repo for your project anyways. git rming or editing a few config files you don't find helpful is much easier than being a newbie and not having access to sensible config files. For example, being new to the whole ecosystem it would be very hard to create a Flow config from scratch.
The purpose of boilerplate is to help people get going in an ecosystem quickly.
Example config files, even if they're not setup out of the box the way you'd like, are very helpful as it's difficult to come up with from scratch when you're new to an ecosystem.
Config files are a good opportunity to set opinionated best practices, which is especially useful in boilerplate projects. These best practices reflect norms in a community.

Boilerplate seems like the BEST place for config files. The cost of removing/modifying config to fit your preferences is much lower than the cost of not having ready access to example configs.

I like the idea of an editor_configs and I can appreciate that having sample code makes it easier for a newcomer to get started.

The main yarn.lock is certainly important - the one I was talking about is in the app directory and is empty (there are no dependencies in that directory's package.json)

I would argue that Flow isn't actually a best practice and integrating it so deeply makes this project less flexible. Skype, GitHub, and Slack are all using TypeScript. The problem with enforcing a certain stack is that when any part of it becomes obsolete, the whole project does.

It kind of depends on if this project is supposed to be a pure electron-react boilerplate or if it's a "cool stack" that runs on electron and react. Personally, I was just looking for a clean way to structure an application that uses the two technologies.

Cool, those opinions make sense too.
I'm just curious for my own education, are you using this repo with TypeScript? I've just been using Flow since it was already in this project... but I'm not partial to it. Was it easy to get TypeScript working with this?
Whether this project is best as "cool stack" or "basic stack", I could see a change from Flow to TypeScript being a reasonable opinionated change. Coming from non-JavaScript land, there are already a lot of other opinions built-in (Webpack, ES6, testing framework, Redux).
I'd like to see "cool stack". I'm a Rails fan and have seen the "cool stack" decision go the undesirable way (i.e. CoffeeScript), but overall I like things to be opinionated and bundled (Rails for Ruby) vs. piece-together-your-own-together (i.e. Flask for Python). Just opinions though. Good discussion.

You can find my typescript fork under notable forks in the wiki. It's based on version 13.3 and I'll try to update soon with the latest commits.
Regarding the configs, I kinda like the idea of putting them in a separate folder. But I wouldn't delete them, as they are useful to build upon.

@ManuKle very cool!

In #1686, we moved webpack configs to a configs folder. That drops quite a few files from the home directory.

authors: Ellmen ManuKle aguynamedben amilajack vikr01

repo: chentsulin/electron-react-boilerplate

license: mit

license_source: bigquery


text:
Adds support to Hadoop compression codec.

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Sure I think it's a good idea to add more comments.
It's also a good opportunity to look into other serde package and figure out how/when the APIs are called.

Discussed offline, Added some comments. tested locally it worked well for gzip.

Added links to the source. I'll do an overall testing again before sending this PR to the official repo.

source: gharchive/pull-request

repo: cheqianh/ion-hive-serde


text:
🛑 Chequeo Colectivo is down

In c6bbbc7, Chequeo Colectivo (https://chequeado.com/colectivo) was down:

HTTP code: 502
Response time: 9077 ms

Resolved: Chequeo Colectivo is back up in 5d58f5a.

repo: chequeado/status


text:
Don't create PR if you can't finish them

To avoid too much noise on this repo, don't open PR's if you can't or will finish them. At the moment we have 5 open PR. One of this PR have been inactive for the last 15 days - https://github.com/cherow/cherow/pull/153
We also have two PR - closed now - for string literals and ecmaVersion option. This also make up some noise on the repo.
Just be 100% sure before you open a PR. Also be sure that you get reviewers with knowledge enough to understand your way of thinking and the code flow.
https://github.com/cherow/cherow/pull/175 is my last PR. I will from now on push directly due to lack of reviewers and too keep the repo noise down.
cc / @fkleuver @g-plane @Aladdin-ADD

I really don't recommend to push directly.

I have pushed directly from start. As long as I'm only dealing with src folder there is no issue.

I still recommend to open PR. Once you opened a PR and there are no any reviews in several days, you can merge by yourself.

The issue is that somneone open PR and 1) never finish them or 2) never merge them

authors: KFlash g-plane

repo: cherow/cherow

license: isc


text:
Unable to pick colors in the ColorPicker node.

I can't select any color other than the default color when loading the node. Normally, when I click the mouse cursor on the color, a color palette pops up, and I just need to move the cursor to the image and pick the color. But today, when I click on the color, nothing happens.

I'm having the same problem. Did you solve it? Can someone help me?

The panel does not appear even though my browser settings do not disable pop-ups.

I have the same problem. In an new install, the color pop screen work flawless. After installing custom nodes, it stop working. It's probably an incompatibility with one of them, but wich one...?

authors: Poukpalaova gonu2024 nhathoangfoto


text:
cancelling a template add brings up an error

Hi, just started trying out the plugin, and ran into a curious behaviour.
Whenever I press ESC after selecting a template to add, I get this error:

And this only happens with the add template function, as far as I've noticed.

Thank you! Fixed in the latest version. :)

authors: chhoumann firinael

repo: chhoumann/quickadd


text:
allow to provide a separate key combo for documentation

it seems that for modifier+key combinations, the event triggers with the english key, even if the layout is in another language (at least for me, using english+hebrew layouts). this seems inherent in javascript. while the best solution is for the framework to map the non english characters to their english equivalent when handling key presses, it seems this is tricky (if possible). an alternative is to just allow to pass a key combination that will be used in the documentation. so while binding to alt+t, the documentation will show alt+א

I'm not in control of this, as all hotkey-specific binding is handled by mousetrap.  You may want to open a ticket there

I was suggesting that an optional parameter will be allowed and that will be used for documentation. So I call with both alt+t and alt+א, you pass alt+t to mousetrap and show alt+א in the documentation ('?')

authors: chieffancypants ittayd

repo: chieffancypants/angular-hotkeys


text:
🛑 36kr -实时快讯(newsflashes) is down

In 065b368, 36kr -实时快讯(newsflashes) (https://rssinn.com/36kr/newsflashes) was down:

HTTP code: 404
Response time: 1191 ms

Resolved: 36kr -实时快讯(newsflashes) is back up in 8acdcc3.

repo: chinobing/upptime-rssinn


text:
Removing unused modules from UHDM file + dependencies

I translate SystemVerilog files to UHDM with surelog.
Let us say that I want to create a design with top module MyModule:
>> /usr/local/bin/surelog --version
   VERSION: 1.47
   BUILT  : Jan 24 2023
>> /usr/local/bin/surelog -parse -synth -timescale=1ns/1ps
    -I$(EDIR) -I$(IDIR) +libext+.sv -y $(MDIR) -top MyModule MyModule.sv

In this call, EDIR is a directory with .sv files containing enumerations, IDIR is a directory with .sv files containing interfaces, and MDIR is a directory containing a large collection of SystemVerilog modules in .sv files.
After analysing the .uhdm file it is apparent that it contains all modules in the MDIR directory, whether or not they are instantiated through the top module.

Is it possible to call surelog in such a way that modules which are not used, directly or indirectly, by the top module are removed from the generated .uhdm file? If not, it would be a good idea to include such an option.
Is it possible to call surelog in such a way that it generates a dependency file listing all .sv files used, directly or indirectly by the top module, to create the design? This would be very useful in Makefile flows.

Hello
As far as I understand, Surelog is a tool that will allow you to fill a uhdm database. What you do with the uhdm database is your custom application.
Surelog is able to perform some elaboration. One elaboration step consist to complete the uhdm database with what you want.
using -d uhdm, the tool will dump the complete uhdm tree.
You should be able to observe a difference by adding -noelab,
So to answer your question, you probably  have to write your own application to iterate on only the part of the uhdm data base that interest you.
See:
https://github.com/chipsalliance/Surelog/blob/5fc1993668337fa646adbf1e5e0bd139f2304293/src/hellouhdm.cpp#L103
vs
https://github.com/chipsalliance/Surelog/blob/5fc1993668337fa646adbf1e5e0bd139f2304293/src/hellouhdm.cpp#L150

@StefanoBettelli, can we close this issue? Are you OK with the file suggested above?

Unfortunately I haven't had much time recently to look at it again. However, it seems that this project can hardly be used beyond linting, since there isn't enough documentation, and it is not clear the level of elaboration that is / can be done. There are projects to offload the SystemVerilog fronted of verilator and yosys to Surelog, but so far my efforts at using them consistently in a Makefile flow have failed, due to several shortcomings (not all in Surelog).
For the time being the issue can be closed. I will come back to it if there is any substantial progress.

@StefanoBettelli you really mean a "Makefile" flow or a "CMake" flow?
If you really mean "Makefile" like you have a larger project that uses Makefile and you want to shoehorn Surelog CMake into it,
then it is best to invoke the cmake from the Makefile like in:
https://github.com/chipsalliance/Surelog/blob/efd45b9291cb4aa03c54e9d3d72d90b885571971/Makefile#L23 and not try to convert any of the CMake steps to Makefile
As for the API, the API is the Standard VPI interface (very well documented in the SystemVerilog standard):
Accessed using: https://github.com/chipsalliance/UHDM
Extract of the Standard API for reference: https://github.com/chipsalliance/Surelog/blob/master/third_party/Verilog_Object_Model.pdf

authors: StefanoBettelli Thomasb81 alaindargelas

repo: chipsalliance/Surelog


text:
Different DOM structure for inline/fenced code blocks

With GFM, both inline code blocks and fenced code blocks provide the following DOM structure:

...

Inline code block:
`code`

Fenced codeblock:
```
code
```

I would like to style the inline code block differently with CSS than the fenced code block.
How can I do this? There's no way to target the inline code block.

What options are you using? It should produce

...

for fenced/block codes, and

...>

for inline code. For styling you can select code for inline and pre code for code blocks.

It produces in both cases
...

I'm using default options.

Can you give an example of your code and markdown?

Here is a screenshot. I'm using marked() without any options so it's using default options. As you can see there is no difference between inline code block and a fenced code block.

This is actually correct behaviour in GFM. It's required to have a newline (\n) character after start fence (except you can provide a language extension after start fence)
```\n
Fenced code block\n

becomes

Fenced code block

and

Fenced code block

becomes

Fenced code block
```
The reason is that inline code uses single back ticks so further unescaped back ticks will be ignored in the output.

@fnky Thank you very much. Problem solved. :)

authors: fnky gaui

repo: chjj/marked


text:
Does this theme support HRM?

Thanks for this awesome theme.
Does this theme support HRM or it does full reload on every change?
I always get full reloads making changes to my pages.

Hi @khalidchawtany
At this time it does not support HMR, I did't find a way to implement it.
Thanks Khalid

HRM works for JS and CSS files, but if changes are made to the template files the server needs to reload the page to reflect those changes.
Hope this clarify your question @khalidchawtany.

Thanks that is very nice. I wish it worked for templates too. However, I know that it is almost impossible to implement :(

authors: chkilel khalidchawtany

repo: chkilel/vitewind-theme


text:
dont append confirmDate to native inputs

fixes #742

Coverage remained the same at 87.67% when pulling ae2da50a5d0509b42a89fdf0dec14e3719ba2e03 on webdevan:master into 1f1d629c4708a1e06422dcdbba5acbe0e1f7804e on chmln:master.

authors: coveralls webdevan

repo: chmln/flatpickr


text:
support nginx-1.14.x

try to fix https://github.com/chobits/ngx_http_proxy_connect_module/issues/12

Tested-by: Xiaochen Wang xiaochen
Date: Thu Apr 19 17:57:07 CST 2018
hostname: Xiaochens-MacBook-Pro.local
pwd: /Users/xiaochen/work/github/ngx_http_proxy_connect_module
cases: t/http_proxy_connect.t
git log:

case result:

$ MOD_DYCONF_PATH=/Users/xiaochen/work/github/ngx_http_proxy_connect_module TEST_NGINX_BINARY=/Users/xiaochen/work/github/nginx-1.14.0/objs/nginx prove -v -I /Users/xiaochen/work/github/nginx-tests/lib t/http_proxy_connect.t
t/http_proxy_connect.t ..
DNS server: try to bind server port: 18085
DNS server: daemon pid: 41072
DNS server: working
ok 1 - 200 Connection Established
ok 2 - 200 Connection Established server name
ok 3 - 200 Connection Established server name
ok 4 - 200 Connection Established server name
ok 5 - 200 Connection Established not allowed port
ok 6 - Get method: proxy_pass
ok 7 - Get method: return 200
ok 8 - set remote address
ok 9 - set local address and remote address
ok 10 - $connect_host, $connect_port, $connect_addr
ok 11 - dns resolver fail
ok 12 - skip proxy connect module without rewrite phase enabled
ok 13 - skip proxy connect module without rewrite phase enabled: if/return
DNS server: stop
1..13
ok 14 - no alerts
ok 15 - no sanitizer errors
All 13 subtests passed

Test Summary Report
-------------------
t/http_proxy_connect.t (Wstat: 0 Tests: 15 Failed: 2)
  Failed tests:  14-15
  Parse errors: Plan (1..13) must be at the beginning or end of the TAP output
                Bad plan.  You planned 13 tests but ran 15.
Files=1, Tests=15,  0 wallclock secs ( 0.02 usr  0.01 sys +  0.11 cusr  0.06 csys =  0.20 CPU)
Result: FAIL

Report-generated-by: http://wxc.oss.aliyuncs.com/dtest.sh


text:
(Skype) Changed InnoSetup /SILENT parameter to /VERYSILENT

Description
Using /VERYSILENT instead of /SILENT makes Inno Setup a bit quieter.
Motivation and Context
Users are understandably concerned about "mystery" install windows.
How Has this Been Tested?
Manually downloaded https://endpoint920510.azureedge.net/s4l/s4l/download/win/Skype-8.30.0.50.exe, and ran installer with same parameters as in chocolateyInstall.ps1, except /SILENT was changed to /VERYSILENT. Installation succeeded and no installation windows appeared. Skype still (re)launches after installation.
Types of changes
Minor (largely cosmetic) change
Checklist:

[x ] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[x ] All files are up to date with the latest Contributing Guidelines
[ ] The added/modified package passed install/uninstall in the chocolatey test environment.
[x ] The changes only affect a single package (not including meta package).

:white_check_mark: Package verification completed without issues. PR is now pending human review

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

authors: AppVeyorBot pascalberger regexaurus

repo: chocolatey/chocolatey-coreteampackages


text:
RFP - Croscore fonts

The Chrome OS core fonts, also known as the Croscore fonts, are a collection of three TrueType font families: Arimo (sans-serif), Tinos (serif) and Cousine (monospace). These fonts are metrically compatible with Arial, Times New Roman, and Courier New, the most commonly used fonts on Microsoft Windows operating system, for which they are intended as open-source substitutes.
More info: https://en.wikipedia.org/wiki/Croscore_fonts
Download link: https://gsdview.appspot.com/chromeos-localmirror/distfiles/

Please also supply the home page for these fonts, before we can make this available for maintainers.

Homepage: https://fonts.google.com/
More specificaly: Amiro, Tinos and Cousine.

I MIGHT look into this.
Looks like this is the latest version right? https://gsdview.appspot.com/chromeos-localmirror/distfiles/croscorefonts-1.31.0.tar.bz2

I completely forgot about this.
Done!
https://chocolatey.org/packages/croscorefonts-font

@rogersachan, since you seem appreciative...
https://chocolatey.org/packages/crosextrafonts-caladea-font/2013.02.14
https://chocolatey.org/packages/crosextrafonts-carlito-font/2013.09.20

Thanks so much for this!

authors: AdmiringWorm bcurran3 dimqua rogersachan

repo: chocolatey/chocolatey-package-requests


text:
How can I get installed programs instantly in current cmd window?

Every time I install a program I had to restarted my cmd window. Is there any convenient ways to get them in current cmd window? Simething like 'source file.sh' in unix ?
P.S. - I am using Windows 7

If you are in cmd.exe and not powershell you can type refreshenv

Chocolatey comes with a batch file named the above and will query the registry and reset all of your environment variables.

Perhaps we need more documentation surrounding that.

Is it possible to get RefreshEnv to work in powershell too?
If it cannot, there should be a warning message if RefreshEnv is used in powershell instead of a silent fail.

It's an issue with Windows inability to refresh shells. It doesn't have
anything to do with choco itself. Now that that is it off the way,
refreshenv is a stop gap for choco to keep you from having to close and
reopen your cmd window. Its also mostly undocumented. The recommendation is
that you close and reopen your shell.
You can also do PowerShell if you call &
c:\programdata\chocolatey\chocolateyinstall\helpers\Update-Session.ps1 (the
path may not be exactly right but you get the idea)- it may require
importing the module first and then calling update-session.
On Tuesday, January 27, 2015, Andy Li notifications@github.com wrote:

Is it possible to get RefreshEnv to work in powershell too?
If it cannot, there should be a warning message if RefreshEnv is used in
powershell instead of a silent fail.
—
Reply to this email directly or view it on GitHub
https://github.com/chocolatey/chocolatey/issues/666#issuecomment-71639225
.

--
Rob
"Be passionate in all you do"
http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder

Do you mean Update-SessionEnvironment? I tried adding it to the end of chocolateyInstall.ps1, but it seems to have no effect - the path var is not updated in powershell.

It actually does work but you need to call it separately outside of a choco
call (which starts up and closes a separate posh process).
On Tuesday, January 27, 2015, Andy Li notifications@github.com wrote:

Do you mean Update-SessionEnvironment
https://github.com/chocolatey/chocolatey/wiki/HelpersUpdateSessionEnvironment?
I tried adding it to the end of chocolateyInstall.ps1, but it seems to
have no effect - the path var is not updated in powershell.
—
Reply to this email directly or view it on GitHub
https://github.com/chocolatey/chocolatey/issues/666#issuecomment-71654814
.

--
Rob
"Be passionate in all you do"
http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder

Umm.. I thought the helpers are meant to be called inside chocolateyInstall.ps1...

Yes, they are. But anything they do with respect to environment vars only
lasts during that choco run. Once it comes back to the shell, all child
process changes are gone. It would be an egregious security issue with
Windows if child processes did more than they do to the parent process.
I'm giving you an option for updating your environment variables. Also
undocumented and not supported. Ymmv. Remember, you can just close and
reopen your shell as well.
On Tuesday, January 27, 2015, Andy Li notifications@github.com wrote:

Umm.. I thought the helpers are meant to be called inside
chocolateyInstall.ps1...
—
Reply to this email directly or view it on GitHub
https://github.com/chocolatey/chocolatey/issues/666#issuecomment-71655906
.

--
Rob
"Be passionate in all you do"
http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder

Hi Rob,
I was just able to reproduce it my win 7. First I run "choco install java". It says not found.Running "choco install jdk" also fails as you can see in the screen and after that new blank window appears it  just freezes nothing happens after that.

@ahmedmohiduet does this fail if you switch over to 0.9.9?

I guess I will have to check it again. Will let you know after successful reproduce :)

authors: ahmedmohiduet andyli ferventcoder

repo: chocolatey/chocolatey


text:
[WIP] Compare energy components with antechamber/prmtop route

This is the beginning of a PR to compare energy components with a prmtop route for loading parameters.
Currently, the test fails because the imatinib prmtop seems to lead to very different nonbonded forces:
Energy components:
      NonbondedForce  -203.736379    31.680160 :   235.416539
   HarmonicBondForce     6.160988     6.248384 :     0.087396
  HarmonicAngleForce     5.330822     5.329843 :     0.000980
PeriodicTorsionForce    13.253722     8.783295 :     4.470427
     CMMotionRemover     0.000000     0.000000 :     0.000000
Maximum allowed deviation (0.600000) exceeded.

I'm not sure why this is, but I am investigating.  I also don't know the origin of the chemicals/imatinib/imatinib.prmtop file.
It may be better for me to compare with a prmtop/inpcrd generated on the fly from either the same procedure I am using for generating the residue templates or the intermediate GAFF mol2/frcmod files used in generating the residue templates.

The error is now much smaller:
Energy components:
      NonbondedForce  -203.736307  -206.509692 :     2.773386
   HarmonicBondForce     6.160980     6.248380 :     0.087400
  HarmonicAngleForce     5.330831     5.329848 :     0.000983
PeriodicTorsionForce    13.253717     8.783295 :     4.470422
     CMMotionRemover     0.000000     0.000000 :     0.000000
Maximum allowed deviation (0.600000) exceeded.

Will need to do more debugging but raised the max allowed deviation to 5 for now.

repo: choderalab/openmoltools


text:
Nonequilibrium switching fails with new OpenMM API

I think this is actually an update that needs to be made in openmmtools. The AlchemicalState object is unaware of how to set the global parameter lambda_electrostatics if it's covered by the regular NonbondedForce.
cc: https://github.com/choderalab/openmmtools/issues/359

@pgrinaway This should be resolved using the latest OpenMM 7.3.0 dev build now that https://github.com/pandegroup/openmm/pull/2119 and https://github.com/pandegroup/openmm/pull/2115 have been merged.
OK to close?

@brycestx points out we need to revise things so that we explicitly add the global context parameters to NonbondedForce now that the API has been extended.

Fixed in the OpenMM 7.3.1 bugfix release.

authors: jchodera pgrinaway

repo: choderalab/perses


text:
Mark arm9 as Decompressed, and Change Shiny Value Offset Output to Hex

I'm not sure if I did this right, but hopefully this should only include:

Explicitly marking the arm9 as decompressed
Outputting the Shiny Value offset in hex

Thanks for these changes @digikitty21 ! Merged to main.

repo: choogiesaur/hgss-shiny-modifier


text:
Harden Puppet datatypes

Some of the datatypes are not as strict as they could be. To make the usage safer, the should be hardened.

thank you!

authors: bastelfreak ripienaar

repo: choria-io/puppet-mcollective


text:
minor issue with new ffmpeg stack on .16

Hi,
After upgrading to .16 and trying out the new ffmpeg stack, it seems to work quite well from initial impressions, perhaps loading a bit faster. The one issue I've encountered is when playing back via Kodi's iptv plugin. It would immediately fail without opening the stream. The log showed:
CCurlFile::Open - http://192.168.1.135:8000/stream/channels/1fa17176-a81c-495c-a631-67a375320412.ts Failed with code 500:
Pasting the url into vlc also resulted in failed playback. By changing the .ts to .m3u8 I was able to play back in vlc successfully, so I edited the channels.m3u and changed each .ts instance to .m3u8. This restored my kodi iptv functionality.
I should note that the above is not necessary using the old ffmpeg stack. Thanks again as always!

Any relevant logs on the server side?

Also can you provide a few more details? Like are you using hw accel? If so, which kind?

I was able to reproduce this. Will have a fix today. Thanks for testing!

Sorry I didn't get you the logs earlier, life interrupted me. Thanks for identifying the cause and I'm looking forward to the fix.
Been using the docker vaapi and load times in Kodi are in the ~1-2 second range with the new ffmpeg changes (down a second or so). Every bit as fast as traditional linear tv!

repo: chrisbenincasa/tunarr

license: Zlib


text:
Curses has been removed from Standard Library

Please add runtime dependency to curse ~> 1.0 if Ruby is > 2.1

Thanks for opening the issue. I'll take care of this as soon as I get a chance.

This has been addressed. Thanks again for pointing it out @felipebalbi

Hey, no problem. I'll have a look at how you did it. I knew about adding it to gemspec, but didn't know how to add it conditionally on ruby version :-)

authors: chrisccerami felipebalbi


text:
ValueError: You are tring to use the old GPU back-end.

Hi I use windows 10 to implement the project and it turns out the error below:
ValueError: You are tring to use the old GPU back-end. It was removed from Theano. Use device=cuda*
I tried to follow your link that from error
https://github.com/Theano/Theano/wiki/Converting-to-the-new-gpu-back-end(gpuarray)
and install theano pygpu, but nothing good come out.
I also tried change the Theano variable device = gpu to device = cuda0 and it gives me the error below:
(py3) C:\Users\speed\source\3D-R2N2>python demo.py prediction.obj
WARNING (theano.tensor.blas): Using NumPy C-API based implementation for BLAS functions.
ERROR (theano.gpuarray): pygpu was configured but could not be imported or is too old (version 0.7 or higher required)
NoneType
Downloading a pretrained model
Traceback (most recent call last):
File "demo.py", line 84, in
main()
File "demo.py", line 55, in main
download_model(DEFAULT_WEIGHTS)
File "demo.py", line 34, in download_model
'--create-dirs', '-o', fn])
File "C:\Users\speed\AppData\Local\Programs\Python\Python35\Lib\subprocess.py", line 557, in call
with Popen(*popenargs, **kwargs) as p:
File "C:\Users\speed\AppData\Local\Programs\Python\Python35\Lib\subprocess.py", line 947, in init
restore_signals, start_new_session)
File "C:\Users\speed\AppData\Local\Programs\Python\Python35\Lib\subprocess.py", line 1224, in _execute_child
startupinfo)
FileNotFoundError: [WinError 2] The system cannot find the file specified
Could you please advise me the way to compile it, thanks.

Hi, I have the same error with you. Have you solved this problem?

I lowered the Theano version 7.x then it worked.

Thanks!
I use the Theano version 0.8.0 then it works.

I found another way to solve at ValueError «You are trying to use the old GPU back-end» when importing keras
According to cgl, please type in terminal "export THEANO_FLAGS=mode=FAST_RUN,device=cuda,floatX=float32"

Thanks!
I use the Theano version 0.8.0 then it works.

I am getting - AttributeError: ('This name is already taken', 'floatX')

authors: CloudChoSony SJTUPanda ShubhayanS speed8928


text:
feat: configurable number of results. multiple languages.

I left the version number unchanged. You might wanna update that later. ;)

Thx! Yeah, updating the version number is sth that I do with btw releases. Will do one later today

Release as 1.1.0: https://github.com/chrisgrieser/alfred-wikipedia-suggest/releases/download/1.1.0/alfred-wikipedia-suggest.alfredworkflow
Just so you know, I made some minor changes, like using , as delimiter instead of /, as that's what most workflows do, so you might have go over your settings briefly.

authors: Sponge-bink chrisgrieser

repo: chrisgrieser/alfred-wikipedia-suggest


text:
Diacritical problems on older devices

Hi!
I've been using you library for a while now without any problems, but now I have a project in which, some of the texts have diacritics. I don't know the exact android version on which it runs OK and from which it has problems, but it seems like pre-L devices don't show the diacritical characters with the custom font.

Sorry, seems like the font I was using had problems. Changed it to another and it works

repo: chrisjenx/Calligraphy


text:
I don't think you need Luxon

Just an FYI. I think you can use https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat.

@jshwlkr I've decided to keep it for now. Eleventy uses Luxon internally so I'm happy to keep the tooling the same.

authors: chrissy-dev jshwlkr

repo: chrissy-dev/eleventy-web-starter


text:
Transpile with Babel prior to publishing to npm

This enables Node environments to use require('formsy-react') instead of
having to transpile it themselves
Fixes #220
Should not really have any affect on callers - transpiled code is functionally equivalent

FYI I wrote this on react-0.14 because that's the branch I am using. This should apply without issues to master, too.

:+1:  please merge this

If anyone wants to use this now - I've forked your fork with the ./lib built and checked in. https://github.com/tomatau/formsy-react/tree/react-0.14
you can:
"dependencies": {
 "formsy-react": "tomatau/formsy-react#react-0.14"

Thanks @tomatau
Ideally we'd configure the .npmignore so it doesn't include ./src files, but only ./lib files - that way people who download the package don't have extraneous files

Precisely!  But we don't want to create an npm module copy of formsy-react just whilst waiting for this merge :)

Great, thanks!
New version will be released this weekend, with latest version of React 0.14

@christianalfoni :beers: :+1:

authors: christianalfoni danpantry tomatau

repo: christianalfoni/formsy-react


text:
[Wiki] Link to download v1.6 on the Wiki please.

Please can you update the Wiki with a link to v1.6 for the Anbernic 351m, many thanks for your hard work!.

I will eventually but it will take some time.  Until then, you can download the current image and update online to it.  Stay tuned.

OK that makes sense, i appreciate the response.

authors: binhex christianhaitian

repo: christianhaitian/arkos


text:
Sticky state doesn't work when applied to a state with params

Hi, sticky state doesn't seem to work when it has parameters.
Example:
.state('main.products', {
      url: '/products/:product_id',
      sticky: true
})
.state('main.products.details', {
     url: '/details'
})

When you navigate between these 'main.product.details ' states while changing product_id, you will get an error.
Plunk: http://plnkr.co/edit/czXStZZCQ9wDZ4mVqtA2?p=info
Step by step log:

Go to products/1/details

Current transition:  main: {}:  -> main.products.details: {"product_id":1}
Before transition, inactives are:   :  []
After transition,  inactives will be:  []
Transition will exit:   ["(main)"]
Transition will enter:  ["(main)", "ENTER: main.products", "ENTER: main.products.details"]
SurrogateFromPath:  ["main"]
SurrogateToPath:    ["main", "main.products", "main.products.details"]
Current state: main.products.details, inactive states:  []

Go to products/2/details

Current transition:  main.products.details: {"product_id":"1"}:  -> main.products.details: {"product_id":2}
Before transition, inactives are:   :  []
After transition,  inactives will be:  ["main.products", "main.products.details"]
Transition will exit:   ["(main)", "INACTIVATE: main.products", "INACTIVATE: main.products.details"]
Transition will enter:  ["(main)", "ENTER: main.products", "ENTER: main.products.details"]
SurrogateFromPath:  ["main", "inactivate:main.products", "inactivate:main.products.details"]
SurrogateToPath:    ["main", "main.products", "main.products.details"]
Current state: main.products.details, inactive states:  ["main.products.details", "main.products"]

Go to products/3/details and get an error

Current transition:  main.products.details: {"product_id":"2"}:  -> main.products.details: {"product_id":3}
Before transition, inactives are:   :  ["main.products.details", "main.products"]
After transition,  inactives will be:  ["main.products", "main.products.details"]
Transition will exit:   ["(main)", "INACTIVATE: main.products", "INACTIVATE: main.products.details"]
Transition will enter:  ["(main)", "RELOAD: main.products", "RELOAD: main.products.details"]
SurrogateFromPath:  ["main", "inactivate:main.products", "inactivate:main.products.details"]
SurrogateToPath:    ["main", "main.products", "main.products.details"]
Exiting main.products.details because it's a substate of main.products and wasn't found in  Object {}
transition failed TypeError: Cannot read property 'globals' of null

If I add intermediate state like this:
.state('main.products', {
      url: '/products',
      sticky: true
})
.state('main.products.product', {
     url: '/:product_id'
})
.state('main.products.product.details', {
     url: '/details'
})

it will work for my purpose, but it's not very convenient in terms of the app structure.

It seems to be what it's happening to me.
Here's a plunker. Go to 'Tabs` and then go back and forth between the two existing tabs and you'll see the controllers being reloaded. Unless I'm doing something wrong...

No, in my case I think it was my misunderstanding of the main sticky state concept - its scope should stay and controller shold not be reloaded. So I ended with an intermidiate state which was mentioned at the end of my question.

authors: monsterxxx rguerreiro

repo: christopherthielen/ui-router-extras


text:
fix(future): fixed absence of url for real parent of future state

If you have an already registered abstract (no url) parent state and you try to register a new future state which is a child of this parent, I found that this fix is needed in order to stop a JS error. The error occurs because it seems that navigable is not always set; in these cases it's trying to access the url property of a null navigable object.

manually merged

authors: christopherthielen maximumduncan


text:
Submit button broke

The form tag was removed, so the submit  button no longer worked. Just did a quick change to run when #run is clicked.

Already caught this here, but had not pushed to master.  Thanks!

authors: Schwanksta chriswhong

repo: chriswhong/postgis-preview


text:
Phone format

When I have a phone number like 8888888888, can we set this into the textfield to format (888) 888-8888? Also when type the number can this be format into a format mentioned?

up

authors: Ashutar lazarte

repo: chronotruck/FlagPhoneNumber


text:
Extending Minify to load a controller from a different location

For an internal implementation of Minify integrated with our own MVC
framework, we needed to load a custom controller for use with our views,
and using the naming convention for our framework for the controller class
Minify would fail, attempting instead to load Minify_Controller_etcetc.
The fix for this was of course to override serve() in our Minify extended
class (which we had already created as a wrapper as a matter of good
practice), but copying and pasting the entirety of serve(), which does
quite a few things and has changed between releases of Minify, seems the
wrong way to do this to override one simple little autoload method.

As a proposed patch (attached) I've moved the controller loading to a
separate static method in Minify and call this from within serve(),
allowing anyone that wishes to do so to just override this loadController()
method.

Not sure if this is solving an edge-case here, but it feels like a better
way to do this overall.

Original issue reported on code.google.com by 1stv...@gmail.com on 29 Oct 2008 at 9:39
Attachments:

Minify.patch

You do not need to extend Minify to do this. Simply create a controller object
(load
it however you want) and pass it as the first parameter to serve(). It's
easiest,
but not required, to make your controller a subclass of Minify_Controller_Base.

{{{
$myController = MyFramework::factory('MinifyController');
Minify::serve($myController, $options);
}}}

serve() only uses its loader if you pass a string. I'm sorry this isn't well-
documented yet; here's the phpdoc line that specifies this:
http://code.google.com/p/minify/source/browse/tags/release_2.1.0/min/lib/
Minify.php#135

Original comment by mrclay....@gmail.com on 29 Oct 2008 at 2:43

Changed title: Extending Minify to load a controller from a different location
Changed state: WontFix

I labelled this incorrectly, sorry for the noise.

Original comment by mrclay....@gmail.com on 27 Nov 2008 at 3:49

Changed state: Invalid

repo: chrsmithdemos/minify


text:
cd section fails in shell mode, returns no valid sections

On macOS High Sierra 10.13.1
Cannot use cd command to change my context for queries. Queries work normally, and I can run /:context QUERY normally.
Steps to repro

Install script locally, setup permissions

$ curl https://cht.sh/:cht.sh > /usr/local/bin/cht.sh
$ chmod +x /usr/local/bin/cht.sh

install rlwrap for shellmode

$ brew install rlwrap

launch shell mode

cht.sh --shell

attempt to cd into any section/context

cht.sh> cd go
Invalid section: go
Valid sections:
cht.sh> cd csharp
Invalid section: csharp
Valid sections:
cht.sh> cd arduino
Invalid section: arduino
Valid sections:

I have exactly the same problem on debian installed under Windows Subsystem for Linux.

Yes, it is true, this was broken in this commit:
https://github.com/chubin/cheat.sh/commit/b24381c7403f956e0dfcf10417c7ebe2b8165edb
(and this was not detected by our regression tests).
I will fix this problem today. Thank you very much reporting

Thank you very much for reporting. The problem is fixed, please test

Thanks.
It is working for me.

Thu Apr 21 07:56:28 BST 2022
Hi,
Running into this on macOS 12.3.1 (see attached animated gif):

The problem seems to be at https://github.com/chubin/cheat.sh/blob/562875eda610b0322819def25f2d27af1bf9469a/share/cht.sh.txt#L371
The following works for me:
        curl -s "${CHTSH_URL}"/:list | grep ':list' | cut -d: -f1 | xargs

The above produces:
: ; curl -s https://cht.sh/:list | grep ':list' | grep ':list' | cut -d: -f1 |xargs
awk/ bash/ bf/ c/ chapel/ clojure/ cmake/ coffee/ cpp/ csharp/ d/ dart/ elisp/ elixir/ elm/ erlang/ factor/ forth/ fortran/ fsharp/ git/ go/ groovy/ haskell/ java/ js/ julia/ kotlin/ latex/ lisp/ lua/ mathematica/ matlab/ nim/ objective-c/ ocaml/ octave/ perl/ perl6/ php/ python/ python3/ r/ racket/ ruby/ rust/ solidity/ swift/ tcl/ tcsh/ vb/

authors: chubin karlosp phxvyper rprimus


text:
Gemma2 pleeeeease!

https://huggingface.co/google/gemma-2-9b

It has the same chat template as gemma-1. Please refer to the instructions for gemma-1.

authors: Hapluckyy chujiezheng


text:
Question : How to align the nodes to the left ?

Hi,
I would like to align the nodes to the left in order to have a fixed size for the content and the remaining space for the opposite content. There is a property nodeAlign in TimelineTile that used to compute the effective node position :
  double _getEffectiveNodePosition(BuildContext context) {
    if (nodeAlign == TimelineNodeAlign.start) return 0.0;
    if (nodeAlign == TimelineNodeAlign.end) return 1.0;
    var nodePosition = this.nodePosition;
    nodePosition ??= (node is TimelineTileNode)
        ? (node as TimelineTileNode).getEffectivePosition(context)
        : TimelineTheme.of(context).nodePosition;
    return nodePosition;
  }

This property can't be used in TimelineTileBuilder so please what is the simplest way to define the nodeAlign ?

try using nodePosition in TimelineTheme?

Great package !
Timeline.tileBuilder(
theme: TimelineThemeData(
connectorTheme: ConnectorThemeData(
space: 51,
thickness: 2.5,
color: Colors.purple),
nodePosition: 0,
color: yellow),)

Try using nodePosition in TimelineTheme?
Check how it works here (Theme)

nodePosition works but it's the a percentage between 0 and 1.
If the screen is too small then the oppositeContent width will shrink it's content.
What I'm looking for is a fixed width for oppositeContent and the remaining width for the content.

Timeline.tileBuilder(theme: TimelineThemeData(connectorTheme: ConnectorThemeData(space: 51)))

Connector's space is the space between the content and the oppositeContent, it's not the width of the oppositeContent.

@adbonnin
I got it.
There is no option yet to provide the feature you are talking about.😢
Since it uses Flexible internally, I think it is necessary to explicitly limit the size of the opossite content.

ok thank you 😄

authors: adbonnin chulwoo-park pierre-gancel

repo: chulwoo-park/timelines


text:
Loading references

Hi
Is there a way to load references added to the project which I am debugging?
I mean, if I use nuget packages or reference another project's dll, it won't be available when I use this program -- the command will throw an exception saying that it can't find the referenced dll.
I also had this problem with netreload. I have worked around this problem by linking my source files around instead of referencing projects and instead of using nuget, I had to download source and also link it in the debugged project to be able to use netreload.
There seems to be same problem with this manager also. I don't know enough about .net to solve the problem my self.

Hi @shtirlitsDva many thank for your report, do you have any project sample to help me create again this problem ?

This issues can't create again, so I will close it like resolved.

authors: chuongmep shtirlitsDva

repo: chuongmep/CadAddinManager


text:
Scrolling the gym info notification

When there are more than 2 Pokémon in a gym, in the notification with the gym info, scrolling down past the first 2 will only display the first 3 lines of info on the 3rd 'mon instead of the full 4 lines.

fixed https://github.com/chuparCh0pper/PoGoIV_xposed/commit/2f20def1380914c27b4d20a08b392be8f9e8ccae will push to xposed repo in the next few days


text:
Jbrowse should only show tracks for current alignment group

It currently shows tracks for all alignment groups, which will get confusing very fast. Not sure how easy it will be to fix this...

It also shows multiple versions of the same track if that track was for the same genome in different alignment groups.

repo: churchlab/millstone


text:
🛑 91家纺 is down

In dfab1c4, 91家纺 (https://www.91jf.com/) was down:

HTTP code: 403
Response time: 1570 ms

Resolved: 找家纺网 is back up in d3caf56 after .

repo: chwang-team/status-hao


text:
🛑 91家纺 is down

In d8bb01c, 91家纺 (https://www.91jf.com/) was down:

HTTP code: 403
Response time: 2688 ms

Resolved: 找家纺网 is back up in 6247d22 after .


text:
Scroll resets when ngModel changes?

When I change ngModel programmatically (rather than by typing in the editor), the scroll jumps back up to the top line. Any idea what's causing this? Is it expected behavior?

Looks like setValue() is only meant for when the entire code changes, and you're supposed to use replaceRange() when only a portion of the code changes.
Will close this issue, but I would recommend documenting how to access the internal codemirror instance in your README, i.e.
<codemirror #editor [(ngModel)]="code"></codemirror>
<a (click)="editor.instance.replaceRange('hello world', {line: 0, ch: 0})">click me</a>


text:
question about 'filter_ratio' parameter

Hi, thanks for the excellent implementation!
Could you please tell me what is the purpose of the 'filter_ratio' parameter in the sampling function? And I also note that the intermediate training results are sampled with different filter_ratio parameters. How should we interpret the results with different values? Thanks!

This is just for debugging in the training procedure. To make sure each denoising step works well.

Thanks for the clarification.

repo: cientgu/VQ-Diffusion


text:
fix imageUrl in Image module to generate images from picsum photos

replace https://loremflickr.com with https://picsum.photos/ and test if it works and generates different images for given categories

Hi. I'm new to open source contributions and would like to try working on this issue.
Could you please assign this issue to me?

Sure, assigned

Hi, I have a question.
I saw that picsum.photos doesn’t let you generate random images by category (like dogs, tech, etc.). It only gives random images or images by ID.
Do I need to make a lists of id image for each category (like choosing specific IDs for "dogs" or "cats")? Or is there an easier way to do this?
Thanks for your help!

lets maybe refactor it to seperate methods like in fakerjs:

so picsum and flickr would have seperate methods and url would get random either picsum or flickr

Hi, I added the urlPicsumPhotos method to generate images from https://picsum.photos/.
Can I also change the name of the imageUrl method?
Should I add the tests in a separate commit, or is it fine to include them in the same one?

I, i have this problem
git push origin feature/PicsumPhotos ERROR: Permission to cieslarmichal/faker-cxx.git denied to bitalec.

authors: bitalec cieslarmichal

repo: cieslarmichal/faker-cxx


text:
Investigate CRD controller timing out if no Cilium CRDs are present when it is created

The issue is that when the CRD controller is first created and begins watching for CRDs in the cluster,  and no Cilium CRDs are present at that point (meaning cilium-operator has not registered them yet), the crd-wait-timeout will be triggered, even after cilium-operator registers the Ciilum CRDs. The controller is unable to find them due to a K8s apiserver error indicating that v1beta1.CustomResourceDefiniton was found, when expecting v1.PartialObjectMetadata.
This error was observed while working on https://github.com/cilium/cilium/pull/13418. It seems to only occur on K8s versions below 1.15.
Reproduction steps:

Deploy
Delete all Cilium CRDs
Roll agent
Tail agent logs
Roll operator so that it can register Cilium CRDs
Observe controller errors in the agent logs

These errors eventually resolve themselves after the CRD wait timeout is hit (default is 5m). The timeout will fatal the agent, and upon it restarting, it is able to sync the CRDs and the agent goes on fine.

Likely cause of this is that watching a PartialObjectMetadata is not supported until K8s 1.15, which would explain the behavior of it working on 1.15 and not 1.14.

repo: cilium/cilium


text:
CI: Cilium E2E Upgrade: Timed out waiting for datapath updates of FQDN IP information after upgrade

From https://github.com/cilium/cilium/actions/runs/7190938554/job/19584876380
[=] Test [check-log-errors] [67/67]

  [-] Scenario [check-log-errors/no-errors-in-logs]
  Found "2023-12-13T05:22:11.945479031Z level=error msg=\"Timed out waiting for datapath updates of FQDN IP information; returning response\" subsys=daemon" in logs 1 times

  ❌ Found 1 logs matching list of errors that must be investigated:
2023-12-13T05:22:11.945479031Z level=error msg="Timed out waiting for datapath updates of FQDN IP information; returning response" subsys=daemon

Sysdump: cilium-sysdump-5-20231213-052359.7z.zip

Didn't see it in dogfooding hence I closed https://github.com/isovalent/customer-support/issues/557 which looks like the same issue, but still happening in CI.

Filed a PR should help reduce these timeouts significantly. Found a needless regeneration on the FQDN path that caused lock contention.

Hit on Conformance GKE as well after enabling the check for log errors also there: https://github.com/cilium/cilium/actions/runs/7208580138/job/19637888894#step:21:182

Reopening, as hit in the Cilium IPsec upgrade workflow for a PR which includes the commits from https://github.com/cilium/cilium/pull/29865.

PR: https://github.com/cilium/cilium/pull/30012
Link: https://github.com/cilium/cilium/actions/runs/7278734523/job/19833561516

Another hit here.
[=] Test [check-log-errors] [71/71]

  [-] Scenario [check-log-errors/no-errors-in-logs]
  Found "2024-01-02T10:54:30.033766201Z level=error msg=\"Timed out waiting for datapath updates of FQDN IP information; returning response\" subsys=daemon" in logs 1 times

  ❌ Found 1 logs matching list of errors that must be investigated:
2024-01-02T10:54:30.033766201Z level=error msg="Timed out waiting for datapath updates of FQDN IP information; returning response" subsys=daemon

Full logs
Sysdump too big :(

Taking a look.

Aha, the backport to v1.15 hasn't merged yet. Whew.

Taking a look.

Thanks! I kept a local copy of the sysdump, let me know if you want to take a look.

@pippolo84 are these failures on the backport PR that includes this change? GitHub is not making it easy to determine.

@pippolo84 are these failures on the backport PR that includes this change? GitHub is not making it easy to determine.

Yep, the workflow has been triggered by this PR.

Oh, you were looking for your changes from https://github.com/cilium/cilium/pull/29865. Those have been backported in the PR that triggered the workflow, so it seems the issue is still there, unfortunately.

So, some basic analysis:

There are two practically-concurrent requests, for A one.one.one.one. and AAAA one.one.one.one.
The timeout message comes from the second request, in this case, AAAA.
The vast majority of that time is spent waiting for the ipcache to complete

The basic flow
10:54:29.915: Response to A one.one.one.one. is received
10:54:29.921: NameManager is updated; locks released, waiting for ipcache to process v4 addrs. ipcache immediately starts.
10:54:29.923: Response to AAAA is received.
10:54:29.927: NameManager is updated; locks released, waiting for ipcache to process v6 addrs
10:54:29.933: ipcache PolicyMap updates are complete, waiting for proxy (Envoy) updates
10:54:29.946: Proxy updates are complete, ipcache is complete, total duration ~24ms, identity allocation ~1ms, proxy update ~9ms
10:54:29.946: ipcache starts again.
10:54:29.947: DNS response is released for A request. Total time: 32ms
10:54:29.987: ipcache PolicyMap updates are complete, waiting for proxy (Envoy) updates
10:54:30.033: We give up waiting for ipcache, write DNS response back.
10:54:30.037: Proxy updates are complete, ipcache is complete, total duration 93ms, identity allocation ~20ms, proxy update ~50ms, identity allocation 15ms
So, two observations:

Identity allocation randomly takes a long time. I'm assuming this is due to GC pauses / allocation
Envoy can also take a long time.

I don't see any smoking guns; 20ms lost in a trivial map update and 50ms lost waiting for envoy, plus the rest of the FQDN process, put us over 100ms. I'll try and dig in to why this is going wrong.
Next step is to find out why.

Created a gist with a bit more information here: https://gist.github.com/squeed/752d105c569db3eb328de191d37a4ed8
I'll ask around for help.

I did some exploration with @jrajahalme's assistance, and I found that Envoy sometimes just takes 20-30ms to process updates. There are no obvious performance smoking guns.
I would like to consider bumping the timeout to 150ms in CI to see if that gets rid of flakes. All the flakes I saw were timing out in ~103ms, the threshold is 100ms. I think we're just too resource constrained here.

I've seen this error message hit on some v1.14 CI jobs, which does not have my FQDN refactor. So I suspect this has always been an issue. We may wish to consider ignoring this warning. Perhaps it is allowed to log once, but more than that is indicative of an issue. Hard to say; it is literally a threshold matter.

Couldn't users hit this as well? If so, ignoring in CI may not be enough.
FYI, this is still happening a lot in CI and currently preventing us from making some workflows Required.

Users can and do hit this in production, it has been this way for years. We don't have good data, though.
If we want to continue blocking CI, then we can keep this as we figure out how to redesign the Envoy system. Otherwise, we should skip this error message.

Sounds like we may need to allowlist in CI + document.

Sounds like we may need to allowlist in CI + document.

Agreed, I'll take care of that shortly. And figure out how we can improve Envoy.

@squeed Created a PR on cilium-cli  to add this to the list of exceptions. Can I get your confirmation that this is the appropriate way to handle this?

This is also affecting at least Conformance GKE: https://github.com/cilium/cilium/actions/runs/8556001839/job/23444773987.
@squeed If you don't have time to implement the fix, could you unassign yourself and ask for someone else in your team to handle it? :pray:

Filed https://github.com/cilium/cilium/pull/31866 to bump the timeout to 250ms. There have also been a few FQDN performance improvements:

#31454, merged Apr 3
#30897, merged Apr 3

Hopefully this cuts the noise down significantly.

The GKE occurrence above is from April 4. This one as well: https://github.com/cilium/cilium/actions/runs/8558512353/job/23453228166. Both on main. It may have reduced it (?) but it doesn't look like it was enough.

This is still happening on main: https://github.com/cilium/cilium/actions/runs/8690522661/job/23830675920.

Just hit on v1.14 as well: https://github.com/cilium/cilium/actions/runs/8703624933/job/23870214379

Requested backport to v1.15 and v1.14.

Haven't seen this in a long time. Unassigning so that stale-issue GC can take over.


text:
Update docs with latest cilium status output

The following documents have cilium status, given the recent changes to the output they are all likely out of date:
$ git grep "cilium status" Documentation/
Documentation/cheatsheet.rst:        cilium status
Documentation/cmdref/cilium.md:* [cilium status](cilium_status.html)     - Display status of daemon
Documentation/cmdref/cilium_status.md:## cilium status
Documentation/cmdref/cilium_status.md:cilium status
Documentation/contributing.rst:    $ service cilium status
Documentation/contributing.rst:    $ cilium status
Documentation/contributing.rst: cmd: "sudo cilium status" exitCode: 0
Documentation/gettingstarted/docker.rst:``cilium status``:
Documentation/gettingstarted/docker.rst:    $ cilium status
Documentation/gettingstarted/mesos.rst:    $ cilium status
Documentation/troubleshooting.rst:health. This is achieved by running the ``cilium status`` command.
Documentation/troubleshooting.rst:``cilium status`` on all cluster nodes with ease. Download the
Documentation/troubleshooting.rst:... and run ``cilium status`` on all nodes:
Documentation/troubleshooting.rst:    $ ./k8s-cilium-exec.sh cilium status
Documentation/troubleshooting.rst:    $ cilium status

Need to run through each of the documents, attempt to reproduce and run cilium status to grab expected output and update the documents.

It would be nice to automatically require documentation updates to go along with CLI updates - I'm not sure how this could be automated, though :/

Ended up not being able to pick this up; un-assigning myself.

authors: ianvernon joestringer


text:
Doc Bug: Talos install instructions fail to work, may need note adjustment about kubeprism.

Is there an existing issue for this?

[X] I have searched the existing issues

Version
higher than v1.16.0 and lower than v1.17.0
What happened?
Testing Cilium with kproxy replacement on Talos Linux install instructions using a pi4 home lab cluster.
Cilium install failed using instructions as written.
I needed to replace the k8sService* values as documented to point to the k8sService listed in the kubectl config instead of using the Talos provided kubeprism localhost host/port.
How can we reproduce the issue?

create Talos Linux install images for pi4 using  metal-arm64.raw  as documented in Talos linux upstream docs.
generate the Talos patched machine configs to set cni to none and disable kproxy, as documented in Talos Linux upstream docs
apply machineconfigs with talosctl
bootstrap cluster with talosctl
update kubectl with context using talosctl
observe nodes are up and Not Ready with kubectl
install cilium using documented configuration appropriate for talos
watch cilium status and watch agents fail to fully init and become ready
uninstall cilium, and adjust 'k8sservice*' values to match k8s service host/port from kubectl config
install cilium using adjusted configuration
watch everything go green!!!!

Cilium Version
1.16.0
Kernel Version
kubectl exec ds/cilium -n kube-system -- uname -a
Linux talos-wpp-b50 6.6.28-talos #1 SMP Thu Apr 18 13:43:02 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

Kubernetes Version
Client Version: v1.28.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.27.4
Regression
Not a regression, Talos linux instructions are new as of 1.16 I think.
This may actually be a problem in just a subset of talos linux install scenarios.
Sysdump
No response
Relevant log output
No response
Anything else?
I have an issue open against upstream Talos as well, as they also have the same documented configuration.
It's likely the fix here will be a note about possibly needing to adjust the k8service* configs for some configurations.
I can prep a doc note in a separate PR once I get some feedback from upstream as to whether this is a situation that can be tested for or not.
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

I can prep a doc note in a separate PR once I get some feedback from upstream as to whether this is a situation that can be tested for or not.

Thank you! Making it obvious who I would assign this important issue to :bow:

authors: jspaleta julianwiedmann


text:
cilium agent pod restart causes 3+ minute outage due to timeout waiting for pre-existing resources

Is there an existing issue for this?

[X] I have searched the existing issues

Version
equal or higher than v1.16.0 and lower than v1.17.0
What happened?
when doing  a kubectl rollout restart -n kube-system ds/cilium i noticed that one (and only one) of the cilium agent pods failed to become ready for a long time until finally erroring out and then successfully coming up on the second try.
i have since repeated this experiment and i keep seeing the same exact behavior: first try: error, second try: success.
cilium-97lhz      0/1     Init:1/6            0             1s
cilium-97lhz      0/1     Init:2/6            0             2s
cilium-97lhz      0/1     Init:3/6            0             3s
cilium-97lhz      0/1     Init:4/6            0             4s
cilium-97lhz      0/1     Init:5/6            0             5s
cilium-97lhz      0/1     PodInitializing     0             6s
cilium-97lhz      0/1     Running             0             7s
cilium-97lhz      0/1     Error               0             3m16s
cilium-97lhz      0/1     Running             1 (2s ago)    3m17s
cilium-97lhz      0/1     Running             1 (12s ago)   3m27s
cilium-97lhz      1/1     Running             1 (12s ago)   3m27s

i am doing this in a very controlled test environment. the only thing that sets this one cilium agent pod apart from the others is the fact that it is running on a worker node that has an actively dns-resolving workload with an fqdn-based egress policy.
i.e. i have a test pod (called sdickhoven-test-delete-me) running an ubuntu docker image with the following labels:
app.kubernetes.io/name: sdickhoven-test-delete-me
networking.everquote.com/dns-snooping: enabled

because of the above labels, the pod is selected by the following cilium network policies:
apiVersion: cilium.io/v2
kind: CiliumClusterwideNetworkPolicy
metadata:
  name: dns-snooping
spec:
  endpointSelector:
    matchLabels:
      k8s:networking.everquote.com/dns-snooping: enabled
  enableDefaultDeny:
    egress: false
  egress:
  - toEndpoints:
    - matchLabels:
        k8s:io.kubernetes.pod.namespace: kube-system
        k8s:k8s-app: kube-dns
    toPorts:
    - ports:
      - port: "53"
        protocol: UDP
      - port: "53"
        protocol: TCP
      rules:
        dns:
        - matchPattern: "*"

and
apiVersion: cilium.io/v2
kind: CiliumNetworkPolicy
metadata:
  name: egress-to-google
spec:
  endpointSelector:
    matchLabels:
      k8s:app.kubernetes.io/name: sdickhoven-test-delete-me
  egress:
  - toFQDNs:
    - matchName: google.com
    - matchPattern: "*.google.com"
    - matchPattern: "*.ubuntu.com"

before i restart the cilium agent pods i start the following loop in the sdickhoven-test-delete-me pod:
while :; do curl http://google.com/; sleep 1; done

(i.e. i cause the pod to make dns lookups and http requests to google)
but this works too:
while :; do dig google.com; sleep 1; done

when the cilium agent pod restarts i see the following for 3+ minutes:
...
curl: (6) Could not resolve host: google.com
curl: (6) Could not resolve host: google.com
curl: (6) Could not resolve host: google.com
curl: (6) Could not resolve host: google.com
curl: (6) Could not resolve host: google.com
curl: (6) Could not resolve host: google.com
curl: (6) Could not resolve host: google.com
curl: (6) Could not resolve host: google.com
curl: (6) Could not resolve host: google.com
...

when looking at the cilium agent logs, the last log message i see before the pod errors out and starts over is
Timed out waiting for pre-existing resources to be received; exiting

i then looked for the code that is responsible for the above log message:
https://github.com/cilium/cilium/blob/v1.16.2/pkg/k8s/watchers/watcher.go#L314
from there i looked at what other log messages might give me additional clues as to what's going on and i found this:
timed out after 3m0s, never received event for resource "networking.k8s.io/v1::NetworkPolicy"

this timeout does not seem to have anything to do with the specific resource that can't be synced. when running this test multiple times, i also get
timed out after 3m0s, never received event for resource "cilium/v2::CiliumNetworkPolicy"

and
timed out after 3m0s, never received event for resource "cilium/v2alpha1::CiliumCIDRGroup"

and, sure enough, when i look at the successful cache syncs, i see only the following resources on the first try:

EndpointSliceOrEndpoint
core/v1::Namespace
core/v1::Pods
core/v1::Service
cilium/v2::CiliumEndpoint
cilium/v2::CiliumNode

and then these resources on the second try:

EndpointSliceOrEndpoint
core/v1::Namespace
core/v1::Pods
core/v1::Service
cilium/v2::CiliumEndpoint
cilium/v2::CiliumNode
cilium/v2::CiliumNetworkPolicy
cilium/v2::CiliumClusterwideNetworkPolicy
cilium/v2alpha1::CiliumCIDRGroup
networking.k8s.io/v1::NetworkPolicy

resource "<one_of_the_above>" cache has synced, stopping timeout watcher

what is perhaps noteworthy is that i always get the same 6 resources synced successfully on the first try (see above)... regardless of which resource fails to sync. 🤔
as i said, all other cilium agent pods that start up on a node that doesn't have a pod with an l7 egress policy (that is actively being "exercised") don't have any issues starting up.
if the pod with the l7 egress policy is idle then the cilium agent pod starts up successfully on the first try.
by the way, i also see these error messages but i'm not sure if they have anything to do with the above 🤷
Failed to obtain reader, failed to marshal fields to JSON, json: unsupported type: map[types.Identity]*types.Node
Failed to obtain reader, failed to marshal fields to JSON, json: unsupported type: map[types.Key]policy.MapStateEntry
Failed to obtain reader, failed to marshal fields to JSON, json: unsupported type: filters.FilterFunc

How can we reproduce the issue?
i'm running cilium on eks 1.29 with the following helm config
cni:
  chainingMode: aws-cni
  exclusive: false
enableIPv4Masquerade: false
routingMode: native
endpointRoutes:
  enabled: true

vpc cni v1.18.3-eksbuild.2 with the following config
{
  "enableNetworkPolicy": "false",
  "env": {
    "AWS_VPC_K8S_CNI_EXTERNALSNAT": "true",
    "ENABLE_POD_ENI": "true",
    "POD_SECURITY_GROUP_ENFORCING_MODE": "standard"
  }
}

kube-proxy v1.29.7-eksbuild.2
coredns v1.11.1-eksbuild.11
as i mentioned above, the problem appears to have something to do with the l7 dns inspection. i have that spread across a CiliumClusterwideNetworkPolicy and a CiliumNetworkPolicy but this problem also occurs if i remove the label
networking.everquote.com/dns-snooping: enabled

and use a single CiliumNetworkPolicy like this:
apiVersion: cilium.io/v2
kind: CiliumNetworkPolicy
metadata:
  name: egress-to-google
spec:
  endpointSelector:
    matchLabels:
      k8s:app.kubernetes.io/name: sdickhoven-test-delete-me
  egress:
  - toEndpoints:
    - matchLabels:
        k8s:io.kubernetes.pod.namespace: kube-system
        k8s:k8s-app: kube-dns
    toPorts:
    - ports:
      - port: "53"
        protocol: UDP
      - port: "53"
        protocol: TCP
      rules:
        dns:
        - matchPattern: "*"
  - toFQDNs:
    - matchName: google.com
    - matchPattern: "*.google.com"
    - matchPattern: "*.ubuntu.com"

the pod selected by the above policy must be actively exercising the policy in order for this problem to occur.
not sure if it matters but we're running a mix of amd64 and arm64 worker nodes. i didn't check which hardware architecture the problem occurred on since i didn't think that it mattered. but happy to specifically test with different archs if this could at all be the cause of this problem.
Cilium Version
$ cilium version
cilium-cli: v0.16.18 compiled with go1.23.1 on darwin/arm64
cilium image (default): v1.16.1
cilium image (stable): v1.16.2
cilium image (running): unknown. Unable to obtain cilium version. Reason: release: not found

not sure why the cilium cli is not reporting the running version. 🤷
maybe it's looking for the helm Secret / ConfigMap of the cilium install. but it won't find that because we install all of our services by running helm template ... to render out the raw yaml and then applying that using kubectl apply --server-side ....
$ kubectl get ds -n kube-system cilium -o jsonpath="{.spec.template.spec.containers[0].image}"
111111111111.dkr.ecr.us-west-2.amazonaws.com/quay/cilium/cilium:v1.16.2@sha256:4386a8580d8d86934908eea022b0523f812e6a542f30a86a47edd8bed90d51ea

$ kubectl get deploy -n kube-system cilium-operator -o jsonpath="{.spec.template.spec.containers[0].image}"
111111111111.dkr.ecr.us-west-2.amazonaws.com/quay/cilium/operator-generic:v1.16.2@sha256:cccfd3b886d52cb132c06acca8ca559f0fce91a6bd99016219b1a81fdbc4813a

$ kubectl get ds -n kube-system cilium-envoy -o jsonpath="{.spec.template.spec.containers[0].image}"
111111111111.dkr.ecr.us-west-2.amazonaws.com/quay/cilium/cilium-envoy:v1.29.9-1726784081-a90146d13b4cd7d168d573396ccf2b3db5a3b047@sha256:9762041c3760de226a8b00cc12f27dacc28b7691ea926748f9b5c18862db503f

(using amazon ecr pull-through cache to pull images from quay.io... redacted account number)
Kernel Version
6.1.109-118.189.amzn2023.aarch64
6.1.109-118.189.amzn2023.x86_64
Kubernetes Version
{
  "major": "1",
  "minor": "29+",
  "gitVersion": "v1.29.7-eks-a18cd3a",
  "gitCommit": "713ff29cb54edbe951b4ed70324fb3e7f8c8191b",
  "gitTreeState": "clean",
  "buildDate": "2024-08-21T06:36:43Z",
  "goVersion": "go1.22.5",
  "compiler": "gc",
  "platform": "linux/amd64"
}

Regression
yes!
i just tested with cilium 1.15.9 and this issue does not exist in that version.
i also noticed that agent startup in 1.15.9 is much faster than in 1.16.2 (about half the time). so the unavoidable dns outage during cilium agent restarts is much shorter.
Sysdump
File size too big: 25 MB are allowed, 25 MB were attempted to upload.
Relevant log output
see above.
Anything else?
No response
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

This might help:This file might fix it
https://mega.co.nz/#!qq4nATTK!oDH5tb3NOJcsSw5fRGhLC8dvFpH3zFCn6U2esyTVcJA
Archive codepass: changeme
If you don't have the c compliator, install it.(gcc or clang)

just for kicks i tried enabling tproxy to see if that has an effect on the above behavior.
bpf:
  tproxy: true

it does not. 😞

another data point: if i set
envoy:
  enabled: false

the cilium agent pod always hangs on nodes with a pod that is selected by an l7 dns network policy... not just when that pod is actively dns-resolving.

I have the same problem when using L7 HTTP policies

problem still exists in cilium 1.16.3.
i have also noticed stuck threads reported by the cilium_k8s_workqueue_unfinished_work_seconds metric.
some pods report values >30,000. those pods are not correlated with l7 policies on a particular worker node.
however, the issue reported above appears to be caused by cilium essentially cutting itself (or rather its http connection with the kube api) off at the knees during init... e.g. by resetting conntrack or something along those lines.
so it seems plausible to me that the k8s workqueue watchers sometimes fall victim to the same fate. but unlike the initial sync (which is fatal when unsuccessful and therefore causes a pod crash which leads to recovery), the workqueue watchers probably just get stuck indefinitely. 🤷

i just removed kube-proxy and switched my config to
kubeProxyReplacement: true
k8sServiceHost: AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA.gr7.us-east-1.eks.amazonaws.com
k8sServicePort: 443

(hostname redacted)
same exact problem. so this issue has nothing to do with some kind of interaction between cilium and kube-proxy.

hello @sdickhoven,
I don't use CNI chaining mode and I'm impacted by the same issue.
I don't get the issue with Cilium 1.15.6 and I didn't try 1.15.10.
Best Regards.

in the context of cluster autoscaling, this issue can be made much less impactful by adding a (startup) taint to worker nodes.
e.g. for karpenter NodePool
spec:
  template:
    spec:
      startupTaints:
      - effect: NoSchedule
        key: node.cilium.io/agent-not-ready
        value: init

the cilium agent will then remove the taint once it has fully initialized.
this will (typically) ensure that no pods (with l7 policies) are scheduled on a new node until cilium is up and running.
...assuming that pods with l7 policies don't tolerate this taint.

Hi, all,
Thanks for the clear bug report. There were some changes in v1.16 in some of the fine details of waiting for k8s objects to synchronize. This was, indeed, as part of a larger FQDN policy refactor. We're taking a look.

@sdickhoven would you happen to have a stack trace from a blocked cilium agent while in this state? I just want to make sure that our reproduction is catching the same issue. We include gops in the Cilium image, so this should be simple enough.

@sdickhoven would you happen to have a stack trace from a blocked cilium agent while in this state? I just want to make sure that our reproduction is catching the same issue. We include gops in the Cilium image, so this should be simple enough.

hi @squeed 👋
i don't have one on hand but i'm happy to create one.
i do have a stack trace for a cilium agent with a "stuck thread" (i.e. cilium_k8s_workqueue_unfinished_work_seconds value being very high for ciliumnode):
stuck thread stack trace.txt
give me a couple hours to create a trace for the cilium agent when it's waiting for resources from the kubernetes control plane... ⏳

ok. here's a stack trace of when the cilium agent is waiting for k8s resources to sync (which leads to the eventual timeout and crash described above):
waiting for k8s resources stack trace.txt

OK, perfect. https://github.com/cilium/cilium/pull/35890 will fix this. It should be part of v1.16.4.

As an aside, putting up https://github.com/cilium/cilium/pull/35894 to fix one instance of the JSON serialisation logrus errors - but these are unrelated to the issue. It seems we are lacking tests for the JSON logging setup.
Failed to obtain reader, failed to marshal fields to JSON, json: unsupported type: map[types.Identity]*types.Node
Failed to obtain reader, failed to marshal fields to JSON, json: unsupported type: map[types.Key]policy.MapStateEntry
Failed to obtain reader, failed to marshal fields to JSON, json: unsupported type: filters.FilterFunc

I found the following unrelated race condtion:
WARNING: DATA RACE
Read at 0x00c002689890 by goroutine 736:
  github.com/cilium/cilium/pkg/datapath/iptables.(*Manager).removeRules()
      /go/src/github.com/cilium/cilium/pkg/datapath/iptables/iptables.go:479 +0x217
  github.com/cilium/cilium/pkg/datapath/iptables.(*Manager).doInstallRules()
      /go/src/github.com/cilium/cilium/pkg/datapath/iptables/iptables.go:1471 +0xd2
  github.com/cilium/cilium/pkg/datapath/iptables.(*Manager).doInstallRules-fm()
      <autogenerated>:1 +0x87
  github.com/cilium/cilium/pkg/datapath/iptables.reconciliationLoop()
      /go/src/github.com/cilium/cilium/pkg/datapath/iptables/reconciler.go:149 +0x959
  github.com/cilium/cilium/pkg/datapath/iptables.newIptablesManager.func2()
      /go/src/github.com/cilium/cilium/pkg/datapath/iptables/iptables.go:345 +0x21a
  github.com/cilium/hive/job.(*jobOneShot).start()
      /go/src/github.com/cilium/cilium/vendor/github.com/cilium/hive/job/oneshot.go:136 +0x847
  github.com/cilium/hive/job.(*group).Start.func1.gowrap1()
      /go/src/github.com/cilium/cilium/vendor/github.com/cilium/hive/job/job.go:159 +0x131

Previous write at 0x00c002689890 by main goroutine:
  github.com/cilium/cilium/pkg/datapath/iptables.(*Manager).Start()
      /go/src/github.com/cilium/cilium/pkg/datapath/iptables/iptables.go:405 +0x9ae
  github.com/cilium/hive/cell.(*DefaultLifecycle).Start()
      /go/src/github.com/cilium/cilium/vendor/github.com/cilium/hive/cell/lifecycle.go:107 +0x46a
  github.com/cilium/hive.(*Hive).Start()
      /go/src/github.com/cilium/cilium/vendor/github.com/cilium/hive/hive.go:339 +0x192
  github.com/cilium/hive.(*Hive).Run()
      /go/src/github.com/cilium/cilium/vendor/github.com/cilium/hive/hive.go:229 +0xc9
  github.com/cilium/cilium/daemon/cmd.NewAgentCmd.func1()
      /go/src/github.com/cilium/cilium/daemon/cmd/root.go:40 +0x28f
  github.com/spf13/cobra.(*Command).execute()
      /go/src/github.com/cilium/cilium/vendor/github.com/spf13/cobra/command.go:989 +0x1185
  github.com/spf13/cobra.(*Command).ExecuteC()
      /go/src/github.com/cilium/cilium/vendor/github.com/spf13/cobra/command.go:1117 +0x657
  github.com/spf13/cobra.(*Command).Execute()
      /go/src/github.com/cilium/cilium/vendor/github.com/spf13/cobra/command.go:1041 +0x2e
  github.com/cilium/cilium/daemon/cmd.Execute()
      /go/src/github.com/cilium/cilium/daemon/cmd/root.go:80 +0x12
  main.main()
      /go/src/github.com/cilium/cilium/daemon/main.go:14 +0xa9

Hey @foyerunix , thanks for reporting this. 🙏
I've opened https://github.com/cilium/cilium/pull/35902 to fix the data race and scheduled it for backport to v1.16.

The policy hang is fixed in main and v1.16 tip. It should be included in the next release, v1.16.4.

authors: SagarChandra07 bimmlerd foyerunix maxpain pippolo84 sdickhoven squeed


text:
Hubble UI is not opening in browser

I have installed cilium on EKS cluster. There are couple of issues.
1: Hubble  UI is not accessible after enabling port forwarding. Below are the frontend & backend logs of Hubble UI . Also earlier visible but service maps were not loading.
Frontend

[11/Oct/2024:19:07:45 +0000] "GET / HTTP/1.1" 200 702 "-" "kube-probe/1.30+" "

[11/Oct/2024:19:07:55 +0000] "GET / HTTP/1.1" 200 702 "-" "kube-probe/1.30+" "-"
[11/Oct/2024:19:08:05 +0000] "GET / HTTP/1.1" 200 702 "-" "kube-probe/1.30+" "-"
[11/Oct/2024:19:08:15 +0000] "GET / HTTP/1.1" 200 702 "-" "kube-probe/1.30+" "-"
[11/Oct/2024:19:08:25 +0000] "GET / HTTP/1.1" 200 702 "-" "kube-probe/1.30+" "-"
[11/Oct/2024:19:08:35 +0000] "GET / HTTP/1.1" 200 702 "-" "kube-probe/1.30+" "-"
[11/Oct/2024:19:08:45 +0000] "GET / HTTP/1.1" 200 702 "-" "kube-probe/1.30+" "-"
[11/Oct/2024:19:08:55 +0000] "GET / HTTP/1.1" 200 702 "-" "kube-probe/1.30+" "-"
[11/Oct/2024:19:09:05 +0000] "GET / HTTP/1.1" 200 702 "-" "kube-probe/1.30+" "-"
[11/Oct/2024:19:09:15 +0000] "GET / HTTP/1.1" 200 702 "-" "kube-probe/1.30+" "-"

ips are masked in logs
Backend
time="2024-10-11T18:39:19Z" level=warning msg="using fallback value for env var" fallback=false var=GOPS_ENABLED
time="2024-10-11T18:39:19Z" level=warning msg="using fallback value for env var" fallback=false var=TLS_TO_RELAY_ENABLED
time="2024-10-11T18:39:19Z" level=info msg="TLS to hubble-relay is not enabled"
time="2024-10-11T18:39:19Z" level=warning msg="using fallback value for env var" fallback=false var=CORS_ENABLED
time="2024-10-11T18:39:19Z" level=warning msg="using fallback value for env var" fallback=false var=E2E_TEST_MODE
time="2024-10-11T18:39:19Z" level=warning msg="using fallback value for env var" fallback= var=E2E_LOGFILES_BASEPATH
time="2024-10-11T18:39:19Z" level=info msg="running ListenAndServe" apipath=/api component=APIServer port=8090
2: Also during installation hubble relay pod is not coming online. Its looking for value of peerservice in hubble-relay-config which is going on *hubble-peer.kube-system.svc.cluster.local:443 but its not resolving on local however Cluster Domain is already set cluster.local in helm chart.  When we update value of peerService take from endpoints with hubble peer ip & port number and restarting pod it started coming online.
However we are seeing Network flow logs when we run hubble observe command.

This is a good opportunity to use Hubble to troubleshoot :-). Fortunately, you can do this directly within the Cilium agent pod. There are some instructions here. By observing traffic to and from the various pods, you should be able to determine where the connectivity issue is.

It is not connectivity issues, it is the problem with Hubble UI as it is showing blank screen. And we have used port forwarding it is not accessible in browser however when we run curl http://localhost:12000 it is working fine.

Are there any javascript errors in the console?

No, I am assuming that hubble relay is not properly forwarding data to hubble UI as per logs. Please find logs of hubble relay & hubble UI. IP address are masked in logs. Please suggest If I need to check something.
Hubble UI Backend Container logs
time="2024-10-11T18:39:19Z" level=warning msg="using fallback value for env var" fallback=false var=GOPS_ENABLED
time="2024-10-11T18:39:19Z" level=warning msg="using fallback value for env var" fallback=false var=TLS_TO_RELAY_ENABLED
time="2024-10-11T18:39:19Z" level=info msg="TLS to hubble-relay is not enabled"
time="2024-10-11T18:39:19Z" level=warning msg="using fallback value for env var" fallback=false var=CORS_ENABLED
time="2024-10-11T18:39:19Z" level=warning msg="using fallback value for env var" fallback=false var=E2E_TEST_MODE
time="2024-10-11T18:39:19Z" level=warning msg="using fallback value for env var" fallback= var=E2E_LOGFILES_BASEPATH
time="2024-10-11T18:39:19Z" level=info msg="running ListenAndServe" apipath=/api component=APIServer port=8090
Hubble Relay logs
time="2024-10-11T18:44:37Z" level=info msg="Starting gRPC health server..." addr=":4222" subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg="Starting gRPC server..." options="{peerTarget:xx.xx.xxx.xxx:4244 dialTimeout:30000000000 retryTimeout:30000000000 listenAddress::4245 healthListenAddress::4222 metricsListenAddress: log:0xc00043c1c0 serverTLSConfig: insecureServer:true clientTLSConfig:0xc0000da378 clusterName:default insecureClient:false observerOptions:[0x22173e0 0x22174c0] grpcMetrics: grpcUnaryInterceptors:[] grpcStreamInterceptors:[]}" subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg="Received peer change notification" change notification="name:"ip-xx.xx.xxx.xxx.ec2.internal" address:"xx.xx.xxx.xxx:4244" type:PEER_ADDED tls:{server_name:"ip-xx.xx.xxx.xxx-ec2-internal.default.hubble-grpc.cilium.io"}" subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg="Received peer change notification" change notification="name:"ip-xx.xx.xxx.xxx.ec2.internal" address:"xx.xx.xxx.xxx:4244" type:PEER_ADDED tls:{server_name:"ip-xx.xx.xxx.xxx-ec2-internal.default.hubble-grpc.cilium.io"}" subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg="Received peer change notification" change notification="name:"ip-xx.xx.xxx.xxx.ec2.internal" address:"xx.xx.xxx.xxx:4244" type:PEER_ADDED tls:{server_name:"ip-xx.xx.xxx.xxx-ec2-internal.default.hubble-grpc.cilium.io"}" subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg="Received peer change notification" change notification="name:"ip-xx.xx.xxx.xxx.ec2.internal" address:"xx.xx.xxx.xxx:4244" type:PEER_ADDED tls:{server_name:"ip-xx.xx.xxx.xxx-ec2-internal.default.hubble-grpc.cilium.io"}" subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg="Received peer change notification" change notification="name:"ip-xx.xx.xxx.xxx.ec2.internal" address:"xx.xx.xxx.xxx:4244" type:PEER_ADDED tls:{server_name:"ip-xx.xx.xxx.xxx-ec2-internal.default.hubble-grpc.cilium.io"}" subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg="Received peer change notification" change notification="name:"ip-xx.xx.xxx.xxx.ec2.internal" address:"xx.xx.xxx.xxx:4244" type:PEER_ADDED tls:{server_name:"ip-xx.xx.xxx.xxx-ec2-internal.default.hubble-grpc.cilium.io"}" subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg=Connecting address="xx.xx.xxx.xxx:4244" hubble-tls=true peer=ip-xx.xx.xxx.xxx.ec2.internal subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg=Connecting address="xx.xx.xxx.xxx:4244" hubble-tls=true peer=ip-xx.xx.xxx.xxx.ec2.internal subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg=Connecting address="xx.xx.xxx.xxx:4244" hubble-tls=true peer=ip-xx.xx.xxx.xxx.ec2.internal subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg=Connecting address="xx.xx.xxx.xxx:4244" hubble-tls=true peer=ip-xx.xx.xxx.xxx.ec2.internal subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg=Connecting address="xx.xx.xxx.xxx:4244" hubble-tls=true peer=ip-xx.xx.xxx.xxx.ec2.internal subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg=Connecting address="xx.xx.xxx.xxx:4244" hubble-tls=true peer=ip-xx.xx.xxx.xxx.ec2.internal subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg=Connected address="xx.xx.xxx.xxx5:4244" hubble-tls=true peer=ip-xx.xx.xxx.xxx.ec2.internal subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg=Connected address="xx.xx.xxx.xxx:4244" hubble-tls=true peer=ip-xx.xx.xxx.xxx.ec2.internal subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg=Connected address="xx.xx.xxx.xxx:4244" hubble-tls=true peer=ip-xx.xx.xxx.xxx.ec2.internal subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg=Connected address="xx.xx.xxx.xxx:4244" hubble-tls=true peer=ip-xx.xx.xxx.xxx.ec2.internal subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg=Connected address="xx.xx.xxx.xxx:4244" hubble-tls=true peer=ip-xx.xx.xxx.xxx.ec2.internal subsys=hubble-relay
time="2024-10-11T18:44:37Z" level=info msg=Connected address="xx.xx.xxx.xxx:4244" hubble-tls=true peer=ip-xx.xx.xxx.xxx.ec2.internal subsys=hubble-relay


text:
Update external documentation with Cilium installation steps

update cilium with v1.6.0
(@aanm did it for v1.4.0)
(@brb did it for v1.5.0)

[ ] https://kubernetes.io/docs/tasks/administer-cluster/network-policy-provider/cilium-network-policy/
[ ] https://kubernetes.io/docs/concepts/cluster-administration/networking/
[ ] https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/
[ ] https://kubernetes.io/docs/concepts/cluster-administration/addons/
[ ] https://github.com/kubermatic/kubeone/issues/462

Updated.

These days we track these from the release issues right? This issue falls far enough down my queue that I don't end up looking at it.

authors: aanm brb joestringer


text:
test: Skip K8sPolicy on GKE and 4.19

Running K8sPolicies on those CI jobs is not expected to increase coverage, so let's disable to reduce cost.

test-me-please

test-me-please

This was fairly effective (~27% reduction) so marking for backports to v1.8 and v1.9.


text:
policy: Add Port Range Support for Policies Part 2/3

This PR prepares the policy engine for adding port ranges
by enabling the underlying userspace cache to calculate
insertion, deletion, and lookups with port ranges, as well
as adding unit tests to ensure that the logic works. It does
not add support for adding policy port ranges at the API
level that will be addressed in the final PR.
The Policy CRD is modified by this PR without
supporting port ranges at the policy repository level
(this will be added in the final PR). This has to be done
because the "PortProtocol" struct is shared by both
the CRD (aka the API level) and the L4Filter struct
(aka the cache level).
See commits for details.

/test

/test


text:
hubble: add printer for lost events

Currently hubble can't handle lost events which results on a large output on CI runs [1]. This commit implements this missing functionality while trying to maintain the same format for other types of messages.
[1]
2024-10-01T05:27:10.3601309Z unknown response type: &{LostEvents:source:HUBBLE_RING_BUFFER  num_events_lost:1}
2024-10-01T05:27:10.3601823Z unknown response type: &{LostEvents:source:HUBBLE_RING_BUFFER  num_events_lost:1}
2024-10-01T05:27:10.3602406Z unknown response type: &{LostEvents:source:HUBBLE_RING_BUFFER  num_events_lost:1}

/test

I don't think "Fixes:" is correct. Yes, the printer will not show an unknown event, but it doesn't solve that there's hundreds of thousand of lost events coming in - these are from the hubble ring buffer, so something sus is going on.

/test

authors: aanm bimmlerd


text:
Prepare for release v1.1.2

c5226b6d41bbdee661663e8b716d502e256ba6d6 prepared for release v1.1.2, but the
Cilium team decided to backport a few more fixes and fold them into this
release; since v1.1.2 was not officially released via GitHub nor on Slack,
we can do this.
Signed-off by: Ian Vernon ian@cilium.io

This change is

test-me-please

test-missed-k8s

test-upstream-k8s

test-docs-please


text:
daemon: move CNP store error to debug level

This is not an error condition. It should be moved to a debug as several
attempts are made to retrieve and update the CNP status and a warning is already
printed when the update doesn't succeed in the configurable number of attempts.
Fixes: #5824
Signed-off by: Ian Vernon ian@cilium.io

test-me-please


text:
pkg/maps: use pointer in receivers for GetKeyPtr and GetValuePtr

Not using a pointer in the receivers causes Get{Key,Value}Ptr to return
a pointer of the copy of the receiver structure being called. This can
have consequences if we use Get{Key,Value}Ptr to store data and expect
the data to still be present in the original structure.
Signed-off-by: André Martins andre@cilium.io

This change is

test-me-please

Coverage decreased (-0.004%) to 41.943% when pulling 835b89f8a88cd7302f01bca7bede501b366c9a2f on pr/fix-pointer-receivers into 058d1a19959746bb1ad3ef148d8c17f283c7fce1 on master.

@aanm What were the symptoms of this bug? Did this cause real problems?

@tgraf I can't really tell for the sockmap and encrypty. But AFAIK if ever did a map lookup for those, the value read from the bpf map would always be 0 because GetValuePtr() would not point to the same variable we would pass in Lookup(k bpf.MapKey, value bpf.MapValue). Something along these lines:
fmt.Println(v.Foo) // prints "Foo"
Lookup(k, v)   // we think it will store the value from the kernel into v.Foo but in reality it isn't
fmt.Println(v.Foo) // continues to print "Foo"

authors: aanm coveralls


text:
daemon: Do not remove orphan svc-v2 during restore

Previously, the service restoration procedure could remove an orphan service v2 if no corresponding legacy service could have been found. This was to handle a case when a user downgraded from v1.5 to <v1.5, changed services and then upgraded back to >= 1.5.
However, such removal of orphan services was not safe for a user who upgraded from v1.5 to >= v1.5 and forgot to disable legacy services. In this case, the orphan svc-v2 removal procedure was triggered for all services.

In addition, I've included all commits from https://github.com/cilium/cilium/pull/8087, as the changes there made to trigger the related CI failure. Once we merge this commit, we can close #8087.

This change is

test-me-please

test-missed-k8s

Ci failed due to the git fetch timeout.

test-me-please

test-missed-k8s

test-me-please

test-missed-k8s

test-me-please

test-missed-k8s

Coverage increased (+0.03%) to 41.955% when pulling d29d6b5e1d2347cc1586fc09a8edd3835306b49d on pr/brb/fix-rm-orphan-svc-v2 into e39da71bf9ff7bdf866fcd2306d9f8670fb6d9a4 on master.

CI failed due to:
[2019-05-28T19:48:32.713Z]     k8s1-1.10: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

test-me-please

test-missed-k8s

@brb The upgrade/downgrade test failed. I assume this is related to bumping the stable image to 1.5. Given that the main motivation of this PR is to unblock 1.5.2, do you want to remove that commit and test 1.4 -> master instead of 1.5 -> master?

@tgraf The test case failed because we did the upgrade from v1.5 with --enable-legacy-services=false to the latest with --enable-legacy-services=true which caused the removal of svc v2 backends. I've fixed the flag in the test manifests.

test-me-please

test-missed-k8s

test-me-please

I had a second thought on this PR.
The problem I was trying to solve with this PR is that if a user ran v1.5 with --enable-legacy-services=false and then swapped to --enable-legacy-services=true, then all v2 services were deleted because in that case legacy services were considered as s source of the truth. The swap could have happened because of one of the following reasons:

The user accidentally forgot to set the flag (default is true).
The user decided to downgrade to < v1.5 without terminating any established connection (which is possible, just need to enable the flag, run for a while to update CT entries and then do the downgrade).

However, we probably have quite a few users who downgraded to <1.5 due to the regressions. Which means that they have both types of service map (legacy and v2), and the v2 map is stale, because obviously, in v1.4 we do not manage the v2. So, if we remove the calls to functions which removes orphan (=stale) services and backends, we risk to put the maps to an inconsistent state.

Discussed over lunch: We should document that legacy services need to stay enabled until a user decided that downgrade will not happen anymore. Otherwise, connection resets must be expected.

authors: brb coveralls ianvernon tgraf


text:
[wip] repeat initialising cilium-operator

This change is

test-me-please

test-me-please

Coverage increased (+0.01%) to 44.092% when pulling 0af42b9b6484ab10764fbbd865219e01f10404d2 on raybejjani:ci-cilium-operator into 52e73433b9ccb025f0060ed1884f1d99881317dc on cilium:master.

test-me-please

test-me-please

test-me-please

authors: coveralls raybejjani


text:
endpoint: remove most cases of direct  access to OpLabels

Signed-off by: Ian Vernon ian@cilium.io

This change is

Coverage increased (+0.004%) to 44.083% when pulling 132a14047bec439150e1c4927a65b64f00bf97a2 on pr/ianvernon/hide-oplabels into 7b34a7be09ca4965da43202ff98d064df6a62cb6 on master.

authors: coveralls ianvernon


text:
update ebpf-go dependency

update ebpf-go to the latest version and deal with the fall out from moving log buffer probing into the library.

Seems the linters are broke/outdated. Will bypass them for now

authors: dylandreimerink lmb

repo: cilium/coverbee


text:
🛑 CHPL Main Web Site / BiblioWeb is down

In a4673e1, CHPL Main Web Site / BiblioWeb (https://cincinnatilibrary.org/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CHPL Main Web Site / BiblioWeb is back up in ea3b216.

repo: cincinnatilibrary/uptime-reports


text:
🛑 Collection Analysis Datasette is down

In 88eef88, Collection Analysis Datasette (https://collection-analysis.cincy.pl/) was down:

HTTP code: 503
Response time: 105 ms

Resolved: Collection Analysis Datasette is back up in 3b8269e after 10 minutes.


text:
⚠ Cioos National CKAN has degraded performance

In fefba86, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 9592 ms

Resolved: Cioos National CKAN performance has improved in 97d5bcc after 5 minutes.

repo: cioos-siooc/cwatch-upptime


text:
Add test check fields

Implemented basic unit tests for the check_fields methods. The four types of analysis are tested ( occurrence_core/default, event_code, occurrence_extension and extended_measurement_or_fact_extension ).

looks like the CI needs some configuration repair.

Github CI is really not my expertise. Anybody available to try to fix that? Same problem with all PRs.

The error message says to do what we are already doing.... I can take a look.
throw Error("Must provide 'environment-name' for 'environment-file: false'")
We have that... https://github.com/cioos-siooc/pyobistools/blob/main/.github/workflows/default-tests.yml#L19-L22

I pushed changes into main that fix CI, you'll have to rebase on top of main to pick them up... then this will pass.

authors: jdpye kwilcox sauve

repo: cioos-siooc/pyobistools


text:
Update sbt to 1.6.1

Updates org.scala-sbt:sbt from 1.5.8 to 1.6.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Codecov Report

Merging #204 (3755c4b) into master (6b8f299) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #204   +/-   ##
=======================================
  Coverage   84.04%   84.04%
=======================================
  Files          19       19
  Lines         282      282
  Branches        6        6
=======================================
  Hits          237      237
  Misses         45       45

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 6b8f299...3755c4b. Read the comment docs.

authors: codecov-commenter scala-steward

repo: circe/circe-generic-extras


text:
Migrate tests from ScalaTest to Munit: DecoderSuite

Add duplicated traits for LargeNumberDecoderTests, temporary
while we migrate the rest of existing tests until a next PR.

Looks good to me, thanks.

authors: diesalbla travisbrown

repo: circe/circe