useTestNg() has limited list of command line args which can be passed to TestNg runner

The list of command line arguments supported by TestNg runner is changing. New arguments appear. TestNg plugin supports parameters defined in TestNgOptions class only. Which is not flexible and limits features can be used.
Expected Behavior
It is possible to pass TestNg command line arguments as string key/value pairs.
Current Behavior
Can only set limited number of command line attributes.
Context
It is possible to inject TestNg listeners via ServiceLoader. A feature which allows to disable some of injected implementations was added in latest TestNg versions. I want to pass a command line argument "spiListenersToSkip"; but it's not possible as the argument is not supported by plugin.

Could you pls. provide an exact setup/reproducer to check against, if we add the missing features?

@jbartok Sure. Will provide.

Please, see example projects here: https://github.com/achahan/spiExample
projA contains implementations for two TestNg listeners: MySuiteListener, MyTestListener.
Above listeners will be wired to projB via Service Loader since projB depends on proA.
So, if one will run "gradle test" from projB root the output will be the following:
On Suite Start
On Start
.........
On Finish
On Suite Finish
Now I want to disable wired "MySuiteListener" so that there were no "On Suite ..." messages. This feature is available from TestNg 7.4. There is a TestNg command line parameter "-spilistenerstoskip" followed by comma-separated list of listeners to skip.
The problem is that gradle testNg plugin does not support above mentioned parameter. So, "test" task can't be used with excluded listener.
However list of listeners to skip can be passed from "JavaExec" based gradle task. See projB/build.gradle/runJavaExec task for example.
So, the issue was created because it might make sense to add custom parameters support to gradle testng plugin. In order not to support each of possible TestNg command line parameters. So that one could do something like example below from gradle test task:
test {
useTestNG() {
arguments = [suite:"suite location", spilistenerstoskip:"com.example.MySuiteListener", :"some value"]
}
}

Sorry for the late reply.
Thank you for your interest in Gradle!
This feature request is in the backlog of the relevant team, but this area of Gradle is currently not a focus one, so it might take a while before it gets implemented.

I would like to have this feature added to TestNGOptions class so we we can inject this argument -reporter with value org.testng.reporters.XMLReporter:generateTestResultAttributes=true,generateGroupsAttribute=true to TestNG, so TestNG test task will be executed with these specific options. It will then enable TestNG to produce XML reprots with additional custom attributes.
I have explained this in detail in my ticket:
Ability to inject custom comandline arguments to TestNG is missing
I don't think this will require much effort on Gradle's end to enable this feature to allow users to send custom args to TestNG invocation. This is already supported by TestNG and Maven surefire plugin. It will be also helpful for many other use cases where people are using Gradle with TestNG. Please prioritise this issue if possible.
Existing Gradle DSL is really limited in terms of TestNG usage and it would be really helpful to allow this option for maximum flexibility while using TestNG as test framework with gradle.

I have a similar request because TestNG has added a feature I need to use but cannot pass the argument to useTestNG().
Specifically -listenercomparator=org.testng.MyComparator to allow ordering the listeners.
See TestNG issue #2874
I could look at the code needed to make this happen in Gradle. Is anyone actively working on this now?
Thanks in advance

Ability to inject custom comandline arguments to TestNG is missing

@ljacomet could you please provide some hints or updates on this issue? perhaps @jensenbrian could help with PR

Hi again. I'm looking for any guidance here.
Without the ability to pass arguments it is causing issues with tests in Selenide issue #2755
Thank you

@ov7a - Is it possible to at least hint at the relevant sections of the Gradle codebase that needs to be addressed to accommodate this so that some brave soul who lands in the comments of this issue tries to take a jab at this issue and perhaps even raise a Pull Request? 😁

@krmahadevan You can take a look at TestNGOptions, testng package and their usage.
Note that this area is out of focus for now, and before opening a PR, please share your design ideas in this issue, so they can be eventually discussed with the @gradle/bt-jvm team, who is responsible for that area.

@ov7a when you say not in focus does it mean that for users who want to use newer features in TestNG they are better off in creating their own custom Gradle tasks?
Want to get a sense of what is the recommendation going forward.

@krmahadevan there are some workarounds described in

https://github.com/gradle/gradle/issues/29135

There is also an option to add support for parameters one by one using the current approach, but it's not very sustainable long-term.

@ov7a Thank you so much for sharing this info. I will go through them.


webApiPermissionRequests : Microsoft Graph Error

Bug
Hi Team,
I am not able to deploy successfully when I add webapiPermissionRequest in my manifest .
Could you please help me on this . I need to use  Calendar events in  my application using Microsoft Graph API .
Thanks,
Rani

What error are you getting? Could you share the exact permission scope snippet?

   "webApiPermissionRequests": [{
        "resource": "Microsoft Graph",
        "scope": "Calendar.Read"
    }

When I deploy the code I get "Error in the application"

Is your tenant on the targeted release?

If the Error in the application" comes when you add the package to app-catalog, then this indicates that your tenant is not marked to be in Targeted Release. Please confirm that it's case. Notice that the setting has to be on tenant level.


Exception: Result incomplete: Write stall

Hello,
the db.write with a WriteBatch object is throwing the "Exception: Result incomplete: Write stall" error. I'm having a hard time debugging the issue.
My situation involves a process (gatherer) that generates key-value pairs and puts them in a Queue.
Another process (writer) that gets a batch of key-value pairs from the Queue, checks whether the keys are already in the database, and if they are not then it puts a WriteBatch object. Once the entire batch has been process I call the db.write method.
Do you have any suggestion of how I can investigate this issue?
Thanks,
Michelangelo

Is the batch size and everything else totally identical in the two cases (sub-process vs main process)? Emm, curious.

Write stall may suggest that each write batch is too large, but I am unsure about this too.

There are several reasons that might cause a write stall.
Maybe this link is helpful too: https://github.com/EighteenZi/rocksdb_wiki/blob/master/RocksDB-Tuning-Guide.md#flushing-options.
In your case, I conjecture that maybe your write batch fills up all the memtable and causes write to stop. So, you might try to increase the write_buffer_size or max_write_buffer_number and see if it helps.

Can you provide a minimal example? So I may try to reproduce it.

I've been unsuccessfully trying to reproduce the issue on a simplified version of the code. It seems like you conjecture is correct. It's rather caused by some problem with the options of the db rather than with the multiprocessing.
Further, I was spawning processes from an IPython console. This may also be part of the issue.
Thank you very much!


ReactPlayer not working in React 17

Current Behavior
@cookpete, Hi!
I can confirm that ReactPlayer not working in React 17 with client-side rendering.
I use react-player version 2.8.2. Error came right after i upgrade react and react-dom packages versions from "16.14.0" to "17.0.1".
I saw other react 17 issue https://github.com/cookpete/react-player/issues/1165, but in my case it doesn't connected with NextJS because i don't use it so i create the separated issue for react 17 only.
Current packages versions:
...
"react-player": "2.8.2",
"react": "17.0.1",
"react-dom": "17.0.1",
...

Console error message:
Uncaught undefined
The above error occurred in one of your React components:
    in Unknown (created by ReactPlayer)
    in Suspense (created by ReactPlayer)
    in div (created by ReactPlayer)
    in ReactPlayer (created by PlayerBlock)

Steps to reproduce:
I use "react-player" in my "Movies" project and created branch with "react" and "react-dom" packages bumped to "17.0.1": https://github.com/nk11dev/movies/tree/REACT-17-react-player-error-reproduce

clone repo and install dependencies
run npm run dev
go to root url (http://localhost:8080/, by default). I put "react-player" in the root script (/src/app/index.client.js) to easily reproduce error

Expected behavior:
As i mentioned above, i already use "react-player" in my app with react and react-dom packages  "16.14.0" versions and it works fine. Expected behavior is like there (player works ok): https://nk11dev-movies.herokuapp.com/movies/464052?lng=en. On site it runs in SSR mode, but errors come in client-side rendering too.
Environment:
Browser: Chrome 88.0.4324.150
Operating system: Windows 10

Looks like you need to bump @hot-loader/react-dom to 17.0.1 too.

Thanks, you're right. After updating @hot-loader/react-dom to 17.0.1 it works.

Same issue still in Gatsby 3.11.1. installed @hot-loader/react-dom and that made no difference


Repo folders and subdirectories

We should organize our files in a few main subdirectories:

img: images
data: data files
doc: documentation and any .md files directly relating to the project itself (Other docs like license, contract/code of conduct should probably just be left in root)
src: python/R scripts and jupyter notebooks

Agreed. So I will push the Code of Conduct (.md file) to the root.

I was thinking that it makes sense to organize our src folder into python_scripts and jupyter_notebooks, thoughts on this?


fix autocomplete do not hide on blur bug

Please makes sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's Contributing Guide.
[ ] Make sure you are merging your commits to dev branch.
[ ] Add some descriptions and refer relative issues for you PR.

修正 autocomplete 在 blur 事件触发 suggestions 时没有收起的问题 #2155
补充 trigger-on-focus 的文档

测试挂了


Doctrine UoW execution order vs. no flush policy

Hello,
I have two questions.
The documentation states:

Don't call flush() yourself: Once you have added this middleware, you shouldn't call EntityManager::flush() manually from inside your command handlers anymore.

Why should I not do that? (I also can not find any failing case in the tests)
How to handle a case when I want to replace an entity with unique constraints with another entity that would violate the constraints? Doctrine Unit of Work execute inserts before deletes, therefore violating the constraints. The standard solution to such situation is to call flush after the delete and again after the persist, but the library is discouraging that.

Nice library btw 👍  .

Why should I not do that?

The reason behind this is that during the handeling of the command you are in a running transaction and if you flush in a handler and the handler fails after it is done then half of the work is done. This can lead to data that is incorrect. But it is a suggestion and you can still do this if you want to but you need to be carful when doing a flush in a command.

(I also can not find any failing case in the tests)

In my opinion this is a suggestion not a hard requirement

How to handle a case when I want to replace an entity with unique constraints with another entity that would violate the constraints? Doctrine Unit of Work execute inserts before deletes, therefore violating the constraints. The standard solution to such situation is to call flush after the delete and again after the persist, but the library is discouraging that.

Yeah, this is the reason why I personally in rare cases flush inside a command handler I don't have a other solution for this.

Thanks for your explanation! :)

The reason behind this is that during the handeling of the command you are in a running transaction and if you flush in a handler and the handler fails after it is done then half of the work is done

Not sure what you mean. If I fail in a transaction then the whole transaction is rolled back, at least when it comes to the SQL transactions. Moreover, a flush does not commit the transaction. Therefore flush should result only in SQL being executed and should not leave any corupted data if it fails.
Am I missing something?

Not sure what you mean. If I fail in a transaction then the whole transaction is rolled back, at least when it comes to the SQL transactions. Moreover, a flush does not commit the transaction. Therefore flush should result only in SQL being executed and should not leave any corupted data if it fails.

You are right in this case;

http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/transactions-and-concurrency.html

But the statement still stands as you shouldn't call EntityManager::flush() manually because the middleware takes care of that. But you can if you really need it :-)


add school603-spb.txt

Request to add Saint-Petersburg State Budgetary Educational Institution School 603

@trappergor First stage of verification passed, official domain is school603-spb.ru as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@trappergor Pull request merged. Thank you.


Prd daemon fixes

Enable opal-prd on P9 FSP system and add few validations.
-Vasant

This change is

Awesome, thanks!


PHP 8.0 support

Feature Request

Q
A

New Feature
yes

Summary
To be prepared for the december release of PHP 8.0, this repository has some additional TODOs to be tested against the new major version.
In order to make this repository compatible, one has to follow these steps:

[ ] Modify composer.json to provide support for PHP 8.0 by adding the constraint ~8.0.0
[ ] Modify composer.json to drop support for PHP less than 7.3
[ ] Modify composer.json to implement phpunit 9.3 which supports PHP 7.3+
[ ] Modify .travis.yml to ignore platform requirements when installing composer dependencies (simply add --ignore-platform-reqs to COMPOSER_ARGS env variable)
[ ] Modify .travis.yml to add PHP 8.0 to the matrix (NOTE: Do not allow failures as PHP 8.0 has a feature freeze since 2020-08-04!)
[ ] Modify source code in case there are incompatibilities with PHP 8.0

@boesing
Is this issue still relevant?

@froschdesign nope, will close this now :)


