text:
Deleting scalar list throws error ' violates foreign key constraint'

I am trying to perform a cascading delete on User for the schema below. Note, that Course has a scalar list field colors: [String!]!. The deletion is working properly when the field colors is empty. However, when it is not empty, I receive the following error (obtained with docker-compose logs:

postgres_1  | 2018-06-12 09:28:24.910 UTC [58] ERROR:  update or delete on table "Course" violates foreign key constraint "Course_colors_nodeId_fkey" on table "Course_colors"
postgres_1  | 2018-06-12 09:28:24.910 UTC [58] DETAIL:  Key (id)=(cjibh0fvk003808019s4j55mk) is still referenced from table "Course_colors".

It seems like the Postgresql connector is not properly  deleting the corresponding entries in the automatically generated table Course_colors.
Or maybe the schema is designed in a wrong way?
type User {
    id: ID! @unique,
    createdAt: DateTime!,
    courses: [Course!]! @relation(name: "CoursesForUser", onDelete: CASCADE)
}

type Course {
    id: ID! @unique,
    createdAt: DateTime!,
    colors: [String!]!,
    user: [User!]! @relation(name: "CoursesForUser")
}

Same here, can't delete an user containing a scalar list as a field :/
type User {
  id: ID! @unique
  createdAt: DateTime!
  updatedAt: DateTime!
  username: String @unique
  groups: [String!]!
  emails: [Email!]!
  services: [Service!]!
  profile: Profile
}

The error :

org.postgresql.util.PSQLException: ERROR: update or delete on table "User" violates foreign key constraint
"User_groups_nodeId_fkey" on table "User_groups"

Detail: Key (id)=(cjibsmf4s02g20a54y930o6a0) is still referenced from table "User_groups".

Some additionnal logs :

org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2433)
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2178)
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:306)
org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:441)
org.postgresql.jdbc.PgStatement.execute(PgStatement.java:365)
org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:155)
org.postgresql.jdbc.PgPreparedStatement.execute(PgPreparedStatement.java:144)
com.zaxxer.hikari.pool.ProxyPreparedStatement.execute(ProxyPreparedStatement.java:44)
com.zaxxer.hikari.pool.HikariProxyPreparedStatement.execute(HikariProxyPreparedStatement.java)
slick.jdbc.StatementInvoker.results(StatementInvoker.scala:39)
slick.jdbc.StatementInvoker.iteratorTo(StatementInvoker.scala:22)
slick.jdbc.Invoker.first(Invoker.scala:31)
slick.jdbc.Invoker.first$(Invoker.scala:30)
slick.jdbc.StatementInvoker.first(StatementInvoker.scala:16)
slick.jdbc.StreamingInvokerAction$HeadAction.run(StreamingInvokerAction.scala:52)
slick.jdbc.StreamingInvokerAction$HeadAction.run(StreamingInvokerAction.scala:51)
slick.dbio.DBIOAction$$anon$4.$anonfun$run$3(DBIOAction.scala:240)
scala.collection.Iterator.foreach(Iterator.scala:929)
scala.collection.Iterator.foreach$(Iterator.scala:929)
scala.collection.AbstractIterator.foreach(Iterator.scala:1417)
scala.collection.IterableLike.foreach(IterableLike.scala:71)
scala.collection.IterableLike.foreach$(IterableLike.scala:70)
scala.collection.AbstractIterable.foreach(Iterable.scala:54)
slick.dbio.DBIOAction$$anon$4.run(DBIOAction.scala:240)
slick.dbio.DBIOAction$$anon$4.run(DBIOAction.scala:238)
slick.dbio.SynchronousDatabaseAction$FusedAndThenAction.$anonfun$run$4(DBIOAction.scala:534)
slick.dbio.SynchronousDatabaseAction$FusedAndThenAction.$anonfun$run$4$adapted(DBIOAction.scala:534)
scala.collection.Iterator.foreach(Iterator.scala:929)
scala.collection.Iterator.foreach$(Iterator.scala:929)
scala.collection.AbstractIterator.foreach(Iterator.scala:1417)
scala.collection.IterableLike.foreach(IterableLike.scala:71)
scala.collection.IterableLike.foreach$(IterableLike.scala:70)
scala.collection.AbstractIterable.foreach(Iterable.scala:54)
slick.dbio.SynchronousDatabaseAction$FusedAndThenAction.run(DBIOAction.scala:534)
slick.dbio.DBIOAction$$anon$1.$anonfun$run$1(DBIOAction.scala:187)
scala.collection.Iterator.foreach(Iterator.scala:929)
scala.collection.Iterator.foreach$(Iterator.scala:929)
scala.collection.AbstractIterator.foreach(Iterator.scala:1417)
scala.collection.IterableLike.foreach(IterableLike.scala:71)
scala.collection.IterableLike.foreach$(IterableLike.scala:70)
scala.collection.AbstractIterable.foreach(Iterable.scala:54)
slick.dbio.DBIOAction$$anon$1.run(DBIOAction.scala:187)
slick.dbio.DBIOAction$$anon$1.run(DBIOAction.scala:184)
slick.dbio.SynchronousDatabaseAction$FusedAndThenAction.$anonfun$run$4(DBIOAction.scala:534)
slick.dbio.SynchronousDatabaseAction$FusedAndThenAction.$anonfun$run$4$adapted(DBIOAction.scala:534)
scala.collection.Iterator.foreach(Iterator.scala:929)
scala.collection.Iterator.foreach$(Iterator.scala:929)
scala.collection.AbstractIterator.foreach(Iterator.scala:1417)
scala.collection.IterableLike.foreach(IterableLike.scala:71)
scala.collection.IterableLike.foreach$(IterableLike.scala:70)
scala.collection.AbstractIterable.foreach(Iterable.scala:54)
slick.dbio.SynchronousDatabaseAction$FusedAndThenAction.run(DBIOAction.scala:534)
slick.dbio.SynchronousDatabaseAction$$anon$11.run(DBIOAction.scala:571)
slick.dbio.SynchronousDatabaseAction$$anon$6.run(DBIOAction.scala:470)
slick.dbio.SynchronousDatabaseAction$$anon$10.run(DBIOAction.scala:562)
slick.dbio.SynchronousDatabaseAction$$anon$7.run(DBIOAction.scala:487)
slick.basic.BasicBackend$DatabaseDef$$anon$2.liftedTree1$1(BasicBackend.scala:240)
slick.basic.BasicBackend$DatabaseDef$$anon$2.run(BasicBackend.scala:240)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)

Any updates on this? Or did someone find a workaround for this?

I use mysql for now ....

What also works is to update the fields to be empty again before the deletion.
mutation {
  updateCourse(
    where: { id: "cjivp6ydh14930707kn0q1ble" },
  	data: {
    	colors: {set: []},
  	})
  {
    id
    colors
  },

  deleteCourse(
  	where: { id: "cjivp6ydh14930707kn0q1ble" } )
  {
    id
  }

}

Thanks for your additional input! We will add a resolution to the beta channel soon 🙂

This was fixed in this PR and is now available in 1.12-beta.

authors: Aetherall Jaszkowic marktani

repo: prismagraphql/prisma


text:
Cannot get rich Text to work

