error: 3801 bytes of body are still expected when installing

Operating system and version: Raspbian 11 lite, running on a pi zero W
nvm debug output:

(nothing, nvm isn't installed)

nvm ls output:

(nothing, nvm isn't installed)

How did you install nvm?

Using curl, $ curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
What steps did you perform?
Just ran that, and it failed
What happened?
It failed, logging the following:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 16555  100 16555    0     0  19250      0 --:--:-- --:--:-- --:--:-- 19250
=> Downloading nvm from git to '/home/pi/.nvm'
=> Cloning into '/home/pi/.nvm'...
remote: Enumerating objects: 365, done.
remote: Counting objects: 100% (365/365), done.
remote: Compressing objects: 100% (314/314), done.
error: 3801 bytes of body are still expectedB | 16.00 KiB/s
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: index-pack failed
Failed to clone nvm repo. Please report this!

What did you expect to happen?
It installing normally, without errors
Is there anything in any of your profile files that modifies the PATH?

Nothing afaik

If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?

*   Trying <IP_ADDRESS>:443...
* Connected to nodejs.org (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=*.nodejs.org
*  start date: Feb  3 00:00:00 2023 GMT
*  expire date: Mar  5 23:59:59 2024 GMT
*  subjectAltName: host "nodejs.org" matched cert's "nodejs.org"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x2b5d70)
> HEAD /dist/ HTTP/2
> Host: nodejs.org
> user-agent: curl/7.74.0
> accept: */*
> accept-encoding: deflate, gzip, br
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
< HTTP/2 200
HTTP/2 200
< date: Tue, 02 Jan 2024 21:22:46 GMT
date: Tue, 02 Jan 2024 21:22:46 GMT
< content-type: text/html
content-type: text/html
< cache-control: public, max-age=3600, s-maxage=14400
cache-control: public, max-age=3600, s-maxage=14400
< last-modified: Tue, 02 Jan 2024 15:35:21 GMT
last-modified: Tue, 02 Jan 2024 15:35:21 GMT
< cf-cache-status: HIT
cf-cache-status: HIT
< age: 7627
age: 7627
< vary: Accept-Encoding
vary: Accept-Encoding
< strict-transport-security: max-age=31536000; includeSubDomains; preload
strict-transport-security: max-age=31536000; includeSubDomains; preload
< x-content-type-options: nosniff
x-content-type-options: nosniff
< server: cloudflare
server: cloudflare
< cf-ray: 83f60f2d8e9b06e9-LHR
cf-ray: 83f60f2d8e9b06e9-LHR
< content-encoding: br
content-encoding: br

<
* Connection #0 to host nodejs.org left intact

Can you confirm how much disk space is available?

to be honest I only just saw your reply and I don't have access to that pi anymore, so I really can't help
I'll leave it open in case anyone else has the same issue and can fix it

ok, I’ll close for now then; happy to reopen if you or someone else can repro


TubiTv - R-rated does not work

Checklist

[X] I'm reporting a broken site support issue
[X] I've verified that I'm running youtube-dl version 2021.05.16
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar bug reports including closed ones
[X] I've read bugs section in FAQ

Verbose log

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://tubitv.com/movies/589923/hedwig-and-the-angry-inch?start=true']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2021.05.16
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.19041
[debug] exe versions: ffmpeg N-102417-g7539a01bb0, ffprobe N-102417-g7539a01bb0
[debug] Proxy map: {}
[debug] Using fake IP [-deleted this-] (US) as X-Forwarded-For.
[TubiTv] 589923: Downloading JSON metadata
[TubiTv] 589923: Downloading m3u8 information
Traceback (most recent call last):
  File "__main__.py", line 19, in <module>
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp8rlhijs0\build\youtube_dl\__init__.py", line 475, in main
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp8rlhijs0\build\youtube_dl\__init__.py", line 465, in _real_main
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp8rlhijs0\build\youtube_dl\YoutubeDL.py", line 2069, in download
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp8rlhijs0\build\youtube_dl\YoutubeDL.py", line 808, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp8rlhijs0\build\youtube_dl\YoutubeDL.py", line 815, in wrapper
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp8rlhijs0\build\youtube_dl\YoutubeDL.py", line 836, in __extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp8rlhijs0\build\youtube_dl\extractor\common.py", line 534, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp8rlhijs0\build\youtube_dl\extractor\tubitv.py", line 80, in _real_extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp8rlhijs0\build\youtube_dl\extractor\common.py", line 1643, in _extract_m3u8_formats
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp8rlhijs0\build\youtube_dl\extractor\common.py", line 667, in _download_webpage_handle
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp8rlhijs0\build\youtube_dl\extractor\common.py", line 629, in _request_webpage
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp8rlhijs0\build\youtube_dl\utils.py", line 2158, in sanitized_Request
  File "C:\Python\Python34\lib\urllib\request.py", line 267, in __init__
  File "C:\Python\Python34\lib\urllib\request.py", line 293, in full_url
  File "C:\Python\Python34\lib\urllib\request.py", line 322, in _parse
ValueError: unknown url type: ''

I did delete the ip, don't know if I am suppose to when posting here?
Description

It does not want to download R-rated movies, however other movies does work.

the firefox addon called the stream detector will grab the m3u8 files but the
film will not download because it is DRM protected.

How weird only r-rated movies has drm. In that case it's not much to do.

Issue should be closed, URL is dead


Delayed Job Tests

Add integration tests for the delayed job integration.
I've added a step to maze to be able to build the current gem and put that into the test docker container. At the moment that invalidates the build because I'm guessing the gem contains the build time - so we need to fix that.
Once we have the framework up and running adding the rests of the tests should be easy.

I've taken this up, fixed the existing Maze-tests and added a couple of features to the Delayed job tests.  As these tests aren't currently running on CI, reviewers should manually run the delayed_job feature.


⚠ Jenkins Plugins Artifactory has degraded performance

In 5f90bfc, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1287 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 97c9538 after 26 minutes.


Cluster the FS on ASCS server

Hi,
As per SAP's earlier traditional concept, where /sapmnt/.... & /usr/sap.... were itself on ASCS
cluster itself and not had any dedicated NFS server for those mount point. Any specific reason why HA for SAP, Azure recommend for having dedicated NFS cluster server for those mount points rather than building cluster file system on ASCS/SCS server itself which will help to bring Single point of failure as ASCS, otherwise in case where we have ASCS and NFS both running on 2 different cluster it become single point of failure as ASCS and NFS as well.
Thanks, Anil

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5d2a9d09-f0f0-f02a-dfc6-f9562c0d66ec
Version Independent ID: f7c0b99d-daae-5616-ab57-ff256d65bc2a
Content: Azure Virtual Machines high availability for SAP NetWeaver on SUSE Linux Enterprise Server for SAP applications
Content Source: articles/virtual-machines/workloads/sap/high-availability-guide-suse.md
Service: virtual-machines-windows
GitHub Login: @MSSedusch
Microsoft Alias: sedusch

@anilbsap To assist you better on your query could you provide us with the link to the document you are referring to ?
In case your query in not related to document content, open a new forum thread either in MSDN or StackOverflow as it could be better place to get help on your scenario where the community members could provide their expert guidance to you based on their experience.

Please find the below Azure link which refers to NFS cluster for ASCS instance.
https://docs.microsoft.com/en-gb/azure/virtual-machines/workloads/sap/high-availability-guide-suse
Also, find the RHEL document which talks about FS cluster is will be ASCS server itself, whereas we don't need separate NFS server. (point no: 4.2.2)
https://access.redhat.com/articles/3150081#ascs-ers-with-shared-filesystems-managed-by-cluster
So I am not clear why a separate NFS cluster is needed for SAP ASCS requirement, as there is no clear statement written about it.

@MSSedusch Can you please share your insights on this customer's query? Thanks :)

@anilbsap mixing the Pacemaker configuration of the SAP NetWeaver (A)SCS and the NFS server is not supported by SUSE or Red Hat. In some situations, having the NFS server and the ASCS in the same Pacemaker cluster can lead to blocking situations that would result in a hanging ASCS stop process. If you want to get rid of the NFS server, you can use Azure NetApp files as described in this article: https://docs.microsoft.com/azure/virtual-machines/workloads/sap/high-availability-guide-suse-netapp-files

Thanks @MSSedusch
@anilbsap Let us know if that helped answer your question.
We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


⚠ SceneTime has degraded performance

In ca60929, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1163 ms

Resolved: SceneTime performance has improved in a9983f6 after 6 minutes.


Add vcxproj targeting Android and update code to support build

This adds an Android-specific vcxproj and updates the code to support building Android/ARM. This does not contain any concrete implementation for http calls yet, but should be the infrastructure needed for both iOS and Android versions of the library.

@brianpepin, can you review these files?

Refers to: Source/Task/AsyncLib.cpp:3 in f74d27c. [](commit_id = f74d27c21bdb0fe0c3162b20dfed384688568fc9, deletion_comment = False)

Reviewed.  The only thing I’d request changing is to not return HC errors from async lib.  There are three error codes that were defined.  Instead, I’d define these as top level E_ error codes like you already do for things like E_INVALIDARG, and we’ll work on getting them also defined in the Windows headers.
From: Jason Sandlin<EMAIL_ADDRESS>Reply-To: Microsoft/libHttpClient<EMAIL_ADDRESS>Date: Wednesday, April 25, 2018 at 5:09 PM
To: Microsoft/libHttpClient<EMAIL_ADDRESS>Cc: Brian Pepin<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Microsoft/libHttpClient] Add vcxproj targeting Android and update code to support build (#139)
@brianpepinhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbrianpepin&data=02|01|brianpe%40microsoft.com|563f4671a2264cba2d2a08d5ab09f0d6|72f988bf86f141af91ab2d7cd011db47|1|0|636602981538282061&sdata=vqmDvHl0T7CCRM21HDN1Ca4gaFnsXyAGtRi%2F%2F%2Fc90rE%3D&reserved=0, can you review these files?

Refers to: Source/Task/AsyncLib.cpp:3 in f74d27chttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FlibHttpClient%2Fcommit%2Ff74d27c21bdb0fe0c3162b20dfed384688568fc9&data=02|01|brianpe%40microsoft.com|563f4671a2264cba2d2a08d5ab09f0d6|72f988bf86f141af91ab2d7cd011db47|1|0|636602981538282061&sdata=qEOcTrKyXKTLb1XoFwoKA0ikSfYvvv%2FWfrE%2BFZbW6nc%3D&reserved=0. [](commit_id = f74d27chttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FlibHttpClient%2Fcommit%2Ff74d27c21bdb0fe0c3162b20dfed384688568fc9&data=02|01|brianpe%40microsoft.com|563f4671a2264cba2d2a08d5ab09f0d6|72f988bf86f141af91ab2d7cd011db47|1|0|636602981538292066&sdata=wiGuMe06e5QMWCbFlL%2FRJR3%2BLwhFBfPGa8LDJGTDl7M%3D&reserved=0, deletion_comment = False)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FlibHttpClient%2Fpull%2F139%23issuecomment-384471660&data=02|01|brianpe%40microsoft.com|563f4671a2264cba2d2a08d5ab09f0d6|72f988bf86f141af91ab2d7cd011db47|1|0|636602981538292066&sdata=r%2B8ZYHKMARMaEYmnx1MzjF7TF0IOg%2F59Er7kvT2QUDc%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJuzbgKt2hVWlRCmNvKGh_zhePqYyIleks5tsRAogaJpZM4TkUsP&data=02|01|brianpe%40microsoft.com|563f4671a2264cba2d2a08d5ab09f0d6|72f988bf86f141af91ab2d7cd011db47|1|0|636602981538302071&sdata=zG8jCP19lIikSkt%2FhpoTTIlaEGXFpbhSTaf8JczxCA0%3D&reserved=0.


feature: Support find

Contact Details
<EMAIL_ADDRESS>Feature Description
Add find to the managed packages
Why?
Allows searching in filesystems
What-should happen?
find should be a package in the index.json
Steps to Test

jq '.packages[] | select(.name = "find")' resources/install/index.json should return the details for managing the find package

Code of Conduct

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

https://ioflood.com/blog/install-find-command-linux/


Use integration strategy squash

[x] This only affects the JavaScript OpenTelemetry library
[ ] This may affect other libraries, but I would like to get opinions here first

I propose to use integration strategy squash also here link in api and core repo.

@Flarna just changed, thx for noticing


Call site argument dataflow

When input code is this:
1 void myfunc()
2 {
3     int a = 42;
4     foo(a);
5     bar(a);
6 }

I get REACHING_DEF edges (written by line number here):
3 -> 4
4 -> 5

I was expecting edges:
3 -> 4
3 -> 5

That is, I expected line 3 to be a def and lines {4,5} to be use, but it appears line 4 is counting as a def of a.
Is the behavior I am observing correct / expected (if so, why?) ? Or is this a bug?
Here is a joern query you can run to get the same result:
joern> cpg.graph.edges("REACHING_DEF").foreach((e: Edge) => { println(s"${e.outNode.propertyMap.get("LINE_NUMBER")}: ${e.outNode.propertyMap.get("CODE")} -> ${e.inNode.propertyMap.get("LINE_NUMBER")}: ${e.inNode.propertyMap.get("CODE")}")  })

3: a -> 4: a
3: a -> 3: a = 42
3: 42 -> 3: a = 42
3: 42 -> 3: a
4: a -> 5: a
4: a -> 4: foo(a)
5: a -> 5: bar(a)

Thanks!

Hi! Yes, this is correct. In the PDG we generate, we overtaint severely, and we then use semantics at query-time to ignore defs. I'll be writing a detailed article about this soon, and since you're the third person to ask about this this week alone, I think a decent API to retrieve DDG edges according to the data flow semantics is in order.

Great, thanks for the clarification! If it makes sense to you, just adding additional "DDG" edges similar to the "CDG" edges would be pretty intuitive, at least in my usage of the library thus far, along with the brief explanation of difference between REACHING_DEF and DDG edges. Thanks again!

Related: https://github.com/ShiftLeftSecurity/joern/issues/333

Work-in-progress PR at https://github.com/ShiftLeftSecurity/codepropertygraph/pull/958

Update: one can now traverse the DDG backwards step by step, taking into account the semantics. The plotting code also takes into account semantics now. I'll move to fixing the script for PDG export, as that seems to be a common use case.

https://github.com/ShiftLeftSecurity/codepropertygraph/pull/963

@fabsx00 I revisited this today. My understanding is that I can now define semantics that contain a list of function names and the dataflow pattern for each argument, then use something like dotDdg to generate edges. I tried this for the example above. I add the semantics rule: "foo" 1->-1. However, I still get the same edges reported in the first post. Is this still the expected behavior, or is there a path to getting the expected edges (i.e. someway to indicate that a parameter is not DEF'd in the call)?
Thanks!

How are you retrieving edges? If you're looking at all REACHING_DEF edges, then that will not take into account semantics. dotDdg on the other hand should now return the edges, taking into account the semantics.

Here is what I did:
./joern-parse myfunc.c
importCpg("cpg.bin")
import io.shiftleft.dataflowengineoss.semanticsloader.{Parser, Semantics}
implicit val s = Semantics.fromList(new Parser().parseFile("../ddg.semantics"))
cpg.method.name("myfunc").dotDdg.l.head

Where ddg.semantics contains:
"<operator>.assignment" 2->1
"<operators>.assignmentAnd" 2->1 1->1
"<operators>.assignmentArithmeticShiftRight" 2->1 1->1
"<operator>.assignmentDivision" 2->1 1->1
"<operators>.assignmentExponentiation" 2->1 1->1
"<operators>.assignmentLogicalShiftRight" 2->1 1->1
"<operator>.assignmentMinus" 2->1 1->1
"<operators>.assignmentModulo" 2->1 1->1
"<operator>.assignmentMultiplication" 2->1 1->1
"<operators>.assignmentOr" 2->1 1->1
"<operator>.assignmentPlus" 2->1 1->1
"<operators>.assignmentShiftLeft" 2->1 1->1
"<operators>.assignmentXor" 2->1 1->1
"<operator>.postDecrement" 1->1
"<operator>.preDecrement" 1->1
"<operator>.postIncrement" 1->1
"<operator>.preIncrement" 1->1
"<operator>.memberAccess" 1->-1
"<operator>.indirectComputedMemberAccess" 1->-1
"<operator>.indirectMemberAccess" 1->-1
"<operator>.computedMemberAccess" 1->-1
"<operator>.indirection" 1->-1
"<operator>.addressOf" 1->-1
"<operator>.fieldAccess" 1->-1
"<operator>.indirectFieldAccess" 1->-1
"<operator>.indexAccess" 1->-1
"<operator>.indirectIndexAccess" 1->-1
"<operator>.pointerShift" 1->-1
"<operator>.getElementPtr" 1->-1
"<operator>.addition" 1->-1 2->-1
"<operator>.conditional" 2->-1 3->-1
"foo" 1->-1

And here is the output:
res3: String = """digraph myfunc {
"1000108" [label = "(<operator>.assignment,a = 42)" ]
"1000109" [label = "(IDENTIFIER,a,a = 42)" ]
"1000110" [label = "(LITERAL,42,a = 42)" ]
"1000111" [label = "(foo,foo(a))" ]
"1000112" [label = "(IDENTIFIER,a,foo(a))" ]
"1000113" [label = "(bar,bar(a))" ]
"1000114" [label = "(IDENTIFIER,a,bar(a))" ]
"1000105" [label = "(METHOD,myfunc)" ]
"1000115" [label = "(METHOD_RETURN,void)" ]
  "1000109" -> "1000108"  [ label = "a"]
  "1000110" -> "1000108"  [ label = "42"]
  "1000110" -> "1000109"  [ label = "42"]
  "1000105" -> "1000109"
  "1000105" -> "1000110"
  "1000112" -> "1000111"  [ label = "a"]
  "1000109" -> "1000112"  [ label = "a"]
  "1000105" -> "1000112"
  "1000114" -> "1000113"  [ label = "a"]
  "1000112" -> "1000114"  [ label = "a"]
  "1000105" -> "1000114"
  "1000105" -> "1000115"
}
"""

I was expecting an edge from 1000109 -> 1000114.

What you're doing looks correct. Let me look into it.

It looks like semantics are not correctly picked up in joern while they are picked up correctly in the codepropertygraph unit tests. Looking into this now. Thanks for reporting, seems like a bug.

Confirmed, this is a problem that isn't in the data flow tracker but rather in passing semantics to the tracker. Slight relieve there, otherwise I would have started questioning those unit tests.

Ok, I understand the problem now.  That idea of just following incoming REACHING_DEF edges while honoring the semantics to then obtain a nice DDG is a bit flawed. I failed to take into account the visible field in the path elements. This shouldn't be hard to fix though.

This should fix it: https://github.com/ShiftLeftSecurity/codepropertygraph/pull/968
Bringing into joern...

Confirmed to work in joern in a local deployment, however, the Semantics implicit needs to be set by hand (as you do in your example). This needs to be fixed, but I'll do that in a separate PR.

@kzsnow the problem should be fixed on joern's current master. Could you take a look? If it works, we can close the ticket. I'm hoping to find time soon to clean up the generated DDGs a bit. In particular, it would probably be nicer to draw edges from calls to calls, now that edges are labeled with the variable that is propagated.

@fabsx00 It works, yay! Feel free to close the issue!
Is it the case that by default call arguments arguments will be treated as defs, unless specifically added to the semantics to indicate otherwise? I am envisioning some type propagation to try and give a best guess based on whether the argument type is a pointer.
Would it be possible to give a quick example of using ddgIn or ddgPathElement to get a list of edges similar to the dotDdg output? Those I could not figure out :-)

Yes, by default, we assume that calls to methods taint their arguments. I know I've promised an article about this, which I haven't gotten to, but the intuition is that this makes sense for exploratory code analysis because it will by default return longer more detailed flows containing calls to escaping routines, even if these escaping routines are external methods that have not been annotated with a semantic.
For ddgIn/ddgPathElem, the unit tests in this PR show how it is used. I've also polished the API a bit.
https://github.com/ShiftLeftSecurity/codepropertygraph/pull/969

https://github.com/ShiftLeftSecurity/codepropertygraph/pull/973

@kzsnow this may be of interest to you as well: https://github.com/ShiftLeftSecurity/joern/pull/357


Deprecation warning upon installing project

Describe the bug
It's coming from svelte-check -> svelte-preprocess -> sorcery -> sourcemap-codec
Reproduction
I installed the demo app with TypeScript support and then ran npm install
Logs
npm WARN deprecated<EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead

System Info
latest

Severity
annoyance
Additional Information
No response

Hmm https://www.npmjs.com/package/sorcery hasn't been updated in 7 years. It sounds a bit like magic-string. Was it a precursor to it?

no, totally separate. i'll update the package to use @jridgewell/sourcemap-codec

Just please don't remove commonjs at the same time 😅 svelte-preprocess which depends on it is commonjs so couldn't use it if it became esm.

lol i was about to do exactly that. i guess i can add a prepublish esbuild step since it only exports default

CJS can use ESM code though. It shouldn't be an issue should it? I would still make it ESM-only personally. We should probably update svelte-preprocess to be ESM as well anyway

I mean you could do minor release to swap out the package and then another major release to remove commonjs; svelte-preprocess and all other commonjs modules can then happily use the previous major version without getting deprecation warnings

it's a 7 year old package — one does not simply swap things out... it needs some fairly drastic surgery to get things back into a publishable state (you can't even run npm install in that repo as things stand)

CJS can use ESM code though

nope, other way round

import() is synchronous, and you can't use top-level await in CJS. in certain circumstances that's okay but not in the general case. if the goal is to make a library consumable by CJS consumers you can't rely on that

My hope would be that, since you only need to swap out the depending package (it has the same signature AFAIK), you wouldn't need to touch anything else.

That was my hope too!

ok fuck it, this was taking too long. i swapped out the packages and did the minimal changes necessary to get it to publish — the tests don't pass, and the package is a mess, but at least we can get rid of the deprecation warning now

This should be good to go now with the release of<EMAIL_ADDRESS>


Fix html reporter with more than one embedded screenshot

Summary
There was typo in #next_id method: @indices used incorrect key for incrementing screenshot number (:type as a symbol instead of type as a variable). It was lead to confusion when every screenshot in reporter pointed to the same image id.
How Has This Been Tested?
formatter/html_spec.rb has been extended to cover a case with more than one screenshot in html-report.
Screenshots (if appropriate):

Types of changes

[ ] Refactor (code change that does not change external functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] I've added tests for my code
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Looks like failed scenarios is not related to my changes. Anyway, I performed bundle exec rake locally and it has been passed successfully.

@olleolleolle thanks!

@nonkor Thanks for sticking with it!

Hi @nonkor,
Thanks for your making your first contribution to Cucumber, and welcome to the Cucumber committers team! You can now push directly to this repo and all other repos under the cucumber organization! 🍾
In return for this generous offer we hope you will:

✅ Continue to use branches and pull requests. When someone on the core team approves a pull request (yours or someone else's), you're welcome to merge it yourself.
💚 Commit to setting a good example by following and upholding our code of conduct in your interactions with other collaborators and users.
💬 Join the community Slack channel to meet the rest of the team and make yourself at home.
ℹ Don't feel obliged to help, just do what you can if you have the time and the energy.
🙋 Ask if you need anything. We're looking for feedback about how to make the project more welcoming, so please tell us!

On behalf of the Cucumber core team,
Aslak Hellesøy
Creator of Cucumber


Request: Push a new tag

I'm submitting a ...

[ ] bug report
[x] feature request

What is the current behavior?
This repository hasn't had a new tag pushed since October 2022, but there have been several PRs and dependency updates merged since then. I was going through my pre-commit hooks and noticed this one hasn't had an update in quite a while.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
N/A

What is the expected behavior?
N/A

What is the motivation / use case for changing the behavior?
Stay up to date on new changes.

Please tell us about your environment:

detect-secrets Version: N/A
Python Version: N/A
OS Version: N/A
File type (if applicable): N/A

Other information

Thank you for maintaining this pre-commit hook.

@jmctune you're most definitely right. We're aware of this and I can promise you that we'll make a release by the end of this month. Apologies again, but we've been quite busy in the past months.

@jmctune detect-secrets v1.5 is out! I'll close this issue, but thank you again for your patience!


Update userstyles.md

@ParmuzinAlexander Nice job! Sabaki is getting official themes, so I'm no longer listing plain userstyles in the documentation. But it's very easy to make a theme from userstyles, check the guide for instructions. You're welcome to send in pull requests for themes.


Fix syntax error: change 'header' to 'headers'

Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

Registered github account. CLA check should pass now.


Lots of warning and errors compiling V2

Ive downloaded the 'V2' RuntimeMeshComponent_v2.0, when compiling with unreal 4.17 this gives a bunch of erros and warnings, while the master seems to be working okay.
Did i missed anything? is the current Master V2.0?

RMC 2.0 is incompatible with 4.16+

Seems i actualy have 2.1 !

Thanks for notifying! I also got 2.1 now and it compiles perfectly. )

Hello,
All existing issues for RMCv2 are being closed as RMCv2 is no longer being supported.  RMCv3 is in beta here : https://github.com/Koderz/RuntimeMeshComponent/tree/Version3Dev
If you encounter this or any new issues in v3 please feel free to open a new issue!
Thanks!
-Koderz


[Hugging Face Demo] Provide a InternLM-20B-Chat Demo

https://huggingface.co/spaces/BridgeEight/internlm-20B-chat-w4-turbomind

error?
bridgeeight-internlm-20b-chat-w4-turbomind.hf.space’s server IP address could not be found.

@MJIMMYA sorry, I didn't get it.
Are you requesting us to deploy an InternLM-20B-Chat model on hugging face, or reporting an issue?


Fix nullability warnings

This fixes the following warnings in several places if the consuming project does not define enable:

[CS8632] The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

Note that this is not technically required in all *.pp files (only required in NullabilityInfo.cs and NullabilityInfoContext.cs) but it doesn't hurt to explicitly specify it should nullable reference types be used in the future.

thanks. deployed

The re sync commit (1b82b188d97d19b03e0fc161e6b726677a881fb9) reverted the #nullable enable pragma in NullabilityInfoContext.cs.pp. As a result, there are still warnings when consuming the NullabilityInfo NuGet package from a project that doesn't have <Nullable>enable</Nullable>.

I did not realize that NullabilityInfoContext.cs.pp and NullabilityInfo.cs.pp were automatically synchronized from the .NET repository. I submitted #5 which addresses the sync issue.


component-adapter: update the adapt command in readme

--adapt flag needs to specify the name of the module

Thanks! The wasm-tools subcommand should infer the name of the adapter from the name of the file, though, so in this example in the README I don't think it's necessary?

Thanks! The wasm-tools subcommand should infer the name of the adapter from the name of the file, though, so in this example in the README I don't think it's necessary?

I saw https://github.com/bytecodealliance/wasm-tools/pull/1065, good idea


Assigning clusters to workspaces does not work (Fleet)

Related: https://github.com/rancher/dashboard/issues/4798
Summary:

If I try to assign any cluster to a Workspace I created the modal is stuck when I try to add it with "Applying..." and never completes. In the browser dev console we see a TypeError.

Environment:
Rancher version: v2.6-head 39cecf0 12/17/2021
Rancher cluster type: single-node docker install
Docker version: 20.10
Downstream cluster type: RKE2
Downstream K8s version: 1.21
Steps to Reproduce:
0. Have rancher installed and at least one downstream rke2 cluster.

Create a fleet workspace. Note during this process you will get an error due to the related bug, https://github.com/rancher/dashboard/issues/4798.
Now, navigate to the Clusters page (under Continuous Delivery) and click the checkbox for it. Click the "Assign to..." button. Try to assign it to the workspace.

Expected Result:
Assigns without any issues.
Actual Result:
The modal gets stuck and we see a TypeError in the browser dev console.
Additional Info:

I can reproduce this on additional environments on latest v2.6-head, but on those I get a slightly different TypeError like:

Rancher version: 2.6-head 981fbc8
Rancher cluster type: HA
Downstream cluster type: aws ec2 node cluster
Downstream K8s version: v1.21.7

was able to assign a cluster to a workspace
https://user-images.githubusercontent.com/40282141/146614365-1db1dade-e104-4da8-b970-ea15253dc9b7.mp4

Latest v2.6-head b4d83fb
I have 2 HA setups now that reproduce and 2 single-node docker setups that reproduce. Gary and team are looking into the issue.

on 2.6.3-rc8

No error seen when assigning clusters to workspaces
Assigned multiple clusters to different workspaces successfully


Configuration global

I think changing Vue.vueDragula to Vue.dragula for to global settings object would be a nice tweak as it is more readable.
Super minor detail but am a fan of clean readable code.

Sounds good, but this will be a breaking change. May be put this on version 2.0


Encounters, vitals, panels... way after death

I don't know if this happens a lot or if I just got lucky -- but I was looking at a patient and noticed her deceasedDateTime was "1992-08-05T00:53:26-04:00", but she had several encounter, observations, and panels from 1993.  The file is attached (w/ txt extension so GitHub allows it).
Jodie811_Leffler128_0de37a5a-b57c-4871-afc8-c819f8567cbc.json.txt
This was generated from current master branch.

In the docs for the death state this behavior is explained.
Implementation Warning: If a Death state is processed after a Delay, it may cause inconsistencies in the record. This is because the Delay implementation must rewind time to correctly honor the requested delay duration. If it rewinds time, and then the patient dies at  the rewinded time, then any modules that were processed before the generic module may have created events and records with a timestamp after the patient's death.

Very strange. The death certification has a date of 1993-09-01 and cause of death is "natural causes". I haven't seen this before but I'll keep an eye out. @KeeyanGhoreshi is right that the rewinding time can cause some weirdness, but it should only be within a single timestep -- 7 days by default

This problem still exists and in some cases the encounter occurs years after death. See attached.
post_death_encounters.xlsx


Prefix are broken

I just started having this problem where when I add two parent groups to an other group, it gives that other group the parent prefixs and uses one as display in chat. When I do /lp group (that group) info it says it has 3 prefixs. How do I remove them?

I think, setting different weights to the prefixes should help.
Or just negate the permission of the prefix (prefix.[wheight].[prefix with color/formattingcodes]) in the group, that inherits the groups

How do I set the weight of the prefix? I set the weight of the ranks already from 15weight-1weight (1 is owner and admin is 2 and so on)

It's exactly the oposite...
Higher numbers are higher priorities....
You can set it with /lp group <your group> meta addprefix <wheight> <prefix>

Neither work. I set the weights and the other prefix still shows and I did the negate permission part and still did't work.

I did Set prefix.1.[PokeNoob] to false for mod in context global for the negate and I did owner as 15 and went down from there and still no.

You remove existing prefixes by running /lp group <group> meta info, and clicking on the values you want to remove.

It worked Thank you!

Awesome!
If you encounter any further issues, feel free to open a new ticket / drop a message in Discord.


Make script work from any location

Hello. What do you think? This way users can add scripts to their $PATH and run it from literally everywhere, plus it doesn't matter where they clone the repository.
Variable names of course can be edited, and whatever other changes you like.

The idea is good, but we need to change everything anyway for versions v2.0.0 that will allow you to pick a specific region.
If we decide to move into this direction, we can't save all the OpenVPN variables in the folder used for the git repo, since we risk pushing all of that to git by mistake. There are other pulls/issues analyzing a change from /opt/pia-manual/, but that is still under review.
I think we should get back to this in January, after we merge v2.0.0 (which is having some blockers at the moment).

Speaking of /opt/pia-manual location, it might be stored in another variable like PIA_MANUAL_LOCATION'. Hence there can be a user.confconsisting of all PIA_variables which users might easily modify and avoid passing environment variables on terminal (which is less secure). Then there can be acommon()function, which determinesSCRIPTDIRand sources$PIA_MANUAL_LOCATION/user.confat the beginning of every script. I'll make another prototype. Good luck withv2`.


Attempted fix for "Discarded TranslateJob due to a ActiveJob::DeserializationError"

I checked the logs for the project mentioned in the task description, which ended up not being translated. The error I found in the log was Discarded TranslateJob due to a ActiveJob::DeserializationError, which I think might have to do with passing an AR object as argument to the background job. While in principle that should work, I am not really sure how CloudTasks interacts with those arguments, and so to be on the safe side I think it is worth passing objects to translate by id and see if this error goes away (there are multiple instances in the logs, related to different types of translated objects, so there's nothing specifically wrong about projects I think).
Testing instructions
I tested that translation jobs still run locally, so at least this is not worse than it was, but really it needs to be vetted on staging, as I never came across this error locally previously.
Tracking
https://vizzuality.atlassian.net/browse/LET-1172?atlOrigin=eyJpIjoiNzBkNmRiN2QyZDkzNDE4YTllZTYxZGVkYjhhNmNjMjMiLCJwIjoiaiJ9

I have checked https://staging.hecoinvest.org/backend/api/v1/background_job_events?page[size]=70&filter[created_at_min]=2022-09-26T09%3A29%3A46.389Z&filter[created_at_max]=2022-09-26T10%3A29%3A46.389Z (need to be logged as Admin to see results) and from it is clear that this job (I guess it was one responsible for translation) was correctly enqueued and completed --> in second case, it is visible from log that object was correctly deserialised, because it contains attributes of object saved inside log.

I have checked https://staging.hecoinvest.org/backend/api/v1/background_job_events?page[size]=70&filter[created_at_min]=2022-09-26T09%3A29%3A46.389Z&filter[created_at_max]=2022-09-26T10%3A29%3A46.389Z (need to be logged as Admin to see results) and from it is clear that this job (I guess it was one responsible for translation) was correctly enqueued and completed --> in second case, it is visible from log that object was correctly deserialised, because it contains attributes of object saved inside log.

Interesting! Still, there was an error on this job, and I suppose the logic is if a job is discarded like that, it still ends up as "completed", even if it ended up doing nothing.

Yes, discarding error will for sure complete job without crash. Hmm, from your logs it truly looks like problem is deserialization and cloudtasker....


[Android] Audio starts auto when I have a phone call (if app is open and track player is stopped)

I'm doing a live radio app and I found this issue and I don't know how to fix it!
I use the last version of React Native Track Player.
How to reproduce:
Open app > Play > Stop ... Call to someone and Finnish call... audio starts auto.
This only happens when app is on, because if you kill the app or the notification, not happen.
Can help me to fix this?

I have the same problem. I had to completely remote the remoteDucking from my code for now.

Experiencing the same issue.

By last version do you mean version 3.2.0 or nightly?

@puckey I tried both! When is playing, if I stop... I get a call... when call is over, app is running the sound again... like auto play...

@pmafpinho okay thanks – I will try to reproduce it soon

I am unable to reproduce this issue using nightly in combination with the example app on a phone with android 13. Am I missing something?

open the app on test phone
press play
press pause
call the test phone
hangup call
expect audio to start playing (which doesn't happen)

it also does not happen with the same steps as above, when I place a call to another phone from the test phone instead of receiving one..

If I am doing everything correctly, please clone the repo and change the code of the example app to such a degree that we can replicate this issue.

@puckey I'm using : "react-native-track-player": "^3.2.0",
I open the app, I click on play / stop... i get a call from a person and when I finnish the call, audio starts! I can do a video to show you. I also can send you APK or the code.

Please try the nightly version instead. If it still gives you the same issues, clone the react-native-track-player repo and change the code of the example app to such a degree that we can replicate this issue.

https://user-images.githubusercontent.com/22176917/217234376-08c1d055-efaa-4937-a1de-f76511c1a786.mp4

@puckey I installed the nightly version and not fixed this issue!

@puckey the example project not working!

@puckey I tryed on android and work's, no problem! I check your Live Stream example, but not sense the pause button, a Live Stream is a Live Stream, you can't pause (because you want ear something LIVE). That's why a Stop button must be implemented and you guys removed. Live Stream it's for radios, and I made a lot to get the live result. I will try to create APK for this, and test is it's happens...

@puckey I tryed on android and work's, no problem! I check your Live Stream example, but not sense the pause button, a Live Stream is a Live Stream, you can't pause (because you want ear something LIVE). That's why a Stop button must be implemented and you guys removed. Live Stream it's for radios, and I made a lot to get the live result. I will try to create APK for this, and test is it's happens...

TrackPlayer.stop() is supported again in nightly..

In ‘nightly’ you can also use ‘autoHandleInterruptions’ in player options: https://github.com/doublesymmetry/react-native-track-player/blob/211a3fbda0e408a70fc9421bd31fd686fa1a68d0/docs/docs/api/objects/player-options.md

It's fixed! Thank's!


Roll Flutter Engine from 4d8d8517a0ff to 6d340446ca6c (1 revision)

https://github.com/flutter/engine/compare/4d8d8517a0ff...6d340446ca6c
2024-09-14<EMAIL_ADDRESS>Add xcprivacy privacy manifest to macOS framework (flutter/engine#55078)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC aaclarke@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


analytics: Remove underscore from client names in populate_analytics_db.

@rishig can you expand the commit message to explain what's going on for posterity?

updated!

Merged, thanks @rishig!


Does this module support TCP port of Graylog Input?

As subject, wondering if gelf moudle supports TCP port?

No it does not, but you can simple implements TCP client:
conn, _ := net.Dial("tcp", "grayloghost:12204")
message := gelf.Create("Short message content")
conn.Write([]byte(message.ToJSON()))

got it, thanks!


Improve APIv2 support for Attach

A few major fixes here:

Support for attaching to Configured containers, to match Docker behavior.
Support for stream parameter has been improved (we now properly handle cases where it is not set).
Initial support for logs parameter has been added.

Still to do:

The attach query parameters (stdin, stdout, stderr) must be supported even when the container has a terminal
Logs parameter currently causes segfaults trying to read the logs, which is bad. Also does not split logs into stdin/out/err when terminal is not specified.
Errors do not seem to be written after the hijack has begun.
Swagger must be updated to reflect these changes

@marusak This is the start of the attach fixes we talked about, hopefully should have it ready soon.

Have some questions for @baude about the logs stuff that will probably have to wait until tomorrow for answers.

Logs stuff is fixed

Errors are now properly written. Just need to fix up handling of streams when a TTY is allocated and update swagger.

Stripping WIP, this should be ready now.
@marusak Any chance you could test this and verify it fixes the issues you've been seeing?

Any chance you could test this and verify it fixes the issues you've been seeing?

Thank you so much! It works as expected for my usecase.
LGTM

/lgtm


Correction in PlaybackLatency description

Sorry for the delay getting back to you on this. It was actually quite hard to find any official documentation on what the units of this parameter are, but I agree it does seem to be samples (or perhaps more accurately "sample frames" - i.e. it hasn't been multiplied by the channel count)


CONTRIBUTING: Simplify and shorten docs

Right now, CONTRIBUTING.md is excellent, but long.
Thoughts I had:

Remove second cask example (genymotion) - yes, it shows multiple artifact stanzas...but that's about it
Promote appcast/shasum stanzas to "Other commonly-used stanzas" - maybe also auto_updates?
Put special use-case stanzas in Cask Language Reference (leave pkg and binary) - the rest can be pretty specialized and just lengthen the document
"SourceForge/OSDN URLs" should go...somewhere... It doesn't particularly feel like this is the best spot for it
Add rubocop-cask mention (again) to Style guide section
Add in note about not having extraneous comments in Style section

Agreed on everything, except

"SourceForge/OSDN URLs" should go...somewhere... It doesn't particularly feel like this is the best spot for it

I don’t think we have a better spot for it, and it is indeed something to be aware of at contribution time.

Put special use-case stanzas in Cask Language Reference

They should already all be there.

I meant remove the rest of the artifacts from CONtRIBUTING


Notification thresholds

You once suggested upvote thresholds for notifications on legendary items (also #64 ). This PR will allow users to set custom thresholds for legendary cards and rapports respectively. The values can be set in the Notifications page.
I added threshold values in ClientSettingsController for both cards and rapports for each rarity, although currently only the legendary rarity is being used. But maybe we want to extend this in the future (see notification settings, stuff grows big fast), so it's already prepared for this case.
Additionally a notification is now requested on every OnUpdateVoteTotal hub-message. To prevent the resulting notification spam on each upvote, I added an internal "cooldown" timer in ClientNotificationService so each merchant can only have one notification per spawn cycle.
One last thing I did not implement yet but could be important: A popup for users to inform them of the new feature, so they set their thresholds. I'm picturing something like the browser-sound-disabled popup from #33 , just different placement and color. Let me know what you think.

A popup for users to inform them of the new feature, so they set their thresholds.

Something I've been thinking about is a dismissable info box at the top of the page with some sort of "new/changed feature!" type messages. Would probably need to do some basic tracking in a local storage key of whether a user has seen a message or not (maybe only saves that a message is seen when the box is manually cleared?). Probably only really need a constant or something to keep the most recent message and then some functionality around it.


[CT-1200] [Bug] Grants colliding with Snowflake Shares

Is this a new bug in dbt-snowflake?

[X] I believe this is a new bug in dbt-snowflake
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
dbt is attempting to revoke select permissions on a Snowflake Share.
Expected Behavior
dbt's grant feature, release in v1.2, should only apply to roles and not Snowflake shares
Steps To Reproduce

Follows steps 1-3 to

create a share
grant permissions to the share
link a share with a reader account (see here on how to create a reader if one is needed)

Add select grant permissions on model tied to share{{ config(grants = {'select': ['user_c']}) }}

Run model and error should appear

Relevant log output
No response
Environment
- OS: macOS Monterey Version 12.5.1
- Python: 3.9.13
- dbt-core: 1.2.0
- dbt-snowflake: 1.2.0

Additional Context
-- table with Snowflake share
show grants on table analytics.demand.fridge_hour;

@aaron-ortega Thanks for opening! Very glad you're using the (relatively new) grants feature :)
It sounds like we need an additional bit of logic in our post-processing step, which operates on the result of show grants. Similar to what we have currently for privilege != "OWNERSHIP":
https://github.com/dbt-labs/dbt-snowflake/blob/6748104c669d484200e559fe67ae946b2d4e4e65/dbt/adapters/snowflake/impl.py#L160-L172
Something like:
granted_to = row["granted_to"]
if granted_to == 'role':  # or != 'share' ?
    ...

Would you be interested in contributing the fix? Otherwise someone can pick it up

so fast! i was about to link to the exact code block
Yes, I would be interested. What behavior should we be thinking about implementing?

Skip shares (easy) - we only care about providing permissions for roles
for row in grants_table:
    grantee = row["grantee_name"]
    granted_to = row["granted_to"]
    privilege = row["privilege"]
    if privilege != "OWNERSHIP" and granted_to == "ROLE":

Include shares in granting select. This would require the revoke/grant step to update
-- e.g.
revoke SELECT on "table" from "share_name"; --old
revoke SELECT on "table" from share "share_name"; --new

@aaron-ortega Ooh, that's a good question!
So the quickest way to resolve this bug is probably to remove shares from consideration. Then we could open a feature request about adding support for granting to shares. Might we want dbt to natively support defining/creating/updating shares, too?
If we wanted to support shares, we'd need some way to identify them as such, so that dbt knows to run:
grant select on <table> to share <share_name>;
grant revoke on <table> from share <share_name>;

Instead of:
grant select on <table> to <share_name>;
grant revoke on <table> from <share_name>;

Potential syntaxes:
models:
  - name: my_model
    config:
      grants:
        # option A: allow strings for default types, or dicts to provide custom type
        select:
          - some_role
          - name: some_share
            type: share
        # option B: inspired by google/bigquery, use string prefixes for principal type
        select:
          - some_role  # could also be role:some_role
          - share:some_share


CODEOWNERS file

Read this before submitting the PR

Always create a Draft PR first
Go through sections 1-5 below, fill them in and check all the boxes
Make sure that the branch is updated; if there's an "Update branch" button at the bottom of the PR, rebase or update branch.
When all boxes are checked, information is filled in, and the branch is updated: mark as Ready For Review and tag reviewers (top right)
Once there is a submitted review, implement the suggestions (if reasonable, otherwise discuss) and request an new review.

If there is a field which you are unsure about, enter the edit mode of this description or go to the PR template; There are invisible comments providing descriptions which may be of help.
1. Description / Summary
Adding our team as code owners of all files in the repository in order to set the requirement that any changes to the repo requires an approval from one of us.
2. Jira task / GitHub issue
https://scilifelab.atlassian.net/jira/software/projects/DDS/boards/13/backlog?epics=visible&selectedIssue=DDS-2054
3. Type of change
What type of change(s) does the PR contain?
Check the relevant boxes below. For an explanation of the different sections, enter edit mode of this PR description template.

[ ] New feature

[ ] Breaking: Why / How? Add info here.
[ ] Non-breaking

[ ] Bug fix
[ ] Security Alert fix

[ ] Package update

[ ] Major version update

[ ] Documentation <!-- Should be checked if the PR adds or updates the CLI documentation -- anything in docs/ directory. -->
[x] Workflow
[ ] Tests only

4. Additional information

[x] Sprintlog
[ ] Blocking PRs

[ ] Merged

[ ] PR to master branch: If checked, read the release instructions

[ ] I have followed steps 1-8.

5. Actions / Scans
Check the boxes when the specified checks have passed.
For information on what the different checks do and how to fix it if they're failing, enter edit mode of this description or go to the PR template.

[x] Black

[x] Pylint

[x] Prettier

[x] Yamllint

[x] Tests

[x] TestPyPI

[x] CodeQL

[x] Trivy

[x] Snyk

with the same remark about retrospectively changing the SPRINTLOG

In this case I don't entirely see it as retrospectively changing the sprintlog, just keeping documentation regarding what happened during previous sprints.


Build(deps-dev): Bump @storybook/react from 6.4.13 to 6.4.14 (#2464)

Pull request opened by the merge tool on behalf of #2464

Merged in cfb091c0acdcb7b07abbd590e68aed082b0623a3


Always lower hostname with kubernetes.io/hostname label

Fixes hosts file modification feature test.
Node label kubernetes.io/hostname will be the same as nodeName, and it's always lower cased.

LGTM


align names on browse and package pages

sometimes the names we list on the browse page are different than the package page
we should align these
some examples:

elastic is ec on the browse page and ElasticCloud (EC) on the package page
artifactory is artifactory on the browse page and Artifactory on the package page
astra is astra on the browse page and Astra on the package page
awsx is awsx on the browse page and AWSx on the package page
miniflux is Miniflux on the browse page and AWS Miniflux on the package page

questions:

why do we have different metadata for these things, can they be the same?

related issues:

https://github.com/pulumi/registry/issues/839

I do agree things are fairly "weird" here today.
A few thoughts:

Should we require a display name for all packages?  If not, should we just only use the raw package name for all packages?
If no to both of the above, should we always show the raw package name in addition to display name when it is available?
Is there a 3rd piece of metadata?  How is it that Elastic Cloud is named named "ec" on the index page but "ElasticCloud (EC)" on the description page?

for the most part this is now done. we still don't have a single source of truth for this, but the two pieces of data is now fixed.
for anyone else who comes across this...

browse page uses display name for the package if it exists, otherwise it uses the package name from the meta data; but there are exceptions here: https://github.com/pulumi/pulumi/blob/master/pkg/codegen/docs/gen.go#L57-L152 which controls the name that shows on the browse page
for the package page, the name comes from the title in the meta data which is in this repo


[🐛 in esl-scrolbar]: remove unnecessary width

There is a width: 16px for the scrollbar componet that that affects adjusting the right padding for scrollable content.

:tada: This issue has been resolved in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Question: columns in file test.clean.deeparg.align.daa.tsv

Hello. I have just installed and ran tets of deeparg for short reads and it worked perfectly. My question is about file test.clean.deeparg.align.daa.tsv generated. What is the meaning of each column? Thanks in advance

this is the output from diamond alignment:
                   BH[i[0]][2][8],  # alignment gene start                     BH[i[0]][2][9],  # alignment gene end                     i[0],  # read-id                     i[1],  # predicted type                     x_bh,  # best hit                     str(i[2]),  # probability                     BH[i[0]][2][2],  # identity                     BH[i[0]][2][3],  # alignment length                     BH[i[0]][2][-1],  # bitscore                     BH[i[0]][2][-2],  # evalue                     '1'  # count
https://github.com/gaarangoa/deeparg/blob/b4daa15ebcc3afb792a76bae5c3d33a2947bfb59/deeparg/predict/bin/deepARG.py#L168-L178

Could you please be more specific about the order of the columns? It doesn't seem to match the one in the code above.


cloud reader: infinite spin + no user feedback with non-existing ebook URL, or corrupted EPUB

Fixed (see above commits). To test the error dialog, simply open the cloud reader with URL ?epub=MISSING_EBOOK_PATH.


Add timeout support and "searchTimeout" option.

This pull request includes a

[ ] Bug fix
[X] New feature
[ ] Translation

The following changes were made

Added the keyword "searchTimeout"
Added functionality to allow for a msec timeout to be set before  options are searched.

If this is related to an existing ticket, include a link to it as well.
https://github.com/select2/select2/issues/4914

Fixing the issues and will setup a new pull request.

It would seem that jshint doesn't like setTimeout and clearTimeout: https://travis-ci.org/select2/select2/builds/289120165#L680-L684

Locally I have the issue fixed.   Keeping this request open for reference while I work on a better solution.


Refinements - where we left off

After 2 days of working on refinements they actually work most of the way. However, they don't totally work.
They can be enabled with --refine  and a simple test of them is that they actually find map properly in the dreamcoder example:
cargo run --release --bin=compress -- data/basic/map.json -a1  --refine
=======Compression Summary=======
Found 1 inventions
Cost Improvement: (3.38x better) 2729 -> 808
fn_0 (3.38x wrt orig): utility: 252 | final_cost: 808 | 3.38x | uses: 2 | body: [fn_0 arity=1: (Y (lam (lam (if (is_nil $0) nil (cons (#0 (car $0)) ($1 (cdr $0)))))))]
Time: 5ms

However, sometimes they blowup, for example if  you use a higher refinement arity:
cargo run --release --bin=compress -- --fmt=dreamcoder -a3 data/dc/origami/iteration_0_3.json -i1 --no-top-lambda --verbose-best --refine -t8 --max-refinement-arity=2
which utlimately ends up searching through many millions of refinements and takes about 5 minutes on sketch4.
For this reason I added the  --max-refinement-size flag which lets you change the max cost of something that can be refined out. For example if we know we only want to refine out things with at most 2 nonterminals and 3 terminals we can set this to 302.
Additionally there's the --max-refinement-arity flag for how many things to refine out within a single refinement site (default 1).
Finding fold
cargo run --release --bin=compress -- --fmt=dreamcoder -a3 data/dc/origami/iteration_0_3.json -i1 --no-top-lambda --verbose-best --refine
yields fold:
=======Compression Summary=======
Found 1 inventions
Cost Improvement: (1.18x better) 70899 -> 60193
fn_0 (1.18x wrt orig): utility: 9185 | final_cost: 60193 | 1.18x | uses: 15 | body: [fn_0 arity=3: (fix1 #0 (lam (lam (if (empty? $0) (#1 $0) (#2 (car $0) ($1 (cdr $0)))))))]
Time: 685ms

Well, actually  that's a tiny bit different from fold, and is slightly better in terms of our utility but also matches at fewer places. Alternatively we can turn our refinement arity up to 2 and ask it to find fold exactly:
cargo run --release --bin=compress -- --fmt=dreamcoder -a3 data/dc/origami/iteration_0_3.json -i1 --no-top-lambda --verbose-best --refine --track='(fix1 #0 (lam (lam (if (empty? $0) #1 #2))))' --track-refined='(fix1 #0 (lam (lam (if (empty? $0) #1 (#2 ($1 (cdr $0)) (car $0))))))' --max-refinement-arity=2 --no-opt --follow-track
you need to run this one a few times before the argument order is randomly correct so tracking can pick it up, then youll get:
Cost Improvement: (1.13x better) 70899 -> 63021
fn_0 (1.13x wrt orig): utility: 6509 | final_cost: 63021 | 1.13x | uses: 21 | body: [fn_0 arity=3: (fix1 #0 (lam (lam (if (empty? $0) #1 (#2 ($1 (cdr $0)) (car $0))))))]

if we knew how to get a pcfg score for a set of dc frontiers we could compare pcfg scores in the log files with the ones we're getting here as a way of telling if we actually did identical rewrites ofc thatd be so painful if they differed bc all you have is a number to go by
You can only use the refinement arity 1 version by including the second arg in the body, but this limits how many places it matches at so its not great and i doubt dreamcoder does this since it seems to have the args in the opposite order:
cargo run --release --bin=compress -- --fmt=dreamcoder -a3 data/dc/origami/iteration_0_3.json -i1 --no-top-lambda --verbose-best --refine --track='(fix1 #0 (lam (lam (if (empty? $0) #1 (#2 ($1 (cdr $0)))))))' --track-refined='(fix1 #0 (lam (lam (if (empty? $0) #1 (#2 (car $0) ($1 (cdr $0)))))))' --max-refinement-arity=1 --no-opt --follow-track
Cost Improvement: (1.11x better) 70899 -> 63819
fn_0 (1.11x wrt orig): utility: 5711 | final_cost: 63819 | 1.11x | uses: 15 | body: [fn_0 arity=3: (fix1 #0 (lam (lam (if (empty? $0) #1 (#2 (car $0) ($1 (cdr $0)))))))]

We dont do multiuse
Additionally there's this piece of code that prevents refining something that's used in more than one place. Multiuse actually isn't complicated, it's just an extra term in the loss since you dont gain the same sort of body utility that you would otherwise or something, we just don't do it:
for (i,_) in new_pattern.first_zid_of_ivar.iter().enumerate() { // for each arg
                        if new_pattern.arg_choices.iter().filter(|l |l.ivar == i).count() > 1 {
                            refinements_by_arg[i] = Vec::new(); // todo limitation: we dont refine multiuse
                        }
                    }

We don't handle two of the dreamcoder origami functions
fn_7 - count_down
(fn_4 (lam (lam (- $1 $0))) (#0 #1) #1)

arity 2; #0 is higher order and the input is #1

fn_10 - zip
(fn_2 (fn_5 (fn_6 #0)) (lam (#1 (fn_9 $0 #2) (fn_9 $0 #0))))

arity 3; #1 takes a double lambda and feeds it a functions of #0 and #2

Yes it would be post refinement still which is nice. It'd be post refinement where your arity budget isn't met so you spend some arity creating special refinements with new vars in them. These could be punching out subtrees.

precompute refinements but also arity 1 refinements. These have some prim NEWVAR or # -1 in them.

You shouldn't need to subset more based on that bc they're literally allowed to vary between each.

Ah but you do want to multiuse (and no arity budget cost) if your newvar is the same as a global var, which happens in the count_down example

In general I suspect handling these would be a real stretch. It's super possible just not something we can do right now, and it'd probably not be nice and clean and formal

doing all the refinement at the end
It might be wise to save a big donelist of everything youre considering and then do all the refinements together at the end, just in case that makes it possible to avoid some.
closing thoughts
I actually think we're extremely close to having this. We can find something that's basically fold after all. There are a handful of little questions like "even though we can find fold, are we sure we're finding all the true places it's useful just as dreamcoder does? how many use site does dreamcoder find for it?". We likely won't get count_down or zip but a) perhaps we're lucky and they are already syntactically there or b) it's not a big deal anyways bc theyre leaves of the invention tree they arent used for anything else.
I do think it's really hard to hand-verify equivalence between dreamcoder and stitch on these things. Stitch always likes its inventions more than what dreamcoder does but its not clear if its just not finding all the rewrite places that dreamcoder likes - which is why its important to either rerun dreamcoder with printouts of that or something else
also theres another crash
cargo run --release --bin=compress -- --fmt=dreamcoder -a3 data/dc/origami/iteration_3_1.json -i1 --no-top-lambda --verbose-best --refine -t8
also tracking for zip seems hard this doesnt seem to do it cargo run --release --bin=compress -- --fmt=dreamcoder -a3 data/dc/origami/iteration_3_1.json -i1 --no-top-lambda --verbose-best --refine -t8 --track='(fn_2 (fn_5 (fn_6 #0)) (lam #1))' --follow-track --no-opt --max-refinement-arity=2 --track-refined='(fn_2 (fn_5 (fn_6 #0)) (lam (#1 (fn_9 $0 #2) (fn_9 $0 #0))))'

We should drop refinements entirely - kevins vspace solution or babble merge makes more sense

dropping refinements in favor of an egraph or version space based approach in the future


Expose custom fields

Firstly, thanks for building these packages!
Having access to custom fields would add a lot of value to the Asana data in our DW.  Would it be possible to add them as an object to the task model?  Adding them as a separate model would be fine.
I'm happy to help work on this but I would appreciate input on how best to implement it.
Thanks!

Hey Charlie, thank you! If you'd like to work on this, that would be great!  Here is some info to get you going. LMK if you have any questions along the way.

A good example of how we've done this in the pass is in our salesforce model.
Once you identify the models you'd like to include passthrough columns to, the steps include the following. I've linked examples of this work for each item.
Source package:

Update dbt_project.yml file to include passthrough variables
Update staging models to utilize passthrough columns. Note this needs to be done in two places - here and here.
- Update README configuration to call out use of passthrough columns

Transform package:

Update dbt_project.yml file to include passthrough columns
Update any applicable models so that the passthrough columns flow through to final models.  Example of final model here.
Update README

@mjrsnyder I just created new releases for the packages. You'll be able to upgrade to asana version 0.3.1 once you see it on the hub here (I expect this to take no less than 1 day).

@fivetran-kristin Thanks for you and are your team's responsiveness!


Game fails to load if Useful Spyglass is installed

Minecraft Version
1.20.1
Describe the Bug
The game stops loading and closes during the mod scanning phase if both CCK and Useful Spyglass are installed.
NeoForge 47.1.104
Create 0.5.1f
CCK 1.13.2
Useful Spyglass 0.6.0
prism log
BrokenK3yboard/UsefulSpyglass#9

Useful Spyglass is responsible for the crash as it bundles the NeoForge specific artifact instead of the Forge one, which is not suitable for mods under NeoForge 20.2.84.
I'm closing this since the developer of Useful Spyglass has confirmed the exact issue and will be patching it in next release.


return original array if no child mapping for array mapping

What kind of change does this PR introduce? (check one with "x")
[*] Bugfix
[] Feature
[] Code style update (formatting, local variables)
[] Refactoring (no functional changes, no api changes)
[] Other... Please describe:

Fixes: #
What is the current behavior?
What is the new behavior?
If there is no child mapping for array mapping then we return original data. such as:
     "array": {
                  "@foreach($activity[rest].data.array)":{}
         }

We will copy $activity[rest].data.array to array.  This is the behavior we did in flogo-lib,  so make these changes to keep consistency with previous.

I read this as creating an empty array the length of $activity[rest].data.array.  If I were to assign an array I would do =$activity[rest].data.array .  @mellistibco thoughts on this?
or
maybe something like this... not sure...
"array": {
"@foreach($activity[rest].data.array)":[
"=$loop"
]
}

@fm-tibco @mellistibco Actually there is possible 2 behavior

Do nothing
Just create an empty array
Copy all from the source array

I think both 1 and 3 make sense.  I don't think there is much use case to create an empty array.
There is no mapping at child level we can take is as 3 to copy all from the original. They can remove foreach node if they want to do nothing.

Whatever we decide, we should definitely add documentation on the object mapping stuff.
"array": {
    "@foreach($activity[rest].data.array)":{}
 }

It still isn't clear enough to me that the statement above is the same as this
"array":"=$activity[rest].data.array"

I have a question, how do we do the following
array[0] =  $activity[rest].data.array[0].subVal
array[1] =  $activity[rest].data.array[1].subVal
array[2] =  $activity[rest].data.array[2].subVal
array[3] =  $activity[rest].data.array[3].subVal
I think if we resolve this, it will might tell us what is the right approach on this issue.
@mellistibco ?

@fm-tibco Yes, It is same with "array":"=$activity[rest].data.array".
But we cannot handle this today, the key of must be an real key.
array[0] = $activity[rest].data.array[0].subVal
array[1] = $activity[rest].data.array[1].subVal
array[2] = $activity[rest].data.array[2].subVal
array[3] = $activity[rest].data.array[3].subVal

maybe we can do the following with a special "=" value:
copy values:
"array": {
    "@foreach($activity[rest].data.array)":{
        "=" : "=$loop"
    }
 }

copy sub values:
"array": {
    "@foreach($activity[rest].data.array)":{
        "=" : "=$loop.subVal"
    }
 }

set fixed values, same length of array:
"array": {
    "@foreach($activity[rest].data.array)":{
        "=" : "defaultValue"
    }
 }

@mellistibco thoughts on this?

Hmm, tricky. I'm not super fond of any option nor do I have a better suggestion... I think we should probably go with the following. It seems to be the most logical to me...
"array": {     "@foreach($activity[rest].data.array)":{         "=" : "=$loop.subVal"     }  }

thanks, @mellistibco  and @fm-tibco , I will update the PR.


Add HeaderMap annotation

Code/tests are not at merge quality, but submitting PR for discussion on general approach/feature

NetflixOSS » feign » feign-pull-requests #249 SUCCESS
This pull request looks good

PR for #363

NetflixOSS » feign » feign-pull-requests #252 SUCCESS
This pull request looks good

Improved documentation in comment for HeaderMap and in commit message. Still not complete (real submission would have more test coverage and update CHANGELOG and README), but waiting for discussion on issue to resolve before doing polish work.

NetflixOSS » feign » feign-pull-requests #254 SUCCESS
This pull request looks good

NetflixOSS » feign » feign-pull-requests #255 SUCCESS
This pull request looks good

NetflixOSS » feign » feign-pull-requests #257 SUCCESS
This pull request looks good


AttributeError: 'EfficientNetFeatures' object has no attribute 'act1'

The problem description is below, how should I resolve this problem?
Unexpected keys (bn2.bias, bn2.num_batches_tracked, bn2.running_mean, bn2.running_var, bn2.weight, classifier.bias, classifier.weight, conv_head.weight) found while loading pretrained weights. This may be expected if model is being adapted.
Traceback (most recent call last):
File "D:\Project\BinocularStereoVision\IGEV-plusplus\demo_imgs.py", line 90, in
demo(args)
File "D:\Project\BinocularStereoVision\IGEV-plusplus\demo_imgs.py", line 30, in demo
model = torch.nn.DataParallel(IGEVStereo(args), device_ids=[0])
File "D:\Project\BinocularStereoVision\IGEV-plusplus\core\igev_stereo.py", line 107, in init
self.feature = Feature()
File "D:\Project\BinocularStereoVision\IGEV-plusplus\core\extractor.py", line 333, in init
self.act1 = model.act1
File "D:\Anaconda\Anaconda3\envs\MedSAM\lib\site-packages\torch\nn\modules\module.py", line 1614, in getattr
raise AttributeError("'{}' object has no attribute '{}'".format(
AttributeError: 'EfficientNetFeatures' object has no attribute 'act1'

pip install timm==0.5.4

please install the corresponding timm version.


Use latest gentool

Ok, so when we create a release of everything this will go to the corresponding release tag, correct?


Bad seek errors when processing HEIC formats using Sharp 0.28.2 "Error: source: bad seek to 2994402 heif: Unsupported feature: Unsupported codec (4.3000)"

Are you using the latest version? Is the version currently in use as reported by npm ls sharp the same as the latest version as reported by npm view sharp dist-tags.latest?
Yes, version ^0.28.2
What are the steps to reproduce?
Download and install latest libvips binaries from brew
Convert any HEIC photo to a buffer array, and then load it into sharp. The error is thrown immediately.
I can confirm that heif-convert can process the images
heif-convert IMG_4299.HEIC PNG_4299_CONVERTED.png
File contains 1 images
Written to PNG_4299_CONVERTED.png

I can confirm that an older version of sharp continues without error
 "sharp": "^0.26.2"

What is the expected behaviour?
Continues without error, this issue is resolved by using an older version of sharp
Are you able to provide a minimal, standalone code sample, without other dependencies, that demonstrates this problem?
Sample Code
const content = fs.readFileSync('./sample1.heic');

// This will throw the described error
const rotateImage = sharp(content);

Error Output
Error: source: bad seek to 2994402
heif: Unsupported feature: Unsupported codec (4.3000)
heif: Unsupported feature: Unsupported codec (4.3000)

Are you able to provide a sample image that helps explain the problem?
It's happening with all of our HEIC photos. But I can't supply a test sample publically sorry.
What is the output of running npx envinfo --binaries --system?
  System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
    Memory: 546.43 MB / 8.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 12.16.1 - ~/.nvm/versions/node/v12.16.1/bin/node
    Yarn: 1.22.5 - /usr/local/bin/yarn
    npm: 7.5.4 - ~/.nvm/versions/node/v12.16.1/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
    libvips: vips-8.10.5-Fri Dec 18 10:14:09 UTC 2020
    heif-convert: 1.11.0

libvips: vips-8.10.5-Fri Dec 18 10:14:09 UTC 2020

HEIC images require the use of a globally-installed libvips. sharp v0.28.x requires libvips 8.10.6, so you're probably using the prebuilt binaries that do not support HEIC images. Please can you upgrade libvips to 8.10.6 then re-install sharp.

Perfect. That was exactly the issue.
Just confirming that I upgraded my globally installed vips to 8.10.6; and rebuilt the binaries after a full rm -rf of the node_modules folder.
Thanks @lovell


A compile error and how to solve it

A compile error

lastest version, compile at 2023/4/26
cmake default setting with VS2022
here is the log

E:\linyaodong\SPlisHSPlasH\SPlisHSPlasH\Utilities\SceneParameterObjects.h(79,31): error C2079: “Utilities::FluidModelParameterObject::resolutionSDF”

Why

the std:;array header file is not right included

How to solve this

simply add  in the begining

Thanks for reporting this. I just tested on my system with VS 2022. However, I don't get any compiler error.
I added the additional include so this should solve the problem on any system.

Thanks for your respond :)

Thanks for reporting this. I just tested on my system with VS 2022. However, I don't get any compiler error.
I added the additional include so this should solve the problem on any system.


Debian: tsfixcc conflicts with opencaster

Hi,
I successfully built tsduck_3.10-674_amd64.deb from source on Debian Stretch 9.4 (current master commit = e58d3c12feaff581c4718e0eac72844bef30c871 Apr 11 23:23:44 2018 +0200).
However, I cannot install the .deb created by make deb as it conflicts with tsfixcc which is also provided by opencaster:
    >sudo dpkg -i installers/tsduck_*.deb
    (Reading database ... 138664 files and directories currently installed.)
    Preparing to unpack .../tsduck_3.10-674_amd64.deb ...
    Unpacking tsduck (3.10-674) ...
    dpkg: error processing archive installers/tsduck_3.10-674_amd64.deb (--install):
     trying to overwrite '/usr/bin/tsfixcc', which is also in package opencaster 3.2.2+dfsg-1.1+b1

A workaround for me is to uninstall opencaster as I am not currently using it but ideally there should be no conflicting names.
Another option would be to document the equivalent of:
./configure --prefix=/usr/local
for whatever build system you are using.
I think as it stands it looks like make install installs to /usr when source installs should install to /usr/local (http://www.pathname.com/fhs/pub/fhs-2.3.html#USRLOCALLOCALHIERARCHY)
Is there any expectation of this package being accepted into Debian in the near future?
Regards,
Bruce.
PS I also note there is a unit test failure - though this may be okay as this is not a release tag:
 make test
source release-x86_64/setenv.sh && release-x86_64/utest

!!!FAILURES!!!
Test Results:
Run:  341   Failures: 1   Errors: 0

1) test: DemuxTest::testTOT (F) line: 375 utestDemux.cpp
assertion failed
- Expression: tot.regions[0].next_change == ts::Time(2008, 3, 30, 1, 0, 0)

Makefile:61: recipe for target 'test' failed
make[1]: *** [test] Error 1
Makefile:55: recipe for target 'test' failed
make: *** [test] Error 2

Hello,
Thank you for reporting this. Let's take all points one by one.

Opencaster

I was not aware that opencaster provided a command named tsfixcc. I never used opencaster. All TSDuck commands starts with the prefix ts, probably too short to be unique. On the other hand, I would rather not have to type long command names such as tsduck-fixcc or whatever.
tsfixcc, tsanalyze, tstables were commands I wrote 12 years ago (although not released in open source at the time) and which were more or less superseded with tsp plugins later. But the old commands remained, both for compatibility and because they were shorter to type than a complete tsp command.
I can offer no solution right now, except removing tsfixcc or ask opencaster to remove theirs :)

configure

TSDuck does not use a configure script. I have always hated those software with hard-coded paths. I have always considered this as bad design. And the fact that so many people copy those practices is not a proof of good choice, just a lack of imagination.
On the contrary, all TSDuck commands work relatively to the directory were the executable is located.
So, simply move the whole set of TSDuck binary files somewhere else and they will still work. No need to patch and rebuild.

Use of /usr/local

Well, this is a disputed topic. Each Unix flavor, and even each Linux distro, has its own set of rules, all being self-proclaimed standards. The FHS is just one of these self-proclaimed standards and it is not without ambiguity. It states that the /usr/local hierarchy is for use by the system administrator when installing software locally, without specifying what installing software locally means. Many people interpret this as if you manually copy files for all users, put them in /usr/local, which also means that the /usr hierarchy outside /usr/local shall be kept clean and maintained by the system packager, rpm, dpkg, etc, which ultimately means if you build a software package using the standard system packager, install your files in /usr. Honestly, I cannot recall a .rpm or  .deb package installing files in /usr/local.
There is only one context into which TSDuck installs its files in /usr/local, this is macOS. This is because macOS uses a System Integrity Protection infrastructure which prevents even an administrator from writing in /usr. This is why commonly-used macOS packagers such as Homebrew use /usr/local as secondary - but still centrally managed - software deployment area.
So, the TSDuck packages, .rpm, .deb or Homebrew, follow the same usages as their corresponding packagers.
That being said, since you rebuilt TSDuck from sources, you may install it anywhere else using
make install SYSPREFIX=/some/where/else

The failing unitary test

It is a coincidence that, probably at the same time you typed your message, I released version 3.10-674.
So, your failing test is quite worrying for me. But I cannot reproduce it. I build TSDuck on :

Windows Intel 32 and 64
Fedora Intel 64
Ubuntu Intel 64
Raspbian, ARM 32
and sometimes CentOS Intel 64

There is no such failure on any of these platforms. Is this the only failing test?
The test manipulates time values, which are built and analyzed by system libraries. So, when handling values which are before the epoch of one specific OS, there could be non-portability issues. But here the date is in 2008, the year I wrote this test. So, this is not the point.
Could you please make sure there was no build issue? At worst:
make distclean
make test

Let me know, I don't like this one.

OK, I think I get it.
The time from the test is, by definition, the transition time - UTC - for daylight saving time (the next change in a TOT). It is a UTC time.
The system libraries compute times, interpreting them as local time. The last Sunday of March, the range 1 AM (UTC) to 2 AM "does not exist". But this depends on the local time settings of your system.
I am located in Paris (UTC + 1) :
$ date --date='2008-03-30 01:00:00'
Sun Mar 30 01:00:00 CET 2008
$ date --date='2008-03-30 02:00:00'
date: invalid date ‘2008-03-30 02:00:00’
$ date --date='2008-03-30 02:30:00'
date: invalid date ‘2008-03-30 02:30:00’
$ date --date='2008-03-30 03:00:00'
Sun Mar 30 03:00:00 CEST 2008

So, the local time of the change (2 AM) is UTC 1 AM. But when the system libraries manipulate "1 AM", they use one 1 AM local time. Anywhere on the planet, except on London meridian, the test works. I see from your profile that you are based in London, this is why it fails on your system. Many people use TSDuck, in Europe, Russia, Asia or America. But it seems obvious that you are the first one to run the unitary tests in London (or somewhere where local time is UTC).
This was unexpected but interesting. I will think at the best way to fix this.
For the time being, the only impact is on very specific time values, so this will likely not impact normal usage.
Interesting, really.

Thanks for the quick response. I heartily agree regarding hard coded paths.
I was looking for the SYSPREFIX option. It may be a good idea to mention it in src/doc/building.md and didn't think to look for it in makefile.common
Regarding the use of /usr/local I am not claiming it should be the default for installing a system package like a .deb or .rpm. What I am really saying is that when building from source using "make install" should not install to /usr as that IS reserved for system packages. The conventions I'm familiar with have source installs done to /usr/local for this reason.
I agree the FHS can be too vague but I think this is one of the points where it is clearer (I sent you an old link when I should have sent you https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf but you seem familiar with it anyway). And while there are some relatively obscure distributions like gobolinux that don't follow it most accept the FHS (as part of the LSB).

Hi @KantarBruceAdams
I have fixed the time bug around DST in commit 97482f7f0a9d052e7a907c057923fc26139c7f43
I added enough unitary tests to spot the error in any local time zone. Since you seem to be a Unix programmer, the core problem is the impossibility on Unix to build a UTC time from a broken-down time (individual values for year, month, etc). You must convert it to local time with obvious issues when the corresponding local time does not exist (ie. the missing hour the last Sunday of March).
You may pull and rebuild if you like (and make install SYSPREFIX=/usr/local if you prefer).
Let me know if this is OK for you.

I was looking for the SYSPREFIX option. It may be a good idea to mention it in src/doc/building.md

Just done.

Looks good.


[BUG] Generate Random Key/Code Repetition Bug

For instance, when I put the format for the key to be 2 capital letters and 6 numbers, it'll make them perfectly fine like HD591921, but after a while, it will start making AA000000 over and over until I restart OpenBullet. I do not know how to recreate this, since it happened randomly twice of out four days. The feature request I recently put in was because of this, since I had to restart OpenBullet twice and lose my runners. Thanks!

Could be due to OpenBullet not actually "locking" its BotData#Random?
https://github.com/openbullet/openbullet/blob/master/RuriLib/Blocks/BlockFunction.cs#L665
https://docs.microsoft.com/en-us/dotnet/api/system.random?redirectedfrom=MSDN&view=netframework-4.8#the-systemrandom-class-and-thread-safety

Yes that's a really good idea, I will add locking to that property then. Thanks!

Nevermind, I just saw your pull request, I will check it and merge it as soon as I can. Thanks!

This should be fixed thanks to @Laiteux 's PR


Remove trace lines about NO_COLOR.

Currently there is a warning for every command run when NO_COLOR is set. For example:
$ headscale nodes
{"level":"trace","time":"2021-09-12T07:31:48-06:00","message":"NO_COLOR is set, disabling colors"}
Manage the nodes of Headscale

Usage:
  headscale nodes [command]

Available Commands:
  delete      Delete a node
  list        List the nodes in a given namespace
  register    Registers a machine to your network
  share       Shares a node from the current namespace to the specified one

Flags:
  -h, --help               help for nodes
  -n, --namespace string   Namespace

Global Flags:
  -o, --output string   Output format. Empty for human-readable, 'json' or 'json-line'

Use "headscale nodes [command] --help" for more information about a command.
$

This disables that.

I don't have strong opinions of this, iirc this might be set up before the log level?
If it can disabled by setting lower than tracing, I would suggest that rather than removing.

I am using the default log level - and the output happens on the command line.
Personally - I think it's annoying. I know I have color disabled, I set NO_COLOR explicitly and any thing that is informing me of that is just adding noise.

by "default log level" I mean I have nothing explicitly set in my config.json that increases or decreases the logging.


Does yolov5-icevision support video streaming as like the original YOLOv5?

Hello,
I wanna use LoadStreams in YOLOv5/utils/datasets.py to handle video streaming, but I can't find any similar functions in yolov5-icevision. Doesn't yolov5-icevision support object detection for video streaming yet?
Thanks in advance.

We currently don't have helper functions for videos =/
I think it might be possible to still train your model using icevision and then using their LoadStreams as their instruct to run on videos (since we're basically training their models anyways)

Thanks for informing me!


[SPARK-44868][SQL] Convert datetime to string by to_char/to_varchar

What changes were proposed in this pull request?
In the PR, I propose to use the DateFormatClass expression for formatting a datetime expression to string in the to_char/to_varchar functions, and the ToCharacter expression in other cases.
Why are the changes needed?
To achieve feature parity with other systems, and make the migration from them eaiser:

Snowflake: https://docs.snowflake.com/en/sql-reference/functions/to_char
PostgreSQL: https://www.postgresql.org/docs/current/functions-formatting.html
MariaDB: https://mariadb.com/kb/en/to_char/
DB2: https://www.ibm.com/docs/en/db2/11.5?topic=sf-char
Exasol: https://docs.exasol.com/db/latest/sql_references/functions/alphabeticallistfunctions/to_char (datetime).htm

Does this PR introduce any user-facing change?
No, but it can if an user's query depends on errors from to_char.
How was this patch tested?
By running the affected test suites:
$ SPARK_GENERATE_GOLDEN_FILES=1 PYSPARK_PYTHON=python3 build/sbt "sql/testOnly org.apache.spark.sql.SQLQueryTestSuite"
$ build/sbt "test:testOnly *StringExpressionsSuite"
$ build/sbt "sql/test:testOnly org.apache.spark.sql.expressions.ExpressionInfoSuite"

Merged to master.

late LGTM


Unable to use Conda's libclang package

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
Unable to use Conda's libclang package, using conda install libclang will result in an error when import clang. But when I use pip install libclang, import clang will run normally,it's so strange!?And my colleagues and I have both tried, but it shouldn't be a problem with the computer.
Installed packages
libclang from pypi is ok!

(plane) PS C:\Users\Administrator\Desktop\hello_python> conda list
# packages in environment at D:\anaconda\envs\plane:
#
# Name                    Version                   Build  Channel
ca-certificates           2023.01.10           haa95532_0    https://mirrors.ustc.edu.cn/anaconda/pkgs/main
certifi                   2022.12.7        py38haa95532_0    https://mirrors.ustc.edu.cn/anaconda/pkgs/main
et_xmlfile                1.1.0            py38haa95532_0    https://mirrors.ustc.edu.cn/anaconda/pkgs/main
libclang                  16.0.0                   pypi_0    pypi
lxml                      4.9.2                    pypi_0    pypi
openpyxl                  3.0.10           py38h2bbff1b_0    https://mirrors.ustc.edu.cn/anaconda/pkgs/main
openssl                   1.1.1t               h2bbff1b_0    https://mirrors.ustc.edu.cn/anaconda/pkgs/main
pip                       23.0.1           py38haa95532_0    https://mirrors.ustc.edu.cn/anaconda/pkgs/main
python                    3.8.8                hdbf39b2_5    https://mirrors.ustc.edu.cn/anaconda/pkgs/main
python-docx               0.8.11                   pypi_0    pypi
setuptools                65.6.3           py38haa95532_0    https://mirrors.ustc.edu.cn/anaconda/pkgs/main
sqlite                    3.41.1               h2bbff1b_0    https://mirrors.ustc.edu.cn/anaconda/pkgs/main
vc                        14.2                 h21ff451_1    https://mirrors.ustc.edu.cn/anaconda/pkgs/main
vs2015_runtime            14.27.29016          h5e58377_2    https://mirrors.ustc.edu.cn/anaconda/pkgs/main
wheel                     0.38.4           py38haa95532_0    https://mirrors.ustc.edu.cn/anaconda/pkgs/main
wincertstore              0.2              py38haa95532_2    https://mirrors.ustc.edu.cn/anaconda/pkgs/main

### Environment info

```shell
(plane) PS C:\Users\Administrator\Desktop\hello_python> conda info

     active environment : plane
    active env location : D:\anaconda\envs\plane
            shell level : 2
       user config file : C:\Users\Administrator\.condarc
 populated config files : C:\Users\Administrator\.condarc
          conda version : 4.10.1
    conda-build version : 3.21.4
         python version : 3.8.8.final.0
       virtual packages : __win=0=0
                          __archspec=1=x86_64
       base environment : D:\anaconda  (writable)
      conda av data dir : D:\anaconda\etc\conda
  conda av metadata url : https://repo.anaconda.com/pkgs/main
           channel URLs : https://mirrors.bfsu.edu.cn/anaconda/cloud/pytorch/win-64
                          https://mirrors.bfsu.edu.cn/anaconda/cloud/pytorch/noarch
                          https://mirrors.ustc.edu.cn/anaconda/pkgs/free/win-64
                          https://mirrors.ustc.edu.cn/anaconda/pkgs/free/noarch
                          https://mirrors.ustc.edu.cn/anaconda/pkgs/main/win-64
                          https://mirrors.ustc.edu.cn/anaconda/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/main/win-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/win-64
                          https://repo.anaconda.com/pkgs/r/noarch
                          https://repo.anaconda.com/pkgs/msys2/win-64
                          https://repo.anaconda.com/pkgs/msys2/noarch
          package cache : D:\anaconda\pkgs
                          C:\Users\Administrator\.conda\pkgs
                          C:\Users\Administrator\AppData\Local\conda\conda\pkgs
       envs directories : D:\anaconda\envs
                          C:\Users\Administrator\.conda\envs
                          C:\Users\Administrator\AppData\Local\conda\conda\envs
               platform : win-64
             user-agent : conda/4.10.1 requests/2.25.1 CPython/3.8.8 Windows/10 Windows/10.0.22621
          administrator : True
             netrc file : None
           offline mode : False

In general, please provide the output of conda list for the failing environment, not the one that's working with PyPI.
That said, conda-forge and PyPI have different namespaces, and not every package maps 1:1. PyPI lives in a python-only world, so sometimes packages take names that are already occupied in the broader scope of conda-packages.
This appears for several packages, but in any case, libclang in conda-forge is a pure C library with no python bindings, so you cannot import clang. To have the python bindings, you need to specify python-clang as your dependency.

Closing this as solved. Please us know if your issues persist when using python-clang as a dependency.


Updated rbac to use version v1 instead of v1beta1

ClusterRole and ClusterRoleBinding don't exist in rbac.authorization.k8s.io/v1beta1
What does this PR do?
Updates the example configuration to use endpoint rbac.authorization.k8s.io/v1 instead of rbac.authorization.k8s.io/v1beta1, because ClusterRole and ClusterRoleBinding don't exist in v1beta1 anymore.
Motivation
Was running v1.7 traefik to test something in a local cluster and noticed the documentation wasn't correct.

Actually, scrap this. If you're using a later version of k8s, probably shouldn't be using 1.7 anyway.