Documentation (& code) regarding determining temp_storage_bytes not very clear

I would like to be able to determine my device-wide primitive's temp_storage_bytes before I have all of the primitive's arguments ready. The interface for obtaining it ostensibly requires everything to be ready for the actual run - and the documentation does not make it clear what arguments it actually needs and what it's going to do with them (e.g. will it look at the input at all, in any way? Probably not, but who knows)
Also, delving into the source (in my case: dispatch_select_if.cuh), I see:
if (d_temp_storage == NULL)
{
    // Return if the caller is simply requesting the size of the storage allocation
    break;
}

which is super-weird. What if I passed a pointer to a size_t containing 2^64-1? Would my code be led to believe it has to allocate that much? Hmm.

From my experience with library, the arguments to calculate temp storage size are data type(s) (templated) and length of it.
I call the methods very early in the code with all pointers set to nullptr and only non-zero argument is size of the data to be processed and get the temp size that works fine till the very end.
Hope this helps.

Yep. That is the case for everything currently in CUB: we need to know the data types and length of input.

We should add a section to the docs about this. A generic section that explains the common pattern and conventions for using the cub::Device* API would be useful.


always take the last lastBuiltRevision

sometimes, a source-release job is triggered by multiple merges, which
results in multiple BuildData objects being present in the JSON output
the old jq query printed all SHA1 of these, resulting in bad Debian
changelogs being generated
lets take only the last entry and print its SHA1

if you're curious (I know you are!), one such job was: https://ci.theforeman.org/job/foreman-develop-source-release/1404/

I wondered if there was a native way of doing this. In https://github.com/theforeman/jenkins-jobs/pull/133 I wondered about this. Perhaps we can create a dedicated archive file for the commit?

Funfact, we actually do!
https://ci.theforeman.org/job/foreman-develop-source-release/1404/artifact/commit

So I guess this is the way? https://github.com/theforeman/jenkins-jobs/pull/133/files#r743590778


Do not assume libcupti.so location

libcupti.so can sometimes be located under cuda/extras/CUPTI/lib64/ instead

@cloudhan @jsharpe @ryanleary please let me know if there are any other contributors better suited for reviewing the PR


[5.8] Add previous method to UrlGenerator interface

