sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: `createSession` passes in a set of scopes and the session returned shouldn't need to match those scopes
Labels: bug,authentication

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
Version: 1.84.2 (user setup)
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:51:52.184Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.22621

Steps to Reproduce:
I'm developing a Visual Studio Code extension and trying to create my own Authentication Provider. I've noticed that the 'sign in' option doesn't disappear even after I've already signed in. I have to reopen Visual Studio Code to get rid of it. Does anyone know the reason behind this and how to fix it?
![image](https://github.com/microsoft/vscode/assets/39795353/30348cc6-c923-4262-b159-b26db915a02f)

I get the code is from https://github.com/estruyf/vscode-auth-sample/blob/main/src/auth0AuthenticationProvider.ts
1. open vscode
2. sign in using customed Authentication Provider
Repository: create-react-app
Issue: Changes to types in node_modules results in typescript errors while using the dev env
Labels: needs triage,issue: bug report

### Describe the bug

If I install a new version of a package with different typescripts types, the webpack process started by `react-scripts start` command does not take into consideration the newly added types and results in a typescript error.

### Did you try recovering your dependencies?

not applicable

### Which terms did you search for in User Guide?

Here https://facebook.github.io/create-react-app/docs/troubleshooting I have searched for "types".

### Environment

```
Environment Info:

  current version of create-react-app: 5.0.1
  running from /Users/iulian-bogdanvlad/.npm/_npx/c67e74de0542c87c/node_modules/create-react-app

  System:
    OS: macOS 13.4
    CPU: (10) arm64 Apple M1 Max
  Binaries:
    Node: 16.17.0 - ~/.nvm/versions/node/v16.17.0/bin/node
    Yarn: 3.6.4 - ~/.nvm/versions/node/v16.17.0/bin/yarn
    npm: 8.15.0 - ~/.nvm/versions/node/v16.17.0/bin/npm
  Browsers:
    Chrome: 119.0.6045.199
    Edge: Not Found
    Firefox: 115.0.3
    Safari: 16.5
  npmPackages:
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    react-scripts: 5.0.1 => 5.0.1
  npmGlobalPackages:
    create-react-app: Not Found
```

### Steps to reproduce

1. Run create react app with typescript template.
2. Create a package P that contains some types and publish it to npm
3. Import the types from P in your app and use them somewhere
4. run `npm start`
5. Update the P package, by adding a new type.
6. Run `npm install P` to install the latest version while `npm start` is still running.
7. Import the new type and use it in your code.
8. `npm start` will complain that the new type does not exist and there is no way to make it work without restarting. The webpack bundling finishes correctly, but the type checking fails.

### Expected behavior

I would expect that the newly added type to be seen by `npm start` without restarting it.

### Actual behavior

I receive an error and I have to restart `npm start` to make it work again.

![Screenshot 2023-12-04 at 12 29 55](https://github.com/facebook/create-react-app/assets/2605114/3609055e-be4e-4163-855c-75291664ac2a)

### Reproducible demo

[Here](https://github.com/vladiulianbogdan/demo-bug-create-react-app/blob/main/package.json) I have a simple CRA app. The project uses a library `test-getting-started-genezio-typescript-newest_us-east-1` that has two versions: `1.0.0-local` and `1.0.1-local` the only difference between the two is that the 1.0.1 has a new type. First install 1.0.0, run `npm start`, then install 1.0.1, use the new type.
Repository: three.js
Issue: Cache clobbering when loading same file through `FileLoader`, `ImageBitmapLoader`, or `ImageLoader`
Labels: Loaders

### Description

Currently, all these 3 classes use the `THREE.Cache` data structure to store their caches. However, whilst all of them return different values, they all key by URL & it means loading the same URL the second time through a different loader will produce an incorrect result.

### Reproduction steps

1. Load a file using `FileLoader`
2. Load a file using `ImageBitmapLoader`
3. The returned value from `ImageBitmapLoader` will be the value from `FileLoader`, instead of an `ImageBitmap`


### Code

```js
import * as THREE from 'three';

THREE.Cache.enabled = true;

const fileLoader = new THREE.FileLoader();
file = await (new Promise((resolve) => {
	fileLoader.load(url, (v) => {
		resolve(v);
	});
}));

const imageBitmapLoader = new THREE.ImageBitmapLoader();
imageBitmap = await (new Promise((resolve) => {
	imageBitmapLoader.load(url, (v) => {
		resolve(v);
	});
}));

if (file === imageBitmap) throw new Error('Incorrect cached data!');
```


### Live example

* [Svelte playground](https://svelte.dev/repl/4ff1ff176ff74704a8b07c4a1988d018?version=4.2.8)

When on the page, press `Enable cache` to see the incorrect result.

> Sorry, I'm not familiar with JSFiddle!


### Screenshots

_No response_

### Version

r159

### Device

_No response_

### Browser

_No response_

### OS

_No response_
Repository: vscode
Issue: Color picker is far too wide and does not remember when I resize it smaller
Labels: bug,editor-hover

This was discussed a little in #178670, but I'm not sure I totally understand the logic behind it sometimes not saving my size. Additionally, it now seems even wider than it was back then.

https://github.com/microsoft/vscode/assets/1078012/e4ed2947-e391-4834-a899-c0f13559cc12
Repository: ant-design
Issue: "Default" Button does not have a standalone hover color config for text and background.
Labels: 💡 Feature Request,Inactive

### What problem does this feature solve?

The Button uses the same `colorPrimaryHover` config for both "primary" background and "default" text color. Can we have a separated config for default's hover background and text?

### What does the proposed API look like?

- `defaultBgHover` - for "default" Button background's color when hover. Value default to `defaultBg` if not specified.
- `defaultColorHover` - for "default" Button text's color when hover. Value default to `colorPrimaryHover` if not specified.
- `defaultBorderColorHover` - for "default" Button border's color when hover. Value default to `defaultColorHover` if not specified.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: neovim
Issue: `ui_events_metadata.generated.h` reproducible builds
Labels: bug,enhancement,build,distribution

### Problem

While working on [reproducible builds](https://reproducible-builds.org/) for [openSUSE](https://en.opensuse.org/openSUSE:Reproducible_Builds), I found that in our `neovim` package,
`neovim-0.9.4/build/src/nvim/auto/api/private/ui_events_metadata.generated.h`
and the resulting `nvim` binary vary between builds.

This is probably generated in `src/nvim/generators/gen_api_ui_events.lua`

    dump_bin_array(metadata_output, 'ui_events_metadata', packed)

and lua is notorious for its indeterministic order.


### Steps to reproduce

Build neovim from scratch twice and compare results.

### Expected behavior

It should be possible to build identical binaries twice.

### Neovim version (nvim -v)

0.9.4

### Vim (not Nvim) behaves the same?

vim behaves better

### Operating system/version

openSUSE Tumbleweed 20231129

### Terminal name/version

N/A

### $TERM environment variable

N/A

### Installation

rpm/spec: https://github.com/bmwiedemann/openSUSE/blob/75d0b7716ffaf62a6764e3b87f1e5aa54049d32d/packages/n/neovim/neovim.spec#L169
Repository: go
Issue: x/text/secure/precis: UsernameCaseMapped and UsernameCasePreserved should disallow empty usernames
Labels: NeedsInvestigation

### Go version

go version go1.21.3 linux/amd64

### What operating system and processor architecture are you using (`go env`)?

<details>
```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/mitar/.cache/go-build'
GOENV='/home/mitar/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/mitar/.go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/mitar/.go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/local/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/local/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.21.3'
GCCGO='/usr/bin/gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build3082737491=/tmp/go-build -gno-record-gcc-switches'
```
</details>

### What did you do?

Ran `precis.UsernameCaseMapped.String("")`.

### What did you expect to see?

An error returned as written in [RFC 8265](https://datatracker.ietf.org/doc/html/rfc8265#section-3.1):

> A username MUST NOT be zero bytes in length.  This rule is to be enforced after any normalization and mapping of code points.

It seems `DisallowEmpty` option should be added to `UsernameCaseMapped` and `UsernameCasePreserved`. It is already added to `Nickname` and `OpaqueString`.

### What did you see instead?

No error returned.
Repository: next.js
Issue: Next 14 build errors on jspm.dev urlImports (works in Next 12 w/ babel)
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/strange-lamarr-drl3wf

### To Reproduce

Open https://codesandbox.io/p/devbox/strange-lamarr-drl3wf and observe the build errors.

This same project builds without any issues on Next.js 12.1.0 using babel.

### Current vs. Expected behavior

That the project doesn't fail to build jspm.dev url imports by migrating from Next 12 to Next 14.

This same project builds without any issues on Next.js 12.1.0 using babel.

### 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 PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 14.0.4-canary.39
  eslint-config-next: 14.0.3
  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)

Not sure

### Additional context

I noticed that 14.0.3 and 14.0.4 canary produce different build errors. 14.0.3 complains about a missing `_` export. Canary about `self` in the jspm file.
Repository: vscode
Issue: Aux window: should change the cursor style within the dropping area
Labels: help wanted,feature-request,workbench-dnd,workbench-auxwindow

Currently, when attempting to drop the window on the desktop, the cursor indicates 'not allowed.' However, once the editor can be dragged outside, the cursor should switch to the appropriate grabbing icon. Alternatively, it would be beneficial if an animation similar to the Chromium browser's could be implemented.

//cc @bpasero 

https://github.com/microsoft/vscode/assets/50770619/81ce6fd7-e75e-4222-b3e6-d6273afbd66f
Repository: godot
Issue: Editor crashes on textures import
Labels: bug,topic:core,topic:import,crash,topic:2d

### Godot version

v4.2.stable.official [46dc27791]

### System information

Fedora 39 KDE Plasma 5.27.9

### Issue description

Since upgrading my project from Godot 3 to 4, there is a recurrent bug with textures import that is present on some machines/OSes and not present on others (there is no system in its behavior as I can see). On my machine the editor prints this error for every imported texture and then crashes (sometimes it doesn't crash):
```
ERROR: Expected Image data size of 182x242x1 (DXT1 RGB8 with 7 mipmaps) = 30120 bytes, got 30216 bytes instead.
   at: initialize_data (core/io/image.cpp:2219)
```
On my coworkers' machines (both Linux and Windows) it may work fine for some time, but then suddenly it starts to show these errors too.

### Steps to reproduce

1. Launch the attached project

### Minimal reproduction project

[Bug.zip](https://github.com/godotengine/godot/files/13546902/Bug.zip)
Repository: PowerToys
Issue: Powertoys installed twice and can't uninstall any of them
Labels: Issue-Bug,Area-Setup/Install,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.75.1 

### Installation method

PowerToys auto-update, WinGet

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

Not sure how happened but I ended up with 2 versions of PowerToys and now I can't uninstall any if them. 

I found the problem because it crashed after clicking on the install button, or after a reboot it didn't auto start. 

already tried uninstalling via Winget, Add or Remove Programs, and control panel, I get the following pop up. 

I've attached the .zip file generated via report a bug, and the log file provided by the pop up. 

![image](https://github.com/microsoft/PowerToys/assets/120376830/df233e31-49b0-46aa-bff8-7e34034080d0)

[powertoys-bootstrapper-msi-0.74.1_20231204143107.log](https://github.com/microsoft/PowerToys/files/13547345/powertoys-bootstrapper-msi-0.74.1_20231204143107.log)

[PowerToysReport_2023-12-04-14-28-16.zip](https://github.com/microsoft/PowerToys/files/13547322/PowerToysReport_2023-12-04-14-28-16.zip)




### ✔️ Expected Behavior

Being able to update or uninstall the application

### ❌ Actual Behavior

It doesn't update or uninstall. I had to disable auto-updates. I have 2 versions installed, 0.74.1 and 0.75.1

![image](https://github.com/microsoft/PowerToys/assets/120376830/af6984d4-74cc-4263-8bd5-af855d227923)


### Other Software

_No response_
Repository: vscode
Issue: The IDE keeps crashing
Labels: freeze-slow-crash-leak,linux,under-discussion

I was editing a file and the IDE just crashed.
A popup window showed up saying "Sorry for the inconvenience bla bla bla" and that I could "restart from where I left" or something like that, I don't remember the exact wording.
There was a button that I don't remember whether it was "reopen" or "restore", and I clicked it, but it did NOT relaunch the IDE. I had to relaunch it manually.

Fortunately, most of the unsaved changes I had made to the current file (which got reopened when I manually launched the IDE again) were there, but not exactly everything. The last dozen or so keystrokes were lost.

I wasn't offered any option to upload a crash log or something like that.

What I would expect:
1. The IDE should never, ever crash in the first place. Stability is the number one priority.
2. If it does, everything to the very last keystroke must have been saved, and be restored upon restarting
3. If it says it's going to reopen and offers me a button called "reopen" or "restore", I expect it to restore. Otherwise just tell me that I have to do it myself (but then again, why shouldn't be able to do it?)
4. When there's a crash, you must indicate me at the very least where I can find a log, hopefully with relevant information about the crash or about what happened just before it, that I can upload here or wherever. Usually, decent software shows a button that automatically sends the relevant logs to the developers. I would be happy with just not having to look for the logs, or the menu option.

If there is some log that I can fetch, let me know so I upload it if it's not too late.


version 1.84.2 on Manjaro Linux
Repository: pytorch
Issue: Undefined symbol: cuOccupancyMaxActiveClusters
Labels: triaged,oncall: pt2

### 🐛 Describe the bug

`torch.compile` is failing on nightly:
Starting docker `FROM pytorch/pytorch:2.1.0-cuda11.8-cudnn8-devel`

`pip install --upgrade --pre torch torchvision torchaudio --index-url https://download.pytorch.org/whl/nightly/cu118`
```
torch._dynamo.exc.BackendCompilerFailed: backend='inductor' raised:
 ImportError: /tmp/torchinductor_root/triton/0/4fcaf02726b7cedfebb83bbf158e9de6/cuda_utils.so: undefined symbol: cuOccupancyMaxActiveClusters
```

### Versions

`torch-2.2.0.dev20231204%2Bcu118-cp310-cp310-linux_x86_64.whl`

cc @ezyang @msaroufim @wconstab @bdhirsh @anijain2305 @zou3519
Repository: material-ui
Issue: [material-ui][Chip] The `skipFocusWhenDisabled` prop skips the focus when set to false and when disabled is true
Labels: bug 🐛,component: chip,package: material-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example:

Steps:

1. Go to the Mui chip link https://mui.com/material-ui/react-chip/
2. Goto the clickable section 
3. update the example with the following code
 `<Chip label="Clickable" disabled skipFocusWhenDisabled={false}  onClick={handleClick} /> 
<Chip label="Clickable" variant="outlined" onClick={handleClick} />`




### Current behavior 😯

If you inspect the first chip component that is disabled if you set skipFocusWhenDisabled={true} the tabIndex is set to -1 which I think is correct if you then set skipFocusWhenDisabled={false} the tabIndex is still  -1 which I think is incorrect.

### Expected behavior 🤔

When disabled is set to true and skipFocusWhenDisabled={false} the Index should not be -1 it should allow it to have focus.

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: go
Issue: cmd/link: test timeouts
Labels: help wanted,NeedsInvestigation,compiler/runtime

```
#!watchflakes
post <- pkg == "cmd/link" && log ~ `test timed out`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/a6ac06d6b94a466299ba8b4fab41d48d3295a497)):

    --- FAIL: TestLargeReloc (168.16s)
        exec.go:193: test timed out while running command: /tmp/workdir-host-ios-arm64-corellium-ios/go/bin/go run -ldflags=-linkmode=external /tmp/workdir-host-ios-arm64-corellium-ios/tmp/TestLargeReloc2020861662/001/x.go
        link_test.go:1106: build failed: exit status 2. output:
            SIGQUIT: quit
            PC=0x1afbe3374 m=0 sigcode=0
    
            goroutine 0 gp=0x100f61900 m=0 mp=0x100f62e00 [idle]:
            syscall.syscall6(0xc?, 0x1300736b0?, 0x1000118?, 0x101f36478?, 0x90?, 0x10162c108?, 0x90?)
            	runtime/sys_darwin.go:45 +0x68 fp=0x1300735e0 sp=0x130073520 pc=0x1005398c8
            syscall.wait4(0x130073678?, 0x1005b1758?, 0x90?, 0x100bd3460?)
    ...
            r24     0x6b0f25af94fec10d
            r25     0xb2e301ebc884e399
            r26     0x0
            r27     0x838
            r28     0x100f61900
            r29     0x16f93afa8
            lr      0x10053e818
            sp      0x16f93afa0
            pc      0x1afbe3374
            fault   0x1afbe3374


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: material-ui
Issue: [material-ui][Autocomplete] Input is not resetting on value changes with `freeSolo` prop
Labels: bug 🐛,package: material-ui,component: autocomplete

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: https://codesandbox.io/p/sandbox/awesome-lucy-vtndj5?file=%2Fsrc%2FApp.tsx%3A17%2C3

Steps:

1. Select any value
2. Click on reset value button 


### Current behavior 😯

input is not resetting on value changes with freeSolo prop

### Expected behavior 🤔

input is resetting on value changes with freeSolo prop
without this prop all good works https://codesandbox.io/p/sandbox/quiet-sky-xvllpd?file=%2Fsrc%2FApp.tsx

### Context 🔦

Autocomplete which having reset values in some cases with enabled freeSolo


### Your environment 🌎

```
  System:
    OS: macOS 14.1.2
  Binaries:
    Node: 18.12.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.19.2 - /usr/local/bin/npm
  Browsers:
    Chrome: 119.0.6045.199
    Edge: Not Found
    Safari: 17.1.2
  npmPackages:
    @emotion/react: 11.11.1 => 11.11.1 
    @emotion/styled: 11.11.0 => 11.11.0 
    @mui/base:  5.0.0-beta.25 
    @mui/core-downloads-tracker:  5.14.19 
    @mui/icons-material: 5.14.19 => 5.14.19 
    @mui/material: 5.14.19 => 5.14.19 
    @mui/private-theming:  5.14.19 
    @mui/styled-engine:  5.14.19 
    @mui/styles: 5.14.19 => 5.14.19 
    @mui/system:  5.14.19 
    @mui/types:  7.2.10 
    @mui/utils:  5.14.19 
    @types/react:  18.2.41 
    react: 17.0.2 => 17.0.2 
    react-dom: 17.0.2 => 17.0.2 

```
Repository: TypeScript
Issue: Vanilla JS: Mixins break inherited type hints
Labels: Suggestion,Help Wanted,Domain: Quick Info,Experience Enhancement

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.84.2
- OS Version: Windows 10

The issue is quite simple, as shown below, mixins break inherited type hints. `exampleMethod()` below should have hint references for `this.myStr` and `this.propIsHinted` but does not.

Apologies if this belongs somewhere else like the typescript repo, it's vanilla JS but it's probably related to typescript/JSDoc functionality.

```js
function NumberMixin( Base ) {

	return class NumberMixin extends Base {

		/** @type {number} */
		myNum;

	};

}

function StringMixin( Base ) {

	return class StringMixin extends Base {

		/** @type {string} */
		myStr;

	};

}

class MyBase {

	/** @type {boolean} */
	propIsHinted;

}

class SuperClass extends NumberMixin(StringMixin(MyBase)) {

	exampleMethod() {

		// Hinted
		this.myNum;

		// Not hinted
		this.myStr;

		// Not hinted
		this.propIsHinted;

	}

}
```