Replaced 0 with PUGIXML_NULL when a nullptr would have been needed.

Fixed a GCC warning about using a const literal zero in place of nullptr (-Wzero-as-null-pointer-constant) by using the already defined PUGIXML_NULL macro when the C++ version supports nullptr.

Just want to check - does using NULL instead of PUGIXML_NULL in pugixml.cpp also silence the warnings?
The reason to prefer NULL in this case is that since pugixml isn't a C++11 codebase, and 0 vs nullptr have different semantics in certain cases for overloads, it would be a little safer for future changes to use NULL internally. We use PUGIXML_NULL in the external interface to ensure maximum compliance vs aggressive analysis tools like clang-tidy but I'm wondering if this is necessary in the implementation.

If this PR switches to NULL + has no unrelated whitespace changes I'd be happy to merge this.

Using NULL  does fix the issue with GCC but Clang still complains :

warning: zero as null pointer constant [-Wzero-as-null-pointer-constant]

So to keep it compatible with C++ from before C++11, PUGIXML_NULL is the better solution.

Using NULL does fix the issue with GCC but Clang still complains

That is unfortunate :-/ gcc explicitly silences this for NULL, https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=752e7593b0f19af233a0b7e72daab8413662b605, but it looks like clang version was implemented before this change was in effect, and never relaxed.
NULL felt like a straightforward fix but PUGIXML_NULL is significantly noisier, and we can't use nullptr because pre-C++11 support is important :-/ I'm now considering possibly silencing this diagnostic for clang in the source file via pragmas.

I'm going to merge this as is for now; we'll see if clang revisits the gcc compatibility (in which case we could enable the warning on clang depending on the version), but this definitely provides the readability improvements that the warning was intended to carry without sacrificing anything.


Transactions take 6 confirmations but stakes take 50/51 confirmations?

send/receive tx take 6 confirmations but stakes tx take 50/51 confirmations?
@aguycalled is this by design or a bug?

stake maturation of 50 blocks is by design.
6 confirmations for normal tx is inherited from bitcoin and should be adapted

So the 5/6 block maturity for normal tx should take 50/51?

i don't think the 5/6 block maturity requirement is enforced in order to be able to spend outputs. it's just a gui indication iirc
the staking maturity requirement is to prevent precomputing of stake kernel hashes

i don't think the 5/6 block maturity requirement is enforced in order to be able to spend outputs. it's just a gui indication iirc
the staking maturity requirement is to prevent precomputing of stake kernel hashes

So nothing to fix then, I'll close the issue.


how to compiler

HI dear author,
It's truly a honor to write a letter to you,  I'm building your project nowadays and found the error when building as following, I wonder if there is a chance that you know the reason? :)

thank you
best regards to you
William

HI dear author,
It's truly a honor to write a letter to you, I'm building your project nowadays and found the error when building as following, I wonder if there is a chance that you know the reason? :)

Thank you for your kind words and your interest in the project.
I can not say for sure why you have this problem.  I can only guess you use a bit different LLV M version.  LLVM notoriuosly known for its version API instability therefore a lot projects using LLVM actually require a specific version of LLVM.  I decided to use LLVM C API (not C++ one) as more stable one but even this probably did not save us from the problem.
LLVM to MIR translator is not finished yet and can be buggy (e.g. I know some bugs in out-of-SSA code). LLVM-to-MIR translator will be definitely absent in the first release of MIR project code.
Also it is better to use make instead of cmake.  Makefilelist for cmake was origionaly written by another guy for Windows port.  Cmake Makefilelist has only a small part of functionality of Makefile (GNUMakefile).
So I would recommend you to comment entries in GNUMakefile for building l2m.  They are placed in one section of the make file.


step description updates

Codecov Report

Merging #39 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #39   +/-   ##
=======================================
  Coverage   44.18%   44.18%
=======================================
  Files           6        6
  Lines         430      430
=======================================
  Hits          190      190
  Misses        210      210
  Partials       30       30

Continue to review full report at Codecov.

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


Always return true once full fill the requirements

Hi Ravish1, thank you for your interest and taking the time to post an issue. Can you provide steps on how to replicate the issue you are seeing? Thanks!


Fix Expo.Message.msgctxt/0 type

Fixes #112

Pull Request Test Coverage Report for Build ff318407389d54d32c4f6b7427c8a37da42e25fc-PR-113

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build e03b8733b041b0af6a3523a22a06749baa669501:
0.0%

Covered Lines:
374

Relevant Lines:
374

💛  - Coveralls


Dropping vanished followers works again.

An exception response to a replication request is now handled properly,
such that a vanished follower can properly be dropped and the leader can
move on. This functionality is covered by the node resilience tests,
which lead to the discovery of this bug.

http://jenkins.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/11454/

@graetzer i am happy to review and/or discuss an alternative fix. We started discussion in internal issue and should continue.
Nevertheless this fixes the problem at hand and is available now.
So we at least should consider it in my opinion, but as I said happy to go for a better variant.

http://jenkins.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/11457/

We try a different approach which would get rid of the exception in the first place.

http://jenkins.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/11461/

http://jenkins.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/11471/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/11504/

Tests blue.


Update conformance runner csv files for CL 3.0

The csv's need updating to reflect the required tests that must pass for an implementation to be conformant.

I'll submit a PR for this in the morning. Currently planning on dropping the API specific files at the same time.

Closing due to https://github.com/KhronosGroup/OpenCL-CTS/pull/971 having merged.


Refs #31275 -- Make sql_flush() faster on MySQL.

I checked the time taken by flush command with 100 tables. See the source code at https://github.com/c-bata/django-fast-mysql-flush

number of records on each table
before
after reset_sequences=False (default)
after reset_sequences=True (optional)

10
3.893 sec (+/- 0.3141)
0.535 sec (+/- 0.0797)
1.762 sec (+/- 0.0968)

100
3.889 sec (+/- 0.5504)
0.580 sec (+/- 0.0341)
1.818 sec (+/- 0.0346)

1000
3.912 sec (+/- 0.2674)
1.132 sec (+/- 0.0445)
2.465 sec (+/- 0.0724)

Please note that the benchmark script was run on my laptop. So the times should not be taken precisely.
Ticket URL is https://code.djangoproject.com/ticket/31275

Hmm... I don't know why this change breaks tests like:

Is it an existing issue?

@c-bata the failure was introduced by your proposed changes but the failure you pointed at seems to be a side effect on another crash
If you look at the raw stdout output of the suite execution you'll notice that the first failure is
======================================================================
ERROR [0.011s]: test_for_update_after_from (select_for_update.tests.SelectForUpdateTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/backends/mysql/base.py", line 73, in execute
    return self.cursor.execute(query, args)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/tests/.env/lib/python3.6/site-packages/MySQLdb/cursors.py", line 209, in execute
    res = self._query(query)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/tests/.env/lib/python3.6/site-packages/MySQLdb/cursors.py", line 315, in _query
    db.query(q)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/tests/.env/lib/python3.6/site-packages/MySQLdb/connections.py", line 239, in query
    _mysql.connection.query(self, query)
MySQLdb._exceptions.IntegrityError: (1062, "Duplicate entry '1' for key 'person_id'")

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/tests/select_for_update/tests.py", line 33, in setUp
    self.person_profile = PersonProfile.objects.create(person=self.person)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/models/manager.py", line 82, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/models/query.py", line 443, in create
    obj.save(force_insert=True, using=self.db)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/models/base.py", line 750, in save
    force_update=force_update, update_fields=update_fields)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/models/base.py", line 788, in save_base
    force_update, using, update_fields,
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/models/base.py", line 891, in _save_table
    results = self._do_insert(cls._base_manager, using, fields, returning_fields, raw)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/models/base.py", line 930, in _do_insert
    using=using, raw=raw,
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/models/manager.py", line 82, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/models/query.py", line 1235, in _insert
    return query.get_compiler(using=using).execute_sql(returning_fields)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/models/sql/compiler.py", line 1381, in execute_sql
    cursor.execute(sql, params)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/backends/utils.py", line 66, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/backends/utils.py", line 75, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/utils.py", line 90, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/django/db/backends/mysql/base.py", line 73, in execute
    return self.cursor.execute(query, args)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/tests/.env/lib/python3.6/site-packages/MySQLdb/cursors.py", line 209, in execute
    res = self._query(query)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/tests/.env/lib/python3.6/site-packages/MySQLdb/cursors.py", line 315, in _query
    db.query(q)
  File "/home/jenkins/workspace/pull-requests-bionic/database/mysql/label/bionic-pr/python/python3.6/tests/.env/lib/python3.6/site-packages/MySQLdb/connections.py", line 239, in query
    _mysql.connection.query(self, query)
