sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue:  Import trace for requested module error even in new project
Labels: Upstream,create-next-app,bug,Navigation,Runtime

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/abdorabee/saas

### To Reproduce

Create a new Next.js project.
Run the development server.
Open the browser and navigate to the project's homepage.
You should see the error message "Import trace for requested module:" in the console.

### Current vs. Expected behavior

The project should start without any errors.

vs 

The project starts, but the error message "Import trace for requested module:" is displayed in the console.



### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 20.6.1
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.20-canary.26
      eslint-config-next: 13.4.19
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.2.2
    Next.js Config:
      output: N/A
```


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

App Router, CLI (create-next-app), Middleware / Edge (API routes, runtime), Operating System (Windows, MacOS, Linux), Package manager (npm, pnpm, Yarn), Routing (next/router, next/navigation, next/link)

### Additional context

I am getting the error "Import trace for requested module:" even in a new Next.js project that doesn't have any packages installed yet.
Repository: TypeScript
Issue: Certain conditional types allow unsound assignments
Labels: Bug,Help Wanted,Cursed?

### 🔎 Search Terms

"conditional type" generic assignment

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about conditional types

### ⏯ Playground Link

https://www.typescriptlang.org/play?#code/C4TwDgpgBAQg9gDwDwBUB8UC8UDeUBuAhgDYCuEAXFClAL4BQ9okUAqgHYBGiAku+xABOqDNhoQEwCOwAmAZ1iIkAS3YAzIVABKGAPxsuvfkKQ6oVPKUMIIMqjQbNoHbsnRYDrvgOHoA2gDkVq62AQC6jDIQAMbEhILQalbRwMpw7FDBSugAFAj2AJRULtlojEnsKWkZEoQAtmDEECJ5hbj0UFBNwFCEHlkIeQUdvR4BwAAWygpyE3CkxDJQnNCENYKCcIIB9LRAA

### 💻 Code

```ts
type Box<T> = { value: T }

type UnboxInner<T> = T extends Box<infer R> ? UnboxInner<R> : { unboxed: T }
type Unbox<T> = UnboxInner<T>['unboxed']

declare function unbox<T>(x: T): Unbox<T>

function example<T>(x: T) {
  let a = unbox(x)
  a = 'this should be an error'
}
```

### 🙁 Actual behavior

In `example` we can assign arbitrary values to `a`, even though it's typed as `Unbox<T>`.

### 🙂 Expected behavior

Attempting to assign invalid values to `a` (just about anything, since its type depends on a type parameter) should cause a type error.

### Additional information about the issue

These issues may possibly be related:
- #52021
- #35533

cc @webstrand
Repository: go
Issue: testing: TB.TempDir paths can be too long for Unix socket paths
Labels: Unfortunate,NeedsDecision


### What version of Go are you using (`go version`)?

Go 1.21
darwin/arm64

### What did you do?

I renamed a test to make it more descriptive (longer) and then my test failed:

```
    integration_test.go:879: sockFile path "/var/folders/0f/7sz95dc94nj46b6yz8p_fqd40000gn/T/TestIncrementalMapUpdatePeersRemoved1080118162/001/tailscale.sock" (len 114) is too long, must be < 104
```

Turns out darwin, openbsd, and freebsd at least limit the length of a unix socket to 104 bytes.

Because `os.TempDir` on darwin is a long user-specific thing (e.g. `/var/folders/0f/7sz95dc94nj46b6yz8p_fqd40000gn/`) and `testing.TB.TempDir` includes the test name and some suffix (`TestIncrementalMapUpdatePeersRemoved1080118162`), by the time those are all concatenated, you're out of space for a unix socket filename that fits in 104 bytes.

Apparently @josharian discovered this two years ago in https://github.com/tailscale/tailscale/commit/f80193fa4c3b0d5b2e5ed50cec0402cf5114a5fe where I approved a rename to make test names shorter but it didn't cross my mind to file this bug until I just hit it again now.

I ended up working around it by:

```go
	dir := t.TempDir()
	sockFile := filepath.Join(dir, "tailscale.sock")
	if len(sockFile) >= 104 {
		// Maximum length for a unix socket on darwin. Try something else.
		sockFile = filepath.Join(os.TempDir(), rands.HexString(8)+".sock")
		t.Cleanup(func() { os.Remove(sockFile) })
	}
