Critical vulnerability reported by trivy scan

Alluxio Version:
alluxio:2.4.1-1-SNAPSHOT-9833d5f
Describe the bug
libbz, sqlite-libs in using with critical vunerability reported by trivy scan
registry.cn-huhehaote.aliyuncs.com/alluxio/alluxio:2.4.1-1-SNAPSHOT-9833d5f (alpine 3.9.4)
==========================================================================================
Total: 194 (UNKNOWN: 0, LOW: 98, MEDIUM: 74, HIGH: 20, CRITICAL: 2)

+-------------------+------------------+----------+-------------------+---------------+-----------------------------------------+
|      LIBRARY      | VULNERABILITY ID | SEVERITY | INSTALLED VERSION | FIXED VERSION |                  TITLE                  |
+-------------------+------------------+----------+-------------------+---------------+-----------------------------------------+
| freetype          | CVE-2020-15999   | MEDIUM   | 2.9.1-r2          | 2.9.1-r3      | freetype: Heap-based buffer             |
|                   |                  |          |                   |               | overflow due to integer                 |
|                   |                  |          |                   |               | truncation in Load_SBit_Png             |
|                   |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2020-15999   |
+-------------------+------------------+----------+-------------------+---------------+-----------------------------------------+
| krb5-libs         | CVE-2020-28196   | HIGH     | 1.15.5-r0         | 1.15.5-r1     | krb5: unbounded recursion via an        |
|                   |                  |          |                   |               | ASN.1-encoded Kerberos message          |
|                   |                  |          |                   |               | in lib/krb5/asn.1/asn1_encode.c         |
|                   |                  |          |                   |               | may lead...                             |
|                   |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2020-28196   |
+-------------------+------------------+----------+-------------------+---------------+-----------------------------------------+
| libbz2            | CVE-2019-12900   | CRITICAL | 1.0.6-r6          | 1.0.6-r7      | bzip2: out-of-bounds write              |
|                   |                  |          |                   |               | in function BZ2_decompress              |
|                   |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2019-12900   |
+-------------------+------------------+----------+-------------------+---------------+-----------------------------------------+
+-------------------+------------------+----------+-------------------+---------------+-----------------------------------------+
| sqlite-libs       | CVE-2019-8457    | CRITICAL | 3.26.0-r3         | 3.28.0-r0     | sqlite: heap out-of-bound               |
|                   |                  |          |                   |               | read in function rtreenode()            |
|                   |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2019-8457    |
+                   +------------------+----------+                   +---------------+-----------------------------------------+
|                   | CVE-2019-19244   | HIGH     |                   | 3.28.0-r2     | sqlite: allows a crash                  |
|                   |                  |          |                   |               | if a sub-select uses both               |
|                   |                  |          |                   |               | DISTINCT and window...                  |
|                   |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2019-19244   |
+                   +------------------+          +                   +---------------+-----------------------------------------+
|                   | CVE-2019-5018    |          |                   | 3.28.0-r0     | sqlite: Use-after-free in               |
|                   |                  |          |                   |               | window function leading                 |
|                   |                  |          |                   |               | to remote code execution                |
|                   |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2019-5018    |
+                   +------------------+          +                   +---------------+-----------------------------------------+
|                   | CVE-2020-11655   |          |                   | 3.28.0-r3     | sqlite: malformed window-function       |
|                   |                  |          |                   |               | query leads to DoS                      |
|                   |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2020-11655   |
+                   +------------------+----------+                   +---------------+-----------------------------------------+

To Reproduce
trivy image alluxio:2.4.1-1-SNAPSHOT-9833d5f

Expected behavior
no critical VULNERABILITY report
Urgency
we have a project depend this alluxio version and want to public these days;

Fixed by #12782
Thanks for your contribution!


Sample IOS Jenkinsfile

cc @laurafitzgerald @odra

@aliok from a quick look this seems fine. I will try to build an app using it now.

@laurafitzgerald I just realized that I have written no verification instructions.
I tested it by creating a pipeline job in Jenkins for https://github.com/feedhenry-templates/helloworld-ios-swift and pasted the Jenkinsfile in there. I didn't really add any Jenkinsfile in the Git repo.
So, that needed 1 modification:
checkout scm step had to be changed to git 'https://github.com/feedhenry-templates/helloworld-ios-swift.git'
Jenkins job also needs to be parametrized: a single param named FH_CONFIG_CONTENT

@aliok I was able to successfuly build an app on OSM4


Local func vars

jenkins test ceph_ansible-kraken-centos7_cluster

jenkins test ceph_ansible-kraken-centos7_cluster

Without https://github.com/ceph/ceph-build/pull/713 CI 'for sloppy bash' will never be happy :)

jenkins test this please

jenkins test ceph_ansible-jewel-xenial_cluster

jenkins test ceph_ansible-jewel-centos7_cluster

jenkins test this please

jenkins test this please

jenkins test this please

jenkins test for sloppy bash

jenkins lint

jenkins lint

jenkins lint

jenkins lint

awesome! jenkins lint works! I need to rework so issues.

jenkins test ceph_ansible-kraken-centos7-cluster

jenkins test ceph_ansible-jewel-centos7-cluster

jenkins test ceph_ansible-kraken-xenial-cluster

jenkins test ceph_ansible-luminous-centos7-cluster

jenkins test ceph_ansible-jewel-centos7-cluster

jenkins test ceph_ansible-jewel-centos7-dedicated_journal

jenkins test ceph_ansible-jewel-centos7-dedicated_journal

jenkins test ceph_ansible-jewel-centos7-dedicated_journal

jenkins test ceph_ansible-kraken-centos7-dedicated_journal

jenkins test ceph_ansible-kraken-xenial-cluster

jenkins test ceph_ansible-kraken-centos7-dedicated_journal

jenkins test ceph_ansible-kraken-centos7-dedicated_journal

jenkins test ceph_ansible-jewel-centos7-dedicated_journal

jenkins test ceph_ansible-kraken-centos7-dedicated_journal

jenkins test ceph_ansible-kraken-xenial-cluster

jenkins test ceph_ansible-jewel-centos7-dedicated_journal

jenkins test ceph_ansible-kraken-centos7-dedicated_journal

The CI is experiencing the race condition again.. merging anyway.


Persisting the outdated .ts segments index in the m3u8 file for HLS streams

@josephnhtam, Is there a way to persist the .ts segments in the m3u8 which are outdated?
I found a DeleteOutdatedSegments which was used for restricting deletion of older segments in an ongoing stream, to maintain all the streamed ts segments.
But the m3u8 file is getting updated to the latest segments on each write operation. Would it be possible to maintain the older ts segments as well in the m3u8 file?

Hi @shreyanshJain852
You can set the SegmentListSize in HlsTransmuxerConfiguration to int.MaxValue for achieving this


Display redirect page for login in new tab instead of popup?

Is it possible to change method for opening login window?
There is a "display" property in UserManagerSettings, but I don't know how to use it. I recon default is "popup" tho.
Thanks

Use signinRedirect instead of signinPopup?

@brockallen No becauce I want to open a new window, but in a tab, not in a popup.  I need to stay on the page where the login function using "signinPopup" is called.

Can you control this via popupWindowFeatures? https://github.com/IdentityModel/oidc-client-js/wiki

@brockallen Yes sort of, I can set that to NULL in the oidc-client source code to make it do what I want. However, I don't know how to manipulate the string from my application to make it happen. If I set that property to NULL in my code, the oidc-client source code replaces it with default string.

Hmm, ok... so then a new tab... why not just do your own window.open to the new tab that points to your own page that then initiates a normal signin and callback. The problem then is how to convey the authentication results back -- if you use localStorage (instead of the default of sessionStorage) then it'd work.

Also, I had forgotten that I have a popupWindowTarget setting in there -- perhaps you can set that to a new tab instead.


aria-labelled-by should be aria-labelledby

According to the MDN documentation aria-labelled-by should be aria-labelledby. I haven't found any mention on the web that aria-labelled-by is a thing. Even if it is you should also support aria-labelledby.

:+1: Thanks!


Fixing specification of file level attributes in AvroHdfsDataWriter

This PR fixes the specification of file level attributes in AvroHdfsDataWriter. One can now specify the codec type, permissions, block size, replication factor, etc. of the avro files.

@ydailinkedin @liyinan926 please take a look when you have time.

LGTM other than the minor comments.

LGTM.

Merged


CUDA 7.0 is hard-coded in configure script for Linux

I am running Ubuntu 15.04 with CUDA 7.5 installed. However, CUDA 7.0 is hard-coded in the configure script, and I am unable to configure to use CUDA 7.5:
❯❯❯ ./configure
Do you wish to build TensorFlow with GPU support? [y/n] y
GPU support will be enabled for TensorFlow

Please specify the location where CUDA 7.0 toolkit is installed. Refer to README.md for more details. [Default is /usr/local/cuda]:
Invalid path to CUDA 7.0 toolkit. /usr/local/cuda/lib64/libcudart.so.7.0 cannot be found

This is because CUDA 7.5's libraries have the .7.5 suffix rather than .7.0:
❯❯❯ ls -l /usr/local/cuda/lib64/libcudart.so*
lrwxrwxrwx 1 root root     16 Aug 15 08:55 /usr/local/cuda/lib64/libcudart.so -> libcudart.so.7.5
lrwxrwxrwx 1 root root     19 Aug 15 08:55 /usr/local/cuda/lib64/libcudart.so.7.5 -> libcudart.so.7.5.18
-rwxr-xr-x 1 root root 383336 Aug 15 08:55 /usr/local/cuda/lib64/libcudart.so.7.5.18

see https://github.com/tensorflow/tensorflow/issues/54 or https://github.com/tensorflow/tensorflow/issues/20

Ah, thanks for pointing out those bugs. Feel free to de-dup this issue.

Hi, i had the same problem, and if you take a look about the configure script:
if [ -z "$CUDA_TOOLKIT_PATH" ]; then
default_cuda_path=/usr/local/cuda
read -p "Please specify the location where CUDA $TF_CUDA_VERSION toolkit is installed. Refer to README.md for more details. [Default is $default_cuda_path]: " CUDA_TOOLKIT_PATH
So you have nothingt to do, just find your nvidia toolkit, mine was located in:
/usr/lib32/nvidia-364
so just:
export CUDA_TOOLKIT_PATH=/usr/lib32/nvidia-364
And you are done


will support also BulkUpdate, BulkDelete and BulkInsertOrUpdate methods for mysql

adding bulk update and bulk delete methods

All basic CRUD seem to work fine.
One situation that did not work is for Update or InsertOrUpdare with custom UpdateByProp (no Unique Index)
SO_mysql-insert-on-duplicate-update-for-non-primary-key
I've supported it by temporary adding UNIQUE CONSTRAINT, similarly is done for PG.
Added Segment of MySql Test with 'entities4'.

