Spring Boot cannot build a Java 17 native Docker image because native-image is failing to unresolved method

What happened?
I have a simple Spring Boot application using Java 17 and Maven with the following dependencies I would like to build using spring-boot-maven-plugin as a native Docker image. The parent version is 2.6.0:

org.springframework.boot:spring-boot-starter-data-r2dbc
org.springframework.boot:spring-boot-starter-webflux
org.springframework.boot:spring-boot-starter-actuator
org.springframework.experimental:spring-native (from org.springframework.experimental)
io.r2dbc:r2dbc-postgresql

What were you attempting to do?
I attempt to build a native Docker image using Packeto (that uses GraalVM) using the following command:
./mvnw.cmd spring-boot:build-image -DskipTests

What did you expect to happen?
I expect the image is built with no error.
What was the actual behavior? Please provide log output, if possible.
Here is a full log output: log.txt
The image cannot be built and the following error is displayed:
[INFO]     [creator]     [/layers/paketo-buildpacks_native-image/native-image/sandbox.Application:174]    classlist:   6,368.93 ms,  0.96 GB
[INFO]     [creator]     [/layers/paketo-buildpacks_native-image/native-image/sandbox.Application:174]        (cap):   2,071.22 ms,  0.96 GB
[INFO]     [creator]     [/layers/paketo-buildpacks_native-image/native-image/sandbox.Application:174]        setup:   6,094.75 ms,  0.96 GB
[INFO]     [creator]     [/layers/paketo-buildpacks_native-image/native-image/sandbox.Application:174]     analysis:  10,400.77 ms,  1.68 GB
[INFO]     [creator]     Fatal error:com.oracle.graal.pointsto.util.AnalysisError$ParsingError: Error encountered while parsing org.springframework.beans.BeanUtils.instantiateClass(java.lang.Class)
[INFO]     [creator]     Parsing context:
[INFO]     [creator]        at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:141)
[INFO]     [creator]        at org.springframework.boot.context.properties.bind.JavaBeanBinder.create(JavaBeanBinder.java:67)
[INFO]     [creator]        at org.springframework.boot.context.properties.bind.Binder.create(Binder.java:366)

...
[INFO]     [creator]     Caused by: com.oracle.graal.pointsto.util.AnalysisError: parsing had failed in another thread
[INFO]     [creator]            at com.oracle.graal.pointsto.util.AnalysisError.shouldNotReachHere(AnalysisError.java:153)
[INFO]     [creator]            at com.oracle.graal.pointsto.meta.AnalysisMethod.ensureGraphParsed(AnalysisMethod.java:656)
[INFO]     [creator]            at com.oracle.graal.pointsto.phases.InlineBeforeAnalysisGraphDecoder.lookupEncodedGraph(InlineBeforeAnalysis.java:182)
[INFO]     [creator]            at jdk.internal.vm.compiler/org.graalvm.compiler.replacements.PEGraphDecoder.doInline(PEGraphDecoder.java:1120)
[INFO]     [creator]            at jdk.internal.vm.compiler/org.graalvm.compiler.replacements.PEGraphDecoder.tryInline(PEGraphDecoder.java:1103)
[INFO]     [creator]            at jdk.internal.vm.compiler/org.graalvm.compiler.replacements.PEGraphDecoder.trySimplifyInvoke(PEGraphDecoder.java:961)
[INFO]     [creator]            at jdk.internal.vm.compiler/org.graalvm.compiler.replacements.PEGraphDecoder.handleInvoke(PEGraphDecoder.java:915)
[INFO]     [creator]            at jdk.internal.vm.compiler/org.graalvm.compiler.nodes.GraphDecoder.processNextNode(GraphDecoder.java:791)
[INFO]     [creator]            at com.oracle.graal.pointsto.phases.InlineBeforeAnalysisGraphDecoder.processNextNode(InlineBeforeAnalysis.java:242)
[INFO]     [creator]            at jdk.internal.vm.compiler/org.graalvm.compiler.nodes.GraphDecoder.decode(GraphDecoder.java:532)
[INFO]     [creator]            at jdk.internal.vm.compiler/org.graalvm.compiler.replacements.PEGraphDecoder.decode(PEGraphDecoder.java:787)
[INFO]     [creator]            at com.oracle.graal.pointsto.phases.InlineBeforeAnalysis.decodeGraph(InlineBeforeAnalysis.java:99)
[INFO]     [creator]            at com.oracle.graal.pointsto.flow.MethodTypeFlowBuilder.parse(MethodTypeFlowBuilder.java:171)
[INFO]     [creator]            at com.oracle.graal.pointsto.flow.MethodTypeFlowBuilder.apply(MethodTypeFlowBuilder.java:321)
[INFO]     [creator]            at com.oracle.graal.pointsto.flow.MethodTypeFlow.createTypeFlow(MethodTypeFlow.java:293)
[INFO]     [creator]            ... 12 more
[INFO]     [creator]     Caused by: org.graalvm.compiler.java.BytecodeParser$BytecodeParserError: com.oracle.graal.pointsto.constraints.UnresolvedElementException: Discovered unresolved method during parsing: org.springframework.beans.BeanUtils$Kot
linDelegate.instantiateClass(java.lang.reflect.Constructor, java.lang.Object[]). To diagnose the issue you can use the --allow-incomplete-classpath option. The missing method is then reported at run time when it is accessed the first time.
[INFO]     [creator]            at parsing org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:196)
[INFO]     [creator]            at jdk.internal.vm.compiler/org.graalvm.compiler.java.BytecodeParser.throwParserError(BytecodeParser.java:2624)
[INFO]     [creator]            at com.oracle.svm.hosted.phases.SharedGraphBuilderPhase$SharedBytecodeParser.throwParserError(SharedGraphBuilderPhase.java:107)

...
[INFO]     [creator]     Caused by: com.oracle.graal.pointsto.constraints.UnresolvedElementException: Discovered unresolved method during parsing: org.springframework.beans.BeanUtils$KotlinDelegate.instantiateClass(java.lang.reflect.Constructor, ja
va.lang.Object[]). To diagnose the issue you can use the --allow-incomplete-classpath option. The missing method is then reported at run time when it is accessed the first time.
[INFO]     [creator]            at com.oracle.svm.hosted.phases.SharedGraphBuilderPhase$SharedBytecodeParser.reportUnresolvedElement(SharedGraphBuilderPhase.java:307)
[INFO]     [creator]            at com.oracle.svm.hosted.phases.SharedGraphBuilderPhase$SharedBytecodeParser.handleUnresolvedMethod(SharedGraphBuilderPhase.java:298)
[INFO]     [creator]            at com.oracle.svm.hosted.phases.SharedGraphBuilderPhase$SharedBytecodeParser.handleUnresolvedInvoke(SharedGraphBuilderPhase.java:252)
[INFO]     [creator]            at jdk.internal.vm.compiler/org.graalvm.compiler.java.BytecodeParser.genInvokeStatic(BytecodeParser.java:1677)
[INFO]     [creator]            at jdk.internal.vm.compiler/org.graalvm.compiler.java.BytecodeParser.genInvokeStatic(BytecodeParser.java:1652)
[INFO]     [creator]            at jdk.internal.vm.compiler/org.graalvm.compiler.java.BytecodeParser.processBytecode(BytecodeParser.java:5419)
[INFO]     [creator]            at jdk.internal.vm.compiler/org.graalvm.compiler.java.BytecodeParser.iterateBytecodesForBlock(BytecodeParser.java:3477)
[INFO]     [creator]            ... 39 more

I assume there is something wrong with native-image buildpack since the following lines can be found in the log:
[INFO]     [creator]     # Printing build artifacts to: /layers/paketo-buildpacks_native-image/native-image/sandbox.Application.build_artifacts.txt
[INFO]     [creator]     Error: Image build request failed with exit status 1
[INFO]     [creator]     unable to invoke layer creator
[INFO]     [creator]     unable to contribute native-image layer
[INFO]     [creator]     error running build
[INFO]     [creator]     exit status 1
[INFO]     [creator]     ERROR: failed to build: exit status 1

Build Configuration
I use paketobuildpacks (I have no idea what should be specified as a "platform") and here is the full build configuration:
<build>
	<finalName>spring-boot-reactive</finalName>
	<plugins>
		<plugin>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-maven-plugin</artifactId>
			<configuration>
				<image>
					<builder>paketobuildpacks/builder:tiny</builder>
					<env>
						<BP_BOOT_NATIVE_IMAGE>1</BP_BOOT_NATIVE_IMAGE>
						<BP_BOOT_NATIVE_IMAGE_BUILD_ARGUMENTS>-Dspring.spel.ignore=true</BP_BOOT_NATIVE_IMAGE_BUILD_ARGUMENTS>
					</env>
					<buildpacks>
						<buildpack>gcr.io/paketo-buildpacks/java-native-image:5.12.0</buildpack>
					</buildpacks>
				</image>
			</configuration>
		</plugin>

	</plugins>
</build>

What buildpacks are you using? Please include versions.
I use java-native-image of version 5.12.0 as long as it is compatible with GraalVM supporting Java 17.
What builder are you using? If custom, can you provide the output from `pack
inspect-builder `?
I use paketobuildpacks/builder:tiny as shown in the configuration above.
Can you provide a sample app or relevant configuration (buildpack.yml,
nginx.conf, etc.)?
I have no other configuration.