The UrlGenerator interface does not contain the previous() method that is implemented by the UrlGenerator class
Adding it allows me to use previous() while referencing the interface (and keep my IDE happy).
It would add an extra burden on other implementations of that interface that are out in the wild, making it a breaking change.
(Reapplied https://github.com/laravel/framework/pull/25609 to master instead of 5.7)

is there a place we can start tracking these breaking changes right away so it's easier for us to write a good upgrade guide for 5.8?
do we just start the upgrade guide for 5.8 right now?

https://github.com/laravel/docs/pull/4515

@browner12 , maybe it will be better to have changelog within this repository?
It will help to add the changes to changelog with actual changes in one PR


404 on enumerating contents of a shared folder using One drive for business API

I was using one drive for business API and was trying to retrieve and access the shared with me files and folders.

I am not able to enumerate the contents of shared folder. It always returns 404 Not Found error.
part of the response from the GET <serviceEndpointUri>/drive/sharedWithMe
`"remoteItem": {
"createdBy": {
  "user": {
    "displayName": "abc"
  }
},
"createdDateTime": "0001-01-01T00:00:00Z",
"fileSystemInfo": {
  "createdDateTime": "0001-01-01T00:00:00Z",
  "lastModifiedDateTime": "2016-09-02T11:57:00Z"
},
"folder": {
  "childCount": 0
},
"id": "03573WEOCZ4LCMXDTQ6ZAJMHHM62HZ7OK6",
"lastModifiedBy": {
  "user": {
    "displayName": "abc"
  }
},
"lastModifiedDateTime": "2016-09-02T11:57:00Z",
"name": "bm",
"parentReference": {
  "driveId": "b!ZoYKIsneuEOLnrc5r-V_pacv7nIc2-tMiOMGPnRSb3y_JXvXPJYsTacVGx6k6DFd"
}

}`
Request Made : GET <serviceEndPointUri>/drives/b!ZoYKIsneuEOLnrc5r-V_pacv7nIc2-tMiOMGPnRSb3y_JXvXPJYsTacVGx6k6DFd/items/03573WEOCZ4LCMXDTQ6ZAJMHHM62HZ7OK6/children. Request always returns 404 Not found error.
Response :
{ "error": { "code": "itemNotFound", "message": "The resource could not be found." } }
Tried with different shared folders in the response same error with every folder.

I have shared two files, one with only read permission and the other with read and write permission. When I made a call using GET <serviceEndpointUri>/drive/sharedWithMe, there is no difference in the response for both the files. How do we retrieve the permissions associated with a shared file?
I tried GET /drives/<drive-id>/items/{item-id}/permissions but even this return 404 resource not found error. Same is the case with the copy and also download operation. What could be the possible issue? Is it a different web service call that has to be made for these operations?

+1

@katahir any update on this

Facing same issue. I am trying to GET "/content" instead of "/children". Any idea or workarounds? Files however, are visible online. Any help/workaround is much appreciated.
Thank you.

You can't use the same <serviceEndPointUri> for calls to your own and to a remote drive.

I think it may have something to do with the scopes you have in the access token. Can you please paste the scopes part here. I tried this on my test tenant and I cant repro the issue. The scopes needed to access files in drives not owned by the user are files.readwrite.all/files.read.all. Can you request these scopes and then try again?

@katahir right now, we ask the customers only for two permissions

@katahir right now, we ask the customers only for two permissions. 1. Read user profiles 2. Read and write user files. Is requesting for files.readwrite.all/files.read.all scopes, the only way to download, access shared with me files?

@katahir we have tried adding the files.readwrite.all and files.read.all scopes but still the same issue persists. part of the response after login is as follows:
`{
 "token_type": "Bearer",
 "scope": "Directory.AccessAsUser.All Directory.Read.All Directory.ReadWrite.All **Files.Read.All Files.ReadWrite.All** Group.Read.All Group.ReadWrite.All MyFiles.Write User.Read User.Read.All User.ReadBasic.All",
 "expires_in": "3599",
 "ext_expires_in": "0",
 "expires_on": "1493217576",
 "not_before": "1493213676",
 "resource": "https://api.office.com/discovery/",
 "access_token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6ImEzUU4wQlpTN3M0bk4tQmRyamJGMFlfTGRNTSIsImtpZCI6ImEzUU4wQlpTN3M0bk4tQmRyamJGMFlfTGRNTSJ9.eyJhdWQiOiJodHRwczovL2FwaS5vZmZpY2UuY29tL2Rpc2NvdmVyeS8iLCJpc3MiOiJodHRwczovL3N0cy53aW5kb3dzLm5ldC8zMmQ4NWY2NS02YTYyLTQzMmEtOWFiMy05NDFhM2I5Zjg1YmQvIiwiaWF0IjoxNDkzMjEzNjc2LCJuYmYiOjE0OTMyMTM2NzYsImV4cCI6MTQ5MzIxNzU3NiwiYWNyIjoiMSIsImFpbyI6IlkyWmdZTGhpM2ZZcWUrbTErVXhYNnB2dXQvV2ZZOG9wN09PK3ZPYzNyNmJkNGNCTjcwMEIiLCJhbXIiOlsicHdkIl0sImFwcGlkIjoiNjBiODk5YTYtZmJlNC00MjI5LTg2ZTctMzMxZGM3ZGVlODA4IiwiYXBwaWRhY3IiOiIwIiwiZmFtaWx5X25hbWUiOiJNRE0wNSIsImdpdmVuX25hbWUiOiJmaWJlcmxpbmtxYSIsImlwYWRkciI6IjExMS45My4yNDUuMzciLCJuYW1lIjoi55Sz6KuL54Sh44GX44Ki44OX44Oq44Kx44O844K344On44Oz5LiA6KanIiwib2lkIjoiZTNkY2YyMzUtNjVmNy00MmZkLWJjNWYtYjM3ZjhhNTU0ZGJjIiwicGxhdGYiOiIzIiwicHVpZCI6IjEwMDMzRkZGODY5M0RDODkiLCJzY3AiOiJEaXJlY3RvcnkuQWNjZXNzQXNVc2VyLkFsbCBEaXJlY3RvcnkuUmVhZC5BbGwgRGlyZWN0b3J5LlJlYWRXcml0ZS5BbGwgRmlsZXMuUmVhZC5BbGwgRmlsZXMuUmVhZFdyaXRlLkFsbCBHcm91cC5SZWFkLkFsbCBHcm91cC5SZWFkV3JpdGUuQWxsIE15RmlsZXMuV3JpdGUgVXNlci5SZWFkIFVzZXIuUmVhZC5BbGwgVXNlci5SZWFkQmFzaWMuQWxsIiwic3ViIjoiNzV1b3ak1zSkE0VndpUEZhT2RxcmhqNCIsInRpZCI6IjMyZDg1ZjY1LTZhNjItNDMyYS05YWIzLTk0MWEzYjlmODViZCIsInVuaXF1ZV9uYW1lIjoiZmliZXJsaW5rcWFAbWRtMDUub25taWNyb3NvZnQuY29tIiwidXBuIjoiZmliZXJsaW5rcWFAbWRtMDUub25taWNyb3NvZnQuY29tIiwidmVyIjoiMS4wIn0.H2fPIJcFgnR4kM1jeQuFsndbjx-Ns5xQcoZNA-HHDyEZ7USBsEW6lb8bCY
}`

you can see that the scope value has the files.readwrite.all/files.read.all  in it.

Can you please share the response headers of a 404 request with me? Since I cant repro, I will need the logs to see what is going on.

@katahir Here is the response headers for a 404 api request made to download a shared file.
Cache-Control →private, max-age=0
Content-Type →application/json;odata.metadata=minimal;odata.streaming=true;IEEE754Compatible=false;charset=utf-8
Date →Tue, 02 May 2017 05:20:12 GMT
Expires →Mon, 17 Apr 2017 05:20:12 GMT
Last-Modified →Tue, 02 May 2017 05:20:12 GMT
MicrosoftSharePointTeamServices →<IP_ADDRESS>20
ODATA-VERSION →4.0
P3P →CP="ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI"
SPClientServiceRequestDuration →23
SPRequestDuration →421
SPRequestGuid →6e9ced9d-9017-3000-165b-850aa9f80e92
Server →Microsoft-IIS/8.5
Strict-Transport-Security →max-age=31536000
Transfer-Encoding →chunked
X-AspNet-Version →4.0.30319
X-Content-Type-Options →nosniff
X-FRAME-OPTIONS →SAMEORIGIN
X-MS-InvokeApp →1; RequireReadOnly
X-MSEdge-Ref →Ref A: 826547FB92D445EFA734FED43DCE2C57 Ref B: BOM01EDGE0221 Ref C: Mon May 1 22:20:13 2017 PST
X-Powered-By →ASP.NET
X-SP-SERVERSTATE →ReadOnly=0
X-SharePointHealthScore →0
request-id →6e9ced9d-9017-3000-165b-850aa9f80e92`
```

@katahir any update on this.

@rgregg @katahir any update for this, we have the customer pushing for this. And we are not able to proceed.

@katahir @rgregg it is really disappointment to see no update here at all.

Facing exactly same issue. Any idea or workarounds? Any help is much appreciated.
Thank you.

Hi sanjaynetision, can you include the request, and the full response (headers + body) for the error you are seeing?

@rgregg thanks for quick response.Here is my code.
GET /_api/v2.0/me/drive/sharedwithme
when I run above code I got the result below :
{
<EMAIL_ADDRESS>"#oneDrive.item",
<EMAIL_ADDRESS>"/_api/v2.0/drive/items/01YH4M3NJX244RV73L5BDLAYVW2H6FJNWE",
<EMAIL_ADDRESS>"drive/items/01YH4M3NJX244RV73L5BDLAYVW2H6FJNWE",
"createdBy": {
"user": {
"email": "",
"displayName": ""
}
},
"createdDateTime": "0001-01-01T00:00:00Z",
"id": "01YH4M3NJX244RV73L5BDLAYVW2H6FJNWE",
"lastModifiedBy": {
"user": {
"email": "",
"displayName": ""
}
},
"lastModifiedDateTime": "2017-11-09T10:12:00Z",
"name": "CSLTest",
"parentReference": {
"driveId": "b!JDUyUEXv30Ox3fJCk9h9k7YuJTRxBXpOlg7swVPzQSlbBMNLaGQrQYjZGhpaFPT0",
"driveType": "business"
},
"fileSystemInfo": {
"createdDateTime": "0001-01-01T00:00:00Z",
"lastModifiedDateTime": "2017-11-09T10:12:00Z"
},
"folder": {
"childCount": 0
},
"remoteItem": {
"createdBy": {
"user": {
"email"<EMAIL_ADDRESS>"displayName": "Pallav Jain"
}
},
"createdDateTime": "0001-01-01T00:00:00Z",
"fileSystemInfo": {
"createdDateTime": "0001-01-01T00:00:00Z",
"lastModifiedDateTime": "2017-11-09T10:12:00Z"
},
"folder": {
"childCount": 0
},
"id": "01YH4M3NJX244RV73L5BDLAYVW2H6FJNWE",
"lastModifiedBy": {
"user": {
"email": "",
"displayName": ""
}
},
"lastModifiedDateTime": "2017-11-09T10:12:00Z",
"name": "CSLTest",
"parentReference": {
"driveId": "b!sBnp-sc0oE28Ol8s8f7gCgLVjw2KNfdEkFYC3I1gjb7h58QNe-f9RoXQ8Nc3YpPM"
},
"shared": {
"scope": "users",
"sharedBy": {
"user": {
"email": "",
"displayName": "**"
}
},
"sharedDateTime": "2017-11-09T10:14:00Z"
},
},
GET  /_api/v2.0/drives/b!sBnp-sc0oE28Ol8s8f7gCgLVjw2KNfdEkFYC3I1gjb7h58QNe-f9RoXQ8Nc3YpPM/items/01YH4M3NJX244RV73L5BDLAYVW2H6FJNWE
authorization : Bearer
when I run above code I got the result below :
Response Header :
cache-control:
private, max-age=0
transfer-encoding:
chunked
content-type:
application/json;odata.metadata=minimal;odata.streaming=true;IEEE754Compatible=false;charset=utf-8
expires:
Mon, 30 Oct 2017 08:43:05 GMT
last-modified:
Tue, 14 Nov 2017 09:43:05 GMT
server:
Microsoft-IIS/8.5
x-sharepointhealthscore:
0
x-sp-serverstate:
ReadOnly=0
odata-version:
4.0
spclientservicerequestduration:
107
sprequestduration:
234
x-aspnet-version:
4.0.30319
sprequestguid:
5fc12c9e-50ef-4000-f1c5-e777b4a38ce0
request-id:
5fc12c9e-50ef-4000-f1c5-e777b4a38ce0
ms-cv:
nizBX+9QAEDxxed3tKOM4A.0
strict-transport-security:
max-age=31536000
x-frame-options:
SAMEORIGIN
x-powered-by:
ASP.NET
microsoftsharepointteamservices:
<IP_ADDRESS>01
x-content-type-options:
nosniff
x-ms-invokeapp:
1; RequireReadOnly
p3p:
CP="ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI"
date:
Tue, 14 Nov 2017 09:43:05 GMT
{
"error": {
"code": "itemNotFound",
"message": "The resource could not be found."
}
Please Help !

Thanks for the details. I’m going to pull up the logs and see what’s happening server side. Just to confirm though, which permissions / scopes has your app requested? Can you use https://jwt.ms to decode your access token and copy out the scopes in the token for me too?

@rgregg , Thanks for the reply.
I have decoded the token and following are the scopes .Do I need to mention any other scopes
to access shared files?
"scp": "email Files.ReadWrite Mail.Send offline_access openid profile User.Read",
"app_displayname": "DaymonOneDrive",
"appid": "37c2f667-a3d5-4d66-8a93-effcc80f04bb",
"appidacr": "1",
"oid": "c9472432-d36b-4dd0-a97a-1c5a1474aa57",
"puid": "10033FFFA0E8BB71",
"scp": "email Files.ReadWrite Mail.Send offline_access openid profile User.Read",
"signin_state": [
"kmsi"
],

@rgregg Any update on this.Please help.

@sanjaynetision It looks like you're missing the Files.ReadWrite.All permission scope, which is required to get access to shared files.

Sorry about this very old issue going stale.  If this is still reproducing, could you please provide updated request & response information to help us investigate further?  Thanks.


tweaks to try to make it friendlier for the uninitiated

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


fix: Update event handing documentation for api 2.0.0

[ ] I have added automatic tests where applicable.
[x] The PR contains a description of what has been changed.
[ ] The description contains manual test instructions.
[ ] The PR contains updates to the release notes.
[x] I have verified that the documentation is still up to date.

Changes
Update documentation passing auto_connect_event_hub=True in event handling examples.

duplicate of : https://github.com/ftrackhq/ftrack-python/pull/11


Is it possible to add headless run ?

Well i know it is technically possible with some workaround. I just hacked the library to add test running in xvfb. This is a quick and (realy) dirty implementation.
modify the init.py at the root library folder
`
...
required modules
import os
import Xlib.display
from pyvirtualdisplay.smartdisplay import SmartDisplay
new method to add running test in xvfb
def start_xvfb(self, width=1920, height=1080, depth=24):
'''Allow to execute tests in a virtual display (Xvfb)'''
LOGGER.info("STARTING VIRTUAL DISPLAY : %sx%sx%s " % (width, height, depth))
display = SmartDisplay(visible=0, size=(width, height), color_depth=depth)
display.start()
SmartDisplay()
# this is the tricky part !
ag._pyautogui_x11._display = Xlib.display.Display(os.environ["DISPLAY"])
LOGGER.info("DISPLAY IS : %s " % os.environ["DISPLAY"])
....
`
All of this is just a copy/paste implementation from this post : http://fredtantini.free.fr/blog/index.php?article58/automatiser-des-actions-avec-selenium-pyautogui-et-xvfb
Of course this is just a proof of concept that just work (except you have to take care of windows decoration) and just for Gnu/linux distro.

Caution: this will work only if your dev environment is identical to runner. Especially if you plan to rely on decorated windows and dialog. If you develop on unity and want to run on gnome or lxde this will not work.

Couldn't you do this with xvfb-run? That way you would not need to hack the library and the library would not need to concern about if it's running headless or not. xvfb-run linux command comes when you install Xvfb.
Could you test if this works for you (without your solution at all):
$ xvfb-run robot my_IHL_tests/

Thx for the answer, i know xvfb is capable (the solution provided encapsulate xvfb call). The main benefit is to be able to pass arguments (resolution, depth ...) from within scenario. Similary i could have used my own bindings with pyautogui and not use ImageHorizonLibrary, but your lib is a more convenient way to achieve my goals.  I will fork and patch so it can be integrated in my works. Thx anyway this was a great job.

No problem, glad to hear the lib is used :)
Out of curiosity, what kind of test case requires you to set up xvfb dynamically during test execution?


RTSP Ondemand Proxy - Regression from 1.0.0 to 1.0.1+

Which version are you using?
v1.0.3 (issue starts with v1.0.1)
Which operating system are you using?

[x ] Linux amd64 standard

Describe the issue
I have a fairly simple setup with some wyze cameras flashed with rtsp (wz_hacks) that mediamtx is a rtsp proxy server ondemand to clients (android tinycam). Wyze RTSP feeds are secured with basic user/pass authentication. No authentication on rtsp proxy output side.
Within a minute of starting the stream, the rtsp server seems to drop the stream and restart it; leading to a dropped video. Rolling back to v1.0.0 fixes the issue.
Describe how to replicate the issue

start the server (v1.0.1+) with rtsp ondemand proxy pointing to wyze camera rtsp feed
publish with proxy path
read proxy path with android rtsp (tinycam)
watch stream for little while, stream will drop out

Did you attach the server logs?
yes
Here is a IP cleaned log of v.1.0.1 from the time the stream started to when I closed it at the end.
2023/09/05 19:34:43 DEB [RTSP] [conn xxx.94:46618] [c->s] GET_PARAMETER rtsp://xxx.12:8554/xxx-crib/ RTSP/1.0
CSeq: 5
Session: e2e6f29d30ff4069aeb6722684291891
User-Agent: Live555

2023/09/05 19:34:43 DEB [RTSP] [conn xxx.94:46618] [s->c] RTSP/1.0 200 OK
CSeq: 5
Content-Type: text/parameters
Server: gortsplib
Session: e2e6f29d30ff4069aeb6722684291891

2023/09/05 19:35:01 DEB [path xxx-crib] [RTSP source] c->s OPTIONS rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic removed
CSeq: 7
Session: 00133631
User-Agent: gortsplib

2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] c->s TEARDOWN rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic removed
CSeq: 8
Session: 00133631
User-Agent: gortsplib

2023/09/05 19:35:11 INF [path xxx-crib] [RTSP source] stopped
2023/09/05 19:35:11 INF [RTSP] [conn xxx.94:46618] closed (terminated)
2023/09/05 19:35:11 INF [RTSP] [session 5e4e4190] destroyed (terminated)
2023/09/05 19:35:11 INF [RTSP] [conn xxx.94:46640] opened
2023/09/05 19:35:11 DEB [RTSP] [conn xxx.94:46640] [c->s] OPTIONS rtsp://xxx.12:8554/xxx-crib RTSP/1.0
CSeq: 1
User-Agent: Live555

2023/09/05 19:35:11 DEB [RTSP] [conn xxx.94:46640] [s->c] RTSP/1.0 200 OK
CSeq: 1
Public: DESCRIBE, ANNOUNCE, SETUP, PLAY, RECORD, PAUSE, GET_PARAMETER, TEARDOWN
Server: gortsplib

2023/09/05 19:35:11 DEB [RTSP] [conn xxx.94:46640] [c->s] DESCRIBE rtsp://xxx.12:8554/xxx-crib RTSP/1.0
Accept: application/sdp
CSeq: 2
User-Agent: Live555

2023/09/05 19:35:11 INF [path xxx-crib] [RTSP source] started
2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] connecting
2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] c->s OPTIONS rtsp://xxx.104:8554/1080p RTSP/1.0
CSeq: 1
User-Agent: gortsplib

