text:
6.1.x pint2

Description
pint merge from 6.0.x to 6.1.x
Fixes # (issue)
Type of change

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

How Has This Been Tested?
https://jenkins.confluent.io/job/cp-ansible-on-demand/318/
1 test failing was due to debian repo. It's passing locally now.
Test Configuration:
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Any dependent changes have been merged and published in downstream modules
[ ] Any variable changes have been validated to be backwards compatible

Hey Anuj,
If there's no new change moving from one branch to another, we can do without a PR. You can merge directly following the instructions on resolving pint merge conflict.

repo: confluentinc/cp-ansible


text:
Disable fips on mtls-java11-rhel

Description
Disabled fips to make the scenrio 'mtls-java11-rhel' work properly since fips is not supported with java11 as per the docs here.
Fixes # (6.0.x release readiness)
Type of change

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

How Has This Been Tested?
molecule test -s mtls-java11-rhel on 6.0.x gave all pass/success.
Test Configuration:
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Any dependent changes have been merged and published in downstream modules
[ ] Any variable changes have been validated to be backwards compatible

@utkarsh5474 We should not be disabling FIPS, as we need to test for this.  My suggestion would be to move this scenario to Java8 for now.

Sure @JumaX. I ran this yesterday with FIPS enabled on java8, but the scenario converge failed. Haven't triaged yet. Will update once that's solved.

source: gharchive/pull-request

license_type: permissive

license_source: github-api


text:
Reduce debug log output

Finish the major re-factoring first which will help isolate logout put two specific subjects first.

Closing Issue

source: gharchive/issue

authors: astubbs johnbyrnejb

repo: confluentinc/parallel-consumer


text:
Authentication Failed when connecting using a CC SSO user account

Code of Conduct

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

On what operating system are you seeing the problem?
Windows (x64)
VS Code version
Version: 1.95.3 (user setup)
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631
Version of Confluent extension
0.21.3
To Reproduce

Click on Connect to Confluent Cloud
The VSCode dialog box appears, and clicked the Allow button, to allow the extension to sign in to Confluent Cloud.
Enter my SSO email address
Then a web page appears with the Authentication Failed message

Current vs. Expected behavior
I expect the login to be successful and see my CC resources in Confluent for VScode extension.
Relevant log output
2024-12-05 09:32:34.207 [error] [errors] [browser sign-in flow] error: {"authStatus":"NO_TOKEN","connectionId":"vscode-confluent-cloud-connection"}
2024-12-05 09:32:34.218 [error] [commands.connections] error creating CCloud connection {"error":{"name":"Error","message":"Authentication failed, see browser for details"}}
2024-12-05 09:32:34.219 [error] [commands] Error invoking command "confluent.connections.create": Authentication failed, see browser for details

Which area(s) are affected? (Select all that apply)
Connections, Confluent Cloud, Topics, Schemas, Messages
Additional context
No response

Hey @j3-signalroom, Thanks for reporting the issue!
Do you see any further error message on the web page with the Authentication Failed message?

Hi,
This is the message I get:

@j3-signalroom, Thanks! It looks like the URI of that page contains some kind of error description. Do you mind sharing the full URI here, assuming it doesn't contain sensitive information?

Well it depends, if any of the URL parameter contain secure info:
state
client
protocol
response_type
code_challange_method
code_challenge
redirect_uri
scope

Please advise.

Thanks!
I meant the URL http://127.0.0.1:26636/gateway/v1/callback-vscode-docs?error=invalid_request&error_description=the... from your screenshot. I'd be mainly interested in the query param error_description.

Got it!
http://127.0.0.1:26636/gateway/v1/callback-vscode-docs?error=invalid_request&error_description=the%20connection%20was%20disabled&state=hIeUfrYoAhDB9kHFxw-jjq4yUFyomAZaVvqTzYOkpCY

Thanks, that's helpful!
In general, signing in via SSO works for the VS Code extension. I checked it this morning.
I'll ask our Auth team about the error message and get back to you ASAP. Thanks for your patience!

Yeah, I would think so too!  I appreciate your attention to the matter, and I am looking forward to hearing the feedback from the Auth Team.

Do you mind sharing the email address you're using to sign in with me? We want to confirm the SSO provider is set up correctly. You can send it to ssprenger at confluent dot io. Thanks!

No problem, I went ahead emailed you the email address, yesterday.
(I know you know, I am just keeping this issue dialog up to date.  ;-))

@j3-signalroom could sort out the issue offline. Somehow, the VS Code extension's OAuth app wasn't enabled for their SSO provider. We'll make sure this doesn't happen again.

Thank you, Stefan for being so helpful and getting it done!

repo: confluentinc/vscode


text:
Testing the implementation of EngineFilter

@confused-Techie let me know what do you think.
Tested on jsfiddle a bit and it seems to work giving the proper values.

