text:
[BUG] grayskull pypi jsons failure.

Describe the bug
Receive the following failure when attempting to use grayskull to general recipe for 'jsons' pypi package. AttributeError: Hash information for sdist was not found on PyPi metadata.
Presumably a bug as no indication of missing hash on pypi side:

To Reproduce

grayskull pypi jsons
Expected behavior
Creation of

Outputs
If applicable, add the output to help explain your problem.
Environment:

conda list

packages in environment at

Name                    Version                   Build  Channel
alabaster                 0.7.12                     py_0    conda-forge
astroid                   2.5.2            py38haa244fe_0    conda-forge
attrs                     20.3.0             pyhd3deb0d_0    conda-forge
babel                     2.9.0              pyhd3deb0d_0    conda-forge
beautifulsoup4            4.9.3              pyhb0f4dca_0    conda-forge
boost-cpp                 1.74.0               h54f0996_2    conda-forge
brotlipy                  0.7.0           py38h294d835_1001    conda-forge
bzip2                     1.0.8                h8ffe710_4    conda-forge
ca-certificates           2020.12.5            h5b45459_0    conda-forge
cairo                     1.16.0            hb19e0ff_1008    conda-forge
certifi                   2020.12.5        py38haa244fe_1    conda-forge
cffi                      1.14.5           py38hd8c33c5_0    conda-forge
cfitsio                   3.470                h0af3d06_7    conda-forge
chardet                   4.0.0            py38haa244fe_1    conda-forge
click                     7.1.2              pyh9f0ad1d_0    conda-forge
click-plugins             1.1.1                      py_0    conda-forge
cligj                     0.7.1              pyhd8ed1ab_0    conda-forge
colorama                  0.4.4              pyh9f0ad1d_0    conda-forge
conda                     4.10.0           py38haa244fe_1    conda-forge
conda-build               3.21.4           py38haa244fe_0    conda-forge
conda-package-handling    1.7.2            py38h8934438_0    conda-forge
console_shortcut          0.1.1                         4
cryptography              3.4.7            py38hd7da0ea_0    conda-forge
curl                      7.76.0               hf1763fc_0    conda-forge
docutils                  0.17             py38haa244fe_0    conda-forge
expat                     2.3.0                h39d44d4_0    conda-forge
filelock                  3.0.12             pyh9f0ad1d_0    conda-forge
fiona                     1.8.18           py38h91b197a_1    conda-forge
fontconfig                2.13.1            h1989441_1004    conda-forge
freetype                  2.10.4               h546665d_1    conda-forge
freexl                    1.0.6                ha8e266a_0    conda-forge
gdal                      3.2.2            py38hacca965_2    conda-forge
geopandas                 0.9.0              pyhd8ed1ab_0    conda-forge
geos                      3.9.1                h39d44d4_2    conda-forge
geotiff                   1.6.0                h8e90983_5    conda-forge
gettext                   0.19.8.1          h1a89ca6_1005    conda-forge
git                       2.30.2               h57928b3_1    conda-forge
glob2                     0.7                        py_0    conda-forge
grayskull                 0.8.5              pyhd8ed1ab_0    conda-forge
hdf4                      4.2.13            h0e5069d_1004    conda-forge
hdf5                      1.10.6          nompi_h5268f04_1114    conda-forge
icu                       68.1                 h0e60522_0    conda-forge
idna                      2.10               pyh9f0ad1d_0    conda-forge
imagesize                 1.2.0                      py_0    conda-forge
intel-openmp              2020.3             h57928b3_311    conda-forge
isort                     5.8.0              pyhd8ed1ab_0    conda-forge
jinja2                    2.11.3             pyh44b312d_0    conda-forge
jpeg                      9d                   h8ffe710_0    conda-forge
kealib                    1.4.14               h96bfa42_2    conda-forge
krb5                      1.17.2               hbae68bd_0    conda-forge
lazy-object-proxy         1.6.0            py38h294d835_0    conda-forge
libarchive                3.5.1                h8686738_1    conda-forge
libblas                   3.9.0                     8_mkl    conda-forge
libcblas                  3.9.0                     8_mkl    conda-forge
libcurl                   7.76.0               hf1763fc_0    conda-forge
libffi                    3.3                  h0e60522_2    conda-forge
libgdal                   3.2.2                h48ef39c_2    conda-forge
libglib                   2.68.0               h1e62bf3_2    conda-forge
libiconv                  1.16                 he774522_0    conda-forge
libkml                    1.3.0             h9859afa_1013    conda-forge
liblapack                 3.9.0                     8_mkl    conda-forge
liblief                   0.10.1               ha925a31_2    conda-forge
libnetcdf                 4.7.4           nompi_h3a9aa94_107    conda-forge
libpng                    1.6.37               h1d00b33_2    conda-forge
libpq                     13.1                 h4f54205_2    conda-forge
librttopo                 1.1.0                hb340de5_6    conda-forge
libspatialindex           1.9.3                h39d44d4_3    conda-forge
libspatialite             5.0.1                h6b539a6_4    conda-forge
libssh2                   1.9.0                h680486a_6    conda-forge
libtiff                   4.2.0                hc10be44_0    conda-forge
libwebp-base              1.2.0                h8ffe710_2    conda-forge
libxml2                   2.9.10               hf5bbc77_3    conda-forge
lz4-c                     1.9.3                h8ffe710_0    conda-forge
lzo                       2.10              he774522_1000    conda-forge
m2-msys2-runtime          2.5.0.17080.65c939c               3    conda-forge
m2-patch                  2.7.5                         2    conda-forge
m2w64-gcc-libgfortran     5.3.0                         6    conda-forge
m2w64-gcc-libs            5.3.0                         7    conda-forge
m2w64-gcc-libs-core       5.3.0                         7    conda-forge
m2w64-gmp                 6.1.0                         2    conda-forge
m2w64-libwinpthread-git   5.0.0.4634.697f757               2    conda-forge
markupsafe                1.1.1            py38h294d835_3    conda-forge
mccabe                    0.6.1                      py_1    conda-forge
menuinst                  1.4.16           py38he774522_1
mkl                       2020.4             hb70f87d_311    conda-forge
msys2-conda-epoch         20160418                      1    conda-forge
munch                     2.5.0                      py_0    conda-forge
numpy                     1.20.2           py38h09042cb_0    conda-forge
openjpeg                  2.4.0                h48faf41_0    conda-forge
openssl                   1.1.1k               h8ffe710_0    conda-forge
packaging                 20.9               pyh44b312d_0    conda-forge
pandas                    1.2.3            py38h4c96930_0    conda-forge
pcre                      8.44                 ha925a31_0    conda-forge
pip                       21.0.1             pyhd8ed1ab_0    conda-forge
pixman                    0.40.0               h8ffe710_0    conda-forge
pkginfo                   1.7.0              pyhd8ed1ab_0    conda-forge
poppler                   21.03.0              h9ff6ed8_0    conda-forge
poppler-data              0.4.10                        0    conda-forge
postgresql                13.1                 h0f1a9bc_2    conda-forge
powershell_shortcut       0.0.1                         3
progressbar2              3.53.1             pyh9f0ad1d_0    conda-forge
proj                      8.0.0                h1cfcee9_0    conda-forge
psutil                    5.8.0            py38h294d835_1    conda-forge
py-lief                   0.10.1           py38h4b9bc1a_2    conda-forge
pycosat                   0.6.3           py38h294d835_1006    conda-forge
pycparser                 2.20               pyh9f0ad1d_2    conda-forge
pygments                  2.8.1              pyhd8ed1ab_0    conda-forge
pylint                    2.7.2            py38haa244fe_0    conda-forge
pyopenssl                 20.0.1             pyhd8ed1ab_0    conda-forge
pyparsing                 2.4.7              pyh9f0ad1d_0    conda-forge
pyproj                    3.0.1            py38he394cdd_1    conda-forge
pysocks                   1.7.1            py38haa244fe_3    conda-forge
python                    3.8.8                hdbf39b2_4
python-dateutil           2.8.1                      py_0    conda-forge
python-libarchive-c       2.9              py38haa244fe_2    conda-forge
python-utils              2.5.6              pyh44b312d_0    conda-forge
python_abi                3.8                      1_cp38    conda-forge
pytz                      2021.1             pyhd8ed1ab_0    conda-forge
pywin32                   300              py38h294d835_0    conda-forge
pyyaml                    5.4.1            py38h294d835_0    conda-forge
rapidfuzz                 0.12.5           py38hb99c5c2_0    conda-forge
requests                  2.25.1             pyhd3deb0d_0    conda-forge
ripgrep                   12.1.1               h301d43c_1    conda-forge
rtree                     0.9.7            py38h8b54edf_1    conda-forge
ruamel.yaml               0.16.12          py38h294d835_2    conda-forge
ruamel.yaml.clib          0.2.2            py38h294d835_2    conda-forge
ruamel.yaml.jinja2        0.2.4                      py_1    conda-forge
ruamel_yaml               0.15.80         py38h294d835_1004    conda-forge
setuptools                49.6.0           py38haa244fe_3    conda-forge
shapely                   1.7.1            py38h2426642_4    conda-forge
six                       1.15.0             pyh9f0ad1d_0    conda-forge
snowballstemmer           2.1.0              pyhd8ed1ab_0    conda-forge
soupsieve                 2.0.1                      py_1    conda-forge
sphinx                    3.5.3              pyhd8ed1ab_0    conda-forge
sphinxcontrib-applehelp   1.0.2                      py_0    conda-forge
sphinxcontrib-devhelp     1.0.2                      py_0    conda-forge
sphinxcontrib-htmlhelp    1.0.3                      py_0    conda-forge
sphinxcontrib-jsmath      1.0.1                      py_0    conda-forge
sphinxcontrib-qthelp      1.0.3                      py_0    conda-forge
sphinxcontrib-serializinghtml 1.1.4                      py_0    conda-forge
sqlite                    3.35.3               h8ffe710_0    conda-forge
stdlib-list               0.7.0                      py_2    conda-forge
tiledb                    2.2.7                hf84e3da_0    conda-forge
tk                        8.6.10               h8ffe710_1    conda-forge
toml                      0.10.2             pyhd8ed1ab_0    conda-forge
tqdm                      4.59.0             pyhd8ed1ab_0    conda-forge
urllib3                   1.26.4             pyhd8ed1ab_0    conda-forge
vc                        14.2                 hb210afc_4    conda-forge
vs2015_runtime            14.28.29325          h5e1d092_4    conda-forge
wheel                     0.36.2             pyhd3deb0d_0    conda-forge
win_inet_pton             1.1.0            py38haa244fe_2    conda-forge
wincertstore              0.2             py38haa244fe_1006    conda-forge
wrapt                     1.12.1           py38h294d835_3    conda-forge
xerces-c                  3.2.3                h0e60522_2    conda-forge
xz                        5.2.5                h62dcd97_1    conda-forge
yaml                      0.2.5                he774522_0    conda-forge
zlib                      1.2.11            h62dcd97_1010    conda-forge
zstd                      1.4.9                h6255e5f_0    conda-forge

grayskull --version 0.8.5

Additional context
Add any other context about the problem here.

Probably the same problem as in #209.
Grayskull needs a sdist file but only a wheel is available on PyPI: https://pypi.org/project/jsons/

ahh, yes, just saw that facepalm. Sorry!

No worries, I made the same mistake first.

authors: BastianZim ngodber

repo: conda-incubator/grayskull


text:
config: remove ssh-demo

Following from https://github.com/confidential-containers/operator/issues/370
I think we'll need to cleanup a few things in the docs as well (see https://github.com/confidential-containers/confidential-containers/pull/211)

Hi @ldoktor !

