primordic/IssueDupesLite huggingface dataset:
Repository: open-goal/jak-project

Issue #1792: Game crashes after latest update
Created: 2022-08-23T16:36:33Z
After the latest launcher update, data sync and game update, every time I try to launch Jak 1 the game crashes after the Naughty Dog intro sequence. I can't get through that screen normally.
I use the PAL version of the game and my PC works fine with it.

Duplicate issue #1793: Linux: Game crashes during opening cutscene
Created: 2022-08-23T17:34:28Z
Acknowledgements

 I have searched for duplicate or closed bug reports
 I understand that I am supposed to provide my own legitimately obtained copy of the game

Describe the Bug
OpenGOAL crashes during the opening cutscene where Jak and Daxter arrive at Misty Island, directly after the "Ol' green stuff told us not to come here" line.
The crash happens 100% of the time. Tested on Steam Deck running SteamOS 3.3, with OpenGOAL running as a non-Steam game in game mode. The native Linux version of OpenGOAL was used.
How To Reproduce

On Steam Deck, in desktop mode, install the Linux version of OpenGOAL v0.1.25 using an NTSC 1.0 copy of the game
Add the executable as a non-Steam game
In game mode, launch and start a new game
The game will crash during the misty island cutscene

Does this problem occur on original hardware or PCSX2?
Yes, it's unique to OpenGOAL
Expected Behavior
The game should not crash
Operating System
SteamOS 3.3
OpenGOAL Version
v0.1.25
Game Version
NTSC 1.0 (black label)
Are you using a high refresh-rate monitor (>60Hz)
No

Closing comment (2022-08-23T22:10:08Z): Likely a duplicate of #1792
Can you go into the pc-settings.gc file and change (lod-force-tie 2) to (lod-force-tie 0) and see if that prevents the crash?

That setting was already at 0. Setting it to 2 only reproduced the crash seen in #1792 .
Repository: open-goal/jak-project

Issue #2736: [blerf] pc blend shapes dont work on hiphog mirror
Created: 2023-06-15T19:49:12Z

Duplicate issue #3202: Krew’s reflection has no facial animation
Created: 2023-11-14T22:26:12Z
Acknowledgements

 I have searched for duplicate or closed bug reports
 I understand that I am supposed to provide my own legitimately obtained copy of the game

Describe the Bug
In the cutscene talking with Krew immediately after finishing the mission where you meet Brutter (the talking Lurker), Krew has a scene where he’s talking while looking at himself in the mirror. Krew’s reflection has a blank inanimate expression, no mouth movement or anything, while he is clearly talking and his “real” face can be seen with movement.
I believe this cutscene is where he asks Jak & Daxter to recover a lost statue of Mar from the sewers.
How To Reproduce
Obviously the scene only happens once, BUT, can be reproduced by Replaying the Cutscene once you’ve unlocked Cutscene replay via the “Secrets” menu.
Does this problem occur on original hardware or PCSX2?
Yes, it's unique to OpenGOAL
Expected Behavior
Krew’s reflection’s face/mouth should be moving while he talks.
Environment Information
OpenGOAL v 0.2.2 on Steam Deck via Game Mode (using the shortcut command to play without opening OpenGOAL launcher)
Game Version
NTSC Greatest Hits version (red label)
Have you set the game to something other than 60fps?
No

Closing comment (2023-11-14T22:26:53Z): Duplicate of #2736
Repository: open-goal/jak-project

Issue #1872: [decomp] macro for `(-> self clock frame-counter)`
Created: 2022-09-12T20:15:31Z
appears very often and would hide the process register use

Duplicate issue #1910: Macro for when a function/method accesses the clock from `s6` without having to make it a behavior
Created: 2022-09-24T18:45:19Z
If this is just looking at process clocks, I want to eventually turn this into a macro that doesn't require making things a behavior.
Originally posted by @water111 in #1901 (comment)

Closing comment (2022-09-27T18:51:49Z): duplicate of #1872
Repository: open-goal/jak-project

Issue #1541: Flying Lurker Quest ends with Endless Looping cutscene.
Created: 2022-06-24T13:57:48Z
Acknowledgements

 I have searched for duplicate or closed bug reports
 I understand that I am supposed to provide my own legitimately obtained copy of the game

Describe the Bug
The powercell I'm unable to get no matter what atm is the one in the basin where you have to kill the flying lurkers. I kill the last one and the power cell pops out but it still takes the same AI path as the last lurker killed and the cutscene follows it in an unskippable endless loop. This effectively soft locks the game and I have to restart.
How To Reproduce
Try completing the basin lurker mission via killing all of the flying lurkers. If it works normally, try on a high refresh rate monitor (I use a 200hz monitor).
Does this problem occur on original hardware or PCSX2?
Didn't check
Expected Behavior
The cutscene not looping and the player being able to get the powercell for that mission.
Operating System
Windows
OpenGOAL Version
1.6 and 1.9 release versions
Game Version
NTSC 1.0 (black label)
Are you using a high refresh-rate monitor (>60Hz)
Yes

Duplicate issue #1642: Flying lurkers power cell on Precursor Basin
Created: 2022-07-13T17:20:13Z
Acknowledgements

 I have searched for duplicate or closed bug reports
 I understand that I am supposed to provide my own legitimately obtained copy of the game

Describe the Bug
Flying Lurker power cell on Precursor Basin level cannot be obtained. Camera locks on dropped power cell and follows it as power cell follows the path of killed lurker. At this point game behave like its in a cutsceene. Cannot enter pasue menu and you can only pause it like its cutsceene.

  
    
    

    JakAndDaxterTPOL.-.Precursor.Basin.powercell.bug.mp4
    
  

  

  


How To Reproduce
-Enter Precursor Basin level on a zoomer
-Use zoomer to catch up with flying lurkers (the order doesnt matter)
-Last lurker drops power cell that cannot be obtained
Does this problem occur on original hardware or PCSX2?
Yes, it's unique to OpenGOAL
Expected Behavior
If i kill last lurker Jak should go into powercell animation and collect it.
Operating System
Windows 10 Pro 21H2 OS build 19044.1706
OpenGOAL Version
v0.1.6
Game Version
NTSC 1.0 (black label)
Are you using a high refresh-rate monitor (>60Hz)
Yes