2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 401 Unauthorized
CSeq: 1
WWW-Authenticate: Basic realm="go2rtc"

2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] c->s OPTIONS rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic removed
CSeq: 2
User-Agent: gortsplib

2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 2
Public: OPTIONS, SETUP, TEARDOWN, DESCRIBE, PLAY, PAUSE, ANNOUNCE, RECORD

2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] c->s DESCRIBE rtsp://xxx.104:8554/1080p RTSP/1.0
Accept: application/sdp
Authorization: Basic removed
CSeq: 3
User-Agent: gortsplib

2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 3
Content-Length: 236
Content-Type: application/sdp

v=0
o=- 1 1 IN IP4 <IP_ADDRESS>
s=go2rtc/1.6.0
c=IN IP4 <IP_ADDRESS>
t=0 0
m=video 0 RTP/AVP 96
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1
a=control:trackID=0
m=audio 0 RTP/AVP 97
a=rtpmap:97 PCML/16000
a=control:trackID=1

2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] c->s SETUP rtsp://xxx.104:8554/1080p/trackID=0 RTSP/1.0
Authorization: Basic removed
CSeq: 4
Transport: RTP/AVP/TCP;unicast;interleaved=0-1;mode=play
User-Agent: gortsplib

2023/09/05 19:35:12 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 4
Session: 45701311;timeout=60
Transport: RTP/AVP/TCP;unicast;interleaved=0-1

2023/09/05 19:35:12 DEB [path xxx-crib] [RTSP source] c->s SETUP rtsp://xxx.104:8554/1080p/trackID=1 RTSP/1.0
Authorization: Basic removed
CSeq: 5
Session: 45701311
Transport: RTP/AVP/TCP;unicast;interleaved=2-3;mode=play
User-Agent: gortsplib

2023/09/05 19:35:12 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 5
Session: 63948645;timeout=60
Transport: RTP/AVP/TCP;unicast;interleaved=2-3

2023/09/05 19:35:12 DEB [RTSP] [conn xxx.94:46640] [s->c] RTSP/1.0 200 OK
CSeq: 2
Content-Base: rtsp://xxx.12:8554/xxx-crib/
Content-Length: 306
Content-Type: application/sdp
Server: gortsplib

v=0
o=- 0 0 IN IP4 <IP_ADDRESS>
s=go2rtc/1.6.0
c=IN IP4 <IP_ADDRESS>
t=0 0
m=video 0 RTP/AVP 96
a=control:rtsp://xxx.12:8554/xxx-crib/trackID=0
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1
m=audio 0 RTP/AVP 97
a=control:rtsp://xxx.12:8554/xxx-crib/trackID=1
a=rtpmap:97 PCML/16000

2023/09/05 19:35:12 INF [path xxx-crib] [RTSP source] ready: 2 tracks (H264, Generic)
2023/09/05 19:35:12 DEB [path xxx-crib] [RTSP source] c->s PLAY rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic removed
CSeq: 6
Range: npt=0-
Session: 63948645
User-Agent: gortsplib

2023/09/05 19:35:12 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 6
Session: 63948645

2023/09/05 19:35:12 DEB [RTSP] [conn xxx.94:46640] [c->s] SETUP rtsp://xxx.12:8554/xxx-crib/trackID=0 RTSP/1.0
CSeq: 3
Transport: RTP/AVP/TCP;unicast;interleaved=0-1
User-Agent: Live555

2023/09/05 19:35:12 INF [RTSP] [session d3938ec3] created by xxx.94:46640
2023/09/05 19:35:12 DEB [RTSP] [conn xxx.94:46640] [s->c] RTSP/1.0 200 OK
CSeq: 3
Server: gortsplib
Session: 9e5f6c4dfcc64d6485e83d144eded89e
Transport: RTP/AVP/TCP;unicast;interleaved=0-1;ssrc=99BEB6C2

2023/09/05 19:35:12 DEB [RTSP] [conn xxx.94:46640] [c->s] PLAY rtsp://xxx.12:8554/xxx-crib/ RTSP/1.0
CSeq: 4
Range: npt=0.000-
Session: 9e5f6c4dfcc64d6485e83d144eded89e
User-Agent: Live555

2023/09/05 19:35:12 INF [RTSP] [session d3938ec3] is reading from path 'xxx-crib', with TCP, 1 track (H264)
2023/09/05 19:35:12 DEB [RTSP] [conn xxx.94:46640] [s->c] RTSP/1.0 200 OK
CSeq: 4
RTP-Info: url=rtsp://xxx.12:8554/xxx-crib/trackID=0;seq=2140;rtptime=580324895
Server: gortsplib
Session: 9e5f6c4dfcc64d6485e83d144eded89e

2023/09/05 19:35:13 WAR [path xxx-crib] [RTSP source] 24 RTP packets lost
2023/09/05 19:35:19 DEB [RTSP] [conn xxx.94:46640] [c->s] TEARDOWN rtsp://xxx.12:8554/xxx-crib/ RTSP/1.0
CSeq: 5
Session: 9e5f6c4dfcc64d6485e83d144eded89e
User-Agent: Live555

2023/09/05 19:35:19 INF [RTSP] [session d3938ec3] destroyed (torn down by xxx.94:46640)
2023/09/05 19:35:19 DEB [RTSP] [conn xxx.94:46640] [s->c] RTSP/1.0 200 OK
CSeq: 5
Server: gortsplib

2023/09/05 19:35:19 INF [RTSP] [conn xxx.94:46640] closed (EOF)
2023/09/05 19:35:29 INF [path xxx-crib] [RTSP source] stopped
2023/09/05 19:35:29 DEB [path xxx-crib] [RTSP source] c->s TEARDOWN rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic removed
CSeq: 7
Session: 63948645
User-Agent: gortsplib

in v1.0.1 I see a similar TEARDOWN event before the OPTIONS
2023/09/05 23:16:39 DEB [RTSP] [conn xxx:46836] [s->c] RTSP/1.0 200 OK
CSeq: 5
Content-Type: text/parameters
Server: gortsplib
Session: 4c9e887f382447b18376730ce904ce5e

2023/09/05 23:16:57 DEB [path xxx-crib] [RTSP source] c->s OPTIONS rtsp://xxx:8554/1080p RTSP/1.0
Authorization: Basic removed
CSeq: 7
Session: 59730328
User-Agent: gortsplib

2023/09/05 23:17:07 DEB [path xxx-crib] [RTSP source] c->s TEARDOWN rtsp://xxx:8554/1080p RTSP/1.0
Authorization: Basic removed
CSeq: 8
Session: 59730328
User-Agent: gortsplib

2023/09/05 23:17:07 INF [path xxx-crib] [RTSP source] stopped
2023/09/05 23:17:07 INF [RTSP] [conn xxx:46836] closed (terminated)
2023/09/05 23:17:07 INF [RTSP] [session 1b346072] destroyed (terminated)
2023/09/05 23:17:07 INF [RTSP] [conn xxx:46846] opened
2023/09/05 23:17:07 DEB [RTSP] [conn xxx:46846] [c->s] OPTIONS rtsp://xxx/xxx-crib RTSP/1.0
CSeq: 1
User-Agent: Live555

In v1.0.0 I don't see this TEARDOWN event, not sure if this is the result of another error but there's nothing else in the log.
Did you attach a network dump?
no

Hello, the log you posted are not enough to identify the issue since they start from a point in time when the stream was already running. Please attach a log that contains lines from the moment the server is started to the moment the issue occurs.

I masked the IP subnet and the authentication value but not sure if that is necessary. The stream has issues at
2023/09/05 19:35:11
2023/09/05 19:34:03 INF MediaMTX v1.0.3
2023/09/05 19:34:03 DEB [path xxx-crib] created
2023/09/05 19:34:03 DEB path manager created
2023/09/05 19:34:03 INF [RTSP] listener opened on :8554 (TCP)
2023/09/05 19:34:03 INF [RTMP] listener opened on :1935
2023/09/05 19:34:03 INF [HLS] listener opened on :8888
2023/09/05 19:34:03 INF [WebRTC] listener opened on :8889 (HTTP)
2023/09/05 19:34:03 INF [SRT] listener opened on :8890 (UDP)
2023/09/05 19:34:12 INF [RTSP] [conn xxx.94:46618] opened
2023/09/05 19:34:12 DEB [RTSP] [conn xxx.94:46618] [c->s] OPTIONS rtsp://xxx.12:8554/xxx-crib RTSP/1.0
CSeq: 1
User-Agent: Live555

2023/09/05 19:34:12 DEB [RTSP] [conn xxx.94:46618] [s->c] RTSP/1.0 200 OK
CSeq: 1
Public: DESCRIBE, ANNOUNCE, SETUP, PLAY, RECORD, PAUSE, GET_PARAMETER, TEARDOWN
Server: gortsplib

2023/09/05 19:34:12 DEB [RTSP] [conn xxx.94:46618] [c->s] DESCRIBE rtsp://xxx.12:8554/xxx-crib RTSP/1.0
Accept: application/sdp
CSeq: 2
User-Agent: Live555

2023/09/05 19:34:12 INF [path xxx-crib] [RTSP source] started
2023/09/05 19:34:12 DEB [path xxx-crib] [RTSP source] connecting
2023/09/05 19:34:12 DEB [path xxx-crib] [RTSP source] c->s OPTIONS rtsp://xxx.104:8554/1080p RTSP/1.0
CSeq: 1
User-Agent: gortsplib

2023/09/05 19:34:12 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 401 Unauthorized
CSeq: 1
WWW-Authenticate: Basic realm="go2rtc"

2023/09/05 19:34:12 DEB [path xxx-crib] [RTSP source] c->s OPTIONS rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic xxx
CSeq: 2
User-Agent: gortsplib

2023/09/05 19:34:12 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 2
Public: OPTIONS, SETUP, TEARDOWN, DESCRIBE, PLAY, PAUSE, ANNOUNCE, RECORD

2023/09/05 19:34:12 DEB [path xxx-crib] [RTSP source] c->s DESCRIBE rtsp://xxx.104:8554/1080p RTSP/1.0
Accept: application/sdp
Authorization: Basic xxx
CSeq: 3
User-Agent: gortsplib

2023/09/05 19:34:13 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 3
Content-Length: 236
Content-Type: application/sdp

v=0
o=- 1 1 IN IP4 <IP_ADDRESS>
s=go2rtc/1.6.0
c=IN IP4 <IP_ADDRESS>
t=0 0
m=video 0 RTP/AVP 96
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1
a=control:trackID=0
m=audio 0 RTP/AVP 97
a=rtpmap:97 PCML/16000
a=control:trackID=1

2023/09/05 19:34:13 DEB [path xxx-crib] [RTSP source] c->s SETUP rtsp://xxx.104:8554/1080p/trackID=0 RTSP/1.0
Authorization: Basic xxx
CSeq: 4
Transport: RTP/AVP/TCP;unicast;interleaved=0-1;mode=play
User-Agent: gortsplib

