text:
Replaces localhost with 127.0.0.1 in devServer vue.config.js

This change seem to solve the following proxying issue:
Proxy error: Could not proxy request /api/v1/organizations?itemsPerPage=50&sortBy[]=name&descending[]=false from localhost:8080 to http://localhost:8000.
See https://nodejs.org/api/errors.html#errors_common_system_errors for more information (ECONNREFUSED).

@kevgliss can you test this when you get a change and tell me if it works for you?

For some reason, using localhost started causing issues for me. I see uvicorn running at http://127.0.0.1:8000 when I start the dev server.
INFO:     Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit)

lgtm

source: gharchive/pull-request

authors: kevgliss mvilanova

license_type: permissive

license_source: github-api


text:
bug(core-ticket): Add dispatch_weblink field to core ticket plugin

When using the core ticket plugin, we're getting the error TypeError: DispatchTicketPlugin.update() got an unexpected keyword argument 'dispatch_weblink' This field was added for the Jira ticket plugin but never added to the core plugin. Since the plugin returns no matter the arguments, I've simply added the field.

Happy to. I've got at least one other fix I can push too.

Apologies for the lint error. My IDE is just not set up well for python development. I'll fix that if I push anything more.

repo: Netflix/dispatch


text:
Fix regex support when there are multiple @Path regexes

My last PR had a bug in it when dealing with multiple path params that have regexes in them. This PR fixes that, and also finishes off implementing the jax-rs spec here https://jax-rs-spec.java.net/nonav/2.0/apidocs/javax/ws/rs/Path.html by stripping spaces before and after a param name.

NetflixOSS » feign » feign-pull-requests #121 SUCCESS
This pull request looks good

thanks for the quick turnaround, pushing 8.4.1 shortly!

repo: Netflix/feign

license_source: bigquery


text:
Separating templates for the Metaflow Compute Stack and Sagemaker Notebooks

Changes to metaflow-cfn-template.yml:

Removed all SageMaker notebook dependencies
Explicitely created the ECS instance role
Changed the compute environment to not hold any machines in standby for cost-reasons
Adding P-Instances to enable GPU compute
Autoformatter removed some trailing spaces :)

New file metaflow-notebook-cfn-template.yml:

Changed the permissions to also execute Metaflow tasks (not just use the client)
Lifecycle config changes: Write config file to $METAFLOW_HOME, shut down notebook after idle time, and automatically pull the Metaflow Tutorials to the Jupyter Notebook home in /home/ec2-user/SageMaker

Looks good to me.
Do you have any kind of testing for your templates at netflix @savingoyal ?

@tobias-gp Would it be helpful to make SageMaker setup optional in the first template? That way, consumers will only have to worry about a single template. Other changes look good to me.
@jsaedtler We have been relying on @queueburt's mad cfn skills for testing our templates so far :)

Hi Savin,
Thanks for your feedback! Just to be clear: do you mean (1) a full merge of the two templates and making the setup optional or (2) retaining the two templates with Metaflow stack (+ notebook stack), and notebook  stack. This would of course induce some redundancy.
The reason why we separated the two was because of the 1:N relationship of stacks to notebooks. I am fine with any solution, but on that case (1) seems more logical.

Ping :)

Oops. Sorry, I thought I replied earlier, but clearly not.

Yes, ideally it would be better to just have a single cloud formation template (with optional Sagemaker setup). We can have separate notebooks only template in a different folder in addition.
We can leave the Default for MinVCPUBatch to 8 and pin the MinValue to 0. The reason, why we chose not to set the default to 0 was because then it invariably leads to higher job start-up times leading to degraded user experience. By default, we can leave it to a non-zero value and our cost-conscious users can override it to 0 (which is currently not the case at the tip of the master.)

Also, we are making a few more changes to the permissions in #13 to support SFN.

@savingoyal : Thanks for your feedback.

I have just removed the NB template, which we could do in a separate PR
I have also integrated the API key handling into the lifecycle config
MinVCPUBatch is now set to 8 with MinValue set to 0.
I have also added a section in Readme.md to discuss potential cost savings

@queueburt Can you assist on this PR?

Ping? :)

Ping? :)

