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"
] | WASM - Enable int64 const prop (5d) | https://api.github.com/repos/chakra-core/ChakraCore/issues/3475/comments | 1 | 2017-08-03T22:12:14Z | 2017-08-03T22:24:35Z | https://github.com/chakra-core/ChakraCore/issues/3475 | 247,850,369 | 3,475 | |
[
"chakra-core",
"ChakraCore"
] | WASM - Tail recursion (2w) | https://api.github.com/repos/chakra-core/ChakraCore/issues/3474/comments | 1 | 2017-08-03T22:06:17Z | 2018-02-27T19:34:13Z | https://github.com/chakra-core/ChakraCore/issues/3474 | 247,849,105 | 3,474 | |
[
"chakra-core",
"ChakraCore"
] | #3420 removes tzdata sync calls from xplat DateTime interface due to 10X performance penalty and other concerns mentioned in the same PR. Please read the discussion made under https://github.com/Microsoft/ChakraCore/pull/3420 ( Thanks to @MSLaguana @dilijev for their valuable contributions there)
/cc @bterlson | xplat: ChakraCore doesn't update process tzdata if system timezone changes | https://api.github.com/repos/chakra-core/ChakraCore/issues/3467/comments | 0 | 2017-08-02T16:24:05Z | 2017-08-02T16:24:32Z | https://github.com/chakra-core/ChakraCore/issues/3467 | 247,447,681 | 3,467 |
[
"chakra-core",
"ChakraCore"
] | When the generator object is created we save the interpreterstackframe in it. If we dynamically attach a debugger to it, both the offset and register allocation in the bytecode may defer from the previous values. This will cause issues when we try to continue after an yield from the saved offset. This needs to be fixed... | Fix the dynamic attach scenario for generators | https://api.github.com/repos/chakra-core/ChakraCore/issues/3453/comments | 1 | 2017-07-29T06:40:54Z | 2019-06-07T18:34:30Z | https://github.com/chakra-core/ChakraCore/issues/3453 | 246,503,821 | 3,453 |
[
"chakra-core",
"ChakraCore"
] | > The reserved immediate to the current_memory and grow_memory operators is for future π¦ use and must be 0 in the MVP.
The call_indirect operator takes a list of function arguments and as the last operand the index into the table. Its reserved immediate is for future π¦ use and must be 0 in the MVP.
Currently we j... | WASM: Reserved immediate | https://api.github.com/repos/chakra-core/ChakraCore/issues/3450/comments | 0 | 2017-07-28T18:27:43Z | 2017-08-03T17:27:56Z | https://github.com/chakra-core/ChakraCore/issues/3450 | 246,424,551 | 3,450 |
[
"chakra-core",
"ChakraCore"
] | https://github.com/tc39/proposal-regexp-lookbehind | Implement RegExp lookbehind assertions | https://api.github.com/repos/chakra-core/ChakraCore/issues/3448/comments | 2 | 2017-07-28T07:42:02Z | 2018-11-21T17:17:50Z | https://github.com/chakra-core/ChakraCore/issues/3448 | 246,271,248 | 3,448 |
[
"chakra-core",
"ChakraCore"
] | I've been noticing this for years and I think I reported an old connect bug along these lines, but if you take some method heavy JS and run it in different engines, Chakra always seems to come out the worst for wear and you generally need to manually inline along the hot paths to normalize performance. I was trying to ... | Chakra doesn't seem to inline very well compared to other JS jit implementations. | https://api.github.com/repos/chakra-core/ChakraCore/issues/3442/comments | 1 | 2017-07-27T16:41:44Z | 2017-08-10T23:54:35Z | https://github.com/chakra-core/ChakraCore/issues/3442 | 246,101,225 | 3,442 |
[
"chakra-core",
"ChakraCore"
] | Hello,
I've developed COM component based on chakra engine.
I'm building it one a machine where IE11 is installed. I link with jsrt.lib
When I'm running it on another machine with IE11 installed it works fine, but when I come to register it on a machine with IE10 I get the following Error "The Procedure entry poin... | Got a message JSStringToPointer could not be located in jscript9 | https://api.github.com/repos/chakra-core/ChakraCore/issues/3441/comments | 3 | 2017-07-27T06:55:06Z | 2017-08-10T23:55:57Z | https://github.com/chakra-core/ChakraCore/issues/3441 | 245,942,854 | 3,441 |
[
"chakra-core",
"ChakraCore"
] | This may be a spec issue. However, showing 2 calls corresponding to one call in the user code might be misleading.
Run the following with "ch -Intl -debugLaunch"
```js
var options = { ca: "gregory", hour12: true, timeZone:"UTC" };
var dateFormat1 = new Intl.DateTimeFormat("en-US", options); /**bp:resume('step... | For some Intl function calls where getters are fired, debugger shows 2 calls. | https://api.github.com/repos/chakra-core/ChakraCore/issues/3439/comments | 5 | 2017-07-27T01:32:52Z | 2017-09-07T00:38:04Z | https://github.com/chakra-core/ChakraCore/issues/3439 | 245,900,663 | 3,439 |
[
"chakra-core",
"ChakraCore"
] | It seems an internal anonymous function call during the constructor's execution is being shown in the debugger output.
Run the following with "ch -Intl -debugLaunch"
```js
var options = { ca: "gregory", hour12: true, timeZone:"UTC" };
var dateFormat1 = new Intl.DateTimeFormat("en-US", options); /**bp:resume('... | Intl.js: when the outer function of Intl.js is called (Intl lazy-init), it appears in the debugger dump | https://api.github.com/repos/chakra-core/ChakraCore/issues/3438/comments | 3 | 2017-07-27T01:23:05Z | 2017-07-28T22:11:33Z | https://github.com/chakra-core/ChakraCore/issues/3438 | 245,899,418 | 3,438 |
[
"chakra-core",
"ChakraCore"
] | Repro:
build chakracore on linux:
./build.sh --cc=/usr/bin/clang --cxx=/usr/bin/clang++ --arch=amd64 --debug --static -j 8 --sanitize=address,undefined,signed-integer-overflow
run `./ch -` from `/out/Debug/bin/ch`
output:
==67392==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000eec4 at pc... | Heap overflow in CreateTTDDirectoryAsNeeded | https://api.github.com/repos/chakra-core/ChakraCore/issues/3434/comments | 6 | 2017-07-26T01:25:00Z | 2017-08-22T15:10:04Z | https://github.com/chakra-core/ChakraCore/issues/3434 | 245,579,455 | 3,434 |
[
"chakra-core",
"ChakraCore"
] | From ``Microsoft.ChakraCore.props``, before copying the dorrect dll to the build output, it seems that the it checks if a `packages.config` exists, which is not the case if your project is using a `project.json` file. | Nuget package Microsoft.ChakraCore doesn't work with solution that uses project.json | https://api.github.com/repos/chakra-core/ChakraCore/issues/3431/comments | 1 | 2017-07-25T21:39:02Z | 2018-05-31T00:31:57Z | https://github.com/chakra-core/ChakraCore/issues/3431 | 245,543,420 | 3,431 |
[
"chakra-core",
"ChakraCore"
] | This commit https://github.com/Microsoft/ChakraCore/commit/9020556559a551daccc5df885cfd19f34a4716f5 added new code which casts string literal to 'uint16 *'. This is not allowed by the standard and /permissive- will catch it:
JsRTApiTest.cpp(2151): error C2440: 'reinterpret_cast': cannot convert from 'const wchar_t... | Issues found when building with MSVC + /permissive- - 3 | https://api.github.com/repos/chakra-core/ChakraCore/issues/3430/comments | 0 | 2017-07-25T19:23:04Z | 2018-05-31T00:31:57Z | https://github.com/chakra-core/ChakraCore/issues/3430 | 245,508,191 | 3,430 |
[
"chakra-core",
"ChakraCore"
] | See: https://github.com/Microsoft/ChakraCore/issues/3204#issuecomment-313806817
The current spec (and proposed, see [proposal](https://tc39.github.io/Function-prototype-toString-revision/#sec-function.prototype.tostring) also linked from the comment above) require that a the toString of a built-in function object ma... | Include function name in built-in function toString (Intl functions) | https://api.github.com/repos/chakra-core/ChakraCore/issues/3427/comments | 0 | 2017-07-25T02:39:30Z | 2018-08-28T15:50:50Z | https://github.com/chakra-core/ChakraCore/issues/3427 | 245,269,191 | 3,427 |
[
"chakra-core",
"ChakraCore"
] | ```javascript
class B {
set x(v) { print("B.prototype.set x"); this._x = v; }
get x() { print("B.prototype.get x"); return this._x; }
}
class A extends B {
set x(v) { print("A.prototype.set x"); super.x = v + 100; }
get x() { print("A.prototype.get x"); return super.x; }
}
var a = new A();
... | Repeated calls to class setter triggers assertion | https://api.github.com/repos/chakra-core/ChakraCore/issues/3423/comments | 2 | 2017-07-24T22:36:58Z | 2017-08-11T18:13:32Z | https://github.com/chakra-core/ChakraCore/issues/3423 | 245,229,838 | 3,423 |
[
"chakra-core",
"ChakraCore"
] | CCRobot found an issue on master branch;
command line;
```
out/Test/ch -WERExceptionSupport -ExtendedErrorStackForTestHost -BaselineMode -forceNative -off:simpleJit -bgJitDelay:0 -dynamicprofileinput:profile.dpl.2047 -force:deferparse -args summary -endargs /home/helixbot/dotnetbuild/work/f4c635b9-0126-4e05-bca5-b... | crash: es6/default-splitscope.js crashes randomly [master] | https://api.github.com/repos/chakra-core/ChakraCore/issues/3419/comments | 2 | 2017-07-23T18:35:50Z | 2018-05-31T00:31:57Z | https://github.com/chakra-core/ChakraCore/issues/3419 | 244,927,682 | 3,419 |
[
"chakra-core",
"ChakraCore"
] | Both IE and Edge is missing `tooShort` property of `validity` property.
See [ValidityState specification](https://www.w3.org/TR/html5/forms.html#validitystate) and [compare with MSDN](https://msdn.microsoft.com/en-us/library/hh772951(v=vs.85).aspx).
Meaning of `tooShort` from spec:
> Suffering from being too ... | validity property of type ValidityState is missing tooShort property | https://api.github.com/repos/chakra-core/ChakraCore/issues/3410/comments | 3 | 2017-07-20T23:45:18Z | 2017-07-31T23:18:50Z | https://github.com/chakra-core/ChakraCore/issues/3410 | 244,527,008 | 3,410 |
[
"chakra-core",
"ChakraCore"
] | There are a number of cases that are currently not working properly, for example:
```js
function foo(a = function () { }) { return a; }
print(foo().name);
```
Expected: 'a'
Actual: ''
This appears to be fixed with the ES6FunctionName flag - we should consider enabling this. Anyone know why this isn't yet ena... | Enable ES6 function name inference | https://api.github.com/repos/chakra-core/ChakraCore/issues/3407/comments | 6 | 2017-07-20T22:03:18Z | 2020-03-25T17:13:13Z | https://github.com/chakra-core/ChakraCore/issues/3407 | 244,509,733 | 3,407 |
[
"chakra-core",
"ChakraCore"
] | The proposal is stage 3 and will very likely be in ES2018. Object rest and spread are very useful tools (especially in some ecosystems like React) and idioms from it are becoming more common (eg. shallow copy via `let copy = { ... otherObj };`)
Specification text: https://github.com/tc39/proposal-object-rest-spread | Implement Object Rest & Spread | https://api.github.com/repos/chakra-core/ChakraCore/issues/3406/comments | 19 | 2017-07-20T21:44:10Z | 2019-07-01T19:16:30Z | https://github.com/chakra-core/ChakraCore/issues/3406 | 244,505,438 | 3,406 |
[
"chakra-core",
"ChakraCore"
] | ```js
let x;
eval('var x');
```
Expected: early syntax error when doing EvalDeclarationInstantiation
Actual: Runtime Let/Const Redeclaration error. | Direct eval variable declaration with same name as outer lexical binding should be early syntax error | https://api.github.com/repos/chakra-core/ChakraCore/issues/3405/comments | 0 | 2017-07-20T21:34:31Z | 2019-06-07T18:26:25Z | https://github.com/chakra-core/ChakraCore/issues/3405 | 244,503,400 | 3,405 |
[
"chakra-core",
"ChakraCore"
] | ```js
Object.defineProperty(this, 'f', {
enumerable: true,
writable: true,
configurable: false
});
print(JSON.stringify(Object.getOwnPropertyDescriptor(this, 'f')));
eval('function f() { return 2222; }');
print(JSON.stringify(Object.getOwnPropertyDescriptor(this, 'f')));
```
Expected: descriptor doe... | Global declarations created inside eval should not change configurability of existing properties | https://api.github.com/repos/chakra-core/ChakraCore/issues/3404/comments | 0 | 2017-07-20T21:29:46Z | 2018-08-01T00:41:52Z | https://github.com/chakra-core/ChakraCore/issues/3404 | 244,502,374 | 3,404 |
[
"chakra-core",
"ChakraCore"
] | String properties should be enumerated in creation order. For classes, this should be `length`, `prototype`, string-based static keys of the class, and finally `name`. | Enumeration order of class properties is incorrect | https://api.github.com/repos/chakra-core/ChakraCore/issues/3396/comments | 0 | 2017-07-19T21:58:52Z | 2019-06-07T19:08:50Z | https://github.com/chakra-core/ChakraCore/issues/3396 | 244,186,771 | 3,396 |
[
"chakra-core",
"ChakraCore"
] | Given something of the form:
```js
{
function foo() { }
function foo() { }
}
```
where either function might be a regular function, generator, async function, or class:
Expected: error (static semantics contains duplicate lexical declaration)
Actual: no error | Declarations (other than var) within the same block should throw in all modes | https://api.github.com/repos/chakra-core/ChakraCore/issues/3395/comments | 0 | 2017-07-19T21:35:00Z | 2019-06-07T18:43:26Z | https://github.com/chakra-core/ChakraCore/issues/3395 | 244,181,472 | 3,395 |
[
"chakra-core",
"ChakraCore"
] | ```js
function foo(a) {
Object.defineProperty(arguments, "0", {configurable: false});
var args = arguments;
(function() { "use strict";
delete args[0];
})();
}
foo(1);
```
Expected: TypeError, deleting non-configurable property in strict mode
Actual: No error | Arguments object properties should throw an error when non-configurable | https://api.github.com/repos/chakra-core/ChakraCore/issues/3394/comments | 2 | 2017-07-19T21:02:00Z | 2019-06-07T18:43:18Z | https://github.com/chakra-core/ChakraCore/issues/3394 | 244,172,989 | 3,394 |
[
"chakra-core",
"ChakraCore"
] | The spec does not require that these are present as of ES2017 (see the [final note](https://tc39.github.io/ecma262/#sec-arguments-exotic-objects) of this clause). | Remove strict mode poisoning of 'caller' from arguments object | https://api.github.com/repos/chakra-core/ChakraCore/issues/3393/comments | 2 | 2017-07-19T20:23:59Z | 2017-07-28T17:12:18Z | https://github.com/chakra-core/ChakraCore/issues/3393 | 244,162,917 | 3,393 |
[
"chakra-core",
"ChakraCore"
] | Seems this option was added after Dev12 (compiler toolchain used by the legacy configuration).
`cl : Command line warning D9002: ignoring unknown option '-Zc:implicitNoexcept-'`
See: https://ci2.dot.net/job/Microsoft_ChakraCore/job/release_1.6/job/daily_dev12_x86_debug/36 | [Legacy config] cl : Command line warning D9002: ignoring unknown option '-Zc:implicitNoexcept-' | https://api.github.com/repos/chakra-core/ChakraCore/issues/3388/comments | 1 | 2017-07-18T21:24:41Z | 2018-03-01T05:00:10Z | https://github.com/chakra-core/ChakraCore/issues/3388 | 243,856,090 | 3,388 |
[
"chakra-core",
"ChakraCore"
] | https://github.com/Microsoft/ChakraCore/wiki/Build-Status-%28release-1.6%29#legacy-builds
https://ci2.dot.net/job/Microsoft_ChakraCore/job/release_1.6/job/daily_dev12_x86_debug/
```
D:\j\workspace\daily_dev12_x---006604c1\lib\Runtime\Language\i386\AsmJsJitTemplate.cpp(534): error C2220: warning treated as error - ... | [Legacy x86 debug 1.6, 1.7, master] Build failure (warn as error: unused variable) related to SIMD code removal | https://api.github.com/repos/chakra-core/ChakraCore/issues/3387/comments | 0 | 2017-07-18T21:16:56Z | 2017-07-19T01:00:12Z | https://github.com/chakra-core/ChakraCore/issues/3387 | 243,854,199 | 3,387 |
[
"chakra-core",
"ChakraCore"
] | ```js
'use strict';
var \u0079ield = 1
```
Expected: SyntaxError (yield is a reserved identifier)
Actual: No Error | Yield created with an escape sequence should be an error in strict mode | https://api.github.com/repos/chakra-core/ChakraCore/issues/3376/comments | 0 | 2017-07-17T18:32:31Z | 2017-07-21T18:55:12Z | https://github.com/chakra-core/ChakraCore/issues/3376 | 243,485,781 | 3,376 |
[
"chakra-core",
"ChakraCore"
] | ```js
(0, eval)('function f() { }');
print(JSON.stringify(Object.getOwnPropertyDescriptor(this, 'f')));
```
Expected: {"writable":true,"enumerable":true,"configurable":true}
Actual: {"writable":true,"enumerable":true,"configurable": *false*}
See [EDI](https://tc39.github.io/ecma262/#sec-evaldeclarationin... | Properties of the global object created from function declarations in indirect eval should be configurable | https://api.github.com/repos/chakra-core/ChakraCore/issues/3375/comments | 1 | 2017-07-17T18:24:29Z | 2018-05-31T00:31:57Z | https://github.com/chakra-core/ChakraCore/issues/3375 | 243,483,648 | 3,375 |
[
"chakra-core",
"ChakraCore"
] | Eshost Repro:
```js
Object.defineProperty(
this,
'data1',
{ configurable: false, value: 0, writable: true, enumerable: false }
);
let cmpn = $.evalScript(`
var x;
function data1() { }
`);
print(cmpn.type);
```
Expected: throw (of a TypeError per [GDI](https://tc39.github.io/ecma262/#sec-globa... | Function declarations should not shadow non-enumerable non-configurable properties of the global object | https://api.github.com/repos/chakra-core/ChakraCore/issues/3374/comments | 1 | 2017-07-17T18:10:54Z | 2018-06-06T18:44:26Z | https://github.com/chakra-core/ChakraCore/issues/3374 | 243,480,003 | 3,374 |
[
"chakra-core",
"ChakraCore"
] | It is presently a reference error. Other identifier names appear to throw the proper error.
```js
let undefined;
```
Actual: ReferenceError
Expected: SyntaxError (normal let-const redecl error) | Lexical declaration of `undefined` in global scope should result in SyntaxError | https://api.github.com/repos/chakra-core/ChakraCore/issues/3373/comments | 0 | 2017-07-17T17:57:58Z | 2018-06-27T23:09:41Z | https://github.com/chakra-core/ChakraCore/issues/3373 | 243,476,609 | 3,373 |
[
"chakra-core",
"ChakraCore"
] | ```js
Object.preventExtensions(this);
$.evalScript(`let foo = 1`);
print(foo);
```
Expected: 1
Actual: `undefined` or an error depending on strictness. | Lexical declarations should be shared when global object is non-extensible | https://api.github.com/repos/chakra-core/ChakraCore/issues/3372/comments | 0 | 2017-07-17T17:53:15Z | 2018-07-23T18:51:19Z | https://github.com/chakra-core/ChakraCore/issues/3372 | 243,475,303 | 3,372 |
[
"chakra-core",
"ChakraCore"
] | Is presently a runtime reference error. `super()` has the proper error, however.
```js
super.foo
```
Expected: Early syntax error
Actual: Runtime reference error | Super property reference in global scope should be an early syntax error | https://api.github.com/repos/chakra-core/ChakraCore/issues/3371/comments | 2 | 2017-07-17T17:36:10Z | 2020-03-31T16:03:21Z | https://github.com/chakra-core/ChakraCore/issues/3371 | 243,470,833 | 3,371 |
[
"chakra-core",
"ChakraCore"
] | [test.zip](https://github.com/Microsoft/ChakraCore/files/1153306/test.zip)
Open the attached test.html
Expected: you should see message `Complete without errors`.
Actual: the message `Error in pass ????: if-condition is true instead of false` is shown.
This comparison of two constants occasionally evaluates to ... | The >>> operator returns incorrect result | https://api.github.com/repos/chakra-core/ChakraCore/issues/3370/comments | 1 | 2017-07-17T16:34:57Z | 2017-07-21T00:30:05Z | https://github.com/chakra-core/ChakraCore/issues/3370 | 243,454,457 | 3,370 |
[
"chakra-core",
"ChakraCore"
] | run `Symbol.species.toString()`
expected result: **Symbol(Symbol.species)**
ChakraCore-release-1.6 result: **Symbol([Symbol.species])**
run `Symbol.match.toString();`
or `Symbol.replace.toString();`
or `Symbol.search.toString();`
or `Symbol.split.toString();`
expected result: **Symbol(Symbol.match)** ...
Cha... | Incorrect realization of Symbol.xxx.toString() | https://api.github.com/repos/chakra-core/ChakraCore/issues/3368/comments | 2 | 2017-07-17T13:49:03Z | 2017-07-21T18:55:51Z | https://github.com/chakra-core/ChakraCore/issues/3368 | 243,401,496 | 3,368 |
[
"chakra-core",
"ChakraCore"
] | Hello,
the documentation for _FetchImportedModuleFromScriptCallBack_ is copy and pasted from _NotifyModuleReadyCallback_. Could this be fixed with correct documentation? This would be very helpful.
You can check yourself: https://github.com/Microsoft/ChakraCore/blob/master/lib/Jsrt/ChakraCore.h#L70-L83 | Jsrt documentation is incorrect | https://api.github.com/repos/chakra-core/ChakraCore/issues/3367/comments | 5 | 2017-07-16T16:00:07Z | 2018-01-23T01:19:09Z | https://github.com/chakra-core/ChakraCore/issues/3367 | 243,248,622 | 3,367 |
[
"chakra-core",
"ChakraCore"
] | I think in https://stackoverflow.com/questions/45122823/is-there-any-reason-why-edge-returns-true-for-xml-i-testxml-version I have found a bug with the regular expression `test` method in the Javascript engine of Edge 40.15063.0.0.
```
var xml = '<?';
var regex = /^.+<\?/i;
var test = regex.test(xml);
```
As th... | /^.+<\?/i.test('<?') gives true in Edge 40.15063.0.0 but false in other browsers/engines | https://api.github.com/repos/chakra-core/ChakraCore/issues/3366/comments | 4 | 2017-07-16T09:22:09Z | 2017-07-20T23:53:04Z | https://github.com/chakra-core/ChakraCore/issues/3366 | 243,228,052 | 3,366 |
[
"chakra-core",
"ChakraCore"
] | ```html
<!DOCTYPE html>
<html>
<head>
</head>
<body>
<script type="module">
import; // expected: syntax error, actual: Exception thrown and not caught
console.log(test);
</script>
</body>
</html>
```
```html
<!DOCTYPE html>
<html>
<head>
</head>
<body>
<script type="module">
... | Module syntax errors not showing properly | https://api.github.com/repos/chakra-core/ChakraCore/issues/3357/comments | 5 | 2017-07-14T20:48:58Z | 2020-03-31T15:58:10Z | https://github.com/chakra-core/ChakraCore/issues/3357 | 243,108,596 | 3,357 |
[
"chakra-core",
"ChakraCore"
] | I am encountering a lot of problems when trying to use WScript.LoadModule, mostly due to very different behavior between jshost and ch.
### ch.exe
- [ ] Memory leak on Syntax error with multiple modules
```js
WScript.LoadModule(``);
WScript.LoadModule(`//as`);
WScript.LoadModule(`const a = () -> {};`);
```
##... | WScript.LoadModule inconsistencies | https://api.github.com/repos/chakra-core/ChakraCore/issues/3356/comments | 0 | 2017-07-14T19:24:06Z | 2019-06-07T18:52:48Z | https://github.com/chakra-core/ChakraCore/issues/3356 | 243,088,867 | 3,356 |
[
"chakra-core",
"ChakraCore"
] | Currently asm.js has numerous problems in es6 modules.
- [ ] Support reparsing without asm.js on validation error (currently throws)
```js
WScript.LoadModule(`
function asmModule() {
"use asm"
function x(v) {
v = v | 0;
return v | 0;
}
}`);
```
- [ ] Add support for asm.js module in default ex... | Fix asm.js in ES6 Modules | https://api.github.com/repos/chakra-core/ChakraCore/issues/3355/comments | 2 | 2017-07-14T19:08:56Z | 2018-05-31T00:31:57Z | https://github.com/chakra-core/ChakraCore/issues/3355 | 243,085,300 | 3,355 |
[
"chakra-core",
"ChakraCore"
] | I compiled ChakraCore using the official build guide.
On ubuntu 16.04, ch crashes with the following test case.
I also noticed that if we slightly change the code (using a proper indentation), the Seg fault will be gone.
The hashtag of my chakracore build is
commit cb9c8271c8c9e2a0daec635504b5279168d92f1b
$ ~/... | xplat: Enable JIT for debugging | https://api.github.com/repos/chakra-core/ChakraCore/issues/3352/comments | 1 | 2017-07-14T06:33:20Z | 2018-01-03T21:16:06Z | https://github.com/chakra-core/ChakraCore/issues/3352 | 242,909,772 | 3,352 |
[
"chakra-core",
"ChakraCore"
] | Once #3341 is merged and ported to release/1.6.
Re-enable test `test/wasm/params.js`.
A functional bug was preventing this test from running correctly in release/1.5 which was fixed in release/1.6. | Re-enable test in release/1.6 after 17-07 servicing release | https://api.github.com/repos/chakra-core/ChakraCore/issues/3344/comments | 0 | 2017-07-13T17:55:34Z | 2017-07-17T16:46:15Z | https://github.com/chakra-core/ChakraCore/issues/3344 | 242,781,630 | 3,344 |
[
"chakra-core",
"ChakraCore"
] | It is similar to the second issue in https://github.com/Microsoft/ChakraCore/issues/2862.
ch.cpp(877): error C2362: initialization of 'initRpcServer' is skipped by 'goto cleanup'
Revision https://github.com/Microsoft/ChakraCore/commit/e8f31729a0e8f04a68269698680657698e918053#diff-9aa417ac81c06da693354e50d1edd449 ... | Issues found when building with MSVC + /permissive- - 2 | https://api.github.com/repos/chakra-core/ChakraCore/issues/3343/comments | 0 | 2017-07-13T17:44:13Z | 2017-07-13T22:37:16Z | https://github.com/chakra-core/ChakraCore/issues/3343 | 242,778,750 | 3,343 |
[
"chakra-core",
"ChakraCore"
] | ```javascript
class c1 {
Β Β Β constructor() {
Β Β Β Β Β Β Β return { };
Β Β Β }
};
class c2 extends c1 {
Β Β Β constructor(a = 1, b = () => { a; super(); }) {
Β Β Β Β Β Β Β super();
Β Β Β Β Β Β Β b(); // Should throw
Β Β Β Β Β Β Β return {};
Β Β Β }
}
new c2();
``` | Should throw a TypeError when super is called through a lambda defined in param scope after super is called in the body | https://api.github.com/repos/chakra-core/ChakraCore/issues/3335/comments | 1 | 2017-07-13T00:26:00Z | 2017-10-04T19:54:10Z | https://github.com/chakra-core/ChakraCore/issues/3335 | 242,552,706 | 3,335 |
[
"chakra-core",
"ChakraCore"
] | We are correct according to the spec (both current and proposed), but all other engines include the name of the function in the toString, whereas we do not.
/cc @bterlson
```
> eshost -h d8,node,sm,jsc,ch-dev-che3 -its .\test.js
## Source
print('' + Intl.DateTimeFormat.supportedLocalesOf);
print('' + Intl.get... | Native function toString is inconsistent with other engines | https://api.github.com/repos/chakra-core/ChakraCore/issues/3332/comments | 1 | 2017-07-13T00:02:46Z | 2020-03-31T16:00:23Z | https://github.com/chakra-core/ChakraCore/issues/3332 | 242,549,552 | 3,332 |
[
"chakra-core",
"ChakraCore"
] | * Move to `tools/*/<scripts>`
* Reduce duplication.
See https://github.com/Microsoft/ChakraCore/pull/3323#discussion_r127020344
| Refactor bytecode regen scripts | https://api.github.com/repos/chakra-core/ChakraCore/issues/3330/comments | 2 | 2017-07-12T22:33:16Z | 2021-02-01T08:51:04Z | https://github.com/chakra-core/ChakraCore/issues/3330 | 242,535,363 | 3,330 |
[
"chakra-core",
"ChakraCore"
] | ```
auto str = "function test(){}"
auto fn = JsRun str
JsValueRef info = JS_INVALID_REFERENCE
auto result = JsDiagGetFunctionPosition fn, &info
```
is ok.
```
auto str = "function test(){
console.log("");
console.log("");
console.log("");
console.log("");
... repeat 200 ...// need more in you... | about JsDiagGetFunctionPosition. This maybe a bug. | https://api.github.com/repos/chakra-core/ChakraCore/issues/3325/comments | 1 | 2017-07-12T07:04:32Z | 2019-06-07T19:13:29Z | https://github.com/chakra-core/ChakraCore/issues/3325 | 242,279,665 | 3,325 |
[
"chakra-core",
"ChakraCore"
] | WScriptJsrt uses global states to store sourceContext and maps for moduleRecords, etc..
Changes must be made to support cross-thread scenarios:
1) Module-related maps must be per JsContext to provide isolation between threads
2) Module-related maps have the same lifetime as JsContext
3) Code that updates sourceCo... | ch.exe's global states (e.g. sourceContext, module*Map) need to change to work cross-thread | https://api.github.com/repos/chakra-core/ChakraCore/issues/3319/comments | 0 | 2017-07-11T17:44:40Z | 2018-03-17T00:33:21Z | https://github.com/chakra-core/ChakraCore/issues/3319 | 242,129,127 | 3,319 |
[
"chakra-core",
"ChakraCore"
] | ```javascript
// mod0.js
console.log("mod0");
```
```javascript
// bug0.js
// expected: mod0
// actual: ASSERTION (bin\ch\WScriptJsrt.h, line 83) false Unexpected JsErrorCode: JsErrorWrongThread
WScript.LoadScript(`WScript.LoadScriptFile("./mod0.js", "module");`, "crossthread");
```
```javascript
// bug1.js
... | ch.exe doesn't support module load cross-thread | https://api.github.com/repos/chakra-core/ChakraCore/issues/3318/comments | 3 | 2017-07-11T17:11:26Z | 2018-03-17T00:33:21Z | https://github.com/chakra-core/ChakraCore/issues/3318 | 242,120,147 | 3,318 |
[
"chakra-core",
"ChakraCore"
] | Hit this bug while working on #3257. To check in fix as part of #3284.
```javascript
// bug.js
WScript.LoadScriptFile("./mod0.js", "module");
WScript.LoadScriptFile("./script0.js");
```
```javascript
// mod0.js
import './mod1.js';
import './mod2.js';
console.log("mod0");
```
```javascript
// mod1.js
impor... | Module: premature instantiation of dynamic import modules | https://api.github.com/repos/chakra-core/ChakraCore/issues/3306/comments | 0 | 2017-07-08T01:53:33Z | 2017-07-11T23:37:13Z | https://github.com/chakra-core/ChakraCore/issues/3306 | 241,416,708 | 3,306 |
[
"chakra-core",
"ChakraCore"
] | Discovered in #3303
Restoring the .gitattributes caused a bunch of tests to start failing -- probably baselines which were checked in since .gitattributes changed. See: https://ci2.dot.net/job/Microsoft_ChakraCore/job/release_1.6/job/x64_debug_prtest/341/
See https://github.com/dilijev/ChakraCore/tree/gitattr for... | .gitattributes missing | https://api.github.com/repos/chakra-core/ChakraCore/issues/3305/comments | 2 | 2017-07-07T22:29:55Z | 2017-07-10T23:22:14Z | https://github.com/chakra-core/ChakraCore/issues/3305 | 241,396,378 | 3,305 |
[
"chakra-core",
"ChakraCore"
] | ```js
// Dynamic functions
var x = "function(a, b, c) { console.log('hello'); }";
var func = new Function(x);
```
Today, for above code, we [create a pid hash table](https://github.com/Microsoft/ChakraCore/blob/master/lib/Parser/Parse.cpp#L11287-L11289) while validating syntax for formals (`(a,b,c)`) and for func... | Reuse of pid hashtable of parser for DynamicFunction | https://api.github.com/repos/chakra-core/ChakraCore/issues/3302/comments | 0 | 2017-07-07T18:44:45Z | 2017-08-15T21:33:58Z | https://github.com/chakra-core/ChakraCore/issues/3302 | 241,347,809 | 3,302 |
[
"chakra-core",
"ChakraCore"
] | Hi,
We found an failed assertion in the ChakraCore interpreter (ch) when you run the following test case:
```
WScript = {};
WScript.Echo = console.log;
$ERROR = console.log;
assert = {};
assert.sameValue = function (x
,y
,z) {
return x == y;
... | Assertion failed at lib/Runtime/Types/RecyclableObject.inl | https://api.github.com/repos/chakra-core/ChakraCore/issues/3299/comments | 1 | 2017-07-07T13:38:22Z | 2017-07-12T01:34:13Z | https://github.com/chakra-core/ChakraCore/issues/3299 | 241,266,544 | 3,299 |
[
"chakra-core",
"ChakraCore"
] | I can't find any examples of how to use JsConstructObject in the ChakraSamples repo. In particular, I'm curious what the arguments array needs to look like.... can I pass any object as the first argument, or does it need to be a newly created one that the constructor can fill by referring to 'this'? | [Question] JsConstructObject, examples of use? | https://api.github.com/repos/chakra-core/ChakraCore/issues/3293/comments | 14 | 2017-07-06T02:27:45Z | 2018-04-27T22:22:17Z | https://github.com/chakra-core/ChakraCore/issues/3293 | 240,827,174 | 3,293 |
[
"chakra-core",
"ChakraCore"
] | I am trying to build x64 Debug ChakraCore from source, here's my setup:
- Windows 10.0.14393
- Visual Studio 2015 Pro 14.0.25431.01 Update 3
- Windows SDK 10.0.15063.468
- I've checkout the most recent source using git in the folder P:\dev\ChakraCore
(_Note that I have build ChakraCore on this machine successful... | Windows: Cannot build | https://api.github.com/repos/chakra-core/ChakraCore/issues/3287/comments | 9 | 2017-07-04T16:12:42Z | 2017-09-10T13:56:50Z | https://github.com/chakra-core/ChakraCore/issues/3287 | 240,461,089 | 3,287 |
[
"chakra-core",
"ChakraCore"
] | Hi,
We found an failed assertion in the ChakraCore interpreter (ch) when you run the following test case:
```
function foo() {
var x = "bp A";
x;
x = "Hit loc B";
x;
x = "bp C, BUG";
x;
x = "bp D, BUG";
x;
x = "bp D";
x;
}
WScript.Attach(foo);
WScript.Detach(foo);
WSc... | Failed assertion at lib/Runtime/Base/FunctionBody.h | https://api.github.com/repos/chakra-core/ChakraCore/issues/3285/comments | 1 | 2017-07-03T23:38:21Z | 2017-12-01T09:06:01Z | https://github.com/chakra-core/ChakraCore/issues/3285 | 240,281,712 | 3,285 |
[
"chakra-core",
"ChakraCore"
] | `RecyclerWeakReference` data structure is a data structure used to store weak reference to strong reference mapping inside recycler. Internally it uses hash table with chaining to save the mapped entries.
[HashKeyToBucket](https://github.com/Microsoft/ChakraCore/blob/master/lib/Common/Memory/RecyclerWeakReference.h#L... | Re-evaluate hash function for RecyclerWeakReference | https://api.github.com/repos/chakra-core/ChakraCore/issues/3282/comments | 6 | 2017-07-03T19:50:08Z | 2019-06-07T18:25:39Z | https://github.com/chakra-core/ChakraCore/issues/3282 | 240,253,089 | 3,282 |
[
"chakra-core",
"ChakraCore"
] | ```javascript
1337in{1337:1}
```
Expected: Syntax error. In operator cannot follow number.
Actual: true
Firefox, Chrome and Safari all throw exceptions. | In operator allowed to follow a number | https://api.github.com/repos/chakra-core/ChakraCore/issues/3281/comments | 1 | 2017-07-03T12:20:36Z | 2017-09-08T00:57:25Z | https://github.com/chakra-core/ChakraCore/issues/3281 | 240,156,110 | 3,281 |
[
"chakra-core",
"ChakraCore"
] | Hi,
We found an failed assertion in the ChakraCore interpreter (ch) when you run the following test case:
```
foo.prototype = new Array(1
,2
,3);
function foo() {
}
var f = new foo();
f.length /= null;
var callCnt = 0;
function cb() {
callCnt++;
}
... | Failed assertion at lib/Common/Memory/HeapBlock.cpp | https://api.github.com/repos/chakra-core/ChakraCore/issues/3280/comments | 4 | 2017-07-03T12:14:47Z | 2017-12-09T00:56:22Z | https://github.com/chakra-core/ChakraCore/issues/3280 | 240,154,877 | 3,280 |
[
"chakra-core",
"ChakraCore"
] | Jitted code for setting an element to a typed array checks if the length is greater than 0. If not, it just bypasses the set.
We set the length of the typed array to 0 if its array buffer was detached, so bypassing the set if the length is 0 prevents us from writing to detached buffer, but it also means that we won't ... | Jitted code doesn't throw ArrayBuffer detached exception | https://api.github.com/repos/chakra-core/ChakraCore/issues/3277/comments | 0 | 2017-06-30T23:55:51Z | 2019-06-07T19:00:15Z | https://github.com/chakra-core/ChakraCore/issues/3277 | 239,912,342 | 3,277 |
[
"chakra-core",
"ChakraCore"
] | Not documented on the [header](https://github.com/Microsoft/ChakraCore/blob/d3b6d103bbfa6207d18b74cbf77ca9a48455b8e6/lib/Jsrt/ChakraCommon.h#L694), but if it's the same as `JsCallFunction` then `arguments[0]` should be `this`. The behavior only seems right if in strict mode. Is this a bug or intended?
```cpp
#defi... | [JSRT] JsNativeFunction arguments[0] yields undefined instead of globalObj when called as property of globalObj | https://api.github.com/repos/chakra-core/ChakraCore/issues/3276/comments | 5 | 2017-06-30T22:28:01Z | 2017-07-03T20:41:13Z | https://github.com/chakra-core/ChakraCore/issues/3276 | 239,902,565 | 3,276 |
[
"chakra-core",
"ChakraCore"
] | ```js
let a = 1;
eval('function a() { };');
```
Expected: SyntaxError per https://tc39.github.io/ecma262/#sec-evaldeclarationinstantiation 5.a.i.1
Actual: no syntax error, function is assigned to let variable.
```js
(function () {
let a = 1;
eval('function a() { }');
})();
```
Expected: SyntaxError pe... | Eval containing a function declaration with a same-named lexical declaration in outer scope should throw | https://api.github.com/repos/chakra-core/ChakraCore/issues/3275/comments | 0 | 2017-06-30T19:23:14Z | 2018-05-01T22:41:15Z | https://github.com/chakra-core/ChakraCore/issues/3275 | 239,867,694 | 3,275 |
[
"chakra-core",
"ChakraCore"
] | Part 1 (#3273) of this change is to ifdef the code to not build. Once we figure out what can be reused for WASM simd we should remove rest of the code | Remove Simd.js code from ChakraCore - Part 2 (Remove) | https://api.github.com/repos/chakra-core/ChakraCore/issues/3274/comments | 0 | 2017-06-30T18:07:05Z | 2018-02-21T18:29:23Z | https://github.com/chakra-core/ChakraCore/issues/3274 | 239,850,722 | 3,274 |
[
"chakra-core",
"ChakraCore"
] | simd.js is no longer planned for in its current form. V8 has already removed it and ChakraCore should also remove it.
Since some code of simd.js can be reused for WASM simd. In first part of change try to ifdef out simd.js specific code to not build and then in second part remove code which is not needed for WASM si... | Remove Simd.js code from ChakraCore - Part 1 (ifdef out) | https://api.github.com/repos/chakra-core/ChakraCore/issues/3273/comments | 4 | 2017-06-30T18:04:41Z | 2017-07-24T19:32:03Z | https://github.com/chakra-core/ChakraCore/issues/3273 | 239,850,194 | 3,273 |
[
"chakra-core",
"ChakraCore"
] | when i run ./build.sh --arch=arm --target=android on linux i get this error of pal
error: typedef redefinition with different types ('char' vs '__int8_t' (aka 'signed char'))
typedef __int8 int8_t;
| build.sh --arch=arm --target=android typedef redefinition with different types | https://api.github.com/repos/chakra-core/ChakraCore/issues/3272/comments | 4 | 2017-06-30T16:50:40Z | 2018-03-17T00:33:20Z | https://github.com/chakra-core/ChakraCore/issues/3272 | 239,833,712 | 3,272 |
[
"chakra-core",
"ChakraCore"
] | ```javascript
eval('_'+String.fromCharCode(1320)+'_=alert(1)')
```
Expected: alert function to be called and variable assigned
Actual: Invalid character exception
Every other browser treats the characters as a valid variable part. The following characters are also treated incorrectly.
895,1320,1321,1322,132... | Multiple characters not treated as valid variable part | https://api.github.com/repos/chakra-core/ChakraCore/issues/3271/comments | 2 | 2017-06-30T08:39:59Z | 2017-07-11T22:26:49Z | https://github.com/chakra-core/ChakraCore/issues/3271 | 239,713,470 | 3,271 |
[
"chakra-core",
"ChakraCore"
] | Does ChakraCore have a build for android, is it really efficient and works well for android without bugs or performace?
Well I would very much like to use this engine in a desktop / android project, but I have this doubt, because in the case of the controller I would have to choose either v8 or JavaScriptCore. | ChakraCore on android is viable ? | https://api.github.com/repos/chakra-core/ChakraCore/issues/3270/comments | 1 | 2017-06-30T06:22:47Z | 2017-11-30T23:39:14Z | https://github.com/chakra-core/ChakraCore/issues/3270 | 239,687,752 | 3,270 |
[
"chakra-core",
"ChakraCore"
] | We encountered an issue that on a hello world scenario with ChakraCore, Linux Skylake server generates a segmentation fault. This issue only happens on Skylake server, not on Haswell server, not on Skylake client system either. It only happens on Linux, not on Windows.
Following is hello world test case and call st... | ChakraCore hello scenario generates segmentation fault on Linux Skylake server | https://api.github.com/repos/chakra-core/ChakraCore/issues/3262/comments | 0 | 2017-06-29T18:02:33Z | 2017-07-11T12:02:37Z | https://github.com/chakra-core/ChakraCore/issues/3262 | 239,564,485 | 3,262 |
[
"chakra-core",
"ChakraCore"
] | ```javascript
eval('\0');
```
Expected: Illegal character exception
Actual: undefined
Multiple NULL characters throw an exception however it's possible to call a function before the NULL. E.g
```javascript
eval('alert(1)\0');
``` | NULL character ignored and exception is not thrown | https://api.github.com/repos/chakra-core/ChakraCore/issues/3261/comments | 0 | 2017-06-29T12:50:31Z | 2017-07-28T17:13:03Z | https://github.com/chakra-core/ChakraCore/issues/3261 | 239,467,940 | 3,261 |
[
"chakra-core",
"ChakraCore"
] | what's the relationship between chakracore and edge js engine chakra?Can I guess which version of chakracore is used by chakra engine based on the version of chakra.dll? | releationship between chakracore and chakra.dll? | https://api.github.com/repos/chakra-core/ChakraCore/issues/3260/comments | 3 | 2017-06-29T08:29:39Z | 2017-11-30T23:40:18Z | https://github.com/chakra-core/ChakraCore/issues/3260 | 239,402,613 | 3,260 |
[
"chakra-core",
"ChakraCore"
] | Currently, all imports are relative to CWD. It should instead be relative to the module doing the import. | Module imports in ch.exe/jshost.exe should be relative to the current module | https://api.github.com/repos/chakra-core/ChakraCore/issues/3257/comments | 0 | 2017-06-28T21:54:35Z | 2017-07-11T23:37:13Z | https://github.com/chakra-core/ChakraCore/issues/3257 | 239,309,242 | 3,257 |
[
"chakra-core",
"ChakraCore"
] | ```js
// some module.js
if (false) export default null;
```
Actual: no error
Expected: early syntax error
This also applies to (at least) the else block, the body of loop constructs, and labels.
| Module import/export should not be allowed in the statement of an if/else/while/etc. | https://api.github.com/repos/chakra-core/ChakraCore/issues/3256/comments | 0 | 2017-06-28T21:50:30Z | 2017-07-10T23:17:37Z | https://github.com/chakra-core/ChakraCore/issues/3256 | 239,308,282 | 3,256 |
[
"chakra-core",
"ChakraCore"
] | ```js
// some module.js
return;
```
Actual: bails out of the module (kind of handy actually)
Expected: Early syntax error
| Modules should not allow `return` at top level | https://api.github.com/repos/chakra-core/ChakraCore/issues/3255/comments | 0 | 2017-06-28T21:45:01Z | 2017-07-10T23:17:52Z | https://github.com/chakra-core/ChakraCore/issues/3255 | 239,307,016 | 3,255 |
[
"chakra-core",
"ChakraCore"
] | ```js
var f;
function f() {}
```
Actual: No Error
Expected: Early Syntax Error (redeclaration of f).
| Duplicate VarDeclaredName and LexicallyDeclaredName is always an error in Modules | https://api.github.com/repos/chakra-core/ChakraCore/issues/3254/comments | 0 | 2017-06-28T21:42:40Z | 2019-06-07T18:52:38Z | https://github.com/chakra-core/ChakraCore/issues/3254 | 239,306,497 | 3,254 |
[
"chakra-core",
"ChakraCore"
] | ```js
// bug-dep.js
import * as ns from './bug-dep.js';
print(Object.prototype.hasOwnProperty.call(ns, Symbol.iterator));
```
Actual: true
Expected: false ([spec changed](https://github.com/tc39/ecma262/commit/814463f4819f30fe2bc2db56a00b63e3f76167af)) | Module namespace objects should not have Symbol.iterator property | https://api.github.com/repos/chakra-core/ChakraCore/issues/3252/comments | 0 | 2017-06-28T21:38:51Z | 2017-07-10T23:18:21Z | https://github.com/chakra-core/ChakraCore/issues/3252 | 239,305,641 | 3,252 |
[
"chakra-core",
"ChakraCore"
] | ```js
import * as ns from './bug-dep.js';
print(ns.local1);
export let local1 = 23;
```
Actual: undefined
Expected: TDZ error on access of ns.local1
| Modules do not throw TDZ errors for accessing imported TDZ'd bindings | https://api.github.com/repos/chakra-core/ChakraCore/issues/3251/comments | 3 | 2017-06-28T21:33:28Z | 2019-06-23T22:45:41Z | https://github.com/chakra-core/ChakraCore/issues/3251 | 239,304,393 | 3,251 |
[
"chakra-core",
"ChakraCore"
] | ```js
// bug.js
WScript.LoadModule(`import "bug-dep.js"`);
// bug-dep.js
import * as ns from './bug-dep.js';
export let c_localUninit1;
export { c_localUninit1 as f_indirectUninit } from './bug-dep2.js';
var stringKeys = Object.getOwnPropertyNames(ns);
print(JSON.stringify(stringKeys));
// bug-dep2.js
... | Module crash in circular import case | https://api.github.com/repos/chakra-core/ChakraCore/issues/3250/comments | 0 | 2017-06-28T21:27:41Z | 2017-08-16T17:04:23Z | https://github.com/chakra-core/ChakraCore/issues/3250 | 239,302,978 | 3,250 |
[
"chakra-core",
"ChakraCore"
] | ```js
// bug-dep.js
import * as ns from './bug-dep.js';
print(JSON.stringify(Object.getOwnPropertyDescriptor(ns, Symbol.toStringTag)));
```
Actual: writable true, enumerable true
Expected: writable false, enumerable false ([spec](https://tc39.github.io/ecma262/#sec-@@tostringtag)) | Module namespace object's Symbol.toStringTag has incorrect attributes | https://api.github.com/repos/chakra-core/ChakraCore/issues/3249/comments | 0 | 2017-06-28T21:25:16Z | 2017-07-14T23:22:53Z | https://github.com/chakra-core/ChakraCore/issues/3249 | 239,302,411 | 3,249 |
[
"chakra-core",
"ChakraCore"
] | ```js
import * as ns from './bug-dep.js';
export let x = 1;
export { x as renamed } from "./bug-dep.js";
var stringKeys = Object.getOwnPropertyNames(ns);
print(JSON.stringify(stringKeys));
```
Actual: ['x']
Expected: ['renamed', 'x']
| Module namespace object not populated with bindings exported and renamed from self | https://api.github.com/repos/chakra-core/ChakraCore/issues/3248/comments | 1 | 2017-06-28T21:20:24Z | 2017-07-24T23:24:08Z | https://github.com/chakra-core/ChakraCore/issues/3248 | 239,301,255 | 3,248 |
[
"chakra-core",
"ChakraCore"
] | ```js
// bug.js
WScript.LoadModule(`import "bug-dep.js"`);
// bug-dep.js
import './bug-dep.js';
print('eval');
```
Actual: eval printed twice
Expected: eval printed once | Modules evaluated twice when referenced circularly | https://api.github.com/repos/chakra-core/ChakraCore/issues/3247/comments | 0 | 2017-06-28T21:14:24Z | 2017-07-11T23:37:13Z | https://github.com/chakra-core/ChakraCore/issues/3247 | 239,299,526 | 3,247 |
[
"chakra-core",
"ChakraCore"
] | When constructing a module namespace object, the keys [should be ordered](https://tc39.github.io/ecma262/#sec-modulenamespacecreate) as if passed to Array.prototype.sort with the default comparator.
```js
// root.js
WScript.LoadModule(`import "bug-dep.js"`);
// bug-dep.js
var x;
export { x as Ο }; // u03c0
e... | Module namespace entries are not sorted properly | https://api.github.com/repos/chakra-core/ChakraCore/issues/3246/comments | 0 | 2017-06-28T20:43:52Z | 2017-07-14T23:26:48Z | https://github.com/chakra-core/ChakraCore/issues/3246 | 239,290,502 | 3,246 |
[
"chakra-core",
"ChakraCore"
] | ```js
WScript.LoadModule(`
export default function f() {} if (true) { };
`);
```
Actual: Syntax error, expected `;`
Expected: No syntax error
Examining the syntax for [export forms](https://tc39.github.io/ecma262/#prod-ExportDeclaration), some do not require a semicolon to follow them.
| Semicolon should not be required after certain module export forms | https://api.github.com/repos/chakra-core/ChakraCore/issues/3245/comments | 0 | 2017-06-28T20:30:54Z | 2017-08-16T19:37:25Z | https://github.com/chakra-core/ChakraCore/issues/3245 | 239,286,648 | 3,245 |
[
"chakra-core",
"ChakraCore"
] | ```js
Function('1=1')
```
Expected: ReferenceError ([spec](https://tc39.github.io/ecma262/#sec-createdynamicfunction))
Actual: No error until the function is invoked
V8 and SM throw this error. | Function constructor should throw when it contains an invalid LHS assignment | https://api.github.com/repos/chakra-core/ChakraCore/issues/3242/comments | 3 | 2017-06-28T16:48:28Z | 2018-06-04T19:27:43Z | https://github.com/chakra-core/ChakraCore/issues/3242 | 239,227,255 | 3,242 |
[
"chakra-core",
"ChakraCore"
] | When invoking toString() on a native method, I would think one generally expects to see something like the following, if the function were called 'foo':
"function foo() { [native code] }"
If a function is created via JsCreateNamedFunction, however, invoking toString() on it only gives back:
"foo"
Was this b... | Question/bug: functions created by JsCreateNamedFunction when converted to string simply show the function name | https://api.github.com/repos/chakra-core/ChakraCore/issues/3241/comments | 1 | 2017-06-28T05:22:19Z | 2017-06-28T22:21:45Z | https://github.com/chakra-core/ChakraCore/issues/3241 | 239,055,683 | 3,241 |
[
"chakra-core",
"ChakraCore"
] | Response apis have changed name since it was first implemented.
https://github.com/WebAssembly/design/blob/master/Web.md#additional-web-embedding-api
Need to rename | WASM - Response api rename | https://api.github.com/repos/chakra-core/ChakraCore/issues/3231/comments | 0 | 2017-06-27T01:08:44Z | 2017-06-28T16:41:55Z | https://github.com/chakra-core/ChakraCore/issues/3231 | 238,710,728 | 3,231 |
[
"chakra-core",
"ChakraCore"
] | I have a Wordpress Website (formen.co.il) In which I use a page builder. The page builder for some odd reason adds `<br>` tags to buttons added with it. To remove these added br tags with Js, I added a custom.js file, to which I added the following Js code:
```
for (const element of document.querySelectorAll(".elem... | FOR OF loop works on Chrome and Firefox but not on Microsoft Edge 40.15063.0.0 | https://api.github.com/repos/chakra-core/ChakraCore/issues/3229/comments | 1 | 2017-06-27T00:19:06Z | 2017-07-11T18:44:41Z | https://github.com/chakra-core/ChakraCore/issues/3229 | 238,704,593 | 3,229 |
[
"chakra-core",
"ChakraCore"
] | Implement non-trapping float-to-int conversions
https://github.com/WebAssembly/design/pull/1089 | WASM - Non-trapping float-to-int conversion (3d) | https://api.github.com/repos/chakra-core/ChakraCore/issues/3228/comments | 1 | 2017-06-26T23:48:20Z | 2018-04-26T02:03:14Z | https://github.com/chakra-core/ChakraCore/issues/3228 | 238,700,375 | 3,228 |
[
"chakra-core",
"ChakraCore"
] | Repro:
```
<pre id="log"></pre>
<script>
function log(msg) { document.getElementById('log').textContent += msg + '\n'; }
function Base() {}
function Derived() {}
Derived.prototype = Object.create(Base.prototype); // OPTIONAL
log(new Base() instanceof Derived); // correctly logs 'false'
Reflect.construc... | Reflect.construct permanently corrupts the invoked constructor | https://api.github.com/repos/chakra-core/ChakraCore/issues/3217/comments | 0 | 2017-06-23T21:21:26Z | 2017-07-21T23:09:54Z | https://github.com/chakra-core/ChakraCore/issues/3217 | 238,256,759 | 3,217 |
[
"chakra-core",
"ChakraCore"
] | We have been successfully using Chakra in our application for over 2 years (before it was even open sourced). It is a great JS engine. Today we released some work via the Windows store, and apps that work fine on our workstations, fail at runtime with the following error:
```
System.TypeLoadException: Unresolved P/... | Unresolved P/Invoke method 'JsCreateExternalArrayBuffer!Chakra.dll' | https://api.github.com/repos/chakra-core/ChakraCore/issues/3216/comments | 1 | 2017-06-23T19:44:19Z | 2018-02-13T23:45:32Z | https://github.com/chakra-core/ChakraCore/issues/3216 | 238,236,246 | 3,216 |
[
"chakra-core",
"ChakraCore"
] | There are some FncFlags in ptree.h that are unsused right now.
We should clean up those to free up some space and also shold change sxFnc.flags to use type FncFlags instead of uint to help debugging.
Unused flags found so far
- [x] kFunctionDoesNotEscape
- [x] kFunctionHasThisStmt
- [x] kFunctionHasNewTargetRefe... | Remove unused FncFlags | https://api.github.com/repos/chakra-core/ChakraCore/issues/3212/comments | 0 | 2017-06-23T00:33:37Z | 2017-08-16T23:21:10Z | https://github.com/chakra-core/ChakraCore/issues/3212 | 238,009,902 | 3,212 |
[
"chakra-core",
"ChakraCore"
] | In "Test" builds of ChakraCore, we can see that with specific frameworks and libraries there are higher incidences of functions that eventually get JIT compiled to native code, but then get un-JITd.
I'd like to be able to have a Test build of ChakraCore output some JSON that I can feed into a Release build that lists... | Allow for user-defined blacklists so JIT is not attempted on specific functions | https://api.github.com/repos/chakra-core/ChakraCore/issues/3209/comments | 8 | 2017-06-22T18:16:30Z | 2017-09-06T20:50:05Z | https://github.com/chakra-core/ChakraCore/issues/3209 | 237,929,948 | 3,209 |
[
"chakra-core",
"ChakraCore"
] | For every script (`Utf8SourceInfo`) a global function contains `boundPropertyRecords` map which is a hash set of `propertyId` to `ProperytRecord*`. All the functions of that script share this map and add entries of property it finds during bytecodegen of that function. This map is at global function level because mul... | Possibility of optimizing memory of BoundpropertyRecordList | https://api.github.com/repos/chakra-core/ChakraCore/issues/3206/comments | 0 | 2017-06-22T05:51:46Z | 2017-08-15T21:34:26Z | https://github.com/chakra-core/ChakraCore/issues/3206 | 237,738,591 | 3,206 |
[
"chakra-core",
"ChakraCore"
] | ```
print(Intl.DateTimeFormat.supportedLocalesOf);
print(Intl.getCanonicalLocales);
```
```
function() {
[native code]
}
function CanonicalizeLocaleList() { [native code] }
```
Should do something similar here to hide name of the implementing function as we did for `supportedLocalesOf`. | Name of function `Intl.getCanonicalLocales` is incorrectly `CanonicalizeLocaleList` -- should be hidden. | https://api.github.com/repos/chakra-core/ChakraCore/issues/3204/comments | 3 | 2017-06-22T01:30:28Z | 2017-07-20T20:44:17Z | https://github.com/chakra-core/ChakraCore/issues/3204 | 237,708,219 | 3,204 |
[
"chakra-core",
"ChakraCore"
] | For example:
```
new Intl.DateTimeFormat.supportedLocalesOf();
```
outputs:
```
TypeError: Function 'Intl.DateTimeFormat.supportedLocalesOf' is not a constructor
at Global code (e:\work\intl-icu-xplat\test\iswellformedlanguagetag.js:2:1)
```
Similar should happen for
```
new Intl.getCanonicalLoc... | `new Intl.getCanonicalLocales()` should fail with `not a constructor` | https://api.github.com/repos/chakra-core/ChakraCore/issues/3203/comments | 0 | 2017-06-22T01:23:42Z | 2017-07-20T20:44:17Z | https://github.com/chakra-core/ChakraCore/issues/3203 | 237,707,375 | 3,203 |
[
"chakra-core",
"ChakraCore"
] | In the following test case
```js
function foo() {
return function bar(a) {
a = 4;
console.log(arguments[0])
}
}
foo()(2);
```
In the parser (Parse.cpp:1710), when we defer parse `foo` (or -force:deferparse) it looks like we incorrectly set `m_currentNodeFunc->sxFnc.SetHasAnyWriteToFormals(tr... | HasAnyWriteToFormals in deferparse | https://api.github.com/repos/chakra-core/ChakraCore/issues/3194/comments | 1 | 2017-06-20T19:02:12Z | 2018-05-31T00:31:56Z | https://github.com/chakra-core/ChakraCore/issues/3194 | 237,312,215 | 3,194 |
[
"chakra-core",
"ChakraCore"
] | I'd like some method to remove my non-null promise continuation callback from the JavaScriptContext.
However, I get a ``JavaScriptErrorCode.NullArgument`` if I call ``JavaScriptContext.SetPromiseContinuationCallback(null, IntPtr.Zero)``
I presume the argument validation is too strict? | can't cleanup after JsSetPromiseContinuationCallback | https://api.github.com/repos/chakra-core/ChakraCore/issues/3192/comments | 2 | 2017-06-20T15:54:21Z | 2017-07-19T19:11:18Z | https://github.com/chakra-core/ChakraCore/issues/3192 | 237,260,789 | 3,192 |
[
"chakra-core",
"ChakraCore"
] | https://stackoverflow.com/a/44637643/646551
### Steps to reproduce
Run the following code using ch.exe:
```
// var earlyDateString = new Date().toLocaleString();
Map = {};
var dateString = new Date().toLocaleString();
```
### Expected result
dateString contains something like "β20β/β06β/β2017β β5β:β46β:β... | Date locale functions fail if Map is overridden | https://api.github.com/repos/chakra-core/ChakraCore/issues/3189/comments | 3 | 2017-06-20T07:57:15Z | 2017-06-20T22:02:20Z | https://github.com/chakra-core/ChakraCore/issues/3189 | 237,123,169 | 3,189 |
[
"chakra-core",
"ChakraCore"
] | Hello,
The following code behaves incorrectly (inconsistent with the standard and other engines) in Chakra due to incorrect realization of SetItems() functions:
```
var y = 0;
var t = [1,2,3];
var mp = new Proxy([], {
get: function (oTarget, sKey) {
print("get " + sKey.toString());
y = y + 1;
p... | Incorrect realization of SetItem() functions | https://api.github.com/repos/chakra-core/ChakraCore/issues/3187/comments | 10 | 2017-06-20T01:49:01Z | 2019-06-07T19:10:02Z | https://github.com/chakra-core/ChakraCore/issues/3187 | 237,070,090 | 3,187 |
[
"chakra-core",
"ChakraCore"
] | Turn on WasmMathExFilter and cover the case for `rem_s(min_int , -1)` where we need to resume after the exception and set RDX to 0 | WASM - Turn on -WasmMathExFilter | https://api.github.com/repos/chakra-core/ChakraCore/issues/3182/comments | 0 | 2017-06-19T18:29:57Z | 2018-05-07T22:19:28Z | https://github.com/chakra-core/ChakraCore/issues/3182 | 236,979,784 | 3,182 |
[
"chakra-core",
"ChakraCore"
] | Lower TrapIfTruncOverflow independently of the conversion. If we deadstore the conversion we still have the checks to trap | WASM - Lower TrapIfTruncOverflow (2d) | https://api.github.com/repos/chakra-core/ChakraCore/issues/3180/comments | 0 | 2017-06-19T18:22:35Z | 2018-05-07T22:19:43Z | https://github.com/chakra-core/ChakraCore/issues/3180 | 236,977,784 | 3,180 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.