Compiler

What version of Next.js are you using?

12.0.1

What version of Node.js are you using?

14.17.4

What browser are you using?

Chrome

What operating system are you using?

Windows

How are you deploying your application?

Vercel

Describe the Bug

I implemented PWA using next-pwa in my application, and went through all the necessary steps. ( creating

Describe the bug
The content of the the svelte file is a large HTML chunk, without any script logic or styling being involved. Max stack size exceeded error while compiling.

To Reproduce
https://svelte.dev/repl/a9dfcc17551c4aeb95e8fe748a97061d?version=3.20.1

Expected behavior
Compiling should not break

Information about your Svelte project:
Svelte 3.20.1, Rollup, Windo

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

The

💻

• Would you like to work on a fix?

How are you using Babel?

Other (Next.js, Gatsby, vue-cli, ...)

Input code

This lines from node_modules/@babel/runtime/helpers/esm/possibleConstructorReturn.js

import _typeof from "@babel/runtime/helpers/typeof";
import assertThisInitialized from "./assertThisInitialized.js";

should be

import _typeof from "./

Marked version:
3.x.x

Describe the bug
A clear and concise description of what the bug is.

Right now, import {use} from "markedjs" does not work, this worked in 2.x.x.

To Reproduce
Steps to reproduce the behavior:

Install & import it.
The DefinitelyTyped definitions also mark this incorrectly as being supported still.

A workaround is importing one of the structur

It is awkward, but TypeScript officially supports using .js in import specifiers, like so:

import {foo} from './path/to/some/file.js'
console.log(foo)

where ./path/to/some/file.js does not actually exist, but th

### Example
let unreachableProxy = "http://127.0.0.1:8888"
try:
  let client = newHttpClient(proxy=newProxy(unreachableProxy), timeout=1)
  var res = client.getContent("https://github.com")
  echo res
except:
  echo "Timed out"

Current Output

timeout variable is ignored, program stuck until default socket timeout will happen

Expected Output

Timed out a

For now, Object protocol methods are (mostly) thin wrapper of matching vm functions. Because we don't need to have duplicated functions for same features, they need to be moved from vm to object protocol functions.

• vm path: vm/src/vm.rs
• object protocol path: vm/src/protocol/object.rs

The matching vm functions are easy to find because object methods are calling it.

• get_att

I was trying to use CE to show case address sanitizers

With GCC a typical output might look like

READ of size 4 at 0x7ffdb0b840dc thread T0
    #0 0x4012d2 in main /app/example.cpp:6
    #1 0x7f0f0fc790b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc

I believe this is undocumented behaviour.

import numba as nb


@nb.njit
def f1():
    for i in nb.prange(1):
        print(type(i))  # >>> int64


@nb.njit(parallel=True)
def f2():
    for i in nb.prange(1):
        print(type(i))  # >>> uint64


f1()
f2()

This caused a nasty bug in my own code that was hard to debug as the problem did not exist without `parallel=Tr