text:
Read through fuse points to incorrect URL

Sponsors SeaweedFS via Patreon https://www.patreon.com/seaweedfs
Describe the bug
Using weed mount command to mount a directory. Directory tree can be listed but failed when try to achieve an object
System Setup

In server 172.27.221.2

nohup ./weed master -mdir="./mdata" > master.log 2>&1 &
nohup ./weed volume -mserver="localhost:9333" -port=8081 -dir="./data" -publicUrl="172.27.221.2:8081" > volume.log 2>&1 &
nohup ./weed filer > filer.log 2>&1 &

In client 172.28.43.46

nohup ./weed mount -filer=172.27.221.2:8888 -dir=rdir -filer.path=/ 2>&1 &

Expected behavior
Achieve files as local storagement.
Screenshots
Some log related.
➜  rdir ls -l
total 0
-rw-rw----. 1 scper scper 143028 Sep  4 10:51 162d749c1064bac28.jpg
-rw-rw-r--. 1 root  root       0 Sep  4 11:02 bug.txt
-rw-rw-r--. 1 root  root       0 Sep  4 11:48 docker-compose.yml
-rw-r--r--. 1 root  root    5380 Sep  4 11:03 kubecfg-kube-admin.yaml
-rw-rw----. 1 scper scper  45056 Sep  4 11:31 test
drwxrwx---. 1 scper scper      0 Sep  4 11:46 test1
-rw-rw----. 1 scper scper   2007 Sep  4 10:50 youtube_with_pyspider.py
➜  rdir cat kubecfg-kube-admin.yaml
cat: kubecfg-kube-admin.yaml: Input/output error
➜  rdir stat .
  File: .
  Size: 0               Blocks: 0          IO Block: 4096   directory
Device: 100022h/1048610d        Inode: 1           Links: 1
Access: (0777/drwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Context: system_u:object_r:fusefs_t:s0
Access: 2018-09-04 11:35:16.332740191 +0800
Modify: 2018-09-04 11:35:16.332740191 +0800
Change: 2018-09-04 11:35:16.332740191 +0800

Log of mount process

I0904 12:26:16 32361 filehandle.go:115] //kubecfg-kube-admin.yaml read http://127.0.0.1:8081/1,0f2510b483 0 bytes: Get http://127.0.0.1:8081/1,0f2510b483: dial tcp 127.0.0.1:8081: connect: connection refused

Additional context
I think the problem is mainly the filer doesn't use the public URL to access volume server.
Another situation may be help show below
➜  rdir ll
total 0
-rw-rw----. 1 scper scper 140K Sep  4 10:51 162d749c1064bac28.jpg
-rw-rw-r--. 1 root  root     0 Sep  4 11:02 bug.txt
-rw-rw-r--. 1 root  root     0 Sep  4 11:48 docker-compose.yml
-rw-r--r--. 1 root  root  5.3K Sep  4 11:03 kubecfg-kube-admin.yaml
-rw-rw-r--. 1 root  root   158 Sep  4 14:40 Pipfile
-rw-rw----. 1 scper scper  44K Sep  4 11:31 test
drwxrwx---. 1 scper scper    0 Sep  4 11:46 test1
-rw-rw----. 1 scper scper 2.0K Sep  4 10:50 youtube_with_pyspider.py
➜  rdir cp ~/hello.exs .
cp: failed to close './hello.exs': Input/output error
➜  rdir ll
total 0
-rw-rw----. 1 scper scper 140K Sep  4 10:51 162d749c1064bac28.jpg
-rw-rw-r--. 1 root  root     0 Sep  4 11:02 bug.txt
-rw-rw-r--. 1 root  root     0 Sep  4 11:48 docker-compose.yml
----------. 1 root  root    34 Sep  4 14:41 hello.exs
-rw-r--r--. 1 root  root  5.3K Sep  4 11:03 kubecfg-kube-admin.yaml
-rw-rw-r--. 1 root  root   158 Sep  4 14:40 Pipfile
-rw-rw----. 1 scper scper  44K Sep  4 11:31 test
drwxrwx---. 1 scper scper    0 Sep  4 11:46 test1
-rw-rw----. 1 scper scper 2.0K Sep  4 10:50 youtube_with_pyspider.py

And the log of the mount process is
I0904 14:41:05 32361 upload_content.go:89] failing to upload to http://127.0.0.1:8081/1,15329ff42d Post http://127.0.0.1:8081/1,15329ff42d: dial tcp 127.0.0.1:8081: connect: connection refused
I0904 14:41:05 32361 dirty_page.go:145] upload data hello.exs to http://127.0.0.1:8081/1,15329ff42d: Post http://127.0.0.1:8081/1,15329ff42d: dial tcp 127.0.0.1:8081: connect: connection refused
2018/09/04 14:41:05 fuse: panic in handler for Flush [ID=0xe7c Node=0x3 Uid=1000 Gid=1000 Pid=14931] 0x1 fl=0x0 lk=0xb6a74297c26d5718: runtime error: invalid memory address or nil pointer dereference
goroutine 12406 [running]:
bazil.org/fuse/fs.(*Server).serve.func2(0x10d3860, 0xc0000dc0a0, 0xc00044def8, 0xc00044de77)
        /home/travis/gopath/src/bazil.org/fuse/fs/serve.go:857 +0x1ac
panic(0xe2d080, 0x17f6260)
        /home/travis/.gimme/versions/go/src/runtime/panic.go:513 +0x1b9
github.com/chrislusf/seaweedfs/weed/filesys.(*FileHandle).Flush(0xc0000300f0, 0x10d7ba0, 0xc00049e080, 0xc0000dc0a0, 0xc0000300f0, 0x47fa01)
        /home/travis/gopath/src/github.com/chrislusf/seaweedfs/weed/filesys/filehandle.go:182 +0x4a9
bazil.org/fuse/fs.(*Server).handleRequest(0xc0003760c0, 0x10d7ba0, 0xc00049e080, 0x10cb020, 0xc0000300a0, 0xc00023c040, 0x10d3860, 0xc0000dc0a0, 0xc00044def8, 0x10ca6a0, ...)
        /home/travis/gopath/src/bazil.org/fuse/fs/serve.go:1282 +0x2bec
bazil.org/fuse/fs.(*Server).serve(0xc0003760c0, 0x10d3860, 0xc0000dc0a0)
        /home/travis/gopath/src/bazil.org/fuse/fs/serve.go:878 +0x410
bazil.org/fuse/fs.(*Server).Serve.func1(0xc0003760c0, 0x10d3860, 0xc0000dc0a0)
        /home/travis/gopath/src/bazil.org/fuse/fs/serve.go:425 +0x6e
created by bazil.org/fuse/fs.(*Server).Serve
        /home/travis/gopath/src/bazil.org/fuse/fs/serve.go:423 +0x321

set your ip when starting volume server
"./weed volume -ip=172.27.221.2 ...."

authors: Eloahman chrislusf


text:
I can't delete photos

I can't delete photos
First time
curl -X DELETE http://********:8080/4,07545dad5c6733
{"size":76956}

And this second time
curl -X DELETE http://********:8080/4,07545dad5c6733
{"size":76956}

Which the second half should be 0
(Other some id can be 0)

Follow the issue template to add more info.

can not help without details. please follow issue template with more context.

source: gharchive/issue

repo: chrislusf/seaweedfs

license_type: permissive

license_source: bigquery


text:
Update README.md

"export GO111MODULE=on" specified

Why this is needed? This is default to on for Go later versions.

Yes, you are right. But some developers may have changed it to off at some point and later have trouble figuring out why go get does not work properly.

Prefer not to add more lines here. The README is not to prevent all possible human errors. It's just to show the simplest way to get it up and running.

source: gharchive/pull-request


text:
and $ characters do not render in dialogue.

Adding either a # or $ character to a dialogue window does not render the text either in preview or in game. Assuming this is a big due to how wildcards for variable work. Unsure if this can be escaped with a special character, I haven't been able to find one.

Hi @proximitysound Just pushed a fix for this in 9bda3ab69b9e79b1d3f0080c89c181ca4ddf56e3 :-)

authors: chrismaltby proximitysound

repo: chrismaltby/gb-studio

license: MIT

license_source: github-api


text:
Common tileset optimizations on compilation

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
-Optimizes compilation of background and tilesets to prevent data redundancy and unused generated data.

What is the current behavior? (You can also link to an open issue here)
-currently tilesets compiled with common tilesets duplicates data despite having the exact same data

currently background with a common tilesets in all scenes will still compile a version without the common tileset even if never used.

What is the new behavior (if this is a feature change)?

reuses tilesets with the exact same data instead of duplicating it
dont compile backgrounds without a common tileset if there is no scene that uses the background without a common tileset

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No breaking changes or user changes needed.

Other information:
Example project that uses a common tileset among 13 scenes gives me a 30% size reduction of the rom used with the optimization (% size reduction is even greater the more scene I add):

This is great! Improved efficiency is very welcome


text:
update for phergie version 2 packages

Starting working on updating packages for Phergie version 2. Will update this PR once we merge in http (which is the current blocker for this)

Any chance of getting this rebased into a single commit? I'll merge it straight in after that

Any chance of getting this rebased into a single commit? I'll merge it straight in after that

To save time (and because I'm on a roll tonight) I've just made the changes along with the other tweaks and pushed a new tag (v2.1.0)


text:
Failing dates

I got random failures in our tests that seem to be valid dates to me but they get denied anyway.
While testing that with validator 4.2 another date test was failing too.

Thanks. What's your timezone offset? new Date().getTimezoneOffset()

-60

Thanks. Would you mind running the test suite from the #447 branch to see if the issue is still present?

@chriso my mentioned date works with #447 :+1:
But the one that I mentioned that it's failing local is still failing. It's confusing to me that travis has no issue but it does not run on my machine.

The travis containers have their system timezone set to UTC and unfortunately there's no way (AFAIK) of emulating an alternate timezone in JavaScript.

Can you try #447 again?

@chriso still failing

This should be fixed in version 4.2.1. Thanks for your help!

@chriso you're welcome. All tests pass now. Thx for fixing it so fast :)

authors: BridgeAR chriso

license: mit


text:
Feature request: m3u filter toggle for psx

Consider adding "Script" to adjust what formats are displayed in some of the systems.
For example, pretty much the only system that is impacted for me is PS1 games.
I use .chd that are working fine, the problem arises when the game has multiple disks.
Fix is simple, use .m3u, but the problem is that you now have entries for each disk+m3u listed after that.
In some other OS's you can set a filter to define which files to display, thus I have m3u created for each game, even single disc games.
In ArkOS, to my knowledge, you need to edit:
etc/emulationstation/es_systems.cfg
<name>psx</name>
<fullname>Sony - PlayStation</fullname>
<path>/roms/psx/</path>
<extension>.m3u .M3U</extension>
So pretty much an entry in Options - "PS1 - Show only m3u games" / "PS1 - Show all games".
That would modify the "extensions" part of the config.
*Bonus points would be to have a script that creates these m3u files from ArkOS itself.
**Multiple disc games in my environment are in sub-folder, single disk games are in the root folder of psx

This would require extensive modification to emulationstation that I'm not willing to invest time in for this.  You're welcome to review the emulationstation source used in ArkOS here and submit a PR for the functionality.

I now realize that the request is just to add the ability to change this option from a script in the options menu.

for file in *.chd; do echo "$file" >> "$(basename "$file").m3u"; done on linux
@echo off for /R "C:\Users\vaido\Downloads\Test\" %%I in (*.chd) do for %%J in ("%%~dpI.") do echo %%~nxI>>"%%~dpI%%~nxJ.m3u"  on windows via .bat

This is a handy feature and I have found a script (https://github.com/danyboy666/Generate-PSX-m3u-playlist/blob/master/generate_psx_m3u.sh ) that I’ve modified to handle .m3u creation even for subfolders.  Thanks for helping to test it.

This has been accommodated with today's update for the RGB10, RK2020, and the OGAs.  Will also be available in the next update for the RG351V.

authors: christianhaitian farfenkugell

repo: christianhaitian/arkos


text:
Problema na instalação da dependência Sqlite3'

Olá @christyanbrayan, tudo bem? Eu também criei esse mesmo sistema e subi para a minha conta do Github, eu quis baixar ele para ver algumas coisas nele no meu outro PC, porém estou tendo problemas para instalar a dependência sqlite3, você teve esse mesmo problema? Se teve, conseguiu solucionar?

@lucas-rabelo perdão pela demora na resposta. Faz um tempo que não mexo com esse repositório, e também estava afastado do GitHub como um todo. Quando eu tiver um tempo vou dar uma olhada. Mas pelo que posso lembrar acho que não tive nenhum problema nesse sentido não. Se puder depois detalhar mais esse problema, se ainda estiver com ele, que depois posso tentar ver.

authors: christyanbrayan lucas-rabelo

repo: christyanbrayan/casa-criativa


text:
[Feature Request]: How to export data?

Describe the problem
I have add lots of data in my chroma db, include embeddings.  My question is how can I export these data from the db, I do want embedding them again.  Thank you!
Describe the proposed solution
.
Alternatives considered
No response
Importance
would make my life easier
Additional Information
No response

@vegetax when you say export.. is there a particular format you are thinking of?

@jeffchuber  I'm looking for this as well.  ANY data format would suffice to know about, honestly.

I believe that I've figured it out.
My logic might be a little off here, but my assumptions are:

If the DB is small enough, collection.get() should do a dump.
If the DB is not small enough, but you're IDs are in order, you can do collection.count() to determine how many items there are, and then query by IDs to get batch values.

@jzombie you can use limit and offset to page through your data. like this!
def get(ids: Optional[OneOrMany[ID]] = None,
        where: Optional[Where] = None,
        limit: Optional[int] = None,
        offset: Optional[int] = None,
        where_document: Optional[WhereDocument] = None,
        include: Include = ["metadatas", "documents"]) -> GetResult

@jeffchuber I appreciate this update!

Closing this as it is stale. Please let me know if anything else pops up here and we can re-open it.
Other means of export will be supported in the future!

authors: jeffchuber jzombie vegetax

repo: chroma-core/chroma


text:
[BUG]: Python client sqlite issue

Refs: #1206
Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

Conditional import of sqlite for python client

Test plan
How are these changes tested?

[x] Tests pass locally with pytest for python

Additional test in older disto (debian buster) was run:
pip install chromadb-client
root@c26a0fadfcdc:~# python
Python 3.10.12 (main, Jun 13 2023, 12:02:28) [GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sqlite3
>>> print(sqlite3.sqlite_version_info)
(3, 27, 2)
>>> import chromadb
>>>

Documentation Changes
N/A

Thanks!

authors: HammadB tazarov


text:
[ENH] WIP: Support >= numpy 2.0

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

numpy 2.0 was not support because of ONNX runtime

New functionality

...

Test plan
How are these changes tested?

[ ] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

#2776  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @spikechroma and the rest of your teammates on  Graphite

Were you able to test this / confirm that onnxruntime released a supporting version to Pypi?
https://github.com/microsoft/onnxruntime/pull/21085

Were you able to test this / confirm that onnxruntime released a supporting version to Pypi?
microsoft/onnxruntime#21085

this is still in wip. let me test it today

Mac and Windows test passing for the
numpy 1.26.0 and onnxruntime 1.19.2
numpy 2.1.1 and onnxruntime 1.19.2

Closing in favor of #2811

authors: HammadB spikechroma


text:
CrossPlatDemo startup

I followed the steps in the readme, I can restore, build and run without any problems or errors. Also the initial download of the missing binaries was successful.
What I get after dotnet run:
2020-03-21 11:27:47.176 [INFO] Running MacOSX chromium 77.0.3865.120
On CefGlue child process launch arguments:
/Users/user/source/demo-projects/regular-chromely/CrossPlatDemo/bin/Debug/netcoreapp3.1/osx-x64/crossplatdemo --type=gpu-process --field-trial-handle=1718379636,5549198414550298470,15611372194352481318,131072 --disable-features=OutOfBlinkCors --no-sandbox --locales-dir-path=/Users/user/source/demo-projects/regular-chromely/CrossPlatDemo/bin/Debug/netcoreapp3.1/osx-x64/locales --log-file=logs\chromely.cef_20200321.log --log-severity=info --resources-dir-path=/Users/user/source/demo-projects/regular-chromely/CrossPlatDemo/bin/Debug/netcoreapp3.1/osx-x64/ --lang=en-US --default-encoding=utf-8 --allow-file-access-from-files --allow-universal-access-from-files --disable-web-security --ignore-certificate-errors

DevTools listening on ws://127.0.0.1:20480/devtools/browser/d40e206c-2b73-46f4-9215-68d981416982
2020-03-21 11:27:47.423 [INFO] Running MacOSX chromium 77.0.3865.120
On CefGlue child process launch arguments:
/Users/user/source/demo-projects/regular-chromely/CrossPlatDemo/bin/Debug/netcoreapp3.1/osx-x64/crossplatdemo --type=utility --field-trial-handle=1718379636,5549198414550298470,15611372194352481318,131072 --disable-features=OutOfBlinkCors --lang=en-US --service-sandbox-type=network --no-sandbox --locales-dir-path=/Users/user/source/demo-projects/regular-chromely/CrossPlatDemo/bin/Debug/netcoreapp3.1/osx-x64/locales --log-file=logs\chromely.cef_20200321.log --log-severity=info --resources-dir-path=/Users/user/source/demo-projects/regular-chromely/CrossPlatDemo/bin/Debug/netcoreapp3.1/osx-x64/ --lang=en-US --default-encoding=utf-8 --allow-file-access-from-files --allow-universal-access-from-files --disable-web-security --ignore-certificate-errors
On CefGlue child process launch arguments:
/Users/user/source/demo-projects/regular-chromely/CrossPlatDemo/bin/Debug/netcoreapp3.1/osx-x64/crossplatdemo --type=renderer --no-sandbox --log-file=logs\chromely.cef_20200321.log --field-trial-handle=1718379636,5549198414550298470,15611372194352481318,131072 --disable-features=OutOfBlinkCors --lang=en-US --locales-dir-path=/Users/user/source/demo-projects/regular-chromely/CrossPlatDemo/bin/Debug/netcoreapp3.1/osx-x64/locales --log-file=logs\chromely.cef_20200321.log --log-severity=info --resources-dir-path=/Users/user/source/demo-projects/regular-chromely/CrossPlatDemo/bin/Debug/netcoreapp3.1/osx-x64/ --default-encoding=utf-8 --allow-file-access-from-files --allow-universal-access-from-files --disable-web-security --ignore-certificate-errors
2020-03-21 11:27:47.645 [INFO] Running MacOSX chromium 77.0.3865.120
2020-03-21 11:27:47.660 [INFO] Running MacOSX chromium 77.0.3865.120

I assumed a window would pop up? I would appreciate any tips to debug what's going on.
Additional info:
OS: MacOS Mojave 10.14.6
.net: dotnet-core 3.1
BR Merl
Edit: I just tried starting it on Linux and everything worked, restore, build, run -> downloads binaries, window appears.

@merl111 if that was the first time you are running, I will suggest you try it again. I have seen this many times, the CEF binaries downloads sometimes creates race issue with the startup. But once you have the binaries, it is usually smooth.
If this is not the issue try run the application itself on the terminal (should be crossplatdemo).
I also assume you are using the right chromelyconfig.json file. If in doubt, you can delete the file. It will fallback to using the C# default configured.

I have tried it a few times before, tried again, sadly same result. I tried running the application itself, has the same effect. The config should be the correct one, since I copied the osx cfg from the config directory, nevertheless, I removed the config, to with the fallback one, but still no change.

When you say start successfully, meaning it is working now?
Possibly you share a screenshot of what pop ups?
Unless there are security issues, it will be good to know more of what is going on. From your logs CEF itself seems to be running successful. It is likely to do with Cocoa API or some OS security.

repo: chromelyapps/demo-projects


text:
add checksum for metanode snapshoting and add 2 config about it

What this PR does / why we need it:
meatanode: add a checksum file for each snapshot file. forward compatible and support fallback
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #993
Special notes for your reviewer:
Taking into account the forward compatibility of the snapshot file, we only create a new "checksum file" for each snapshot, instead of adding a checksum at the end of the snapshot file. For example, the resulting file-tree of snapshot dir will be :
.
├── .checksum.apply
├── .checksum.dentry
├── .checksum.extend
├── .checksum.inode
├── .checksum.multipart
├── .sign
├── apply
├── dentry
├── extend
├── inode
└── multipart

Release note:

add configure "checksumFunc" for meta node：the value could be crc32|crc64|md5|sha1|sha256|sha512 (No case limit)
add configure "ignoreChecksumError" to neglect checksum not match error. (Once if the data is abnormal)

We have tested and verified the following in the test environment as above:

The correctness of cheksum logic.
Forward compatibility of snapshot file format.
Seamless fallback (only need to fallback binary).

repo: chubaofs/chubaofs


text:
Query 24hr dusk/dawn in JSON format

I'm building a

"sun sets in X minutes / at XX:XX"
"it will be dark in y minutes / at YY:YY"
status bar entry.

For this i need the advanced astronomy data from v2
I'm using JSON as the format which doesn't have dusk and dawn, just sunset and sunrise.
And, those fields are in AM/PM format.
Is there a way to get 24hr dusk and dawn info in JSON format?
I haven't found it in the docs yet.

@alexd2580 Sascha hi! Maybe you could use the one-line output format instead?
$ curl wttr.in/Munich?format="%C+\nFeels+like:+%f+\nActually+is:+%t+\nSunrise:+%S+\nSunset:+%s\n"
Sunny
Feels like: +16°C
Actually is: +16°C
Sunrise: 06:57:44
Sunset: 16:56:08

If this is still relevant - technically yes, but no.
My conflict here is between:

Using just one json query for all the data that i need: Temp / Sunrise / Sunset / WeatherDesc / WeatherCode
and having to parse AM/PM into 24hr format

Using two queries: Astronomical data in 24hr format + Other params via regular JSON
I can't use only the custom format query, because the weather-code can't be selected in custom format


text:
updated user_service signals.py file

hello bro! cool project you're working on.
I was testing the app when I bumped into the signals post-save functionality in the user_service app. The "not" in the conditional statement conflicted with the real intentions of the application by flipping the value of the .is_instructor field. so I took it off.

Hey man, thanks for the observation. I looked at it again and you are right. Whilst the code is technically correct, it didn't state a clear intention. I am going to merge your PR.

authors: chukaibejih devsylva


text:
add BAZEL build

add configuration to make it possible to build lib with BAZEL

Add me to this one, please. I want to take a look how to use bazel with this project.
At least, we can try the basic first, only build the library.

authors: cieslarmichal uilianries

repo: cieslarmichal/faker-cxx


text:
CI: port forwarding super flaky on AKS

kubectl port-forward to hubble relay frequently dies while running connectivity tests on AKS.
Error: Unable to port forward: unable to execute "kubectl port-forward -n kube-system svc/hubble-relay --address 127.0.0.1 4245:80": exit status 1
....❌ Unable to execute "kubectl port-forward -n kube-system svc/hubble-relay --address 127.0.0.1 4245:80":
 Forwarding from 127.0.0.1:4245 -> 4245
Handling connection for 4245
error: lost connection to pod

this error rarely happens on GKE or EKS. i'm disabling flow validation on AKS until we fix this issue 😞
ci failures:

https://github.com/cilium/cilium-cli/actions/runs/9687204699/job/26731315565#step:12:1043

This could be related to https://github.com/cilium/cilium/issues/33145. It might be that we need to increase the timeout between relay and hubble, and/or improve the health checking of hubble/relay. I'm hypothesizing that in some situations, we port-forward to relay, but hubble becomes unavailable, which causes relay to fail its health check, which breaks the port-forward.

authors: chancez michi-covalent

repo: cilium/cilium-cli


text:
adds custom mount cmd for k3d

As k3s images - which k3d rely on - are based on busybox and container runtime is CRI-O, so:

raw commands doesn't work, there for mount went /bin/busybox mount
the second command mount --make-shared /sys/fs/bpf is the result of an error message that was stating that this mount point was not shared (got the command from here).

Thanks for your contribution!
Could you please extend your commit message explaining why the change is needed.

Hello there @brb, my pleasure to contribute! Just updated the PR message and also signed-off the commit.

Hi @vniche

raw commands doesn't work, there for mount went /bin/busybox mount

We've removed the dependency on having mount installed on the underlying distro in Cilium OSS daemonset yaml [1]. I'll be making similar changes to the cilium-cli crafted yaml.

the second command mount --make-shared /sys/fs/bpf is the result of an error message that was stating that this mount point was not shared (got the command from here).

See this commit on cilium repo that uses bidirectional mount in lieu of the running the mount command to mount BPF fs - https://github.com/cilium/cilium/pull/16656. /cc @aanm
[1] https://github.com/cilium/cilium/pull/16815/commits/c11ca032e1d60ac2f927462490acc49830d78bcb

Considering the @aditighag comment above, marking the PR as draft.

I don't mind if this gets closed to help on cleaning of open PRs, no use but reference for a workaround until the actual is merged.

authors: aditighag brb vniche


text:
Update the date in the blog when the new sidecar data was added

Also two links got messed up in the last PR. Have fixed them as well.

@xmulligan @liquidat


text:
Fail to pull docker.io/cilium/startup-script using podman/cri-o/skopeo

Bug report

General Information

Cilium version: master
Orchestration system version in use: none

How to reproduce the issue
Detected whilst installing cilium + hubble using the docs on a k8s 1.18 running with cri-o. But in fact the problem has nothing to do with k8s, but with cri-o/podman/skopeo suite not being able to pull the startup-script container

Try to pull docker.io/cilium/startup-script using podman:

$ podman pull docker.io/cilium/startup-script:af2a99046eca96c0138551393b21a5c044c7fe79
Trying to pull docker.io/cilium/startup-script:af2a99046eca96c0138551393b21a5c044c7fe79...
  unsupported docker v2s2 media type: "application/vnd.oci.image.layer.v1.tar+gzip"
Error: error pulling image "docker.io/cilium/startup-script:af2a99046eca96c0138551393b21a5c044c7fe79": unable to pull docker.io/cilium/startup-script:af2a99046eca96c0138551393b21a5c044c7fe79: unable to pull image: Error initializing image from source docker://cilium/startup-script:af2a99046eca96c0138551393b21a5c044c7fe79: unsupported docker v2s2 media type: "application/vnd.oci.image.layer.v1.tar+gzip"

Kindly, @mtrmac pointed out at one possible cause could be that the manifest  seems to mix schema2 and OCI types:
skopeo inspect --raw docker://docker.io/cilium/startup-script@sha256:e133ee31652634c899083c36978289fa615e73abde90237b4f9768c6e5731dd3
{
  "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
  "schemaVersion": 2,
  "config": {
   "mediaType": "application/vnd.docker.container.image.v1+json",
   "digest": "sha256:3aaedd2a2ed6d6283e59d65006d1489c3559ad907ddca43fb52967ffbf79b2b5",
   "size": 664
  },
  "layers": [
   {
     "mediaType": "application/vnd.oci.image.layer.v1.tar+gzip",
     "digest": "sha256:2043e810dacbb87950b0f851bc40a4c95dcabd28c12f0d3bcaf1c45aaf6d2ed3",
     "size": 5250766
   }
  ]
}

@amorenoz thank you for opening the GH issue. Can you try podpam pull docker.io/cilium/cilium-dev:v1.9.0-rc0?
@mtrmac does this means that podman does not support images build with docker buildx? https://github.com/cilium/image-tools/blob/master/scripts/build-image.sh#L130

@aanm, cilium-dev:v1.9.0-rc0 works fine.
Following the initial hypothesis that suggests that the problem may be related to the mixed mediatypes, I see a strong correlation when looking at all the available startup-scrip images:
Image inspection script: https://gist.github.com/amorenoz/9776cf139e2f112177cc522a508b5c8f
Tag: 2de58e53a7060593c91d0655b337a57f06bf5d66
Iterating over nested manifests:
Media types of manifest at docker://cilium/startup-script@sha256:1b28adb6bbc81250e420ada632d53942b754bc43d14c710c251ed2f6f4bba948
Manifest MediaType application/vnd.docker.container.image.v1+json
Layers:
    Layer: sha256:9a2474c4081001ca048fd5ef0229f7db69e16518315c268e8699bcbcc55b251d MediaType = application/vnd.oci.image.layer.v1.tar+gzip
Media types of manifest at docker://cilium/startup-script@sha256:fce5ef936f4b323234152efa278a3004d38a088de4c830b9f1a24e39da536bdf
Manifest MediaType application/vnd.docker.container.image.v1+json
Layers:
    Layer: sha256:b5c12a9e76b67e7641a754c1f8b05107b2059a442bc73209fe91b84c0fe6257d MediaType = application/vnd.oci.image.layer.v1.tar+gzip

Can be pulled? No

Tag: 62bfbe88c17778aad7bef9fa57ff9e2d4a9ba0d8
Iterating over nested manifests:
Media types of manifest at docker://cilium/startup-script@sha256:1daf817f34000399fcb5da9a94cb299e2810d2c7a52e51de22ba0d4783b6ce84
Manifest MediaType application/vnd.docker.container.image.v1+json
Layers:
    Layer: sha256:958191dd4f98636293fc4381a84a72d32d66d0829889597cd247fd8dcd0706e5 MediaType = application/vnd.docker.image.rootfs.diff.tar.gzip
    Layer: sha256:4428bbec36060b183447e498441d6f8b8d72136e667e367741e65092f29b31ae MediaType = application/vnd.docker.image.rootfs.diff.tar.gzip
Media types of manifest at docker://cilium/startup-script@sha256:43418fc3f91235bc103d1516f06f89c4e61b801be85edab153c6a42279a4076d
Manifest MediaType application/vnd.docker.container.image.v1+json
Layers:
    Layer: sha256:c9a3864bf69d175a0b1fc7203052660f5e410555a6b5b527e039336a045066c4 MediaType = application/vnd.docker.image.rootfs.diff.tar.gzip
    Layer: sha256:7f3549c550bfa81d8845cdd5ef563d0dc9a04fc325c63ede9f8b68b79edef258 MediaType = application/vnd.docker.image.rootfs.diff.tar.gzip

Can be pulled? Yes

Tag: af2a99046eca96c0138551393b21a5c044c7fe79
Iterating over nested manifests:
Media types of manifest at docker://cilium/startup-script@sha256:e133ee31652634c899083c36978289fa615e73abde90237b4f9768c6e5731dd3
Manifest MediaType application/vnd.docker.container.image.v1+json
Layers:
    Layer: sha256:2043e810dacbb87950b0f851bc40a4c95dcabd28c12f0d3bcaf1c45aaf6d2ed3 MediaType = application/vnd.oci.image.layer.v1.tar+gzip
Media types of manifest at docker://cilium/startup-script@sha256:438c9bbc398fc06cca517c89242a0aca688f53d490d0b30941b9a4036952307c
Manifest MediaType application/vnd.docker.container.image.v1+json
Layers:
    Layer: sha256:d3b0893334d1dbc9f1643af909a9129775ba8088f0b6cee0e365470c9fe8c0d6 MediaType = application/vnd.oci.image.layer.v1.tar+gzip

Can be pulled? No

Tag: pr-registry-move-to-nodes-eks
plain manifest
Media types of manifest at docker://cilium/startup-script:pr-registry-move-to-nodes-eks
Manifest MediaType application/vnd.docker.container.image.v1+json
Layers:
    Layer: sha256:89d9c30c1d48bac627e5c6cb0d1ed1eec28e7dbdfbcc04712e4c79c0f83faf17 MediaType = application/vnd.docker.image.rootfs.diff.tar.gzip
    Layer: sha256:292f84b1ac1dd864d3c908a355141fba745e21957fe024bc1b0f229602cd6cda MediaType = application/vnd.docker.image.rootfs.diff.tar.gzip
    Layer: sha256:68e6d981d2af799f4621f49e2ce5ce569e09655073fe424f1a212f1060a58c77 MediaType = application/vnd.docker.image.rootfs.diff.tar.gzip

Can be pulled? Yes

Tag: v1
plain manifest
Media types of manifest at docker://cilium/startup-script:v1
Manifest MediaType application/vnd.docker.container.image.v1+json
Layers:
    Layer: sha256:89d9c30c1d48bac627e5c6cb0d1ed1eec28e7dbdfbcc04712e4c79c0f83faf17 MediaType = application/vnd.docker.image.rootfs.diff.tar.gzip
    Layer: sha256:6f7a951811b23e7193dfc9d7f10361e3fb5f35385ba26c3b2f73758087965903 MediaType = application/vnd.docker.image.rootfs.diff.tar.gzip
    Layer: sha256:08bbda82e8703240281275efccbd40aa223ebdc692a53ddd82f552bcbe80076c MediaType = application/vnd.docker.image.rootfs.diff.tar.gzip

Can be pulled? Yes

Tag: v2
plain manifest
Media types of manifest at docker://cilium/startup-script:v2
Manifest MediaType application/vnd.docker.container.image.v1+json
Layers:
    Layer: sha256:89d9c30c1d48bac627e5c6cb0d1ed1eec28e7dbdfbcc04712e4c79c0f83faf17 MediaType = application/vnd.docker.image.rootfs.diff.tar.gzip
    Layer: sha256:f0c3733dbe306df009d59349c757def7a0b1f266beb9c4db863070d0744dba9c MediaType = application/vnd.docker.image.rootfs.diff.tar.gzip
    Layer: sha256:344fdc6cc5b3b7aedde4b321e62701ce65210429beb66305fba3cfe65c0c7006 MediaType = application/vnd.docker.image.rootfs.diff.tar.gzip

Can be pulled? Yes

Tag: v3
plain manifest
Media types of manifest at docker://cilium/startup-script:v3
Manifest MediaType application/vnd.docker.container.image.v1+json
Layers:
    Layer: sha256:e6b0cf9c0882fb079c9d35361d12ff4691f916b6d825061247d1bd0b26d7cf3f MediaType = application/vnd.docker.image.rootfs.diff.tar.gzip
    Layer: sha256:ec786b53c2801aa25a849fc7b7d438b217c30b47d7a0c8669a486804f9b3c541 MediaType = application/vnd.docker.image.rootfs.diff.tar.gzip
    Layer: sha256:7b5bebdcb6322030b920c3e3565ed592ed5d432fc7a3a9d30719a287444c1bf8 MediaType = application/vnd.docker.image.rootfs.diff.tar.gzip

Can be pulled? Yes

@amorenoz thanks for reporting this! I think this is basically the effect of a bug in buildkit (https://github.com/docker/buildx/issues/300) that we've discovered when we were trying to enable mirroring the image to quay as well as Docker Hub. It's been fix in latest version of BuildKit, and we have a work-around for it as well (https://github.com/cilium/image-tools/pull/59).
We believe that most recent tag (i.e. either quay.io/cilium/startup-script:62bfbe88c17778aad7bef9fa57ff9e2d4a9ba0d8  or docker.io/cilium/startup-script:62bfbe88c17778aad7bef9fa57ff9e2d4a9ba0d8) should work just fine, if so we must update the image for 1.9.0 and 1.8.5.

@amorenoz can you confirm if this issue is fixed with the images I mentioned above?

@errordeveloper Yes both docker.io/cilium/startup-script:62bfbe88c17778aad7bef9fa57ff9e2d4a9ba0d8 and quay.io/cilium/startup-script:62bfbe88c17778aad7bef9fa57ff9e2d4a9ba0d8 work fine

authors: aanm amorenoz errordeveloper

repo: cilium/cilium


text:
Cilium agent opens ports in all interfaces (maybe unnecessarily?)

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I've noticed that cilium agent opens several ports on all interfaces, while some ports only listen on localhost.
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.1:9879          0.0.0.0:*               LISTEN      1345831/cilium-agen
tcp        0      0 127.0.0.1:9890          0.0.0.0:*               LISTEN      1345831/cilium-agen
tcp6       0      0 :::4244                 :::*                    LISTEN      1345831/cilium-agen
tcp6       0      0 :::4240                 :::*                    LISTEN      1345831/cilium-agen
tcp6       0      0 :::36195                :::*                    LISTEN      1345831/cilium-agen
tcp6       0      0 :::9962                 :::*                    LISTEN      1345831/cilium-agen
udp6       0      0 :::36195                :::*                                1345831/cilium-agen

I'm trying to secure a cluster where all traffic between nodes goes through a private network, but then Cilium agent is listening on all interfaces. It seems to me that this makes security more difficult to implement. I wasn't able to find documentation about what those ports do, but I would expect them to listen on the interface of the node's InternalIP.
I found that a similar question was asked in Slack, and it was suggested that a new issue should be opened if using a recent version of cilium.
Cilium Version
cilium-cli: v0.12.11 compiled with go1.19.3 on linux/amd64
cilium image (default): v1.12.2
cilium image (stable): v1.12.5
cilium image (running): v1.12.3
Kernel Version
Linux node1 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
1.23
Sysdump
No response
Relevant log output
No response
Anything else?
I've tried using firewall, but setting up an external firewall with cilium is breaking connectivity. It feels like this solution is bound to create many issues
Code of Conduct

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

I have a similar question, does cilium support configure interface or node CIDR to use for pod to pod traffic? Like what Antrea did in this issue https://github.com/antrea-io/antrea/pull/2704

Unassigned myself as #24011 is merged which handles the case for all Envoy proxy ports being bound to all interfaces.
There are still services left on the above mentioned ports which should be looked into but I am probably not the best person to investigate those :)

These are the ports which are still bound to all interfaces. Except the dynamically assigned DNS proxy redirect port - all of them are documented as mentioned by @rolinh
4240 -> Agent Health
4244 -> Hubble Server
9962 -> Agent Prometheus Metrics
36195 -> DNS Proxy redirect port (dynamically assigned - can be double-checked by executing cilium status --all-redirects and checking Proxy Status output from within the Cilium Agent Pod)

@mhofstetter can we open the DNS proxy ones on the local interfaces?

We have addressed the overall concern in this issue and the remaining open ports are

4240 -> Agent Health
4244 -> Hubble Server (uses TLS)
9962 -> Agent Prometheus Metrics

Both Agent Health and Agent Prometheus Metrics are necessary to receive connections from outside of the node so we can't simply open them in the localhost. Pinning them to the node's InternalIP, as proposed in the issue description, is good solution and so, if you want, feel free to open a PR with that solution implemented.
Thank you!

@aanm I like to pick this up if not by anyone else

@tamilmani1989 sure, what do you have in mind?

@aanm as you mentioned in above comment, I'm considering to make Agent Health and Agent Prometheus Metrics to listen on nodeip instead of listening on all interfaces

looked at the code.. can update for agent health but little complicated for Prometheus. Prometheus address and port coming via cilium config and default config is set to :9962.
https://github.com/cilium/cilium/blob/bbdad5d38364ce9d715f57986fa2f11361a326d9/pkg/metrics/registry.go#L38C43-L38C62
I'm not sure if we can override config and change that internally. Let me know if you have any suggestions here.

Does hubble server (4244) requires receiving connections from outside?

Yes.

For prometheus, I tried to update to listen on nodeip here https://github.com/cilium/cilium/blob/d5ee4e70cfa5ea6941633d1cce545a541875b964/pkg/metrics/registry.go#L27C1-L27C1 to
var defaultRegistryConfig = RegistryConfig{
	PrometheusServeAddr: fmt.Sprintf("%s:9962", node.GetCiliumEndpointNodeIP()),
}

and importing node package resulted in cyclic dependency error. any suggesions here?

authors: aanm cortopy meyskens mhofstetter rolinh tamilmani1989 ydp


text:
contrib: Add script to bump stable releases

Add a script to create a new commit bumping the README and github
actions for newly released versions.
Usage:
$ git fetch origin
$ git checkout -b pr/bump-readme-$(date --rfc-3339=date) origin/master
$ ./contrib/release/bump-readme
$ git push
<open PR>

Used to create #10710.

Coverage decreased (-0.01%) to 45.408% when pulling 0323269c204df6c40e867f9fb812c6ed920e4014 on joestringer:submit/bump-release-script into cc023f1a65a3572777cfbe123495605194f48dc6 on cilium:master.

Ah, good point, I was assuming that these are set in the included common/lib scripts and that those settings would propagate out to this script, which I think is true but worth double-checking.
Agree on the docs, question will be whether we move towards retiring the docs for generating releases and roll this into the github issue template for releases.
Or for that matter if we just avoid using this script manually and script up a github action to invoke it automatically..

I quickly glanced at the "usage" section of the script and thought that could go in the docs. But it seems simple enough after a second look, so probably not worth doing. Eventually a GitHub action is probably the most fitting for this kind of thing. :+1:

@aanm Good to go for me.

Moved, and updated the issue template for releases.

authors: christarazi coveralls joestringer


text:
v1.8 backports 2020-06-18

#12085 -- api/v1: Add observation proto enum (@glibsm)
#12076 -- test: Fix hubble-relay image helm path (@jrajahalme)
#12088 -- doc: Misc fixups for Transparent Encryption GSG (@christarazi)
#12101 -- daemon: fix panic when starting Cilium (@aanm)
#12121 -- bpf: Use nproc --all for NR_CPUS (@gandro)
#12090 -- test: Fix typo (@jrajahalme)
#12114 -- Add Hubble store getter to gain access to k8s data store. (@lzang)
#12106 -- Use right CCNP validation (@aanm)
#12099 -- test: fix cli flags handling (@nebril)
#11905 -- test: Skip Istio test if Ginkgo runs on unsupported runtime. (@jrajahalme)
#12109 -- test: Download correct cilium-istioctl for the executing OS. (@jrajahalme)
#12089 -- Ginkgo: Simplify all --focus regexes (@jrajahalme)
#12110 -- test: Add generated files to .gitignore, avoid pulling stale images. (@jrajahalme)
#12126 -- contrib: Misc. fixups for k8s-cilium-exec.sh script (@christarazi)
#11979 -- 1.8 documentation updates: Concepts & menu structure (@tgraf)
#11969 -- test: Set devices and enable host firewall in kube-proxy CI (@pchaigno)
#12143 -- k8s/watchers: fix missing missing CNP/CCNP updates (@aanm)
#12150 -- docs: NodePort XDP on Azure (@gandro)
#10899 -- operator: Wait for CRDs before running informers (@mrostecki)
#12156 -- docs: NodePort XDP on AWS (@borkmann)
#12157 -- docs: fix line-break in parsed-literal instance (@borkmann)
#12148 -- docs: simplify one of the steps in GKE guide (@errordeveloper)
#12139 -- helm: Remove affinity from cilium-etcd-operator (@brb)
#12149 -- doc: Specify CILIUM_NAMESPACE for Hubble installation instruction (@michi-covalent)
#12097 -- doc: Ensure ConfigMap remains compatible across 1.7 -> 1.8 upgrade (@tgraf)
#12146 -- pkg/option: disable K8sEventHandover if Cilium is running without KVStore (@aanm)
#12172 -- docs: mention disabling of lro on hv_netvsc (@borkmann)

Once this PR is merged, you can update the PR labels via:
$ for pr in 12085 12076 12088 12101 12121 12090 12114 12106 12099 11905 12109 12089 12110 12126 11979 11969 12143 12150 10899 12156 12157 12148 12139 12149 12097 12146 12172; do contrib/backporting/set-labels.py $pr done 1.8; done

Added next batch into this branch:

#12164 -- Tidy & expand policy docs (@joestringer)
#12166 -- daemon: Warn when policy audit mode is enabled (@joestringer)
#12108 -- docs: Improve consistency in Azure docs (@errordeveloper)
#12033 -- helm: Clean up the hubble-relay DNS name in the UI chart (@michi-covalent)
#12174 -- Fix commands in EKS kube-proxy free GSG (@tklauser)
#12171 -- pkg/k8s: ignore status field in CNP DeepEqual (@aanm)
#12155 -- doc: add Networking and security observability with Hubble guide (@michi-covalent)
#12151 -- cilium/charts: set system-{node,cluster}-critical priorityClass for k8s >= 1.17 (@aanm)

Once this PR is merged, you can update the PR labels via:
$ for pr in 12164 12166 12108 12033 12174 12171 12155 12151; do contrib/backporting/set-labels.py $pr done 1.8; done

test-backport-1.8

test-backport-1.8

test-backport-1.8

bookinfo flake on 4.19, rerunning

retest-4.19

@borkmann there's no point in rerunning the CI without https://github.com/cilium/cilium/pull/12171

test-me-please

test-backport-1.8

The 4.19 still has the single bookinfo test fail, as discussed with @aanm and @joestringer it should not block the PR and the fix is coming in the next batch here https://github.com/cilium/cilium/pull/12190 . Once Cilium-PR-Ginkgo-Tests-K8s is done & green, we can merge.

authors: aanm borkmann jrajahalme


text:
pkg/azure: fix potential deadlocks

Read per commit, this fixes some potential deadlocks found
Fixes #13262
Fix 1 potential deadlock in Azure IPAM and 1 other in ENI and Azure IPAM

test-me-please


text:
doc: getting started minor fixes

See patches.

Can you please fix the typos in your commit descriptions reported by checkpatch?

@qmonnet @michi-covalent marking this PR as ready-to-merge as it doesn't need a full CI run (doc only updates).

Third commit can now be removed.

@kaworu What's the status on this? Looks ready to merge?

@kaworu What's the status on this? Looks ready to merge?

Yes I think so, marking as ready-to-merge since it this PR doesn't need a CI run (doc only changes).

authors: kaworu qmonnet


text:
test: Extend validateCiliumSvc to consider all cluster IPs

Previously, the validateCiliumSvc(), which checks whether "cilium
service list" is in sync with "kubectl get svc", did not consider all
cluster IPs. It was only comparing against ".spec.ClusterIP", and did
not compare against ".spec.ClusterIPs" which can store a ClusterIP per
family when the DualStack is on.
The limitation was obvious when trying to backport the recent
K8sServices suite refactoring to the v1.11. The CI was failing with:
Could not find Cilium service with ip fd03::e44e in k8s

Further investigation showed, that the svc IP addr was in
".spec.ClusterIPs", but not in ".spec.ClusterIP".

/test

Closing, as we already have the check in the main branch. The v1.11 is failing, because https://github.com/cilium/cilium/pull/18184/commits/cc10609d8c1b824479d26a7dbad17069ad64bec3 has not been backported.


text:
v1.12 Backports 2024-01-10

[x] #29310 (@julianwiedmann)
[ ] #29971 (@renovate[bot])

Once this PR is merged, a GitHub action will update the labels of these PRs:
 29310 29971

/test-backport-1.12


text:
Bugtool: Added more debugging commands

Added cilium endpoint list and service list to know that there is
no difference with BPF maps.
Added Cilium Network Policies and Network Policies in Kubernetes
output.

Signed-off-by: Eloy Coto eloy.coto@gmail.com

test-me-please


text:
Ingress/Gateway API: merge Envoy listeners for HTTP(S) and TLS passthrough

Currently, the translation from Ingress controller & Gateway API resources into the corresponding CiliumEnvoyConfig creates two Envoy listeners for TLS passthrough (Ingress annotation or GW-API TLSRoute) and HTTP(S) related functionality.

TLS Passthrough implemented with Envoy TCPProxy network filter
HTTP(S) implemented with Envoy HCM network filter

This works fine for Gateway API and Dedicated Ingresses where the two use-cases are never combined into the same CiliumEnvoyConfig - but leads to problems with Shared Ingresses.
Problem 1: Listener name clash
The two listeners have the same name listener - hence only one of them ends up in the configuration (in most of the cases the TLS Passthrough one which appears later in the configuration).
Problem 2: TPROXY redirection to different listeners with same frontend service port
After solving the name clash, there's still an issue with TLS Passthrough and HTTPS using the same "frontend" port 443 (or the corresponding NodePort) on the Ingress Service that is handled by different Envoy listeners. The current implementation (based on TPROXY) is not able to conditionally (HTTPS or TLS Passthrough) forward traffic to one of these two Listeners.
Therefore, this PR merges the two functionalities within the same Envoy listener by using different filterchains and filterchain-matches based on the servernames (SNI).
Fixes: https://github.com/cilium/cilium/issues/31242
Related to: https://github.com/cilium/cilium/pull/30840

/ci-ingress

/ci-gateway-api

/ci-ingress

/ci-gateway-api

/test

/test

/test

/test

rebased to main to resolve conflicts in cmd-ref-docs

Do we need to worry about removing existing fields? Were these fields present in a released version?

Do we need to worry about removing existing fields? Were these fields present in a released version?

@squeed No, these Helm values (and annotations) were added with the PR https://github.com/cilium/cilium/pull/30840 which lands in v1.16. Therefore they weren't released except for the pre-releases (https://github.com/cilium/cilium/releases/tag/v1.16.0-pre.0)

Improvements

naming of annotation & helm values after merging them (including listener in name) (annotation: ingress.cilium.io/host-listener-port / helm: ingressController.hostNetwork.sharedListenerPort)
explicit sharedListenerPort of 80 (in addition to implicit one)

rebased to main to fix issues with build commit check (introduced via changes in clangd: https://github.com/cilium/cilium/pull/31754)
contrib/scripts/builder.sh make build -j 4: 1: contrib/scripts/builder.sh: not found

:crossed_fingers:

authors: mhofstetter squeed


text:
RFC: Test add custom errors on helpers

Added a new helper error message, that has a callback function that can be called when the Ginkgo trigger an error, so the errors dump to users are more powerful.

This change is

test-me-please

test-me-please


text:
Fix Makefile coverpkg when using TESTPKGS=...

The coverpkg parameter was not passing the correct value to go test when
the user specified TESTPKGS, which meant that if developers wanted to
figure out the coverage of a particular package, they'd either have to
run the full set of unit tests or figure out the correct COVERPKG
argument and pass that into "make unit-tests".
Fix it so that COVERPKG inherits the correct package names from TESTPKGS.

This change is

Coverage remained the same at ?% when pulling 65bf1e165fe735edca8fe4d57bd548e9919d39ce on joestringer:submit/fix-coverpkg into 47f24484ec775edadd54c8febe854cd6542792e1 on cilium:master.

Bah, broke the "normal" case apparently, given coveralls' summary there. Back to the drawing board I guess.

test-me-please

test-me-please

Only tests that failed are Istio tests, doesn't make any sense why this PR would cause those to fail:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/13089/
(#8346)

authors: coveralls joestringer


text:
⚠ St. Lawrence Global Observatory CKAN Sitemap has degraded performance

In 55e05be, St. Lawrence Global Observatory CKAN Sitemap (https://catalogue.ogsl.ca/sitemap/sitemap-1.xml) experienced degraded performance:

HTTP code: 200
Response time: 5754 ms

Resolved: St. Lawrence Global Observatory CKAN Sitemap performance has improved in 4bbcd09 after 8 minutes.

repo: cioos-siooc/cwatch-upptime


text:
⚠ Cioos National CKAN has degraded performance

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

HTTP code: 200
Response time: 9553 ms

Resolved: Cioos National CKAN performance has improved in 15d692b after 5 minutes.


text:
🛑 Cioos Pacific CKAN Sitemap is down

In aaa42f6, Cioos Pacific CKAN Sitemap (https://catalogue.cioospacific.ca/sitemap/sitemap-1.xml) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cioos Pacific CKAN Sitemap is back up in 7065133 after 39 minutes.


text:
🛑 Cioos Atlantic CKAN is down

In b83c4bd, Cioos Atlantic CKAN (https://catalogue.cioosatlantic.ca/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cioos Atlantic CKAN is back up in 2eb60c1 after 10 minutes.


text:
Make Float decoding match java.lang.Float.parseFloat

Fixes #1063.

Codecov Report

Merging #1160 into master will increase coverage by 0.15%.
The diff coverage is 80%.

@@            Coverage Diff             @@
##           master    #1160      +/-   ##
==========================================
+ Coverage   86.45%   86.61%   +0.15%
==========================================
  Files          85       85
  Lines        2821     2832      +11
  Branches      108      112       +4
==========================================
+ Hits         2439     2453      +14
+ Misses        382      379       -3

Impacted Files
Coverage Δ

.../core/shared/src/main/scala/io/circe/Decoder.scala
86.93% <100%> (+0.5%)
:arrow_up:

...re/shared/src/main/scala/io/circe/JsonNumber.scala
96.51% <100%> (+0.26%)
:arrow_up:

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
87.71% <40%> (-1.44%)
:arrow_down:

...les/core/shared/src/main/scala/io/circe/Json.scala
80.36% <0%> (+0.61%)
:arrow_up:

...re/shared/src/main/scala/io/circe/KeyDecoder.scala
97.29% <0%> (+2.7%)
:arrow_up:

...rc/main/scala/io/circe/shapes/SizedInstances.scala
92.85% <0%> (+14.28%)
: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 a6b59d8...daa141f. Read the comment docs.

authors: codecov-io travisbrown

repo: circe/circe


text:
Sample Report Output

Is it possible to provide a sample output of the report generated by this tool?

+1

+1

M365BaselineConformance_2022_11_01_08_32_30.zip
Thanks for the suggestion. Attached is a sample report from a test tenant (so most controls fail).
We plan to add this to the repo in future releases.

Re-opening until we merge next release

Closed in #24

authors: PeanutTheAdmin anthonynogales ethanb-cisa ramarasuriya

repo: cisagov/ScubaGear


text:
Implement functional testing

🐛 Summary
Once #8 is merged a large number of the tests defined in this repository will be disabled. This is due to the fact that they were written based on working out of a running Docker orchestration and not stand-alone package testing. Given how our GitHub Actions testing is written this is not readily implementable for this project. It is also desirable to have stand-alone testing for the Python package if at possible.
Expected behavior
Using our GitHub Actions workflow or running pytest locally results in all tests that are defined passing.
implementation notes
When testing trying to get them running as-is I first added pyfakefs to insert an appropriate configuration file at the default location (/run/secrets/admiral.yml). Once I was able to do that I then ran into the problem that it needs a running redis server.

This will be easier to tackle once all the various components are split up into their respective repositories. See https://github.com/cisagov/admiral-docker/pull/5 and https://github.com/cisagov/ansible-role-admiral/pull/3.

authors: king-alexander mcdonnnj

repo: cisagov/admiral


text:
Freshly Built dashboard AMI does not Provide Functional Dashboard

🐛 Summary
I built and deployed a fresh dashboard AMI from cisagov/cyhy_amis in my development environment. When I attempted to access the dashboard from the environment I was greeted with the following page:

Upon investigating I found that a Node.js error is preventing the ncats-webui Docker image from running correctly.
To reproduce
Steps to reproduce the behavior:
Error was a result of building and deploying a new dashboard AMI. This resulted in a fresh, local Docker image being created for this project. After confirming the error I attempted:

docker-compose down
docker-compose up

Same result observed, and again after rebuilding the Docker image.
Expected behavior
Website is accessible and provides a functional dashboard.
Any helpful log output or screenshots
$ docker-compose logs
Attaching to ncats-webui_web-server_1
web-server_1  | Starting up development server...
web-server_1  | cp -n src/config/config.sample.json src/config/config.json || :
web-server_1  | find src -type f -print0 | sort -z | xargs -0 shasum | shasum > src/config/app.version
web-server_1  | ** NG Live Development Server is listening on 0.0.0.0:4200, open your browser on http://localhost:4200 **
web-server_1  | 19 03 2021 20:17:56.646:WARN [karma]: No captured browser, open http://localhost:9876/
web-server_1  | 19 03 2021 20:17:56.663:INFO [karma]: Karma v1.4.1 server started at http://0.0.0.0:9876/
web-server_1  65% building modules 909/981 modules 72 active ...rc/app/node_modules/contra/emitter.js 65% building modules 568/611 modules 43 active ...srcwebpack: wait until bundle finished: /
 95% emitting[../../../../../src recursive \.spec\.ts$] ./src \.spec\.ts$ 1.68 kB {main} [built]                                web-server_1  | [../../../../../src/app/fema/fema.component.spec.ts] ./src/app/fema/fema.component.spec.ts 740 bytes {main} [optional] [built]
web-server_1  | [../../../../../src/app/hiringdashboard/hiringdashboard.component.spec.ts] ./src/app/hiringdashboard/hiringdashboard.component.spec.ts 882 bytes {main} [optional] [built]
web-server_1  | [../../../../../src/polyfills.ts] ./src/polyfills.ts 681 bytes {polyfills} [built]
web-server_1  | [../../../../../src/test.ts] ./src/test.ts 861 bytes {main} [built]
web-server_1  | [../../../../zone.js/dist/async-test.js] ./node_modules/zone.js/dist/async-test.js 10.5 kB {vendor} [built]
web-server_1  | [../../../../zone.js/dist/fake-async-test.js] ./node_modules/zone.js/dist/fake-async-test.js 30.1 kB {vendor} [built]
web-server_1  | [../../../../zone.js/dist/jasmine-patch.js] ./node_modules/zone.js/dist/jasmine-patch.js 12.3 kB {vendor} [built]
web-server_1  | [../../../../zone.js/dist/long-stack-trace-zone.js] ./node_modules/zone.js/dist/long-stack-trace-zone.js 6.18 kB {vendor} [built]
web-server_1  | [../../../../zone.js/dist/proxy.js] ./node_modules/zone.js/dist/proxy.js 8.18 kB {vendor} [built]
web-server_1  |    [1] multi ./src/polyfills.ts 28 bytes {polyfills} [built]
web-server_1  | [../../../../zone.js/dist/sync-test.js] ./node_modules/zone.js/dist/sync-test.js 1.42 kB {vendor} [built]
web-server_1  | [../../../core/@angular/core.es5.js] ./node_modules/@angular/core/@angular/core.es5.js 492 kB {vendor} [built]
web-server_1  | [../../../core/@angular/core/testing.es5.js] ./node_modules/@angular/core/@angular/core/testing.es5.js 40.6 kB {vendor} [built]
web-server_1  | [../../../platform-browser-dynamic/@angular/platform-browser-dynamic/testing.es5.js] ./node_modules/@angular/platform-browser-dynamic/@angular/platform-browser-dynamic/testing.es5.js 3.61 kB {vendor} [built]
web-server_1  |     + 908 hidden modules
web-server_1  |
web-server_1  | WARNING in ./node_modules/colorbrewer/index.js
web-server_1  | 3:24-31 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
web-server_1  |
web-server_1  | ERROR in /usr/src/app/node_modules/@types/node/index.d.ts (20,1): Invalid 'reference' directive syntax.
web-server_1  | Date: 2021-03-19T20:18:10.521Z
web-server_1  | Hash: 27d9527686207fea37d6
web-server_1  | Time: 19095ms
web-server_1  | chunk {inline} inline.bundle.js, inline.bundle.js.map (inline) 5.83 kB [entry] [rendered]
web-server_1  | chunk {main} main.bundle.js, main.bundle.js.map (main) 358 kB {vendor} [initial] [rendered]
web-server_1  | chunk {polyfills} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 367 kB {inline} [initial] [rendered]
web-server_1  | chunk {styles} styles.bundle.js, styles.bundle.js.map (styles) 11.3 kB {inline} [initial] [rendered]
web-server_1  | chunk {vendor} vendor.bundle.js, vendor.bundle.js.map (vendor) 4.69 MB [initial] [rendered]
web-server_1  |
web-server_1  | WARNING in ./node_modules/colorbrewer/index.js
web-server_1  | 3:24-31 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
web-server_1  |     at CommonJsRequireContextDependency.getWarnings (/usr/src/app/node_modules/webpack/lib/dependencies/CommonJsRequireContextDependency.js:27:4)
web-server_1  |     at Compilation.reportDependencyErrorsAndWarnings (/usr/src/app/node_modules/webpack/lib/Compilation.js:677:24)
web-server_1  |     at Compilation.finish (/usr/src/app/node_modules/webpack/lib/Compilation.js:535:9)
web-server_1  |     at applyPluginsParallel.err (/usr/src/app/node_modules/webpack/lib/Compiler.js:512:17)
web-server_1  |     at /usr/src/app/node_modules/tapable/lib/Tapable.js:289:11
web-server_1  |     at _addModuleChain (/usr/src/app/node_modules/webpack/lib/Compilation.js:481:11)
web-server_1  |     at processModuleDependencies.err (/usr/src/app/node_modules/webpack/lib/Compilation.js:452:13)
web-server_1  |     at _combinedTickCallback (internal/process/next_tick.js:73:7)
web-server_1  |     at process._tickCallback (internal/process/next_tick.js:104:9)
web
web-server_1  | webpack: Compiled with warnings.

diff of the results of npm list in my production environment's image vs the prod-a image:
16,17c16,17
< | | | `-- electron-to-chromium@1.3.692
< | | +-- caniuse-db@1.0.30001203
---
> | | | `-- electron-to-chromium@1.3.633
> | | +-- caniuse-db@1.0.30001171
174,175c174,175
< | | | `-- renderkid@2.0.5
< | | |   +-- css-select@2.1.0
---
> | | | `-- renderkid@2.0.4
> | | |   +-- css-select@1.2.0
177,178c177,178
< | | |   | +-- css-what@3.4.2
< | | |   | +-- domutils@1.7.0
---
> | | |   | +-- css-what@2.1.3
> | | |   | +-- domutils@1.5.1
181c181
< | | |   | |   `-- entities@2.2.0
---
> | | |   | |   `-- entities@2.1.0
259c259
< | +-- lodash@4.17.21
---
> | +-- lodash@4.17.20
351c351
< | | | | | `-- uri-js@4.4.1
---
> | | | | | `-- uri-js@4.4.0
424c424
< | +-- resolve@1.20.0
---
> | +-- resolve@1.19.0
513c513
< | | | | | +-- bn.js@5.2.0
---
> | | | | | +-- bn.js@5.1.3
515,516c515,516
< | | | | | +-- elliptic@6.5.4
< | | | | | | +-- bn.js@4.12.0
---
> | | | | | +-- elliptic@6.5.3
> | | | | | | +-- bn.js@4.11.9
523c523
< | | | | |     `-- bn.js@4.12.0
---
> | | | | |     `-- bn.js@4.11.9
525c525
< | | | | | `-- bn.js@4.12.0
---
> | | | | | `-- bn.js@4.11.9
534c534
< | | | | | +-- bn.js@4.12.0
---
> | | | | | +-- bn.js@4.11.9
536c536
< | | | | |   `-- bn.js@4.12.0
---
> | | | | |   `-- bn.js@4.11.9
539c539
< | | | | | `-- bn.js@4.12.0
---
> | | | | | `-- bn.js@4.11.9
543c543
< | | | +-- events@3.3.0
---
> | | | +-- events@3.2.0
594c594
< | | | +-- chokidar@3.5.1
---
> | | | +-- chokidar@3.4.3
601,602c601,602
< | | | | +-- UNMET OPTIONAL DEPENDENCY fsevents@~2.3.1
< | | | | +-- glob-parent@5.1.2
---
> | | | | +-- UNMET OPTIONAL DEPENDENCY fsevents@~2.1.2
> | | | | +-- glob-parent@5.1.1
604c604
< | | | | | `-- binary-extensions@2.2.0
---
> | | | | | `-- binary-extensions@2.1.0
663c663
< | |   +-- y18n@3.2.2
---
> | |   +-- y18n@3.2.1
673,674c673,674
< | | | | | `-- call-bind@1.0.2
< | | | | |   `-- get-intrinsic@1.1.1
---
> | | | | | `-- call-bind@1.0.0
> | | | | |   `-- get-intrinsic@1.0.2
676,678c676,678
< | | | | +-- is-regex@1.1.2
< | | | | | `-- has-symbols@1.0.2
< | | | | +-- object-is@1.1.5
---
> | | | | +-- is-regex@1.1.1
> | | | | | `-- has-symbols@1.0.1
> | | | | +-- object-is@1.1.4
681c681,689
< | | | | `-- regexp.prototype.flags@1.3.1
---
> | | | | `-- regexp.prototype.flags@1.3.0
> | | | |   `-- es-abstract@1.17.7
> | | | |     +-- es-to-primitive@1.2.1
> | | | |     | `-- is-symbol@1.0.3
> | | | |     +-- is-callable@1.2.2
> | | | |     +-- object-inspect@1.9.0
> | | | |     +-- object.assign@4.1.2
> | | | |     +-- string.prototype.trimend@1.0.3
> | | | |     `-- string.prototype.trimstart@1.0.3
810c818
< | | | |   +-- http-parser-js@0.5.3
---
> | | | |   +-- http-parser-js@0.5.2
817c825
< | | | `-- url-parse@1.5.1
---
> | | | `-- url-parse@1.4.7
828c836
< | | |   +-- detect-node@2.0.5
---
> | | |   +-- detect-node@2.0.4
855c863
< | |   +-- y18n@3.2.2
---
> | |   +-- y18n@3.2.1
879c887
< +-- @types/socket.io-client@1.4.36
---
> +-- @types/socket.io-client@1.4.34
882c890
< +-- bower@1.8.12
---
> +-- bower@1.8.8
892c900
< +-- colorbrewer@1.4.0
---
> +-- colorbrewer@1.3.0
1060c1068
< | |       `-- type@2.5.0
---
> | |       `-- type@2.1.0
1076c1084
< |   `-- y18n@3.2.2
---
> |   `-- y18n@3.2.1
1223c1231
< |   | | `-- source-map-url@0.4.1
---
> |   | | `-- source-map-url@0.4.0
1270,1271c1278,1283
< | | | |   +-- cli-table@0.3.6
< | | | |   | `-- colors@1.0.3
---
> | | | |   +-- cli-table@0.3.4
> | | | |   | `-- string-width@4.2.0
> | | | |   |   +-- emoji-regex@8.0.0
> | | | |   |   +-- is-fullwidth-code-point@3.0.0
> | | | |   |   `-- strip-ansi@6.0.0
> | | | |   |     `-- ansi-regex@5.0.0
1382c1394
< | +-- graceful-fs@4.2.6
---
> | +-- graceful-fs@4.2.4
1385c1397
< | | +-- follow-redirects@1.13.3
---
> | | +-- follow-redirects@1.13.1
1434c1446
< |   | `-- handlebars@4.7.7
---
> |   | `-- handlebars@4.7.6
1474c1486
< | `-- webdriver-manager@12.1.8
---
> | `-- webdriver-manager@12.1.7
1653,1654c1665,1666
< |   +-- mime-types@2.1.29
< |   | `-- mime-db@1.46.0
---
> |   +-- mime-types@2.1.27
> |   | `-- mime-db@1.44.0

Building locally with colorbrewer pinned to 1.3.0 (version in production) still results in an error:
$ docker-compose logs
Attaching to ncats-webui_web-server_1
web-server_1  | Starting up development server...
web-server_1  | cp -n src/config/config.sample.json src/config/config.json || :
web-server_1  | find src -type f -print0 | sort -z | xargs -0 shasum | shasum > src/config/app.version
web-server_1  | ** NG Live Development Server is listening on 0.0.0.0:4200, open your browser on http://localhost:4200 **
web-server_1  | 29 03 2021 18:35:37.085:WARN [karma]: No captured browser, open http://localhost:9876/
web-server_1  | 29 03 2021 18:35:37.100:INFO [karma]: Karma v1.4.1 server started at http://0.0.0.0:9876/
web-server_1  |  10% building modules 3/3 modules 0 active 10% building modules 0/1 modules 1 active multi /usr/src/app/ 11% building modules 11/13 modules 2 activ 10% building modules 1/2 modules 1 active ...src/index.js!/usr/src/app/src/t 22% building modules 104/105 modules 1 act 21% building modules 98/99 modules 1 active ...es/@angular/core/@angular/cor 21% building modules 98/101 modules 3 active ...ode_modules/webpack/buildin/global.js 22% building modules 105/134 modu 27% building modules 148/301 modules 153 active ...modules/socket.io-client/lib/index.js 45% building modules 294/325 m 29% building modules 159/301 modules 142 active ...modules/socket.io-client/lib/index.js 45% building modules 294/352 m 45% building modules 294/366 modules 72 active ...odules/core-js/modules/_is-integer.js 29% building modules 164/301 mo 30% building modules 169/301 modules 132 active ...modules/socket.io-client/lib/index.js 45% building modules 294/377 m 45% building modules 294/379 modules 85 active ...e-js/modules/_advance-string-index.js 30% building modules 170/301 mo 45% building modules 294/383 modules 89 active ...re-js/modules/_species-constructor.js 30% building modules 172/301 mo 36% building modules 220/301 modules 81 active ...modules/socket.io-client/lib/index.js 46% building modules 307/413 mo 47% building modules 309/413 modules 104 active ...re-js/modules/_array-from-iterable.js 36% building modules 221/301 m 47% building modules 311/413 modules 102 active ...re-js/modules/_array-from-iterable.js 36% building modules 222/301 m 47% building modules 313/413 modules 100 active ...re-js/modules/_array-from-iterable.js 37% building modules 225/301 m 42% building modules 270/301 modules 31 active ...modules/socket.io-client/lib/index.js 48% building modules 324/415 mo 55% building modules 380/415 modules 35 active ...lar/compiler/@angular/compiler.es5.js 43% building modules 276/315 mo 66% building modules 596/630 modules 34 active ...de_modules/rxjs/operators/finalize.js 51% building modules 419/601 mo 54% building modules 601/818 modules 217 active .../app/node_modules/moment/locale/sl.js 55% building modules 459/610 m 53% building modules 601/828 modules 227 active .../app/node_modules/moment/locale/tg.js 55% building modules 461/610 m 52% building modules 602/857 modules 255 active ...odules/rxjs/testing/ColdObservable.js 61% building modules 526/610 m 51% building modules 603/875 modules 272 active ...e_modules/rxjs/observable/interval.js 65% building modules 560/610 m 65% building modules 566/610 modules 44 active ...src/app/node_modules/debug/browser.js 50% building modules 603/890 mo 50% building modules 603/892 modules 289 active ...e_modules/rxjs/operator/bufferTime.js 65% building modules 567/610 m 65% building modules 568/610 modules 42 active ...src/app/node_modules/debug/browser.js 50% building modules 603/894 mo 50% building modules 603/904 modules 301 active ...s/operator/distinctUntilKeyChanged.js 66% building modules 572/610 m 66% building modules 576/610 modules 34 active ...src/app/node_modules/debug/browser.js 49% building modules 603/915 mo 66% building modules 579/610 modules 31 active ...src/app/node_modules/debug/browser.js 49% building modules 603/924 mo 49% building modules 603/927 modules 324 active ...de_modules/rxjs/operator/multicast.js 67% building modules 580/610 m 48% building modules 603/934 modules 331 active ...odules/rxjs/operator/publishReplay.js 67% building modules 584/610 m 48% building modules 603/937 modules 334 active .../node_modules/rxjs/operator/repeat.js 67% building modules 585/610 m 48% building modules 630/975 modules 345 active ...modules/rxjs/operator/windowToggle.js 69% building modules 610/613 m 67% building modules 610/639 modules 29 active ...p/node_modules/rxjs/operators/find.js 49% building modules 634/975 mo 66% building modules 610/653 modules 43 active ...s/rxjs/operators/onErrorResumeNext.js 49% building modules 636/975 mo 51% building modules 673/975 modules 302 active ...modules/rxjs/operator/windowToggle.js 56% building modules 611/793 m 54% building modules 611/818 modules 207 active ...pp/node_modules/rxjs/operator/take.js 51% building modules 675/975 m 54% building modules 611/824 modules 213 active ...modules/rxjs/operator/throttleTime.js 51% building modules 676/975 m 51% building modules 677/975 modules 298 active ...modules/rxjs/operator/windowToggle.js 54% building modules 611/831 m 53% building modules 612/836 modules 224 active .../node_modules/rxjs/operator/zipAll.js 51% building modules 681/975 m 52% building modules 694/975 modules 281 active ...modules/rxjs/operator/windowToggle.js 54% building modules 617/836 m 53% building modules 703/975 modules 272 active ...modules/rxjs/operator/windowToggle.js 54% building modules 624/836 m 56% building modules 646/836 modules 190 active .../node_modules/rxjs/operator/zipAll.js 55% building modules 740/975 m 56% building modules 753/975 modules 222 active ...modules/rxjs/operator/windowToggle.js 57% building modules 656/836 m 57% building modules 769/975 modules 206 active ...modules/rxjs/operator/windowToggle.js 58% building modules 669/836 m 59% building modules 685/836 modules 151 active .../node_modules/rxjs/operator/zipAll.js 58% building modules 786/975 m 58% building modules 793/975 modules 182 active ...modules/rxjs/operator/windowToggle.js 59% building modules 689/836 m 59% building modules 690/836 modules 146 active .../node_modules/rxjs/operator/zipAll.js 58% building modules 794/975 m 59% building modules 695/836 modules 141 active .../node_modules/rxjs/operator/zipAll.js 59% building modules 806/975 m 60% building modules 699/837 modules 138 active ...modules/_array-species-constructor.js 60% building modules 815/975 m 60% building modules 823/975 modules 152 active ...modules/rxjs/operator/windowToggle.js 61% building modules 713/838 m 61% building modules 841/975 modules 134 active ...modules/rxjs/operator/windowToggle.js 61% building modules 720/842 m 62% building modules 853/979 modules 126 active ...xjs/observable/ArrayLikeObservable.js 64% building modules 771/842 m 65% building modules 773/842 modules 69 active ...c/app/node_modules/dragula/dragula.js 62% building modules 854/979 mo 65% building modules 776/842 modules 66 active ...c/app/node_modules/dragula/dragula.js 62% building modules 856/979 mo 62% building modules 861/979 modules 118 active ...xjs/observable/ArrayLikeObservable.js 66% building modules 787/842 m 66% building modules 795/842 modules 47 active ...c/app/node_modules/dragula/dragula.js 62% building modules 864/980 mo 63% building modules 874/980 modules 106 active ...rc/app/node_modules/contra/emitter.js 67% building modules 807/842 m 63% building modules 880/980 modules 100 active ...rc/app/node_modules/contra/emitter.js 68% building modules 815/842 m 64% building modules 888/980 modules 92 active ...rc/app/node_modules/contra/emitter.js 68% building modules 821/842 mo 64% building modules 892/980 modules 88 active ...rc/app/node_modules/contra/emitter.js 68% building modules 826/842 mo 64% building modules 894/980 modules 86 active ...rc/app/node_modules/contra/emitter.js 69% building modules 828/842 mo 69% building modules 840/849 modules 9 active ...src/app/node_modules/indexof/index.js 66% building modules 929/980 mod 68% building modules 955/980 modules 25 active ...rc/app/node_modules/contra/emitter.js 69% building modules 842/854 mo 68% building modules 849/866 modules 17 active ...es/rxjs/observable/DeferObservable.js 69% building modules 974/980 mo 68% building modules 851/876 modules 25 active ...es/rxjs/observable/TimerObservable.js 69% building modules 975/981 mo 68% building modules 975/994 modules 19 active ...es/sockjs-client/lib/utils/browser.js 68% building modules 861/881 mo 69% building modules 883/886 modules 3 active ...modules/engine.io-client/lib/index.js 67% building modules 984/1019 mo 69% building modules 883/888 modules 5 active ...de_modules/crossvent/src/crossvent.js 67% building modules 985/1019 mo 68% building modules 1010/1030 modules 20 active ...node_modules/rxjs/scheduler/Action.js 69% building modules 898/901  67% building modules 1019/1055 modules 36 a 69% building modules 903/904 modules 1 active ...et.io-parser/node_modules/ 68% building modules 1023/1056 modules 33 active .../lib/transport/browser/eventsource.js 69% building modules 905/909  69% building modules 1043/1057 modules 14 a 69% building modules 918/919 modules 1 active ...e.io-client/lib/transports 92% chunk asset [../../../../../src recursive \.spec\.ts$] ./src \.spec\.ts$ 1.68 kB {main} [built]
web-server_1  | [../../../../../src/app/fema/fema.component.spec.ts] ./src/app/fema/fema.component.spec.ts 740 bytes {main} [optional] [built]
web-server_1  | [../../../../../src/app/hiringdashboard/hiringdashboard.component.spec.ts] ./src/app/hiringdashboard/hiringdashboard.component.spec.ts 882 bytes {main} [optional] [built]
web-server_1  | [../../../../../src/polyfills.ts] ./src/polyfills.ts 681 bytes {polyfills} [built]
web-server_1  | [../../../../../src/test.ts] ./src/test.ts 861 bytes {main} [built]
web-server_1  | [../../../../zone.js/dist/async-test.js] ./node_modules/zone.js/dist/async-test.js 10.5 kB {vendor} [built]
web-server_1  | [../../../../zone.js/dist/fake-async-test.js] ./node_modules/zone.js/dist/fake-async-test.js 30.1 kB {vendor} [built]
web-server_1  | [../../../../zone.js/dist/jasmine-patch.js] ./node_modules/zone.js/dist/jasmine-patch.js 12.3 kB {vendor} [built]
web-server_1  | [../../../../zone.js/dist/long-stack-trace-zone.js] ./node_modules/zone.js/dist/long-stack-trace-zone.js 6.18 kB {vendor} [built]
web-server_1  | [../../../../zone.js/dist/proxy.js] ./node_modules/zone.js/dist/proxy.js 8.18 kB {vendor} [built]
web-server_1  |    [1] multi ./src/polyfills.ts 28 bytes {polyfills} [built]
web-server_1  | [../../../../zone.js/dist/sync-test.js] ./node_modules/zone.js/dist/sync-test.js 1.42 kB {vendor} [built]
web-server_1  | [../../../core/@angular/core.es5.js] ./node_modules/@angular/core/@angular/core.es5.js 492 kB {vendor} [built]
web-server_1  | [../../../core/@angular/core/testing.es5.js] ./node_modules/@angular/core/@angular/core/testing.es5.js 40.6 kB {vendor} [built]
web-server_1  | [../../../platform-browser-dynamic/@angular/platform-browser-dynamic/testing.es5.js] ./node_modules/@angular/platform-browser-dynamic/@angular/platform-browser-dynamic/testing.es5.js 3.61 kB {vendor} [built]
web-server_1  |     + 907 hidden modules
web-server_1  |
web-server_1  | ERROR in /usr/src/app/node_modules/@types/node/index.d.ts (20,1): Invalid 'reference' directive syntax.
web-server_1  | Date: 2021-03-29T18:35:51.810Z
web-server_1  | Hash: 4e5989938e044fd0578d
web-server_1  | Time: 19516ms
web-server_1  | chunk {inline} inline.bundle.js, inline.bundle.js.map (inline) 5.83 kB [entry] [rendered]
web-server_1  | chunk {main} main.bundle.js, main.bundle.js.map (main) 357 kB {vendor} [initial] [rendered]
web-server_1  | chunk {polyfills} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 367 kB {inline} [initial] [rendered]
web-server_1  | chunk {styles} styles.bundle.js, styles.bundle.js.map (styles) 11.3 kB {inline} [initial] [rendered]
web-server_1  | chunk {vendor} vendor.bundle.js, vendor.bundle.js.map (vendor) 4.69 MB [initial] [rendered]
web-server_1  |
web-server_1  | WARNING in ./src/app/host-map/host-map.component.ts
web-server_1  | 45:36-52 "export 'RdBu' (imported as 'colorbrewer') was not found in 'colorbrewer'
web-server_1  |     at HarmonyImportSpecifierDependency._getErrors (/usr/src/app/node_modules/webpack/lib/dependencies/HarmonyImportSpecifierDependency.js:65:15)
web-server_1  |     at HarmonyImportSpecifierDependency.getWarnings (/usr/src/app/node_modules/webpack/lib/dependencies/HarmonyImportSpecifierDependency.js:39:15)
web-server_1  |     at Compilation.reportDependencyErrorsAndWarnings (/usr/src/app/node_modules/webpack/lib/Compilation.js:677:24)
web-server_1  |     at Compilation.finish (/usr/src/app/node_modules/webpack/lib/Compilation.js:535:9)
web-server_1  |     at applyPluginsParallel.err (/usr/src/app/node_modules/webpack/lib/Compiler.js:512:17)
web-server_1  |     at /usr/src/app/node_modules/tapable/lib/Tapable.js:289:11
web-server_1  |     at _addModuleChain (/usr/src/app/node_modules/webpack/lib/Compilation.js:481:11)
web-server_1  |     at processModuleDependencies.err (/usr/src/app/node_modules/webpack/lib/Compilation.js:452:13)
web-server_1  |     at _combinedTickCallback (internal/process/next_tick.js:73:7)
web-server_1  |     at process._tickCallback (internal/process/next_tick.js:104:9)

web-server_1  | webpack: Compiled with warnings.

Building and allowing it to pull in the latest version of colorbrewer (1.5.0) results in what appears to be the same error as for 1.3.0:
$ docker-compose logs
Attaching to ncats-webui_web-server_1
web-server_1  | Starting up development server...
web-server_1  | cp -n src/config/config.sample.json src/config/config.json || :
web-server_1  | find src -type f -print0 | sort -z | xargs -0 shasum | shasum > src/config/app.version
web-server_1  | ** NG Live Development Server is listening on 0.0.0.0:4200, open your browser on http://localhost:4200 **
web-server_1  | 29 03 2021 18:40:36.264:WARN [karma]: No captured browser, open http://localhost:9876/
web-server_1  | 29 03 2021 18:40:36.278:INFO [karma]: Karma v1.4.1 server started at http://0.0.0.0:9876/
web-server_1  |  10% building modules 3/3 modules 0 active 10% building modules 0/1 modules 1 active multi /usr/src/app/ 11% building modules 10/12 modules 2 activ 10% building modules 1/2 modules 1 active ...src/index.js!/usr/src/app/src/t 11% building modules 9/11 modules 2 active ...p/src/app/cyhy-update.service.spec.ts 12% building modules 20/23 modules  11% building modules 10/12 modules 2 active .../src/app/src/app/fema.service.spec.ts 12% building modules 21/23 modules 15% building modules 43/86 modules 43 active ...keholders/stakeholders.component.html 16% building modules 55/64 module 22% building modules 105/137 modules 32 active ...-js/modules/es6.string.starts-with.js 21% building modules 97/97 modu 21% building modules 97/98 modules 1 active .../src/app/src/app/utilities/url-lib.ts 22% building modules 105/191 modul 22% building modules 105/217 modules 112 active ...e-js/modules/es6.reflect.construct.js 21% building modules 98/98 mod 22% building modules 105/276 modules 171 act 21% building modules 98/99 modules 1 active ...es/@angular/core/@angular/c 39% building modules 245/284 modules 39 active ...src/app/metrics/metrics.component.css 28% building modules 151/301 mo 39% building modules 246/303 modules 57 active ...pp/node_modules/rxjs/observable/of.js 37% building modules 233/301 mo 39% building modules 246/310 modules 64 active .../node_modules/rxjs/operator/reduce.js 38% building modules 235/301 mo 45% building modules 294/317 modules 23 active ...c/app/node_modules/ansi-html/index.js 45% building modules 294/411 mo 51% building modules 343/415 modules 72 active ...lar/compiler/@angular/compiler.es5.js 48% building modules 317/382 mo 48% building modules 317/391 modules 74 active ...les/core-js/modules/_array-methods.js 51% building modules 346/415 mo 48% building modules 317/394 modules 77 active ...core-js/modules/_array-copy-within.js 51% building modules 347/415 mo 48% building modules 317/396 modules 79 active ...odules/core-js/modules/_array-fill.js 51% building modules 348/415 mo 52% building modules 353/415 modules 62 active ...lar/compiler/@angular/compiler.es5.js 48% building modules 317/407 mo 56% building modules 384/415 modules 31 active ...lar/compiler/@angular/compiler.es5.js 48% building modules 320/443 mo 48% building modules 320/454 modules 134 active ...s/rxjs/add/observable/bindCallback.js 58% building modules 404/415 m 59% building modules 415/421 modules 6 active ...c/app/node_modules/rxjs/Subscriber.js 49% building modules 603/921 mod 49% building modules 603/923 modules 320 active ...app/node_modules/rxjs/operator/min.js 59% building modules 415/423 m 49% building modules 603/925 modules 322 active ...de_modules/rxjs/operator/observeOn.js 59% building modules 415/425 m 59% building modules 415/426 modules 11 active .../rxjs/util/ArgumentOutOfRangeError.js 49% building modules 603/926 mo 48% building modules 603/949 modules 346 active ...de_modules/rxjs/operator/startWith.js 59% building modules 415/444 m 48% building modules 603/951 modules 348 active .../node_modules/rxjs/operator/switch.js 59% building modules 415/445 m 59% building modules 415/447 modules 32 active ..._modules/rxjs/operators/catchError.js 47% building modules 603/953 mo 47% building modules 603/955 modules 352 active ...ode_modules/rxjs/operator/takeLast.js 59% building modules 415/449 m 53% building modules 415/573 modules 158 active ...modules/rxjs/add/operator/takeLast.js 47% building modules 606/975 m 47% building modules 607/975 modules 368 active ...de_modules/socket.io-client/lib/on.js 52% building modules 415/585 m 52% building modules 419/593 modules 174 active ...agula/components/dragula.directive.js 48% building modules 627/975 m 51% building modules 419/605 modules 186 active ...e-js/modules/_array-species-create.js 48% building modules 629/975 m 52% building modules 428/609 modules 181 active ...dules/core-js/modules/es6.weak-map.js 49% building modules 648/975 m 52% building modules 429/609 modules 180 active ...dules/core-js/modules/es6.weak-map.js 49% building modules 649/975 m 56% building modules 468/610 modules 142 active ...src/app/node_modules/debug/browser.js 53% building modules 703/975 m 56% building modules 473/610 modules 137 active ...src/app/node_modules/debug/browser.js 53% building modules 707/975 m 55% building modules 735/975 modules 240 active ...de_modules/socket.io-client/lib/on.js 63% building modules 548/610 m 68% building modules 610/625 modules 15 active ...de_modules/rxjs/operators/debounce.js 61% building modules 831/975 mo 61% building modules 834/975 modules 141 active ...de_modules/socket.io-client/lib/on.js 66% building modules 610/645 m 65% building modules 610/665 modules 55 active ...e_modules/rxjs/operators/retryWhen.js 61% building modules 837/975 mo 62% building modules 849/978 modules 129 active ...rxjs/observable/IteratorObservable.js 62% building modules 610/697 m 62% building modules 849/979 modules 130 active ...xjs/observable/ArrayLikeObservable.js 62% building modules 610/698 m 60% building modules 610/726 modules 116 active .../scheduler/AnimationFrameScheduler.js 62% building modules 856/979 m 60% building modules 611/728 modules 117 active ...s/rxjs/observable/bindNodeCallback.js 62% building modules 862/979 m 62% building modules 865/980 modules 115 active ...rc/app/node_modules/contra/emitter.js 57% building modules 611/778 m 63% building modules 867/980 modules 113 active ...rc/app/node_modules/contra/emitter.js 56% building modules 611/789 m 63% building modules 869/980 modules 111 active ...rc/app/node_modules/contra/emitter.js 56% building modules 611/791 m 63% building modules 876/980 modules 104 active ...rc/app/node_modules/contra/emitter.js 55% building modules 611/810 m 55% building modules 611/812 modules 201 active ...de_modules/rxjs/operator/skipWhile.js 63% building modules 877/980 m 54% building modules 611/823 modules 212 active ...modules/rxjs/operator/throttleTime.js 63% building modules 879/980 m 63% building modules 880/980 modules 100 active ...rc/app/node_modules/contra/emitter.js 54% building modules 611/827 m 64% building modules 882/980 modules 98 active ...rc/app/node_modules/contra/emitter.js 54% building modules 611/832 mo 53% building modules 611/834 modules 223 active ...app/node_modules/rxjs/operator/zip.js 64% building modules 883/980 m 54% building modules 620/836 modules 216 active .../node_modules/rxjs/operator/zipAll.js 66% building modules 919/980 m 54% building modules 624/836 modules 212 active .../node_modules/rxjs/operator/zipAll.js 67% building modules 932/980 m 56% building modules 652/836 modules 184 active .../node_modules/rxjs/operator/zipAll.js 67% building modules 976/1010  68% building modules 1009/1028 modules 19 active .../src/app/node_modules/backo2/index.js 60% building modules 709/838  61% building modules 714/838 modules 124 active ...s/core-js/modules/_collection-weak.js 68% building modules 1009/1033 68% building modules 1009/1035 modules 26 active ...modules/socket.io-parser/is-buffer.js 61% building modules 715/838  60% building modules 715/842 modules 127 active ...c/app/node_modules/dragula/dragula.js 68% building modules 1010/1035 68% building modules 1025/1056 modules 31 active .../lib/transport/browser/eventsource.js 63% building modules 744/842  63% building modules 748/842 modules 94 active ...c/app/node_modules/dragula/dragula.js 68% building modules 1029/1056  68% building modules 1035/1057 modules 22 active ...c/app/node_modules/contra/debounce.js 64% building modules 765/842  69% building modules 1054/1062 modules 8 active ...les/sockjs-client/lib/utils/iframe.js 69% building modules 841/851 m 68% building modules 1055/1073 modules 18 active ...-client/lib/transport/receiver/xhr.js 69% building modules 842/854  69% building modules 1062/1080 modules 18 active ...node_modules/rxjs/util/MapPolyfill.js 68% building modules 855/880  69% building modules 1078/1084 modules 6 active ...modules/engine.io-client/lib/index.js 69% building modules 881/886 m 69% building modules 1080/1086 modules 6 active ...pp/node_modules/custom-event/index.js 69% building modules 883/887 m 69% building modules 894/897 modules 3 69% building modules 1096/1097 modules 1 active ...dules/engine.io-parser/lib/br 69% building modules 897/899 modules 69% building modules 1099/1100 modules 1 active ...et.io-parser/node_modules/ms/in 69% building modules 1106/1108 modules 2 a 69% building modules 903/904 modules 1 active ...p/node_modules/ticky/ticky- 94% asset optimization[../../../../../src recursive \.spec\.ts$] ./src \.spec\.ts$ 1.68 kB {main} [built]
web-server_1  | [../../../../../src/app/fema/fema.component.spec.ts] ./src/app/fema/fema.component.spec.ts 740 bytes {main} [optional] [built]
web-server_1  | [../../../../../src/app/hiringdashboard/hiringdashboard.component.spec.ts] ./src/app/hiringdashboard/hiringdashboard.component.spec.ts 882 bytes {main} [optional] [built]
web-server_1  | [../../../../../src/polyfills.ts] ./src/polyfills.ts 681 bytes {polyfills} [built]
web-server_1  | [../../../../../src/test.ts] ./src/test.ts 861 bytes {main} [built]
web-server_1  | [../../../../zone.js/dist/async-test.js] ./node_modules/zone.js/dist/async-test.js 10.5 kB {vendor} [built]
web-server_1  | [../../../../zone.js/dist/fake-async-test.js] ./node_modules/zone.js/dist/fake-async-test.js 30.1 kB {vendor} [built]
web-server_1  | [../../../../zone.js/dist/jasmine-patch.js] ./node_modules/zone.js/dist/jasmine-patch.js 12.3 kB {vendor} [built]
web-server_1  | [../../../../zone.js/dist/long-stack-trace-zone.js] ./node_modules/zone.js/dist/long-stack-trace-zone.js 6.18 kB {vendor} [built]
web-server_1  | [../../../../zone.js/dist/proxy.js] ./node_modules/zone.js/dist/proxy.js 8.18 kB {vendor} [built]
web-server_1  |    [1] multi ./src/polyfills.ts 28 bytes {polyfills} [built]
web-server_1  | [../../../../zone.js/dist/sync-test.js] ./node_modules/zone.js/dist/sync-test.js 1.42 kB {vendor} [built]
web-server_1  | [../../../core/@angular/core.es5.js] ./node_modules/@angular/core/@angular/core.es5.js 492 kB {vendor} [built]
web-server_1  | [../../../core/@angular/core/testing.es5.js] ./node_modules/@angular/core/@angular/core/testing.es5.js 40.6 kB {vendor} [built]
web-server_1  | [../../../platform-browser-dynamic/@angular/platform-browser-dynamic/testing.es5.js] ./node_modules/@angular/platform-browser-dynamic/@angular/platform-browser-dynamic/testing.es5.js 3.61 kB {vendor} [built]
web-server_1  |     + 907 hidden modules
web-server_1  |
web-server_1  | ERROR in /usr/src/app/node_modules/@types/node/index.d.ts (20,1): Invalid 'reference' directive syntax.
web-server_1  | Date: 2021-03-29T18:40:48.660Z
web-server_1  | Hash: 4e5989938e044fd0578d
web-server_1  | Time: 16575ms
web-server_1  | chunk {inline} inline.bundle.js, inline.bundle.js.map (inline) 5.83 kB [entry] [rendered]
web-server_1  | chunk {main} main.bundle.js, main.bundle.js.map (main) 357 kB {vendor} [initial] [rendered]
web-server_1  | chunk {polyfills} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 367 kB {inline} [initial] [rendered]
web-server_1  | chunk {styles} styles.bundle.js, styles.bundle.js.map (styles) 11.3 kB {inline} [initial] [rendered]
web-server_1  | chunk {vendor} vendor.bundle.js, vendor.bundle.js.map (vendor) 4.69 MB [initial] [rendered]
web-server_1  |
web-server_1  | WARNING in ./src/app/host-map/host-map.component.ts
web-server_1  | 45:36-52 "export 'RdBu' (imported as 'colorbrewer') was not found in 'colorbrewer'
web-server_1  |     at HarmonyImportSpecifierDependency._getErrors (/usr/src/app/node_modules/webpack/lib/dependencies/HarmonyImportSpecifierDependency.js:65:15)
web-server_1  |     at HarmonyImportSpecifierDependency.getWarnings (/usr/src/app/node_modules/webpack/lib/dependencies/HarmonyImportSpecifierDependency.js:39:15)
web-server_1  |     at Compilation.reportDependencyErrorsAndWarnings (/usr/src/app/node_modules/webpack/lib/Compilation.js:677:24)
web-server_1  |     at Compilation.finish (/usr/src/app/node_modules/webpack/lib/Compilation.js:535:9)
web-server_1  |     at applyPluginsParallel.err (/usr/src/app/node_modules/webpack/lib/Compiler.js:512:17)
web-server_1  |     at /usr/src/app/node_modules/tapable/lib/Tapable.js:289:11
web-server_1  |     at _addModuleChain (/usr/src/app/node_modules/webpack/lib/Compilation.js:481:11)
web-server_1  |     at processModuleDependencies.err (/usr/src/app/node_modules/webpack/lib/Compilation.js:452:13)
web-server_1  |     at _combinedTickCallback (internal/process/next_tick.js:73:7)
web-server_1  |     at process._tickCallback (internal/process/next_tick.js:104:9)
web-server_1  | webpack: Compiled with warnings.

I redeployed my testing environment's dashboard instance and the result was a functional dashboard. I can only guess at this point that https://github.com/saikocat/colorbrewer/issues/8 was the result of the initial problem, and on redeploy the newer version was picked up and used. The errors are still present in the log, but not appear to result in failing functionality.

repo: cisagov/ncats-webui


text:
Fix mypy Error and Correct Platforms in README

🗣 Description
This PR fixes a mypy error and corrects an oversight in the project's README.

💭 Motivation and context
The latest cisagov/action-apb triggered GitHub Actions run had the following error:
src/vdp_scanner.py:258: error: Argument 2 to "str" has incompatible type "Optional[str]"; expected "str"

In the process of resolving that issue I noticed that the README did not have the correct platforms listed so I corrected them while I was working on the repo.

🧪 Testing

Automated tests pass. A local testing image ran as expected.

✅ Checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[x] All new and existing tests pass.

Switched this to a release candidate because I will be stacking in multiple PRs for the final 0.0.5 version.

repo: cisagov/vdp-scanner-docker


text:
Add border device in SDA Fabric

Prerequisites

[x] Have you tested the operation in the API directly?
[x] Do you have the latest Terraform provider version?

Describe the bug
(dnacenter_sda_fabric_border_device) Resource fails to Add border device in SDA Fabric
Expected behavior
API call should succeed and device should be configured as Border, Control Plane and Edge. If all three roles are included.
Screenshots
when '[' and ']' are used with "virtualNetwork":  the API fails:

terraform also includes '[' and ']' - so it fails.

However without '[' and ']'  it works:

Environment (please complete the following information):

DNAC = 2.2.3.5
Terraform version: 1.2.1
Cisco DNA Center provider version: 1.0.2-beta
OS Version:

Additional context
It seems that's how this API is also documented on DNAC:

@artur-tekieli version 1.0.2-beta was published with a possible solution to your problem, please verify it's now working for you and let us know how it went.

@fmunozmiranda, I still see an error although its different:

The device is provisioned and assigned to site:

@artur-tekieli could you please try it again with version 1.0.4-beta?, I need your confirmation because on my part I need data to prove it, thank you.

@artur-tekieli could you export this env variable or include debug in provider configuration and show me all answer you have please?
Env Variable:
TF_LOG=DEBUG

Provider configuration:
provider "dnacenter" {
  debug = "true"
}

@artur-tekieli sorry for the delay, we had some problems when publishing, there is a new version in which your problem should be solved, check that the version you are using is 1.0.5-beta, also look at the example: https ://github.com/cisco-en-programmability/terraform-provider-dnacenter/blob/main/examples/resources/dnacenter_sda_fabric_border_device/resource.tf, if the change does not work for you it would be very important for us that you pass us your file test(tf file) along with the full response with DEBUG enabled.
Note:
Thanks for reporting, it helps us a lot.

@fmunozmiranda - I can confirm in my test that it works. Thanks.

authors: artur-tekieli fmunozmiranda


text:
haidetection profile not displaying action detections

Hugo: I am using server2.py at the moment. I'll take a look at this to see if server.py code should be ported or if we only need server.py after the refactoring.

issue resolved

repo: cisco-open/DeepVision


text:
h264 does not get recognized

I am using firefox 38.0 on a Win 8.1 64bit system.
I have openH264 1.4 installed. However youtube does not recognize it at all (via youtube.com/html5). This results in beeing unable to watch most videos on youtube in quality above 360p. Some videos work with 1080p 60 fps.
This issue is connected to this superuser entry: https://superuser.com/questions/913936/firefox-html5-only-360p

OpenH264 is not used in Firefox for playing youtube videos.  It is used for WebRTC real-time video.  Your issue may be related to one of these in Mozilla's bugzilla, or you can create a new bug for it there:
https://bugzilla.mozilla.org/show_bug.cgi?id=1139290
https://bugzilla.mozilla.org/show_bug.cgi?id=1109833
https://bugzilla.mozilla.org/show_bug.cgi?id=987120

authors: Wandang ethanhugg


text:
Without configuration change, ublock origin disabled globally, webex "Media connection failed"

I had used Webex from browser (firefox on debian) for ~3 years without problems - last use was on 28 June, at the time my debian is on "bookworm" (stable).
Today, trying to join a meeting on webex.com from browser resulted in everything working as usual - including the camera preview showing up & microphone getting audio input - until I hit the final "join meeting" button, when it results in an error message "Media connection failed".
The last system update has been more than a week ago, and the configuration is:
env DBUS_SESSION_BUS_ADDRESS=none firejail --noprofile --private=~/.firejail firefox-esr
Firefox: 115.11.0esr (64-bit)
ublock origin: disabled globally
about:plugins
OpenH264 Video Codec provided by Cisco Systems, Inc.
File: 2.3.2
Path: /home/user/.mozilla/firefox/syxtm1vf.default-esr/gmp-gmpopenh264/2.3.2
Version: 2.3.2
State: Enabled
This plugin is automatically installed by Mozilla to comply with the WebRTC specification and to enable WebRTC calls with devices that require the H.264 video codec. Visit https://www.openh264.org/ to view the codec source code and learn more about the implementation.

about:config
media.gmp-gmpopenh264.lastUpdate   1718224762 == GMT: Wednesday, June 12, 2024 8:39:22 PM
When trying the same configuration outside firejail, I get a different error:
"The meeting number or meeting link is invalid. Check the number or link and then try again."
(Correlation ID is briefly shown and vanishes before it can be read, replaced by only the above text)
Everything works fine when using chromium with the libopenh264-7 codec.
The issue is reproducible on my other machine running debian trixie (but the same firefox-esr).
Any ideas how webex.com could have messed up the compatibility? Could it be because the debian firefox esr is way behind the non-esr version numbers?

There was an issue in the webex web app yesterday, causing it to fail with "Media connection failed" message on Firefox 115 ESR - it's because the web app was trying to access the sctp property on the RTCPeerConnection object and that version of Firefox doesn't support it. It has been fixed already, so please try again - it should work for you now.

Thank you @marcin-bazyl - I can confirm that the "Media connection failed" error is gone & I can join my meetings again as of today.
You'd think that a company like cisco is big enough to test something like this before pushing to production systems, but oh well - I guess they're short on qualified people because shareholders took all the money :( Hooray for capitalism.

authors: aral-matrix marcin-bazyl


text:
display owned plots list on YOUR PLOTS link click

fixed this

This does not work as I tested. can u check?

repo: citydaoproject/app