Very much appreciate the fast work on this one. And this looks way more inline with what I was hoping for this to become. Love the contribution. My only concern is your test do contain a failure
Expected: "what-a-package"
    Received: undefined
      30 |   test("Valid package, gives correct object", async () => {
      31 |     const res = await request(app).get("/api/packages/what-a-package");
    > 32 |     expect(res.body.name).toBe("what-a-package");
         |                           ^
      33 |   });
      34 |   test("Invalid Package, gives 'Not Found'", async () => {
      35 |     const res = await request(app).get("/api/packages/invalid-package");
      at Object.toBe (src/tests/main.test.js:32:27)

But I don't think that is because of this commit. So I'm gonna merge this commit, and look further into that issue the test is pointing out. As always thank you!

license: MIT


text:
Allow changing user appearance

Is your feature request related to a problem? Please describe.
Currently, users are either a robot head or a video box with their own camera stream. We need to make this a bit more flexible.
Describe the solution you'd like
Would like the ability to:

define the dimensions of the video box (to support AR/VR portals);
define the source of the video stream to a different stream than the user (to support an external video stream, coming from a different camera);
make the user completely invisible (don't show the robot head nor the video cube).

Believe this should only be available to scene writers.
Additional context
These features would better support some of the remote conference-type of experiences.

Added in https://github.com/conix-center/ARENA-core/pull/338

authors: mwfarb nampereira

repo: conix-center/ARENA-core


text:
Improved workspace version update to support private packages

Just pushing some updates after running through a release and noting some rough edges with scripts.

Marking as draft until release is done in case there are more changes.

I think there's another issue: The function readPackages expects a directory with packages. It doesn't recognize packages/examples/react/basic as a package.

The current Node.js LTS - v22 - implements glob. This makes it easy to read all packages:
import { readFileSync, existsSync, globSync } from "node:fs";
import { dirname, join } from "node:path";

/**
 * Read the given root package.json file, and return an array of workspace
 * packages.
 *
 * @param {string} rootPackageJsonPath
 * @return {{path: string, pkg: Record<string, unknown>}[]}
 */
function findWorkspacePackages(rootPackageJsonPath) {
  const root = JSON.parse(readFileSync(rootPackageJsonPath, "utf-8"));
  if (!Array.isArray(root.workspaces) || root.workspaces.some(w => typeof w !== "string")) {
    throw new Error(`Missing or malformed "workspaces" array in ${rootPackageJsonPath}`);
  }
  const rootDir = dirname(rootPackageJsonPath);
  return root.workspaces
    .flatMap(ws => globSync(join(rootDir, ws, "package.json")))
    .filter(path => existsSync(path))
    .map(path => {
      const pkg = JSON.parse(readFileSync(path, "utf-8"));
      return { path, pkg };
    });
}

We can bump to Node v22 (we can still use older versions in CI) and use that. Need to update writePackages a bit. I think it's worth it.

Closing in preference to #499

Reopening since I realized #499 was merging into this branch 😵

authors: paul-sachs timostamm

repo: connectrpc/connect-query-es


text:
TestAsset has been setup incorrectly on linea

Describe the bug
The canonical id of TestERC20 should be 0x0000000000000000000000007ea6ea49b0b0ae9c5db7907d139d9cd3439862a1. but on linea it is 0x000000000000000000000000b4fbf271143f4fbf7b91a5ded31805e42b2208d6
TheTestERC20 token transfers to linea are getting stuck forever due to the incorrect asset setup

Update:

Both canonical ids registered onchain with the same TEST asset
The subgraph was storing the Asset entity under the local address emitted in the event
When the asset with id 0x000000000000000000000000b4fbf271143f4fbf7b91a5ded31805e42b2208d6 was registered after 0x0000000000000000000000007ea6ea49b0b0ae9c5db7907d139d9cd3439862a1, because they both shared the same local asset, the canonical id was overwritten

Solution:

Refactor subgraph to store Asset entity with hash(canonicalId, canonicalDomain)
Remove the AssetStatus entity, and instead add it to the corresponding Asset entity

authors: LayneHaber wanglonghong

repo: connext/monorepo


text:
Transparency not working

I added let g:SnazzyTransparent = 1 to my .vimrc and some transparency to the background of Termite. I am using compton as my compositor.
The terminal transparency works just fine but vim still uses an opaque background.
Is there something I am doing wrong? How is the transparency supposed to work?
Sincerely,
Franz

Hey Franz,
Are you using the latest version of vim?

Output of vim --version:
VIM - Vi IMproved 8.1 (2018 May 18, compiled Apr 26 2019 21:55:55)
Included patches: 1-1186
Compiled by Arch Linux
Huge version without GUI.  Features included (+) or not (-):
+acl               +extra_search      +mouse_netterm     -tag_old_static
+arabic            -farsi             +mouse_sgr         -tag_any_white
+autocmd           +file_in_path      -mouse_sysmouse    +tcl/dyn
+autochdir         +find_in_path      +mouse_urxvt       +termguicolors
-autoservername    +float             +mouse_xterm       +terminal
-balloon_eval      +folding           +multi_byte        +terminfo
+balloon_eval_term -footer            +multi_lang        +termresponse
-browse            +fork()            -mzscheme          +textobjects
++builtin_terms    +gettext           +netbeans_intg     +textprop
+byte_offset       -hangul_input      +num64             +timers
+channel           +iconv             +packages          +title
+cindent           +insert_expand     +path_extra        -toolbar
-clientserver      +job               +perl/dyn          +user_commands
-clipboard         +jumplist          +persistent_undo   +vartabs
+cmdline_compl     +keymap            +postscript        +vertsplit
+cmdline_hist      +lambda            +printer           +virtualedit
+cmdline_info      +langmap           +profile           +visual
+comments          +libcall           +python/dyn        +visualextra
+conceal           +linebreak         +python3/dyn       +viminfo
+cryptv            +lispindent        +quickfix          +vreplace
+cscope            +listcmds          +reltime           +wildignore
+cursorbind        +localmap          +rightleft         +wildmenu
+cursorshape       +lua/dyn           +ruby/dyn          +windows
+dialog_con        +menu              +scrollbind        +writebackup
+diff              +mksession         +signs             -X11
+digraphs          +modify_fname      +smartindent       -xfontset
-dnd               +mouse             +startuptime       -xim
-ebcdic            -mouseshape        +statusline        -xpm
+emacs_tags        +mouse_dec         -sun_workshop      -xsmp
+eval              +mouse_gpm         +syntax            -xterm_clipboard
+ex_extra          -mouse_jsbterm     +tag_binary        -xterm_save
   system vimrc file: "/etc/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -D_FORTIFY_SOURCE=2  -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -L. -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -fstack-protector-strong -rdynamic -Wl,-export-dynamic -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.28/core_perl/CORE  -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -L/usr/local/lib -Wl,--as-needed -o vim        -lm -ltinfo -lelf -lnsl    -lacl -lattr -lgpm -ldl   -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.28/core_perl/CORE -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -fstack-protector-strong -L/usr/local/lib  -L/usr/lib/perl5/5.28/core_perl/CORE -lperl -lpthread -ldl -lm -lcrypt -lutil -lc   -L/usr/lib -ltclstub8.6 -ldl -lz -lpthread -lm

Would you be able to share your vimrc?

call plug#begin('~/.vim/plug')
Plug 'junegunn/vim-easy-align'
Plug 'itchyny/lightline.vim'
Plug 'junegunn/fzf'
Plug 'connorholyday/vim-snazzy'
Plug 'https://github.com/chrisbra/Colorizer'
Plug 'lervag/vimtex'
Plug 'fatih/vim-go', { 'do': ':GoUpdateBinaries' }
call plug#end()

colorscheme snazzy
let g:lightline = { 'colorscheme': 'snazzy' }
let g:SnazzyTransparent = 1
set laststatus=2

Ah, try moving the settings above the colorscheme declaration, like so:
call plug#begin('~/.vim/plug')
Plug 'junegunn/vim-easy-align'
Plug 'itchyny/lightline.vim'
Plug 'junegunn/fzf'
Plug 'connorholyday/vim-snazzy'
Plug 'https://github.com/chrisbra/Colorizer'
Plug 'lervag/vimtex'
Plug 'fatih/vim-go', { 'do': ':GoUpdateBinaries' }
call plug#end()

let g:lightline = { 'colorscheme': 'snazzy' }
let g:SnazzyTransparent = 1
colorscheme snazzy
set laststatus=2

It works now, thanks.

authors: MiltFra connorholyday

repo: connorholyday/vim-snazzy


text:
Increase visiblity of checkbox

Thank you for developing the Sakura Night theme. Its design, inspired by sakura trees, is both beautiful and calming. As a Japanese user, I find it especially appealing and well-crafted.
I am writing this with the help of GPT, as I am not a native English speaker.
I’ve encountered an issue regarding checkbox visibility.

The background color of checkboxes appears the same whether they are checked or unchecked, making it difficult to distinguish their state.
This may be a bug, but the published screenshots don't show the checkbox, so I couldn't be sure this is correct.
The contrast between the checkmark and the background is relatively low, which makes it harder to notice at a glance.
While this may be an intentional design choice, I think improving the contrast or adjusting the background color for checked checkboxes would make the theme even more user-friendly.
I tried with IntelliJ IDEA 2024.3 (Ultimate Edition) #IU-243.21565.193
I will be glad to provide any information that is needed.
Thank you again for your excellent work. I hope you’ll consider this suggestion for a future update.

Hi @Manapia, thanks for the kind words! I will of course look into this in the next couple of days for you 👍

Hi @Manapia, I've uploaded an update to the JetBrains marketplace which should be usable in the next couple of days. They've been fairly quick recently.
Regarding the fix, I couldn't find much I could do with it unfortunately. It seems like JetBrains have a bug where in themes marked as dark mode themes, the background of the checkbox is always the selected color, whereas on light themes it's transparent. Marking the theme as a light mode theme would have other implications so it doesn't seem like a good idea.
Hopefully this helps with the visibility at least.
Let me know how you get on with it, I'll close this in the meantime 👍
Thanks again for raising this issue

Thank you for the feedback, and glad that it has helped. Looking at some other themes, they tend to keep the checkbox background transparent, which I could change it to if needed

You're right—many other themes tend to use transparent checkboxes, which might make it easier for users migrating from other themes to feel more familiar.
To preserve the uniqueness of this theme, I think using a lighter shade of pink could also work well

![image](https://github.com/user-attachments/assets/a5da4db5-6a0e-4078-ba3e-38f83138c9ad)

That said, I’m not familiar with JetBrains IDE theme settings. If making the checkboxes transparent or using lighter colors unintentionally affects the background of other controls, it might be better to leave things as they are. The background color of the "OK" button, for example, doesn't seem to have changed (though it looks a bit too bright), so my concern may be unnecessary.
In any case, I’m happy with the current design. Thank you!

authors: Manapia connorwyatt

repo: connorwyatt/sakura-intellij-theme


text:
Touch visualiser on single view

want to see touch on single uiview not on uiwindow. is that possible?

Unfortunately, not with the current state of this project.  Right now it's all or nothing.

I modified your work  To work on single view here is the link to it -https://github.com/ajaysinghthakur/ASTTouchVisualizeView

I've got another project I'm working on for visualizing all sensor information.  Maybe I can eventually incorporate this into that project.

authors: ajaysinghthakur joeblau

repo: conopsys/COSTouchVisualizer

license: mit

license_source: bigquery


text:
Add ZHT to my itoken2 wallet?

How is this done please?
Hello hello??

below is the tutorial, you can refer to it.
https://github.com/consenlabs/token-profile#token-profile-guideline

authors: frhenzie tstt

repo: consenlabs/token-profile


text:
Add LIT token

Project team background:
Hanwen Cheng, the founder of Litentry, is a former Product Owner of Parity Signer, an Ethereum offline wallet. The development team of 11 members is currently based in Berlin, Germany with years of experience in the blockchain industry.
Project basic information:
Litentry is a decentralized identity aggregation protocol across multiple networks, featuring a Decentralized Identity (DID)
indexing mechanism and a Substrate-based credit computation network. The objective of Litentry is to enable DID
aggregation, verification, and credit calculation.
Media publications:
offical website : https://www.litentry.com/
blog: "https://litentry.medium.com/",
twitter: "https://twitter.com/litentry",
telegram: "https://t.me/Litentry",
github: "https://github.com/litentry",
medium: "https://litentry.medium.com/"
Binance research: https://research.binancezh.cc/en/projects/litentry
Tradeable exchanges:
Binance: https://www.binance.com/en
WBF: https://www.wbfex.com/
Lbank: https://www.lbank.info
Coinbene: https://www.coinbene.com/
Recommended Gas Limit (For ERC-20 project teams) for transaction:  60,000

欢迎在社区中推荐用户使用 imToken 2.0 ，imToken 支持比特币, 以太坊, Comos, EOS, 波场, Nervos, 比特币现金, 莱特币，波卡等资产管理；同时支持去中心化币币兑换功能 Tokenlon；转账页面支持 ETH, USDT, EOS, BTC OTC 功能；另外对于没有 ETH 矿工费的用户，也提供 ETH 手续费充值功能。


text:
importing bad paths fails with incorrect error

If a go file that's being compiled has a bad import path, gb will claim:

FATAL: command "build" failed: no packages supplied

Even though there are valid files. This is true even if there are many files that are correct, with only one file containing an invalid import.
This is reproduced with a simple test file:
package main

import (
	"log"
	"this/is/a/bad/path"
)

func main() {
	log.Println("Hello World.")
}

The reason this is happening is for several reasons. In context.go, matchPackages has a call to filepath.Walk that isn't handling the error that's returned. The error that's being returned (but not handled) is correctly calling out

import "this/is/a/bad/path": not a directory

but that isn't being passed higher up the stack. It's alsonot specifying which file (or line) is causing the bad import, which makes it a bit harder for the user to track down the offending line of code.
I tried to figure out a good way to pass along the information to main so it call fatalf out, but nothing came to mind in the bit that I looked at it since there's no error structure set up in place for that section of code. I'd be happy to try to fix it if you're willing to give a bit of guidance, or if you want to fix this yourself I'm totally happy with that as well.

Thanks for reporting this bug, which revision of gb are you using ?

I'm working in this area right now.

I grabbed head as of this morning. https://github.com/constabulary/gb/commit/5217deb25e4ba2962b4212c1f701ebe61383a5f2 to be exact.

Thanks for logging this bug, I think i've cleaned up the worst of the mess.

authors: austinkelmore davecheney

repo: constabulary/gb


text:
🛑 divag.parishq.net is down

In dbcacbc, divag.parishq.net (https://divag.parishq.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: divag.parishq.net is back up in 40bb5c0.

repo: constructions-incongrues/status


text:
🛑 gallery.parishq.net is down

In debcfbe, gallery.parishq.net (https://gallery.parishq.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: gallery.parishq.net is back up in 551c975.


text:
🛑 sauvemoidesagios.resterdigne.net is down

In 908f1d6, sauvemoidesagios.resterdigne.net (https://sauvemoidesagios.resterdigne.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: sauvemoidesagios.resterdigne.net is back up in 3b4e5d9 after 20 hours, 39 minutes.

Resolved: sauvemoidesagios.resterdigne.net is back up in b0829bb after 20 hours, 39 minutes.


text:
Update continuity to d3c23511c1bf5851696cba83143d9

This includes updates for resolving links on windows.
Signed-off-by: Michael Crosby crosbymichael@gmail.com

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2362   +/-   ##
=======================================
  Coverage   44.99%   44.99%
=======================================
  Files          92       92
  Lines        9336     9336
=======================================
  Hits         4201     4201
  Misses       4457     4457
  Partials      678      678

Flag
Coverage Δ

#linux
49.29% <ø> (ø)
:arrow_up:

#windows
41.25% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

LGTM

LGTM

authors: codecov-io crosbymichael dmcgowan ehazlett

repo: containerd/containerd


text:
[release/1.3 backport] shim v2 runc: propagate options.Root to Cleanup

Previously shim v2 (io.containerd.runc.{v1,v2}) always used /run/containerd/runc as the runc root.
backport of https://github.com/containerd/containerd/pull/4327
fixes https://github.com/containerd/containerd/issues/4326
fixes https://github.com/containerd/containerd/issues/2767

@AkihiroSuda ptal


text:
meta.json is not removed when the container process exits

Description
container Poststop hook is not triggered when container exists: meta.json is not removed when the container process exits.
Steps to reproduce the issue

nerdctl run  --name toto alpine
nerdctl kill toto
/var/lib/nerdctl/<ADDRHASH>/etchosts/default/<ID>/meta.json is still present

Describe the results you received and expected
/var/lib/nerdctl/<ADDRHASH>/etchosts/<NS>/<ID>/meta.json should be removed when container with id  ID exists
What version of nerdctl are you using?
latest
Are you using a variant of nerdctl? (e.g., Rancher Desktop)
None
Host information
No response

container Poststop is executed in the Runtime Namespace and not the container ns

Hey folks.
Wondering if we do really want this.
meta.json will get deleted when the container gets removed (postStop).
Is removing at stop really bring anything valuable to the table?

@fahedouch ^

@AkihiroSuda @fahedouch shall we close this?
I do not think we should remove it when the container stops. It is removed when the container is removed though.

We may remove it when the container exits, but it’s not a critical requirement

We may remove it when the container exits, but it’s not a critical requirement

I do not think it is feasible, as we do not get ocihooks events for container stop/start.
Generally speaking, we cannot ensure we do things when containers stop outside of us explicitly calling stop.

authors: AkihiroSuda apostasie fahedouch

repo: containerd/nerdctl


text:
volume: resolve symlink paths in volumes

Closes: https://github.com/containers/libpod/issues/1608

this is a quite important fix to have I think, but unfortunately it is still blocked on the Buildah PR

vendored a new buildah

F28 is CGroups flake

bot, retest this please

Did vndr hiccup? It looks like we're bringing in a lot more of buildah than before

good question @mheon, there's a lot of Buildah code being dragged in with this that I'd not expect to see, pull, commit, images, etc....

Did vndr hiccup? It looks like we're bringing in a lot more of buildah than before

yes, something went wrong.  I've ran it again and now there are less files changed

/lgtm

authors: TomSweeneyRedHat giuseppe mheon rhatdan

repo: containers/libpod


text:
create pod on the fly

when a user specifies --pod to podman create|run, we should create that pod
automatically.  the port bindings from the container are then inherited by
the infra container.  this signicantly improves the workflow of running
containers inside pods with podman.  the user is still encouraged to use
podman pod create to have more granular control of the pod create options.
Signed-off-by: baude bbaude@redhat.com

/approve

I am not a huge fan of side effects like this.  The biggest problem I have with them, is it allows typos to succeed and the user has no idea what went wrong.
Why not just inform the user to add the port if it does not exist.
pod foobar does not exist.  Create the foobar pod by executing podman pod create foobar.

because that isnt the end of the story.  the user then has to go extract the port bindings from the container image and add them to the pod creation.  if you are worried about typos, consider the opportunity to mess that up (or the user forgets to add ports, or doesnt know we cannot add ports to a pod afterwards).  then the user has to delete the pod (and potentially container) and start over.

Sadly, I guess I got to agree with you. But we have that type of issue all over the place.
Of course if the container fails to be created, it could cause issues, since now the user need to clean up the pod.
But I will go along with it in this case.
Should we fail if the user creates a container with a pod that exists and the user specified exposed ports, and tell them that will not work.  Or will it work in libpod but not in Kubernetes?

I really don't like this. What happens if I typo "pod1" as "pod2" when trying to add a container to a pod, and end up making an entirely new pod (and being really confused as to why my new container can't talk to anything else in the pod)?

If we are going to do this - we really ought to have a special sigil of some sort for creating and not joining pods. --pod=new: or something.
And we need to refactor the pod create code to only happen in one place, like @rhatdan said

Yes, I kind of like --pod=new, and then the pod would be named the same as the container.
podman create --pod=new --name walsh ...
You end up with a container and a pod named walsh.

This then requires that the user must pass a container name or we have to fail them because we dont have a auto-generated container name until the container is created; and once the container is created, it cannot be added to the pod.  i also dont love when we use the command input to be meaningful like netmode is ... meaning what the user puts in could be a name or some other type but if this is a strong requirement, i'll play along.

@baude Eh, I'd be fine with them passing in the name too... Maybe --pod=new:pod_name or similar?

I would go allong with --pod new:name

bot, retest this please

LGTM, one nit

/lgtm

/lgtm

/retest

/retest

/retest

/test images

authors: baude mheon rhatdan


text:
Attempt to turn on rpmbuild tests

Signed-off-by: Daniel J Walsh dwalsh@redhat.com

/lgtm


text:
change links as owner changes.

Youki changed the owner from utam0k to containers.
The link needs to be changed accordingly.

already fix by https://github.com/containers/youki/pull/61

repo: containers/youki


text:
CoreDNS ClusterRole name might conflicts

Feature Request
Proposal
The name of the ClusterRole defined for CoreDNS when installed with helm and the kubedns option might conflict. Indeed, this resource is not namespaces and since it's name is coredns the chance of already having a ClusterRole with this name is very high.
I suggest we rename it into maesh-coredns and also rename the ClusterRoleBinding into maesh-coredns-binding
Workarounds
It's not an issue if the operator doesn't already have a coredns RoleBinding in it's cluster.

Do all CoreDNS components need to be renamed for consistency?

authors: jspdown walbertus

repo: containous/maesh


text:
Multiply maxconn extractorfunc's

Can I do something like this?
docker service create
    --label traefik.backend.maxconn.f1.amount=1 \
    --label traefik.backend.maxconn.f1.extractorfunc=client.ip \
    --label traefik.backend.maxconn.f2.amount=16 \
    --label traefik.backend.maxconn.f2.extractorfunc=request.host \
    ...

Thanks for your interest in Traefik !
Every questions in the issues is a feature less.
The issue tracker is for reporting bugs and feature requests only.
For end-user related support questions, refer to one of the following:

Stack Overflow using the "traefik" tag
the Traefik community Slack channel

authors: JAremko ldez

repo: containous/traefik


text:
Use sdnotify for systemd

This is useful if a configuration is long to load.
Systemd will continue dependency chain only when server have finish to start.
https://www.freedesktop.org/software/systemd/man/systemd.service.html#Type=

After a night of reflection... I think we can do a better design :)
More to come

Main problem is server.Start() is a blocking function. I can't evaluate when it finish to listen on socket etc.
With current patch it's working but it will send ready signal some little time before socket init...

Changes can be squashed and pushed with 1-clic

Many thanks to @Nikkau !

Let's squash the commit too if possible :angel:

@vdemeester this can be done via GH button ;)

@guilhem that's true, but I am not a huge fan of that :smile_cat: — but let's do it :stuck_out_tongue_closed_eyes:

@vdemeester this have 1 advantage: keeping history in PR.
But I'm not really sure if good or not :/
Just experiment this pattern for now ^^

@guilhem hum yeah but sometimes you want to actually have a PR with multiples commit merged as is. Anyway, this is no big deal :stuck_out_tongue_closed_eyes:

authors: guilhem vdemeester


text:
Cannot install with Symfony 6.0.7 (issue with PHP8 and psr/cache 3)

Hello !
I've just tried to install the bundle on a fresh Symfony 6.0.7 install with PHP 8.0.18 (I had to downgrade from PHP 8.1.4 to PHP8.0.18) and it's not working.
Here is the error message on install :
➜  symfony-ux git:(feature/contentful-integration) ✗ composer require contentful/contentful-bundle
Info from https://repo.packagist.org: #StandWithUkraine
Using version ^7.1 for contentful/contentful-bundle
./composer.json has been updated
Running composer update contentful/contentful-bundle
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - cache/void-adapter 1.0.0 requires php ^5.6 || ^7.0 -> your php version (8.0.18) does not satisfy that requirement.
    - cache/void-adapter 1.1.0 requires psr/cache ^1.0 -> found psr/cache[1.0.0, 1.0.1] but the package is fixed to 3.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - contentful/contentful[6.1.0, ..., 6.2.0] require psr/cache ^1.0 -> found psr/cache[1.0.0, 1.0.1] but the package is fixed to 3.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - cache/void-adapter 1.2.0 requires psr/cache ^1.0 || ^2.0 -> found psr/cache[1.0.0, 1.0.1, 2.0.0] but the package is fixed to 3.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - contentful/contentful[6.0.0, ..., 6.0.5] require php ^7.2 -> your php version (8.0.18) does not satisfy that requirement.
    - contentful/contentful 6.4.0 requires psr/cache ^1.0|^2.0 -> found psr/cache[1.0.0, 1.0.1, 2.0.0] but the package is fixed to 3.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - contentful/contentful-bundle 7.1.0 requires contentful/contentful ^6.0 -> satisfiable by contentful/contentful[6.0.0, ..., 6.4.0].
    - contentful/contentful 6.3.0 requires cache/void-adapter ^1.0 -> satisfiable by cache/void-adapter[1.0.0, 1.1.0, 1.2.0].
    - Root composer.json requires contentful/contentful-bundle ^7.1 -> satisfiable by contentful/contentful-bundle[7.1.0].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require contentful/contentful-bundle:*" to figure out if any version is installable, or "composer require contentful/contentful-bundle:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Is it an error that you have on your side ? I saw that PHP8 support was updated (https://github.com/contentful/ContentfulBundle/issues/52) ... but I can't make it work.
Thanks for your help.
Best regards.

Hi,
not a clean solution, but with the following steps it works:
composer require contentful/contentful -W
composer require contentful/contentful-bundle

It will downgrade the following packages:

psr/cache from 3.0.0 to 2.0.0
symfony/cache-contracts from 3.0.1 to 2.5.1

BTW when running composer require contentful/contentful without -W I get this error
composer require contentful/contentful
Using version ^6.4 for contentful/contentful
./composer.json has been updated
Running composer update contentful/contentful
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires contentful/contentful ^6.4 -> satisfiable by contentful/contentful[6.4.0].
    - contentful/contentful 6.4.0 requires psr/cache ^1.0|^2.0 -> found psr/cache[1.0.0, 1.0.1, 2.0.0] but the package is fixed to 3.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require contentful/contentful:*" to figure out if any version is installable, or "composer require contentful/contentful:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.
unable to run /usr/local/bin/composer require contentful/contentful

Seems like there's some version conflict; it does work for me on a new app. Would you mind sharing the require portion of your composer.json?
You can also try downgrading your contentful/contentful dependency to ^6.3.

Hi folks,
sure, here is the require portion:
    "require": {
        "php": ">=8.0.2",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "contentful/contentful": "^6.4",
        "contentful/contentful-bundle": "^7.1",
        "symfony/asset": "6.0.*",
        "symfony/console": "6.0.*",
        "symfony/dotenv": "6.0.*",
        "symfony/flex": "^2",
        "symfony/framework-bundle": "6.0.*",
        "symfony/monolog-bundle": "^3.0",
        "symfony/runtime": "6.0.*",
        "symfony/twig-bundle": "6.0.*",
        "symfony/webpack-encore-bundle": "^1.14",
        "symfony/yaml": "6.0.*",
        "twig/extra-bundle": "^2.12|^3.0",
        "twig/twig": "^2.12|^3.0"
    },

Thanks for your help.
Best.

Hey @ghisleouf , with the new version installing a new repo with your require list works for me now. Can you check as well? :)

authors: Sebb767 bchatard ghisleouf

repo: contentful/ContentfulBundle


text:
Low vram?

Hi, Unfortunately I don't have a good graphics card. Is there still ways to run this on 8gb of vram?

Hi @Zegervg, it should be fine for your card.
Let us know if it is not the case.

Idk man, doesnt look so good.

How many points do you have from your point cloud ?

17004 in the input.py if thats what you mean

It was fixed, the resolution for my input images were way to high. Thanks.

authors: Zegervg rvandeghen

repo: convexsplatting/convex-splatting


text:
Missing uninstallation documentation

Console has a link to uninstall a rack but it gives a 404.

You can remove this Rack from Convox. This will not delete any resources. To do so, please see the Uninstalling Convox guide.

https://convox.com/docs/uninstall-convox/

This is fixed

authors: ddollar nathany

repo: convox/site


text:
feat(scripts): Enhance the deploy-s3-cf script

Goals

CI control via ENV variables
user control (or CI overrides) via CLI options
sanitized output format for CI readability
verbose mode (prints the called aws CLI commands with all the options)
backwards compatibility with the original code (via ENV control)
valid for sh

Usage: ./deploy-s3-cf.sh [-h] [-v] -s <SOURCE_DIR> -u <AWS_S3_BUCKET_URI> -i <AWS_CF_DISTRIBUTION_ID>

Options:
  -s SOURCE_DIR
        Local source directory
        REQUIRED (Can be also provided via environment variable)
  -u AWS_S3_BUCKET_URI
        AWS S3 bucket URI in the following format: 's3://<bucket>/[<subdir>]'
        REQUIRED (Can be also provided via environment variable or constructed. See below)
  -i AWS_CF_DISTRIBUTION_ID
        AWS CloudFront Distribution ID
        REQUIRED (Can be also provided via environment variable)
  -v    Verbose output (print API commands being executed)
  -h    Display this help message

Other supported environment variables:
  AWS_S3_BUCKET  Can be used to construct the S3 bucket URI.
                 If used, AWS_S3_BUCKET_URI doesn't have to be set.
  AWS_S3_PATH    Can be used to further specify bucket path in the S3 URI.
                 Has to start with '/'. Works only when AWS_S3_BUCKET is set.
                 Defaults to '/'.

Description
When all needed ENV variables are set, running the script without any options (./deploy-s3-cf.sh) just works!
The direct CLI way to set the destination in S3 supports subdirs and renders into AWS_S3_BUCKET_URI. The variable value is verified that it contains valid URL s3://.../[...].
The AWS_S3_BUCKET_URI is required to be set, however there's a way to set it indirectly using the standard AWS_S3_BUCKET variable, which contains the bucket name. Also a subdir within the bucket can be specified using the optional AWS_S3_PATH variable. Value of this variable must begin with /.

Please merge with squash
Also should be tested with CI to verify it works properly
CC @Vrtak-CZ

repo: cookielab/container-image-deployer


text:
sql

您好可以提供一下这个代码的sql文件吗

已经添加，在sql文件夹下 @shenxixi250


text:
MacOs icon size

When using Dialogic on a Mac the icons don't resize properly to the display. This does not happen in Windows at any display % resolution.

I'm not sure if this is a Godot bug or an extra setting that I need to check, but leaving the issue here so I don't forget to fix it

It seems to be a problem with Godot: https://github.com/godotengine/godot/issues/20197

repo: coppolaemilio/dialogic


text:
2.0 Additional Background Options

Adds the background crossfade option back from 1.x. It's skipped on loading custom scenes as a background, since they should be let to do their own thing, but maybe sending them a signal with the fade time if they want to use it would be a good idea.
Also I will add the hide dialog option back as well, but not in yet as of this comment. Skippable was also a property on them as well, ive not looked at how much of the skipping has been implemented yet tho

wait hide dialog wasn't on Background initially, it's on a wait. Skippable wasn't before either, but it should maybe be implicitly skippable and skip the wait time


text:
I want to translate that mod to Turkish language.

Hello.I want to translate that mod to turkish language.What should i do ?
Note : I know about fork , .lang files etc.
Btw can you give me the translation file as a list ? Because it is very hard to translate it as non-list.I can write somethings wrong.

I'm a little confused. They should be in a list, as seen here..? Could it be that you're opening the language file in a text editor that doesn't support unix-style line-breaks? In that case, I would recommend another editor (such as Notepad++ or VS Code) or editing the file directly on github.com.
Keep in mind that I don't know when there will be a next release that will include your changes, though. I'll leave it up to @ChloeDawn (maybe @asiekierka) to make that decision.

repo: copygirl/WearableBackpacks


text:
Add setup script for local testing

A lot of contributors use CI to test their changes without testing them locally. This is a waste of contributors' time and CI resources. Probably the biggest reason is that it's not straight forward to setup the tests locally.
We should create a setup script that allows people to test their changes locally before pushing.

Running all the tests in a row would be really useful. Currently it is quite redundant

authors: Aursen acheroncrypto

repo: coral-xyz/anchor


text:
🛑 Guangdianyun Consoles is down

In 8edfe9e, Guangdianyun Consoles (https://consoles.guangdianyun.tv) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Guangdianyun Consoles is back up in fd7e878.

repo: corcd/charlotte


text:
Add udev rules for Azure disks

Fixes: https://github.com/coreos/bugs/issues/2481
This change allows to use proper Azure disk paths in ignition.

The linked issue mentions AWS, too.  Does this also need to add 90-cloud-storage.rules?

If we pull in the aws rules we also need to pull in the helper script (which is fine). I'm fine taking this with or without the AWS fix (but leave the bug open if we don't include the AWS rules).

I didn't check if all the utilies needed by the AWS script are in the initramfs. I'd say we land this to unblock @r7vme and then we check if there other bits we should pull in too.

Okay, then I'll merge it as is.
@r7vme This also needs to be updated in the coreos-overlay repo to be included in the OS.  If you'd like to do it, the process is to take the latest commit ID in bootengine's master branch and update sys-kernel/bootengine in the overlay with it, then bump the symlink's version number.  See its Git log for details.

repo: coreos/bootengine


text:
Add development docs and improve Makefile usability

Add docs on development  loop, requirements, and how to validate basic functionality (#90)
Makefile targets

build/build-image.sh currently builds a binary, builds an image, and pushes the image behind make image. Add Makefile targets for each step individually to make development easier (open to different naming):
make release-bin - Builds update-operator and update-agent inside the build image for repeatability
make image - Builds the docker image
make docker-push - Pushes the docker image (including to a developer's Quay account)

Fixes #92 where scripts assumed sudo-less docker was allowed on the developer's machine

Added ^

repo: coreos/container-linux-update-operator


text:
kube-aws: instance names should be prefixed (or postfixed) with cluster name

Monitoring EC2 is a mess when every instance is named "kube-aws-worker".

Related: https://github.com/coreos/coreos-kubernetes/issues/221

@cgag @aaronlevy I have submitted the PR https://github.com/coreos/coreos-kubernetes/pull/435 for this. Would you mind reviewing it?

authors: aaronlevy cgag mumoshu

repo: coreos/coreos-kubernetes


text:
jenkins: Can't access GCE node internal IP from pod

Our migration tests on jenkins are now failing consistently. Digging into the problem, it seems that k8s pod couldn't access IP of nodes.
In migration test, we use GetDefaultHost(), which returns internal IP "10.240.0.x". Then we use it as network interface that etcd binds to. But etcd operator was trying to do migrate, it failed:
grpc: time out when dialing

I test it by running an etcd server locally:
etcd --listen-peer-urls 'http://10.240.0.7:12380' --listen-client-urls 'http://10.240.0.7:12379' --initial-advertise-peer-urls http://10.240.0.7:12380 --advertise-client-urls http://10.240.0.7:12379 --initial-cluster 'boot=http://10.240.0.7:12380' --name boot

Then create a pod to contact it:
kubectl run --rm -i --tty fun --image quay.io/coreos/etcd --restart=Never -- /bin/sh
/ # ETCDCTL_API=3 etcdctl --endpoints http://10.240.0.7:12379 get foo
Error:  grpc: timed out when dialing

It also turns out to be inaccessible.

@xiang90
I rethink about the network assumptions made in e2e test, and come up with ideas to get rid of those assumptions to make test simpler and more generic.
1. migrate boot member
It requires an IP address that's accessible from within k8s cluster. Other than that, we don't really care where it's running, as long as it's an etcd server and will get migrated successfully.
Why don't we just create a pod for it? Conceptually, it's just another service that we can access matching exactly what we did now.
2. make backup
In disaster recovery test, we don't need to assume service IP is accessible on test machine as in: https://github.com/coreos/etcd-operator/blob/50c140012bc4a24342bf49b76e0c58d223fc7db4/test/e2e/util.go#L59-L62
Because we are already using the http client inside kube client, we can actually use it to access the known backup service directly.

The proposal wont solve all problems I am afraid.
Yes, we can run the boot member in pod, but not the actual self-hosted members. We do want to test self-hosted features which should run on host network.
I do not want to make stuff complicated now. I think we can:

run jenkins jobs sequentially
do not run anything other than CI on jenkins slaves

For 2, yea, it does not really matters.

Digging into the problem, it seems that k8s pod couldn't access IP of nodes.

Do we know why? It should be able to access.

Do we know why? It should be able to access.

No idea. It was still OK yesterday.

Yes, we can run the boot member in pod, but not the actual self-hosted members.

It's just boot member. So you agree on this too?

No idea. It was still OK yesterday.

We should figure this out.

It's just boot member. So you agree on this too?

I mean we can. But why we need to?

We need to fix the test.
Currently it's failing all the time.
Changing it to pod will also make it simpler and more generic, e.g. we don't need to set up kubelet/proxy on test machine anymore.

Changing it to pod will also make it simpler and more generic, e.g. we don't need to set up kubelet/proxy on test machine anymore.

I do not understand. Right now, we start etcd boot member on local network. It does not rely on k8s network. I do not think it has anything to do with kubelet/proxy.
Also I do not understand why it is simper and more generic.

We need to fix the test.
Currently it's failing all the time.

How will move the boot member into pod fix the problem? We need to fix this:
pod should be able to access node ip

We start an pod as a single etcd server.
We take it as boot member, and get uses its Pod IP to form bootMemberClientEndpoint.

I do not understand. Right now, we start etcd boot member on local network. It does not rely on k8s network. I do not think it has anything to do with kubelet/proxy.

It needs proxy because it needs to talk to migrated cluster before being removed off membership.
It's simpler because e2e test infra doesn't need to assume test machine needs to setup kubelet/proxy anymore.

We start an pod as a single etcd server.
We take it as boot member, and get uses its Pod IP to form bootMemberClientEndpoint.

Why do we need to do this? What exactly problem can this solve?

It needs proxy because it needs to talk to migrated cluster before being removed off membership.

No, it does not need. migrated member is on host network.

Why do we need to do this? What exactly problem can this solve?
master is failing now.
The failure is caused by network issue talking to test machine IP.

The failure is caused by network issue talking to test machine IP.

Right. Fix this.

All right.
I have fixed it.
It's firewall issue. Not sure why it works before though.

Can we close this issue then?

Verified it's fixed.

The second point (make backup) isn't true

repo: coreos/etcd-operator


text:
etcd elections result in "too many open files"

https://gist.github.com/temujin9/88497a9c6fe5ab863808 happened, ultimately resulting in a cluster where all etcd processes had failed.

@temujin9 This is not caused by leader election. The leader election is caused by the fd problem.
So I am wondering what is the cause of fd problem? Are you having a lot of clients?

No, this was a three node test cluster for flynn.io, with one client application running (with almost no usage). Nothing about its usage would suggest a natural reason to run out of fds.

For reference, each node in the Flynn cluster should have exactly two watch connections, each to the local etcd instance.

@temujin9 @titanous Can you please list the fds etcd are using when run out of fds and post it here?
Or can you tell me how to reproduce the issue by using etcd and a simple client?
Thanks.

@temujin9 @titanous Any update on this issue?

We updated Flynn to the release version of etcd v2 yesterday, and haven't gotten any new reports. So far have not been able to track a fd-exhausted instance that was still up to get the fd list.

@titanous We have added fd/runtime metrics into etcd. Hopefully this will make detect this issue easier.

@temujin9 @titanous I am closing this due to inactivity. Reopen if you find this problem again with the log for us to investigate. Thanks for reporting.

repo: coreos/etcd


text:
Always "Internal Server Error"

I'm using etcd 2.0 release version and set up a 5 instances cluster by DNS record discovery.
My services use etcd to do server discovery and heartbeating, about 20 instances sending requests to etcd every 5s.
Each time the request the service sending are:

PUT new values with ttl to two files (In different directory)
Update ttl to an existed directory
And each service watching for a directory to get notified when change happened. TTL update changes are filtered by client.

That's all my scenarios, and I'm keeping receive "Internal Service Error" From etcd when PUT new value or update ttl with no X-Etcd-Index header and no related logs I found in etcd log. The interval between each errors could be smaller than 1s or larger than 10 hour.
I just cannot figured out what's happening, could you guys take a look at this?
More details, the put/update path looks like:
Dir: /v2/keys/service/mongodb/cluster/bj/instance/mongo0
File: /v2/keys/service/mongodb/cluster/bj/instance/mongo0/registry
File:/v2/keys/routing/mongo0-bj
Both of these nodes has a ttl equals 15s. The value of registry is quite small, just { "host": "1234xxx" }
And all 5 etcd instances are in one local network connected through 1000Mbps ethernet network, the ping latency among these instances is smaller than 1ms.
Any response is appreciated.

@snowdreamist Can you please provide etcd log? Are you seeing raft term increase? Did leader election happen?
Can you try to reproduce the problem with a simple setup. We can help you debug the problem with log or more detailed information.

of course, I'll record related info in 1 or 2 days. @xiang90

OK, I got a piece of log may related to this error:
2015/02/10 19:45:17 raft: b3cf14a3ff886f6e [term: 7] received a MsgVote message with higher term from 4d18ffbde916ed55 [term: 8]
2015/02/10 19:45:17 raft: b3cf14a3ff886f6e became follower at term 8
2015/02/10 19:45:17 raft: b3cf14a3ff886f6e [logterm: 7, index: 610357, vote: 0] voted for 4d18ffbde916ed55 [logterm: 7, index: 610357] at term 8
2015/02/10 19:45:17 raft.node: b3cf14a3ff886f6e lost leader a607f655c64595cc at term 8
2015/02/10 19:45:17 raft.node: b3cf14a3ff886f6e elected leader 4d18ffbde916ed55 at term 8
2015/02/10 19:45:17 sender: the connection with a607f655c64595cc becomes active
2015/02/10 19:45:17 rafthttp: starting client stream to 4d18ffbde916ed55 at term 8
2015/02/10 19:45:22 etcdhttp: unexpected error: etcdserver: request timed out
2015/02/10 19:45:23 etcdhttp: unexpected error: etcdserver: request timed out
2015/02/10 19:45:23 etcdhttp: unexpected error: etcdserver: request timed out
2015/02/10 20:07:39 etcdserver: start to snapshot (applied: 620132, lastsnap: 610127)
2015/02/10 20:07:39 etcdserver: compacted log at index 620132
2015/02/10 20:07:39 etcdserver: saved snapshot at index 620132
2015/02/10 20:07:52 filePurge: successfully removed file /var/lib/etcd/default.etcd/wal/0000000000000039-000000000008b307.wal
2015/02/10 20:07:52 filePurge: successfully removed file /var/lib/etcd/default.etcd/snap/0000000000000007-000000000008b306.snap
And the ts exactly match the error log of our service log's ts.
@xiang90

@snowdreamist
2015/02/10 19:45:17 rafthttp: starting client stream to 4d18ffbde916ed55 at term 8

There is a leader election happened at 19:45:17.
2015/02/10 19:45:22 etcdhttp: unexpected error: etcdserver: request timed out
2015/02/10 19:45:23 etcdhttp: unexpected error: etcdserver: request timed out
2015/02/10 19:45:23 etcdhttp: unexpected error: etcdserver: request timed out

There are three timeout happened after around 5 seconds.
There might be proposal during leader election. And the proposal waiting timeout is around 5 seconds.
I highly suspect that the timeout is caused by the leader lost.
So you need to find out if the leader election is expected. Was the leader machine down for a while? Was there a network problem? Or the leader machine was slow for a while?

@snowdreamist In the future, we might improve this by buffering proposals and trying to resend them if they are lost due to leader lost.

Thanks for reply! I'll take a look at the server log.
By the way, I found our DNS server (bind9) is somehow unstable, and I use domain name instead of IP address in the SRV record for setting up etcd cluster. Will it affect etcd?
And when will an etcd node notice that the leader is lost? Heart beat timed out?
@xiang90

@snowdreamist In Raft Protocol, the leader must send heartbeats(empty AppendEntries RPCs) to maintain the authority, if the electionTimeout elapses with no RPCs, the follower will assume that the leader crashes. Hope this will help you...

@snowdreamist I am closing this. Reopen if you have any follow up.

I haven't found why internal error still always happened, I can't be sure if it is a network issue or not. Bug the connections between services and mongodb instances is pretty stable.
And I found another issue, if the internal server error happened, etcd may block the connection forever.

etcd may block the connection forever.

We are solving this.
/cc @yichengq

@snowdreamist Do you have more detailed context, or TCP status at that time, or log for the block issue?
From your description, I think it is more reasonable to say that the block of the connection causes the internal server error.

authors: AdoHe snowdreamist xiang90 yichengq


text:
etcdserver/api/rafthttp: clarify "became inactive" warning

"became inactive" is not a clear warning, when what's actually happening is failure to send HTTP requests.

Codecov Report

Merging #10024 into master will decrease coverage by 0.23%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master   #10024      +/-   ##
==========================================
- Coverage   69.37%   69.13%   -0.24%
==========================================
  Files         386      386
  Lines       36057    36060       +3
==========================================
- Hits        25013    24930      -83
- Misses       9243     9338      +95
+ Partials     1801     1792       -9

Impacted Files
Coverage Δ

etcdserver/api/rafthttp/peer_status.go
89.47% <100%> (ø)
:arrow_up:

etcdserver/api/v3rpc/interceptor.go
39.47% <0%> (-57.85%)
:arrow_down:

clientv3/balancer/grpc1.7-health.go
46.22% <0%> (-12.8%)
:arrow_down:

proxy/grpcproxy/register.go
69.44% <0%> (-11.12%)
:arrow_down:

pkg/netutil/netutil.go
63.11% <0%> (-6.56%)
:arrow_down:

proxy/grpcproxy/watcher.go
85.71% <0%> (-4.09%)
:arrow_down:

proxy/httpproxy/director.go
80% <0%> (-2.86%)
:arrow_down:

clientv3/concurrency/election.go
79.52% <0%> (-2.37%)
:arrow_down:

etcdserver/api/v3rpc/watch.go
73.52% <0%> (-2.29%)
:arrow_down:

integration/bridge.go
70.22% <0%> (-1.53%)
:arrow_down:

... and 17 more

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 6890a9e...156ff64. Read the comment docs.

authors: codecov-io gyuho


text:
tools/etcd-dump-*: add TODOs, --decode flag

Helpful when debugging issues like https://github.com/coreos/etcd/pull/9031. And take data directory as an argument rather than flag (less typing).
Also add TODO for https://github.com/coreos/etcd/issues/7620.
etcd-dump-db iterate-bucket ./agent-1/etcd.data/ lease --decode
lease ID=5f3b606ba41b115a, TTL=120s
lease ID=5f3b606ba41b1158, TTL=120s
lease ID=5f3b606ba41b1156, TTL=120s
lease ID=5f3b606ba41b1154, TTL=120s
lease ID=5f3b606ba41b1152, TTL=120s

etcd-dump-db iterate-bucket ./agent-1/etcd.data/ key --decode
rev={main:6984 sub:0}, value=[key "foo000000000003ccd8" | val "aaa" | created 6984 | mod 6984 | ver 1]
rev={main:6983 sub:0}, value=[key "foo00000000000004f3" | val "aaa" | created 6983 | mod 6983 | ver 1]
rev={main:6982 sub:0}, value=[key "foo000000000002eaee" | val "aaa" | created 6982 | mod 6982 | ver 1]

/cc @jpbetz

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a7445d7). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #9041   +/-   ##
=========================================
  Coverage          ?   76.08%
=========================================
  Files             ?      359
  Lines             ?    29838
  Branches          ?        0
=========================================
  Hits              ?    22701
  Misses            ?     5562
  Partials          ?     1575

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 a7445d7...931dfd7. Read the comment docs.

@jpbetz can you please take a look?

authors: codecov-io gyuho xiang90


text:
secure metrics port for scheduler and controller-manager

fixes https://github.com/coreos/kube-prometheus/issues/443
tested with 1.17.9 kubeadm cluster, after kubeadm upgrade disabled the insecure metrics port for scheduler+controller.
also changed the ports for other cluster-types, but i can't really say if the secure port is provided on those platforms.

Very nice!
This needs a re-generate via make generate, and the port name should probably now be https-metrics.

Thank you! lgtm :tada:

authors: brancz tafkam

repo: coreos/kube-prometheus


text:
FAIL: TestNonRootFetchRmGCImage: permission denied, are you root or the owner of the image?

=== RUN   TestNonRootFetchRmGCImage
--- FAIL: TestNonRootFetchRmGCImage (3.04s)
	rkt_non_root_test.go:114: Running /home/runner/rkt/builds/build-rkt-src-v222/build-rkt-1.1.0+git/tmp/functional/rkt --dir=/tmp/datadir-286405353 --local-config=/tmp/localdir-233653044 --system-config=/tmp/systemdir-381948163 image gc
	rkt_non_root_test.go:119: Running /home/runner/rkt/builds/build-rkt-src-v222/build-rkt-1.1.0+git/tmp/functional/rkt --dir=/tmp/datadir-286405353 --local-config=/tmp/localdir-233653044 --system-config=/tmp/systemdir-381948163 image rm sha512-1e1f38f2e986a4cf07a2d5aba53405a0
	rkt_non_root_test.go:128: Running /home/runner/rkt/builds/build-rkt-src-v222/build-rkt-1.1.0+git/tmp/functional/rkt --dir=/tmp/datadir-286405353 --local-config=/tmp/localdir-233653044 --system-config=/tmp/systemdir-381948163 image rm sha512-9ac6a413f73dee17b64224927c6da704
	rkt_tests.go:300: didn't receive expected output "successfully removed": rm: error removing aci for image "sha512-9ac6a413f73dee17b64224927c6da7045a67183a8fe80fac9ab4fc195e606ba2" ("coreos.com/rkt-inspect"): permission denied, are you root or the owner of the image?

		rm: 1 image(s) cannot be removed

		rm: error(s) found while removing images

	rkt_tests.go:138: rkt terminated with unexpected status 1, expected 0
		Output:

It happened one time to me, see:
https://semaphoreci.com/coreos/rkt/branches/pull-request-2286/builds/1
@iaguis suspects a setgid goroutine leak. @krnowak suggested to compile every test as a separate binary.

Comical
On Wed, Mar 16, 2016 at 2:40 PM Alban Crequy notifications@github.com
wrote:

=== RUN   TestNonRootFetchRmGCImage
--- FAIL: TestNonRootFetchRmGCImage (3.04s)
rkt_non_root_test.go:114: Running /home/runner/rkt/builds/build-rkt-src-v222/build-rkt-1.1.0+git/tmp/functional/rkt --dir=/tmp/datadir-286405353 --local-config=/tmp/localdir-233653044 --system-config=/tmp/systemdir-381948163 image gc
rkt_non_root_test.go:119: Running /home/runner/rkt/builds/build-rkt-src-v222/build-rkt-1.1.0+git/tmp/functional/rkt --dir=/tmp/datadir-286405353 --local-config=/tmp/localdir-233653044 --system-config=/tmp/systemdir-381948163 image rm sha512-1e1f38f2e986a4cf07a2d5aba53405a0
rkt_non_root_test.go:128: Running /home/runner/rkt/builds/build-rkt-src-v222/build-rkt-1.1.0+git/tmp/functional/rkt --dir=/tmp/datadir-286405353 --local-config=/tmp/localdir-233653044 --system-config=/tmp/systemdir-381948163 image rm sha512-9ac6a413f73dee17b64224927c6da704
rkt_tests.go:300: didn't receive expected output "successfully removed": rm: error removing aci for image "sha512-9ac6a413f73dee17b64224927c6da7045a67183a8fe80fac9ab4fc195e606ba2" ("coreos.com/rkt-inspect"): permission denied, are you root or the owner of the image?
    rm: 1 image(s) cannot be removed

    rm: error(s) found while removing images

rkt_tests.go:138: rkt terminated with unexpected status 1, expected 0
    Output:

It happened one time to me, see:
https://semaphoreci.com/coreos/rkt/branches/pull-request-2286/builds/1
@iaguis https://github.com/iaguis suspects a setgid goroutine leak.
@krnowak https://github.com/krnowak suggested to compile every test as
a separate binary.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/coreos/rkt/issues/2287

Komisch

Komiczne

This happened again on Fedora-Rawhide with the host flavor.

and again on seamphore

Yeah, we should print the gids..

Yeah, we should print the gids..

So maybe we should just merge https://github.com/coreos/rkt/pull/2805?

@dgonyeo caught this today:
=== RUN   TestNonRootFetchRmGCImage
--- FAIL: TestNonRootFetchRmGCImage (6.77s)
    rkt_non_root_test.go:115: Running /home/runner/rkt/builds/build-rkt-kvm/build-rkt-1.8.0+git/tmp/functional/rkt --dir=/tmp/datadir-775069046 --local-config=/tmp/localdir-541324893 --system-config=/tmp/systemdir-052462616 --user-config=/tmp/userdir-074739351 image gc
    rkt_non_root_test.go:120: Running /home/runner/rkt/builds/build-rkt-kvm/build-rkt-1.8.0+git/tmp/functional/rkt --dir=/tmp/datadir-775069046 --local-config=/tmp/localdir-541324893 --system-config=/tmp/systemdir-052462616 --user-config=/tmp/userdir-074739351 image rm sha512-0aef5d84bc6b4d21e7bd3445f3ef4fe6
    rkt_non_root_test.go:129: Running /home/runner/rkt/builds/build-rkt-kvm/build-rkt-1.8.0+git/tmp/functional/rkt --dir=/tmp/datadir-775069046 --local-config=/tmp/localdir-541324893 --system-config=/tmp/systemdir-052462616 --user-config=/tmp/userdir-074739351 image rm sha512-0ac4a14f6a32a6a7744fff954d87a4bb
    rkt_tests.go:320: didn't receive expected output "successfully removed": rm: error removing aci for image "sha512-0ac4a14f6a32a6a7744fff954d87a4bbbdab8aa863a96089f047109e9f560b5a" ("coreos.com/rkt-inspect"): permission denied on /tmp/datadir-775069046/cas/blob/sha512/0a, directory owner id (0) does not match current real id (65534). Are you root or the owner of the image?

        rm: 1 image(s) cannot be removed

        rm: error(s) found while removing images

    rkt_tests.go:140: rkt terminated with unexpected status 1, expected 0
        Output:

So I think the reason is the hash of the image fetched by root has the same prefix as the hash of the image fetched by nobody, so the image both ends up in /tmp/datadir-775069046/cas/blob/sha512/0a, and this directory has the UID = root.
I recalled this problem has been mentioned somewhere before.

authors: alban iaguis jonboulle krnowak s-urbaniak yifan-gu

repo: coreos/rkt


text:
docs: update policy to include signed releases

Signed-off-by: Felipe Zipitria felipe.zipitria@owasp.org

Update security policy to include release verification
Add pointer to the sandbox to verify bypasses

This is written in a very clear way and I do not have any comments. (Yet I did not try out the commands).
Thank you very much. LGTM.

repo: coreruleset/coreruleset


text:
Rendering improvements

Improves a number of rendering issues, including:

Dynamic lights now only show on surfaces "facing" the light source (i.e., surfaces whose normals have a negative dot product with the direction vector from the light to the surface). Dynamic lights still do not have shadows, however.
Lightmap calculations have been simplified to remove the 8.8 fixed-point math. Surfaces with multiple lightmaps have each lightmap written to a separate channel of the light target.
brush::TextureKind is now uploaded using push constants rather than a dynamic uniform buffer.
Animated brush textures now work. Alternate animations are still forthcoming.
The crosshair has been offset slightly to more accurately reflect the direction of projectiles. This is not a totally solvable problem due to limited precision with which Quake sends angles over the network.

bors r+

repo: cormac-obrien/richter


text:
Is there any option to change the color of marks which are drawn by tools like length, textmarker?

Prerequisites

[x] Which version are you using? (Is it latest?)
[x] Are you reporting to the correct repository?
[ ] Did you search existing issues? (Were any related?)

Description
I need to change the color of the marks which are drawn by tools.
CodeSandbox With Reproduction of Issue:

Basic Template

+1

Take a look at the methods available in stateManagement/toolColors.js
These are exposed as top level api on the cornerstoneTools.toolColors object so you can do something like this.
import  cornerstoneTools from 'cornerstone-tools';

cornerstoneTools.toolColors.setToolColor('red');
cornerstoneTools.toolColors.setActiveColor('hsl(288deg 100% 63%)');

You can use any color value that you would use in html or css - so named colors, hex colors or rgb, hsl etc. should all work.

Oh, thank you very much for your replay. I'll try that.

The cornerstonetool 4.0 version I use has a color attribute when the tool is defined, which supports self-definition.

authors: QeassureGitHub mikehazell sequba xiaozhidave

repo: cornerstonejs/cornerstoneTools


text:
UI partially not updating when exposure check is run in the foreground

Avoid duplicates

[x] Bug is not mentioned in the FAQ
[x] Bug is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
[x] Bug is not already reported in another issue

Describe the bug

The "Updated: Today, 06:33" part of the risk card on the main view does not update, when the exposure check is run in the foreground, i.e. when an update was not done in the last ~24 hours and the user opens the app, so that the exposure check is manually triggered.
I opened the app this morning, the check ran (visible in the UI), and afterwards the first two lines of the risk card updated correctly (in the first line, the number of exposures went up from 1 to 2 for me today; in the second line it read "Exposure logging permanently active" again after the check). In the third line, it still read "Updated: Yesterday, [time]" Closing and reopening the app updated the UI, so that it read "Updated: Today, 06:33". I noticed the same bug yesterday.
Expected behaviour

The "Updated" part of the UI should update immediately after the check is run in the foreground, as the other parts of the UI apparently do.
Steps to reproduce the issue

Put the app in a condition, where it needs to do a manual run of the exposure check.
Open the app.
Let the exposure check run.

Technical details

Mobile device: Samsung Galaxy S10
Android version: Android 10

Possible Fix

Additional context

@crcsn
Your problems sounds very similar to https://github.com/corona-warn-app/cwa-app-android/issues/1081
In particular

The mainView/risk card is not completely refreshed
Internal Tracking ID: EXPOSUREAPP-2795

Do you agree? If so feel free to close this issue here and move the discussion over to https://github.com/corona-warn-app/cwa-app-android/issues/1081 🙂.

@daimpi
true, that is indeed the same issue (EXPOSUREAPP-2795) that is supposed to be discussed in the #1081
Will close this.

@crcsn no worries… it's hard to find the right one among the the plethora of issues 😅.

authors: crcsn daimpi

repo: corona-warn-app/cwa-app-android


text:
Update Risk Score more than once a day (EXPOSUREAPP-3455)

Use a hybrid approach of day and hour key packages to provide risk score updates as often as the quota allows.

Change the download mechanisms to the new download & sync behavior.
Smarter timeout behavior that times out individual downloads to allow proceeding with subsets before the global timeout hits.
Allow cache invalidation via protobuf config.
Allow custom timeouts via protobuf config.
Download day packages on any type of connection, hourly packages only on metered.
New test fragment

TODO

[x] Finish tests
[x] Finish test menu
[x] Merge #1545 into release/1.7.x first

Out of scope

New error card for the home screen that shows (EXPOSUREAPP-3411)

Testing

Smoke test & Check logs
Check unit tests for edge cases (package de.rki.coronawarnapp.diagnosiskeys)
Compare against requirements

Spotted an app crash on start with a clean install:
2020-11-12 19:00:38.739 9323-9379/de.rki.coronawarnapp.test V/OkHttp: <-- HTTP FAILED: de.rki.coronawarnapp.exception.http.NotFoundException: error during web request, http status 404
2020-11-12 19:00:38.741 9323-9366/de.rki.coronawarnapp.test W/AppConfigRetriever: Failed to download AppConfig from server .
    de.rki.coronawarnapp.exception.http.NotFoundException: error during web request, http status 404
        at de.rki.coronawarnapp.http.HttpErrorParser.intercept(HttpErrorParser.kt:44)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
        at de.rki.coronawarnapp.http.interceptor.RetryInterceptor.intercept(RetryInterceptor.kt:15)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
        at okhttp3.logging.HttpLoggingInterceptor.intercept(HttpLoggingInterceptor.kt:221)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
        at de.rki.coronawarnapp.http.interceptor.WebSecurityVerificationInterceptor.intercept(WebSecurityVerificationInterceptor.kt:11)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
        at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
        at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:517)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:764)
2020-11-12 19:00:38.741 9323-9366/de.rki.coronawarnapp.test V/AppConfigStorage: get() AppConfig
2020-11-12 19:00:38.742 9323-9366/de.rki.coronawarnapp.test E/AppConfigStorage: Couldn't load config.
    java.io.FileNotFoundException: /data/user/0/de.rki.coronawarnapp.test/files/appconfig_storage/appconfig.json (No such file or directory)
        at java.io.FileInputStream.open0(Native Method)
        at java.io.FileInputStream.open(FileInputStream.java:231)
        at java.io.FileInputStream.<init>(FileInputStream.java:165)
        at de.rki.coronawarnapp.appconfig.download.AppConfigStorage.getStoredConfig(AppConfigStorage.kt:97)
        at de.rki.coronawarnapp.appconfig.AppConfigSource$retrieveConfig$2.invokeSuspend(AppConfigSource.kt:49)
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
        at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
        at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:738)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)
```

As aligned with @d4rken this will be fixed with https://github.com/corona-warn-app/cwa-app-android/pull/1553 !

Went on WRU-XD to the new test menu, enabled Hourly okg on metered netowrks, clicked on Download and the app crashed
2020-11-12 19:32:07.561 14442-14592/de.rki.coronawarnapp.test V/AppConfigStorage: Overwriting 426 from 1605205927000
2020-11-12 19:32:07.564 14442-14481/de.rki.coronawarnapp.test D/KeySync:HourSync: No invalid files to delete.
2020-11-12 19:32:07.571 14442-14488/de.rki.coronawarnapp.test V/OkHttp: --> GET <ENDPOINT>/version/v1/diagnosis-keys/country/EUR/date/2020-11-12/hour
2020-11-12 19:32:07.572 14442-14488/de.rki.coronawarnapp.test V/OkHttp: --> END GET
2020-11-12 19:32:07.722 14442-14488/de.rki.coronawarnapp.test V/OkHttp: <-- HTTP FAILED: de.rki.coronawarnapp.exception.http.NotFoundException: error during web request, http status 404
2020-11-12 19:32:07.742 1687-3390/system_process W/ActivityManager:   Force finishing activity de.rki.coronawarnapp.test/de.rki.coronawarnapp.ui.main.MainActivity
2020-11-12 19:32:07.758 14442-14466/de.rki.coronawarnapp.test I/Process: Sending signal. PID: 14442 SIG: 9
2020-11-12 19:32:07.907 1687-1916/system_process W/InputDispatcher: channel '2f9a4cb de.rki.coronawarnapp.test/de.rki.coronawarnapp.ui.main.MainActivity (server)' ~ Consumer closed input channel or an error occurred.  events=0x9
2020-11-12 19:32:07.907 1687-1916/system_process E/InputDispatcher: channel '2f9a4cb de.rki.coronawarnapp.test/de.rki.coronawarnapp.ui.main.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed!

Also happens when the Hourly pkg on metered networks is disabled:
2020-11-12 19:35:01.199 15349-15402/de.rki.coronawarnapp.test D/KeySync:HourSync: No invalid files to delete.
2020-11-12 19:35:01.202 15349-15434/de.rki.coronawarnapp.test V/OkHttp: --> GET <ENDPOINT>/version/v1/diagnosis-keys/country/EUR/date/2020-11-12/hour
2020-11-12 19:35:01.202 15349-15434/de.rki.coronawarnapp.test V/OkHttp: --> END GET
2020-11-12 19:35:01.325 15349-15434/de.rki.coronawarnapp.test V/OkHttp: <-- HTTP FAILED: de.rki.coronawarnapp.exception.http.NotFoundException: error during web request, http status 404
2020-11-12 19:35:01.327 15349-15402/de.rki.coronawarnapp.test E/DownloadDiagnosisKeysTask: de.rki.coronawarnapp.exception.http.NotFoundException: error during web request, http status 404
        at de.rki.coronawarnapp.http.HttpErrorParser.intercept(HttpErrorParser.kt:44)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
        at de.rki.coronawarnapp.http.interceptor.RetryInterceptor.intercept(RetryInterceptor.kt:15)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
        at okhttp3.logging.HttpLoggingInterceptor.intercept(HttpLoggingInterceptor.kt:221)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
        at de.rki.coronawarnapp.http.interceptor.WebSecurityVerificationInterceptor.intercept(WebSecurityVerificationInterceptor.kt:11)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
        at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
        at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:517)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:764)
2020-11-12 19:35:01.328 15349-15402/de.rki.coronawarnapp.test D/DownloadDiagnosisKeysTask: Initiate Rollback
2020-11-12 19:35:01.339 15349-15402/de.rki.coronawarnapp.test I/DownloadDiagnosisKeysTask: Finished (isCanceled=false).
2020-11-12 19:35:01.340 15349-15402/de.rki.coronawarnapp.test D/TaskController: Task ended: InternalTaskState(id=d04652bf-ccb3-4012-a2d6-3a1b4d003acd, request=DefaultTaskRequest(type=class de.rki.coronawarnapp.diagnosiskeys.download.DownloadDiagnosisKeysTask (Kotlin reflection is not available), arguments=de.rki.coronawarnapp.diagnosiskeys.download.DownloadDiagnosisKeysTask$Arguments@4e4e04c, id=b5e8bd36-4b43-4fab-989c-6200e745ec7b), createdAt=2020-11-12T18:35:00.399Z, startedAt=null, finishedAt=null, error=null, result=null, config=Config(executionTimeout=PT480S, collisionBehavior=ENQUEUE), job="coroutine#99":LazyDeferredCoroutine{Cancelled}@428b1ad, task=de.rki.coronawarnapp.diagnosiskeys.download.DownloadDiagnosisKeysTask@4448ce2)
2020-11-12 19:35:01.342 15349-15402/de.rki.coronawarnapp.test D/TaskController: Processing task data (count=2)
2020-11-12 19:35:01.343 15349-15402/de.rki.coronawarnapp.test V/TaskController: Tasks before processing: [InternalTaskState(id=26167883-4eac-4273-b4c0-8905fa340c1d, request=DefaultTaskRequest(type=class de.rki.coronawarnapp.diagnosiskeys.download.DownloadDiagnosisKeysTask (Kotlin reflection is not available), arguments=de.rki.coronawarnapp.diagnosiskeys.download.DownloadDiagnosisKeysTask$Arguments@78d516f, id=b03a7fb5-6d9d-4cfd-b7ac-05dcf2357be5), createdAt=2020-11-12T18:34:59.802Z, startedAt=2020-11-12T18:34:59.811Z, finishedAt=2020-11-12T18:35:00.929Z, error=de.rki.coronawarnapp.exception.http.NotFoundException: error during web request, http status 404, result=null, config=Config(executionTimeout=PT480S, collisionBehavior=ENQUEUE), job="coroutine#11":LazyDeferredCoroutine{Cancelled}@f314a73, task=de.rki.coronawarnapp.diagnosiskeys.download.DownloadDiagnosisKeysTask@49ded30), InternalTaskState(id=d04652bf-ccb3-4012-a2d6-3a1b4d003acd, request=DefaultTaskRequest(type=class de.rki.coronawarnapp.diagnosiskeys.download.DownloadDiagnosisKeysTask (Kotlin reflection is not available), arguments=de.rki.coronawarnapp.diagnosiskeys.download.DownloadDiagnosisKeysTask$Arguments@4e4e04c, id=b5e8bd36-4b43-4fab-989c-6200e745ec7b), createdAt=2020-11-12T18:35:00.399Z, startedAt=2020-11-12T18:35:00.932Z, finishedAt=null, error=null, result=null, config=Config(executionTimeout=PT480S, collisionBehavior=ENQUEUE), job="coroutine#99":LazyDeferredCoroutine{Cancelled}@428b1ad, task=de.rki.coronawarnapp.diagnosiskeys.download.DownloadDiagnosisKeysTask@4448ce2)]
2020-11-12 19:35:01.345 15349-15402/de.rki.coronawarnapp.test E/TaskController: Task failed: InternalTaskState(id=d04652bf-ccb3-4012-a2d6-3a1b4d003acd, request=DefaultTaskRequest(type=class de.rki.coronawarnapp.diagnosiskeys.download.DownloadDiagnosisKeysTask (Kotlin reflection is not available), arguments=de.rki.coronawarnapp.diagnosiskeys.download.DownloadDiagnosisKeysTask$Arguments@4e4e04c, id=b5e8bd36-4b43-4fab-989c-6200e745ec7b), createdAt=2020-11-12T18:35:00.399Z, startedAt=2020-11-12T18:35:00.932Z, finishedAt=null, error=null, result=null, config=Config(executionTimeout=PT480S, collisionBehavior=ENQUEUE), job="coroutine#99":LazyDeferredCoroutine{Cancelled}@428b1ad, task=de.rki.coronawarnapp.diagnosiskeys.download.DownloadDiagnosisKeysTask@4448ce2)
    de.rki.coronawarnapp.exception.http.NotFoundException: error during web request, http status 404
        at de.rki.coronawarnapp.http.HttpErrorParser.intercept(HttpErrorParser.kt:44)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
        at de.rki.coronawarnapp.http.interceptor.RetryInterceptor.intercept(RetryInterceptor.kt:15)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
        at okhttp3.logging.HttpLoggingInterceptor.intercept(HttpLoggingInterceptor.kt:221)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
        at de.rki.coronawarnapp.http.interceptor.WebSecurityVerificationInterceptor.intercept(WebSecurityVerificationInterceptor.kt:11)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
        at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
        at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:517)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:764)

c31937b3d63d6ec189dc0bc512e783f7e1ff75b9 doesn't compile for me:
failed
:Corona-Warn-App:compileDeviceForTestersDebugKotlin
Corona-Warn-App/build/generated/source/navigation-args/deviceForTesters/debug/de/rki/coronawarnapp/test/crash/ui/SettingsCrashReportFragmentDirections.kt
Unresolved reference: action_crashReportFragment_to_settingsCrashReportDetailsFragment
Corona-Warn-App/build/generated/source/navigation-args/deviceForTesters/debug/de/rki/coronawarnapp/test/menu/ui/TestMenuFragmentDirections.kt
Unresolved reference: action_testMenuFragment_to_settingsCrashReportFragment
Unresolved reference: action_test_menu_fragment_to_appConfigTestFragment
Unresolved reference: action_test_menu_fragment_to_debugOptionsFragment
Unresolved reference: action_test_menu_fragment_to_keyDownloadTestFragment
Corona-Warn-App/src/deviceForTesters/java/de/rki/coronawarnapp/test/appconfig/ui/AppConfigTestFragment.kt
Unresolved reference: test_appconfig_fragment
Corona-Warn-App/src/deviceForTesters/java/de/rki/coronawarnapp/test/crash.ui/SettingsCrashReportFragment.kt
Unresolved reference: action_testMenuFragment_to_settingsCrashReportFragment
Corona-Warn-App/src/deviceForTesters/java/de/rki/coronawarnapp/test/debugoptions/ui/DebugOptionsFragment.kt
Unresolved reference: test_debugoptions_fragment
Corona-Warn-App/src/deviceForTesters/java/de/rki/coronawarnapp/test/keydownload/ui/KeyDownloadTestFragment.kt
Unresolved reference: test_keydownload_fragment
Compilation error

When I run c31937b3d63d6ec189dc0bc512e783f7e1ff75b9 against my local CWA server, after an initial download of all available data, moving the app to background, and opening again, I see the following requests immediately:

/version/v1/diagnosis-keys/country/EUR/date
/version/v1/diagnosis-keys/country/EUR/date/2020-11-10/hour
/version/v1/diagnosis-keys/country/EUR/date
/version/v1/diagnosis-keys/country/EUR/date/2020-11-10/hour

Looks like something is scheduled twice.

/version/v1/diagnosis-keys/country/EUR/date/2020-11-10/hour is requested despite (real) metered network (and Is metered network? true) in the Developer Menu.

Everytime I open the the client, it sends a request to /version/v1/diagnosis-keys/country/EUR/date although the the most recent Day Package has already been downloaded.

Everytime I open the the client, it sends a request to /version/v1/diagnosis-keys/country/EUR/date although the the most recent Day Package has already been downloaded.

Fixed with https://github.com/corona-warn-app/cwa-app-android/pull/1550/commits/f3f548f718acf5e952dda96bdcaccf05d8b2273d

Looks like something is scheduled twice.

Fixed with https://github.com/corona-warn-app/cwa-app-android/pull/1550/commits/42807e55b4f8c984b01ec6755dec98eb0e8c8343

Would appreciate more than 2 approvals on such a large PR.

authors: d4rken harambasicluka mlenkeit


text:
Spacing issue with \colorbox and operators.

When I use \colorbox to render static latex, it messes with the natural spacing around operators. E.g., in 1+\colorbox{blue}{\ensuremath{2}}+1+2, I'd expect the spacing between the first 1+2 to be the same as for the second 1+2, but it isn't.
Note: when applying \colorbox using the interactive math-field and the virtual keyboard, it initially shows the correct spacing. Setting the state of the math-field to that same latex expression will break the correct spacing around the +.

Refiled as https://github.com/arnog/mathlive/issues/1743

Fixed now.

authors: arnog eweitnauer

repo: cortex-js/compute-engine


text:
Record page is only showing reminders sidebar

Describe the bug
When you use the "Create record list" link in the modules page the "+ Add new record" opens an empty record page - only showing the reminders sidebar on the left.
To Reproduce
Steps to reproduce the behavior:

Create a module at https://latest.cortezaproject.org/compose/ns/test_record_list_page_button/admin/modules?sortBy=name
Add a title to the sample field
Hit save
Select "Create record list"
-> Record list page is opened
In this record list, set the "Sample" field to the visible column (so that it will show in the list)
Hit save and close.
Enter the page option
Check "Page visible?"
Hit save and close
Go back to modules again
Select "Page Builder" to create the record page
12 Add a "record" block and hit Save and Close (you are redirected to the list of pages in the admin area, and now there is a list page and a record page)
Click on the link public pages
-> The record list of the page created opens
Select "+ Add new record"
-> See error: the page opens with only the reminders sidebar on the left. See screenshot.

Expected behavior
Open the existing record page for the module
Desktop (please complete the following information):

Firefox, latest

Same issue in Chrome, latest version.

@medouederni thank you
You can work around this on yourself by removing record list block and adding it back again.
We'll have this fixed in the next version. Sorry for the inconvenience.

authors: darh lennyhorstink medouederni zmija

repo: cortezaproject/corteza-webapp-compose


text:
Delegate page is not working

Not sure what happened, but npm run testnet works for me again. Anyone still having this problem?

repo: cosmos/cosmos-ui


text:
docs: updates due to 02-client routing refactoring

Description

closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/).
[ ] Added relevant godoc comments.
[ ] Provide a conventional commit message to follow the repository standards.
[ ] Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
[ ] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

Summary by CodeRabbit

Documentation Updates

Added new methods for light client modules, such as RegisterStoreProvider, LatestHeight, UpdateState, UpdateStateOnMisbehaviour, RecoverClient, and VerifyUpgradeAndUpdateState.
Updated guides on handling updates, misbehaviour, and upgrades in the IBC protocol.
Integrated a new light client module for WebAssembly (Wasm) in the application.

took the liberty of implementing some of the coderabbit suggestions!

authors: charleenfei crodriguezvega

repo: cosmos/ibc-go


text:
Update packet commitment with the new Eureka specs

We can hold off on this for the time being as I think there is a decent chance that the commitment will change once again
https://github.com/cosmos/ibc-go/pull/6986/files/7e7be960feca637236d9f2508c03109a48c746c6

When addressing this issue, you should also switch to end-to-end testing with the new ibc-eureka feature branch instead of the old POC one that we are currently using.

This is closed by #88

repo: cosmos/solidity-ibc-eureka


text:
Unable to install

I am unable to install ngx-awesome-popup
D:\development\workspaces\lwwork\joulez-ui>npm i @costlydeveloper/ngx-awesome-popup
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: joulez-ui@0.0.0
npm ERR! Found: rxjs@6.6.7
npm ERR! node_modules/rxjs
npm ERR!   rxjs@"~6.6.0" from the root project
npm ERR!   peer rxjs@"^6.5.3" from @angular/common@12.1.5
npm ERR!   node_modules/@angular/common
npm ERR!     @angular/common@"~12.1.0" from the root project
npm ERR!     peer @angular/common@">8.0.0" from @costlydeveloper/ngx-awesome-popup@2.0.1
npm ERR!     node_modules/@costlydeveloper/ngx-awesome-popup
npm ERR!       @costlydeveloper/ngx-awesome-popup@"" from the root project
npm ERR!   1 more (@angular/core)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer rxjs@">6.." from @costlydeveloper/ngx-awesome-popup@2.0.1
npm ERR! node_modules/@costlydeveloper/ngx-awesome-popup
npm ERR!   @costlydeveloper/ngx-awesome-popup@"" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\Agnihotra\AppData\Local\npm-cache\eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Agnihotra\AppData\Local\npm-cache_logs\2021-10-29T03_15_38_186Z-debug.log

Ok, thank you @oRoz89 I will investigate that soon.

something is strange there, I have made a project with your package.json and I have no problem with installing this library, In this moment I think it is the problem with something else, I will continue with trying to reproduce that scenario.

thank you for reply. I just successfully installed package adding "--force"
to command
ned, 31. lis 2021. u 13:51 CostlyDeveloper @.***>
napisao je:

something is strange there, I have made a project with your package.json
and I have no problem with installing this library, In this moment I think
it is the problem with something else, I will continue with trying to
reproduce that scenario.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/costlydeveloper/ngx-awesome-popup/issues/17#issuecomment-955694854,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGSBFNDHGEJWLVDTV3FL3DUJU3WBANCNFSM5G6KIZQA
.

thank you for reply. I just successfully installed package adding "--force" to command ned, 31. lis 2021. u 13:51 CostlyDeveloper @.***> napisao je:
…
something is strange there, I have made a project with your package.json and I have no problem with installing this library, In this moment I think it is the problem with something else, I will continue with trying to reproduce that scenario. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGSBFNDHGEJWLVDTV3FL3DUJU3WBANCNFSM5G6KIZQA .

np, thank you, I found something, I have made project with @oRoz89 package json and it has no issue. Probably related to the npm version. I found this issue, https://github.com/npm/cli/issues/3152 I will see to make changes if new version of npm criteria changed, just working on that,
Yeah it will not be issue in this case to install it with --force because it use only things what angular use, and there is no 3rd party libraries needed.

Many thanks to @agnirpoli and @oRoz89 for reporting and helping resolve this issue, this should be fixed in this new release https://github.com/costlydeveloper/ngx-awesome-popup/releases/tag/2.0.2
P.S. If you find this useful, don't hesitate to give a star to a GitHub repo.

authors: agnirpoli costlydeveloper oRoz89

repo: costlydeveloper/ngx-awesome-popup


text:
🛑 Mainnet Smartpy (mainnet.smartpy.io) is down

In 4484339, Mainnet Smartpy (mainnet.smartpy.io) (https://mainnet.smartpy.io/chains/main/blocks/head/header) was down:

HTTP code: 503
Response time: 680 ms

Resolved: Mainnet Smartpy (mainnet.smartpy.io) is back up in 126e8ef after 14 minutes.

repo: cotezos/teznodes


text:
🛑 Mainnet Smartpy (mainnet.smartpy.io) is down

In cad82e2, Mainnet Smartpy (mainnet.smartpy.io) (https://mainnet.smartpy.io/chains/main/blocks/head/header) was down:

HTTP code: 502
Response time: 502 ms

Resolved: Mainnet Smartpy (mainnet.smartpy.io) is back up in fb7738a after 27 minutes.


text:
🛑 Mainnet Giganode [tezos Ukraine] is down

In e0f4da9, Mainnet Giganode [tezos Ukraine] (https://mainnet-tezos.giganode.io/chains/main/blocks/head) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mainnet Giganode [tezos Ukraine] is back up in e7125d5.


text:
少年派网页版登陆障碍

少年派网页版登陆障碍
华东师范大学第二附属中学
华为C5
软件版本：5.2.4.52441
hsefz.lexuewang.cn:8003

您好，请问遇到了什么问题？

感谢您的反馈，对于您在PadPlus（少年派桌面客户端）中遇到的登录问题，请参见issue#14。

issue#14的机型与系统与此略有出入，望留意

经测试，华东师范大学第二附属中学各平板均可登录，预计明天早上推送版本更新

authors: EndeavourCHN cotzhang


text:
List of Cities in the Philippines

Regions list is not valid.

ref: https://en.wikipedia.org/wiki/Provinces_of_the_Philippine
correct list: phillippinesRegions.txt

Thanks @bilalrashid300, I'll update it in todays release based on this data. Looks like someone had set the region values to cities, like you said.
https://en.wikipedia.org/wiki/Regions_of_the_Philippines

repo: country-regions/country-region-data


text:
Fixes

Fixes https://github.com/coursier/coursier/issues/1204.
Fixes https://github.com/coursier/coursier/issues/1178.

Thanks for the fixe @alexarchambault, this is awesome!
@eed3si9n Do you know if this will go in SBT 1.3.0 or 1.3.1?

repo: coursier/coursier


text:
Update case-app to 2.0.5

Updates com.github.alexarchambault:case-app from 1.2.0 to 2.0.5.
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!

Files still referring to the old version number
The following files still refer to the old version number (1.2.0).
You might want to review and update them manually.
project/plugins.sbt

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.alexarchambault", artifactId = "case-app" } ]

labels: library-update, semver-major, old-version-remains

Superseded by #54.

repo: coursier/http-server


text:
memory leak fix

https://moskud.xyz/debugging-memory-leak-in-elixir

Great work 👏
Awesome to see new blog posts from you

repo: covalenthq/rudder


text:
fix(homepage): fix style for page title

Proposed Changes
Adjust the size for the title to be smaller
before:

After:

Potential Breaking Changes
none
Acceptance Criteria

[ ] The proposed changes are covered by unit tests
[ ] The potential breaking changes are clearly identified
[ ] README.md is adjusted to reflect the proposed changes (if relevant)

Random question, were these new page-title class dimension height and font size recommended on figma/UX? did they officially told you yeah 133 px and 140 or did you eye balled it and thought it looked better that way? (no wrong answer :P ) Either way it looks better!

Those are the dimensions from Figma, no eye ball :joy_cat:
I think that it was too big with the previous style and Gustavo made adjustments at my request :heart:

repo: coveo/plasma