2023/09/05 19:34:13 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 4
Session: 35042212;timeout=60
Transport: RTP/AVP/TCP;unicast;interleaved=0-1

2023/09/05 19:34:13 DEB [path xxx-crib] [RTSP source] c->s SETUP rtsp://xxx.104:8554/1080p/trackID=1 RTSP/1.0
Authorization: Basic xxx
CSeq: 5
Session: 35042212
Transport: RTP/AVP/TCP;unicast;interleaved=2-3;mode=play
User-Agent: gortsplib

2023/09/05 19:34:13 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 5
Session: 00133631;timeout=60
Transport: RTP/AVP/TCP;unicast;interleaved=2-3

2023/09/05 19:34:13 INF [path xxx-crib] [RTSP source] ready: 2 tracks (H264, Generic)
2023/09/05 19:34:13 DEB [RTSP] [conn xxx.94:46618] [s->c] RTSP/1.0 200 OK
CSeq: 2
Content-Base: rtsp://xxx.12:8554/xxx-crib/
Content-Length: 306
Content-Type: application/sdp
Server: gortsplib

v=0
o=- 0 0 IN IP4 <IP_ADDRESS>
s=go2rtc/1.6.0
c=IN IP4 <IP_ADDRESS>
t=0 0
m=video 0 RTP/AVP 96
a=control:rtsp://xxx.12:8554/xxx-crib/trackID=0
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1
m=audio 0 RTP/AVP 97
a=control:rtsp://xxx.12:8554/xxx-crib/trackID=1
a=rtpmap:97 PCML/16000

2023/09/05 19:34:13 DEB [path xxx-crib] [RTSP source] c->s PLAY rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic xxx
CSeq: 6
Range: npt=0-
Session: 00133631
User-Agent: gortsplib

2023/09/05 19:34:13 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 6
Session: 00133631

2023/09/05 19:34:13 DEB [RTSP] [conn xxx.94:46618] [c->s] SETUP rtsp://xxx.12:8554/xxx-crib/trackID=0 RTSP/1.0
CSeq: 3
Transport: RTP/AVP/TCP;unicast;interleaved=0-1
User-Agent: Live555

2023/09/05 19:34:13 INF [RTSP] [session 5e4e4190] created by xxx.94:46618
2023/09/05 19:34:13 DEB [RTSP] [conn xxx.94:46618] [s->c] RTSP/1.0 200 OK
CSeq: 3
Server: gortsplib
Session: e2e6f29d30ff4069aeb6722684291891
Transport: RTP/AVP/TCP;unicast;interleaved=0-1

2023/09/05 19:34:13 DEB [RTSP] [conn xxx.94:46618] [c->s] PLAY rtsp://xxx.12:8554/xxx-crib/ RTSP/1.0
CSeq: 4
Range: npt=0.000-
Session: e2e6f29d30ff4069aeb6722684291891
User-Agent: Live555

2023/09/05 19:34:13 INF [RTSP] [session 5e4e4190] is reading from path 'xxx-crib', with TCP, 1 track (H264)
2023/09/05 19:34:13 DEB [RTSP] [conn xxx.94:46618] [s->c] RTSP/1.0 200 OK
CSeq: 4
Server: gortsplib
Session: e2e6f29d30ff4069aeb6722684291891

2023/09/05 19:34:43 DEB [RTSP] [conn xxx.94:46618] [c->s] GET_PARAMETER rtsp://xxx.12:8554/xxx-crib/ RTSP/1.0
CSeq: 5
Session: e2e6f29d30ff4069aeb6722684291891
User-Agent: Live555

2023/09/05 19:34:43 DEB [RTSP] [conn xxx.94:46618] [s->c] RTSP/1.0 200 OK
CSeq: 5
Content-Type: text/parameters
Server: gortsplib
Session: e2e6f29d30ff4069aeb6722684291891

2023/09/05 19:35:01 DEB [path xxx-crib] [RTSP source] c->s OPTIONS rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic xxx
CSeq: 7
Session: 00133631
User-Agent: gortsplib

2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] c->s TEARDOWN rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic xxx
CSeq: 8
Session: 00133631
User-Agent: gortsplib

2023/09/05 19:35:11 INF [path xxx-crib] [RTSP source] stopped
2023/09/05 19:35:11 INF [RTSP] [conn xxx.94:46618] closed (terminated)
2023/09/05 19:35:11 INF [RTSP] [session 5e4e4190] destroyed (terminated)
2023/09/05 19:35:11 INF [RTSP] [conn xxx.94:46640] opened
2023/09/05 19:35:11 DEB [RTSP] [conn xxx.94:46640] [c->s] OPTIONS rtsp://xxx.12:8554/xxx-crib RTSP/1.0
CSeq: 1
User-Agent: Live555

2023/09/05 19:35:11 DEB [RTSP] [conn xxx.94:46640] [s->c] RTSP/1.0 200 OK
CSeq: 1
Public: DESCRIBE, ANNOUNCE, SETUP, PLAY, RECORD, PAUSE, GET_PARAMETER, TEARDOWN
Server: gortsplib

2023/09/05 19:35:11 DEB [RTSP] [conn xxx.94:46640] [c->s] DESCRIBE rtsp://xxx.12:8554/xxx-crib RTSP/1.0
Accept: application/sdp
CSeq: 2
User-Agent: Live555

2023/09/05 19:35:11 INF [path xxx-crib] [RTSP source] started
2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] connecting
2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] c->s OPTIONS rtsp://xxx.104:8554/1080p RTSP/1.0
CSeq: 1
User-Agent: gortsplib

2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 401 Unauthorized
CSeq: 1
WWW-Authenticate: Basic realm="go2rtc"

2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] c->s OPTIONS rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic xxx
CSeq: 2
User-Agent: gortsplib

2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 2
Public: OPTIONS, SETUP, TEARDOWN, DESCRIBE, PLAY, PAUSE, ANNOUNCE, RECORD

2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] c->s DESCRIBE rtsp://xxx.104:8554/1080p RTSP/1.0
Accept: application/sdp
Authorization: Basic xxx
CSeq: 3
User-Agent: gortsplib

2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 3
Content-Length: 236
Content-Type: application/sdp

v=0
o=- 1 1 IN IP4 <IP_ADDRESS>
s=go2rtc/1.6.0
c=IN IP4 <IP_ADDRESS>
t=0 0
m=video 0 RTP/AVP 96
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1
a=control:trackID=0
m=audio 0 RTP/AVP 97
a=rtpmap:97 PCML/16000
a=control:trackID=1

2023/09/05 19:35:11 DEB [path xxx-crib] [RTSP source] c->s SETUP rtsp://xxx.104:8554/1080p/trackID=0 RTSP/1.0
Authorization: Basic xxx
CSeq: 4
Transport: RTP/AVP/TCP;unicast;interleaved=0-1;mode=play
User-Agent: gortsplib

2023/09/05 19:35:12 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 4
Session: 45701311;timeout=60
Transport: RTP/AVP/TCP;unicast;interleaved=0-1

2023/09/05 19:35:12 DEB [path xxx-crib] [RTSP source] c->s SETUP rtsp://xxx.104:8554/1080p/trackID=1 RTSP/1.0
Authorization: Basic xxx
CSeq: 5
Session: 45701311
Transport: RTP/AVP/TCP;unicast;interleaved=2-3;mode=play
User-Agent: gortsplib

2023/09/05 19:35:12 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 5
Session: 63948645;timeout=60
Transport: RTP/AVP/TCP;unicast;interleaved=2-3

2023/09/05 19:35:12 DEB [RTSP] [conn xxx.94:46640] [s->c] RTSP/1.0 200 OK
CSeq: 2
Content-Base: rtsp://xxx.12:8554/xxx-crib/
Content-Length: 306
Content-Type: application/sdp
Server: gortsplib

v=0
o=- 0 0 IN IP4 <IP_ADDRESS>
s=go2rtc/1.6.0
c=IN IP4 <IP_ADDRESS>
t=0 0
m=video 0 RTP/AVP 96
a=control:rtsp://xxx.12:8554/xxx-crib/trackID=0
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1
m=audio 0 RTP/AVP 97
a=control:rtsp://xxx.12:8554/xxx-crib/trackID=1
a=rtpmap:97 PCML/16000

2023/09/05 19:35:12 INF [path xxx-crib] [RTSP source] ready: 2 tracks (H264, Generic)
2023/09/05 19:35:12 DEB [path xxx-crib] [RTSP source] c->s PLAY rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic xxx
CSeq: 6
Range: npt=0-
Session: 63948645
User-Agent: gortsplib

2023/09/05 19:35:12 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 6
Session: 63948645

2023/09/05 19:35:12 DEB [RTSP] [conn xxx.94:46640] [c->s] SETUP rtsp://xxx.12:8554/xxx-crib/trackID=0 RTSP/1.0
CSeq: 3
Transport: RTP/AVP/TCP;unicast;interleaved=0-1
User-Agent: Live555

2023/09/05 19:35:12 INF [RTSP] [session d3938ec3] created by xxx.94:46640
2023/09/05 19:35:12 DEB [RTSP] [conn xxx.94:46640] [s->c] RTSP/1.0 200 OK
CSeq: 3
Server: gortsplib
Session: 9e5f6c4dfcc64d6485e83d144eded89e
Transport: RTP/AVP/TCP;unicast;interleaved=0-1;ssrc=99BEB6C2

2023/09/05 19:35:12 DEB [RTSP] [conn xxx.94:46640] [c->s] PLAY rtsp://xxx.12:8554/xxx-crib/ RTSP/1.0
CSeq: 4
Range: npt=0.000-
Session: 9e5f6c4dfcc64d6485e83d144eded89e
User-Agent: Live555

2023/09/05 19:35:12 INF [RTSP] [session d3938ec3] is reading from path 'xxx-crib', with TCP, 1 track (H264)
2023/09/05 19:35:12 DEB [RTSP] [conn xxx.94:46640] [s->c] RTSP/1.0 200 OK
CSeq: 4
RTP-Info: url=rtsp://xxx.12:8554/xxx-crib/trackID=0;seq=2140;rtptime=580324895
Server: gortsplib
Session: 9e5f6c4dfcc64d6485e83d144eded89e

2023/09/05 19:35:13 WAR [path xxx-crib] [RTSP source] 24 RTP packets lost
2023/09/05 19:35:19 DEB [RTSP] [conn xxx.94:46640] [c->s] TEARDOWN rtsp://xxx.12:8554/xxx-crib/ RTSP/1.0
CSeq: 5
Session: 9e5f6c4dfcc64d6485e83d144eded89e
User-Agent: Live555

2023/09/05 19:35:19 INF [RTSP] [session d3938ec3] destroyed (torn down by xxx.94:46640)
2023/09/05 19:35:19 DEB [RTSP] [conn xxx.94:46640] [s->c] RTSP/1.0 200 OK
CSeq: 5
Server: gortsplib

2023/09/05 19:35:19 INF [RTSP] [conn xxx.94:46640] closed (EOF)
2023/09/05 19:35:29 INF [path xxx-crib] [RTSP source] stopped
2023/09/05 19:35:29 DEB [path xxx-crib] [RTSP source] c->s TEARDOWN rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic xxx
CSeq: 7
Session: 63948645
User-Agent: gortsplib

