setting default["apache"]["version"] = "2.4" does not work

we are on redhat-release-server-6Server-<IP_ADDRESS>.el6.x86_64 and it installs apache2.4 but with 2.2 configuration files.
in apache2/attributes/default.rb  Line 57 there is no condition for >=6.0 and it defaults to 2.2
this causes these issues:
Invalid command 'LockFile', perhaps misspelled or defined by a module not included in the server configuration
httpd: Syntax error on line 106 of /etc/httpd/conf/httpd.conf: Syntax error on line 1 of /etc/httpd/mods-enabled/authz_default.load: Cannot load /usr/lib64/httpd/modules/mod_authz_default.so into server: /usr/lib64/httpd/modules/mod_authz_default.so: cannot open shared object file:
No such file or directory
Invalid command 'LockFile', perhaps misspelled or defined by a module not included in the server configuration
did anyone had these issues ?
shall I submit a PR to add that condition to support for RHEL 6.0 ?
please advise we are blocked by this and we dont want one more wrapper cookbook just for this fix  ?

What version of apache2 is getting installed? Rhel 6 shipped with 2.2. you
can not just change the apache.version to have it install 2.4.

Server version: Apache/2.4.20 (Unix) is getting installed.   RHEL was not shipped with 2.2 and we are trying to install 2.4

https://access.redhat.com/solutions/445713

yes the article shows but  checked again on our hosts and none of them have 2.2

@sbalaram when you run the cookbook it will install apache.package which on redhat is httpd via yum. The errors you are seeing above in the show 2.2 directives. In 2.4 LockFile is now Mutex and there is no mod_authz_default in 2.4, as it is replaced by mod_authz_core.
This suggests to me that are either not setting apache.version to 2.4 early enough or not at all, as the cookbook is behaving as if apache.version was not set to 2.4 when the cookbook ran.

thanks @svanzoest the attribute was not set early enough was the issue, re-arranged the recipe include and it was all good


Doc store: naive implementation

Create naive doc store implementation so we can progress for testing and otherwise

I've integrated lmdb


published 5.0.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

This should be made to a new branch once PR is complete, then we can do proper sub-releases.

@conda-forge-admin, please rerender

Pushed to v5.0.x as a new release series.


[Basic] Add TemporaryFile class.

This class provides APIs to create and manage temporary disposable
files. It wraps posix's mkstemps method and adds additional
functionality on top of that.

Thanks for working on this! Class looks pretty good I just have concerns on a couple of the helper APIs that I would rather clients just manage themselves (I like keeping a high bar on what API we elevate to the Basic level).

@ddunbar Updated

@swift-ci  please test

@swift-ci please test

LGTM, thanks!


Allow client to work with JFR

I was playing around with enabling Java Flight Recorder to look at the graviton issue, https://github.com/Tony-X/search-benchmark-game/issues/36 . While comparing the graviton3 vs graviton 2 jfr didn't bring up anything too interesting, I'll push this so there is less setup required next time we look at jfr.

Changes to Lucene Makefile in testing:
serve:
        @java -Xmx$(HEAP) -Xms$(HEAP) -XX:+UseParallelGC -XX:+UnlockDiagnosticVMOptions -XX:+DebugNonSafepoints -XX:+FlightRecorder -XX:StartFlightRecording=dumponexit=true,filename=grav3.jfr,settings=profile -cp build/libs/search-index-benchmark-game-lucene-1.0-SNAPSHOT-all.jar DoQuery idx

Thanks for trying JFR! Is it possible to suppress JFR's output to stdout or redirect it to another file?

Thanks for trying JFR! Is it possible to suppress JFR's output to stdout or redirect it to another file?

Thanks for the suggestion Tony.
I had a dig around and found this: https://github.com/openjdk/jdk/pull/3417
Specifying the param: -Xlog:jfr+startup=off will suppress the JFR output. This is the better solution going forward. Will close the issue without merging.

Thanks for trying JFR! Is it possible to suppress JFR's output to stdout or redirect it to another file?

Thanks for the suggestion Tony.
I had a dig around and found this: https://www.github.com/openjdk/jdk/pull/3417
Specifying the param: -Xlog:jfr+startup=off will suppress the JFR output. This is the better solution going forward. Will close the issue without merging.


400 Error: wrong region

When uploading, I am getting the following error "the region 'us-east-1' is wrong; expecting 'us-west-1":
Is there an option to configure the region, I can't see anywhere in the documentation a way to configure something like this.