django.db.utils.IntegrityError: (1062, "Duplicate entry '1' for key 'person_id'")

Since sql_flush() is heavily used during tests by TransactionTestCase this issue then snowballed to other failures.

Hi @charettes. Thank you for your swift reply! I see. I'll debug the problem.

Hi @adamchainz What do you think about changing the default behavior to use DELETE FROM table_name?
At least, it is a rare case to create more than 1000 records on unit tests. But sql_flush() is used another functions like flush management command. So if it's difficult to change the default behavior, it seems to be better to close this pull request.

The benchmark result of c3c1470 is:
(venv) $ python manage.py bench_sql_flush 10
0th elapsed: 2.023
1th elapsed: 1.837
2th elapsed: 1.791
3th elapsed: 1.932
4th elapsed: 1.962
elapsed: 1.909 sec (+/- 0.09399143936388689)
(venv) $ python manage.py bench_sql_flush 100
0th elapsed: 2.149
1th elapsed: 2.059
2th elapsed: 2.042
3th elapsed: 2.169
4th elapsed: 2.163
elapsed: 2.116 sec (+/- 0.06102950355064902)
(venv) $ python manage.py bench_sql_flush 1000
0th elapsed: 2.852
1th elapsed: 2.993
2th elapsed: 3.093
3th elapsed: 2.779
4th elapsed: 2.856
elapsed: 2.915 sec (+/- 0.12635354027361947)

This benchmark script was run on my laptop. So the times should not be taken precisely.
https://github.com/c-bata/django-fast-mysql-flush

I force-pushed to resolve conflicts and squash commits.

I agree with Simon. @c-bata Do you have time to update this patch? If not I can do this.

I see! I'll update soon!

#12634

@c-bata Thanks :+1: Welcome aboard :boat:


debian 11: libappindicator3-1 are no longer provided

On debian 11 on wards, libappindicator3-1 package has removed from repo. As it depends upon it, it can not be installed. Now, debian uses libayatana-appindicator
Announcement: https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html#noteworthy-obsolete-packages
Technical info: https://lists.debian.org/debian-devel/2018/03/msg00506.html

Is there any update about this?

I dont currently dev using debian but I can setup a vm if I need to. Is this also an issue for the snap version or just the deb release?

It was deb version. Also, I do not use Debian any more. I'm on Arch


Layout issue?

This is excellent, many thanks for your efforts here.
I raised an order with PCBWAY for some of these to be built, and they have reported this to me:

After checking your file, we found that there is via on pad in picture showing, may I know whether we should fill with resin or not

Fill with resin, the cost of pcb will increase and it will be good for assembly
2.Without resin, when you solder SMD components on pad, then paster will be easy leak out from pad

Can you advise please?
Thanks

Hi, some PCB manufacturers ask you about vias on pads because it could be a mistake, but not in this case.


Unblock/Unmute not supported in site UI

It seems that users cannot unmute/unblock a user they have blocked/muted. If we are secretly toggling this in the API then we aren't presenting the current state in a very good way.

We don't have a good way to display the block/mute/favorite state per-profile. But they can be un-[block/mute] via the /blocks page. So this is good enough.


Add pull request template

Is your feature request related to a problem? Please describe.
We need a default PR template.
Describe the solution you'd like
A reference to the issue and a checklist like:
<!-- Please refer to your issue number here:
     A brief summary of what you've done would be appreciated. -->
Pull request for #000.

<!-- Please do not forget to check these tasks:
     You can check them if not applicable. -->
- [ ] Added new tests
- [ ] Updated documentation
- [ ] Updated release notes

Describe alternatives you've considered
-
Additional context
If possible automate the release number.

[ ] Also refer to this: https://github.blog/2015-01-21-how-to-write-the-perfect-pull-request/


Add GET, POST and DELETE api routes

Must have both GET and POST routes for retrieving and adding new data.
Must include full CRUD routes.

Use Node.js and Express.js to create a RESTful API.


Support span tags in rendering description

When copy/pasting text into the description field on contentstack. Contentstack will wrap the text in a span tag. This is fine except the open source library doesn't support span tags. As a result, during the write back process the description field is set to an empty string and the entry will fail to import due to validation errors.
This fork of the library will add support for spans. Note I will also open a PR on the open source repo, and reference it in the contenthub rails app as we will need to use this fork until the PR is merged.

To see the specific tasks where the Asana app for GitHub is being used, see below:

https://app.asana.com/0/0/1204015722962791

PR to opensource library https://github.com/contentstack/contentstack-utils-ruby/pull/9


Failed to access socket path: /var/run/fail2ban/fail2ban.sock. Is fail2ban running?

Previously ansible-fail2ban always worked for me on Debian. But now when using your unmodified role  (even with just the default sshd jail) I always get:

"Failed to access socket path: /var/run/fail2ban/fail2ban.sock. Is fail2ban running?"

But when I install manually with the same configurations it works.  Tried multiple times with various settings, but can't figure out why it is not working:
root@proxmox:~# systemctl restart fail2ban; systemctl status fail2ban
● fail2ban.service - Fail2Ban Service
   Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-08-13 16:28:50 PST; 8ms ago
     Docs: man:fail2ban(1)
  Process: 1190 ExecStartPre=/bin/mkdir -p /var/run/fail2ban (code=exited, status=0/SUCCESS)
 Main PID: 1197 (fail2ban-server)
    Tasks: 1 (limit: 4915)
   Memory: 1.7M
   CGroup: /system.slice/fail2ban.service
           └─1197 /usr/bin/python3 /usr/bin/fail2ban-server -xf start

Aug 13 16:28:50 proxmox systemd[1]: Starting Fail2Ban Service...
Aug 13 16:28:50 proxmox systemd[1]: Started Fail2Ban Service.

root@proxmox:~# fail2ban-client -v status
 Loading configs for fail2ban under /etc/fail2ban
   Loading files: ['/etc/fail2ban/fail2ban.conf']
   Loading files: ['/etc/fail2ban/fail2ban.local']
   Loading files: ['/etc/fail2ban/fail2ban.conf', '/etc/fail2ban/fail2ban.local']
 Using socket file /var/run/fail2ban/fail2ban.sock
 Using pid file /var/run/fail2ban/fail2ban.pid, [INFO] logging to /var/log/fail2ban.log
 Failed to access socket path: /var/run/fail2ban/fail2ban.sock. Is fail2ban running?

Tested on Debian 10 buster
When cutting the fail2ban role to its bare essentials it works again:
root@proxmox:~# fail2ban-client -v status
 Loading configs for fail2ban under /etc/fail2ban
   Loading files: ['/etc/fail2ban/fail2ban.conf']
   Loading files: ['/etc/fail2ban/fail2ban.conf']
 Using socket file /var/run/fail2ban/fail2ban.sock
 Using pid file /var/run/fail2ban/fail2ban.pid, [INFO] logging to /var/log/fail2ban.log
Status
|- Number of jail:	2
`- Jail list:	proxmox, sshd

==== minimal fail2ban role ====
# tasks file for fail2ban
---
- name: Ensure, that fail2ban is installed on Debian.
  apt:
    name: fail2ban
    state: present
    update_cache: true
    cache_valid_time: 3600

- name: update configuration file - /etc/fail2ban/jail.local
  copy:
    src: jail.local
    dest: /etc/fail2ban/jail.local
  notify: restart fail2ban

- name: copy filter
  copy:
    src: proxmox.conf
    dest: /etc/fail2ban/filter.d/
  notify: restart fail2ban

# jail.local
[sshd]
enabled = true
port = 22,722
maxretry = 3

[proxmox]
enabled = true
port = https,http,8006
filter = proxmox
logpath = /var/log/daemon.log
maxretry = 3

# proxmox.conf filter
[Definition]
failregex = pvedaemon\[.*authentication failure; rhost=<HOST> user=.* msg=.*
ignoreregex =

# handlers file for fail2ban
---
- name: restart fail2ban
  service:
    name: fail2ban
    state: restarted

Debian 10 is not supported yet. Changing fail2ban_socket and fail2ban_pidfile (/var/run/ ->  /run/) propably fixes the problem (for you).
If you have some time feel free to add support for Debian 10

I have not tried it yet with /run/, but the defaults are still the same in Debian 10 fail2ban.conf:
# Option: socket
# Notes.: Set the socket file. This is used to communicate with the daemon. Do
#         not remove this file when Fail2ban runs. It will not be possible to
#         communicate with the server afterwards.
# Values: [ FILE ]  Default: /var/run/fail2ban/fail2ban.sock
#
socket = /var/run/fail2ban/fail2ban.sock

# Option: pidfile
# Notes.: Set the PID file. This is used to store the process ID of the
#         fail2ban server.
# Values: [ FILE ]  Default: /var/run/fail2ban/fail2ban.pid
#
pidfile = /var/run/fail2ban/fail2ban.pid

Hello!
I've tried it with renaming the paths from /var/run/... into /run/... at the fail2ban.conf file.
I also did this change at /usr/lib/tmpfiles.d/fail2ban-tmpfiles.conf
sudo fail2ban-client status
Status
|- Number of jail:      10
`- Jail list:   apache-auth, apache-badbots, apache-botsearch, apache-fakegooglebot, apache-modsecurity, apache-nohome, apache-noscript, apache-overflows, apache-shellshock, sshd