In case this is helpful, this is the log from v1.0.0 where the issue does not appear.
2023/09/05 19:39:03 INF MediaMTX v1.0.0
2023/09/05 19:39:03 DEB [path xxx-crib] created
2023/09/05 19:39:03 DEB path manager created
2023/09/05 19:39:03 INF [RTSP] listener opened on :8554 (TCP)
2023/09/05 19:39:03 INF [RTMP] listener opened on :1935
2023/09/05 19:39:03 INF [HLS] listener opened on :8888
2023/09/05 19:39:03 INF [WebRTC] listener opened on :8889 (HTTP)
2023/09/05 19:39:03 INF [SRT] listener opened on :8890 (UDP)
2023/09/05 19:39:30 INF [RTSP] [conn xxx.94:46648] opened
2023/09/05 19:39:30 DEB [RTSP] [conn xxx.94:46648] [c->s] OPTIONS rtsp://xxx.12:8554/xxx-crib RTSP/1.0
CSeq: 1
User-Agent: Live555

2023/09/05 19:39:30 DEB [RTSP] [conn xxx.94:46648] [s->c] RTSP/1.0 200 OK
CSeq: 1
Public: DESCRIBE, ANNOUNCE, SETUP, PLAY, RECORD, PAUSE, GET_PARAMETER, TEARDOWN
Server: gortsplib

2023/09/05 19:39:30 DEB [RTSP] [conn xxx.94:46648] [c->s] DESCRIBE rtsp://xxx.12:8554/xxx-crib RTSP/1.0
Accept: application/sdp
CSeq: 2
User-Agent: Live555

2023/09/05 19:39:30 INF [path xxx-crib] [RTSP source] started
2023/09/05 19:39:30 DEB [path xxx-crib] [RTSP source] connecting
2023/09/05 19:39:30 DEB [path xxx-crib] [RTSP source] c->s OPTIONS rtsp://xxx.104:8554/1080p RTSP/1.0
CSeq: 1
User-Agent: gortsplib

2023/09/05 19:39:30 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 401 Unauthorized
CSeq: 1
WWW-Authenticate: Basic realm="go2rtc"

2023/09/05 19:39:30 DEB [path xxx-crib] [RTSP source] c->s OPTIONS rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic xxx
CSeq: 2
User-Agent: gortsplib

2023/09/05 19:39:30 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 2
Public: OPTIONS, SETUP, TEARDOWN, DESCRIBE, PLAY, PAUSE, ANNOUNCE, RECORD

2023/09/05 19:39:30 DEB [path xxx-crib] [RTSP source] c->s DESCRIBE rtsp://xxx.104:8554/1080p RTSP/1.0
Accept: application/sdp
Authorization: Basic xxx
CSeq: 3
User-Agent: gortsplib

2023/09/05 19:39:30 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 3
Content-Length: 236
Content-Type: application/sdp

v=0
o=- 1 1 IN IP4 <IP_ADDRESS>
s=go2rtc/1.6.0
c=IN IP4 <IP_ADDRESS>
t=0 0
m=video 0 RTP/AVP 96
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1
a=control:trackID=0
m=audio 0 RTP/AVP 97
a=rtpmap:97 PCML/16000
a=control:trackID=1

2023/09/05 19:39:30 DEB [path xxx-crib] [RTSP source] c->s SETUP rtsp://xxx.104:8554/1080p/trackID=0 RTSP/1.0
Authorization: Basic xxx
CSeq: 4
Transport: RTP/AVP/TCP;unicast;interleaved=0-1;mode=play
User-Agent: gortsplib

2023/09/05 19:39:30 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 4
Session: 50949733;timeout=60
Transport: RTP/AVP/TCP;unicast;interleaved=0-1

2023/09/05 19:39:30 DEB [path xxx-crib] [RTSP source] c->s SETUP rtsp://xxx.104:8554/1080p/trackID=1 RTSP/1.0
Authorization: Basic xxx
CSeq: 5
Session: 50949733
Transport: RTP/AVP/TCP;unicast;interleaved=2-3;mode=play
User-Agent: gortsplib

2023/09/05 19:39:30 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 5
Session: 12208073;timeout=60
Transport: RTP/AVP/TCP;unicast;interleaved=2-3

2023/09/05 19:39:30 INF [path xxx-crib] [RTSP source] ready: 2 tracks (H264, Generic)
2023/09/05 19:39:30 DEB [path xxx-crib] [RTSP source] c->s PLAY rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic xxx
CSeq: 6
Range: npt=0-
Session: 12208073
User-Agent: gortsplib

2023/09/05 19:39:30 DEB [RTSP] [conn xxx.94:46648] [s->c] RTSP/1.0 200 OK
CSeq: 2
Content-Base: rtsp://xxx.12:8554/xxx-crib/
Content-Length: 300
Content-Type: application/sdp
Server: gortsplib

v=0
o=- 0 0 IN IP4 <IP_ADDRESS>
s=Stream
c=IN IP4 <IP_ADDRESS>
t=0 0
m=video 0 RTP/AVP 96
a=control:rtsp://xxx.12:8554/xxx-crib/trackID=0
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1
m=audio 0 RTP/AVP 97
a=control:rtsp://xxx.12:8554/xxx-crib/trackID=1
a=rtpmap:97 PCML/16000

2023/09/05 19:39:30 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 6
Session: 12208073

2023/09/05 19:39:31 DEB [RTSP] [conn xxx.94:46648] [c->s] SETUP rtsp://xxx.12:8554/xxx-crib/trackID=0 RTSP/1.0
CSeq: 3
Transport: RTP/AVP/TCP;unicast;interleaved=0-1
User-Agent: Live555

2023/09/05 19:39:31 INF [RTSP] [session 785b85d8] created by xxx.94:46648
2023/09/05 19:39:31 DEB [RTSP] [conn xxx.94:46648] [s->c] RTSP/1.0 200 OK
CSeq: 3
Server: gortsplib
Session: c0526fee33c044b4b25b7fe5be814685
Transport: RTP/AVP/TCP;unicast;interleaved=0-1

2023/09/05 19:39:31 DEB [RTSP] [conn xxx.94:46648] [c->s] PLAY rtsp://xxx.12:8554/xxx-crib/ RTSP/1.0
CSeq: 4
Range: npt=0.000-
Session: c0526fee33c044b4b25b7fe5be814685
User-Agent: Live555

2023/09/05 19:39:31 INF [RTSP] [session 785b85d8] is reading from path 'xxx-crib', with TCP, 1 track (H264)
2023/09/05 19:39:31 DEB [RTSP] [conn xxx.94:46648] [s->c] RTSP/1.0 200 OK
CSeq: 4
Server: gortsplib
Session: c0526fee33c044b4b25b7fe5be814685

2023/09/05 19:40:01 DEB [RTSP] [conn xxx.94:46648] [c->s] GET_PARAMETER rtsp://xxx.12:8554/xxx-crib/ RTSP/1.0
CSeq: 5
Session: c0526fee33c044b4b25b7fe5be814685
User-Agent: Live555

2023/09/05 19:40:01 DEB [RTSP] [conn xxx.94:46648] [s->c] RTSP/1.0 200 OK
CSeq: 5
Content-Type: text/parameters
Server: gortsplib
Session: c0526fee33c044b4b25b7fe5be814685

2023/09/05 19:40:18 DEB [path xxx-crib] [RTSP source] c->s OPTIONS rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic xxx
CSeq: 7
Session: 12208073
User-Agent: gortsplib

2023/09/05 19:40:31 DEB [RTSP] [conn xxx.94:46648] [c->s] GET_PARAMETER rtsp://xxx.12:8554/xxx-crib/ RTSP/1.0
CSeq: 6
Session: c0526fee33c044b4b25b7fe5be814685
User-Agent: Live555

2023/09/05 19:40:31 DEB [RTSP] [conn xxx.94:46648] [s->c] RTSP/1.0 200 OK
CSeq: 6
Content-Type: text/parameters
Server: gortsplib
Session: c0526fee33c044b4b25b7fe5be814685

2023/09/05 19:40:49 DEB [RTSP] [conn xxx.94:46648] [c->s] TEARDOWN rtsp://xxx.12:8554/xxx-crib/ RTSP/1.0
CSeq: 7
Session: c0526fee33c044b4b25b7fe5be814685
User-Agent: Live555

2023/09/05 19:40:49 INF [RTSP] [session 785b85d8] destroyed (torn down by xxx.94:46648)
2023/09/05 19:40:49 DEB [RTSP] [conn xxx.94:46648] [s->c] RTSP/1.0 200 OK
CSeq: 7
Server: gortsplib

2023/09/05 19:40:49 INF [RTSP] [conn xxx.94:46648] closed (EOF)
2023/09/05 19:40:59 INF [path xxx-crib] [RTSP source] stopped
2023/09/05 19:40:59 DEB [path xxx-crib] [RTSP source] c->s TEARDOWN rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic xxx
CSeq: 8
Session: 12208073
User-Agent: gortsplib

2023/09/05 20:35:32 INF [RTSP] [conn xxx.94:46694] opened
2023/09/05 20:35:32 DEB [RTSP] [conn xxx.94:46694] [c->s] OPTIONS rtsp://xxx.12:8554/xxx-crib RTSP/1.0
CSeq: 1
User-Agent: Live555

2023/09/05 20:35:32 DEB [RTSP] [conn xxx.94:46694] [s->c] RTSP/1.0 200 OK
CSeq: 1
Public: DESCRIBE, ANNOUNCE, SETUP, PLAY, RECORD, PAUSE, GET_PARAMETER, TEARDOWN
Server: gortsplib

2023/09/05 20:35:32 DEB [RTSP] [conn xxx.94:46694] [c->s] DESCRIBE rtsp://xxx.12:8554/xxx-crib RTSP/1.0
Accept: application/sdp
CSeq: 2
User-Agent: Live555

2023/09/05 20:35:32 INF [path xxx-crib] [RTSP source] started
2023/09/05 20:35:32 DEB [path xxx-crib] [RTSP source] connecting
2023/09/05 20:35:32 DEB [path xxx-crib] [RTSP source] c->s OPTIONS rtsp://xxx.104:8554/1080p RTSP/1.0
CSeq: 1
User-Agent: gortsplib

2023/09/05 20:35:32 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 401 Unauthorized
CSeq: 1
WWW-Authenticate: Basic realm="go2rtc"

2023/09/05 20:35:32 DEB [path xxx-crib] [RTSP source] c->s OPTIONS rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic xxx
CSeq: 2
User-Agent: gortsplib

2023/09/05 20:35:32 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 2
Public: OPTIONS, SETUP, TEARDOWN, DESCRIBE, PLAY, PAUSE, ANNOUNCE, RECORD

2023/09/05 20:35:32 DEB [path xxx-crib] [RTSP source] c->s DESCRIBE rtsp://xxx.104:8554/1080p RTSP/1.0
Accept: application/sdp
Authorization: Basic xxx
CSeq: 3
User-Agent: gortsplib

2023/09/05 20:35:32 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 3
Content-Length: 236
Content-Type: application/sdp

v=0
o=- 1 1 IN IP4 <IP_ADDRESS>
s=go2rtc/1.6.0
c=IN IP4 <IP_ADDRESS>
t=0 0
m=video 0 RTP/AVP 96
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1
a=control:trackID=0
m=audio 0 RTP/AVP 97
a=rtpmap:97 PCML/16000
a=control:trackID=1