InvalidArgumentthe region 'us-east-1' is wrong; expecting 'us-west-1'X-Amz-CredentialAKIAIQOLYIZLBGQIJAYQ/20151120/us-east-1/s3/aws4_requestus-west-1EB6D80227BE0BBD7cWAR4fRSd2IgzmohUhF1Tu/pJk3A0RC6XtqkfjALS/kB7PO+jnV4QLJLHQarhkFUGVpjUiAsBWI=

Ah sorry, I've been staring at this way too long and battling with errors. I found the relevant info now. Sorry!

@isjackwild Hi, can you tell me what was your issue?
I have the same error: <Message>the region 'us-east-1' is wrong; expecting 'eu-central-1'</Message>


docs: create rudus website

Closes #153

Codecov Report

Merging #154 (56a1890) into main (c5a28e8) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #154   +/-   ##
=======================================
  Coverage   97.86%   97.86%
=======================================
  Files          19       19
  Lines         187      187
  Branches       29       29
=======================================
  Hits          183      183
  Misses          4        4

Impacted Files
Coverage Δ

src/combinators/anyOf.ts
100.00% <ø> (ø)

src/combinators/between.ts
100.00% <ø> (ø)

src/combinators/many.ts
100.00% <ø> (ø)

src/combinators/many1.ts
100.00% <ø> (ø)

src/combinators/optional.ts
100.00% <ø> (ø)

src/combinators/separatedBy.ts
100.00% <ø> (ø)

src/combinators/sequenceOf.ts
100.00% <ø> (ø)

src/parsers/endOfInput.ts
100.00% <ø> (ø)

src/parsers/endOfLine.ts
100.00% <ø> (ø)

src/parsers/lazy.ts
100.00% <ø> (ø)

... and 5 more

Continue to review full report at Codecov.

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


Improve RNN cell abstraction.

The existing RNNCell protocol and RNNInput type are not flexible in that each time step has the take both the previous output and the hidden state. This PR lifts that restriction.

Rename RNNInput to RNNCellInput so that it's more accurate.
Add a new RNNCellOutput generic structure type that stores an output and a state.
Add associated type State in RNNCell.
Make the Output type of RNNCell be RNNOutput<TimeStepOutput, State>.

Thanks @superbobry for the suggestions.

@superbobry @tanmayb123 @eaplatanios Please review when you get a chance.

Thanks Richard! This looks good to me.


[WW-5388] Uses the latest JakartaEE FileUpload Servlet 6 package

Closes WW-5388

/cc: @burtonrhodes

/cc: @deki

@lukaszlenart  Looks good. The current version of this PR works well in my initial testing (dev) environment.

Just FYI, I implemented this PR on a small subset of my server cluster and have been receiving the following ambiguous errors in some of the upload requests.  I can't duplicate it in any testing environment, but curious if you might have a clue as to why Struts is creating an actionError with no value for the file.  For this implementation, I am not using the stream parser
Error printed by the code below
Unidentified ActionError present for file upload: [Error uploading: {0}!, Error uploading: {0}!]

Code that quickly checks for any file upload errors
if (hasActionErrors()) {
    List<String> uploadErrors = (List<String>) getActionErrors();
    log.error("Unidentified ActionError present for file upload: " + uploadErrors);
}

A redacted version of the action
public class UploadLocalFileJsonAction extends ActionSupport implements Validateable, UploadedFilesAware<UploadedFile<File>> {

    private FileAttachmentUpload fileAttachmentUpload;

    @Override
    public void withUploadedFiles(List<UploadedFile<UploadedFile<File>>> uploadedFiles) {
        if (!uploadedFiles.isEmpty()) {
            fileAttachmentUpload = UploadedFileHelper.createFromUploadedFile(uploadedFiles.get(0));
        }
    }

    public void validate() {
        // First check to see if there are any errors from the file upload
        if (hasActionErrors()) {
            List<String> uploadErrors = (List<String>) getActionErrors();
            log.error("Unidentified ActionError present for file upload: " + uploadErrors);
        }
    }

    public String execute() throws Exception {
        // Omitted for brevity
    }
}

@burtonrhodes I tried to play with the Showcase app and right now there is a problem uploading large files - I get blank page, yet the app is using the new Action Upload Interceptor

@burtonrhodes did you have a chance to re-test the latest changes? Everything works fine when testing with the Showcase app yet it uses the new action upload interceptor, but still the same MultiPartParser is used behind the scene. I even added a dedicated integration test to cover max files constraint.

@lukaszlenart yes, all looks good on my end.

LGTM 💯


Multiple changes