vagrant up --provision debian-10

seems to work just fine.
root@ansible-fail2ban-debian-10:~# sudo fail2ban-client status
Status
|- Number of jail:	1
`- Jail list:	sshd
root@ansible-fail2ban-debian-10:~# systemctl status fail2ban.service
● fail2ban.service - Fail2Ban Service
   Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-03-31 10:55:22 UTC; 1min 47s ago
     Docs: man:fail2ban(1)
  Process: 1801 ExecStartPre=/bin/mkdir -p /var/run/fail2ban (code=exited, status=0/SUCCESS)
 Main PID: 1802 (fail2ban-server)
    Tasks: 3 (limit: 240)
   Memory: 11.7M
   CGroup: /system.slice/fail2ban.service
           └─1802 /usr/bin/python3 /usr/bin/fail2ban-server -xf start

Mar 31 10:55:22 ansible-fail2ban-debian-10 systemd[1]: Starting Fail2Ban Service...
Mar 31 10:55:22 ansible-fail2ban-debian-10 systemd[1]: Started Fail2Ban Service.
Mar 31 10:55:23 ansible-fail2ban-debian-10 fail2ban-server[1802]: Server ready

root@ansible-fail2ban-debian-10:~# sudo fail2ban-client status
Status
|- Number of jail:	1
`- Jail list:	sshd

no role changes were needed

https://github.com/Oefenweb/ansible-fail2ban/releases/tag/v3.3.11

It looks like it has something to do with your setup

Hello!
I got exactly the same error.
Here is the piece of code in file fail2ban.conf:
`# Option: socket
Notes.: Set the socket file. This is used to communicate with the daemon. Do
not remove this file when Fail2ban runs. It will not be possible to
communicate with the server afterwards.
Values: [ FILE ]  Default: /var/run/fail2ban/fail2ban.sock

socket = /var/run/fail2ban/fail2ban.sock
Option: pidfile
Notes.: Set the PID file. This is used to store the process ID of the
fail2ban server.
Values: [ FILE ]  Default: /var/run/fail2ban/fail2ban.pid

pidfile = /var/run/fail2ban/fail2ban.pid
`
Fail2ban installed on Bitrix VM.
I would be grateful for the help
Best Regards, Anatoly

Maybe your logpath is wrong, you can check if there is a /var/log folder

Hi everybody, I could solve with chmod, I think is the access permission on the directory:
chmod -x /var/run/

@dammdev Can you create a PR (targetting the affected OS versions)?

Hello,
@dammdev I tried chmod -x /var/run/ that did not work for me.
I just came across this issue. I am not sure what information is relevant. Let me know if any other information is needed.
I am on Ubuntu 22.04.
I had to start the service, the guide I was following stated "The service automatically starts.". I assume this is not true anymore? There may be more confusion because this is on a popular Akamai/Linode guide https://www.linode.com/docs/guides/using-fail2ban-to-secure-your-server-a-tutorial/
I will report an issue on the guide to get that removed.
I had to run:
sudo fail2ban-client start
after that sudo fail2ban-client status Worked as expected.
Thank you.

I think in recent versions /var/run should be /run. Not sure that it makes any difference tough.

I am curious if fail2ban is supported by Debian 12? I tried running it by typing
sudo systemctl restart fail2ban
And it's giving this error
Failed to access socket path: /var/run/fail2ban/fail2ban.sock. Is fail2ban running?

No, not yet. But feel free to add a PR.

No, not yet. But feel free to add a PR.

I think i have found a work around. the problem stems from a missing line "sshd_backend = systemd" under  /etc/fail2ban/paths-debian.conf file.
after adding it, fail2ban works like normal under Debian 12.

Also on Debian 12. sudo fail2ban-client start does cause /var/run/fail2ban/fail2ban.sock (and fail2ban.pid) to be created.
The pid points to /usr/bin/python3 /usr/bin/fail2ban-server --async -b -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid --loglevel INFO --logtarget /var/log/fail2ban.log --syslogsocket auto
Strangely, running sudo fail2ban-client status kills that process, showing the original error reported in this ticket:
# fail2ban-client status
2024-07-20 17:19:02,233 fail2ban                [3399565]: ERROR   Failed to access socket path: /var/run/fail2ban/fail2ban.sock. Is fail2ban running?


Testnet with custom epochLength

Confirmation that the reconfiguration worked:
$ grep -R '"epochLength"' /private/var/folders/zh/ln41q4zs52x2fd61rxccmq640000gn/T/chairman/test-f5183437f11f5251 2> /dev/null
/private/var/folders/zh/ln41q4zs52x2fd61rxccmq640000gn/T/chairman/test-f5183437f11f5251/genesis.json:    "epochLength": 999,
/private/var/folders/zh/ln41q4zs52x2fd61rxccmq640000gn/T/chairman/test-f5183437f11f5251/genesis.spec.json:{"activeSlotsCoeff":0.25,"protocolParams":{"poolDeposit":0,"protocolVersion":{"minor":0,"major":0},"minUTxOValue":0,"decentralisationParam":0.7,"maxTxSize":16384,"minPoolCost":0,"minFeeA":0,"maxBlockBodySize":65536,"minFeeB":0,"eMax":18,"extraEntropy":{"tag":"NeutralNonce"},"maxBlockHeaderSize":1100,"keyDeposit":0,"nOpt":100,"rho":0,"tau":0,"a0":0},"genDelegs":{},"updateQuorum":5,"networkId":"Testnet","initialFunds":{},"maxLovelaceSupply":1000000000,"networkMagic":1893,"epochLength":999,"staking":{"pools":{},"stake":{}},"systemStart":"2020-11-25T08:18:11Z","slotsPerKESPeriod":129600,"slotLength":0.2,"maxKESEvolutions":60,"securityParam":10}

bors merge

bors r+?


nodejs: 20.18.0 -> 22.11.0

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I suspect this is the kind of changes which should wait for branchoff.

Please rebase. Otherwise LGTM. When does 18 go EOL, again?

According to https://github.com/nodejs/release#release-schedule, 22.x became the active LTS on 2024-10-29, and 18.x will go EOL on 2025-04-30.

Oh I thought the branch off would happen later. Let me rebase then

master branches off within the next few days, but since we already started the last staging-next before release, anything that goes into staging now won’t make it for 24.11. (Which is why the release schedule shows breaking changes as being permitted on that branch sooner than master.)

The nodejs_22 bump part of this should probably go to master so that 24.11 gets it.


Moved all the american countries in their own module

You might want to split the tests as well.

You might want to split the tests as well.

Ah you're right

well, we didn't do it after the "Europe" split... I wonder if it's necessary for this one... except that I'm expecting a "test_brazil.py" module pretty soon (ref: #187)

That was an idea but i you feel it is not needed you can ignore my comment.


The Splashscreen

Describe the Issue

It's a bit irritating to see the splashscreen animations everytime , we open the app , It should be opened only when the person opens the app for the first time . And if he logs out and opens the app again.
Would you like to work on the issue?
I want to resolve this issue .
@SAITARUN55 please assign this to me.

Before raising an issue, please check the previous issues and raise...this is a duplicate one, as it is already raised #50

@anjalisoni3655 u r also talking abt "welcome to Metro App"? Or only Splash screen

Yah , both , Sorry i did not check the issue #50 , I wanted to make these animations better . And to appear only once . Well , that progress bar is  not needed in the splashscreen , We can add a plane splashscreen with some animation . The app should direct to the homescreen directly and instantly .
The main purpose is to provide the travel details.
i  hope my points are clear now .


sh: 1: ./support/app_slug_compile.sh: Permission denied

-----> Deleting 57 files matching .slugignore patterns.
-----> PHP app detected
-----> Bootstrapping...
-----> Installing platform packages...
- php (7.3.11)
- ext-gd (bundled with php)
- apache (2.4.41)
- nginx (1.16.1)
-----> Installing dependencies...
Composer version 1.9.0 2019-08-02 20:55:32
Loading composer repositories with package information
Installing dependencies from lock file
Package operations: 23 installs, 0 updates, 0 removals
- Installing composer/installers (v1.7.0): Downloading (100%)
- Installing cweagans/composer-patches (1.6.7): Downloading (100%)
- Installing automattic/batcache (dev-master 81d6fbf): Downloading (100%)
- Installing ralouphie/getallheaders (3.0.3): Downloading (100%)
- Installing psr/http-message (1.0.1): Downloading (100%)
- Installing guzzlehttp/psr7 (1.6.1): Downloading (100%)
- Installing guzzlehttp/promises (v1.3.1): Downloading (100%)
- Installing guzzlehttp/guzzle (6.4.1): Downloading (100%)
- Installing mtdowling/jmespath.php (2.4.0): Downloading (100%)
- Installing aws/aws-sdk-php (3.120.0): Downloading (100%)
- Installing humanmade/s3-uploads (2.2.1): Downloading (100%)
- Installing predis/predis (v1.1.1): Downloading (100%)
- Installing wordpress/wordpress (5.2.3): Downloading (100%)
- Installing wp-cli/php-cli-tools (v0.11.11): Downloading (100%)
- Installing wp-cli/mustangostang-spyc (0.6.3): Downloading (100%)
- Installing symfony/finder (v4.3.8): Downloading (100%)
- Installing rmccue/requests (v1.7.0): Downloading (100%)
- Installing mustache/mustache (v2.12.0): Downloading (100%)
- Installing wp-cli/wp-cli (v2.4.0): Downloading (100%)
- Installing wpackagist-plugin/jetpack (7.9.1): Downloading (100%)
- Installing wpackagist-plugin/redis-cache (1.5.2): Downloading (100%)
- Installing wpackagist-plugin/secure-db-connection (1.1.6): Downloading (100%)
- Installing wpackagist-plugin/sendgrid-email-delivery-simplified (1.11.8): Downloading (100%)
Generating optimized autoload files
> ./support/app_slug_compile.sh
sh: 1: ./support/app_slug_compile.sh: Permission denied
Script ./support/app_slug_compile.sh handling the post-install-cmd event returned with error code 126
!     WARNING: A post-install-cmd script terminated with an error
!     ERROR: Dependency installation failed!
!
!     The 'composer install' process failed with an error. The cause
!     may be the download or installation of packages, or a pre- or
!     post-install hook (e.g. a 'post-install-cmd' item in 'scripts')
!     in your 'composer.json'.
!
!     Typical error cases are out-of-date or missing parts of code,
!     timeouts when making external connections, or memory limits.
!
!     Check the above error output closely to determine the cause of
!     the problem, ensure the code you're pushing is functioning
!     properly, and that all local changes are committed correctly.
!
!     For more information on builds for PHP on Heroku, refer to
!     https://devcenter.heroku.com/articles/php-support
!
!     REMINDER: the following warnings were emitted during the build;
!     check the details above, as they may be related to this error:
!     - A post-install-cmd script terminated with an error
!     Push rejected, failed to compile PHP app.
!     Push failed

reference #91


Feshly installed Jupyterlab Desktop: Failed to create session

Hi!
I freshly installed the App several minutes ago via the windows installer. After startup, I was prompted to install a python environment. I decided to use the bundled python installer. Now, in the setting the Bundled Python environment is selected. After restart, I clicked "New notebook" but now I see "Failed to create session! Error: Jupyter Server process terminated before the initialization completed".
What is the problem here?

Could you please provide logs as requested by the bug issue template?