2023/09/05 20:35:32 DEB [path xxx-crib] [RTSP source] c->s SETUP rtsp://xxx.104:8554/1080p/trackID=0 RTSP/1.0
Authorization: Basic xxx
CSeq: 4
Transport: RTP/AVP/TCP;unicast;interleaved=0-1;mode=play
User-Agent: gortsplib

2023/09/05 20:35:32 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 4
Session: 36404501;timeout=60
Transport: RTP/AVP/TCP;unicast;interleaved=0-1

2023/09/05 20:35:32 DEB [path xxx-crib] [RTSP source] c->s SETUP rtsp://xxx.104:8554/1080p/trackID=1 RTSP/1.0
Authorization: Basic xxx
CSeq: 5
Session: 36404501
Transport: RTP/AVP/TCP;unicast;interleaved=2-3;mode=play
User-Agent: gortsplib

2023/09/05 20:35:32 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 5
Session: 64675691;timeout=60
Transport: RTP/AVP/TCP;unicast;interleaved=2-3

2023/09/05 20:35:32 INF [path xxx-crib] [RTSP source] ready: 2 tracks (H264, Generic)
2023/09/05 20:35:32 DEB [path xxx-crib] [RTSP source] c->s PLAY rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic xxx
CSeq: 6
Range: npt=0-
Session: 64675691
User-Agent: gortsplib

2023/09/05 20:35:32 DEB [RTSP] [conn xxx.94:46694] [s->c] RTSP/1.0 200 OK
CSeq: 2
Content-Base: rtsp://xxx.12:8554/xxx-crib/
Content-Length: 300
Content-Type: application/sdp
Server: gortsplib

v=0
o=- 0 0 IN IP4 <IP_ADDRESS>
s=Stream
c=IN IP4 <IP_ADDRESS>
t=0 0
m=video 0 RTP/AVP 96
a=control:rtsp://xxx.12:8554/xxx-crib/trackID=0
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1
m=audio 0 RTP/AVP 97
a=control:rtsp://xxx.12:8554/xxx-crib/trackID=1
a=rtpmap:97 PCML/16000

2023/09/05 20:35:32 DEB [path xxx-crib] [RTSP source] s->c RTSP/1.0 200 OK
CSeq: 6
Session: 64675691

2023/09/05 20:35:32 DEB [RTSP] [conn xxx.94:46694] [c->s] SETUP rtsp://xxx.12:8554/xxx-crib/trackID=0 RTSP/1.0
CSeq: 3
Transport: RTP/AVP/TCP;unicast;interleaved=0-1
User-Agent: Live555

2023/09/05 20:35:32 INF [RTSP] [session 8c1a4b6a] created by xxx.94:46694
2023/09/05 20:35:32 DEB [RTSP] [conn xxx.94:46694] [s->c] RTSP/1.0 200 OK
CSeq: 3
Server: gortsplib
Session: 25c835e4dca94aa1adbe728fa51c2dfb
Transport: RTP/AVP/TCP;unicast;interleaved=0-1

2023/09/05 20:35:32 DEB [RTSP] [conn xxx.94:46694] [c->s] PLAY rtsp://xxx.12:8554/xxx-crib/ RTSP/1.0
CSeq: 4
Range: npt=0.000-
Session: 25c835e4dca94aa1adbe728fa51c2dfb
User-Agent: Live555

2023/09/05 20:35:32 INF [RTSP] [session 8c1a4b6a] is reading from path 'xxx-crib', with TCP, 1 track (H264)
2023/09/05 20:35:32 DEB [RTSP] [conn xxx.94:46694] [s->c] RTSP/1.0 200 OK
CSeq: 4
Server: gortsplib
Session: 25c835e4dca94aa1adbe728fa51c2dfb

2023/09/05 20:35:33 INF [RTSP] [conn xxx.94:49385] opened
2023/09/05 20:35:33 INF [RTSP] [conn xxx.94:49385] closed (EOF)
2023/09/05 20:35:34 INF [RTSP] [conn xxx.94:46694] closed (read tcp xxx.12:8554->xxx.94:46694: read: connection reset by peer)
2023/09/05 20:35:34 INF [RTSP] [session 8c1a4b6a] destroyed (not in use)
2023/09/05 20:35:44 INF [path xxx-crib] [RTSP source] stopped
2023/09/05 20:35:44 DEB [path xxx-crib] [RTSP source] c->s TEARDOWN rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic xxx
CSeq: 7
Session: 64675691
User-Agent: gortsplib

I think i've understood where the bug is. Between v1.0.0 and v1.0.1, the RTSP client was improved in order to support receiving server requests. A side effect of this refactoring is that the client now checks whether keepalive requests are acknowledged or not. Your camera doesn't reply to keepalive requests:
2023/09/05 19:40:18 DEB [path xxx-crib] [RTSP source] c->s OPTIONS rtsp://xxx.104:8554/1080p RTSP/1.0
Authorization: Basic xxx
CSeq: 7
Session: 12208073
User-Agent: gortsplib

There should be a s->c RTSP/1.0 OK after this request but there isn't. This behavior for some reason freezes the library, and no packets are sent to VLC anymore. Consequently, VLC closes the connection with the server after some time:
2023/09/05 19:40:49 DEB [RTSP] [conn xxx.94:46648] [c->s] TEARDOWN rtsp://xxx.12:8554/xxx-crib/ RTSP/1.0
CSeq: 7
Session: c0526fee33c044b4b25b7fe5be814685
User-Agent: Live555

And since the source is on demand, and no one is reading it anymore, the source is stopped by the server:
2023/09/05 19:40:59 INF [path xxx-crib] [RTSP source] stopped

Of course all this needs to be fixed.

please try the attached nightly release and let me know if it fixes the issue.
mediamtx_v1.0.3-11-gbbb9c80_darwin_amd64.tar.gz
mediamtx_v1.0.3-11-gbbb9c80_darwin_arm64.tar.gz
mediamtx_v1.0.3-11-gbbb9c80_linux_amd64.tar.gz
mediamtx_v1.0.3-11-gbbb9c80_linux_arm64v8.tar.gz
mediamtx_v1.0.3-11-gbbb9c80_linux_armv6.tar.gz
mediamtx_v1.0.3-11-gbbb9c80_linux_armv7.tar.gz
mediamtx_v1.0.3-11-gbbb9c80_windows_amd64.zip

So far so good with the v1.0.3-11 version but I'll let it run through the paces tonight.
As for the keep-alive requests; I'm not sure if wz_mini_hacks change to go2rtc impacted anything? I switched over to using go2rtc server for the rtsp feeds. I think previously it used v4l2rtspserver. Is the lack of a keepalive a bug that should be reported on the go2rtc side as well? Or is something just missing in my configuration?

Is the lack of a keepalive a bug?

MediaMTX now supports RTSP streams regardless of the fact that keepalive responses are sent or not. We can't consider the lack of keepalive responses a bug since there are cameras that don't send them, as we have just demonstrated.

fixed in v1.1.0


Support negative timestamps

If I understand correctly, here we use u64 to hold the timestamp, which obviously doesn't work if the timestamp is negative (before 1970-01-01T00:00:00Z):
https://github.com/fbriden/yahoo-finance-rs/blob/97499b8d59cca979dd3333d0d7698bebadcadd00/src/yahoo/chart.rs#L33
So it needs to be changed to i64.

This was not fixed, as the PR #19 was not merged in a proper manner, and was subsequently reverted in #22.
Can we reopen?


Add font

@ghutchis Added Poppins font for better readability!

Isn't it cool?

As I said, please post at https://discuss.avogadro.cc (with screenshot) to make your argument for the rest of the community.

https://discuss.avogadro.cc/t/change-font-to-poppins/5563

@ghutchis Let's discuss this topic again after the project has developed further!

@rivercory - perfect. We'd definitely welcome font / style tweaks as the docs get closer to finish. Thanks!


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.12.12",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fdd51e34f45311ab6e48d2147cbc2904731b9993"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "fdd51e34f45311ab6e48d2147cbc2904731b9993",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "net: ieee802154: fix null deref in parse dev addr\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.12.12 by commit fdd51e34f45311ab6e48d2147cbc2904731b9993. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001046


[dv/flash_ctrl] mass erase en fix & bkdr if data type change

Signed-off-by: Eitan Shapira<EMAIL_ADDRESS>Hi,
Following Sri request this is my PR for flash_ctrl.

@eshapira CI failed with this error.

UVM_ERROR @ 207286713 ps: (prim_fifo_sync.sv:156) [ASSERT FAILED] DataKnown_A

@eshapira CI failed with this error.

UVM_ERROR @ 207286713 ps: (prim_fifo_sync.sv:156) [ASSERT FAILED] DataKnown_A

@eshapira CI failed with this error.

UVM_ERROR @ 207286713 ps: (prim_fifo_sync.sv:156) [ASSERT FAILED] DataKnown_A

Sorry for that. All is fixed now.

@eshapira CI failed with this error.

UVM_ERROR @ 207286713 ps: (prim_fifo_sync.sv:156) [ASSERT FAILED] DataKnown_A

Sorry for that. All is fixed now.

What was the issue?

What was the issue?


Ball and stick in the air

What happened?
While playing, the ball just stood in the air, no way to play.
Steps to reproduce
Ball to elevator - ball does not stand in elevator, it stays in the air.
Operating System
Windows 10  (10.0.22000) 64bit
Wallet
Metamask
CPU
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
GPU
NVIDIA GeForce GTX 1650 3962MB
RAM
16235MB
Kernel Version
1.0.0-2189800740.commit-1ab8e83
Unity Version
desktop-main.commit-64822b7
Realm
dg
NameTag
IggyRock#0d13

In which scene did this happen? It looks like a problem with the scene's code not the client

Hi,
Attached a pic of the scene I am stuck in.
Its a nice game.
Best,
Iggy
El El vie, 22 abr 2022 a las 18:40, Pravus @.***>
escribió:

In which scene did this happen? It looks like a problem with the scene's
code not the client
—
Reply to this email directly, view it on GitHub
https://github.com/decentraland/explorer-desktop/issues/251#issuecomment-1106683916,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APYOTXV5C2TMM2UR77H7Q4DVGLI77ANCNFSM5T7MUM4Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

Issue in the scene


Allow all optional props for NodejsFunction to be passed to defineFunction in @aws-amplify/backend-function

Environment information
System:
  OS: macOS 14.6.1
  CPU: (8) arm64 Apple M2
  Memory: 140.08 MB / 16.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 20.11.0 - ~/.nvm/versions/node/v20.11.0/bin/node
  Yarn: undefined - undefined
  npm: 10.2.4 - ~/.nvm/versions/node/v20.11.0/bin/npm
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/auth-construct: 1.3.0
  @aws-amplify/backend: 1.2.0
  @aws-amplify/backend-auth: 1.1.3
  @aws-amplify/backend-cli: 1.2.5
  @aws-amplify/backend-data: 1.1.3
  @aws-amplify/backend-deployer: 1.1.0
  @aws-amplify/backend-function: 1.3.4
  @aws-amplify/backend-output-schemas: 1.2.0
  @aws-amplify/backend-output-storage: 1.1.1
  @aws-amplify/backend-secret: 1.1.0
  @aws-amplify/backend-storage: 1.1.2
  @aws-amplify/cli-core: 1.1.2
  @aws-amplify/client-config: 1.3.0
  @aws-amplify/deployed-backend-client: 1.4.0
  @aws-amplify/form-generator: 1.0.1
  @aws-amplify/model-generator: 1.0.5
  @aws-amplify/platform-core: 1.0.7
  @aws-amplify/plugin-types: 1.2.1
  @aws-amplify/sandbox: 1.2.0
  @aws-amplify/schema-generator: 1.2.1
  aws-amplify: 6.5.4
  aws-cdk: 2.154.1
  aws-cdk-lib: 2.154.1
  typescript: 5.5.4