Closing comment (2022-07-13T17:30:07Z): Closing this issue as it is a duplicate of #1541 #1524
This is also resolved in #1518
If you update from 0.1.6 this issue will fix
Repository: open-goal/jak-project

Issue #3285: [jak2] Sounds cutting out or loss of sound when running a gun course
Created: 2024-01-01T05:06:28Z
Acknowledgements

 I have searched for duplicate or closed bug reports
 I understand that I am supposed to provide my own legitimately obtained copy of the game

Describe the Bug
When running the gun course it seems the sequence has a lot of sounds playing at once that overlap one another and in parts or sometimes nearly the entirety of running the gun course.
How To Reproduce
Obtain any gun mod and run the gun course for it. I've only tested this with the scatter gun and blaster.
Does this problem occur on original hardware or PCSX2?
Not needed, bug is obvious
Expected Behavior
All sound is meant to play without cut outs or complete loss of sound.
Environment Information
CPU: Intel i7-7700K 4.2GHz
GPU: Nvidia GTX 1070 8GB VRAM
OS: WIndows 10 64-bit Build 21H2 19044.3086
OpenGoal Version: v0.2.4
In-game options running
1920x1080
Windowed
Aspect Ratio Automatic
60FPS
V-Sync off
MSAA 2x
LOD Background High
LOD Foreground High
Particle Culling Off
Object Shadows Extended
High-Resolution Sky On
Game Version
NTSC Greatest Hits version (red label)
Have you set the game to something other than 60fps?
No

Duplicate issue #3286: Gun course sound breaks
Created: 2024-01-01T06:17:44Z
Acknowledgements

 I have searched for duplicate or closed bug reports
 I understand that I am supposed to provide my own legitimately obtained copy of the game

Describe the Bug
When doing the gun courses (both scattergun and blaster), partway through the course the audio of certain things cuts out. These include gun sounds, targets popping up, targets breaking, score sounds, etc. Once they break, they might occasionally work again for a few shots, but most sounds were silenced for the remainder of the course.
How To Reproduce
Do a gun course using either scattergun or blaster (haven't tested other weapons, haven't made it that far in the game yet).
Does this problem occur on original hardware or PCSX2?
Yes, it's unique to OpenGOAL
Expected Behavior
Sounds should go off when doing things.
Environment Information
opengoal-support-package.zip
Game Version
NTSC Greatest Hits version (red label)
Have you set the game to something other than 60fps?
No

Closing comment (2024-01-01T13:37:26Z): "I have searched for duplicate or closed bug reports"
Duplicate of #3285
Repository: open-goal/jak-project

Issue #2840: (Jak 1) Credits don't look right
Created: 2023-07-23T23:42:00Z
Acknowledgements

 I have searched for duplicate or closed bug reports
 I understand that I am supposed to provide my own legitimately obtained copy of the game

Describe the Bug
https://github.com/open-goal/jak-project/assets/28773304/8905e081-0626-4e52-8513-cce1c1735cc3
There is a black 4:3 box that flickers a lot, this may be an issue with high frame rate. You can also see the level geometry on the left and Jak behind the box, which I don't think is intentional.
How To Reproduce
View the credits at 16:9 and running at 150 fps
Does this problem occur on original hardware or PCSX2?
Yes, it's unique to OpenGOAL
Expected Behavior
https://youtu.be/J56g-ULzfBQ
Operating System
Windows 10 Pro
OpenGOAL Version
v0.1.38
Game Version
NTSC 1.0 (black label)
Are you using a high refresh-rate monitor (>60Hz)
Yes

Duplicate issue #3401: Steam Deck Jak 1 intro & credits graphical display issue
Created: 2024-03-05T15:19:12Z
Acknowledgements

 I have searched for duplicate or closed bug reports
 I understand that I am supposed to provide my own legitimately obtained copy of the game

Describe the Bug
Both at the intro and credits the main dark eco purple backdrop and eco effects would flicker on/off to a black display, except for 1 cm sidbars of the display that would show part of the dark eco backdrop and part of the sky line for the after credit scene. The cast/credit scrolling text had no graphical issues whatsoever. The after-credit cutscene resumed without any graphical hiccups.
How To Reproduce
Played to 100% completion to end credits
Does this problem occur on original hardware or PCSX2?
Yes, it's unique to OpenGOAL
Expected Behavior
The dark eco backdrop with the eco particle effects should display in the background for the duration of Samos' early intro speech until Jak's introduction and to completion of the end credits with the text scrolling, both without pop-in or flickering
Environment Information
Settings/configuration:

Steam Deck Oled SSD swapped to 1TB
SteamOS v3.5.17 stable
Decky Loader v2.11.1 stable
decky OpenGOAL 1.1.2
VibrantDecks 2.0.0-1 @ 130
Performance Frame Limit 90 PFS (90 Hz) Disable Frame Limit
Jak1 Graphics settings:1280x800, Display Mode Fullscreen, V-sync on, Display XWAYLANDO 7" (1), Aspect Ratio Fit-to-screen, MSAA x16, Frame Rate (Experimental) 100, PS2 Options: Level of Detail (background high, foreground high), Particle Culling off, Force Environment Mapping on, Actor Culling on

Game Version
NTSC 1.0 (black label)
Have you set the game to something other than 60fps?
Yes

Closing comment (2024-03-05T15:24:44Z): Pretty sure this is a duplicate of #2840 which is caused by non-60fps
Repository: open-goal/jak-project

Issue #1521: Credits/Prologue has a distinct black-box on wider aspect ratios
Created: 2022-06-22T22:51:42Z
Describe the Bug
https://youtu.be/JPK14SSUIdg
I updated OpenGoal to v0.1.9, went to run to check some stuff and noticed the prologue was flickering, tried updating my nvidia drivers and it was still doing the same thing.
How To Reproduce
Running it.
Expected Behavior
Too not flicker during the prologue.
Operating System
Windows 11
OpenGOAL Version
Release
Game Version
NTSC 1.0 (black label)