Hey Tobias, I have a PR I just finished that includes necessary bits for Step Functions here (#13), but I also incorporated some of your feedback along the way regarding non-singular ECS Task roles and optionality of Sagemaker Notebooks.  I'll glance over this PR early next week and try to work out what gaps we need to reconcile between the two, but could I trouble you to do the same for mine?  I'd love to combine these both together into one clean result.

@queueburt : Sorry for the slow reply. I agree that bringing in the structural changes first makes sense!

authors: jsaedtler queueburt savingoyal tobias-gp

repo: Netflix/metaflow-tools


text:
Fixing an issue where we were incorrectly returning the class type fo…

…r PHDRMetaDataTrackSubDescriptorBO as PHDRMetaDataTrackSubDescriptor.

lgtm

authors: rpuri-netflix schakrovorthy

repo: Netflix/photon


text:
Worker not working: AttributeError: async

Please make sure that you have checked the boxes:

[X ] Pease review the Troubleshooting doc for additional details regarding your issue.
[X ] Review the Quickstart guide
[X ] Search for both open and closed issues regarding the problem you are experiencing
[ ] For permissions issues (Access Denied and credential related errors), please refer to the requisite docs before submitting an issue:
AWS, GCP, OpenStack, GitHub

Description of issue:
Hey guys!
I followed everything in the QuickStart and Autostarting documentation, but my Worker process on Supervisor always gets a FATAL Exited too quickly message.
Here is the log section on securitymonkeyworkers-stderr:
/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/Flask_SQLAlchemy-1.0-py2.7.egg/flask_sqlalchemy/__init__.py:30: ExtDeprecationWarning: Importing flask.ext.sqlalchemy is deprecated, use flask_sqlalchemy instead.   from flask.ext.sqlalchemy._compat import iteritems, itervalues, xrange, \ /usr/local/src/security_monkey/venv/lib/python2.7/site-packages/Flask_SQLAlchemy-1.0-py2.7.egg/flask_sqlalchemy/__init__.py:30: ExtDeprecationWarning: Importing flask.ext.sqlalchemy._compat is deprecated, use flask_sqlalchemy._compat instead.   from flask.ext.sqlalchemy._compat import iteritems, itervalues, xrange, \ /usr/local/src/security_monkey/venv/lib/python2.7/site-packages/psycopg2-2.7.4-py2.7-linux-x86_64.egg/psycopg2/__init__.py:144: UserWarning: The psycopg2 wheel package will be renamed from release 2.8; in order to keep installing from binary please use "pip install psycopg2-binary" instead. For details see: <http://initd.org/psycopg/docs/install.html#binary-install-from-pypi>.   """) Traceback (most recent call last):   File "/usr/local/src/security_monkey/venv/bin/celery", line 11, in <module>     load_entry_point('celery', 'console_scripts', 'celery')()   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/celery-4.2.0rc2-py2.7.egg/celery/__main__.py", line 16, in main     _main()   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/celery-4.2.0rc2-py2.7.egg/celery/bin/celery.py", line 322, in main     cmd.execute_from_commandline(argv)   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/celery-4.2.0rc2-py2.7.egg/celery/bin/celery.py", line 484, in execute_from_commandline     super(CeleryCommand, self).execute_from_commandline(argv)))   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/celery-4.2.0rc2-py2.7.egg/celery/bin/base.py", line 275, in execute_from_commandline     return self.handle_argv(self.prog_name, argv[1:])   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/celery-4.2.0rc2-py2.7.egg/celery/bin/celery.py", line 476, in handle_argv     return self.execute(command, argv)   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/celery-4.2.0rc2-py2.7.egg/celery/bin/celery.py", line 408, in execute     ).run_from_argv(self.prog_name, argv[1:], command=argv[0])   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/celery-4.2.0rc2-py2.7.egg/celery/bin/worker.py", line 223, in run_from_argv     return self(*args, **options)   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/celery-4.2.0rc2-py2.7.egg/celery/bin/base.py", line 238, in __call__     ret = self.run(*args, **kwargs)   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/celery-4.2.0rc2-py2.7.egg/celery/bin/worker.py", line 257, in run     **kwargs)   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/celery-4.2.0rc2-py2.7.egg/celery/worker/worker.py", line 101, in __init__     self.setup_instance(**self.prepare_args(**kwargs))   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/celery-4.2.0rc2-py2.7.egg/celery/worker/worker.py", line 124, in setup_instance     self.should_use_eventloop() if use_eventloop is None   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/celery-4.2.0rc2-py2.7.egg/celery/worker/worker.py", line 243, in should_use_eventloop     self._conninfo.transport.implements.async and   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/kombu-4.2.0-py2.7.egg/kombu/transport/base.py", line 125, in __getattr__     raise AttributeError(key) AttributeError: async
I have two test accounts (AWS and GCP), and running monkey find -a gets everything done.
Weird, right?
Please let me known if you have any thoughts on this...

Yes -- I have reproduced this.
We need to upgrade to the latest celery RC.  PR and release coming soon.

This PR should fix: https://github.com/Netflix/security_monkey/pull/1074

@devlinrcg : can you try with the latest develop branch?

Thank you for your reply on this, @mikegrima !
I'll give it a try and let you guys know in a few.

Yep, worked with the latest develop branch.
Getting another error, related to https://github.com/Netflix/security_monkey/issues/1038. I'll follow-up there.
Thank you once again, @mikegrima

source: gharchive/issue

authors: devlinrcg mikegrima


text:
Add starknet-rs tests to CI

https://github.com/xJonathanLEI/starknet-rs
After staging is updated, we can run starknet-rs testsuite against our goerli node.
quoting jonathan from slack

replace all occurrences of https://rpc-goerli-1.starknet.rs/rpc/v0.3 to your local node. The test data were meant for goerli-1 so you need a node for that network. Then run cargo test --all

Depends on https://github.com/xJonathanLEI/starknet-rs/issues/462

https://github.com/xJonathanLEI/starknet-rs/pull/463

https://github.com/xJonathanLEI/starknet-rs/pull/463#issuecomment-1683440725

BTW some tests are marked as ignore due to pathfinder bugs (fixed in 0.7.2 but I'm still running 0.7.1 as of now). If you want to run all tests you need to do something like cargo test --all -- --include-ignored.

repo: NethermindEth/juno


text:
Configure cbor to allow unmarshaling specified types to interfaces they implement

For example;

type A struct {
	B string
	C uint
}

func TestA(t *testing.T) {
	inst := A{"hello", 42}

//	encoder.RegisterType(reflect.TypeOf(inst))

	data, _ := encoder.Marshal(inst)
	var recovered any
	encoder.Unmarshal(data, &recovered)

	switch v := recovered.(type) {
	case A:
		t.Error("success:", v)
	default:
		panic(v)
	}
}

if RegisterType is not called, test will panic at the type switch. If type A is registered, we will be able to cast recovered to A in runtime.
This helps us to have a []Transaction in our block body and allows us to cast them to our individual transaction types in runtime.

When requesting cosmetic or nitpick changes, please approve the PR. So that we don't have to wait for a second round of reviews to merge a PR.


text:
update description of Schmitt et al. (2021)

Hi,
we have updated our pre-print on model misspecification and, among other changes, show that the model misspecification method is generalizable to other SBI architectures with learned summary statistics (aka "embedding networks"). I have altered the description to include this.
New description for Schmitt et al. (2021):

They add probabilistic structure to learned summary statistics to detect model misspecification with MMD, e.g. for APT/SNPE-C (Greenberg et al., 2019) or BayesFlow (Radev et al., 2020).

Thank you for creating and maintaining this great collection!
Marvin

Hi Marvin, thanks a lot for updating that, really appreciate it!
Lorenzo

authors: LoryPack marvinschmitt

license: MIT


text:
Nonhuman Primate Reaching Dataset spike_train

Hi, I would like to ask about the NHP Reaching Dataset. In my understanding, the element of spike_train array represent how many spikes happened at some point in time and a bin_width second after that. However line 243 of the code bellow makes the element of spike_train to only represent whether there was any spike or not.
https://github.com/NeuroBench/neurobench/blob/968c627d561949f68b5f6c7bcf0a75434d0fcf5c/neurobench/datasets/primate_reaching.py#L231-L243
For example in the first unit and first channel, there are spikes at index 3019 (at 3360.99321431 second) and index 3020 (at 3360.99546708 second), which both happened in the same bin_width. Therefore, the bins result from histogram has a value of 2 at index 269749, which is the index of 3360.991999974485 second in new_t. However, spike_train[0,0,269750] has a value of 1, not 2, because of line 243 of the code above. Would you please explain why? Thank you in advance!
In addition, I am just wondering why some timestamps in t and most of new_t are not divisible by 0.004. When I open the .mat file in MATLAB, sometimes the timestamps has an extra 0.000000000000001 second. Does this make a rounding error when the file is read by h5py? Would this rounding error makes some spikes to be included in the wrong bins? However the np.arrange() function seems to be the problem too, np.arange(2281.996, 4731.676, 0.004)[269749] still produces the value 3360.991999974485, which is indivisible by 0.004. Thanks again!

@vinniesun Can you help out on a couple of questions on the primate reaching data processing?
For your second question about timestamp being off, I think this is normal for floating point arithmetic and shouldn't cause any issues when the delta is more than seven decimal points.

Sorry for the late reply. Essentially, what we are doing here is just finding if there's any spike activity within the time bin. The time array of the dataset is not the actual sampling rate of the array attached to the monkey, but the sampling rate for cursor_pos, finger_pos and and target_pos.

@vinniesun No worries! I was wrong mentioning about bin_width since that argument is not used at all in the code above. I understand that the variable t from the dataset is kinematic timestamps, not neural timestamps, but that is the reason why I open this issue. The sampling rate of the electrode array attached to the monkey is far higher than the sampling rate for cursor_pos etc, so we would loss some spiking events if we only "finding if there's any spike activity within the time bin", where the time bin is from the kinematic sampling rate (new_t variable), not the neural sampling rate. Is this intended? Would you please explain why? Thanks!
@jasonlyik Thank you for you answer!

@morenzoe This is intended. I think the easiest way to look at this is the alignment of the spike data with the label. As our labels/velocity are recorded at every 4ms, we should be aligning our spike data within that 4ms period as well.

@vinniesun I see, thank you for your explanation!

authors: jasonlyik morenzoe vinniesun

repo: NeuroBench/neurobench


text:
Fix bug when using Credentials for initialization

When initializing the Nexmo instance using Rails Credentials, if you did not provide a path to a private_key than the application would fail on a nil error for the #exists? check, since there was no string provided. This PR fixes that issue and bumps up the version to 0.4.2.

@benhayehudi Can we add a test for this to prove that it's fixed?

authors: benhayehudi mheap

repo: Nexmo/nexmo-rails


text:
Certificate Assocation lost after ACL is edited

When editing an ACL Subnet list associated with a proxy host with an SSL Cert the cert becomes unassigned and reverts back to the localhost cert

+1 I am also experiencing this.

mee too.

+1 the same problem here. When editing an ACL, all assigned hosts with LetsEncrypt Certificates will loose their SSL configuration.
To recreate:

Createn an ACL with one or more allow xxx.xxx.xxx.xxx and one deny all entry
Create a proxy host with its own LetsEncrypt SSL certificate
Assign it to said ACL
Verify that everything works as expected
Edit and save the ACL
SSL is now broken on said proxy host

A proxy host configuration before editing the ACL:
# ------------------------------------------------------------
# <REDACTED>.mydomain.tld
# ------------------------------------------------------------

server {
  set $forward_scheme http;
  set $server         "<REDACTED_proxy_host>.mydomain.tld";
  set $port           6012;

  listen 80;
  listen [::]:80;

  listen 443 ssl http2;
  listen [::]:443 ssl http2;

  server_name <REDACTED>.mydomain.tld;

  # Let's Encrypt SSL
  include conf.d/include/letsencrypt-acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate /etc/letsencrypt/live/npm-22/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-22/privkey.pem;

  # HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years)
  add_header Strict-Transport-Security "max-age=63072000; preload" always;

  # Force SSL
  include conf.d/include/force-ssl.conf;

  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection $http_connection;
  proxy_http_version 1.1;

  access_log /data/logs/proxy-host-11_access.log proxy;
  error_log /data/logs/proxy-host-11_error.log warn;

  location / {

    # Access Rules
    allow 10.0.0.0/8;
    allow 127.0.0.1/32;
    allow 172.16.0.0/12;
    deny all;

    # Access checks must...
    satisfy all;

    # HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years)
    add_header Strict-Transport-Security "max-age=63072000; preload" always;

    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;

    # Proxy!
    include conf.d/include/proxy.conf;
  }

  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

Same config after editing the ACL:
# ------------------------------------------------------------
# <REDACTED>.mydomain.tld
# ------------------------------------------------------------

server {
  set $forward_scheme http;
  set $server         "<REDACTED_proxy_host>.mydomain.tld";
  set $port           6012;

  listen 80;
  listen [::]:80;

  server_name <REDACTED>.mydomain.tld;

  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection $http_connection;
  proxy_http_version 1.1;

  access_log /data/logs/proxy-host-11_access.log proxy;
  error_log /data/logs/proxy-host-11_error.log warn;

  location / {

    # Access Rules
    allow 10.0.0.0/8;
    allow 127.0.0.1/32;
    allow 172.16.0.0/12;
    allow 192.168.0.0/16;
    deny all;

    # Access checks must...
    satisfy all;

    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;

    # Proxy!
    include conf.d/include/proxy.conf;
  }

  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

Screenshots:

authors: aaronbolton jeanpaulrh mvnmgrx pmoon00

repo: NginxProxyManager/nginx-proxy-manager


text:
Thoughts on Freenginx

I noticed this link today and the content is quite eye opening: https://www.infoq.com/news/2024/03/freenginx-ngnix-web-server/
It talks about security concerns with F5 and I was wondering if you’d consider adopting the new fork to embrace a more safer and secure path forward which sticks with the original intentions of Nginx
As of now the source code is not available in GitHub but in Hg (Mercurial), I’m keeping an eye on it to see if there will be a container image or not to simplify things.
Code: http://freenginx.org/hg/nginx

I found this unofficial mirror: https://github.com/freenginx-mirror/nginx

Be aware that this project uses OpenResty, not nginx.

Be aware that this project uses OpenResty, not nginx.

The name threw me off 😅

authors: JBlond Pyroseza


text:
IOS16注入不了

请求好像会直接被屏蔽，抓包抓不到js请求，测试安卓可以抓到可以注入

请求好像会直接被屏蔽，抓包抓不到js请求，测试安卓可以抓到可以注入

iOS 16.6 我试了下 Edge， Chrome 是能正常使用的，Safari的话提示了 “只支持Chrome/Edge浏览器进行调试”

请求好像会直接被屏蔽，抓包抓不到js请求，测试安卓可以抓到可以注入

iOS 16.6 我试了下 Edge， Chrome 是能正常使用的，Safari的话提示了 “只支持Chrome/Edge浏览器进行调试”

试的微信和Safari

用ios16下的微信或safari里打开http://192.168.1.151:8080/remote/debug/dist/page/sdk.js，看看能不能正常访问

使用ios16下的微信或safari里打开http://192.168.1.151:8080/remote/debug/dist/page/sdk.js，看看能否正常访问 @lsdlh

可以

用https即可

authors: Nice-PLQ lsdlh nsear

repo: Nice-PLQ/devtools-remote-debugger


text:
Add strictness flag which causes LSODA to exit on warning

Add flags to the Python wrapper which tell LSODA to terminate whenever the
` 'lsoda -- warning..internal t = %g and h_ = %g are such that in the machine, t + h_ = t on the next step"
warning is issued.
Currently, the user is only told about this warning through stderr. Allowing the user to set numbalsoda to be more strict will allow for better unit testing in code using numbalsoda.
To do this, a flag is added to the numba function lsoda(), which defaults to the original behaviour. The same flag is added to LSODA::lsoda, LSODA::update and lsoda_wrapper. When this flag is set to true and the above warning is issued, the solver will terminate with istate* = -2.

It looks like you didn't pass exit_on_warning to lsoda_update: https://github.com/joeyshuttleworth/numbalsoda/blob/bfe92d1df2b9dc55ddb898e0d071da1d8b55e9eb/src/wrapper.cpp#L39

Can you fix this?

Whoops, I've fixed that. I also added a test which shows the desired behaviour.

Thanks!

authors: Nicholaswogan joeyshuttleworth

repo: Nicholaswogan/numbalsoda


text:
JavaScript

JavaScript
User Story
As a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I can see the four topics I learned listed along with a suggestion on what I should study first

Done

repo: Nick-Menzhuber/prework-study-guide


text:
https://screentogif.codeplex.com/ has TLS certificate issues

Searching 'gif screen capture' in both Google and Duck Duck Go returns https://screentogif.codeplex.com/ as the first result.
However, that link is broken, since the TLS certificate has issues (expired?)
Here is a screenshot of what users see in Firefox.
Just thought you'd want to know so people stop getting a bad first impression.

My idea for letting that page alive was to redirect everyone here and to ScreenToGif.com.
I'll delete the project tonight. Not sure how long does it take to stop appearing in a web search.

authors: NickeManarin movermeyer

repo: NickeManarin/ScreenToGif

license: MS-PL


text:
Crash on startup

   在 System.Net.ServicePointManager.ValidateSecurityProtocol(SecurityProtocolType value)
   在 ScreenToGif.App.Application_Startup(Object sender, StartupEventArgs e)
   在 System.Windows.Application.OnStartup(StartupEventArgs e)
   在 System.Windows.Application.<.ctor>b__1_0(Object unused)
   在 System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   在 System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

System.ValidateSecurityProtocol

Version 2.20 onwards requires .NET Framework 4.8.
The bug here is that I added a code before the part of the app that verifies the .NET Framework version and it's crashing.
It is fixed. Thanks.

authors: NickeManarin byzod


text:
🛑 Hacker News is down

In a5812f4, Hacker News (https://news.ycombinator.com) was down:

HTTP code: 502
Response time: 198 ms

Resolved: Hacker News is back up in 019c465.

repo: NicolasAbihaggle/serviciosestados


text:
Slider in initially hidden tabs

Hi. When using vue-slider-component in initially hidden bootstrap tab when switching tabs, sliders are being drawn incorrect. I could manually refresh sliders on click event but I have a lot of them.
What could be done in such situation the best?

Have you fixed it? Can you please tell me how you did it?

                    Text

                    Text

        <template v-if="tabs['first']">
            ......her goes you tab content with sliders
        </template>

        <template v-if="tabs['second']">
            ......her goes you tab content with sliders
        </template>

export default{
        data() {
            return {
                tabs: {
                    first: false,
                    second: false
                }
            }
        },
        mounted(){
              let vm = this;
              $(document).on('shown.bs.tab', '#tab-id a[data-toggle="tab"]', function(){
                  vm.tabs[$(this).attr('href').slice(1)] = true;
              })
        }
 }

This is only example. You can implement it however you want. The idea is to render content of tab when the tab is shown

repo: NightCatSama/vue-slider-component

license: mit


text:
how to generate bootable .iso with the installer?

Hi,
thanks for the project.
I'm new to Nix so could you describe the process?
I would like to use the .iso on SD card of my Chromebox to install Nix to NVMe, unattended.
Thanks.

Nix(OS)'s concept in general is that you declare  what you want, and Nix makes it so.
NixOS installations, unfortunately, were a manual process. A (Nix)OS installation is one or more formatted disk with some files on it.
The concept of this installer is that you give it a  declaration of a system, with some extra information about partitions and such, and it will make it so, locally on the disks you provide, out to disk image files.
So, if you can, connect the NVMe to some other Linux computer, then you can directly use this installer.
For the how, see: https://github.com/NiklasGollenstede/nixos-installer/blob/master/hosts/example.nix.md#installation
Feb 2, 2024 02:27:49 Andrey Butirsky @.***>:

Hi,
thanks for the project.
I'm new to Nix so could you describe the process?
I would like to use the .iso on SD card of my Chromebox to install Nix to NVMe, unattended.
Thanks.
—
Reply to this email directly, view it on GitHub[https://github.com/NiklasGollenstede/nixos-installer/issues/1], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ACQQFXY5DPZA4U7VDYMVCN3YRQQHHAVCNFSM6AAAAABCVYIW7CVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEYTGNZQGY3TQMQ].
You are receiving this because you are subscribed to this thread.
[Tracking image][https://github.com/notifications/beacon/ACQQFXYVGBYKURKXDX6RFALYRQQHHA5CNFSM6AAAAABCVYIW7CWGG33NNVSW45C7OR4XAZNFJFZXG5LFVJRW63LNMVXHIX3JMTHH37E3DY.gif]

So, if you can, connect the NVMe to some other Linux computer, then you can directly use this installer.

This is the point - I actually can't.
Of course I could flash some mini-distro to SD card and install from that, but this is not a way I'm searching for.
I really need unattended installation from the .iso.
Maybe we could think how to implement it for your installer?
That would be awesome.

Ok, I see.
In all unattendedness, you will at least need to make your computer boot from an external install medium.
That said and done, it should be quite possible to add a mode to the installer that prepares a disk (image) such that it, when booted, automatically does the actual installation, similar to how the existing VM mode of the installer works.
I would essentially create a system variant/specialization that replaces the disk/filesystem  config to include only a single disk with boot + nix store, and a stage 2 init that starts the install command or a shell (like the VM re-exec).
Then you run the installer to install that variant, which in turn does the actual installation when booted.
(But I won't be able to even start on that before next week.)
Feb 5, 2024 03:38:06 Andrey Butirsky @.***>:

So, if you can, connect the NVMe to some other Linux computer, then you can directly use this installer.
This is the point - I actually can't.
Of course I could flash some mini-distro to SD card and install from that, but this is not a way I'm searching for.
I really need /unattended/ installation from the .iso.
Maybe we could think how to implement it for your installer?
That would be awesome.
—
Reply to this email directly, view it on GitHub[https://github.com/NiklasGollenstede/nixos-installer/issues/1#issuecomment-1926018896], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ACQQFX2OW5RVVFA7BCE4YCTYSASWZAVCNFSM6AAAAABCVYIW7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRWGAYTQOBZGY].
You are receiving this because you commented.
[Tracking image][https://github.com/notifications/beacon/ACQQFX5LH6227TJDUSW7JSDYSASWZA5CNFSM6AAAAABCVYIW7CWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTSZS3VA.gif]

Thank you, that would be awesome.

In all unattendedness, you will at least need to make your computer boot from an external install medium.

The UEFI firmware boots from SD card automatically if no other options exist (and there will be no other options as the installation happens to the fresh NVMe).

I'll try to have a look at this next week.

The UEFI firmware boots from SD card automatically if no other options exist

Well ... if exactly that is the boot logic, then as soon as a boot partition is created and populated on the NVMe, it will try to boot that.
And then you'd be sick if that system then doesn't actually boot.
On hardware that you don't know in detail (I'm assuming from the blank disk that you haven't used the hardware yet), that's possible.
Feb 7, 2024 02:39:23 Andrey Butirsky @.***>:

Thank you, that would be awesome.
In all unattendedness, you will at least need to make your computer boot from an external install medium.
The UEFI firmware boots from SD card automatically if no other options exist (and there will be no other options as the installation happens to the fresh NVMe).
—
Reply to this email directly, view it on GitHub[https://github.com/NiklasGollenstede/nixos-installer/issues/1#issuecomment-1930951506], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ACQQFX2YK6CT65Z7O2QW6FLYSK5KTAVCNFSM6AAAAABCVYIW7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZQHE2TCNJQGY].
You are receiving this because you commented.
[Tracking image][https://github.com/notifications/beacon/ACQQFX2QBT5SDTX32UQPX53YSK5KTA5CNFSM6AAAAABCVYIW7CWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTTC75VE.gif]

The hardware is known, in my case it's ASUS Chromebox 3:
https://www.asus.com/commercial-mini-pcs/asus-chromebox-3/specifications/
I'm targeting to boot it wirelessly, without LAN connected, though.

And then you'd be sick if that system then doesn't actually boot.

Fixing the error by regenerating the .iso is not a problem, providing meaningful error description is outputted to the screen/log on some writable partition of the SD card.

(But I won't be able to even start on that before next week.)

Any hope for the start?

@NiklasGollenstede any update?

repo: NiklasGollenstede/nixos-installer


text:
Textfeld änderbar

Das Textfeld bei login.html soll sich an den Text anpassen und mehrere Zeilen hat

Nicht mehr benötigt


text:
Graph node misaligned with commit list item.

Describe the bug
The height between two graph nodes is slightly smaller than the list item's height, as a result the graph will misaligned with the list after some pages.
To Reproduce
Steps to reproduce the behavior:

Go to Commits tag in this repository.
Load some more pages.
See the misaligned.

Expected behavior
The graph will always align to the tree.
Screenshots

Version information:

OS: Windows 11 Pro build 22631.3527
Browser: Edge 124.0.2478.105
Version: 1.2.8
Repository where this issue was observed: https://github.com/NirmalScaria/le-git-graph/

Additional context
I found that the height of graph's line is 57.5px, where the height of an item of list is 58.39px. And after I disabled the border of list item (which size is max(1px, 0,0625rem)), the list item's height becomes 57.49px that basiclly solves this problem.

My browser uses 'Medium' font size which rem seems to be 16px, and uses 'Arial' as default font (if this matters).

The issue seems to be fixed now, if now please help me reproduce it. i am getting

There is no any misalignment now.

authors: AishwaryaAgr Eyre-S

repo: NirmalScaria/le-git-graph


text:
get_assertion: Skip attStmt unless requested

For makeCredential, a missing attestation format preference list means that we should use the default format (packed).  For getAssertion, it means that we should skip the attestation statement entirely. Previously, we implemented the makeCredential algorithm for both cases. This caused an incompatibility with firefox because it fails on unexpected fields in the response (in this case, the attestation statement).  This patch fixes this issue and applies the correct default for getAssertion requests.
Fixes: https://github.com/Nitrokey/fido-authenticator/issues/98

verified using nk3am + firefox 131 + webauthn.io

authors: daringer robin-nitrokey

repo: Nitrokey/fido-authenticator


text:
apply-overlays-dtmerge for Pi4 seems to fail on 22.05

{
  hardware = {
    raspberry-pi."4".apply-overlays-dtmerge.enable = true;

    deviceTree = {
      overlays = [
        {
          name = "vc4-kms-v3d-pi4";
          dtboFile = "${config.boot.kernelPackages.kernel}/dtbs/overlays/vc4-kms-v3d-pi4.dtbo";
        }
      ];
    };
  };
}

where kernelPackages = pkgs.linuxKernel.packages.linux_rpi4;
fails with
./broadcom -> /nix/store/pc46arc6g6bkx9ny2lsi9hparhizis0q-device-tree-overlays/./broadcom
'./broadcom/bcm2711-rpi-400.dtb' -> '/nix/store/pc46arc6g6bkx9ny2lsi9hparhizis0q-device-tree-overlays/./broadcom/bcm2711-rpi-400.dtb'
'./broadcom/bcm2711-rpi-4-b.dtb' -> '/nix/store/pc46arc6g6bkx9ny2lsi9hparhizis0q-device-tree-overlays/./broadcom/bcm2711-rpi-4-b.dtb'
'./broadcom/bcm2711-rpi-cm4.dtb' -> '/nix/store/pc46arc6g6bkx9ny2lsi9hparhizis0q-device-tree-overlays/./broadcom/bcm2711-rpi-cm4.dtb'
Applying overlay vc4-kms-v3d-pi4 to bcm2711-rpi-400.dtb
cp: cannot create regular file '/nix/store/vrs5pi8qi943svd9l4vmz2bmz984klcj-linux-5.15.32-1.20220331/dtbs/overlays/vc4-kms-v3d-pi4.dtbo.dtbo': Permission denied

Is this a regression or am I doing something wrong?
Thanks.

Hey @WizardUli, I've reproduced the issue and verified that the fix works in #518, hoping to get it merged soon.

close for now, we can re-open if it does not work.

authors: Mic92 WizardUli carlossless

repo: NixOS/nixos-hardware


text:
Add missing Intel CPU modules as flake outputs

Description of changes
Some Intel CPU modules were not added as flake outputs.
Things done

[x] Tested the changes in your own NixOS Configuration
[x] Tested the changes end-to-end by using your fork of nixos-hardware and
importing it via <nixos-hardware> or Flake input

I would like to put this on hold, because of this: https://github.com/NixOS/nixos-hardware/issues/992

I think I stick to this decision.


text:
Unityhub: no more splashscreen (regression) and no .desktop file

Describe the bug
Since my last upgrade (from unstable 5ff6700bb82 to unstable 83d907fd760) unityhub does not display a splashscreen anymore when starting a project, the image is not found:

Before, a nice picture was displayed. Also, unityhub does not have any .desktop file, meaning that I need to start it from command line directly. Note that unityhub still works even without this.
To Reproduce
Steps to reproduce the behavior:

Install unityhub, and run it (via command line since there is no .desktop)
Start a project
While loading the project no splash screen is displayed

Notify maintainers
@tesq0

@tobiasBora
this one adds a .desktop file #132745
and i think this also fixes the splash #132737

repo: NixOS/nixpkgs


text:
pythonPackages.MySQL_python seems broken in 16.03

Issue description
MySQL python binding is broken in 16.03 channel. Is seems to be OK in master. Apparently, 5982591afc07480808d9c71a5b97463fc4cc9943 is the commit in master that fixed that issue.
If it is OK, I’d like to cherrry pick that commit into the 16.03 branch (this will imply a massive re-downloads from the cache for the users).
Steps to reproduce
$ nix-shell -p pythonPackages.MySQL_python --command "python -c 'import MySQLdb'"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/nix/store/l7bgcgm270zmq1138cm4qspb648qdgz2-python2.7-MySQL-python-1.2.5/lib/python2.7/site-packages/MySQLdb/__init__.py", line 19, in <module>
    import _mysql
ImportError: /nix/store/l7bgcgm270zmq1138cm4qspb648qdgz2-python2.7-MySQL-python-1.2.5/lib/python2.7/site-packages/_mysql.so: symbol mysql_use_result, version libmysqlclient_16 not defined in file libmysqlclient.so.18 with link time reference

Technical details

System: 16.03.468.2d840da (Emu)
Nix version: nix-env (Nix) 1.11.2
Nixpkgs version: 16.03.526.567b65d

cc @domenkozar

@edolstra any objections for a full rebuild of 16.03? Maybe there's a workaround for this bug.

The error in #14351 seems related to this.

Cherry-picked to 16.03

authors: basvandijk domenkozar lancelotsix


text:
Unable to install virtualenvwrapper for Python 3.5

Issue description
Trying to install python35Packages.virtualenvwrapper gives the following build error:
error: sphinx-1.2.3 not supported for interpreter python3.5m

I don't understand why virtualenvwrapper is concerned about sphinx package??
Steps to reproduce
Add the following to environment.systemPackages = with pkgs; list:
   python35Packages.virtualenvwrapper

Technical details

System: (NixOS: nixos-version, Ubuntu/Fedora: lsb_release -a, ...)

# nixos-version
16.03.898.3111985 (Emu)

Nix version: (run nix-env --version)

# nix-env --version
nix-env (Nix) 1.11.2

Nixpkgs version: (run nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion)

# nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion
"16.03.898.3111985"

I don't understand why virtualenvwrapper is concerned about sphinx package??

Nix builds up a graph of dependencies. Sphinx 1.2.3 is somewhere an (indirect) dependency of virtualenvwrapper. Likely one or more packages need to be updated to get this working for you.

Ok, thanks. Do you have any pointers what I could do about it? I just installed Nix(OS) so I'm new to this.

Typically dependencies are added for a reason. It is a bit strange though, that we have things depending on specifically Sphinx 1.2.x, and not 1.3.x which is the default Sphinx. I suggest you have a look at python-packages.nix, and start updating packages, beginning with virtualenvwrapper, so that eventually you can get rid of Sphinx 1.2.x and use 1.3.x instead.
At this point I do have to ask you. Why are you interested in virtualenvwrapper? Is it because you simply have to work with virtualenv? Since now you're on Nix you have a far more powerful tool for creating such environments: nix-shell

Pypi suggests virtualenvwrapper itself is not tested on python 3.5.
Maybe you can use pythonPackages34.virtualenvwrapper?

Thanks for pointing out nix-shell. I read about it but I couldn't quite figure out how I can use it to replace virtualenv. For instance, is it possible to install packages via pip into that development environment without virtualenv.
I found this, but seems quite experimental and not very well working yet:
https://github.com/garbas/nix-virtualenv
Also, I found these interesting posts:
http://datakurre.pandala.org/2015/10/nix-for-python-developers.html
http://datakurre.pandala.org/2014/09/nix-expressions-as-executable-commands.html
So, perhaps I'll study a bit and see what would be a good approach. Anyway, I like the virtualenv integrations, for instance, in Emacs (e.g., possibility to activate different virtualenvs within Emacs and run unit tests etc) and workon myproject in virtualenvwrapper
Thanks!

@jluttine with Nix we don't have a global/user site-packages. Therefore, if you use nix-shell, and try a pip install a package it will complain because it cannot install anything in the store. Of course, you could install those packages elsewhere.
Now, you can create a virtualenv, and then use pip. However, packages that were included in your nix-shell will leak into your virtualenv. This can be considered both a bug and a feature :)
Some more details about this can be found in the https://github.com/NixOS/nixpkgs/issues/15224
Anyway, I will close this issue because it is simply not possible at this point to install virtualenvwrapper on Python 3.5 because of the currently defined dependencies. And as  @groxxda pointed out, 'officially' it is not supported either.

authors: FRidh groxxda jluttine


text:
newlib fails to cross-compile for arm-embedded

Steps To Reproduce
Steps to reproduce the behavior:

nix build nixpkgs#pkgsCross.arm-embedded.buildPackages.newlib

Build log
I believe the relevant errors are
[...]
/nix/store/1b9p07z77phvv2hf6gm9f28syp39f1ag-bash-5.1-p16/bin/bash: line 1: arm-none-eabi-cc: command not found
[...]
/nix/store/1b9p07z77phvv2hf6gm9f28syp39f1ag-bash-5.1-p16/bin/bash: line 3: arm-none-eabi-ar: command not found
[...]

full output here: https://gist.github.com/rndmono/b18bee838ef7e497dd17b1672ef72f87
Notify maintainers
@Ericson2314 @matthewbauer
Metadata

system: "x86_64-linux"
host os: Linux 5.15.63, NixOS, 22.05 (Quokka), 22.05.2764.0ba2543f8c8
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.8.1
channels(root): "nixos-22.05, nixos-hardware, nixos-unstable"
channels(user): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

I had the same issue and was told (on NixOS Matrix) to either omit .buildPackages or use .__splicedPackages.
$ nix build nixpkgs#pkgsCross.arm-embedded.__splicedPackages.newlib
$ nix build nixpkgs#pkgsCross.arm-embedded.newlib

Both of the above commands finish successfully on 22.11.

I had the same issue and was told (on NixOS Matrix) to either omit .buildPackages or use .__splicedPackages.
$ nix build nixpkgs#pkgsCross.arm-embedded.__splicedPackages.newlib
$ nix build nixpkgs#pkgsCross.arm-embedded.newlib

Both of the above commands finish successfully on 22.11.

Thank you! I can confirm that this still works on 23.05.

... and was told (on NixOS Matrix) to either omit .buildPackages or use .__splicedPackages.

Do you know why adding sub attrs buildPackages will cause this failure?

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/newlib-failed-to-build-in-pkgscross-armv7l-hf-multiplatform/36845/1

authors: Avimitin nixos-discourse quapka rndmono


text:
Freecad: cannot be called without required argument "gitpython"

Steps To Reproduce
Steps to reproduce the behavior:
sudo nixos-rebuild switch --upgrade
Build log
error: Function called without required argument "gitpython" at /nix/store/v8cyxca406hl8yf95d6qqc6zdcm2jdaq-nixos/nixos/pkgs/applications/graphics/freecad/default.nix:7, did you mean "GitPython"?

Additional context
It seems to be commit 26d68b5350e4c5f6e283f153d43d19083a1df450 the problem.
Notify maintainers

@viric @gebner @AndersonTorres
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.0.11, NixOS, 23.05 (Stoat), 23.05pre432338.6e51c97f1c8`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.1`
 - channels(root): `"nixos"`
 - channels(goetz): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

This should already be fixed by #205058, which hit nixos-unstable ~6 hours ago (so not long after you opened the issue)
Can you try pulling/updating nixos-unstable again?

authors: MrTarantoga lilyinstarlight


text:
Package request: pytest-pudb

Project description

Pytest PuDB debugger integration based on pytest PDB integration
Metadata

homepage URL: https://pypi.org/project/pytest-pudb/
source URL: https://github.com/wronglink/pytest-pudb
license: mit
platforms: unix, linux, darwin, ...

@Freed-Wu pudb is in nixpkgs now, can you close this please?

authors: Freed-Wu mmlb


text:
Package request: kinto

Project description
Mac-style shortcut keys for Linux
Setup video
Metadata

homepage URL: https://github.com/rbreaves/kinto
source URL: https://github.com/rbreaves/kinto
license: gpl2
platforms: unix, linux, darwin

dupe of #137698

authors: carleeto eclairevoyant


text:
How to represent license choice (disjunctively licensed software)

Issue description
There exists software (like libgmp [1]) that gives you the choice between multiple licenses. According to the SPDX specification [2] this is expressed through an OR connection. I understand that an AND connection of licenses is already available in Nix through lists. But would it be possible to implement disjunction (choice)?
If someone points me into the right direction I might give it a try.
[1] https://gmplib.org/
[2] https://spdx.org/spdx-specification-21-web-version#h.jxpfx0ykyb60

the only license which is interpreted by scripts is unfree. All the rest are just a free text, which does not obey any schema.

The answer to the question has been posted. Closing.

tldr; assign a list to meta.licenses, because that implies an or relationship.
The mentioned library is already packaged in nixpkgs- search for "gmp" and "gmp-with-cxx" to observe single licensed and dual licensed software packaged.

@prusnak where has the answer been posted?

Can we reopen this issue? This is a very common thing and it is documented nowhere. I think it should be clarified and documented.

I do not know who can say something authoritative about this, otherwise I would just document this.

authors: Bert-Proesmans KaiHa MangoIV prusnak volth


text:
Build failure: PHP 8.3 with php-acpu

Steps To Reproduce
I have this in my flake:
  environment.systemPackages = [
    pkgs.nodejs
    pkgs.nodePackages.node-pre-gyp
    (pkgs.php83.buildEnv {
      extensions = ({enabled, all}: enabled ++ (with all; [
        apcu
        bcmath
        gmp
        imagick
        opcache
        pdo
        pdo_pgsql
        redis
      ]));
      extraConfig = ''
        apc.enable_cli = 1
      '';
    })
  ];

Build log
https://gist.github.com/voidzero/596e5d1c9ef60aa552a30fbc540ce367#file-php_test_results_20231230_2225-txt-L288
Additional context
NixOS 23.11.
Notify maintainers

@aanderse @drupol @etu @Ma27 @talyz
Metadata
The metadata from nix-info -m is not relevant as I am currently on 23.05 but performing an upgrade to 23.11. The system is x86_64-linux. multi-user and sandbox are yes.
Workaround: This issue does not occur on php82 so I'll be using that for now.

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

Hi,
I'm not able to reproduce the issue, therefore could you run this command on your machine?
nix build --impure --expr '(import ./. {}).php83.withExtensions({ enabled, all }: (enabled ++ (with all; [apcu bcmath gmp imagick opcache pdo pdo_pgsql redis])))' --show-trace

Thanks!

Hi @drupol thanks, I am getting the same output as before.
error: builder for '/nix/store/9mvc08wnf8lvig8a8wc8mrhzy66s9a94-php-apcu-5.1.22.drv' failed with exit code 2;
       last 10 log lines:
       > ---------------------------------------------------------------------
       > Success parameters should respect property types [tests/typed_prop.phpt]
       > =====================================================================
       >
       > You may have found a problem in PHP.
       > This report can be saved and used to open an issue on the bug tracker at
       > https://github.com/php/php-src/issues
       > This gives us a better understanding of PHP's behavior.
       > Do you want to save this report in a file? [Yn]: Report saved to: /build/source/php_test_results_20240102_1144.txt
       > make: *** [Makefile:138: test] Error 1
       For full logs, run 'nix log /nix/store/9mvc08wnf8lvig8a8wc8mrhzy66s9a94-php-apcu-5.1.22.drv'.
error: 1 dependencies of derivation '/nix/store/4rh0daclxc6rqm7g2yhf64s4gcp1ic3y-php-extra-init-8.3.1.ini.drv' failed to build
error: 1 dependencies of derivation '/nix/store/2fx3xq2yfci5c5jwkffs0f9sxjylpcsq-php-with-extensions-8.3.1.drv' failed to build

I don't have the same path for php-with-extensions-8.3.1.drv, I guess your nixpkgs is out of date.

Ah, I am indeed on 23.11 so that might explain things, even though I've updated today.
I'll update again in one week and keep you posted whether it will work now.
Thanks for helping 😃

You're welcome, feel free to close the issue when it's resolved !

I've just synched nixpkgs 23.11, but it doesn't look like your backport has landed, so nothing has changed yet. Just letting you know, I'll try again later this week or perhaps next week.

Indeed, there hasn't been a new channel update since we merged this PR (https://hydra.nixos.org/eval/1803447?filter=apcu&compare=1803374&full=#tabs-still-succeed). I guess that build is going to be successful and you'll be able to enjoy the fix very soon.

Thanks for the link - haven't seen that before. Can I view on hydra when there is a channel update?

Yes, just look at this page: https://status.nixos.org/ (last update was 10h ago)
You can also "watch" a PR with this useful tool: https://nixpk.gs/pr-tracker.html?pr=278271

Hello,
Can I close the issue now?

Yes, it works. Just tested. Much thanks @drupol, also for the other links and extra info. 😇

authors: drupol voidzero


text:
Module request: libmultiprocess

Description

libmultiprocess is a C++ library and code generator making it easy to call functions and reference objects in different processes.
Bitcoin Core is starting to use this lib as dependency for IPC. It would be nice to have libmultiprocess available for derivation builds via pkg-config + cmake.
Notify maintainers

@prusnak @roconnor

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

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

cc @ryanofsky

Can you try to come up with a PR? Should not be that hard.
Tag me in the PR so I can review it.

authors: plebhash prusnak


text:
nix repl :r does not actually seem to reload anything

Issue description
nix repl's :r command doesn't seem to actually reload anything. I noticed this issue a few weeks ago, but was busy, and just came across it again.
Steps to reproduce
git clone git@github.com:NixOS/nixpkgs
cd nixpkgs
nix repl default.nix

nix-repl> openconnect
«derivation /nix/store/5lyrm0chwnq9dpb2bl7lchmnnkx6qi4f-openconnect-7.08.drv»

# NOW, change pkgs/tools/networking/openconnect/default.nix
# What I did was remove "dev" from outputs, then save the file

nix-repl> :r
Loading 'default.nix'...
Added 9690 variables.

nix-repl> openconnect
«derivation /nix/store/5lyrm0chwnq9dpb2bl7lchmnnkx6qi4f-openconnect-7.08.drv»
# same as before

# NOW, I reverted the "dev" change, and instead changed a character in the hash, then saved the file
# Same problem
nix-repl> openconnect
«derivation /nix/store/5lyrm0chwnq9dpb2bl7lchmnnkx6qi4f-openconnect-7.08.drv»
# same as before

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.74, NixOS, 19.03pre154487.0a7e258012b (Koi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.1.3`
 - channels(root): `"nixos-19.03pre158246.6141939d6e0"`
 - channels(chessai): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

apparently @cleverca22 has also noticed this behaviour.

This is as issue with the package manager itself not nixpkgs, it's best to report it there instead https://github.com/NixOS/nix.


text:
nix-prefetch-git produce wrong hash on git LFS

Describe the bug
Github uses Git LFS to store binary files in repos. This leads to mismatched hashes between nix-prefetch-git and nix-prefetch-url --unpack.
To Reproduce
Example for https://github.com/KhronosGroup/OpenVX-cts.
nix-prefetch-git:
$ nix-prefetch-git --quiet https://github.com/KhronosGroup/OpenVX-cts --branch-name openvx_1.3 | jq -r .sha256
1cgp1nrwbh3mcpcaa7i8yfqvl9pa3iq0vhzpym4ypwarl268228k

nix-prefetch-url (this is equal to fetchFromGitHub):
$ nix-prefetch-url --unpack https://github.com/KhronosGroup/OpenVX-cts/archive/openvx_1.3.tar.gz
[38.1 MiB DL]
path is '/nix/store/a030nyv0db095z1yvbpfgzak705wij0f-openvx_1.3.tar.gz'
1z882v2j91p1217sm0qvs0wzhrrkgpd2j8ybsz042f2laiivy4jv

Expected behavior
The hashes should be equal for both methods.
Additional context
I've noticed difference in files OpenVX-cts/test_conformance/Networks/Binaries. There are a lot of binary files but their contents after git clone (without git lfs checkout step) is like
$ cat OpenVX-cts/test_conformance/Networks/Binaries/Alexnet/conv1_bias.bin
version https://git-lfs.github.com/spec/v1
oid sha256:651901ab77fd02ea8f247a65d720973ca4ef1ebe32bc137476aea2653c203721
size 192

fetchFromGitHub produced correct binary files:
$ sha256sum /nix/store/n13p4cmzb76vfc9wwhadyby1kxq9a8cc-source/test_conformance/Networks/Binaries/Alexnet/conv1_bias.bin
651901ab77fd02ea8f247a65d720973ca4ef1ebe32bc137476aea2653c203721  /nix/store/n13p4cmzb76vfc9wwhadyby1kxq9a8cc-source/test_conformance/Networks/Binaries/Alexnet/conv1_bias.bin

Does this problem affect fetchgit module?
Notify maintainers
cc @jtojnar @bhipple as last active maintainers.
Metadata
nix-shell -p nix-info --run "nix-info -m":

system: "x86_64-linux"
host os: Linux 5.4.44, NixOS, 20.09pre228622.029a5de0839 (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.6
channels(root): "nixos-20.09pre228622.029a5de0839"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Github uses Git LFS to store binary files in repos.

that is not quite right, GitHub only does that if it got configured.
This is related to GitHub not adding the files in the archive download, see https://github.com/git-lfs/git-lfs/issues/903


text:
haskellPackages.shellFor: add a doBenchmark argument for enabling benchmark deps

Motivation for this change
Add a doBenchmark argument for enabling benchmark deps when creating a development shell with shellFor.
This is necessary for users that want to make sure shellFor creates a package database with benchmark-specific libraries (like criterion).
cc @maralorn @peti @harendra-kumar
This supercedes #102323.
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
[ ] 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)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build tests.haskell-shellFor

I've confirmed locally that the hash for tests.haskell-shellFor doesn't change with the introduction of this PR.  That's a good indication that this PR at least won't affect any current users negatively.
I've also tested it against the example in https://github.com/NixOS/nixpkgs/pull/102323#issuecomment-720859113, and it appears to correctly give benchmark deps.

I haven‘t tested it, but this looks totally reasonable.

Thanks for the review!

authors: cdepillabout maralorn


text:
erlangR23: 23.1.2 -> 23.1.4

Motivation for this change
Upstream release: https://github.com/erlang/otp/releases/tag/OTP-23.1.4
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 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 106167 run on x86_64-linux 1

1 package built:

erlangR23

Result of nixpkgs-review pr 106167 run on x86_64-darwin 1

1 package built:

erlangR23


text:
jetbrains: updates

Motivation for this change
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/)
[ ] 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.

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

1 package built:

jetbrains.rider

Tested it starts up and the first few screens of the activation dialogs work, but I don't have a license, so I didn't get past the activation dialog.


text:
radvd: 2.18 -> 2.19

Motivation for this change
Update to latest upstream release 2.19
Change log: https://github.com/radvd-project/radvd/blob/master/CHANGES
Fixes #111408
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 111553 run on x86_64-linux 1

1 package built:

radvd


text:
log4cplus: 2.0.5 -> 2.0.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/log4cplus/versions.
meta.description for log4cplus is: "A port the log4j library from Java to C++"
meta.homepage for log4cplus is: "http://log4cplus.sourceforge.net/"
meta.changelog for log4cplus 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 2.0.6 with grep in /nix/store/6n99i8kp5a551fm0pzszp58i02aw6iax-log4cplus-2.0.6

directory tree listing: https://gist.github.com/adb369f9d12a3fbe4f054ed3fcdb040c

du listing: https://gist.github.com/233091bdae9865052ad492ade9086ab2

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

8 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
kea
log4cplus

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6n99i8kp5a551fm0pzszp58i02aw6iax-log4cplus-2.0.6 \
  --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 log4cplus https://github.com/r-ryantm/nixpkgs/archive/ba02fd22e590e5ea9ff74aa74e0e24ad42b9c0fe.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/6n99i8kp5a551fm0pzszp58i02aw6iax-log4cplus-2.0.6
ls -la /nix/store/6n99i8kp5a551fm0pzszp58i02aw6iax-log4cplus-2.0.6/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 built:

kea
log4cplus

Maintainer pings

Result of nixpkgs-review pr 114207 at ba02fd22 run on aarch64-linux 1

2 packages built:

kea
log4cplus

1 suggestion:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/libraries/log4cplus/default.nix:14:3:
   |
14 |   meta = {
   |   ^

authors: r-rmcgibbo r-ryantm


text:
ocamlPackages.dune: rename as dune_1 and disable for OCaml ≥ 4.12

Motivation for this change
Fixes #114421.
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 114478 at f9441389 run on x86_64-linux 1

1 package built:

dune_1

What would be the impact of making dune_2 the default in dunePackage?

FWIW I've been running dune_2 exclusively in my overlays and, apart from packages that still have jbuild files, most failing packages can be fixed by adding dune-configurator to buildInputs.

dune_2 would have to be the default at least for 4.12, otherwise many packages wouldn't build anymore that support dune2 but don't have useDune2=true set

authors: Zimmi48 anmonteiro r-rmcgibbo tg-x vbgl


text:
stix-two: 2.11 -> 2.12

Motivation for this change
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.

@GrahamcOfBorg eval


text:
python3Packages.sphinx: 3.3.1 -> 3.5.4

Motivation for this change
Update sphinx to latest version 3.5.4.
Changelog:
https://github.com/sphinx-doc/sphinx/blob/9f44ee4dd1761e12a25b63671dcc4b8ace1f2555/CHANGES#L199-L553
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.

/rebase staging


text:
bzrtp: 4.5.1 -> 4.5.10

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bzrtp/versions.
meta.description for bzrtp is: "An opensource implementation of ZRTP keys exchange protocol"
meta.homepage for bzrtp is: "https://gitlab.linphone.org/BC/public/bzrtp"
meta.changelog for bzrtp 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 4.5.10 with grep in /nix/store/rbihdazpf6h2wzqjdphdh94wzyljclqr-bzrtp-4.5.10

found 4.5.10 in filename of file in /nix/store/rbihdazpf6h2wzqjdphdh94wzyljclqr-bzrtp-4.5.10

directory tree listing: https://gist.github.com/4fa3f31244f91c083c5bd1d88bf2d28f

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

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

19 total rebuild path(s)

6 package rebuild(s)

6 x86_64-linux rebuild(s)
6 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
6 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
bzrtp
liblinphone
linphone
mediastreamer
mediastreamer-openh264
msilbc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/rbihdazpf6h2wzqjdphdh94wzyljclqr-bzrtp-4.5.10 \
  --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 bzrtp https://github.com/r-ryantm/nixpkgs/archive/9ce0f45e8ebdc2fcbf42c7844a105554c5cbe88b.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/rbihdazpf6h2wzqjdphdh94wzyljclqr-bzrtp-4.5.10
ls -la /nix/store/rbihdazpf6h2wzqjdphdh94wzyljclqr-bzrtp-4.5.10/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

6 packages built:

bzrtp
liblinphone
linphone
mediastreamer
mediastreamer-openh264
msilbc

Maintainer pings
cc @jluttine for testing.

Result of nixpkgs-review pr 120971 at 9ce0f45e run on aarch64-linux 1

2 packages marked as broken and skipped:

liblinphone
linphone

4 packages built successfully:

bzrtp
mediastreamer
mediastreamer-openh264
msilbc


text:
sage: 9.3 -> 9.4

Motivation for this change
Tracking upstream changes so we are ready when 9.4 gets released. As of July 31st, tests for 9.4.rc0 pass.
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
[ ] 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"
[x] 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

[x] Fits CONTRIBUTING.md.

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

8 packages built:

maxima
maxima-ecl
pynac
python38Packages.memory-allocator
python39Packages.memory-allocator
sage (sagemath)
sageWithDoc
wxmaxima

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

8 packages built:

maxima
maxima-ecl
pynac
python38Packages.memory-allocator
python39Packages.memory-allocator
sage (sagemath)
sageWithDoc
wxmaxima

ofBorg seems happy, both on x86_64 and on aarch64.

Thanks for merging!

Thank you once again for keeping sage running and up-to-date :)

authors: collares timokau


text:
yabar: support cross-compilation, format

Motivation for this change
More cross-compilation support!
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/)
[x] Fits CONTRIBUTING.md.

I've also diffed the output for native using diffoscope (before and after this change), the only difference is the order of paths embedded in the executable.
Note: targeting staging due to zstd cross-compilation being broken in master (https://github.com/NixOS/nixpkgs/pull/129873 fixes this). It's impossible to check compilation on master, on staging it's at least possible.

pkgsCross.aarch64-multiplatform.yabar builds for me, yay!

authors: Mindavi siraben


text:
rednotebook: 2.21 -> 2.22

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for rednotebook is: "A modern journal that includes a calendar navigation, customizable templates, export functionality and word clouds"
meta.homepage for rednotebook is: "https://rednotebook.sourceforge.io/"
meta.changelog for rednotebook is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

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

/nix/store/k0icz7fjgcfc0bfiby2q6j0xslwiapf6-rednotebook-2.22/bin/rednotebook passed the binary check.

Warning: no invocation of /nix/store/k0icz7fjgcfc0bfiby2q6j0xslwiapf6-rednotebook-2.22/bin/.rednotebook-wrapped had a zero exit code or showed the expected version

1 of 2 passed binary check by having a zero exit code.

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

found 2.22 with grep in /nix/store/k0icz7fjgcfc0bfiby2q6j0xslwiapf6-rednotebook-2.22

found 2.22 in filename of file in /nix/store/k0icz7fjgcfc0bfiby2q6j0xslwiapf6-rednotebook-2.22

directory tree listing: https://gist.github.com/f97e32ae0f15e13e4b7b5255dbdfa1f2

du listing: https://gist.github.com/7c0c0156b2f6bdc91a5ce776cbcbde19

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

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
rednotebook

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/k0icz7fjgcfc0bfiby2q6j0xslwiapf6-rednotebook-2.22 \
  --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 rednotebook https://github.com/r-ryantm/nixpkgs/archive/3c8bfff92c29713c471ca77e384e99b4202b8380.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/k0icz7fjgcfc0bfiby2q6j0xslwiapf6-rednotebook-2.22
ls -la /nix/store/k0icz7fjgcfc0bfiby2q6j0xslwiapf6-rednotebook-2.22/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

1 package built:

rednotebook

Maintainer pings
cc @orivej for testing.

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

1 package built:

rednotebook

authors: r-ryantm siraben


text:
bats: fixes installation

Things done:

[x] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
[x] Built on platform(s): NixOS
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

The build was failing with:
/...-stdenv/setup: ./install.sh: /usr/bin/env: bad interpreter: No such file
or directory
See https://hydra.nixos.org/build/32353411/log

Looks like I forgot to test this with a chroot


text:
llvmPackages_13: Fix the build on AArch64

The compiler-rt build was failing with:
/build/source/compiler-rt/build/lib/fuzzer/libcxx_fuzzer_aarch64/include/c++/v1/__config:1065:41: error: a destructor cannot be 'constexpr'
1065 | #  define _LIBCPP_CONSTEXPR_AFTER_CXX17 constexpr
|                                         ^~~~~~~~~
make[5]: *** [cxx/src/CMakeFiles/cxx_static.dir/build.make:303: cxx/src/CMakeFiles/cxx_static.dir/optional.cpp.o] Error 1
make[2]: *** [lib/fuzzer/CMakeFiles/libcxx_fuzzer_aarch64-build.dir/build.make:80: lib/fuzzer/libcxx_fuzzer_aarch64-stamps/libcxx_fuzzer_aarch64-build] Error 2
See:

https://hydra.nixos.org/job/nixpkgs/trunk/llvmPackages_13.compiler-rt.aarch64-linux/all
https://hydra.nixos.org/log/nlcppawcbnpff23mdxxk6ianrwp8p7j7-compiler-rt-libc-13.0.0-rc2.drv

Motivation for this change
Things done

Built on platform(s)

[ ] 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"
[ ] 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

[ ] Fits CONTRIBUTING.md.

@ofborg build llvmPackages_13
Let's see if this is enough.

Unfortunately it now fails during the linking:
collect2: error: ld returned 1 exit status
make[2]: *** [tools/llvm-shlib/CMakeFiles/LLVM.dir/build.make:308: lib/libLLVM-13.so] Error 1
make[1]: *** [CMakeFiles/Makefile2:33523: tools/llvm-shlib/CMakeFiles/LLVM.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 74%] Linking CXX static library ../../../../lib/libLLVMExegesisX86.a
[ 74%] Built target LLVMExegesisX86
make: *** [Makefile:171: all] Error 2
builder for '/nix/store/x3w4hdzx59wp66j4l6ps29xagawz3dkk-llvm-13.0.0-rc2.drv' failed with exit code 2

I don't have enough time to have a look at it.

FYI this is because libcxx and compiler-rt have different minimum compiler requirements to core LLVM. As per https://libcxx.llvm.org/#platform-and-compiler-support we need at least GCC 11 to build these, but it looks like you tried with GCC 9.3 and GCC 10.

Unfortunately it now fails during the linking:
collect2: error: ld returned 1 exit status

Before that message I'm seeing many errors similar to:
[...]/bin/ld: AArch64PBQPRegAlloc.cpp:([...]): undefined reference to `__aarch64_ldadd4_acq_rel'

Cursory research seems to indicate this is caused by -moutline-atomics (docs), which is enabled by default in newer GCCs.
Because the build is targeting the base ARMv8.0 instruction set atomic operations are not guaranteed to be available (they are part of Armv8.1-A), so helpers from libgcc are injected for atomic operations (which then fail to link).
Potential fixes include setting -mno-outline-atomics, targeting a higher version of the instruction set (I'm assuming this wouldn't be acceptable for nixpkgs?) or figuring out what leads to the linker failures.

I just tried to build llvm using GCC11 with -mno-outline-atomics (commit). Linking worked, but tests failed:
llvm> LLVM :: CodeGen/ARM/vararg_no_start.ll              Exception in thread Thread-3:
llvm> Traceback (most recent call last):
llvm>   File "/nix/store/8zhpsi47a8v89l23fzplan67gmx7x0b5-python3-3.9.6/lib/python3.9/threading.py", line 973, in _bootstrap_inner
llvm>     self.run()
llvm>   File "/nix/store/8zhpsi47a8v89l23fzplan67gmx7x0b5-python3-3.9.6/lib/python3.9/threading.py", line 910, in run
llvm>     self._target(*self._args, **self._kwargs)
llvm>   File "/nix/store/8zhpsi47a8v89l23fzplan67gmx7x0b5-python3-3.9.6/lib/python3.9/multiprocessing/pool.py", line 576, in _handle_results
llvm>     task = get()
llvm>   File "/nix/store/8zhpsi47a8v89l23fzplan67gmx7x0b5-python3-3.9.6/lib/python3.9/multiprocessing/connection.py", line 256, in recv
llvm>     return _ForkingPickler.loads(buf.getbuffer())
llvm> _pickle.UnpicklingError: invalid load key, '\x00'.

I'll try GCC10 next.

Tests seem to fail at random points (CodeGen/ARM/vararg_no_start.ll, CodeGen/AMDGPU/add_i1.ll, CodeGen/ARM/vararg_no_start.ll) with the above message, so I'm assuming that's unrelated to the build (maybe it's caused by running in binfmt?).
So the build is probably fine, I just can't verify it. @primeos Can you pick this back up from here?

I've debugged this with @BBBSnowball for a few more hours. -mno-outline-atomics only masks the underlying issue; the actual issue is that glibc contains a libgcc from the bootstrap tools (which is a GCC 8.3), which doesn't have the relevant helpers. I'm surprised this hasn't caused more problems.
The issue for the problem is https://github.com/NixOS/nixpkgs/issues/36947.

authors: lorenz primeos queezle42


text:
[DRAFT] bluemail: init at 1.1.119

Motivation for this change
Fixes https://github.com/NixOS/nixpkgs/issues/154270 , adds package and mail app BlueMail, graphical desktop mail client which also includes a calendar.
nix-build currently fails with:
error: suspicious ownership or permission on '/nix/store/yjwxbw37aqq8q40wrd9m6n6x0mrxg0xk-bluemail-1.1.119.drv.chroot/nix/store/1y818h5fa3q2bdabx10nam3ayx7312zp-bluemail-1.1.119' for output 'out'; rejecting this build output

Don't know why yet :(
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

It seems you forgot to upload pkgs/applications/networking/mailreaders/bluemail/default.nix ?

It seems you forgot to upload pkgs/applications/networking/mailreaders/bluemail/default.nix ?

Added the missing file :)

Try this:
  nativeBuildInputs = [
    autoPatchelfHook
    dpkg
  ];

  buildInputs = [
    pango
    gtk3
    alsa-lib
    nss
    libXdamage
    libdrm
    mesa
    libxshmfence
  ];

  unpackCmd = "${dpkg}/bin/dpkg-deb -x $src debcontents";

  dontBuild = true;
  dontStrip = true;

  installPhase = ''
    mkdir -p $out
    mkdir $out/bin
    mv opt/BlueMail/* $out
    ln -s $out/bluemail $out/bin/bluemail
  '';

It builds fine, but I can't launch the app..

Thank you for figuring this out, maybe we'll can also fix the segfault somehow :)

Not stale.

I switched to a snapshot of the release tarball so we'll have a fixed source. I prefer this approach since it is already working and easier to manage. I added a comment on how to update for later releases. Thank you all for reviewing and giving tips!

authors: FliegendeWurst Mikilio onny


text:
wireplumber: 0.4.6 → 0.4.7

Motivation for this change
Big upstream release: https://gitlab.freedesktop.org/pipewire/wireplumber/-/tags/0.4.7
Notably:

Fixed a regression in 0.4.6 that caused the selection of the default audio sources and sinks to be delayed until some event, which effectively caused losing audio output in many circumstances
Fixed a regression in 0.4.6 that caused the echo-cancellation pipewire module (and possibly others) to not work

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Please link the changelog in the motivation section of the PR

Diff and changelog lgtm, but selecting the default device seems to be broken in this version?

Huh. It's been the opposite for me?

Yeah nah, for me it does not seem to honour the default device selection at all and insists on playing all audio via the front panel jack... which has nothing plugged into it, so any attempts at playing something just fail.

That's weird. Have you reported it upstream?

fwiw I'm still on 0.4.4 because 0.4.5 introduced some weird issues where it kept unlinking nodes... I'll try out 0.4.6 and 0.4.7 when I get a chance to in the next few days though.

That's weird. Have you reported it upstream?

I have not. It does look pretty similar to the issues the changelog claims this fixes though.

Nice. I don't trust myself enough around the codebase to just apply this in nixpkgs, so let's just wait what upstream says.

The nixpkgs bit is quite straightforward:
diff --git a/pkgs/development/libraries/pipewire/wireplumber.nix b/pkgs/development/libraries/pipewire/wireplumber.nix
index 14957478fee..0a8ce1f5eae 100644
--- a/pkgs/development/libraries/pipewire/wireplumber.nix
+++ b/pkgs/development/libraries/pipewire/wireplumber.nix
@@ -1,5 +1,6 @@
 { lib
 , stdenv
+, fetchpatch
 , fetchFromGitLab
 , nix-update-script
 , # base build deps
@@ -30,6 +31,13 @@ stdenv.mkDerivation rec {

   outputs = [ "out" "dev" ] ++ lib.optional enableDocs "doc";

+  patches = [
+    (fetchpatch {
+      url = "https://gitlab.freedesktop.org/pipewire/wireplumber/-/merge_requests/294.patch";
+      sha256 = "sha256-KQ9oglD8D8HWLo4irakRo+dOkwZ9eB4pfknIkX3C1JA=";
+    })
+  ];
+
   src = fetchFromGitLab {
     domain = "gitlab.freedesktop.org";
     owner = "pipewire";

Oh yeah, I'm not saying I don't know how to apply it to Nixpkgs, I'm saying I don't know if it is going to break other things in Wireplumber :)

The MR got merged, it's now in upstream master: https://gitlab.freedesktop.org/pipewire/wireplumber/-/commit/ad80faaa8da75fd562cac4eb776312b83160c9d9.patch

K900: please don't backport this commit, I'm about to revert it

George in #pipewire
Let's just not.

@jansol can you test https://gitlab.freedesktop.org/pipewire/wireplumber/-/commit/211f1e6b6cd4898121e4c2b821fae4dea6cc3317?

Works, in fact it has even nicer behaviour than the previous one by restoring the default device that was configured before switching the default to a bluetooth headset when said headset disconnects. The previous patch would pick the wrong device in that situation.

That's the one George told me to backport, and there will be no hotfix release, so I guess let's go with that?

Sounds like a plan.
A slightly slower option is to watch https://src.fedoraproject.org/rpms/wireplumber/tree/rawhide and see what patches they add on top of the release. The fedora packages are AFAIK maintained by upstream themselves so they should be a safe reference for patch backporting.

authors: K900 arcnmx jansol


text:
stage2: if no /proc, also mount /sys

Motivation for this change
For Cerana we do a bunch of additional configuration before systemd launches. Some of it needs access to /sys. I'm pretty sure this should be fine upstream in NixOS too.
Things done

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

[ ] NixOS
[ ] OS X
[x] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

cc @edolstra

Thanks!

authors: joachifm nshalman