This pull request covers many commits. Almost all of them cover the addition of descriptions to methods and properties throughout the Express classes. When fields have descriptions then hovering over them in the IDE will show the description at the bottom of the IDE's code editor which I find really helpful.
You'll notice that the description is pulled from the comment at the top of each method. These "header comments" as I call them have three forward slashes (///). This not only visually separates them but allows me to automatically copy them to the description field with an IDE script.
In addition to the documentation changes I've also changed every local variable so that it starts with a lowercase letter. This is Xojo's recommended style of coding. Using lowercase identifiers for local variables makes it much easier to tell what is a class property (title cased) and what is local.

i wis the IDE did set the "Description" to the top comment (if any).
I must say i like the way you did this.
version may be upped to 5.0.4 let me know if the brance is ready.

Ready to go from my stand point.
Also happy to share the IDE script I use if that’s helpful.


User should be able to specify specific scenarios to run in the reporting pipeline

Right now all scenarios will be run every time the reporting pipeline is invoked. Some configuration mechanism should be implemented to select the scenarios to be run.

Anything after tests in the docker compose command will be appended to the Dockerfile's CMD so we need to just update report.py to accept arguments


Release ACS Chat Net SDK

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


I can´t use the @ in Chatterino

I can´t write the "@" in Chat but the copy works.
I use it on MacOS 10.14.6 (18G6042) I thinks this is the Problem.
The version is Chatterino 2.2.2 (commit 07fc0c3ad)
I hope this will help you.
Kind regards

This makes absolutely no sense. Could you provide more information?

If i type +L for the @ symbol they are nothing happens. But if i go in my Browser ich can type "@" and it copy and paste in Chatterino.

This is related to macOS keyboard inputs which are very different from other operating systems - I will mark this with "help wanted" as I'm not in a position to reproduce/fix this

There has been an issue similar to this posted here, but I can't find it.

Duplicate of #1979

sorry, I commented on wrong issue

From my comment in #3099: "The Chatterino keybindings page says that "Alt + Arrow keys" should change the selected split. I just found out that arrow keys dont work for me, instead those functions are on "Alt + H/J/K/L" for whatever reason."

From my comment in #3099: "The Chatterino keybindings page says that "Alt + Arrow keys" should change the selected split. I just found out that arrow keys dont work for me, instead those functions are on "Alt + H/J/K/L" for whatever reason."
So that function overwrites the @ key.

Does your keyboard have dedicated arrow keys? Or are the arrow keys accessed by using some keyboard combination like FN+something

It has dedicated Arrow Keys. (Roccat Vulcan TKL)

The arrow keys seem to send the correct code, however, arrow keys always seem to also add the "keypad" or "numpad" modifier, which is what confuses Chatterino.
I don't think we will end up doing a quick fix for this, but rather in the PR that will rework all hotkeys (including the ability to add custom hotkeys) we'd want to ensure we take this into account.
CC @Mm2PL
Thanks for helping me investigate @c0ldplasma

Issue still exist on macos build :/

Issue still exist on macos build :/

What build specifically, commit can be found in ⚙ -> About ( in brackets )
I ask because I'm unsure if it ended up being fixed intentionally or accidentally in #2340

This issue should definitely be fixed by #2340 (it is for me) since chatterino no longer has default keybindings for VIM hotkeys (Option+HJKL), which was overwriting the macOS default keybinding Option+L for @ before that PR.

Can confirm that its fixed in the newest nightly macos build

@Felanbird Chatterino 2.3.4 (commit 4e5170799)

@Felanbird Chatterino 2.3.4 (commit 4e51707)

That's what I expected, you can find and download the newest nightly build here.

@Felanbird on 34203dfa7 issue not longer exist

Fixed by #2340


Automated cherry pick of #2457: region: capability domain public network must equal domain_id

Cherry pick of #2457 on release/2.12.
#2457: region: capability domain public network must equal domain_id

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.12@609b052). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.12   #2460   +/-   ##
==============================================
  Coverage                ?   7.08%
==============================================
  Files                   ?     456
  Lines                   ?   71761
  Branches                ?       0
==============================================
  Hits                    ?    5081
  Misses                  ?   66261
  Partials                ?     419

Flag
Coverage Δ

#aFlag
7.08% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/capabilities.go
0% <0%> (ø)

Continue to review full report at Codecov.

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

/lgtm

/approve


Test with external datasets

[ ] QM9
[ ] Materials Project
[ ] OQMD
[ ] Matbench
etc.

Closing: HydraGNN


Onedrive file saver limit

Is it also limit to only 4MB when upload from URL with javascript file saver ?
Thanks,

hey @neunygph , I think it is 100M for url uploading.

ah I see, thanks @daboxu


How to use

I just installed the plugin but I don't see any option to use it.

Found it on the convert page! Works excellent, thanks for the work. :)