Hi @krassowski,
sure! Below you find everything that was in the main.log file. Hope that helps.
Just to add some context, I have a running Python 3.10 installation that I use with PyCharm. Maye there is some conflict here?
[2023-02-25 17:38:41.372] [error] Failed to create free server Error: No default environment found!
at C:\JupyterLab\resources\app.asar\build\out\main\registry.js:191:32
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[2023-02-25 17:38:41.376] [error] (node:15404) UnhandledPromiseRejectionWarning: Error: No default environment found!
at C:\JupyterLab\resources\app.asar\build\out\main\registry.js:191:32
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
(Use JupyterLab --trace-warnings ... to show where the warning was created)
[2023-02-25 17:38:41.377] [error] (node:15404) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[2023-02-25 17:39:55.160] [error] Failed to create free server Error: No default environment found!
at C:\JupyterLab\resources\app.asar\build\out\main\registry.js:191:32
[2023-02-25 17:39:55.172] [error] (node:1908) UnhandledPromiseRejectionWarning: Error: No default environment found!
at C:\JupyterLab\resources\app.asar\build\out\main\registry.js:191:32
(Use JupyterLab --trace-warnings ... to show where the warning was created)
[2023-02-25 17:39:55.174] [error] (node:1908) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[2023-02-25 17:40:14.361] [error] Failed to create free server Error: No default environment found!
at C:\JupyterLab\resources\app.asar\build\out\main\registry.js:191:32
[2023-02-25 17:40:14.365] [error] (node:1088) UnhandledPromiseRejectionWarning: Error: No default environment found!
at C:\JupyterLab\resources\app.asar\build\out\main\registry.js:191:32
(Use JupyterLab --trace-warnings ... to show where the warning was created)
[2023-02-25 17:40:14.366] [error] (node:1088) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[2023-02-25 17:46:55.219] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 17:47:32.717] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 17:47:32.723] [error] (node:13916) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'protocol')
at new LabView (C:\JupyterLab\resources\app.asar\build\out\main\labview\labview.js:60:50)
at SessionWindow._loadLabView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:282:25)
at SessionWindow._updateContentView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:697:18)
at IpcMainImpl. (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:429:18)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
(Use JupyterLab --trace-warnings ... to show where the warning was created)
[2023-02-25 17:47:32.724] [error] (node:13916) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[2023-02-25 17:47:40.927] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 17:47:40.931] [error] (node:13916) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'protocol')
at new LabView (C:\JupyterLab\resources\app.asar\build\out\main\labview\labview.js:60:50)
at SessionWindow._loadLabView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:282:25)
at SessionWindow._updateContentView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:697:18)
at IpcMainImpl. (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:429:18)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[2023-02-25 17:47:40.932] [error] (node:13916) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
[2023-02-25 17:48:00.155] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 17:48:03.720] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 17:48:03.725] [error] (node:24988) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'protocol')
at new LabView (C:\JupyterLab\resources\app.asar\build\out\main\labview\labview.js:60:50)
at SessionWindow._loadLabView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:282:25)
at SessionWindow._updateContentView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:697:18)
at IpcMainImpl. (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:429:18)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
(Use JupyterLab --trace-warnings ... to show where the warning was created)
[2023-02-25 17:48:03.726] [error] (node:24988) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[2023-02-25 17:48:27.801] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 17:48:30.826] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 17:48:30.830] [error] (node:20888) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'protocol')
at new LabView (C:\JupyterLab\resources\app.asar\build\out\main\labview\labview.js:60:50)
at SessionWindow._loadLabView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:282:25)
at SessionWindow._updateContentView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:697:18)
at IpcMainImpl. (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:429:18)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
(Use JupyterLab --trace-warnings ... to show where the warning was created)
[2023-02-25 17:48:30.831] [error] (node:20888) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[2023-02-25 17:50:15.340] [error] (node:20888) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead
[2023-02-25 17:50:26.268] [error] Error: Installer Exit: 1
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\app.js:473:50)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 17:51:07.034] [error] Error: Installer Exit: 1
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\app.js:473:50)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 17:51:15.561] [error] Failed to create free server Error: No default environment found!
at C:\JupyterLab\resources\app.asar\build\out\main\registry.js:191:32
[2023-02-25 17:51:15.566] [error] (node:14728) UnhandledPromiseRejectionWarning: Error: No default environment found!
at C:\JupyterLab\resources\app.asar\build\out\main\registry.js:191:32
(Use JupyterLab --trace-warnings ... to show where the warning was created)
[2023-02-25 17:51:15.567] [error] (node:14728) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[2023-02-25 17:56:23.558] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 17:56:25.637] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 17:56:25.643] [error] (node:19424) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'protocol')
at new LabView (C:\JupyterLab\resources\app.asar\build\out\main\labview\labview.js:60:50)
at SessionWindow._loadLabView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:282:25)
at SessionWindow._updateContentView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:697:18)
at IpcMainImpl. (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:429:18)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
(Use JupyterLab --trace-warnings ... to show where the warning was created)
[2023-02-25 17:56:25.644] [error] (node:19424) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[2023-02-25 17:59:18.004] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 17:59:21.441] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 17:59:21.446] [error] (node:26416) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'protocol')
at new LabView (C:\JupyterLab\resources\app.asar\build\out\main\labview\labview.js:60:50)
at SessionWindow._loadLabView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:282:25)
at SessionWindow._updateContentView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:697:18)
at IpcMainImpl. (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:429:18)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
(Use JupyterLab --trace-warnings ... to show where the warning was created)
[2023-02-25 17:59:21.446] [error] (node:26416) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[2023-02-25 17:59:27.651] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 17:59:27.655] [error] (node:26416) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'protocol')
at new LabView (C:\JupyterLab\resources\app.asar\build\out\main\labview\labview.js:60:50)
at SessionWindow._loadLabView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:282:25)
at SessionWindow._updateContentView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:697:18)
at IpcMainImpl. (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:429:18)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[2023-02-25 17:59:27.657] [error] (node:26416) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
[2023-02-25 18:13:33.176] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 18:13:35.503] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 18:13:35.508] [error] (node:16444) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'protocol')
at new LabView (C:\JupyterLab\resources\app.asar\build\out\main\labview\labview.js:60:50)
at SessionWindow._loadLabView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:282:25)
at SessionWindow._updateContentView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:697:18)
at IpcMainImpl. (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:429:18)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
(Use JupyterLab --trace-warnings ... to show where the warning was created)
[2023-02-25 18:13:35.509] [error] (node:16444) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[2023-02-25 18:18:31.653] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 18:18:31.678] [error] (node:16444) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'protocol')
at new LabView (C:\JupyterLab\resources\app.asar\build\out\main\labview\labview.js:60:50)
at SessionWindow._loadLabView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:282:25)
at SessionWindow._updateContentView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:697:18)
at IpcMainImpl. (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:429:18)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[2023-02-25 18:18:31.679] [error] (node:16444) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
[2023-02-25 18:18:52.397] [error] (node:16444) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'workingDirectory')
at C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:835:55
[2023-02-25 18:18:52.398] [error] (node:16444) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 5)
[2023-02-25 18:18:52.392] [error] undefined
[2023-02-25 18:18:55.133] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 18:18:55.136] [error] (node:16444) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'protocol')
at new LabView (C:\JupyterLab\resources\app.asar\build\out\main\labview\labview.js:60:50)
at SessionWindow._loadLabView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:282:25)
at SessionWindow._updateContentView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:697:18)
at IpcMainImpl. (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:429:18)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[2023-02-25 18:18:55.137] [error] (node:16444) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)
[2023-02-25 18:24:28.969] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 18:24:38.841] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 18:24:38.846] [error] (node:17816) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'protocol')
at new LabView (C:\JupyterLab\resources\app.asar\build\out\main\labview\labview.js:60:50)
at SessionWindow._loadLabView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:282:25)
at SessionWindow._updateContentView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:697:18)
at IpcMainImpl. (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:429:18)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
(Use JupyterLab --trace-warnings ... to show where the warning was created)
[2023-02-25 18:24:38.847] [error] (node:17816) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[2023-02-25 18:27:33.157] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 18:27:51.448] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 18:27:53.957] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 18:27:53.962] [error] (node:16908) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'protocol')
at new LabView (C:\JupyterLab\resources\app.asar\build\out\main\labview\labview.js:60:50)
at SessionWindow._loadLabView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:282:25)
at SessionWindow._updateContentView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:697:18)
at IpcMainImpl. (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:429:18)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
(Use JupyterLab --trace-warnings ... to show where the warning was created)
[2023-02-25 18:27:53.962] [error] (node:16908) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[2023-02-25 18:28:15.721] [error] undefined
[2023-02-25 18:28:28.412] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 18:28:30.443] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 18:28:30.449] [error] (node:17944) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'protocol')
at new LabView (C:\JupyterLab\resources\app.asar\build\out\main\labview\labview.js:60:50)
at SessionWindow._loadLabView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:282:25)
at SessionWindow._updateContentView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:697:18)
at IpcMainImpl. (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:429:18)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
(Use JupyterLab --trace-warnings ... to show where the warning was created)
[2023-02-25 18:28:30.449] [error] (node:17944) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[2023-02-25 18:28:53.469] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 18:29:45.912] [error] (node:17476) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'workingDirectory')
at C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:835:55
(Use JupyterLab --trace-warnings ... to show where the warning was created)
[2023-02-25 18:29:45.913] [error] (node:17476) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[2023-02-25 18:29:45.915] [error] undefined
[2023-02-25 18:29:49.415] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 18:29:49.420] [error] (node:17476) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'protocol')
at new LabView (C:\JupyterLab\resources\app.asar\build\out\main\labview\labview.js:60:50)
at SessionWindow._loadLabView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:282:25)
at SessionWindow._updateContentView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:697:18)
at IpcMainImpl. (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:429:18)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[2023-02-25 18:29:49.421] [error] (node:17476) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
[2023-02-25 18:30:26.606] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 18:30:29.392] [error] Failed to start server Error: Jupyter Server process terminated before the initialization completed
at ChildProcess. (C:\JupyterLab\resources\app.asar\build\out\main\server.js:285:28)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
[2023-02-25 18:30:29.397] [error] (node:10628) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading 'protocol')
at new LabView (C:\JupyterLab\resources\app.asar\build\out\main\labview\labview.js:60:50)
at SessionWindow._loadLabView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:282:25)
at SessionWindow._updateContentView (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:697:18)
at IpcMainImpl. (C:\JupyterLab\resources\app.asar\build\out\main\sessionwindow\sessionwindow.js:429:18)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
(Use JupyterLab --trace-warnings ... to show where the warning was created)
[2023-02-25 18:30:29.398] [error] (node:10628) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)

@davidbbaumann can you try to launch the server manually using command prompt? It might show you why the server launch is failing. below are the commands on my test machine that you can follow.
C:\Users\IEUser>cd C:\Users\IEUser\AppData\Roaming\jupyterlab-desktop\jlab_server
C:\Users\IEUser\AppData\Roaming\jupyterlab-desktop\jlab_server>condabin\activate.bat
C:\Users\IEUser\AppData\Roaming\jupyterlab-desktop\jlab_server>conda.bat activate
(base) C:\Users\IEUser\AppData\Roaming\jupyterlab-desktop\jlab_server>python -m jupyterlab --no-browser --expose-app-in-browser --ServerApp.port=8888 --ServerApp.password="" --ServerApp.token="abcde" --LabApp.quit_button=False --JupyterApp.config_file_name="" --ContentsManager.allow_hidden=True

Hi @mbektas,
thanks for your support! Below you'll find the logs from the command prompt. It seems that the server is running now but unfortunately, the jupyter lab app still shows the error message.
(base) C:\Users\David Baumann\AppData\Roaming\jupyterlab-desktop\jlab_server>python -m jupyterlab --no-browser --expose-app-in-browser --ServerApp.port=8888 --ServerApp.password="" --ServerApp.token="abcde" --LabApp.quit_button=False --JupyterApp.config_file_name="" --ContentsManager.allow_hidden=True [W 2023-02-26 20:26:09.845 ServerApp] ServerApp.token config is deprecated in 2.0. Use IdentityProvider.token. [I 2023-02-26 20:26:09.902 ServerApp] Package jupyterlab took 0.0001s to import [I 2023-02-26 20:26:09.914 ServerApp] Package jupyter_server_fileid took 0.0108s to import [I 2023-02-26 20:26:09.999 ServerApp] Package jupyter_server_terminals took 0.0839s to import [I 2023-02-26 20:26:10.314 ServerApp] Package jupyter_server_ydoc took 0.3141s to import [I 2023-02-26 20:26:10.315 ServerApp] Package nbclassic took 0.0000s to import [W 2023-02-26 20:26:10.320 ServerApp] A_jupyter_server_extension_pointsfunction was not found in nbclassic. Instead, a_jupyter_server_extension_pathsfunction was found and will be used for now. This function name will be deprecated in future releases of Jupyter Server. [I 2023-02-26 20:26:10.320 ServerApp] Package notebook_shim took 0.0000s to import [W 2023-02-26 20:26:10.321 ServerApp] A_jupyter_server_extension_pointsfunction was not found in notebook_shim. Instead, a_jupyter_server_extension_paths` function was found and will be used for now. This function name will be deprecated in future releases of Jupyter Server.
[I 2023-02-26 20:26:10.330 ServerApp] jupyter_server_fileid | extension was successfully linked.
[I 2023-02-26 20:26:10.337 ServerApp] jupyter_server_terminals | extension was successfully linked.
[I 2023-02-26 20:26:10.344 ServerApp] jupyter_server_ydoc | extension was successfully linked.
[W 2023-02-26 20:26:10.348 LabApp] 'quit_button' is not found in LabApp, but it was found in both NotebookApp and ServerApp. This is likely a recent change. This config will only be set in ServerApp. Please check if you should also config these traits in NotebookApp for your purpose.
[W 2023-02-26 20:26:10.349 LabApp] 'quit_button' is not found in LabApp, but it was found in both NotebookApp and ServerApp. This is likely a recent change. This config will only be set in ServerApp. Please check if you should also config these traits in NotebookApp for your purpose.
[I 2023-02-26 20:26:10.358 ServerApp] jupyterlab | extension was successfully linked.
[I 2023-02-26 20:26:10.366 ServerApp] nbclassic | extension was successfully linked.
[I 2023-02-26 20:26:10.374 ServerApp] Writing Jupyter server cookie secret to C:\Users\David Baumann\AppData\Roaming\jupyter\runtime\jupyter_cookie_secret
[I 2023-02-26 20:26:11.150 ServerApp] notebook_shim | extension was successfully linked.
[I 2023-02-26 20:26:11.436 ServerApp] notebook_shim | extension was successfully loaded.
[I 2023-02-26 20:26:11.437 FileIdExtension] Configured File ID manager: ArbitraryFileIdManager
[I 2023-02-26 20:26:11.438 FileIdExtension] ArbitraryFileIdManager : Configured root dir: C:/Users/David Baumann/AppData/Roaming/jupyterlab-desktop/jlab_server
[I 2023-02-26 20:26:11.440 FileIdExtension] ArbitraryFileIdManager : Configured database path: C:\Users\David Baumann\AppData\Roaming\jupyter\file_id_manager.db
[I 2023-02-26 20:26:11.447 FileIdExtension] ArbitraryFileIdManager : Successfully connected to database file.
[I 2023-02-26 20:26:11.447 FileIdExtension] ArbitraryFileIdManager : Creating File ID tables and indices.
[I 2023-02-26 20:26:11.487 FileIdExtension] Attached event listeners.
[I 2023-02-26 20:26:11.488 ServerApp] jupyter_server_fileid | extension was successfully loaded.
[I 2023-02-26 20:26:11.495 ServerApp] jupyter_server_terminals | extension was successfully loaded.
[I 2023-02-26 20:26:11.498 ServerApp] jupyter_server_ydoc | extension was successfully loaded.
[I 2023-02-26 20:26:11.500 LabApp] JupyterLab extension loaded from C:\Users\David Baumann\AppData\Roaming\jupyterlab-desktop\jlab_server\lib\site-packages\jupyterlab
[I 2023-02-26 20:26:11.501 LabApp] JupyterLab application directory is C:\Users\David Baumann\AppData\Roaming\jupyterlab-desktop\jlab_server\share\jupyter\lab
[I 2023-02-26 20:26:11.509 ServerApp] jupyterlab | extension was successfully loaded.

| | | |_ __  | | | | ___
| || | ' /  / _ |  / -)
_/| ./_,_,|____|
|_|
Read the migration plan to Notebook 7 to learn about the new features and the actions to take if you are using extensions.
https://jupyter-notebook.readthedocs.io/en/latest/migrate_to_notebook7.html
Please note that updating to Notebook 7 might break some of your extensions.
[I 2023-02-26 20:26:11.523 ServerApp] nbclassic | extension was successfully loaded.
[I 2023-02-26 20:26:11.526 ServerApp] Serving notebooks from local directory: C:\Users\David Baumann\AppData\Roaming\jupyterlab-desktop\jlab_server
[I 2023-02-26 20:26:11.526 ServerApp] Jupyter Server 2.3.0 is running at:
[I 2023-02-26 20:26:11.527 ServerApp] http://localhost:8888/lab?token=...
[I 2023-02-26 20:26:11.527 ServerApp]     http://<IP_ADDRESS>:8888/lab?token=...
[I 2023-02-26 20:26:11.528 ServerApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[I 2023-02-26 20:29:18.848 ServerApp] 302 GET / (@::1) 1.00ms
[I 2023-02-26 20:29:18.856 LabApp] 302 GET /lab? (@::1) 2.00ms
`
When I enter http://localhost:8888/lab into my browser address bar I see a Jupyter login page. There I entered the token from the command line "abcde". After that, I can access jupyter in my browser. Unfortunately, the jupyter desktop app still shows the same error ""Failed to create session! Error: Jupyter Server process terminated before the initialization completed".
Any ideas why this is the case?

I noticed from logs that your username has a space in it. conda doesn't support such environment paths. that is probably the source of the issue. can you follow these steps

Uninstall existing JupyterLabDesktopAppServer
Reinstall (you can find the installer in C:\JupyterLab\resources\env_installer\) but during installation choose another path that doesn't have a space in it. (something like C:\jlab_server)
Launch JupyterLab Desktop and go to Settings to change the default Python environment to your new installation path. instructions here.

Yes! That solved the issue! Didn't thought that this would be such a problem, thanks! :)
So I'm wondering, what would be the best way to handle multiple environments for different projects?

@davidbbaumann glad to hear that your issue is fixed now. you can create multiple environments using conda, and you can select them for your projects by following the instructions in user guide.


Refactor/graph ql trackerstore

The tests using rasa should still pass because even if rasa do not have the proper trackerstore it will default to the InMemory one
however if some tests check data using the trackerstore from rasa (conversation/ new utterances) they should not work
before merging : https://github.com/botfront/rasa-addons/pull/58 should have been merge and released

[x] I wrote tests for the feature
[ ] I documented the feature if needed

If the feature is a refactor, please explain why your way is better

Needs a migration.


BUG: Installing MEV-Boost with Custom Installation with Prysm doesn't wire fully

Describe the bug
Custom Installer wires to the Prysm Validator service correctly, but not to the Prysm Beacon Chain service. --http-mev-relay is missing in the config of Prysm's consensus client.
To Reproduce
Steps to reproduce the behavior:

Setup Prysm
Add Mev Boost with Custom Installation
Open Expert Mode on Prysm's consensus client, no --http-mev-relay in it

Expected behavior
--http-mev-relay get's added with the url to the MEV Boost service.
Desktop (please complete the following information):

OS: MacOS
Launcher version 1.0.0-rc.10

Node (please complete the following information):

OS: Ubuntu 22.04
Affected service: Prysm

I think I forgot to click on the consensus client to make it green (connected). This explains this issue but raises another one: When I didn't select the consensus client when installing MEV Boost, why was --enable-builder=true set on Prysm's validator service after install?

--enable-builder, --enable-validator-registration  Enables Builder validator registration APIs for the validator client to update settings such as fee recipient and gas limit. Note* this flag is not required if using proposer settings config file (default: false)
this has nothing to do with mev-boost


Sleeping pose

Hello, it would be awesome to have the "sleeping" pose implemented into the API:
Method setPose = Entity.class.getDeclaredMethod("setPose", EntityPose.class);
setPose.setAccessible(true);
setPose.invoke(npc, EntityPose.SLEEPING);
connection.sendPacket(new PacketPlayOutEntityMetadata(npc.getId(), npc.getDataWatcher(), false));

That... is a lot easier than I thought it would be. I'll implement this for the next version of NPCLib! :)


Program dashboard v2

As a learner, I'd like to see:

what programs I am enrolled in
what courses make up those programs
what my status is in those courses

Designs and Mockups