Yep, seems to cover all mentionings of ssh-demo here. Wainer, is your blog post updated, can we merge this?

On the blog post https://www.redhat.com/en/blog/how-use-confidential-containers-without-confidential-hardware luckily It points to a tagged file, so this removal is fine.

Hi @ldoktor !

Yep, seems to cover all mentionings of ssh-demo here. Wainer, is your blog post updated, can we merge this?

On the blog post https://www.redhat.com/en/blog/how-use-confidential-containers-without-confidential-hardware luckily It points to a tagged file, so this removal is fine.

Thanks for the confirmation. Shouldn't the https://github.com/confidential-containers/confidential-containers/tree/main/demos/ssh-demo be removed too? (which would require the blog to be updated as well...)

Shouldn't the https://github.com/confidential-containers/confidential-containers/tree/main/demos/ssh-demo be removed too?

No. See commit message.

source: gharchive/pull-request

authors: fitzthum ldoktor wainersm

repo: confidential-containers/operator

license_type: permissive

license_source: github-api


text:
Consistent log messages

Describe the purpose of your pull request
Revises log messages to make them consistent with other SDKs and also adds event ids for easier log event identification.
Note: The current logging abstraction (ILogger class) doesn't support structured logging, so it can't be done without introducing BCs. If we want to enable it, I suggest following the solution used in the .NET SDK.
Requirement checklist (only if applicable)

[ ] I have covered the applied changes with automated tests.
[ ] I have executed the full automated test set against my changes.
[ ] I have validated my changes against all supported platform versions.
[ ] I have read and accepted the contribution agreement.

If you don't mind, I remove this line from the code on this branch: //class ConfigCatLogger : public ILogger {

repo: configcat/cpp-sdk

license: MIT


text:
Add CLI command to set withdraw address

This would be handy. Current workflow is via web frontend only.
The validator-operator would have to run the command to authorize a new address to execute withdrawals.
This is implemented in the tg4-engagement  contract.
A workaround would be to execute the json message directly via CLI:
# UNTESTED example
msg='{"delegate_withdrawal":{"delegated":"<NEW_ADDRESS>}}'
contract_address=$(tgrade q poe contract-address ENGAGEMENT -o json | jq -r '.address')
tgrade tx wasm execute ${contract_address} ${msg}

The CLI command should be added to the poe module so that it is listed with tgrade tx poe -h

Moved to a post mainnet milestone as a workaround exists.

source: gharchive/issue

repo: confio/tgrade


text:
Inconsistent configuration properties names for aws credentials

TF provider uses inconsistent names for the AWS key/secret pairs.
For example
Kinesis source
aws.access.key.id
aws.secret.key.id

S3 source
aws.access.key.id
aws.secret.access.key

@Schekn thanks for reporting an issue!
Unfortunately it's not something that can be fixed in a client but I'll pass this to our backend team to update our Connect API.


text:
🛑 Miniflux is down

In ad45b26, Miniflux ($MINIFLUX) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Miniflux is back up in a8f3f54 after 13 minutes.

repo: congnews/upuptime


text:
Refresh landing page

Update landing page with more recent videos/images.
Thoughtline 2/17 (?)

Completed:

https://github.com/conix-center/ARENA-core/commit/c8369c74e6eaeb816ec1dd10f391cf977274fbf7
https://github.com/conix-center/ARENA-website/commit/ef4d2d39e019f14b63af00b258f1ca03bb03e24e

Wrong repo

repo: conix-center/arena-account


text:
Update translations

Closes #491

Coverage decreased (-0.2%) to 35.252% when pulling 225b71e69f49a2d5ca456c77ae6c32c41314350c on kruton:upd-long-it-strings into ddba58d36d62ae4ccc9cd17de326fd78909da04c on connectbot:master.

Coverage remained the same at 35.481% when pulling 225b71e69f49a2d5ca456c77ae6c32c41314350c on kruton:upd-long-it-strings into ddba58d36d62ae4ccc9cd17de326fd78909da04c on connectbot:master.

authors: coveralls kruton

repo: connectbot/connectbot

license_source: bigquery


text:
[ST] Large ezETH transfer from Ethereum mainnet stuck in slow path

Describe the bug
There're two transactions reported in the ticket that the transaction stuck longer than expected for slow path

(16.22 ezETH) https://connextscan.io/tx/0xce08c923ecb56287968d560d4dffaa867d4d5d9aa716a5d9b98534759f78c851
(205.81 ezETH) https://connextscan.io/tx/0x37abd0cc93f0d8a47082c6b5b3552b8b41560e5aa8d0f47953bb12b11bf1ec98

One tx took more than a day to complete
Where did the user initiate this transfer?
Connext UI
@oncall

Other transactions here:
https://connextscan.io/tx/0x5cc5a17d085b919d4659695370b5c4909981e60a7e3de00a8fcba91c83b954f4
https://connextscan.io/tx/0x113800963a7f162733a6f314193dfc0c8ede156432ae70757bba8ffa09d6d93b
https://connextscan.io/tx/0xd8ad5849556aeb198c6552451b6caf8ba2458b03f020c9e9895006b351dd0637
https://connextscan.io/tx/0x5841c3726f4c76535fe2ca04c0dd66c92d36108355d56e1f5ba7a468bada6918
https://connextscan.io/tx/0x8cbb9d0ec31385b449022a3939accef7cc08df262339be82d8bbae810da22a01
https://connextscan.io/tx/0xd336c209647672562fe8def636422c25f7ef732ca2a7afc043dd15510c454308

https://connextscan.io/tx/0xf7f807dc1f5a57073b3ac25f7338ca988f16493d2cfd7cf084df673a7345f0cc

repo: connext/monorepo


text:
Find variable min/max one slice at a time to reduce memory errors

This PR adjusts the describe logic when determining variable min/max values. Previously, the function would silently ignore memory errors, resulting in a describe that would succeed, but with no min/max values.
The new logic loads one slice at a time of the first dimension (usually time) when there are more than two dimensions. This logic is far from perfect, but should cover many cases until a better solution can be developed.
While it would be possible to make this change and keep the silent memory error handling, IMHO this makes problems more difficult to diagnose when client code is depending on min/max values. However, I'm open to other points of view on this.

I don't know what's up with Travis. It's having trouble building NetCDF apparently:
error: unknown file type '.pyx' (from 'netCDF4/_netCDF4.pyx')
The same error occurred on the other PR I just submitted, but after an unrelated change, got past that and failed only on the Python 2.7 build with TypeError: invalid dtype: dtype('float32'), which doesn't seem right.

Coverage increased (+0.01%) to 40.158% when pulling 5ceb121e2b7f336537493b64eb9dc9a0fbeb6048 on large-dataset-minmax into 138d7edc6c3eee3636658afe74ce38afe8eab75b on master.

The build on master now fails with the same error, without any code changes. So the CI failure here is not due to code changes.

authors: coveralls nikmolnar

repo: consbio/clover


text:
SEOS

SUPER EOS COMMUNITY
SEOS can be understood as a block chain operation system designed for commercial distributed applications. A new block chain architecture introduced by SEOS software is designed to achieve the performance extension of distributed applications. By creating a developer-friendly block chain underlying platform, similar to the block chain operating system, SEOS is powerful, can support multiple applications simultaneously, can support multiple programming languages at the same time, for the development of dApp developers to provide the underlying module, reduce the development threshold, like Microsoft Windows, while SE OS solves the problem of latency and data throughput through parallel chains and DPOS. SEOS is not as simple as bitcoin and Ethernet as digital currency. Yaniv Leven, founder of the SEOS technology team, and Bennett, former core member of the EOS BM technology team, jointly build the SEOS digital assets. The aim is to create a more perfect SEOS ecosystem, known as block chain 3.
Brief history of creator and partnership process
The team is joined by former AI equipment engineers from well-known AI companies: Google, Microsoft, IBM, etc., and operated by the famous block chain application operation team in Britain. The organizational structure of SEOS is from top to bottom as follows: the Executive Committee of SEOS makes important decisions and manages operations; the following is the establishment of technology research and development center, which is mainly responsible for technical matters; the global branch joint management center, which is mainly responsible for global branch matters; and the operation center, which is mainly responsible for the global operation of SEOS. The headquarters of the SEOS Foundation Federation establishes London, UK, and the North American Branch is located in the United States. The European Branch is located in London, UK; the Asian Branch is located in Tokyo, Japan; and the Oceania Branch is located in Sydney, Australia.
official website：http://www.3seos.org/
Whitepaper：http://www.3seos.org/seosen.pdf
Media reports:
http://markets.financialcontent.com/stocks/news/read/36870293/
http://finance.dailyherald.com/dailyherald/news/read/36870293/
http://thenumbers.marketplace.org/publicradio/news/read/36870293/
http://markets.post-gazette.com/postgazette/news/read/36870293/

你好，
请重新拉去提交
无此文件 erc20/0xF41861F194e7Ba8dE95144a89E0C6ed16EE0B3A0.json

Hello, you need to pull back and delete the useless files.

authors: SEOSclub wenyanwang

repo: consenlabs/token-profile


text:
Undt token

为确保 Token Profile 的顺利通过，务必逐一确保以下检查项并补充项目资料：
.json 及 .png 文件检查项

[ ] logo 尺寸：120*120 px
[ ] logo 背景：透明
[ ] 代币有至少一笔成功的转账记录
[ ] 此项对于 ERC-20 项目方：合约地址有大小写（做 checksum）
[ ] .json 和 .png 文件名一致（包括大小写）

项目资料：
官方公告：https://uniondao.com
转账所需 Gas Limit（对 ERC-20 项目方）：（默认为 60000）

Please check the following to ensure a successful verification of Token Profile
.json and .png document checklists

[ ] logo dimensions: 120*120 px
[ ] logo background: Transparent
[ ] At least one transaction on the token contract
[ ] For ERC-20 project teams: Upper and lower capitalized alphabets in token address (For checksum purposes)
[ ] Same document name for both .json and .png (Including capitalization)

Project background:
Official announcement:https://uniondao.com
Recommended Gas Limit (For ERC-20 project teams) for transaction: (Default is 60,000)

pr 中存在的问题已在标签中指出，请参考教程检查修改。
教程链接：
https://github.com/consenlabs/token-profile#token-profile-guideline
另外，解决以上问题后：
由于贵方是稳定币项目，请提供权威媒体报道

authors: tstt uniondao


text:
🛑 notgay.resterdigne.net is down