Duplicate issue #2840: (Jak 1) Credits don't look right
Created: 2023-07-23T23:42:00Z
Acknowledgements

 I have searched for duplicate or closed bug reports
 I understand that I am supposed to provide my own legitimately obtained copy of the game

Describe the Bug
https://github.com/open-goal/jak-project/assets/28773304/8905e081-0626-4e52-8513-cce1c1735cc3
There is a black 4:3 box that flickers a lot, this may be an issue with high frame rate. You can also see the level geometry on the left and Jak behind the box, which I don't think is intentional.
How To Reproduce
View the credits at 16:9 and running at 150 fps
Does this problem occur on original hardware or PCSX2?
Yes, it's unique to OpenGOAL
Expected Behavior
https://youtu.be/J56g-ULzfBQ
Operating System
Windows 10 Pro
OpenGOAL Version
v0.1.38
Game Version
NTSC 1.0 (black label)
Are you using a high refresh-rate monitor (>60Hz)
Yes

Closing comment (2023-07-24T00:05:33Z): Likely a duplicate of #1521 The flickering was described as fixed as of 0.1.12, could be a recent regression.
Repository: open-quantum-safe/liboqs

Issue #1768: dlfcn required for windows build
Created: 2024-04-25T14:26:36Z
Describe the bug
When building on windows receive a compile error from src/common/ossl_helpers.c - dlfcn.h is not available on windows
To Reproduce
Try to build on windows :)
Expected behavior
One of four things:

Provide cross-platform code to load shared libraries (alternative to dlopen / dlclose)
#ifdef around #include <dlfcn.h> / dlfcn functions (simply ignore on windows and assume that required libraries are loaded).
Require dlfcn-win32 package with basic instructions on the liboqs github page on how to install (prerequisite).
Auto-install dlfcn-win32 from dlfcn-win32 github page as part of standard build.

Screenshots
I even put on a screenshot for you :)

Environment (please complete the following information):

OS: Windows 11 with Visual Studio 2022 latest patches
OpenSSL version: 3.3.0
Compiler version used: MSVC (CL) 19.39.33523
Build variables used: no overrides
liboqs version: main branch

