ui_ng fix

I commit this pr for two problem I melt in page: project -> detail -> repositories

the cell of the subgrid are not aligned
the 'author' and 'version' cell of the subgrid is not big enough when my author name is an email, and version is something looks like '17.06.0-ce', it also cause a word wrap issue of the grid title when it is in chinese languge.

ps: hope you can understand what I wrote, I tried but poor in english :)

Coverage increased (+0.008%) to 54.7% when pulling 5bc8c9b5fd86559bb33cb898284b38fc6fc4b69d on qinershi:master into bb00c2c2cfea1207d7b7c1e4a87cec219eeaf4b6 on vmware:master.

@qinershi，
Thanks a lot for contributing code to Harbor. Just one question,  have you checked and verified the UI changes you made? Seems the widths of the columns are changed to be bigger a lot.

@steven-zou,
Thank you for replying me.
You are right, it's too big, I have restore the width what it is before.
And one more question, as the 'author' is come for username of the user, can harbor limits the length of the username when creating users? In this case the 'author' will not be too long for the cell.

Coverage increased (+0.02%) to 54.711% when pulling 0b5ebb8baff75e4928176cc0da6853228a6b9f75 on qinershi:master into bb00c2c2cfea1207d7b7c1e4a87cec219eeaf4b6 on vmware:master.

@qinyuanbin
Seems this PR is already outdated, I'll close it. If you still want to resize the column width, you can submit a new one.
BTW, we already have resized the column width,  please check the latest code before do additional changes. Thanks


Create icon

We need an icon for the app

Submitted Pull Request
https://github.com/Keboo/PointerStar/pull/64


[firebase_auth] 0.18 Changelog doesn't incude emailVerified

I upgraded from 0.16 to 0.18 and I can see FirebaseUser.isEmailVerified was changed to User.emailVerified, so there's no is anymore (which I personally don't like, I read it better with the is), but this wasn't included on the Changelog.

https://pub.dev/packages/firebase_auth/changelog

Still not added, fairly easy to find but still. :)

Will close this one off - fairly dated now - apologies it was missed.


Structured Data Provider

Allows for generation of structured data.  Currently includes CSS, Delimited, and HTML methods.

What's the use case for this? I'm not against it at all, just curious.

@drpoggi HTML and delimited I think would be useful if you are developing something that allows users to input HTML (CMS, for example) or to import delimited date (database front-end/spreadsheet app).
Faker also offers a HTML lorem provider that generates a complete HTML document and this is an initial step towards implementing something more like that.   Might be useful if you are developing say, a search engine that indexes HTML documents.

Ok makes sense, thought it might be something like that, thanks for the explanation!

Current coverage is 99.24% (diff: 100%)

Merging #105 into master will increase coverage by 0.04%

@@             master       #105   diff @@
==========================================
  Files            41         43     +2
  Lines          1751       1855   +104
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1737       1841   +104
  Misses           14         14
  Partials          0          0

Powered by Codecov. Last update 028dedf...8efe374

@wikkiewikkie I'm not sure that html tags are useful, but i will merge it, because i think thtat delimited() is very useful. Also it would be great, if you add to Structured jsonify() that will write data to json file.

@wikkiewikkie We need refactoring of Structured. PEP8.


Wazuh-dashboard fails at stopping service after upgrade to 4.9.0

Describe the bug
In this issue https://github.com/wazuh/wazuh-jenkins/issues/6822 it has been detected that wazuh-dashboard service fails at stopping after upgrading to 4.9.0 and starting the service using service wazuh-dashboard start. It has been detected in automated tests using pytest.
To Reproduce
Steps to reproduce this error in a local environment are explained in the following comment: https://github.com/wazuh/wazuh-jenkins/issues/6822#issuecomment-2278493473.
In short, it was possible to reproduce the error with a rather simple script:
script2.sh
#!/bin/bash

service wazuh-dashboard start
systemctl status wazuh-dashboard
service wazuh-dashboard stop
systemctl status wazuh-dashboard

The steps to reproduce are:

Deploy a virtual machine with Ubuntu 20.04
Install AIO Wazuh 4.8.1 using:

curl -sO https://packages.wazuh.com/4.8/wazuh-install.sh && sudo bash ./wazuh-install.sh -a

Download the 4.9.0 package for wazuh-dashboard

wget https://packages-dev.wazuh.com/pre-release/apt/pool/main/w/wazuh-dashboard/wazuh-dashboard_4.9.0-1_amd64.deb

Take a snapshot to be able to return to this point for retesting.

Upgrade wazuh-dashboard to 4.9.0 using the following command:

dpkg --force-confold -i wazuh-dashboard_4.9.0-1_amd64.deb

Run the script with:

./script2.sh

To re-run the test, return to the snapshot and re-run the script.

The following shows how the problem was carried out and successfully reproduced:
root@wazuh3-aio:/home/vagrant# dpkg --force-confold -i wazuh-dashboard_4.9.0-1_amd64.deb
(Reading database ... 226490 files and directories currently installed.)
Preparing to unpack wazuh-dashboard_4.9.0-1_amd64.deb ...
Unpacking wazuh-dashboard (4.9.0-1) over (4.8.1-1) ...
Setting up wazuh-dashboard (4.9.0-1) ...
Installing new version of config file /etc/default/wazuh-dashboard ...
Installing new version of config file /etc/systemd/system/wazuh-dashboard ...
Installing new version of config file /etc/systemd/system/wazuh-dashboard.service ...
Installing new version of config file /etc/wazuh-dashboard/node.options ...

Configuration file '/etc/wazuh-dashboard/opensearch_dashboards.yml'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
 ==> Using current old file as you requested.
root@wazuh3-aio:/home/vagrant# ./script2.sh
● wazuh-dashboard.service - wazuh-dashboard
     Loaded: loaded (/etc/systemd/system/wazuh-dashboard.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2024-08-09 17:45:41 UTC; 5s ago
   Main PID: 55055 (node)
      Tasks: 11 (limit: 4595)
     Memory: 194.1M
     CGroup: /system.slice/wazuh-dashboard.service
             └─55055 /usr/share/wazuh-dashboard/node/bin/node /usr/share/wazuh-dashboard/src/cli/dist -c /etc/wazuh-dashboard/opensearch_dashboards.yml

Aug 09 17:45:41 wazuh3-aio systemd[1]: Started wazuh-dashboard.
● wazuh-dashboard.service - wazuh-dashboard
     Loaded: loaded (/etc/systemd/system/wazuh-dashboard.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Fri 2024-08-09 17:45:50 UTC; 15ms ago
    Process: 55055 ExecStart=/usr/share/wazuh-dashboard/bin/opensearch-dashboards -c /etc/wazuh-dashboard/opensearch_dashboards.yml (code=exited, status=1/FAILURE)
   Main PID: 55055 (code=exited, status=1/FAILURE)

Aug 09 17:45:49 wazuh3-aio opensearch-dashboards[55055]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 09 17:45:49 wazuh3-aio opensearch-dashboards[55055]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 09 17:45:49 wazuh3-aio opensearch-dashboards[55055]: /usr/share/wazuh-dashboard/node_modules/rxjs/internal/util/hostReportError.js:4
Aug 09 17:45:49 wazuh3-aio opensearch-dashboards[55055]:     setTimeout(function () { throw err; }, 0);
Aug 09 17:45:49 wazuh3-aio opensearch-dashboards[55055]:                              ^
Aug 09 17:45:49 wazuh3-aio opensearch-dashboards[55055]: [Error [ObjectUnsubscribedError]: object unsubscribed]
Aug 09 17:45:49 wazuh3-aio opensearch-dashboards[55055]: Node.js v18.19.0
Aug 09 17:45:50 wazuh3-aio systemd[1]: wazuh-dashboard.service: Main process exited, code=exited, status=1/FAILURE
Aug 09 17:45:50 wazuh3-aio systemd[1]: wazuh-dashboard.service: Failed with result 'exit-code'.
Aug 09 17:45:50 wazuh3-aio systemd[1]: Stopped wazuh-dashboard.
root@wazuh3-aio:/home/vagrant# cat script2.sh
#!/bin/bash

service wazuh-dashboard start
systemctl status wazuh-dashboard
service wazuh-dashboard stop
systemctl status wazuh-dashboard

journalctl -r -u wazuh-dashboard output
-- Logs begin at Fri 2024-08-09 14:17:54 UTC, end at Fri 2024-08-09 17:46:34 UTC. --
Aug 09 17:45:50 wazuh3-aio systemd[1]: Stopped wazuh-dashboard.
Aug 09 17:45:50 wazuh3-aio systemd[1]: wazuh-dashboard.service: Failed with result 'exit-code'.

Aug 09 17:45:49 wazuh3-aio opensearch-dashboards[55055]: {"type":"log","@timestamp":"2024-08-09T17:45:49Z","tags":["info","plugins-service"],"pid":55055,"message":"Plugin \"dataSource\" is disabled."}
Aug 09 17:45:49 wazuh3-aio opensearch-dashboards[55055]: {"type":"log","@timestamp":"2024-08-09T17:45:49Z","tags":["info","plugins-service"],"pid":55055,"message":"Plugin \"cspHandler\" is disabled."}
Aug 09 17:45:49 wazuh3-aio opensearch-dashboards[55055]: {"type":"log","@timestamp":"2024-08-09T17:45:49Z","tags":["info","plugins-service"],"pid":55055,"message":"Plugin \"applicationConfig\" is disabled."}
Aug 09 17:45:49 wazuh3-aio opensearch-dashboards[55055]: {"type":"log","@timestamp":"2024-08-09T17:45:49Z","tags":["info","plugins-service"],"pid":55055,"message":"Plugin \"dataSourceManagement\" has been disabled since the following d>
Aug 09 17:45:47 wazuh3-aio systemd[1]: Stopping wazuh-dashboard...
Aug 09 17:45:41 wazuh3-aio systemd[1]: Started wazuh-dashboard.
Aug 09 17:44:10 wazuh3-aio systemd[1]: Stopped wazuh-dashboard.
Aug 09 17:44:10 wazuh3-aio systemd[1]: wazuh-dashboard.service: Succeeded.
Aug 09 17:44:10 wazuh3-aio opensearch-dashboards[53808]: {"type":"log","@timestamp":"2024-08-09T17:44:10Z","tags":["info","plugins-system"],"pid":53808,"message":"Stopping all plugins."}
Aug 09 17:44:10 wazuh3-aio systemd[1]: Stopping wazuh-dashboard...
Aug 09 14:28:04 wazuh3-aio opensearch-dashboards[53808]: {"type":"response","@timestamp":"2024-08-09T14:28:03Z","tags":[],"pid":53808,"method":"get","statusCode":200,"req":{"url":"/status","method":"get","headers":{"host":"localhost",">
Aug 09 14:28:01 wazuh3-aio opensearch-dashboards[53808]: {"type":"log","@timestamp":"2024-08-09T14:28:01Z","tags":["info","http","server","OpenSearchDashboards"],"pid":53808,"message":"http server running at [https://<IP_ADDRESS>:443](https://<IP_ADDRESS>/)"}
Aug 09 14:28:01 wazuh3-aio opensearch-dashboards[53808]: {"type":"log","@timestamp":"2024-08-09T14:28:01Z","tags":["listening","info"],"pid":53808,"message":"Server running at [https://<IP_ADDRESS>:443](https://<IP_ADDRESS>/)"}

It can be seen that at 14:28 Wazuh AOI 4.8.1 was installed in the virtual machine and at 17:44 the wazuh-dashboard update to 4.9.0 started running, finishing this update at 17:45:41, at which time the script was executed and the above output was obtained.
Expected behavior
The expected behavior is that it should not fail to stop the wazuh-dashboard service.

Following the provided steps, I could replicate the problem:

root@ubuntu20:/home/vagrant# journalctl -r -u wazuh-dashboard
-- Logs begin at Mon 2024-08-12 07:51:13 UTC, end at Mon 2024-08-12 08:38:46 UTC. --
Aug 12 08:38:46 ubuntu20 systemd[1]: Stopped wazuh-dashboard.
Aug 12 08:38:46 ubuntu20 systemd[1]: wazuh-dashboard.service: Succeeded.
Aug 12 08:38:46 ubuntu20 systemd[1]: Stopping wazuh-dashboard...
Aug 12 08:38:45 ubuntu20 systemd[1]: Started wazuh-dashboard.
Aug 12 08:38:10 ubuntu20 systemd[1]: Stopped wazuh-dashboard.
Aug 12 08:38:10 ubuntu20 systemd[1]: wazuh-dashboard.service: Succeeded.
Aug 12 08:38:09 ubuntu20 systemd[1]: Stopping wazuh-dashboard...
Aug 12 08:38:09 ubuntu20 systemd[1]: Started wazuh-dashboard.
Aug 12 08:20:52 ubuntu20 systemd[1]: Stopped wazuh-dashboard.
Aug 12 08:20:52 ubuntu20 systemd[1]: wazuh-dashboard.service: Failed with result 'exit-code'.
Aug 12 08:20:52 ubuntu20 systemd[1]: wazuh-dashboard.service: Main process exited, code=exited, status=1/FAILURE
Aug 12 08:20:52 ubuntu20 opensearch-dashboards[66443]: Node.js v18.19.0
Aug 12 08:20:52 ubuntu20 opensearch-dashboards[66443]: [Error [ObjectUnsubscribedError]: object unsubscribed]
Aug 12 08:20:52 ubuntu20 opensearch-dashboards[66443]:                              ^
Aug 12 08:20:52 ubuntu20 opensearch-dashboards[66443]:     setTimeout(function () { throw err; }, 0);
Aug 12 08:20:52 ubuntu20 opensearch-dashboards[66443]: /usr/share/wazuh-dashboard/node_modules/rxjs/internal/util/hostReportError.js:4
Aug 12 08:20:52 ubuntu20 opensearch-dashboards[66443]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 08:20:52 ubuntu20 opensearch-dashboards[66443]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 08:20:52 ubuntu20 opensearch-dashboards[66443]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 08:20:52 ubuntu20 opensearch-dashboards[66443]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 08:20:52 ubuntu20 opensearch-dashboards[66443]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 08:20:52 ubuntu20 opensearch-dashboards[66443]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 08:20:51 ubuntu20 opensearch-dashboards[66443]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 08:20:51 ubuntu20 opensearch-dashboards[66443]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 08:20:51 ubuntu20 opensearch-dashboards[66443]: [Error [ObjectUnsubscribedError]: object unsubscribed]
Aug 12 08:20:51 ubuntu20 opensearch-dashboards[66443]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 08:20:51 ubuntu20 opensearch-dashboards[66443]: {"type":"log","@timestamp":"2024-08-12T08:20:51Z","tags":["info","plugins-service"],"pid":66443,"message":"Plugin \"visTypeXy\" is dis>
Aug 12 08:20:51 ubuntu20 opensearch-dashboards[66443]: {"type":"log","@timestamp":"2024-08-12T08:20:51Z","tags":["info","plugins-service"],"pid":66443,"message":"Plugin \"dataSource\" is di>
Aug 12 08:20:51 ubuntu20 opensearch-dashboards[66443]: {"type":"log","@timestamp":"2024-08-12T08:20:51Z","tags":["info","plugins-service"],"pid":66443,"message":"Plugin \"cspHandler\" is di>
Aug 12 08:20:51 ubuntu20 opensearch-dashboards[66443]: {"type":"log","@timestamp":"2024-08-12T08:20:51Z","tags":["info","plugins-service"],"pid":66443,"message":"Plugin \"applicationConfig\>
Aug 12 08:20:51 ubuntu20 opensearch-dashboards[66443]: {"type":"log","@timestamp":"2024-08-12T08:20:51Z","tags":["info","plugins-service"],"pid":66443,"message":"Plugin \"dataSourceManageme>
Aug 12 08:20:49 ubuntu20 systemd[1]: Stopping wazuh-dashboard...
Aug 12 08:20:37 ubuntu20 systemd[1]: Started wazuh-dashboard.
Aug 12 08:17:42 ubuntu20 systemd[1]: Stopped wazuh-dashboard.
Aug 12 08:17:42 ubuntu20 systemd[1]: wazuh-dashboard.service: Succeeded.
Aug 12 08:17:42 ubuntu20 opensearch-dashboards[65507]: {"type":"log","@timestamp":"2024-08-12T08:17:42Z","tags":["info","plugins-system"],"pid":65507,"message":"Stopping all plugins."}
Aug 12 08:17:42 ubuntu20 systemd[1]: Stopping wazuh-dashboard...
Aug 12 08:02:57 ubuntu20 opensearch-dashboards[65507]: {"type":"response","@timestamp":"2024-08-12T08:02:56Z","tags":[],"pid":65507,"method":"get","statusCode":200,"req":{"url":"/status","m>
Aug 12 08:02:48 ubuntu20 opensearch-dashboards[65507]: {"type":"log","@timestamp":"2024-08-12T08:02:48Z","tags":["info","http","server","OpenSearchDashboards"],"pid":65507,"message":"htt

The error only happened the first time I executed the provided script and regarding the logs the service seems to be stopped as it was pretended. I tried to execute the script more times and the error did not happen again.
The error does not show much information, so it could be required trying to get more information. But the error seems to be related to trying of unsubscribing of an unsubscribed object and this could be related to some code of platform.

I added a wait time to stop the service after this is started, and I got the error too.

root@ubuntu20:/home/vagrant# journalctl -r -u wazuh-dashboard
-- Logs begin at Mon 2024-08-12 07:51:13 UTC, end at Mon 2024-08-12 10:10:28 UTC. --
Aug 12 10:09:36 ubuntu20 systemd[1]: Stopped wazuh-dashboard.
Aug 12 10:09:36 ubuntu20 systemd[1]: wazuh-dashboard.service: Failed with result 'exit-code'.
Aug 12 10:09:36 ubuntu20 systemd[1]: wazuh-dashboard.service: Main process exited, code=exited, status=1/FAILURE
Aug 12 10:09:36 ubuntu20 opensearch-dashboards[67467]: Node.js v18.19.0
Aug 12 10:09:36 ubuntu20 opensearch-dashboards[67467]: [Error [ObjectUnsubscribedError]: object unsubscribed]
Aug 12 10:09:36 ubuntu20 opensearch-dashboards[67467]:                              ^
Aug 12 10:09:36 ubuntu20 opensearch-dashboards[67467]:     setTimeout(function () { throw err; }, 0);
Aug 12 10:09:36 ubuntu20 opensearch-dashboards[67467]: /usr/share/wazuh-dashboard/node_modules/rxjs/internal/util/hostReportError.js:4
Aug 12 10:09:36 ubuntu20 opensearch-dashboards[67467]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 10:09:36 ubuntu20 opensearch-dashboards[67467]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 10:09:36 ubuntu20 opensearch-dashboards[67467]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 10:09:36 ubuntu20 opensearch-dashboards[67467]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 10:09:36 ubuntu20 opensearch-dashboards[67467]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 10:09:36 ubuntu20 opensearch-dashboards[67467]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 10:09:35 ubuntu20 opensearch-dashboards[67467]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 10:09:35 ubuntu20 opensearch-dashboards[67467]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 10:09:35 ubuntu20 opensearch-dashboards[67467]: [Error [ObjectUnsubscribedError]: object unsubscribed]
Aug 12 10:09:35 ubuntu20 opensearch-dashboards[67467]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 10:09:35 ubuntu20 opensearch-dashboards[67467]: {"type":"log","@timestamp":"2024-08-12T10:09:35Z","tags":["info","plugins-service"],"pid":67467,"message":"Plugin \"visTypeXy\" is dis>
Aug 12 10:09:35 ubuntu20 opensearch-dashboards[67467]: {"type":"log","@timestamp":"2024-08-12T10:09:35Z","tags":["info","plugins-service"],"pid":67467,"message":"Plugin \"dataSource\" is di>
Aug 12 10:09:35 ubuntu20 opensearch-dashboards[67467]: {"type":"log","@timestamp":"2024-08-12T10:09:35Z","tags":["info","plugins-service"],"pid":67467,"message":"Plugin \"cspHandler\" is di>
Aug 12 10:09:35 ubuntu20 opensearch-dashboards[67467]: {"type":"log","@timestamp":"2024-08-12T10:09:35Z","tags":["info","plugins-service"],"pid":67467,"message":"Plugin \"applicationConfig\>
Aug 12 10:09:35 ubuntu20 opensearch-dashboards[67467]: {"type":"log","@timestamp":"2024-08-12T10:09:35Z","tags":["info","plugins-service"],"pid":67467,"message":"Plugin \"dataSourceManageme>
Aug 12 10:09:31 ubuntu20 systemd[1]: Stopping wazuh-dashboard...
Aug 12 10:09:28 ubuntu20 systemd[1]: Started wazuh-dashboard.

I tried with OpenSearch Dashboards 2.13.0 (.deb package), and I got to replicate the same problem if stop the service after (2-3) seconds

Version

root@ubuntu20:/usr/share/opensearch-dashboards# grep version /usr/share/opensearch-dashboards/package.json
  "version": "2.13.0",

Error:

root@ubuntu20:/etc/opensearch-dashboards# journalctl -u opensearch-dashboards | tail -n30
Aug 12 11:04:05 ubuntu20 systemd[1]: Started "OpenSearch Dashboards".
Aug 12 11:04:07 ubuntu20 systemd[1]: Stopping "OpenSearch Dashboards"...
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: {"type":"log","@timestamp":"2024-08-12T11:04:09Z","tags":["info","plugins-service"],"pid":71073,"message":"Plugin \"dataSourceManagement\" has been disabled since the following direct or transitive dependencies are missing or disabled: [dataSource]"}
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: {"type":"log","@timestamp":"2024-08-12T11:04:09Z","tags":["info","plugins-service"],"pid":71073,"message":"Plugin \"applicationConfig\" is disabled."}
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: {"type":"log","@timestamp":"2024-08-12T11:04:09Z","tags":["info","plugins-service"],"pid":71073,"message":"Plugin \"cspHandler\" is disabled."}
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: {"type":"log","@timestamp":"2024-08-12T11:04:09Z","tags":["info","plugins-service"],"pid":71073,"message":"Plugin \"dataSource\" is disabled."}
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: {"type":"log","@timestamp":"2024-08-12T11:04:09Z","tags":["info","plugins-service"],"pid":71073,"message":"Plugin \"visTypeXy\" is disabled."}
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: [Error [ObjectUnsubscribedError]: object unsubscribed]
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 11:04:09 ubuntu20 opensearch-dashboards[71073]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 11:04:10 ubuntu20 opensearch-dashboards[71073]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 11:04:10 ubuntu20 opensearch-dashboards[71073]: [agentkeepalive:deprecated] options.freeSocketKeepAliveTimeout is deprecated, please use options.freeSocketTimeout instead
Aug 12 11:04:10 ubuntu20 opensearch-dashboards[71073]: /usr/share/opensearch-dashboards/node_modules/rxjs/internal/util/hostReportError.js:4
Aug 12 11:04:10 ubuntu20 opensearch-dashboards[71073]:     setTimeout(function () { throw err; }, 0);
Aug 12 11:04:10 ubuntu20 opensearch-dashboards[71073]:                              ^
Aug 12 11:04:10 ubuntu20 opensearch-dashboards[71073]: [Error [ObjectUnsubscribedError]: object unsubscribed]
Aug 12 11:04:10 ubuntu20 opensearch-dashboards[71073]: Node.js v18.19.0
Aug 12 11:04:10 ubuntu20 systemd[1]: opensearch-dashboards.service: Main process exited, code=exited, status=1/FAILURE
Aug 12 11:04:10 ubuntu20 systemd[1]: opensearch-dashboards.service: Failed with result 'exit-code'.
Aug 12 11:04:10 ubuntu20 systemd[1]: Stopped "OpenSearch Dashboards".

This is the behavior of the upstream opensearch. We will implement a workaround in the test.


[DO NOT MERGE] Trying to understand bug #1203

Trying to work out what is happening in issue #1203

@nonhermitian this passes on mine so I'm not sure what you are seeing. Lets see if it passes here.

This now passes so closing.


Prevent misfiring dblclick events on touch devices

Fixes #7422
Existing code assumes that touchend events can only occur after touchstart events. This assumption is flawed because touchstart event can be cancelled or propagation stopped. This PR removes this assumption.
Additional context:
DoubleTap handler listens for touchstart events and uses a timer to determine if two touchstart events occur within a specified delta. If they happen within a delta, a doubleTap flag is set to true. On a touchend event, if the doubleTap flag is set to true a dblclick event is dispatched and the timer is reset, HOWEVER, the doubleTap flag remains true until another touchstart event occurs.
The assumption here is that there CANNOT be a touchend event that's not preceded with be a touchstart.
Unfortunately, if an element has stopClickPropagation enabled, the element no longer propagates mousedown touchstart dblclick but will still propagate touchend to the map.
The other way to fix this is to modify stopClickPropagation to prevent all mousedown touchstart touchend dblclick events from propagating but I think this approach is safer.

Nice catch!

The other way to fix this is to modify stopClickPropagation to prevent all mousedown touchstart touchend dblclick events from propagating but I think this approach is safer.

I suppose opposite - safer prevent touched (as well as touchmove and touchcancel).
Or (considering other possible sideeffects) maybe that part of code needs full revision.
As for dblckick you may try #7027.

Nice catch!

The other way to fix this is to modify stopClickPropagation to prevent all mousedown touchstart touchend dblclick events from propagating but I think this approach is safer.

I suppose opposite - safer prevent touched (as well as touchmove and touchcancel).
Or (considering other possible sideeffects) maybe that part of code needs full revision.
As for dblckick you may try #7027.

I suppose opposite - safer prevent touched (as well as touchmove and touchcancel).
Or (considering other possible sideeffects) maybe that part of code needs full revision.

I worry there may be unintended side effects where you start a touch on the map and drag your finger into an area with disableClickPropagation enabled.

I suppose opposite - safer prevent touched (as well as touchmove and touchcancel).
Or (considering other possible sideeffects) maybe that part of code needs full revision.

I worry there may be unintended side effects where you start a touch on the map and drag your finger into an area with disableClickPropagation enabled.

@johnd0e is this obsolete with #7027?

I close this because the linked issue is fixed


Small Mistake in Mamba2 - Eq (9)

First of all, great work!
I think I found a small mistake in equation 9 (section 4.1.1) of the recent Mamba 2 paper:

The last projection should be
𝑌 = 𝑀𝑉 (T, P)
instead of
𝑌 = 𝐺𝑉 (T, P).

you're right, thanks for the catch! will be updated in next version


Add support for Oracle / Scientific Linux 6.X

https://travis-ci.org/chef-cookbooks/etcd/builds/105838151
+1 shipit
On Sat, Jan 30, 2016 at 1:25 AM, Tim Smith<EMAIL_ADDRESS>wrote:

Assigned #58 https://github.com/chef-cookbooks/etcd/pull/58 to @someara
https://github.com/someara.
—
Reply to this email directly or view it on GitHub
https://github.com/chef-cookbooks/etcd/pull/58#event-532263467.


Update iot-hub-gateway-sdk-physical-device.md

Hi, in the sample of yours, it uses HTTP.

Hi @eissi, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@eissi : Thanks for your contribution to the Azure documentation! The author, @chipalost, has been notified to review your proposed change.

#sign-off
Hi @eissi, thanks for the update. Well spotted!

Only the author of the article can use the sign off comment to add the ready-to-merge label.


Still not available on hacs

Last update should have solved the issue of not showing the integration on hacs. However, searching for "_Resol_Controller" or any part of that does not show the expected  result in the list. Only the older variant of  dm82m/hass-Deltasol-KM2 is listed.
Expected behavior
I expected the integration to be listed in HACS when searching for resol

Hi Felix,
Thanks I am aware of it and flagged it here.
I am very new to this and don't understand what is going on.
Have you got a. better understanding?
Thanks for your help.
Martin

On another note, you can install it as a custom repo by just copying the link. Its just not that great as I did publish it to HACS.

On another note, you can install it as a custom repo by just copying the link. Its just not that great as I did publish it to HACS.

Thanks for the tip. It is working now! Great functionality what you made; just what I was looking for!
I am new on HA and github, so in the first phase of trying to get understanding of all. So, I am the wrong person to ask for help on this one...
Thanks, Felix.

Thanks Felix, happy you like it. First time for me to program in Python and do something on HACS, Github etc. as well.

Hello,
I have the same issue as Felix-Jan. I can't find it in HACS.  I checked this link
https://github.com/hacs/default/pull/2179#pullrequestreview-1887308073
Sry, how can I install it?
Thanks

Hello, I have the same issue as Felix-Jan. I can't find it in HACS. I checked this link hacs/default#2179 (review) Sry, how can I install it? Thanks

Sorry about this. I been out of action for a while, will try to re-submit to HACS.
You can manually install by referencing this repository: https://github.com/evercape/hass-resol-KM2
If you want to try and add a custom repository to HACS do the following:
Go to any of the sections (integrations, frontend, automation).
Click on the 3 dots in the top right corner.
Select "Custom repositories"
Add the URL to the repository.
Select the correct category.
Click the "ADD" button.

Hello,
I try, but there is written.. see pic below

Thanks, works. Thanks for these tool!

Great to know it's working. I really struggle with HACS and once I am back mid July from holidays will look into this again.

Finally its available in HACS - you need to search for RESOL CONTROLLER


Fix the daily run of freshclam

Isn't there a restriction on running processes at root in CP?

@steverendell has a much better fix


Simplify setup without a Connected App, Auth. Provider, and Named Credential

Current version of the app requires the admin to setup a Connected App, Auth. Provider, and Named Credential for the actions to use the REST API. Prior to Winter '19, this was a limitation of Lightning components having a limited-api session id and asynchronous (batch jobs) having no-api session id.
Winter '19 allows asynchronous apex session ids to call out to the Salesforce API for orgs with My Domain enabled.
My REST API Lightning component removes need for components to require Named Credentials to call out to the Salesforce API too.
This feature request will upgrade the app so that no Named Credentials are necessary, greatly simplifying the setup process.

Fixed in develop branch for future release.


Implement Deref{Mut} for AllowStdIo.

This PR adds Deref{Mut} which internally just call get_{ref|mut}, which will stay, as to not break compatibility.

The clippy lint as well as the rustdoc crash appear to be unrelated to this PR, does anyone know why they are happening. I tested it against the latest nightly version of clippy and rustdoc and both succeed with out warnings.

The bug causing the CI failure was patched in the latest release of rustdoc.

I think this could cause breakage if a different method with the same name as a method in std::io traits is added to futures::io traits.

Closing this due to the above concern.
Thanks anyway for the PR!


Bug - Content Carousel fading effect

How to reproduce

Go to https://develop--vg-volvotrucks-us-rd--netcentric.hlx.page/
Scroll to the content carousel
Go to the mobile and/or tablet viewport

Expected result
There is a fading effect.

Actual result
There is no fading effect.

Dependent on ticket #297 to avoid code issues, will be unblocked once the mentioned ticket is done.

confirmed as fixed
as it complies with the design here https://www.figma.com/file/4PrFQO93oPaF721aT3meXj/VNL-Digital-Reveal?type=design&node-id=4929-64357&mode=dev
and as tested on: https://297-content-carousel--vg-volvotrucks-us-rd--netcentric.hlx.page/block-library/blocks/v2-content-carousel


Jvenstad/deblock system app order across parallel zones

@freva please review since @mpolden is away.

Mostly because of the part that will be removed again when hosts are upgraded, though :p

Ok, I think that's better, though, since it doesn't hide the actual logic. It's just one word longer, too.


Replace AdventureWorks with AdventureWorksLT

"We'll use the AdventureWorks database in this lab, so let's start by exploring it in Azure Data Studio."
I know it's a little thing, but this is bugging me. We are not using the AdventureWorks database; we are using the AdventureWorksLT database.

It's the LT schema, but the database is called adventureworks.


Mapping the Slack installation Object to the specific user in my DB.

Description
Hello, for sending out notifications via my Slack App(bot), I am trying to add the Slack Installation object, which is given when a user installs my App in his or her Slack workspace, to my user DB. In order for me to send notification messages regarding activities on my website to only the users that have installed/integrated my Slack App, I believe I need to map the Slack installation object with the user who has installed the app during the installation phase.
I understand that I can just save the Slack Installation objects onto my DB but unfortunately, this won't do anything since my service won't know which one of my users is installing or has installed my Slack App for the integration.
So when installing my App (Slack Bot), a user clicks Connect Slack Channel  on my website.  and then gets directed to the request URL, which is https://myAppDomain.com/slack/install.
My question is that is it possible for me to pass any parameters such as userId from my DB to the request URL /slack/install ,  so that  I can map the Slack installation object with the specific user in my DB?
For example, like the Notion's slack integration, when I press the integration button, it opens up a new page looking like the below image

And if I press Allow button to install the app, then it is probably (my guess) now mapping the Slack installation object that contains my Slack userId and incomingWebHook.URL and etc., into Notion DB.
but I'm so puzzled as to how I am supposed to know which one of my users is installing the app when I am just saving the Slack installation object that is given to me. Are there any ways to map or connect the Slack installation object with the specific user(the user who is installing my Slack App) in my DB?
I've been contemplating for days but the only idea I came up with is passing parameters to /slack/install URL to grab then use the parameters grabbed from the URL when saving the Slack installation object into my DB.
If my question is unclear, please let me know so that I can elaborate differently.
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[ x ] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[ x ] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[ x ] I've read and agree to the Code of Conduct.
[ x ] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version:
node version:
OS version(s):
Steps to reproduce:

Expected result:
What you expected to happen
Actual result:
What actually happened
Attachments:
Logs, screenshots, screencast, sample project, funny gif, etc.

Hi @esphoenixc, thanks for asking the question!

My question is that is it possible for me to pass any parameters such as userId from my DB to the request URL /slack/install , so that I can map the Slack installation object with the specific user in my DB?

Yes, it is possible. You can use the following callback functions:

installPathOptions.beforeRedirection: This function sets a browser cookie value to relay your service's user ID
callbackOptions.afterInstallation: This function extracts the user ID from the cookie value and then attaches the value to the installation object that will be stored by storeInstallation method.

Please refer to the following resources for more details.
Documents:

https://slack.dev/bolt-js/concepts#authenticating-oauth
https://slack.dev/node-slack-sdk/oauth#persisting-data-during-the-oauth-flow

The interface details:

https://github.com/slackapi/bolt-js/blob/%40slack/bolt%403.12.1/src/receivers/HTTPReceiver.ts#L106-L107
https://github.com/slackapi/node-slack-sdk/blob/%40slack/oauth%402.5.4/packages/oauth/src/install-path-options.ts
https://github.com/slackapi/node-slack-sdk/blob/%40slack/oauth%402.5.4/packages/oauth/src/callback-options.ts

Similar questions:

https://github.com/slackapi/bolt-js/issues/1497
https://github.com/slackapi/bolt-js/issues/1211

I hope this helps.

Hi, thank you again for your reply, It has helped me greatly. As you suggested, I am using two callback functions :
installPathOptions.beforeRedirection callbackOptions.afterInstallation to achieve mapping my service user Id with the Slack installation object.
However, I was unable to do use installPathOptions.beforeRedirection to set a browser cookie as the value that is related to my service's user ID.
 installPathOptions: {
      beforeRedirection: async (req, res, installURLOptions) => {
        req.setHeaders('Cookie', 'myServiceUserID')
        return true;
      },
    },

This is how I tried to set a browser cookie value to relay my service's user Id (referred to this document : https://slack.dev/node-slack-sdk/oauth#persisting-data-during-the-oauth-flow )

it's giving me req.setHeaders is not a function error.  so I was unable to pass my service user Id through the headers.
Is there something I am missing?

it's giving me req.setHeaders is not a function error. so I was unable to pass my service user Id through the headers.
Is there something I am missing?

This error message indicates that your code may be trying to call "setHeaders" (plural form of header) method. However. the correct name should be "setHeader" (singular form of header).

it's giving me req.setHeaders is not a function error. so I was unable to pass my service user Id through the headers.
Is there something I am missing?

This error message indicates that your code may be trying to call "setHeaders" (plural form of header) method. However. the correct name should be "setHeader" (singular form of header).

I am so sorry that was a wrong example code I put. I did correctly put req.setHeader() in my code and still giving me the same error

I found that the document is wrong. It needs to be res.setHeader instead. Sorry for the confusion here. I will update the documents later on.

Thank you for your reply, after reading the references that you've provided, I am now successfully able to set a cookie (my mock service user id) from beforeRedirection to afterInstallation.
However, like I just mentioned above, that was a mock data I just wrote, a string value just to test out setting a cookie value and passing it down and mapping it with the Slack installation object.
So, I know how to set a cookie value and also know how to successfully pass the cookie from beforeRedirection to afterInstallation. However, I just can't figure out a way to get my service user id in the first place. In order for me to set a cookie value that is my service user id, I need to have my service user from my service beforehand.
So, what I've tried is that I created an API gateway for my Slack App, which is on AWS lambda. Through the API gateway, I pass my service user id by requesting post method with the parameter of my service user id. However, this attempt was unsuccessful as it is giving out an error of  "Unable to determine event source based on event.",
I believe that error is not the boltjs error. That error is most likely caused from when my API gateway is trying to invoke my Slack App
I am still puzzled as to how I can get my service user id from my service to my Slack App. and I can't seem to find a solid way to solve this problem.
How do I get my service user id from my service, a website, in the first place to my Slack App, deployed on AWS lambda?

The most straight-forward and secure way to connect your Slack OAuth flow and your service account would be to have an authentication of your service in the same domain as a requirement for starting the Slack OAuth flow. Once your end-user logged into your service through OAuth 2 / OpenID Connect, or whatever your service supports, your Slack OAuth flow can know which service the installing user is going to connect by checking the login user and service associated to your service's login session.
Regardless of details of OAuth/OpenID Connect flow implementations, it is a common (and the best) approach to initiate several OAuth flow including the Slack one in the same browser session for linking external services and Slack.
I cannot help you out for designing the details of your service. I hope you will figure out the reasonable way for your service!

Thank you! This is the last step for my app I believe haha. I am really grateful for your help @seratch You've been tremendously helpful!!!!!!!!!!! 😁👍🙏🙇♂

Thank you for your reply, after reading the references that you've provided, I am now successfully able to set a cookie (my mock service user id) from beforeRedirection to afterInstallation.

Hey, could you please tell me how did you retrieved the id from the cookie in 'afterInstallation'?


Trying to Connect Collabora/code to this container

When I publish a port besides 80 and 443 in this container, it doesn't make any attempt to proxy that new port.  I checked the file created and it only made rules for port 80 and 443  In my case, I tried to publish port 9980 for a Collabora/Code container.   The certificate creation appears to work correctly but the reverse proxy only sets itself up on port 80/443.

As you describe it, this issue seems related to pini-gh/nginx-proxy, and not to pini-gh/docker-letsencrypt-nginx-proxy-companion. Is that correct?
And please post your redacted docker-compose.yml file so I could understand what you're trying to do.

I realized I posted this on the wrong repository and put my response here.
https://github.com/pini-gh/nginx-proxy/issues/1

I realized I posted this on the wrong repository and put my response here.
pini-gh/nginx-proxy#1

Closing this one then.


Dot key + filter

Hello, i'm using JsonPath + SPEL
Considering this json :
{
    "item.thing": [
        {"key" : "nomatch", "value" : "a"},{"key" : "match", "value" : "b"},{"key" : "nomatch", "value" : "c"}
    ]
}

i'm trying to reach item.thing and filter the array like this :
{item.thing[?(@.key=="match")].value}.get(0)=='b'"
it's doesn't works because "item" key is missing from my json (seems fair)
so i tried to escape the key :
{"item.thing"[?(@.key=="match")].value}.get(0)=='b'"
but doesn't seems to work neither apparently due to the filter function
not sure how to find correct syntax neither if it's even possible with filter function
it's working when i don't have a key with a dot, e.g :
{item[?(@.key=="match")].value}.get(0)=='b'"
any suggestion ?

The problem arises because dots are typically used as delimiters in JSONPath expressions, so having a key with a dot in it can lead to unexpected behavior.
In this case, since your key is "item.thing," it is being interpreted as a nested structure. You've tried escaping the dot with quotes, but it seems that the filter function is causing complications.
One way to approach this is to use the bracket notation to access the property. Here's an example that might work for your case:
json
['item.thing'][?(@.key=="match")].value
This way, you are treating "item.thing" as a single key rather than a nested structure. The bracket notation can help in cases where the key contains special characters like dots.

Your expression might look like this:
json
['item.thing'][?(@.key=="match")].value.get(0)=='b'
This assumes that the JSONPath library you are using supports the bracket notation for keys.
If this doesn't work, you might need to refer to the documentation or specific implementation details of the JSONPath library you are using to see if there are any special considerations or syntax for handling keys with dots. If the library supports escaping characters in keys, check for the correct syntax according to its documentation.


Container crashes upon start

Describe the Bug
The container crashes approximately a minute after start. The game appears to download but upon starting the server the container crashes
Your Runtime Command or Docker Compose File
docker create --name='Satisfactory-Server' --net='bridge' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'MAXPLAYERS'='16' -e 'STEAMBETA'='true' -p '7777:7777/udp' -p '15000:15000/udp' -p '15777:15777/udp' -v '/mnt/user/appdata/Satisfactory':'/config':'rw' --hostname 'satisfactory-server' 'wolveix/satisfactory-server'

System Specs (please complete the following information):

OS: Unraid 6.9.2
Dell R710 2x Xeon x5660
12GB ecc ddr3

Additional Context
This issue occurred upon updating the container to the latest version. Last night the server was working fine and I was able to connect to the server

Please provide the full log. I'm unable to help you without it.

Gathering the logs now: Forgot to attach them on my original post

Here's the logs
ErrorWarningSystemArrayLogin

Setting max players to 16
Experimental flag is set. Experimental will be downloaded instead of Early Access.
Checking available space...7488GB detected
Downloading the latest version of the game...

Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
[ 0%] Checking for available updates...
[----] Downloading update (112 of 54,186 KB)...
[ 0%] Downloading update (1,527 of 54,186 KB)...
[ 2%] Downloading update (2,727 of 54,186 KB)...
[ 5%] Downloading update (4,432 of 54,186 KB)...
[ 8%] Downloading update (5,198 of 54,186 KB)...
[ 9%] Downloading update (6,265 of 54,186 KB)...
[ 11%] Downloading update (7,678 of 54,186 KB)...
[ 14%] Downloading update (8,914 of 54,186 KB)...
[ 16%] Downloading update (10,392 of 54,186 KB)...
[ 19%] Downloading update (12,039 of 54,186 KB)...
[ 22%] Downloading update (13,490 of 54,186 KB)...
[ 24%] Downloading update (14,848 of 54,186 KB)...
[ 27%] Downloading update (16,318 of 54,186 KB)...
[ 30%] Downloading update (17,848 of 54,186 KB)...
[ 32%] Downloading update (19,378 of 54,186 KB)...
[ 35%] Downloading update (20,807 of 54,186 KB)...
[ 38%] Downloading update (22,362 of 54,186 KB)...
[ 41%] Downloading update (23,855 of 54,186 KB)...
[ 44%] Downloading update (25,280 of 54,186 KB)...
[ 46%] Downloading update (26,836 of 54,186 KB)...
[ 49%] Downloading update (28,060 of 54,186 KB)...
[ 51%] Downloading update (29,307 of 54,186 KB)...
[ 54%] Downloading update (30,950 of 54,186 KB)...
[ 57%] Downloading update (32,142 of 54,186 KB)...
[ 59%] Downloading update (32,869 of 54,186 KB)...
[ 60%] Downloading update (33,712 of 54,186 KB)...
[ 62%] Downloading update (34,509 of 54,186 KB)...
[ 63%] Downloading update (35,301 of 54,186 KB)...
[ 65%] Downloading update (35,772 of 54,186 KB)...
[ 66%] Downloading update (36,403 of 54,186 KB)...
[ 67%] Downloading update (37,105 of 54,186 KB)...
[ 68%] Downloading update (37,921 of 54,186 KB)...
[ 69%] Downloading update (38,677 of 54,186 KB)...
[ 71%] Downloading update (39,321 of 54,186 KB)...
[ 72%] Downloading update (39,856 of 54,186 KB)...
[ 73%] Downloading update (40,614 of 54,186 KB)...
[ 74%] Downloading update (41,389 of 54,186 KB)...
[ 76%] Downloading update (41,770 of 54,186 KB)...
[ 77%] Downloading update (42,506 of 54,186 KB)...
[ 78%] Downloading update (42,888 of 54,186 KB)...
[ 79%] Downloading update (43,569 of 54,186 KB)...
[ 80%] Downloading update (44,334 of 54,186 KB)...
[ 81%] Downloading update (44,906 of 54,186 KB)...
[ 82%] Downloading update (45,292 of 54,186 KB)...
[ 83%] Downloading update (45,571 of 54,186 KB)...
[ 84%] Downloading update (45,651 of 54,186 KB)...
[ 84%] Downloading update (46,366 of 54,186 KB)...
[ 85%] Downloading update (46,976 of 54,186 KB)...
[ 86%] Downloading update (47,498 of 54,186 KB)...
[ 87%] Downloading update (47,686 of 54,186 KB)...
[ 88%] Downloading update (47,849 of 54,186 KB)...
[ 88%] Downloading update (48,540 of 54,186 KB)...
[ 89%] Downloading update (49,199 of 54,186 KB)...
[ 90%] Downloading update (49,770 of 54,186 KB)...
[ 91%] Downloading update (50,474 of 54,186 KB)...
[ 93%] Downloading update (51,218 of 54,186 KB)...
[ 94%] Downloading update (51,897 of 54,186 KB)...
[ 95%] Downloading update (52,587 of 54,186 KB)...
[ 97%] Downloading update (53,376 of 54,186 KB)...
[ 98%] Downloading update (54,186 of 54,186 KB)...
[100%] Downloading update (54,186 of 54,186 KB)...
[100%] Download complete.
[----] Installing update...
[----] Extracting package...
[----] Extracting package...
[----] Extracting package...
[----] Extracting package...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Cleaning up...
[----] Update complete, launching Steamcmd...
Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
[ 0%] Checking for available updates...
[----] Verifying installation...
[ 0%] Downloading update...
[ 0%] Checking for available updates...
[----] Download complete.
[----] Extracting package...
[----] Extracting package...
[----] Extracting package...
[----] Extracting package...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Cleaning up...
[----] Update complete, launching Steamcmd...
Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
Update state (0x5) verifying install, progress: 2.96 (133295201 /<PHONE_NUMBER>)
Update state (0x5) verifying install, progress: 7.92 (357073360 /<PHONE_NUMBER>)
Update state (0x5) verifying install, progress: 15.29 (689270576 /<PHONE_NUMBER>)
Update state (0x5) verifying install, progress: 24.73<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x5) verifying install, progress: 31.93<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x5) verifying install, progress: 35.53<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x5) verifying install, progress: 42.78<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x5) verifying install, progress: 49.49<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x5) verifying install, progress: 56.95<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x5) verifying install, progress: 66.70<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x5) verifying install, progress: 76.45<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x5) verifying install, progress: 84.98<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x5) verifying install, progress: 92.05<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x5) verifying install, progress: 97.89<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x1) running, progress: 0.00 (0 / 0)
Update state (0x81) verifying update, progress: 7.14 (321744695 /<PHONE_NUMBER>)
Update state (0x81) verifying update, progress: 16.34 (736397446 /<PHONE_NUMBER>)
Update state (0x81) verifying update, progress: 25.85<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x81) verifying update, progress: 34.55<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x81) verifying update, progress: 42.83<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x81) verifying update, progress: 51.21<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x81) verifying update, progress: 60.51<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x81) verifying update, progress: 70.23<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x81) verifying update, progress: 79.95<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x81) verifying update, progress: 88.77<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x81) verifying update, progress: 97.16<PHONE_NUMBER> /<PHONE_NUMBER>)
Update state (0x101) committing, progress: 49.07<PHONE_NUMBER> /<PHONE_NUMBER>)
Success! App '1690800' fully installed.
Project file not found: /config/gamefiles/FactoryGame/FactoryGame.uproject
sh: 1: xdg-user-dir: not found
4.26.1-170636+++FactoryGame+main 522 3
Disabling core dumps.
LogInit: Display: Running engine for game: FactoryGame
LogInit: Display: Project file not found: /config/gamefiles/FactoryGame/FactoryGame.uproject
LogInit: Display: Attempting to find via project info helper.
LogUProjectInfo: Found projects:
LogPakFile: Display: Found Pak file ../../../FactoryGame/Content/Paks/FactoryGame-LinuxServer.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../FactoryGame/Content/Paks/FactoryGame-LinuxServer.pak.
LogPakFile: PakFile PrimaryIndexSize=586698
LogPakFile: PakFile PathHashIndexSize=670088
LogPakFile: PakFile FullDirectoryIndexSize=1859590
LogPakFile: OnPakFileMounted2Time == 0.000001
LogPlatformFile: Using cached read wrapper
LogTaskGraph: Started task graph with 4 named threads and 8 total threads with 1 sets of task threads.
LogICUInternationalization: ICU TimeZone Detection - Raw Offset: -6:00, Platform Override: ''
LogPluginManager: Mounting plugin ReplicationGraph
LogPluginManager: Mounting plugin DTLSHandlerComponent
LogPluginManager: Mounting plugin Wwise
LogPluginManager: Mounting plugin GeometryMode
LogPluginManager: Mounting plugin ApexDestruction
LogPluginManager: Mounting plugin BlueprintStats
LogPluginManager: Mounting plugin OnlineFramework
LogPluginManager: Mounting plugin OnlineSubsystem
LogPluginManager: Mounting plugin OnlineSubsystemUtils
LogPluginManager: Mounting plugin LensDistortion
LogPluginManager: Mounting plugin WindowsDeviceProfileSelector
LogPluginManager: Mounting plugin SteamController
LogPluginManager: Mounting plugin SteamShared
LogPluginManager: Mounting plugin RawInput
LogPluginManager: Mounting plugin MfMedia
LogPluginManager: Mounting plugin OnlineSubsystemSteam
LogPluginManager: Mounting plugin OnlineSubsystemEOS
LogPluginManager: Mounting plugin SignificanceManager
LogPluginManager: Mounting plugin PythonScriptPlugin
LogPluginManager: Mounting plugin EditorScriptingUtilities
LogPluginManager: Mounting plugin EditorTests
LogPluginManager: Mounting plugin FbxAutomationTestBuilder
LogPluginManager: Mounting plugin FunctionalTestingEditor
LogPluginManager: Mounting plugin RuntimeTests
LogPluginManager: Mounting plugin ScreenshotTools
LogPluginManager: Mounting plugin CSSEditorToolsExtension
LogPluginManager: Mounting plugin Paper2D
LogPluginManager: Mounting plugin AISupport
LogPluginManager: Mounting plugin EnvironmentQueryEditor
LogPluginManager: Mounting plugin LightPropagationVolume
LogPluginManager: Mounting plugin AnimationSharing
LogPluginManager: Mounting plugin PluginUtils
LogPluginManager: Mounting plugin PropertyAccessEditor
LogPluginManager: Mounting plugin UObjectPlugin
LogPluginManager: Mounting plugin AssetManagerEditor
LogPluginManager: Mounting plugin FacialAnimation
LogPluginManager: Mounting plugin SpeedTreeImporter
LogPluginManager: Mounting plugin DatasmithContent
LogPluginManager: Mounting plugin VariantManagerContent
LogPluginManager: Mounting plugin AlembicImporter
LogPluginManager: Mounting plugin GeometryCache
LogPluginManager: Mounting plugin AutomationUtils
LogPluginManager: Mounting plugin BackChannel
LogPluginManager: Mounting plugin ChaosClothEditor
LogPluginManager: Mounting plugin ChaosCloth
LogPluginManager: Mounting plugin ChaosEditor
LogPluginManager: Mounting plugin PlanarCut
LogPluginManager: Mounting plugin GeometryProcessing
LogPluginManager: Mounting plugin EditableMesh
LogPluginManager: Mounting plugin GeometryCollectionPlugin
LogPluginManager: Mounting plugin ProceduralMeshComponent
LogPluginManager: Mounting plugin ChaosSolverPlugin
LogPluginManager: Mounting plugin ChaosNiagara
LogPluginManager: Mounting plugin Niagara
LogPluginManager: Mounting plugin CharacterAI
LogPluginManager: Mounting plugin MotoSynth
LogPluginManager: Mounting plugin PlatformCrypto
LogPluginManager: Mounting plugin ImgMedia
LogPluginManager: Mounting plugin MediaCompositing
LogPluginManager: Mounting plugin MeshPainting
LogPluginManager: Mounting plugin TcpMessaging
LogPluginManager: Mounting plugin UdpMessaging
LogPluginManager: Mounting plugin ActorSequence
LogPluginManager: Mounting plugin LevelSequenceEditor
LogPluginManager: Mounting plugin MatineeToLevelSequence
LogPluginManager: Mounting plugin TemplateSequence
LogPluginManager: Mounting plugin OnlineSubsystemNull
LogPluginManager: Mounting plugin LauncherChunkInstaller
LogPluginManager: Mounting plugin ActorLayerUtilities
LogPluginManager: Mounting plugin AppleImageUtils
LogPluginManager: Mounting plugin AssetTags
LogPluginManager: Mounting plugin AudioCapture
LogPluginManager: Mounting plugin CableComponent
LogPluginManager: Mounting plugin ChunkDownloader
LogPluginManager: Mounting plugin CustomMeshComponent
LogPluginManager: Mounting plugin ExampleDeviceProfileSelector
LogPluginManager: Mounting plugin GooglePAD
LogPluginManager: Mounting plugin LinuxDeviceProfileSelector
LogPluginManager: Mounting plugin PhysXVehicles
LogPluginManager: Mounting plugin RuntimePhysXCooking
LogPluginManager: Mounting plugin SoundFields
LogPluginManager: Mounting plugin Synthesis
LogPluginManager: Mounting plugin AudioSynesthesia
LogInit: Using libcurl 7.65.3-DEV
LogInit: - built for x86_64-unknown-linux-gnu
LogInit: - supports SSL with OpenSSL/1.1.1c
LogInit: - supports HTTP deflate (compression) using libz 1.2.8
LogInit: - other features:
LogInit: CURL_VERSION_SSL
LogInit: CURL_VERSION_LIBZ
LogInit: CURL_VERSION_IPV6
LogInit: CURL_VERSION_ASYNCHDNS
LogInit: CURL_VERSION_LARGEFILE
LogInit: CURL_VERSION_TLSAUTH_SRP
LogInit: CurlRequestOptions (configurable via config and command line):
LogInit: - bVerifyPeer = true - Libcurl will verify peer certificate
LogInit: - bUseHttpProxy = false - Libcurl will NOT use HTTP proxy
LogInit: - bDontReuseConnections = false - Libcurl will reuse connections
LogInit: - MaxHostConnections = 16 - Libcurl will limit the number of connections to a host
LogInit: - LocalHostAddr = Default
LogInit: - BufferSize = 65536
Shutdown handler: initalize.
LogOnline: OSS: Creating online subsystem instance for: EOS
LogOnline: OSS: FOnlineSubsystemEOS: Init success.
LogSteamShared: Display: Loading Steam SDK 1.47
LogCore: Warning: dlopen failed: /config/gamefiles/Engine/Binaries/Linux/libsteam_api.so: cannot open shared object file: No such file or directory