```

But that's a little gross.

### What did you expect to see?

Operating systems to be less annoying. Failing that, maybe the testing package could help work around it somehow?

### What did you see instead?

Failure to make a unix socket in a test.
Repository: pytorch
Issue: Pytorch ROCM windows builds
Labels: module: windows,module: rocm,triaged

### 🚀 The feature, motivation and pitch

There are more guides showing up for ROCM on Windows such as this cuda program which needed cublas dependencies compiled with AMDs equivalent HIPblas:
https://github.com/YellowRoseCx/koboldcpp-rocm/releases/tag/Windows-v1.43-ROCm

As of July 27th, AMD officially supports HIP SDK on windows:
https://www.amd.com/en/developer/rocm-hub/hip-sdk.html

It would be very good for Pytorch Windows to function with a greater variety of AMD devices.

### Alternatives

_No response_

### Additional context

_No response_

cc @peterjc123 @mszhanyi @skyline75489 @nbcsm @vladimir-aubrecht @iremyux @Blackhex @cristianPanaite @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang
Repository: flutter
Issue: Reevaluate getting and parsing of iOS/macOS build settings
Labels: platform-ios,tool,P2,c: tech-debt,team-ios,triaged-ios

We use `xcodebuild -showBuildSettings` to get the build settings for iOS and macOS projects.
https://github.com/flutter/flutter/blob/adaf78a60dd9af5b7d16f87b56a7c35b981af29f/packages/flutter_tools/lib/src/ios/xcodeproj.dart#L175-L244

However, there appears to be some potential problems with this functionality:
1) If both `-target` and `-scheme` are used, it will error
2) If the scheme has multiple targets, it will use the build settings of whichever target it lists last, unless the setting is not found in the last target

For example, if you set two targets to `Run` for the scheme
![Screenshot 2023-09-13 at 10 44 01 AM](https://github.com/flutter/flutter/assets/15619084/5d0ef8d4-82ac-4c24-a5cd-267178afeb37)

And then did `xcodebuild -project xxx -configuration xxx -scheme Runner -showBuildSettings`, it would show something like:
```
Build settings for action build and target Runner:
...
Build settings for action build and target RunnerTests:
...
```

This has caused uncertainty in what to use, as seen in https://github.com/flutter/flutter/pull/134571#discussion_r1323473761.

We should make this functionality safer and easier to use.
Repository: next.js
Issue: Next TS plugin warning 'TS71007: Props must be serializable for components in the "use client" entry file' does not work with export default
Labels: bug

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/brave-northcutt-3h899t?file=%2Fapp%2Fpage.tsx%3A22%2C1

### To Reproduce

```typescript
type myProps = {
  myFunc: () => void;
};
const myComponent = ({ myFunc }: myProps) => {
  myFunc();
  return <></>;
};

export default myComponent;

export const myComponent2 = ({ myFunc }: myProps) => {
  myFunc();
  return <></>;
};

export function myComponent3({ myFunc }: myProps) {
  myFunc();
  return <></>;
}
```

only `myComponent2` and `myComponent3` show the warning. 

### Current vs. Expected behavior

Warning should also show for `myComponent`

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 23.0.0: Thu Aug 17 21:23:05 PDT 2023; root:xnu-10002.1.11~3/RELEASE_ARM64_T6000
    Binaries:
      Node: 20.3.1
      npm: 10.1.0
      Yarn: 1.22.19
      pnpm: 8.7.4
    Relevant Packages:
      next: 13.4.19
      eslint-config-next: 13.4.19
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.2.2
    Next.js Config:
      output: standalone
```


### Which area(s) are affected? (Select all that apply)

App Router

### Additional context

Code sandbox is a little redundant but see the `components.tsx` file inside `app` folder for the same code as above. The plugin code for this warning is here: https://github.com/vercel/next.js/blob/canary/packages/next/src/server/typescript/rules/client-boundary.ts
Repository: flutter
Issue: Update dart-internal results so that every build (including drones) are displayed on the dashboard
Labels: team-infra,P2,triaged-infra

Currently, we are only displaying the parent builds, `engine_release_builder`, `packaging_release_builder`, and `flutter_release_builder`. These LUCI builds have many sub builds that can be confusing to navigate. We would instead like to publish the child builds to the dashboard as well so that it takes less navigation to find an issue with a candidate branch build.

A couple things that need to be addressed:
* All sub builds are under the builder `{Platform} Engine Drone`, but will need to be named differently in the datastore
* We will need to add logic on the frontend to display the correct name, as well as handle the build link correctly
Repository: pytorch
Issue: inductor/test_max_autotune having timeout issues
Labels: module: tests,triaged,oncall: pt2,module: inductor

These tests sometimes take <1min, and other times cause the entire test file to timeout, meaning they are taking upwards of 20 minutes.  Sometimes they succeed on reruns which has been reducing the impact, but if it happens to more than just 1 or 2 tests, then the job will fail since it will run out of rerun chances.

They seem to only impact `linux-focal-cuda12.1-py3.10-gcc9-sm86 / test (default)` tests

Visible on hud https://hud.pytorch.org/hud/pytorch/pytorch/bfa8429c6a2ee9e0f4050066304743f6b13f14f7/1?per_page=100 (check show unstable)

The tests were introduced in https://github.com/pytorch/pytorch/pull/108015/files

Unlikely related to parallelization, the serial mem leak check job also had problems https://github.com/pytorch/pytorch/actions/runs/6169966074/job/16746129137, but I submitted https://github.com/pytorch/pytorch/pull/109209 just to be sure.

Here is a list of tests I have noticed do this:
```
inductor/test_max_autotune.py::TestDoBench::test_max_autotune_cutlass_backend_addmm_dynamic_False_max_autotune_gemm_backends_CUTLASS
inductor/test_max_autotune.py::TestDoBench::test_max_autotune_cutlass_backend_addmm_dynamic_False_max_autotune_gemm_backends_ATen, Triton, CUTLASS
inductor/test_max_autotune.py::TestDoBench::test_max_autotune_cutlass_backend_regular_mm_dynamic_False_max_autotune_gemm_backends_CUTLASS
inductor/test_max_autotune.py::TestDoBench::test_max_autotune_cutlass_backend_regular_mm_dynamic_False_max_autotune_gemm_backends_ATen, Triton, CUTLASS
inductor/test_max_autotune.py::TestDoBench::test_max_autotune_cutlass_backend_mm_bias_dynamic_False_max_autotune_gemm_backends_CUTLASS
inductor/test_max_autotune.py::TestDoBench::test_max_autotune_cutlass_backend_mm_bias_dynamic_False_max_autotune_gemm_backends_ATen, Triton, CUTLASS
```

If this doesn't get fixed, I'm going to need to revert the change or disable all these tests.

Example log: https://ossci-raw-job-status.s3.amazonaws.com/log/16755850617
ctrl f for `KeyboardInterrupt` and the relevant logs should be above it


cc @mruberry @ezyang @msaroufim @wconstab @bdhirsh @anijain2305 @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @Xia-Weiwen @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @ngimel @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov
Repository: go
Issue: net: TestVariousDeadlines failure on Windows LUCI builder
Labels: OS-Windows,NeedsInvestigation

```
#!watchflakes
post <- pkg == "net" && test == "TestVariousDeadlines" && `connectex: A connection attempted failed`
```

From https://ci.chromium.org/ui/p/golang/builders/try-workers/gotip-windows-amd64-test_only/b8770051282862599649/overview:
```
=== RUN   TestVariousDeadlines
=== PAUSE TestVariousDeadlines
=== CONT  TestVariousDeadlines
    timeout_test.go:1003: 1ns 0/1
    timeout_test.go:1019: 1ns 0/1: good timeout after 82.7µs; 0 bytes
    timeout_test.go:1003: 2ns 0/1
    timeout_test.go:1019: 2ns 0/1: good timeout after 891.3µs; 0 bytes
    timeout_test.go:1003: 5ns 0/1
    timeout_test.go:1019: 5ns 0/1: good timeout after 72µs; 0 bytes
    timeout_test.go:1003: 50ns 0/1
    timeout_test.go:1019: 50ns 0/1: good timeout after 833.5µs; 0 bytes
    timeout_test.go:1003: 100ns 0/1
    timeout_test.go:1007: dial tcp 127.0.0.1:56139: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
--- FAIL: TestVariousDeadlines (1.03s)
```

See previously #19519.

(CC @ianlancetaylor @neild)
Repository: go
Issue: html/template: treatment of CDATA sections in foreign content diverges from browsers
Labels: Security,NeedsFix

CDATA sections are only valid in foreign content (i.e. \<math\> or \<svg\>), and have various different meanings within that content (love to mix XML and HTML).

Per the HMTL specification (https://html.spec.whatwg.org/#cdata-sections and https://html.spec.whatwg.org/#cdata-section-state) the contents of CDATA sections are considered plaintext for the purposes of parsing, as such the two following fragments are treated differently:

```
<svg>
<script>
</script>
</script>
</svg>

---

<svg>
<script>
<![CDATA[
</script>
]]>
</script>
</svg>
```

In the first fragment the first `</script>` tag terminates the script section, but in the second fragment, since the first `</script>` tag is inside of a CDATA section, it is treated as plaintext and doesn't terminate the script block.

This can cause some strange interactions, since there are ways to structure something that looks like an end tag, but is valid JS (i.e. depending on the context, `</script/>` may be interpreted as a regex literal, while being interpreted by an HTML parser as an ending tag).

In an _extremely cursed_ template, this can cause html/template to improperly derive the correct context for contextual auto-escaping, leading to (extremely unlikely) XSS.

The following template illustrates this; since the parser does not believe the action is within the JS context (since it thinks `</script/>` terminated the script block), it will allow JS to be inserted unescaped.

```
<svg>
<script>
<![CDATA[
console.log(1</script/>`{{.}}`);
]]>
</script>
</svg>
```

(For those interested, this works because the JS interpreter treats this as an inequality `1 < /regex lit/ > "string"` which is obviously majorly broken, but will be happily executed. You can then use the JS template literal syntax to inject code using string interpolation syntax, i.e. `${alert(1)}`.)

This is obviously an incredibly contrived example, and is unlikely to ever actually impact any real world implementations, but should probably still be fixed. How to fix it is not immediately obvious, other than increasing the complexity of the parser to understand (a) foreign content sections and (b) CDATA (but only for the purposes of HTML parsing semantics). 

[golang.org/x/net/html](https://pkg.go.dev/golang.org/x/net/html) handles this correctly, since it applies the proper CDATA rules (and it doesn't need to understand JS semantics).

Thanks to @arkark for reporting this issue.

cc @golang/security @nigeltao
Repository: material-ui
Issue: [joy-ui][Button] Improve disabled buttons' text selection
Labels: waiting for 👍,component: button,package: joy-ui,enhancement

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

Joy's button text selection should behave as follows:

- Text selection from outside is possible
- Text selection from double-click is not possible

This seems to be the most common behavior. Right now, this is implemented for enabled buttons, **but not disabled ones**.

### Examples 🌈

You can see this behavior in Chrome and Safari in: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/button

https://github.com/mui/material-ui/assets/16889233/ac945e8f-fd77-45ea-b34f-28fe72d962fa

In Firefox, the buttons' text is not selectable.

### Motivation 🔦

Following up on Point 13 of this comment: https://github.com/mui/material-ui/pull/36622#issuecomment-1644790976.
Repository: electron
Issue: [Bug]: Clipboard.read doesn't return values when available format is text/uri-list 
Labels: platform/windows,bug :beetle:,has-repro-gist,26-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

26.2.0

### What operating system are you using?

Windows

### Operating System Version

windows 10 22H2

### What arch are you using?

x64

### Last Known Working Electron version

unknown

### Expected Behavior

Trying to retrieve the file list copied to the clipboard on windows using clipboard.read() and the resulting list is empty.  Calling availableFormats() returns text/uri-list as the available format.  If you read("text/uri-list") you get a zero length string.  Previously you could request clipboard format CF_HDROP and get back a string with the selected files.



### Actual Behavior

No list of files is available through the clipboard api

### Testcase Gist URL

https://gist.github.com/rstupek/2e50c95f740548cf54d6b283f69f9e16

### Additional Information

You need to open windows explorer and select multiple files and choose Copy.
Repository: go
Issue: net: TestUDPReadSizeError failures
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "net" && test == "TestUDPReadSizeError" && `panic: test timed out`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/7a4042b5f780d94b5a0c865452ec5a45a7c73df0)):

    panic: test timed out after 3m0s
    running tests:
    	TestUDPReadSizeError (2m54s)
    
    runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?)
    	/tmp/workdir/go/src/runtime/proc.go:398 +0xce fp=0xc000421b80 sp=0xc000421b60 pc=0x43a88e
    runtime.netpollblock(0x0?, 0x405266?, 0x0?)
    	/tmp/workdir/go/src/runtime/netpoll.go:573 +0xf7 fp=0xc000421bb8 sp=0xc000421b80 pc=0x434157
    internal/poll.runtime_pollWait(0x847af6090, 0x72)
    	/tmp/workdir/go/src/runtime/netpoll.go:345 +0x85 fp=0xc000421bd8 sp=0xc000421bb8 pc=0x465fe5
    internal/poll.(*pollDesc).wait(0xc000537100?, 0xc0000a1878?, 0x0)
    	/tmp/workdir/go/src/internal/poll/fd_poll_runtime.go:84 +0x27 fp=0xc000421c00 sp=0xc000421bd8 pc=0x4936c7
    internal/poll.(*pollDesc).waitRead(...)
    	/tmp/workdir/go/src/internal/poll/fd_poll_runtime.go:89
    internal/poll.(*FD).ReadFromInet4(0xc000537100, {0xc0000a1878, 0x13, 0x13}, 0xc0001e7cd8?)
    	/tmp/workdir/go/src/internal/poll/fd_unix.go:247 +0x22b fp=0xc000421c98 sp=0xc000421c00 pc=0x494f4b
    net.(*netFD).readFromInet4(0xc000537100, {0xc0000a1878?, 0x4967cf?, 0xc000537180?}, 0xc0000a1860?)
    	/tmp/workdir/go/src/net/fd_posix.go:66 +0x25 fp=0xc000421ce8 sp=0xc000421c98 pc=0x559b45
    net.(*UDPConn).readFrom(0x30?, {0xc0000a1878?, 0xc0002c05d0?, 0x0?}, 0xc0002c05d0)
    	/tmp/workdir/go/src/net/udpsock_posix.go:52 +0x1b2 fp=0xc000421dd8 sp=0xc000421ce8 pc=0x579c32
    net.(*UDPConn).readFromUDP(0xc0006163a8, {0xc0000a1878?, 0x44f5a9?, 0x13?}, 0x638ae0?)
    	/tmp/workdir/go/src/net/udpsock.go:149 +0x30 fp=0xc000421e30 sp=0xc000421dd8 pc=0x577c50
    net.(*UDPConn).ReadFrom(0x683cd6?, {0xc0000a1878, 0x13, 0x13})
    	/tmp/workdir/go/src/net/udpsock.go:158 +0x4a fp=0xc000421e70 sp=0xc000421e30 pc=0x577dea
    net.TestUDPReadSizeError(0xc0002c2340)
    	/tmp/workdir/go/src/net/udpsock_test.go:423 +0x33f fp=0xc000421f70 sp=0xc000421e70 pc=0x5fd53f
    testing.tRunner(0xc0002c2340, 0x69b3b0)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: next.js
Issue: page.tsx causes internal server error when searchParams is used
Labels: bug

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/geotrev/next-server-search-params

### To Reproduce

1. Create a new `app/<route>/page.tsx` file
2. Define the component using `searchParams`
3. Deploy to netlify using a basic configuration (`next build`)
4. Attempt to navigate to the new route via browser.

This occurs with or without the use of this metadata export:

```jsx
export const dynamic = 'force-dynamic'
```

See both live examples here:
- No `force-dynamic`: [link](https://server-page--next-server-search-params.netlify.app/)
- With `force-dynamic`: [link](https://dynamic-page--next-server-search-params.netlify.app/)

### Current vs. Expected behavior

Current: Page throws 500 internal server error

Expected: page loads normally.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Fri Jan 27 02:56:13 UTC 2023
Binaries:
  Node: 18.12.1
  npm: 9.8.1
  Yarn: N/A
  pnpm: 8.7.5
Relevant Packages:
  next: 13.4.20-canary.27
  eslint-config-next: 13.4.19
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A
```


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

App Router

### Additional context

This is a netlify + next deploy as shown in the reproduction repo.

---

The latest canary release has a completely new error:

```
 Runtime.ImportModuleError - Error: Cannot find module 'styled-jsx/style' Require stack: - /var/task/node_modules/next/dist/server/import-overrides.js - /var/task/node_modules/next/dist/server/require-hook.js - /var/task/node_modules/next/dist/server/next-server.js - /var/task/.netlify/functions-internal/___netlify-handler/___netlify-handler.js - /var/task/___netlify-handler.js - /var/runtime/index.mjs 
```

Stack trace:

```
Runtime.ImportModuleError: Error: Cannot find module 'styled-jsx/style'
Require stack:
- /var/task/node_modules/next/dist/server/import-overrides.js
- /var/task/node_modules/next/dist/server/require-hook.js
- /var/task/node_modules/next/dist/server/next-server.js
- /var/task/.netlify/functions-internal/___netlify-handler/___netlify-handler.js
- /var/task/___netlify-handler.js
- /var/runtime/index.mjs
    at _loadUserApp (file:///var/runtime/index.mjs:1061:17)
    at async UserFunction.js.module.exports.load (file:///var/runtime/index.mjs:1093:21)
    at async start (file:///var/runtime/index.mjs:1256:23)
    at async file:///var/runtime/index.mjs:1262:1
```
Repository: pytorch
Issue: AOTAutograd should track view chains so it can replay them, instead of using as_strided.
Labels: triaged,oncall: pt2,module: aotdispatch,module: pt2-dispatcher

This is a tracker issue for doing the longer term thing described in https://github.com/pytorch/pytorch/issues/109053.

The point of this is mainly perf: As mentioned in this internal issue, calling as_strided() means that as_strided_backward() will show up in the backward graph, which is known to be slow (internal post: https://fb.workplace.com/groups/147416452503510/posts/1211736186131257/)

cc @ezyang @msaroufim @wconstab @anijain2305 @zou3519