Support for different authorization methods when using RTMP

Good evening
Do you plan to add support for Adobe authorization or correct parsing of URL-based authorization?
We want to install a pair of IP cameras with OpenIPC in our lyceum on the top floor overlooking the sea, but have encountered problems with the transfer of traffic to Nimble.
Thank you.

outgoing:
  -<EMAIL_ADDRESS>
15:33:49  <       majestic> [    rtmp] try_connect@470               Connecting to RTMP URL<EMAIL_ADDRESS>15:33:49  <       majestic> [    rtmp] log_rtmp@44                   Parsing...
15:33:49  <       majestic> [    rtmp] log_rtmp@44                   Parsed protocol: 0
15:33:49  <       majestic> [    rtmp] log_rtmp@44                   Parsed host    : login
15:33:49  <       majestic> [    rtmp] log_rtmp@44                   Parsed app     : openipc/lyceum-178
15:33:49  <       majestic> [    rtmp] log_rtmp@44                   Could not resolve login: Unknown error (11)
15:33:49  <       majestic> [    rtmp] connect_thread@546            Connection to<EMAIL_ADDRESS>failed: -2

Never used forementioned Nimble before. Could you write thorough instruction how to reproduce your setup and test streaming Nimble with RTMP authorization?
I don't feel adding RTMP authorization would be tricky

outgoing:
  - rtmp://nimble.server/openipc?rtmpauth=login:password/lyceum-178

15:38:34  <       majestic> [    rtmp] try_connect@470               Connecting to RTMP URL rtmp://nimble.server/openipc?rtmpauth=login:password/lyceum-178...
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   Parsing...
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   Parsed protocol: 0
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   Parsed host    : nimble.server
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   Parsed app     : openipc?rtmpauth=login:password/lyceum-178
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   RTMP_Connect1, ... connected, handshaking
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   HandShake: Type Answer   : 03
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   HandShake: Server Uptime : 0
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   HandShake: FMS Version   : <IP_ADDRESS>
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   HandShake: Handshaking finished....
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   RTMP_Connect1, handshaked
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=4, ts=0
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=273, ts=0
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   Invoking connect
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   HandleServerBW: server BW = 5000000
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   HandleClientBW: client BW = 5000000 2
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   HandleCtrl, received ctrl. type: 0, len: 6
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   HandleCtrl, Stream Begin 0
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   HandleChangeChunkSize, received: chunk size change to 4128750
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ClientPacket, received: invoke 160 bytes
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   (object begin)
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., STRING:	_error>
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., NUMBER:	1.00>
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   Property: NULL
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., OBJECT>
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   (object begin)
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:              level, STRING:	error>
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:               code, STRING:	NetConnection.Connect.Rejected>
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:        description, STRING:	[ AccessManager.Reject ] : [ code=403 need auth; authmod=adobe ] : >
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   (object end)
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   (object end)
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   HandleInvoke, server invoking <_error>
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   HandleInvoke, received error for method call <connect>
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   HandleInvoke, error description: [ AccessManager.Reject ] : [ code=403 need auth; authmod=adobe ] :
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   PublisherAuth, need to set pubUser & pubPasswd for publisher auth
15:38:34  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
15:39:18  <       majestic> [    rtmp] log_rtmp@44                   RTMPSockBuf_Fill, remote host closed connection
15:39:18  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket, failed to read RTMP packet header
15:39:18  <       majestic> [    rtmp] connect_thread@546            Connection to rtmp://nimble.server/openipc?rtmpauth=login:password/lyceum-178 failed: -3

A little later I will try another method related to key generation and give information.
But in any case it is more complicated and I would not like to use it in the future on a permanent basis.
https://blog.wmspanel.com/2015/10/rtsp-publish-control-framework-overview.html
https://github.com/Softvelum/publish_control/blob/master/python/publish_signature_generator.py

For now, RTMP support within Majestic considered MVP, because it hasn't tested widely yet. It's not a problem to add new functions (like authorization) but for tests to ensure that task is done we should have actual setup

Okay, I'll ask my friends at Softvelum to create a couple of test accounts and pass them to you via PM.
Thank you very much for your technical support and quick responses ;)