LogSteamShared: Warning: Could not find system one, loading bundled libsteam_api.so.

LogSteamShared: Display: Loaded libsteam_api.so at 0x449db0
LogSteamShared: Steam SDK Loaded!
LogOnline: OSS: Creating online subsystem instance for: STEAM
LogOnline: Warning: STEAM: Steam API failed to initialize!

LogOnline: Display: STEAM: OnlineSubsystemSteam::Shutdown()
LogOnline: OSS: Unable to create OnlineSubsystem module STEAM
LogOnline: OSS: TryLoadSubsystemAndSetDefault: Loaded subsystem for module [EOS]
LogOnline: OSS: Creating online subsystem instance for: STEAM
LogOnline: Warning: STEAM: Steam API failed to initialize!

LogOnline: Display: STEAM: OnlineSubsystemSteam::Shutdown()
LogInit: Build: ++FactoryGame+main-CL-170636
LogInit: Engine Version: 4.26.1-170636+++FactoryGame+main

LogInit: Compatible Engine Version: 4.26.1-170636+++FactoryGame+main

LogInit: Net CL: 170636
LogInit: OS: GenericOSVersionLabel (GenericOSSubVersionLabel), CPU: Intel(R) Xeon(R) CPU X5660 @ 2.80GHz, GPU: GenericGPUBrand