Program Details pane
Course cards revisited

Acceptance Criteria:

[ ] Add a Program tab to the dashboard
[ ] When the program tab is clicked, display all the programs the user is enrolled in
[ ] When a program is clicked, open the program drawer (program detail pane)
[ ] The program drawer lists all the courses in the program, with the learner's status
[ ] learner statuses:

[ ] if the learner isn't enrolled at all, display the "Enroll Today" card extension (if the course is open for enrollment)
[ ] if the learner is enrolled but hasn't paid, display the "Upgrade today" card extension (same as course dashboard)
[ ] if the learner is enrolled in the certificate track, display the appropriate tag (with no call to action)
[ ] if the learner has passed the course display the "course passed" label
[ ] if the learner has a course certificate, display the "course certificate" link
[ ] if the learner failed the course, go back to the "Enroll Today" card extension  (if the course is open for enrollment)

Out of Scope

Group the courses in the program detail pane according to required, elective, etc.

Couple questions regarding mostly the Program Details pane mock:

The red underline for active tab is the same red we use elsewhere (like on the Enroll buttons, etc.), correct? Assuming yes but there's not a view of this without a backdrop.
The dashboard seems slightly confused. Does My Courses work like the dashboard currently does (i.e., lists out all of your enrolled courses, regardless of program membership, but does not list out any programs)? That seems the most logical approach but the mockup has a program in it.
The program drawer is visible on the My Courses page. Also assuming that won't necessarily be the case? (This ties in a bit with the second item.)


MAC M1 下载依赖包报错

1、执行pip install -r requirements.txt报错
clang -DNDEBUG -fwrapv -O2 -Wall -fPIC -O2 -isystem /Users/wangjiahao/miniconda3/envs/chat/include -arch arm64 -fPIC -O2 -isystem /Users/wangjiahao/miniconda3/envs/chat/include -arch arm64 -I/private/var/folders/hj/rrkxr32x3mjbk4bxn8fjxg3w0000gn/T/pip-install-3ev1k7l0/xformers_6d0fb03ff6a6406099d94c30c5474f96/xformers/csrc -I/Users/wangjiahao/miniconda3/envs/chat/lib/python3.11/site-packages/torch/include -I/Users/wangjiahao/miniconda3/envs/chat/lib/python3.11/site-packages/torch/include/torch/csrc/api/include -I/Users/wangjiahao/miniconda3/envs/chat/lib/python3.11/site-packages/torch/include/TH -I/Users/wangjiahao/miniconda3/envs/chat/lib/python3.11/site-packages/torch/include/THC -I/Users/wangjiahao/miniconda3/envs/chat/include/python3.11 -c xformers/csrc/attention/attention.cpp -o build/temp.macosx-11.1-arm64-cpython-311/xformers/csrc/attention/attention.o -O3 -std=c++17 -fopenmp -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE="_clang" -DPYBIND11_STDLIB="_libcpp" -DPYBIND11_BUILD_ABI="_cxxabi1002" -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=0
clang: error: unsupported option '-fopenmp'
error: command '/usr/bin/clang' failed with exit code 1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for xformers
Running setup.py clean for xformers
Failed to build xformers
ERROR: Could not build wheels for xformers, which is required to install pyproject.toml-based projects

我是用这个方法解决
安装特殊
brew install llvm libomp
在项目环境中执行以下
export CC=/opt/homebrew/opt/llvm/bin/clang
export CXX=/opt/homebrew/opt/llvm/bin/clang++
export LDFLAGS="-L/opt/homebrew/opt/libomp/lib"
export CPPFLAGS="-I/opt/homebrew/opt/libomp/include"


Problem with WASM data served without MIME type

When the wasm data is served without a given MIME type the following error can be seen in the browser console:
TypeError: WebAssembly: Response has unsupported MIME type '' expected 'application/wasm'

This can be fixed by adding the correct MIME type when serving the file. If this is not possible falling back to WebAssembly.instantiate(...) instead of WebAssembly.instatiateStreaming(...) should help.

Not sure about falling back to WebAssembly.instantiate as it might affect how wasm works on certain browsers.

Then we need to open a ticket for OVH to fix this.

How is this OVH's problem..?

We are using a Webhosting service provided by OVH which means we just copy the static files there and their whatever webserver is serving the files. Having the correct MIME type requires configuration of the Webserver which is in this case managed by OVH.

Ahh, I see ... sorry I thought we just had VPSes from them.

Not sure about falling back to WebAssembly.instantiate as it might affect how wasm works on certain browsers.
@donpui , do we have more technical insight on that finding?

We already fall back to WebAssembly.instantiate for browsers that don't support instantiateStreaming
https://github.com/LeastAuthority/winden/blob/691a0e4557fcbccd548e5b4dafe8c8e01aa586e2/client/src/worker/index.ts#L153-L160
I can remove the branching for now so all browsers use instantiate (at least until the MIME type is added in the backend)

There is note:
https://developer.mozilla.org/en-US/docs/WebAssembly/JavaScript_interface/instantiate
Can't find exact issue or discussion about instantiateStreaming. Anyhow it will require quick retest if we don't have prioblem with Mobile browsers on IOS and Android.

There is note: https://developer.mozilla.org/en-US/docs/WebAssembly/JavaScript_interface/instantiate
Can't find exact issue or discussion about instantiateStreaming. Anyhow it will require quick retest if we don't have prioblem with Mobile browsers on IOS and Android.

The main concern raised there is that using WebAssembly.instantiate(...) is less efficient. As this only happens when loading the app it will most probably not hurt us.

Created a ticket at OVH to fix the problem on the server side: https://ca.ovh.com/manager/#/dedicated/support/tickets/6277237

As OVH is using Apache we can fix that behaviour with a .htaccess file deployed to the source directory having the following content:
AddType application/wasm .wasm


Add eslint rule: space before (anonymous) function parentheses

