| 4 Nov 2025 |
 Manuel Bärenz | I got a fixed package from my partner and can now run it with dotnet run. I'd like to package it, but after dotnetConfigureHook I get:
Finished dotnetConfigureHook
jq: parse error: Invalid numeric literal at line 1, column 6
| 14:46:37 |
 Corngood | In reply to @manuelbaerenz:matrix.org
I got a fixed package from my partner and can now run it with dotnet run. I'd like to package it, but after dotnetConfigureHook I get:
Finished dotnetConfigureHook
jq: parse error: Invalid numeric literal at line 1, column 6
Could you enable shell tracing and see what it's actually doing? | 15:25:29 |
| Manuel Bärenz | I don't know how to do that inside the nix build | 15:25:59 |
 Emma [it/its] | add set -x somewhere in your hook | 15:26:23 |
| Emma [it/its] | unless thats not what corngood meant | 15:26:45 |
| Corngood | Yeah, that's what I meant. Say preConfigure = "set -x";. I just couldn't remember if there was a better way to do it with NIX_DEBUG or something, but it doesn't look like it. | 15:30:17 |
| Manuel Bärenz | That's a very neat trick :) it seems to fail in nuget-to-json | 15:44:02 |
| Manuel Bärenz | But the temporary file is gone | 15:44:27 |
| Manuel Bärenz | To be sure, I have to run the fetch-deps helper as the very first thing, right? | 15:47:17 |
| Manuel Bärenz | Well, I guess it's possible that my partner's nuget server somehow produces invalid package directories or nuget-to-json doesn't deal with other nuget servers | 16:27:01 |
| Corngood | I'm not sure what you mean by this. If it's failing from a jq call inside nuget-to-json, you can hack that script to set -x as well. This is using a private nuget repo? | 16:30:57 |
| Manuel Bärenz | Yes, it's a private nuget repo, but without credentials | 16:31:35 |
| Manuel Bärenz | Ah. The private nuget repo returns XML, not JSON. I think I can't reconfigure that. | 16:49:14 |
| Manuel Bärenz | Meanwhile, I can run the project with dotnet run. So maybe packaging it isn't as urgent? I guess it's a little less reproducible as a 100% nix solution... | 16:57:05 |
| Corngood | So the index (equivalent of https://api.nuget.org/v3/index.json) is in XML? | 17:25:41 |
| Manuel Bärenz | Yes, it seems so | 17:25:58 |
| Corngood | Is the URL index.xml or something? | 17:27:03 |
| Corngood | I've just never seen a public server like that. We could probably improve support in nuget-to-json, but we'd need some way to test it | 17:27:47 |
| Manuel Bärenz | The url is like nuget.somepartnerdomain.com/Something/nuget, and it returns something like
<?xml version="1.0" encoding="utf-8"?>
<service xml:base="https://nuget.somepartnerdomain.com/Something/nuget" xmlns="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom">
<workspace>
<atom:title type="text">Default</atom:title>
<collection href="Packages">
<atom:title type="text">Packages</atom:title>
</collection>
</workspace>
</service>
| 17:31:00 |
| Manuel Bärenz | And when I go to http://nuget.somepartnerdomain.com/Something/nuget/Packages, I get an XML with package descriptions | 17:31:32 |
| Corngood | It sounded like you had this working with dotnet run? in that case, what url is in your nuget.config? The same one? | 17:54:40 |
| Manuel Bärenz | Yes. It seems like dotnet is able to work with this. Or else it serves an index.json on some path that I haven't discovered yet (I've tried a few) | 18:28:34 |
| Manuel Bärenz | * Yes. It seems like dotnet is able to work with this. Or else that nuget server serves an index.json on some path that I haven't discovered yet (I've tried a few) | 18:30:02 |
| Manuel Bärenz | I believe XML vs JSON is a question of nuget v2 vs v3 | 18:31:05 |
| Corngood | The XML just looks like an atom feed. I wonder how it works. | 20:37:50 |
| Emma [it/its] | "intentionally undocumented" | 22:55:32 |
| 5 Nov 2025 |
 Whovian9369 | Hey, I have a Visual Studio Code flake for messing with C# stuff.
I went to try and debug an app, and got the following error. Any ideas on what could be wrong, if I'm missing a package or something, etc?
`Couldn't find a debug adapter descriptor for debug type 'coreclr' (extension might have failed to activate)` | 05:45:19 |
| Whovian9369 | Nudging this just in case anyone knows! | 18:50:14 |
| 6 Nov 2025 |
| Emma [it/its] | if i override the version, it gets further, odd | 00:01:59 |
| Emma [it/its] | i wonder why nuget is fine with the version on nuget.org but not with the same version on disk | 00:02:46 |