Additional context
I added logs collected from my run which shows all the configuration occurring.
buildliboqs.log''
I worked around the problem as follows:
// ABr: avoid dlfcn on windows
#if !defined(_MSC_VER)
#include <dlfcn.h>
#endif
[...]
static void ensure_symbol(const char *name, void **symp) {
#if !defined(_MSC_VER)
	if (!*symp) {
		void *sym = dlsym(libcrypto_dlhandle, name);
		if (!sym) {
			exit(EXIT_FAILURE);
		}
		*symp = sym;
	}
#endif
}
static void ensure_library(void) {
#if !defined(_MSC_VER)
	if (!libcrypto_dlhandle) {
		libcrypto_dlhandle = dlopen(OQS_OPENSSL_CRYPTO_SONAME,
		                            RTLD_LAZY | RTLD_LOCAL);
		if (!libcrypto_dlhandle) {
			exit(EXIT_FAILURE);
		}
	}

#define ENSURE_SYMBOL(name) \
    ensure_symbol(#name, (void **)&_oqs_ossl_sym_##name)
#define FUNC(ret, name, args, cargs)        \
    ENSURE_SYMBOL(name);
#define VOID_FUNC FUNC
#include "ossl_functions.h"
#undef VOID_FUNC
#undef FUNC
#undef ENSURE_SYMBOL
#endif
}

Duplicate issue #1935: Compilation error: Cannot open include file: 'dlfcn.h'
Created: 2024-09-26T06:07:10Z
Describe the bug
When building for windows on windows with VS19 I get the following compilation error:
20:58:05  C:\Users\****local\workspace\422-use-oqs-provider-main-branch\submodules\linphone-sdk\external\liboqs\src\common\ossl_helpers.c(7): fatal error C1083: Cannot open include file: 'dlfcn.h': No such file or directory

Environment (please complete the following information):

OS: windows, VS 19
OpenSSL version: -
liboqs version: main

Closing comment (2024-09-27T13:47:22Z): Closing as a duplicate of #1768.
Repository: open-quantum-safe/liboqs

Issue #1894: SLH-DSA: integrate final standard
Created: 2024-08-15T14:22:46Z
In line with FIPS 205.
We have support for Round 3 SPHINCS+, but nothing more recent. Our current upstream source is https://github.com/sphincs/sphincsplus via PQClean, so we should find out their plans for updates.
Tagging @bwesterb as a significant upstream contributor: are there plans to bring the implementation in sync with the final standard?

Duplicate issue #2052: SLH-DSA support
Created: 2025-01-24T16:21:06Z
Hello,
I see that both Dilithium* and ML-DSA-* algorithms are supported.
But only Sphincs+* algorithms are there without SLH-DSA-*.
Is there a plan to support SLH-DSA-* algorithms too?

Closing comment (2025-01-24T16:29:51Z): Closing as duplicate of #1894: Please see/track status there.
Repository: open-quantum-safe/liboqs

Issue #1891: ML-DSA: integrate final standard
Created: 2024-08-13T15:44:06Z
The final standards were published today: FIPS203 and FIPS204.
This is to track the integration of the updated algorithms.
I'd suggest the following steps:

Pull update from pq-crystals upstream once available
The current ML-DSA-ipd/ML-KEM-ipd implementations would be dropped
Integrate test vectors from NIST ACVP repository

update (Aug 22):

pq-crystals/kyber upstream has been updated
ML-KEM / ML-DSA OIDs have been published
ACVP repository has been updated
#1899 integrates ML-KEM and ACVP vectors

Update (Aug 27):
ML-KEM landed in main, remaining is ML-DSA integration
Update (Sep 5):
ML-DSA is available upstream: https://github.com/pq-crystals/dilithium

Duplicate issue #1850: Latest updates to ML-DSA are not implemented yet
Created: 2024-07-19T17:55:15Z
Describe the bug
Looks like NIST has updated the parameters for Dilithium and Kyber which is still not implemented in the OQS.
Please refer below link from atsec
https://atsec-information-security.blogspot.com/2023/11/pqc-kyber-and-dilithium-state-of-draft.html
If that is true and If NIST has already made the changes for Its ACVP demo server , is there any plan to incorporate these changes in OQS anytime soon ?

Closing comment (2024-08-16T12:50:49Z): Tracked in #1891.
Repository: open-quantum-safe/liboqs

Issue #2098: Solicit more schemes from NIST signature on-ramp round 2
Created: 2025-03-07T18:33:33Z
Get feedback from CROSS team and UOV team (@mkannwischer) about how it went for them adding their schemes to liboqs (@baentsch volunteered to reach out, I think)
 Develop a short primer on how to get started
 Reach out to teams to solicit their contributions

Duplicate issue #2101: Adding FAEST
Created: 2025-03-14T11:30:43Z
I am looking into adding FAEST to liboqs. Since I have last worked with liboqs, the build setup has changed quite significantly. What is the recommended way to add a single implementation to liboqs that provides all variants? All signature schemes using copy_from_upstream have multiple copies of similar/same files. Also, can I get copy_from_upstream to perform pre-configuration steps before copying files?

Closing comment (2025-03-14T11:39:01Z): This is related to #2098.
I can add FAEST as it was done for Picnic. If that is still okay with the current setup, I have a PR almost ready to go.
Repository: open-quantum-safe/liboqs

Issue #1831: Update CBOM to CycloneDX 1.6 format
Created: 2024-07-01T16:38:40Z
State of current BOM:
The current BOM at docs/cbom.json mostly validates against the 1.4 spec with just 1 issue

metadata.,timestamp value of 2024-03-05T11:49:42.428605 fails with String is not a RFC3339 date-time.

In RFC3339 a time-offset is required, ie can be Z.
Using 2024-03-05T11:49:42.428605Z passes validation.
This change is needed in the tooling that builds/tests the BOM
Improvement to include pointer to schema
Many BOMs include a pointer to the spec ie we could add
  "$schema": "https://raw.githubusercontent.com/IBM/CBOM/main/bom-1.4-cbom-1.0.schema.json#",

Aside - as an alternative, and for testing, the following can be added in .vscode settings:
    "json.schemas": [
        

        {
            "fileMatch": [
                "cbom.json"
            ],
            "url": "https://raw.githubusercontent.com/IBM/CBOM/main/bom-1.4-cbom-1.0.schema.json"
        }
    ]

Cyclone DX 1.6
CBOM is now incorporated into CycloneDX 1.6, but here the schema as evolved a little
We can validate against the new spec - the example below includes the vscode definition:
    "json.schemas": [


        {
            "fileMatch": [
                "cbom.json"
            ],
            "url": "http://cyclonedx.org/schema/bom-1.6.schema.json"
        }
    ]

If $schema is included in the bom, then other tools wouldn't need to explicitly be configured, and should find the schema definition automatically
In CycloneDX 1.6 the following is noted:

 "bomFormat": "CBOM", -> can only be 'CycloneDX'
"type": "crypto-asset", -> 'cryptographic-asset'
In algorithmProperties, variant & implementationLevel are not allowed. where the last segment of Variant includes a platform like x86_64 this probably is now best matched to implementationPlatform , whilst implementationLevel is executionEnvironment
in cryptoProperties, nistQuantumSecurityLevel is not allowed - it has moved under algorithmProperties
"primitive": "blockcipher", -> block-cipher
"dependencyType": "uses" - not allowed. there is a new property provides which seems to make sense where an algorithm is provided, whilst just having a dependency presumes uses ..?

Note the above is from a quick scan - need to check in more detail...
@bhess @dstebila I think it would be useful to consider this update now that the 1.6 spec is out, and we're seeing more tooling support CBOM.
Happy to work on some updates if it's helpful - or perhaps you plan to @bhess ?

Duplicate issue #1753: Update CBOM to CycloneDX 1.6 specification
Created: 2024-04-10T07:20:25Z
The specification used for CBOMs has been upstreamed to CycloneDX 1.6:
https://github.com/CycloneDX/specification/releases/tag/1.6
This issue is to update the CBOM in liboqs, and its generation script to the CycloneDX 1.6 specification.

Closing comment (2024-07-23T14:41:32Z): Closing this issue as a dupe of #1831.
Repository: open-quantum-safe/liboqs

Issue #1026: Pull updated NTRU Prime from PQClean
Created: 2021-06-18T01:02:07Z

Duplicate issue #1031: Add NTRU HPS-4096-1229
Created: 2021-06-24T02:58:22Z
NTRU team submitted Security Category 5 parameter set NTRU-HPS-4096-1229 (available source is at https://github.com/jschanck/ntru).
Could you please add it to the library?

Closing comment (2021-06-25T06:55:36Z): Isn't this issue basically the same as #1026, @~jschanck ?

NTRU Prime is a different NIST submission.
Repository: open-quantum-safe/liboqs

Issue #1401: Is there a method to display the public key of signatures?
Created: 2023-01-19T13:07:35Z
There are 2 ways to init the signatures. One is to initiate with
signer.Init(sigName, nil)
After that, a keypair can be generated with
signer.GenerateKeyPair()
which returns the public key.
The second way is to initiate with:
signer.Init(sigName, secretKeyBytes)
This function doesn't return a public key. I also didn't find a function like:
signer.publicKey()
Is there a best practice for extracting the public key? It would be great if this function would be part of the liboqs-go library.

Duplicate issue #2030: Signatures: derive keypair from seed or public key from private key
Created: 2025-01-02T13:07:08Z
Signature schemes  generate keypair from seed , and recontruct public key from private key.

Closing comment (2025-01-03T21:45:50Z): Hi @mraksoll4, would you consider this issue to be a duplicate of #1401 or #1802 (or both)?

It’s similar, but I don’t think so, since that issues there relate to encapsulations, and mine are related to Signature schemes.

That's fair. I've renamed the issue to make its categorization a little more clear.
Repository: open-quantum-safe/liboqs

Issue #1894: SLH-DSA: integrate final standard
Created: 2024-08-15T14:22:46Z
In line with FIPS 205.
We have support for Round 3 SPHINCS+, but nothing more recent. Our current upstream source is https://github.com/sphincs/sphincsplus via PQClean, so we should find out their plans for updates.
Tagging @bwesterb as a significant upstream contributor: are there plans to bring the implementation in sync with the final standard?

Duplicate issue #1917: Support FIPS 205
Created: 2024-09-10T10:49:25Z
Anyone interested to add SLH-DSA to the list of supported algorithms both in liboqs and oqsprovider? Also see IETF-Hackathon/pqc-certificates#137 (in case OQS wants to provide a comparable level of functionality as BouncyCastle).

Closing comment (2024-09-10T13:17:16Z): @baentsch, OK if I close this as a duplicate of #1894? (Or merge the two if there's a way to do that.)
Repository: open-telemetry/opentelemetry-rust

Issue #2753: OpenTelemetry API should not expose Sampling related constructs
Created: 2025-03-04T14:54:08Z
https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry/src/trace/tracer.rs#L384-L408 is exposing Sampling related constructs. Sampling is a sdk (opentelemetry_sdk) concern, and these APIs should not exposed from opentelemetry crate.
Related to #2420 as these were originally exposed to special case tracing-opentelemetry

Duplicate issue #2745: SpanBuilder should not allow with_status
Created: 2025-03-03T19:57:47Z
Similar to #2743
I am not sure what is the need of with_status in the SpanBuilder. SpanBuilder is used to create a new Span, at which point the status should be unknown. It totally is valid to have this API on the Span itself as that'll be called only after a Span has been created.

Closing comment (2025-03-05T04:58:20Z): Yes, it is similar to #2753
We cannot stabilize Otel Tracing API with these APIs exposed. (A lot of special casing to support tracing-opentelemetry actually).
Hopefully @bantonsson's work will allow us to trim public APIs.
Repository: open-telemetry/opentelemetry-rust

Issue #3: Add CODEOWNERS and corresponding permissions
Created: 2019-11-27T00:14:23Z
Let's make sure everyone has permission to review (and that PRs actually require appropriate checks!), get assigned issues, etc.

Duplicate issue #32: Please setup CODEOWNERS.
Created: 2019-12-02T19:16:16Z

Closing comment (2019-12-02T19:35:04Z): Closing as a duplicate of #3
@bogdandrutu I believe you only the TC has the power to do this (per open-telemetry/community#262) 🙃
Repository: open-telemetry/opentelemetry-rust

Issue #1966: [Docs]: Compatibility matrix
Created: 2024-07-25T13:11:53Z
Related Problems?
No response
Describe the solution you'd like:
This is very much just a this-crate issue. But the usage of traits from different otel crates is widespread enough that whenever I attempt to upgrade I end up in some compatibility nightmare trying to get all the versions aligned to the correct one. As far as I see if it, the solution would be either to move versions up lockstep and disregarding semver (or at least broadening it's definition to cover all the various crates), or alternatively document for each opentelemetry version what the latest compatible version for the other crates are.
I'd rather not spend another hour of my life trying to solve issues like the trait JaegerTraceRuntimeis not implemented forTokio`` whenever I upgrade this crate. Unfortunately, the opentelemetry upgrades are the most painful upgrades I've found in the Rust ecosystem 😢
Considered Alternatives
No response
Additional Context
No response

Duplicate issue #2084: Unified versioning across all crates
Created: 2024-09-07T14:09:14Z
Problem:
Currently, each crate in this repo is independently versioned. This makes it difficult to track issues when users report issues, as we need to ask for the version of every individual crate before we can investigate. This is unnecessary overhead. When we do a release, it is equally hard to "name" the overall release. We have been using the pattern "Release ABC", where ABC is the version of the API crate.
Proposal:
Proposing that we use a single version number(Major.Minor) for all crates in this repo. This would mean that when one crate is updated, all crates would use the same version number (Major.Minor), regardless of whether they had changes or not. Although this could result in “empty” releases for crates without actual changes, such occurrences are extremely rare. A hotfix for a leaf crate (which no other crate depends on) would only update a patch version number, so no need to force a version bump for all other crates, as the proposal is to use uniform Major.Minor for all crates, and patch number could be different if there is a need.
Once we reach the 1.0 release, we can revisit the versioning strategy if necessary. However, unifying the versions now simplifies pre-1.0 development and testing, which is our current focus.
Please share thoughts/feedback on this. If no concerns, I plan to use this approach for the release planned now. (Release was originally planned for earlier this week, but I expect to do it by Monday)

Closing comment (2024-09-09T08:21:26Z): Related to #1966
Repository: open-telemetry/opentelemetry-rust

Issue #955: Remove stale gauges
Created: 2023-01-24T21:46:52Z
Hi!
I have the following example that exports a set of gauges.
In some cases, my gauges become stale (i.e the thing they track no longer exists), in which case, I don't wish for them to be exported anymore.
Failing to do this just makes the gauge retain it's value forever, which makes my metric aggregations wrong.
Is there a way to remove these stale metrics from my meter or registry?

Duplicate issue #1221: Reset ObservableGauge for all cached attributes sets to 0
Created: 2023-08-22T23:00:54Z
I'm using an ObservableGauge to track errors of certain entities that the application is monitoring might have encountered.
The application scans the state of those entities, in periodic intervals, aggregates errors, and then updates gauges according to the latest state. This uses code along:
let mut attrs: Vec<KeyValue> = attributes.to_vec();
attrs.push(KeyValue::new("error", "".to_string()));
let mut total_errs = 0;

for (error, &count) in m.errors_encountered.iter() {
    total_errs += count;
    attrs.last_mut().unwrap().value = error.to_string().into();
    self.errors_gauge
        .observe(otel_cx, count as u64, &attrs);
}

attrs.last_mut().unwrap().value = "any".to_string().into();
self.errors_gauge
    .observe(otel_cx, total_errs as u64, &attrs);
That works fine for all errors that had been recently encountered.
However I noticed that once one scan doesn't report a certain error anymore, the opentelemetry-rust/promtheus stack still reports the old error. It would need to be explicetly set to 0.
Is there any mechanism in opentelemetry-rust that allows to reset a gauge (with all variations of attributes) to 0 before updating them again?
If there would be a well-defined set of errors, I could obviously manually update the values that are not part of errors_encountered to 0. But since those errors are dynamic strings that are received from another application that isn't easily possible.
Maybe the right answer here is also "you are doing it wrong and shouldn't use gauges for it", which is certainly debatable :)  But for this particular problem where the exact amount of entities in a certain state should be determined independently of the report frequency and without metric math, they seem much easier to use.

Closing comment (2023-10-01T18:21:27Z): It seems to be related to #955. I think the issue has been patched in v0.20 so will close this out for now. Feel free to reopen if you have other questions/comments
Repository: open-telemetry/opentelemetry-rust

Issue #1209: Perf bottleneck when Loggers upgrade weak ref to LoggerProvider
Created: 2023-08-17T00:48:43Z
Noticed while stress testing Logs, but should be applicable to Tracing as well, as they follow the same pattern, where Logger (Tracer), holds a Weak ref to LoggerProvider (TracerProvider), and in hoth path (logger.EmitLog, span.Record), the weak reference to provider is upgraded to Arc, to obtain things like processor list, resource etc. from the provider. This weak -> Arc upgrade seems to be the bottleneck.
Here's how I tested:

Ran the stress test for logs, in my box, and it shows ~7M/sec throughput.
Modified the NoOpLogProcessor in the above test to  return false, which should make the throughput skyrocket as we don't have to do anything like creating LogRecord or invoke processors etc. This did increase the throughput to ~35M/sec, but I was expecting 200+M/sec, as I get similar throughout when using tracing+no-op-tracing-subscriber, without any OpenTelemetry component.
After some manual explorations, found that the upgrading of weak to Arc in the hot path of checking if event is enabled is the bottleneck.
I refactored the code so that Logger is holding an Arc instead of Weak (draft code ), so there is no longer the need for upgrading to Arc in hotpath. With this change, the throughput shot to ~250M/sec (in line with what was seen with using tracing+no-op subscriber alone).

The weak ref to provider was introduced for Tracing (and then followed for Logging), in this PR. Using Arc does mean that the Provider won't be dropped and shutdown won't be signaled until the last Logger is dropped, but that seems okay to me. In the case of Logging, Logger's are held only by the appenders (tokio-tracing subscribers etc), which, when dropped, will drop their Logger as well, allowing provider to be dropped....
I do not know if this has any further implications, especially for Tracer/Span case.
The (perf) issue is applicable to Span as well as this upgrade occurs (I think) twice - when span begins and when span ends...
Opening this issue to get feedback on this from experts and to check if this draft code is a reasonable direction to further explore.

Duplicate issue #542: Closing and exporting all spans on panic (when panic=abort)?
Created: 2021-05-08T03:35:45Z
I'm using tracing-opentelemetry. From what I understand, spans rely on Drop implementations to close, and until the span is closed it won't be shipped off. I'm currently using panic=abort for various reasons. I'd love to have a global method that I can call from a panic handler that will close and export all spans before exiting, to make sure enough tracing information has been sent out to debug the panic.

Closing comment (2023-10-24T16:55:04Z): Related to #1209
Repository: open-telemetry/opentelemetry-rust

Issue #1427: [Feature]: Port opentelemetry-http to hyper 1.x
Created: 2023-12-05T10:18:41Z
Related Problems?
hyperium/tonic#1307
Describe the solution you'd like:
Hyper 1.0 has been released and as such it'd be nice to upgrade opentelemetry-http's HttpClient to the new version
Considered Alternatives
No response
Additional Context
No response

Duplicate issue #1916: Upgrade to tonic 0.12 and prost 0.13 for hyper 1.x
Created: 2024-07-08T22:05:12Z
Hyper and HTTP reaches 1.x at the end of last year. Now tonic releases 0.12 to catch up this change and opentelemetry-rust could follow it.

Closing comment (2024-07-08T22:31:34Z): Thank you! Close as a duplicate of #1427.
Repository: openaddresses/openaddresses

Issue #5919: Australia has wrong lng/lat projection
Created: 2021-10-01T21:29:25Z
The lng/lat in:

au/countrywide - addresses - country: https://batch.openaddresses.io/job/161058
au/qld/brisbane_city_council - addresses - city: https://batch.openaddresses.io/job/70545

Duplicate issue #5906: nz_countrywide has lat/lon values flipped
Created: 2021-09-29T11:30:00Z
Heya,
I downloaded the nz_countrywide-addresses-country.geojson.gz file today and noticed that the lat/lon coordinates are reversed.
Looking at the source it seems to be mapped correctly 🤷
https://github.com/openaddresses/openaddresses/blob/master/sources/nz/countrywide.json#L29-L30

note: latitude values >90.0

gzcat ~/Downloads/nz_countrywide-addresses-country.geojson.gz | head -n2 | jq .geometry
{
  "type": "Point",
  "coordinates": [
    -36.6304294,
    174.4978477
  ]
}
{
  "type": "Point",
  "coordinates": [
    -36.630864,
    174.4972355
  ]
}
I also checked another file file from NZ and it was correct:
gzcat ~/Downloads/nz_greater_wellington-addresses-city.geojson | head -n2 | jq .geometry
{
  "type": "Point",
  "coordinates": [
    174.9550451,
    -40.9808712
  ]
}
{
  "type": "Point",
  "coordinates": [
    174.954071,
    -40.981851
  ]
}

Closing comment (2021-11-04T01:09:54Z): probably the same as #5919 (comment)
Repository: openaddresses/openaddresses

Issue #5917: Slovenia flipped coords
Created: 2021-10-01T07:32:08Z
The source has the columns as:
lon;lat;number;street;city;commune;region;postcode;id
13.9095556;45.8873882;1;Cankarjev trg;Ajdovščina;Ajdovščina;Goriška;5270;11028489
13.909424;45.8875309;2;Cankarjev trg;Ajdovščina;Ajdovščina;Goriška;5270;11028497
...

lon=longitude E
lat=latitude N
In PoC #5909 i have flipped them around to confirm that this is the problem, but obviously that is not right solution.
Related to:

openaddresses/batch#90
PoC: #5909
similar #5906
similar #5908 & #5910
similar #5911
similar #5912
similar #5919
possibly blocking #5907

According to the history log the change happened between

Job 115435 / 2021-06-11 which was last OK ✅  and
Job 118280 / 2021-06-18 which was the first with error  ❌


Between those jobs thee openaddresses/batch-machine#15 was merged on 2021-06-16 ⚠️

Duplicate issue #5919: Australia has wrong lng/lat projection
Created: 2021-10-01T21:29:25Z
The lng/lat in:

au/countrywide - addresses - country: https://batch.openaddresses.io/job/161058
au/qld/brisbane_city_council - addresses - city: https://batch.openaddresses.io/job/70545

Closing comment (2021-10-03T09:59:55Z): Possibly due to openaddresses/batch#90, similar to #5917 (and other issues listed in there).
Repository: openaddresses/openaddresses

Issue #5462: Door County, WI has no land boundaries
Created: 2020-11-25T20:29:59Z
The upper half of the peninsula in Wisconsin (Door County) shows as water with roads on all zoom levels except the closest few, where the land boundaries suddenly render.

Duplicate issue #5463: Castaic Lake shows as land with little streams
Created: 2020-11-25T20:30:45Z
Castaic Lake in northern Los Angeles County, California does not show as a lake but as a series of small streams on land.

Closing comment (2020-11-25T20:37:30Z): Dupe #5462
Repository: openaddresses/openaddresses

Issue #4619: Latest download only 2GB(6GB)
Created: 2019-09-12T14:52:51Z
Dear all,
The latest download available on https://results.openaddresses.io/ seems to be way smaller than expected. It seems to include sources that are only of type esri.
Best,
Cyprien

Duplicate issue #4624: Maine Missing from download data
Created: 2019-09-13T17:42:09Z
when downloading in batch from https://data.openaddresses.io/openaddr-collected-us_northeast.zip  - it appears there is no ME directory, and all addresses are missing. Why?

Closing comment (2019-09-13T17:57:31Z): perhaps this issue is related to #4619 ?
Repository: openaddresses/openaddresses

Issue #3842: Thames-Coromandel District Councils (TCDC), NZ Addresses
Created: 2018-01-27T13:53:14Z
https://services5.arcgis.com/MYtLmLEStmKgdmln/ArcGIS/rest/services/Property_Information/FeatureServer/0
found in: https://hub.arcgis.com/datasets/tcdc::parcel-boundaries

Duplicate issue #4045: Thames-Coromandel District Councils (TCDC), New Zealand
Created: 2018-06-06T14:44:04Z
https://services5.arcgis.com/MYtLmLEStmKgdmln/arcgis/rest/services/Property_Information/FeatureServer/0

Closing comment (2018-08-31T04:56:40Z): duplicate of #3842
Repository: openaddresses/openaddresses

Issue #4994: Italy data text encoding problem
Created: 2020-04-28T14:34:44Z
A data user reported that the Italy countrywide source has some text encoding issues:
Hi, i’ve download the italy countrywide set but i see some encoding errors.
for example i see "CANICATTÃŒ”.  but the city is named Canicattì.

Duplicate issue #6070: it/countrywide: Wrong encoding
Created: 2022-06-18T12:47:42Z
The output of it/countrywide has wrong encoding.
To fix the problem I've to convert from utf8 to latin1, as if there was an unnecessary latin1 to utf8 conversion.
I tried to fix it by editing the schema and configuring encoding="iso-8859-1" or encoding="utf-8" but nothing changed in either case.
encoding="iso-8859-1": https://batch.openaddresses.io/job/257622
encoding="utf-8": https://batch.openaddresses.io/job/257623
Example: CANICATTÃ� should be CANICATTÌ

Closing comment (2023-06-09T13:53:46Z): Duplicate of #4994
Repository: openaddresses/openaddresses

Issue #2207: Imperial county, California
Created: 2016-12-07T05:08:47Z
Part of "finish California" sprint.

Duplicate issue #2515: Imperial County, California Data Request
Created: 2017-02-09T17:51:13Z
emailed Imperial County - assessor@co.imperial.ca.us
http://www.co.imperial.ca.us/Assessor/FIRelease.html
data here: http://services.geoviewer8.com/arcgis/rest/login?redirect=http%3A//services.geoviewer8.com/arcgis/rest/services/ImperialCounty_Public/MapServer/

Closing comment (2017-02-09T17:58:39Z): This is a dup of #2207.
Repository: openaddresses/openaddresses

Issue #2422: Sweden National Addresses
Created: 2017-01-24T16:15:13Z
http://www.lantmateriet.se/sv/Kartor-och-geografisk-information/Geodatatjanster/Tjanster-enligt-Inspire1/#faq:Adress-Nedladdning-Inspire

Duplicate issue #2468: Open-Data Sweden
Created: 2017-01-31T16:02:43Z
Find out if addresses delivered by Swedish kommuns is (or how to make them) Open Data. There is no what so ever information that the data Swedish kommuns is providing this project over services or other media is Open Data and may be used for openaddresses.
BTW According to Malmö kommun they do not have any Open.
Please help use solve this problem, Benny Jonsson Lunds Kommun.

Closing comment (2017-08-03T19:42:11Z): This looks like a duplicate of #2422, closing this one.
Repository: openaddresses/openaddresses

Issue #2185: 2016 Washington State parcels (polygons)
Created: 2016-12-02T15:49:35Z
http://geoservices.wa.gov/arcgis/rest/services/Parcels/ECY_Washington_State_Parcel_Database_2016/MapServer/0

Duplicate issue #2141: State of Washington address data (points)
Created: 2016-11-17T23:24:19Z
Joy Paulus, Senior Policy & Program Manager
State GIS Coordinator, Geospatial Program Office
PO Box 42440, Olympia, WA 98504-2440
360.407.8691 | joy.paulus@ocio.wa.gov
Spoke to Joy on the phone tonight for about 20 minutes.  The state is getting ready to release their state-wide address dataset!  She wanted to have it done by October, but other projects came up.  They are shooting for some time in December.  She told me to check the Washington State Data Bridge and just be a little patient (http://geo.wa.gov/)
Cheers!

Closing comment (2016-12-13T21:24:24Z): @justinelliotmeyers I think this work is a duplicate of #2185? Can you confirm, and if so please close.
Repository: openaddresses/openaddresses

Issue #2650: Cuyahoga County, Ohio
Created: 2017-03-05T17:00:20Z
Cuyahoga County (Cleveland, Ohio) has parcel and address data via their GIS Esri System: http://myplace.cuyahogacounty.us/
I did not see any source within ohio (oh).

Duplicate issue #3634: Cuyahoga County, OH
Created: 2017-11-15T14:29:28Z
http://cuyahoga.maps.arcgis.com/home/item.html?id=a0d90f4c3b60495aa53f18db0dfd9071
contacted here: http://gis.cuyahogacounty.us/en-US/GIS-Data.aspx
to make sure license/ TOU align with OA

Closing comment (2017-12-22T16:36:09Z): dupe of #2650 ;)
Repository: openapi-ts/openapi-typescript

Issue #1410: openapi-fetch sends `Content-Type: application/json` header on GET requests
Created: 2023-10-26T12:22:54Z
Description
When sending GET requests with openapi-fetch, a Content-Type: application/json header is always included, even though GET requests should not have a body.
This causes problems in my case when talking to an ASP.NET API, which (nonsensically) tries to parse the non-existent GET body as JSON with the header present, fails, and then returns a 400. When the header is omitted or set to text/plain, everything works fine.
Reproduction
Generate a client schema from a Swagger JSON with a GET request. Then use said get request and observe that a Content-Type: application/json header is sent.
Expected result
The header should not be included.
Checklist

 I’m willing to open a PR (see CONTRIBUTING.md)

Duplicate issue #1431: There seems to be an issue when including credentials
Created: 2023-11-08T03:24:49Z
Description
When setting credentials: 'include' the api call does not get made. It gives a CORS error, but its not even hitting the server

I tested this both on the same domain as another API, and a different one. This DOES work when using fetch so there's an issue somewhere.
Reproduction
I can throw up a repo, try commenting the credentials: 'include' part in the lib/api/index.ts
https://github.com/amritk/-example-openapi-fetch-react-query
Expected result
The call gets made and succeeds or fails
Checklist

 I’m willing to open a PR (see CONTRIBUTING.md)

I will look into the code and see if I can find the issue

Closing comment (2023-11-08T05:06:02Z): Well looks like it was a duplicate of #1410, just had to pass
'Content-Type': null,
Repository: openapi-ts/openapi-typescript

Issue #1845: Wrong type in openapi-react-query when using select to transform data
Created: 2024-08-13T13:18:54Z
Mind: This is a bug in openapi-react-query. There is no template for opening Bugs for the openapi-react-query package yet.
Description
The select transformer in the queryOptions of the useQuery method expects a value of type data as return value. The value should be transformable to an arbitrary value (and be inherited correctly). Example:
Cool:
$api.useQuery('get', '/pets/person', {},
  {
    select: (data) => data,
  }
);
Not cool:
$api.useQuery('get', '/pets/person', {},
  {
    select: (data) => data.age, // or any other value
  }
);
Reproduction
See the implementation at the bottom of fetchClient.ts in this  Stackblitz.
Expected result
Arbitrary return values in the select method do not throw type errors. Furthermore, data should infer the type of the returned value of the select method (if set):
const { data } = $api.useQuery('get', '/pets/person', {},
  {
    select: (data) => data.age, // this shouldn't throw any type errors
  }
);

const str: number | undefined = data; // this shouldn't throw any type errors either as date.age is of type number and optional.

Duplicate issue #1949: openapi-react-query select option does not infer types correctly
Created: 2024-10-16T13:12:27Z
Description
The select property of the query options does not infer the type correctly.
Reproduction
Simply return a different type from the select call.
Example:
const { data: firstUser } = QAPI.useQuery(
    "get",
    "/api/users", // endpoint usually returns an array of users, e.g. User[]
    {},
    {
      select: (data) => data[0], // want to return something different here, i.e. User
    },
  );
In this case you get an error from the compiler stating Type User is not assignable to type User[] ...
Expected result
Type inference just works.
Checklist

 I’m willing to open a PR (see CONTRIBUTING.md)

Closing comment (2024-12-19T10:14:32Z): Closing as duplicate of #1845
Repository: openapi-ts/openapi-typescript

Issue #1828: openapi-react-query: support for useInfiniteQuery()
Created: 2024-08-07T20:40:13Z
@kerwanp I think it would be useful to support useInfiniteQuery().
If you agree, can I work on it?

Duplicate issue #2077: Support for infiniteQueryOptions and useSuspenseInfiniteQuery
Created: 2025-01-02T01:20:06Z
Hello,
First of all, thank you for developing the open-source project based on OpenAPI.
While using it recently, I noticed that infiniteQueryOptions and useSuspenseInfiniteQuery are not yet supported, which was disappointing.
If you are not currently working on these features, I would like to contribute to their implementation.
I would appreciate your feedback.
Happy New Year!

Closing comment (2025-01-04T02:00:08Z): Oh shoot I forgot there was an open PR already (I could have sworn someone had mentioned it, but neither came up in search 😅)
Since there’s already an issue, I’ll close as a duplicate of #1828