Yes, it seems that the problem is due to parsing conditions.
I think we have to work with parameters like "host", "port", "app", "app_param", "stream" and others.
Unfortunately my experimental work through the key also failed
18:37:46  <       majestic> [    rtmp] try_connect@470               Connecting to RTMP URL rtmp://nimble.server/openipc?publishsign=aWQ9...pcD0=/lyceum-178...
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Parsing...
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Parsed protocol: 0
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Parsed host    : nimble.server
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Parsed app     : openipc?publishsign=aWQ9...pcD0=/lyceum-178
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   RTMP_Connect1, ... connected, handshaking
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   HandShake: Type Answer   : 03
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   HandShake: Server Uptime : 0
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   HandShake: FMS Version   : <IP_ADDRESS>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   HandShake: Handshaking finished....
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   RTMP_Connect1, handshaked
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=4, ts=0
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=432, ts=0
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Invoking connect
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   HandleServerBW: server BW = 5000000
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   HandleClientBW: client BW = 5000000 2
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   HandleCtrl, received ctrl. type: 0, len: 6
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   HandleCtrl, Stream Begin 0
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   HandleChangeChunkSize, received: chunk size change to 4128750
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ClientPacket, received: invoke 132 bytes
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   (object begin)
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., STRING:	_result>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., NUMBER:	1.00>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., OBJECT>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   (object begin)
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:             fmsVer, STRING:	Nimble/3.7.12-2>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   (object end)
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., OBJECT>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   (object begin)
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:              level, STRING:	status>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:               code, STRING:	NetConnection.Connect.Success>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:     objectEncoding, NUMBER:	0.00>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   (object end)
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   (object end)
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   HandleInvoke, server invoking <_result>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   HandleInvoke, received result for method call <connect>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=39, ts=0
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Invoking releaseStream
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=35, ts=0
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Invoking FCPublish
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=25, ts=0
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Invoking createStream
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ClientPacket, received: invoke 142 bytes
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   (object begin)
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., STRING:	onFCPublish>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., NUMBER:	0.00>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Property: NULL
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., OBJECT>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   (object begin)
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:              level, STRING:	status>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:               code, STRING:	NetStream.Publish.Start>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:        description, STRING:	FCPublish to stream zftlab-178.>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           clientid, NUMBER:<PHONE_NUMBER>.00>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   (object end)
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   (object end)
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   HandleInvoke, server invoking <onFCPublish>
18:37:46  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ClientPacket, received: invoke 29 bytes
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   (object begin)
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., STRING:	_result>
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., NUMBER:	4.00>
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   Property: NULL
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., NUMBER:	1.00>
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   (object end)
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   HandleInvoke, server invoking <_result>
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   HandleInvoke, received result for method call <createStream>
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=40, ts=0
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   Invoking publish
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   RTMPSockBuf_Fill, remote host closed connection
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=37, ts=0
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   Invoking FCUnpublish
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=34, ts=0
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   Invoking deleteStream
18:37:47  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket, failed to read RTMP packet header
18:37:47  <       majestic> [    rtmp] connect_thread@546            Connection to rtmp://nimble.server/openipc?publishsign=aWQ9...pcD0=/lyceum-178 failed: -3

What chunk size do I need for Majestic during negotiation ?
On the Nimble side, can set it with the parameter rtmp_chunk_size = <value>

Server access details sent to your email
Thank you.

So, now let's try to stream without authorization
outgoing:
  - rtmp://nimble.server/openipc/lyceum-178

