text:
Implement Kaniko plugin

ref: https://github.com/GoogleCloudPlatform/kaniko/issues/63
As of writing CBI only implements Git context.
To support Kaniko, we need to implement GCS context (#13) and/or ConfigMap context (#12).

PR: https://github.com/containerbuilding/cbi/pull/35

repo: containerbuilding/cbi


text:
Update containerd to a6a0c8b6e36415a151d93d096c1c0af9e0bd7977.

We've got more test coverage in the cri repo.
Let's update containerd to include https://github.com/containerd/containerd/pull/3711, so that we get more test coverage before cherrypicking it.
Signed-off-by: Lantao Liu lantaol@google.com

@Random-Liu - Is there a general strategy for updating this? Or said differently, is there a future where cri moves into containerd to avoid this need?

One test pod got killed with exit status 137, I guess it is OOM kill.
Triggered rerun.

Is there a general strategy for updating this? Or said differently, is there a future where cri moves into containerd to avoid this need?

Moving the CRI plugin into containerd/containerd shouldn't be too hard. The annoying part is to update all the test/release scripts and infrastructure.
For example, do we want a 1hour windows CRI validation presubmit test in the containerd repo? I think not...

The PR includes 2 test changes:

Tolerant not found error in restart test. There is a race condition that containerd event monitor may delete the pod sandbox before the test after it is killed. The state call is faster now, which somehow exposed this race.
The unknown state restart test is removed. I really don't want to remove it. However, after the runc state fix, getting container state doesn't need runc anymore, the original way to move runc around to produce a container in unknown state doesn't work any more... And I think very hard, but really can't find a way to create a container in unknown state in the test....

/test pull-cri-containerd-verify

Updated containerd again to include https://github.com/containerd/containerd/pull/3730 for the test.

/test pull-cri-containerd-verify

Apply LGTM based on LGTMs above.

source: gharchive/pull-request

repo: containerd/cri

license_type: permissive

license_source: github-api


text:
feat: add cgroup v2 support for metrics

This commits adds cgroup v2 support for collecting metrics in the shim.
Additionally, it uses CPU controller instead of the CPUAcct controller
for reporting CPU metrics back to containerd.
Closes #162

This PR includes changes from https://github.com/containerd/rust-extensions/pull/161
Could you pls rebase this PR against main branch?

Could you pls rebase this PR against main branch?

Absolutely. Done :)

LGTM
Would it be worth adding ubuntu 22.04 to https://github.com/containerd/rust-extensions/blob/27a503a474c68cdba7eff5b9f1b439d1846c39e0/.github/workflows/ci.yml#L96  I believe 22.04 has cgroupv2 by default so that would add some coverage? Maybe in a follow up incase there are other issues?

Could we merge this? @mxpv

Done!

authors: Mossaka jsturtevant mxpv

repo: containerd/rust-extensions


text:
Switch to using libnetwork's resolvconf package

Libnetwork provides a well-tested package for generating resolv.conf from the host's that has some features our current implementation does not. Swap to using their code and remove our built-in implementation.
Fixes #1533

Alright, they're still on the old Sirupsen package in the tag I used, but not master.
Let me bump to master...

Alright, the vendoring situation is getting absurd. Going to move the code into a pkg/ dir in our repo.

bot, retest this please

Failing cloud podman is due to Podman 0.9.3 making its way into the crio-tested repo, so we're pulling the version with the bug we fixed in 0.9.3.1

/approve

bot, retest this please

rebase

bot, retest this please

@rhatdan @baude @TomSweeneyRedHat @vrothberg PTAL

bot, retest this please

LGTM

Lots of failures?

Network flakes. Always the network.

bot, retest this please

@mheon, looks like some integration tests are unhappy.

Changes LGTM, I suspect some of the userns tests may need some tweaking though:
/go/src/github.com/containers/libpod/test/e2e/run_userns_test.go:11
  podman uidmapping and gidmapping --net=host [It]
  /go/src/github.com/containers/libpod/test/e2e/run_userns_test.go:68

  Expected
      <int>: 127
  to equal
      <int>: 0

Pushed again, integration tests should hopefully be fixed.

All green now

/lgtm

authors: TomSweeneyRedHat baude mheon rhatdan vrothberg

repo: containers/libpod


text:
trivial cleanups from golang

the results of a code cleanup performed by the goland IDE.
Signed-off-by: baude bbaude@redhat.com

LGTM

/lgtm

authors: baude giuseppe rhatdan


text:
Update all intra-package references to refer to containers/libtrust

Primarily this matters for jsonsign_test.go; otherwise go.mod records the dependency of containers/libtrust.test on docker/libtrust/testutil and adds spurious dependency entries that trigger repeated searches for unmigrated users.
@rhatdan PTAL.

LGTM

authors: mtrmac rhatdan

repo: containers/libtrust


text:
run: Add support for --bind (on linux, with virtiofsd)

This is extremely useful for local development cases, as
I can e.g. bind mount binaries I built on the host system.
Signed-off-by: Colin Walters walters@verbum.org

Maybe time to revive this PR?

authors: cgwalters vrothberg

repo: containers/podman-bootc


text:
Update Podman Desktop Playwright E2E with podman nightly

Images, parameters, etc. needs to be updated.

what images? params?

@adrianriobo I have update the description.

source: gharchive/issue

authors: adrianriobo odockal


text:
cannot obtain certificates map[*.mydomain.xyz:Time limit exceeded

Do you want to request a feature or report a bug?

BUG
What did you do?

What did you expect to see?
ACME with wildcard
What did you see instead?
Unable to obtain ACME certificate for domains "*.mydomain.xyz" : cannot obtain certificates map[mydomain.xyz:Time limit exceeded. Last error: NS prd4.azuredns-cloud.net. did not return the expected TXT record]
Output of traefik version: (What version of Traefik are you using?)

Version:      v1.6.0-rc6
Codename:     tetedemoine
Go version:   go1.10.1
Built:        2018-04-17_11:59:31AM
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml, provider, platform, ...)?
    [acme]
    email = "acme@fleeto.us"
    storage = "/var/data/acme.json"
    entryPoint = "https"

    [acme.dnsChallenge]
      provider = "namedotcom"
      delayBeforeCheck = 0
    [[acme.domains]]
      main = "*.mydomain.xyz"

Kubernetes 1.8.11 running on azure (acs-engine).
Name Provider: name.com
Env vars had been set in deployment of k8s.
DNS：*.mydomain.xyz CNAME mydomain.southeastasia.cloudapp.azure.com
If applicable, please paste the log output at DEBUG level (--logLevel=DEBUG switch)
time="2018-04-28T15:19:36Z" level=info msg="Testing certificate renew..."
time="2018-04-28T15:19:36Z" level=debug msg="Configuration received from provider ACME: {}"
time="2018-04-28T15:19:36Z" level=debug msg="Looking for provided certificate(s) to validate [\"*.mydomain.xyz\"]..."
time="2018-04-28T15:19:36Z" level=debug msg="Domains [\"*.mydomain.xyz\"] need ACME certificates generation for domain
s \"*.mydomain.xyz\"."
time="2018-04-28T15:19:36Z" level=debug msg="Loading ACME certificates [*.mydomain.xyz]..."
time="2018-04-28T15:19:36Z" level=debug msg="Building ACME client..."
time="2018-04-28T15:19:36Z" level=debug msg="https://acme-v02.api.letsencrypt.org/directory"
time="2018-04-28T15:19:36Z" level=info msg="Server configuration reloaded on :80"
time="2018-04-28T15:19:36Z" level=info msg="Server configuration reloaded on :443"
time="2018-04-28T15:19:36Z" level=info msg="Server configuration reloaded on :8080"
time="2018-04-28T15:19:36Z" level=debug msg="Received Kubernetes event kind *v1.Service"
time="2018-04-28T15:19:36Z" level=debug msg="Configuration received from provider kubernetes: {}"
......
time="2018-04-28T15:19:37Z" level=debug msg="Using DNS Challenge provider: namedotcom"
......
time="2018-04-28T15:20:37Z" level=debug msg="http: TLS handshake error from 10.240.0.65:55289: EOF"
time="2018-04-28T15:20:38Z" level=debug msg="http: TLS handshake error from 10.240.0.34:51857: EOF"
time="2018-04-28T15:20:38Z" level=debug msg="Received Kubernetes event kind *v1.Endpoints"
time="2018-04-28T15:20:38Z" level=debug msg="Skipping Kubernetes event kind *v1.Endpoints"
time="2018-04-28T15:20:39Z" level=debug msg="Received Kubernetes event kind *v1.Endpoints"
time="2018-04-28T15:20:39Z" level=debug msg="Skipping Kubernetes event kind *v1.Endpoints"
time="2018-04-28T15:20:40Z" level=debug msg="Received Kubernetes event kind *v1.Endpoints"
time="2018-04-28T15:20:40Z" level=debug msg="Skipping Kubernetes event kind *v1.Endpoints"
time="2018-04-28T15:20:41Z" level=error msg="Unable to obtain ACME certificate for domains \"*.mydomain.xyz\" : cannot
 obtain certificates map[mydomain.xyz:Time limit exceeded. Last error: NS prd2.azuredns-cloud.net. did not return the
expected TXT record]"

Changed my dns record from cname to a record:
Time limit exceeded. Last error: NS ns2bkr.name.com. did not return the expected TXT record]"

Thanks for your interest in Traefik 😃
It's an issue with your DNS provider.

Thank you @ldez , I will try to get support from name.com.

authors: fleeto ldez

repo: containous/traefik

license: MIT


text:
Limit label selector to Ingress factory.

What does this PR do?
Limit the Kubernetes label selector to the Ingress factory.
Motivation
Fix a regression when we switched to the newer shared informer factory.
Reviewer Notes
@yue9944882 could you please take a look and let me know if this seems good to you?
I'm also open to any suggestions how we could possibly implement this more elegantly.
Thanks!
Refs #3128

@ldez done.

I didn't really notice that this labelSelector should only be applied for ingress. How about renaming the parameter to ingressLabelSelector to emphasise it?

Code looks good, but do you think we should have a test for this? since we merged a regression without it being caught?

@dtomcej

Code looks good, but do you think we should have a test for this? since we merged a regression without it being caught?

I agree with you that we should have a test (in fact, tests for most of our low-level Kubernetes integration functionality). However, I don't think that unit tests would be really valuable in this case: The code in client.go largely depends on the client-go library, which means that any tests we write would heavily depend on the fake implementation that comes with it. IMHO, it'd be the classical case of testing against a test double without really testing the production code.
What I think we need are proper integration tests for Kubernetes. I've been working on #1889 for quite a while; it's not quite done, but I hope to finish it rather soon. Personally, I'd rather invest into these when it comes to validating our integration logic.

I manually tested the PR both with and without a configured label selector. Looks like it's working as expected.

authors: dtomcej timoreimann yue9944882


text:
Deribit: Add WebSocket channels

Added WebSocket chart.trades, ticker, and user.changes channels to Deribit API.
Additionally improved the code a little bit by giving the request models reasonable names.

Unfortunately this PR hasn't been approved/merged for several months.


text:
contenful-action erroring out

I am using the contentful action for my github action .

on:
  push:
    branches:
      - main
      - 'feature/**'
  pull_request:
    branches:
      - main
      - 'feature/**'
      - 'fix/**'
      - 'chore/**'

jobs:
  build:
    runs-on: [self-hosted, XXXXXXX]
    name: Contentful Migration Example
    steps:
      - name: Check out code into the directory
        uses: actions/checkout@v2

      - name: Contentful Migration
        id: migrate
        uses: contentful-userland/contentful-action@v1
        with:
          delete_feature: false
          space_id: ${{ secrets.SPACE_ID }}
          management_api_key: ${{ secrets.MANAGEMENT_API_KEY }}
        env:
          LOG_LEVEL: verbose

      - name: Create commit comment
        uses: peter-evans/commit-comment@v1
        with:
          body: |
            See changes to the [${{steps.migrate.outputs.environment_name }} ][1] Environment on Contentful.
            [1]: ${{steps.migrate.outputs.environment_url}}```

but t seems it is failing with following error

`Contentful Migration Example
Unexpected input(s) 'delete_feature', 'space_id', 'management_api_key', valid inputs are ['']`

it was an issue in my side and resolved

repo: contentful-userland/contentful-action


text:
Update dependencies

Fixes #62

Coverage decreased (-2.4%) to 84.444% when pulling 3aa6d33f34560addf941d695fc68f34c23920e2c on update-dependencies into a5372720dd4d76426d5444e8559ed28162037235 on master.

authors: coveralls loudmouth


text:
require_all 2.0 not compatible with contentful_model

$ ruby -v
ruby 2.3.5p376 (2017-09-14 revision 59905) [x86_64-darwin17]

$ cat Gemfile
source 'https://rubygems.org'
gem 'contentful_model'

$ bundle show
Gems included by the bundle:
  * activesupport (5.1.5)
  * addressable (2.5.2)
  * bundler (1.16.1)
  * concurrent-ruby (1.0.5)
  * contentful (0.12.0)
  * contentful-management (1.10.1)
  * contentful_model (0.2.0)
  * domain_name (0.5.20170404)
  * http (1.0.4)
  * http-cookie (1.0.3)
  * http-form_data (1.0.3)
  * http_parser.rb (0.6.0)
  * i18n (0.9.5)
  * json (1.8.6)
  * minitest (5.11.3)
  * multi_json (1.13.1)
  * public_suffix (3.0.2)
  * redcarpet (3.4.0)
  * require_all (2.0.0)
  * thread_safe (0.3.6)
  * tzinfo (1.2.5)
  * unf (0.1.4)
  * unf_ext (0.0.7.5)

$ cat test.rb
require 'contentful_model'

$ bundle exec ruby test.rb
/Users/joe/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/require_all-2.0.0/lib/require_all.rb:102:in `rescue in block in require_all': Could not require /Users/joe/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/contentful_model-0.2.0/lib/contentful_model/base.rb (uninitialized constant ContentfulModel::ChainableQueries). Please require the necessary files (RequireAll::LoadError)
	from /Users/joe/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/require_all-2.0.0/lib/require_all.rb:97:in `block in require_all'
	from /Users/joe/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/require_all-2.0.0/lib/require_all.rb:96:in `each'
	from /Users/joe/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/require_all-2.0.0/lib/require_all.rb:96:in `require_all'
	from /Users/joe/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/require_all-2.0.0/lib/require_all.rb:118:in `block in require_rel'
	from /Users/joe/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/require_all-2.0.0/lib/require_all.rb:117:in `each'
	from /Users/joe/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/require_all-2.0.0/lib/require_all.rb:117:in `require_rel'
	from /Users/joe/.rbenv/versions/2.3.5/lib/ruby/gems/2.3.0/gems/contentful_model-0.2.0/lib/contentful_model.rb:4:in `<top (required)>'
	from test.rb:1:in `require'
	from test.rb:1:in `<main>'

It looks like base.rb gets loaded before the file that defines ChainableQueries gets loaded?

It works if I downgrade the require_all gem to 1.5.0.

https://github.com/contentful/contentful_model/pull/96 probably fixes

@joevandyk yes that's exactly what's happening and, yes, downgrading require_all resolves it. I'll rename the ticket per your suggestion.

https://github.com/contentful/contentful_model/pull/97 shows that tests are failing on latest master.

The gemspec should explicitly depend on 1.5.0 until work can be done to make it work with require_all 2.0.

https://github.com/contentful/contentful_model/pull/96/files fixes it. @dlitvakb can that get merged and released?

Hi there,
If possible, lock the version in your local Gemfile (this works unless you have other conflicting gems).
Within the next 2 weeks, work on 1.0.0 will be restarted and the require_all dependency will be completely removed.
Cheers

@dlitvakb Not releasing a fix means that version 0.2 is broken for just about everyone until they come to this issue and learn that they have to add another (non-obvious) line to their Gemfile.
I think it would be worthwhile to release a new version of contentful_model that works on a new application.

Hey @joevandyk,
I can do the merge, but cannot make a release, I'm currently on vacation and away from a computer. If just merging and then using master works for you, that would be ideal.
Also, making a 0.2.1 release currently is non-trivial, as there are a lot of minor (but still) breaking changes, and I'd spend a lot of time figuring out what should or should not be cherry-picked.
Cheers

authors: dlitvakb joevandyk raybradley rezonant


text:
Can multiple useMDXComponent be used safely?

I'm making a list of mdx content. Each item in the list ends up needing to use useMDXComponent for the card. Is useMDXComponent expensive? Is it alright to use it multiple times on a page?

@khinshankhan Hi, I am not quite sure, if this is an issue. It sounds more as a question, than an error.
Maybe instead of asking help in an issue ticket you want to ask your question in the Contentlayer Discord Channel - probably you get an response / answer much quicker.

Oh I see. I joined and asked, thanks :+1:

authors: git-no khinshankhan

repo: contentlayerdev/contentlayer


text:
Fixed crash of dictionary serialization

Fixed this problem #28
Added HighloadV1
Added Some unit tests for dict serialization

Hello, out library already has some of the presented commits, which you have been added in prev pull request. Please update the last dev branch and reopen with new changes.


text:
@contexts no longer show up if I type the @ sign

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
Version: 1.95.3
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.1.0
continue v0.9.231 (pre-release)

Description
The context dropdown does not work.
Reference: https://discord.com/channels/1108621136150929458/1306627295967973387
To reproduce
No response
Log output
No response

Same here :(

Thanks for the heads up Priyash! Going to keep this open but will be following up in this thread: https://github.com/continuedev/continue/issues/2990

Hi folks, this should be fixed here: https://github.com/continuedev/continue/pull/3086
Will be available in pre-release v0.9.236 by end of day. Please let us know if you're still having issues!

authors: Patrick-Erichsen priyashpatil vlebert

repo: continuedev/continue


text:
Vagrant and Docker script changes for consul cluster integration

This set of changes brings in necessary scripting and configuration to bring up a consul cluster in our test/demo environments.
In subsequent PRs I shall bring in consul integration with the netplugin.
Note: As part of docker-in-docker script changes, I have moved to using the customized ubuntu image (viz. contiv/ubuntu) that is published and pulled from docker-hub. That image get's updated everytime a change is pushed to our Dockerfile in the repo (by using the automated-build feature of docker hub). This relieves us of managing the image every time Dockerfile changes. But this requires us to push Dockerfile to github first, which implies it requires some manual testing of image on Dockerfile editor's end. I need to see if I can eliminate this requirement while keeping goodness of automated-build.

@mapuri - I understand you already merged the changes; one small question - do we bring up both clusters (etcd and consul) with these changes and per the choice of runtime use one or the other?

do we bring up both clusters (etcd and consul) with these changes and per the choice of runtime use one or the other?

Yes, that is correct. For the test/demo environment I bring-up both the data stores. The idea is to be able to run systemtests for both the data-stores in one spin-up of the test environment. The data store will be chosen based on the configuration settings (for netplugin, netdcli etc). A little bit refactoring of code is needed there, which I am planning to push in my next PR.

I’m seeing some heisenbugs in the unit tests surrounding consul testing. Is it related to this patch?

On Jun 11, 2015, at 5:30 PM, Madhav Puri notifications@github.com wrote:
This set of changes brings in necessary scripting and configuration to bring up a consul cluster in our test/demo environments.
In subsequent PRs I shall bring in consul integration with the netplugin.
Note: As part of docker-in-docker script changes, I have moved to using the customized ubuntu image (viz. contiv/ubuntu) that is published and pulled from docker-hub. That image get's updated everytime a change is pushed to our Dockerfile in the repo (by using the automated-build feature of docker hub). This relieves us of managing the image every time Dockerfile changes. But this requires us to push Dockerfile to github first, which implies it requires some manual testing of image on Dockerfile editor's end. I need to see if I can eliminate this requirement while keeping goodness of automated-build.
You can view, comment on, or merge this pull request online at:
https://github.com/contiv/netplugin/pull/96 https://github.com/contiv/netplugin/pull/96
Commit Summary
Add necessary configuration for consul cluster in Vagrantfile
Add necessary configuration for consul cluster in dind script
File Changes
M Vagrantfile https://github.com/contiv/netplugin/pull/96/files#diff-0 (15)
M scripts/dockerhost/Dockerfile https://github.com/contiv/netplugin/pull/96/files#diff-1 (19)
M scripts/dockerhost/start-dockerhosts https://github.com/contiv/netplugin/pull/96/files#diff-2 (40)
Patch Links:
https://github.com/contiv/netplugin/pull/96.patch https://github.com/contiv/netplugin/pull/96.patch
https://github.com/contiv/netplugin/pull/96.diff https://github.com/contiv/netplugin/pull/96.diff
—
Reply to this email directly or view it on GitHub https://github.com/contiv/netplugin/pull/96.

@erikh do you have failed test logs? I can check. There were some timing related conditions around updating state and starting watch back to back in the tests for which I had added a workaround by adding a sleep. Are you seeing failures in Watch related tests?

authors: erikh jainvipin mapuri

repo: contiv/netplugin


text:
🛑 MPS - TESTPROCESS is down

In 5142699, MPS - TESTPROCESS ($TESTPROCESS_URL) was down:

HTTP code: 200
Response time: 678 ms

Resolved: MPS - TESTPROCESS is back up in 6d21096 after 10 minutes.

repo: conuti-das/status-lfrcs


text:
compilemessages not working in production using docker

What happened?
Running docker-compose -f production.yml run --rm django python manage.py compilemessages does not produce any .mo file, whereas running docker-compose -f local.yml run --rm django python manage.py compilemessages does.
What should've happened instead?
Running docker-compose -f production.yml run --rm django python manage.py compilemessages should produce .mo files at locale/<locale>/LC_MESSAGES.
Additional details
Logs show no error, i.e. processing file django.po in /app/locale/fr/LC_MESSAGES.
I suppose that the issue comes from the fact that the local.yml compose setup defines a volume for the django app whereas the production.yml does not.

Host system configuration:

Version of cookiecutter CLI (get it with cookiecutter --version):
OS name and version: Ubuntu 22.04.2 LTS
Python version, run python3 -V: 3.10.10
Docker version (if using Docker), run docker --version: 23.0.1, build a5ee5b1
docker-compose version (if using Docker), run docker-compose --version: 2.16.0

Running docker-compose -f production.yml run --rm django python manage.py compilemessages does not produce any .mo file, whereas running docker-compose -f production.yml run --rm django python manage.py compilemessages does.

I'm having a hard time spotting the difference between the 2 commands, did you mean to use local.yml in the 2nd one?

I suppose that the issue comes from the fact that the local.yml compose setup defines a volume for the django app whereas the production.yml does not.

That is correct, why do you need to compile messages on production?

I am sorry,  indeed I mean to use local.ymlin the second command (I have amended the issue accordingly).
Maybe I am missing something about how django translations work, but I have some static pages that are manually translated using version-controlled .po files and which are not properly translated in the served website if the .mo files are not present. Am I not supposed to use compilemessages for that? what am I missing?
Thanks in advance!

Right, the .mo files are ignored by git:
https://github.com/cookiecutter/cookiecutter-django/blob/6e7355a8c9a44926bc8456f722c9ed542ef8a7da/{{cookiecutter.project_slug}}/.gitignore#L49-L51
I actually don't know how one is supposed to handle this. The way I usually do it is generate them locally, commit these files in source control and call it a day, but maybe there is a better way to do that. I found this stackoverflow question, where the "right" answer is no but the practical answer is more around the lines of maybe 😃
To summarize:

These files should not in git as they are generated
We need to generate them before the application is started

That leaves 2 options (I think) to generate them:

when the Docker image is built
when the container starts

I feel like option 1 is better, as option 2 would mean we do the work multiple time (each time the container starts) and slow down start up time.

authors: browniebroke martibosch

repo: cookiecutter/cookiecutter-django


text:
[Bug]: n8n status running (unhealthy)

Description
Hello, I am trying to install n8n but it not working well. Can you please help me check it? I tried many way but look like it not work.
Minimal Reproduction (if possible, example repository)
I don't know how to reproduce it. Here is some screenshots

Here is the log

Here env inside docker
DB_POSTGRESDB_USER=0z83pfZQ6WQGuoCV
N8N_HOST=n8n-pw8sk84.tkgiare.com
DB_TYPE=postgresdb
NODE_VERSION=18.19.1
HOSTNAME=5c9de97a4d55
YARN_VERSION=1.22.19
SHLVL=1
DB_POSTGRESDB_PORT=5432
HOME=/home/node
DB_POSTGRESDB_DATABASE=n8n
NODE_ICU_DATA=/usr/local/lib/node_modules/full-icu
GENERIC_TIMEZONE=Europe/Berlin
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
SERVICE_FQDN_N8N_5678=https://n8n-pw8sk84.tkgiare.com:5678
SHELL=/bin/sh
N8N_RELEASE_TYPE=stable
PWD=/home/node
WEBHOOK_URL=https://n8n-pw8sk84.tkgiare.com
N8N_EDITOR_BASE_URL=https://n8n-pw8sk84.tkgiare.com
DB_POSTGRESDB_PASSWORD=UtIsC4KWyoRcguPS6s8O9imfrMKQInU4
DB_POSTGRESDB_SCHEMA=public
TZ=Europe/Berlin
NODE_ENV=production
DB_POSTGRESDB_HOST=postgresql
N8N_VERSION=1.38.2

Exception or Error
No response
Version
v4.0.0-beta.271

Hi, same thing here. when try to visit, the following msg:
404 page not found

could this be related to #2073 ?

could this be related to #2073 ?

If it related, I had some with healthcheck not running because I was using alpine as the base image and there was no curl installed. I use the healthcheck outside the docker image and this only came up on the latest version (v4.0.0-beta.271).

I was facing the same issue, i made two changes in the docker compose.yml.
instead of localhost use 127.0.0.1
bind the port but i don't think that does anything
 ports:       - '5678:5678'     healthcheck:       test:         - CMD-SHELL         - 'wget -qO- http://127.0.0.1:5678/'

I think the issue can be verified by executing the wget command on the container from the execute command section
Also I am not seeing the healthcheck ui, i believe that is because the healthcheck is being done based on docker healthcheck.
This is my first day using coolify so could be totally wrong about all things :D

Hi, same thing here. when try to visit, the following msg:
404 page not found
For those getting 404 and wondering why you cannot access n8n, its due to healthcheck failing. In my case changing it to 127.0.0.1 allows me to access n8n again.

Same issue here. Wget inside the container doesn't exist.
[COMMAND] docker inspect --format='{{json .State.Health.Status}}' ngkgcc8-153359868832
[OUTPUT] "starting"
[2024-May-21 15:34:50.846913]

[COMMAND] docker inspect --format='{{json .State.Health.Log}}' ngkgcc8-153359868832
[OUTPUT] [{"Start":"2024-05-21T15:34:29.84040601Z","End":"2024-05-21T15:34:29.955666544Z","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"},{"Start":"2024-05-21T15:34:34.960016774Z","End":"2024-05-21T15:34:35.060940428Z","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"},{"Start":"2024-05-21T15:34:40.065515946Z","End":"2024-05-21T15:34:40.166334183Z","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"},{"Start":"2024-05-21T15:34:45.169709751Z","End":"2024-05-21T15:34:45.29051727Z","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"},{"Start":"2024-05-21T15:34:50.295815317Z","End":"2024-05-21T15:34:50.419374948Z","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"}]
[2024-May-21 15:34:50.849970] Attempt 9 of 10 | Healthcheck status: "starting"
[2024-May-21 15:34:50.856968] Healthcheck logs: /bin/sh: 1: wget: not found | Return code: 1
[2024-May-21 15:34:55.960714]

[COMMAND] docker inspect --format='{{json .State.Health.Status}}' ngkgcc8-153359868832
[OUTPUT] "unhealthy"
[2024-May-21 15:34:56.054879]

[COMMAND] docker inspect --format='{{json .State.Health.Log}}' ngkgcc8-153359868832
[OUTPUT] [{"Start":"2024-05-21T15:34:34.960016774Z","End":"2024-05-21T15:34:35.060940428Z","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"},{"Start":"2024-05-21T15:34:40.065515946Z","End":"2024-05-21T15:34:40.166334183Z","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"},{"Start":"2024-05-21T15:34:45.169709751Z","End":"2024-05-21T15:34:45.29051727Z","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"},{"Start":"2024-05-21T15:34:50.295815317Z","End":"2024-05-21T15:34:50.419374948Z","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"},{"Start":"2024-05-21T15:34:55.423010837Z","End":"2024-05-21T15:34:55.542787818Z","ExitCode":1,"Output":"/bin/sh: 1: wget: not found\n"}]
[2024-May-21 15:34:56.058278] Attempt 10 of 10 | Healthcheck status: "unhealthy"
[2024-May-21 15:34:56.061511] Healthcheck logs: /bin/sh: 1: wget: not found | Return code: 1
[2024-May-21 15:34:56.063506] Removing old containers.
[2024-May-21 15:34:56.065402] New container is not healthy, rolling back to the old container.

Having the same issue as GeorgeNance, wget: not found. After disabling healthcheck, the container works perfectly fine and deploys as expected.

N8N has been already fixed since.
I also added wget/curl to nixpacks setup phase, so it should have installed, but unfortunately for example Rust nixpacks deployments does not include wget/curl in the start phase as it starts differently than others.

authors: ChrisvanChip GeorgeNance IRediTOTO andrasbacsai fcpauldiaz gkibria john-afolabi lego-sharat pushad

repo: coollabsio/coolify


text:
[Feat]: A services marketplace

Description
A marketplace (maybe a repo) for one click services.
Users can deploy or upload a new services from a website (e.g. market.coolify.io ) or from the same coolify ui.
Users can up vote and down vote new services.
Users can upload services by a web interface that ask for docker file and a docker compose file, and an environment variables, etc.
I know that's a lot of work, but it will be awesome.
Minimal Reproduction (if possible, example repository)
A feature request
Exception or Error
No response
Version
v4.0.0-beta.293

hey @ZilloweZ, I think the current solution is cool and easier to manage.
all things in one centralized place, easy to deploy too.
making a market place for people to upload stuff will be a lot of work, and we are devs, so i think github is a better place to handle those.

Yeah, I'm planning this for the future, maybe when v4 releases

authors: YazeedAlKhalaf ZilloweZ


text:
[Bug]: logout causes infinity alert loop "This page has expired. Would you like to refresh the page?"

Description
When I logged out from Coolify with Instance's Domain
the dashboard kept showing:

an alert

This page has expired.
Would you like to refresh the page?

this popup/modal

Minimal Reproduction (if possible, example repository)

added Instance's Domain
Log out
This kept happening, even if I close and reopen in another browser!
Only solution was to change the Instance's Domain sub-domain.

https://github.com/user-attachments/assets/3eb0f8d8-2803-4e4c-b3b8-d41d11e8c7c2
Exception or Error
No response
Version
v4.0.0-beta.319
Cloud?

[ ] Yes
[X] No

I cannot reproduce it. Can you please send me an email with an invitation link to your instance, so I can take a look?

Hi!
I have the same problem. I updated from 306 to 319 with the CLI installing .sh and now I'm getting the same error.
I cannot start new services and handling the old ones gives the same error.
I have restarted proxy, emptied browser cookies but have not found a fix yet. Pls inform if you get it sorted.

I am unable to reproduce this issue, please upgrade to the latest version of Coolify v4 and try again, and if this is still an issue, feel free to reopen this issue or create a new one.

I am also running into this exact issue, running on the latest 4.0.0-beta.360

authors: Bl0ckS0lid andrasbacsai louisjrdev mustafaabobakr peaklabs-dev


text:
Support the --no-cache Docker build flag

I'd like to have support for the --no-cache Docker build flag in Coolify as it is helpful if you need to specifically rebuild a specific image from scratch every time.

Whoops, just realised this is the wrong repo... I clicked the GitHub logo on the docs thinking it would lead me to the Coolify repo, my bad.

repo: coollabsio/documentation-coolify


text:
Performance test: ~2.5s to add 10,000 objects to an array

This issue is a follow-up to the replies to this tweet. I added 10,000 objects to an array, and on my it took about ~2.50s.
I'm using:
Chrome 118.0.5993.117 (Official Build) (arm64)
16GB, M1 Macbook Pro (2020)

Here is a sample trace:
Trace-20231031T225959.json
The code I used to add 10,000 objects to an array is this:
import { types } from "mobx-state-tree";
import { nanoid } from "nanoid";

const Bus = types.model({
  name: types.string,
  id: types.string,
});

const BusLine = types
  .model({
    distance: 0,
    stops: 0,
    buses: types.array(Bus),
  })
  .actions((self) => ({
    addBus(name: string) {
      self.buses.push({ name, id: nanoid(5) });
    },
  }));

const store = BusLine.create();

export function MSTTest() {
  return (
    <>
      <div>
        <button
          onClick={() => {
            performance.mark("1");
            for (let i = 0; i < 10000; i++) {
              store.addBus("hello world");
            }
            performance.mark("2");
            performance.measure("Add 10000 items", "1", "2");
            console.log("ADDED 10000");
          }}
        >
          Add 10000
        </button>
      </div>
    </>
  );
}

Do note that I didn't write this to try and be as optimal as possible, nor to make it the most helpful test for debugging performance issues. I wrote this to get a comparison with the other state management library I'm tested on the tweet.
For example, I generate an id for every object, which in isolation is noise, but in the context on my test and application was necessary, since I do need an id, and I generate them on the test where I use the other library.
Out of curiosity I ran a version of it that doesn't generate ids and the difference is trivial.

@mrkev thank you so much! I will adapt this into the existing benchmarks. I'm sure your own state library will keep your hands full, but let me know if you ever want to talk shop about MST/state management performance.
We'll get these numbers down. Reproduction steps like this are very helpful to diagnosing issues and proving solutions!

authors: coolsoftwaretyler mrkev


text:
docs: beautify badges

I've beautified a few badges by adding brand logos. For Python and PyPI, I've adopted the logo color from the CI badge because the original logo color (a shade of blue) doesn't go well with the dark gray background color of the badges.

Codecov Report

Merging #827 (729b669) into master (e8d6239) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #827   +/-   ##
=======================================
  Coverage   96.68%   96.68%
=======================================
  Files          41       41
  Lines        2986     2986
=======================================
  Hits         2887     2887
  Misses         99       99

Flag
Coverage Δ

unittests
96.68% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

authors: codecov-commenter sisp

repo: copier-org/copier


text:
Scaling on 2D

So right now in 2D, there is a problem
If you have a lower resolution (320x180, 2D Stretch)
This Happens:

What I recommend is to make a feature to rescale the text or provide a workaround to fix this problem. As I have been trying to fix it for an hour.

What version are you using?

3.2.3 (Latest)

1.0

Could you please try your project with 1.1 WIP. Make sure to make a copy of your project!
It could be that this problem is already solved. Support for all stretch modes is still in the work ;).

It seems like you are using the default theme. You need to create a custom one with your desire size and make it fit to your resolution. Hope that helps! 👍🏻

repo: coppolaemilio/dialogic


text:
Setting initial screen resolution

I couldn't find a way to size the terminal container to my needs yet. Is there any option I can pass to the V86Starter to set the screen resolution?

Unfortunately the resolution is set by the OS and the options are very limited (at least for vga). Better terminal emulation for the serial console could help with this (#172).

authors: Radiergummi copy


text:
🛑 Guangdianyun is down

In 0cae45b, Guangdianyun (https://www.guangdianyun.tv) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Guangdianyun is back up in c03bcf5.

repo: corcd/charlotte


text:
Clair not pulling NVD Feeds

Description of Problem / Feature Request
I believe my Clair engine is not pulling any NVD Data feeds. When looking at the docker logs, I see:
"fetching vulnerability update for [ubuntu, oracle, RHEL, Debian, Alphine]"
I tried this on builds v2.0.7 and v.2.0.6
Expected Outcome
To have a log entry or some verification that clair engine has successfully pulled nvd feeds.
Actual Outcome
No verification whatsoever, and I believe complete lack of pulling feeds. (So far my scans indicate far fewer vulnerabilities than expected and shown with other tools)
Environment

Clair version/image: v.2.0.6-7
Running on Amazon EC2 Instance with plenty of memory and storage provisioned. No other errors. Using klar for frontend if you would like to know.

Can you run an update with the --debug flag on and post the logs here? That should show us if NVD is maybe filtering your requests.

authors: LewisPlangrid jzelinskie

repo: coreos/clair


text:
Documentation: add a group query example for the ldap connector.

A lot of people seem to be confused about how they should implement group specific queries. Thought it would be nice to have this as part of our docs.

@ericchiang do you want me to replace user DN with just DN?

Added an LDIF object example to clarify "DN". Also moved the example to the config section.

@ericchiang any additional change suggestions?

repo: coreos/dex

license_source: bigquery


text:
*: remove upgrading related stuff

sorry everybody...
/cc @yichengq @philips @kelseyhightower @barakmich

LGTM

repo: coreos/etcd


text:
leasing: retry on errors from acquire txn

Gets should retry on transient failure, but the txn inserts a write, skipping
the retry logic in the client. Instead, check the error if the txn should be
retried.
Fixes #8372

oh just saw test CI failures... Are these related?

yeah, related

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a9b9ef5). Click here to learn what that means.
The diff coverage is 75%.

@@            Coverage Diff            @@
##             master    #8374   +/-   ##
=========================================
  Coverage          ?   77.12%
=========================================
  Files             ?      353
  Lines             ?    28091
  Branches          ?        0
=========================================
  Hits              ?    21664
  Misses            ?     4907
  Partials          ?     1520

Impacted Files
Coverage Δ

clientv3/leasing/kv.go
90.35% <75%> (ø)

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 a9b9ef5...cf0eb3b. Read the comment docs.

authors: codecov-io gyuho heyitsanthony


text:
fleetctl uses /root/.ssh while remote machine uses /home/core/.ssh for finding public keys

Hi,
We have a 3 node CoreOS cluster running and i start experimenting with auto deployment. I am trying to clone a repo in a execStartPre directive like:
execStartPre=/usr/bin/git clone git@github.com:some/repo.git /tmp/app
Every time i start the service i get an authentication failed. If i use this snippet git clone git@github.com:some/repo.git manually on the CoreOS remote it works perfectly.
After debugging i saw that the fleet client on the remote uses /root/.ssh instead /home/core/.ssh as its directory for looking up keys.
Any idea how to fix this issue?

You can change the user that runs the unit with User=core or User=root. Can you try that and see if it fixes your issue?

@robszumski Thanx this solved the issue for me!

authors: robszumski twanies

repo: coreos/fleet


text:
fleetctl start serv@1.service doesn't automatically start serv-sidekick@1.service

I have a "sidekick" unit serv-sidekick@.service:
[Unit]
Description=serv-sidekick
BindsTo=serv@%i.service
Before=serv@%i.service
...
[X-Fleet]
MachineOf=serv@%i.service

and a regular unit called serv@.service. I fleetctl submit both of them:
fleetctl submit serv@1.service
fleetctl submit serv-sidekick@1.service

and then just start serv@1.service.
fleetctl start serv@1.service

I would expect serv-sidekick@1.service to be launched automatically before serv@1.service is started due to the BindsTo and Before directives but this doesn't happen. Am I misunderstanding something about fleet? How can I accomplish this?

The unit file is there for reference: https://github.com/olalonde/coreos-bitcoind/blob/master/bitcoind-ebs%40.service (commented out the problematic directives)

Deprecating this issue in favour of https://github.com/coreos/fleet/issues/1388


text:
examples/terraform: Add experimental self-hosted etcd option

Add an option to try experimental self-hosted etcd which uses the etcd-operator to deploy an etcd cluster as pods atop Kubernetes and disables the on-host etcd cluster on controllers and gateway on workers
When enabled, configure locksmithd to coordinate reboots through self-hosted etcd since there is no on-host etcd to use.

Warning: This feature is still experimental and potentially dangerous. It is opt-in.

Closes #515

repo: coreos/matchbox


text:
file: add helper for updating timestamps

This adds an helper method to update all the timestamps on a file
through its raw FD, wrapping futimens.

/cc @cgwalters

repo: coreos/openat-ext


text:
Resource Prometheus can be created by Deployment?

What did you do?
I deployed a prometheus cluster by prometheus-operator, and the operator created prometheus
as statefulset.
The prometheus data
# kubectl get sts -n kube-system
NAME                DESIRED   CURRENT   AGE
alertmanager-main   1         1         5d
prometheus-k8s       1         1         5d

And then, I poweroff the master node (I have  3 master nodes) that prometheus pod exists.
What did you expect to see?
The Prometheus pod will run in other master nodes.
What did you see instead? Under which circumstances?
[root@master1 ~]# kubectl get po -n kube-system -o wide | grep prom
prometheus-k8s-0                                       3/3       Unknown             7          5d        10.244.0.59    master2

The pod can not run on other node.
Environment

Prometheus Operator version:
v0.24.0

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.0", GitCommit:"3d2c54994840f73bd2ac99e505a3cad2c70e8161", GitTreeState:"clean", BuildDate:"2018-08-08T01:40:36Z", GoVersion:"go1.10.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.0", GitCommit:"3d2c54994840f73bd2ac99e505a3cad2c70e8161", GitTreeState:"clean", BuildDate:"2018-10-18T20:21:30Z", GoVersion:"go1.10.2", Compiler:"gc", Platform:"linux/amd64"}

Does prometheus operator create the prometheus by deployment instead of statefulset?
And I don't want to delete the prometheus pod mannually.

@aixeshunter prometheus operator will use statefulsets as prometheus is a stateful backend. If you power down the node and don't drain it, the k8s scheduler won't reschedule it on a different node, also see https://kubernetes.io/docs/tasks/run-application/force-delete-stateful-set-pod/.

@s-urbaniak Thanks ! I have a question now: why prometheus operator not monitor prometheus pod status?
If operator can delete the prometheus pod with Unknown status automatically, is it better?

Monitoring the prometheus' pod status is in the responsibility domain of k8s, via the statefulset controller in the controller manager. The prometheus operator is supposed to only monitoring the statefulset status.

@s-urbaniak
I am sorry to ask you another question.
I found that alertmanager pod can be rescheduled in another node but prometheus not, and they were all controlled by statefulset.
[root@master1 prometheus-plugin]# kubectl get sts -n monitoring
NAME                DESIRED   CURRENT   AGE
alertmanager-main   1         1         46d
prometheus-k8s      1         1         46d

before the power down:
alertmanager-main-0                    2/2       Running    0          1d       172.18.1.53    node1.hikcloud
prometheus-k8s-0                       3/3       Running    0           1d       172.18.2.19    node1.hikcloud

power down the node1 and wait for 5m:
alertmanager-main-0                    2/2       Running    0          1m        172.18.2.32    master3.hikcloud
prometheus-k8s-0                       3/3       Unknown0           1d       172.18.2.19    node1.hikcloud

The Alertmanager resource yaml:
apiVersion: monitoring.coreos.com/v1
kind: Alertmanager
metadata:
  labels:
    alertmanager: main
  name: main
  namespace: monitoring
  resourceVersion: "11969572"
  selfLink: /apis/monitoring.coreos.com/v1/namespaces/monitoring/alertmanagers/main
  uid: d0ede83c-db34-11e8-966a-5254008abd3e
spec:
  baseImage: quay.io/prometheus/alertmanager
  externalUrl: http://127.0.0.1:9093
  replicas: 1
  version: v0.15.2

The Prometheus resource yaml:
apiVersion: monitoring.coreos.com/v1
kind: Prometheus
metadata:
  labels:
    prometheus: k8s
  name: k8s
  namespace: monitoring
  resourceVersion: "11998660"
  selfLink: /apis/monitoring.coreos.com/v1/namespaces/monitoring/prometheuses/k8s
  uid: f05c4968-db34-11e8-966a-5254008abd3e
spec:
  alerting:
    alertmanagers:
    - name: alertmanager-main
      namespace: monitoring
      port: web
  baseImage: quay.io/prometheus/prometheus
  replicas: 1
  retention: 168h
  ruleSelector:
    matchLabels:
      prometheus: k8s
      role: alert-rules
  serviceAccountName: prometheus-k8s
  serviceMonitorSelector:
    matchExpressions:
    - key: k8s-app
      operator: Exists
  storage:
    volumeClaimTemplate:
      spec:
        resources:
          requests:
            storage: 20Gi
        selector:
          matchLabels:
            app: prometheus-k8s
  version: v2.4.3

@aixeshunter there is no difference between the two, both are statefulsets. Please consider to iterate on the scheduling behavior of k8s with regard to statefulsets. The reason why alertmanager was rescheduled and prometheus can depend on the the specific situation in your cluster.
As per https://kubernetes.io/docs/tasks/run-application/force-delete-stateful-set-pod/#delete-pods:
Kubernetes (versions 1.5 or newer) will not delete Pods just because a Node is unreachable. The Pods running on an unreachable Node enter the ‘Terminating’ or ‘Unknown’ state after a timeout. Pods may also enter these states when the user attempts graceful deletion of a Pod on an unreachable Node. The only ways in which a Pod in such a state can be removed from the apiserver are as follows:

The Node object is deleted (either by you, or by the Node Controller).
The kubelet on the unresponsive Node starts responding, kills the Pod and removes the entry from the apiserver.
Force deletion of the Pod by the user.

The recommended best practice is to use the first or second approach. If a Node is confirmed to be dead (e.g. permanently disconnected from the network, powered down, etc), then delete the Node object. If the Node is suffering from a network partition, then try to resolve this or wait for it to resolve. When the partition heals, the kubelet will complete the deletion of the Pod and free up its name in the apiserver.
Normally, the system completes the deletion once the Pod is no longer running on a Node, or the Node is deleted by an administrator. You may override this by force deleting the Pod.

Hi, i have the same issue.
I use kubeadm to create kubernetes cluster. Maybe operator handler alertmanager lifecycle? I don't know more about it.
Kubernetes version information:
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.0", GitCommit:"ddf47ac13c1a9483ea035a79cd7c10005ff21a6d", GitTreeState:"clean", BuildDate:"2018-12-03T21:04:45Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.0", GitCommit:"ddf47ac13c1a9483ea035a79cd7c10005ff21a6d", GitTreeState:"clean", BuildDate:"2018-12-03T20:56:12Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"}

We moved everything to use a parallel pod management policy in the statefulset, we've seen that to help with this behavior. Let us know if it helps you too. I'm closing this, here but if you are still seeing behavior that you feel is not appropriate, please feel free to create a new issue! :slightly_smiling_face:

authors: aixeshunter brancz pytimer s-urbaniak

repo: coreos/prometheus-operator


text:
kube-prometheus: bind mount host rootfs into node exporter

Fixes https://github.com/prometheus/node_exporter/issues/474 in the operator
Fixes #569 (by making the mount explicit)

A lightbulb just turned on: we should keep in mind that the mountPropagation field is a beta feature and consider its use when making decisions about taking the operator to 1.0.0.

@squat good point, yes :+1:

A lightbulb just turned on: we should keep in mind that the mountPropagation field is a beta feature and consider its use when making decisions about taking the operator to 1.0.0.

kube-prometheus just happens to be part of this repository but is not versioned along with the Prometheus Operator so I don't think it's relevant. It is relevant however for the whole monitoring stack to be considered stable.

hmm, I believe CI failed, because I rewrote the commit message which in turn changed the commit hash, let me rebundle the jsonnet files.

CI resolved @brancz @squat PTAL

authors: brancz s-urbaniak squat


text:
check_root: add test for missing interpreters

Following up from https://github.com/coreos/scripts/pull/505.
INFO    build_image: Checking /mnt/host/source/src/build/images/amd64-usr/developer-983.0.0+2016-03-14-1832-a1/rootfs
/usr/libexec/git-core/git-contacts: /usr/bin/perl does not exist
/usr/libexec/selinux/semanage_migrate_store: /usr/bin/python does not exist
/usr/sbin/nfsiostat: /usr/bin/python does not exist
/usr/sbin/ebtables-save: /usr/bin/perl does not exist
/usr/bin/glib-mkenums: /usr/bin/perl does not exist
/usr/bin/import-tars: /usr/bin/perl does not exist
/usr/bin/diff-highlight: /usr/bin/perl does not exist
/usr/bin/mtrace: /usr/bin/perl does not exist
/usr/share/rsync/logfilter: /usr/bin/perl does not exist
/usr/share/rsync/files-to-excludes: /usr/bin/perl does not exist
/usr/share/rsync/file-attr-restore: /usr/bin/perl does not exist
/usr/share/rsync/lsh: /usr/bin/perl does not exist
/usr/share/rsync/rsyncstats: /usr/bin/perl does not exist
/usr/share/rsync/git-set-file-times: /usr/bin/perl does not exist
/usr/share/rsync/mnt-excl: /usr/bin/perl does not exist
/usr/share/rsync/atomic-rsync: /usr/bin/perl does not exist
/usr/share/rsync/rrsync: /usr/bin/perl does not exist
/usr/share/rsync/mapfrom: /usr/bin/perl does not exist
/usr/share/rsync/mapto: /usr/bin/perl does not exist
/usr/share/rsync/munge-symlinks: /usr/bin/perl does not exist
/usr/share/rsync/cvs2includes: /usr/bin/perl does not exist
/usr/share/git/contrib/fast-import/git-import.perl: /usr/bin/perl does not exist
/usr/share/git/contrib/fast-import/import-tars.perl: /usr/bin/perl does not exist
/usr/share/git/contrib/fast-import/import-directories.perl: /usr/bin/perl does not exist
/usr/share/git/contrib/hooks/update-paranoid: /usr/bin/perl does not exist
/usr/share/git/contrib/hooks/setgitperms.perl: /usr/bin/perl does not exist
/usr/share/git/contrib/stats/mailmap.pl: /usr/bin/perl does not exist
/usr/share/git/contrib/stats/packinfo.pl: /usr/bin/perl does not exist
/usr/share/git/contrib/buildsystems/generate: /usr/bin/perl does not exist
/usr/share/git/contrib/buildsystems/engine.pl: /usr/bin/perl does not exist
/usr/share/git/contrib/buildsystems/parse.pl: /usr/bin/perl does not exist
/etc/ssl/misc/tsget: /usr/bin/perl does not exist
/etc/ssl/misc/CA.pl: /usr/bin/perl does not exist
WARNING build_image: test_image_content: Failed #! check
INFO    build_image: Writing coreos_production_image_packages.txt
INFO    build_image: Writing coreos_production_image_licenses.txt
INFO    build_image: Extracting docs
INFO    configure_bootloaders.sh: Installing legacy PV-GRUB configuration
INFO    configure_bootloaders.sh: Installing legacy SYSLINUX configuration
INFO    build_image: Writing coreos_production_image_contents.txt

/cc @marineam

LGTM

authors: crawford marineam

repo: coreos/scripts


text:
Enable plugin for single server/location only

First of all many thanks for the great job the whole crs team is doing to make the web more secure!
I just found this plugin and would like to try it on my system. Is there any possibility to enable the plugin only on server/location level? In the old rule implementation there is the possibility to enable it with the variable crs_exclusions_phpmyadmin which allowed to enable it in specific directives only. Do you plan to support this here as well?
This is a very specific plugin and should be only enabled on the server/location where it is needed. On the other plugins this configuration option was not needed as they are for the general server protection, but I believe most users have also other websites on the web server where this exclusion rules could be a security risk.

Hi @flo-mic,
You can limit the uses of the phpmyadmin exclusion package, for instance by activating it only in the certain .
SecAction \
 "id:123456,\
  phase:1,\
  nolog,\
  pass,\
  t:none,\
  setvar:tx.crs_exclusions_phpmyadmin=1"

It's also possible to only activate it on certain paths - if you use Apache it can be done within a <Location>.

Sorry, I replied to you, but my solution only was relevant for CRS 3.3.x. Hopefully somebody else has a good solution for your problem. Otherwise we will take it to our next meeting.

I think we should keep the new plugin repositories private until they are officially released with CRS 4, to prevent confusion (otherwise we have two lots of REs officially available at once…)
Personally, I would put such a configuration in its own <VirtualHost> section, e.g. a WordPress only section with the WordPress RE plugin enabled.
@flo-mic For the avoidance of doubt, this rule exclusion plugin is the same as the one you can currently get in the official CRS release using the crs_exclusions_phpmyadmin variable, so you can get exactly the same effect by using it in, say, v3.3.2 as usual.

For context, the CRS official documentation currently advises the following:

Tip
If running multiple web applications, it is highly recommended to enable a rule exclusion package only for the location where the corresponding web application resides. For example, to enable the WordPress rule exclusion package only for locations under ‘/wordpress’, a rule like the following could be used:
SecRule REQUEST_URI "@beginsWith /wordpress/" setvar:tx.crs_exclusions_wordpress=1...

That is correct. We do not have this option when people want to restrict plugins / RE-plugins to individual hosts.
Moving REs to plugins is still the right move, but it does not really allow us to make them more flexbile with the use of Startup time exclusions.

I think we should implement this feature (and i'm sure @airween will agree with me). @dune73 I asked you this some time ago in some other discussion but you didn't reply: Are there any technical problems why this cannot be implemented?

Yes, true. I did not respond. Sorry.
The problem is this is applied context-wide. So either you load the rules / plugins on the server and then it's applied everywhere. Or you load it on the VH, and then you duplicate the rule base. Technically, that works AFAICT (but I do not run it in prod like this), but ModSecurity is known to produce memory leaks this way and hosters run thousands of VHs on the same server, so it's kind of annoying ...

@dune73 @azurit not sure if this is the right approach. But I combined the plugin and rule based implementation in my pgadmin plugin (https://github.com/flo-mic/pgadmin-rule-exclusions-plugin)
I think a option to enable/disable a plugin is not needed for every plugin. If we have a application specific plugin like pgadmin or phpmyadmin this option should be available. On generic plugins like antivirus or fake-bot detection it might not be required. Therefore the generic plugins can still use features like SecRuleUpdateTargetByTag.

@dune73 Why we cannot implement a configuration option which can be used to disable a plugin?
I think enable/disable is needed only for RE plugins like phpmyadmin, as @flo-mic already stated.

This should be implemented, can you confirm @flo-mic ?

Yes, it's implemented with latest plugin change. Thanks

authors: RedXanadu azurit dune73 flo-mic lifeforms


text:
Calling bind_to_thread on all api calls

Resolves #160
Resolves #161
Resolves #165
Resolves #108

I ran some really simple benchmarks with just calling alloc_zeros() and drop on the resulting slice a bunch of times in a row. The timings didn't change between this branch and main, so I think bind_to_thread()? is very cheap.

repo: coreylowman/cudarc


text:
Can you share the wallpaper?

https://github.com/cormiertyshawn895/PixelPerfect/blob/main/PixelPerfect/Screenshots/screenshot-animation.gif
I love PixelPerfect App.
I also like the blue wallpaper, can you share it?
Sorry about this issue.

Of course! The blue wallpaper is a simple gradient sampled from Mouse and Trackpad videos in System Settings.


text:
Run tests against PyPy and Python 3 on Travis

After #20 is merged, it will be possible to run futurize --stage2 in CI, then run the test suite against Python 3.
(In our quick experiments on Monday, stage 2 changed the behaviour of exec and broke the tests on Python 2.  We'll want to fix that before the tutorial in June, but we can start testing against Python 3 even before we adopt those changes on master.)
Once we're running multiple Python versions in CI, it might also be useful to test against PyPy as well as Python 3 - even without the customized Bits support it should work as that's "just" a performance optimization.  Perhaps we should even test on PyPy3!

Closed by #37.


text:
Can you guide me to use elliptical roi based on measurement data

Prerequisites

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

Description
I am new to cornerstone and have started it from 7 days back, so pardon me if my question is very basic or wrong.
I have loaded and displayed my Image in onInit and then I have a button on click of which I want to draw an elliptical tool of certain measurement. The code which I have written for it is :
const element = document.querySelector('.image-canvas');
const EllipticalRoiTool = cornerstoneTools.EllipticalRoiTool;

const measurementData = {
  visible: true,
  active: true,
  color: 'white',
  invalidated: true,
  handles: {
    start: {
      x: 300,
      y: 200,
      highlight: true,
      active: false
    },
    end: {
      x: 632.7370089285714,
      y: 623.59857142857143,
      highlight: true,
      active: true
    },
    initialRotation: 0,
    textBox: {
      active: false,
      hasMoved: false,
      movesIndependently: false,
      drawnIndependently: true,
      allowedOutsideImage: true,
      hasBoundingBox: true
    }
  }
}

cornerstoneTools.addToolState(element, 'EllipticalRoi', measurementData);
cornerstoneTools.setToolPassive('EllipticalRoi');

Its adding elliptical tool when I move mouse over element
What else should I write now, to display this tool on my displayed Image without any mouse movement?

I found the solution by using updateImage method

repo: cornerstonejs/cornerstoneTools

license: mit


text:
Cause 2: NotEnoughSpaceOnDiskException even though plenty free space

Avoid duplicates

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

Describe the bug

Upon opening the app I'm confronted with Cause 2 even though there is enough storage available.
Expected behaviour
No error message at all.

Steps to reproduce the issue

Open the app
You are shown the following error upon pressing "Details":

(sometimes multiple times)

Technical details

Mobile device: Samsung Galaxy Note 9
Android version: 10

Possible Fix
Maybe storage space availabiltity is not checked regulary?

Additional context
Since installing the app I almost ran out of storage once.

It might be helpful to enable copying the stack trace.

Thanks for your input! How much storage space is actually consumed? The current space threshold is set kind of high so this could happen if you go below the threshold

I still have ca. 600 MB of storage left.

@fabianhick for security we could not store information on SD/External card. Could you confirm that there is free space on internal memory? Thank you.

@AlexanderAlferov Sure! I currently only use internal storage.
Usage: 127.4/128 GB
Free memory: 594 MB

+1 for this issue. Samsung Galaxy A3, 553MB/15,5GB free

Same for me on a Samsung A3 2017. Even with >600Mb free memory (according to the system tools) it did not work. With now slightly above 700, it works again.
The critical thing about this is, that one only notices this issue when opening the app. My app has not been downloading keys for 5 days when I did so.

Me too! Samsung A3 2017 fails with 400 to 500MB of internal Storage, works with 1GB ( after deleting data of other apps). As it takes less than a second to update the status once it works, it is unlikely that there are 400MB of data downloaded!

Thanks for reporting guys. Our current assumption is that there is not enough space broadcast as available from the OS and we are looking into it.

I had this problem, too (on an A5). Even when there is actually not enough space, the error message should be improved. The consequence of the problem (not syncing with the server I guess, so not checking for infections?) should be clearly stated in the message.
And maybe a link to the OS to clear memory should be provided?

I am not convinced that this is a threshold problem. I guess the error is thrown falsely without passing the threshold. I encountered it on my BlackBerry with at least 500 MB free (so more than the 200 MB threshold that is currently set). It also seems to occur on iOS, even with more than 200 GB (!) free. Please see: https://twitter.com/henningtillmann/status/1276998571959689216

I also agree with @ArneLimburg, since this error will appear commonly anyway, the app should show a userfriendly error message.

@yorickreum Yes, the issue also occurs on iOS, but that's a different topic, as the error there is thrown by the (Apple) Exposure Notification Framework itself, and not the app.

@tkowark Okay! I will wait for the update and see if this fixes the problem on my BlackBerry.

Had the same problem on my Huawei p10 with ~710 MB internal storage free for the last 3 days (pictures attached).
Deleted some things (not because of that) and suddenly app worked again with no error. Tried to recreate it with going down with free storage but didn't work.
I did not update the App, so should be still a bug to fix.

The update was not deployed yet.

Same for me on a Samsung A3 2017. Even with >600Mb free memory (according to the system tools) it did not work. With now slightly above 700, it works again.
The critical thing about this is, that one only notices this issue when opening the app. My app has not been downloading keys for 5 days when I did so.

I think the fact that there is no automatic notification about the memory problem should also be changed.

Had the same issue the last days. Glad to see that there is already a potential fix available. Additionally I agree to @grpingel that there should be a notification to make the user aware that the app is not working properly due to low disk space.
I would assume that even with the fix this error might occur with having 500MB or less left. Maybe the error message could be improved by explaining to the user why this is not enough as the first reaction might always be something like "I have 400MB space left, what the hell is the App doing?"

Good point, we are thinking of improving the error message to explain this implementation detail.

Any update on this problem?
The App is now not working since more than 11 days on my device.
Due to FAQ it need 20MB, I have more than 600MB free space on internal storage.
Hopefully this bug will be fixed soon. Because without the risk detection this App makes absolutely no sense.

Same here. App is not updating for weeks. 500MB free space and still getting the error message.

Ran into the same problem (Google Pixel). I think the App should displays some numbers in the error message:

how much space is required (FREE_SPACE_THRESHOLD)
how much space it thinks is available.

Thanks for the suggestion @schulzch . We'll take this to the product managers and push for this to be implemented. As the free space seems to be wrongly reported by some OS, this would at least make clear which amount of free space to aim for.
Following suggestions for an error message:
"There is not enough space left on the device. The operating system reports that XXXMB are free and YYMB are needed for the App to perform risk calculation."
And this message should pop up as soon as the crash is detected, not only when opening the app.
Any additions / objections?

@tkowark As I wrote earlier: The message should clearly state that the app stops working correctly, too

Is this issue fixed with the release of 1.1.1 (which contains https://github.com/corona-warn-app/cwa-app-android/pull/760)?

Is this issue fixed with the release of 1.1.1 (which contains #760)?

Lowering the threshold is only a mitigation - the error message is still pretty much useless.

I'm still seeing this error message at v.1.3.0, Samsung a5 2016 at intern 15.4/16GB and extern 31.9/32GB memory consumption.
When more memory is free it works, but I still wish for a more consumer-usable error message

I have the same issue. I cannot wait, until it is fixed. So question: can I move everything to a new phone? Because if that is possible, I simply bye a second one...

@dl1chb unfortunately you cannot migrate the keys from your old phone to your new one unless you have root, for more info see here.

Dear @fabianhick, @dl1chb, @deepdigger, @feyyd1, @Ced4, @ArneLimburg, @sandrasie, @kilian-gebhardt, @drillabit, @Kroko7733, @yorickreum, and community:
We would appreciate some feedback: Do you still experience this issue with the actual CWA version 1.6.1? Thanks!
Best wishes,
DS

Corona-Warn-App Open Source Team

@dsarkar I managed to free up enough space and actually got a new smartphone. But I can update to 1.6.1 on my old and try to reproduce this if it helps you

Since CWA Android 1.7.1 is just being released, I would hang on for a little bit. I can't see it on the Google Play Store right now, but it should be out soon.

Dear @fabianhick, @dl1chb, @deepdigger, @feyyd1, @Ced4, @ArneLimburg, @sandrasie, @kilian-gebhardt, @drillabit, @Kroko7733, @yorickreum, and community:
We would appreciate some feedback: Do you still experience this issue with the actual CWA version 1.7.1? Thanks!
Best wishes,
DS
Corona-Warn-App Open Source Team

I did not experience this issue in the last weeks.

I tested it with 110 MB free storage and the app worked.
So it seems to work.

Should be fixed since CWA 1.5 since there have been no more reports about this issue.

Corona-Warn-App Open Source Team

authors: AlexanderAlferov ArneLimburg Ced4 Kroko7733 MikeMcC399 daimpi deepdigger dl1chb drillabit dsarkar ennyKey fabianhick feyyd1 grpingel heinezen jakobmoellersap sandrasie schulzch tkowark yorickreum

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


text:
display issues after deleting the rapid test profile

Description
Pop to the correct VC
Link to Jira

Can you please link the JIRA issue?

@nickguendling  yes sorry i already put it but for some reason it didnt appear before

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


text:
Clear recommendation needed whether or not to switch Active Region/App while traveling in Europe.

Where to find the issue
The issue occurs in directly linked or indirectly linked FAQs.
Describe the issue
A traveler arriving in a different EU location is faced with the choice as to whether to continue to use the CWA, or download a local app, and also whether to switch the Local Region to the country they are traveling in or about to travel in.  Some countries require Covid-19 tests to be made before arriving in the country, and some after arriving in the country to leave quarantine. So the handling of test-results also has to be taken into consideration.
Now that interoperability between several European Apps has been enabled, the in-app documentation and UI should reflect this, and the traveler should be given clear answer as to whether to stick with the CWA in the new country, or switch to the local compatible app.
Currently, this information can only be gleaned through linked faqs and is often contradictory depending on how many links you traverse. So linking is not sufficient.
Examples:
Caveat: I have included the UK NHS app in these examples, even though it is no longer EU and not compatible (but uses the Google/Apple AP), simply to give examples of issues that will almost certainly occur in other apps in future, if not already. I have not installed all national compatible apps to give a comprehensive as-is comparison because what follows are simply examples.
Example 1: FAQs
The EU claims that a switch is necessary when a test is performed:
"You can only insert a positive coronavirus test result in the app of the country where the test was taken."
https://ec.europa.eu/commission/presscorner/detail/en/qanda_20_1905#gateway
But elsewhere in the same FAQ
"Thanks to the EU interoperability gateway service, citizens can use one single app even when they travel cross-borders, while continuing to benefit from contact tracing and being able to report a positive test or to receive an alert."
The RKI linked from the CWA recommends sticking to the original Active Area when traveling:
"If you are in another EU country or in one of these countries and have made a molecular biological test (PCR test) which is positive, you can upload it to the Corona-Warn-App. To do so, it is necessary to verify your identity by calling the hotline +49 800 7540002."
(As an aside, often 800 numbers cannot be reached from other countries. My test with the French covid number failed, but the German number did work from Ireland).
Example 2: Local Capabilities
The CWA does not support extended functions in other countries. So by not transferring away from the CWA you would be at a disadvantage.
Other EU apps sometimes show local information.
E.g. Irish apps show local infection rates. It also enables a call-back number. UK app supports  QR-Code venue registration. Local regulations may also already be supported in some apps.
However, some apps do not let you use the app unless you switch to their active region (E.g. UK). So often the app's secondary value over and above the Google/API RPI tracking cannot be used unless the Local Region is set to the local country (deactivating the CWA).
In future, we can expect local diversification to play an even more important role.
Suggested change
Because linking to FAQs will inevitably lead to different sources (RKI, Telekom, SAP technical, BDI...) with often outdated information contradictions are inevitable. So linking to FAQs is not sufficient. One bullet point in the "Learn More and Help" wizard is what's needed. Alternatively, a sentence of recommendation in the Transnational Exposure Logging section.

Note - I deleted example 3, which showed the exposure logging as only being active since the Active Region was re-activated. I cannot reproduce this with the Irish App or any of the other EU compatible apps. Apologies if this caused anyone on the team to perform additional research.

Hey @alanrick ,
Thanks for the input. However, I'm still not sure whether you are addressing one issue or multiple issues at once. It would be better if you would create individual issues for each example in the respective repositories (cwa-website or cwa-wishlist).
Furthermore, I should note that your suggestion of putting the information is probably not practical, since we cannot update the app as often as the FAQs.

Corona-Warn-App Open Source Team

I'm trying to answer the question in the title "Clear recommendation is needed whether or not to switch Active Region/App while traveling in Europe". As you can see from the examples having different answers spread over different FAQs is confusing and worth avoiding.
My crude analysis of the other 8 transnational apps took several hours but resulted in a clear "yes - switch apps". Having this embedded in the app avoids the FAQ conflicts and confusion while simplifying the decision when arriving at the border.
I don't see any reason why this answer will change, even when more apps are added.

@alanrick wow - I did just look at your Excel sheet with the comparison of the apps.
Nice. I was not aware how many countries there are meanwhile.
Do you know if all these contries participate in DEK distribution / exchange with each other?
And another question: What is your definition of "open source"?

Thanks @ndegendogo . They are just scrappy notes and you're already found the first mistake. Germany is of course opensource, and Ireland sadly isn't. I added links to the repositories as I only stumbled on then by accident and they may not be true.
I assume the DEKs (Diagnosis Keys?) are exchanged, but strictly speaking it's my interpretation of "Interoperable - this app already talk to another app" from the official EU table.
All credit to the EU for fostering this diversity coupled with integration. And all credit to the German Warn App which appears to be the only one to support returning the results of a test in the app (after the qr-code scan).

@heinezen I’ve noticed that other apps display information on-place but extracted from a central source-of-truth using an API.

This appears to me to be the ideal solution in terms of trustworthiness, reliability and dynamic.
Ideally this question would be answered in the transnation section using this technique and that would fulfil your wish for it to be kept up to date.

authors: alanrick heinezen ndegendogo

repo: corona-warn-app/cwa-documentation


text:
Add least privilege principle for services

Please contact me before merging.

Role Separation for CWA-Server
CWA-Server consists of two separate services named Distribution and Submisison in this document. for security reasons, we strive to strictly follow least privilege  principle. Hence, we assume two different users (roles) assigned to both sservices.
In addition to those service users, both services will make use of Flyway to ensure consitent database migrations. This user will neeed to have another set of permisions to fulfill its function. We made sure that the flyway user is separted from the service users.
The following section will show examples how to create users with adequate role permissions.
How To Create Roles
Flyway
Flyway assumes a user with broad permissions to modify tables in the cwa database.
CREATE ROLE cwa_flyway_user WITH
  LOGIN
  NOSUPERUSER
  NOINHERIT
  NOCREATEDB
  NOCREATEROLE
  NOREPLICATION
  PASSWORD 'INSERT A PASSWORD HERE';

GRANT ALL ON DATABASE cwa TO cwa_flyway_user;

Distribution
The service should only have permission to the diagnosis_key table and does need to perform an SELECT and DELETE operation in this table.
CREATE ROLE cwa_distribution_user WITH
	LOGIN
	NOSUPERUSER
	NOCREATEDB
	NOCREATEROLE
	NOINHERIT
	NOREPLICATION
	CONNECTION LIMIT -1
	PASSWORD 'INSERT A PASSWORD HERE';

GRANT CONNECT ON DATABASE cwa TO cwa_distribution_user;
GRANT SELECT, DELETE ON TABLE public.diagnosis_key TO cwa_distribution_user;

# Only include this permisssions for deployments with activated "testdata" spring profile
GRANT INSERT ON TABLE public.diagnosis_key TO cwa_distribution_user;
GRANT USAGE, SELECT ON SEQUENCE public.diagnosis_key_id_seq TO cwa_distribution_user;

Submission
The service should only have permission to the diagnosis_key table and does need to perform an INSERT in this table and the related sequence for the id column.
CREATE ROLE cwa_submission_user WITH
	LOGIN
	NOSUPERUSER
	NOCREATEDB
	NOCREATEROLE
	NOINHERIT
	NOREPLICATION
	CONNECTION LIMIT -1
	PASSWORD 'INSERT A PASSWORD HERE';

GRANT CONNECT ON DATABASE cwa TO cwa_submission_user;
GRANT INSERT ON TABLE public.diagnosis_key TO cwa_submission_user;
GRANT USAGE, SELECT ON SEQUENCE public.diagnosis_key_id_seq TO cwa_submission_user;

Provide User Credentials To The Application
This sysem introduces the necessity to provide additional credentials on system startup. For docker-compose setups, the variables can be omitted and the relevant defaults will be used automatically.
Submission
POSTGRESQL_PASSWORD_SUBMISION
POSTGRESQL_USER_SUBMISION
POSTGRESQL_PASSWORD_FLYWAY
POSTGRESQL_USER_FLYWAY

Distribution
POSTGRESQL_PASSWORD_DISTRIBUTION
POSTGRESQL_USER_DISTRIBUTION
POSTGRESQL_PASSWORD_FLYWAY
POSTGRESQL_USER_FLYWAY

Please add the nice write up to a runbook.

We should merge #388 first. Then, the permissions on the id sequence can be removed here. The other way around this would create inconsistent state.

@ole-lilienthal Do you have actual issues popping up with the docker-compose setup in this PR? I tested with docker-compose and everything went fine because it will default for the postgres user in docker-compose. I made this behaviour more explicit now.

authors: MKusber johanneseschrig

repo: corona-warn-app/cwa-server


text:
R 2.20 FAQ update #rec_cert

EN

DE

Internal Tracking ID: EXPOSUREAPP-12442

@MikeMcC399 Thanks for reviewing! Enjoy Sunday evening!

@dsarkar
You're quite welcome! Have a nice evening yourself!

@MikeMcC399 FYI -  I actually added another sentence.

EN

DE

repo: corona-warn-app/cwa-website


text:
LINQ filtering methods

Hello,
I'm having some issues with the LINQ implementation, specifically the .Where() method. I'm trying to filter some data using methods like:
.Where(x => x.Contains("string"))
or
.Where(x => x.Id.Equals(id))
Here's an example:
var q = await arango.Query<AnotherTestPerson>("TestDB").Where(x => x.Fullname.Contains("D")).FirstOrDefaultAsync();
Is there any possibility for getting support for these methods in the future? For now I have to convert the arango IQueryable to a list, then cast it again as a IQuearyable to access those methods.

Just rewrite them with
.Where(x => Aql.Contains(x.Name, "D"))

or
.Where(x => x.Id == id)

Supporting the other notations should be possible though.

So calling methods normally in LINQ need to be done via the Aql functions? Or it's just the ones I listed here? I haven't tested other methods.

Yeah for now use the Aql. functions as they are bound to work natively - the ones with params are broken though
need to reqrite them with 1..5 named params or so
Just noticed even a basic list.Contains(y.Id)
needs to be written as Aql.Position(list, x.Prop)
if any aql function is missing you can write one yourself with
public partial class AqlCustom
{
        private static Exception E => new NotImplementedException();

        [AqlFunction("FNV64")]
        public static string Fnv64(object value)
        {
            throw E;
        }
}

Hi @coronabytes ,
I'm working together with @Mrjuanblack on a project where we use this project to integrate with Arango. Thank you for your feedback so far.
The problem we are facing is that we need to integrate with a number of clients through a LINQ abstraction. They are currently depending on this abstraction to make things work with other databases and we should be able to just swap the implementation to one supporting Arango without breaking the interface. Because of that, it is not feasible to rely on Aql helpers -- methods like 'Contains' should work like in any other LINQ implementation.
What is the underlying reason for the current implementation through Aql helpers? And what kind of work would need to be done to support things like '.Contains' directly? We are happy to contribute to the project to get this to work but need some pointers for where to start.
Looking forward to working with you on this.

Well the LINQ code is basically just a fork of the first Arango .NET driver. (https://github.com/ra0o0f/arangoclient.net)
Relinq should be able to quite easily support String. Math. and Date. functions,
if its GroupBy you are looking for thats gota be a challenge, but contributions are welcome,
I'll try to add String.contains and then the rest is just copy pasta.

Ok got you a starting point
https://github.com/coronabytes/dotnet-arangodb/tree/LinqMethods
the tricky part was finding out  how to move the <x.Name>.Contains inside the Arguments, but thats seems to work,
Please do not map StartsWith, EndsWith, Contains with LIKE Operator, because of % injection, use the native aql methods
also try x.Name.ToLower().Trim().Contains() and so on

@coronabytes awesome. We'll start working on this on a fork (after the holidays probably).

authors: Mrjuanblack coronabytes jannesiera

repo: coronabytes/dotnet-arangodb


text:
BUG: UI-Testing VIII

TESTED VERSION: STAGING 2023-11-24T14:43:55 bd01264

PRIO1 ... critical bug, blocks usage, !!relevant for release!!
PRIO2 ... bug, but doesn't block usage optional for release
PRIO3 ... not nice, not critical for release

[ ] (PRIO2) Startscreen is still not correctly resizing in the height. In the work--messenger-web branch visible. (also in staging)
[ ] (PRIO1) Rainbowwallet still doesn't work -> if problem is not yet solved, deactivate Rainbow wallet
[ ]  (PRIO1) Walletconnect still doesn't work -> if problem is not yet solved, deactivate Walletconnect

@steffenkux I check the Rainbow wallet and Walletconnect, its the issue with testnet. Before shifting to Goerli testnet when we did testing with Ethereum mainnet everything worked fine. So it should work fine with mainnet. If still it has to be decativated, tell me I will do it.

authors: Bhupesh-mfsi steffenkux


text:
Fix support for hostbuild executables when cross-compiling to non-windows on windows hosts

Defer the determination of whether to apply a .exe suffix for the byproduct copying and imported location setting if possible
Determine the .exe suffix first based on the existence of the hostbuild property and then fall back Rust_CARGO_TARGET_OS

This is an initial attempt at fixing the issue where we cross-compile on Windows to a non-Windows target but still build and call a host-build tool.
I don't quite know how to best automate testing this, but this is what I did manually:

Install ESP-IDF https://docs.espressif.com/projects/esp-idf/en/stable/esp32/get-started/windows-setup.html#standard-setup-of-toolchain-for-windows , a toolchain/framework for cross-compiling for Espressif MCUs.
Within an ESP-IDF enabled command prompt, configure Corrosion with tests enabled and -DRust_CARGO_TARGET=tensa-esp32-none-elf
Run ctest -C Debug -R hostbuild . to get build coverage for the described scenario. The test fails to build at the byproduct copying stage before the patch, and succeeds afterwards. The imported location path I verified via the cmake debug output Corrosion produces.

I've now been able to verify that the imported location bit also works. The "higher level" test case is to clone Slint from git, and from an ESP-IDF prompt change into examples/carousel/esp-idf/s3-box and run idf.py build. It fails before this patch trying to copy slint-compiler as byproduct, when it should be slint-compiler.exe. After this patch the build passes.

According to the test failures in the CI here, it seems that this requires further work.

Regarding testing, perhaps this is reproducible to some extent in the CI by just doing say -DRust_CARGO_TARGET=aarch64-unknown-linux-gnu (after installing such toolchain on Windows). I'm not sure entirely how to configure test.yaml for this.

Yep, this is much easier to reproduce on Windows without ESP-IDF by simply adding rustup target add aarch64-unknown-linux and then configuring with -DRust_CARGO_TARGET=aarch64-unknown-linux-gnu.

I'm going to need guidance though how to extend test.yaml best, if it's required to cover this in the CI.

Currently most of the CI logic sits in this action.yaml. But I would prefer to remove most of the logic from there and instead use CMake toolchain files.
Currently, the action has the assumption that host_os == target_os (and that the OS is either windows, mac or linux), so at the very least that would need to be changed. But it would probably be simpler to do the refactoring towards toolchain files instead.

if it's required to cover this in the CI.

I would prefer if this would be tested, otherwise it's hard to ensure that it doesn't break again.

Short update: I've experimented a bit with toolchain files + CMakePresets.json and it seems quite promising.

Sorry for the delay, this MR fell a bit off my radard.

I'm going to need guidance though how to extend test.yaml best, if it's required to cover this in the CI.

Do you know what dependencies you need to install for the test and what parameters CMake needs to be configured with?
Once we have that, adding a test should be very straight forward.

Yes, I think it’s sufficient to add rustup target add aarch64-unknown-linux and just configure with -DRust_CARGO_TARGET=aarch64-unknown-linux-gnu to reproduce the failure and see the tests pass with this PR.

What about installing a cross c compiler for the linking? I think the Linux targets all still default to using cc as the linker and not lld.

I think for all tests you'd indeed need a cross c compiler for linking. But for testing this particular issue I've just used this:

Configure with -DRust_CARGO_TARGET=aarch64-unknown-linux-gnu
Run ctest -C Debug -R hostbuild .

With master it fails:
Test project C:/dev/corrosion/build
    Start 37: hostbuild_build
1/3 Test #37: hostbuild_build ...................***Failed   14.96 sec
    Start 38: hostbuild_run_rust-host-program
2/3 Test #38: hostbuild_run_rust-host-program ...***Not Run (Disabled)   0.00 sec
    Start 39: hostbuild_cleanup
3/3 Test #39: hostbuild_cleanup .................   Passed    0.15 sec

50% tests passed, 1 tests failed out of 2

Total Test time (real) =  15.21 sec

The following tests did not run:
         38 - hostbuild_run_rust-host-program (Disabled)

The following tests FAILED:
         37 - hostbuild_build (Failed)
Errors while running CTest
Output from these tests are in: C:/dev/corrosion/build/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.

...
  Error copying file (if different) from "C:/dev/corrosion/build/test/hostbuild/build-hostbuild/x64/Debug/cargo/build/x86_64-pc-windows-msvc/debug/rust-host-program" to "C:/dev/corrosion/build/test/hostbuild/build-hostbuild".
...

But this PR it succeeds.

Rebase pushed.

Thanks!

Any chances in backporting that in the 4.x branch and having a release?
This issue is preventing our Windows users to use Slint for MCUs from C++.

authors: jschwe ogoffart tronical

repo: corrosion-rs/corrosion


text:
AllOf schemas generate inconsistent models when combining schemas containing properties with the same name

When having an AllOf keyword combining two schemas and those schemas contains properties with the same name the generator seems to pick one of them instead of trying to combine them. Which one is chosen seem to be random causing generated models to switch randomly between them when generating.
Example:
allOf:
  - $ref: "http://foo.com/schema.yaml"
  - type: object
    properties:
      foo:
        type: number
        minimum: 5

Where http://foo.com/schema.yaml would define the same property, for example:
properties:
  foo:
    type: number
    minimum: 0

This would generate a class containing foo defined by a generated subclass from one of the schemas, seemingly picked randomly.

The heuristic for properties attempts to find properties provided by various routes. (The most controversial part is then,else, dependentSchemas and dependencies - these can, of course, be completely incompatible, and you should be TryAs() the target types to determine which to use; but we found some common patterns where it was useful to provide "guesses" on the base which are clearly only valid if the relevant part is valid.
The order of search is deterministic
required is overridden by
allOf is overridden by
then is overridden by
else is overridden by
dependentSchemas is overridden by
dependencies is overridden by
$ref/$recursiveRef/$dynamicRef is overridden by
properties
And they are stored in an ImmutableArray, with the overrides performed "in place".
Any local properties are enumerated in the order in which they are found in the schema.
Testing this with JSON schema equivalent to your example:

Create a file baseschema.json

{
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "allOf": [
        {
            "$ref": "./schema.json#"
        },
        {
            "type": "object",
            "properties": {
                "foo": {
                    "type": "number",
                    "minimum": 5
                }
            }
        }
    ]
}

Create a file schema.json

{
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
        "foo": {
            "type": "number",
            "minimum": 0
        }
    }
}

Then, running the type generator (I have tried with 2.0.5 and 2.0.6)
generatejsonschematypes.exe --rootNamespace Example --outputPath Generated .\baseschema.json

This generates two types - one for each of the distinct foo properties.
One is in Baseschemajson.AllOf1Entity.FooEntity.*
One is in SchemaJson.FooEntity.*
The properties exposed in the BaseschemaJson type and the SchemaJson type are of the correct local types, and the validation is performed correctly.
So, I think I must be misunderstanding the issue described.
Could you zip up an example with the relevant files and a .cmd or .ps1 that runs any necessary prep (I presume you are translating from yaml to JSON at some point in your pipeline) and the generator tool, along with any tools (and version numbers) needed to repro the  issue.
Thanks.

Got it! OK; I'm not sure why this is happening because I thought it was deterministic - but clearly not!
We'll prioritize a fix.

Just waiting for a CI build and the fix should be up on nuget.org by about 12pm GMT.

authors: Fresa mwadams