As discussed (reference: http://javascript.crockford.com/code.html#function) before, and in agreement with most code editors defaults.

No

@owennw - sorry, I'm closing this for now as per our discussion on Slack.


Enable distinct test with correct expectation.

I don't know why this integration test expectation got changed. This is the commit it got changed in https://github.com/quasar-analytics/quasar/commit/518dc93b61b337da23bbbd35237d60ec7578325e. SQL semantics along with the other integration tests confirm that the new expectation (which is also the expectation on master) is the one we want.

@rintcius yeah you're right. I really don't like this implicit select value though because it's not consistent with a query like select foo, bar from baz which will return an object with two fields. I think the user should have to explicitly select value in their query if they want to return the unwrapped values.

The reason this particular query is returning the wrapped values is because of implementation details wrt the order by. So the correct thing to do for now is to fix this test to be consistent with a version of the query without order by. But I would like to revisit our previous decision on implicit select value at some point.

To note, we have other tests on both master and next-major https://github.com/quasar-analytics/quasar/blob/next-major/it/src/main/resources/tests/shortCities.test which inconsistently expect results to be wrapped in a field name. So we need to audit all these tests and expect a consistent result.

@rintcius so I'm thinking about reopening this. On master we have an inconsistency where tests like shortCities.test and citiesByLargestZip.test returned object-wrapped results, while tests like the ones you pointed out return just the values. citiesByLargestZip.test is returning correct results for many connectors, modulo the object-wrapping. So rather than change the test expectation away from the one on master now, what do you think about keeping the test expectation the same as it is in maste and then later (after next-major is merged into master) we have a discussion with @jdegoes to determine a sane behavior that we will enforce consistently.

@alissapajer Yeah fixing this consistently after next-major has been merged into master & discussing with John sounds good.
With respect to what to do right now, maybe just open an issue & spend minimum dev time now?

@rintcius that sounds good to me. I'll reopen this since on master this test expects the values to be wrapped.

The argument for implicit SELECT VALUE is roughly as follows:
Ordinary SQL SELECT had no ability to return anything other than a table, so if you issued some query like SELECT COUNT(*) FROM foo, you always got the result boxed in an ordinal column:
-----
| 0 |
-----
| 3 |
-----

SQL2 has no such limitations, because it can return single values, sets of values, or traditional "records" (string-valued maps).
More than that, however, there are two obvious cases in which auto-boxing combined with SQL2 semantics produces extremely confusing results.
The first case is when users generate records directly. For example:
SELECT {"foo": foo, "bar": bar, "type": "baz"} FROM table

In this case, the user is explicitly constructing a record, and yet the entire result set is boxed in "0".
The other, far more common use case is in any sub select. For example, a sub select with IN:
... WHERE foo IN (SELECT bar FROM baz)

This class of queries, which work in ANSI SQL, fail in SQL2 with auto-boxing, because the semantics of SQL2 allow IN to work with records, so the fact that the sub select results in a dataset of records is not sufficient reason to auto-unbox (whereas, in SQL, all values are primitives so it can magically auto-infer this semantic).
A similar situation results in many other sub selects.
One can either require SELECT VALUE in such cases as these, which breaks compatibility with SQL in a way that causes simple SQL queries to not work at all in SQL2, or one can do implicit SELECT VALUE, which causes all sub select queries to work, but at the cost of sometimes unexpectedly returning data that is unboxed with the ordinal 0.
The reason I argue for implicit SELECT VALUE is that the user can easily restore the SQL semantic by using AS, e.g. SELECT foo AS `0` FROM bar, or by using JSON notation.
In addition, I'd further make the case that interpreting AS and , as row-builder expressions means that a, b or a AS b has a different semantic than a. i.e. the former should result in a record, because a keyword or column concatenation operator is being used, whereas the latter should not result in a record.
Those are just my initial thoughts though, I'm open to what others think on this issue.

A part of me likes the explicit SELECT VALUE (assuming it would be SELECT VALUE foo FROM bar), because that's a more principled solution when considering SQL2 in isolation (but yeah the disadvantage of breaking compat. with SQL is quite big).
Sounds unfortunate that we can't auto-unbox when doing sub-selects, since it looks like that could have opened the door to a more satisfactory solution (not breaking compatibility with SQL for sub selects & not unboxing when doing a select of a single column).
Makes me curious, what's the semantics of IN for records (and why)? Is it an essential part of how SQL2 operates?
FWIW I did a bit of experimentation:
// SETS
// works as expected
select foo from bar where foo in (1, 2)
// excerpt from generated mongo query:
//  { "$match": { "foo": { "$in": [NumberInt("1"), NumberInt("2")] } } }

// ARRAYS
// I expected this to work in the same way, but it didn't give any results.
select foo from bar where foo in [1, 2]
// excerpt shows that's it's wrapping the array in another `[..]`:
//  { "$match": { "foo": { "$in": [[NumberInt("1"), NumberInt("2")]] } } },

// RECORDS
// Was expecting this to not compile (if you wouldn't have said otherwise ;) )
select foo from bar where foo in {"baz": 42}
// also wrapping in `[...]` for records:
//  { "$match": { "foo": { "$in": [{ "baz": NumberInt("42") }] } } }


implemented connectivity check retries

Coverage decreased (-0.3%) to 27.925% when pulling 2004f1110a09a0193897061341e39e6a12f6cd32 on u9520107:enhance/connectivity-check into 408a39e57fca2c3fca69ad7187faf64df5cd3453 on ringcentral:master.


User Settings: Implement settings validators

As an extension developer, I want to be able to validate the newly set values for my user settings on the PAPI so I and others can use my settings and trust they are within expected constraints.

Add a way for extensions to validate changes to their settings so they and others can only set the settings to be expected values:

papi.settings.registerValidator(key, validatorCallback) - register a validator that the PAPI will call when someone tries to change that setting

type SettingValidator: (newValue, currentValue, key, allChanges) => Promise<boolean> where allChanges is an object representing all changes being made in one call to update settings. The object's keys are the setting keys being updated and values are objects with newValue and currentValue. Returns true if the new setting value is valid, false otherwise
When someone calls papi.settings.set, we should internally run the setting validator registered for that setting if one is available.

If a setting validator is not available, just let the set go through and update the value

Note: We decided that, between making absolutely sure getting a setting wouldn't blow up your code by being the wrong data type and making settings easy to set without tons of requirements, we should favor the second.
Should we not set if a validator is not available? That way, a setting will be the expected value. Disabling an extension wouldn't let you change it to some crazy value

Depends on #502
Settings & State Design Doc

Test Repo steps
In my test extension I registered a settings validator in the main.ts
const SettingItemsPerPageValidator: SettingValidator<'paranext-ext-testing.itemsPerPage'> = async (
newValue,
) => {
logger.debug(In SettingItemsPerPageValidator ${newValue});
return typeof newValue === 'number' && newValue >= 5 && newValue <= 20;
};
On the webview used the 'useSetting' hook to display the default.
Confirmed that registerValidation is triggered when user set invalid value.
Confirmed that error message is logged on the dev tools console log with message
'network.service.ts:228 Uncaught (in promise) Error: Error setting value for key 'paranext-ext-testing.itemsPerPage': Error: validation failed
at requestUnsafe (network.service.ts:228:32)'

Added another scenario where validation is not registered on Settings.
Behaves similar to issue #511 and #887 @tjcouch-sil


[SuSpect] Trimming via "exclude"

This is a running list of objects that have spectra in need of a shave. I will add "exclusion" regions to the json files after redshift corrections are complete.

[x] 08D
[x] 04S
[ ] 03bg
[ ] 02bo
[ ] 01ig
[ ] 01dc
[ ] 00H
[ ] 00E
[ ] 00cx
[ ] 99ex
[ ] 99em
[ ] 99ee
[ ] 99cq
[ ] 99br
[ ] 98fa
[ ] 98A
[ ] 97D
[ ] 97cy
[ ] 97cn
[ ] 97br
[ ] 96X
[ ] 96L
[ ] 94S
[ ] 91T
[ ] 90I
[ ] 90E
[ ] 89B
[ ] 86G
[ ] 83G

This issue was moved to astrocatalogs/supernovae#8


Machine  mode atomic extension tests?

The Atomic suite in this repository is labeled 'ua'. Are there any machine mode only Atomic extension compliance suite tests?

Other will correct me, for sure, but:
The only difference in a machine mode vs. user mode test for this is
whether this is executed in VM mode with address translation (with the
implication it could trap).
Since this test is in the unprivileged test suite, it shouldn't require
privileged resources (and, indeed, the tests themselves don't),  and
shouldn't cause traps (which require privileged mode resources).
So this may be in user mode test, but it should (or could) be operating in
a bare physical-only mode or under VM and either in Mmode or uMode.
Having said that: I would expect similar tests in the privileged test suite
that would add test that get page faults, etc.
On Sat, Feb 16, 2019 at 7:48 PM aprnath<EMAIL_ADDRESS>wrote:

The Atomic suite in this repository is labeled 'ua'. Are there any machine
mode only Atomic extension compliance suite tests?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/riscv/riscv-compliance/issues/47, or mute the thread
https://github.com/notifications/unsubscribe-auth/Ad96ptZhHDV-QEwquIWmAwpdyibSeUJDks5vONDxgaJpZM4a_WHl
.

The ua tests will be deprecated for now. They were directly borrowed from the riscv-tests repo for reference purposes. Dedicated tests for the A extension (machine, supervisor, user) are yet to be developed by the compliance group.


Push Notification on android

Hi @davodesign84, thanks for the great work 👍
I am trying to make push notification work for my react-native app. My push notifications work like a charm on ios but on Android, I have an issue.
I am using react-native-push-notification to get device token to be sent using Mixpanel.addPushDeviceToken(token). but the problem is I am only receiving a silent notification on my app when I use the mixpanel UI to send push notification which not the case when I am using third-party service to test push notification like PushWatchwith.
lets me know if you need more details

Hi @yjose
Push notification works fine with me on android without using react-native-push-notification  and without sending token Mixpanel.addPushDeviceToken(token)
I m just creating a profile with function
import DeviceInfo from 'react-native-device-info';       const deviceId = DeviceInfo.getDeviceId(); Mixpanel.identify(deviceId);

Adding this to the AndroidManifest.xml file fix my issue
<receiver android:name="com.mixpanel.android.mpmetrics.GCMReceiver"
                  android:permission="com.google.android.c2dm.permission.SEND" >
            <intent-filter>
                <action android:name="com.google.android.c2dm.intent.RECEIVE" />
                <action android:name="com.google.android.c2dm.intent.REGISTRATION" />
                <category android:name="com.myname.myapp" /> <!-- <-- replace with your package name  -->
            </intent-filter>
        </receiver>

@yjose its crashs and return
Unable to instantiate receiver com.mixpanel.android.mpmetrics.GCMReceiver:
java.lang.ClassNotFoundException: Didn't find class "com.mixpanel.android.mpmetrics.GCMReceiver"
 on path: DexPathList