Using an example repo by Birkir
https://github.com/birkir/gatsby-source-prismic-graphql/blob/master/examples/arnaud/src/pages/index.js
Using  <RichText render={data.title} linkResolver={linkResolver} />
I get
Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.
Is there any documentation around the expected json data the component expects?
                {
                  "type": "heading1",
                  "text": "my homepage",
                  "spans": []
                }
              ]```

I;m being an idiot. It was using an older version of prismic js

source: gharchive/issue

repo: prismicio/prismic-reactjs

license_type: permissive

license_source: github-api


text:
Need help compiling an Android plugin (.so) which uses WebRTC

I've successfully built the Android WebRTC libraries using the scripts in this repository.  Now what I really want to do is compile an Android C++ library (.so) which uses WebRTC together with a bunch of other code for my use.  I want to use the typical ndk-build system (with Android.mk, Application.mk) to create this plugin.  My main struggle has generally been knowing which C++ runtime (APP_STL) to choose, and maybe someone can help me with this.
Specifically my Android library will not only use WebRTC, but also the boost libraries as well as other third party libraries.  So I need to find a way that all of them can be linked together with consistent C++ runtime...
Before dealing with the hard case of mixing WebRTC with boost, I wanted to verify that I know how to build an Android library which only links to WebRTC.  So I created the dummy cpp file, foo.cpp, seen below, and eventually determined the right .mk files that allow it to build with ndk-build.
foo.cpp
#include "webrtc/base/thread.h"
extern "C" void foo() { rtc::Thread *thread = new rtc::Thread; }

Application.mk:
NDK_TOOLCHAIN := arm-linux-androideabi-4.9
APP_ABI := armeabi-v7a
APP_STL := c++_static

Android.mk:
LOCAL_PATH := $(call my-dir)
WEBRTC_ROOT = /home/vagrant/mybuild/webrtc/src
WEBRTC_LIB_ROOT = $(WEBRTC_ROOT)/out_android_armeabi-v7a/Release/obj

include $(CLEAR_VARS)
LOCAL_CFLAGS    := -DNDEBUG -DWEBRTC_POSIX -DWEBRTC_LINUX -DWEBRTC_ANDROID -std=gnu++11
LOCAL_LDLIBS    :=  -llog -L$(WEBRTC_LIB_ROOT)/webrtc/base \
                   -lrtc_base -lrtc_base_approved \
                   -L$(NDK_ROOT)/sources/cxx-stl/llvm-libc++/libs/armeabi-v7a \
                   -lc++_static

LOCAL_MODULE    := foo
LOCAL_SRC_FILES := ../foo.cpp
LOCAL_C_INCLUDES:= $(WEBRTC_ROOT)
include $(BUILD_SHARED_LIBRARY)

This is the combination that seemed to work for me.  Other choices of APP_STL seemed to fail...  Does that seem right?  Do I have to use c++_static in order to be consistent with the way the WebRTC libraries were built?
But now I'm struggling with mixing it with boost.  Until now I've been dealing with boost by building using CrystaX NDK which seemed to have simpler support for boost.  When I've done this in the past, I've generally set APP_STL:=gnustl_static, which seems like it may be inconsistent with the way we built WebRTC...  Does that mean I will need to configure WebRTC to build with CrystaX too? Does anyone know of a simpler solution to add the boost libraries to the mix?
Any help would be appreciated.
Eran.

Eran,
I'm not sure I can help you, WebRTC is meant to be built using the scripts and not the NDK.
Can't you just link the built libraries in your project? Can't they be mixed together after they are actually built?

Thanks.  I did (hopefully) solve this issue in the end.
Again the issue was that I needed to use both WebRTC and boost in my project, and the former is built (by default) with llvm-libc++, while the latter is built with gnustl.  And mixing them together caused problems.
So what I ended up doing is creating a thin, C-style wrapper around the functions I needed from WebRTC.  I built this wrapper into a shared library (.so), by statically linking to a long list of WebRTC .a files, and also making sure to link with libc++_static to be consistent with the WebRTC compilation.
Then I used this .so with the rest of my boost-dependent project by compiling with crystax instead of the stock NDK and linking with gnustl.
I saw "hopefully solved" because it does produce some warning related to the fact that my code mixes two types of runtimes, but so far it seems to work okay despite these warnings...

glad to hear you overcame the issue

I caught this problem too.
So I have to build all third party lib to c++_static which cost me a lot of time.

Thanks for the solution ,that was a great help.

hi, eguendelman, I meet the issue, can you show you compile command? thanks a lot

authors: ArikYa aagmangour eguendelman hdchenjian oldmtn

repo: pristineio/webrtc-build-scripts

license_source: bigquery


text:
Bug: Hide Sign up if already signed up

Report from user from Loom: https://www.loom.com/share/7da7aae4aa9e4a9cb48965e73e61f1a6?sid=ef95c42e-f387-48c2-84d6-4a0d68334082

Seems like this is already fixed? @kittybest @crisgarner can you confirm please?

so the issue here it's that the check if a user is signed up fails because it tries to fetch more than 1024 block at a time, so it will just throw. We need to fix this on MACI side https://github.com/privacy-scaling-explorations/maci/blob/dev/cli/ts/commands/signup.ts#L106

fixed by #138

repo: privacy-scaling-explorations/maci-rpgf

license: MIT


text:
What will consent banner look

Once google removes support for 3PC what will a consent banner look like? I'm.guessing as still have 1st party cookies if could look kind of similar with strictly necessary, functional still existing? And perhaps performance cookies like GA being deprecated. I do wonder what privacy companies like OneTrust and Trustarc are doing to work with Google Privacy Sandbox. I'm proposing internally we replace cookie policy pages with privacy trust policy pages. Cookies will remain post Googles changes but they will taste a bit different

Hi @Dory998 — thanks for your question, and apologies for the delay in responding.
The Privacy Sandbox Privacy-related compliance FAQs provides information about consent and ePrivacy.
We recommend that you contact your Consent Management Platform (CMP) to find out more about future consent banner requirements.

I'm closing this as completed, as there hasn't been any follow up in several weeks, but feel free to reopen if necessary.


text:
Update bidding_auction_cost.md

Added a line about extra traffic from SFE to Buyer RTB servers.

LGTM

source: gharchive/pull-request

authors: akshaypundle galarragas


text:
Kill 2

Looks like this code is never referenced. OK to kill it?

lets just fix the formatting and push it

authors: akoshelev benjaminsavage

repo: private-attribution/ipa


text:
docs: Make examples ESM

Before we enforce ESM, we should probably make it best-practice and recommend it for new apps.
This is a draft because I have not yet validated all examples.
I also noticed we need to update the testing docs, I'll do that in a separate PR.

Maybe also take care of create-probot-app?

authors: AaronDewes Uzlopak

repo: probot/probot

license: ISC


text:
Small bug in the Service tab with "Timeline" enabled.

BAM!
https://i.imgur.com/QN3tx9N.png
So I was just testing out this Timeline column thing by enabling it, and noticed anything placed the right of this column will also gain a green highlight color as you mouse over them. Looks to me like the timeline "bar" is spilling on out over onto whatever it is next too.
Image above should show off the issue better then my words can.
So that's pretty much it, we'll need a clean up on aisle 46, no rush dmex. : P

Are you running an old nightly build from 6 months ago?

3.0.4444

I haven't been able to reproduce it?

Well I'm not at my machine now or until tomorrow but I'll try and make a gif of it then. All I do is toggle the timeline column to show, and so it appears on the far, far right as a new column, then I drag it past other columns to the left, now when I highlight over the columns on the right they get that green color to them.
To me it's no big deal, I won't use that timeline column in the future, it was just a "try before buy" thing I did, but figured I would report the strange behavior none the less.

As promised, a crappy little gif, (I'm not crazy!)
https://i.imgur.com/NGPPVbV.gif
But again I'm not doing anything special here, if you cannot reproduce, welp, I will just blame this on my config or something then, I'm way to lazy to try and troubleshoot this as I won't use this timeline anyways.

@ImSpecial
Can you check the Uptime value shown by Process Hacker on the System Information > CPU panel exactly matches the Uptime in Task Manager > Performance > Cpu panel? The uptime (bootstart) time determines the value of the timeline graphs.

Oh wow, I think this/that may have been it, I've since booted my machine and cannot reproduce my issue now, but if I play with the Date & Time of Windows, I can again... So I guess this was never an issue with Process Hacker to begin with and all on "my config". Well that was a waste of time...
You a sharp guy dmex! I'm going to call you Sherlock dmex now.

if I play with the Date & Time of Windows, I can again

What did you change to reproduce it?

Use this device (https://i.imgur.com/srQBh6s.png) to go back and meet up with Marty's mom, good luck!

Use this device

Where do you find that?

God Windows 10 sucks! I dunno, I use Open-Shell and it just shows up if I search for "date" also it's in the control panel. (the good one)
https://i.imgur.com/5XljoC5.png

it just shows up if I search for "date" also it's in the control panel

I can't find it

The screenshot looks like of timedate.cpl.

Fixed

Oh good, I'm still here.

authors: Biswa96 ImSpecial dmex

repo: processhacker/processhacker


text:
C1047 error while compiling

Describe the bug
While compiling, C1047 errors. Yesterday and today source

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Windows]
Version [e.g. Vista]

Additional context
Add any other context about the problem here.

Which version of Visual Studio are you using?
The problem is that your version isn't compatible with our pre-compiled static libraries. You have to recompile \tools\thirdparty\thirdparty.sln for both Release and Debug.

Which version of Visual Studio are you using?
The problem is that your version isn't compatible with our pre-compiled static libraries. You have to recompile \tools\thirdparty\thirdparty.sln for both Release and Debug.

VS2019 16.10
Ok I try later

Which version of Visual Studio are you using?
The problem is that your version isn't compatible with our pre-compiled static libraries. You have to recompile \tools\thirdparty\thirdparty.sln for both Release and Debug.

Builded OK

VS2019 16.10

I have 16.10 and couldn't reproduce the build issues so not sure why yours failed but mine doesn't... Either way I'll update the precompiled libraries after Appveyor updates their build image 👍

Why are those precompiled?

Why are those precompiled?

The same reasons anyone uses a precompiled library? 🤔
Thirdparty is completely isolated from the project which is necessary for licensing. It also contains static code that rarely if ever changes and a precompiled library significantly reduces compilation time required to build the project.
There are 5 solutions in that project with a significant amount of code that would otherwise have to be compiled by everyone, every single time you build the project including by Appveyor when they compile the nightly builds so having a precompiled library saves a significant amount of compilation time. This also majorly improves performance of various Visual Studio features because it doesn't have to index/compile databases for intellisense and search since all that code is completely isolated.
I don't know why it needs explaining since everyone does this (including the Windows SDK). I think the issue is that recent versions of Visual Studio changed those error messages and error C1047 stopped telling you thirdparty.lib caused the problem and instead only saying its phlib.lib 🤷♀

I think ProcessHacker is not so huge project which can time out any CI builds.

ProcessHacker is not so huge project which can time out any CI builds.

CI wasn't the problem.

authors: Avtroman Biswa96 dmex


text:
Credits

We need to write up some credits - this will appear when users look at the "about" menu.

Hi @antiboredom, if you want, I work on this feature.

@nucliweb that would be great - thank you!

@antiboredom do you like the system of Brackets for show credits?

@nucliweb I hadn't seen this before, but yeah I really like it!

Ok, I will work in this concept for the credits section ;)

authors: antiboredom nucliweb

license: mit


text:
Index the first element of the node_versions array

The -1 syntax doesn't work and it shouldn't matter which version we are using here.
Change-type: patch
Signed-off-by: Kyle Harding kyle@balena.io

I self-certify!

repo: product-os/flowzone


text:
🛑 Multi Hardware is down

In 7bb65a2, Multi Hardware (https://www.multi-hardware.com/retrogami) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Multi Hardware is back up in 334bfa1 after 7 minutes.

repo: proger-su/upptime


text:
Edition 2018 port

hey,
here's a small patch that updates the codebase to Rust edition 2018. Tests pass.
The second commit updates all dependencies, small crates updates that don't seem to break anything (again, tests pass). But if you prefer, I can move this commit to a separate PR.
thanks for evaluating the patch!

Merged #33.

authors: apiraino programble

repo: programble/scraper


text:
Pressing shift shows the window bar

I have all keyboard shortcuts disabled but whenever I press shift the window bar opens. This is really weird when typing capital letters as it flashes open and close

This is only a problem when I have Enable Full Toolbar Auto-collapse enabled

I cannot seem to reproduce this behavior. Could you send me your config file and a list of plugins that you have enabled?


text:
make chokes on invalid css (which is totally valid)

Make dies with:
mkdir -p build/webfrontend/
cat src/webfrontend/example-plugin.scss | sass --stdin > build/webfrontend/example-plugin.css || ( rm -f build/webfrontend/example-plugin.css ; false )
Error: Invalid CSS after "10px": expected expression (e.g. 1px, bold), was ";"
        on line 2 of standard input
  Use --trace for backtrace.
make: *** [easydb-library/tools/base-plugins.make:20: build/webfrontend/example-plugin.css] Error 1

This is weird, as the css that is mentioned is actually valid. The full stack trace produced by sass looks like this:
$ cat src/webfrontend/example-plugin.scss | sass --stdin --trace > build/webfrontend/example-plugin.css
Traceback (most recent call last):
	27: from /usr/bin/sass:8:in `<main>'
	26: from /usr/lib/ruby/vendor_ruby/sass/exec/base.rb:18:in `parse!'
	25: from /usr/lib/ruby/vendor_ruby/sass/exec/base.rb:50:in `parse'
	24: from /usr/lib/ruby/vendor_ruby/sass/exec/sass_scss.rb:63:in `process_result'
	23: from /usr/lib/ruby/vendor_ruby/sass/exec/sass_scss.rb:392:in `run'
	22: from /usr/lib/ruby/vendor_ruby/sass/engine.rb:290:in `render'
	21: from /usr/lib/ruby/vendor_ruby/sass/engine.rb:417:in `_to_tree'
	20: from /usr/lib/ruby/vendor_ruby/sass/engine.rb:557:in `append_children'
	19: from /usr/lib/ruby/vendor_ruby/sass/engine.rb:557:in `each'
	18: from /usr/lib/ruby/vendor_ruby/sass/engine.rb:558:in `block in append_children'
	17: from /usr/lib/ruby/vendor_ruby/sass/engine.rb:541:in `build_tree'
	16: from /usr/lib/ruby/vendor_ruby/sass/engine.rb:541:in `each'
	15: from /usr/lib/ruby/vendor_ruby/sass/engine.rb:548:in `block in build_tree'
	14: from /usr/lib/ruby/vendor_ruby/sass/engine.rb:557:in `append_children'
	13: from /usr/lib/ruby/vendor_ruby/sass/engine.rb:557:in `each'
	12: from /usr/lib/ruby/vendor_ruby/sass/engine.rb:558:in `block in append_children'
	11: from /usr/lib/ruby/vendor_ruby/sass/engine.rb:539:in `build_tree'
	10: from /usr/lib/ruby/vendor_ruby/sass/engine.rb:666:in `parse_line'
	 9: from /usr/lib/ruby/vendor_ruby/sass/engine.rb:707:in `parse_property_or_rule'
	 8: from /usr/lib/ruby/vendor_ruby/sass/engine.rb:745:in `parse_property'
	 7: from /usr/lib/ruby/vendor_ruby/sass/engine.rb:1169:in `parse_script'
	 6: from /usr/lib/ruby/vendor_ruby/sass/script.rb:27:in `parse'
	 5: from /usr/lib/ruby/vendor_ruby/sass/script/parser.rb:228:in `parse'
	 4: from /usr/lib/ruby/vendor_ruby/sass/script/parser.rb:69:in `parse'
	 3: from /usr/lib/ruby/vendor_ruby/sass/script/parser.rb:897:in `assert_done'
	 2: from /usr/lib/ruby/vendor_ruby/sass/script/lexer.rb:240:in `expected!'
	 1: from /usr/lib/ruby/vendor_ruby/sass/scss/parser.rb:1308:in `expected'
