WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
In a really long line of text, after the 235th character, Ruby language formatting is lost, and shows up as the last mark, such as a closing quote makes the rest of the text appear as green, or grey. This still happen with the text being word-wrapped.

Issue 2:
I opened a Python file with the following line (#963):

PrintAndLog(u"SSID: " + RememberedNetwork["SSIDString"].decode("utf-8") + u" - BSSID: " + RememberedNetwork["CachedScanRecord"]["BSSID"] + u" - RSSI: " + str(RememberedNetwork["CachedScanRecord"]["RSSI"]) + u" - Last connected: " + str(RememberedNetwork["LastConnected"]) + u" - Security type: " + RememberedNetwork["SecurityType"] + u" - Geolocation: " + Geolocation, "INFO")

Which led to the following bug:

You can find this as the main file in osxauditor.py.
Issue 1:
When using InstancedMesh for repeating objects and then exporting it through ColladaExporter, only the base mesh appears in exported model, no instances.

Issue 2:
Description of the problem

Since the new animation system I can't make my key animations stop at their last frame. Most of the Three.js examples have animations with a infinite loop and so the bug is not visible. My animations are made to run once, but they get resetted to the first frame after the one loop. Even when I use .time = 1; command, they still reset to the first frame.

Three.js version

r75

r74

r73

Browser

All of them

OS

All of them
Issue 1:
by x41@freeshell.org:

Exploiting #221 in a different way:
Fresh install of:

Last version of Golang
cb140bac9ab0 release.2009-11-12/release

Tested on Ubuntu 9.04 and Ubuntu 9.10
XXXX@XXXX:~/go_src/src$ uname -a
Linux XXXX 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
i686 GNU/Linux

Attached Valgrind report and GDB report.

Binary: 8a

go_src/src/lib9/main.c

Breakpoint 1, main (argc=0x2, argv=0xbfdd72d4) at
/home/dsdsds/go_src/src/lib9/main.c:35
35 p9main(argc, argv);
gdb> list
30 extern void p9main(int, char**);
31
32 int
33 main(int argc, char **argv)
34 {
35 p9main(argc, argv);
#######################################
HERE
36 exits("main");
37 return 99;
HERE
#######################################
38 }

Run it
r `python -c 'print "\x41"*99 + "\x42"'`
Just.. 99 + 1

Thanks guys!

Attachments:

debuginfo1.tar.gz (2029 bytes)

Issue 2:
Before filing a bug, please check whether it has been fixed since
the latest release: run "hg pull", "hg update default", rebuild, and
retry
what you did to
reproduce the problem. Thanks.

What steps will reproduce the problem?
Attempt to use the http.Client using the default Transport when
hitting a server who's TLS cert hostname does not match the DNS name.

What is the expected output?
The transport will fail with an error.

What do you see instead?
Optionally allow such a connection to succeed.
(disable the check in http/transport.go:365)

Which compiler are you using (5g, 6g, 8g, gccgo)?
6g

Which operating system are you using?
Linux

Which revision are you using? (hg identify)
99ea0887e633+ tip

Please provide any additional information below.
Suggest adding an field in either http.Transport or tls.Config like DisableHostnameCheck.
Issue 1:
Version Info

electron: 4.0.0

OS: Windows 10 x64 10.0.17134.472

Expected Behavior

require('crypto').createCipheriv('rc4', 'asdasd', null)
require('crypto').createCipheriv('rc4', 'asdasd', '')

work well as node v10.15.0

Actual behavior

require('crypto').createCipheriv('rc4', 'asdasd', null)

cause renderer process crash

require('crypto').createCipheriv('rc4', 'asdasd', '')

throw

Invalid IV length
at Cipheriv.createCipherBase (internal/crypto/cipher.js:79)
at Cipheriv.createCipherWithIV (internal/crypto/cipher.js:119)
at new Cipheriv (internal/crypto/cipher.js:225)
at Object.createCipheriv (crypto.js:105)
at <anonymous>:1:19
createCipherBase @ internal/crypto/cipher.js:79
createCipherWithIV @ internal/crypto/cipher.js:119
Cipheriv @ internal/crypto/cipher.js:225
createCipheriv @ crypto.js:105

To Reproduce

exec code above in devTools

Issue 2:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

Electron Version: 9.0.5

Operating System: Windows 10

Last Known Working Electron version: I didn't work with electron for a long time, but last time I played with it the app had similar runtime reloading stuff going on and I don't remember it ever causing issues. That was Electron 1.6.2

Expected Behavior

Reloading window with any of (renderer process) location.reload(), or (main process) window.reload(), window.webContents.reload(), window.webContents.reloadIgnoringCache(), should reload the process and work just as initial load of the same file.

Actual Behavior

Whenever I try reloading window (no matter the method, as described above), my app initialization process hangs as soon as it touches fs.readdir() call, despite it working just fine on initial load. No errors or any indication or clue anywhere as to what might be happening.

Here is the snippet from the isolated example below:

const FS = require('fs');
const {promisify} = require('util');
const readdir = promisify(FS.readdir);

async function load() {
console.log('load(): start');
try {
await readdir('.'); // <= it hangs here on reload
document.body.innerHTML = 'success! press F5 to reload';
} catch (error) {
document.body.innerHTML = `<pre>${error.message || error.stack}</pre>`;
}
console.log('load(): end');
}

load().then(console.log, console.error);

To Reproduce

git clone https://gist.github.com/aa794ac2dc3662fee5d800da420a4813.git reloadbug
cd reloadbug
npm install
npm start

Hit F5 until it happens. On my app it happens almost 100% of the time. In the reproduction example around 50% of the time.

Screenshots
Issue 1:
Developers often use code samples in their module readmes, so it would be really nice to have deno fmt format the code inside markdown code blocks. This would lead to more consistent styles in presentation as well. :)

Issue 2:
At the moment Deno only formats JS and TS, but dprint can also format markdown including JS and TS code blocks:

#6682 (comment)

This would be an awesome feature for documentation, is it possible to enable it? Then we can get rid of Prettier.
Issue 1:
There are many different implementations of essentially the same module resolution algorithm in our system. They all do the same, but are used in different situations.

CliModuleLoader::resolve link

Used with run --no-check and probably also for pure JS.

deno::tsc::op_resolve link

Used with type checking. Calls deno::graph::Graph::resolve

deno::lsp::tsc::op_resolve link

Special resolver for LSP. Does not call deno::graph::Graph::resolve.

deno_graph::source::Resolver::resolve link

Trait for resolving modules, similar to deno_core::ModuleLoader::resolve

eszip::resolve_import::resolve_import link

used just for eszip

deno_core::ModuleLoader::resolve link

(Feel free to add to this list if you find more)

Issue 2:
@MarkTiedemann I was wondering if the jsdom port is still happening? I see it was never merged: denoland/deno_std#542

It would be amazing to be able to test code for the browser in Deno 1.0. Thanks!
Issue 1:
due to the use of apply_over_axis masked median operations gets incredibly slow when computing them along a small dimension of a large array:

In [3]: d = np.random.uniform(size=(200, 200, 50))
In [4]: %timeit np.median(d,axis=2)
10 loops, best of 3: 40.1 ms per loop
In [5]: %timeit np.nanmedian(d,axis=2)
1 loops, best of 3: 1.32 s per loop
In [6]: %timeit np.ma.median(d,axis=2)
1 loops, best of 3: 4.89 s per loop

a way out is using bottlenecks nanmedian which is on par with our non-masked performance (and better for the slow axis) but I think we should think of ways to improve this in numpy.

I can think of following improvements for median:

implement apply_over_axis in C, should be relatively easy but will only give us ~50% boost at best. it should still be worthwhile as there are likely more users of that function out there.

extend partition to broadcast the index, then one could compute the right index from the mask and do everything in one partition call. Probably worthwhile but it will make the partition interface more complicated and would probably imply rewritting our pretty ugly sorting code.

probably the simplest would be add a check on the size of the axis and use sort instead of partition as currently done in ma.median but then instead of selecting via apply_along_axis, one selects the elements to average (or not) via fancy indexing (always select the middle two and if the non-masked count is odd duplicate one of the elements so mean() does nothing)

add a MaskedPartition C-Api function

see if we can integrate bottleneck directly somehow

any more options I'm might be overlooking?

Issue 2:
We have two pages labeled "diversity statement":

The new one: NumPy diversity and inclusion statement

The one in the Code of Conduct: Diversity Statement

Neither mentions the other.

Should the new statement have at least a link to the CoC diversity statement?

Should the new statement say "September 2020" in the title to indicate that it's issued at a particular point in time in response to events (unlike the CoC), and will be updated?

NumPy diversity and inclusion statement: September 2020
Issue 1:
Right now there are at least 3 places with duplicates of the .tmbundle: here, here, and here.