AWS environment variables:
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Describe the feature
Currently the FunctionProp type only allows for specific props.
Allow all optional props for NodejsFunction, such as logRetention, to be passed to defineFunction
Use case

Converting existing CDK functions using NodejsFunction to defineFunction from @aws-amplify/backend
Adding log retention to functions creating with defineFunction from @aws-amplify/backend

@ykethan I created #1971 to implement this feature. It would be great to get it reviewed or at least the test run allowed so I can fix things as needed


Fork @iov/tendermint-rpc

We need @cosmjs/tendermint-rpc here, then remove 0.31 support and add 0.33 support.

@webmaster128 Do we still want v0.32 support? There were some pretty serious breaking changes in v0.33 which will invalidate some of the cross-version types.

Good question.
Cosmos SDK 0.38 started to use Tendermint 0.33 and for all pre-0.39 blockchains we cannot decode the Amoni data we get from Tendermint. So I think it is safe to remove support for Tendermint 0.32.
My only concern is that we don't show the multi version support anymore if only 0.33 is supported. But that's okay if we keep the infrastructure in place to support 0.33+ in the future.


breakpoint xs

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
What about an additional breakpoint e.g. at 380px?
Motivation and context
Very often we have the problem that we have to design pages for small smartphones like iPhone SE. Unfortunately, the smallest breakpoint at 576px offers too much leeway, so it either looks good at 500px or at 300px but not at both.

No plans to add this ourselves, but you can by modifying the Sass map.


Use rounded brackets rather than curly brackets

Minor syntactic point: swaps out the {{old-style}} of param references in favor of ((this-type-of)) param references.
Obviously completely understand if you don't want to accept this, but the {{old-style}} went out of fashion sometime back in Concourse 3.x, I think?

Absolutely no pressure at all to take this PR but are you interested in taking this at some point? If not no problem I'll close it out 👍

Thanks for bumping @aegershman


[WASM] Module not found: Error: Can't resolve

🐞 bug report
Description
wasm-pack creates a bundle which ends up doing this:
import * as wasm from './my_wasm' (my_wasm is in reality my_wasm.wasm, notice the absence of the .wasm extension.)
When I import the package in my angular project I get the following error during ng build:
Module not found: Error: Can't resolve './my_wasm' in 'my_package'.
While it is supposed to work with Webpack. As far as I can tell one solution is to add resolve.extensions: ['.wasm'] to the webpack configuration, but Angular doesn't expose that option.
🌍  Your Environment
Angular Version:
8.0.3
Anything else relevant?

@suyoshi currently to apply custom webpack config using ngx-build-plus.

Webpack adds in the .wasm extension by default, so Angular's behavior violates the expected Webpack behavior.

It's true that Webpack adds the .wasm extension to their resolve options, but Angular CLI does not have as a goal to expose Webpack semantics or default configuration. We try to maintain our own list of extensions and mainfields that the default build system of Angular CLI uses and only explicitly support those.
In fact we do our best to keep anything that is webpack-specific away from project source-code, because at some point in the future we might decide to change our build system.
Is it problematic to just import my_wasm.wasm instead? This is a valid import.

Is it problematic to just import my_wasm.wasm instead? This is a valid import.

And what about a library which internally uses WebAssembly and imports it without the .wasm extension? In that case you cannot modify the code, so you're stuck.
This is a common use case, there are already several npm libraries which internally use WebAssembly to speed up their internal algorithms, and the usage of WebAssembly will only go up over time.
You cannot expect all library authors to explicitly import .wasm, especially since importing without .wasm works fine with Webpack, and Webpack is the de-facto bundler (and thus most code is written for it).

I think you're giving Webpack a bit too much importance in this topic. Webpack is very popular, but that doesn't mean everyone uses Webpack.
For instance, a lot of toolchains use Rollup instead. The WASM rollup plugin shows an example of importing a .wasm file with the extension. Parcel is popular as well, and their WASM support also lists an example of using the extension. I couldn't actually find a page in the Webpack docs showing how to use WASM, but there is an example in the repository that also shows imports with the extension. Aside from bundlers, Both browsers and NodeJS show examples of loading WASM files with an extension. So from this admittedly short survey of the package and runtime landscape, I saw none that directed users to import WASM without extensions.
If you have a library and you package it in a way that assumes Webpack, then you are limiting how consumers can use your library. The limitations are both that consumers must use webpack, and that webpack must be configured in a certain way to use the library. This is a serious limitation because it gets passed on transitively to both your direct and indirect consumers. A user might not use a library directly and still run into these problems because of an indirect dependency.
The specific case of changing the an extension resolver also has performance implications. That's the list of extensions the resolver will try to load before it gives up on loading a file. So each extension added there increases total file system operations by a factor relative to its position in the priority array. In Webpack's case, .wasm is the first one, followed by .mjs, then .js, then .json. If I ask Webpack to bundle a .js file without an extension, it will first try to load .wasm and .mjs. So for the case of .js files, this triples file reads for existing files. For nonexistent files, it adds 1/4 more reads. This cost is incurred for all resolutions, so a large project that uses a single library with a .wasm import must pay the cost on all attempted resolutions.
I'm sure Webpack has great reasons for listing .wasm on their default extension resolver. But like I said before, it was never a goal for Angular CLI to expose Webpack semantics. Another example of not exposing Webpack semantics is not using require in user code for .html and .css files, or not exposing Node globals. We avoid Webpack-specific semantics because it creates coupling of the CLI and user code to Webpack. If in the future we want to migrate to another setup, this couple would create problems. If a user wants to move away from the CLI to another bundler, the same coupling will also create problems for them.
If importing .wasm files without an extension was indeed a standard in platforms (like NodeJS or Chrome), it would make sense for Angular CLI to do it. If it was common practice among bundlers, it would make sense to consider the pros and cons and perhaps do it as well. But as far as I can tell it's neither.
If you have a library that assumes the .wasm extension will automatically be attempted by the consumers toolchain, I urge you to adopt a more consumer friendly packaging approach. Coupling your library to the semantics of a specific tool (be it Webpack, or any other) is harmful for the JS ecosystem.


Wrong refactoring for application without space

Given
f x = g(x)

hlint --refactor tells you
f x = gx  -- no space between g and x

Thanks! Another case of insufficient testing

CC @zliu41 - this seems to still occur with my version of refactor (which is not the latest from GitHub)


Improve versioning and installs for commitlint

Fixes commitlint to at least have a default config specification (originally it errored, complaining about the lack of one).
Also provide instructions on how to override the listed commitlint plugins (the recommendation requires >1.6.0, hence the specification. I can make this >=1.6.0 if desired).
In the future, we will probably want to explicitly version these sort of actions via config so that we can guarantee hermetic treatment.

I recall some discussion about what might enforce the consistency of these versions - like an action - is that captured somewhere?

@laurit17 Overriding the packages file and checking it in could achieve this... otherwise I'm not sure what you're referring to?

Filed https://linear.app/trunk/issue/TRUNK-6288/support-a-versioning-story-for-actions, we can triage as needed during our next planning


[Feature request] Enhancements for particles

Editor:
Bounciness and drag factor for particles
The eye in UI, for hiding, currently doesn't work for particle effect
API:
From discord discussion: The interface is a little barebones at the moment. I will expose all the available functionality

The eye in UI, for hiding, currently doesn't work for particle effect

This is fixed in v0.4.0-beta10.

@trsh v0.4.0-beta13 adds support for linear and collision damping coefficients.


Update XBean to 4.7

@jgallimore please close this PR, I don't have enough karma do do that, thanks.


INFO don't get logged for custom logger handle

OS X  19.7.4, python 2.7.1, flask 0.9
as in this example https://gist.github.com/3257877 , in log file there is nothing for level INFO

Not sure why this is even a ticket.


Support replication

Please summarize your feature request
Using with Postgres logical replication to get a stream of changes to the database
Describe the functionality you're seeking in more detail
I'd like to use postgres-nio to work with logical replication but it looks like for now messages related to it are marked precondition failures. It looks like a lot of the functionality in the New folder is moving towards making messages, etc internal, which may mean trying to extend things to intercept and process these messages myself won't be possible. Is there any recommended way I could do this while still using postgres-nio as a base? Or is the only option to fork/wait for it to be implemented given the direction the library is headed?
Have you considered any alternatives?
I've started to work through forking but would rather avoid that if possible

As replication likely requires different state machines, I'm pretty confident that forking is the best option right now. We might want to consider putting the messages into an extra target, that you could depend upon. Not sure if there is much more reusable besides the message definitions.


Implementing Notation directory structure

implement notation directory structure (link)
Design:

base.go does cross platform checking and initialize the base directories for notation, including SystemLibexec, SystemConfig, UserLibexec, UserConfig and UserCache.
Always check the path under user directory before system directory when access the specific file. If user directory has the target file, it returns the path directly, otherwise it returns the path under the system directory.
Add a UnionDirFS, a union directory file system, to merge multiple directories and simulate as one directory, which is base on io/fs package and easy to test and compatible with plugin/manager.

This is the one of two patches for this issue (link). Additional test and config package will be added in the next patch.

Can we actually expose an interface so that other components can easily mock these paths? Something like below
type Path interface {
	Config() string
	Localkey(keyName string) string
	SigningKeyConfig() string
	TrustPolicy() string
	X509TrustStore(prefix, storeName) string
	PluginBin(name string) string
}

Contributor

Do you mean that change the package to be a struct which implements the Path interface?

Can we actually expose an interface so that other components can easily mock these paths? Something like below
type Path interface {
	Config() string
	Localkey(keyName string) string
	SigningKeyConfig() string
	TrustPolicy() string
	X509TrustStore(prefix, storeName) string
	PluginBin(name string) string
}

Updated the code, please review it.

lgtm

LGTM

Looks like we're good to merge! 🎉


Peek Definition from Command window goes to definition

VSCode Version: 1.1.0-alpha
OS Version: Windows 10

Steps to Reproduce:

Click on a variable
F1 > Peek Definition

It looks like it brings up the peek window and also performs the go to definition command.

Might be because quick open focusses the editor when it closes...

@bpasero Is there anything special wrt Enter? When the command is invoked from the F1 palette the tree in the peek widget immediately receives an onEnter event which makes it jump to the declaration. Now I wonder where that event comes from

Maybe F1 triggers the command onKeyDown and thus onKeyUp might go to the editor. Though if that is true I wonder why you do not end up with a newline in the editor for any other command?

fixed by ce3fb81


[Das_Schwarze_Auge_4-1] Fix Mixed Up Spells

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

Changes / Description

Fixes

Fix: Function of roll buttons of spells 'Kraft des Erzes', 'Kraft des Humus' and 'Krähenruf' are no longer swapped (2b290269e2d2ecd54abba596b830745b07c2b3cb)

Miscellaneous

Bump version number (7cc62be78781b3ebb62ce614f6a889c93bc80fe2)
Info on the latest version/changes (7cc62be78781b3ebb62ce614f6a889c93bc80fe2)

Character Sheet Info Roll20 Internal Use only.


Update TagfsUtilities.py

getboundary is os dependent currently, making the change.

This fixes the issue: https://github.com/rteja/HTFS/issues/10