(sass):2: Invalid CSS after "10px": expected expression (e.g. 1px, bold), was ";" (Sass::SyntaxError)

Sorry to let you hanging here. If this is still an issue, please write to support@programmfabrik.de
To avoid this in the future we will disables issues on github, as we use our internal issue tracker.

repo: programmfabrik/easydb-example-plugin


text:
How to uninstall a plugin?

I've installed dokku-bower-install as described on their GitHub readme. Now I get the nasty ! [remote rejected] master -> master (pre-receive hook declined) error when pushing a node.js application. Not sure if it's the plugins fault, but before the install it worked, so there's that. So general question:
How to uninstall this (or any other) plugin properly?
The Wiki Page only states how to create and install plugins, not how to remove them.

Thanks @AlJohri.

@juanpastas please do not comment on old issues.

authors: arechsteiner josegonzalez juanpastas

repo: progrium/dokku


text:
[Feature] (Android) Request to perform NOC generation in cloud but perform device attestation locally

Feature description
On iOS, there was a shouldSkipAttestationCertificateValidation flag added that enabled these processes to be decoupled. Their device controller uses that flag to determine whether it should use the default DAC verifier or the partial DAC verifier here
It would be nice if Android had the same functionality, so we don't have to build CHIP for our cloud servers or re-implement in another tech stack.
Platform
android
Platform Version(s)
1.1.0.1
Anything else?
No response

@yufengwangca can we have this flag? thanks

authors: tnguyen-alarm yunhanw-google

repo: project-chip/connectedhomeip


text:
Compilation getting stuck [1.2]

Reproduction steps
Try to build version 1.2.0.0 after giving git Xdf clean
Bug prevalence
[0/172] c++ obj/commands/discover/chip-tool-utils.DiscoverCommand.cpp while compiling 1.2v it is getting stuck at his file every time and not proceeding forward .Rpi is getting hanged every time need to reboot still it is not proceeding a single step from this file
GitHub hash of the SDK that was being used
Dont know
Platform
raspi
Platform Version(s)
4
Type
Platform Issue
Anything else?
Rpi getting need to fix to resolve this issue

To use -j1 try to it.

To use -j1 try to it  still not working getting stuck at same file
[0/172] c++ obj/commands/discover/chip-tool-utils.DiscoverCommand.cpp.

I too had faced the similar issue. Did git pull and submodule init. If your build is getting stuck, try -j1. I too had tried with -j1 when my build got stuck.
git pull
git submodule update --init
gn gen out/host
ninja -j1 -C out/host


text:
Add a TestCluster response command that just returns a boolean.

Use this instead of relying on status codes in various tests.
Fixes https://github.com/project-chip/connectedhomeip/issues/10555
Problem
See #10555
Change overview
See above.
Testing
Ran the TestClusterComplexTypes yaml test and it passes.

Fast tracking, as this is adding tests.

authors: bzbarsky-apple woody-apple


text:
Rendezvous cleanup

Problem
Rendezvous Session and surrounding code still has message based API support. It's been deprecated in favor of delegate based callbacks. The old code should be removed.
Summary of Changes
This change removes the deprecated code, and also hooks up the callbacks for Rendezvous status updates.
Fixes #3177

@saurabhst, @jelderton , do you have any comments?


text:
Update the top level template json file based on ZCL extensions

Add the zcl extension files to part of its crc check.
If the crc changes based on the inclusion of extensions then reload the top level template json file and turn its IN_SYNC to true and turn the old on to false
These changes make sure that when a zcl extension file (eg json files in zcl section such as cluster-to-component.json) is updated then everything from the top level json files are loaded again
JIRA: ZAPP-1092

Unify CI failure is a known failure and is being looked into. Will be disabled for the short term.

repo: project-chip/zap


text:
Handling Endianness correctly

Handling the negative default values and float values for attributes correctly in terms of endianness(little/big)

Some unit test seems to be failing.

Some unit test seems to be failing.
https://github.com/project-chip/zap/issues/593 Logged this for a UI warning when user enters an invalid hex value as an attribute default which was the reason for the test failure. Will be a better experience for a user to see this in the UI immediately than during compile time.

authors: brdandu tecimovic


text:
More functions and correct return type format

Here is the list of this PR for.

Add Array functions
Add DateTime functions
Add boolean function
Add more string functions
Add go module file for utils function
Base on the discussion we made to change the return type to an object

 "return": {
        "type": "string"
      }

@mellistibco does encoding a string to base64 even make sense? I think we do that in util and strings package.  Shouldn't it just be a single base64 encode in util that encodes a binary to a string and decodes a string to a binary.  Not sure it makes sense to encode a string to a string, that is not the purpose of base64 encoding.

I think i'd put encoding stuff in utils and allow it to base64 encode more than just a string typ...

@mellistibco  The encode and decode function under utils are for string only(from code).  Why not move to string category?

Let's do the opposite and make the encode/decode in utils support more than just string type?

@mellistibco  Make sense.  Will keep it in utils and remove from strings.

@mellistibco @fm-tibco Updated PR, please have another look.

@fcastill note the descriptor change.

authors: fm-tibco lixingwang mellistibco

repo: project-flogo/contrib


text:
adding simple travis.yml file

adding a travis file to test all of the inference activities test cases.

Thanks Tracy, I have removed git and depth.

repo: project-flogo/ml


text:
Add "not configured" empty state

https://issues.redhat.com/browse/COST-5102

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 70.00%. Comparing base (8b683f3) to head (d22dea2).
Report is 5 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #354   +/-   ##
=======================================
  Coverage   70.00%   70.00%
=======================================
  Files          81       81
  Lines        1080     1080
  Branches      244      246    +2
=======================================
  Hits          756      756
  Misses        313      313
  Partials       11       11

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter dlabrecq

repo: project-koku/koku-ui-mfe


text:
Update toolbar to use PF DataToolbarChipGroup interface

Replace workarounds for PatternFly's DataToolbarFilter with the new DataToolbarChipGroup interface.
https://github.com/project-koku/koku-ui/issues/1523

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1524   +/-   ##
=======================================
  Coverage   76.26%   76.26%
=======================================
  Files         199      199
  Lines        3590     3590
  Branches      685      685
=======================================
  Hits         2738     2738
  Misses        762      762
  Partials       90       90

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 048f9cf...78a9c54. Read the comment docs.

authors: codecov-io dlabrecq

repo: project-koku/koku-ui


text:
Consolidate combinational Cava instances

At the moment, we have separate Cava (combinational semantics) typeclass instances for "combinational circuits" (CombinationalSemantics from CombinationalMonad.v) and "combinational components of sequential circuits" (SequentialCombSemantics from Sequential.v). This means that proofs about combinational components don't carry over once the combinational component is put into a sequential circuit unless the proof is done twice. We should either:

Make the SequentialCombSemantics version the canonical combinational semantics, since the only really interesting circuits to us have sequential components. Port all the existing proofs over to SequentialCombSemantics. The main potential pitfall here is increased complexity in the combinational proofs/definitions.
Don't require the sequential and combinational typeclasses to use the same datatype; let the sequential typeclass use a projection from the combinational datatype (e.g. list), and make the CombinationalSemantics instance the canonical combinational semantics. The main potential pitfall is that then we're dealing with differently-typed data for sequential and combinational components, which could complicate circuit descriptions.

Complicating circuit descriptions is worse than complicating proofs of combinational combinators, so I'll try 1) first, and if I run into problems I'll try 2) and see how it goes.

This is a prerequisite for #413, because we will need to make a loop and use proofs of combinational combinators to prove properties about it.

This is a prerequisite for #413, because we will need to make a loop and use proofs of combinational combinators to prove properties about it.

repo: project-oak/oak-hardware


text:
lang: Program id errors should log the program addresses

try_from errors should give more context on the program ids by logging the expected vs given

related: https://github.com/project-serum/anchor/issues/798

one way to do this would be:

add a pubkeys field to AnchorError (maybe also to ProgramErrorWithOrigin) pubkeys: Option<[Pubkey;2]>
add another match arm to err! `err!(<error_code>, , )
Do 5 log statements:

"Expected pubkey:"
.log()
"Was pubkey: "
.log()

Has to be 5 instead of 1 because we have to use Pubkey::log (200 CU). using format! would cost 12K per pubkey.
Alternatively, we could make it more generic by detecting (or using a different format for) pubkeys so we could have another field values: [String;2] which is filled using format if expected and actual are not pubkeys and then logged as a single log statement (or as 5 log statements to be consistent) and otherwise we do the 5 log statements.

format! for Pubkey (i.e. Display/Debug) cost 12K per key? wow

authors: armaniferrante fanatid paul-schaaf

repo: project-serum/anchor


text:
Problem with ERC-20 USDT conversion

Good evening,
I used the send option with ERC20 USDT.  Then the wallet asked me if i wanted to convert USDT to ERC20 using metamask.  I said yes and sent them.  When Metamask transaction popped up I realized that I don’t have enough ETH and rejected the transaction.  I’tc been 2,5 days I can’t see my USDT neither at Sollet or metamask neither or see the transaction on etherscan.  I’ve tried to do the same yesterday by sending $1 USDT hoping that would help, but same thing happen.  Please help.

i have same issue @@

repo: project-serum/spl-token-wallet


text:
[New Feature] Add a Trip Review feature in the My Trips section

Include a button in the details of a trip in My Trips section labeled as "Review your trip"

Tap on button > Write a review (string format) > Send to backend
Make a new section for each city called Trip Reviews and display all reviews in this section
Trip reviews can be customized to share publicly or only with friends

@knightcube We don't have backend support for this. So, before adding such issue in Android repo,  create it on the server repo first.
We can't start working on this.

It requires a lot of backend support first. Let's build that first & then, reopen this issue.

repo: project-travel-mate/Travel-Mate


text:
Change monument detection logic from estimote beacons to GPS location

Currently monuments or near by attractions are detected using estimote beacons but we decided to remove it to improve usability and scalability of the app.
Instead, use the current GPS location of the user and constantly poll (in certain interval ~600 seconds) the server providing the GPS coordinates and the proximity radius (in meters) to get a list of attractions near-by and accordingly send out a push notification.

Hi
I just wanna give you a suggestion: use the "estimote beacons" just as some source of gamefication, to make the users to search & find the places with those items and help them to explore the city.
And please, really do this enhancement purposed on this issue. Using this hardware (estimote beacons) to track monuments is not the best way to do this (and makes your app too costly to keep)
Congrats to the app, It's a really good idea

The estimote logic is removed in 1f9b6b408ac52a1fb0f5941f65854a5b905c7c5a


text:
required for zfsbootmenu

zfz
kexec-tools

Problem with this PR:
A "zfz" packages does not seem to exist in the void repos. I found a "fzf" package (command-line fuzzy-finder) - not sure if this was intented instead though.

corrected

repo: project-trident/trident-installer


text:
Link not identified as a link [iOS]

The “Find a site near you” link on the My Health Log Results C (“Not feeling well”) screen is not conveyed to VoiceOver users as a link.

Use the accessibilityRole attribute on the interactive element (TouchableOpacity, Pressable, etc.) to convey a link role to VoiceOver users.
<TouchableOpacity onPress={…} accessibilityRole='link'>
  <Text>Find a site near you</Text>
</TouchableOpacity>

@willslone Can you check in the next build please. Thanks

Looks good.

authors: floridemai helloantoine willslone

repo: project-vagabond/covid-green-app


text:
PDF: Use bold for act/scene divisions

@JackWilton1594 suggests:
"Can we use bold weight for the act/scene divisions? "
I assume this means bold text for the Act and Scene headings. Easily done, I think, if there's a consensus.

I agree, so we have achieved consensus. Please make it so.

It is so, as of rev 19109.

authors: JanelleJenstad martindholmes

repo: projectLEMDO/lemdoIssues


text:
Add support for registry cert authentication.

Open this for early review, before I start working on some tests

This commit allows to use the registry certificates to
authenticate. It makes use of the registry secret to either
store a .dockercfg file with username/password or
a registry.crt and registry.key files that will be used
by the requests session.
Signed-off-by: Clement Verna cverna@tutanota.com

Looks reasonable.

Ok, so I am not sure how to proceed with this change.

In that case, this seems to be an ad-hoc method for storing a certificate and key. :(

I tend to agree here with @twaugh, and it seems that the setup we have in Fedora infra is not the norm so maybe keeping this change as a patch maintained only in the fedora rpm is the way to go.
Another solution would be to go with @owtaylor first proposal

skopeo reads /etc/docker/certs.d, so could require configuration of certificates in the builder image. But for that approach, it would be good if the atomic-reactor code would also just understand certificates in that location, to avoid having to configure the certificates in three places. (And secrets in the builder image are a ratherugly.)

And change atomic-reactor so that it will use the certs in /etc/docker/certs.d in the builder image.
I might go the patch in Fedora way while working on atomic-reactor to use certs present in /etc/docker/certs.d.

I don't have a firm recommendation. The most straightforward way to just get things working would be to switch Fedora authentication to the registry to use passwords. I don't think the security of that is significantly lower, but it does require different configuration - you'd either have to hardcode services in the docker registry configuration. or do a bunch of LDAP configuration work. Feedback from Randy and Patrick about whether this is an acceptable route would be great.
The second most straightforward route would be, as you suggest, extending this patch to read  /etc/docker/certs.d and baking the certs into the buildroot image. This definitely violates best practices for container management - but might be secure enough if we check that there is no way for the buildroot image to be leaked out of Fedora infrastructure.
Or, you could just proceed with the approach here, but that's going to require skopeo work - I can help out with that if you want to proceed that way.
(From the Fedora perspective, the best thing would be OIDC authentication, but that would require seeing if the differences between docker-registry Oauth2 and Fedora OIDC can be papered over, AND adding support for Oauth2 to both this code and to skopeo ... an even bigger project.)

The most straightforward way to just get things working would be to switch Fedora authentication to the registry to use passwords

I think we are heading in that direction, that will make more sense, therefore I am closing this PR.

authors: cverna lcarva owtaylor

repo: projectatomic/atomic-reactor


text:
docker-novolume-plugin should be socket activated

This way if it dies or the next authorization will create it again.
docker-novolume-plugin might suffer the same problems that docker does as far as writing to stdout/stderr if journald dies.
It should be doing all of its output to syslog.
We want to make sure that docker rejects everything if the auth plugins die.

@rhatdan docker will eventually reject everything if one of the plugins dies because it will time out trying  to  reach  the plugin
I might have to understand better what's actually happening if plugins die after being lazy initialized
Thanks for opening this reminder

Ack to logs to syslog though

already done upstream

Awesome.

authors: rhatdan runcom

repo: projectatomic/docker-novolume-plugin


text:
Minor doc fix for #1196

Fixes incorrect docstring example in calicoctl profile command

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Stephen Schlie seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.

@heschlie You should sign the CLA :)

LGTM.

@caseydavenport I have, not sure why it isn't updating on github, checking the cla again just tells me I've signed it :/

authors: CLAassistant caseydavenport heschlie

repo: projectcalico/calico-containers


text:
TLS-enabled etcdv3 : grpc: timed out when dialing

I cannot get calico to connect to etcd, when etcd runs on https (with TLS enabled).
Here is my etcd configuration on a single test host:

ETCD_ADVERTISE_CLIENT_URLS=https://etcd.my.domain:2379
ETCD_CERT_FILE=/nix/store/mp1lvz3xxfh82k50m4kc2ly7acs3bgv5-master-keys/etcd.pem
ETCD_CLIENT_CERT_AUTH=1
ETCD_DATA_DIR=/var/lib/etcd
ETCD_DISCOVERY=
ETCD_INITIAL_ADVERTISE_PEER_URLS=https://192.168.1.1:2380
ETCD_INITIAL_CLUSTER=machine=https://192.168.1.1:2380
ETCD_INITIAL_CLUSTER_STATE=new
ETCD_INITIAL_CLUSTER_TOKEN=test
ETCD_KEY_FILE=/nix/store/mp1lvz3xxfh82k50m4kc2ly7acs3bgv5-master-keys/etcd-key.pem
ETCD_LISTEN_CLIENT_URLS=https://192.168.1.1:2379
ETCD_LISTEN_PEER_URLS=https://192.168.1.1:2380
ETCD_NAME=machine
ETCD_PEER_CERT_FILE=/nix/store/mp1lvz3xxfh82k50m4kc2ly7acs3bgv5-master-keys/etcd.pem
ETCD_PEER_KEY_FILE=/nix/store/mp1lvz3xxfh82k50m4kc2ly7acs3bgv5-master-keys/etcd-key.pem
ETCD_PEER_TRUSTED_CA_FILE=/nix/store/vv1h95iz6kn02158x33x644pkrwm7h86-worker-keys/ca.pem
ETCD_TRUSTED_CA_FILE=/nix/store/vv1h95iz6kn02158x33x644pkrwm7h86-worker-keys/ca.pem

Here is my Calico Node configuration:

docker run --rm --net=host --privileged --name=calico-node
--log-driver=none
-e ETCD_ENDPOINTS=https://etcd.my.domain:2379
-e ETCD_KEY_FILE=/nix/store/vv1h95iz6kn02158x33x644pkrwm7h86-worker-keys/etcd-client-key.pem
-e ETCD_CERT_FILE=/nix/store/vv1h95iz6kn02158x33x644pkrwm7h86-worker-keys/etcd-client.pem
-e ETCD_CA_CERT_FILE=/nix/store/vv1h95iz6kn02158x33x644pkrwm7h86-worker-keys/ca.pem
-e NODENAME="calico1"
-e NO_DEFAULT_POOLS=false
-e CALICO_LIBNETWORK_ENABLED=true
-e CALICO_STARTUP_LOGLEVEL=WARNING
-e CALICO_DISABLE_FILE_LOGGING=true
-e FELIX_LOGSEVERITYSCREEN=Warning
-e FELIX_LOGSEVERITYFILE=Fatal
-e FELIX_LOGSEVERITYSYS=
-e FELIX_LOGFILE=
-e FELIX_IPV6SUPPORT=false
-e CALICO_NETWORKING_BACKEND=bird
-e FELIX_DEFAULTENDPOINTTOHOSTACTION=Accept
-v /var/run/calico:/var/run/calico
-v /lib/modules:/lib/modules
-v /run/docker/plugins:/run/docker/plugins
-v /var/run/docker.sock:/var/run/docker.sock
80a64d11695d7d72dc02eb28d06aee79ee8af78ffb8e5575416956cf62d07947

etcdctl uses the same set of certificates and settings, and it connects to the etcd server just fine.
Disabling client-cert auth on etcd makes no difference. "One-way TLS" doesn't work either.
Everything works fine if I disable https all-together, making etcd listen on the http:// scheme.
Expected Behavior
Calico should be able to TLS-connect to its etcdv3 datastore.
Current Behavior
ERROR: Error accessing the Calico datastore: grpc: timed out when dialing
Possible Solution
I suspect that there is an error in the instantiation parameters of the etdv3 client from libcalico. Or perhaps a bug in the etcdv3 client itself? A possible scenario could be that the etcdv3 client always tries to connect to http://127.0.0.1:2379 - ignoring the ETCD_ENDPOINTS env-var that I set for Calico?
Setting loglevels to DEBUG doesn't reveal which endpoint the etcdv3 client actually tries to call. :(
Steps to Reproduce (for bugs)

Start etcd with above configuration
wget https://github.com/projectcalico/calico/releases/download/v3.0.1/release-v3.0.1.tgz
tar -xf release-v3.0.1.tgz
docker load -i release-v3.0.1/images/calico-node.tar
docker run .... (see above)

Context
I'm building a custom Nix module for Calico and I would prefer to be able to connect to a TLS-enabled etcd cluster.
Your Environment
Calico version v3.0.1
etcd version v3.1.6 as well as v3.2.15
Docker v17.09.1-ce
NixOS v17.09

Hm, the libcalico code for that is here: https://github.com/projectcalico/libcalico-go/blob/master/lib/backend/etcdv3/etcdv3.go#L55-L67
It seems correct to me, though we are ignoring a returned error there which isn't great, and could be related.

Also running into this problem. Calico cannot talk to etcd while etcdctl can.
Environment:
Calico Version: v3.0.0
Etcd Version: 3.2.12
Docker Version: 17.03.2~ce-0~ubuntu-xenial
Ubuntu 16.04 LTS

@johanot It looks like you need to add a volume mount to make those certificates available in the container.  Could you try adding that and see what you get then? If the error still exists could you add a larger log snippet from calico/node (see the note below).
@evident-sbellows Looking at your slack message here it looks like you've got the certs mounted in. Could you jump into the container and verify that the certs and key are available where you expect? If that still looks good could you add a larger snippet from the logs too (see the node below).
Could you both try setting CALICO_STARTUP_LOGLEVEL=debug and see if that provides any additional information?

I was able to run the make st-ssl target in calico_node which runs our system tests against an etcd that is configured for TLS so that gives a little confidence that it is not totally broken. @johanot I guess there is the possibility that it is only connecting to localhost.
Could you both take a look at your etcd logs and see if you see calico/node attempting to connect? It might provide some info about what the problem is too.  Thanks

I just got this same message: "grpc: timed out when dialing" and it turned out my problem was that I had a typo in the path to my etcdKeyFile, etcdCert, and etcdCACertFile entries in my calicoctl.cfg file.  So maybe verify that the path for those entries is correct in your config.
Also, @tmjd, it would be nice if calicoctl would return a more descriptive error when the path to one of the cert or key files was incorrect (i.e. pointed to a file that does not exist).  When I used etcdctl with a bad file path it gave me a nice error Error:  open /home/sysadmin/etcd.pem: no such file or directory

I've raised #1696, which I think is the real problem here.
@johanot @evident-sbellows could you confirm whether or not you're seeing the same issue as Brad?

With the v3.0.3 release yesterday there is better error reporting when there are issues with the etcd certificates.  @johanot and @evident-sbellows if you could try again and report your results it would be appreciated.

@caseydavenport @tmjd Sorry for the late response. I've now tested with v3.0.3 on the same setup. This is the error message I get from the two versions respectively:
v3.0.3:

Error accessing the Calico datastore: context deadline exceededCalico node failed to start

v3.0.1:

Error accessing the Calico datastore: grpc: timed out when dialingCalico node failed to start

I don't see much difference in the error reporting here? .. etcd is running and it is TLS-enabled. I can curl to https://etcd.domain:2379 and get a response.
There is a slight chance that there is a certificate misconfiguration still somehow, but why would that manifest as a timeout?
Anyway.. I switched attention to Kube-router now, and Kubernetes has no problem TLS-connecting to the same etcd instance.

@johanot Thanks trying again and reporting back.  Did you add a volume mount like I suggested in https://github.com/projectcalico/calico/issues/1659#issuecomment-363877333 so that the certificates are available in the calico-node container?

@tmjd I finally managed to get time to test again. Sorry (again).
I found out that two things where missing in my setup:

The volume-mount for the certs, as you mentioned. (thanks)
The CN / SAN of the server cert did not match the test hostname I had setup.

... Fixing either of the two still gave me:
v3.0.3:

Error accessing the Calico datastore: context deadline exceededCalico node failed to start

v3.0.1:

Error accessing the Calico datastore: grpc: timed out when dialingCalico node failed to start

... Fixing both 1 and 2 made Calico-node start up healthy.
I only found out for sure about both errors by manually curl'ing etcd.
[root@machine:~]# curl --cacert /nix/store/wz91nni0kpbbm8gmsq9sgxcxj5arnbmp-master-keys/ca.pem https://etcd:2379
curl: (51) SSL: no alternative certificate subject name matches target host name 'etcd'

[root@machine:~]# curl --cacert /file/not/found/wz91nni0kpbbm8gmsq9sgxcxj5arnbmp-master-keys/ca.pem https://etcd:2379
curl: (77) error setting certificate verify locations:
  CAfile: /file/not/found/wz91nni0kpbbm8gmsq9sgxcxj5arnbmp-master-keys/ca.pem
  CApath: none

If Calico had given me error messages like curl does, my life would have been easier :-)
Thanks for continuous support and work!

authors: bradbehle caseydavenport evident-sbellows johanot tmjd

repo: projectcalico/calico


text:
Windows package of 3.24.3 NSSM folder name is wrong.

Windows package of 3.24.3 NSSM folder name is wrong.
Expected Behavior

Clean install Calico on a windows node
Current Behavior

An error during install due to Calico scripts expects nssm.exe being under ./nssm folder, in fact falder now called nssm-2.24-103-gdee49fc due to 3a2abe57cb9467a34353d8c5dad3e56caf09c90a.
Possible Solution

Steps to Reproduce (for bugs)

Download install-calico-windows.ps1 for 3.24.3
Initiate install
Observe the error during install

Context

At the moment I can't proceed with Calico deployment on a windows nodes
Your Environment

Calico version: 3.24.3
Orchestrator version (e.g. kubernetes, mesos, rkt): kubernetes 1.22
Operating System and version: Windows Server 2019
Link to your project (optional):

A workaround for this is to pin to the older release of the calico-windows binary.
.\install-calico-windows.ps1 -ReleaseBaseURL "https://github.com/projectcalico/calico/releases/download/v3.24.1/" -ReleaseFile calico-windows-v3.24.1.zip

@chrisjohnson00 Thanks for reporting this. Let me see what I can do to fix this.

@chrisjohnson00 Can you download the installation script and try it again? This issue is fixed. I'll be working on a better solution in the mean time.

@chrisjohnson00 Can you download the installation script and try it again? This issue is fixed. I'll be working on a better solution in the mean time.

Will do! I was testing a non related change when I ran into this, so I will rebuild and test today.

I did not report this, just bubbled it up to your attention

Sorry my mistake. Thanks @p-v-a for reporting this issue.

@chrisjohnson00 Can you download the installation script and try it again? This issue is fixed. I'll be working on a better solution in the mean time.

Will do! I was testing a non related change when I ran into this, so I will rebuild and test today.

Yes, it seems to be working fine now!  Thanks!!

@song-jiang  - thanks for the fix!
While I have your attention.
Is there another url for install-calico-windows.ps1 which would allow me to pin our automation to a full version?  Instead of this link which is v3.24.x I'd like to pin to v.3.24.2 for example.
https://projectcalico.docs.tigera.io/archive/v3.24/scripts/install-calico-windows.ps1

I'm afraid there's no URL for v3.24.2 installation script.
If you really want to do it, maybe download v3.24.3 script and run
./install-calico-windows.ps1 -ReleaseBaseURL https://github.com/projectcalico/calico/releases/download/v3.24.2 -ReleaseFile calico-windows-v3.24.2.zip

I haven't tried it myself and it is not recommended.

I'm afraid there's no URL for v3.24.2 installation script. If you really want to do it, maybe download v3.24.3 script and run
./install-calico-windows.ps1 -ReleaseBaseURL https://github.com/projectcalico/calico/releases/download/v3.24.2 -ReleaseFile calico-windows-v3.24.2.zip

I haven't tried it myself and it is not recommended.

Yes, thanks.  Those URL parameters are part of the workaround I commented about initially on this issue.
Thanks for the help and quick responses on this!!

authors: chrisjohnson00 p-v-a song-jiang


text:
An option to configure the felix via operator

Hello there,
basically I want to be able to configure the felix software via helm installation so I can change some configs defined here: https://docs.tigera.io/archive/v3.7/reference/felix/configuration
I can find that my calico configuration is having felix cfg file, but it is hardcoded in the container: /etc/calico/felix.cfg
Expected Behavior
I am expecting to have ability to configure felix via values.yaml.
Current Behavior
Currently I am seeing it is not possible: https://docs.tigera.io/calico/latest/reference/felix/configuration
If you have installed Calico using the operator, you cannot modify the environment provided to felix directly.

Possible Solution
Maybe would be great if we can add different options in the values.yaml, for example:
installation:
  kubernetesProvider: EKS
  felix:
    LogFilePath: /tmp/logfile.log
    UsageReportingEnabled: false

Steps to Reproduce (for bugs)
Follow instruction for helm install calico
Context
I want to change some configurations in felix
Your Environment

Calico version: docker.io/calico/node:v3.25.0
Orchestrator version (e.g. kubernetes, mesos, rkt): EKS

Right now, the way to do this is to create a FelixConfiguration API object. However, this has to happen post-helm, because the API won't exist until after Calico is installed.

Hi @caseydavenport and thank you for the reply,
Is there any document how to do that? Sorry, I am not very familiar with the Felix and not sure if I know the proper steps I need to follow. Thank you.

I created a PR to address this issue: https://github.com/projectcalico/calico/pull/7836

Is there a way to configure the default FelixConfiguration that is created by the operator?
I want to enable wireguard on all nodes by default. The documentation for felix configuration is this:

Configuration for Felix is read from one of four possible locations, in order, as follows.

Environment variables.
The Felix configuration file.
Host-specific FelixConfiguration resources (node.).
The global FelixConfiguration resource (default).

Based on my understanding of this and a bit of experimentation, the only way to set a global default is to update the default resource. However, since this is something that is created by the operator, it cannot be IaC managed, unless the operator exposes configuration via helm.

@WoodyWoodsta I believe there is some work to expose FelixConfiguration via the helm chart in the works.
You should in the meantime be able to create a default FC with calicoctl.  e.g.,

kubectl create -f tigera-operator.yaml
calicoctl create -f fc.yaml
kubectl create -f custom-resources.yaml

This series allows you to set the default prior to the operator creating it. Obviously this would be better if the helm chart just supported it, though. And that's where we''d like to be.

https://github.com/tigera/docs/pull/1333
This PR documents changes added for the upcoming v3.28 Calico release that allow setting default felix configuration via helm

@caseydavenport  I am unclear on which yaml file and what version of API to use when trying to create the default resource with a customized FelixConfiguration.   Installation requires operator.tigera.io/v1 and FelixConfiguration option requires projectcalico.org/v3.
This is my yaml file for deploying the Calico CNI:   [I am trying to set iptablesBackend].  Where are the default options placed in this example?
---
apiVersion: operator.tigera.io/v1
kind: Installation
metadata:
  name: default
spec:
  calicoNetwork:
     # Note: The ipPools section cannot be modified post-install.
    ipPools:
      - blockSize: 122
        cidr: fd00:26c::/64
        encapsulation: VXLAN
        natOutgoing: Enabled
        nodeSelector: all()
---
# This section configures the Calico API server.
# For more information, see: https://docs.tigera.io/calico/latest/reference/installation/api#operator.tigera.io/v1.APIServer
apiVersion: operator.tigera.io/v1
kind: APIServer
metadata:
  name: default
spec: {}

It would go into the helm values.yaml file as outlined here: https://docs.tigera.io/calico/latest/reference/installation/helm_customization#common-customizations

Thanks for the Helm hint and documentation snippet!  There is not a lot of great documentation on installing Operator with Helm.   I believe I have combined my original Operator config correctly into this values.yaml file, but the iptablesBackend setting does not seem to be getting to the node/daemonset.  There is no FELIX_IPTABLESBACKEND entry after install.   Is it your opinion that this projectcalico.org/v3 settings can be pushed with a helm install?
Environment:
Kubernetes 1.30.4
Calico 3.28.1
Using command helm install -f values.yaml calico projectcalico/tigera-operator --namespace tigera-operator
imagePullSecrets: {}
installation:
  enabled: true
  kubernetesProvider: ""
  calicoNetwork:
    ipPools:
    - blockSize: 122
      cidr: fd00:26c::/64
      encapsulation: VXLAN
      natOutgoing: Enabled
      nodeSelector: all()

apiServer:
  enabled: true
certs:
  node:
    key:
    cert:
    commonName:
  typha:
    key:
    cert:
    commonName:
    caBundle:

defaultFelixConfiguration:
  enabled: true
  iptablesBackend: NFT

resources: {}
tolerations:
- effect: NoExecute
  operator: Exists
- effect: NoSchedule
  operator: Exists
nodeSelector:
  kubernetes.io/os: linux
podAnnotations: {}
podLabels: {}
tigeraOperator:
  image: tigera/operator
  registry: quay.io
calicoctl:
  image: docker.io/calico/ctl

/var/lib/kubelet
kubeletVolumePluginPath: None
kubernetesServiceEndpoint:
  host: ""
  port: "6443"

kubectl -n calico-system describe pod calico-node-9t4r8 | fgrep FELIX
      FELIX_DEFAULTENDPOINTTOHOSTACTION:  ACCEPT
      FELIX_HEALTHENABLED:                true
      FELIX_HEALTHPORT:                   9099
      FELIX_TYPHAK8SNAMESPACE:            calico-system
      FELIX_TYPHAK8SSERVICENAME:          calico-typha
      FELIX_TYPHACAFILE:                  /etc/pki/tls/certs/tigera-ca-bundle.crt
      FELIX_TYPHACERTFILE:                /node-certs/tls.crt
      FELIX_TYPHAKEYFILE:                 /node-certs/tls.key
      FELIX_TYPHACN:                      typha-server
      FELIX_IPV6SUPPORT:                  true

authors: PauloGDPeixoto WoodyWoodsta caseydavenport resworld ziptx


text:
Impact of a cni daemonset rolling restart?

We recently moved some more stateful applications (e.g. databases) to our k8s cluster, and we were wondering about the possible impact of a CNI restart (mostly in the context of a patch/minor version upgrade).
If my understanding of the CNI is correct then the daemonset pod need only be running when a pod is created or deleted in order to add/remove a pod IP from the network, and a daemonset pod restart should have no impact on the networking of existing pods?
Additionally, how do networkpolicies factor into this? I assume a change in a networkpolicy requires the daemonset pod to be up in order to process the change?
I could not find information related to this in the calico docs, althoug the CNI spec suggests the above is correct.
Your Environment

Calico version 3.26.3
Orchestrator version (e.g. kubernetes, mesos, rkt): kubernetes 1.28.2
Operating System and version:
Link to your project (optional):

@bh-tt You are right. Rolling update of the daemonset should have no impact on the networking of the existing pods. In order to process any change in the networkpolicy, the pods should be up and running.

authors: bh-tt sridhartigera


text:
Document host protection + IPIP

If you're using host protection with IPIP for workloads, you need to adjust the policy to allow IPIP packets.  We should document that somewhere.
In general, it'd be good to have a worked example of setting up host protection with k8s, say.

There is now the k8s worked example on the Host Protection Overview page.  It does not specifically call out the policy needed to allow IPIP, do we need that? if so I think probably just a note to that page would satisfy this issue.

ping @fasaxc would you be comfortable closing out this issue if we added a note on enabling IPIP to this doc? https://docs.projectcalico.org/master/getting-started/bare-metal/bare-metal
Can you clarify what the IPIP rule is supposed to apply to (all workloads? Only hostendpoints?)

Agree, note on that page sounds like the way to go.

@fasaxc can you make this adjustment yourself, or clarify what the IPIP rule is supposed to look so that @emanic can resolve it?

authors: fasaxc ozdanborne tmjd


text:
Update various field names to their v2 api equivalent

Description
Update various field names to their v2 api equivalent - a few field names were renamed during v2 api migration. This update should get them. Note that I looked for confignamev1: in libcalico-go/lib/apis/v2/* to locate renamed fields.

Todos

[X] Tests - see https://github.com/projectcalico/calicoctl/pull/1750

Release Note

None required

Good catch!


text:
Revert "[c2][encoder] Disable VP9 Encoder 10bit support"

This reverts commit 9787058103e452c007fae774c52804eb3f9ae433. We revert this commit because we have to support vp9 10bit to pass some performance test.
Case:
android.mediapc.cts.MultiTranscoderPerfTest#test4kHbd[10_Pair{video/hevc c2.intel.hevc.decoder} _Pair{video/x-vnd.on2.vp9 c2.intel.vp9.encoder}_true]
Tracked-On: OAM-120841

Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web  for more details.

SUCCESS: Android CI has completed Engineering Build for this issue.Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has started MERGE Build for this pr ,Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has completed MERGE Build for this pr, build is SUCCESS. Please check the linked Tracked-On issue/Android CI Web  for more details. For Binaries: /cactus-absp-or-local/celadon-merge/572

authors: nanazhan sysopenci


text:
Use linear decode output buffer in the hybrid-GPU case

In hybrid GPU case, video decoder could be iGPU and the coded images would be consumed by dGPU. Unfortunately, it's likely that we can hardly find a tiling format supported by both of them. To achieve best compatibility and make our life better, simply use linear buffers for decoded images.
By setting CPU_READ and CPU_WRITE flags, we force OneVPL to allocate internal buffers and blit decoded content to external buffers. In this way we can work around hardware limitation that DG2 cannot decode to linear buffers.

Improper Commit Message
Tracked on not found in commit message,
make sure Tracked-On: Jira-ticket  is present.

Improper Commit Message
Tracked on not found in commit message,
make sure Tracked-On: Jira-ticket  is present.

Close with https://github.com/projectceladon/MediaSDK_C2/pull/202.

authors: phreer sysopenci


text:
Discord integration sends empty messages

Notify version:
1.0.6
Current Behavior:
when trying to set notify to send messages over discord, it sends empty messages with not content.
this is not problem with the discord webhook as it works just fine if POST request is sent, the messages are sent as normal, but for some reason, notify sends empty message
Expected Behavior:
should send correct messages
Steps To Reproduce:
steps to reproduce the behavior:

Set provider-config.yaml to the the webhook

discord:
  - id: "subs"
    discord_channel: "bbh"
    discord_username: "Spidey Bott"
    discord_format: "{{data}}"
    discord_webhook_url: "https://discord.com/api/webhooks/*************(REDACTED_WEBHOOK_URL)"

run notify, for example, echo 'hi' | notify -pc ./provider-config.yaml
See that messages are being sent empty

Screenshots:

Couldn't repro the issue with the same config:

discord:
  - id: "subs"
    discord_channel: "#general"
    discord_username: "dogancanbakir-bot"
    discord_format: "{{data}}"
    discord_webhook_url: "https://discord.com/api/webhooks/XXX/YYY"

It seems to be an account-related issue.

Nonetheless, there should be some type of warning or error message. I haven't looked deeply into the tool, but isn't there a -debug flag that prints more information?

😉

😉

That Fixes the issue, Thank you good sir! have a nice day

authors: ahm3dkira ahmedgomaaa dogancanbakir

repo: projectdiscovery/notify


text:
Feature request: Make all config secrets templatable

Currently, we can't securely put alertmanager config in source control because secrets such as email smpt_auth_password must be in-lined in the config file.
Some configs like pagerduty service_key don't have the issue because they are templatable. Templates can easily be mounted individually as secrets without being part of source control, and then "referenced" by the config file.
My suggestion is to make all config secrets (documented here) tmpl_secrets instead. This would allow us to put the config file in source control without in-lining any secrets.

I'd suggest to adopt the practice of being able to source secrets from other file, like we do in prometheus (password_file).

Being able to read certain secrets from files isn't anything to do with avoiding putting secrets in files - they're still in files after all, and nothing prevents the usual pattern of checking in the config file with a placeholder and interpolation before laying it down.
Reading secrets also from separate files is supported only where it is common that the secret is updated/rotated by an automated process that's completely independent of the regular config file reload cycles (e.g. kubernetes bearer tokens), which I think is safe to say is not the case for any of the secrets that we're talking about in the alertmanager which are all very static with any rotation being rare and manual. In addition having only some templating fields come from separate files would be a bit weird and confusing, kinda similar to how users confuse some secrets being templatable for being a security feature rather than a risk.

The generic http_config block uses the password_file convention @roidelapluie referred to which is a convenient way of providing the basic_auth credentials in a secret for http-based alerts. It would be nice to be able to provide SMTP credentials in the same way.
@brian-brazil would you have any objection to the addition of a parameter like smtp_auth_password_file that would be mutually exclusive with smtp_auth_password? I'd be open to digging into the code and providing a PR.

What's your reason for wanting to add it? I've already covered how we approach these things in my above comment.

For consistency with the way we use secrets to pass basic_auth credentials for http-based clients. It's not obvious to me why SMTP credentials would be treated differently?

That was already answered in https://github.com/prometheus/alertmanager/issues/1704#issuecomment-679870168 above.

Reading secrets also from separate files is supported only where it is common that the secret is updated/rotated by an automated process that's completely independent of the regular config file reload cycles (e.g. kubernetes bearer tokens), which I think is safe to say is not the case for any of the secrets that we're talking about in the alertmanager

If you're referring to this, as best as I can understand, you seem to be grouping credentials into "dynamic" and "static" buckets to justify treating them differently.
Even if it were appropriate to lump plain basic_auth credentials into the "dynamic" bucket, it's not clear to me why alertmanager should think about them differently. What if I am deploying to an environment where the password for the SMTP service account is rotated on a daily basis? This distinction imposes AM's idea of what are "static" credentials, and makes it more inconvenient to use.

What if I am deploying to an environment where the password for the SMTP service account is rotated on a daily basis?

If you were, you would have provided that as your argument. However that is not the argument you provided, nor have I ever heard of such a setup. I prefer to base design decisions on users' actual use cases, not hypotheticals as those could be used to justify anything. I've already explained the reasoning, I don't feel the need to get involved in an further argument around this point.

I do agree with Brian, and I would also add that you can safely use the tools provided by your config management to store secrets in git, e.g. I am using ansible-vault for this purpose.

I prefer to base design decisions on users' actual use cases, not hypotheticals as those could be used to justify anything.

Do you think I would be spending my time posting on this issue, and even offering to even help code an enhancement, if this were just a hypothetical scenario that I dreamed up? Frequent rotation of credentials for production systems that you think of as "static" are a common practice, and it's a trend that will continue as secrets management in platforms like k8s makes it easier to do.
I hope you will reconsider this impediment to the use of AM in production scenarios at some point in the future, and I would be glad to help in whatever way I can. Thanks for your time.

It seems that all sides have been heard here, but anyway, the scope is beyond alertmanager as we'd like to keep this consistent within all the projects.
Can you please contact the Developers mailing list about your proposal: https://groups.google.com/g/prometheus-developers where more people will be able to discuss this matter, and we can adopt the same point of view in all the Prometheus projets.
Thanks!

authors: Wenzil atomic77 brian-brazil roidelapluie

repo: prometheus/alertmanager


text:
webhook custom style

Is it possible to make alertmanager webhook like this https://github.com/opsgenie/kubernetes-event-exporter#webhookshttp
https://github.com/opsgenie/kubernetes-event-exporter/blob/master/config.example.yaml
  - name: "pipe"
    webhook:
      endpoint: "http://localhost:3000"
      headers:
        X-API-KEY: "123-456-OPSGENIE-789-ABC"
        User-Agent: "kube-event-exporter 1.0"
      streamName: "applicationMetric"
      layout:
        endpoint: "localhost2"
        eventType: "kube-event"
        createdAt: "{{ .GetTimestampMs }}"
        details:
          message: "{{ .Message }}"
          reason: "{{ .Reason }}"
          tip: "{{ .Type }}"
          count: "{{ .Count }}"
          kind: "{{ .InvolvedObject.Kind }}"
          name: "{{ .InvolvedObject.Name }}"
          namespace: "{{ .Namespace }}"
          component: "{{ .Source.Component }}"
          host: "{{ .Source.Host }}"
          labels: "{{ toJson .InvolvedObject.Labels}}"

Or any other  opensource alert manage can implement ？

Your request looks similar to https://github.com/prometheus/alertmanager/issues/1496?

authors: simonpasquier xuchongchong


text:
Kubernetes SD: Allow restricting namespaces

Currently the Kubernetes SD lists and watches all changes for each role. This is problematic for two reasons:

Scalability: Watching and acting on every event of a Pods and Endpoints objects can get problematic due to the sheer amount of events in a large cluster.
Security: Advanced setups include role based access to limit what a service account is able to access, and thus will make Prometheus error when it tries to list/watch all namespaces, when it is only allowed to access certain namespaces.

I see two possibilities (this part is up for discussion):

An array of namespaces in the Kubernetes SD config, which if empty has the same behavior as it does now, so lists and watches all namespaces, and if specified only watches/lists those in the list.
A subsection to discover namespaces, which would also be relabelable.

The second solution seems like it is the desirable one, but besides adding complexity it requires the ability to watch/list namespaces in the first place, I'm not sure if this is ok. Possibly this is not an "or" decision, but both are required to cover everyones needs.
This will make #2191 a bit more complicated for the Kubernetes SD, but still doable.
@fabxc @beorn7 @juliusv @brian-brazil @matthiasr @alexsomesan

A subsection to discover namespaces, which would also be relabelable.

Let's try to avoid additional types of relabelling, they cause enough confusion as-is. A simple regex is the most we should need.

A simple regex is the most we should need.

Agreed.

Mh, if I cannot get a list of all namespaces due to access control, how can I apply a regex to it to filter namespaces?

@fabxc Yes that was my thought with

it requires the ability to watch/list namespaces in the first place, I'm not sure if this is ok.

Listing namespaces is a different level of access than looking inside them.
I'd like to have a way to select namespaces by label – since namespaces are
not nested, the only way to group by multiple dimensions is to construct a
namespace name somehow and use labels for the real breakdown. Selecting
with a regex is ambiguous in this case.
On Wed, Dec 14, 2016, 08:25 Frederic Branczyk notifications@github.com
wrote:

@fabxc https://github.com/fabxc Yes that was my thought with
it requires the ability to watch/list namespaces in the first place, I'm
not sure if this is ok.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/prometheus/issues/2280#issuecomment-266962327,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAICBrp8eJqr-suICbBozLAK0XKwLEQ1ks5rH5n_gaJpZM4LMYtm
.

I agree that label selection is the way to do it. Any SD-specific mechanism
should we add should also stick with the ideal methods of that particular
SD. And Kubernetes' design is relatively explicitly against encoding
grouping information into the plain name.
We probably need label selection and plain names for cases where Prometheus
doesn't have perms to list all namespaces/list resources without namespace
specification.
Have there been any scalability issues yet? The former could be solved via
relabeling too. But the collection under the hood would be quite exotic and
I'd certainly don't rate it as a target label anymore with that level of
indirection.
On Wed, Dec 14, 2016 at 8:38 AM Matthias Rampke notifications@github.com
wrote:

Listing namespaces is a different level of access than looking inside them.
I'd like to have a way to select namespaces by label – since namespaces are
not nested, the only way to group by multiple dimensions is to construct a
namespace name somehow and use labels for the real breakdown. Selecting
with a regex is ambiguous in this case.
On Wed, Dec 14, 2016, 08:25 Frederic Branczyk notifications@github.com
wrote:

@fabxc https://github.com/fabxc Yes that was my thought with
it requires the ability to watch/list namespaces in the first place, I'm
not sure if this is ok.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/prometheus/prometheus/issues/2280#issuecomment-266962327
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAICBrp8eJqr-suICbBozLAK0XKwLEQ1ks5rH5n_gaJpZM4LMYtm
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/prometheus/issues/2280#issuecomment-266964347,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEuA8mdLVY-b1zMqsQrHYYQCXc6MAFh7ks5rH5zogaJpZM4LMYtm
.

see #1951

@fabxc what I mainly meant in terms of the "scalability" issue is that if we have the informers setup to list/watch on all namespaces, then we are filling and updating our cache unnecessarily much when we could restrict it to the objects that we are interested in.

label selection is the way to do it. Any SD-specific mechanism
should we add should also stick with the ideal methods of that particular
SD.

Agreed, however then it would probably make sense to adapt here as well.

Yes, I totally agree that there's overhead and it will most likely become a scalability issue eventually. Was just wondering whether it came up it – but probably not given Kubernetes clusters still being fairly small on average.
How do you mean adapt? Just in terms of generating the appropriate config if possible or change the selection field in the operator in some way?

I think i have hit such problem which needs restricting namespaces or sth similar. My problem is described here. node_exporter as well as kube_state_metrics are deployed as daemonset and deployment respectively. I do not know what @brian-brazil had in mind with

For example the configuration for the node exporters should already be a separate scrape_config so splitting it out to a separate Prometheus should be straightforward by splitting the configuration file.

as node_exporter does not have separate configuration as it is a part of kubernetes_sd_config and it is a subject to autodiscovery. So I can not see any possibility to create separate configuration for

node_exporter metrics
kube_state_metrics
all other namespaces metrics

@widgetpl This is about a different issue. I commented on the stackoverflow thread to keep this on-topic.

@brancz I will not agree that this is a bit different issue, for me it sound a little bit different. One of the reasons of this issue is

Scalability: Watching and acting on every event of a Pods and Endpoints objects can get problematic due to the sheer amount of events in a large cluster.

and i think this is the same problem which I have ( large cluster and big amount of events/metrics ) unless you are talking only about kubernetes cluster itself without annotated services, pods etc. but I think they are included. In my opinion it depends how you look on it. I suppose that prometheus is watching and listing changes inside cluster through the API to know where it can find some metrics and when this cluster grows it has more and more Kubernetes objects to check. Allowing Prometheus to watch and list specific namespeces or even services, deployments, daemonsets inside those namespeces will reduce those events but it will also scrape specific metrics. Then we can be able to do functional sharding inside Kubernetes.
Unfortunately I have not found how i can make functional sharding inside Kubernetes cluster when everything is a Kubernetes object and my question was not about what should I do but how can I do this inside Kubernetes.
One solution which I mentioned is static_config but it is not best solution as my pod can float between Kubernetes nodes.
Another splution would be to set Prometheus target in static config to external IP of service but then Prometheus will not use Kubernetes API for service discovery.
Please correct me if I am wrong.

@widgetpl This is a different issue, please don't pollute the bug tracker.

We're in need of being able to run Prometheus without it having access to all namespaces as well. I'm willing to put together a PR, but is there a decision on what approach to take?
Our usecase would be satisfied with just having a list of namespaces (that is, no need for automagically inspecting what namespaces are available to the service account). Is that something everyone is satisfied with? If no config is given by the user, the current NamespaceAll would be used, I assume.
From a quick glance at the code, I'm changes would be around here? Anything in particular that would be done more than just looping over those?

Yes that's where I would start as well.
I'm thinking that we actually would want both, in fact I'm thinking of something like Namespace discovery similar to Target discovery, where you could either specify a static list of namespaces if they are known at point of configuring, or be able to specify a label-selector for listing namespaces (which would require RBAC roles to access the list namespaces endpoint). Although labeling namespaces seems to be getting more widely adopted it may also be wanted to filter based on the namespace name, although I would hold off on that until it is a wanted feature.
Wdyt @fabxc @brian-brazil @matthiasr ?

Do we still need this given RBAC? I'd presume it'll just return the namespaces you are allowed see.

Can we check what the k8 plans are there? In particular what happens when you don't have that role?

Currently, you can either list all namespaces or none. This is the same with all resources in Kubernetes - the list action applies to all of that resource type.  For namespaced resources (pods, services, etc), a role can be grant access on a per namespace basis, however, namespaces themselves are cluster level.
Unsure of future plans in k8s, though.

Implemented in #2642.

authors: bakins brancz brian-brazil carlpett fabxc grobie matthiasr nsams widgetpl

repo: prometheus/prometheus


text:
connection reset by peer

prometheus: version2.15.2
config:
global:
scrape_interval: 1m
scrape_timeout: 1m
evaluation_interval: 1m
prometheus-center  pull the sub_prometehus
sub_prometheus log:
level=error ts=2020-03-14T09:04:55.620Z caller=federate.go:184 component=web msg="federation failed" err="write tcp 10.151.16.31:9090->10.151.10.34:39190: write: connection reset by peer"

Thanks for your report. It looks as if this is actually a question about usage and not development.
It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.

authors: fcddk roidelapluie


text:
Merge release-2.33 forward into main

Thanks!


text:
Simplify Makefile promu fetch

Closes: https://github.com/prometheus/prometheus/issues/3460

For the test issues, see https://github.com/prometheus/prometheus/issues/3462.

@sdurrheimer

@sdurrheimer PTAL

@brian-brazil actually I think this is good  to go , it is quite straight forward.

It would be nice to get one official maintainer thumb on this one.

authors: SuperQ brian-brazil grobie krasi-georgiev


text:
Fix target metadata API for empty match_targets

According to the documentation, the target metadata API accepts it,
if no value for match_target has been provided. This was not the case
in the implementation.
This commit make the API behave as described in the docs.
Signed-off-by: Tobias Guggenmos tguggenm@redhat.com

Seems good to me, thanks! It would be nice to also have tests for this endpoint, but since there are none at all for it yet, l I won't force it in this PR.

authors: juliusv slrtbtfs


text:
Add test for sparse histogram compaction

NOTE: This is pointing to the sparsehistogram branch.
I was trying to make compactions work for sparse histograms, but turns out it already works. The query handling that we did many weeks ago seems to have taken care of block compaction for histograms even when we are compacting >1 block into one.
So in this PR, I am adding a unit test for that. I will extend that same test later for queries over block and >1 block.
cc @beorn7

(This is only for non-vertical compaction, vertical compaction is not supported yet)


text:
Support int and uint as datatype for template formatting

Fixes GH-9679
Signed-off-by: Jacques-Etienne Beaudet jebeaudet@gmail.com

Converted as a draft until I think about https://github.com/prometheus/prometheus/issues/9679#issuecomment-962161263

Thanks for your PR. For legal reasons, we require that all commits are signed with a DCO before we can merge them. See this blog post for considerations around this.
This means that the last line of your commit message should read like:
Signed-Off-By: Your Name <your@email.address>
If you are using GitHub through the web interface, it's quickest to close this PR and open a new one with the appropriate line.
If you are using Git on the command line, it is probably quickest to amend and force push. You can do that with
git commit --amend --signoff
git push -f $remote $remote_branch_for_pr

As always, be careful when force-pushing.

@roidelapluie Done for the DCO, mismatched my professional email for my personal email in the signed off thing, that's why it didn't match before.

thanks!

authors: jebeaudet roidelapluie


text:
Update GIE constructors - model engine file should be optional

Update the GIE model_engine_file parameter for both primary and secondary GIE constructors to allow either NULL/None or empty string ("") to specify none - and that the model engine file should be generated according to the config file parameters.

Done


text:
The unspecified location constraint is incompatible for the region specific endpoint

An error occurred (IllegalLocationConstraintException) when calling the CreateBucket operation: The unspecified location constraint is incompatible for the region specific endpoint this request was sent to.
getting the above error.

Hi!
Sounds possibly related to #16 -- but hard to know without more information about the parameters being passed (e.g., the region of the API, the region of the bucket, but even better would be the details of the request sent and response received).
Also, note that there was an S3 outage yesterday in US/East -- if you suddenly started getting errors from a configuration that was previously working, that could be the culprit.
Brian

repo: promptworks/aws-secrets


text:
Anyone deployed a version of Prose to Heroku?

Anyone got their own version of Prose running on Heroku?
I've followed the docs and got Gatekeeper up and running by Prose isn't playing ball
N00bing out over here :)

I just tried doing this, and luckily I stumbled upon this exchange. Saved me a ton of time. :)

authors: benedfit daestrada

repo: prose/prose


text:
Prose is mucking up YAML front-matter

Every time I try to change one of my posts now, prose.io does three things, all of which cause trouble:

published is coerced into a list.
Prose's publish button doesn't change published to true, but rather adds "false" (with the quotes) to the newly-created list.
The dates go from whatever they were before to {}.

Here is the "Revew your changes" view when I click the publish button on an unpublished post with no body, and then click the save button:
http://cl.ly/image/3m2R3E3K2k2C
Here's the actual post:
https://raw.github.com/crucornell/crucornell.github.com/master/_posts/2012-08-15-blog.md
I actually don't have to publish posts to get published coerced into a list and the date mangled - if I just open it up and click save it will do it.
Is anyone else getting this?

Also experiencing this. Especially the date-mangling was problematic, since an invalid date will stop a previously working page from building in Jekyll.

I'm also seeing this, specifically after making this edit with Prose.io

Any update on this?
Prose.io still removes the date when I edit a post, which then leads to a build error ('does not have a valid date in teh YAML front matter').
This is quite annoying...

authors: danielpcox gitkrax habi


text:
Initial configuration, should I have 2 yml config files?

I've created a configruation using the web interface and have downloaded it, the name is tfpfb.com.tar.yaml (I don't have an idea of where tfpfb.com comes from)
Should I have 2 yml? common.yml and the downloaded one? or should I rename the one I generated using the web interface to common.yml?
This is not clear on documentation

I agree. On the Your box is ready! page it says:

Alternatively you can click on the download button and copy the file to data/config/ in your protobox directory.

When instructions tell you to save a file in a directory they, generally, state what the filename should be. This is not mentioned on that page at all which implies the choice of name is up to the user. However, there is no explanation to indicate how vagrant knows how to find that newly created yml file.
Some allusion to the config filename and how it connects to vagrant would be most helpful.

I have got the thing working now and I ended up with two configuration files.
File A
The common.yml  that was created whilst following the Install process, and
File B
The one that was created when I had finished using Web GUI to build my custom configuration. It was created when I followed the instructions saying:

Once installed, open terminal to your protobox directory and paste the command in the textbox below...

$ vagrant protobox install 'http://getprotobox.com/share/mg71'

The file that was created was in data\config and named: mg71.yml

I note from comments in other issues that you can tell vagrant protobox to provide help info which lead me to realise you can make use of different configuration files by running a switch command.
Run vagrant protobox switch -h for the info:
$ vagrant protobox switch -h
Usage: vagrant protobox switch <config>
    -h, --help                       Print this help

Note: As I mentioned in Issue #170, if you do switch between configs, it is often worth running vagrant destroy to reset the box to avoid creating a provisioning mashup of multiple, and possibly conflicting, configs.

authors: johnniewalker neohunter

repo: protobox/protobox


text:
🛑 consensus-factory.io is down

In 276c2af, consensus-factory.io (https://consensus-factory.io) was down:

HTTP code: 404
Response time: 763 ms

Resolved: consensus-factory.io is back up in e4988d9 after 17 minutes.

repo: protocol/upptime-pln


text:
🛑 saft-project.com is down

In bdc6d80, saft-project.com (https://saft-project.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: saft-project.com is back up in 054c19d after 4 hours, 47 minutes.


text:
How to skip useless import path

I have a import which is not used for javascript
When use this plugin to generate the code, the useless import become a require(xxx)
How to disable this.

@dibenede
I want to generate both the server's code and the browser's javascript code
Some import is only for server like field value validate extend
Need a way to skip this, there are too may other extends can be find on github

repo: protocolbuffers/protobuf-javascript


text:
Review RWTH Aachen analysis of 388 open source energy projects and identify potential overlap

https://www.eenewseurope.com/en/study-shows-388-open-source-energy-projects/

This is our first citation and it comes from by home town. :partying_face:
We can learn from this publication a lot:

The references they used.
They extended the method we used in some ways.
We have to check their database and see if they are having projects we are missing.

We can also see here that it is relatively easy to derive peer-reviewed publications through our work. We should also try to do this in the future.

repo: protontypes/open-sustainable-technology


text:
Adding Low-Voltage Load Forecasting Datasets to Curated Lists

Hi! I was referred to this list, and since I couldn't find it on the list, I suggest adding it to the Curated Lists part. I am not affiliated.
URLs to the project:
https://github.com/low-voltage-loadforecasting/low-voltage-loadforecasting.github.io
This list specifically addresses the Low-Voltage Load Forecasting field and seems to be a useful resource to keep updated with regard to available datasets. The maintainers welcome contributions of additional datasets which can be utilized in low-voltage load forecasting.

Thank you so much @Zhenev. I had to shorten the description and link directly to the repository. We are doing this because the list gets automaticlly parsed for the study we are doing. I hope we can soon show a better website based on the metadata we are collecting.

Great to hear,  @Ly0n! Thank you for the update! I am currently checking some other sources, planning to suggest adding them if they do not appear on the list yet.
The website and the table view are amazing and so helpful. Looking forward to the updates to come!


text:
it doesn't work in windows 7(python3) as a tip "From station not found."

i use powershell.
how can i solve it?
PS C:\Python34\Scripts> tickets  北京 上海 20160701
From station not found.

@magic5650
Thank you for your spot. It was my original idea  that create this  tool for linux user who frequently used command-line. But it's seems that there are lots of Windows user. I will work on the Windows compatibility this week.

repo: protream/tickets


text:
Tune the Filebeat config in EFK module

We need to make several configuration templates for Filebeat so that we can collect them separately: infrastructure logs (eks, aws, elb, etc.), application logs, depending on the type of application. As an example, use specific labels on the pods, log_type: "multiline"

https://github.com/provectus/sak-efk/tree/issue_149

authors: akastav wallhided

repo: provectus/swiss-army-kube


text:
Add gRPC query to get all contract specs and record specs for a scope spec

Summary
There a several gRPC queries used by Explorer to fetch spec data. However, there is not a one and done query to get all contract and record specs under a scope spec, as there is for sessions and records under a scope. This would add a query that gives all requested information under a scope spec.
Proposal

TBD @iramiller

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

I just got some counts of specs on mainnet.
Scope Specs: 22
Contract Specs: 7609
Record Specs: 24983
Ave record specs per contract spec = 24983/7609 = 3.28334866605336
Ave contract specs per scope spec = 7609/22 = 345.863636363636
Ave record specs per contract spec = 24983/22 = 1135.59090909091
So the average result would have 1 scope spec + 3 contract specs + 1136 record specs = 1140 things in the result.
That's a pretty big result.
Furthermore, since there's only 22 scopes, I grabbed them all to get contract spec counts for each. Here's the distribution:

scope specs
number of contract specs

15
1

1
112

1
129

1
2401

1
30

1
5

1
747

1
9

That scope spec with 2401 contract specs probably has 2401 * 3.28334866605336 = 7883.32014719412 records. That's 1 scope + 2401 contract specs + 7883 record specs = 10285 things in the result. That's more than likely a problem.
Pagination doesn't make sense for this query since we're returning three different types of things. I guess only two might need pagination, but that's still complicated.
Testnet has more of each spec type, but the averages and that max are pretty similar.
I guess this is something to consider, and keep an eye on, but it's possible the query just doesn't work for some scope specs (or takes multiple tries).

Also, rather than adding a new query for this, it's probably best to just enhance the ScopeSpecification query to behave similar to the Scope query.

authors: SpicyLemon minxylynx

repo: provenance-io/provenance


text:
Unable to revert back to normal

I was checking some command and I saw the convert into captain one. I tried it but now I want to go back to normal, yet there seems to be no command to revert it back

Hey, I should really just include such a function already ^^
In this issue I talk about how to turn yourself back

authors: PlantXD PuckiSilver

repo: ps-dps/MobCaptains


text:
Required sampling rate unit for getFFTFreq Method?

For the getFFTFreq method, what should be the units for the sampling rate which needs to be provided to this method?  Should the sampling rate provided as a parameter to this method be in Hertz?

Yes. It is the sampling frequency in Hz.

Sorry if this follow-up question is somewhat redundant, but does this then mean that the "FastFourier" class (that the "getFFTFreq" method applies to) also deals in terms of Hertz too (for instance if I were to store the results of getFFTFreq in my own array, the individual array elements would then be in units of Hertz also?)?  Thanks.


text:
add Reverse operation

Make sure that you've checked the boxes below before you submit PR that adds a new operation:

[x] I implemented the operation for all applicable types
[x] I put all code in a seperate .go file named after the operation
[x] I included tests for all functions
[x] I documented all functions
[x] I named all functions using the OperationType convention. For example MinInt32 instead of Int32Min
[x] I included one testable example at the end of the test file
[x] I added a simple example in the Example section of Readme
[x] I updated the Operations section of Readme

Thanks for your PR, you're awesome! :+1:

Codecov Report

Merging #9 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master     #9    +/-   ##
======================================
  Coverage     100%   100%
======================================
  Files           5      6     +1
  Lines         772    943   +171
======================================
+ Hits          772    943   +171

Flag
Coverage Δ

#unittests
100% <100%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

reverse.go
100% <100%> (ø)

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 1c7c9e6...1ebee83. Read the comment docs.

authors: codecov-io psampaz

repo: psampaz/slice


text:
Log Verbosity erhöhen

Zusätzlich zu (val) loss noch accuracy epochal angeben

Vllt. ergänzend dazu: Wenn man CV nutzt wird in den Logs die Ergebnisse der einzelnen Folds gespeichert aber nicht die finale mean-Accuracy die im Terminal ausgegeben wird.
terminal_2024-07-30_11-16-28.txt
logz_2024-07-30_11-16-28.txt

repo: psorus/eereid