Thank you.
If you dont mind, i wanna have a conversation with you.
On Mon, 8 Aug 2022, 22:34 Boris Djurdjevic, @.***>
wrote:

All basic CRUD seem to work fine.
One situation that did not work is for Update or InsertOrUpdare with
custom UpdateByProp (no Unique Index)
SO_mysql-insert-on-duplicate-update-for-non-primary-key
https://stackoverflow.com/questions/33495194/mysql-insert-on-duplicate-update-for-non-primary-key
I've supported it by temporary adding UNIQUE CONSTRAINT, similarly is done
for PG.
Added Segment of MySql Test with 'entities4'.
—
Reply to this email directly, view it on GitHub
https://github.com/borisdj/EFCore.BulkExtensions/pull/913#issuecomment-1208440841,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARR32R6RK5EWYFZFFKYYBSTVYFD35ANCNFSM55YZGYJA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Sure, you can text me on<EMAIL_ADDRESS>and we can arrange a time.


<EMAIL_ADDRESS>decompress error

Attempting to install Gimp v2.10.38-1 with the command 'scoop install extras/gimp' gives the current following error:
"Failed to extract files from C:\Users\JPWheeler\scoop\apps\gimp\2.10.38-1\gimp-2.10.38-setup-1.exe.
Log file:
~\scoop\apps\gimp\2.10.38-1\innounp.log"
Mentions the setup executable is corrupted.  However, I've tried the command at least five times with the same result.  Perhaps the checksum is invalid?
Log file attached.
innounp.log

Duplicates #14126.


Multiple Accounts shown together in Device View

System Health details
Good morning
what's the point of having several Google Fit accounts, but all the sensors of "X" accounts are in the same window, I don't find that interesting or logical

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
what's the point of having several Google Fit accounts, but all the sensors of "X" accounts are in the same window, I don't find that interesting or logical
Reproduction steps
what's the point of having several Google Fit accounts, but all the sensors of "X" accounts are in the same window, I don't find that interesting or logical
Debug logs
what's the point of having several Google Fit accounts, but all the sensors of "X" accounts are in the same window, I don't find that interesting or logical

Diagnostics dump
No response

@c7274864, I've no idea why this is happening and it isn't the expected behaviour. I suspect it's something to do with the device ID's not being unique enough so HA groups everything together.


Divide commands whether sudo is required or not

For example

dotfiles/sudo_install_*.sh
dotfiles/install_*.sh

Implemented. 02ea8cfb1bb16dc6f2b99f65ce5a7756030295cc


Add Description to README

Hi,
If I could offer a tip, I think it'd be helpful to add the Introduction blurb from the help docs to the repo README. I think it would help folks understand this plugin better without having to install it.
This is the blurb I am referring to:

ranger.nvim is inspired by ranger (the console file manager) and is a rewrite
of vim-netranger, which brings together the good-looking UI in ranger, native
key-binding and editing power from vim.

Before installing, I thought it was just another ranger wrapper.
Just an idea. Kudos on the excellent plugin!

Thanks!


Record calls

Hi there,
Thanks a lot for the repo! How could I record the calls?
Thank you in advance.

This can be done in via TwiML https://www.twilio.com/docs/voice/twiml/record

I try the TwiML but always have errors. In the end, I just record it in my local PC. Very simple

Hi @lanceyuu , would you mind sharing how you do it?
Thank you in advance!

hi @adamrobertolo78
i add the following code to main.py
`    # Initialize files for recording
incoming_audio_path = f"recordings/incoming_audio_{int(asyncio.get_event_loop().time())}.raw"
outgoing_audio_path = f"recordings/outgoing_audio_{int(asyncio.get_event_loop().time())}.raw"
os.makedirs('recordings', exist_ok=True)  # Ensure the recordings directory exists

incoming_file = await aiofiles.open(incoming_audio_path, mode='wb')
outgoing_file = await aiofiles.open(outgoing_audio_path, mode='wb')`

Also, you can use this file to convert the raw recording to wmv file.
https://github.com/lanceyuu/Automated-Interviews-Ai/blob/main/convert.py


unable to upload files/folders from Dropbox/MS Teams Folder

Expected Behaviour
Folders/Files should be uploaded into the DAM. (Not sure if this feature is supported yet)

Not enough information here to fully understand the requirements. Will need either more detail or, preferably, a PR with the proposed feature.


Replace all CGroup{G,S} to use abstraction in container_lxc.go

Added the rest of controllers to support different properties and controllers for issue #6305

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

This branch needs a bit of rebasing so that the .idea removing from the last commit is merged with the commit which introduces that directory.
You should also split things such that you have separate commits for adding any needed infrastructures to the cgroup package, then a commit adding all the new abstraction functions in there and then one or multiple commits porting the existing code over to them.
That's on top of @brauner's suggestion to start using a swtich statement.

Thanks for the quick feedback, will do!

Hi @stgraber @brauner ,
We made the changes based on your feedback. Much appreciated if you could have a look,thanks

Hi @brauner, updated the first function with the switch case as well. As for the the errors, we based it off https://github.com/lxc/lxd/blob/master/lxd/cgroup/errors.go where "ErrControllerMissing indicates that the requested controller isn't setup on the system" while "ErrUnknownVersion indicates that a version other than those supported was detected during init." so the latter is the case if a V2 controller is detected but we don't support that function with V2 just yet.

jenkins: test this please

static analysis is not happy. :)
/lxc-ci/build/tmp.DURBLEprU8/go/src/github.com/lxc/lxd/lxd/container_lxc.go:5740:7: ineffectual assignment to err
/lxc-ci/build/tmp.DURBLEprU8/go/src/github.com/lxc/lxd/lxd/container_lxc.go:5807:6: ineffectual assignment to err

Thanks, @brauner, fixed! Could you please run the tests on Jenkins once again as well to confirm :)

Jenkins: test this please

Thanks, @brauner, fixed! Could you please run the tests on Jenkins once again as well to confirm :)

Sure. :)
Done!

Looks like you need to run go fmt and include the result in your commits.

Hopefully third time's the charm -- seems like we had some issue running make static-analysis since $GOPATH/bin wasn't in our PATH and it couldn't run xgettext-go:
https://github.com/lxc/lxd/blob/daa7c0d478112fd0ac8811db2b354d91e32bcb55/Makefile#L206-L207

Jenkins: test this please

@brauner did the changes you requested myself, will merge once jenkins confirms it's happy.

jenkins: test this please

Thanks for doing this work! :) Much appreciated! 🤗


Go get is unable to fetch a module because it's using a wrong proxy address.
What did you expect to see?

Related Issues

net: PreferGo DNS resolver failure #56107 (closed)
net: pure Go DNS resolver hangs with ipv6 link-local address on macOS #52839
net: Error when running concurrent DNS queries using cgo on MacOS #30521 (closed)
Golang net resolver error messages are incorrect. #43702 (closed)
cmd/go: GOPROXY should not override GONOPROXY/GOPRIVATE #56477 (closed)
net: resolver error messages indicate wrong dns server when using custom resolver #43703
net: "<IP_ADDRESS>:" should be an invalid tcp4 address for ResolveTCPAddr #56144 (closed)
x/net: MacOS lookupIP resolves domains different if CGO_ENABLED flag used. #51753 (closed)
cmd/go: get not using GOPROXY and bypassing operation to git #39835 (closed)
net: DNS Lookups Very Slow (netgo) #49253 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

That's not proof that IPv6 is disabled, only that dig defaults to an A (IPv4) query.

From the output it is clear that the cgo resolver is being used, so out of our scope.

https://danp.net/posts/macos-dns-change-in-go-1-20/
This had started happening relatively recently and I believe it is caused by changes above.

Can you try forcing the go resolver and see if it helps in your case? GODEBUG=netdns=go

How do I enable both this feature and dns debug so we can see it is used for real?

GODEBUG=netdns=go+2

For reference, curl does this:
% curl -v https://proxy.golang.org/nhooyr.io/websocket/@v/list

Host proxy.golang.org:443 was resolved.
IPv6: 2a00:1450:4003:80c::2011
IPv4: <IP_ADDRESS>
Trying <IP_ADDRESS>:443...
Trying [2a00:1450:4003:80c::2011]:443...
Connected to proxy.golang.org (<IP_ADDRESS>) port 443
ALPN: curl offers h2,http/1.1

What if you pass --ipv6 to curl?
In theory go's network stack should also be doing fast fallback / dual stack ipv4 and ipv6

So the tittle is incorrect, it resolves correctly, but it fails to connect to the server when ipv6 is unavail.

curl gets stuck when forced to use ipv6. It may be that despite underlying adapter has ipv6 disabled, the Cisco vpn client pretends it's got an ipv6 address on the utun interface. Yet it causes no issues anywhere, everything works fine apart from go.
% curl -v --ipv6 https://proxy.golang.org/nhooyr.io/websocket/@v/list

Host proxy.golang.org:443 was resolved.
IPv6: 2a00:1450:4003:80c::2011
IPv4: (none)
Trying [2a00:1450:4003:80c::2011]:443...
... waits for timeout

The address is of course correct, it's the action of resolving the AAAA and sticking to it rather than resolving A is incorrect. :-)

From the discussion so far, it sounds like:

Your Mac is configured with IPv6 enabled (that is, IPv6 sockets can be created successfully).
Your DNS resolver is responding to AAAA requests with IPv6 addresses.
Go looks up proxy.golang.org and gets both IPv6 and IPv4 addresses.
Go connects to one of the IPv6 addresses seemingly successfully. Specifically, it does the connect and then runs getsockopt(fd, SOL_SOCKET, SO_ERROR) in net/fd_unix.go and gets syscall.EISCONN, which makes it return from Dial.
A future write on that connection gets syscall.ENOTCONN, as shown in the error messages.

Normally, when IPv6 addresses can't be used, the connect never succeeds (fails or times out). In your case, it appears that the connect is succeeding but then the connection breaks very quickly after that, perhaps on the first write.
Do you know of anything strange about your Mac's network or IPv6 configuration? Or some firewall that is actively breaking IPv6 connections?
For example on my Mac:
% host proxy.golang.org
proxy.golang.org has address <IP_ADDRESS>
proxy.golang.org has IPv6 address 2607:f8b0:4006:80e::2011
proxy.golang.org mail is handled by 40 alt4.gmr-smtp-in.l.google.com.
proxy.golang.org mail is handled by 10 alt1.gmr-smtp-in.l.google.com.
proxy.golang.org mail is handled by 5 gmr-smtp-in.l.google.com.
proxy.golang.org mail is handled by 30 alt3.gmr-smtp-in.l.google.com.
proxy.golang.org mail is handled by 20 alt2.gmr-smtp-in.l.google.com.
% sudo route add -inet6 2607:f8b0:4006:80e::2011 ::1
add host 2607:f8b0:4006:80e::2011: gateway ::1
% go mod download -json rsc.io/markdown@latest
{
	"Path": "rsc.io/markdown",
	"Version": "v0.0.0-20240617154923-1f2ef1438fed",
	"Query": "latest",
	"Info"<EMAIL_ADDRESS>	"GoMod"<EMAIL_ADDRESS>	"Zip"<EMAIL_ADDRESS>	"Dir"<EMAIL_ADDRESS>	"Sum": "h1:savaUwUp0YCIxdaF9EFOMB3j+TQnoLop+cNp2KPC9jk=",
	"GoModSum": "h1:rzOcjAz36Xzvwf6iaJSYXkmNbvu5XHelis1egIN0Cys="
}
% curl -v --ipv6 https://proxy.golang.org
* Host proxy.golang.org:443 was resolved.
* IPv6: 2607:f8b0:4006:80e::2011
* IPv4: (none)
*   Trying [2607:f8b0:4006:80e::2011]:443...
^C
% sudo route delete -inet6 2607:f8b0:4006:80e::2011
delete host 2607:f8b0:4006:80e::2011
% curl -v --ipv6 https://proxy.golang.org
* Host proxy.golang.org:443 was resolved.
* IPv6: 2607:f8b0:4006:80e::2011
* IPv4: (none)
*   Trying [2607:f8b0:4006:80e::2011]:443...
* Immediate connect fail for 2607:f8b0:4006:80e::2011: No route to host
* Failed to connect to proxy.golang.org port 443 after 3 ms: Couldn't connect to server
* Closing connection
curl: (7) Failed to connect to proxy.golang.org port 443 after 3 ms: Couldn't connect to server
%

The problem only happens with VPN enabled, I mentioned it before. The VPN in question is Cisco secure client, aka AnyConnect. I'm working with people who manage the Cisco VPN for us to see if they can change anything on their side (AnyConnect is supposed to be server side controlled, so not much can be done on the client side).

Only Go breaks on our current setup; all other applications seem to work just fine. Go used to work previously, it only started breaking relatively recently (may be caused by 1.20 changes or by some changes to AnyConnect setup).
Go can be made to work by using ifconfig to erase IPv6 addresses from the utun device in use by AnyConnect. This, however, has to be done on any VPN reconnection (due to how AnyConnect works).

@rsc I get the same issue when trying to install things using 1.22.6 on my MacBook while on our corporate VPN (which is also Cisco AnyConnect).
My testing reveals there are two underlying issues:

The IPv4 dial (which, contrary to the documentation, actually happens first, see #68795) takes longer than 300 milliseconds to complete.
Somehow Go believes the IPv6 dial works even though it clearly didn't really. (Kernel bug?)

Increasing the dialer's FallbackDelay is enough to resolve the issue, but I have no control over what go install is doing. Would it be possible to allow overriding the 300 ms default via some env var?


(2.x) is there any way to kill a custom setup after it has initialized on my form?

with a very basic 'custom' setup, I have a simple form working with the 2.27.0 version of this library here:
https://gist.github.com/jasonfb/73a769ade9e81f29c512038fea95c7e2
Can I turn the braintree setup off entirely after it has been initialized? My normal first-card entry workflow works fine, but I want the user to be able to select an existing credit card and this is where I am getting stuck because the Braintree javascript is throwing "User did not input payment method" validation on the form
So basically if the user chooses from an existing card instead of entering a new one I want the previously-initialized braintree to be disabled.
Something like
braintree.kill()
Anything available like this in the 2.27.0 version?

There sure is! It's called teardown. Here are the docs for it: https://developers.braintreepayments.com/reference/client-reference/javascript/v2/best-practices#teardown


Regression: logfile in 2.4.1 is not written

The shinyproxy.log file is properly written using shinyproxy 2.3.1, but is not written in version 2.4.0 onwards:
Working:
FROM openjdk:11-jre
RUN wget https://www.shinyproxy.io/downloads/shinyproxy-2.3.1.jar -O shinyproxy.jar
CMD java -jar shinyproxy.jar >/dev/null 2>&1 & sleep 5 && [ -f shinyproxy.log ] && echo "shinyproxy.log exists!" || echo "shinyproxy.log does NOT exist!"

λ docker build -t shinyproxy-logtest . && docker run shinyproxy-logtest
shinyproxy.log exists!

Not working:
FROM openjdk:11-jre
RUN wget https://www.shinyproxy.io/downloads/shinyproxy-2.4.1.jar -O shinyproxy.jar
CMD java -jar shinyproxy.jar >/dev/null 2>&1 & sleep 5 && [ -f shinyproxy.log ] && echo "shinyproxy.log exists!" || echo "shinyproxy.log does NOT exist!"

λ docker build -t shinyproxy-logtest . && docker run shinyproxy-logtest
shinyproxy.log does NOT exist!

Hi @shosaco
Starting from ShinyProxy 2.4.0 you have to adapt the logging config slightly, such as:
logging:
  file:
    name: shinyproxy.log

I'll update the relevant documentation on our site.

Works like a charm, thank you for the information!


FR: add reading of ENV vars for configuration

Can the sync plugin get authorization data from vault or environment variables?
Maybe in settings.ini
api_token = $API_TOKEN_NETBOX
[source/my-vcenter-example]
username = $USERNAME
password = $PASSWORD

Hi,
I had this idea in mind for a long time. Also a more general approach to support all variables would be great.
The issue is the naming of according vars.
example for NetBox vars would be fairly easy:
NBS_NETBOX_API_TOKEN=

with sources not so easy. I only came up with two approaches.
first:
NBS_SOURCE_my-vcenter-example_USERNAME

But this would limit the possible characters for source names. Also we need to parsing of available vars first
Second idea is to enumerate sources:
NBS_SOURCE_1_NAME=my-vcenter-example
NBS_SOURCE_1_TYPE=vmware
NBS_SOURCE_1_USERNAME=readonlyuser

This is also not very intuitive.
Any ideas/suggestions/recommendations?

I think the second option is easier. I think if described in the documentation there will be no big problems.
To make it clearer, you can make it mandatory to indicate the order in the sort.
For example,
[source-1/my-vcenter-1]
...

[source-2/my-vcenter-2]
...

This functionality would be very useful for me.

Hey, this would imply that every user has to change their config without a direct benefit for everyone. This is not possible. There must be a different way.

Then I think the first option is better.

But this would limit the possible characters for source names

I don't think this is a problem. The documentation can describe naming examples. If the name does not match, then it is expected that all parameters are specified only in the config
I think the most important thing is to hide the passwords and the token. Other parameters can be left in the config.
NBS_NETBOX_API_TOKEN=<token>
NBS_SOURCE_my-vcenter-example_PASSWORD=<password>

What do you think about it?

This will be part of the next version.
Did a complete rewrite of config parsing.
Config types supported:

INI files
YAML files
Environment variables

Just the documentation part is still left.

Would you be able to try out "feature/improved-config-parsing" branch?

Hey @nikolasj,
I just finished the documentation. You can find it here:
https://github.com/bb-Ricardo/netbox-sync/blob/development/README.md#configuration
it is now merged to the development branch. Would you mind to try it out?
thank you.

@nikolasj did you have any chance to test this?


Bitcode generation conflict when two files have the same name but different extensions

Hi Ian,
I recently ran into an issue in a project with a C and C++ file have the same name but different extension (.c vs .cpp). The result being that the bitcode from one is clobbered by the other.
To reproduce, try the example below:
root@3dece5d8f0c9:/tmp/gllvm# cat test.c
#include <stdio.h>

int main(int argc, const char *argv[]) {
	printf("Hello from C!\n");
	return 0;
}
root@3dece5d8f0c9:/tmp/gllvm# cat test.cpp
#include <iostream>

int main(int argc, const char *argv[]) {
	std::cout << "Hello from C++" << std::endl;
	return 0;
}
root@3dece5d8f0c9:/tmp/gllvm# gclang -o test.c.bin test.c
objcopy: st0NVLch: Failed to find link section for section 8
objcopy: st0NVLch: Failed to find link section for section 8
root@3dece5d8f0c9:/tmp/gllvm# gclang++ -o test.cpp.bin test.cpp
objcopy: stmMWA24: Failed to find link section for section 13
objcopy: stmMWA24: Failed to find link section for section 13
root@3dece5d8f0c9:/tmp/gllvm# get-bc -b -o test.c.bc test.c.bin
Bitcode file extracted to: test.c.bc.
root@3dece5d8f0c9:/tmp/gllvm# llvm-dis test.c.bc
root@3dece5d8f0c9:/tmp/gllvm# grep 'C++' test.c.ll
@.str = private unnamed_addr constant [15 x i8] c"Hello from C++\00", align 1
root@3dece5d8f0c9:/tmp/gllvm#

The root cause seems to be that getArtifactNames strips the extension from the source file and appends .bc. Would it be feasibly to either keep the full file name before appending .bc, or use some kind of content hash to name the files?

So it may succeed if you use the bitcode archive feature (the documentation is currently only in one place), which isn't this repo.  Try that. If it doesn't work, I can fix this guy to handle this obscure case. Looks like you need to upgrade your objcopy too.

We weren't able to get the archive feature to work for our (admittedly unusual) use-case, but we did re-organize the source to build the .c and .cpp in different directories, which worked around the issue.
A fix would be nice, but I can understand if its not a priority since this is a fairly unusual situation.

I think it is a very easy fix. Let me see if it breaks anything.

Artem, See if this works for you ...

Confirming this fixes the issue, thanks!


[cloud|google] Only using Service Accounts for GCE credentials

This addresses issue #6966.
Since GCE is only going to use Service Accounts in the short-term, this change drops the specific Service Account credentials tab and moves that functionality up as the Default.
I also took a stab at a custom message but don't yet know what to do about l10n.
/cc @blomquisg, @agrare

:+1: LGTM


Documentation of Memory Section

Looks good. Just for the sake of the git history, can you merge the 4 commits into 1?


MOSN: practice/mosn.md

This article is waiting to be claimed. practice/mosn.md

/accept

/assign @wangfakang


Exchange Phishlets here

we all can exchange phishlets

yes we can exchange let me know when you ready

Any one have facebook phishlet

telegram @DrainC0d3r

**Hi 👽 ! If you are interested in ⚙Advanced Phishing⚙ and the ✨Evilginx3✨ tool then I offer you Google Gmail and Custom Phishlets with a ✅Free Tutorial✅ which arrives if the 📈Telegram reaches 50 Subscribers📈
⏳ GOOGLE GMAIL PHISHLET 2024 WITH PROOF ⏳
->
⛔https://www.youtube.com/watch?v=nA47UknIE6A⛔
🔓 Ask your questions and a free tutorial from 50 subs on telegram !!!
->
📩https://t.me/Noremorse1011📩**


Request: support for providing Slurm Accounting DatabaseName to ParallelCluster UI

We are currently developing a migration plan in between ParallelCluster versions, which includes a ParallelCluster UI upgrade when new versions are available. So far, one of the road blocks we are running into is how Slurm Accounting databases can be migrated between ParallelCluster versions, see https://github.com/aws/aws-parallelcluster/issues/6214.
In the issue, it was mentioned that with newer ParallelCluster versions it seems to be possible to supply a DatabaseName for the Slurm Accounting database, which seems to have been included in ParallelCluster since September/October 2023: https://github.com/aws/aws-parallelcluster/pull/5718.
In the issue, we are exploring the migration use case. It was suggested to create a request here about support for DatabaseName in ParallelCluster UI. Effectively, it boils down to adding a field to the UI which passes the specified database name to ParallelCluster when the cluster is created.
Wondering what's possible, thanks in advance for your insights!

Hi @christianversloot thanks for this feature request.
We tracked it in our backlog.


CHANGELOG.md is missing information for most v13.3 versions

The CHANGELOG.md appears to be missing versions. The first two stanzas in the file are currently for v13.3.33 and v13.3.27 (which as far as I can tell aren't actually "released" even though they are tagged as releases?).
However, the next entry is v12.19.33 - there is no changelog at all listed for v13.2.20 which is the current actual release on downloads.chef.io. Nor indeed is there any changelog for any of the v13 releases prior to v13.3.27
It's actually quite unclear - from the changelog or from anywhere else that I've been able to find - trying to work out what Chef versions have actually been officially released, and what changes they introduce.

We've switched changelog generators and fixed the issue going forward, but we do have issues with the current changelog. I'll see what I can do to generate a better changelog for the previoius 13.X releases.

Great, thanks @tas50

I've backfilled the latest Chef 12 releases here.
https://github.com/chef/chef/blob/master/CHANGELOG.md
Chef 13+ is going to take a bit longer, but this gets us closer

13.0 releases have been added

looks fixed for now


Change common dependency

This is what we should be depending on, not https://github.com/googleapis/google-cloud-cpp/archive/v0.13.0.tar.gz:
https://github.com/googleapis/google-cloud-cpp-common/archive/v0.13.0.tar.gz
https://github.com/googleapis/google-cloud-cpp-common/releases

This issue is stale. Closing.


connect ECONNREFUSED <IP_ADDRESS>:6000

VSCode Version: 1.52.0-insider
OS Version: Windows_NT x64 10.0.19041

Steps to Reproduce:

Debug in Firefox (using Debugger for Firefox)
Randomly get popup:  "connect ECONNREFUSED <IP_ADDRESS>:6000". Also breakpoints do not seem to hit.

Does this issue occur when all extensions are disabled?: No

This error is probably happening because you habe not configured Firefox as a launch configuration in launch.json
launch.json is located in your "project root file/.vscode" folder.
Here is a sample launch.json for Firefox
{
    "configurations": [
        {
            "type": "firefox",
            "request": "launch",
            "reAttach": true,
            "name": "Launch localhost",
            "url": "http://localhost:8080/",
            "webRoot": "${workspaceFolder}",
            "firefoxExecutable": "C:\\Program Files\\Firefox Nightly\\firefox.exe"
        }
    ]
}

Got this after installing new version of insiders and thought it was related to new version.
Then found this: https://stackoverflow.com/questions/36783068/cannot-connect-to-the-target-connect-econnrefused-127-0-0-19222/36845875
Rebooted PC and everything was fine. Breakpoints working again too.


Docs.MS Release Updates for Azure.Analytics.Synapse.Monitoring

Update docs metadata and targeting for release of Azure.Analytics.Synapse.Monitoring

Docs Build status updates of commit 3e67458:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

xml/Azure.Storage.Blobs.Specialized/SpecializedBlobExtensions.xml
:x:Error

Details

api/overview/azure/analytics.synapse.monitoring-readme-pre.md
:warning:Warning

Details

xml/Azure.Storage.Blobs.Specialized/SpecializedBlobExtensions.xml

Line 0, Column 0: [Error-ECMA2Yaml_DocId_Duplicated] Duplicated DocId found: M:Azure.Storage.Blobs.Specialized.SpecializedBlobExtensions.GetParentBlobContainerClient(Azure.Storage.Blobs.Specialized.BlobBaseClient)
Line 0, Column 0: [Warning-ECMA2Yaml_MemberNameAndSignature_NotUnique] Member GetParentBlobContainerClient's name and signature is not unique
Line 0, Column 0: [Warning-duplicate-uid] UID 'Azure.Storage.Blobs.Specialized.SpecializedBlobExtensions.GetParentBlobContainerClient_m' is duplicated in 'api/Azure.Storage.Blobs.Specialized.SpecializedBlobExtensions.GetParentBlobContainerClient_m.yml(26,8)', 'api/Azure.Storage.Blobs.Specialized.SpecializedBlobExtensions.GetParentBlobContainerClient_m.yml(4,8)'.
Line 0, Column 0: [Warning-duplicate-uid] UID 'Azure.Storage.Blobs.Specialized.SpecializedBlobExtensions.GetParentBlobContainerClient_m' is duplicated in 'api/Azure.Storage.Blobs.Specialized.SpecializedBlobExtensions.GetParentBlobContainerClient_m.yml(26,8)', 'api/Azure.Storage.Blobs.Specialized.SpecializedBlobExtensions.GetParentBlobContainerClient_m.yml(4,8)'.

api/overview/azure/analytics.synapse.monitoring-readme-pre.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'synapseanalytics'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 73, Column 1: [Suggestion-table-syntax-invalid] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines. NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 3e67458:
:warning: Validation status: warnings

File
Status
Preview URL
Details

api/overview/azure/analytics.synapse.monitoring-readme-pre.md
:warning:Warning
View
Details

api/overview/azure/analytics.synapse.monitoring-readme-pre.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'synapseanalytics'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 73, Column 1: [Suggestion-table-syntax-invalid] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines. NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Remove jqLite#bind & jqLite#unbind

Note: for support questions, please use one of these channels: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#question. This repository's issues are reserved for feature requests and bug reports.
Do you want to request a feature or report a bug?
A refactor (removing a feature).
What is the current behavior?
jqLite#bind & jqLite#unbind exist and are aliases to jqLite#on & jqLite#off respectively.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar (template: http://plnkr.co/edit/tpl:yBpEi4).
N/A
What is the expected behavior?
jqLite#bind & jqLite#unbind should be removed.
What is the motivation / use case for changing the behavior?
Those methods will be deprecated in 1.6.0 so we should remove them in 1.7.0.
Which versions of Angular, and which browser / OS are affected by this issue? Did this work in previous versions of Angular? Please also test with the latest stable and snapshot (https://code.angularjs.org/snapshot/) versions.
N/A
Other information (e.g. stacktraces, related issues, suggestions how to fix)
N/A

@mgol Why plan for removal at all?  It seems like a potentially big breaking change in order to save 2 lines of code that don't introduce significant complexity, and it doesn't align with jQuery's goals of deprecation without removal for event shorthands/aliases (as you definitely know)

We have recently decided that deprecated features should generally stay in the code for one minor release and be removed in the next minor (breaking) release. And that we should create issues with an appropriate milestone as a reminder.
This is not a hard rule; we can discuss it when the time comes for 1.7.0.
--
Admittedly, bind/unbind are kind of special, since they are just alises. On the other hand, migrating is pretty easy, so I don't see much benefit in allowing people use a method that has been deprecated for a long time. (Just my 2 cents.)
In any case, thx for raising this @dcherman so we can take it into account when the time comes :smiley:

Thanks @dcherman for the comment.
@gkalpak It's true it's easy to change the code but this applies to your code only. jQuery has a large ecosystem of plugins, not all of which are regularly updated, especially as long as jQuery doesn't remove a particular deprecated API.
Maybe we should treat jqLite-related deprecations differently than for the rest of Angular: wait for removal in jQuery before removing the API in Angular itself?

Maybe we should treat jqLite-related deprecations differently than for the rest of Angular: wait for removal in jQuery before removing the API in Angular itself?

Makes sense.

We've decided to follow this strategy:

we should treat jqLite-related deprecations differently than for the rest of Angular: wait for removal in jQuery before removing the API in Angular itself

We'll document it in FAQ.
I'm closing this ticket; thanks, @dcherman!


(chores) camel-kafka: added tests for handling invalid authentication

Components tested:
Total 	Tested 	Failed ❌ 	Passed ✅
2 	2 	1 	2

The failure is not here, so good to merge.


EC2 instances should be managed by AWS Systems Manager

Describe the bug
Stopped EC2 Instances are reported as non-compliant by the EC2 instances should be managed by AWS Systems Manager check. As they are stopped, they are not reporting to SSM and therefore can never be compliant.
Steampipe version (steampipe -v)
v18.0
Plugin version (steampipe plugin list)
Default in SPC
Mod version 0.54.0
To reproduce
Stop an instance that has been reporting into SSM, wait 24hrs, and it becomes non-compliant.
Expected behavior
Stopped instances should be excluded from the query so as not to generate distracting false positive findings.
Additional context
Add any other context about the problem here.

@jchrisfarris Thanks for this testing & feedback!
We will check this and take appropriate action. In this case, we followed the AWS config rule specified here. I guess, initially, we thought irrespective of instance state (running/stopped), we would consider the SSM manages the instance.
To be a managed instance, instances must meet the following prerequisites: reference

Have the AWS Systems Manager Agent (SSM Agent) installed and running.
Have connectivity with Systems Manager endpoints using the SSM Agent.
Have the correct AWS Identity and Access Management (IAM) role attached.
Have connectivity to the instance metadata service.
So in the query, we just picked the managed instance ID from aws_ssm_managed_instance to consider the outcome.

Should we include the instance state validation in it? Or maybe, we can recheck how the config rule evaluates the same at our end. If you can share, the result will be helpful.

I spent time yesterday trying to find the code for these AWS Config rules (and couldn't find it). If you know where the lambda source for these lives, please share.
From a practitioner's standpoint - I don't want to report a violation unless the violation can be fixed. If I wanted a rule that says "Thou shalt not have stopped instances" I'd write that as the rule so it's easy for teams to know what to fix.
In this case, if having stopped instances isn't a requirement, there is no way a team can make a stopped instance complaint with this SSM check unless they start the non-compliant instance - a result that leads to both added expense and risk.

@jchrisfarris, thanks for the input; I follow this, but it's separate from how the AWS config rule source code is developed.
In the current state, we don't have any SDK support to get the instance stop time, hence would it make sense for us to capture the instance stopped state and inform users about it as info
select
  -- Required Columns
  i.arn as resource,
  case
    when i.instance_state = 'stopped' then 'info'
    when m.instance_id is null then 'alarm'
    else 'ok'
  end as status,
  case
    when i.instance_state = 'stopped' then i.title || ' is in stopped state.'
    when m.instance_id is null then i.title || ' not managed by AWS SSM.'
    else i.title || ' managed by AWS SSM.'
  end as reason,
  -- Additional Dimentions
  i.region,
  i.account_id
from
  aws_ec2_instance i
  left join aws_ssm_managed_instance m on m.instance_id = i.instance_id;


[BUG] Serialisation prevents use of hypen in serial numbers

Describe the bug
The database schema supports (and should continue to support (IMO)) hyphens in serial numbers, as these are common. When serialising a number of items, any hyphen is interpreted as a range operation even in cases where it is nonsensical.
Expected behavior
Some variation of the following logic should be added to group definitions:

If the count of serial entries == the number of items to be serialised, skip group interpolation
If there is more than one hyphen per word, skip group interpolation for this word

Version Information
master
I am happy to write this patch but want to discuss that it is acceptable first.

Not a bug - was an intentional design decision to enable after input

@SchrodingersGat @eeintech what are your opinions here? I see no reason to not change it if the fast input gets preserved.
Some clear way to communicate the change in the UI should be added though.
Would be happy to see @exp work on this if above questions are resolved.

Proposed UI communication:
Enter serial numbers for new items — You may use groups (1-10) or sequences (5+) if you enter fewer serial numbers than items.
Do you want to keep this strictly to very few words? Mentioning space or comma separation I think would also be valuable.

@exp I do not really care about the length of the documentation/info as long as the syntax for input is not becoming complex
Small wrong example (which I have seen in another system):
``
1{{-}}5
{1-{{15}}}-{1-{{20}}}
``

Using a reserved token character in the serials will vastly increase complexity and associated considerations here.
@exp if you can show a "one size fits all" solution which accommodates hyphens in the serial numbers, we can consider it, but not if it has complex edge cases that need to be communicated to users (across multiple languages!)
e.g. what does the following string evaluate to?
5 unique serial numbers to be extracted from 1-5, 2, 3-5
This could be ambiguous!

@SchrodingersGat I think prohibiting - from being included in serials would be a mistake, as there are millions of physical items with those serials lying around. Furthermore you can already edit the serial attribute to include this, so production Inventree databases and printed labels undoubtedly exist with them already.
The example you give already fails due to the expansion of those groups so I can't really tell you how it should behave, but there exists one case I can think of that would currently cause an error but after patching, would be accepted erroneously:
Count: 5; Serials: '1 2 3 4 5-10'
In my proposal the 5th item would be given the serial 5-10 instead of the expansion flagging an error for too many serials. I think that's what you're alluding to, but I think that's quite a minor worry. There are no proposed syntax changes and the code complexity is extremely simple (len(groups) == expected_quantity and the removal of one error case).
If the above is more of a worry than I think, would you accept a javascript driven warning as an alternative? I really don't want to have to mangle (literally hundreds of) serial numbers across my stock. Thanks for your time!

@exp I would tend to agree, if you submit a PR with the proposed set of changes we'll certainly take a look!

Understood, this isn't strictly related to this bug, but I assume you envisage a serial field of 1 2 ~ ~ ~ to imply  1 2 3 4 5 and not 1 2 3 3 3? I figured that might as well be fixed too.

I don't think we had ever considered the case of multiple sequential ~ characters, tbh

This has been merged, not sure why the PR wasn't linked to this automatically.


[ai-form-recognizer] Add tracing spans and tests

Packages impacted by this PR
@azure/ai-form-recognizer
Issues associated with this PR
Closes #20313
Describe the problem that is addressed by this PR
This PR adds tracing spans to most methods (does not add them for PagedAsyncIterableIterator methods).
Are there test cases added in this PR? (If not, why?)
Yes. Tracing support is validated with assert.supportsTracing.
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[x] Added impacted package name to the issue description

API change check for @azure/ai-form-recognizer
API changes are not detected in this pull request for @azure/ai-form-recognizer


Extend the Chain trait to enable listening for IBC events from non-Cosmos SDK chains, eg. Substrate

Crate
None
Summary
init_event_monitor Support multiply chain to event mointor
https://github.com/informalsystems/ibc-rs/blob/8944f94815c35b2d3297971aa437900d259dc75a/relayer/src/chain.rs#L99
/// Initializes and returns the event monitor (if any) associated with this chain.
    fn init_event_monitor(
        &self,
        rt: Arc<TokioRuntime>,
    ) -> Result<(EventReceiver, TxMonitorCmd), Error>;

https://github.com/informalsystems/ibc-rs/blob/8944f94815c35b2d3297971aa437900d259dc75a/relayer/src/event/monitor.rs#L132
pub struct EventMonitor {
    chain_id: ChainId,
    /// WebSocket to collect events from
    client: WebSocketClient,
    /// Async task handle for the WebSocket client's driver
    driver_handle: JoinHandle<()>,
    /// Channel to handler where the monitor for this chain sends the events
    tx_batch: channel::Sender<Result<EventBatch>>,
    /// Channel where to receive client driver errors
    rx_err: mpsc::UnboundedReceiver<tendermint_rpc::Error>,
    /// Channel where to send client driver errors
    tx_err: mpsc::UnboundedSender<tendermint_rpc::Error>,
    /// Channel where to receive commands
    rx_cmd: channel::Receiver<MonitorCmd>,
    /// Node Address
    node_addr: Url,
    /// Queries
    event_queries: Vec<Query>,
    /// All subscriptions combined in a single stream
    subscriptions: Box<SubscriptionStream>,
    /// Tokio runtime
    rt: Arc<TokioRuntime>,
}

Problem Definition
Recently I am doing support for substrate relayer support, for event listening here, it seems that there is no support for multiple chains like ChainEndpoint defines an interface, here for EventMonitor to listen to events suitable for tendermint-rpc strong binding, no implementation and different chains between the loose coupling. Is there a good implementation to achieve this part of the function, because I found that this EventMointor in the implementation of start and listen command is related.
Proposal
None
Acceptance Criteria
None

For Admin Use

[x] Not duplicate issue
[x] Appropriate labels applied
[x] Appropriate milestone (priority) applied
[x] Appropriate contributors tagged
[x] Contributor assigned/self-assigned

@DaviRain-Su What do you think of the refactoring in #2865? Does this help with your use case?

It looks good, but there are still some components that are strongly related to tendermint that I wish could be abstracted

Closed by #2865: https://github.com/informalsystems/hermes/pull/2865#discussion_r1036039050


Hierarchical clustering in neo4j

Using the Louvain hierarchical clustering algorithm to generate communities of nodes for the graph resulting in annotating the abstracts of source level nodes.

We might use dvc to version the data.


[SR-13527] printing localizedDescription on an Error which is a class crashes on Linux

Previous ID
SR-13527

Radar
None

Original Reporter
adirburke (JIRA User)

Type
Bug

Attachment: Download

Environment
Swift version 5.1.1 (swift-5.1.1-RELEASE)
Target: x86_64-unknown-linux-gnu

Additional Detail from JIRA

Votes
0

Component/s

Labels
Bug

Assignee
None

Priority
Medium

md5: cbf8bc584e034113cec37bd027cf9d0c

Issue Description:
Creating a error on a class and printing an unspecified localizedDescription in linux causes an SegFault while doesnt on OSX

This is crashing for me even if I implement LocalizedError on the type:
test.swift contents:
import Foundation

class E: Swift.Error { }

extension E: LocalizedError {
  public var errorDescription: String? {
      return "message"
  }
}

let e = E()
e.localizedDescription

> swift test.swift
Stack dump:
0.	Program arguments: /usr/libexec/swift/6.0.1/bin/swift-frontend -frontend -interpret test.swift -disable-objc-interop -color-diagnostics -empty-abi-descriptor -resource-dir /usr/libexec/swift/6.0.1/lib/swift -module-name test -plugin-path /usr/libexec/swift/6.0.1/lib/swift/host/plugins -plugin-path /usr/libexec/swift/6.0.1/local/lib/swift/host/plugins
1.	Swift version 6.0.1 (swift-6.0.1-RELEASE)
2.	Compiling with effective version 5.10
3.	While running user code "test.swift"
#0 0x00000000073dc648 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/usr/libexec/swift/6.0.1/bin/swift-frontend+0x73dc648)
#1 0x00000000073da3ee llvm::sys::RunSignalHandlers() (/usr/libexec/swift/6.0.1/bin/swift-frontend+0x73da3ee)
#2 0x00000000073dccb8 SignalHandler(int) (/usr/libexec/swift/6.0.1/bin/swift-frontend+0x73dccb8)
#3 0x00007f711164fd00 __restore_rt (/lib64/libc.so.6+0x40d00)

💣 Program crashed: Bad pointer dereference at 0x0000000000000000

Thread 0 "swift-frontend" crashed:

0 0x0000000000000000
1 0x00007f7111a6614b

Backtrace took 0.00s

From another shell, please run

lldb --attach-pid 1780963 -o c
fish: Job 1, 'swift test.swift' terminated by signal SIGSEGV (Address boundary error)

> swift --version
Swift version 6.0.1 (swift-6.0.1-RELEASE)
Target: x86_64-unknown-linux-gnu

When I run lldb, it seems like it's failing on this instruction: callq  0x7f710d3c7b90 ; symbol stub for: swift_release.   Is swift_release not getting linked in?


chore(CONTRIBUTING.md): change some typo and sentence

In reading this file for prepare another PR I saw some minor arrangement to do.

Thanks for the contribution!


Minor versioning prototype

This is a draft PR to illustrate my idea for handling TO API minor versioning.
Essentially, requests that come in at a previous minor version will be "upgraded" into requests of the next latest versions until they are finally handled by one "main" handler that always handles requests at the latest minor version. The result is then passed back down the chain until the result is translated back into the minor version that the client originally requested.
For POST requests, the "upgrade" process is simply just taking the specific minor version, embedding it into the next latest struct version, and passing it up. For PUT requests, the "upgrade" process would include reading the existing fields for the next latest minor version from the DB and passing it up to the next handler.
What we end up with is a chain of "sub-handlers" that simply upgrade requests into the next latest minor version until the request is finally handled at the latest minor version -- the "main" handler -- then downgrade that result until the originally requested minor version is returned.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3607/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3608/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3611/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3615/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3826/
Test PASSed.

closing this as the refactor has been applied to the DS API in https://github.com/apache/trafficcontrol/pull/3713


DB2 SQL for dropping a primary key is invalid

The SQL code to drop a primary key/unique constraints is invalid for a DB2 database.
Steps to reproduce:

Select/Open a DB2 database.
Select/Open a schema.
Select/Open a table.
Right click on Unique Constraints and select View Unique Constraints.
Select the primary key and click Delete (or the red cross at bottom right).
Click Save
This displays the SQL preview for dropping the primary key of the form

ALTER TABLE SCHEMA.TABLENAME DROP PRIMARY_KEY  ;
This SQL is invalid and the command fails.
The correct SQL is
ALTER TABLE SCHEMA.TABLENAME DROP PRIMARY KEY  ;
(note PRIMARY_KEY should be PRIMARY KEY, no underscore).

Sorry this defect manifests in Community edition 4.2.2

Seems to be fixed in 4.2.3.


Support for more syntax and better multiline ERB formatting

Hi,
First of all, thanks for building syntax_tree-erb! It was the closest to what I was looking for, so I forked it and made a few changes. I think you may agree with most (or all?) of them, so I'm letting you know what I did here.
My code is slightly hacky in places and I don't fully know what I'm doing, so do let me know if you'd like me to clean something up.
Multiline ERB formatting
Before my change multiline ERB would be formatted more or less like this:
<%= with_brackets(
  argument1,
  argument2,
  argument3
) %>
<%= without_brackets argument1,
                 argument2,
                 argument3 %>

I think whether the version with brackets looks good is subjective, but I have to assume the version without brackets wasn't intended - the alignment is off by the length of <%=  prefix.
One way to improve it may be to use the erb plugin together with the no_alignment plugin, which will give something like this:
<%= without_brackets argument1,
  argument2,
  argument3 %>

That still doesn't look great though.
What my branch (this PR) does is the following:
<%=
  with_brackets(
    argument1,
    argument2,
    argument3
  )
%>
<%=
  without_brackets argument1,
                   argument2,
                   argument3
%>

It adds more linebreaks, but I much prefer it.
I think it could be a configuration option if you (or other users) prefer the more condensed version.
ERB inside HTML tags
Previous state:
<%# supported %>
<tag <% something %> />
<tag attr="<%= something %>" />
<tag attr="<% if a %>b<% end %>" />

<%# unsupported %>
<tag <%= something %> />
<tag <% if a %>b="c"<% end %> />

In my branch all of these cases are supported.
when 1, 2
Previous state:
<%# supported %>
<% case foo %>
<% when 1 %>foo
<% end %>

<%# unsupported %>
<% case foo %>
<% when 1, 2 %>foo
<% end %>

In my branch comma-separated arguments are also supported.
Formatting of keywords in ERB blocks
Previously code like below was possible
<%
if
  some_method(argument1, argument2, argument3)
%>
foo
<% end %>

In my branch keywords are formatted together with the rest of the Ruby code, so it looks better:
<%
  if some_method(argument1, argument2, argument3)
%>
foo
<% end %>

And that's it for now.
Let me know what you think.

Could you see why the tests are failing?

I am on vacation, so I am not by my computer as much.


Save overwritten when not backed up properly.

Ludusavi version
v0.27.0
Operating system
Windows
Installation method
Standalone
Description
I have ludusavi on both my steamdeck and Windows computer. I used the wrap with --force command to backup my games for both the steamdeck and windows computer automatically. I forgot to properly close the game when I was shutting down my computer so the backup was never taken.  I then used my steamdeck and it restored to cloud automcatically. Since my computer saw a newer save in  the cloud it then overwrote my backup locally and in the cloud. we need some proper timestamp checking to detect this.
Logs
No response

I propose we use the the size /file modified to check before restoring.
my situation happened because my new save wasn't uploaded  or even synced with the backup so cloud sync saw a newer save on the cloud and decided to restore that one.  This would also happen if the user is offline when progressing there save and doesn't initiate a save
if the local file size is > than the local backup file size  and cloud sync backup . Another check would be to check the modified timestamp on top of that. if the local file modified timestamp is <= local backup file timestamp and local file size > local backup timestamp  we should raise a error and let the user decide what to do.  we could also implement automatic rules to let it automatically decide what to do.


Setup CI with Travis

We can run this on the same build-server as all of the other Akka.NET stuff if you'd like... But honestly,I think it'd be really cool to see this up and running on Travis even though I think .NET support is still in beta there. I'd love to know how to configure a project to run there :)

I will take a stab at getting this to run under travis with .net.

Steps for configuration that I can partially do where the setup aspect on travis ci needs to be done an admin of the hocon gh repo.
[ ] Sign in to Travis CI with your GitHub account, accepting the GitHub access permissions confirmation.
[ ] Once you’re signed in, and travis ci has synchronized your repositories from GitHub, go to your profile page and enable Travis CI for the repository you want to build.
*** Note: You can only enable Travis CI builds for repositories you have admin access to. ***
[ ] Add a .travis.yml to the root directory
language: csharp
solution: solution-name.sln

I assigned this issue to @Aaronontheweb to do these bits:

[ ] Sign in to Travis CI with your GitHub account, accepting the GitHub access permissions confirmation.
[ ] Once you’re signed in, and travis ci has synchronized your repositories from GitHub, go to your profile page and enable Travis CI for the repository you want to build.

Ok dokey, thanks @haighis - will do

Done!

https://travis-ci.org/akkadotnet/HOCON


Running tests in isolation on CLI

After the big refactor of this library, it is no longer easy to run individual test suites in isolation.  It used to be that one could at least run, for example, something like npx mocha [flags] test/core/interface/block.js in js-ipfs-api.
There is no way to do this anymore. All of the tests now run from one test file in the repos that consume this library.  I don't see that there's a readily documented way to isolate tests out, which makes development very slow as one has to run the entire test suite to work on one small feature and its subsequent tests.
I see that in examples, all of the isolation is done via code, meaning that one's best option currently would be to write a one-off, temporary test file that manually duplicates the testing you want to isolate.  One would have to remember to also remove this file before committing.  This doesn't seem very handy or straightforward.
Is there any plan or mechanism for running isolated tests either by command or feature set on the cli?

Made a PR in aegir that's an attempt at solving this

You're correct, running tests like this from the CLI is not possible anymore. You'll need to find the subsystem you want to isolate tests from in interface.js and add the only option as either an array or boolean, docs here.
I think your PR to AEgir is a good solution to restore this ability 👍

Just a thought but we could always move the each subsystem out of interface.spec.js and into their own files again - that would restore the feature. I only put them all in the same file because it's short and saves on boilerplate.

The Aegir PR solves this problem in an even more granular way than reverting the files would.

closing as https://github.com/ipfs/aegir/pull/252 has now been merged


self production of periodogram and phase-folded plot for high variability

When the AUTO_DETREND_ENABLED flag is activated, two plots corresponding to the periodogram and the phase fold  are produced via Lightkurve package. These plots are not optimal and they might be produced directly by SHERLOCK.


Add support for optional path parameters

Hapi supports optional parameters in a route's path, designated by a ? at the end of the parameter name.
The Swagger 2.0 spec does not allow optional path parameters:

Determines whether this parameter is mandatory. If the parameter location is "path", this property is REQUIRED and its value MUST be true. Otherwise, the property MAY be included and its default value is false.

This change allows for a valid Swagger 2.0 file to be generated from routes with optional path parameters by duplicating such routes and adjusting the parameter definitions to match.

Coverage remained the same at 100.0% when pulling 2f8b14b563dced6263a2a748d88c07ef312083e4 on lroggendorff:add-support-for-single-optional-path-parameters into d54f707c86f28ec60ad8a88e2c701b09bb5ff6ee on z0mt3c:master.

@JoshMock Funny you should ask... I wondered the same thing, and even started writing a test, and then upon getting an Invalid path error from Hoek decided to look it up:

It is important to be aware that only the last named parameter in a path can be optional.

Go fig. Now, if someone wants to adds support for multi-segment parameters... that'd be fun.

perfect... thanks!


Bad Request

Hi mate, thanks for awesome and simple guideline. I followed all steps and resolution also working without any issue. However, I am always getting "Bad Request" output no matters what URL type follow by domain name.
Can you please help ?

Was using https://URL instead http.
Thanks.


Monitor Candidate Data

Feature
Refer to existing functionality in Character Checks and ensure SETs can request data from candidates and track their responses. Also see Pre-selection day workflow and documentation.
Task list:

[ ] View status of candidate data requests (not requested, requested, started, completed)
[ ] Search candidates
[ ] Send (notify) requests to all
[ ] Send (notify) requests to custom selection
[ ] Send (notify) reminders to all candidates who haven't completed
[ ] Send (notify) reminders to custom selection
[ ] Continue / close the candidate forms

Miro Board
https://miro.com/app/board/uXjVNez9BuM=/?moveToWidget=3458764567208308949&cot=14

@nickaddy I will create the email templates on Notify. Do we have the content of the email templates:

Request of pre-selection day questionnaire
Reminder of pre-selection day questionnaire

@HalcyonJAC Can we unpack what the user is requesting here?


remove usage of config files, go to etcd

config files are against the stateless nature of our Zero-OS
we should do the following

move all configuration settings to etcd
each daemon (service) starts with list of etcd to work with & his own key

$pathToServiceBinary $ip1,$ip2,$ip3 $servicename $instancename
key generated = $servicename_$instancename (in relation to ays)

use watching of keys to see when config changes

https://coreos.com/etcd/docs/latest/learning/api.html#watch-api
if it changes reload
an also use this to send some commands to a daemon e.g. have in toml file: cmds section
suggested requirements

store config for each service as toml file
run max 5 etcd daemons (ays manages the setup of these daemons), they are in 1 cluster

todo

spec the required config formats per service e.g. nbdserver

store config for each service as toml file

Which service are we talking about here ?

an also use this to send some commands to a daemon e.g. have in toml file: cmds section
suggested requirements

Didn't get that, can you elaborate ?

Completely removing config file doesn't seems to be a good idea either. For developement we should be able ton configure ndbserver/tlog without the need of etcd which is more complex to deal with then configuration file.
But for production, etcd is indeed pretty cool.
Regarding the format of the configuration in etcd, I think we should stick with what we have.
Do you see any reason to change the current format ?

etcd is honestly very simple to deal with
not sure why config file would be harder
copy to etcd or copy to filesystem is +- same thing
On Mon, Jul 10, 2017 at 8:35 AM, Christophe de Carvalho <
<EMAIL_ADDRESS>wrote:

Completely removing config file doesn't seems to be a good idea either.
For developement we should be able ton configure ndbserver/tlog without the
need of etcd which is more complex to deal with then configuration file.
But for production, etcd is indeed pretty cool.
Regarding the format of the configuration in etcd, I think we should stick
with what we have.
Do you see any reason to change the current format ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zero-os/0-Disk/issues/316#issuecomment-314017903, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFvi1ICM_cMMV7CI0WauYWuX1hvLAdxdks5sMcY2gaJpZM4OSZ1U
.

--
Kristof De Spiegeleer
+971525609014 (my telegram account registered on this nr, best way to reach
me)
+201206927877
+32 475405474
skype: despiegk

As discussed in scrum:

Let's try to keep the config module as it is, as much as possible;
We'll need to support toml tags alongside the yaml tags, and whatever else of functionality toml requires;
It might still be useful to keep supporting loading a config from disk (for dev purposes), but the HotReloader can be refactored to start using stuff like the etcd watch feature to do the reloading instead;
Need to add functions to load a config from etcd;
Need to vendor a toml library and etcd lib;
Need to integrate etcd in the config module;
Ideally the rest of the codebase can remain unaware of this new config change, except for the parts where they actually load a config, or create the new HotReloader, as this will now require some etcd information I guess;

Also we'll need to figure out what information we'll require for etcd, is it just one address, a bunch of addressed? etc...

NOTE: in some scenarios the 0-Disk code also wants to updates the config. The only example of this is currently where in the tlogStorage we use the slave storage as the primary storage. Thus it should be possible to also have a function which allows to write a config object to etcd.

we'll need to figure out what information we'll require for etcd, is it just one address, a bunch of addressed ?

In practice we only need one etcd address since you can hit any etcd of the cluster, the data will be the same. AYS is aware of where the etcd runs, so we can pass a unique argument to the process, the address of one of the etcd.

Has to be some DNS than I guess, as that one address would be a critical point of failure. Because in case that one given server is down for whatever reason, the nbdserver would no longer have access to the etcd cluster. Or am I missing something here?

@GlenDC I think that as soon as connection is established with 1 node the etcd client will receive a list of the other nodes but will keep using the assigned node if the connection is good, if the connection goes down, the etcd client will round robin with the other nodes in the cluster as far as I read.

Has to be some DNS than I guess, as that one address would be a critical point of failure. Because in case that one given server is down for whatever reason, the nbdserver would no longer have access to the etcd cluster. Or am I missing something here?

No need for DNS, simple ip/port is enough.
Also I said one is enought, but we can pass the list of address of all of the etcd, it doesn't really matter.

I'm not too happy with the current direction PR #330 is going. So let's start again from the current config state in master, and take it from there.
First things first, what config is used how and where (ignoring hotreloading in this thought exercise, as it would distract too much)?

ardb:

BackendFactory: read: vdisk's tlogrpc;
Tlogstorage:

Switch ARDB Slave: write: vdisk's slaveStoragecluster as the `storageCluster;
HandleSighup: read: tlogrpc;

tlog:

server.vdisk:

manageSlaveSync: read: vdisk's slaveSync;

tlogserver.slaveSync.slaveSyncer:

initMetaRedisPool: read: storageCluster.Meta;

zeroctl (only reads):

Most commands require the vdisk's type and the storageCluster;

Based on this, I can tell that the entire config-user (tlogserver vs nbdserver) doesn't make sense, and we instead could split the data into four big parts:
// NOTE: names and specifics aren't too important,
// it's more about the idea

// used for any location which requires the basic vdisk info
type baseConf struct {
    BlockSize uint64
    ReadOnly  bool
    Size      uint64
    Type      VdiskType
}

// used for nbdserver storage purposes
type nbdConf struct {
    StorageCluster     StorageClusterConfig
    RootStorageCluster StorageClusterConfig
    RootVdiskID        string
}

// used for tlogserver storage purposes
type tlogConf struct {
    TlogStorageCluster StorageClusterConfig
    SlaveSync          bool
}

// used for backup storage purposes
type slaveConf struct {
    SlaveStorageCluster StorageClusterConfig
}

You'll see that I didn't just split up the vdisk config into 4 different configs, but I also don't refer any longer to a config name, this is to make things easier and simpeler. If you think the referring should still be a thing and what I'm doing here is stupid, feel free to justify and go for your approach.
But basically by splitting up the data we avoid a lot of messy design (such as the config user), and just use the config structs that we care about.
By splitting up the data, we can also have the config stored in ETCD as follows:

"<VdiskID>:conf" -> serialize(baseConf);
"<VdiskID>:conf:nbd" -> serialize(nbdConf);
"<VdiskID>:conf:tlog" -> serialize(tlogConf);
"<VdiskID>:conf:slave" -> serialize(slaveConf);

Using a naming scheme such as this, means we no longer require the keys to be known up front, and instead they can be dynamically generated whenever forever, based on the vdiskID.
Perhaps you have good reasons to think that splitting up the data is stupid, than you just need 1 key of course. Still doesn't take away that a naming scheme like this is the way to go, such that we can keep the nbdserver as stateless as possible.

I don't have a final design ready, but here is a direction towards a new design.
We could thing of the config as:
source: load -> deserialization -> validation -> data

If we somehow always store our content in the same format (e.g. toml) as a byte slice, we could probably define an interface which allows to implement sources. ETCD would be obviously the default implementation, also used for prod. But we could also keep supporting file configuration by adding a 2nd source which loads from a file.
Somehow I think if we serialize for all sources in the same format (e.g. toml) we could make an interface for source which simply serialized and deseiralises a byte slice
By having the data serialized as bytes, we can provide for all config data structs a constructor which creates the data given a byte slice. In these constructors we could then also provide the validation (as we do now as well in the config code of master), This way the consturctors will always guarantee that the loaded config files are correct.

Depending on the source, the hot reloading would work differently under the hood:

for the file config we use SIGHUP, as we do already (NOTE: as we only use the file config, you might want to drop the file config support for the file config);
for the ETCD config we would use the watch API for this.

The hot reload-ready data is used from 2 different approaches in the codebase:

Sometimes we don't know when an update will take place, and we just want to be able to use the latest config whenever it is loaded. In such case a subscribe model might fit better (and in fact that's what the master code dos for now.)
Othertimes we don't really care about when the config is updated, as we don't regularly require the config files. In such case we could just make sure to provide functions to get the vdisk conf, which should return the latest version at all times;

How the final API and design would look like, I don't know for now. I didn't have a lot of time today to think about this issue, but hopefully these thoughs give you some idea on the direction I want you to work towards in this issue.

Based on this, I can tell that the entire config-user (tlogserver vs nbdserver) doesn't make sense, and we instead could split the data into four big parts:

Just curious, why not do this data structure change in next iteration?
So, we can focus on files->etcd change for now.

Just curious, why not do this data structure change in next iteration?
So, we can focus on files->etcd change for now.

I'm only proposing because it will impact also how the Cairo team has to store the data on ETCD, so I would ratter prefer to keep to a solution and not have to change it in future milstones, unless it's required.
Also the config work related to implementing ETCD will change all those code parts anyhow, I don't see why not do it properly at once.
But the data struct split is just a proposal, I don't think the direction I want hangs or stands on that part, but I do think it would make it cleaner and simpeler. If you or @chrisvdg can come up with a better idea, than go for that one.

I like the idea of splitting the config.
This will prevent from having some duplicate values in etcd.
But indeed this kind of change will have a big impact on how we deal with configuration in the 0-orchestrator project.

@chrisvdg make sure to also update the documentation (only document ETCD config for now) first thing you do when you come in the office:
./docs/config.md:
# 0-Disk Configuration

// explain how config is modularized for each use case
// summarize what ETCD is and how we use it for configuration
// explain how we use a key pattern to store ETCD configs
// explain how we serialize and deserialize our configuration
// document, expose and explain the base config (include key pattern and use cases)
// document, expose and explain the nbd config (include key pattern and use cases)
// document, expose and explain the tlog config (include key pattern and use cases)
// document, expose and explain the slave config (include key pattern and use cases)

./docs/nbd/config.md:
# NBD Server Configuration

// summary `./docs/config.md` and link to that page for more information (tell also what the more information will be about).
// explain which subconfigs are used and how they are used within the nbdserver

./docs/tlog/config.md:
# TLog Server Configuration

// summary `./docs/config.md` and link to that page for more information (tell also what the more information will be about).
// explain which subconfigs are used and how they are used within the tlogserver

By doing it the first thing when you come in the office (and commit it to your PR branch), it would be ready for Jo. So that we can link it to him when I approved it.


Fix image pulling with Transfer service

https://github.com/containerd/containerd/pull/8062 and https://github.com/containerd/containerd/pull/8193 seem to have broken image pulling using ctr image pull --local=false. This PR attempts to address that.
The first issue is that the new OCIRegistry transfer types are not registered due to the missing import _ "github.com/containerd/containerd/pkg/transfer/registry". This results in the error
ctr: rpc error: code = Unimplemented desc = method Transfer not implemented for containerd.types.transfer.OCIRegistry to containerd.types.transfer.ImageStore

Once that's fixed, the next issue encountered on image pull is:
ctr: rpc error: code = Unknown desc = unable to initialize unpacker: snapshotter must be provided to unpack

This appears to be because the unpack.Platforms constructed in plugins/transfer/plugin.go do not have the Snapshotter or Applier fields set.
I don't think this PR is a complete fix (e.g. there appears to be no way to configure the SnapshotterOpts and ApplyOpts for the transfer service) and I'm not sure if it's correct (should we use the plugin.DiffPlugin or the DiffService plugin.ServicePlugin?). I primarily put this PR together so I could test pulling via the Transfer service in https://github.com/containerd/containerd/pull/8269

Thanks for the PR, I can take a look.

/ok-to-test

/ok-to-test


fix: glyph fitting in texture

Sometimes, depending on the parameters, the font doesn't fit the texture, making the result unusable.
This pull request is to fix this issue:

Used signedDistExtent() instead of mHeight/mWidth * ratioSpreadToGlyph() for initial glyph size calculation, to match computation in setSignedDist()

Added a ceil() to final glyph size calculation, to avoid potential overlap caused by rounding errors

For scale factor computation, reduce texture width/height by 1 pixel per glyph, to avoid exceeding boundaries because of rounding errors

Hi @GuB-42 -
Thanks for finding the problem and providing the solution.
The code changes look good and as soon as I get positive results from some tests on my side, I'll merge them.
Allow me some time as I'm traveling overseas now.
Thanks!

Hi @GuB-42 ,
Sorry for the belated reply (I was moving from Germany to Japan).
I tested it and it works great. I'm merging it now.
Thanks for the bugfix!
Sho


[Bug]: 2024.12.0 Breaks loxone.event_websocket_command

Describe the bug
It seems like the newest Home Assistant versions break my automations (which uses the PyLoxone: Send Websocket Command). Is this correct? I have rolled back my Home Assistant to 2024.11.3 and that works fine. This shouldn't have happend right? Or did I mis a breaking change?
This is the action of my automation:
data:   uuid: _UUID_   value: "{{ states('sensor._sensorname'_) |float }}" action: loxone.event_websocket_command
Firmware of your Miniserver
<IP_ADDRESS>
HomeAssistant install method
HAOS
Version of HomeAssistant
2024.12.0
Version of Pyloxone
0.7.1
Update pyloxone
This is the latest version right?
Log
Already rolled back my firmware and can't get the error log back (only if I update it again I think). There should be enough information in this issue. If not, please contact me!

Seems after updating PyLoxone (It didn't show that were any updates but after restarting and going to HACS there was a update). Then updating to Home Assistant 2024.12.0 it's seems to work again!


Implement Snapshot Testing/Something Similar to ensure either nothing is changing or changes are intended (phew!)

This is really moving!!
We have a lot of cooks in the kitchen now and maybe we should be building in some sort of testing on the final outputs before merging into main?  This way as we make changes the Pull Requests can help us catch little updates that might change the data examples in untoward ways??
I'm not sure if it is possible to set up snapshot testing here to check that outputs match previous outputs.  Or if there is some other method to help us capture the new static outputs and compare against the old outputs.
@ddsjoberg @cicdguy I think this is possible just never done anything like this outside of an R package.

hey hey @bms63 ! Which final outputs are you referring to?

I think the final dataset in each example or dataset used to display the output.
For example in https://pharmaverse.github.io/examples/adam/adpc.html

just checking that nothing changed at the end for adpc_xpt when a new change is applied in the repo.

@bms63 i'm hesitant to close another issue 😬 but i'm thinking this one might be overkill for an examples site?? i'd get such testing for something like the admiral templates, but these are just examples for people to play around with so the main CI check i care about each time would be with the latest CRAN packages does the example fail or fall over. what do you think? sorry, i'm being a bit strict today trying to channel my inner product owner!

all good to close!
My only hesitation is we don't have any detection for things being deprecated in our examples.  So functions could be outputting warnings without us knowing??

fair point! i'll try and keep an eye as will be checking periodically for any new releases as need to maintain the posit cloud package installations anyway, so if there are i could always do a quick test run when i make that update.

Maybe a Pull Request Template could be created to help give us some reminders on things to check??

Good idea - feel free to make an issue for this (and PR of course if you had time, but no pressure!)


Asset Library Supports Regex Search

Aws Connected Device Framework Affected Module(s):

I'm submitting a ...

[ ] bug report
[x] feature request

Description:

With the introduction of TinkerPop 3.6.x, it is now possible to search via regex, which should make it much easier to find matches. The request is to support this functionality by adding updating the minimum cluster version to <IP_ADDRESS>.R2, which includes TinkerPop 3.6 and updating the relevant CDF code to take regex input as an argument.
Current behavior:

CDF supports the ability to search, but doesn't support regex capability.
Expected behavior:

Steps to reproduce:

Additional Information:
Currently WIP on a branch in my fork.

Hi @anish-kunduru - Do you mind opening a PR of your WIP branch and we can discuss what's required to finish it/get it merged?

Hi @canavandl ,
In order for regex to work NeptuneDB engine version has to be <IP_ADDRESS>: https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases-<IP_ADDRESS>.html
However if we deploy CDF with Asset Library the Neptune version deployed is <IP_ADDRESS>
I'm working on a feature, where version can be specifies in addition to the instance family.
CC: @jaychung-aws
https://github.com/aws/aws-connected-device-framework/issues/170

PR is now ready: https://github.com/aws/aws-connected-device-framework/pull/179

Verified that this works E2E with a minor change on gremlin version[updated] just make sure https://github.com/aws/aws-connected-device-framework/pull/179 is merged first
CC: @jaychung-aws thanks for figuring out the issue

@canavandl I was out on vacation, so @joysl picked this up for me.
Does it make sense for us to combine Joyson's PR into this feature and merge both at the same time? We'll have to rebase to pull in the latest changes from master and I'd like to avoid doing that multiple times.


Remove brightness control?

Hi there
Many thanks for having developed this plugin.
Hoping you can clarify where the Feature Options (as shown on WebUI) are defined? It refers to Projects page but I can’t see anything there.
Also, is possible to disable brightness control? It’s of minor importance and the brightness read-out clutters up the Home interface. In fact, it would be nicer if single-tap switched the unit on/off and tap&hold brought up fanspeed slider. Right now every action requires min. 3 taps.
Also would obviously be nice if the fanspeed control could be a 3 step slider rather than one with granular control…but I presume Home doesn’t support that…?
Thanks again - great plug-in!
robin

Ah, hadn’t realised it’s a grouped accessory! Ungrouping has addressed most of points I raised. Thank you.


Log-on screen has the old Buddycloud logo.

New logos are at https://drive.google.com/open?id=0B8fJyujQqIAJU2JNbk5GUi1uaEk&authuser=1

perhaps easier for you:
http://janlindenberg.net/buddycloud/style-guide.html#identity-logo (see: android launcher icons)

Changed the app launcher and logo on the login screen.
Fixed the adjustResize screen issues with keypad.


Close App With Esc Key

Added a line that closes the app when the escape key is pressed.

No, this isn't how app.exec_() works. Besides, the segfault seems to have been fixed already.


Only update modified fields for datastore entities

When datastore entities are changed, only the modified fields need to be updated in datastore.

Is this still current?
Which sample are you referring to?

Bookshelf is being replaced


Custom download generator don't have body{} in min.css

Hey guys,
I download the custom bootstrap from the site with all options, but in min.css don't have the body{} element...

Just checked this, bootstrap.min.css includes the same body style as bootstrap.css.
@media (max-width: 980px) {   body {     padding-top: 0;   }   ... }

I noticed this last night as it doesn't include a default font family without the body tag. Not sure if this was intentional or not...

No, this block of code don't appear:
  margin: 0;
  font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;
  font-size: 13px;
  line-height: 18px;
  color: #333333;
  background-color: #ffffff;
}

Oh I see. I thought you were referring to a discrepancy between the two .css files.

@dwightwatson Doesn't appear to be intentional. The other type declarations are in there.

Yes, it's a important fix.

Looks like the following files are in the /less folder but not listed as CSS components on the download page:

hero-unit.less
mixins.less
patterns.less
print.less
scaffolding.less
variables.less

I'm assuming some are included by default (mixins.less, variables.less), not sure on the others. @fat can you confirm this?
scaffolding.less contains the body styles you're after.
patterns.less and print.less are also excluded from the master bootstrap.less file.

even if you customize the "@linkColor" or "@baseFontFamily" in the customize variables section, the "scaffolding.less" file is still not included so all links look pretty bad and the body variables are missing.

Also missing are a and a:hover selectors (seems like scaffolding.less might be missing from the "Customise" build)

Any fix for this yet?

yep @cgunther is right - we'll get a fix for you guys asap

Just pushed an update for this, sorry for the problems, folks. We've added the scaffolding and hero unit files back and just updated the docs. Print and patterns were not meant to be included, so we've striped those out as we never compiled those master.
Mixins and variables aren't optional—those are included by default for every build, no need to specify. We'll update the docs to reflect this soon.


chore(Labs): Flattens labs file structure [GM-201]

Overview
Removes the distinction between brand / experimental to make this a blanket component library.

Flattens labs to a single level structure brand and experimental.
Flattens other index files.

PR Checklist

[ ] Related to designs:
[x] Related to JIRA ticket: GM-201
[x] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.29-alpha.69de15.0@codecademy/gamut-labs@13.5.6-alpha.69de15.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut-kit@0.3.29-alpha.33a1aa.0@codecademy/gamut-labs@13.5.6-alpha.33a1aa.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://607c94bc20bfc4002a542e44--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.3.29-alpha.514e9e.0@codecademy/gamut-labs@13.5.6-alpha.514e9e.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://607d85868a19395ffa2841d0--gamut-preview.netlify.appDeploy Logs


Question about annotations.txt

Hey,
great repo! thank you!
Just a question about annotations.txt. Am i right in the assumption that if I do NOT include a datapoint in annotations.txt, it will not be included in the dataset although it is in the same folder? Is this correct? That would be great for things like cross validation.
And by the way, the pytorch-lightning version that works with the repo in 2023 is 1.7.7(at least for me). Maybe include that in readme
All the best!

Hi! Thanks for the message!
Yes, you are right. If a datapoint is not included in annotations.txt, it
will never be included in the dataset, even though the data is in the same
folder.
Also, thanks for the heads up about the pytorch lightning version! I should
update the readme soon about stuff like that again. Its been a while!
Thanks. Hope my repo helps you with your work!
El El lun, 13 feb 2023 a la(s) 12:35, staniPetrox @.***>
escribió:

Hey,
great repo! thank you!
Just a question about annotations.txt. Am i right in the assumption that
if I do NOT include a datapoint in annotations.txt, it will not be included
in the dataset although it is in the same folder? Is this correct? That
would be great for things like cross validation.
And by the way, the pytorch-lightning version that works with the repo in
2023 is 1.7.7(at least for me). Maybe include that in readme
All the best!
—
Reply to this email directly, view it on GitHub
https://github.com/RaivoKoot/Video-Dataset-Loading-Pytorch/issues/20,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHCGB33U6QDHTZXKMTK2OITWXJWGXANCNFSM6AAAAAAU2RWFBQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


ZARF removes namespace labels pertaining to pod security when using --adopt-existing-resources

Environment
Device and OS:
App version:  0.33.1
Kubernetes distro being used: rke2 1.28.9
Other:
Steps to reproduce

Create a namespace with the labels required to allow a pod to have privileges when restricted pod security context is enabled per CIS benchmark
Deploy an app (in our case mattermost-team-edition) via helm to that namespace
Create a zarf package for the app and deploy it with --adopt-existing-resources
The pods will not be scheduled due to security context violations and the labels will have been removed from the namespace

Expected result
The existing labels that do not interfere with ZARF remain
Actual Result
Existing labels pertaining to pod security are removed
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Additional Context
Add any other context or screenshots about the technical debt here.

Confirmed this is a bug, thanks!