In 5809ab4, notgay.resterdigne.net (https://notgay.resterdigne.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: notgay.resterdigne.net is back up in 6457ce9.

repo: constructions-incongrues/status


text:
Виджет для RGB-диммера и для RGB-контрола в девайсах

subj. Добавил angular-minicolor, но сходу прикрутить не получилось

Resolved in d3802296507fe36cadf547e150bd3e58691edd38

repo: contactless/homeui

license: mit


text:
consider providing (templates for) best practice container spec?

In https://github.com/docker/swarmkit/pull/1965 I ended up copying chunks of github.com/docker/docker/oci/DefaultSpec into [my containerd executor for swarmkit(https://github.com/ijc25/swarmkit/blob/4e1ce17f7f27e246298e9f78b61d6eb6fdb7d218/agent/exec/containerd/adapter.go#L345..L410), which makes me a touch uncomfortable.
I wonder if perhaps there is scope for pulling out the common (i.e. obvious/non-opinionated) bits out of that code into some central location, such as a containerd package, where it can be used as a base?
Or perhaps this is more of a https://github.com/opencontainers/runc thing? Although I expect the further down the stack we go the less common ground there will be.
/cc @stevvooe

I think it is something that we can pull out into our client libs that will give a good default spec.  Docker has good defaults that have worked for the majority of use cases and is secure so we should use that as our base.  It should not go to OCI.

I think this is covered more than adequately by spec_unix.go:createDefaultSpec() now. I'll close.

repo: containerd/containerd


text:
pod healthchecks fail when host IPv6 is disabled

Description
Our kubernetes hosts have IPv6 disabled via the following sysctl settings:
net.ipv6.conf.all.disable_ipv6 =  1
net.ipv6.conf.default.disable_ipv6 = 1

When containerd starts the pod, it does so without honouring those sysctl values, and IPv6 is therefore enabled in the pod.
kubelet creates an /etc/hosts file in the pod with the following lines (amongst others):
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback

Given the app reasonably expects IPv6 to be disabled on the pod (it was disabled when running under docker after all), it only tries to bind to the IPv4 interface.
The pod's healthcheck, trying to reach http://localhost:8080, then fails because:

IPv6 being enabled in the pod causes localhost to resolve to ::1
The app isn't bound to ::1
Healthcheck fails with a connection refused error.

Steps to reproduce the issue

Describe the results you received and expected
Results received:

DNS resolves localhost to ::1
Pod healthchecks fail with a connection refused error

Results expected:

DNS resolves localhost to 127.0.0.1
Pod healthchecks pass

What version of containerd are you using?
1.6.12
Any other relevant information
$ runc --version
runc version 1.1.4-0ubuntu1~22.04.3
spec: 1.0.2-dev
go: go1.18.1
libseccomp: 2.5.3

$ nerdctl info
Client:
 Namespace:	k8s.io
 Debug Mode:	false

Server:
 Server Version: 1.6.12-0ubuntu1~22.04.3
 Storage Driver: overlayfs
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Log: fluentd journald json-file syslog
  Storage: native overlayfs
 Security Options:
  apparmor
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.19.0-1028-aws
 Operating System: Ubuntu 22.04.2 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 30.83GiB

$ uname -a
Linux ip-xx-xx-xx-xx 5.19.0-1028-aws #29~22.04.1-Ubuntu SMP Tue Jun 20 19:12:11 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Show configuration if it is related to CRI plugin.
No response

I was able to workaround this problem by overriding our CNI's config so that it forces IPv6 to be disabled in pods. Details at https://github.com/aws/amazon-vpc-cni-k8s/issues/2483#issuecomment-1674634880. But ideally there should be a way to avoid this mismatch in configuration between DNS resolution and network interface binding.

I could be mistaken here, but this does not seem like a containerd issue.
containerd is not touching networking, the CNI provider is.

@cpuguy83 as I understand it, containerd creates the container network namespace and passes it as an argument to the CNI. The CNI could choose to disable IPv6 in the container network namespace, but it does not currently do that, and I think containerd should be inheriting the host-level settings

The VPC CNI does enable IPv6 on the container's loopback interface when this is an IPv6 pod: https://github.com/aws/amazon-vpc-cni-k8s/blob/master/cmd/routed-eni-cni-plugin/driver/driver.go#L148 , so a case could be made for VPC CNI to disable IPv6 in the netns when it does not need to be enabled, but it would be interesting to know why containerd does not inherit the host-level settings

Ah, that's an interesting line! We don't explicitly disable IPv6 on the lo interface using the net/ipv6/conf/lo/disable_ipv6 setting but instead expect it to be disabled because net/ipv6/conf/all/disable_ipv6 is set. I'll try setting that sysctl parameter when I'm back at work on Monday and see if that helps at all. That said, it's still interesting to me that it worked with the existing settings under docker.

啊，这是一句有趣的台词！我们不会使用该设置在接口上显式禁用 IPv6，而是希望它被禁用，因为已设置。当我周一回到工作岗位时，我会尝试设置该 sysctl 参数，看看是否有帮助。也就是说，它与 docker 下的现有设置一起工作对我来说仍然很有趣。lo``net/ipv6/conf/lo/disable_ipv6``net/ipv6/conf/all/disable_ipv6

Are we encountering the same problem?
root@k8s-master01:~# sysctl -a  | grep net.ipv6.conf.*.disable_ipv6
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.eth0.disable_ipv6 = 0
net.ipv6.conf.lo.disable_ipv6 = 1

@henry118 I modified /etc/hosts on the host OS to remove IPv6 entries, in addition to setting networking sysctls on host OS to disable IPv6, but I still see an IPv6 address assigned to the loopback interface in container network namespaces

I believe the IPv6 address is only configured on the loopback interface at https://github.com/containernetworking/plugins/blob/main/plugins/main/loopback/loopback.go#L66 because containerd does not inherit the networking sysctls from the host. As for whether localhost still resolves to an IPv6 address after removing the IPv6 entry in /etc/hosts, I have not tried that, but can try today

because containerd does not inherit the networking sysctls from the host

containerd is no different than any other system service, though that depends on how you installed it.

Ah that is very helpful, thanks @henry118! Yeah, it looks like the loopback interface is created by upstream containernetworking

Linking to my AWS VPC CNI comment on solving this by making bootloader changes: https://github.com/aws/amazon-vpc-cni-k8s/issues/2483#issuecomment-1693515358

I'm happy for this to be closed off given that the bootloader-based behaviour is understood and that there's going to be an easy to apply workaround for the amazon-vpc-cni side. Thanks @henry118.

I think we can close this, thanks @henry118 @mattburgess ! Hopefully someone debugging in the future stumbles onto this during their search.


text:
Bump runc to 74a17296470088de3805e138d3d87c62e613d

This bumps the runc version to 74a17296470088de3805e138d3d87c62e613dfc4
that includes various fixes.
Signed-off-by: Michael Crosby crosbymichael@gmail.com

Codecov Report

Merging #1665 into master will increase coverage by 0.19%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1665      +/-   ##
==========================================
+ Coverage   48.75%   48.94%   +0.19%
==========================================
  Files          27       27
  Lines        4080     4080
==========================================
+ Hits         1989     1997       +8
+ Misses       1672     1668       -4
+ Partials      419      415       -4

Impacted Files
Coverage Δ

metadata/snapshot.go
50.28% <0%> (+0.93%)
:arrow_up:

metadata/db.go
67% <0%> (+1.5%)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-io crosbymichael


text:
nerdctl compose up stuck on creating container

Description
I'm trying to create an environment to use fluentbit and forawrd logs to an HTTP and a TCP service.
I have been able to do this in Docker but it seems that there is a bug in containerd so I need to test it.
I have installed Rancher Desktop on windows and I'm using nerdctl CLI to create everything from a docker-compose.yml file (The same used with docker).
Unfortunately the process is getting stuck on the following step:
avillegas@ITMES5CD41761PF:~/fluentbit-local$ nerdctl --insecure-registry compose --debug -f docker-compose.yml up
<3>WSL (2574) ERROR: CreateProcessParseCommon:711: Failed to translate \\wsl.localhost\Ubuntu\home\avillegas\fluentbit-local
INFO[0000] Creating network nerdctl-tmp1559687876_default
WARN[0000] Ignoring: service fluentbit: depends_on: http-service: [Required]
WARN[0000] Ignoring: service fluentbit: depends_on: tcp-service: [Required]
INFO[0000] Ensuring image fluentbit-local-http-service:latest
DEBU[0000] verifying process skipped
INFO[0000] Ensuring image fluentbit-local-tcp-service:latest
DEBU[0000] verifying process skipped
INFO[0000] Ensuring image fluent/fluent-bit:3.1.6-amd64
DEBU[0000] verifying process skipped
DEBU[0000] filters: [labels."com.docker.compose.project"==nerdctl-tmp1559687876,labels."com.docker.compose.service"==http-service]
INFO[0000] Creating container express-logger
DEBU[0000] verifying process skipped
DEBU[0000] generated log driver: binary:///usr/local/libexec/nerdctl/nerdctl?_NERDCTL_INTERNAL_LOGGING=%2Fvar%2Flib%2Fnerdctl%2Fdbb19c5e
DEBU[0000] remote introspection plugin filters           filters="[type==io.containerd.snapshotter.v1, id==overlayfs]"

The first time I ran the compose up I was able to create all the containers but I had a problem with the etc volume for fluentbit. After fixing the  mapping issue (changing relative path to absolute) the containers never started again. They even got stuck till the point I had to kill Rancher Desktop to destroy them.
Here is the compose yaml:
services:
  http-service:
    image: fluentbit-local-http-service:latest
    #build: ./express
    container_name: express-logger
    ports:
      - "9999:9999"
    environment:
      PORT: 9999

  tcp-service:
    image: fluentbit-local-tcp-service:latest
    #build: ./tcp
    container_name: tcp-logger
    ports:
      - "7777:7777"
    environment:
      PORT: 7777

  fluentbit:<!-- Failed to upload "http-service.zip" -->

    image: fluent/fluent-bit:3.1.6-amd64
    container_name: fluentbit-local
    ports:
      - "2020:2020"
    depends_on:
      - http-service
      - tcp-service
    volumes:
      - /home/avillegas/fluentbit-local/etc:/fluent-bit/etc
      - /mnt/c/AnypointStudio/plugins/org.mule.tooling.server.4.7.ee_7.18.0.202405262218/mule/logs:/home/nonroot

Both images

fluentbit-local-tcp-service:latest
fluentbit-local-http-service:latest
Have been exported from docker using docker save -o local-image.tar image:tag and imported to containerd using nerdctl load < local-images.tar. So bith the images are local.

Everything is being run from WSL (Ubuntu) on a Windows 11 machine.
Steps to reproduce the issue

Import and pull the images
Change the volume paths to something on your local machine
run the nerdctl compose up command with the yaml provided

Describe the results you received and expected
The expected result is that the 3 containers will start and I will be able to use the fluent bit container to forward the logs from a tailed file to the HTTP and TCP services on the other containers
What version of nerdctl are you using?
Client:
Version:       v1.7.7
OS/Arch:       linux/amd64
Git commit:    5882c720f4e7f358fb26b759e514b3ae9dd8ea83
buildctl:
Version:      v0.16.0
GitCommit:    0865fcc9b78559e856e81dc52b3613701e7be28d
Server:
containerd:
Version:      v1.7.22
GitCommit:    7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c
runc:
Version:      1.1.15
GitCommit:    v1.1.15-0-gbc20cb44
Are you using a variant of nerdctl? (e.g., Rancher Desktop)
None
Host information
Client:
Namespace:     default
Debug Mode:    false
Server:
Server Version: v1.7.22
Storage Driver: overlayfs
Logging Driver: json-file
Cgroup Driver: none
Cgroup Version: 1
Plugins:
Log: fluentd journald json-file syslog
Storage: native overlayfs
Security Options:
seccomp
Profile: builtin
rootless
Kernel Version: 5.15.146.1-microsoft-standard-WSL2
Operating System: Ubuntu 22.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 7.419GiB
Name: ITMES5CD41761PF
ID: c2a10d8e-6202-4740-a0fa-630d4e37d29f
WARNING: Running in rootless-mode without cgroups. To enable cgroups in rootless-mode, you need to boot the system in cgroup v2 mode.
WARNING: IPv4 forwarding is disabled

Here is a google drive link with the docker images for the HTTP and TCP services
https://drive.google.com/file/d/1sXPMWH2zOhc4cbfnVlG-_QEB-gNhiloI/view?usp=sharing

repo: containerd/nerdctl


text:
Mark cri log viewer as experimental

Follow-up to

#1847

Due to

https://github.com/containerd/nerdctl/issues/1956
https://github.com/containerd/nerdctl/issues/1957

cc @zhaojizhuang

@containerd/nerdctl-maintainers Let me release v1.2.0 after merging this one


text:
nameservers in container's /etc/resolv.conf should be reachable

When launching podman run without --dns option, host's /etc/resolv.conf is used for the container.
This is a problem when host's /etc/resolv.conf only contains nameservers not reachable from the container, e.g. 127.0.0.1.
Docker ignores  127.0.0.1 in host's /etc/resolv.conf. When there’s no other nameserver, it adds 8.8.8.8 and 8.8.4.4.
Is this a BUG REPORT or FEATURE REQUEST?:
kind bug

Looks like docker's resolvconf package is doing all the job of filtering host's resolv.conf.
Do you think that this could be imported in libpod ?

@mheon thanks

Using the command line switch for --dns is not desirable ?

@baude that's a possibility, but probably a user expects a docker-like user experience when using podman.
Also passing --dns is not always an option (e.g. podman used in a script).

Going to take a look at this one today

Opened #1537 to fix

authors: baude marcov mheon

repo: containers/libpod


text:
Feature - Podman pull status even when under Kubernetes

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:
/kind bug

/kind feature
Description
Image pull status. Right now, unless you run the image pull interactively, you can't watch the status. This is sub-optimal when you are running under Kubernetes. For example, there is no way to see how far along the image is. When you are pulling a huge image in Kube/OCP, you just sit there and wait. It gives that sense of no control that users hate. It would be awesome to be able to asynchronously find the status of a pull out.
This is the same problem docker has.
Basically, have an option in podman to see the status of containers/storage so that you can see what's going on with CRI-O. That would be super cool.

Steps to reproduce the issue:

Submit a job to kubernetes

Wait :-)

No status on image pull other than, there is an image pull happening.

Describe the results you received:
Describe the results you expected:
Would be cool to have an images --status or some such to watch the status interactively while the images are being pulled.
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.):

The image library, github.com/containers/image, does support writing status back to us, but I suspect that won't make it across processes. We probably need to land support of support upstream to store pull state somewhere (on disk?) where we can get at it and display it

@mtrmac WDYT?

Yeah, containers/image/copy.Options.Progress exists; it might need significant extensions to be really nice, it’s just a stream of (blob ID, offset) updates with no “total number of blobs“, “blob done” or “total expected size” information), but that’s mostly local and trivial work. So, having podman show this (if it does not show the default reporting, which is text-only but more informative) is simple enough.
The higher level, either making the status of CRI-O visible through completely unrelated local podman processes, or through the CRI-O API itself and Kubernetes pod/node(?) status [which one is this issue really about?], would be most of the work.

@haircommander @umohnani8 PTAL
Could you potentially work on this together.

Have there been attempts to extend the CRI with user-friendly pull progress? Doing the dance with Podman seems a bit too complex to me.

(going through issues at the moment)
@fatherlinux @rhatdan, I think this issue needs some more discussion and input from the CRI-O folks (Cc: @mrunalp @runcom). There are many possibilities to implement this (e.g., CRI-O could log, write to a dedicated file, expose a dedicated grpc API, CRI extension) but CRI-O needs to provide something before we can start for Podman. Maybe that's something for porting CRI-O's image handling over to libpod (Cc: @baude).

Ping @runcom, @mrunalp. WDYT?

This issue seems to have gone dead.  Should this issue be moved to CRI-O?

closing as nothing appears to impact podman, re-open on a different component if needed

authors: baude fatherlinux mheon mtrmac rhatdan vrothberg


text:
podman logs -f continues indefinitely on a stopped container

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Running podman logs -f on a stopped container run indefinitely and does not exit
This is a regression of Issue https://github.com/containers/libpod/issues/435 and PR https://github.com/containers/libpod/pull/437

Steps to reproduce the issue:

Run a container which exits immediately

podman run -d --name hello-world hello-world

Follow logs of stopped container

podman logs -f hello-world

Describe the results you received:
Command does not exit; hangs indefinitely
Describe the results you expected:
Command should exit.
Additional information you deem important (e.g. issue happens only occasionally):
The expected behavior of Docker is to exit when following a log of a stopped container
Output of podman version:
Version:      2.0.0-dev
API Version:  1
Go Version:   go1.14.3
Git Commit:   d857275901e8c1ea7515360631e5894018e17f30
Built:        Fri Jun  5 17:00:00 2020
OS/Arch:      linux/amd64

Output of podman info --debug:
host:
  arch: amd64
  buildahVersion: 1.15.0-dev
  cgroupVersion: v2
  conmon:
    package: conmon-2.0.18-0.6.dev.git50aeae4.fc33.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.18-dev, commit: 51e91bbc42aaf0676bb4023fb86f00460bf7a0a2'
  cpus: 4
  distribution:
    distribution: fedora
    version: "33"
  eventLogger: file
  hostname: gallucci-fedora.devlnk.net
  idMappings:
    gidmap: null
    uidmap: null
  kernel: 5.7.0-1.fc33.x86_64
  linkmode: dynamic
  memFree: 15239475200
  memTotal: 16783962112
  ociRuntime:
    name: crun
    package: crun-0.13-2.fc33.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 0.13
      commit: e79e4de4ac16da0ce48777afb72c6241de870525
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
  os: linux
  remoteSocket:
    exists: true
    path: /run/podman/podman.sock
  rootless: false
  slirp4netns:
    executable: ""
    package: ""
    version: ""
  swapFree: 4294963200
  swapTotal: 4294963200
  uptime: 22h 20m 14.55s (Approximately 0.92 days)
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - docker.io
store:
  configFile: /etc/containers/storage.conf
  containerStore:
    number: 6
    paused: 0
    running: 4
    stopped: 2
  graphDriverName: overlay
  graphOptions:
    overlay.mountopt: nodev,metacopy=on
  graphRoot: /var/lib/containers/storage
  graphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "true"
  imageStore:
    number: 3
  runRoot: /var/run/containers/storage
  volumePath: /var/lib/containers/storage/volumes
version:
  APIVersion: 1
  Built: 1591401600
  BuiltTime: Fri Jun  5 17:00:00 2020
  GitCommit: d857275901e8c1ea7515360631e5894018e17f30
  GoVersion: go1.14.3
  OsArch: linux/amd64
  Version: 2.0.0-dev

Package info (e.g. output of rpm -q podman or apt list podman):
podman-2.0.0-0.121.dev.git1fcb678.fc33.x86_64

Additional environment details (AWS, VirtualBox, physical, etc.):
Fedora 33 (Rawhide Prerelease)

Did some extended testing and confirm the issue exists in older versions of podman in addition to the one reported:

podman 1.6.4 - Hangs
podman 1.9.3 - Hangs

Just for grins, what does Docker do?

Docker exits properly. Podman used to have this same functionality and was
fixed in a bug 2 years ago, but the log.go code was completely rewritten so
it is a regression.
On Tue, Jun 9, 2020, 07:38 Daniel J Walsh notifications@github.com wrote:

Just for grins, what does Docker do?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/containers/libpod/issues/6531#issuecomment-641340411,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACEZ4EKCDZ7PCOYAQV76BITRVZCPDANCNFSM4NY2D6FA
.

Great thanks.

@jgallucci32 Interested on working on a fix and opening a PR?

/reopen
This issue was originally fixed in #6591 but has been reverted in #6644 to address problems with tests failing.


text:
Vendor Buildah v1.7

Signed-off-by: TomSweeneyRedHat tsweeney@redhat.com
Vendors in Buildah 1.7 into Podman.

LGTM once CI goes green

@TomSweeneyRedHat Build failures.

Rats, forgot I need imagebuilder too.  Vendoring.

LGTM

/lgtm

@TomSweeneyRedHat Can you rebase? I think CI is fixed upstream.
(We might still have registry issues, but nothing we can do about those)

@mheon, will do.  And Eack, thought this had already made it through.  Thanks for the heads up.

/lgtm

authors: TomSweeneyRedHat mheon rhatdan


text:
disable generation of cni firewall plugin

it turns out that when the firewall plugin is not provided as part of the configuration, then the firewall cni plugin will dynamically figure out if it should use firewalld or iptables.
also removing this from the default configuration file
Signed-off-by: Brent Baude bbaude@redhat.com

LGTM

/lgtm
/hold

/hold cancel

authors: baude mheon rhatdan


text:
[bug] On windows 10 a reboot is need after install wsl

We are seeing failures when trying to podman machine init on windows 10 when no reboot has been executed after install wsl until we get https://github.com/adrianriobo/qenvs/issues/71 fixed the best option is to include a step on our windows flows to handle wsl2 installation + reboot + ensure machine is running again
This requires #30 to avoid installing it within pd-e2e

Closed as https://github.com/adrianriobo/qenvs/pull/149 has been merged as so https://github.com/adrianriobo/qenvs/issues/71 has been fixed


text:
Add breadcrumbs for consistent navigation patterns

In Podman Desktop, when you have a list and get into the details of one of its item, you get a breadcrumb that facilitates the navigation.

We are missing it for Recipes:

We are missing it for Models:

We are missing it for Services too.

@feloy can we close this given #697 merged?

fixed by #697

authors: feloy slemeur vrothberg


text:
ProxyProtocol not working, DigitalOcean LB unhealthy

Do you want to request a feature or report a bug?
Bug
Did you try using a 1.7.x configuration for the version 2.0?

[ ] Yes
[x] No

What did you do?
Put Traefik on DigitalOcean Droplet behind DigitalOcean LoadBalancer. Enable ProxyProtocol on the Loadbalancer and set flag on Traefik Container --entryPoints.web.proxyProtocol.insecure=true

What did you expect to see?
Healthy Loadbalancer and Client IP Addresses in Logs
What did you see instead?
Unhealthy Loadbalancer, and just IP Address of Server
Output of traefik version: (What version of Traefik are you using?)

{"Version":"2.0.0","Codename":"montdor"}

What is your environment & configuration (arguments, toml, provider, platform, ...)?
Docker Provider

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
(paste your output here)

Hey folks,
i had more detailed talk with the DO Support team. It looks, that this issue is not on their site.
I also had NGINX installed on the same Droplet, and it does work with the ProxyProtocol. Just the Traefik v2 ProxyProtocol, seems to have an issue.
Could anyone test and confirm this?
Thanks all in advance.

I also have Traefik running on DO, with an auto-provisioned LB feeding into a managed k8s cluster.  Both insecure and trustedIPs modes for proxyProtocol work fine for me, and the load balancer is able to report healthy values for the nodes in the cluster.  It could be that your healthcheck entryPoint / path is somehow misconfigured with Traefik?

I have some news on this.
With the official release it seems to be different behavior.
When activating ProxyProtocol on DO LB, the health status drops to unhealthy. After around 2hrs it catches up and gets back to healthy.
This repeats on every change. So always 2hrs wait time. Health check is correct on Traefik Version Api Route
I will keep an eye, and report any update

I came across this issue myself, my nodes would start failing health checks as soon as I enabled the protocol on the LB. Turns out the problem is that if you enable proxy protocol on the LB, your Traefik ping endpoint needs to also have proxy protocol enabled, since I guess the LB applies proxy to its health check calls.
Either expose ping on the web entrypoint, which should already have these settings, or create a dedicated entrypoint for it (which is what I did) ...
--ping.entrypoint=ping
--entrypoints.ping.address=:8082
--entrypoints.ping.proxyprotocol
--entrypoints.ping.proxyprotocol.trustedIPs=<CIDR>

I have the same issue, but it seems to be not related to ProxyProtocol at all. ProxyProtocol works just fine.
The issue is that DO healthcheck type http is always failing. Regardless where you point it. Neither :80/ work, nor :8080/ping work, while both being health (I checked it by exposing nodes to internet and checking same host:ports as DO loadbalancer connect to, also when checking :80/ I see connections of LB in traefik logs). Seems DO cannot succeed on HTTP healtheck to traefik.
If you change healtcheck type to TCP, so it just open and close the port - it becomes healthy immideately. Well the logs is going to be poisoned with traefik panicking about connections being opened and closed with no data.

That's interesting, I have my DO LB healthcheck type set as HTTP and its working just fine (once I configured my traefik ping entrypoint to accept proxy protocol). Are you running traefik as k8s ingress controller?

I run it on two dedicated nodes and have their host ports directly exposed and targeted by DO LB. pretty much almost "ingress" just a little bit closer to the network and pinned to nodes with fat CPU to run on. Without k8s Service that searches for where the pods run.
PS. Seems to be you are right, when ProxyProtocol is enabled on DO LB, it does healthcheck with proxy protocol as well, so "traefik" entrypoint need to be configured explicitly to accept proxy protocol and then it works. I did that and it seems to be running fine for few minutes already.

Hey folks,
thanks for your activity on this.
We also have managed to run healthy checks on DO LB.
However our learnings for our production grade setup are the following:

DO LB with Traefik, without ProxyProtocol and health check to :8080 -> live health
DO LB with Traefik, TCP health check -> live health
Traefik ProxyProtocol works correct and fine -> tested with different LB (custom and service)
DO LB ProxyProtocol works correct and fine -> tested with HAProxy and Nginx
DO LB with Traefik, with ProxyProtocol -> it works, but it seems that DO LB needs for us around 2h to get back on track, in the meantime it gets unhealthy peaks (with :80, or :8080 both set to correct settings)

Always to note, we use wildcard's and not dedicated CIDR for our Traefik Settings.
So for us it seems that DO LB and Traefik are a though combination. It works, but if we look at each separate it does work so much smoother.
I don't know if Traefik can do anything about it.
Thanks and keep coding
Alex

We have implemented different solution. So I am going to close

authors: Archanian Owersun alexanderniebuhr zerosym

repo: containous/traefik


text:
Using IPWhiteList with Docker Swarm

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

Bug

What did you do?

I have installed Docker Swarm with two nodes:
Traefik was deployed on master node with such compose file:
services:
  traefik2:
    image: traefik:v2.0
    logging:
      driver: "json-file"
    command: --log.level=DEBUG --api=true --api.insecure=true --entrypoints.web.address=:80 --entryPoints.websecure.address=:443 --providers.docker.endpoint="tcp://10.55.0.31:2375" --providers.docker.swarmMode=true --providers.docker.exposedByDefault=true  --providers.docker=true --providers.docker.network=traefik-proxy --providers.docker.watch=true
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /swarm/volumes:/sw
    deploy:
      mode: replicated
      replicas: 1
      placement:
        constraints:
          - node.role == manager
      restart_policy:
        condition: on-failure
    ports:
      - 80:80
      - 443:443
      - 8080:8080
    networks:
     - traefik-proxy
networks:
  traefik-proxy:
    driver: overlay

Next I deployed sample nginx stack and test white-list functionality:
services:
  mysite:
    image: testswcrlsn.azurecr.io/nginx:latest
    networks:
      - traefik2_traefik-proxy
    deploy:
      mode: replicated
      replicas: 1
      restart_policy:
        condition: on-failure
        delay: 30s
        max_attempts: 3
      placement:
        constraints:
          - node.role == worker
      resources:
        limits:
          cpus: '0.3'
          memory: 256M
      labels:
        - traefik.enable=true
        - traefik.http.routers.mysite-http.entrypoints=web
        - traefik.http.services.mysite.loadbalancer.server.port=80
        - traefik.http.routers.mysite-http.rule=Host(`tili.mylh.ru`)
        - traefik.http.routers.mysite-http.middlewares=test-ipwhitelist
        - traefik.http.middlewares.test-ipwhitelist.ipwhitelist.sourcerange=x.y.w.z
networks:
  traefik2_traefik-proxy:
    external: true

In the sourcerange I specified my IP x.y.w.z.
What did you expect to see?
I have expected that traefik gives access to the nginx site for my ip x.y.w.z
What did you see instead?
I have got an error 403.
Output of traefik version: (What version of Traefik are you using?)

root@testswm:~# docker run e2350c987724 version
Version:      2.0.2
Codename:     montdor
Go version:   go1.13.1
Built:        2019-10-09T19:26:05Z
OS/Arch:      linux/amd64
root@testswm:~#

What is your environment & configuration (arguments, toml, provider, platform, ...)?
# (paste your configuration here)

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
traefik2_traefik2.1.zre22fzy51db@testswm    | time="2019-10-23T11:04:27Z" level=debug msg="rejecting request &{Method:GET URL:/ Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Accept:[text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3] Accept-Encoding:[gzip, deflate] Accept-Language:[en,en-US;q=0.9,ru;q=0.8] Cache-Control:[no-cache] Connection:[keep-alive] Pragma:[no-cache] Upgrade-Insecure-Requests:[1] User-Agent:[Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36] X-Forwarded-Host:[tili.mylh.ru] X-Forwarded-Port:[80] X-Forwarded-Proto:[http] X-Forwarded-Server:[d8f518b2b71c] X-Real-Ip:[10.255.0.3]] Body:{} GetBody:<nil> ContentLength:0 TransferEncoding:[] Close:false Host:tili.mylh.ru Form:map[] PostForm:map[] MultipartForm:<nil> Trailer:map[] RemoteAddr:10.255.0.3:34286 RequestURI:/ TLS:<nil> Cancel:<nil> Response:<nil> ctx:0xc0006cc660}: \"10.255.0.3\" matched none of the trusted IPs" middlewareName=test-ipwhitelist@docker middlewareType=IPWhiteLister
traefik2_traefik2.1.zre22fzy51db@testswm    | time="2019-10-23T11:04:28Z" level=debug msg="rejecting request &{Method:GET URL:/favicon.ico Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Accept:[image/webp,image/apng,image/*,*/*;q=0.8] Accept-Encoding:[gzip, deflate] Accept-Language:[en,en-US;q=0.9,ru;q=0.8] Cache-Control:[no-cache] Connection:[keep-alive] Pragma:[no-cache] Referer:[http://tili.mylh.ru/] User-Agent:[Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36] X-Forwarded-Host:[tili.mylh.ru] X-Forwarded-Port:[80] X-Forwarded-Proto:[http] X-Forwarded-Server:[d8f518b2b71c] X-Real-Ip:[10.255.0.3]] Body:{} GetBody:<nil> ContentLength:0 TransferEncoding:[] Close:false Host:tili.mylh.ru Form:map[] PostForm:map[] MultipartForm:<nil> Trailer:map[] RemoteAddr:10.255.0.3:34286 RequestURI:/favicon.ico TLS:<nil> Cancel:<nil> Response:<nil> ctx:0xc000621a10}: \"10.255.0.3\" matched none of the trusted IPs" middlewareName=test-ipwhitelist@docker middlewareType=IPWhiteLister

I see that traefik banned my http request because it has source address 10.255.0.3. It is some of the IP-addresses of Ingress network of Docker Swarm
In the documentation I did not see any additional steps for configuration IPWhiteList for Docker Swarm.
Please could You give any advice for correct working IPWhiteList with Docker Swarm
Thank Yu

Hi @beelesnik , you might be interested to read the following blog post: https://alex.thom.ae/2019/10/20/protect-website-oauth2_proxy-traefik, with a particular focus on the "Network" section (https://alex.thom.ae/2019/10/20/protect-website-oauth2_proxy-traefik/#networks).
This is related to Docker Swarm default network: as you published the ports of Traefik's container into Swarm's network mesh, then a network "hop" is added to be able to forward packets from one node to the other.
In order to keep the original source IPs, you must publish Traefik's ports directly on Swarm nodes with the mode=host on the ports: directive.
Please look at the official Docker documentation on this topic:
https://docs.docker.com/engine/swarm/services/#publish-a-services-ports-directly-on-the-swarm-node

Hi! I'm Træfiker :robot: the bot in charge of tidying up the issues.
I have to close this one because of its lack of activity :disappointed:
Feel free to re-open it or join our Community Forum.

authors: beelesnik dduportal traefiker


text:
docker.defaultRoute creates both HTTP and HTTPS entrypoints despite no valid HTTPS certificate

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

Bug (but could also be considered a feature request)

What did you do?
Traefik automatically creates routes for docker containers when no routing rule is applied. These routes are then applied to both :80 and :443 entrypoints despite the fact that the route has no valid TLS certificate.

What did you expect to see?
For a default rule the :443 entrypoint should only be created automatically if there is a valid TLS certificate.
There are a few different ways to solve this:

Let the user specify a default cert resolver in traefik.yml/traefik.toml that is applied to all default routes.:

providers:
  docker:
    defaultCertResolver: le

Give the user control over which entrypoints are used for the default routes:

providers:
  docker:
    defaultEntryPoints: web,websecure
... or ...
    defaultEntryPoints: web

What did you see instead?
The :443 route is created by default with an invalid certificate.
Output of traefik version: (What version of Traefik are you using?)
docker-compose.yml:
image: traefik:v2.0

Version:      2.0.7
Codename:     montdor
Go version:   go1.13.5
Built:        2019-12-09T17:51:21Z
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml, provider, platform, ...)?
n/a

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
n/a

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
We dedicate the issue tracker to bug reports and feature requests only. My advanced AI has spotted that your issue might be a configuration problem or relates to something that doesn't look like a bug.
To confirm this, please join our Community Forum and reach out to us on the Traefik section.
In case I'm wrong (well, that would be embarrassing :sweat_smile:), my developers will re-open the issue and fix me!
In the meantime, you can double check Traefik's documentation.

authors: StudioLE traefiker


text:
SSL certs not reloaded from consul kv

Hi,
We see that traefik doesn't watch consul kv/see changes when we modify ssl certs
we run consul catalog as well as consul backend in one config

@seeder Can you give us more details on your config? version? Configuration? Way to reproduce the issue?

Closed due to inactivity.

authors: emilevauge ldez seeder


text:
Update  for Documentation dead links and lower casing the certificate domain name

What does this PR do?
Update for lower casing the certificate domain name in case the same is not set to lower case.
Example Scenario:
certificate generated for LocalNet.com
domain to be checked LocalNet.com
while checking the domain to be checked is lower cased, but the certificate domain name is not set to lower case.
updated the code for the same
Motivation
More

[ ] Added/updated tests
[ ] Added/updated documentation

Additional Notes

Its' already fixed in v1.7.
As we said in the latests release note , we're re-thinking some core aspects of Traefik. As a consequence, the code base has drastically changed in master (you can see for yourself the #4168 PR ... quite a refactoring).
For now I recommend to not use master.

Closed by #4206

authors: ldez mmatur vineetvermait


text:
Update ContextIO.js

check if prop is own property to avoid errors when objects/functions are extended.

:+1:

authors: abstractmatter sushithegreat

repo: contextio/ContextIO-node


text:
Build fixes: Remove duplicated code, re-add overwritten commit

Description
Two issues from the refactor-core merge:

duplicated code
looks like you manually moved one of my changes from preview to refactor-core, but accidentally used the wrong var

Closes #1361

Didn't see this and just opened #1361 - mind adding a closes #1361 to the description?

Good catches, thank you!

authors: Patrick-Erichsen justinmilner1 sestinj

repo: continuedev/continue


text:
Update MULTINODE.md

added comment addressing the time skew issue

Coverage decreased (-0.1%) to 39.489% when pulling 92aa68a5228a9c777847be83862516c36d0bf645 on gilesheron-patch-2 into aa5ad10d5d29c368e10735fd7ccd394b8c4bb450 on master.

authors: coveralls gilesheron

repo: contiv/vpp


text:
🛑 MPS - TESTPROCESS is down

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

HTTP code: 0
Response time: 0 ms

Resolved: MPS - TESTPROCESS is back up in 2ac53b4 after 13 minutes.

repo: conuti-das/status-lfrcs


text:
🛑 MPS - SAP D1V KONNEKTOR TEST is down

In e5ab83f, MPS - SAP D1V KONNEKTOR TEST ($KONNEKTOR_URL) was down:

HTTP code: 504
Response time: 10092 ms

Resolved: MPS - SAP D1V KONNEKTOR TEST is back up in 01975ce after 6 minutes.


text:
Generate changelog for last x feature releases

convco changelog has the parameter --max-versions.
When using semantic versioning, version numbers are split into major, minor and patch versions for breaking releases, feature releases, and pure bugfix releases.
When releasing 2 feature releases and then 5 bug fix releases, --max-versions 5 would only list the bugfix releases.
Depending on release workflows, parallel supported versions, and actual releases, it can make sense and be preferable to include the last x major or minor releases, and all related bugfix releases.
Personally, I would like to generate a changelog for 3 minor releases, while including any bugfix releases that happened in between/after them.
Is this something you would be willing to add?
Although it adds interpretation of version numbers, semantic versioning is quite popular, and possibly not listing the last feature release when using --max-versions seems like a significant issue to me - a hole in/for such a use case.

I see --prefix already does semantic interpretation.
    -p, --prefix <PREFIX>
            Prefix used in front of the semantic version [default: v]

The prefix is only used to parse the number out of the tag.
maybe --max-minors or --max-majors could be specified. you could always specify a range (v2.0.0..) to show/check all changes after v2.0.0

The advantage of --max-x is that it’s relative. Specifying the git baseline requires logic integrating with git and ci at least.

I would also be interested in a similar functionality. My use case is to create up a changelog up until the latest non-milestone release.
To my understanding, currently I can use --max-versions=1 to render a changelog "for this release". However, if I do milestone releases, that would no longer works, as I would only get the changelog between the release and the last milestone release.
So maybe something like: --max-versions=1 --dont-count-milestones (which is a weird name, just to give an example).

What is a “milestone” or “milestone release” in your case? And how, if at all, does it relate to semantic versioning with major.minor.patch version numbering?

Ok, call that "pre-release" in the Rust world: https://doc.rust-lang.org/cargo/reference/resolver.html#pre-releases

Same for Go: https://go.dev/doc/modules/version-numbers#pre-release

That makes sense, to exclude pre-releases when counting tags/releases for changelog generating.
So, with both cases in mind,
convco changelog --max-versions 1 --dont-count-prerelease --dont-count-patch

Pre-release versions are interesting, if one would print a changelog of the last major it should ignore the current pre-release versions, but include the pre-release versions of that major.
e.g. we have the versions 1.x.x, 2.x.x-alpha, 2.x.x and 3.0.0-alpha
--max-major-versions 1 --ignore-pre-release should only print out version 2.x.x.-alpha until including 2.x.x and only ignore the current pre-release versions. If it would be a 3.1.0-alpha it should print a changelog of 3.0.0 until excluding 3.1.0-alpha.
--max-major-versions 1 just prints the changes as from >2.x.x (excluding 2.x.x).
same logic to be hold for --max-minor-versions

@ite-klass and @ctron https://github.com/convco/convco/pull/79 does implement the --max-majors/minors/patches
If multiple flags are combined the first one that is reached will make the changelog generator stop e.g. convco changelog --max-minor 2 --max-patches 2 will show v0.3.11 and v0.3.10 for convco and not show v0.2.2 and v0.2.3. I think that is the most logical option, otherwise i could make the flags conflicting with each other, so you can only specify 1 flag at a time.
I still have to implement the --ignore-pre-release.

I think this ticket / the original request is implemented with --max-majors 2?
I think this ticket should be closed as implemented then. If you still plan on --ignore-pre-release that could be a separated, dedicated issue ticket.

authors: ctron hdevalke ite-klass

repo: convco/convco


text:
Networking-Team-Lead-Spec

closes #6

Closing this as it is duplicated in #42

repo: convict-git/KoraKaagaz


text:
Output Sound choppy