A side question: Does exist a compatibility matrix between Java version, GraalVM version, individual paketo-buildpacks? How is bellsoft-liberica relevant to them?

Native compilation issues are not typically buildpack problems. The buildpack is only responsible for installing and running the native-image tool with some default options that a user can override.
If a compilation problem occurs, it's typically something with the application's code or dependencies.
There are a couple of good sanity checks you can run to help narrow down where the problem exists:

Strip out as much as possible from your application or download a minimal base app from https://start.spring.io and build that. If that works correctly, the problem lies somewhere in the code or dependencies that you've added.

Use the instructions here to build. This does require you to install the native image tools on your machine, so make sure you are installing the exact same versions as being installed by the buildpack. Then build and see if the build works. If this build works, but buildpacks do not, then see if you can put together a reproduction app you can share. I'd be happy to take a look and see what is going on.

Final note. You didn't mention the version of Spring Native that you're using but my understanding is that Spring Native 0.10.x does not support Java 17, but that the next release should.

Thanks for the quick reaction. Yes, I used Spring Native version of 0.10.0 but also 0.11.0-M1 - it results in the very same error. I try to create a task on their repository.

OK, I'm going to close out this issue. If it turns out to be something buildpack related, feel free to reopen this.


Drop php <7.4 support, symfony <4.4, add php 8.1 to pipeline

This PR:

[x] Drops php < 7.4 support
[x] Adds PHP 8.1 to pipeline
[x] Updates PhpParser to 4.13 as it supports PHP 8.1

p.s. It's time to move forward

@exussum12 you can merge it if you have a time to rebase and resolve conflicts. Or we can close your PR in favor of this one.

@exussum12 could you please review this one so it can be merged and released? Thank you.


[Request] Beheading Module

Describe the feature you'd like to have added
Self-explanatory. Not many mods handle Beheading anymore, or are difficult to find, I recently suggested adding Mob Grinding Utils strictly for lack of Beheading, but giving us a module for our sword/axe too? might help a lot, especially since most players will be using your Clicker and swords to make a mob farm anyway.
I suggest making it so that the module can be either upgraded to higher levels of Beheading just with weapon tiers or better yet both that and the ability to enchant the module with Efficiency or Sharpness first before adding it gives us higher levels of Beheading, in case for some reason a person enjoys Blazegold or Celestagem tier more than the Eclipse Alloy tier, for looks, or if Eclipse Alloy tier is limited to Beheading III, but Apotheosis allows for your module to reach Beheading X.
Additional information
No response

I think I'll leave this one off for now, but thanks for the suggestion!


[K32W] Save PDM to external flash on the DK6 board

Problem
What is being fixed?
Decrease the usage of the internal flash space (640K).
Change overview
Move Persistent Data Manager (PDM) from the internal flash to the external flash available on the DK6 development board.
Basically, we saved 32.5K of internal flash.
Testing
Created a large application (almost 640K) and run it ok. Before, it was impossible to run it because only PDM required 32.5 of the internal flash.

Can you please fill out the PR template? Thanks!

Done.


Visualforce redirect to Edit page refreshes page infinitely in Lightning Experience

You can use the NPSP Visualforce page HH_ManageHHAccount to override the Account Edit button. If you are in Lightning Experience and then click on the Account Edit button the screen goes into a loop and continually refreshes. i.e. The Visualforce page tries to redirect to the Edit page but constantly refreshes. The Edit override works correctly in Salesforce classic.
I've seen a similar known issue, but that's for View override (https://success.salesforce.com/issues_view?id=a1p3A0000001BYwQAM). This could be the same underlying issue but raising in case they are unrelated.
Steps to reproduce:

On Account, override the Edit button with the Visualforce page npsp__HH_ManageHHAccount
Switch to Lightning Experience
Select an account and click the Edit button
Page refreshes continually

'Never override the edit button. You use the manage household button'
https://powerofus.force.com/articles/Resource/NPSP-Enable-the-Manage-Household-Button


Get quality in p like 180p 240p 360p

How get quality of video in format 180p, 240p,... etc . I use track selection and I get format.width and format.hight and I need get like youtube format . Thanks.

Assuming your content is progressive (which it presumably is if you want the 'p' suffix), you should just be able to do:
String heightWithP = format.height + "p";

i.e. 180p content is just content with 180 lines, i.e. a height of 180.


Torch7/LeNet: use cudnn when available

On MNIST (1x28x28, 45k training images, 15k validation images),
with batch size of 64.
Training time for 20 epochs:
Original: 8m26s
With CuDNN: 3m7s

Will help for #339

Works for me.
On MNIST (1x28x28), 7.5k training images, 2.5k validation images)
Training time for 30 epochs:
Original: 1m14s
With cuDNN v3: 39s


First run telemetry notice

Print telemetry notice on first run.
Conditions: In Cloud Shell AND have not run previously (no ~/.azd/first-run file present)

Disable telemetry for the command
Print telemetry notice
Create ~/.azd/first-run file

Will need some help from @weikanglim to ensure that telemetry is properly disabled.

Straightforward way is to update initialize in telemetry.go. If initialize returns nil for TelemetrySystem, telemetry is disabled.
Do you expect the telemetry notice to be printed before, or after the command execution?


fix: accept neg lock ID for migration

Closes: #XXX
What is the purpose of the change
This is not ideal, but we are at a point where frontend QA is blocked on getting unlocked migration message working. Frontend is not able to create the message with a zero lock ID, so I added this hack to accept negative numbers to indicate the same thing. This should be non problematic since it is only used to route the message where it needs to go.
Its gross and hacky, but we need as much time as possible with frontend working 100 percent to ensure we hit all QA targets.
Jon tested this on frontend and it works.

@stackman27 according to Jon it did not


Implement simple base class

Codecov Report

Merging #68 (57bc451) into master (a235938) will increase coverage by 0.12%.
The diff coverage is 82.92%.

@@            Coverage Diff             @@
##           master      #68      +/-   ##
==========================================
+ Coverage   35.48%   35.60%   +0.12%
==========================================
  Files          48       49       +1
  Lines       21690    21744      +54
==========================================
+ Hits         7697     7743      +46
- Misses      13993    14001       +8

Impacted Files
Coverage Δ

resqpy/olio/xml_et.py
65.19% <25.00%> (-0.45%)
:arrow_down:

resqpy/olio/base.py
84.72% <84.72%> (ø)

resqpy/well.py
29.87% <100.00%> (-0.43%)
:arrow_down:

resqpy/model.py
60.79% <0.00%> (ø)

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 a235938...57bc451. Read the comment docs.


talon command scope delimiters not quite correct

foo:
    insert("foo\n")

run clone command fine. result:
foo:
    insert("foo\n") foo:
    insert("foo\n")

cc @AndreasArvidsson

I know what the problem is. Just need to add an insertion delimiter.


dash-lyft-explorer example does not work after following README instructions (installed incompatible versions)

App name
dash-lyft-explorer example
Description of bug
Followed readme (conda env + pip for requirements), crashed with:
[2024-01-01 08:37:22 -0600] [64238] [ERROR] Exception in worker process
Traceback (most recent call last):
  File "/home/aaron/anaconda3/envs/dash-lyft-explorer/lib/python3.7/site-packages/gunicorn/arbiter.py", line 609, in spawn_worker
    worker.init_process()
  File "/home/aaron/anaconda3/envs/dash-lyft-explorer/lib/python3.7/site-packages/gunicorn/workers/base.py", line 134, in init_process
    self.load_wsgi()
  File "/home/aaron/anaconda3/envs/dash-lyft-explorer/lib/python3.7/site-packages/gunicorn/workers/base.py", line 146, in load_wsgi
    self.wsgi = self.app.wsgi()
  File "/home/aaron/anaconda3/envs/dash-lyft-explorer/lib/python3.7/site-packages/gunicorn/app/base.py", line 67, in wsgi
    self.callable = self.load()
  File "/home/aaron/anaconda3/envs/dash-lyft-explorer/lib/python3.7/site-packages/gunicorn/app/wsgiapp.py", line 58, in load
    return self.load_wsgiapp()
  File "/home/aaron/anaconda3/envs/dash-lyft-explorer/lib/python3.7/site-packages/gunicorn/app/wsgiapp.py", line 48, in load_wsgiapp
    return util.import_app(self.app_uri)
  File "/home/aaron/anaconda3/envs/dash-lyft-explorer/lib/python3.7/site-packages/gunicorn/util.py", line 371, in import_app
    mod = importlib.import_module(module)
  File "/home/aaron/anaconda3/envs/dash-lyft-explorer/lib/python3.7/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/aaron/Documents/workspace/NEW_DIBS/dash-sample-apps/apps/dash-lyft-explorer/app.py", line 231, in <module>
    dbc.FormGroup(
  File "/home/aaron/anaconda3/envs/dash-lyft-explorer/lib/python3.7/site-packages/dash_bootstrap_components/__init__.py", line 51, in __getattr__
    f"{name} was deprecated in dash-bootstrap-components version "
AttributeError: FormGroup was deprecated in dash-bootstrap-components version 1.0.0. You are using 1.5.0. For more details please see the migration guide: https://dash-bootstrap-components.opensource.faculty.ai/migration-guide/
[2024-01-01 08:37:22 -0600] [64238] [INFO] Worker exiting (pid: 64238)
Done reverse indexing in 0.0 seconds.

See error message complaining about incompatible versions.
How to replicate the bug
Follow README.md instructions for example app.
Other notes

Hi, I am a simply user of Dash. I just downloaded the sample and had the same problem as you had.
The problem seems to be due to an upgraded version on dash-bootstrap-components which has some incompatibilities with the version originally used for building the package. By executing this command it should be solved
``pip install "dash-bootstrap-components<1


Windows/Linux/Docker??

Hi all!
I'm interested on this Zenbot, but before downloading & installing it I just wanted to ask your opinion for the most suitable platform for it. My both PC's have Windows 10, so I don't have any Linux machines available, and no any other need for Linux either. Naturally I could run some Linux distro on VM, if it gives any benefit over running it directly in Windows. I'm surely not a Linux expert in ways, but I'm think that with loooots of Googling I could manage it.
Docker is totally new for me, just checked from Wikipedia what it even is ;=)
So, what's your opinion on this, should this newbie use Win10, Win10 + (some? )Linux VM, or Win10 + Docker??

Docker probably, but to be honest, I generally do not understand anything, especially where to insert api keys, how to properly start the docker, I'm new, too. Here if on youtube someone has hung a installation visually or on screens would be abruptly

Ok, thanks, but why? I would like to understand pros/cons of all these options, if there really is any real life difference between them.

Now that I think, maybe it would be best to use Linux anyway. I'm surely going for some cloud platform, and Linux seems to be the cheapest option by far. Digital Ocean for example offers a Linux VM's starting from 5$/month!  Ok, maybe a desktop usage would require that 10$ version with 1MB of memory, but it's still quite cheap.
But does it matter at all which distro I choose? Does it make any difference from Zenbot point of view if I use Ubuntu, CentOS, Fedora or Debian?

@jasurakk you don't need to choose a specific OS. If you use Docker you can keep your favourite one since the options remain in x86 and ARM.
It lacks documentation and I'm completing it but you only need to 'volume' your conf.js file. It will be updated on my docker hub @mluis
Enjoy :)

Ok, thanks mluis! :=)


[explogs] refactor experiment scripts

[x] fix logo at footer
[x] decide what to do with mermaid js flowcharts since GitHub's Markdown doesn't render them
[x] rename experiments folders
[ ] write top-level script to generate PTS files prior to calling Python "vizzes". This includes a previous re-run to check if they are indeed working
~[ ] write data prep section on top-level to pull M/F dataset from DVC (TBD)~
[x] create requirements.txt or write a check_dependencies.sh if there isn't one yet

Decide to leave dvc pull for the user at execution time rather than placing on a script. I can't actually put it into a docker file straightaway because the Google Drive API is annoying with all those auth steps involving copy-and-pasting some URLs.  Same for embedding into a .sh file. Instructions are inside README.md

I'll assume PTS are generated successfully from my last run (except for PROPOR's) and close this issue :)


Message dialog overlay is not displayed

Hello,
I some cases when the message dialog is shown using ShowMessageAsync() method the dark overlay is not displayed. In my own project it happens a lot of times, but is hard to reproduce all cases because I use a dll library, threads, ASP.NET Identity for login, large code file,... I have found a simple example when it happens, may be fixing this bug solves all cases.
This is my environment:

Windows 8.1 Pro (64 bits)
Visual Studio Ultimate 2013 Update 4

I'm using Mahapps stable libraies:

Mahapps.Metro <IP_ADDRESS>
Mahapps.Metro.SimpleChildWindow <IP_ADDRESS>

Here is the sample code to reproduce de issue (I don't know why, but I can't uplad it to this post):
http://1drv.ms/1JJWO5G
You can follow the 4 steps in the application, one for each button, and you will see this 3 message dialogs:
When step 1 button is clicked (fine):

When step 2 (show child window) and 3 buttons are clicked (improvable, the displayed overlay is because the child window is shown, but message dialog overlay is not displayed):

And when the step 4 button is clicked (wrong):

Due to SimpleChildWindow is involved, I will open another issue in it's repository.

should be fixed with MahApps.Metro.SimpleChildWindow v1.3.0 and MahApps.Metro v1.2.3

Thank you very much @punker76 I will try it on monday with my solution


Improve README.md

Add install section, fix src of the script and other format.

Thanks for that!


[Fix]Fixed the issue where tensor would cause training to exit with a…

…n error on different devices.
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Fixed the issue where tensor would cause training to exit with an error on different devices.
Modification
Modified mmdet\models\task_modules\assigners\point_assigner.py file.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects, like MMDet or MMPreTrain.
The documentation has been modified accordingly, like docstring or example tutorials.

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

@LRJKD Please fix the lint

请修复棉绒

ok

请修复棉绒

@hhaAndroid

Completed @hhaAndroid


Data Formatting

I am having some trouble getting my own data into the software, do you have an example .csv you could share, thanks in advance

Hi @ctparsons,
There are two examples in the repository: mice dataset and human dataset.
Hope this helps.

@JelenaBanjac
That was just what I needed, everything appears to be working well now, thank you.


Issue upgrading 1.7.10-b.10 to 1.7.0-rc.1 via CLI GPM

➜ bin/gpm selfupgrade

GPM Releases Configuration: Testing

Grav v1.7.0-rc.1 is now available [release date: Thu Nov  7 00:52:29 2019].
You are currently using v1.7.0-beta.10.
Would you like to read the changelog before proceeding? [y|N] n
Would you like to upgrade now? [y|N] y

Preparing to upgrade to v1.7.0-rc.1..
  |- Downloading upgrade [5.1M]...     0%
In Response.php line 316:

  Error while trying to download (code: ):

self-upgrade [-f|--force] [-y|--all-yes] [-o|--overwrite]

Actually this is fixed in RC.1 but won't be resolved until you have RC.1 already installed: https://github.com/getgrav/grav/issues/2681


v3 and v4 docs are unavailable

Describe the bug
As of very recently (I think max 2-3 days) the docs for v3 and v4 lead to an error page:

v3: https://tanstack.com/query/v3/docs/framework/react/overview
v4: https://tanstack.com/query/v4/docs/framework/react/overview

Your minimal, reproducible example
n/a
Steps to reproduce
n/a
Expected behavior
n/a
How often does this bug happen?
None
Screenshots or Videos

Platform
n/a
Tanstack Query adapter
None
TanStack Query version
n/a
TypeScript version
No response
Additional context
No response

we're aware. it's related to a recent refactoring of the docs page. @lachlancollins fyi

Fixed in #7102 and #7103


NetNewsWire for Mac should use NNW blue instead of system accent color

When you use the system blue accent color in light mode on the Mac, it looks pretty decent.  Switch to darkmode and the system blue is off compared to the NNW blue we use in darkmode.  Use any other system accent color besides gray, and things look real weird.
On iOS we use a NNW blue for our accent color.  I think it makes the NNW UI look more cohesive when the unread indicators and cell selection state color match the color used in the article view.

Before:

After:

On my machine I use a non-blue accent color. Is it possible to detect when it’s set to blue and then use a different color only in that case?
For reference, here’s my machine:

I don't think I can reliably detect the blue.  I could hard code the RGB values, but they might not be the same between OS releases.
I was suggesting that we ignore the accent colors all together, but I now see that isn't very Mac like.  Instead, maybe embracing the accent colors a little more is what is needed to stop the clashing colors between the table view selections and the article?

I'm not completely sold on the idea though.

The coloring looks like a bit much in the examples I gave.  It would be better if didn't have the article title in the accent color.  I'll mock that up real quick.

I think this might work.

I can see removing the blue from the title. I’m not sure about using the accent color for other links. That might be more orange than I actually want.
But maybe not?
I’ll think about this some more.

I pushed the code to a feature branch so that you could try it out with different colors and see if it grows on you.  The branch is accent-color-experimental.
We might be able to tone down the accent color in the article view if it is too distracting.  We could increase brightness or decrease brightness.

Here are some screenshots where we lighten the accent color 25% in dark mode and darken it 25% in light mode.  This decreases the amount of contrast between the links and regular text, making it pop out less at the user.

It seems to do a decent job of toning even the most garish of accent colors.
Code is in the repo if you get time to check it out.

Opacity of the article accent color is currently set at 75%.  You can mess with that in the CSS file to change how much the accent color pops.

This has been implemented.  We can open another issue if we don't like how it as done.


It shows that the resource was stopped successfully, but the azure redis instance was not deleted

Describe the bug

Steps to reproduce

Add a template with source https://github.com/walrus-catalog-sandbox/terraform-azure-redis.
Using the template to create a  resource.
Stop the resource while the azure redis instace is being created.
Check the resource run status.
Check the redis instance status on the azure console.

Result

It shows that the stop was successful and the resource was destroyed.

2024-03-08T06:47:20.394Z [INFO]  Terraform version: 1.5.7
2024-03-08T06:47:20.394Z [INFO]  Go runtime version: go1.20.7
2024-03-08T06:47:20.394Z [INFO]  CLI args: []string{"/bin/terraform", "init", "-no-color"}
2024-03-08T06:47:20.394Z [INFO]  Loading CLI configuration from /root/.terraformrc
2024-03-08T06:47:20.395Z [INFO]  CLI command args: []string{"init", "-no-color"}

Initializing the backend...

Successfully configured the backend "http"! Terraform will automatically
use this backend unless the backend configuration changes.
Initializing modules...
Downloading git::https://github.com/walrus-catalog-sandbox/terraform-azure-redis?ref=main for az-redis...
- az-redis in .terraform/modules/az-redis

Initializing provider plugins...
- Finding hashicorp/random versions matching ">= 3.5.1"...
- Finding hashicorp/azurerm versions matching ">= 3.88.0"...
- Installing hashicorp/random v3.6.0...
- Installed hashicorp/random v3.6.0 (unauthenticated)
- Installing hashicorp/azurerm v3.94.0...
- Installed hashicorp/azurerm v3.94.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Warning: Incomplete lock file information for providers

Due to your customized provider installation methods, Terraform was forced to
calculate lock file checksums locally for the following providers:
  - hashicorp/random

The current .terraform.lock.hcl file only includes checksums for linux_arm64,
so Terraform running on another platform will fail to install these
providers.

To calculate additional checksums for another platform, run:
  terraform providers lock -platform=linux_amd64
(where linux_amd64 is the platform to generate)

Terraform has been successfully initialized!
2024-03-08T06:47:28.134Z [INFO]  Terraform version: 1.5.7
2024-03-08T06:47:28.134Z [INFO]  Go runtime version: go1.20.7
2024-03-08T06:47:28.134Z [INFO]  CLI args: []string{"/bin/terraform", "apply", "plan.out", "-no-color"}
2024-03-08T06:47:28.134Z [INFO]  Loading CLI configuration from /root/.terraformrc
2024-03-08T06:47:28.135Z [INFO]  CLI command args: []string{"apply", "plan.out", "-no-color"}
2024-03-08T06:47:28.253Z [INFO]  backend/local: starting Apply operation
2024-03-08T06:47:28.260Z [INFO]  provider: configuring client automatic mTLS
2024-03-08T06:47:28.270Z [INFO]  provider.terraform-provider-azurerm_v3.94.0_x5: configuring server automatic mTLS: timestamp=2024-03-08T06:47:28.269Z
2024-03-08T06:47:28.416Z [INFO]  provider: configuring client automatic mTLS
2024-03-08T06:47:28.420Z [INFO]  provider.terraform-provider-random_v3.6.0_x5: configuring server automatic mTLS: timestamp=2024-03-08T06:47:28.420Z
2024-03-08T06:47:28.430Z [INFO]  backend/local: apply calling Apply
2024-03-08T06:47:28.432Z [INFO]  provider: configuring client automatic mTLS
2024-03-08T06:47:28.435Z [INFO]  provider.terraform-provider-random_v3.6.0_x5: configuring server automatic mTLS: timestamp=2024-03-08T06:47:28.435Z
module.az-redis.random_string.name_suffix: Destroying... [id=s3kzdcbxfl]
2024-03-08T06:47:28.445Z [INFO]  Starting apply for module.az-redis.random_string.name_suffix
module.az-redis.random_string.name_suffix: Destruction complete after 0s

Apply complete! Resources: 0 added, 0 changed, 1 destroyed.

But the deletion actually failed

Expected behavior

Environment

Walrus version: v0.6.0-rc1

Additional context
Add any other context about the problem here.

Test Result:
Cannot be reproduced.
In main 61070fa9f82dd3630b4aadb8626245dcef93e722, the resource status changes to "Ready" only after the component appears.
In v0.6.0-rc1, stopping the resource when the status is "ready" without the component being synchronized will not generate a run.
Close this issue for now and reopen it if it can be reproduced.


[DEV] Error on startup of fresh install

Expected Behavior
No errors on startup.
Actual Behavior
TypeError on fresh install (error occurs ONLY during the first startup!)
Your FULL config.json (remove your username, password, gmapkey and any other private info)
Default config.example.json
Output when issue occurred
[2016-09-01 10:23:35] Found encrypt.dll! Platform: win32 encrypt.dll directory: [...]
[2016-09-01 10:23:35]
Traceback (most recent call last):
File "[...]Python\lib\logging_init_.py", line 861, in emit
msg = self.format(record)
File "[...]Python\lib\logging_init_.py", line 734, in format
return fmt.format(record)
File "[...]Python\lib\logging_init_.py", line 465, in format
record.message = record.getMessage()
File "[...]Python\lib\logging_init_.py", line 329, in getMessage
msg = msg % self.args
TypeError: not all arguments converted during string formatting
Logged from file init.py, line 1354
[2016-09-01 10:23:36] No inventory file [...]pokemongo_bot..\web\inventory-[...].json found. Creating a new one
Steps to Reproduce
Use fresh install of dev version and start bot
Other Information
OS: Win10 64 bit
Branch: dev
Git Commit: d5059ed
Python Version: 2.7.12

PR #5072 should fix

Merged #5072


fix(client): Replace node-sass with sass

Description of change
node-sass is no longer maintained and is causing security alerts:

If you’re a user of Node Sass, migrating to Dart Sass is straightforward: just replace node-sass in your package.json file with sass. Both packages expose the same JavaScript API.

https://sass-lang.com/blog/libsass-is-deprecated#how-do-i-migrate
Type of change

Bug fix (a non-breaking change which fixes an issue)

How the change has been tested
N/A
Change checklist

[x] My code follows the contribution guidelines for this project
[x] I have performed a self-review of my own code

I already have this done in another branch, and also replace sass-lint with stylelint - need to do a bit more testing before I merge


Expose metadata endpoint via configuration option

Check for configuration option entityid_endpoint.
When set to true the metadata will be served at the URL pointed by the entityid URI.
This commit introduces a new class SAMLBaseModule which serves as a common place for both frontend and backend saml modules.
An example configuration would be:
module: satosa.backends.saml2.SAMLBackend
name: Saml2
config:
  entityid_endpoint: true
  sp_config:
    entityid: <base_url>/<name>/proxy_saml2_backend.xml
    ...

Even though I like the addition of the SAMLBaseModule (and think other configuration could use that abstraction) I don't know if it is ok to add it just for this config option. Or should we add it and see it as a start for similar config abstractions?

The SAMLBaseModule class serves as a common placeholder for common functionality in both the SAML frontend and backend modules. While at the moment it only offers that option, in the future it could hold more information (I plan to do that).
If you do not want to go forward with that, what would the alternative to share code between the frontend and backend modules be? I am open to suggestions, though I definitely do not want to duplicate the code. The only other option I can think of atm, is putting the code in a function in a generic file like utils.py and calling into that (which I feel is uglier).

I feel this is a cleaner way to add the common functionality needed in all SAML SATOSA plugins than any of the alternatives I can think of. And I know that @c00kiemon5ter has more functionality to submit that fits nicely on that base class so I'm all in for accepting this. We can by all means discuss it further though, if anyone has concerns

Just what I hoped you would say, that it's just a start :)


allow connect with DSN

it seems we can not use DSN to create a connection in databend-py yet.
with having a DSN, it's easier to put the connection info in a single environment variable, which is convinient in many use cases.

noticed that there is a Client.from_url(), let me try it


Run out of tokens

Help, I'm addicted. I need more tokens but I cant see how to buy more. I'm desperate man.

Did you subscribe for the pro version?

Hi Abraham,
Yes, indeed. See the attached invoice.
Had the same experience as others as discussed in the link below
https://github.com/stackblitz/bolt.new/issues/218
Kind Regards,
On Wed, Oct 9, 2024 at 9:38 AM Abraham Dahunsi @.***>
wrote:

Did you subscribe for the pro version?
—
Reply to this email directly, view it on GitHub
https://github.com/stackblitz/bolt.new/issues/271#issuecomment-2401568844,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BALIDLVK5EECGOFAVOK4GTLZ2TMPNAVCNFSM6AAAAABPT327EOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBRGU3DQOBUGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hey @yazoosa , thank you for reporting the issue! We are actively working on a solution and implementing several changes to support token reloading, provide a clearer in-app status for the tokens and more subscription tiers for token. We appreciate your patience and will deploy the first updates as soon as possible so today and over the next couple of days, you can expect a continually improving experience.

Hey, @yazoosa! While we have been working on optimizing the tokens usage we have accidentally triggered the limit on the accounts that weren't close to the limit. So yes, this was a bug.
We've reverted the change so this should now be resolved and you should have your correct limit back. I'll close the issue, but in case a problem persist, please open a new one! And we are working on more subscription tiers and ways to purchase additional tokens, too! Thank you for being an early adopter and for your patience as we're ironing out the experience on bolt!

Here's the info on purchasing additional tokens:
https://x.com/stackblitz/status/1844138865508134999


Robust value kind name

Hello,
I tested this code:
import nap

let bar = use_arg(name="bar", kind="value", required=false, value="cosmic", help="Heaps Alloy", alt="b")

parse_args()

if bar.used:
    echo bar.value

And I found these results:
$ ./tests/test --ba
cosmic
$ ./tests/test --bar
cosmic
$ ./tests/test --ba=lol
lol

It's normal ?

Yes. The first two use the value provided to 'bar' (value="cosmic").
As for why '--ba' works: https://github.com/madprops/nap/issues/1
The last line sets the value of 'bar' to 'lol'.
As for why the first two don't throw an error, it's because internally they already have a value (cosmic) so it doesn't fail when checked. Though I admit this is kind of confusing since the flags are being used incorrectly.


Please add support for configuration automatic assignment in addition to reviews

Hi. After much searching for an action that can automatically assign reviewers based on file globs, this seems like by far the best choice. However, my team's workflow actually hinges on utilizing assignment for "take another pass/work on this PR" rather than just reviewers. Might it be possible to extend this action's functionality to include a configuration for assigning & marking reviewers for folks that match the criteria to review a particular PR?
Per the code, I think I can go ahead and make this change if there's limited availability to work on the action but it will probably take me a few days before I can make the time for it.

@BenHenning Hi. Thanks for your feature request. If I understand correctly, you'd like to automatically set both "Assignees" and "Reviewers" using the different sets of configuration, correct?

For instance, when you make some changes on JavaScript files, you'd like to set "Member A" and "Member B" as "Assignees" while setting "Member C" as a "Reviewer". Something like that?
If that's correct, what I can think of is to make it configurable which type of assignees/reviewers you'd like to automatically assign with this action, "Assignees" or "Reviewers" with something like:
options:
  set_assignees: true # default false - if true, assignees will be set instead of reviewers

Then, you can set up two different workflows using this action. Does it satisfy your use case?
Another way is to provide an assignees section, however, I feel that would make the action a bit too complicated.

Thanks for the follow up @necojackarc! Yes, that would work for our use case.
To provide a bit more clarity (if it's useful): we'd like to preliminarily assign team members to manage and/or initially review PRs who aren't codeowners, but we otherwise rely on codeowners for automatic reviewers.
A separate question that's pertinent to my team adopting this: does the action support assigning from a GitHub team like codeowners does? I see that the action has its own built-in group support, but that's a bit less flexible than GitHub groups since it requires changing the configuration file. If it doesn't have such support, have there been considerations to add it?

@BenHenning Thanks. That's good to know. Then, it should be possible to implement by tweaking this function
https://github.com/necojackarc/auto-request-review/blob/f014ee85bde58d4bf063125d7542ebf00cde0b41/src/github.js#L79-L90
to take an option like use_assiggnees and use some function provided by octokit.pulls to set assignees, instead of reviewers, when use_assiggnees is true.

re: assigning from a GitHub team
That's a good point. I actually didn't know if it worked with GitHub teams; I played around with it and it turned out it didn't -so I've added support for GitHub teams in v0.6.0.
N.B. As the support for assignees isn't yet implemented, this issue hasn't been resolved.


CCompiler.has_function() does not delete temporary files.

Depending on the check result it leaves temporary C source, object and executable files.

Fixed in https://github.com/pypa/distutils/pull/32


Need to be able to execute queries

Need to be able to execute SQL queries and return results in C# objects
Probably expose PetaPoco database object, but compile it as part of the Cake.SqlServer.dll

Does PetaPoco support materializing immutable structs and classes by passing everything via constructor?

@jnm2  do you mean classes like this?
public class MyProduct
{
    public String Name { get; private set; }
    public String Description { get; private set; }

    public MyProduct(string name, string descr)
    {
            Name = name;
            Description = descr;
    }
}

No, I don't think so PetaPoco will handle this. What I've seen/used before were POCOs, same as for EF:
public class MyProduct
{
    public String Name { get; set; }
    public String Description { get; set; }
}

Yes. BTW they are both POCOs because neither inherits from a persistence base class or has a state tracking property.

After looking and thinking about this for a while I came to conclusion that querying should not be part of this project. If you need to query just use Dapper or PetaPoco via NuGets available. These do querying far better than I'll ever produce here.


⚠ Fortnite has degraded performance

In 3f0aeb5, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1574 ms

Resolved: Fortnite performance has improved in 6189c68.


Modal Pop-out for Target Translation

This PR adds the following:
In VerseCheck: Modal Pop-out for Target Translation #863
Expected behavior:
opens a modal pop-out when the expand button in my target language is clicked  that displays more context
Test
click the expand button in my target language area and it should open a modal that displays more context of the current chapter.

This change is

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Comments from Reviewable


modernize it?

modernize it with nodejs codebase. this project it self is very attractive, and still got lots of pissibility. but the code and tech is outdated.

Outdated? How is code that performs well and works outdated? Just because it's not in the language and framework flavor of the month?
Jokes aside you're free to re-write it in whatever and make a pull request. Personally I have no time to at the moment. :)


Extension 'msazurermtools.azurerm-vscode-tools' uses a document selector without scheme

Extension 'msazurermtools.azurerm-vscode-tools' uses a document selector without scheme. Learn more about this: https://go.microsoft.com/fwlink/?linkid=872305 #16

Already have this?

azurerm-vscode-tools/Deployment Template Opened


Add insert function

This PR adds an insert function to complement the without function. It's pretty straightforward - really just a small modification of the replace function.

@wmhilton Thank you


LD_LIBRARY_PATH not set correctly,causing plasmasession to not start

Describe the bug
On latest nixos-unstable, the plasma session could not start without the following workaround:
environment.sessionVariables.LD_LIBRARY_PATH="/run/current-systyem/sw/lib";

Notify maintainers
@NixOS/qt-kde
Metadata

system: "x86_64-linux"
host os: Linux 5.10.27, NixOS, 21.05.20210405.3d1a771 (Okapi)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.4pre20210326_dd77f71
channels(root): ""
nixpkgs: /nix/store/sz015sc0y6adpacafc4zs35wf8364c6a-source

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

Can you please describe the problem in detail? What does it mean that plasmasession does not start? Do you see a blank screen, or you are returned to the login screen, or your computer reboots... etc.? Do you see any messages in the system log (journalctl)?
LD_LIBRARY_PATH should not be set like that on a running system, so knowing your workaround does not help me diagnose the problem.

journalctl --user
…
apr 07 21:10:50 nixos systemd[1934]: plasma-kactivitymanagerd.service: Succeeded.
apr 07 21:10:50 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=exited, status=1/FAILURE
apr 07 21:10:50 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'exit-code'.
apr 07 21:10:50 nixos xsession[2049]: The X11 connection broke (error 1). Did the X11 server die?
apr 07 21:10:50 nixos xsession[1988]: Application::crashHandler() called with signal 11; recent crashes: 1
apr 07 21:10:50 nixos xsession[1988]: malloc_consolidate(): unaligned fastbin chunk detected
apr 07 21:10:50 nixos xsession[1988]: KCrash: Application 'kwin_x11' crashing...
apr 07 21:10:50 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 1.
apr 07 21:10:50 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:10:50 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:10:50 nixos obexd[2186]: OBEX daemon 5.56
apr 07 21:10:50 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Successfully activated service 'org.bluez.obex'
apr 07 21:10:50 nixos systemd[1934]: Started Bluetooth OBEX service.
apr 07 21:10:50 nixos obexd[2186]: stat(/home/paki/.cache/obexd): No such file or directory (2)
apr 07 21:10:50 nixos obexd[2186]: Unable to setup root folder /home/paki/.cache/obexd
apr 07 21:10:50 nixos systemd[1934]: obex.service: Main process exited, code=exited, status=1/FAILURE
apr 07 21:10:50 nixos systemd[1934]: obex.service: Failed with result 'exit-code'.
apr 07 21:10:51 nixos org.kde.kwalletd5[2192]: qt.qpa.xcb: could not connect to display :0
apr 07 21:10:51 nixos org.kde.kwalletd5[2192]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:10:51 nixos org.kde.kwalletd5[2192]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:10:51 nixos org.kde.kwalletd5[2192]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:10:51 nixos kglobalaccel5[2201]: qt.qpa.xcb: could not connect to display :0
apr 07 21:10:51 nixos kglobalaccel5[2201]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:10:51 nixos kglobalaccel5[2201]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:10:51 nixos kglobalaccel5[2201]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:10:52 nixos systemd-coredump[2225]: [🡕] Process 2192 (.kwalletd5-wrap) of user 1001 dumped core.
apr 07 21:10:52 nixos xsession[1983]: Couldn't start kwalletd:  QDBusError("org.freedesktop.DBus.Error.Spawn.ChildSignaled", "Process org.kde.kwalletd5 received signal 6")
apr 07 21:10:52 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activated service 'org.kde.kwalletd5' failed: Process org.kde.kwalletd5 received signal 6
apr 07 21:11:09 nixos xsession[2063]: Fallimento: Inizializzazione del modulo non riuscita
apr 07 21:10:52 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activating service name='org.kde.kwalletd5' requested by ':1.7' (uid=1001 pid=1983 comm="/run/current-system/sw/bin/kded5 ")
apr 07 21:11:09 nixos xsession[1983]: Couldn't start kwalletd:  QDBusError("org.freedesktop.DBus.Error.Spawn.ChildSignaled", "Process org.kde.kwalletd5 received signal 6")
apr 07 21:11:09 nixos org.kde.kwalletd5[2243]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:09 nixos org.kde.kwalletd5[2243]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:09 nixos org.kde.kwalletd5[2243]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:09 nixos org.kde.kwalletd5[2243]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:09 nixos kglobalaccel5[2262]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:09 nixos kglobalaccel5[2262]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:09 nixos kglobalaccel5[2262]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:09 nixos kglobalaccel5[2262]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:10:53 nixos pulseaudio[2075]: Module "module-suspend-on-idle" should be loaded once at most. Refusing to load.
apr 07 21:10:53 nixos systemd[1934]: Started Sound Service.
apr 07 21:11:09 nixos kglobalaccel5[2269]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:09 nixos kglobalaccel5[2269]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:09 nixos kglobalaccel5[2269]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:09 nixos kglobalaccel5[2269]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:10:54 nixos systemd-coredump[2226]: [🡕] Process 2201 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:10 nixos xsession[1983]: Couldn't start kwalletd:  QDBusError("org.freedesktop.DBus.Error.Spawn.ChildSignaled", "Process org.kde.kwalletd5 received signal 6")
apr 07 21:10:54 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
apr 07 21:11:10 nixos org.kde.kwalletd5[2276]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:10 nixos org.kde.kwalletd5[2276]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:10 nixos org.kde.kwalletd5[2276]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:10 nixos org.kde.kwalletd5[2276]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:10:54 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:07 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activated service 'org.kde.kwalletd5' failed: Process org.kde.kwalletd5 received signal 6
apr 07 21:10:54 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:07 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activating service name='org.kde.kwalletd5' requested by ':1.7' (uid=1001 pid=1983 comm="/run/current-system/sw/bin/kded5 ")
apr 07 21:10:54 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 2.
apr 07 21:11:10 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activated service 'org.kde.kwalletd5' failed: Process org.kde.kwalletd5 received signal 6
apr 07 21:10:54 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:10 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activating service name='org.kde.kwalletd5' requested by ':1.7' (uid=1001 pid=1983 comm="/run/current-system/sw/bin/kded5 ")
apr 07 21:10:54 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:10:54 nixos pulseaudio[2075]: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
apr 07 21:10:55 nixos pulseaudio[2075]: XOpenDisplay() failed
apr 07 21:10:55 nixos pulseaudio[2075]: Failed to load module "module-x11-publish" (argument: "display=:0 xauthority=/home/paki/.Xauthority"): initialization failed.
apr 07 21:10:59 nixos systemd[1934]: plasma-kglobalaccel.service: start operation timed out. Terminating.
apr 07 21:11:05 nixos systemd[1934]: plasma-kglobalaccel.service: State 'stop-sigterm' timed out. Killing.
apr 07 21:11:05 nixos systemd[1934]: plasma-kglobalaccel.service: Killing process 2262 (.kglobalaccel5-) with signal SIGKILL.
apr 07 21:11:05 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=killed, status=9/KILL
apr 07 21:11:05 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'timeout'.
apr 07 21:11:05 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:05 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 3.
apr 07 21:11:05 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:05 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:11:07 nixos systemd-coredump[2258]: [🡕] Process 2243 (.kwalletd5-wrap) of user 1001 dumped core.
apr 07 21:11:09 nixos systemd-coredump[2264]: [🡕] Process 2262 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:10 nixos org.kde.kwalletd5[2295]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:10 nixos org.kde.kwalletd5[2295]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:10 nixos org.kde.kwalletd5[2295]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:10 nixos org.kde.kwalletd5[2295]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:11 nixos xsession[1983]: Couldn't start kwalletd:  QDBusError("org.freedesktop.DBus.Error.Spawn.ChildSignaled", "Process org.kde.kwalletd5 received signal 6")
apr 07 21:11:11 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activated service 'org.kde.kwalletd5' failed: Process org.kde.kwalletd5 received signal 6
apr 07 21:11:11 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activating service name='org.kde.kwalletd5' requested by ':1.7' (uid=1001 pid=1983 comm="/run/current-system/sw/bin/kded5 ")
apr 07 21:11:11 nixos kglobalaccel5[2301]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:11 nixos kglobalaccel5[2301]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:11 nixos kglobalaccel5[2301]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:11 nixos kglobalaccel5[2301]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:10 nixos systemd-coredump[2278]: [🡕] Process 2276 (.kwalletd5-wrap) of user 1001 dumped core.
apr 07 21:11:10 nixos systemd-coredump[2200]: [🡕] Process 1988 (kwin_x11) of user 1001 dumped core.
apr 07 21:11:12 nixos org.kde.kwalletd5[2321]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:12 nixos org.kde.kwalletd5[2321]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:12 nixos org.kde.kwalletd5[2321]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:12 nixos org.kde.kwalletd5[2321]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:10 nixos systemd-coredump[2271]: [🡕] Process 2269 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:10 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
apr 07 21:11:10 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:10 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:12 nixos kglobalaccel5[2332]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:12 nixos kglobalaccel5[2332]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:12 nixos kglobalaccel5[2332]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:12 nixos kglobalaccel5[2332]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:10 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 4.
apr 07 21:11:10 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:10 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:11:12 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activated service 'org.kde.kwalletd5' failed: Process org.kde.kwalletd5 received signal 6
apr 07 21:11:12 nixos xsession[1983]: Couldn't start kwalletd:  QDBusError("org.freedesktop.DBus.Error.Spawn.ChildSignaled", "Process org.kde.kwalletd5 received signal 6")
apr 07 21:11:12 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activating service name='org.kde.kwalletd5' requested by ':1.7' (uid=1001 pid=1983 comm="/run/current-system/sw/bin/kded5 ")
apr 07 21:11:11 nixos systemd-coredump[2302]: [🡕] Process 2295 (.kwalletd5-wrap) of user 1001 dumped core.
apr 07 21:11:13 nixos org.kde.kwalletd5[2338]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:13 nixos org.kde.kwalletd5[2338]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:13 nixos org.kde.kwalletd5[2338]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:13 nixos org.kde.kwalletd5[2338]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:14 nixos xsession[1983]: Couldn't start kwalletd:  QDBusError("org.freedesktop.DBus.Error.Spawn.ChildSignaled", "Process org.kde.kwalletd5 received signal 6")
apr 07 21:11:13 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activated service 'org.kde.kwalletd5' failed: Process org.kde.kwalletd5 received signal 6
apr 07 21:11:12 nixos systemd-coredump[2309]: [🡕] Process 2301 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:13 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activating service name='org.kde.kwalletd5' requested by ':1.7' (uid=1001 pid=1983 comm="/run/current-system/sw/bin/kded5 ")
apr 07 21:11:14 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activated service 'org.kde.kwalletd5' failed: Process org.kde.kwalletd5 received signal 6
apr 07 21:11:15 nixos xsession[1983]: plasma-nm: Error opening kwallet.
apr 07 21:11:12 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
apr 07 21:11:15 nixos kglobalaccel5[2352]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:15 nixos kglobalaccel5[2352]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:15 nixos kglobalaccel5[2352]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:15 nixos kglobalaccel5[2352]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:15 nixos org.kde.kwalletd5[2351]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:15 nixos org.kde.kwalletd5[2351]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:15 nixos org.kde.kwalletd5[2351]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:15 nixos org.kde.kwalletd5[2351]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:12 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:12 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:12 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 5.
apr 07 21:11:12 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:12 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:11:12 nixos systemd-coredump[2326]: [🡕] Process 2321 (.kwalletd5-wrap) of user 1001 dumped core.
apr 07 21:11:15 nixos kglobalaccel5[2372]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:15 nixos kglobalaccel5[2372]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:15 nixos kglobalaccel5[2372]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:15 nixos kglobalaccel5[2372]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:13 nixos systemd-coredump[2341]: [🡕] Process 2332 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:13 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
apr 07 21:11:16 nixos kglobalaccel5[2380]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:16 nixos kglobalaccel5[2380]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:16 nixos kglobalaccel5[2380]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:16 nixos kglobalaccel5[2380]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:13 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:13 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:13 nixos systemd-coredump[2343]: [🡕] Process 2338 (.kwalletd5-wrap) of user 1001 dumped core.
apr 07 21:11:17 nixos pulseaudio[2075]: Invalid MIT-MAGIC-COOKIE-1 key
apr 07 21:11:13 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 6.
apr 07 21:11:17 nixos kglobalaccel5[2388]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:17 nixos kglobalaccel5[2388]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:17 nixos kglobalaccel5[2388]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:17 nixos kglobalaccel5[2388]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:13 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:13 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:11:14 nixos systemd-coredump[2354]: [🡕] Process 2351 (.kwalletd5-wrap) of user 1001 dumped core.
apr 07 21:11:15 nixos systemd-coredump[2356]: [🡕] Process 2352 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:19 nixos kglobalaccel5[2398]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:19 nixos kglobalaccel5[2398]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:19 nixos kglobalaccel5[2398]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:19 nixos kglobalaccel5[2398]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:15 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
apr 07 21:11:19 nixos kglobalaccel5[2404]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:19 nixos kglobalaccel5[2404]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:19 nixos kglobalaccel5[2404]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:19 nixos kglobalaccel5[2404]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:15 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:15 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:15 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 7.
apr 07 21:11:15 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:15 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:11:15 nixos systemd-coredump[2374]: [🡕] Process 2372 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:15 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
apr 07 21:11:15 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:15 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:16 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 8.
apr 07 21:11:16 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:16 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:11:16 nixos systemd-coredump[2382]: [🡕] Process 2380 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:16 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
apr 07 21:11:16 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:20 nixos kglobalaccel5[2416]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:20 nixos kglobalaccel5[2416]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:20 nixos kglobalaccel5[2416]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:20 nixos kglobalaccel5[2416]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:16 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:17 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 9.
apr 07 21:11:17 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:17 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:11:17 nixos systemd[1934]: pulseaudio.service: Succeeded.
apr 07 21:11:17 nixos systemd-coredump[2390]: [🡕] Process 2388 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:17 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
apr 07 21:11:17 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:17 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:18 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 10.
apr 07 21:11:18 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:18 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:11:18 nixos systemd-coredump[2400]: [🡕] Process 2398 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:18 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
apr 07 21:11:18 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:18 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:19 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 11.
apr 07 21:11:19 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:19 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:11:19 nixos systemd-coredump[2408]: [🡕] Process 2404 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:20 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
apr 07 21:11:23 nixos xsession[1983]: Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyThe X11 connection broke: I/O error (code 1)
apr 07 21:11:23 nixos xsession[1983]: X connection to :0 broken (explicit kill or server shutdown).
apr 07 21:11:20 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:20 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:20 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 12.
apr 07 21:11:20 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:20 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:11:21 nixos systemd-coredump[2418]: [🡕] Process 2416 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:21 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
apr 07 21:11:21 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:21 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:21 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 13.
apr 07 21:11:21 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:21 nixos systemd[1934]: plasma-kglobalaccel.service: Start request repeated too quickly.
apr 07 21:11:21 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:21 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:28 nixos systemd-coredump[2432]: [🡕] Process 2102 (.ibus-daemon-wr) of user 1001 dumped core.
apr 07 21:11:29 nixos xsession[2047]: kf.plasma.quick: Applet preload policy set to 1
apr 07 21:11:30 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activating via systemd: service name='org.kde.kglobalaccel' unit='plasma-kglobalaccel.service' requested by ':1.19' (uid=1001 pid=2047 comm="/nix/store/26h6vx2m25z23j51cgksi2m3szzdi7i8-plasma")
apr 07 21:11:30 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:11:30 nixos kglobalaccel5[2439]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:30 nixos kglobalaccel5[2439]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:30 nixos kglobalaccel5[2439]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:30 nixos kglobalaccel5[2439]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:30 nixos systemd-coredump[2441]: [🡕] Process 2439 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:30 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
apr 07 21:11:30 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:31 nixos kglobalaccel5[2447]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:31 nixos kglobalaccel5[2447]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:31 nixos kglobalaccel5[2447]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:31 nixos kglobalaccel5[2447]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:30 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:31 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 1.
apr 07 21:11:31 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:31 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:11:31 nixos systemd-coredump[2449]: [🡕] Process 2447 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:31 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
apr 07 21:11:31 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:32 nixos kglobalaccel5[2455]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:32 nixos kglobalaccel5[2455]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:32 nixos kglobalaccel5[2455]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:32 nixos kglobalaccel5[2455]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:31 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:31 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 2.
apr 07 21:11:31 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:31 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:11:32 nixos xsession[2036]: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.27'
apr 07 21:11:32 nixos systemd-coredump[2457]: [🡕] Process 2455 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:32 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
apr 07 21:11:32 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:33 nixos kglobalaccel5[2463]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:33 nixos kglobalaccel5[2463]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:33 nixos kglobalaccel5[2463]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:33 nixos kglobalaccel5[2463]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:32 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:32 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 3.
apr 07 21:11:32 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:32 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:11:33 nixos systemd-coredump[2465]: [🡕] Process 2463 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:33 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
apr 07 21:11:33 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:34 nixos kglobalaccel5[2471]: Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
apr 07 21:11:34 nixos kglobalaccel5[2471]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
apr 07 21:11:34 nixos kglobalaccel5[2471]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
apr 07 21:11:34 nixos kglobalaccel5[2471]: Available platform plugins are: wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
apr 07 21:11:33 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:33 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 4.
apr 07 21:11:33 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:33 nixos systemd[1934]: Starting KDE Global Shortcuts Server...
apr 07 21:11:34 nixos systemd-coredump[2473]: [🡕] Process 2471 (.kglobalaccel5-) of user 1001 dumped core.
apr 07 21:11:34 nixos systemd[1934]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
apr 07 21:11:34 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:34 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:34 nixos systemd[1934]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 5.
apr 07 21:11:34 nixos systemd[1934]: Stopped KDE Global Shortcuts Server.
apr 07 21:11:34 nixos systemd[1934]: plasma-kglobalaccel.service: Start request repeated too quickly.
apr 07 21:11:34 nixos systemd[1934]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
apr 07 21:11:34 nixos systemd[1934]: Failed to start KDE Global Shortcuts Server.
apr 07 21:11:35 nixos org.freedesktop.Notifications[2114]: org.kde.knotifications: WaitForName: Service was not registered within timeout
apr 07 21:11:35 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1
apr 07 21:11:43 nixos xsession[2036]: Document not (yet) known, signaling newFile "/home/paki/.config/khotkeysrc"
apr 07 21:11:49 nixos org.kde.KSplash[2188]: org.kde.knotifications: WaitForName: Service was not registered within timeout
apr 07 21:11:49 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash exited with status 1
apr 07 21:12:15 nixos sddm-helper[2490]: pam_kwallet5: final socket path: /run/user/1001/kwallet5.socket
apr 07 21:12:15 nixos sddm-helper[2492]: Adding cookie to "/home/paki/.Xauthority"
apr 07 21:12:17 nixos xsession[2489]: Qt: Session management error: Could not open network socket
apr 07 21:12:18 nixos xsession[2522]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
apr 07 21:12:18 nixos xsession[2522]: kf.coreaddons: Failed to establish shared memory mapping, will fallback to private memory -- memory usage will increase
apr 07 21:12:19 nixos xsession[2514]: org.kde.plasma.session: process job  "kcminit_startup" finished with exit code  0
apr 07 21:12:19 nixos xsession[2530]: kf.service.sycoca: Couldn't lock "/home/paki/.cache/ksycoca5_it_wIVPHBt5Js2_6ZI_kLAL8NGV+3A=.lock"
apr 07 21:12:19 nixos xsession[2530]: kf.service.sycoca: Couldn't lock "/home/paki/.cache/ksycoca5_it_wIVPHBt5Js2_6ZI_kLAL8NGV+3A=.lock"
apr 07 21:12:19 nixos xsession[2530]: kf.service.sycoca: Couldn't lock "/home/paki/.cache/ksycoca5_it_wIVPHBt5Js2_6ZI_kLAL8NGV+3A=.lock"
apr 07 21:12:19 nixos xsession[2530]: Could not open sycoca database, you must run kbuildsycoca first!
apr 07 21:12:19 nixos xsession[2530]: kf.service.sycoca: No ksycoca database available! Tried running kbuildsycoca5 ?
apr 07 21:12:19 nixos xsession[2530]: kf.service.services: KServiceTypeTrader: serviceType "KDEDModule" not found
apr 07 21:12:19 nixos xsession[2530]: bluedevil: Created
apr 07 21:12:20 nixos xsession[2534]: Failed to create /home/paki/.cache/mesa_shader_cache for shader cache (Permission denied)---disabling.
apr 07 21:12:20 nixos xsession[2534]: kf.coreaddons: Failed to establish shared memory mapping, will fallback to private memory -- memory usage will increase
apr 07 21:12:20 nixos xsession[2534]: kwin_xkbcommon: XKB: /nix/store/cc2grj0c1hix1415iy2v42cpqhl9n7wk-libX11-1.7.0/share/X11/locale/en_US.UTF-8/Compose:5079:46: this compose sequence is a duplicate of another; skipping line
apr 07 21:12:20 nixos xsession[2534]: kwin_xkbcommon: XKB: /nix/store/cc2grj0c1hix1415iy2v42cpqhl9n7wk-libX11-1.7.0/share/X11/locale/en_US.UTF-8/Compose:5081:48: this compose sequence is a duplicate of another; skipping line
apr 07 21:12:20 nixos xsession[2534]: kwin_xkbcommon: XKB: /nix/store/cc2grj0c1hix1415iy2v42cpqhl9n7wk-libX11-1.7.0/share/X11/locale/en_US.UTF-8/Compose:5083:48: this compose sequence is a duplicate of another; skipping line
apr 07 21:12:20 nixos xsession[2534]: kwin_xkbcommon: XKB: /nix/store/cc2grj0c1hix1415iy2v42cpqhl9n7wk-libX11-1.7.0/share/X11/locale/en_US.UTF-8/Compose:5087:47: this compose sequence is a duplicate of another; skipping line
apr 07 21:12:20 nixos xsession[2534]: kwin_xkbcommon: XKB: /nix/store/cc2grj0c1hix1415iy2v42cpqhl9n7wk-libX11-1.7.0/share/X11/locale/en_US.UTF-8/Compose:5089:46: this compose sequence is a duplicate of another; skipping line
apr 07 21:12:20 nixos xsession[2534]: kwin_xkbcommon: XKB: /nix/store/cc2grj0c1hix1415iy2v42cpqhl9n7wk-libX11-1.7.0/share/X11/locale/en_US.UTF-8/Compose:5097:48: this compose sequence is a duplicate of another; skipping line
apr 07 21:12:20 nixos xsession[2534]: kwin_xkbcommon: XKB: /nix/store/cc2grj0c1hix1415iy2v42cpqhl9n7wk-libX11-1.7.0/share/X11/locale/en_US.UTF-8/Compose:5101:46: this compose sequence is a duplicate of another; skipping line
apr 07 21:12:20 nixos xsession[2534]: kwin_xkbcommon: XKB: /nix/store/cc2grj0c1hix1415iy2v42cpqhl9n7wk-libX11-1.7.0/share/X11/locale/en_US.UTF-8/Compose:5103:46: this compose sequence is a duplicate of another; skipping line
apr 07 21:12:20 nixos xsession[2534]: kwin_xkbcommon: XKB: /nix/store/cc2grj0c1hix1415iy2v42cpqhl9n7wk-libX11-1.7.0/share/X11/locale/en_US.UTF-8/Compose:5107:45: this compose sequence is a duplicate of another; skipping line
apr 07 21:12:20 nixos xsession[2534]: kwin_xkbcommon: XKB: /nix/store/cc2grj0c1hix1415iy2v42cpqhl9n7wk-libX11-1.7.0/share/X11/locale/en_US.UTF-8/Compose:5110:46: this compose sequence is a duplicate of another; skipping line
apr 07 21:12:20 nixos xsession[2534]: kwin_xkbcommon: XKB: Couldn't process include statement for 'it(\0)'
apr 07 21:12:20 nixos xsession[2534]: kwin_xkbcommon: XKB: Abandoning symbols file "(unnamed)"
apr 07 21:12:20 nixos xsession[2534]: kwin_xkbcommon: XKB: Failed to compile xkb_symbols
apr 07 21:12:20 nixos xsession[2534]: kwin_xkbcommon: XKB: Failed to compile keymap
apr 07 21:12:20 nixos dbus-daemon[1963]: [session uid=1001 pid=1963] Activating via systemd: service name='org.kde.ActivityManager' unit='plasma-kactivitymanagerd.service' requested by ':1.37' (uid=1001 pid=2534 comm="/run/current-system/sw/bin/kwin_x11 ")
…

After latest update it now workd without the workaround. My bad, just the usual brokeness of updating plasma

After latest update it now workd without the workaround. My bad, just the usual brokeness of updating plasma

That means if I'm currently hitting this issue again (on 21.11), I'll just have to wait with updating for some time, and at a later point the updates will just start working again?


CTRL+ commands do not work properly

Hi,
Firstly, hanks for contribution to Atom, I really needed something like your built-in terminal emulator.
I encountered an issue today, when using Atom on MacOS X
Steps to reproduce

Open new terminal, execute arbitrary commands
Execute CTRL+ commands (such as CTRL+L to clear the terminal)

Expected result:

Terminal is cleared

Actual result:

Nothing happens

Workaround:

Issuing CTRL+L again does the trick

I know this isn't a solution but typing clear and hitting enter will clear the terminal as well.

Hi.
I've faced the same issue in Linux.
Though hitting the CTRL+L again does not seem to be necessary.
Typing any key after a CTRL+L clears the terminal.

At First thanks to the author for the plugin, very useful for me
@erwstout workaround Typing any key after a CTRL+L clears the terminal works
but  it would be nice to fix it properly.
Personally for me it is the only thing that causes discomfort when using this plugin

Interesting... I use Fish and there CTRL+L works fine, but CTRL+:arrow_right: doesn't (it is used to fill the next suggested word). Instead, it prints [5C, which is annoying.

I create an alias on zsh nammed cl
Not the best but works!


email_mirror: Add email address parsing.

When trying to find the email gateway address, use the
email.util.getaddresses function to deal with cases
where multiple recipients are included in the email header
or the stream address appears as an angle-addr with a
name given (e.g. if someone added it to their address book).
Added some other headers where the required address may
appear: "Resent" headers are sometimes used for forwarding,
and streams may also be found in CC. There is no way to find
the address if the email was recieved as a BCC.

Testing Plan:
Unit test included.
GIFs or Screenshots:

Nice work, merged, thanks @tdaff!


registry returns 500

on url https://brackets-npm-registry.herokuapp.com/registry

:open_mouth:

Idd :P also my eslint is broken so I thought update brackets-eslint and then I found the registery was down :P

I'll have to look into it ... seems like heroku has changed something because I definitely didn't ... I've restarted it for now, maybe it'll help.

Thanks!
On Thu, 7 Apr 2016 12:39 Martin Zagora<EMAIL_ADDRESS>wrote:

I'll have to look into it ... seems like heroku has changed something
because I definitely didn't ... I've restarted it for now, maybe it'll help.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/zaggino/brackets-npm-registry/issues/37#issuecomment-206804747

So Heroku added some new rules or npm grew too big ...
2016-04-07T12:07:58.943068+00:00 heroku[web.1]: Error R15 (Memory quota vastly exceeded)
2016-04-07T12:07:58.943068+00:00 heroku[web.1]: Stopping process with SIGKILL
2016-04-07T12:08:00.046108+00:00 heroku[web.1]: Process exited with status 137

When trying to build the registry...

@AdriVanHoudt yay, should be up again -> https://brackets-npm-registry.herokuapp.com/registry


CON-528

@kylycht can you also add logic to utils/compile-thrift-java.sh to generate the thrift sources for the management code?

Tracking at https://github.com/cinchapi/concourse/pull/245


adding PublicAccessBlockConfiguration to s3 buckets, per Nov 19 2018 …

adding PublicAccessBlockConfiguration to s3 buckets, per Nov 19 2018 update

Thanks!


Suites

Start with a simple example for a suites feature discussed in issue #821.

Still got any energy for this @richarda?

Sure. I've been out for a while, but I should jump back in. Let me take a look.

I am looking at this.  It's taking me a while to catch up.  Would the execution behavior of a suite be implemented similarly to a rerun scenario?

I think the changes required here are a bit more fundamental @richarda. The code is going to offer some resistance to this change but once it's done we'll have tackled some of the remaining bits of coupling, so you'll need to be brave!
First off, I think we need to model the configuration differently, so that there's configuration for the overall run that won't change (formatters, for example) and then configuration per suite (e.g. tags to filter by).
Then it's a matter of breaking out some of the functionality in Runtime into a new Suite class that models the execution of a single suite. The Runtime would have a list of suites (by default, just one) that it iterates over and executes. The body of Runtime#run! and its friends would move into the Suite class.
I would start by picking off a single configuration option (like the tags to filter by) and trying to get that to work, then we can iterate and pick off other configuration options that make sense.
Does that help?

Yes @mattwynne. That is helpful. That seems like a very good way to get started.

Sorry if this is slow progress, but I think I'm starting to get the idea here.
I'm just putting the configuration step inline in runtime.rb temporarily but it seems like there should be a method Cucumber.configure coming out of this soon.
In what context would this be written?
Cucumber.configure do |config|
  config.suite(:domain) do |suite_config|
    suite_config.world_modules << DriveDomain
    suite_config.filters << TagFilter.new("~@web")
    suite_config.filters << LocationFilter.new("features/core")
  end

  config.suite(:web) do |suite_config|
    suite_config.world_modules << DriveUI
    suite_config.filters << TagFilter.new("@web")
  end
end

Does that get written somewhere in the support directory like env.rb?

You could actually use an AfterConfiguration block for now, and yes, call it from env.rb

Still working ... Update soon.

Closing due to inactivity. This was a tough one to tackle @richarda. Feel free to ping us if you'd like to get involved again with something easier!


Add install_future to ThreadPool

Same as install, but non-blocking and returns a future

oh right rustup cannot install latest nightly atm...

Not really sure if this is a necessary change, just close it if it's not

@cuviper Like I said, I actually thought of something that didn't quite make sense, and asked myself the same.

OK, thanks anyway!  If you do find the current interfaces lacking, let's figure that out together before we remove the "unstable" feature guard.


[Question] URL for download

Hello,
I wanted to know what URL can be used in the api, like can I use a youtu.be url instead of youtube.com/watch?v=. Also, can your api only download videos from YouTube, or can it download from other videos hosting services (like TikTok for example)
Thanks you !

yea, youtube-dl supports a lot of providers. Just pass the URL to the library 🙂


[BUG] DuplicateCharset: ARIB-STD-B24

Bug description:
tsp ends with terminate called after throwing an instance of 'ts::Charset::DuplicateCharset'
what():  DuplicateCharset: ARIB-STD-B24
Environment:

OS: Linux, Raspbian, current Bullseye running at Pi4
Built from current git source.

This is typically the result of some inconsistency during the build. Maybe an interrupted make, followed by a make command with different parameters. In practice, this means that the object module tsARIBCharset.o containing this character set is activated twice in the same process, resulting in registering the same character set twice. This can also happen if static and shared (default) build are mixed. The object tsARIBCharset.o is present in libtsduck.so and erroneously statically linked in the main executable or another .so.
Just rebuild from a clean state: make clean; make