WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
This may sound weird but a deno.info api would be really helpful for me. (Exposing the output of the deno info command in some form without having to access the CLI.)

My use case is having deno make requests for the module and all imported modules to the webserver it's also running (allowing the server to trigger compiles for said modules.) and caching external modules to the local webserver by making requests. Finally, checking if any of the modules are loading from internet sources as opposed to local cache sources.

I'm sure there could be other ways of doing this, but it might be nice to be able to build custom tooling around the deno info command.

Issue 2:
Currently "deno info https://deno.land/std/http/file_server.ts" will display a dependency graph of the specified module. It would be nice to be able to access this information in a programmatic way.

let depTree = await Deno.deps("https://deno.land/std/http/file_server.ts")

Where depTree would be some JSON encodable object similar to the current output.

The first step to exposing this would be pure rust functionality of turning a Deps structure into a JSON string:

deno/cli/modules.rs

Line 188
in
960ee52

pub struct Deps {
Issue 1:
Challenge Waypoint: Delete Properties from a JavaScript Object has an issue.

User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0.

Please describe how to reproduce this issue, and include links to screenshots if possible.

My code:

var ourDog = {
"name": "Camper",
"legs": 4,
"tails": 1,
"friends": ["everything!"],
"bark": "bow-wow"
};

delete ourDog.bark;

var myDog = {
"name": "Happy Coder",
"legs": 4,
"tails": 1,
"friends": ["Free Code Camp Campers"],
"bark": "woof"
};

// Only change code below this line.
delete myDog.bark;

// Only change code above this line.

(function(z){return z;})(myDog);

Issue 2:
Challenge Waypoint: Delete Properties from a JavaScript Object has an issue.

User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0.

Please describe how to reproduce this issue, and include links to screenshots if possible.

My code:

var ourDog = {
"name": "Camper",
"legs": 4,
"tails": 1,
"friends": ["everything!"],
"bark": "bow-wow"
};

delete ourDog.bark;

var myDog = {
"name": "Happy Coder",
"legs": 4,
"tails": 1,
"friends": ["Free Code Camp Campers"],
"bark": "woof"
};

// Only change code below this line.

delete myDog.bark;

// Only change code above this line.

(function(z){return z;})(myDog);

Issue:

Properties box says:

"Let's delete the "tails" property from myDog."

Test success statement:

"Delete the property "bark" from myDog."

Test succeeds on deleting bark property, not tails.
Issue 1:
Here's my problem.

Using react-router 1.0, i'm going to be re-rendering trees that are 90% the same. We use an external lib for an api that produces video mark up. Totally out of our hands. They modify the dom and that's how it has to be.

My problem comes in that when the routing changes, it re-renders the tree, and wipes out the custom DOM put in by the third party api.

I've tried things like returning false from shouldComponentUpdate always.. using dangerouslySetInnerHtml={{__html: ''}} to a blank string hoping that react would internally not do diff's on it.. nothing seems to work.

Is there anything I can do to stop it?

Issue 2:
When writing a component that contains a set of large subtrees that stay relatively the same, but are simply moved around such that React's virtual DOM diffing can't detect the movement, React will end up recreating huge trees it should simply be moving.

For example, pretend blockA and blockB are very large structures. They may be made of several levels of children and components. For example one could be the entire page contents and the other the sidebar, while this render() is the page root.

render() {
var blockA = <div>AAA</div>,
blockB = <div>BBB</div>;

if ( this.props.layoutA ) {
return <div>
<div className="something">{blockB}</div>
<div className="something">{blockA}</div>
</div>;
} else {
return <div>
{blockA}
{blockB}
</div>;
}
}

Because the blocks aren't at the same level React cannot see the relation between these blocks and key cannot be used to give React any hints. As a result, when layoutA is changed, instead of the two blocks being moved to their new location the entire page is essentially completely unrendered and then re-rendered from scratch.

I understand why this is the case. It would be far to expensive for React to be able to detect movement of nodes like this.

But I do believe we need a pattern to hint to React that this component has large blocks that may be moved around at different levels.

Note that there may be a component in between the rendering component root and the block. So parent semantics scoped to the nearest component won't work. This'll need owner scoping.

I understand that React is trying to eliminate the need for React.createElement to be used and owner scoping within special attributes interferes with that. So instead of a component scoped key="" variant I think a method/object style interface kind of like React.addons.createFragment might work.
Issue 1:
Do you want to request a feature or report a bug?

Bug

What is the current behavior?

The DOM property dateTime isn't converted to its lowercase attribute counterpart datetime for the <time> element when the element is rendered with ReactDOMServer.renderToString().

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template for React 16: https://jsfiddle.net/Luktwrdm/, template for React 15: https://jsfiddle.net/hmbg7e9w/).

const React = require('react');
const ReactDOMServer = require('react-dom/server');

const markup = ReactDOMServer.renderToString(React.createElement('time', {
dateTime: "2017-11-02T20:49:25+01:00"
}));
console.log(markup);

The above will print <time dateTime="2017-11-02T20:49:25+01:00" data-reactroot=""></time>.

What is the expected behavior?

The above output should be <time datetime="2017-11-02T20:49:25+01:00" data-reactroot=""></time>.

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

React 16.0.0

React DOM 16.0.0

Node v6.11.5

Issue 2:
Do you want to request a feature or report a bug?

Bug

What is the current behavior?

ReactDOMServer generates camelCased markup for the cellSpacing and cellPadding attributes:

<table cellSpacing="1" cellPadding="2"></table>

(Here's an example pen: https://codepen.io/anon/pen/jGBLdP)

I believe these attributes are canonically lowercased. If I lowercase the attributes in JSX, React warns that I'm not using the right names:

Warning: Invalid DOM property `cellpadding`. Did you mean `cellPadding`?

What is the expected behavior?

The attribute names would be rendered lowercase:

<table cellspacing="1" cellpadding="2"></table>

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

This is in 16.0.0. Prior versions of React stripped these attributes.
Issue 1:
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke-test/13512/

Run so broken it didn't make JUnit output!

Issue 2:
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke-test/13477/

Run so broken it didn't make JUnit output!
Issue 1:
This is on scipy 0.13.0:

from scipy.signal import lti
import matplotlib.pyplot as plt

for zeta in [0.99999, 1.00000, 1.00001]:
H = lti([1],[1,2*zeta,1])
t,y = H.step()
plt.figure()
plt.plot(t,y)

The zeta = 0.99999 and 1.00001 cases give expected results, but with zeta = 1.00000 the output zooms off to infinity.

Issue 2:
A 6th order analog filter appears very distorted in scipy.signal.step compared to Octave:

z = array([], dtype=float64)
p = array([-2.8576, -2.8576, -2.8576, -2.8576, -2.8576, -2.8576])
k = 544.49693870986994
t_s, y_s = step((z, p, k), T=t)
plot(t_s, y_s)

vs Octave:

z = []
p = [-2.8576 -2.8576 -2.8576 -2.8576 -2.8576 -2.8576]
k = 544.49693870986994
step(zpk(z, p, k), 8)

Even 4th order filters are visibly inaccurate, settling at 1.02 instead of 1.00, which is not a very high-order filter
Issue 1:
Description of the new feature/enhancement

when typing "shift + insert",wsl should insert the content in clipboard into command line

Proposed technical implementation details (optional)

Issue 2:
ctrl+c for copy
ctrl+v for past

why we can't use ctrl+c and ctrl+v in window console? this confuses me for years. the copy and paste are very painful comparing with Mac and Linux, which is the primary reason why I give up development in Windows.

also , I'd like to add some global keyboard shortcuts that works for console and for the whole Windows system. can we do this?

ctrl+a for jump to line head
ctrl+e for jump to line end
Issue 1:
Using your latest version, turns out webpack is producing broken JS code

https://gist.githubusercontent.com/binarykitchen/a1899291fc3b470ba83cb9a245317775/raw/60de0910ca0a6bef87d96a202de8faa0ffb785ce/gistfile1.txt

Chrome complains with

index.coffee:2 Uncaught SyntaxError: missing ) after argument list
at Object../lib/jquery/index.coffee (lib.js:851)
at __webpack_require__ (lib.js:710)
at fn (lib.js:95)
at eval (multi_jquery_goog_ext:1)
at Object.1 (lib.js:1060)
at __webpack_require__ (lib.js:710)
at lib.js:762
at lib.js:765

Tried to find this out by eliminating each option one after one but no luck. Any clues what this could be? I have this error three times for all my three entry points in development mode.

Issue 2:
Bug report

What is the current behavior?

React app doesn't load and throws this console error.

Temporary fixable by disabling the hard-source-webpack-plugin from your Webpack config. Your react app will take a lot longer to build since its not reading from a cache anymore

If the current behavior is a bug, please provide the steps to reproduce.

Run an npm start, load your page, kill npm, run npm start again so webpack reads from the hard-source cache, load your page, and inspect to see the console error

What is the expected behavior?

I can run webpack and kill it any number of times, and when reading from the hard-source cache, the react app still builds and doesn't throw an unknown error

Other relevant information:

webpack version: 4.20.2

Node.js version: 10.11.0

Operating System: MacOS High Sierra 10.13.6

Additional tools:
Issue 1:
Describe the bug

I observe a memory leak when I request a file and pipe to another request and I get the error "Request body larger than maxBodyLength limit"

To Reproduce

To reproduce the problem, I request a file of 20MB and pipe to another request.

Bellow there a sample code:

const optsGetFile = {
method: "get",
url: "http://localhost:7001/download",
responseType: "stream",
};
const optsUploadFile = {
method: "post",
url: "http://localhost:7001/upload",
};

axios(optsGetFile)
.then(({ headers, data }) => {
return axios(_.assign(optsUploadFile, { data, headers }));
})

The entire test code is present at https://github.com/jose-lopes/test_axios .

Next I will describe the environment that I setup to reproduce the problem.

Start fake server. (This program serve /upload and /download (20MB) requests)

node test_fakeserver.js

Start test server and monitor memory with memory-profiler. (This program serve /record request, which it get /download and post to /upload)

mprof run node test.js

execute 20 /record requests with interval of 30 seconds

for test in $(seq 1 20); do curl -X POST localhost:7000/record; sleep 30; done

Stop test server and execute mprof plot to check memory behavior.

mprof plot

Expected behavior

I expected no memory leak even when we got the error "Request body larger than maxBodyLength limit".

I executed again the test server with option maxBodyLength: 3010241024 and I got no memory leak.

Environment

Axios Version: 0.21.0

Node.js Version: v14.15.0

OS: Arch Linux

Additional context/Screenshots

Graph when I execute to reproduce:

Issue 2:
Describe the bug

I observe a memory leak when I pipe two requests with a file and I get the error "Request body larger than maxBodyLength limit"

To Reproduce

To reproduce the problem, I request a file of 20MB and pipe to another request.

Bellow there a sample code:

const optsGetFile = {
method: "get",
url: "http://localhost:7001/download",
responseType: "stream",
};
const optsUploadFile = {
method: "post",
url: "http://localhost:7001/upload",
};

axios(optsGetFile)
.then(({ headers, data }) => {
return axios(_.assign(optsUploadFile, { data, headers }));
})

The entire test code is present at https://github.com/jose-lopes/test_axios .

Next I will describe the environment that I setup to reproduce the problem.

Start fake server. (This program serve /upload and /download (20MB) requests)

node test_fakeserver.js

Start test server and monitor memory with memory-profiler. (This program serve /record request, which it get /download and post to /upload)

mprof run node test.js

execute 20 /record requests with interval of 30 seconds

for test in $(seq 1 20); do curl -X POST localhost:7000/record; sleep 30; done

The execution produces the next graph:

Expected behavior

I expected no memory leak even we got the error "Request body larger than maxBodyLength limit".

I executed again the test with option maxBodyLength: 3010241024 and got the next graph without memory leak.

Environment

Axios Version: 0.21.0

Node.js Version: v14.15.0

OS: Arch Linux

Additional context/Screenshots
Issue 1:
tsc version 1.7.5

target == es6

Notice how the import of 'routes' changes to 'routes_1' in the compiled version (var routes_1 = require('../common/routes');), but the object literal for 'routes' (react_router_1.match({ routes, location: req.url }...) does not.

INPUT

// server.tsx

const express = require('express');
const app = express();

import { renderToString } from 'react-dom/server';
import {
Route,
Router,
match,
RoutingContext } from 'react-router';
import React = require('react');
import invariant = require('invariant');

import {
routes,
} from '../common/routes';

import {
HttpMethods,
RequestStates
} from '../common/utils/http';

app.get('*', (req: any, res: any) => {
match({ routes, location: req.url }, (error: any, redirectLocation: any, renderProps: any) => {
if (error) {
res.status(500).send(error.message)
} else if (redirectLocation) {
res.redirect(302, redirectLocation.pathname + redirectLocation.search)
} else if (renderProps) {
console.log('renderProps', renderProps);
res.status(200).send(renderToString(<RoutingContext {...renderProps} />))
} else {
res.status(404).send('Not found')
}
})
});

const server = app.listen(3000, function () {
const host = server.address().address;
const port = server.address().port;

console.log('Example app listening at http://%s:%s', host, port);
});

OUTPUT

const express = require('express');
const app = express();
var server_1 = require('react-dom/server');
var react_router_1 = require('react-router');
var React = require('react');
var routes_1 = require('../common/routes');

app.get('*', (req, res) => {
react_router_1.match({ routes, location: req.url }, (error, redirectLocation, renderProps) => {
if (error) {
res.status(500).send(error.message);
}
else if (redirectLocation) {
res.redirect(302, redirectLocation.pathname + redirectLocation.search);
}
else if (renderProps) {
console.log('renderProps', renderProps);
res.status(200).send(server_1.renderToString(React.createElement(react_router_1.RoutingContext, React.__spread({}, renderProps))));
}
else {
res.status(404).send('Not found');
}
});
});
const server = app.listen(3000, function () {
const host = server.address().address;
const port = server.address().port;
console.log('Example app listening at http://%s:%s', host, port);
});```

Issue 2:
Using typescript@next (1.8.0-dev.20151109) and the following compilerOptions:

"compilerOptions": {
"target": "ES6",
"module": "commonjs"
}

Any code using named import as a shorthand property will result in invalid code being generated.

Example:

import {foo} from './foo';
const test = {
foo
};

generates

var foo_1 = require('./foo');
const test = {
foo
};

ReferenceError: foo is not defined
Issue 1:
Proxy CONNECT support is required for https urls to work.

When proxy support was added to Scrapy, urllib still didn't supported CONNECT, but that has been fixed now:

http://bugs.python.org/issue1424152

Now we need to add support to Scrapy (which doesn't use urllib at all).

This link contains useful tips on how to add CONNECT support with Twisted:

http://twistedmatrix.com/pipermail/twisted-web/2008-August/003878.html

See originally reported ticket on Trac for more comments: http://dev.scrapy.org/ticket/159

Issue 2:
I have a spider that's throwing the following error when trying to crawl this URL.

>>> fetch('https://vconnections.org/resources')
2015-08-12 10:07:28 [scrapy] INFO: Spider opened
2015-08-12 10:07:28 [scrapy] DEBUG: Retrying <GET https://vconnections.org/resources> (failed 1 times): [<twisted.python.failure.Failure <class 'OpenSSL.SSL.Error'>>]
2015-08-12 10:07:33 [scrapy] DEBUG: Gave up retrying <GET https://vconnections.org/resources> (failed 2 times): [<twisted.python.failure.Failure <class 'OpenSSL.SSL.Error'>>]
Traceback (most recent call last):
File "<console>", line 1, in <module>
File "/Users/gmeans/.virtualenvs/backlink/lib/python2.7/site-packages/scrapy/shell.py", line 87, in fetch
reactor, self._schedule, request, spider)
File "/Users/gmeans/.virtualenvs/backlink/lib/python2.7/site-packages/twisted/internet/threads.py", line 122, in blockingCallFromThread
result.raiseException()
File "<string>", line 2, in raiseException
ResponseNeverReceived: [<twisted.python.failure.Failure <class 'OpenSSL.SSL.Error'>>]

Other SSL urls work fine, and I tried implementing the solution from this previous issue:

#981

class CustomContextFactory(ScrapyClientContextFactory):
def getContext(self, hostname=None, port=None):
ctx = ClientContextFactory.getContext(self)
# Enable all workarounds to SSL bugs as documented by
# http://www.openssl.org/docs/ssl/SSL_CTX_set_options.html
ctx.set_options(SSL.OP_ALL)
if hostname:
ClientTLSOptions(hostname, ctx)
return ctx

Scrapy==1.0.3

Twisted==15.3.0

pyOpenSSL==0.15.1

OpenSSL 1.0.1k 8 Jan 2015

Any ideas on what else I could try? Thanks!
Issue 1:
This is a feature request.

I suggest that we can assign DOM Node to the member of vm.$data like following example.

Template:

<div id="bar">
<div>{{content}}</div>
</div>

Vue:

var node = ...; // `DOM::Node` or `DOM::DocumentFragment`

new Vue({
el: "#bar",
data: {
content: node // This DOM Node will replace `{{content}}` in the above template.
}
});

This use-case

This proposal's use-case is when we need to insert DOM Node directly. In some case, we append the content sanitized with using DOM::DOMParser and traversing it.

Issue 2:
I've already mentioned it in issue #384, but I'd like to gain access to a specific dom node without creating a child VM when not needed, very close to what v-ref do.

So i've thought of something like this:

<canvas v-el="myCanvas"></canvas>

Then using it in parent VM like this:

var ctx = this.$$.myCanvas.getContext('2d');

What would be your approach in this use case? Is $$ appropriated?

Here is a directive I made that do the trick. Please tell me what you think.
Issue 1:
This is magical:

julia> (1:4) .+ (1:4)
2:2:8

I love that we can be so clever. Unfortunately, it can come back and bite us sometimes:

julia> (1:4) .+ (4:-1:1)
ERROR: ArgumentError: step cannot be zero
Stacktrace:
[1] steprange_last(::Int64, ::Int64, ::Int64) at ./range.jl:137
[2] Type at ./range.jl:127 [inlined]
[3] _rangestyle at ./range.jl:90 [inlined]
[4] _range at ./range.jl:88 [inlined]
[5] #range#29 at ./range.jl:73 [inlined]
[6] #range at ./none:0 [inlined]
[7] + at ./range.jl:890 [inlined]
[8] broadcasted at ./broadcast.jl:969 [inlined]
[9] broadcasted(::Function, ::UnitRange{Int64}, ::StepRange{Int64,Int64}) at ./broadcast.jl:1146
[10] top-level scope at none:0

This is very clearly due to us trying to construct the range [5:0:5] that is supposed to be 4 elements long, but unfortunately we lose that information since it's supposed to be implicit in start, stop and step. The range abstraction doesn't know what to do here, and so we fail out.

Likely we should have a fallback for this cleverness that simply constructs an array, but I don't like the idea that Range + Range = Union{Range,Vector}. I would rather that we had a different abstraction similar to UnitRange, perhaps called ConstantRange or something, that takes in a value and an explicit length so that we don't have some poor fool who is doing something like:

for stepA in 1:3
for stepB in -3:-1
x = (1:stepA:stepA*1000000000) .+ (stepB*-1000000000:stepB:1)
println(sum(x))
end
end

and have his memory blow up for very particular values of stepA and stepB. (Note that the code sample above, fanciful as it is, fails on current versions of Julia because it cannot finish the summation of the two ranges)

Issue 2:
Julia 1.0:

I observed that when starting up Julia with the --math-mode=fast option, I get incorrect results for sinpi and cospi functions.

With the default math mode:

julia> a = rand(5)
5-element Array{Float64,1}:
0.5897641978923696
0.2459464145866952
0.06373272357797632
0.26244049804714087
0.7254898186800567

julia> cospi.(a)
5-element Array{Float64,1}:
-0.27827964958957724
0.7160540045153001
0.9800223981473272
0.6789380012385138
-0.650617399829044

julia> sinpi.(a)
5-element Array{Float64,1}:
0.9605000971495538
0.6980448858186719
0.19888715174581242
0.7341956077737403
0.7594056880480248

while with --math-mode=fast option:

julia> cospi.(a)
5-element Array{Float64,1}:
1.0
1.0
1.0
1.0
1.0

julia> sinpi.(a)
5-element Array{Float64,1}:
0.0
0.0
0.0
0.0
0.0
Issue 1:
Description of the new feature/enhancement

The ability to create a new tab with 'Run as a different user' option would be nice. I often need to run shells as different users.

Issue 2:
Description of the new feature/enhancement

Add ability to open new tabs that run one (or more) custom command before the opening

Proposed technical implementation details (optional)

In the profile.json add add a new field, for example commands:

{
"acrylicOpacity" : 0.5,
"background" : "#012456",
"closeOnExit" : true,
"colorScheme" : "Campbell",
"commandline" : "powershell.exe",
"cursorColor" : "#FFFFFF",
"cursorShape" : "bar",
"fontFace" : "Consolas",
"fontSize" : 10,
"guid" : "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
"historySize" : 9001,
"icon" : "ms-appx:///ProfileIcons/{61c54bbd-c2c6-5271-96e7-009a87ff44bf}.png",
"name" : "Conda",
"padding" : "0, 0, 0, 0",
"snapOnInput" : true,
"startingDirectory" : "%USERPROFILE%",
"useAcrylic" : true,
"commands": ["$env:Path += ";PathToConda""]
}

where commands are the commands that the terminal will execute before opening the new tab, in the example it will add the path to conda to the environmental path for the session

a dirty image of what i am talking about