19:40:13  <       majestic> [    rtmp] try_connect@470               Connecting to RTMP URL rtmp://nimble.server/openipc/lyceum-178...
19:40:13  <       majestic> [    rtmp] log_rtmp@44                   Parsing...
19:40:13  <       majestic> [    rtmp] log_rtmp@44                   Parsed protocol: 0
19:40:13  <       majestic> [    rtmp] log_rtmp@44                   Parsed host    : nimble.server
19:40:13  <       majestic> [    rtmp] log_rtmp@44                   Parsed app     : openipc/lyceum-178
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_Connect1, ... connected, handshaking
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandShake: Type Answer   : 03
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandShake: Server Uptime : 0
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandShake: FMS Version   : <IP_ADDRESS>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandShake: Handshaking finished....
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_Connect1, handshaked
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=4, ts=0
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=225, ts=0
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Invoking connect
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandleServerBW: server BW = 5000000
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandleClientBW: client BW = 5000000 2
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandleCtrl, received ctrl. type: 0, len: 6
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandleCtrl, Stream Begin 0
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandleChangeChunkSize, received: chunk size change to 4128750
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ClientPacket, received: invoke 132 bytes
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   (object begin)
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., STRING:	_result>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., NUMBER:	1.00>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., OBJECT>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   (object begin)
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:             fmsVer, STRING:	Nimble/3.7.12-2>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   (object end)
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., OBJECT>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   (object begin)
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:              level, STRING:	status>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:               code, STRING:	NetConnection.Connect.Success>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:     objectEncoding, NUMBER:	0.00>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   (object end)
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   (object end)
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandleInvoke, server invoking <_result>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandleInvoke, received result for method call <connect>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=39, ts=0
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Invoking releaseStream
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=35, ts=0
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Invoking FCPublish
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=25, ts=0
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Invoking createStream
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ClientPacket, received: invoke 142 bytes
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   (object begin)
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., STRING:	onFCPublish>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., NUMBER:	0.00>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: NULL
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., OBJECT>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   (object begin)
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:              level, STRING:	status>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:               code, STRING:	NetStream.Publish.Start>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:        description, STRING:	FCPublish to stream lyceum-178.>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           clientid, NUMBER:<PHONE_NUMBER>.00>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   (object end)
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   (object end)
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandleInvoke, server invoking <onFCPublish>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ClientPacket, received: invoke 29 bytes
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   (object begin)
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., STRING:	_result>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., NUMBER:	4.00>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: NULL
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., NUMBER:	1.00>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   (object end)
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandleInvoke, server invoking <_result>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandleInvoke, received result for method call <createStream>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=40, ts=0
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Invoking publish
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandleCtrl, received ctrl. type: 0, len: 6
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandleCtrl, Stream Begin 1
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ReadPacket: fd=42
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_ClientPacket, received: invoke 130 bytes
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   (object begin)
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., STRING:	onStatus>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., NUMBER:	0.00>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: NULL
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           no-name., OBJECT>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   (object begin)
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:              level, STRING:	status>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:               code, STRING:	NetStream.Publish.Start>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:        description, STRING:	Publishing lyceum-178.>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   Property: <Name:           clientid, NUMBER:<PHONE_NUMBER>.00>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   (object end)
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   (object end)
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandleInvoke, server invoking <onStatus>
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   HandleInvoke, onStatus: NetStream.Publish.Start
19:40:14  <       majestic> [    rtmp] try_connect@518               Connection to rtmp://nimble.server/openipc/lyceum-178 successful
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=46, ts=0
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=34678, ts=0
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=105, ts=40
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=43, ts=80
19:40:14  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=35, ts=120
19:40:15  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=38, ts=160
19:40:15  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=91, ts=200
19:40:15  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=132, ts=240
19:40:15  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=201, ts=280
19:40:15  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=227, ts=320
19:40:15  <       majestic> [    rtmp] log_rtmp@44                   WriteN, RTMP send error 32 (239 bytes)
19:40:15  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=42, size=37, ts=0
19:40:15  <       majestic> [    rtmp] log_rtmp@44                   WriteN, RTMP send error 32 (45 bytes)
19:40:15  <       majestic> [    rtmp] log_rtmp@44                   RTMP_SendPacket: fd=-1, size=34, ts=0
19:40:15  <       majestic> [    rtmp] log_rtmp@44                   WriteN, RTMP send error 9 (42 bytes)
19:40:15  <       majestic> [rtmp-str] nal_cb@838                    RTMP stream disconnected

https://wmspanel.com/nimble/param?g=rtmp#rtmp_check_stream_id_for_protocol_control_messages
On the server side we see the following answers in the logs
[2023-01-02 19:33:09 P283124-T283139] [rtmp] E: unknown message stream id for VideoMessage, msg_id=0
[2023-01-02 19:33:10 P283124-T283139] [rtmp] E: unknown message stream id for VideoMessage, msg_id=-1
[2023-01-02 19:33:12 P283124-T283139] [rtmp] E: unknown message stream id for VideoMessage, msg_id=-1
[2023-01-02 19:33:13 P283124-T283139] [rtmp] E: unknown message stream id for VideoMessage, msg_id=-1
[2023-01-02 19:33:14 P283124-T283139] [rtmp] E: unknown message stream id for VideoMessage, msg_id=-1
[2023-01-02 19:33:15 P283124-T283139] [rtmp] E: unknown message stream id for VideoMessage, msg_id=-1
[2023-01-02 19:33:16 P283124-T283139] [rtmp] E: unknown message stream id for VideoMessage, msg_id=-1

In my humble opinion, the problem must be found somewhere here
https://rtmp.veriskope.com/docs/spec/#61-rtmp-message-format

Do you use H.264 or H.265 codec in last example?

According to RMTP documentation, right URL scheme is rtmp://<IP>:<PORT>/<publishing_point>?<username>&<password>/<stream_name>
Checked with Nimble, it accepts credentials, but anyway it drops subsequent packets for unknown reason. From my perspective, something wrong with stream configuration