Sound output is really choppy, no chance to understand a single bit on the doorbird.
Tried multiple files mp3/wav and preconverted into ulaw 8khz aswell
Please see the AppDaemon Log attached
[13:09:08] INFO: Starting AppDaemon...
s6-rc: info: service legacy-services successfully started
2024-05-27 13:09:10.149301 INFO AppDaemon: AppDaemon Version 4.4.2 starting
2024-05-27 13:09:10.149421 INFO AppDaemon: Python version is 3.11.9
2024-05-27 13:09:10.149524 INFO AppDaemon: Configuration read from: /config/appdaemon.yaml
2024-05-27 13:09:10.149628 INFO AppDaemon: Added log: AppDaemon
2024-05-27 13:09:10.149736 INFO AppDaemon: Added log: Error
2024-05-27 13:09:10.149839 INFO AppDaemon: Added log: Access
2024-05-27 13:09:10.149941 INFO AppDaemon: Added log: Diag
2024-05-27 13:09:10.244897 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2024-05-27 13:09:10.339916 INFO HASS: HASS Plugin Initializing
2024-05-27 13:09:10.340002 WARNING HASS: ha_url not found in HASS configuration - module not initialized
2024-05-27 13:09:10.340069 INFO HASS: HASS Plugin initialization complete
2024-05-27 13:09:10.340260 INFO AppDaemon: Initializing HTTP
2024-05-27 13:09:10.340410 INFO AppDaemon: Using 'ws' for event stream
2024-05-27 13:09:10.342993 INFO AppDaemon: Starting API
2024-05-27 13:09:10.344546 INFO AppDaemon: Starting Admin Interface
2024-05-27 13:09:10.344722 INFO AppDaemon: Starting Dashboards
2024-05-27 13:09:10.352267 INFO HASS: Connected to Home Assistant 2024.5.5
2024-05-27 13:09:10.356045 INFO AppDaemon: App 'hello_world' added
2024-05-27 13:09:10.356712 INFO AppDaemon: App 'doorbird_audio' added
2024-05-27 13:09:10.357177 INFO AppDaemon: Found 2 active apps
2024-05-27 13:09:10.357285 INFO AppDaemon: Found 0 inactive apps
2024-05-27 13:09:10.357373 INFO AppDaemon: Found 0 global libraries
2024-05-27 13:09:10.357468 INFO AppDaemon: Starting Apps with 2 workers and 2 pins
2024-05-27 13:09:10.357880 INFO AppDaemon: Running on port 5050
2024-05-27 13:09:10.384307 INFO HASS: Evaluating startup conditions
2024-05-27 13:09:10.388683 INFO HASS: Startup condition met: hass state=RUNNING
2024-05-27 13:09:10.388926 INFO HASS: All startup conditions met
2024-05-27 13:09:10.421501 INFO AppDaemon: Got initial state from namespace default
2024-05-27 13:09:12.361120 INFO AppDaemon: Scheduler running in realtime
2024-05-27 13:09:12.362035 INFO AppDaemon: Adding /config/apps to module import path
2024-05-27 13:09:12.362838 INFO AppDaemon: Loading App Module: /config/apps/doorbird_audio.py
2024-05-27 13:09:12.396271 INFO AppDaemon: Loading App Module: /config/apps/hello.py
2024-05-27 13:09:12.396822 INFO AppDaemon: Loading app hello_world using class HelloWorld from module hello
2024-05-27 13:09:12.397383 INFO AppDaemon: Loading app doorbird_audio using class DoorbirdAudio from module doorbird_audio
2024-05-27 13:09:12.398044 INFO AppDaemon: Calling initialize() for hello_world
2024-05-27 13:09:12.422741 INFO hello_world: Hello from AppDaemon
2024-05-27 13:09:12.423230 INFO hello_world: You are now ready to run Apps!
2024-05-27 13:09:12.423692 INFO AppDaemon: Calling initialize() for doorbird_audio
2024-05-27 13:09:12.424552 INFO AppDaemon: App initialization complete
2024-05-27 13:09:51.088991 WARNING doorbird_audio: ------------------------------------------------------------
2024-05-27 13:09:51.089135 WARNING doorbird_audio: Unexpected error in worker for App doorbird_audio:
2024-05-27 13:09:51.089257 WARNING doorbird_audio: Worker Ags: {'id': '61125763d71a48fc9732bb56e4d94e7c', 'name': 'doorbird_audio', 'objectid': 'c0d6aa6e93fb4c4a8b2e7141909ff011', 'type': 'event', 'event': 'doorbird_audio', 'function': <bound method DoorbirdAudio.doorbird_audio of <doorbird_audio.DoorbirdAudio object at 0x7fc31b40e210>>, 'data': {'device_ip': '192.168.1.220', 'username': 'XXXXX', 'password': 'XXXXX', 'audio_url': 'http://192.168.1.114:8123/local/doorbird.mp3', 'metadata': {'origin': 'LOCAL', 'time_fired': '2024-05-27T11:09:37.438571+00:00', 'context': {'id': '01HYWVVNRYM361TH1NWNN170QN', 'parent_id': None, 'user_id': '26262bdb3712457486cf0ee731a79cce'}}}, 'pin_app': True, 'pin_thread': 1, 'kwargs': {'__thread_id': 'thread-1'}}
2024-05-27 13:09:51.089370 WARNING doorbird_audio: ------------------------------------------------------------
2024-05-27 13:09:51.091348 WARNING doorbird_audio: Traceback (most recent call last):
File "/usr/lib/python3.11/site-packages/appdaemon/threading.py", line 1095, in worker
funcref(args["event"], data, self.AD.events.sanitize_event_kwargs(app, args["kwargs"]))
File "/config/apps/doorbird_audio.py", line 119, in doorbird_audio
doorbird.send_audio(data["audio_url"])
File "/config/apps/doorbird_audio.py", line 97, in send_audio
with requests.post(
^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/requests/api.py", line 115, in post
return request("post", url, data=data, json=json, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/requests/api.py", line 59, in request
return session.request(method=method, url=url, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/requests/sessions.py", line 587, in request
resp = self.send(prep, **send_kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/requests/sessions.py", line 701, in send
r = adapter.send(request, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/requests/adapters.py", line 531, in send
r = low_conn.getresponse()
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/http/client.py", line 1395, in getresponse
response.begin()
File "/usr/lib/python3.11/http/client.py", line 325, in begin
version, status, reason = self._read_status()
^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/http/client.py", line 307, in _read_status
raise BadStatusLine(line)
http.client.BadStatusLine:
2024-05-27 13:09:51.091472 WARNING doorbird_audio: ------------------------------------------------------------
2024-05-27 13:09:51.092131 WARNING AppDaemon: Excessive time spent in callback 'doorbird_audio() in doorbird_audio', Thread 'thread.thread-1' - now complete after 14.091939 seconds (limit=10)

Fixed it so far
`import appdaemon.plugins.hass.hassapi as hass
import requests
from requests.auth import HTTPBasicAuth
from requests.exceptions import RequestException
import subprocess
from io import BytesIO
from time import sleep, time
class DoorbirdException(Exception):
"""An exception for doorbirds"""
class Doorbird:
CHUNK_SIZE = 4096  # Moderate chunk size in bytes
RATE_LIMIT = 8192  # Bytes per second (8KB per second)
CHUNK_INTERVAL = 0.5  # Interval in seconds (500 ms for larger chunks)
def __init__(self, device_ip, username, password):
    """
    Connect to a Doorbird

    Args:
        device_ip (str): Doorbird device IP address.
        username (str): Doorbird HTTP username.
        password (str): Doorbird HTTP password.

    Raises:
        DoorbirdException
    """
    self.device_ip = device_ip
    self.username = username
    self.password = password
    self.session_id = self._get_session_id()

def _get_session_id(self):
    """
    Get session ID from Doorbird device.

    Raises:
        DoorbirdException: If unable to obtain session ID.
    """
    get_session_url = f"http://{self.device_ip}/bha-api/getsession.cgi"
    auth = (self.username, self.password)
    try:
        response = requests.get(get_session_url, auth=auth)
        response.raise_for_status()
        data = response.json()
        return data["BHA"]["SESSIONID"]
    except RequestException as e:
        raise DoorbirdException(f"Failed to obtain session ID: {e}")

def _convert_audio(self, input_file):
    """
    Convert audio to 8000Hz mono PCM mu-law format.

    Args:
        input_file (str): Path to the input audio file.

    Returns:
        bytes: Converted audio data.
    """
    try:
        process = subprocess.run(
            [
                'ffmpeg', '-y', '-i', input_file, '-ar', '8000', '-ac', '1', '-f', 'mulaw', 'pipe:1'
            ],
            stdout=subprocess.PIPE,
            stderr=subprocess.PIPE,
            check=True
        )
        return process.stdout
    except subprocess.CalledProcessError as e:
        raise DoorbirdException(f"FFmpeg conversion failed: {e.stderr.decode()}")

def _generate_audio_chunks(self, audio_data):
    """
    Generator function to yield chunks of audio data from a file.
    Doorbird is rate-limited to 8KB per second.

    Args:
        audio_data: Converted audio data

    Yields:
        bytes: Chunks of audio data.
    """
    stream = BytesIO(audio_data)
    next_chunk_time = time()
    while True:
        start_time = time()
        chunk = stream.read(self.CHUNK_SIZE)
        if not chunk:
            break
        yield chunk
        elapsed_time = time() - start_time
        next_chunk_time += self.CHUNK_INTERVAL
        sleep_time = max(0, next_chunk_time - time())
        self._log_timing(self.CHUNK_SIZE, elapsed_time, sleep_time)
        sleep(sleep_time)

def _log_timing(self, chunk_size, elapsed_time, sleep_time):
    """
    Log the timing details for each chunk.

    Args:
        chunk_size (int): Size of the chunk.
        elapsed_time (float): Time taken to process the chunk.
        sleep_time (float): Time to sleep before sending the next chunk.
    """
    print(f"Chunk Size: {chunk_size}, Elapsed Time: {elapsed_time:.6f}, Sleep Time: {sleep_time:.6f}")

def send_audio(self, audio_url):
    """
    Send audio to Doorbird device.

    Args:
        audio_url (str): URL of the audio file.

    Raises:
        DoorbirdException: If any step in the process fails.
    """
    try:
        # Download the audio file
        audio_response = requests.get(audio_url)
        audio_response.raise_for_status()
        audio_file_path = '/config/downloaded_audio.mp3'
        with open(audio_file_path, 'wb') as audio_file:
            audio_file.write(audio_response.content)

        # Convert the audio file
        audio_data = self._convert_audio(audio_file_path)

        # Transmit the audio file in chunks
        audio_transmit_url = f"http://{self.device_ip}/bha-api/audio-transmit.cgi?sessionid={self.session_id}"
        auth = HTTPBasicAuth(self.username, self.password)

        def audio_stream():
            for chunk in self._generate_audio_chunks(audio_data):
                yield chunk

        response = requests.post(
            audio_transmit_url,
            headers={"Content-Type": "audio/basic", "Connection": "Keep-Alive", "Cache-Control": "no-cache"},
            data=audio_stream(),
            auth=auth,
            timeout=60
        )

        response.raise_for_status()
        print("Audio transmission completed successfully.")

    except RequestException as e:
        raise DoorbirdException(f"Failed to send audio: {e}")

class DoorbirdAudio(hass.Hass):
"""AppDaemon app to handle Doorbird audio events."""
def initialize(self):
    """Initialize the AppDaemon app."""
    self.listen_event(self.doorbird_audio, "doorbird_audio")

def doorbird_audio(self, event_name, data, kwargs):
    """Handle Doorbird audio event."""
    try:
        self.log(f"Received event: {event_name} with data: {data}")
        doorbird = Doorbird(data["device_ip"], data["username"], data["password"])
        doorbird.send_audio(data["audio_url"])
        self.log("Audio transmission completed successfully.")
    except DoorbirdException as e:
        self.log(f"Failed to send audio: {e}")

`

Can you please explain what you have changed?

repo: coobnoob/ha-appdaemon-doorbird-audio

license: Unlicense


text:
Docker compose方式部署的，Web端请求依然报告”请求失败“，说是token问题，如下图

前后端打包成一个镜像了，请按照readme运行一下，如果有问题再开issue。

authors: brusehht cooderl

repo: cooderl/wewe-rss


text:
这样安装的集群证书有效期是一年吧？kubeadm源码里面写死的是1年。

RT

证书重新生成有单独的步骤吗？不是在kubeadm init时候生成的吗？中途重新生成的方法是怎么样的？对集群以及集群上的业务会有影响的吧。

还有1年的时效限制啊，是每个master中ca.key和ca.crt要更换，还是使用ca.key和ca.crt签署apiserver证书？

不过1年时间，早就换了N个版本了···

@leeningli
$ kubeadm alpha phase certs --help
This command is not meant to be run on its own. See list of available subcommands.

Usage:
  kubeadm alpha phase certs [command]

Aliases:
  certs, certificates

Available Commands:
  all                      Generates all PKI assets necessary to establish the control plane
  apiserver                Generates an API server serving certificate and key
  apiserver-etcd-client    Generates a client certificate for the API server to connect to etcd securely
  apiserver-kubelet-client Generates a client certificate for the API server to connect to the kubelets securely
  ca                       Generates a self-signed kubernetes CA to provision identities for components of the cluster
  etcd-ca                  Generates a self-signed CA to provision identities for etcd
  etcd-healthcheck-client  Generates a client certificate for liveness probes to healthcheck etcd
  etcd-peer                Generates an etcd peer certificate and key
  etcd-server              Generates an etcd serving certificate and key
  front-proxy-ca           Generates a front proxy CA certificate and key for a Kubernetes cluster
  front-proxy-client       Generates a front proxy CA client certificate and key for a Kubernetes cluster
  sa                       Generates a private key for signing service account tokens along with its public key

@cookeem  有个疑问，ca根证书需要替换吗？他的过期时间是十年，是不是不用替换？

@cookeem 我尝试更换证书后，然后修改系统时间，发现并不生效，也重启了kubelet

如果ca证书没有过期，是不需要替换的。v1.13的kubeam开始支持cert renew，官方推荐的方式。
如果你是用v1.11.X版本，建议进行升级，最近爆出来高危漏洞，可获取集群所有节点的root权限，建议进行升级到v1.11.5。 @dotbalo

@cookeem 已经升级到12.3，升级后发现证书也更新了，但是证书只有一年有效期，我在线下测试过1.11和1.12版本的证书更新，发现更新过集群重启有无法启动的情况，1.13的renew你有测试过吗？

authors: cookeem dotbalo leeningli salwell

repo: cookeem/kubeadm-ha


text:
[Chrome/Android] Media notification persists even after player is unmounted

Current Behavior
When a video (longer than 5 seconds) was unmuted and then the player is unmounted, a media session notification will appear: https://developers.google.com/web/updates/2015/07/media-notifications
Expected Behavior
When the player is unmounted, any media session notification related to it should disappear. Ideally I don't even want it to appear in the first place.
Steps to Reproduce

Start a video (muted)
Unmute video
Navigate away (in your SPA) so player is unmounted

Environment

URL attempting to play: File url
Browser: Chrome
Operating system: Android

As per this comment, when the player is removed, the notification should be removed, which doesn't happen: https://github.com/w3c/mediasession/issues/215#issuecomment-500530575
I also tried setting the player url to an empty string, but that doesn't remove the notification either.

Same problem. Looking for a solution as well.

authors: GabrielmLinassi fabyeah

repo: cookpete/react-player


text:
Not working in Inventor 2021, or even the online ThreadModeller BETA

Hi!
I tried installing the add-in from the Autodesk app store, and try it in inventor 2021. The add-in manager did recognize the Add-in, but did not show any option to use it.

Upon further investigation, the publisher said that there is no version for inventor 2021, and asked to use the the Online threadmodeller, but it isn't working on my model:

Can you suggest an alternative or solution?
Warm Regards,
Rohit Kumar J

Found the solution:

Warm Regards,
Rohit Kumar J

repo: coolOrangeLabs/inventor-thread-modeler


text:
[Bug]: Environment variables not replaced in source compose file.

Error Message and Logs
No message but :
We have a Coolify instance to which we added many server.
Few week ago, we added our Django application using docker compose resource and this worked like a charm. For instance, in the docker compose, we have many environment variables such as
    environment:
      - DJANGO_SECRET_KEY
      - DJANGO_SETTINGS_MODULE
      - IPYTHONDIR
      - POSTGRES_DB
      - POSTGRES_HOST
      - POSTGRES_PASSWORD
      - POSTGRES_PORT
      - POSTGRES_USER
      - TOKEN_SECRET_KEY
      - USE_DOCKER
      - REDIS_URL
      - DATABASE_URL
      - EMAIL_PASSWORD
      - SENDER_EMAIL
      - EMAIL_HOST

which were correctly replaced when clicking on the 'Show Deployable Compose' button after adding them through the relevant 'Environment Variables' tab.
Today, we added a new server (remote server) and we recreated the exact same project, with the same environment variables but, those are not being replaced when clicking on the 'Show Deployable Compose' button.
This is confirmed when we start the application because there are failures due to missing values (environment variables are not being filled with expected values).
Steps to Reproduce

Add a remote server. Note that we are using a non-privileged user (usage of sudo).
Add a new resource to that server: Docker based -> Docker compose.
Add the expected environment variables and their values via the 'Environment Variables' tab.
Edit the compose file by clicking on the 'Edit Compose File' button, in the 'Service Stack' tab.
Click on the 'Show Deployable Compose' button.

Current result: Environment variables are not filled.
Expected result: Environment variables need to be filled with values as added via the 'Environment Variables' tab.
To fix the issue temporarily, we have been mandatory to hardcode the environment variables into the Compose file.
Example Repository URL
No response
Coolify Version
v4.0.0-beta.341
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Debian 12
Additional Information
Note: Our Coolify instance is hosted on Debian 12 but the server for which we added the resource is AlmaLinux 9.

@andrasbacsai If you need some screenshots I can provide them, just tell me. Also, if there is any log to look at, feel free to say which are those log.

@andrasbacsai
See the provided screens.

@andrasbacsai More info:
For the project for which this worked (other server), I've added a new environment variable in the compose file and through the environment variables tab too. This variable is not being replaced, while the holdest ones are. We updated to latest Coolify version recently so ...

BTW: As per documentation, it is said that if doing something like this:
environment:
 -SOME_VARIABLE=${SOME_VARIABLE_IN_COOLIFY_UI}

This will creates an uninitialized environment variable editable in Coolify's UI.
That is not working neither ATM.
https://coolify.io/docs/knowledge-base/docker/compose/

Also, surrounding values with single and then double quotes sound really strange to me...
COOLIFY_CONTAINER_NAME: '"django-qsokk40088g4so8wk0k44wcs"'
COOLIFY_APP_NAME: '"service-qsokk40088g4so8wk0k44wcs"'
COOLIFY_SERVER_IP: '"sso-mad-005"'
COOLIFY_ENVIRONMENT_NAME: '"testing"'
COOLIFY_PROJECT_NAME: '"Playground"'

@andrasbacsai Right now, I've downgraded to v331 and the problem is gone. I could update to latest version incrementally to figure out which version is causing the problem but do you need that information ?
Thank you for your time.

repo: coollabsio/coolify


text:
Fix 404

Outdated docs url.

Thank you for the PR!

authors: andrasbacsai carstenjaksch


text:
Tracker IP should be unique

Should tracker IP be unique in the DB? What benefits/drawbacks does this have? Also if #11 gets implemented, IP + port pair should be unique instead maybe?

tracker ip should be unique

authors: aaron-williamson jvaneg


text:
More info on features needed

How displaying messages/errors work?
It stopped working for me and I dont know how to fix it.
I see method inside Create.vue views:
onSuccess(msg) {
    this.displayNotification('success',msg);
}

But cant figure it out, where the code goes further.

How do Excel/export boilerplate work?
I can see generator adds this to controllers:
php use App\Exports\ClassNameExport; use Maatwebsite\Excel\Excel   //no here semicolon
But except that cant find out how to make data export.

Forgot to mention App\Exports\ folder doesn't exist.


text:
I get resource not found while it tries to fetch App Name

I get Resource not found after picking the pic from gallery!!!
on further debugging i found the library was crashing on a very simple thing , which was when it was trying to fetch app name from ApplicationInfo ,
funny part was ur sample app works seamlessly on my phone and blue stacks
but ur library integrated crashes...!!
wat is the best solution u propose ..!!

Can you send me complete logs? Are you running on 6.0? Might be a permissions issue. Device and OS versions information also might help.

same bug
this is the logs
 FATAL EXCEPTION: Thread-230                                                                 Process: ly.neon.daleel, PID: 23898                                                                 android.content.res.Resources$NotFoundException: String resource ID #0x0                                                                     at android.content.res.Resources.getText(Resources.java:299)                                                                     at android.content.res.Resources.getString(Resources.java:385)                                                                     at android.content.Context.getString(Context.java:377)                                                                     at com.kbeanie.multipicker.utils.FileUtils.getAppName(FileUtils.java:56)                                                                     at com.kbeanie.multipicker.utils.FileUtils.getExternalFilesDirectory(FileUtils.java:37)                                                                     at com.kbeanie.multipicker.core.threads.FileProcessorThread.getTargetDirectory(FileProcessorThread.java:490)                                                                     at com.kbeanie.multipicker.core.threads.FileProcessorThread.generateFileName(FileProcessorThread.java:577)                                                                     at com.kbeanie.multipicker.core.threads.FileProcessorThread.getFromContentProvider(FileProcessorThread.java:246)                                                                     at com.kbeanie.multipicker.core.threads.FileProcessorThread.processFile(FileProcessorThread.java:174)                                                                     at com.kbeanie.multipicker.core.threads.FileProcessorThread.processFiles(FileProcessorThread.java:105)                                                                     at com.kbeanie.multipicker.core.threads.FileProcessorThread.run(FileProcessorThread.java:79)                                                                     at com.kbeanie.multipicker.core.threads.ImageProcessorThread.run(ImageProcessorThread.java:41)

OS Version?

API 22, and 24

can you confirm if your application tag in manifest file has a label specified?

That seems to be the issue. I will fix this in the next release. Till then, if it is possible, can you specify the label in the application tag for your application? That should take care of this issue.

Yes i set the label and it works ,but it wont work if i set the label to be just in arabic languege, thank you

You can try the beta build for now.
compile 'com.kbeanie:multipicker:1.1.21-beta@aar'


text:
Add support for mercurial

Is your feature request related to a problem? Please describe.
I need to use mercurial repository as repository containing the template.
I also need to initialize mercurial projects from templates. (it looks like this is something copier is capable of, otherwise it is not needed).
Describe the solution you'd like
I’d like both points to be possible.
It does not look like its possible to indicate the branch to use in a git repository, so that would be nice to be able to do too with mercurial templates.
Describe alternatives you've considered
The alternative would be to use cookiecutter.
The ability to update a project from a template would be missed thought.

Thanks! I knew some day somebody would come up with this! 😆 (Next one will be pijul -- I hope nobody asks for svn or bzr these days).
All Copier's magic is currently very tied to git. Maybe too much indeed. It would be really good if we did this:

Abstract out the vcs operations.
Implement current Git operations as an implementation of that abstract something.
Add mercurial too (this one should be a separate PR).

However I'll close as won't fix for the sake of honesty and to keep the issue tracker clean. FWIW I have no plans to implement this. However, it'd be really nice if somebody wants to propose the PR.

authors: vincent-hatakeyama yajo

repo: copier-org/copier


text:
Fullscreen bricked my grandma's computer

HELP?????
I AM THE SAME PERSON AS BEFORE, AND MY ISSUE WASN'T SOLVED, ESC DOES NOT WORK TO EXIT FULLSCREEN!
I SEE THAT CHROME HAS REMOVED ESC AS A SHORTCUT, BUT CAN YOU PLEASE FIX IT? OR SHOULD I EMAIL CHROME SUPPORT TO ADD ESC SHORTCUT BACK?
THANKS COPY FOR BRICKING WINDOWS 7, NOW MY PARENTS WILL FUCKING KILL ME.

Hold Escape for 5 seconds.

Alright then, I'm killing Chrome (no, like literally) if it doesn't work

IT DOESN'T WORK!!!!!!!!!!!!!!!!!!!!! 👺

IT DOESN'T WORK!!!!!!!!!!!!!!!!!!!!! 👺

You never heard of F11 and a reboot? Imagine.

IT DOESN'T WORK!!!!!!!!!!!!!!!!!!!!! 👺

You never heard of F11 and a reboot? Imagine.

I HAVE BUT THE POWER BUTTON ONLY PUTS IT TO SLEEP AND F11 DOESN'T EVEN DO ANYTHING!!!!!!!!!

authors: Dimka380 copy upintheairsheep


text:
lang: Fuzzing host

Addresses https://github.com/project-serum/anchor/issues/123.

@armaniferrante do you have any updates on this by any chance?

@armaniferrante do you have any updates on this by any chance?

No it's currently on hold.

@armaniferrante  Is this PR still on hold ?

authors: armaniferrante lengdavid macalinao

repo: coral-xyz/anchor


text:
Avoid copy in count / logical nulls

This is a proposed improvement of  https://github.com/apache/arrow-datafusion/pull/8511  to avoid copying Null Buffers in the count aggregator.
Note this targets https://github.com/apache/arrow-datafusion/pull/8511
I will also file a proposal to upstream this change into arrow-rs
cc @joroKr21 and @Dandandan

Ok I see - it kinda makes sense, you handle the known types in a pattern match.
It's unlikely new types will be added before we can upstream this change 👍

I think this may be overkill -- https://github.com/apache/arrow-datafusion/pull/8511#pullrequestreview-1782193343
Closing this PR and let's keep the code simple unless we find some profile or benchmark where it matters

Doh, just missed it !

repo: coralogix/arrow-datafusion


text:
Refactored leader election module and ability to work with CRDs

Implements #166 and makes it possible to implement #165.

That's a good point and it only needs the CRD being embedded as a resource. The registration and the leader election are already in the same artifact.


text:
Incorrect Macro Expansions for Log and Msg of Chained Rule

Description
The MATCHED_VAR_NAME is taken from the chained rule. It should instead be taken from the rule where msg action is defined.
Variables are expanded incorrectly for Log and Msg of Rule
MATCHED_VAR expands to REQUEST_HEADERS:host i.e key but it should be attack i.e. value of MATCHED_VAR
MATCHED_VAR_NAME expands to MATCHED_VARS_NAMES:REQUEST_HEADERS:host i.e. key:value but it should be value of MATCHED_VAR_NAME
It seems the msg, data gets overridden as the chain rule gets evaluated.
Steps to reproduce
rules = `
SecRule REQUEST_HEADERS "@rx attack" \
    "id:20,\
    phase:1,\
    log,\
    msg:'Chained rule test',\
    logdata:'Found %{MATCHED_VAR} in %{MATCHED_VAR_NAME}',\
    chain"
    SecRule MATCHED_VARS_NAMES "@rx host" \
        "block"
`
waf := coraza.NewWaf()
parser, err := seclang.NewParser(waf)
if err != nil {
    fmt.Println(err)
}
err = parser.FromString(rules)
if err != nil {
    fmt.Println(err)
}
tx := waf.NewTransaction()
tx.ForceRequestBodyVariable = true
tx.AddRequestHeader("Host", "attacker")
tx.ProcessURI("/test", "POST", "HTTP/1.1")
tx.ProcessRequestHeaders()
tx.ProcessRequestBody()
fmt.Println("Interruption", tx.Interruption)
for _, match := range tx.MatchedRules {
    fmt.Println("matched Msg ", match.Message)
    fmt.Println("matched Data ", match.Data)
}

Expected result
matched Msg  Chained rule test
matched Data  Found attack in REQUEST_HEADERS:host

Actual result
matched Msg  Chained rule test
matched Data  Found REQUEST_HEADERS:host in MATCHED_VARS_NAMES:REQUEST_HEADERS:host

IMHO this would not work.
A rule like the following would require preserving the last chain. So it would be better to preserve the match message and data from the rule/subrule where the msg, logdata action are specified. I have a fix in work that solves this.
SecRule REQUEST_HEADERS "@rx attack" \
    "id:20,\
    phase:1,\
    log,\
    chain"
    SecRule MATCHED_VARS_NAMES "@rx host" \
         msg:'Chained rule test',\
         logdata:'Found %{MATCHED_VAR} in %{MATCHED_VAR_NAME}',\
        "block"

IMHO this would not work.
A rule like the following would require preserving the last chain. So it would be better to preserve the match message and data from the rule/subrule where the msg, logdata action are specified. I have a fix in work that solves this.
SecRule REQUEST_HEADERS "@rx attack" \
    "id:20,\
    phase:1,\
    log,\
    chain"
    SecRule MATCHED_VARS_NAMES "@rx host" \
         msg:'Chained rule test',\
         logdata:'Found %{MATCHED_VAR} in %{MATCHED_VAR_NAME}',\
        "block"

@piyushroshan
If there are more than one chained rules, say 3, each chained rules has its logdata. Then how we will handle this? Or this is not a valid case?

This was fixed, right @piyushroshan ?

Yes.

authors: ShiMing-Q jptosso piyushroshan

repo: corazawaf/coraza


text:
feat: removed dist directory in published packages

BREAKING CHANGE: Изменена директория расположения индексных файлов в опубликованных пакетах (удалена
директория dist)

С текущим коммитом поднимаются версии всех пакетов

Pull Request Test Coverage Report for Build 2874648618

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 81.785%

Totals

Change from base Build 2874459244:
0.0%

Covered Lines:
5802

Relevant Lines:
6526

💛  - Coveralls

authors: Lacronts coveralls

repo: core-ds/core-components


text:
typeahead:select event does not pass dataset name

The typeahead:selected event, when triggered, used to pass the name of the dataset of the item selected as the third parameter, but it doesn't anymore for the typeahead:select event. How do we know the name of the dataset the selected item belongs to?

@onokazu Is this related (and possibly fixed by) #65?

Duplicate of #63 and #58

authors: jlbooker onokazu


text:
pkg/analytics: Remove Google Analytics tracking

We never even look at these analytics and its unclear what value they provide. No need to tradeoff being creepy if it isn't providing clear value.

Added change to show a warning if -analytics flag is used (regardless of value). Rebased.

repo: coreos/container-linux-update-operator