sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: Java bindings dlls files in jars not working for runnable jars in eclipse
Labels: feature,category: build/install,category: java bindings

### System Information

opencv 4.10.0
win11 java openjdk 22
eclipse ide for java 2024-06

### Detailed description

there are no jar files that encapsulate native dll files loading for jar-in-jar runnable jar loading in eclipse.
even if you put the dll files inside the runnable jar, they are not loaded. if the dll file is next to the jar, it will load.
goal is to have an independent fat runnable jar file including all jars and native dlls.
refer to example of lwjgl of native dll etc files encapsulation into jar files.

### Steps to reproduce

export a working running java opencv project in eclipse as runnable jar (modules or classpath).
try to make the runnable jar working by copying the native dlls into the jar root.

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: godot
Issue: TileMapLayers are emitting `changed()` signal after get_tree().quit() is called.
Labels: bug,topic:2d

### Tested versions

v4.3.stable.arch_linux

### System information

Godot v4.3.stable unknown - Arch Linux #1 SMP PREEMPT_DYNAMIC Tue, 10 Sep 2024 14:37:32 +0000 - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3090 (nvidia; 560.35.03) - AMD Ryzen 7 5800X 8-Core Processor (16 Threads)

### Issue description

When `get_tree().quit()` is called, `TileMapLayer` nodes emit their `changed()` signal after their `TileSet` has been removed from the scene tree. This means that code connected to the changed signal that tries to access properties on the `TileSet` will error for trying to access properties on a null value.

This behaviour is not present on TileMaps in previous versions of Godot (confirmed in 4.2).

### Steps to reproduce

1. Create a `TileMapLayer` with a `TileSet`.
2. Connect a script to the `TileMapLayer` `changed()` signal that accesses `tile_set.tile_size`
3. Call `get_tree().quit()` or close game via the OS close button on the window.
4. Game hangs due to trying to access `tile_set` on a null object.

### Minimal reproduction project (MRP)

See above steps.

I have shared a minimal reproduction project for triggering this issue while using PhantomCamera here: https://github.com/Jack-023/phantom-camera-error-repro
This was set up before determining that this is a Godot issue so it is not technically minimal in the context of Godot but it does demonstrate the issue.
Repository: tensorflow
Issue: An `aborted issue` could be raised in TensorFlow when I used API `math_ops.cast` and `array_ops.split`
Labels: stat:awaiting tensorflower,type:bug,comp:ops,2.17

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

tf-nightly 2.18.0.dev20240817

### Custom code

Yes

### OS platform and distribution

Ubuntu 20.04.3 LTS (x86_64)

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

 An `aborted issue`  could be raised in TensorFlow when I used API `math_ops.cast` and `array_ops.split` . 

### Standalone code to reproduce the issue

```shell
import numpy as np

from tensorflow.python.framework import dtypes
from tensorflow.python.ops import array_ops
from tensorflow.python.ops import math_ops
import tensorflow as tf

tf.compat.v1.disable_eager_execution()
sess = tf.compat.v1.Session()
with sess.as_default():
    a = math_ops.cast([2], dtypes.int32)
    b = math_ops.cast([1], dtypes.int32)
    value = np.random.rand(11, 11)
    array_ops.split(value, [a, b])
```


### Relevant log output

```shell
2024-09-12 15:49:03.711972: F tensorflow/core/framework/tensor_shape.cc:45] Check failed: NDIMS == dims() (1 vs. 2)Asking for tensor of 1 dimensions from a tensor of 2 dimensions
Aborted (core dumped)
```
Repository: tensorflow
Issue: Got one aborted issue when using `data_flow_ops.MapStagingArea` 
Labels: stat:awaiting tensorflower,type:bug,comp:ops,2.17

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

tf-nightly 2.18.0.dev20240817

### Custom code

Yes

### OS platform and distribution

Ubuntu 20.04.3 LTS (x86_64)

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

 An `aborted issue`  could be raised in TensorFlow when I used API `data_flow_ops.MapStagingArea`. The code is as follows:

### Standalone code to reproduce the issue

```shell
from tensorflow.python.framework import dtypes
from tensorflow.python.framework import ops
from tensorflow.python.ops import array_ops
from tensorflow.python.ops import data_flow_ops
from tensorflow.python.ops import math_ops
from tensorflow.python.platform import test
import tensorflow as tf


with ops.Graph().as_default() as g:
    with ops.device('/cpu:0'):
        x = array_ops.placeholder(dtypes.float32)
        pi = array_ops.placeholder(dtypes.int64)
        gi = array_ops.placeholder(dtypes.int64)
        v = 2.0 * (array_ops.zeros([]) + x)
    with ops.device(test.gpu_device_name()):
        stager = data_flow_ops.MapStagingArea([dtypes.float32])
        stage = stager.put(pi, [v], [0])
        k, y = stager.get([])
        y = math_ops.reduce_max(math_ops.matmul(y, y))
g.finalize()
with tf.compat.v1.Session(graph=g) as sess:
    sess.run(stage, feed_dict={x: -1, pi: 0})
    for i in range(10):
        _, yval = sess.run([stage, y], feed_dict={x: i, pi: i + 1, gi: i})
```


### Relevant log output

```shell
2024-09-12 15:57:44.445189: F tensorflow/core/framework/tensor.cc:852] Check failed: 1 == NumElements() (1 vs. 0)Must have a one element tensor
Aborted (core dumped)
```
Repository: tensorflow
Issue: Using `gen_random_index_shuffle_ops.random_index_shuffle` with `rounds=-2` can cause a crash
Labels: stat:awaiting tensorflower,type:bug,comp:ops,2.17

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

tf-nightly 2.18.0.dev20240817

### Custom code

Yes

### OS platform and distribution

Ubuntu 20.04.3 LTS (x86_64)

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

 A `Segmentation fault`  could be raised in TensorFlow when I used API `gen_random_index_shuffle_ops.random_index_shuffle` with `rounds=-2`. The code is as follows:

### Standalone code to reproduce the issue

```shell
from tensorflow.python.framework import dtypes
from tensorflow.python.ops import gen_random_index_shuffle_ops
from tensorflow.python.ops import math_ops

seed = (74, 117)
seed_dtype = dtypes.int32
max_index = 129
index_dtype = dtypes.int32
rounds = 4

seen = (max_index + 1) * [False]
seed = math_ops.cast([seed[0], seed[1], 42], seed_dtype)
for index in range(max_index + 1):
    new_index = gen_random_index_shuffle_ops.random_index_shuffle(math_ops.cast(index, index_dtype), seed, max_index=math_ops.cast(max_index, index_dtype), rounds=rounds)
    # rounds = -2 causes the segmentfault
    new_index = gen_random_index_shuffle_ops.random_index_shuffle(math_ops.cast(index, index_dtype), seed, max_index=math_ops.cast(max_index, index_dtype), rounds=-2)
```


### Relevant log output

```shell
> Segmentation fault (core dumped)
```
Repository: TypeScript
Issue: Generators can return undefined values
Labels: Needs Investigation

## Summary

Should the return type of `yield* a` be `TReturn | undefined` when in strict mode as opposed to `TReturn` (where `TReturn` is the value of the `TReturn` type argument to `a`'s `Iterable` type instantiation)?

Or should the type of `IteratorReturnResult.value` be changed to `TReturn | undefined` when in strict mode (and potentially the type of `Generator.return(value: TReturn)` be relaxed to `Generator.return(value?: TReturn)`)?

Have you considered these scenarios? (A github microsoft site search for "generator return undefined" yields no results).

## Background

Generators will return `undefined` values when:

1) `next()` is called after the generator has already returned its return value:

```TypeScript
function* gen(): Generator<number, string> {
    yield 42;
    return "done";
}

const a = gen();

console.log(a.next()); // { value: 42, done: false }
console.log(a.next()); // { value: 'done', done: true }
console.log(a.next()); // { value: undefined, done: true }
```

2.1) the generator is interrupted via a `break` statement of `for-of` loop on the generator

```TypeScript
const nestedIterableIterator: IterableIterator<string, string, unknown> = {
    [Symbol.iterator]() { return this; },

    next() {
        return { value: "42", done: false }
    },

    return(value: string) {
        console.log("return called with", value);
        return { value, done: true }
    }
}

function* generator() {
    yield* nestedIterableIterator;
    return "never";
}

const it = generator();

it.next();
it.return("passthrough"); // return called with passthrough

for (const x of generator()) {
    break; // return called with undefined
}
```

2.2) the generator is manually interrupted by calling its `return` method without arguments:

```TypeScript
function* gen(): Generator<number, string> {
    yield 42;
    yield 43;
    return "done";
}

const a = gen();

console.log(a.next()); // { value: 42, done: false }
console.log(a.return(undefined as unknown as string)); // { value: undefined, done: true }
console.log(a.next()); // { value: undefined, done: true }
```

3) The generator is attempted to be iterated over using `yield*` after it has already returned:

```TypeScript
function* gen(): Generator<number, string> {
    return "done";
}

function* consumer() {
    const a = gen();

    console.log(yield* a); // done
    console.log(yield* a); // undefined
}

consumer().next();
```

## Effect

The type signature of `Generator.return` guards against 2.2, and there is no way to get the return value from a `for-of` loop.

That leaves scenarios 1 and 3, of which 1 is likely uncommon, 3 is probably the only viable scenario and only in the case of user error...

### ⚙ Compilation target

ES2015

### ⚙ Library

lib.es2015.generator.d.ts

### Missing / Incorrect Definition

`Generator.return` and `IteratorReturnResult.value`

### Sample Code

See above.

### Documentation Link

No relevant documentation.
Repository: tensorflow
Issue: Using `fft_ops`  would cause an `aborted issue`
Labels: stat:awaiting tensorflower,type:bug,comp:ops,2.17

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

tf-nightly 2.18.0.dev20240817

### Custom code

Yes

### OS platform and distribution

Ubuntu 20.04.3 LTS (x86_64)

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

 An `aborted issue`  could be raised in TensorFlow when using `fft_ops`. The code is as follows:

### Standalone code to reproduce the issue

```shell
import numpy as np
from tensorflow.python.ops.signal import fft_ops
import tensorflow as tf
tf.compat.v1.disable_eager_execution()


def _tf_ifft(x, rank, fft_length=None, feed_dict=None):
    with tf.compat.v1.Session() as sess:
        return sess.run(_tf_ifft_for_rank(rank)(x, fft_length), feed_dict=feed_dict)

def _tf_ifft_for_rank(rank):
    if rank == 1:
        return fft_ops.irfft
    elif rank == 2:
        return fft_ops.irfft2d
    elif rank == 3:
        return fft_ops.irfft3d
    else:
        raise ValueError('invalid rank')


rank = 1
extra_dims = 0
np_rtype = np.float32
np_ctype = np.complex64
dims = rank + extra_dims
x = np.zeros((1,) * dims).astype(np_ctype)
tmp_var22 = _tf_ifft(x, rank).shape
```


### Relevant log output

```shell
DUCC FFT c2r failed:
bazel-out/k8-opt/bin/external/ducc/_virtual_includes/fft/ducc/src/ducc0/fft/fft1d_impl.h: 2948 (static Trpass<Tfs> ducc0::detail_fft::rfftpass<float>::make_pass(size_t, size_t, size_t, const Troots<Tfs> &, bool) [Tfs = float]):

Assertion failure
no zero-sized FFTs

Aborted (core dumped)
```
Repository: tensorflow
Issue: `tf_cond.cond` and `tf.function` could cause an aborted issue
Labels: stat:awaiting tensorflower,type:bug,comp:ops,2.17

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

tf-nightly 2.18.0.dev20240817

### Custom code

Yes

### OS platform and distribution

Ubuntu 20.04.3 LTS (x86_64)

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

 An `aborted issue`  could be raised in TensorFlow when using `tf_cond.cond` and `tf.function`. The code is as follows:

### Standalone code to reproduce the issue

```shell
from tensorflow.python.framework import constant_op
from tensorflow.python.framework import ops
from tensorflow.python.ops import cond as tf_cond
from tensorflow.python.ops import control_flow_assert
from tensorflow.python.ops import control_flow_ops
from tensorflow.python.platform import test

import tensorflow as tf
sess = tf.compat.v1.Session()

@tf.function
def func1():
    with sess.as_default():
        with ops.device(test.gpu_device_name()):
            pred = constant_op.constant([True, False])

        def fn1():
            return control_flow_ops.no_op()

        def fn2():
            with ops.device('/cpu:0'):
                return control_flow_assert.Assert(False, ['Wrong!'])

        r = tf_cond.cond(pred, fn1, fn2)

func1()
```


### Relevant log output

```shell
> 2024-09-12 16:43:14.634438: F tensorflow/core/framework/tensor.cc:852] Check failed: 1 == NumElements() (1 vs. 2)Must have a one element tensor
> Aborted (core dumped)
```
Repository: TypeScript
Issue: Inconsistent behaviour of `-?`
Labels: Bug,Help Wanted

### 🔎 Search Terms

optional mapped type

### 🕗 Version & Regression Information

- This changed between versions 5.4.5 and 5.5.4


### ⏯ Playground Link

https://www.typescriptlang.org/play/?exactOptionalPropertyTypes=true#code/C4TwDgpgBA8mwEsD2A7AhgGwCpIKouRQHUFgALfAEwgDMEUJKAeLAPigF4oBvAKCgFQA2gGko9KAGsIIJDShYAugC4FUCAA9gEFJQDOUAEoQAxkgBOzEQBoFoxa36DnAfjsjFT5wNVZ7UAB8oAFddWnpGXgBfXl5QSCgASRRtcwBbBEoENG1OWHhCTBx8QhJyKnCGZm4oNBdVPWBzegBzKCj2AHpOnlr6qEbmlDag0Oo6Kva48GgAGVIIc0w8mrqGptbAkLCJxnaoboG0NOh46DQDZNSMrJyIWLOjCD0ARjzjAEdghHNGJivFjdstouj1Vushm0Yo9jHoAEzvCBfH5-eapTCg3poCGbUY7CKUdpAA

### 💻 Code

```ts
type OptionalToUnionWithUndefined<T> = {
    [K in keyof T]: T extends Record<K, T[K]>
        ? T[K]
        : T[K] | undefined
}

type Intermidiate = OptionalToUnionWithUndefined<{ a?: string }> // { a?: string | undefined }
type Literal = { a?: string | undefined } // same type as Intermidiate

type Res1 = Required<Intermidiate> // { a: string }
type Res2 = Required<Literal> // { a: string | undefined }
```


### 🙁 Actual behavior

`Res1` and `Res2` are different types

### 🙂 Expected behavior

they should be the same because the inputs are

### Additional information about the issue

This issue may share the cause with #59902
Repository: ant-design
Issue: Menu item divider 的 borderTopWidth 和 marginBlock的css属性公用一个变量，不能单独设置
Labels: Inactive

### What problem does this feature solve?

Mnut Item Divider可以设置相关css，marginBlock属性1px，如果设置lineWidth: 0，那么margin和border就没有了
![image](https://private-user-images.githubusercontent.com/49859450/366799156-29f1e0b9-2d5d-4226-989f-5d360c9b49c6.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYxMzI1MDYsIm5iZiI6MTcyNjEzMjIwNiwicGF0aCI6Ii80OTg1OTQ1MC8zNjY3OTkxNTYtMjlmMWUwYjktMmQ1ZC00MjI2LTk4OWYtNWQzNjBjOWI0OWM2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTEyVDA5MTAwNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc4YTA1ZWY1ODE4YjA5NzA1MTZmNzEzYTQ3ZDlmYWE0NGJmMThjYTMzOTU5OGU5NjUzYzM3OWVhN2VjNmRiMDkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.I-YJfbiSgqqrYHclG7P20SJS7ja8vt0__hh0_B_8wU0)


### What does the proposed API look like?

[menu/style/index.ts#L666-L667](https://github.com/ant-design/ant-design/blob/22fb6f67fa10e3cdc0e382c5e73869846e67de02/components/menu/style/index.ts#L666-L667)

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: Decoration Ranges are not always adjusted immediately
Labels: bug,papercut :drop_of_blood:

The strike through was applied to the previous decoration:

![Image](https://github.com/user-attachments/assets/f8f31e1f-d021-4886-8e72-002e65d78d4d)

Here the buggy frame:

![Image](https://github.com/user-attachments/assets/82d24d01-5f36-4d32-a295-f6d66464ccb7)

I replaced the line
```ts
import { ColumnRange, applyObservableDecorations } from '../../inlineCompletions/browser/utils.js';
```
with
```ts
import { ColumnRange } from '../../inlineCompletions/browser/utils.js';
```

@mattbierner @alexdima do you have ideas?
Repository: bitcoin
Issue: cmake: adjust Find modules to try `find_package` & fallback to `pkg_check_modules`
Labels: Build system

See the discussion in: https://github.com/bitcoin/bitcoin/pull/30803#discussion_r1743507523.

> I assume one thing we could do, is try find_package(ZeroMQ) first, and fallback to pkg_check_modules(libzmq), and just maintain this (pretty much) forever. That might be better than somewhat vauge comments about "modern" distros, because, (some) modern distros do already support this, and it's actually the case that all versions of all distros Bitcoin Core supports need to do this, before we could do a complete switch.
Repository: PowerToys
Issue: cannot uninstall after installed DetectedPowerToysUserVersion=0.74.1.0 and DetectedPowerToysVersion=0.82.1.0
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.74.1.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Installer

### Steps to reproduce

1. install DetectedPowerToysUserVersion=0.74.1.0
2. install DetectedPowerToysVersion=0.82.1.0
3. install a newer version of "0.84.1" or try in uninstall 0.74 or 0.82 with those install exec.

### ✔️ Expected Behavior

upgrade successfully or uninstall successfully 

### ❌ Actual Behavior

setup failed
[powertoys-bootstrapper-msi-0.82.1_20240912171930.log](https://github.com/user-attachments/files/16976852/powertoys-bootstrapper-msi-0.82.1_20240912171930.log)
![powertoys_setup_failed](https://github.com/user-attachments/assets/2ae181ed-0e7e-47d2-8cbf-e67fc01679f6)



### Other Software

_No response_
Repository: material-ui
Issue: [docs] MUI-X pages give 404 in v5 docs
Labels: scope: docs-infra,support: docs-feedback

### Related page

https://v5.mui.com/x/react-date-pickers/

### Kind of issue

Other

### Issue description

If you go to https://v5.mui.com/material-ui/getting-started/ and click one of the MUI-X links on the sidebar, it shows a 404 error.

![image (1)](https://github.com/user-attachments/assets/1667dde8-2b81-489c-8b98-b4c97017de58)

User report on discord: https://discord.com/channels/1131323012554174485/1131329150070816868/1283709072901804032

### Context

_No response_

**Search keywords**: none
Repository: tauri
Issue: [feat] Listen to keyboard layout changes
Labels: type: feature request

### Describe the problem

Be able to listen to keyboard layout changes in a cross-platform way. This is useful for apps that depend on the current layout for localization or accessibility.

Tao already listens to keyboard layout changes on Windows and MacOS, but doesn't expose them via a public API (ref [Windows](https://github.com/tauri-apps/tao/blob/ad652e50bfca1195481cd347ccaa486818f9334d/src/platform_impl/windows/event.rs#L135), [MacOS](https://github.com/tauri-apps/tao/blob/ad652e50bfca1195481cd347ccaa486818f9334d/src/platform_impl/macos/event.rs#L79)).

On Windows, it's particularly annoying to hook into keyboard layout changes (e.g. `WM_INPUTLANGCHANGE` is only broadcast to windows _if they're focused_), and creating a secondary keyboard hook to listen to these changes is expensive.

### Describe the solution you'd like

Expose a keyboard layout change event

### Alternatives considered

_No response_

### Additional context

_No response_
Repository: ollama
Issue: ROCm 6.2 upgrade?
Labels: feature request,amd

Would it be possible to upgrade from 6.1.2 -> 6.2 for rocm?

It has [improved vLLM support](https://rocm.docs.amd.com/en/docs-6.2.0/about/release-notes.html#improved-vllm-support), which I assume would be advantageous for ollama.

Thx
Repository: TypeScript
Issue: TS 5.6 requires composite projects with noEmit to have fully accessible types, unlike 5.5
Labels: Needs Investigation

### 🔎 Search Terms

TS2742, TS7056, TS9006, TS4058, TS4023, noEmit, composite, 5.6

### 🕗 Version & Regression Information

- This changed between versions 5.5.4 and 5.6.2

### ⏯ Playground Link

https://github.com/Ambroos/ts-56-composite-project-noemit

### 💻 Code

file: **Internal.ts**
```ts
interface Internal {
    a: boolean,
}

export default function somethingInternal() {
    return {
        one: { a: true } as Internal,
    };
}
```

file: **index.ts**
```ts
import createInternal from "./Internal";
export const one = createInternal().one;
```

file: **tsconfig.json**
```json
{
    "compilerOptions": {
        "composite": true,
        "noEmit": true,
        "strict": true,
    },
    "include": [
        "*.ts"
    ]
}
```


### 🙁 Actual behavior

In TS 5.6.2, run `tsc` and get error:

```
index.ts:3:14 - error TS4023: Exported variable 'one' has or is using name 'Internal' from external module "/Users/ambroos/Dev/ts-composite-5.6/Internal" but cannot be named.

3 export const one = createInternal().one;
```

This is the error in the sample project linked above (or created with the files from the code part). In our actual repo a large amount of new errors appeared that are related: TS2742, TS7056, TS9006, TS4058, TS4023.

### 🙂 Expected behavior

No errors, like 5.5.4 and older.

### Additional information about the issue

This only happens in composite projects, even when not using `--build`. We have a large composite project, but the oldest parts of our code live in projects that don't emit since no-one is allowed to depend on them (they're apps that get built as-is).

In the past, when not emitting type declarations, it was OK to reference types that cannot be named, even in incremental compilation / composite projects. Now however it looks like because `.tsbuildinfo` is always generated, making code able to be emitted seems to have become required.

Maybe this is intentional, but it would be nice to still have some escape hatch for these types of composite project parts that don't actually need to emit declarations, they just need to be checked and transpiled.