Good Afternoon.
The server logs now show a change in the problem data
[2023-01-03 10:07:05 P283124-T283139] [rtmp] E: unknown message stream id for VideoMessage, msg_id=-1
[2023-01-03 10:07:07 P283124-T283139] [rtmp] E: unknown message stream id for VideoMessage, msg_id=-1
[2023-01-03 10:07:08 P283124-T283139] [rtmp] E: unknown message stream id for VideoMessage, msg_id=-1
[2023-01-03 10:07:10 P283124-T283139] [rtmp] E: unknown message stream id for VideoMessage, msg_id=-1
[2023-01-03 10:11:52 P283124-T283143] [rtsp] E: unable to parse request line for [UNKNOWN]: GET / HTTP/1.0
[2023-01-03 10:44:00 P283124-T283139] [rtmp] E: [VM] AVC SEQUENCE header is required first for 'openipc/you-stream-name'
[2023-01-03 10:44:01 P283124-T283139] [rtmp] E: [VM] AVC SEQUENCE header is required first for 'openipc/you-stream-name'
[2023-01-03 10:44:01 P283124-T283139] [rtmp] E: [VM] AVC SEQUENCE header is required first for 'openipc/you-stream-name'
[2023-01-03 10:44:01 P283124-T283139] [rtmp] E: [VM] AVC SEQUENCE header is required first for 'openipc/you-stream-name'
[2023-01-03 10:44:01 P283124-T283139] [rtmp] E: [VM] AVC SEQUENCE header is required first for 'openipc/you-stream-name'
[2023-01-03 10:44:01 P283124-T283139] [rtmp] E: [VM] AVC SEQUENCE header is required first for 'openipc/you-stream-name'
[2023-01-03 10:44:01 P283124-T283139] [rtmp] E: [VM] AVC SEQUENCE header is required first for 'openipc/you-stream-name'
[2023-01-03 10:44:01 P283124-T283139] [rtmp] E: [VM] AVC SEQUENCE header is required first for 'openipc/you-stream-name'

So, I am writing a report on the experiments.
We're definitely making progress on the solution, but there are still a few problems not where we thought we'd be.
All problems remained only in parsing...
So, I will give examples of lines from majestic.yaml and show what we get in Nimble
I will replace the domain name and the login and password, you know which ones to use for tests
TEST № 1 (we disabled authorization for the test)
Majestic config
outgoing:
  - rtmp://nimble.server/openipc/lyceum-178

This is what the server sees in the queries
D: RtmpStreamBuffer::setMetadata for openipc/lyceum-178/lyceum-178

TEST № 2 (authorized)
Majestic config
outgoing:
  -<EMAIL_ADDRESS>
In this case, the server side does not get to check the dogin and password, because the structure is not correct.
By the way, in the Majestic diagnostic the APP name also looks strange and contains the name of the stream.
15:40:17  <       majestic> [    rtmp] log_rtmp@46                   Parsing...
15:40:17  <       majestic> [    rtmp] log_rtmp@46                   Parsed protocol: 0
15:40:17  <       majestic> [    rtmp] log_rtmp@46                   Parsed host    : nimble.server
15:40:17  <       majestic> [    rtmp] log_rtmp@46                   Parsed app     : openipc/lyceum-178

TEST № 3 (truncated line)
Majestic config
outgoing:
  -<EMAIL_ADDRESS>
This is what the server sees in the queries
D: RtmpStreamBuffer::setMetadata for openipc/openipc

Authorization is successful, the stream is broadcast and visible in players.
I think the results of my experiments are clear to you and you will be able to make a structure correction, thank you.

Good evening
So, it's been two days of testing the OpenIPC and Nimble combination.
Everything works quite well and stable, thank you very much.
We tested it on two OpenIPC cameras obtained via OpenCollective (Hisilicon hi3518ev200 processor) and one camera with Ingenic t31x processor.
Now I want to be able to specify any stream names.
Let me remind you that at the moment stream name is copied from the App name and it is somewhere inside Majestic structure because it is not present in config.
Also, my professor in high school asked if this system can stream audio.
At the moment I have not been able to set up the streaming. Is it even possible ?
https://ltdfoto.ru/image/XPkgCW
Also was a great nice impression of the CBR.
Usually we can see the keyframes, but in the Majestic it's not, probably a very strict work VBV (?).
The snapshot is made with the DVB analyzer.

Let's go step-by-step and don't mix different probs in single issue because it'll become unmanageable.
Please test new version with added AAC support to RTMP. Tested on Telegram with 48000 sample rate (not sure that others will be supported)

di niente

