sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [core] Adopt eslint-plugin-react-compiler
Labels: performance,core,scope: code-infra

### Context

The [React Compiler](https://react.dev/learn/react-compiler) optimizes code that follows the rules of React. In order to make it easier to write React compliant code, the React team released an ESLint plugin that reports broken React rules: [eslint-plugin-react-compiler](https://react.dev/learn/react-compiler#installing-eslint-plugin-react-compiler).

The compiler requires React 19, but the ESLint plugin can be adopted earlier to be prepared.

### Motivation

- Follow the rules of React in our code so it can be optimized by the React compiler in the future.
- Follow React best practices in all of our demos that our consumers use.

Note: at the time of writing the ESLint is experimental but it has proven to be [useful](https://github.com/mui/mui-toolpad/pull/3562) for the Toolpad team.

### Tasks

- [x] Configure the ESLint plugin. Only activate locally and manually while it's experimental (https://github.com/mui/material-ui/pull/42555)
- [x] Disable the ESLint plugin for Base (#42563)
- [ ] #42564

**Search keywords**: react compiler, eslint
Repository: vscode
Issue: feature request: open file url without --file-uri flag
Labels: feature-request,workbench-cli

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Open file URLs like `code file:///path` instead of `code --file-uri file:///path`

see #213215
Repository: PowerToys
Issue: Advanced Paster error when using text from a Word File with "Title" style 
Labels: Issue-Bug,Priority-3,Product-Advanced Paste

### Microsoft PowerToys version

0.81.1

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

Advanced Paste

### Steps to reproduce

1. open a MS Word file
2. create a text (e.g. TEXT) with a Title style and copy it
3. paste as markdown in a text editor (e.g., VScode)

### ✔️ Expected Behavior

It should paste the lines:

```
TEXT
===
```

### ❌ Actual Behavior

It currently pastes the lines:

```
TEXT
 <![if !supportLineBreakNewLine]>  
 <![endif]>
```

### Other Software

_No response_
Repository: terminal
Issue: alternate scroll mode breaks ctrl-mousewheel zoom
Labels: Area-Input,Issue-Bug,Product-Terminal,Priority-3

### Windows Terminal version

1.21.1272.0

### Windows build number

10.0.22631.0

### Other Software

nano 6.0
any app that supports alternatve scroll mode

### Steps to reproduce

Run any app that supports alternatve scroll mode
Try to zoom with ctrl+mousewheel

### Expected Behavior

Zooming

### Actual Behavior

Text cursor moves like there is no ctrl pressed

It has always been there (I checked 1.17.11461.0 with `printf "\e[?1007h"` to enable the mode), but after the recent update, alternate scroll mode is enabled by default, conviniently alongside with forced updates and no settings to roll back breaking changes exposed.

The workaround is to add `printf "\e[?1007l"` to ~/.bashrc or to use ctrl+/ctrl- to zoom.
Repository: flutter
Issue: [Feature Request] Add `waitDuration` to `InkWell`
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design,:hourglass_flowing_sand:

### Use case

Like `Tooltip`, we want to config the `hoverWaitTime`.

### Proposal

Is better to add by Flutter.
Repository: node
Issue: Inaccurate windows stacktrace printer
Labels: windows

### Version

v20.11.1

### Platform

Microsoft Windows NT 10.0.19045.0 x64

### Subsystem

debug util

### What steps will reproduce the bug?

One line quick reproduction:

```sh
$ node --max-heap-size=10 -e 'var idx = 0; while (true) {global[idx++] = new Array(10_000_000) }'
```

### How often does it reproduce? Is there a required condition?

Always

### What is the expected behavior? Why is that the expected behavior?

Expected stack trace:

``` 
 1: 00007FF73361E1CB node::DumpNativeBacktrace+155 [D:\dev\nodejs\node\src\debug_utils.cc]:L322
 2: 00007FF733554C24 node::OOMErrorHandler+324 [D:\dev\nodejs\node\src\node_errors.cc]:L621
 3: 00007FF73483A5D1 v8::Utils::ReportOOMFailure+33 [D:\dev\nodejs\node\deps\v8\src\api\api.cc]:L350
 4: 00007FF734821E96 v8::internal::V8::FatalProcessOutOfMemory+694 [D:\dev\nodejs\node\deps\v8\src\api\api.cc]:L302
 5: 00007FF7345952B0 v8::internal::Heap::FatalProcessOutOfMemory+32 [D:\dev\nodejs\node\deps\v8\src\heap\heap.cc]:L6314
 6: 00007FF734590CFD v8::internal::Heap::CollectGarbage+1229 [D:\dev\nodejs\node\deps\v8\src\heap\heap.cc]:L1967
 7: 00007FF7345AFEC4 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath+2084 [D:\dev\nodejs\node\deps\v8\src\heap\heap-allocator.cc]:L108
 8: 00007FF7345B0B5A v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath+90 [D:\dev\nodejs\node\deps\v8\src\heap\heap-allocator.cc]:L124
 9: 00007FF7345C092D v8::internal::Factory::AllocateRaw+541 [D:\dev\nodejs\node\deps\v8\src\heap\factory.cc]:L284
10: 00007FF7345DDA1C v8::internal::FactoryBase<v8::internal::Factory>::NewFixedArray+108 [D:\dev\nodejs\node\deps\v8\src\heap\factory-base.cc]:L172
```

### What do you see instead?

Actual stack trace:

```
 1: 00007FF73D0971AB node::SetCppgcReference+16075
 2: 00007FF73D00DCC6 v8::base::CPU::num_virtual_address_bits+79190
 3: 00007FF73D00FED5 v8::base::CPU::num_virtual_address_bits+87909
 4: 00007FF73DA7F061 v8::Isolate::ReportExternalAllocationLimitReached+65
 5: 00007FF73DA687F8 v8::Function::Experimental_IsNopFunction+1336
 6: 00007FF73D8CA120 v8::Platform::SystemClockTimeMillis+659328
 7: 00007FF73D8C71A8 v8::Platform::SystemClockTimeMillis+647176
 8: 00007FF73D8DC4BA v8::Platform::SystemClockTimeMillis+733978
 9: 00007FF73D8DCD37 v8::Platform::SystemClockTimeMillis+736151
10: 00007FF73D8E596E v8::Platform::SystemClockTimeMillis+772046
```

### Additional information

Only reproducible on Windows release build downloaded from https://nodejs.org/download/ and https://nodejs.org/dist/. Local `.\vcbuild.bat` build can output correct stacktrace.

This is not related to https://github.com/nodejs/node/pull/50849 since that only released in `v20.12.0`. This problem can reproduce on v20.11.1 and previous versions.

/cc @joyeecheung
Repository: ant-design
Issue: Ability to have an icon inside progress bar line
Labels: help wanted,💡 Feature Request,Inactive

### What problem does this feature solve?

I want to show a progress bar with a plane icon going from left to right, to indicate that the progress bar movement is tied to plane movement. Having the ability to put an SVG icon inside the progress bar line would enable this use case.
![image](https://github.com/ant-design/ant-design/assets/615386/44b2a701-4ea2-4b54-92d2-91cba82ceb11)


### What does the proposed API look like?

for type="line" add a icon prop that can be optionally be shown at the tail end of the progress bar  inside the progress bar.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: ui
Issue: [bug]: Error while switching to V0 in Lift Mode 
Labels: bug

### Describe the bug

### Showing an error json when switched to V0 in Lift Mode under the Blocks section of the website.
<img width="420" alt="Screenshot 2024-06-06 at 19 08 59" src="https://github.com/shadcn-ui/ui/assets/141031946/31dfdf5b-e13c-4b03-a2fd-8f3eaf6e2a55">


### Affected component/components

Button

### How to reproduce

1. Visit https://ui.shadcn.com/blocks#authentication-01
2. Toggle **Lift Mode**  
3. Hover over any component
4. Click the _V0_ button

<img width="1389" alt="Screenshot 2024-06-06 at 19 19 20" src="https://github.com/shadcn-ui/ui/assets/141031946/a523835a-a28d-4bbe-8e96-45a24b51ca57">


### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Browser : Arc
System : macOS Sonoma 14.5
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: PowerToys
Issue: MWB sudden CTRL, SHIFT or ALT stay pressed after keyboard button relesaed
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

Mouse without Borders 2.2.1.327

### Installation method

Other (please specify in "Steps to Reproduce")

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

MWB was downloaded from Microsoft Garage (didn't find it in Installation methods). 
I'm using CTRL+SHIFT to change my keyboard layout. Sometimes after keyboard layout change one of keys (CTRL or SHIFT, I didn't find any regularity) stay pressed after physical buttons released. The key remains stucked until it's pressed again or MWB is exited (I'v checked it using on-screen keyboard). I'm using MWB for one year and ALT key stuck issue was only twice (I'm rarely using ALT key). CTRL or SHIFT stuck issue occurs 1-2 times a day.

### ✔️ Expected Behavior

CTRL, SHIFT or ALT key pressed only when physical key is pressed.

### ❌ Actual Behavior

When key stucked:
ALT - can't use other keys
SHIFT - yeah, all text is typed in CAPS
CTRL - the most harmful situation - typing text causes a lot of hotkey shortcuts execution...

### Other Software

_No response_
Repository: storybook
Issue: [Bug]: Storybook builds twice on launch
Labels: bug,performance issue,builder-webpack5,sev:S3

### Describe the bug

When starting Storybook (React latest + webpack 5 template) in a dev mode, build process runs twice before one can freely browse stories.
After some debugging it turned out that the second build is triggered by the file system watcher because of 'removal' of storybook-config-entry.js and storybook-stories.js files.
As I understood from the source code, these are only virtual modules that should not really exist as a separate physical files, so maybe they should be somehow excluded from the watch? I'm not quite sure how though 😅

![image](https://github.com/storybookjs/storybook/assets/84311537/26b584b4-d430-4186-b519-281e3a92104f)

This second build basically doubles Storybook launch time which for larger repos can be quite significant.

As a workaround, we created these files without any content but this is just a temporary solution.


### Reproduction link

It happens on the clean sandbox reproduction repo

### Reproduction steps

1. Create clean reproduction repo with React latest + webpack 5 template (I assume that webpack part might be mandatory in order to reproduce the issue, while the React is optional and the same could happen with other libraries)
2. Install packages and start storybook using standard commands
3. After seeing 'welcome box' (with Storybook version, timings and URLs), notice that the progress plugin prints some output once again (on the clean reproduction repo it's quite fast but as I mentioned before it is dependent on the size of the repo)

### System

```bash
System:
    OS: Windows 10 10.0.19045
    CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
  Binaries:
    Node: 20.11.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - C:\Program Files\nodejs\yarn.CMD <----- active
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.1.2 - C:\Program Files\nodejs\pnpm.CMD
  Browsers:
    Edge: Chromium (125.0.2535.67)
  npmPackages:
    @storybook/addon-essentials: ^8.2.0-alpha.5 => 8.2.0-alpha.5
    @storybook/addon-interactions: ^8.2.0-alpha.5 => 8.2.0-alpha.5
    @storybook/addon-links: ^8.2.0-alpha.5 => 8.2.0-alpha.5
    @storybook/addon-onboarding: ^8.2.0-alpha.5 => 8.2.0-alpha.5
    @storybook/addon-webpack5-compiler-swc: ^1.0.3 => 1.0.3
    @storybook/blocks: ^8.2.0-alpha.5 => 8.2.0-alpha.5
    @storybook/react: ^8.2.0-alpha.5 => 8.2.0-alpha.5
    @storybook/react-webpack5: ^8.2.0-alpha.5 => 8.2.0-alpha.5
    @storybook/test: ^8.2.0-alpha.5 => 8.2.0-alpha.5
    storybook: ^8.2.0-alpha.5 => 8.2.0-alpha.5
```


### Additional context

_No response_
Repository: langchain
Issue: DOCS: Split integrations/llm_cache page into separate pages
Labels: documentation,help wanted,🤖:docs

### Privileged issue

- [X] I am a LangChain maintainer, or was asked directly by a LangChain maintainer to create an issue here.

### Issue Content

https://python.langchain.com/v0.2/docs/integrations/llm_caching/ should be a section with one page per integration, like other components.
Repository: tensorflow
Issue: Crash in `tf.raw_ops.ResizeNearestNeighbor/ResizeNearestNeighborGrad/ResizeArea/ResizeBicubic/ResizeBilinear`
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.16

### Issue type

Bug

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

Yes

### Source

source

### TensorFlow version

TensorFlow Nightly

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu 22.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?

On specific input, these APIs will output "The session crashed because it took up all available RAM." The affected APIs are listed below:

1. tf.raw_ops.ResizeBilinear
2. tf.raw_ops.ResizeBicubic
3. tf.raw_ops.ResizeArea
4. tf.raw_ops.ResizeNearestNeighbor
5. tf.raw_ops.ResizeNearestNeighborGrad

### Standalone code to reproduce the issue

```shell
https://colab.research.google.com/drive/1a6B_lYMfENTbO4ifQMLYe8Hq6CHcc6hP?usp=sharing
```


### Relevant log output

```shell
Timestamp	Level	Message
Jun 6, 2024, 6:57:43 PM	WARNING	WARNING:root:kernel d0444564-3fb8-4d42-ac83-1338e6842d5a restarted
Jun 6, 2024, 6:57:43 PM	INFO	KernelRestarter: restarting kernel (1/5), keep random ports
Jun 6, 2024, 6:57:25 PM	WARNING	2024-06-06 10:57:25.421101: W external/local_tsl/tsl/framework/cpu_allocator_impl.cc:83] Allocation of 51536461872 exceeds 10% of free system memory.
Jun 6, 2024, 6:57:21 PM	WARNING	2024-06-06 10:57:21.507228: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
Jun 6, 2024, 6:57:17 PM	WARNING	To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
Jun 6, 2024, 6:57:17 PM	WARNING	2024-06-06 10:57:17.995922: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
Jun 6, 2024, 6:56:13 PM	WARNING	WARNING:root:kernel d0444564-3fb8-4d42-ac83-1338e6842d5a restarted
Jun 6, 2024, 6:56:13 PM	INFO	KernelRestarter: restarting kernel (1/5), keep random ports
Jun 6, 2024, 6:55:56 PM	WARNING	2024-06-06 10:55:56.764126: W external/local_tsl/tsl/framework/cpu_allocator_impl.cc:83] Allocation of 103072923744 exceeds 10% of free system memory.
Jun 6, 2024, 6:55:52 PM	WARNING	2024-06-06 10:55:52.277507: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
```
Repository: next.js
Issue: Symlinks issue, with tailwind especially
Labels: bug,Webpack,Pages Router

### Link to the code that reproduces this issue

https://github.com/ScreamZ/bug-tw

### To Reproduce

Launch the repository and follow the readme

### Current vs. Expected behavior

I've detailed everything in my original post for tailwind.

https://github.com/tailwindlabs/tailwindcss/issues/13731

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.0.0: Fri Sep 15 14:41:43 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 9.1.4
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: 14.2.3
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Developer Experience, Pages Router, Webpack

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Vercel (Deployed)

### Additional context

I've been experiencing issue with symlinking, which results in tailwind issues. Tailwind maintainer told me this is not related to tw but nextJS, as tailwind is shipped by default i guess this is a good idea to address this.
Repository: vscode
Issue: Investigate Editor Placeholder Adoption
Labels: debt,chat

The editor now supports proper placeholders and we should investigate where we can adopt them.

[Here is an example usage of the new placeholder API](https://microsoft.github.io/monaco-editor/playground.html?source=v0.50.0-dev-20240607#XQAAAAL1AQAAAAAAAABBqQkHQ5NjdMjwa-jY7SIQ9S7DNlzs5W-mwj0fe1ZCDRFc9ws9XQE0SJE1jc2VKxhaLFIw9vEWSxW3yscwzvVxRgmSaumWUF-TBOsVJ4S4FwfCDQb5-2uUHXTVAefbVSd9IzaZ_vv9VR9KugsKijNW9wsk3crkODGT74cZ3jecBB1snCLYAE_E-1hrsCO7URpa9D5nYVED3LkMI0ASDd-LMJMXqUEd9c6JdxpLLTPcnqdz9snZyaF9ZsrmjR9uboi2dGo6EBweN46PL9KFIh8RB1qZuJpa_Xpye5OCCxtKmLgdKcEQKm8T5PwMKydKoZpHXs80fyyeTXPZDi7asGoWGI8UC7Ef8ihB5MhunuEfu8LYYw9rMEgnjGEsIWTZ76zU2yhNugIHRSP4Qn3FGw0N48vxS6javNKXvr1pucfPL9708Tsvuydk4t5NXZ77Wd43PcMAui0pO_pBsmevNniwKfAKp_tsmEfQp2iU0nf9-Cob). 

* [x] @lszomoru https://github.com/microsoft/vscode/blob/2a3498d961675534434e0ad057587a584b5f459b/src/vs/workbench/contrib/scm/browser/scmViewPane.ts#L2341
* [ ] @roblourens https://github.com/microsoft/vscode/blob/2a3498d961675534434e0ad057587a584b5f459b/src/vs/workbench/contrib/chat/browser/contrib/chatInputEditorContrib.ts#L138
* [x] @alexr00 https://github.com/microsoft/vscode/blob/6125cc2332d2d21805f1887c7b944a81ffce423e/src/vs/workbench/contrib/comments/browser/commentReply.ts#L240

Known issue (will be fixed soon)
* https://github.com/microsoft/vscode/issues/211403
Repository: angular
Issue: Add info-level extended diagnostics
Labels: area: compiler

### Which @angular/* package(s) are relevant/related to the feature request?

compiler-cli

### Description

There could be defaulted compilation behavior that doesn't fall into error or warning categories, whereas still deserving a message.

One example potentially being what is suggested in https://github.com/angular/angular/issues/56305

### Proposed solution

Info-level extended diagnostic message support.

P.S.
That seems natural in the long run sooner or later...

### Alternatives considered

NA
Repository: TypeScript
Issue: Feature request: Override and extend callback argument
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

extend callback argument typescript

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

(Possibly a duplicate, but I couldn't find similar issue)
I often need to change type of a callback argument and it always takes an extra line to perform `as` assertions. I propose to add ability to use `as` keyword directly on the argument.

```ts
function withCallback(callback: (arg: { foo: string }) => void) {
  // ...
}

withCallback((arg) => {
  const { foo, bar } = arg as { foo: string; bar: string }; // always an extra line
  // ...
});
```

### 📃 Motivating Example

It would be nice to have a built-in TS feature that makes possible to do that in a shorter manner:

```ts
withCallback(({ foo, bar } as { foo: string; bar: string }) => {
  console.log(foo, bar);
});

// or
withCallback(({ foo, bar } as unknown as { foo: string; bar: string }) => {
  console.log(foo, bar);
});
```

Overriding the type completely isn't needed too often that's why I propose to also enrich this syntax with `extends` (or something more applicable) keyword:

```ts
withCallback(({ foo, bar } as extends { bar: string }) => {
  console.log(foo, bar);
});
```

Thinking thru it I think it would make sense to also add `as extends` for other often appearing use-cases:

```ts
const x = { foo: 'foo' };

const y = x as extends { bar: string };
// same as 
const y = x as typeof x & { bar: string };
```

`as extends T` at this syntax can be interpreted as `as typeof __SELF__ & T`


### 💻 Use Cases

There are million use-cases for this feature. Type assertions in TS are used more often than we might expect while learning it.
Repository: terminal
Issue: Deadlock when pasting >5 KiB into an application that doesn't read it fast enough
Labels: Issue-Bug,Area-TerminalConnection,Product-Terminal

### Windows Terminal version

1.20.11381.0

### Windows build number

10.0.19045.4412

### Other Software

WSL

### Steps to reproduce

1. Open a WSL tab under Windows Terminal (I've reproduced with Ubuntu 20.04 and RHEL 7 distros, though I assume this bug is independent of the chosen distro)
2. Paste this command to your shell, but don't run it yet:
    `python3 -c 'print("Paste now:"); import time; time.sleep(10)'`
3. Copy [the text of Frankenstein](https://raw.githubusercontent.com/asweigart/codebreaker/master/frankenstein.txt) to your clipboard
4. Run the `python3` command you pasted in step 2.
5. When the "Paste now:" message appears, paste the text of Frankenstein to your terminal, and say "paste anyway" at the dialog box.
6. The terminal deadlocks. The first 4096 bytes of Frankenstein appear in the terminal. It is no longer possible to Ctrl-C the python3 script.

### Expected Behavior

The terminal should remain responsive. Ctrl-C should work. The full pasted text should be displayed.

### Actual Behavior

Deadlock. I assume that what's happening here is that Windows Terminal is making blocking write() calls in its paste implementation. If the application doesn't read what's been pasted, or can't keep up, the terminal hangs and becomes totally unresponsive. This was discovered while investigating [an issue with the Python 3.13 REPL](https://github.com/python/cpython/issues/119517), but it appears to be a bug in Windows Terminal itself.
Repository: excalidraw
Issue: refresh share links: so past viewers don't have access
Labels: Excalidraw+

I wish there was a way to reset the share link; to invalidate the prior link and create a new one. Currently, I need to create a duplicate of the entire drawing if I want to restrict access to viewers.