LogInit: Compiled (64-bit): Oct 18 2021 21:21:12
LogInit: Compiled with Clang: 10.0.1 (https://github.com/llvm/llvm-project ef32c611aa214dea855364efd7ba451ec5ec3f74)
LogInit: Build Configuration: Shipping
LogInit: Branch Name: ++FactoryGame+main
LogInit: Command Line: -log -NoSteamClient -unattended
LogInit: Base Directory: /config/gamefiles/Engine/Binaries/Linux/
LogInit: Allocator: binned2
LogInit: Installed Engine Build: 0
LogInit: Launcher File: /config/gamefiles/launcher_id
LogInit: Launcher ID:
LogInit: Launcher Artifact:
LogInit: Presizing for max 2097152 objects, including 1 objects not considered by GC, pre-allocating 0 bytes for permanent pool.
LogStreaming: Display: Async Loading initialized: Event Driven Loader: true, Async Loading Thread: false, Async Post Load: false
LogInit: Object subsystem initialized
[2021.10.30-16.22.38:327][ 0]LogLinux: Selected Device Profile: [LinuxServer]
[2021.10.30-16.22.38:327][ 0]LogInit: Applying CVar settings loaded from the selected device profile: [LinuxServer]
[2021.10.30-16.22.38:328][ 0]LogHAL: Display: Platform has ~ 4 GB [12578684928 /<PHONE_NUMBER> / 12], which maps to Smallest [LargestMinGB=32, LargerMinGB=12, DefaultMinGB=8, SmallerMinGB=6, SmallestMinGB=0)
[2021.10.30-16.22.38:328][ 0]LogInit: Going up to parent DeviceProfile [Linux]
[2021.10.30-16.22.38:328][ 0]LogInit: Going up to parent DeviceProfile []
[2021.10.30-16.22.38:328][ 0]LogInit: Unix hardware info:
[2021.10.30-16.22.38:328][ 0]LogInit: - we are the first instance of this executable
[2021.10.30-16.22.38:328][ 0]LogInit: - this process' id (pid) is 89, parent process' id (ppid) is 25
[2021.10.30-16.22.38:328][ 0]LogInit: - we are not running under debugger
[2021.10.30-16.22.38:328][ 0]LogInit: - machine network name is 'satisfactory-server'
[2021.10.30-16.22.38:328][ 0]LogInit: - user name is 'steam' (steam)
[2021.10.30-16.22.38:328][ 0]LogInit: - we're logged in locally
[2021.10.30-16.22.38:328][ 0]LogInit: - we're running without rendering
[2021.10.30-16.22.38:328][ 0]LogInit: - CPU: GenuineIntel 'Intel(R) Xeon(R) CPU X5660 @ 2.80GHz' (signature: 0x206C2)
[2021.10.30-16.22.38:328][ 0]LogInit: - Number of physical cores available for the process: 24
[2021.10.30-16.22.38:328][ 0]LogInit: - Number of logical cores available for the process: 24
[2021.10.30-16.22.38:328][ 0]LogInit: - Cache line size: 64
[2021.10.30-16.22.38:328][ 0]LogInit: - Memory allocator used: binned2
[2021.10.30-16.22.38:328][ 0]LogInit: - This binary is optimized with LTO: no, PGO: no, instrumented for PGO data collection: no
[2021.10.30-16.22.38:328][ 0]LogInit: - This is a licensee build.
[2021.10.30-16.22.38:328][ 0]LogCore: Benchmarking clocks:
[2021.10.30-16.22.38:328][ 0]LogCore: - CLOCK_MONOTONIC (id=1) can sustain 43653899 (43654K, 44M) calls per second without zero deltas.
[2021.10.30-16.22.38:328][ 0]LogCore: - CLOCK_MONOTONIC_RAW (id=4) can sustain 43001088 (43001K, 43M) calls per second without zero deltas.
[2021.10.30-16.22.38:328][ 0]LogCore: - CLOCK_MONOTONIC_COARSE (id=6) can sustain 98807615 (98808K, 99M) calls per second with 99.998978% zero deltas.
[2021.10.30-16.22.38:328][ 0]LogCore: Selected clock_id 1 (CLOCK_MONOTONIC) since it is the fastest support clock without zero deltas.
[2021.10.30-16.22.38:328][ 0]LogInit: Unix-specific commandline switches:
[2021.10.30-16.22.38:328][ 0]LogInit: -ansimalloc - use malloc()/free() from libc (useful for tools like valgrind and electric fence)
[2021.10.30-16.22.38:328][ 0]LogInit: -jemalloc - use jemalloc for all memory allocation
[2021.10.30-16.22.38:328][ 0]LogInit: -binnedmalloc - use binned malloc for all memory allocation
[2021.10.30-16.22.38:328][ 0]LogInit: -filemapcachesize=NUMBER - set the size for case-sensitive file mapping cache
[2021.10.30-16.22.38:328][ 0]LogInit: -useksm - uses kernel same-page mapping (KSM) for mapped memory (OFF)
[2021.10.30-16.22.38:328][ 0]LogInit: -ksmmergeall - marks all mmap'd memory pages suitable for KSM (OFF)
[2021.10.30-16.22.38:328][ 0]LogInit: -preloadmodulesymbols - Loads the main module symbols file into memory (OFF)
[2021.10.30-16.22.38:328][ 0]LogInit: -sigdfl=SIGNAL - Allows a specific signal to be set to its default handler rather then ignoring the signal
[2021.10.30-16.22.38:328][ 0]LogInit: -httpproxy=ADDRESS:PORT - redirects HTTP requests to a proxy (only supported if compiled with libcurl)
[2021.10.30-16.22.38:328][ 0]LogInit: -reuseconn - allow libcurl to reuse HTTP connections (only matters if compiled with libcurl)
[2021.10.30-16.22.38:328][ 0]LogInit: -virtmemkb=NUMBER - sets process virtual memory (address space) limit (overrides VirtualMemoryLimitInKB value from .ini)
[2021.10.30-16.22.38:328][ 0]LogInit: - Physical RAM available (not considering process quota): 12 GB (11995 MB, 12283872 KB,<PHONE_NUMBER>8 bytes)
LogPluginManager: Mounting plugin ActorSequence
LogPluginManager: Mounting plugin LevelSequenceEditor
LogPluginManager: Mounting plugin MatineeToLevelSequence
LogPluginManager: Mounting plugin TemplateSequence
LogPluginManager: Mounting plugin OnlineSubsystemNull
LogPluginManager: Mounting plugin LauncherChunkInstaller
LogPluginManager: Mounting plugin ActorLayerUtilities
LogPluginManager: Mounting plugin AppleImageUtils
LogPluginManager: Mounting plugin AssetTags
LogPluginManager: Mounting plugin AudioCapture
LogPluginManager: Mounting plugin CableComponent
LogPluginManager: Mounting plugin ChunkDownloader
LogPluginManager: Mounting plugin CustomMeshComponent
LogPluginManager: Mounting plugin ExampleDeviceProfileSelector
LogPluginManager: Mounting plugin GooglePAD
LogPluginManager: Mounting plugin LinuxDeviceProfileSelector
LogPluginManager: Mounting plugin PhysXVehicles
LogPluginManager: Mounting plugin RuntimePhysXCooking
LogPluginManager: Mounting plugin SoundFields
LogPluginManager: Mounting plugin Synthesis
LogPluginManager: Mounting plugin AudioSynesthesia
LogInit: Using libcurl 7.65.3-DEV
LogInit: - built for x86_64-unknown-linux-gnu
LogInit: - supports SSL with OpenSSL/1.1.1c
LogInit: - supports HTTP deflate (compression) using libz 1.2.8
LogInit: - other features:
LogInit: CURL_VERSION_SSL
LogInit: CURL_VERSION_LIBZ
LogInit: CURL_VERSION_IPV6
LogInit: CURL_VERSION_ASYNCHDNS
LogInit: CURL_VERSION_LARGEFILE
LogInit: CURL_VERSION_TLSAUTH_SRP
LogInit: CurlRequestOptions (configurable via config and command line):
LogInit: - bVerifyPeer = true - Libcurl will verify peer certificate
LogInit: - bUseHttpProxy = false - Libcurl will NOT use HTTP proxy
LogInit: - bDontReuseConnections = false - Libcurl will reuse connections
LogInit: - MaxHostConnections = 16 - Libcurl will limit the number of connections to a host
LogInit: - LocalHostAddr = Default
LogInit: - BufferSize = 65536
Shutdown handler: initalize.
LogOnline: OSS: Creating online subsystem instance for: EOS
LogOnline: OSS: FOnlineSubsystemEOS: Init success.
LogSteamShared: Display: Loading Steam SDK 1.47
LogCore: Warning: dlopen failed: /config/gamefiles/Engine/Binaries/Linux/libsteam_api.so: cannot open shared object file: No such file or directory

LogSteamShared: Warning: Could not find system one, loading bundled libsteam_api.so.

LogSteamShared: Display: Loaded libsteam_api.so at 0x449db0
LogSteamShared: Steam SDK Loaded!
LogOnline: OSS: Creating online subsystem instance for: STEAM
LogOnline: Warning: STEAM: Steam API failed to initialize!

LogOnline: Display: STEAM: OnlineSubsystemSteam::Shutdown()
LogOnline: OSS: Unable to create OnlineSubsystem module STEAM
LogOnline: OSS: TryLoadSubsystemAndSetDefault: Loaded subsystem for module [EOS]
LogOnline: OSS: Creating online subsystem instance for: STEAM
LogOnline: Warning: STEAM: Steam API failed to initialize!

LogOnline: Display: STEAM: OnlineSubsystemSteam::Shutdown()
LogInit: Build: ++FactoryGame+main-CL-170636
LogInit: Engine Version: 4.26.1-170636+++FactoryGame+main

LogInit: Compatible Engine Version: 4.26.1-170636+++FactoryGame+main

LogInit: Net CL: 170636
LogInit: OS: GenericOSVersionLabel (GenericOSSubVersionLabel), CPU: Intel(R) Xeon(R) CPU X5660 @ 2.80GHz, GPU: GenericGPUBrand

LogInit: Compiled (64-bit): Oct 18 2021 21:21:12
LogInit: Compiled with Clang: 10.0.1 (https://github.com/llvm/llvm-project ef32c611aa214dea855364efd7ba451ec5ec3f74)
LogInit: Build Configuration: Shipping
LogInit: Branch Name: ++FactoryGame+main
LogInit: Command Line: -log -NoSteamClient -unattended
LogInit: Base Directory: /config/gamefiles/Engine/Binaries/Linux/
LogInit: Allocator: binned2
LogInit: Installed Engine Build: 0
LogInit: Launcher File: /config/gamefiles/launcher_id
LogInit: Launcher ID:
LogInit: Launcher Artifact:
LogInit: Presizing for max 2097152 objects, including 1 objects not considered by GC, pre-allocating 0 bytes for permanent pool.
LogStreaming: Display: Async Loading initialized: Event Driven Loader: true, Async Loading Thread: false, Async Post Load: false
LogInit: Object subsystem initialized
[2021.10.30-16.22.38:327][ 0]LogLinux: Selected Device Profile: [LinuxServer]
[2021.10.30-16.22.38:327][ 0]LogInit: Applying CVar settings loaded from the selected device profile: [LinuxServer]
[2021.10.30-16.22.38:328][ 0]LogHAL: Display: Platform has ~ 4 GB [12578684928 /<PHONE_NUMBER> / 12], which maps to Smallest [LargestMinGB=32, LargerMinGB=12, DefaultMinGB=8, SmallerMinGB=6, SmallestMinGB=0)
[2021.10.30-16.22.38:328][ 0]LogInit: Going up to parent DeviceProfile [Linux]
[2021.10.30-16.22.38:328][ 0]LogInit: Going up to parent DeviceProfile []
[2021.10.30-16.22.38:328][ 0]LogInit: Unix hardware info:
[2021.10.30-16.22.38:328][ 0]LogInit: - we are the first instance of this executable
[2021.10.30-16.22.38:328][ 0]LogInit: - this process' id (pid) is 89, parent process' id (ppid) is 25
[2021.10.30-16.22.38:328][ 0]LogInit: - we are not running under debugger
[2021.10.30-16.22.38:328][ 0]LogInit: - machine network name is 'satisfactory-server'
[2021.10.30-16.22.38:328][ 0]LogInit: - user name is 'steam' (steam)
[2021.10.30-16.22.38:328][ 0]LogInit: - we're logged in locally
[2021.10.30-16.22.38:328][ 0]LogInit: - we're running without rendering
[2021.10.30-16.22.38:328][ 0]LogInit: - CPU: GenuineIntel 'Intel(R) Xeon(R) CPU X5660 @ 2.80GHz' (signature: 0x206C2)
[2021.10.30-16.22.38:328][ 0]LogInit: - Number of physical cores available for the process: 24
[2021.10.30-16.22.38:328][ 0]LogInit: - Number of logical cores available for the process: 24
[2021.10.30-16.22.38:328][ 0]LogInit: - Cache line size: 64
[2021.10.30-16.22.38:328][ 0]LogInit: - Memory allocator used: binned2
[2021.10.30-16.22.38:328][ 0]LogInit: - This binary is optimized with LTO: no, PGO: no, instrumented for PGO data collection: no
[2021.10.30-16.22.38:328][ 0]LogInit: - This is a licensee build.
[2021.10.30-16.22.38:328][ 0]LogCore: Benchmarking clocks:
[2021.10.30-16.22.38:328][ 0]LogCore: - CLOCK_MONOTONIC (id=1) can sustain 43653899 (43654K, 44M) calls per second without zero deltas.
[2021.10.30-16.22.38:328][ 0]LogCore: - CLOCK_MONOTONIC_RAW (id=4) can sustain 43001088 (43001K, 43M) calls per second without zero deltas.
[2021.10.30-16.22.38:328][ 0]LogCore: - CLOCK_MONOTONIC_COARSE (id=6) can sustain 98807615 (98808K, 99M) calls per second with 99.998978% zero deltas.
[2021.10.30-16.22.38:328][ 0]LogCore: Selected clock_id 1 (CLOCK_MONOTONIC) since it is the fastest support clock without zero deltas.
[2021.10.30-16.22.38:328][ 0]LogInit: Unix-specific commandline switches:
[2021.10.30-16.22.38:328][ 0]LogInit: -ansimalloc - use malloc()/free() from libc (useful for tools like valgrind and electric fence)
[2021.10.30-16.22.38:328][ 0]LogInit: -jemalloc - use jemalloc for all memory allocation
[2021.10.30-16.22.38:328][ 0]LogInit: -binnedmalloc - use binned malloc for all memory allocation
[2021.10.30-16.22.38:328][ 0]LogInit: -filemapcachesize=NUMBER - set the size for case-sensitive file mapping cache
[2021.10.30-16.22.38:328][ 0]LogInit: -useksm - uses kernel same-page mapping (KSM) for mapped memory (OFF)
[2021.10.30-16.22.38:328][ 0]LogInit: -ksmmergeall - marks all mmap'd memory pages suitable for KSM (OFF)
[2021.10.30-16.22.38:328][ 0]LogInit: -preloadmodulesymbols - Loads the main module symbols file into memory (OFF)
[2021.10.30-16.22.38:328][ 0]LogInit: -sigdfl=SIGNAL - Allows a specific signal to be set to its default handler rather then ignoring the signal
[2021.10.30-16.22.38:328][ 0]LogInit: -httpproxy=ADDRESS:PORT - redirects HTTP requests to a proxy (only supported if compiled with libcurl)
[2021.10.30-16.22.38:328][ 0]LogInit: -reuseconn - allow libcurl to reuse HTTP connections (only matters if compiled with libcurl)
[2021.10.30-16.22.38:328][ 0]LogInit: -virtmemkb=NUMBER - sets process virtual memory (address space) limit (overrides VirtualMemoryLimitInKB value from .ini)
[2021.10.30-16.22.38:328][ 0]LogInit: - Physical RAM available (not considering process quota): 12 GB (11995 MB, 12283872 KB,<PHONE_NUMBER>8 bytes)
[2021.10.30-16.22.38:328][ 0]LogInit: - VirtualMemoryAllocator pools will grow at scale 1.4
[2021.10.30-16.22.38:328][ 0]LogInit: - MemoryRangeDecommit() will will evict the memory from RAM (re-run with -novmapoolevict to change)
[2021.10.30-16.22.38:371][ 0]LogInit: Physics initialised using underlying interface: PhysX
[2021.10.30-16.22.38:372][ 0]LogInit: Overriding language with engine language configuration option (en-US-Posix).
[2021.10.30-16.22.38:372][ 0]LogInit: Overriding language with engine locale configuration option (en-US-Posix).
[2021.10.30-16.22.38:381][ 0]LogTextLocalizationResource: LocRes '../../../Engine/Content/Localization/Engine/en-US-POSIX/Engine.locres' could not be opened for reading!
[2021.10.30-16.22.38:382][ 0]LogTextLocalizationResource: LocRes '../../../Engine/Plugins/Online/OnlineFramework/Content/Localization/OnlineFramework/en-US-POSIX/OnlineFramework.locres' could not be opened for reading!
[2021.10.30-16.22.38:382][ 0]LogTextLocalizationResource: LocRes '../../../Engine/Plugins/Online/OnlineSubsystem/Content/Localization/OnlineSubsystem/en-US-POSIX/OnlineSubsystem.locres' could not be opened for reading!
[2021.10.30-16.22.38:383][ 0]LogTextLocalizationResource: LocRes '../../../Engine/Plugins/Online/OnlineSubsystemUtils/Content/Localization/OnlineSubsystemUtils/en-US-POSIX/OnlineSubsystemUtils.locres' could not be opened for reading!
[2021.10.30-16.22.38:383][ 0]LogTextLocalizationResource: LocRes '../../../Engine/Plugins/Online/OnlineSubsystemSteam/Content/Localization/OnlineSubsystemSteam/en-US-POSIX/OnlineSubsystemSteam.locres' could not be opened for reading!
[2021.10.30-16.22.38:407][ 0]LogRendererCore: Ray tracing is disabled. Reason: r.RayTracing=0.
[2021.10.30-16.22.38:438][ 0]LogInit: Overriding language with engine language configuration option (en-US-Posix).
[2021.10.30-16.22.38:438][ 0]LogInit: Overriding language with engine locale configuration option (en-US-Posix).
[2021.10.30-16.22.38:445][ 0]LogTextLocalizationResource: LocRes '../../../FactoryGame/Content/Localization/Game/en/Game.locres' could not be opened for reading!
[2021.10.30-16.22.38:452][ 0]LogTextLocalizationManager: Compacting localization data took 1.37ms
[2021.10.30-16.22.38:633][ 0]LogAssetRegistry: FAssetRegistry took 0.1000 seconds to start up
[2021.10.30-16.22.38:713][ 0]LogStreaming: Display: FlushAsyncLoading: 1 QueuedPackages, 0 AsyncPackages
[2021.10.30-16.22.38:713][ 0]LogPackageLocalizationCache: Processed 23 localized package path(s) for 2 prioritized culture(s) in 0.000118 seconds
[2021.10.30-16.22.38:713][ 0]LogPakFile: New pak file ../../../FactoryGame/Content/Paks/FactoryGame-LinuxServer.pak added to pak precacher.
[2021.10.30-16.22.38:717][ 0]LogLinux: Selected Device Profile: [LinuxServer]
[2021.10.30-16.22.38:718][ 0]LogInit: Active device profile: [0x146ef61ba780][0x146f15317630 49] LinuxServer
[2021.10.30-16.22.38:718][ 0]LogInit: Profiles: [0x146ef61ba900][0x146f153189e0 49] Linux, [0x146ef61ba780][0x146f15317630 49] LinuxServer,
[2021.10.30-16.22.38:737][ 0]LogSerialization: Display: AllowBulkDataInIoStore: 'true'
[2021.10.30-16.22.38:738][ 0]LogNetVersion: FactoryGame 1.0.0, NetCL: 170636, EngineNetVer: 16, GameNetVer: 0 (Checksum: 525596976)

[2021.10.30-16.22.39:357][ 0]LogActor: Warning: SetReplicates called on non-initialized actor Default__FGSimulatedWheeledVehicle. Directly setting bReplicates is the correct procedure for pre-init actors.

[2021.10.30-16.22.39:486][ 0]LogNiagara: Warning: NiagaraSystem /Game/FactoryGame/VFX/Factory/Doors/NS_DoorClose_01.NS_DoorClose_01 IsReadyToRunInternal() failed due to missing SystemScript. Spawn[<none>] Update[<none>]

[2021.10.30-16.22.40:535][ 0]LogPakFile: Precache HighWater 16MB

[2021.10.30-16.22.40:535][ 0]LogPakFile: Precache HighWater 32MB

[2021.10.30-16.22.40:535][ 0]LogPakFile: Precache HighWater 48MB

[2021.10.30-16.22.40:535][ 0]LogPakFile: Precache HighWater 64MB

Signal 11 caught.
Malloc Size=65538 LargeMemoryPoolOffset=65554
[2021.10.30-16.22.40:535][ 0]LogNiagara: Warning: NiagaraSystem /Game/FactoryGame/VFX/World/AmbientLife/Flies/NS_Fireflies_01.NS_Fireflies_01 IsReadyToRunInternal() failed due to missing SystemScript. Spawn[<none>] Update[<none>]

[2021.10.30-16.22.40:535][ 0]LogNiagara: Warning: NiagaraSystem /Game/FactoryGame/VFX/World/AmbientLife/Bats/NS_Bats_01.NS_Bats_01 IsReadyToRunInternal() failed due to missing SystemScript. Spawn[<none>] Update[<none>]

[2021.10.30-16.22.40:682][ 0]GameAnalyticsModule: Display: GameAnalyticsModule has started!
[2021.10.30-16.22.40:682][ 0]LogStreaming: Warning: Failed to read file '../../../FactoryGame/Saved/SaveGames/GameAnalytics.sav' error.

[2021.10.30-16.22.41:039][ 0]LogAudioCaptureCore: Display: No Audio Capture implementations found. Audio input will be silent.
[2021.10.30-16.22.41:039][ 0]LogAudioCaptureCore: Display: No Audio Capture implementations found. Audio input will be silent.
[2021.10.30-16.22.41:075][ 0]LogUObjectArray: 49601 objects as part of root set at end of initial load.
[2021.10.30-16.22.41:075][ 0]LogUObjectArray: 2 objects are not in the root set, but can never be destroyed because they are in the DisregardForGC set.
[2021.10.30-16.22.41:075][ 0]LogUObjectAllocator: 15768640 out of 0 bytes used by permanent object pool.
[2021.10.30-16.22.41:075][ 0]LogUObjectArray: CloseDisregardForGC: 49601/49601 objects in disregard for GC pool
[2021.10.30-16.22.41:075][ 0]LogEngine: Initializing Engine...
[2021.10.30-16.22.41:077][ 0]LogStats: UGameplayTagsManager::InitializeManager - 0.002 s
[2021.10.30-16.22.41:086][ 0]LogInit: Initializing FReadOnlyCVARCache
[2021.10.30-16.22.41:086][ 0]LogNetVersion: Set ProjectVersion to <IP_ADDRESS>. Version Checksum will be recalculated on next use.

[2021.10.30-16.22.41:086][ 0]LogInit: Texture streaming: Disabled
[2021.10.30-16.22.41:130][ 0]LogOnline: OSS: Creating online subsystem instance for: STEAM
[2021.10.30-16.22.41:131][ 0]LogOnline: Warning: STEAM: Steam API failed to initialize!

[2021.10.30-16.22.41:131][ 0]LogOnline: Display: STEAM: OnlineSubsystemSteam::Shutdown()
[2021.10.30-16.22.41:131][ 0]LogOnline: OSS: Creating online subsystem instance for: STEAM
[2021.10.30-16.22.41:131][ 0]LogOnline: Warning: STEAM: Steam API failed to initialize!

[2021.10.30-16.22.41:131][ 0]LogOnline: Display: STEAM: OnlineSubsystemSteam::Shutdown()
[2021.10.30-16.22.41:131][ 0]LogOnline: OSS: Creating online subsystem instance for: STEAM
[2021.10.30-16.22.41:131][ 0]LogOnline: Warning: STEAM: Steam API failed to initialize!

[2021.10.30-16.22.41:131][ 0]LogOnline: Display: STEAM: OnlineSubsystemSteam::Shutdown()
CommonUnixCrashHandler: Signal=11
[2021.10.30-16.22.41:179][ 0]LogCore: === Critical error: ===

Unhandled Exception: SIGSEGV: invalid attempt to read memory at address 0x0000000000000070

[2021.10.30-16.22.41:180][ 0]LogCore: Fatal error!

0x0000146ef32438cf libUE4Server-FactoryGame-Linux-Shipping.so!UFGServerSubsystem::Initialize(FSubsystemCollectionBase&) [D:/ws/SB-160502110050-fad/UE4/Games/FactoryGame/Source/FactoryGame/Private/Server/FGServerSubsystem.cpp:170]
0x0000146f1e23440a libUE4Server-Engine-Linux-Shipping.so!FSubsystemCollectionBase::AddAndInitializeSubsystem(UClass*) [D:/ws/SB-160502110050-fad/UE4/Engine/Source/Runtime/Engine/Private/Subsystems/SubsystemCollection.cpp:209]
0x0000146f1e233a3e libUE4Server-Engine-Linux-Shipping.so!FSubsystemCollectionBase::Initialize(UObject*) [D:/ws/SB-160502110050-fad/UE4/Engine/Source/Runtime/Engine/Private/Subsystems/SubsystemCollection.cpp:132]
0x0000146f1dc6a56f libUE4Server-Engine-Linux-Shipping.so!UGameInstance::Init() [D:/ws/SB-160502110050-fad/UE4/Engine/Source/Runtime/Engine/Private/GameInstance.cpp:99]
0x0000146ef300dc51 libUE4Server-FactoryGame-Linux-Shipping.so!UFGGameInstance::Init() [D:/ws/SB-160502110050-fad/UE4/Games/FactoryGame/Source/FactoryGame/Private/FGGameInstance.cpp:78]
0x0000146f1dc44fe3 libUE4Server-Engine-Linux-Shipping.so!UGameEngine::Init(IEngineLoop*) [D:/ws/SB-160502110050-fad/UE4/Engine/Source/Runtime/Engine/Private/GameEngine.cpp:1107]
0x0000146ef300d6ba libUE4Server-FactoryGame-Linux-Shipping.so!UFGGameEngine::Init(IEngineLoop*) [D:/ws/SB-160502110050-fad/UE4/Games/FactoryGame/Source/FactoryGame/Private/FGGameEngine.cpp:40]
0x0000000000214c4e UE4Server-Linux-Shipping!FEngineLoop::Init() [D:/ws/SB-160502110050-fad/UE4/Engine/Source/Runtime/Launch/Private/LaunchEngineLoop.cpp:4008]
0x000000000021623c UE4Server-Linux-Shipping!GuardedMain(char16_t const*) [D:/ws/SB-160502110050-fad/UE4/Engine/Source/Runtime/Launch/Private/Launch.cpp:153]
0x0000146f1bd1ddc5 libUE4Server-UnixCommonStartup-Linux-Shipping.so!CommonUnixMain(int, char**, int (*)(char16_t const*), void (*)()) [D:/ws/SB-160502110050-fad/UE4/Engine/Source/Runtime/Unix/UnixCommonStartup/Private/UnixCommonStartup.cpp:264]
0x0000146f1bb7109b libc.so.6!__libc_start_main(+0xea)
0x0000000000214709 UE4Server-Linux-Shipping!_start()

[2021.10.30-16.22.41:232][ 0]LogExit: Executing StaticShutdownAfterError
Engine crash handling finished; re-raising signal 11 for the default handler. Good bye.
/home/steam/run.sh: line 53: 89 Segmentation fault Engine/Binaries/Linux/UE4Server-Linux-Shipping FactoryGame -log -NoSteamClient -unattended

I'm seeing the same error

Unhandled Exception: SIGSEGV: invalid attempt to read memory at address 0x0000000000000070

Could you try running the dev tag, please?

Just pulled the docker image from dockerhub on dev tag with the same result.  wiped all directories and started over from scratch.  Had to touch the ServerSettings.15777 file to avoid a chmod error.

Just pulled the docker image from dockerhub on dev tag with the same result. wiped all directories and started over from scratch. Had to touch the ServerSettings.15777 file to avoid a chmod error.

Yeah, the chmod issue is fixed in latest. Just wanted to see if the older build on dev worked or not

This and #61 are essentially the same issue, so please continue the discussion there.


NONCE NONCE NONCE (dances to techNOOOOO)

I rule and have completed some work on Case Manager that's ready for review!
Trying out a nonce using SecureRandom (http://daniel.fone.net.nz/blog/2014/12/07/generating-unique-random-tokens/)
This pull request makes the following changes:

Minor changes to application_controller.rb (with large implications)

It relates to the following issue #s:

Fixes #893

@colinxfleming so this kinda switches to nonces, although there's a few issues thus far that I've noticed:

It only applies to inline scripts on self, not every script (guessing this was intentional)
it needs to be applied to the inline script (which I can't find?)

Closing in favor of going with something like #1102 , experimental PR is this one (Yoda would say, or someone like me with bad English)


[N0120] Change RAM address for N0120

This pull request fixes backupStorage and installStorage method for the N0120.
This pull request is in draft as it can't test it for now.
A version of Upsilon Workshop with the patch is available here.
When this version will work, I will add support for the N0120 alongside with the others models.

Superseded by #9.


net: Use k_fifo instead of k_work in RX and TX processing

The k_work handler cannot manipulate the used k_work. This means
that it is not easy to cleanup the net_pkt because it contains
k_work in it. Because of this, use k_fifo instead between
RX thread and network driver, and between application and TX
thread.
A echo-server/client run with IPv4 and UDP gave following
results:
Using k_work
------------
TX traffic class statistics:
TC  Priority	Sent pkts	bytes	time
[0] BK (1)	21922		5543071	103 us	[0->41->26->34=101 us]
[1] BE (0)	0		0	-
RX traffic class statistics:
TC  Priority	Recv pkts	bytes	time
[0] BK (0)	0		0	-
[1] BE (0)	21925		6039151	97 us	[0->21->16->37->20=94 us]

Using k_fifo
------------
TX traffic class statistics:
TC  Priority	Sent pkts	bytes	time
[0] BK (1)	15079		3811118	94 us	[0->36->23->32=91 us]
[1] BE (0)	0		0	-
RX traffic class statistics:
TC  Priority	Recv pkts	bytes	time
[0] BK (1)	0		0	-
[1] BE (0)	15073		4150947	79 us	[0->17->12->32->14=75 us]

So using k_fifo gives about 10% better performance with same
workload.
Fixes #34690
Signed-off-by: Jukka Rissanen<EMAIL_ADDRESS>

@alexanderwachter I converted 6locan to not use k_work in net_pkt. Unfortunately I have no way to test the changes, so asking would you be able to review and possibly check if the changes work as expected.

@mniestroj @tsvehagen You seem to have modified the offloading esp wifi driver last time. The driver uses net_pkt for its internal use but we want to get rid of the k_work in net_pkt. Unfortunately the driver looked somewhat convoluted so I was not able to modify it. Any suggestion how to solve this issue?

I think the use of k_work in net_pkt was a quite recent change. Not sure if it's easy to revert or if we should solve it some other way. What do you think @mniestroj?

Does anyone have time to review this one, it would be nice to get this merged by Friday?

Maybe it would be better to squash the two commits
* drivers: wifi: esp: Temporary fix to allow compilation

* net: Use k_fifo instead of k_work in RX and TX processing

together?

Perhaps, or we could move the esp change before the main commit net: Use k_fifo instead of k_work in RX and TX processing. This way there should be no issue with bisect.

I wonder if we should change the name of the function, since _work_handler is typically associated with Workqueue Threads.

I did not want to do too big changes with naming. The thread is basically doing "work" here, just that it is not happening via k_work. Function naming leads always to interesting discussion, so if there are suggestions what these changed functions should be called, I am all ears.

@mniestroj @tsvehagen You seem to have modified the offloading esp wifi driver last time. The driver uses net_pkt for its internal use but we want to get rid of the k_work in net_pkt. Unfortunately the driver looked somewhat convoluted so I was not able to modify it. Any suggestion how to solve this issue?

@jukkar I will look into ESP driver, but not this week. Unfortunately reverting to k_fifo (as was used before) is not an option, due to bugs that using work object allowed us to solve. It will be major work for ESP driver to get rid of pkt->work...

I will look into ESP driver, but not this week. Unfortunately reverting to k_fifo (as was used before) is not an option, due to bugs that using work object allowed us to solve. It will be major work for ESP driver to get rid of pkt->work...

Yes, I understand. I looked at the driver but it seemed quite a lot of work so did not try to do it myself. I think we should merge this PR like this and ESP changes can come when they are ready.

I agree that this patchset leads to mixed feelings. On one hand, it definitely cleans up structure and processing - it's quite natural that, if we need to decouple IRQ-based and normal processing, then to put packets in a queue. On the other hand, that leads to proliferation of different queues, and most importantly, handlers threads which are just duplication of each other and differ only in which actual handler function they call.
It immediately leads to an idea to add a handler callback to net_pkt, and a common handler thread which would just call the handler. But that's apparently the reason why workqueue was used in the first place! Because it offers just that functionality, except it has the stipulation which net_pkt handling doesn't adhere too.
All in all, I guess it's a good change, but worth being further optimized to minimize number of processing threads (their stacks) somehow. (Not giving +1 right away, as I didn't test these changes yet.)

k_fifo vs k_work time measurements seem suspicious to me and I honestly don't believe in 10% improvement. There is only one step (maybe two with CAN, but not sure) in networking TX packet path where this PR should make a difference. This is net_tc.c code, when CONFIG_NET_TC_TX_COUNT >= 1. So having results like:
k_work
[0] BK (1)	21922		5543071	103 us	[0->41->26->34=101 us]

k_fifo
[0] BK (1)	15079		3811118	94 us	[0->36->23->32=91 us]

seems wrong. IMO just 26 vs 23 shows the difference in k_work vs k_fifo. But then, something had to be wrong with measurement, as other numbers should theoretically be equal. Maybe measurements were not taken over multiple times?
I made some measurements with samples/net/sockets/echo_server and qemu_x86 with overlay-e1000.conf. As a result I get:
k_work
Avg TX net_pkt (709) time 41 us [0->19->6->13=38 us]

k_fifo
Avg TX net_pkt (709) time 39 us [0->19->4->13=36 us]

when taking average from multiple measurements in TX path. In case of RX, I see maybe 1us difference from total of 25us - too little to make any conclusions.

I do like net: Use k_fifo instead of k_work in RX and TX processing commit, as it just changes from workqueue threads to specialized threads consuming k_fifo. It also does come with some performance improvement.
I don't like ppp and 6locan changes however. Most importantly, new threads are added for no good (enough) reason, which results in higher RAM and FLASH usage. I tested PPP with nRF52 based project and it seems that RAM usage increases by 1216 bytes and FLASH usage increases by 276 bytes. I don't like it, as I believe 32kB of RAM was enough to run PPP with some cellular modem and simple app. 1216 is a big difference in that case. On the other hand PPP change isn't that bad  if we take into account that fixing PPP implementation will allow us (propably) to drop this thread. The reason why it shouldn't be needed is that following comment:
https://github.com/zephyrproject-rtos/zephyr/blob/126da28620d7f0f94b44d7ef615a546a9c2f3ffe/subsys/net/l2/ppp/fsm.c#L537-L545
is simply wrong. Calling either k_work_submit or k_fifo_put can reschedule threads, so the original problem is still there, but possibly is not reproduced that often.

k_fifo vs k_work time measurements seem suspicious to me and I honestly don't believe in 10% improvement. There is only one step (maybe two with CAN, but not sure) in networking TX packet path where this PR should make a difference. This is net_tc.c code, when CONFIG_NET_TC_TX_COUNT >= 1. So having results like:
k_work
[0] BK (1)	21922		5543071	103 us	[0->41->26->34=101 us]

k_fifo
[0] BK (1)	15079		3811118	94 us	[0->36->23->32=91 us]

seems wrong. IMO just 26 vs 23 shows the difference in k_work vs k_fifo. But then, something had to be wrong with measurement, as other numbers should theoretically be equal. Maybe measurements were not taken over multiple times?

The number packets is shown there, for k_work it was 21922 and for fifo 15079.

I made some measurements with samples/net/sockets/echo_server and qemu_x86 with overlay-e1000.conf. As a result I get:
k_work
Avg TX net_pkt (709) time 41 us [0->19->6->13=38 us]

k_fifo
Avg TX net_pkt (709) time 39 us [0->19->4->13=36 us]

when taking average from multiple measurements in TX path. In case of RX, I see maybe 1us difference from total of 25us - too little to make any conclusions.

You do not have any TC threads in your tests (note that the default number of TX threads is now 0), so you will not see any difference in your test between k_work and k_fifo.

Maybe measurements were not taken over multiple times?

The number of packets is shown there, for k_work it was 21922 and for fifo 15079.

Okay. I used around 700 (and sometimes 7000) which is equivalent of 100 (1000) runs of echo-client. But then I restarted qemu_x86 machine and retried the whole test multiple times and have noticed that results are different (easily by several %). Even running 21922 vs 15079 would make a big difference. So I tried to average from those multiple "cold-start" runs, always using the same number echo-client runs. I also removed all logs, so they don't interfere.

You do not have any TC threads in your tests (note that the default number of TX threads is now 0), so you will not see any difference in your test between k_work and k_fifo.

I do have TX TC thread. I forgot to mention, that I specifically added CONFIG_NET_TC_TX_COUNT=1. Without that option, there was no difference at all (which is expected), i.e. there was no step that takes 6us in case of k_work and 4us in case of k_fifo.

Fixed merge conflict