issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.46B | issue_number int64 1 127k |
|---|---|---|---|---|---|---|---|---|---|
[
"chakra-core",
"ChakraCore"
] | ``` js
{
let x;
{
var x;
}
}
print(x);
```
Expected: Error, x undeclared.
Actual: prints undefined as the var binding hoists past let.
| Vars should not hoist past lets. | https://api.github.com/repos/chakra-core/ChakraCore/issues/850/comments | 1 | 2016-04-21T18:46:51Z | 2016-08-26T20:07:18Z | https://github.com/chakra-core/ChakraCore/issues/850 | 150,158,257 | 850 |
[
"chakra-core",
"ChakraCore"
] | ```
{ var x; let x; }
```
Expected: SyntaxError, duplicate delcarations.
Actual: No error, var is hoisted out.
| No syntax error for let redeclaring var in a block | https://api.github.com/repos/chakra-core/ChakraCore/issues/849/comments | 3 | 2016-04-21T18:44:28Z | 2019-06-07T18:34:55Z | https://github.com/chakra-core/ChakraCore/issues/849 | 150,157,786 | 849 |
[
"chakra-core",
"ChakraCore"
] | Two SIMD.js ops: **Float32x4.min()** and **Float32x4.max()** produce a wrong result when there's a NaN value in the first operand and a number in the second operand.
For example, if the following two SIMD values are compared both **mix** and **max** ops will set the fourth lane of the resulting value to 42.
```
... | SIMD.js/Asm.js : Float32x4.min/Float32x4.max may produce wrong result if one of the first opnd's lanes is NaN | https://api.github.com/repos/chakra-core/ChakraCore/issues/837/comments | 1 | 2016-04-20T17:15:44Z | 2016-04-21T18:05:32Z | https://github.com/chakra-core/ChakraCore/issues/837 | 149,831,552 | 837 |
[
"chakra-core",
"ChakraCore"
] | how to set TLS version in Edge browser? | https://api.github.com/repos/chakra-core/ChakraCore/issues/834/comments | 1 | 2016-04-20T02:03:28Z | 2016-05-03T00:02:46Z | https://github.com/chakra-core/ChakraCore/issues/834 | 149,633,164 | 834 | |
[
"chakra-core",
"ChakraCore"
] | Hello,
Given a script that looks like:
```
function test1() {
this.number = 1;
this.str = "str";
this.obj = { "a": 1, "b": 2 };
this.arr = [1, 2, 3, 4];
this.func = function () {
var inti = 2;
};
debugger;
}
test1.prototype.snumber = 2;
test1.prototype.sstr = "str2";
test1.prototy... | Get properties for this | https://api.github.com/repos/chakra-core/ChakraCore/issues/832/comments | 5 | 2016-04-19T22:47:28Z | 2016-04-26T21:53:56Z | https://github.com/chakra-core/ChakraCore/issues/832 | 149,604,666 | 832 |
[
"chakra-core",
"ChakraCore"
] | I have a data processing logic (map-reduce) in a _JavaScript file _which currently runs on browser. The user downloads this data processing JS file as part of the html content download, and then the browser runs it.
I currently use _ASP.NET 5 Web API _for data retrieval. I want to move this data processing logic (JS f... | Running ChakraCore in ASP.NET web api | https://api.github.com/repos/chakra-core/ChakraCore/issues/830/comments | 1 | 2016-04-19T12:28:20Z | 2016-05-03T00:03:00Z | https://github.com/chakra-core/ChakraCore/issues/830 | 149,446,825 | 830 |
[
"chakra-core",
"ChakraCore"
] | See also: https://github.com/tc39/ecma262/issues/543
Spec has fixed a bug that was not allowing classes that extend null to use `this` in the constructor body. This has been fixed, and our implementation needs updates to conform!
| class extends null should bind this | https://api.github.com/repos/chakra-core/ChakraCore/issues/829/comments | 1 | 2016-04-19T01:05:23Z | 2017-01-06T23:27:20Z | https://github.com/chakra-core/ChakraCore/issues/829 | 149,316,138 | 829 |
[
"chakra-core",
"ChakraCore"
] | Asmjs validation should require coercion for return values. Simd values needs to be coreced using the check() builtin before returning from asmjs functions. currently this is not enforced.
**Repro Case**
``` javascript
function module(stdlib) {
"use asm"
var b = stdlib.SIMD.Uint8x16;
function foo() {
... | SIMD.js: Asmjs validation allows returning simd values from functions without coercion. | https://api.github.com/repos/chakra-core/ChakraCore/issues/827/comments | 1 | 2016-04-19T00:24:17Z | 2016-04-26T19:09:34Z | https://github.com/chakra-core/ChakraCore/issues/827 | 149,309,342 | 827 |
[
"chakra-core",
"ChakraCore"
] | See https://github.com/Microsoft/ChakraCore/blob/master/lib/Jsrt/ChakraCommon.h#L1113
Since this is a buffer size, the most portable type for the parameter would be `size_t` instead of `unsigned int *`.
@liminzhu: @digitalinfinity mentioned this might not be possible because of compat, but could you confirm that and ... | Use size_t * instead of unsigned int * for JsSerializeScript's bufferSize param | https://api.github.com/repos/chakra-core/ChakraCore/issues/825/comments | 8 | 2016-04-18T21:25:25Z | 2017-01-18T18:28:41Z | https://github.com/chakra-core/ChakraCore/issues/825 | 149,276,823 | 825 |
[
"chakra-core",
"ChakraCore"
] | SIMD.Bool8x16.extractLane produces a wrong result while extracting "true" values.
Repo cmd:
[el_bug.js.txt](https://github.com/Microsoft/ChakraCore/files/224793/el_bug.js.txt)
```
function asmModule(stdlib, imports) {
"use asm";
var b16 = stdlib.SIMD.Bool8x16;
var b16extractLane = b16.extractLane;
f... | AsmJS: SIMD.Bool8x16.extractLane produces a wrong result | https://api.github.com/repos/chakra-core/ChakraCore/issues/824/comments | 3 | 2016-04-18T21:12:29Z | 2016-04-27T22:57:06Z | https://github.com/chakra-core/ChakraCore/issues/824 | 149,273,470 | 824 |
[
"chakra-core",
"ChakraCore"
] | ``` javascript
JSON.parse("")
```
```
$ ch.exe jsonParseEmpty.js
SyntaxError: Syntax error
at Global code (d:\personal\chakracore\build\vcbuild\bin\x64_debug\test.js:1:1)
```
'Syntax Error' is very ambiguous error. It could mean a lot of things. When its part of a large callstack, I would think its a javascript sy... | JSON.parse("") gives very ambigious "Syntax Error". | https://api.github.com/repos/chakra-core/ChakraCore/issues/804/comments | 2 | 2016-04-13T22:11:16Z | 2016-06-06T21:18:56Z | https://github.com/chakra-core/ChakraCore/issues/804 | 148,197,795 | 804 |
[
"chakra-core",
"ChakraCore"
] | Sorry in advance I haven't been able to get a simpler repro case at this time.
My test case is the following
``` js
const n = 500;
function getTest(name) {
var fn;
eval(`fn = function memcopy_${name}(a, b, start, end) {for (let i = start; i < end; i++) { b[i] = a[i]; }}`);
return fn
}
var foo = getTest("Int8")
v... | `let` vs `var` generates a lot more instructions | https://api.github.com/repos/chakra-core/ChakraCore/issues/800/comments | 4 | 2016-04-13T18:27:05Z | 2017-05-18T18:17:23Z | https://github.com/chakra-core/ChakraCore/issues/800 | 148,143,805 | 800 |
[
"chakra-core",
"ChakraCore"
] | **IE browser v:** 11.0.9600.18230
**OS:** 7 Enterprise
**Description:** When attempting to calculate the difference of time (hours) between two JavaScript date variables falling on either side of daylight saving time (spring forward / UTC Central) 2am is improperly handled.
Daylight saving time should recognize 2am (0... | JS Daylight Saving Date Difference | https://api.github.com/repos/chakra-core/ChakraCore/issues/798/comments | 3 | 2016-04-13T15:53:14Z | 2016-05-03T00:03:50Z | https://github.com/chakra-core/ChakraCore/issues/798 | 148,105,765 | 798 |
[
"chakra-core",
"ChakraCore"
] | This is a discussion thread on implementing proper tail calls (PTC) in Chakra. For simplicity, only full jit implementation is discussed.
### Introduction
[Wiki](http://www.lua.org/pil/6.3.html) & in [Javascript](http://www.2ality.com/2015/06/tail-call-optimization.html)
### x86 implementation details of a PTC
Chakr... | Implement Proper Tail Call [Discussion] | https://api.github.com/repos/chakra-core/ChakraCore/issues/796/comments | 11 | 2016-04-13T14:25:23Z | 2018-11-01T16:38:08Z | https://github.com/chakra-core/ChakraCore/issues/796 | 148,078,173 | 796 |
[
"chakra-core",
"ChakraCore"
] | AsmJs parser crashes when parsing a variable declaration w/o an initialization (i.e. no RHS).
Repro case:
Command line args: $CH -asmjs noinitinvardecl.js
Repo testcase:
```
function module(stdlib)
{
"use asm"
function foo()
{
var abc;
}
}
```
Expected Output:
> Invalid (empty) rightha... | AsmJs. Crash in AsmJsModule when parsing a variable declaration w/o an initialization (empty RHS) | https://api.github.com/repos/chakra-core/ChakraCore/issues/786/comments | 2 | 2016-04-12T18:39:00Z | 2016-04-13T01:08:46Z | https://github.com/chakra-core/ChakraCore/issues/786 | 147,837,769 | 786 |
[
"chakra-core",
"ChakraCore"
] | this is likely a bug with setTimeout, so if that's a Edge thing I can reopen there. As reported defunctzombie/node-process#56 it looks like it's possible to add a setTimeout run synchronous code and then call clearTimeout but have the timeout callback called anyway. If I had to guess my suspicion would be that certai... | Timeouts can fire even when unset syncronously | https://api.github.com/repos/chakra-core/ChakraCore/issues/784/comments | 2 | 2016-04-12T13:45:37Z | 2016-05-03T00:04:24Z | https://github.com/chakra-core/ChakraCore/issues/784 | 147,756,098 | 784 |
[
"chakra-core",
"ChakraCore"
] | When calling JsDiagGetObjectFromHandle i'd expect the same property structure for the object returned. It seems that when called on handle returned in the locals array of the JsDiagGetStackProperties method, it will return a structure like:
```
/// {
/// "name" : "this",
/// "type" : "o... | JsDiagGetObjectFromHandle reurns object with JsDiagEvaluate alike properties | https://api.github.com/repos/chakra-core/ChakraCore/issues/775/comments | 1 | 2016-04-11T10:45:10Z | 2016-04-28T16:41:17Z | https://github.com/chakra-core/ChakraCore/issues/775 | 147,387,784 | 775 |
[
"chakra-core",
"ChakraCore"
] | Shift operations can cause SIMD lanes to be zeroed when the shift amounts are set to be greater than the lane element widths. As per the latest spec shift amounts for simd types needs to be masked to be within the lane width.
**Repro Case**
``` javascript
var v = SIMD.Int8x16(1,2,3,4,1,2,3,4,1,2,3,4,1,2,3,4);
var re... | SIMD.js: Shift amounts greater than lane width's causes simd lanes to be zeroed | https://api.github.com/repos/chakra-core/ChakraCore/issues/773/comments | 0 | 2016-04-10T01:59:41Z | 2016-04-11T18:33:41Z | https://github.com/chakra-core/ChakraCore/issues/773 | 147,183,797 | 773 |
[
"chakra-core",
"ChakraCore"
] | Eval this script:
``` javascript
function f(){}; f(f(1,
```
Chakra:
``` javascript
SyntaxError: Syntax error
```
V8:
``` javascript
function f(){}; f(f(1,
^
SyntaxError: Unexpected end of input
```
Can Chakra output a more specific **message** than `Syntax error`? (e.g. other existing Chakra... | More specific SyntaxError message | https://api.github.com/repos/chakra-core/ChakraCore/issues/767/comments | 9 | 2016-04-08T17:42:22Z | 2018-03-25T03:50:52Z | https://github.com/chakra-core/ChakraCore/issues/767 | 146,992,448 | 767 |
[
"chakra-core",
"ChakraCore"
] | ES6 specified that RegExp.prototype is no longer a RegExp object and as a result, eg. RegExp.prototype.global would result in an exception (as is our current semantics under /es6all). However this change is not web compatible and, rather than going back and making RegExp.prototype a RegExp object, the various methods s... | RegExp.prototype getters and methods need a web-compat hack | https://api.github.com/repos/chakra-core/ChakraCore/issues/760/comments | 0 | 2016-04-07T18:30:28Z | 2016-04-27T23:13:44Z | https://github.com/chakra-core/ChakraCore/issues/760 | 146,707,422 | 760 |
[
"chakra-core",
"ChakraCore"
] | It should instead consult the [[OriginalFlags]] internal slot. See https://github.com/tc39/ecma262/pull/494.
| RegExpBuiltinExec should no longer access sticky and global via getters | https://api.github.com/repos/chakra-core/ChakraCore/issues/759/comments | 0 | 2016-04-07T18:24:08Z | 2016-04-18T22:21:06Z | https://github.com/chakra-core/ChakraCore/issues/759 | 146,705,898 | 759 |
[
"chakra-core",
"ChakraCore"
] | A number of errors like this happen:
```
/home/xan/git/ChakraCore/lib/Runtime/Base/FunctionBody.cpp:1070:83: error: no matching constructor for initialization of 'Js::ProxyEntryPointInfo'
this->m_defaultEntryPointInfo = RecyclerNew(scriptContext->GetRecycler(), ProxyEntryPointInfo, DefaultDeferredDeserializeT... | FunctionBody.cpp won't compile with clang >= 3.8.0 | https://api.github.com/repos/chakra-core/ChakraCore/issues/758/comments | 7 | 2016-04-07T18:00:12Z | 2016-05-10T04:09:02Z | https://github.com/chakra-core/ChakraCore/issues/758 | 146,700,375 | 758 |
[
"chakra-core",
"ChakraCore"
] | ``` js
function Arr() {
Object.defineProperty(this, "0", {
configurable: false
});
}
try {
const arr = Array.of.call(Arr, "a");
print(JSON.stringify(arr));
} catch (error) {
print(error);
}
```
Expected result:
```
TypeError: Cannot modify non-writable property '0'
```
Actual result:
``... | Array.of should throw when it sets a non-configurable property | https://api.github.com/repos/chakra-core/ChakraCore/issues/757/comments | 4 | 2016-04-07T14:08:45Z | 2016-11-11T20:22:48Z | https://github.com/chakra-core/ChakraCore/issues/757 | 146,637,706 | 757 |
[
"chakra-core",
"ChakraCore"
] | The SIMD.Uint16x8.Equal() builtin function can return incorrect results when optimized. This happens when the simd values that is being compared has lane values beyond the bounds of uint16 type.
This issue is caused by the incorrect lowering of the comparison operation. The lowerer uses byte comparison instead of wor... | SIMD.js: SIMD.Uint16x8.Equal returns incorrect results when optimized through lowerer | https://api.github.com/repos/chakra-core/ChakraCore/issues/749/comments | 2 | 2016-04-06T17:38:32Z | 2016-04-06T23:18:21Z | https://github.com/chakra-core/ChakraCore/issues/749 | 146,383,886 | 749 |
[
"chakra-core",
"ChakraCore"
] | Scoped enums will not be usable as an array size or index in the future in MSVC.
For example:
enum class Color
{ Red, Green, Blue };
int data[Color::Blue]; // error C3411: 'Color' is not valid as the size of an array as it is not an integer type
This was allowed in previous releases of MSVC, but will not be in the ... | Fix scoped enums that are used as an array size. | https://api.github.com/repos/chakra-core/ChakraCore/issues/745/comments | 2 | 2016-04-05T23:28:38Z | 2016-04-15T02:25:01Z | https://github.com/chakra-core/ChakraCore/issues/745 | 146,137,373 | 745 |
[
"chakra-core",
"ChakraCore"
] | In medium block we use 8 pages for one block, in some cases we can have the whole last page not used. for example, if object size is 0x1600, we only uses first 7 pages and can hold 5 objects.
| Decommit unused page in medium block | https://api.github.com/repos/chakra-core/ChakraCore/issues/742/comments | 1 | 2016-04-05T19:26:31Z | 2017-05-18T16:54:46Z | https://github.com/chakra-core/ChakraCore/issues/742 | 146,086,777 | 742 |
[
"chakra-core",
"ChakraCore"
] | Today we are scanning that. PropertyRecord falls into this category. Only need to call finalizer for these objects.
And looks there's some site uses very long string (something like base64 encoded string) as property name.
| Do not scan Finalizable Leaf blocks | https://api.github.com/repos/chakra-core/ChakraCore/issues/741/comments | 1 | 2016-04-05T19:22:22Z | 2016-05-03T00:04:53Z | https://github.com/chakra-core/ChakraCore/issues/741 | 146,085,849 | 741 |
[
"chakra-core",
"ChakraCore"
] | TypeArrayBase::GetItem() always returns true (unless exception is thrown).
Investigate the impact of returning false for out-of-range.
| TypeArrayBase::GetItem() always returns true? | https://api.github.com/repos/chakra-core/ChakraCore/issues/737/comments | 1 | 2016-04-05T06:12:22Z | 2017-09-15T19:23:41Z | https://github.com/chakra-core/ChakraCore/issues/737 | 145,898,628 | 737 |
[
"chakra-core",
"ChakraCore"
] | Repro case:
ch.exe -simdjs -bgjit- -maic:0 testConversion.js
[testConversion.js.txt](https://github.com/Microsoft/ChakraCore/files/203293/testConversion.js.txt)
Will submit a PR to fix this.
| SIMD.js - Missing Float32x4.fromUint32x4 implementation in Lowerer | https://api.github.com/repos/chakra-core/ChakraCore/issues/730/comments | 3 | 2016-04-04T20:46:24Z | 2016-04-08T22:19:06Z | https://github.com/chakra-core/ChakraCore/issues/730 | 145,799,156 | 730 |
[
"chakra-core",
"ChakraCore"
] | Some SIMD.js x64test jshost failures were related to regAlloc generating bad code if casting to TyInt8. And I had to pin TyInt8 operands to a byteable register (#549).
What we want to do is cast reg2 to 1-byte then sign-extend:
```
IR::RegOpnd *reg2 = IR::RegOpnd::New(TyInt32, m_func);
IR::RegOpnd * t... | Lowerer UseWithNewType() and Legalize() counter-intuitive behavior | https://api.github.com/repos/chakra-core/ChakraCore/issues/727/comments | 2 | 2016-04-04T17:12:53Z | 2018-02-22T19:25:32Z | https://github.com/chakra-core/ChakraCore/issues/727 | 145,746,533 | 727 |
[
"chakra-core",
"ChakraCore"
] | The current implementation of SIMD store ops erroneously returns NULL (instead of Undefined). This causes a crash when merging ValueTypes during profiled interpretation, if store is used in an assignment. The correct behavior is to return the passed value, instead of Undefined.
Repro case:
[stDstBug.js.txt](https://g... | SIMD.js - Store operations return NULL instead of passed value per spec | https://api.github.com/repos/chakra-core/ChakraCore/issues/708/comments | 2 | 2016-03-31T19:09:23Z | 2016-04-12T23:48:55Z | https://github.com/chakra-core/ChakraCore/issues/708 | 144,990,842 | 708 |
[
"chakra-core",
"ChakraCore"
] | When we rejit (which means that some assumption we made in the jit is no longer true and we have bailed out enough times to realize that we want updated profile info) we disable the optimization that caused the bailouts and the rejit. Otherwise, there is a high chance that we will keep bailing out and rejitting because... | Switch optimizations are not disabled when we rejit because of them. | https://api.github.com/repos/chakra-core/ChakraCore/issues/703/comments | 1 | 2016-03-31T00:08:27Z | 2016-03-31T21:35:43Z | https://github.com/chakra-core/ChakraCore/issues/703 | 144,753,316 | 703 |
[
"chakra-core",
"ChakraCore"
] | With register pressure, RegAlloc may fold SIMD operands to be loaded from memory. Since we currently don't ensure 16-byte alignment for SIMD stack syms, this might trigger an AV.
```
// Try folding if there are no registers available
if (!sym->IsConst() && !this->RegsAvailable(regOpnd->GetType()) && EncoderMD::TryFol... | SIMD.js - RegAlloc may fold SIMD operands | https://api.github.com/repos/chakra-core/ChakraCore/issues/695/comments | 3 | 2016-03-30T19:54:55Z | 2016-04-02T00:32:19Z | https://github.com/chakra-core/ChakraCore/issues/695 | 144,702,613 | 695 |
[
"chakra-core",
"ChakraCore"
] | We have two websites based on React js. They both fail with "This page is having a problem loading". I found a crash event log and related log files but there is little information that I can find to go on.
I've compiled this archive with a static html page (sendsms, saved from Chrome) and the log files.
[msedge.zip](... | React-based site - This page is having a problem loading | https://api.github.com/repos/chakra-core/ChakraCore/issues/676/comments | 2 | 2016-03-29T11:01:05Z | 2016-04-08T08:36:22Z | https://github.com/chakra-core/ChakraCore/issues/676 | 144,228,828 | 676 |
[
"chakra-core",
"ChakraCore"
] | For a client (debugger?) to inspect Promise objects, we need APIs to access their "status" and "result".
See https://github.com/nodejs/node-chakracore/issues/41
@liminzhu @agarwal-sandeep
| Need Jsrt API to inspect Promise objects | https://api.github.com/repos/chakra-core/ChakraCore/issues/671/comments | 2 | 2016-03-28T22:48:06Z | 2018-02-21T23:46:21Z | https://github.com/chakra-core/ChakraCore/issues/671 | 144,103,436 | 671 |
[
"chakra-core",
"ChakraCore"
] | We often find bugs in ES6 because we didn't remember to run forceserialize, forceundodefer, etc. They aren't common enough to bloat unit test time, but we should periodically run them to surface bugs.
| Periodically run other RL variants, e.g. forceserialize and forceundodefer. | https://api.github.com/repos/chakra-core/ChakraCore/issues/670/comments | 3 | 2016-03-28T22:43:28Z | 2018-06-28T00:04:52Z | https://github.com/chakra-core/ChakraCore/issues/670 | 144,102,380 | 670 |
[
"chakra-core",
"ChakraCore"
] | ``` js
print(JSON.stringify(Array.from({
[Symbol.iterator]: undefined,
0: "a",
1: "b",
length: 2
})));
```
Expected output: `[ "a", "b" ]`
Actual: `TypeError: Function expected`
| Array.from should ignore @@iterator if it is undefined | https://api.github.com/repos/chakra-core/ChakraCore/issues/667/comments | 4 | 2016-03-28T21:38:53Z | 2016-04-01T00:11:27Z | https://github.com/chakra-core/ChakraCore/issues/667 | 144,090,050 | 667 |
[
"chakra-core",
"ChakraCore"
] | When forcing type-spec on a loop header, globopt wasn't taking multiple loop back edges into account. In case of more than one loop back edges, we can only force type-spec on the loop header for the first edge.
Created from [Bug 4506788](https://microsoft.visualstudio.com/DefaultCollection/OS/_workItems?_a=edit&id=450... | Bug with forcing type-specialization on loop header | https://api.github.com/repos/chakra-core/ChakraCore/issues/664/comments | 0 | 2016-03-28T18:31:36Z | 2016-04-01T19:26:13Z | https://github.com/chakra-core/ChakraCore/issues/664 | 144,046,611 | 664 |
[
"chakra-core",
"ChakraCore"
] | We are incorrectly treating taggedInt as JavascriptNumber.
Same as [OS 6980708](https://microsoft.visualstudio.com/web/wi.aspx?pcguid=cb55739e-4afe-46a3-970f-1b49d8ee7564&id=6980708)
**Details from the bug above:**
I was trying to convert something to a string in an external function. Instead of calling JsConvertVa... | JSRT APIs JsConvertValueToString and JsGetProperty fail if the input value is taggedInt instead of Object | https://api.github.com/repos/chakra-core/ChakraCore/issues/660/comments | 10 | 2016-03-28T17:30:09Z | 2019-06-07T18:49:35Z | https://github.com/chakra-core/ChakraCore/issues/660 | 144,032,913 | 660 |
[
"chakra-core",
"ChakraCore"
] | In Edge 14.14295 a data view has the incorrect [toStringTag](http://www.ecma-international.org/ecma-262/6.0/#sec-dataview.prototype-@@tostringtag).
``` js
Object.prototype.toString.call(new DataView(new ArrayBuffer(23)));
// => [object Object] instead of [object DataView]
```
| DataView does not have correct toStringTag | https://api.github.com/repos/chakra-core/ChakraCore/issues/656/comments | 4 | 2016-03-27T06:48:38Z | 2016-11-03T02:00:19Z | https://github.com/chakra-core/ChakraCore/issues/656 | 143,781,872 | 656 |
[
"chakra-core",
"ChakraCore"
] | Repro code:
```
function test0() {
class class6 {
static func88() {}
}
WScript.Echo(class6.func88.name);
}
// generate profile
test0();
```
With -forceserialized, the output is:
`class6.func88`
This is incorrect. It should be just `func88`, as it is without the flag.
Converted from [OS 6471427](https://mi... | With -forceserialized, the name of a function is not displayed correctly. | https://api.github.com/repos/chakra-core/ChakraCore/issues/652/comments | 0 | 2016-03-26T05:12:06Z | 2016-11-03T02:00:48Z | https://github.com/chakra-core/ChakraCore/issues/652 | 143,664,318 | 652 |
[
"chakra-core",
"ChakraCore"
] | ``` js
const obj = new Proxy({}, {
getPrototypeOf: null
});
print(Object.getPrototypeOf(obj));
```
This code should print `[object Object]`, but it throws `TypeError: 'getPrototypeOf' is not a function`
The trap should be ignored if it is either `undefined` or `null`, but ChackraCore only ignores it in the first ... | Proxy should ignore traps whose value is null | https://api.github.com/repos/chakra-core/ChakraCore/issues/646/comments | 2 | 2016-03-25T13:53:44Z | 2016-04-01T14:58:18Z | https://github.com/chakra-core/ChakraCore/issues/646 | 143,503,552 | 646 |
[
"chakra-core",
"ChakraCore"
] | For example:
```
async function foo() {
(await 1) = 1;
}
```
Expected: early ReferenceError
Actual: no error
| Missing early ReferenceError for some invalid simple assignment targets | https://api.github.com/repos/chakra-core/ChakraCore/issues/640/comments | 4 | 2016-03-24T19:13:17Z | 2020-03-31T15:33:07Z | https://github.com/chakra-core/ChakraCore/issues/640 | 143,334,772 | 640 |
[
"chakra-core",
"ChakraCore"
] | The test `test\es6\toPrimitiveJitBug654983.js` has disabled since late October 2015 (marked with the `fail` tag) because it was occassionally failing with spurious bailout traces in its output.
_Note the `Symbol.toPrimitive` feature is not fully implemented and may change when it is fully implemented rendering this te... | toPrimitiveJitBug654983.js test sometimes fails | https://api.github.com/repos/chakra-core/ChakraCore/issues/638/comments | 1 | 2016-03-24T00:28:55Z | 2017-06-06T22:48:43Z | https://github.com/chakra-core/ChakraCore/issues/638 | 143,113,826 | 638 |
[
"chakra-core",
"ChakraCore"
] | According to the [spec](https://tc39.github.io/ecma262/#sec-built-in-function-objects):
> Built-in function objects that are not identified as constructors do not implement the [[Construct]] internal method unless otherwise specified in the description of a particular function
Since our Intl functions are script func... | Intl functions shouldn't be constructible | https://api.github.com/repos/chakra-core/ChakraCore/issues/637/comments | 9 | 2016-03-23T23:57:54Z | 2018-08-28T15:50:50Z | https://github.com/chakra-core/ChakraCore/issues/637 | 143,109,491 | 637 |
[
"chakra-core",
"ChakraCore"
] | ``` JS
var o = {};
Object.defineProperty(o, 'test', {get: function () {}, set: function () {}});
var desc = Object.getOwnPropertyDescriptor(o, 'test');
desc.get.name === ' test';
desc.set.name === ' test';
```
The names should instead be:
``` JS
desc.get.name === 'get';
desc.set.name === 'set';
```
| Object.defineProperty assigns the wrong name to anonymous getter/setter functions | https://api.github.com/repos/chakra-core/ChakraCore/issues/626/comments | 1 | 2016-03-22T21:10:36Z | 2016-05-03T21:39:22Z | https://github.com/chakra-core/ChakraCore/issues/626 | 142,781,623 | 626 |
[
"chakra-core",
"ChakraCore"
] | I have implemented significant part of new APIs to debug ChakraCore and flushed most of bugs using debugger implemented in ch.
Before opening the PR request for merging code from JsRTDebugging to master it will be good to discuss the APIs name, signature and arguments.
Please take a look at https://github.com/Micros... | Discuss JsRTDebugging APIs | https://api.github.com/repos/chakra-core/ChakraCore/issues/619/comments | 46 | 2016-03-21T19:08:11Z | 2016-09-07T16:40:00Z | https://github.com/chakra-core/ChakraCore/issues/619 | 142,441,345 | 619 |
[
"chakra-core",
"ChakraCore"
] | string.bold() is non-standard es3 extension methods and hence not available in WWA.
ES6 adds them back to spec as part of Annex B.
| string.bold() not available for WWA (ES3 non standard). Now added back on ES6 | https://api.github.com/repos/chakra-core/ChakraCore/issues/618/comments | 3 | 2016-03-21T19:01:50Z | 2016-03-25T18:43:41Z | https://github.com/chakra-core/ChakraCore/issues/618 | 142,439,688 | 618 |
[
"chakra-core",
"ChakraCore"
] | Would like to have some way of waiting to attach debugger to ch.exe when starting up as an option.
I'm currently adding a 10 second sleep in ch.cpp
```
int _cdecl wmain(int argc, __in_ecount(argc) LPWSTR argv[])
{
if (argc < 2)
{
PrintUsage();
return EXIT_FAILURE;
}
// Use Ctrl+Alt+P ... | How can I attach a debugger to ch.exe on start up? | https://api.github.com/repos/chakra-core/ChakraCore/issues/614/comments | 5 | 2016-03-19T21:30:20Z | 2016-04-14T18:13:46Z | https://github.com/chakra-core/ChakraCore/issues/614 | 142,102,186 | 614 |
[
"chakra-core",
"ChakraCore"
] | test\Bugs\bug934443.js failing after commit 353e7d9 with AV (c0000005)
To repro, build the binary with
`jenkins\buildone.cmd x64 debug "/p:BuildJIT=false"`
Failing test is:
`Build\VcBuild.NoJIT\bin\x64_debug\ch.exe -DumpOnCrash -WERExceptionSupport -ExtendedErrorStackForTestHost -nonative -force:fieldcopyprop -off... | [Test] [Daily] [DisableJIT] test\Bugs\bug934443.js failing after commit 353e7d9 with AV (c0000005) | https://api.github.com/repos/chakra-core/ChakraCore/issues/610/comments | 1 | 2016-03-19T00:02:36Z | 2016-03-21T18:54:29Z | https://github.com/chakra-core/ChakraCore/issues/610 | 142,005,111 | 610 |
[
"chakra-core",
"ChakraCore"
] | Thanks to @evilpie for catching this looking at PR #561
``` javascript
var iter = [][Symbol.iterator]()
iter.__proto__.next = function() {
return {done: true};
};
var i32a = new Int32Array([1, 2, 3]);
for (let i = 0; i < i32a.length; i += 1) {
print(i32a[i]);
}
```
Currently prints 1, 2, 3, but should prin... | TypedArray constructor optimizes construction from array when %ArrayIteratorPrototype%.next is no longer the built-in | https://api.github.com/repos/chakra-core/ChakraCore/issues/608/comments | 2 | 2016-03-18T18:06:54Z | 2016-03-26T03:49:31Z | https://github.com/chakra-core/ChakraCore/issues/608 | 141,938,981 | 608 |
[
"chakra-core",
"ChakraCore"
] | ``` javascript
d = new Date().toLocaleString('de')
"17.03.2016 14:21:50"
// I only want to match the time part
// In chrome (v8)
d.match(/(\d+\:\d+\:\d+)/)[1]
"14:27:28" // returns the correct answer
// in edge (chakra)
d.match(/(\d+\:\d+\:\d+)/)
null
// edge matches \: correctly
d.match(/\:/)
[":",":"]
... | Intl: new Date().toLocaleString('de') puts unicode (BiDi) markers around punctuation | https://api.github.com/repos/chakra-core/ChakraCore/issues/599/comments | 18 | 2016-03-17T21:33:05Z | 2017-12-21T00:50:15Z | https://github.com/chakra-core/ChakraCore/issues/599 | 141,712,083 | 599 |
[
"chakra-core",
"ChakraCore"
] | @mmitche and I have recently made some changes to the Jenkins CI configuration to enable alternate test configurations for different branches. This should help ease the transition when CI-breaking changes are made to one branch that don't yet affect other branches. Also, it will allow e.g. the `linux` branch to define ... | [Discussion] Branch-specific Jenkins test configurations | https://api.github.com/repos/chakra-core/ChakraCore/issues/590/comments | 2 | 2016-03-16T18:05:33Z | 2018-01-17T23:19:11Z | https://github.com/chakra-core/ChakraCore/issues/590 | 141,354,757 | 590 |
[
"chakra-core",
"ChakraCore"
] | Small compatibility issue.
```
Error.stackTraceLimit = 0
new Error('abc').stack
```
Chrome: `"Error: abc"`
Edge: `undefined`
| Error.stack undefined when Error.stackTraceLimit == 0 | https://api.github.com/repos/chakra-core/ChakraCore/issues/589/comments | 2 | 2016-03-16T17:20:16Z | 2016-04-06T21:19:17Z | https://github.com/chakra-core/ChakraCore/issues/589 | 141,342,991 | 589 |
[
"chakra-core",
"ChakraCore"
] | Firefox/Chrome:
```
TypeError.prototype.toString === Error.prototype.toString
true
```
Edge: `false`
A small compatibility issue. Don't know if affects anything.
| TypeError.prototype.toString === Error.prototype.toString | https://api.github.com/repos/chakra-core/ChakraCore/issues/588/comments | 2 | 2016-03-16T16:54:20Z | 2017-09-08T13:34:32Z | https://github.com/chakra-core/ChakraCore/issues/588 | 141,333,969 | 588 |
[
"chakra-core",
"ChakraCore"
] | ChakraCore supports Error.stackTraceLimit, but not the other [StackTrace APIs in V8](https://github.com/v8/v8/wiki/Stack%20Trace%20API). Found multiple sites and nodejs modules using other APIs and incompatible with Edge / node-chakracore.
To improve compatibility, we need to consider better support of other APIs, Err... | Support Error.prepareStackTrace and Error.captureStackTrace | https://api.github.com/repos/chakra-core/ChakraCore/issues/587/comments | 6 | 2016-03-16T01:43:26Z | 2019-06-07T18:40:16Z | https://github.com/chakra-core/ChakraCore/issues/587 | 141,146,827 | 587 |
[
"chakra-core",
"ChakraCore"
] | JsCreateNamedFunction sets "functionNameId" as name. That is wrong in current code. Elsewhere we typically call
```
if (scriptContext->GetConfig()->IsES6FunctionNameEnabled())
{
object->SetPropertyWithAttributes(PropertyIds::name, functionName,
PropertyConfigurable, nullptr);... | JsCreateNamedFunction toString result is wrong | https://api.github.com/repos/chakra-core/ChakraCore/issues/586/comments | 2 | 2016-03-16T01:24:37Z | 2017-07-27T16:15:53Z | https://github.com/chakra-core/ChakraCore/issues/586 | 141,143,727 | 586 |
[
"chakra-core",
"ChakraCore"
] | `JavascriptOperators::IsIterable` calls `JavascriptOperators::GetProperty` when the object in question is a `JavascriptProxy`. This will lead to code execution in the case that the property is a getter or the proxy has a `get` trap handler installed.
The use of `IsIterable` appears to be to check whether or not to go... | `JavascriptOperators::IsIterable` can lead to script code getting executed twice instead of once | https://api.github.com/repos/chakra-core/ChakraCore/issues/584/comments | 9 | 2016-03-15T23:54:54Z | 2016-04-01T00:10:59Z | https://github.com/chakra-core/ChakraCore/issues/584 | 141,130,928 | 584 |
[
"chakra-core",
"ChakraCore"
] | ES Spec [19.1.3.6 Object.prototype.toString](https://tc39.github.io/ecma262/#sec-object.prototype.tostring)
``` js
var p = new Promise(function () {});
Object.prototype.toString.call(p);
```
Expected: "[object Promise]"
Actual: "[object Object]"
Resolved OS Bug [4646435](https://microsoft.visualstudio.com/web/wi.as... | Implement @@toStringTag in Object.prototype.toString | https://api.github.com/repos/chakra-core/ChakraCore/issues/580/comments | 3 | 2016-03-15T22:14:33Z | 2016-09-13T19:13:14Z | https://github.com/chakra-core/ChakraCore/issues/580 | 141,114,697 | 580 |
[
"chakra-core",
"ChakraCore"
] | Kangax test case:
``` JS
// RegExp.prototype.test -> RegExpExec -> Get -> [[Get]]
var get = [];
var p = new Proxy({ exec: function() { return null; } }, { get: function(o, k) { get.push(k); return o[k]; }});
RegExp.prototype.test.call(p);
return get + '' === "exec";
```
| RegExp.prototype.test should delegate to "exec" | https://api.github.com/repos/chakra-core/ChakraCore/issues/579/comments | 0 | 2016-03-15T22:11:36Z | 2016-03-17T16:19:49Z | https://github.com/chakra-core/ChakraCore/issues/579 | 141,114,166 | 579 |
[
"chakra-core",
"ChakraCore"
] | Rather than requiring `this` to be a RegExp object, the `toString` method should be generic and use the `source` and `flags` properties to generate the string. Kangax test case:
``` JS
// RegExp.prototype.toString -> Get -> [[Get]]
var get = [];
var p = new Proxy({}, { get: function(o, k) { get.push(k); return o[k]; }... | RegExp.prototype.toString should be generic | https://api.github.com/repos/chakra-core/ChakraCore/issues/578/comments | 0 | 2016-03-15T22:10:49Z | 2016-03-18T19:01:57Z | https://github.com/chakra-core/ChakraCore/issues/578 | 141,114,054 | 578 |
[
"chakra-core",
"ChakraCore"
] | We differ from the spec in two aspects.
First, when the constructor is called as a function, we should use the `constructor` property of the passed RegExp-like object to determine whether we should return the argument as is. Kangax test case:
``` JS
var re = /./;
re[Symbol.match] = false;
var foo = {constructor: RegE... | RegExp constructor should process RegExp-like Objects correctly | https://api.github.com/repos/chakra-core/ChakraCore/issues/577/comments | 0 | 2016-03-15T22:08:31Z | 2016-03-15T23:39:14Z | https://github.com/chakra-core/ChakraCore/issues/577 | 141,113,619 | 577 |
[
"chakra-core",
"ChakraCore"
] | This is an idea I got from code reviewing #561.
There are numerous built-in constructors that optionally construct from a passed in iterable. In all of these constructors we could special case arrays so long as `Array.prototype[Symbol.iterator]` hasn't changed (or rather, the `[Symbol.iterator]` property on the given... | Abstract iterable loop in built-in constructors to reduce down to one implementation that contains special case optimization for arrays | https://api.github.com/repos/chakra-core/ChakraCore/issues/571/comments | 1 | 2016-03-15T18:56:07Z | 2017-05-18T18:07:07Z | https://github.com/chakra-core/ChakraCore/issues/571 | 141,067,409 | 571 |
[
"chakra-core",
"ChakraCore"
] | Now that pre-v1.0 is completed (#440)
There are some items that needs to be fixed before we move on.
The purpose of this issue is to keep track of things we know about and intend to change.
- [x] : Break `ScripContext::LoadWasmScript()` into smaller functions
- [x] : Check if default export should be supported by spec
... | WebAssembly cleanup | https://api.github.com/repos/chakra-core/ChakraCore/issues/568/comments | 1 | 2016-03-15T18:14:42Z | 2016-12-20T00:33:18Z | https://github.com/chakra-core/ChakraCore/issues/568 | 141,056,779 | 568 |
[
"chakra-core",
"ChakraCore"
] | ```
function Foo() {
return new Error();
}
Object.defineProperty(Foo, 'name', {
value: 'something_else'
});
var x = Foo();
console.log(x.stack);
```
Edge output:
```
Error
at Foo (eval code:2:5)
at eval code (eval code:9:1)
```
Expected:
```
Error
at something_else (eval code:2:5)
...
```
| function.name not used in stack trace | https://api.github.com/repos/chakra-core/ChakraCore/issues/564/comments | 7 | 2016-03-14T23:27:44Z | 2018-02-15T00:50:19Z | https://github.com/chakra-core/ChakraCore/issues/564 | 140,825,112 | 564 |
[
"chakra-core",
"ChakraCore"
] | Observable only with ch.exe using Dev'12.
```
E:\nagy\git\chakra5\core\test\AsmJs>..\..\Build\VcBuild\bin\x86_debug\ch.exe -forceAsmJsLinkFail -DumpOnCrash -WERExceptionSupport -ExtendedErrorStackForTestHost -maxInterpretCount:1 -maxSimpleJitRunCount:1 -bgjit- -dynamicprofilecache:profile.dpl.UnnamedTest160 -bgjit- ... | Asm.js tests failing link-time validation crash | https://api.github.com/repos/chakra-core/ChakraCore/issues/560/comments | 0 | 2016-03-14T20:27:59Z | 2016-03-21T20:42:55Z | https://github.com/chakra-core/ChakraCore/issues/560 | 140,788,736 | 560 |
[
"chakra-core",
"ChakraCore"
] | If you're looking at issues in this repo then you might be a candidate to work for Microsoft on ChakraCore. We're looking for code-generation and VM enthusiasts. Holler at me EdMaurer AT microsoft.com
| The ChakraCore Team Is Hiring | https://api.github.com/repos/chakra-core/ChakraCore/issues/556/comments | 7 | 2016-03-14T02:12:43Z | 2016-08-30T01:14:20Z | https://github.com/chakra-core/ChakraCore/issues/556 | 140,557,058 | 556 |
[
"chakra-core",
"ChakraCore"
] | The current IR for i32.trunc_u/f32 is
`s20[CanBeTaggedValue_IntAndLikelyUntagged].u32 = Conv_Prim s26[CanBeTaggedValue_Float].f32 #0003`
However, `Conv_Prim` is invalid with a `uint32`
| Wasm i32.trunc_u/f32 invalid in jit | https://api.github.com/repos/chakra-core/ChakraCore/issues/555/comments | 1 | 2016-03-14T01:57:02Z | 2016-12-20T00:33:18Z | https://github.com/chakra-core/ChakraCore/issues/555 | 140,555,018 | 555 |
[
"chakra-core",
"ChakraCore"
] | Branched from issue #528
http://dotnet-ci.cloudapp.net/job/Microsoft_ChakraCore/job/daily_dev12_x64_release/51/consoleFull#1026559514ac1851af-571d-472f-b664-6657b078a5dd
```
20:38:56 d:\j\workspace\daily_dev12_x---5f770fb3\bin\ch\ch.cpp(254): warning C6102: Using 'bcBuffer' from failed function call at line '179'. [... | [Test failure] [Daily] [dev12] Legacy build PreFAST errors | https://api.github.com/repos/chakra-core/ChakraCore/issues/553/comments | 0 | 2016-03-13T03:16:10Z | 2016-03-21T17:50:41Z | https://github.com/chakra-core/ChakraCore/issues/553 | 140,441,662 | 553 |
[
"chakra-core",
"ChakraCore"
] | `function foo(a=class { }) { }`
Expected: no error
Actual:
`ASSERTION 17108: (E:\core\lib\Runtime\ByteCode\FuncInfo.cpp, line 453) childScope == scope->GetEnclosingScope()`
`Failure: (childScope == scope->GetEnclosingScope())`
`FATAL ERROR: ch.exe failed due to exception code c0000420`
| Assertion: default parameter with class expression | https://api.github.com/repos/chakra-core/ChakraCore/issues/548/comments | 2 | 2016-03-12T01:11:32Z | 2016-03-15T22:29:54Z | https://github.com/chakra-core/ChakraCore/issues/548 | 140,329,574 | 548 |
[
"chakra-core",
"ChakraCore"
] | See the following kangax test case
``` js
class C { foo(){} };
print((new C).foo.name);
```
Expected: foo
Actual: prototype.foo
| Incorrect name for class function member | https://api.github.com/repos/chakra-core/ChakraCore/issues/539/comments | 2 | 2016-03-11T19:35:34Z | 2016-03-16T18:42:43Z | https://github.com/chakra-core/ChakraCore/issues/539 | 140,271,991 | 539 |
[
"chakra-core",
"ChakraCore"
] | See the following kangax test case
``` js
print((function()
{
var promise = new Promise(function(resolve){ resolve(42); });
var FakePromise1 = promise.constructor = function(exec){ exec(function(){}, function(){}); };
var FakePromise2 = function(exec){ exec(function(){}, function(){}); };
Object.defineProperty(F... | Symbol.species does not work with Promise.prototype.then | https://api.github.com/repos/chakra-core/ChakraCore/issues/538/comments | 1 | 2016-03-11T19:30:34Z | 2016-03-19T02:14:27Z | https://github.com/chakra-core/ChakraCore/issues/538 | 140,270,532 | 538 |
[
"chakra-core",
"ChakraCore"
] | Expected true from both the following test cases. Actual: false
This is a kangax test case
``` js
print((function()
{
// Object.prototype.__lookupGetter__ -> [[GetOwnProperty]]
// Object.prototype.__lookupGetter__ -> [[GetPrototypeOf]]
var gopd = [];
var gpo = false;
var p = new Proxy({},
{ getPrototypeOf: function(... | Proxy traps not triggered for __lookupGetter and __lookupSetter_ | https://api.github.com/repos/chakra-core/ChakraCore/issues/535/comments | 5 | 2016-03-11T19:10:30Z | 2016-05-11T17:48:31Z | https://github.com/chakra-core/ChakraCore/issues/535 | 140,265,789 | 535 |
[
"chakra-core",
"ChakraCore"
] | Follow-up #48
Depends on #512
After #512 is merged in, the stubbed-out scripts in the root directory will not be needed anymore for CI checks to pass. They can (and should) be safely deleted.
| CI: Follow-up #48: Remove defunct stubbed jenkins scripts from root directory | https://api.github.com/repos/chakra-core/ChakraCore/issues/529/comments | 0 | 2016-03-11T01:33:55Z | 2016-03-11T06:52:42Z | https://github.com/chakra-core/ChakraCore/issues/529 | 140,060,062 | 529 |
[
"chakra-core",
"ChakraCore"
] | Since the same issues have been there for a while I wanted to open an issue to track.
@nmostafa is investigating and can potentially provide more info on the investigation in this issue.
When these breaks are resolved we can move forward with #330.
See: https://github.com/Microsoft/ChakraCore/wiki/Build-Status#lega... | [Test failure] [Daily] [dev12] Legacy build fails unit tests | https://api.github.com/repos/chakra-core/ChakraCore/issues/528/comments | 10 | 2016-03-11T01:05:01Z | 2016-03-16T17:47:19Z | https://github.com/chakra-core/ChakraCore/issues/528 | 140,055,021 | 528 |
[
"chakra-core",
"ChakraCore"
] | There is an issue in multiple JavascriptArray methods when handling numeric propertyId. Needs a thorough review of JavascriptArray/ES5Array methods. We rarely hit these code paths because we usually call uint32 index methods. With JSRT, one can create a numeric propertyId and use it to access an array.
E.g., compare 2... | JavascriptArray bugs in numeric propertyId handling | https://api.github.com/repos/chakra-core/ChakraCore/issues/526/comments | 5 | 2016-03-10T23:42:50Z | 2019-06-07T18:39:57Z | https://github.com/chakra-core/ChakraCore/issues/526 | 140,041,634 | 526 |
[
"chakra-core",
"ChakraCore"
] | Annex B.1.4 contains exceptions that allow web browsers to diverge from the normal RegExp grammar. These exceptions aren't allowed when the "unicode" flag is present, but our current implementation doesn't take this into account.
There are many exceptions, but a few examples would be:
- PatternCharacter: {
- Character... | [RegExp] Exceptions for RegExp in Annex B of the ES2017 spec shouldn't be applied when the "unicode" flag is present | https://api.github.com/repos/chakra-core/ChakraCore/issues/518/comments | 1 | 2016-03-10T20:02:00Z | 2019-06-07T18:39:53Z | https://github.com/chakra-core/ChakraCore/issues/518 | 139,994,097 | 518 |
[
"chakra-core",
"ChakraCore"
] | When we generate the character casing equivalence sets for RegExp using [UnicodeData.txt](http://ftp.unicode.org/Public/UNIDATA/UnicodeData.txt), we start from lowercase letters and then add the characters that they map to. However, this misses non-letter characters. For example, '\u0345', which is in the "Mn" (Mark, N... | [RegExp] case-insensitive matching misses characters | https://api.github.com/repos/chakra-core/ChakraCore/issues/517/comments | 5 | 2016-03-10T19:58:34Z | 2017-01-14T00:05:30Z | https://github.com/chakra-core/ChakraCore/issues/517 | 139,993,181 | 517 |
[
"chakra-core",
"ChakraCore"
] | ``` javascript
// repro, expected to print "X" but prints "undefined"
function* foo() {
var x = yield 1;
print(x);
}
function* bar() {
yield* foo();
}
var it = bar();
it.next();
it.next("X");
```
From VSO bug [6790309](https://microsoft.visualstudio.com/web/wi.aspx?pcguid=cb55739e-4afe-46a3-970f-1b49d8ee7... | yield* does not forward .next() argument to iterable's .next() call | https://api.github.com/repos/chakra-core/ChakraCore/issues/510/comments | 5 | 2016-03-10T03:47:39Z | 2016-03-10T23:43:54Z | https://github.com/chakra-core/ChakraCore/issues/510 | 139,776,303 | 510 |
[
"chakra-core",
"ChakraCore"
] | ``` javascript
"use strict";
var await = 0;
```
throws a SyntaxError.
`await` is being treated as a FutureReservedWord in all scripts, like `yield`, meaning it is disallowed in strict mode. However, the ES6 spec states that `await` is only treated this way for module scripts.
| `await` incorrectly disallowed as identifier in strict mode | https://api.github.com/repos/chakra-core/ChakraCore/issues/507/comments | 0 | 2016-03-10T02:09:39Z | 2016-03-10T03:21:55Z | https://github.com/chakra-core/ChakraCore/issues/507 | 139,760,881 | 507 |
[
"chakra-core",
"ChakraCore"
] | ``` javascript
function test3() {
var k = 1;
d = 2;
let d;
}
test3();
```
Emits
```
ReferenceError: Use before declaration
at test3 (e:\chgittest\bug8.js:2:3)
at Global code (e:\chgittest\bug8.js:6:1)
```
The line number should be 3.
`EmitUseBeforeDeclaration`does not have enclosing `Start/End Statemen... | Use before declaration error has wrong line number. | https://api.github.com/repos/chakra-core/ChakraCore/issues/505/comments | 2 | 2016-03-10T01:34:10Z | 2016-05-12T00:14:13Z | https://github.com/chakra-core/ChakraCore/issues/505 | 139,755,035 | 505 |
[
"chakra-core",
"ChakraCore"
] | `JsDeleteIndexedProperty` API does not tell if the deletion is successful or not, unlike `JsDeleteProperty` which returns that info in "result". The former also misses "useStrictRules" flag which exists in the later.
```
JsDeleteIndexedProperty(JsValueRef object, JsValueRef index)
JsDeleteProperty(JsValueRef object, ... | JSRT: JsDeleteIndexedProperty does not tell successful or not | https://api.github.com/repos/chakra-core/ChakraCore/issues/504/comments | 10 | 2016-03-10T00:48:30Z | 2018-06-06T23:39:27Z | https://github.com/chakra-core/ChakraCore/issues/504 | 139,747,727 | 504 |
[
"chakra-core",
"ChakraCore"
] | Ensure that the check includes exceptions for tool-generated (or tool-modified) files like .sln and .vcxproj. | Augment EOL Check to catch missing newline at EOF | https://api.github.com/repos/chakra-core/ChakraCore/issues/496/comments | 12 | 2016-03-09T18:59:43Z | 2018-08-28T01:21:14Z | https://github.com/chakra-core/ChakraCore/issues/496 | 139,669,112 | 496 |
[
"chakra-core",
"ChakraCore"
] | Do you have plan to support native (or without transpiling) TypeScript in ChakraCore? | https://api.github.com/repos/chakra-core/ChakraCore/issues/494/comments | 3 | 2016-03-09T13:55:29Z | 2016-03-26T02:37:48Z | https://github.com/chakra-core/ChakraCore/issues/494 | 139,583,590 | 494 | |
[
"chakra-core",
"ChakraCore"
] | To catch situations where files are introduced where some portion of the path differs only in casing under e.g. both `Lib` and `lib` directories, or files which have the same name except casing being introduced under Linux (non-case-sensitive file system), which can cause problems in case-insensitive file systems like ... | Add check for case conflation in directories or files | https://api.github.com/repos/chakra-core/ChakraCore/issues/484/comments | 1 | 2016-03-08T20:51:28Z | 2018-01-17T23:23:51Z | https://github.com/chakra-core/ChakraCore/issues/484 | 139,389,896 | 484 |
[
"chakra-core",
"ChakraCore"
] | Chakra doesn't throw a SyntaxError for this code:
``` js
({ [ 1, 2 ]: 3 });
```
but the specification defines [`ComputedPropertyName`](https://tc39.github.io/ecma262/#prod-ComputedPropertyName) as `[ AssignmentExpression ]`
| Expression shouldn't be allowed as computed property name | https://api.github.com/repos/chakra-core/ChakraCore/issues/472/comments | 9 | 2016-03-06T14:33:29Z | 2016-03-10T03:17:55Z | https://github.com/chakra-core/ChakraCore/issues/472 | 138,795,759 | 472 |
[
"chakra-core",
"ChakraCore"
] | I have ProcDump set to create full minidumps whenever a process crashes.
Yesterday my girlfriend was using Edge and told me that there was a problem.
I do not know the problematic URL or reproduction steps.
But I checked dumps folder and sure enough one of the tabs had crashed.
I can provide the dump itself, but it is ... | Access violation -- Js::DebugManager::Close+0xf | https://api.github.com/repos/chakra-core/ChakraCore/issues/470/comments | 5 | 2016-03-06T01:21:43Z | 2016-03-10T22:20:26Z | https://github.com/chakra-core/ChakraCore/issues/470 | 138,741,713 | 470 |
[
"chakra-core",
"ChakraCore"
] | `wchar_t` and `L"..."` use 2-byte chars on Windows but 4-byte chars on Unix. We need a common representation for cross-platform. We have been experimenting with `wchar16` and `CH_WSTR` in "linux" branch, and realized that's a lot of code noise and would probably result in merge hell. We would like to do a batch replace... | cross-plat: wrap wchar type and string literal | https://api.github.com/repos/chakra-core/ChakraCore/issues/456/comments | 23 | 2016-03-04T19:29:57Z | 2016-03-08T01:18:38Z | https://github.com/chakra-core/ChakraCore/issues/456 | 138,564,475 | 456 |
[
"chakra-core",
"ChakraCore"
] | Hi,
Running the following code in Edge:
```
new Worker(URL.createObjectURL(new Blob([`
var p = Promise.resolve();
p.then(x => console.log("#1"));
p.then(x => console.log("#2"));
`], {type: 'text/javascript'})));
```
prints:
```
#2
#1
```
I think the expected output should be `#1 #2`, according to https://pro... | Promise subscriptions fire in reversed order inside a Worker | https://api.github.com/repos/chakra-core/ChakraCore/issues/451/comments | 3 | 2016-03-04T10:53:37Z | 2016-03-07T20:13:19Z | https://github.com/chakra-core/ChakraCore/issues/451 | 138,443,736 | 451 |
[
"chakra-core",
"ChakraCore"
] | jenkins.buildall.cmd is a convenience script for desktop users who want to build all of the flavors locallly in the same way that jenkins builds them. The script is not used by any automated systems. It defers to the same logic used by the other scripts but ignores any parameters passed.
Might be as easy as adding %\*... | jenkins.buildall.cmd ignores extra parameters | https://api.github.com/repos/chakra-core/ChakraCore/issues/442/comments | 0 | 2016-03-03T22:28:13Z | 2016-03-08T01:22:25Z | https://github.com/chakra-core/ChakraCore/issues/442 | 138,315,900 | 442 |
[
"chakra-core",
"ChakraCore"
] | The WebAssembly spec changed quite a bit recently and we have to update our implementation.
This is a list of things to do
- [ ] : Add `Wasm` Object to the global object (#430)
- [x] : Add `instantiateModule` method to the `Wasm` Object. (In review #486 + #430)
- Takes 2 arguments
- TypedArrayView with the bytes... | WebAssembly pre-v1.0 update | https://api.github.com/repos/chakra-core/ChakraCore/issues/440/comments | 14 | 2016-03-03T20:51:26Z | 2016-12-20T00:33:18Z | https://github.com/chakra-core/ChakraCore/issues/440 | 138,293,748 | 440 |
[
"chakra-core",
"ChakraCore"
] | Last remaining file in lib/Common/Common. This one is harder since it has dependencies on Win32 time APIs that are not implemented in the PAL (TzSpecificLocalTimeToSystemTime and friends)
| [linux] Get DaylightTimeHelper.cpp to compile | https://api.github.com/repos/chakra-core/ChakraCore/issues/437/comments | 1 | 2016-03-03T03:39:46Z | 2016-09-07T10:26:51Z | https://github.com/chakra-core/ChakraCore/issues/437 | 138,066,178 | 437 |
[
"chakra-core",
"ChakraCore"
] | eg.
``` javascript
var a = undefined
a[Object(Symbol())] = 10;
```
as `a`is undefined we throw a type error. While throwing, we are trying to get string from that property to populate error information, which makes `ToString`call to that property (in this scenario that property is `Symbol`).
Is this implicit `ToStri... | Throwing an error causes ToString call on a property, and that property is a Symbol. | https://api.github.com/repos/chakra-core/ChakraCore/issues/435/comments | 3 | 2016-03-03T02:15:42Z | 2016-03-16T19:56:16Z | https://github.com/chakra-core/ChakraCore/issues/435 | 138,053,605 | 435 |
[
"chakra-core",
"ChakraCore"
] | say for
`String(Object(Symbol()));`
We throw : `TypeError: Object doesn't support property or method 'ToString'`
There were suggestion made in #422 to make it more descriptive.
| Fix the message for implicit Symbol.toString to make it more descriptive | https://api.github.com/repos/chakra-core/ChakraCore/issues/434/comments | 2 | 2016-03-03T01:35:14Z | 2018-10-08T16:24:36Z | https://github.com/chakra-core/ChakraCore/issues/434 | 138,046,950 | 434 |
[
"chakra-core",
"ChakraCore"
] | Currently the error message we print is "Cannot modify non-writable property" while it should be "Cannot redefine non-configurable property"
| Fix error message for changing [[Writable]] to true from false for non-configurable properties | https://api.github.com/repos/chakra-core/ChakraCore/issues/424/comments | 4 | 2016-03-01T20:11:51Z | 2017-08-15T16:10:49Z | https://github.com/chakra-core/ChakraCore/issues/424 | 137,674,497 | 424 |
[
"chakra-core",
"ChakraCore"
] | For example, `'ß'.toUpperCase() === 'SS'` should be true, but Chakra doesn't handle that character and it's `'ß'.toUpperCase() === 'ß'` instead.
The list of such characters are maintained in the [SpecialCasing.txt](http://unicode.org/Public/UNIDATA/SpecialCasing.txt) file.
| Unicode: String.prototype.{toUpperCase,toLowerCase} don't handle characters that would increase the string length | https://api.github.com/repos/chakra-core/ChakraCore/issues/421/comments | 5 | 2016-03-01T18:10:19Z | 2018-03-20T20:32:17Z | https://github.com/chakra-core/ChakraCore/issues/421 | 137,646,706 | 421 |
[
"chakra-core",
"ChakraCore"
] | "Windows 7 daily_dev12_x64_test" caused all of the dev12 dailies to be triggered in https://github.com/Microsoft/ChakraCore/pull/417
It matches the regex trigger for all Dev12 builds because "Windows 7" would match, and also "dev12" would match.
See set of regex triggers:
```
daily_dev12_x64_debug_prtest.xml: ... | Trigger phrases like "Windows 7 daily_dev12_x64_test" cause all Windows 7 dailies to be triggered | https://api.github.com/repos/chakra-core/ChakraCore/issues/418/comments | 0 | 2016-03-01T01:03:34Z | 2016-03-01T21:47:05Z | https://github.com/chakra-core/ChakraCore/issues/418 | 137,430,305 | 418 |
[
"chakra-core",
"ChakraCore"
] | I've been tracking this for a while but realized there's no issue open for it.
There is an access violation (0xc0000005) in 14 tests in x64_test
Present since:
http://dotnet-ci.cloudapp.net/job/Microsoft_ChakraCore/job/daily_dev12_x64_test/31/
Latest failure:
http://dotnet-ci.cloudapp.net/job/Microsoft_ChakraCore/jo... | [Test failure] [Daily] [Dev12 x64_test] Access violation (0xc0000005) in some tests. | https://api.github.com/repos/chakra-core/ChakraCore/issues/410/comments | 1 | 2016-02-29T20:01:39Z | 2016-03-02T22:58:20Z | https://github.com/chakra-core/ChakraCore/issues/410 | 137,355,898 | 410 |
[
"chakra-core",
"ChakraCore"
] | AFAIK our intention is to always canonicalize so this should be fixed. Note that this only repros in Edge, not in ch.exe.
``` js
function numberToRawBits(v) {
var isLittleEndian = new Uint8Array(new Uint16Array([1]).buffer)[0] === 1;
var reduce = Array.prototype[isLittleEndian ? 'reduceRight' : 'reduce'];
var ui... | NaN and -NaN can give different bit patterns | https://api.github.com/repos/chakra-core/ChakraCore/issues/398/comments | 3 | 2016-02-26T18:00:32Z | 2019-01-29T01:22:13Z | https://github.com/chakra-core/ChakraCore/issues/398 | 136,768,011 | 398 |
[
"chakra-core",
"ChakraCore"
] | test case
``` javascript
var map = new Map();
map.set(1 , "value");
console.assert(map.get(1) , "ok");
var key = 1.1;
key -= 0.1;
// will assert because "key" is double , and 1 is int
console.assert(map.get(key) , "not ok");
```
| Map.get bug with hash code calc | https://api.github.com/repos/chakra-core/ChakraCore/issues/390/comments | 4 | 2016-02-25T07:16:46Z | 2016-03-22T22:04:23Z | https://github.com/chakra-core/ChakraCore/issues/390 | 136,303,775 | 390 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.