This has worked fine so far, I think people have been good about syncing changes with the main repo and pulling when there are improvements.

But eventually I think it will become a pain. Even now it's potentially unclear where you should submit pull requests. So I think it should be pulled out and, where convenient, submoduled back in.

Issue 2:
I thought this was just an issue in StaticArrays (JuliaArrays/StaticArrays.jl#428), but the same thing is happening in Base.

Currently:

julia> mutable struct MyNumber
val::Float64
end

julia> Base.zero(::Type{MyNumber}) = MyNumber(0.0)

julia> v = zero([MyNumber(1.0), MyNumber(2.0)])
2-element Array{MyNumber,1}:
MyNumber(0.0)
MyNumber(0.0)

julia> v[1].val = 1
1

julia> v
2-element Array{MyNumber,1}:
MyNumber(1.0)
MyNumber(1.0)

I think this is not desirable for non-isbits types.
Issue 1:
when running _nodes?plugin=true it would be great to be able to get the version of the installed plugins

Issue 2:
Relative to #2668

Plugin developpers can now add a version number to their es-plugin.properties file:

plugin=org.elasticsearch.test.integration.nodesinfo.TestPlugin
version=0.0.7-SNAPSHOT

Also, for site plugins, it's recommended to add a es-plugin.properties file in root site directory with description and version properties:

description=This is a description for a dummy test site plugin.
version=0.0.7-BOND-SITE

When running Nodes Info API, you will get information on versions:

$ curl 'http://localhost:9200/_nodes?plugin=true&pretty'

{
"ok" : true,
"cluster_name" : "test-cluster-MacBook-Air-de-David.local",
"nodes" : {
"RHMsToxiRcCXwHiS6mEaFw" : {
"name" : "node2",
"transport_address" : "inet[/192.168.0.15:9301]",
"hostname" : "MacBook-Air-de-David.local",
"version" : "0.90.0.Beta2-SNAPSHOT",
"http_address" : "inet[/192.168.0.15:9201]",
"plugins" : [ {
"name" : "dummy",
"version" : "0.0.7-BOND-SITE",
"description" : "This is a description for a dummy test site plugin.",
"url" : "/_plugin/dummy/",
"site" : true,
"jvm" : false
} ]
},
"IKiUOo-LSCq1Km1GUhBwPg" : {
"name" : "node3",
"transport_address" : "inet[/192.168.0.15:9302]",
"hostname" : "MacBook-Air-de-David.local",
"version" : "0.90.0.Beta2-SNAPSHOT",
"http_address" : "inet[/192.168.0.15:9202]",
"plugins" : [ {
"name" : "test-plugin",
"version" : "0.0.7-SNAPSHOT",
"description" : "test-plugin description",
"site" : false,
"jvm" : true
} ]
},
"H64dcSF2R_GNWh6XRCYZJA" : {
"name" : "node1",
"transport_address" : "inet[/192.168.0.15:9300]",
"hostname" : "MacBook-Air-de-David.local",
"version" : "0.90.0.Beta2-SNAPSHOT",
"http_address" : "inet[/192.168.0.15:9200]",
"plugins" : [ ]
},
"mGEZcYl8Tye0Rm5AACBhPA" : {
"name" : "node4",
"transport_address" : "inet[/192.168.0.15:9303]",
"hostname" : "MacBook-Air-de-David.local",
"version" : "0.90.0.Beta2-SNAPSHOT",
"http_address" : "inet[/192.168.0.15:9203]",
"plugins" : [ {
"name" : "test-plugin",
"version" : "0.0.7-SNAPSHOT",
"description" : "test-plugin description",
"site" : false,
"jvm" : true
}, {
"name" : "test-no-version-plugin",
"version" : "NA",
"description" : "test-no-version-plugin description",
"site" : false,
"jvm" : true
}, {
"name" : "dummy",
"version" : "NA",
"description" : "No description found for dummy.",
"url" : "/_plugin/dummy/",
"site" : true,
"jvm" : false
} ]
}
}
}
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

I have searched out and get #8223 but I cant get any solution

Expected Behavior

In production build of commonjs classnames should not be duplicated

Current Behavior

There is several classnames generated with same identifier

My webpack config for the plugin

module.exports = {
output: {
path: path.resolve(__dirname, 'dist'),
filename: 'index.js',
libraryTarget: 'commonjs2', // common js build
},
plugins: [
new PeerDepsExternalsPlugin(), // will be transform to externals with the list of peer deps(material-ui here as well)
]
}

Your Environment

Tech
Version

Material-UI
1.0.0-beta.17

React
16.0.0

browser
any

etc

Issue 2:
I use dialog fullScreen. When I click button open full-screen dialog, and no any operation even no click anywhere, then press 'esc' key to escape fullscreen. That button still has focus styles. This is not a issue, I just want to know how can I do remove the styles with no operation.

I have searched the issues of this repository and believe that this is not a duplicate.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.11

React
16.0.0

browser
chrome

etc
Issue 1:
Since latest beta, the generated transition property for tabs indicator is transition: all 300ms cubic-bezier(0.4, false, false.2, false) 0ms which is invalid

I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

The default transitions property should be properly generated.

Current Behavior

The default transitions property is wrong.

Your Environment

Tech
Version

Material-UI
beta 28

React
16

browser
Chrome 63

etc
TS 2.6.2

Issue 2:
After installing the typescript/material/react example I saw that the build was failing. Then I found these two issues regarding the build problems I was experiencing: #9881, #9873

I would like to suggest fixing the dependency versions in place. They don't need to be exact of course.

With the dependencies declared as latest I don't have a starting point for debugging.

I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Example build should always be working as it's a starting point for new users.

Current Behavior

Build is broken and will be in the future as well.

Steps to Reproduce (for bugs)

Clone the example

Try to build

It will fail

Your Environment

"dependencies": {
"material-ui": "next",
"react": "latest",
"react-dom": "latest",
"react-scripts-ts": "latest"
},
"devDependencies": {
"@types/jest": "latest",
"@types/node": "latest",
"@types/react": "latest",
"@types/react-dom": "latest",
"@types/react-transition-group": "^2.0.6"
}
Issue 1:
sharex=False works as expected:

titanic = sns.load_dataset("titanic")
titanic = titanic.assign(deck=titanic.deck.astype(object)).sort_values("deck")
g = sns.FacetGrid(titanic, col="sex", sharex=False, sharey=False)
g.map(sns.histplot, "age");

but is ignored when using displot:

sns.displot(titanic, x='age', col='sex', facet_kws=dict(sharex=False, sharey=False));

Versions:

matplotlib 3.4.1 pypi_0 pypi
seaborn 0.11.1 pypi_0 pypi

Issue 2:
Trying to create a displot with non-shared axis (both y and x) using the following function call:

import seaborn as sns
_df = sns.load_dataset("tips")
sns.displot(data=_df, x='tip', col='day', hue='smoker', stat="density", element='step', facet_kws={'sharex': False, 'sharey': False})

The result is, X axis are still shared

I've tried using FacetGrid with histplot, but then I can't get a legend.

g = sns.FacetGrid(_df, col="day", sharex=False, sharey=False)
g.map_dataframe(sns.histplot, x="tip", stat="density", element="step", hue="smoker").add_legend()

matplotlib 3.2.1

seaborn-0.11.0

Also tried upgrading to

seaborn-0.11.1

same issues
Issue 1:
Version

2.5.13

Reproduction link

https://codesandbox.io/s/4895o6nm24

Steps to reproduce

Using Typescript 2.7.1, importing Vue 2.5.13 results in undefined.

To reproduce, create a blank .ts file:

import Vue from "vue";
console.log(Vue); // <-- will be `undefined` (or `null` in Code Sandbox)

This can be fixed by importing like:

import * as Vue from "vue";

... but then new Vue() returns the TS error:

test.ts (3,1): Cannot use 'new' with an expression whose type lacks a call or construct signature. (2351)

Changing this to new Vue.default(); resolves the TS error, but then results in a Node error:

TypeError: Vue.default is not a constructor

What is expected?

No errors

What is actually happening?

See above

Note: I'm not using Webpack in this example. What I assume is happening (referencing the recommended tsconfig.json config) is that import statements are being as-is by Typescript, for Webpack to pick up and use properly.

However, I think that this should be improved to work with Typescript directly, without requiring Webpack to enter the mix. This would benefit server-only environments where code transpilation isn't necessarily required.

Issue 2:
Version

2.5.13

Reproduction link

https://github.com/marpstar/vue-typescript-import-problems

Steps to reproduce

# Clone this repo
git clone https://github.com/marpstar/vue-typescript-import-problems.git

# Install dependencies
npm install

# Compile TS
tsc

# Launch app. You'll see an error "vue_1.default is not a constructor"
node build/main.js

What is expected?

I can create a new Vue instance using the constructor.

What is actually happening?

I get an error "TypeError: vue_1.default is not a constructor"

I believe this is related to the issue #7374, which I've included my comments below:

I'm using commonjs output from TypeScript (no webpack). One similarity between OP and I is that we're both using the TypeScript baseUrl option. Something is definitely wrong with the standard import in TypeScript.

I too am using Vue 2.5.13. I'm setting up SSR on Node 8.9.3 and TypeScript 2.6. My tsconfig.json looks like this:

{
"compilerOptions": {
"outDir": "build",
"target": "es6",
"module": "commonjs",
"moduleResolution": "node",
"sourceMap": true,
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
"rootDir": "./src",
"baseUrl": "./src",
"noUnusedLocals": true
},
"exclude": [
"node_modules",
"typings"
]
}

I tried a number of other workaround, including trying to load the vue.esm.js file via the compilerOptions.paths property, without success. I was getting the exact same vue_1.default is not a constructor error as OP.
Issue 1:
Running

php app/console doctrine:generate:entities MyBundle:MyEntity

on v2.5.0 I get

Deprecated: getEntityNamespace is deprecated since Symfony 2.1. Use
getAliasNamespace instead in .../Doctrine/Bundle/DoctrineBundle/Registry.php
on line 129

Issue 2:
Can I have this:

No more app_dev.php or app.php

Just

index.php

So what about environments?

config/app.yml

What would be in it?

app
environments: ['local'=>'local.domain', 'dev'=>'dev.mysite']

Then I propose an environment detection that loops trough the array in the app config

and loads the right config files, ONLY if they are present. Else they will fall back to default.

So.. how would that look like? Folder structure:

The current situation and the default config file for persistence info:

config/database.yml

Then if I would like to have a different config for dev:

config/dev/database.yml

This will override only the differences. For example.. the password or db user

Then if I would like to have a different config for staging:

config/staging/database.yml

Great!
Issue 1:
Bug report

Bug summary

Minor ticklabels are missing at positions of major ticks.

Code for reproduction

import numpy as np
import matplotlib.dates as mdates
import matplotlib.pyplot as plt

t = np.arange("2018-11-03", "2018-11-06", dtype="datetime64")
x = np.random.rand(len(t))

fig, ax = plt.subplots()
ax.plot(t,x)

ax.xaxis.set_major_locator(mdates.DayLocator())
ax.xaxis.set_major_formatter(mdates.DateFormatter('\n%a'))

ax.xaxis.set_minor_locator(mdates.HourLocator((0,6,12,18)))
ax.xaxis.set_minor_formatter(mdates.DateFormatter('%H:%M'))

plt.show()

Actual outcome

The above code run with current master produces

The minor ticklabels showing the 00:00 hours are missing.

Expected outcome

The expected outcome would be the same as when running the code with matplotlib 3.0.2 or below:

I would expect to see the hours throughout.

Matplotlib version

Operating system: Win8

Matplotlib version: master

Matplotlib backend (print(matplotlib.get_backend())): any

Python version: 3.6

Issue 2:
Bug report

Bug summary

Images plotted by plt.imshow are always clipped, reglardless of the clip_on argument.

Code for reproduction

import numpy as np
import matplotlib.pyplot as plt
from matplotlib.cbook import get_sample_data

fig = plt.figure(figsize=(10,5))
ax = plt.subplot(111)
plt.subplots_adjust(left=0.25, bottom=0.1, right=0.75, top=0.9, wspace=0, hspace=0)

# plot a line. When clip_on is set to False, the line is extended beyond the axes
ax.plot(np.linspace(0,2),np.sin(np.linspace(0,2)),clip_on=False)
plt.xlim([0,1])
plt.ylim([0,1])

# plot a bitmap. Although clip_on is set to False, it is clipped by the axes
logo = plt.imread(get_sample_data("logo2.png", asfileobj=False))
left,right, bottom, top=0.25,0.25+1.12,0.25,0.25+0.24
ax.imshow(X=logo,extent=(left, right, bottom, top),clip_on=False)

Actual outcome

Expected outcome

The matplotlib logo shouldn't be clipped by the axes, since clip_on was set to False.

Matplotlib version

Operating system: Ubuntu 18.04

Matplotlib version: : 3.1.1 (pip installation)

Matplotlib backend: Qt5Agg

Python version: 3.6