Unfortunately, the new version of Majestic was again broken authorization option and there is no way to do tests.
Reports from Nimble server:
[2023-01-06 16:19:54 P315552-T315567] [rtmp] E: publish not authorized for openipc/openipc
[2023-01-06 16:20:47 P315552-T315567] [rtmp] E: publish not authorized for openipc/openipc
[2023-01-06 16:21:11 P315552-T315567] [rtmp] E: publish not authorized for openipc/openipc
[2023-01-06 16:27:11 P315552-T315567] [rtmp] E: publish not authorized for openipc/openipc

Majestic logs:
16:29:37  <       majestic> [    rtmp] try_connect@246               Connecting to RTMP URL rtmp://nimble.server/openipc...
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Parsing...
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Parsed protocol: 0
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Parsed host    : nimble.server
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Parsed app     : openipc
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_Connect1, ... connected, handshaking
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   HandShake: Type Answer   : 03
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   HandShake: Server Uptime : 0
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   HandShake: FMS Version   : <IP_ADDRESS>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   HandShake: Handshaking finished....
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_Connect1, handshaked
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=44, size=4, ts=0
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=44, size=148, ts=0
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Invoking connect
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ReadPacket: fd=44
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   HandleServerBW: server BW = 5000000
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ReadPacket: fd=44
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   HandleClientBW: client BW = 5000000 2
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ReadPacket: fd=44
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   HandleCtrl, received ctrl. type: 0, len: 6
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   HandleCtrl, Stream Begin 0
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ReadPacket: fd=44
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   HandleChangeChunkSize, received: chunk size change to 4128750
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ReadPacket: fd=44
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ClientPacket, received: invoke 132 bytes
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   (object begin)
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., STRING:	_result>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., NUMBER:	1.00>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., OBJECT>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   (object begin)
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:             fmsVer, STRING:	Nimble/3.7.12-2>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   (object end)
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., OBJECT>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   (object begin)
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:              level, STRING:	status>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:               code, STRING:	NetConnection.Connect.Success>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:     objectEncoding, NUMBER:	0.00>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   (object end)
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   (object end)
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   HandleInvoke, server invoking <_result>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   HandleInvoke, received result for method call <connect>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=44, size=36, ts=0
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Invoking releaseStream
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=44, size=32, ts=0
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Invoking FCPublish
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=44, size=25, ts=0
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Invoking createStream
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ReadPacket: fd=44
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ClientPacket, received: invoke 139 bytes
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   (object begin)
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., STRING:	onFCPublish>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., NUMBER:	0.00>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: NULL
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., OBJECT>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   (object begin)
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:              level, STRING:	status>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:               code, STRING:	NetStream.Publish.Start>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:        description, STRING:	FCPublish to stream openipc.>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           clientid, NUMBER:<PHONE_NUMBER>.00>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   (object end)
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   (object end)
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   HandleInvoke, server invoking <onFCPublish>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ReadPacket: fd=44
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ClientPacket, received: invoke 29 bytes
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   (object begin)
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., STRING:	_result>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., NUMBER:	4.00>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: NULL
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., NUMBER:	1.00>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   (object end)
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   HandleInvoke, server invoking <_result>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   HandleInvoke, received result for method call <createStream>
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=44, size=37, ts=0
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Invoking publish
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ReadPacket: fd=44
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMPSockBuf_Fill, remote host closed connection
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=44, size=34, ts=0
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Invoking FCUnpublish
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=44, size=34, ts=0
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   Invoking deleteStream
16:29:37  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ReadPacket, failed to read RTMP packet header
16:29:37  <       majestic> [    rtmp] connect_thread@320            Connection to rtmp://nimble.server/openipc failed: -3

Separately, I want to note that the reconnect connection is not carried out.
I think this is not very good in the future to stabilize the work.

Please test new version with added AAC support to RTMP. Tested on Telegram with 48000 sample rate (not sure that others will be supported)

Thanks
A new Issue on this test has been opened
https://github.com/OpenIPC/majestic/issues/93

RTMP authorization code wasn't touched at all, it is the same as was before

Unfortunately, there is no authorization and you can see it above.
The broadcast has stopped working even with the audio turned off.
Apart from updating the firmware nothing has been done.

I created a test project in my sandbox with Nimble based on Docker container and maybe it will help in our experiments.
Also found a second way to test RTMP streams, an example here


Updated WebSockets tests

Updated https://github.com/aspnet/SignalR/pull/94 in a new PR.
@BrennanConroy @moozzyk @anurse @davidfowl

Hi @mikaelm12, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Looks good! :ship::it:

Here's the build failure on linux and OSX:
fail:     Microsoft.AspNetCore.SignalR.Tests.EndToEndTests.WebSocketsTest [FAIL]
info:       System.PlatformNotSupportedException : The WebSocket protocol is not supported on this platform.
info:       Stack Trace:

:clap: