text:
SampleWorker: "Error when pollig for task" with JsonMappingException

Hello,
I'm trying the SampleWorker at: [https://github.com/Netflix/conductor/tree/dev/client/src/test/java/com/netflix/conductor/client/sample]
I started an instance of kitchensink, and tried to poll task_1 using SampleWorker. However, I got the following errors. I am working on Win 7. Please help. Thanks.
[pool-1-thread-1] ERROR com.netflix.conductor.client.task.WorkflowTaskCoordinator - Error when pollig for task java.lang.RuntimeException: com.sun.jersey.api.client.ClientHandlerException: com.fasterxml.jackson.databind.JsonMappingException: Conflicting setter definitions for property "type": com.netflix.conductor.common.metadata.workflow.WorkflowTask#setType(1 params) vs com.netflix.conductor.common.metadata.workflow.WorkflowTask#setType(1 params) 	at com.netflix.conductor.client.http.ClientBase.handleException(ClientBase.java:189) 	at com.netflix.conductor.client.http.ClientBase.getForEntity(ClientBase.java:179) 	at com.netflix.conductor.client.http.TaskClient.poll(TaskClient.java:88) 	at com.netflix.conductor.client.task.WorkflowTaskCoordinator.pollForTask(WorkflowTaskCoordinator.java:208) 	at com.netflix.conductor.client.task.WorkflowTaskCoordinator.lambda$2(WorkflowTaskCoordinator.java:173) 	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) 	at java.util.concurrent.FutureTask.runAndReset(Unknown Source) 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source) 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 	at java.lang.Thread.run(Unknown Source) Caused by: com.sun.jersey.api.client.ClientHandlerException: com.fasterxml.jackson.databind.JsonMappingException: Conflicting setter definitions for property "type": com.netflix.conductor.common.metadata.workflow.WorkflowTask#setType(1 params) vs com.netflix.conductor.common.metadata.workflow.WorkflowTask#setType(1 params) 	at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:644) 	at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:604) 	at com.sun.jersey.api.client.WebResource.handle(WebResource.java:698) 	at com.sun.jersey.api.client.WebResource.access$300(WebResource.java:74) 	at com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:514) 	at com.netflix.conductor.client.http.ClientBase.getForEntity(ClientBase.java:176) 	... 10 more Caused by: com.fasterxml.jackson.databind.JsonMappingException: Conflicting setter definitions for property "type": com.netflix.conductor.common.metadata.workflow.WorkflowTask#setType(1 params) vs com.netflix.conductor.common.metadata.workflow.WorkflowTask#setType(1 params) 	at com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCache2(DeserializerCache.java:270) 	at com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCacheValueDeserializer(DeserializerCache.java:245) 	at com.fasterxml.jackson.databind.deser.DeserializerCache.findValueDeserializer(DeserializerCache.java:143) 	at com.fasterxml.jackson.databind.DeserializationContext.findContextualValueDeserializer(DeserializationContext.java:406) 	at com.fasterxml.jackson.databind.deser.std.StdDeserializer.findDeserializer(StdDeserializer.java:882) 	at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.resolve(BeanDeserializerBase.java:436) 	at com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCache2(DeserializerCache.java:297) 	at com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCacheValueDeserializer(DeserializerCache.java:245) 	at com.fasterxml.jackson.databind.deser.DeserializerCache.findValueDeserializer(DeserializerCache.java:143) 	at com.fasterxml.jackson.databind.DeserializationContext.findContextualValueDeserializer(DeserializationContext.java:406) 	at com.fasterxml.jackson.databind.deser.std.CollectionDeserializer.createContextual(CollectionDeserializer.java:164) 	at com.fasterxml.jackson.databind.deser.std.CollectionDeserializer.createContextual(CollectionDeserializer.java:25) 	at com.fasterxml.jackson.databind.DeserializationContext.handleSecondaryContextualization(DeserializationContext.java:653) 	at com.fasterxml.jackson.databind.DeserializationContext.findRootValueDeserializer(DeserializationContext.java:444) 	at com.fasterxml.jackson.databind.ObjectReader._findRootDeserializer(ObjectReader.java:1566) 	at com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:1405) 	at com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:860) 	at com.fasterxml.jackson.jaxrs.base.ProviderBase.readFrom(ProviderBase.java:811) 	at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:634) 	... 15 more Caused by: java.lang.IllegalArgumentException: Conflicting setter definitions for property "type": com.netflix.conductor.common.metadata.workflow.WorkflowTask#setType(1 params) vs com.netflix.conductor.common.metadata.workflow.WorkflowTask#setType(1 params) 	at com.fasterxml.jackson.databind.introspect.POJOPropertyBuilder.getSetter(POJOPropertyBuilder.java:293) 	at com.fasterxml.jackson.databind.deser.BeanDeserializerFactory.filterBeanProps(BeanDeserializerFactory.java:583) 	at com.fasterxml.jackson.databind.deser.BeanDeserializerFactory.addBeanProps(BeanDeserializerFactory.java:479) 	at com.fasterxml.jackson.databind.deser.BeanDeserializerFactory.buildBeanDeserializer(BeanDeserializerFactory.java:220) 	at com.fasterxml.jackson.databind.deser.BeanDeserializerFactory.createBeanDeserializer(BeanDeserializerFactory.java:143) 	at com.fasterxml.jackson.databind.deser.DeserializerCache._createDeserializer2(DeserializerCache.java:409) 	at com.fasterxml.jackson.databind.deser.DeserializerCache._createDeserializer(DeserializerCache.java:358) 	at com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCache2(DeserializerCache.java:265) 	... 33 more

@niwy The error indicates the incompatibility between the version of jackson mapper used by conductor and your runtime JVM.
We recommend using 2.7.5 version of jackson-* libraries in your classpath.

@v1r3n Thanks for replying.
I'm using 2.7.5 jackson, and the Java version is 1.8.0_121.
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)

I tired different versions of jackson, e.g., 2.6.7, 2.7.4, 2.8.6. Besides, I exported a jar to run a linux machine with java 1.8.0_101. Anyhow, the errors remain.

@niwy I have renamed the offending method (it was on the TODO list already).  Can you give it a try with the dev branch again?  Let me know if the problem persists.

@v1r3n It works now. Thanks a lot.


text:
Timeline enhancements

This PR includes many enhancements to the incident timeline, including:

Direct link to the timeline for an incident. Users can now browse to .../{org_name}/incidents/{incident_name}/timeline to open the incident view directly to the timeline.
The incident details view pane is now expandable by a click and drag on the vertical divider line.
Icons in the timeline bubbles quickly indicate the type of event.
The incident timeline now has filtering to show/hide different kinds of events, with system events hidden by default.
Users can now add custom events to the timeline directly in the UI by hovering between existing events in the timeline and click the "Add event" button.
Custom events can be edited and/or deleted by the incident commander or reporter.
Messages imported from Slack with the reaction event can now be edited and/or deleted by the incident commander or reporter.

One thing that stands out form a UX perspective in the timeline is user actions vs system actions look very similar. I think it'd help to differentiate them more.
For example, the icon for the user actions could be the users profile picture and names could be bolded/clickable with the user popover component we have.

A minor thing from last screenshot -- the delete / edit icons probably fit best positioned all the way right, under the date. that way they wont cover the text or interfere with the content if it is rich (hoverable/clickable) in the future

One thing that stands out form a UX perspective in the timeline is user actions vs system actions look very similar. I think it'd help to differentiate them more.
For example, the icon for the user actions could be the users profile picture and names could be bolded/clickable with the user popover component we have.

Will pull these ideas into a phase 2, which will align the entire Incident edit/view with the new Case UI.

source: gharchive/pull-request

repo: Netflix/dispatch

license_type: permissive

license_source: github-api


text:
link two flows

Not sure if I just haven't found the right verbage in the documentations, or if there are other built in ways to do this but I want to be able to prospectively link two flows together. For example, let's say there is FlowA and FlowB, and FlowA for example pre-processes data that gets utilized in FlowB. Is there a way I can make sure that I know which data from FlowA was utilized by a certain run in FlowB? One way I guess would be to tag both flows with the same tag or unique ID, does anyone know how to programmatically tag a flow within itself? Should I just combine the two flows into one?
Thanks

@themantalope Tagging is definitely one approach. How are you currently accessing data from FlowA in your FlowB? You could simply store the relevant run id for FlowA in FlowB and access it using the Client API.
We have #159 open which will provide programmatic capabilities for tagging a flow retrospectively.

I see, so in the first step of FlowB I could do something link
from metaflow import FlowSpec, Flow

class FlowB(FlowSpec):
    @step
    def start(self):
         self.last_flow_a_run_id = Flow('FlowA').latest_run.run_id
    // rest of code etc.

And when the data from the FlowB is stored, the data in last_flow_a_run_id will get saved to disk, correct?

Yep, correct.

Great! Really appreciate it!

source: gharchive/issue

authors: savingoyal themantalope

repo: Netflix/metaflow


text:
Strange behaviour matching request modified in beforePersist

Description
I think this is a bug but there's always a chance it's a feature and I haven't understood something.
I'm testing an authentication flow and I don't want the real auth tokens to be committed to the repo. I've set up a beforePersist middleware to replace real-token with dummy-token in the POST bodies. When recording I make the requests with real-token. Then when running my tests against the recordings I make the requests with dummy-token. I would expect this to work because the real-token was changed to dummy-token when saving the HAR. But it doesn't: the request doesn't match.
The really strange thing is that if I run the test against the recordings but using the original real-token that I used when making the recordings it passes, even though that token doesn't appear in the HAR file. How does Polly remember the original token even when I've removed it from the HAR?
I've created a minimal test case here https://github.com/tamlyn/polly-test-case to illustrate the problem.
Node.js v12.13.1
darwin 17.7.0
npm 6.11.3
yarn 1.19.2

@tamlyn even though you're storing the dummy-token in the HAR file, you're still making the request with the real-token. Polly calculates the request's id based on the request you made (not whats stored in the HAR), so you would need to tell Polly to ignore the token altogether. You can do so via matchRequestsBy.

Ah! So the _id is a hash of the request? I thought it was random. Is that documented anywhere? Is the request object as stored in the HAR used for anything?

So the _id is a hash of the request

Correct

Is that documented anywhere?

https://netflix.github.io/pollyjs/#/configuration?id=matchrequestsby

Is the request object as stored in the HAR used for anything?

For completeness with the HAR spec (importing into a HAR tool to inspect for example).  In the future, we may leverage it more.

authors: jasonmit offirgolan tamlyn

repo: Netflix/pollyjs


text:
Configuring PoolingHttpClientConnectionManager with Time to Live?

Hi all,
I am using zuul to route requests to statically configured services according to the request path.
The services behind zuul are addressed using DNS names. The DNS records can change rather frequently (e.g., daily).
I have seen in SimpleHostRoutingFilter  that zuul uses PoolingHttpClientConnectionManager from Apache HttpComponents without configuring the time to live for the connections in the pool
(see https://github.com/Netflix/zuul/blob/939ada9dce57709cf6b250b77fabfa37e8d988bf/zuul-simple-webapp/src/main/groovy/filters/route/SimpleHostRoutingFilter.groovy#L97). Even if the DNS records change, the connection pool in zuul is keeping the connections to the old instances open. Depending on the load, it can take many hours until all the old connections are evicted from the connection pool.
I could subclass SimpleHostRoutingFilter and override the method newConnectionManager() to return my own instance of PoolingHttpClientConnectionManager with a configured TTL. Is there any other way to solve my problem, and  does it make sense to add this feature to zuul?
Best,
Gary

@GJL Hi, I am facing the same behaviour, how did you end up?

@avoosh I moved the issue to https://github.com/spring-cloud/spring-cloud-netflix/issues/1720

authors: GJL avoosh

repo: Netflix/zuul

license_source: bigquery


text:
Add Multi-GPU Training

Multi-GPU training was added using the HuggingFace Accelerate package. Installation shell script was also updated to work with new and updated packages.

@markusatkinson this is ready for review.


text:
Add Linux path to README

Added the path for the filters on Linux. Also changed the formatting a bit (code instead if italic) and replaced the forward slashes with back slashes on Windows, since that is the canonical path separator there.

Thanks, added

authors: NeverSinkDev Xandaros

license: MIT


text:
Harvested blocks are added when switching accounts

0.6.26-BETA
"When I switch between accounts with the "HARVESTED BLOCKS" tab selected the previous accounts harvested blocks gets added to the currently selected accounts harvested blocks."
https://forum.ournem.com/technical-discussion/nem-beta-0-6-26-security-update/msg15902/#msg15902

Can anybody confirm the behavior with version 0.6.28?

authors: BloodyRookie fyahfox

repo: NewEconomyMovement/NemCommunityClient

license: mit


text:
CRUD Finish

MEnyelesaikan Crud mapel

anjay

repo: Nexthrive/Nexademy-api


text:
02-app - 02-api-reference - 02-file-conventions - 01-metadata - app-icons.mdx 번역

기여자용
문서 개선

PR을 열기 전에 pnpm prettier-fix를 실행하여 서식 문제를 해결합니다. - 문서 기여 가이드를 읽고 문서 지침을 따르는지 확인하세요: https://github.com/Nextjs-kr/Nextjs.ko/blob/main/packages/next/README.md

Progress

[x] pnpm prettier-fix
[x] 번역 초안 작성 (Draft translation)
[x] 공통 스타일 가이드 확인 (Check the common style guide)
[x] 모범사례 확인 (Check best practices)
[x] 용어 확인 (Check the term)
[x] 맞춤법 검사 (Spelling check)
[x] 리뷰 반영 (Resolve reviews)

ref #89


text:
ThorZIP: executable file not found in %PATH%

I'm trying to run Generic.Scanner.ThorZIP but it's not working. I have uploaded the zip using ThorZIP tool, I tried both zip with included license and unmodified zip downloaded directly from website, but same problem.
{"client_time":1731337531,"level":"INFO","message":"Starting query execution for Generic.Scanner.ThorZIP/ThorExec.\n"}
{"client_time":1731337531,"level":"DEFAULT","message":"tempfile: removing tempfile C:\\Program Files\\Velociraptor\\Tools\\tmp391399109\n"}
{"client_time":1731337531,"level":"DEFAULT","message":"tempfile: removed tempfile C:\\Program Files\\Velociraptor\\Tools\\tmp391399109\n"}
{"client_time":1731337532,"level":"DEFAULT","message":"Sleeping 7 Seconds\n"}
{"client_time":1731337539,"level":"DEFAULT","message":"URL for thor10.7lite-win-pack_nolic.zip is at https://xxx.azurewebsites.net/file/thor10.7lite-win-pack_nolic.zip and has hash of c1a306af9e9162d14d52374e188a8dc20005752e6c5b580e8316f2323ce7591c\n"}
{"client_time":1731337539,"level":"DEFAULT","message":"Fetching https://xxx.azurewebsites.net/file/thor10.7lite-win-pack_nolic.zip\n"}
{"client_time":1731337539,"level":"DEFAULT","message":"http_client: Downloading https://xxx.azurewebsites.net/file/thor10.7lite-win-pack_nolic.zip into C:\\Program Files\\Velociraptor\\Tools\\tmp1158147984.tmp\n"}
{"client_time":1731337542,"level":"DEFAULT","message":"downloaded hash of C:\\Program Files\\Velociraptor\\Tools\\tmp1158147984.tmp: c1a306af9e9162d14d52374e188a8dc20005752e6c5b580e8316f2323ce7591c, expected c1a306af9e9162d14d52374e188a8dc20005752e6c5b580e8316f2323ce7591c\n"}
{"client_time":1731337542,"level":"DEFAULT","message":"copy: Copying file from C:\\Program Files\\Velociraptor\\Tools\\tmp1158147984.tmp into C:\\Program Files\\Velociraptor\\Tools\\thor10.7lite-win-pack_nolic.zip\n"}
{"client_time":1731337543,"level":"DEFAULT","message":"tempfile: removing tempfile C:\\Program Files\\Velociraptor\\Tools\\tmp1158147984.tmp\n"}
{"client_time":1731337543,"level":"DEFAULT","message":"tempfile: removed tempfile C:\\Program Files\\Velociraptor\\Tools\\tmp1158147984.tmp\n"}
{"client_time":1731337543,"level":"DEFAULT","message":"Adding global destructor for C:\\Program Files\\Velociraptor\\Tools\\tmp3319932095\n"}
{"client_time":1731337543,"level":"WARN","message":"Materialize of LET Unzip: Expand larger than 1000 rows, VQL will switch to tempfile backing on C:\\Program Files\\Velociraptor\\Tools\\VQL_Unzip_.jsonl1648725754 which will be much slower.\n"}
{"client_time":1731337544,"level":"DEFAULT","message":"execve: Running external command [[C:\\Program Files\\Velociraptor\\Tools\\tmp3319932095\\thor64-lite.exe --json -e C:\\Program Files\\Velociraptor\\Tools\\tmp3319932095] []]\n"}
{"client_time":1731337544,"level":"DEFAULT","message":"execve: exec: \"[C:\\\\Program Files\\\\Velociraptor\\\\Tools\\\\tmp3319932095\\\\thor64-lite.exe --json -e C:\\\\Program Files\\\\Velociraptor\\\\Tools\\\\tmp3319932095]\": executable file not found in %PATH%\n"}
{"client_time":1731337544,"level":"DEFAULT","message":"Generic.Scanner.ThorZIP/ThorExec: Time 0: Generic.Scanner.ThorZIP/ThorExec: Sending response part 0 3 B (1 rows)."}
{"client_time":1731337544,"level":"DEFAULT","message":"read_file: Field filename Expecting a path arg type, not types.Null\n"}
{"client_time":1731337544,"level":"DEFAULT","message":"Generic.Scanner.ThorZIP/ThorExec: Time 0: Generic.Scanner.ThorZIP/ThorResultsJson: Sending response part 0 12 B (1 rows)."}
{"client_time":1731337544,"level":"INFO","message":"Collection Generic.Scanner.ThorZIP/ThorExec is done after 13.4206963s\n"}
{"client_time":1731337544,"level":"DEFAULT","message":"tempfile: removing tempfile C:\\Program Files\\Velociraptor\\Tools\\VQL_Unzip_.jsonl1648725754\n"}
{"client_time":1731337544,"level":"DEFAULT","message":"tempfile: removed tempfile C:\\Program Files\\Velociraptor\\Tools\\VQL_Unzip_.jsonl1648725754\n"}
{"client_time":1731337544,"level":"DEFAULT","message":"RemoveDirectory: removing tempdir C:\\Program Files\\Velociraptor\\Tools\\tmp3319932095\n"}
{"client_time":1731337545,"level":"DEFAULT","message":"RemoveDirectory: removed tempdir C:\\Program Files\\Velociraptor\\Tools\\tmp3319932095\n"}
{"client_time":1731337545,"level":"DEBUG","message":"Query Stats: {\"RowsScanned\":3061,\"PluginsCalled\":18,\"FunctionsCalled\":9,\"ProtocolSearch\":459,\"ScopeCopy\":6167}\n"}

Could you send us a screenshot of the directory structure inside of that ZIP file? The binary is probably just inside of a sub folder instead of the root folder.

The structure looks okay.
As you can see the problem is that it doesn't find the executable after the extraction
{"client_time":1731337543,"level":"DEFAULT","message":"Adding global destructor for C:\\Program Files\\Velociraptor\\Tools\\tmp3319932095\n"}
{"client_time":1731337543,"level":"WARN","message":"Materialize of LET Unzip: Expand larger than 1000 rows, VQL will switch to tempfile backing on C:\\Program Files\\Velociraptor\\Tools\\VQL_Unzip_.jsonl1648725754 which will be much slower.\n"}
{"client_time":1731337544,"level":"DEFAULT","message":"execve: Running external command [[C:\\Program Files\\Velociraptor\\Tools\\tmp3319932095\\thor64-lite.exe --json -e C:\\Program Files\\Velociraptor\\Tools\\tmp3319932095] []]\n"}
{"client_time":1731337544,"level":"DEFAULT","message":"execve: exec: \"[C:\\\\Program Files\\\\Velociraptor\\\\Tools\\\\tmp3319932095\\\\thor64-lite.exe --json -e C:\\\\Program Files\\\\Velociraptor\\\\Tools\\\\tmp3319932095]\": executable file not found in %PATH%\n"}

It could be caused by:

AV / EDR
almost full hard disk

Could you verify the SHA256 hash of the ZIP file before you upload it to AWS?

same issue,

Le tme know when you've found the reason.

I have fixed it by changing it to:
LET Exec <= SELECT * FROM execve(argv=[(Executable[0]).F, "--json", "-e", TmpDir])

authors: Neo23x0 gibranalvinda simonstegard


text:
Bootstrap No Longer Available to Download and Unable to Sync from Block 0

The bootstrap is no longer available to download and the protocol is unable to sync from Block 0 without getting stuck on the known block (known issue). @VidereLicet please fix this major issue. We no longer have a way to run a full node making the protocol extremely centralized.

I started looking @ IP's @ the Break, and a Hong Kong Chi-Com IP pops out!
47.75.59.40
I blocked that IP and tried downloading the Blockchain again, and this time @ start of Sync it seemed to not throw type of Orphan before the other Hard Crash Block, but it usually always heals from restarting the Nexus Client!
I think Hard-code a Geo Block for Hong Kong!  Chi-Coms use it as a so called "Democratic" Digital Hub to spread as a Chi-Com Advance Guard!  But it's simple to Geo Block all HK as it has it's own Country Code HK, but otherwise I would recommending maybe blocking this Block of IP's!  Plus It would be a Revolutionary Act to proactively GEO Block the Chi-Coms who only spread Crime around the World and Drugs using Crypto, there has been nothing positive to ever come out of China in regards to Crypto development!  ASIC's will be history as they aren't QUANTUM SECURE~!
Binance is owned by Canadian Born Chi-Com who mastered how the Kosher Bankers Manipulate the System and Setup his Persona as the Hallmark of A+ No Fraud Backup Fund Repair Asian Guy Perfectly!
There is no real Scenario where Nexus Geo Blocking the Chi-Coms could be a bad thing as they provide nothing but wasteful destruction using their Now Privileged Position in the World brought about by Corrupt Elements within the Earth mainly the Kiken Mossad and Vatican once the Jewish Mafias worked out all the Rat Runs for the Chi-Coms to be their Slave labor Engine, to depose the West Morally and Financially dumping the Western Populations in horror of their Porn Capitals Hundred Billion a year Profit Industry @ same time propping up Chi-Com slave labor and Position in the World!
Mostly without a proper Judge upon Earth with enough Power as even now Israel and Russia have both International Arrest Warrants from the UN War Crimes Tribunal but are readily ignored by all the main Actors within each Geo Blocked Sphere the Kosher Bankers have created of the Earth as Sanctions are the Kosher Bankers #1 Tool for Control!
47.75.59.40
47.75.0/255.0/255

On a more Technical Note with Nexus Development
As far as I know Nexus Tritium can cut off the Blockchain from that fork in 2020!  So the Blockchain would be much smaller and start downloading from 2020 or something similar like that!
The main Strategy I think Colin is trying to Solve is using the Old Nexus Bitcoin Code base to Soon have Nexus be able to Import Bitcoin Wallet.dat Files into their Sigchains ect...........and use it as Collateral for NXS/BTC Exchange within the Tritium Nexus GUI
But I think Monero is much better long term Strategy for many reasons, most of which I think it has a lot of Value Creation Compared to Bitcoin's 1.5 Trillion Market Cap Versus Monero 5 Billion Market Cap!
As for this Blockchain Sync Business I am not too worried about it, I could setup my Computer to use Tor Firewall and get it to work, however I don't trust Tor, and Prefer Wireguard Firewall!
I think it will get worked out anyway, the Next Release should be the Hard Fork Release, so it's just a matter of where to place the Hard Fork, but IDK in reality without a lot more discussion!
Either way I think Nexus will as Colin said cut the Old Blockchain Bloat on the Old Code base!  That is where this Issue is stemming from on Bitcoin Code Nexus Blocks from 2015, Not the New Tritium Code base just to Clarify!  So it will get Resolved 1 way or another!

Bootstrap is now consistently available.

authors: NamecoinGithub NealHelman S4X1

repo: Nexusoft/LLL-TAO


text:
Very slow loading behind Cloudflare proxy

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

Yes

Are you sure you're not using someone else's docker image?

Yes

Have you searched for similar issues (both open and closed)?

Yes

Describe the bug
Very slow loading times when behind Cloudflare proxy. Not going through Cloudflare proxy works fine. Issue showed up in 2.11.0, as rolling back to 2.10.4 resolves the problem.
Nginx Proxy Manager Version
2.11.0, 2.11.1, 2.11.2
Additional context
May be related to #3365?

As stated on #3365 running this project behind a proxy isn't really its intended purpose. That said, just like any other website, there shouldn't be a problem. Are you proxying to NPM over HTTP or HTTPS?

repo: NginxProxyManager/nginx-proxy-manager


text:
Bundling FFmpeg

I just tried ScreenToGif for the first time and was a bit surprised to see that exporting to MP4 wasn't natively supported. I realized that it supports FFmpeg output, but it requires it to be installed.
I was wondering if there any limitation to bundle FFmpeg as part of ScreenToGif so users don't have to install it separately?
(I guess retain the ability to override the FFmpeg install as an advanced option)

Also noticed that you do have a button to download FFmpeg in the options, but it prompts the user to specify a download location.
Could I suggest if the app is installed, then at least this button by default would save FFmpeg to the installation directory (so it's 1 step less for the user)?

You might also want to do what ShareX has integrated with their software: an auto-download feature.  That will maintain a small download size and enable video export for the users that need it.

Alternatively, you might point to one of a number of available open FFMPEG font-ends for a video export tool that works with the amazing number of features built into that tool.
Some possibilities:

FFmpegCatapult: https://github.com/mylesthaiss/FFmpegCatapult
SmartFFmpeg: http://freeware.satria.de/SmartFFmpeg/index.php?lang=EN
WinFF: www.biggmatt.com/winff/

Related thread: #376

Worrying about the size of the program is completely wrong headed. Also, ffmpeg encodes to a mind-boggling number of formats, in various containers, so the "MP4" complaint is wrong.

I searched my  machine and it turned out that there are 71 instances of ffmpeg.exe used by various programs- players, converters, video, audio and tag editors, downloaders, catalogs, servers, etc. Most of these programs come with absolute, hard-coded paths to ffmpeg.exe and as a result I have not just multiple instances but also different (in most cases- outdated) versions of ffmpeg.exe. Besides  a huge waste of space it is also a huge waste of time to update these instances one by one.

#563

authors: NickeManarin longzheng riverar smaragdus vatterspun

repo: NickeManarin/ScreenToGif

license: MS-PL


text:
🛑 cedro is down

In b602b57, cedro (https://www.cedro.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cedro is back up in f847b4c after 10 minutes.

repo: NicolasAbihaggle/serviciosestados


text:
Arch version fails to build (includes proposed fix)

As of the new version, I'm having issues installing this on Arch linux via the AUR. I did some digging and discovered that the md5sum changed and the location and name of the .desktop file have also been modified. I was able to get it to build with a few modifications:
The md5sum of the file actually downloaded was d47e22482755a2fc73061860c09d41ac - this might need updated in the source code. If you put this value into PKGBUILD after cloning the repo and run makepkg, it works:
source=('https://shadow.tech/linux/shadow-beta.zip')
md5sums=('d47e22482755a2fc73061860c09d41ac')

The .desktop file, it is actually named shadow-dev.desktop in the new archive so the PKGBUILD script should be updated to reflect this:
	### Edit launcher
	sed -e 's/^Categories=.*$/Categories=Games;Game;Utility;Virtualization/g' "${pkgdir}/usr/share/applications/shadow-dev.desktop" > shadow-beta.desktop
	chmod g-w shadow-beta.desktop

	rm "${pkgdir}/usr/share/applications/shadow-dev.desktop"
	mv shadow-beta.desktop "${pkgdir}/usr/share/applications/shadow-beta.desktop"

Please update this so that others can benefit :)

AUR package updated, thanks to you :)

authors: NicolasGuilloux dylanmtaylor

repo: NicolasGuilloux/blade-shadow-beta


text:
The "Access the webcam" test is outdated

navigator.getUserMedia is deprecated and was replaced by navigator.mediaDevices.getUserMedia

Fixed

authors: LMLB NielsLeenheer


text:
How to disable styles?

Hi,
I want to disable CSS styles plugin, I do not see a way to do it?

What is CSS styles plugin?

What is CSS styles plugin?

vue-slider-component , can I disable styles?

What do you want to do, whether it is a style with the slider disabled or not using the default style of the slider?

not using the default style of the slider  https://yadi.sk/i/p0XVuOLLauGBAg
I use my own styles and I don't need to load slider styles doing the double work of overriding css

Version 2.0 is not easy to rewrite styles, you can upgrade to version 3.0.
You can refer https://nightcatsama.github.io/vue-slider-component/#/style

Version 2.0 is not easy to rewrite styles, you can upgrade to version 3.0.
You can refer https://nightcatsama.github.io/vue-slider-component/#/style

Yes version 3 solved my problem, thanks

authors: NightCatSama Sergey-Ssn

repo: NightCatSama/vue-slider-component


text:
[Feature] – Return transitive dependencies list in alphabetical order

It would be nice if we had this feature to have consistency in the results.

Yes, we can sort the transitive dependencies alphabetically for same error reporting each time 👍
I am more than welcome if you want to contribute to this repo by creating a PR

Yes, we can sort the transitive dependencies alphabetically for same error reporting each time 👍
I am more than welcome @douglasgondim  if you want to contribute to this repo by creating a PR

authors: Nikoloutsos douglasgondim kostasniks


text:
Replace PRIMITIVE_COLORS with COLORS

Replacement of PRIMITIVE_COLORS variable with COLORS to make it shorter and more convenient to use. Name primitive colors makes no since we have no "non-primitive" colors.

It's breaking changes

It should have 3.0 version because it's breaking changes or you should provide backward compatibility

Agree, thanks.

repo: NilFoundation/ui-kit


text:
can't build rss2irc from haskellPackages

nix-env -iA nixos.haskellPackages.rss2irc

output:
Preprocessing executable 'rss2irc' for rss2irc-1.0.6...

Feed.hs:24:8:
    Could not find module ‘Network.URI’
    It is a member of the hidden package ‘network-uri-2.6.0.3@netwo_8g2FaihlDOW7yH7DhmRvHt’.
    Perhaps you need to add ‘network-uri’ to the build-depends in your .cabal file.
    Use -v to see a list of the files searched for.
builder for ‘/nix/store/mw7ai3bngizdcasgajqsdmi22nmyk49s-rss2irc-1.0.6.drv’ failed with exit code 1

It's probably best to report this issue upstream. The package is quite outdated (http://packdeps.haskellers.com/feed?needle=rss2irc) and needs some attention before recent compilers can build it.

authors: Lassulus peti

repo: NixOS/nixpkgs


text:
gimp plugin wavelet-sharpen replaces gimp on upgrade

Describe the bug
Using the current unstable channel, if install gimp in my user environment and then do an upgrade, Nix replaces gimp with the wavelet-sharpen plugin and effectively uninstalls gimp itself from the user environment. This does not happen in the stable branch 20.09.
To Reproduce
Here is a transcript of what happens:
$ which gimp
which: no gimp in (/run/wrappers/bin:/home/manu/.nix-profile/bin:/etc/profiles/per-user/manu/bin:/nix/var/nix/profiles/default/bin:/run/current-system/sw/bin)
$ nix-env -iA nixpkgs.gimp
installing 'gimp-2.10.22'
$ which gimp
/home/manu/.nix-profile/bin/gimp
$ nix-env -q | grep gimp
gimp-2.10.22
$ nix-env --upgrade
upgrading 'gimp-2.10.22' to 'gimp-2.10.22-plugin-wavelet-sharpen-0.1.2'
$ which gimp
which: no gimp in (/run/wrappers/bin:/home/manu/.nix-profile/bin:/etc/profiles/per-user/manu/bin:/nix/var/nix/profiles/default/bin:/run/current-system/sw/bin)
$ nix-env -q | grep gimp
gimp-2.10.22-plugin-wavelet-sharpen-0.1.2
$ nix-env --uninstall gimp
uninstalling 'gimp-2.10.22-plugin-wavelet-sharpen-0.1.2'

Expected behavior
I expect gimp to be upgraded.
Apparently, the fact that that gimp-2.10.22-plugin-wavelet-sharpen-0.1.2 contains numbers in the middle is the source of the problem, as if 2.10.22-plugin-wavelet-sharpen-0.1.2 was a version number, and higher than 2.10.22.
Notify maintainers
The gimp package is maintained by @jtojnar, I don't know about the wavelet-sharpen plugin.
Metadata

system: "x86_64-linux"
host os: Linux 5.4.99, NixOS, 20.09.3246.d4189f68fdb (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.10
channels(manu): "nixpkgs-21.05pre273332.5df05c902cd"
channels(root): "nixos-20.09.3343.8d82c865b41"
nixpkgs: /home/manu/.nix-defexpr/channels/nixpkgs

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

Ugh, I can’t wait for nix-env to be abandoned.
This is a regression caused by https://github.com/NixOS/nixpkgs/commit/ef5475235ce4f3d1405dca5653cbe3599f0ff637 cc @erictapen

On NixOS you probably shouldn't use nix-env at all (use configuration.nix or home-manager instead) and documentation should not encourage to use it imo: https://github.com/NixOS/nixos-homepage/issues/672

I'm all for using the declarative approach to handle user packages, and actually my current setup consists mostly in defining an environment with buildEnv in ~/.config/nixpkgs/config.nix with the packages I want. However I find the stateful system of nix-env to be a useful middle-ground between full declarative and using nix-shell for short-term usage of specific packages.
As a side note, Gimp ended up installed through nix-env instead of config*.nix because of space constraints. On a system with a few gigabytes of storage allocated for /nix/store, upgrading a whole system with several big packages (e.g. Gimp, TeXlive, Haskell and other things) becomes a problem because you must have two versions of each present at the same time before you can switch to the new generation and garbage-collect the old one. At least, with nix-env, you can uninstall those, collect garbage, upgrade and then install them back without having to hack on your declarative configuration.
As for Home Manager, I admit I am reluctant to make the switch from my years-old tuned and portable home configuration as long as the first words of its documentation are a big warning on the fact that it may break things.

Ugh, I can’t wait for nix-env to be abandoned.

To be fair, we would need to also get rid of this behaviour:
nix-repl> builtins.parseDrvName "gimp-2.10.22-plugin-wavelet-sharpen-0.1.2"
{ name = "gimp"; version = "2.10.22-plugin-wavelet-sharpen-0.1.2"; }

Yes, I would kill parseDrvName too, if I could.

authors: jtojnar symphorien veprbl xunam


text:
Q: How can i write an output of a command to file using nixlang?

I want to create a file with the content from stdout of command openssl rand -hex 64 to be provided to services.discourse.secretKeyBaseFile
How can i do that in a reproducible way assuming that the current way is do a build with services.discourse.secretKeyBaseFile = "/run/keys/secret_key_base" and after build do manually openssl rand -hex 64 > /run/keys/secret_key_base && chown discourse:discourse /run/keys/secret_key_base && chmod 440 /run/keys/secret_key_base ?

If you use nixlang I think the secret will end up in the nix store (not so secret). I would write a systemd service for your openssl commands that creates the /run/keys/secret_key_base file at runtime, and makes the discourse service wait for that file.

@bjornfor I rather want to handle it through nixlang where the theory is:
services.discourse.secretKeyBaseFile = pkgs.writeFile "/run/keys/secret_key_base" ''
	${generateTheString}
'';

Where i don't know how could i do the ${generateTheString}

Probably something like reading /dev/random ?
[kreyren@leonid:~]$ head -n1 /dev/random
:#0��Ǟ0�PXn�����t�����gn�p(o�V�+�>g�<̻�Jсo�ԟ�ڀ4 {�I��_f���<�{

runCommand and friends can write data to the nix store, from a shell script. See here: https://nixos.org/manual/nixpkgs/stable/#trivial-builder-runCommand

@legendofmiracles I want that outside of nix store, because it's a secret.. Which i assume is not possible?

You could use nix-instantiate --eval --strict to get Nix values without necessarily writing them to the store. It's what NixOps uses for its keys (secrets) feature. It even has a resources to generate an ssh key and store it in the NixOps state, or do the same for an arbitrary command on the deployer's machine. Sadly, we don't have generated docs for NixOps 2 at the moment, but you can find the option descriptions for these resources here: https://github.com/NixOS/nixops/tree/master/nix

authors: Kreyren bjornfor legendofmiracles roberth


text:
Packaging request: normcap

Project description
OCR-powered screenshot tool to capture text instead of images.
Metadata

homepage URL: https://dynobo.github.io/normcap/
source URL: https://github.com/dynobo/normcap
license: GPL3
platforms: unix
example package: AUR (PKGBUILD)

I started working on this but I'm stuck at how to package with qt

This seems to be a poetry-based project, meaning you should set format="pyproject" and add poetry-core as a nativeBuildInput. If adding the python qt libraries is not sufficient, then try using the hooks for Qt applications.

https://github.com/nix-community/nur-combined/blob/6bddae47680482383b5769dd3aa7d82b88e6cbc8/repos/renesat/pkgs/normcap/default.nix#L42

I'll try to make a PR with this, ty

Is it possible that normcap causes issues in recent NixOS?

error: builder for '/nix/store/zk4imnx8zyibcghr5lriq31rwsyzcpvn-normcap-0.5.4.drv' failed with exit code 1;
       last 10 log lines:
       > =========================== short test summary info ============================
       > FAILED tests/test_app.py::test_get_application - RuntimeError: Please destroy the QApplication singleton before creating a n...
       > FAILED tests/tests_gui/test_loading_indicator.py::test_radius - AttributeError: 'LoadingIndicator' object has no attribute 'timer'
       > FAILED tests/tests_gui/test_loading_indicator.py::test_opacities - AttributeError: 'LoadingIndicator' object has no attribute 'timer'
       > FAILED tests/tests_gui/test_loading_indicator.py::test_show_starts_timer - AttributeError: 'LoadingIndicator' object has no attribute 'timer'
       > FAILED tests/tests_gui/test_loading_indicator.py::test_hide_stops_timer - AttributeError: 'LoadingIndicator' object has no attribute 'timer'
       > FAILED tests/tests_gui/test_loading_indicator.py::test_frame_count_progresses - AttributeError: 'LoadingIndicator' object has no attribute 'timer'
       > FAILED tests/tests_gui/test_loading_indicator.py::test_circles_are_rendered - AttributeError: 'LoadingIndicator' object has no attribute 'timer'
       > ==== 7 failed, 297 passed, 15 skipped, 21 deselected, 13 warnings in 5.69s =====
       > /nix/store/9wnvhjyxjykwn5y06xc9a2h8rs5fbfia-stdenv-linux/setup: line 1579: pop_var_context: head of shell_variables not a function context
       For full logs, run 'nix log /nix/store/zk4imnx8zyibcghr5lriq31rwsyzcpvn-normcap-0.5.4.drv'.
error: 1 dependencies of derivation '/nix/store/2pvf5yvj6qi68k6hzlp6s3pjab7m09m5-home-manager-path.drv' failed to build
error: 1 dependencies of derivation '/nix/store/mja27h5nbrcn4m82rb2mc972sxr625bp-home-manager-generation.drv' failed to build
error: 1 dependencies of derivation '/nix/store/2wxil3bbrlk02vkg8qvwgr56q7i936q7-user-environment.drv' failed to build
error: 1 dependencies of derivation '/nix/store/wib7xmij8pai67c6mvdvcplzqkl797n5-etc.drv' failed to build
error: 1 dependencies of derivation '/nix/store/lbcml8mj88hiv0s2glv86ks2gm5lbr29-nixos-system-nixos-24.05.20240421.6143fc5.drv' failed to build

> nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.21, NixOS, 24.05 (Uakari), 24.05.20240312.0ad13a6`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"nixos-23.11, unstable"`
 - nixpkgs: `/nix/store/k5l01g2zwhysjyl5zjvg5zxnj0lyxpp1-source`

Fixed by https://github.com/NixOS/nixpkgs/pull/305822 which reaches unstable in a few fays

authors: I-Want-ToBelieve cafkafk koppor pbsds


text:
paperless-ngx  pdf import not working

Describe the bug
Using unstable paperless-ngx-1.9.2 (on a 22.05 system) I am no longer able to import documents from the web interface as they fail with a MissingDependencyError in unpaper. Sadly parts of the error log appear to be missing, I am not sure how to get the full output.
Steps To Reproduce
Steps to reproduce the behavior:

Configure service.paperless with package = pkgs.unstable.paperless-ngx
Import document from the web interface

Expected behavior
Document should be processed and show up in the document list
Log
Oct 31 15:24:42 nixos paperless-ngx[38670]: [2022-10-31 14:24:42,168] [ERROR] [paperless.consumer] Error while consuming document censored-document-name.pdf: MissingDependencyError: Ran program '/nix/store/s9qywrdw15ihkxw5fwjya47551fs58vh-unpaper-7.0.0/bin/unpaper' but it exited with an error:
Oct 31 15:24:42 nixos paperless-ngx[38670]: Traceback (most recent call last):
Oct 31 15:24:42 nixos paperless-ngx[38670]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/subprocess/__init__.py", line 157, in get_version
Oct 31 15:24:42 nixos paperless-ngx[38670]:     proc = run(
Oct 31 15:24:42 nixos paperless-ngx[38670]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/subprocess/__init__.py", line 58, in run
Oct 31 15:24:42 nixos paperless-ngx[38670]:     proc = subprocess_run(args, env=env, check=check, **kwargs)
Oct 31 15:24:42 nixos paperless-ngx[38670]:   File "/nix/store/fkcl1wzq3106qqgl84bhgk1lp56q6bzg-python3-3.10.7/lib/python3.10/subprocess.py", line 524, in run
Oct 31 15:24:42 nixos paperless-ngx[38670]:     raise CalledProcessError(retcode, process.args,
Oct 31 15:24:42 nixos paperless-ngx[38670]: subprocess.CalledProcessError: Command '['/nix/store/s9qywrdw15ihkxw5fwjya47551fs58vh-unpaper-7.0.0/bin/unpaper', '--version']' died with <Signals.SIGSYS: 31>.
Oct 31 15:24:42 nixos paperless-ngx[38670]: The above exception was the direct cause of the following exception:
Oct 31 15:24:42 nixos paperless-ngx[38670]: Traceback (most recent call last):
Oct 31 15:24:42 nixos paperless-ngx[38670]:   File "/nix/store/za5yxgmxgmf8rdlhni9xg3w7mcwnf9bm-paperless-ngx-1.9.2/lib/paperless-ngx/src/paperless_tesseract/parsers.py", line 277, in parse
Oct 31 15:24:42 nixos paperless-ngx[38670]:     ocrmypdf.ocr(**args)
Oct 31 15:24:42 nixos paperless-ngx[38670]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/api.py", line 339, in ocr
Oct 31 15:24:42 nixos paperless-ngx[38670]:     check_options(options, plugin_manager)
Oct 31 15:24:42 nixos paperless-ngx[38670]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/_validation.py", line 245, in check_options
Oct 31 15:24:42 nixos paperless-ngx[38670]:     _check_plugin_invariant_options(options)
Oct 31 15:24:42 nixos paperless-ngx[38670]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/_validation.py", line 232, in _check_plugin_invariant_options
Oct 31 15:24:42 nixos paperless-ngx[38670]:     check_options_preprocessing(options)
Oct 31 15:24:42 nixos paperless-ngx[38670]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/_validation.py", line 132, in check_options_preprocessing
Oct 31 15:24:42 nixos paperless-ngx[38670]:     check_external_program(
Oct 31 15:24:42 nixos paperless-ngx[38670]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/subprocess/__init__.py", line 331, in check_external_program
Oct 31 15:24:42 nixos paperless-ngx[38670]:     found_version = version_checker()
Oct 31 15:24:42 nixos paperless-ngx[38670]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/_exec/unpaper.py", line 69, in version
Oct 31 15:24:42 nixos paperless-ngx[38670]:     return get_version('/nix/store/s9qywrdw15ihkxw5fwjya47551fs58vh-unpaper-7.0.0/bin/unpaper')
Oct 31 15:24:42 nixos paperless-ngx[38670]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/subprocess/__init__.py", line 173, in get_version
Oct 31 15:24:42 nixos paperless-ngx[38670]:     raise MissingDependencyError(
Oct 31 15:24:42 nixos paperless-ngx[38670]: ocrmypdf.exceptions.MissingDependencyError: Ran program '/nix/store/s9qywrdw15ihkxw5fwjya47551fs58vh-unpaper-7.0.0/bin/unpaper' but it exited with an error:
Oct 31 15:24:42 nixos paperless-ngx[38670]: The above exception was the direct cause of the following exception:
Oct 31 15:24:42 nixos paperless-ngx[38670]: Traceback (most recent call last):
Oct 31 15:24:42 nixos paperless-ngx[38670]:   File "/nix/store/za5yxgmxgmf8rdlhni9xg3w7mcwnf9bm-paperless-ngx-1.9.2/lib/paperless-ngx/src/documents/consumer.py", line 320, in try_consume_file
Oct 31 15:24:42 nixos paperless-ngx[38670]:     document_parser.parse(self.path, mime_type, self.filename)
Oct 31 15:24:42 nixos paperless-ngx[38670]:   File "/nix/store/za5yxgmxgmf8rdlhni9xg3w7mcwnf9bm-paperless-ngx-1.9.2/lib/paperless-ngx/src/paperless_tesseract/parsers.py", line 333, in parse
Oct 31 15:24:42 nixos paperless-ngx[38670]:     raise ParseError(f"{e.__class__.__name__}: {str(e)}") from e
Oct 31 15:24:42 nixos paperless-ngx[38670]: documents.parsers.ParseError: MissingDependencyError: Ran program '/nix/store/s9qywrdw15ihkxw5fwjya47551fs58vh-unpaper-7.0.0/bin/unpaper' but it exited with an error:
Oct 31 15:24:42 nixos paperless-ngx[38670]: 14:24:42 [Q] INFO Process-1:4 stopped doing work
Oct 31 15:24:42 nixos paperless-ngx[38596]: 14:24:42 [Q] ERROR Failed [censored-document-name.pdf] - censored-document-name.pdf: Error while consuming document censored-document-name.pdf: MissingDependencyError: Ran program '/nix/store/s9qywrdw15ihkxw5fwjya47551fs58vh-unpaper-7.0.0/bin/unpaper' but it exited with an error:
Oct 31 15:24:42 nixos paperless-ngx[38596]:  : Traceback (most recent call last):
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/subprocess/__init__.py", line 157, in get_version
Oct 31 15:24:42 nixos paperless-ngx[38596]:     proc = run(
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/subprocess/__init__.py", line 58, in run
Oct 31 15:24:42 nixos paperless-ngx[38596]:     proc = subprocess_run(args, env=env, check=check, **kwargs)
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/fkcl1wzq3106qqgl84bhgk1lp56q6bzg-python3-3.10.7/lib/python3.10/subprocess.py", line 524, in run
Oct 31 15:24:42 nixos paperless-ngx[38596]:     raise CalledProcessError(retcode, process.args,
Oct 31 15:24:42 nixos paperless-ngx[38596]: subprocess.CalledProcessError: Command '['/nix/store/s9qywrdw15ihkxw5fwjya47551fs58vh-unpaper-7.0.0/bin/unpaper', '--version']' died with <Signals.SIGSYS: 31>.
Oct 31 15:24:42 nixos paperless-ngx[38596]: The above exception was the direct cause of the following exception:
Oct 31 15:24:42 nixos paperless-ngx[38596]: Traceback (most recent call last):
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/za5yxgmxgmf8rdlhni9xg3w7mcwnf9bm-paperless-ngx-1.9.2/lib/paperless-ngx/src/paperless_tesseract/parsers.py", line 277, in parse
Oct 31 15:24:42 nixos paperless-ngx[38596]:     ocrmypdf.ocr(**args)
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/api.py", line 339, in ocr
Oct 31 15:24:42 nixos paperless-ngx[38596]:     check_options(options, plugin_manager)
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/_validation.py", line 245, in check_options
Oct 31 15:24:42 nixos paperless-ngx[38596]:     _check_plugin_invariant_options(options)
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/_validation.py", line 232, in _check_plugin_invariant_options
Oct 31 15:24:42 nixos paperless-ngx[38596]:     check_options_preprocessing(options)
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/_validation.py", line 132, in check_options_preprocessing
Oct 31 15:24:42 nixos paperless-ngx[38596]:     check_external_program(
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/subprocess/__init__.py", line 331, in check_external_program
Oct 31 15:24:42 nixos paperless-ngx[38596]:     found_version = version_checker()
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/_exec/unpaper.py", line 69, in version
Oct 31 15:24:42 nixos paperless-ngx[38596]:     return get_version('/nix/store/s9qywrdw15ihkxw5fwjya47551fs58vh-unpaper-7.0.0/bin/unpaper')
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/dk6m8qsyichiyh4b3v5d5b7kqjjnswgd-python3.10-ocrmypdf-13.7.0/lib/python3.10/site-packages/ocrmypdf/subprocess/__init__.py", line 173, in get_version
Oct 31 15:24:42 nixos paperless-ngx[38596]:     raise MissingDependencyError(
Oct 31 15:24:42 nixos paperless-ngx[38596]: ocrmypdf.exceptions.MissingDependencyError: Ran program '/nix/store/s9qywrdw15ihkxw5fwjya47551fs58vh-unpaper-7.0.0/bin/unpaper' but it exited with an error:
Oct 31 15:24:42 nixos paperless-ngx[38596]: The above exception was the direct cause of the following exception:
Oct 31 15:24:42 nixos paperless-ngx[38596]: Traceback (most recent call last):
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/28535xrr4xv02r0xlq6b5k9gqy96d9cq-python3.10-asgiref-3.5.2/lib/python3.10/site-packages/asgiref/sync.py", line 280, in main_wrap
Oct 31 15:24:42 nixos paperless-ngx[38596]:     raise exc_info[1]
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/za5yxgmxgmf8rdlhni9xg3w7mcwnf9bm-paperless-ngx-1.9.2/lib/paperless-ngx/src/documents/consumer.py", line 320, in try_consume_file
Oct 31 15:24:42 nixos paperless-ngx[38596]:     document_parser.parse(self.path, mime_type, self.filename)
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/za5yxgmxgmf8rdlhni9xg3w7mcwnf9bm-paperless-ngx-1.9.2/lib/paperless-ngx/src/paperless_tesseract/parsers.py", line 333, in parse
Oct 31 15:24:42 nixos paperless-ngx[38596]:     raise ParseError(f"{e.__class__.__name__}: {str(e)}") from e
Oct 31 15:24:42 nixos paperless-ngx[38596]: documents.parsers.ParseError: MissingDependencyError: Ran program '/nix/store/s9qywrdw15ihkxw5fwjya47551fs58vh-unpaper-7.0.0/bin/unpaper' but it exited with an error:
Oct 31 15:24:42 nixos paperless-ngx[38596]: The above exception was the direct cause of the following exception:
Oct 31 15:24:42 nixos paperless-ngx[38596]: Traceback (most recent call last):
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/0lg74rgck6skkf4p14ivqsk1nb60d5ck-python3.10-django-q-1.3.9/lib/python3.10/site-packages/django_q/cluster.py", line 454, in worker
Oct 31 15:24:42 nixos paperless-ngx[38596]:     res = f(*task["args"], **task["kwargs"])
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/za5yxgmxgmf8rdlhni9xg3w7mcwnf9bm-paperless-ngx-1.9.2/lib/paperless-ngx/src/documents/tasks.py", line 154, in consume_file
Oct 31 15:24:42 nixos paperless-ngx[38596]:     document = Consumer().try_consume_file(
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/za5yxgmxgmf8rdlhni9xg3w7mcwnf9bm-paperless-ngx-1.9.2/lib/paperless-ngx/src/documents/consumer.py", line 339, in try_consume_file
Oct 31 15:24:42 nixos paperless-ngx[38596]:     self._fail(
Oct 31 15:24:42 nixos paperless-ngx[38596]:   File "/nix/store/za5yxgmxgmf8rdlhni9xg3w7mcwnf9bm-paperless-ngx-1.9.2/lib/paperless-ngx/src/documents/consumer.py", line 90, in _fail
Oct 31 15:24:42 nixos paperless-ngx[38596]:     raise ConsumerError(f"{self.filename}: {log_message or message}") from exception
Oct 31 15:24:42 nixos paperless-ngx[38596]: documents.consumer.ConsumerError: censored-document-name.pdf: Error while consuming document censored-document-name.pdf: MissingDependencyError: Ran program '/nix/store/s9qywrdw15ihkxw5fwjya47551fs58vh-unpaper-7.0.0/bin/unpaper' but it exited with an error:
Oct 31 15:24:43 nixos paperless-ngx[38594]: 14:24:43 [Q] INFO recycled worker Process-1:4
Oct 31 15:24:43 nixos paperless-ngx[38685]: 14:24:43 [Q] INFO Process-1:5 ready for work at 38685

Notify maintainers
@lukegb, @gador, @erikarvstedt
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
- system: `"x86_64-linux"`
 - host os: `Linux 5.15.74, NixOS, 22.05 (Quokka), 22.05.3900.26eb67abc9a`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.8.1`
 - channels(hendrik): `""`
 - channels(root): `"nixos-22.05, nixos-hardware, nixpkgs-unstable"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

I just tested it on the current master as well as nixos-unstable. Both work just fine.
I suspect it has something to do with you runnung 22.05 and using a package from the unstable branch. I've seen weird errors when mixing those (e.g. with pgadmin here).

@hvraven is this still an issue?

Swapping out the executable with one from a different release is not supported.

authors: Atemu gador hvraven


text:
Cjdns can't create keys in /etc

Issue description
With cjdns enabled, the service complains that it can't create the necessary
keys in /etc
/nix/store/9ms47qxfd0qrxn4s689m9pbdrds57d59-unit-script/bin/cjdns-pre-start: line 9: /etc/cjdns.keys: Read-only file system
Steps to reproduce
services.cjdns.enable = true;
Technical details

System: 17.03pre96925.1c50bdd (Gorilla)
Nix version: 1.11.4
Nixpkgs version: 17.03pre96925.1c50bdd

This seems to be the relevant part in nixpkgs/nixos/modules/services/networking/cjdns.nix
      preStart = if cfg.confFile != null then "" else ''
        [ -e /etc/cjdns.keys ] && source /etc/cjdns.keys
        if [ -z "$CJDNS_PRIVATE_KEY" ]; then
            shopt -s lastpipe
            ${pkg}/bin/makekeys | { read private ipv6 public; }
            umask 0077
            echo "CJDNS_PRIVATE_KEY=$private" >> /etc/cjdns.keys
            echo -e "CJDNS_IPV6=$ipv6\nCJDNS_PUBLIC_KEY=$public" > /etc/cjdns.public
            chmod 600 /etc/cjdns.keys
            chmod 444 /etc/cjdns.public
        fi
        if [ -z "$CJDNS_ADMIN_PASSWORD" ]; then
            echo "CJDNS_ADMIN_PASSWORD=$(tr -dc A-Za-z0-9 </dev/urandom | head -c 96)" \
                >> /etc/cjdns.keys
        fi
      '';

What would be the Nixos way here?

Yes, it's because the "hardening" is too zealous, it needs to let preStart run as root (or not run with ProtectSystem = full or whatever)

@unlmtd can you try something like services.cjdns.serviceConfig.PermissionsStartOnly = true?

nixos-rebuild says that option doesnt exist

Agh, sorry, that should be systemd.services.cjdns.serviceConfig

That didn't do it, Im getting the same error.

Hm, I guess it doesn't pertain to fs isolation options; then you need to change ProtectSystem = "full" to true (or false).

ProtectSystem = "full" prevents writing the keys (/etc is read-only).
pre-start should be refactored to a separate systemd service without
that restriction, and cjdns run with that restriction in another
service.

This should be fixed by a0338afe5faa9f9e403e2caa52e4a8b60c272be9. A better fix is at https://github.com/joachifm/nixpkgs/tree/cjdns-init-keys but is not very well tested.

authors: joachifm tohl unlmtd


text:
With mlocate normal users cannot access /var/cache

Issue description
After switching from the default locate package to mlocate, normal users cannot access /var/cache anymore:
$ locate vertical-dark-opaque.tint2rc
locate: can not open `/var/cache/locatedb': Permission denied

$ ls -l /var | grep cache
drwxr-x---  4 root mlocate 4096 May 21 12:01 cache

My configuration.nix has the following:
  services.locate = {
    enable = true;
    prunePaths = [ "/tmp" "/var/cache" "/var/lock" "/var/run" "/var/spool" ];
    interval = "hourly";
    locate = pkgs.mlocate;
  };

Technical details

System: 17.09pre107265.0afb6d789c (Hummingbird)
Nix version: nix-env (Nix) 1.11.9
Nixpkgs version: "17.09pre107265.0afb6d789c"
Sandboxing enabled: build-use-sandbox = false

cc @pngwjpgh @andyjscott

More information:
# systemctl status update-locatedb
● update-locatedb.service - Update Locate Database
   Loaded: loaded (/nix/store/hvppx691rlm50drqmy3bbxgbihqacd20-unit-update-locatedb.service/update-locatedb.service; linked; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2017-05-24 06:00:01 BRT; 57min ago
  Process: 13268 ExecStart=/nix/store/mhwn1prj1vbn9lqqq2rxin2b8761y569-unit-script/bin/update-locatedb-start (code=exited, status=1/FAILURE)
 Main PID: 13268 (code=exited, status=1/FAILURE)

May 24 06:00:00 jrm.no-ip.org systemd[1]: Started Update Locate Database.
May 24 06:00:01 jrm.no-ip.org update-locatedb-start[13268]: /nix/store/j96vg63fm5v7kxfg308q99jasx40f05h-mlocate-0.26/bin/updatedb: unrecognized option '--localuser=nobody'
May 24 06:00:01 jrm.no-ip.org systemd[1]: update-locatedb.service: Main process exited, code=exited, status=1/FAILURE
May 24 06:00:01 jrm.no-ip.org systemd[1]: update-locatedb.service: Unit entered failed state.
May 24 06:00:01 jrm.no-ip.org systemd[1]: update-locatedb.service: Failed with result 'exit-code'.

This is caused by
            install -m ${if isMLocate then "0750" else "0755"} -o root -g ${if isMLocate then "mlocate" else "root"} -d $(dirname ${cfg.output})

This line should be replaced by
mkdir -m 0755 -p /var/cache

and the cfg.output option should be removed since there is really no reason to make that path configurable.

It looks like localuser = null; should also be set for mlocate due to the failure message:
... mlocate-0.26/bin/updatedb: unrecognized option '--localuser=nobody'

Currently a warning is shown but it should probably be an error as it breaks the update service.

authors: andyjscott edolstra romildo


text:
Package request: ondsel

Project description

Metadata

homepage URL: https://ondsel.com/
source URL:
license: mit, bsd, gpl2+ , ...
platforms: unix, linux, darwin, ...

Add a :+1: reaction to issues you find important.

duplicate of #284524


text:
Keybase GUI shouldn't check hardcoded /keybase mountpoint

Issue description
The keybase-gui wrapper checks for a hardcoded value to see if kbfs is mounted there.
However, this is configurable through the kbfs service, and defaults to ~/keybase.
The wrapper should either be hard-coded to whatever options.services.kbfs.mountPoint is, or verify the status some other way (e.g calling keybase status).
Steps to reproduce

Set the following in configuration.nixservices.keybase.enable = true;
services.kbfs.enable = true;

nix-env -iA nixos.keybase-gui
rebuild your configuration
try to launch keybase-gui

Expected behavior
Tests pass and keybase-gui launches.
Actual behavior
Keybase is not mounted to /keybase.
You might need to run: kbfsfuse /keybase
Set NIX_SKIP_KEYBASE_CHECKS=1 if you want to skip this check.

Technical details

System: 18.03pre119292.cfafd6f5a8 (Impala)
Nix version: 1.11.15
Nixpkgs version: 18.03pre119292.cfafd6f5a8
Sandboxing enabled: false

^ added hardcoded ~/keybase

Hi @brainrape ,
While this does look like it'll work in most scenarios it doesn't solve the overall problem in #31261 as it's now just looking at two options of hardcoded mountpoint.  A better solution would be to have the wrapper (I may have used the wrong word, if so, sorry) check for where keybase is mounted and then use that.
Are we not able to do that instead?

Updated PR with suggested fix.

@brainrape status?

Waiting for merge. @ mentioned maintainer.

authors: 5paceToast IvanMalison brainrape joncojonathan


text:
Update request: flutter 3.22.0 → 3.22.2

Package name: flutter
Latest released version: 3.22.2
Current version on the unstable channel: 3.22.0
Current version on the stable/release channel: 3.22.0

[x] Checked the nixpkgs pull requests

Notify maintainers
@NixOS/flutter

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

I can get this later today

I can get this later today

Thank you!

@Henry-Hiles #318396

I'll test that tomorrow thanks!

authors: Henry-Hiles RossComputerGuy


text:
tmux "crashes???" when konsole tab is closed

Issue description
I've been using Konsole for years and it works great with tmux. However since a few days ago on unstable small, when I close a Konsole tab, the tmux session "in that tab" gets killed/stopped or whatever....
Steps to reproduce

Use nixos-uunstable-small
Open Konsole
SSH into server
Start TMUX session
Right-click the konsole server tab and close it
Open new tap, ssh into same server again
Try to attach tmux

-->  https://youtu.be/-hXLPQfoI70
This has been happening not longer than 2 weeks I think... maybe even less than 1 week - not sure how long but not very long.
Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.

system: "x86_64-linux"
host os: Linux 4.14.21, NixOS, 18.03pre129183.a3c96fd4de3 (Impala)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 1.11.16
channels(hyper): ""
channels(root): "nixos-18.03pre129183.a3c96fd4de3"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

Ok, I tested this on another server - same behaviour:

system: "x86_64-linux"
host os: Linux 4.9.81, NixOS, 18.03pre128357.327a84749ed (Impala)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 1.11.16
channels(root): "nixos-18.03pre128357.327a84749ed"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

If I do this on a non-nixos server it all works fine.

I tested on a third server - this time I get the expected behaviour:

system: "x86_64-linux"
host os: Linux 4.9.75, NixOS, 18.03pre124914.b9806751074 (Impala)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 1.11.16
channels(root): "nixos-18.03pre124914.b9806751074"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

(so all works fine here)

Git bisect blames 672bb6b4abd27d9b2796152522b54f5b82c9f76b, I don't really see anything suspicious in there.

@LnL7 can you track this down with sysdig?

I'm not sure how much time I'll have this weekend, it's pretty easy to reproduce if anybody else wants to take a shot at it. Tmux will die when the ssh connection closes.
{ config, lib, pkgs, ... }:
{
  services.mingetty.autologinUser = "root";
  virtualisation.graphics = false;

  users.users.foo = {
    uid = 1000;
    group = "foo";
    isNormalUser = true;
    openssh.authorizedKeys.keys = [ "..." ];
  };
  users.groups.foo = { gid = 1000; };

  environment.systemPackages = [ pkgs.tmux ];
  services.openssh.enable = true;
}

export QEMU_NET_OPTS="hostfwd=tcp::3000-:22"
nixos-rebuild build-vm -I nixos-config=foo.nix -I nixpkgs=.
./result/bin/run-nixos-vm

ssh -i ./foo_rsa -p 3000 foo@127.0.0.1

Git bisect blames 672bb6b4abd27d9b2796152522b54f5b82c9f76b, but I don't really see anything suspicious in there.

One thing that may be related is that it brings 1de98e85681e7d1028fe866fa220c05ce1ed842f, "plasma: 5.11.5 -> 5.12.1".

@LnL7 ah now, this is a different one. You need lingering enabled in logind, otherwise tmux get killed once, you close your ssh connnection, because your logind seat gets deallocated: https://github.com/NixOS/nixpkgs/issues/29234#issuecomment-340230209

@sjau are you experiencing this on a server via ssh or locally in konsole?

I've seen that issue with nix-build, tmux works fine it uses /tmp/tmux-$UID for the socket.

@Mic92
I experience this via ssh.... I tested it on 3 nixos servers... the 2 newer ones have that isse, an older one doesn't. Also non-nixos server don't have that issue either.

I'm affected by this issue as well, except I'm using rxvt-unicode as the terminal

Btw, it only happens if I start tmux as normal user. When I login by ssh as root user, start tmux, close the konsole tab and re-login, the tmux session is still running

This can be fixed by doing loginctl enable-linger $USER, where $USER is your user.

enable-linger does not change the behaviour.

Note that there's also nothing systemd related in bad commit git bisect ended up in.

I also tested it and the offending comit that I found was
f5e96d3e1b7 xz: set CONFIG_SHELL to /bin/sh, fix retained reference to bootstrap

I tested it now also on a live server - reverting back to commit 122fa75b2de619ceace4b94a613683e54c34ddd0 makes tmux run properly again.

Ok, it might not be that commit as I used
git log --oneline b9806751074..327a84749ed
and those two commits are adjacent

Maybe both enabling lingering and using systemd-run is needed?
cc https://github.com/NixOS/nixpkgs/issues/15798#issuecomment-222352494
Hmm, I tried this but it failed to start due to permissions?
Feb 26 05:52:42 gravity polkitd[8886]: Registered Authentication Agent for unix-process:9169:30559097 (system bus name :1.31 [/run/current-system/sw/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Feb 26 05:52:42 gravity systemd[5382]: run-rff29cc1b2fea4c84ad8787b5f7c40649.scope: Failed to add PIDs to scope's control group: Permission denied
Feb 26 05:52:42 gravity systemd[5382]: run-rff29cc1b2fea4c84ad8787b5f7c40649.scope: Failed with result 'resources'.
Feb 26 05:52:42 gravity systemd[5382]: Failed to start /run/current-system/sw/bin/screen hydra.

Perhaps related: https://bbs.archlinux.org/viewtopic.php?id=227953
Is this really desirable default behavior? If so, should probably be mentioned in release notes....
From https://bbs.archlinux.org/viewtopic.php?pid=1724323#p1724323 possible hint:

Ok, it seems that the distro package maintainer enabled systemd hybrid cgroup without kernel support.

Or maybe -Ddefault-kill-user-processes=false? It does seem rather hostile default behavior.

@dtzWill long long time ago, when this specific crazy change in systemd started affecting NixOS, we did add KillUserProcesses=no into logind.conf and never removed it. Because the default systemd behaviour is indeed hostile to any user who has a chance to install NixOS on their own.

Oh, well hooray for that ^_^.  Good to know.
Chasing that:
$ find -L /run/current-system -name "logind.conf"
/run/current-system/etc/systemd/logind.conf
/run/current-system/systemd/etc/systemd/logind.conf

One of which sets KillUserProcesses=no nicely and the other does not.  Hopefully/presumably the other is just an example/dead-end. Hmm.

Erm, maybe this is the problem? Poking at loginctl to try to see what it is reading from or what config it ends up with led me to try:
$ loginctl -p KillUserProcesses show-session
KillUserProcesses=yes

(I'm not a systemd expert, can someone take a look? Thanks!)

@dtzWill Thanks for the debugging. This is probably a regression due to the recent systemd update. I can confirm that I have KillUserProcesses=no in /etc/systemd/logind.conf but loginctl -p KillUserProcesses show-session will print KillUserProcesses=yes.

@fpletz @dtzWill I looked into that using sysdig it only tries to read ${pkgs.systemd}/etc/systemd/logind.conf, but not /etc/systemd/logind.conf. That's why configuration is never applied.

I made a pull request to our systemd fork that fixes the issue.


text:
bumpver: 2020.1107 -> 2020.1108

Motivation for this change
Update bumpver to last version
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 106551 1

1 package built:

bumpver

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/405

authors: kfollesdal nixos-discourse


text:
nixos/nomad: fix data_dir-default-not-propagating bug

nixos/nomad: add newline
nixos/nomad: move data_dir default setting to allow propagation of default

Motivation for this change
The value of data_dir in the nomad module was only
set to its default if settings was not overridden at all.
This PR fixes the issue so that you can override settings
without having to specify the default value of data_dir.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Once https://github.com/NixOS/nixpkgs/pull/109761 is landed I will update the test here by removing the explicit data_dir setting.

Once https://github.com/NixOS/nixpkgs/pull/109761 is landed I will update the test here by removing the explicit data_dir setting.

Thanks for merging!

Thanks for merging!


text:
sharness: Init at 1.1.0-dev

Motivation for this change
A simple portable shell library to write and run tests adhering to the Test Anything Protocol.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Updated.

Result of nixpkgs-review pr 112309 at 44b06c61 run on aarch64-linux 1

1 package built:

sharness

authors: r-rmcgibbo spacefrogg


text:
python37Packages.django-auth-ldap: 2.2.0 -> 2.3.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python37Packages.django-auth-ldap is: "Django authentication backend that authenticates against an LDAP service"
meta.homepage for python37Packages.django-auth-ldap is: "https://github.com/django-auth-ldap/django-auth-ldap"
meta.changelog for python37Packages.django-auth-ldap is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.3.0 with grep in /nix/store/zlh1jxl5jky18vsnb6qcfcmzd9wdjiy8-python3.7-django-auth-ldap-2.3.0

directory tree listing: https://gist.github.com/7bf054df94955bd3decdb01135a3d207

du listing: https://gist.github.com/a1e51bef52b9f35a33d7a8dbbc37e91b

Rebuild report (if merged into master) (click to expand)

9 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
3 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
3 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python37Packages.django-auth-ldap
python38Packages.django-auth-ldap
python39Packages.django-auth-ldap

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zlh1jxl5jky18vsnb6qcfcmzd9wdjiy8-python3.7-django-auth-ldap-2.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python37Packages.django-auth-ldap https://github.com/r-ryantm/nixpkgs/archive/d158476f6d35ea676cb44fa0b125aa584a03a8b0.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zlh1jxl5jky18vsnb6qcfcmzd9wdjiy8-python3.7-django-auth-ldap-2.3.0
ls -la /nix/store/zlh1jxl5jky18vsnb6qcfcmzd9wdjiy8-python3.7-django-auth-ldap-2.3.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

python37Packages.django-auth-ldap
python38Packages.django-auth-ldap
python39Packages.django-auth-ldap

Maintainer pings
cc @mmai for testing.

Result of nixpkgs-review pr 113482 at d158476f run on aarch64-linux 1

3 packages built:

python37Packages.django-auth-ldap
python38Packages.django-auth-ldap
python39Packages.django-auth-ldap

authors: r-rmcgibbo r-ryantm


text:
zeek: 3.2.3 -> 3.2.4

Motivation for this change
https://github.com/zeek/zeek/releases/tag/v3.2.4
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 114198 run on x86_64-linux 1

1 package built:

zeek

authors: fabaff marsam


text:
liburcu: 0.12.1 -> 0.12.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/liburcu/versions.
meta.description for liburcu is: "Userspace RCU (read-copy-update) library"
meta.homepage for liburcu is: "https://lttng.org/urcu"
meta.changelog for liburcu is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.12.2 with grep in /nix/store/pxnbsjsc4cdvssbdzsqlwp6lpc0k6jlw-liburcu-0.12.2

directory tree listing: https://gist.github.com/1f47726e757fb7834481a662e34e6f23

du listing: https://gist.github.com/0493fa32bbae6ae5eac2181764686ce9

Rebuild report (if merged into master) (click to expand)

105 total rebuild path(s)

46 package rebuild(s)

46 x86_64-linux rebuild(s)
23 i686-linux rebuild(s)
9 x86_64-darwin rebuild(s)
27 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
appgate-sdp
aws-workspaces
bareos
bcachefs-tools
ceph
ceph-client
ceph-dev
codeql
coreclr
glusterfs
knot-dns
knot-resolver
libceph
liburcu
libvmi
lttng-tools
lttng-ust
multipath-tools
netsniff-ng
nfs-ganesha
ntirpc
osu-lazer
powershell
qemu_full
qemu_xen
qemu_xen-light
qemu_xen_4_10
qemu_xen_4_10-light
qubes-core-vchan-xen
samba4Full
sambaFull
vscode-extensions.ms-python.python
vscode-extensions.ms-vsliveshare.vsliveshare
xen
xen-light
xen-slim
xenPackages.xen-light
xenPackages.xen-slim
xenPackages.xen-vanilla
xenPackages.xen_4_10-light
xenPackages.xen_4_10-slim
xenPackages.xen_4_10-vanilla
xen_4_10
xen_4_10-light
xen_4_10-slim
zoxide

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pxnbsjsc4cdvssbdzsqlwp6lpc0k6jlw-liburcu-0.12.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A liburcu https://github.com/r-ryantm/nixpkgs/archive/af3185cdf18dea307f76a0550436c9e29b45f628.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pxnbsjsc4cdvssbdzsqlwp6lpc0k6jlw-liburcu-0.12.2
ls -la /nix/store/pxnbsjsc4cdvssbdzsqlwp6lpc0k6jlw-liburcu-0.12.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages marked as broken and skipped:

bareos
samba4Full

8 packages failed to build:

coreclr
libvmi
qemu_xen (qemu_xen_4_10)
qemu_xen-light (qemu_xen_4_10-light)
qubes-core-vchan-xen
xen
xen-light
xen-slim

23 packages built:

appgate-sdp
aws-workspaces
bcachefs-tools
ceph
ceph-client
codeql
glusterfs
knot-dns
knot-resolver
libceph
liburcu
lttngTools (lttng-tools)
lttngUst (lttng-ust)
multipath-tools (multipath_tools)
netsniff-ng
nfs-ganesha
ntirpc
osu-lazer
powershell
qemu_full
vscode-extensions.ms-python.python
vscode-extensions.ms-vsliveshare.vsliveshare
zoxide

Maintainer pings
cc @bjornfor for testing.

nixpkgs-review successful on macos 10.14

authors: r-ryantm risicle


text:
python3Packages.pyezviz: init at 0.1.8.7

Motivation for this change
Python interface for for Ezviz cameras
https://github.com/baqs/pyEzviz/
This is a Home Assistant dependency.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 118920 run on x86_64-linux 1

2 packages built:

python38Packages.pyezviz
python39Packages.pyezviz

Result of nixpkgs-review pr 118920 at cb564f15 run on aarch64-linux 1

2 packages built successfully:

python38Packages.pyezviz
python39Packages.pyezviz

authors: fabaff r-rmcgibbo


text:
zoom-us 5.6.13632.0328 -> 5.6.16775.0418

Motivation for this change
zoom-us currently is in a broken state.
Version 5.6.13632.0328 is blocked from participating in calls, and fails with a "please upgrade to the latest version" message. At the same time, the tar file that is supposed to be version 5.6.16775.0418 is bit-identical to the previous version.
Thus, no upgrade path to fix the issue is currently available using a tar file.
In consequence, this PR upgrades to the current version using the .deb file provided by Zoom for Debian/Ubuntu.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

backport: https://github.com/NixOS/nixpkgs/pull/120038

Update: Yesterday I submitted a ticket with Zoom. The tar file has now been fixed, and I have verified that upgrading via the tar works again.

Update: Yesterday I submitted a ticket with Zoom. The tar file has now been fixed, and I have verified that upgrading via the tar works again.

Thanks for the update. Using the tarball again in https://github.com/NixOS/nixpkgs/pull/120243 - targeting master and in https://github.com/NixOS/nixpkgs/pull/120242 a backport + fix for the stable channel.

authors: LutzCle Mic92 doronbehar


text:
[21.05] Staging next

Motivation for this change
Jobset: https://hydra.nixos.org/jobset/nixpkgs/staging-21.05
previous 21.05 staging next PR: #124341
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

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

[ ] Fits CONTRIBUTING.md.

I think I'll pause these stable branch staging-next's until hydra recovers. (<60k queued builds)

I don't think that is needed.  Typically the phase of jobset just discovering builds already in cache is quite fast.

I don't think that is needed. Typically the phase of jobset just discovering builds already in cache is quite fast. EDIT: it seemed (mostly?) done when I first posted this comment already.

staging-next-21.05 shares haven't been dialed back from stabilizing the release. Most jobsets have <1000 shares, staging-next-21.05 has 20M https://hydra.nixos.org/jobset/nixpkgs/staging-next-21.05#tabs-configuration

OK, that might be set lower now if there's nothing really urgent, I suppose, but it seems just a matter of relative priorities.

authors: jonringer vcunat


text:
nixos/doc: convert "Chapter 58. Writing NixOS Modules" to CommonMark

Note for reviewers
Thank you for reviewing this PR. :-)
This PR also fixes a small typo in Example 58.12, it should be "Definition of attribute sets of submodules" :-)
The conversion of the examples is done manually, I handle examples in the following way:
The example itself:
::: {#ex-the-id-of-the-example .example}
::: {.title}
**Example: The Name of the Example**
:::
The content of the example.
:::

Mentioning a example:
See [Example: The Name of the Example](#ex-the-id-of-the-example) for more details.

It seems that CommonMark -> DocBook (using Pandoc) won't convert .example into <example></example>, but I still used .example because DocBook will be dropped one day and CommonMark -> HTML (using Pandoc) will produce

 which I think will be fine to handle.
If you have a better idea about how to handle examples feel free to comment, thanks!

Motivation for this change

Related GitHub project
Related Discourse post

Things done
Do conversion of eight files from DocBook to CommonMark per RFC 72.

nixos/doc/manual/development/option-declarations.xml
nixos/doc/manual/development/option-types.xml
nixos/doc/manual/development/option-def.xml
nixos/doc/manual/development/meta-attributes.xml
nixos/doc/manual/development/importing-modules.xml
nixos/doc/manual/development/replace-modules.xml
nixos/doc/manual/development/freeform-modules.xml
nixos/doc/manual/development/settings-options.xml

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[ ] Fits CONTRIBUTING.md.

Will update all options links (if any) to only use the URI fragment tomorrow.


text:
zeroadPackages.zeroad-unwrapped: make it build on Hydra

This time for real, I hope.  I'm sorry for my incomplete advice;
the explicit dontRecurseIntoAttrs confused me about what's the default
behavior in here.
Things done

(nothing applies... no hashes change)

Oops, duplicate of https://github.com/NixOS/nixpkgs/pull/133379
I checked but a bit earlier...


text:
haskellPackages.readline: fix Setup.hs to work with Cabal 3

See https://github.com/NixOS/nixpkgs/pull/111985/ for previous discussion

Motivation for this change
readline is broken for Cabal3 build. I fixed it previously in this pull request, but the fix seems to have disappeared. I just reapplied it.
Is there a better way to keep this fix in place for the future? As you can seen in the previous PR, we tried to reach the maintainers of this package but we didn't succeed.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[X] Fits CONTRIBUTING.md.

Is there a better way to keep this fix in place for the future?

It might be a better idea to send this PR to the haskell-updates branch, and then back-port this PR after it is merged in there.
Each nixos release is branched-off from the master branch here in nixpkgs.  https://github.com/NixOS/nixpkgs/pull/111985 was sent to release-20.09, so it never ended up in master.  Sorry for not let telling you about this at the time.
If you send a PR to haskell-updates, then it should get merged into master.
I think there is some sort of action that lets us automatically create a backport, so hopefully it is not too much additional work for you.

As you can seen in the previous PR, we tried to reach the maintainers of this package but we didn't succeed.

One thing I was wondering, is there a repo for this readline package on github?  If so, can you create an issue or send a PR there and link to it from a comment in the code?  If you are able to send a PR, then you should also just be able to fetchpatch from that PR, which would mean that we wouldn't need to carry this patch around in nixpkgs.
If there is no upstream repo, the we'll probably have to carry around this patch in nixpkgs.

If you send a PR to haskell-updates, then it should get merged into master.
I think there is some sort of action that lets us automatically create a backport, so hopefully it is not too much additional work for you.

Ok, thanks. I'll look into sending this to haskell-updates then.

One thing I was wondering, is there a repo for this readline package on github? If so, can you create an issue or send a PR there and link to it from a comment in the code? If you are able to send a PR, then you should also just be able to fetchpatch from that PR, which would mean that we wouldn't need to carry this patch around in nixpkgs.
If there is no upstream repo, the we'll probably have to carry around this patch in nixpkgs.

I could not find any upstream repo for this package the other time, but from a bit of googling I believe Jan Stolarek may be the maintainer, I have just sent an email to them.
Otherwise I could also upload the source to my github and host the patch there, but that is also relatively ugly as it would end up being a sort of fork from hackage.
Should I close this PR then? I'll open another one to haskell-updates

I went ahead and created the new PR https://github.com/NixOS/nixpkgs/pull/134295.
Still trying to find a maintainer in parallel :)

authors: cdepillabout samuelrivas


text:
helix: 0.4.0 -> 0.4.1

Motivation for this change
Update helix to 0.4.1
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 135311 run on x86_64-linux 1

1 package built:

helix

authors: figsoda yusdacra