WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
In Mac OS X when you paste a minified file like jquery.min.js or bootstrap.min.css Atom crashes or stays unresponsive for a minute or two.

Issue 2:
May be a known issue, but files with large embedded images such as github's public/enterprise/maintenance.html will often cause Atom to freeze (MacVim actually struggles as well).

Seems some of them (github's public/maintenance.html for instance) work fine when in soft wrap mode, or until you move your cursor to the long line when out of soft wrap.
Issue 1:
System information (version)

OpenCV => 3.1

Operating System / Platform => macOS 10.12

Compiler => gcc

Matlab => Matlab_R2016b

Detailed description

Cannot find Matlab automatically, because OpenCVFindMatlab.cmake looks for a wrong name.

Solution

Change in OpenCVFindMatlab.cmake at line 65

file(GLOB MATLAB_ROOT_DIR_ ${DIR_}/MATLAB/R*)

to

if (APPLE)
file(GLOB MATLAB_ROOT_DIR_ ${DIR_}/MATLAB_R*)
else()
file(GLOB MATLAB_ROOT_DIR_ ${DIR_}/MATLAB/R*)
endif()

DONE.

Issue 2:
System information (version)

OpenCV => 3.1

Operating System / Platform => OS X El Capitan 10.11.3

Compiler => Xcode 7.3.1 - Apple LLVM version 7.3.0 (clang-703.0.31)

Detailed description

This line in OpenCVFindMatlab.cmake does not find an existing Matlab installation:

file(GLOB MATLAB_ROOT_DIR_ ${DIR_}/MATLAB/R*)

However, changing it to the following finds the installation correctly:

file(GLOB MATLAB_ROOT_DIR_ ${DIR_}/MATLAB_R*)

Steps to reproduce
Issue 1:
Bug summary

The discrete normalizer produces duplicated labels for the same tick and the colorbar is wrong.

Code for reproduction

import numpy as np
import matplotlib.pyplot as plt
import matplotlib.colors as mcolors
import matplotlib.ticker as mticker

fig, ax = plt.subplots()

edges = np.linspace(0, 3, 13)
norm = mcolors.BoundaryNorm(edges, 1000)
Z = np.random.rand(5, 5) * 3

m = ax.pcolormesh(Z, cmap='viridis', norm=norm)
cb = fig.colorbar(m, ticks=mticker.MultipleLocator(0.25))

fig.show()

Actual outcome

Expected outcome

Correct ticks and colorbar.

Additional information

No response

Operating system

Ubuntu

Matplotlib Version

3.5.0

Matplotlib Backend

module://matplotlib_inline.backend_inline

Python version

Python 3.9.7

Jupyter version

No response

Installation

conda

Issue 2:
Applies to version 1.4.2

When using one of the GUI backends (tested with Tk and Qt using IPython) plot markers are only drawn if markeredgecolor is not set to 'none' and markeredgewidth is nonzero. So

plot(linspace(0,2), linspace(0,2)**2, marker='o', markeredgecolor='blue',
markeredgewidth=0.01, markerfacecolor='blue')

draws plot markers while

plot(linspace(0,2), linspace(0,2)**2, marker='o', markeredgecolor='blue',
markeredgewidth=0, markerfacecolor='blue')

or

plot(linspace(0,2), linspace(0,2)**2, marker='o', markeredgecolor='none',
markerfacecolor='blue')

don't.

Associated with this issue seems to be that the Axes method fill_between doesn’t draw anything if linewidth is set to zero. Could it be that any filled paths without outline are not drawn?

Saving the figure to PDF via the GUI is not affected by this issue, saving to PNG is.
Issue 1:
I would like to extend the jax.checkpoint aprroach to implement binomial checkpointing for computing the vjp of a time stepping loop the performs computation in step():

def timestep(A,N):
for i in range(N):
A = step(A,i)

Theremat approach, as I understand it, generates a version of a function that stores inputs of the function and none of the linearization points. For the vjp calculation, it reruns the function calculation thereby regenerating the intermediate linearization points.

If I use remat for step(A,i), then for each i, the arguments to step(A,i)will be stored. This is not what I want, because in my test case,A` is very large.

An alternate scheme such as binomial checkpointing can use some criterion to decide for which i to store the inputs instead of storing each them for each i. This allows for different tradeoffs between storage and recomputation. To implement such a checkpointing scheme, the following actions will need to be performed:

Store argument of step(A,i)

Restore arguments of step(Ai,)

Run step(i) without storing/restoring arguments based on step(A,i-1)’s completion.

Compute jvp for step(i) assuming that output of jvp(A,i+1) and is available

Does this seem feasible to implement on top of the existing remat approach?

Are there any suggestions on how to go about it?

Issue 2:
It would be great to have a version of lax.scan used a recursive gradient checkpointing (e.g., "binomial checkpointing") that allows for differentiating through long time series with logarithmic time/space costs.

In principle this could be built on top of the experimental remat decorator: #1749
Issue 1:
We seem to have broken compatibility with fortran-interface-only BLAS libraries. Specifically, we use cblas_zdotc_sub and cblas_cdotc_sub, which don't exist in some BLAS implementations such as CentOS 7's default blas package. Is this something we want to work around, revert, or just live with?

Issue 2:
I'd like to propose two added functions to the merge function. I'm not sure if this needs to be in core language or somewhere like in DataFrames, but as long as merge is in core, seems reasonable to put here (though input welcome!).

In particular, I'd like to propose the following two options be offered as optional keywords:

validate: duplicates the functionality of validate keyword in the pandas merge function. Accepts "1:1", "1:m", "m:1", and "m:m", and raises an exception if the merge is not 1 to 1, 1 to many, many to 1, or many to many (respectively).

indicator: duplicates functionality of indicator keyword in pandas [merge] function. If True, adds column to returned object which records whether resulting row has data from both datasets, from the left_only, or the right_only (or if we'd prefer numerics for generality, 1, 2, and 3)

(Both are actually replications of behavior from Stata)

Personally, I find these exceedingly value when working with real world data, as there's no place problems become more evident than in merges, and it gets exhausting writing code the replicates these functionalities every time I merge (especially the indicator command).
Issue 1:
I need to detect taps on a TextField. I'm trying to do this with GestureDetector, but it doesn't seem be working:

GestureDetector(
behavior: HitTestBehavior.translucent,
onTap: () {
print('hi');
},
child: TextField(),
),

Nothing is printed when tapping.

Note that I need to perform an action every time the TextField is tapped, even after it has focus. Therefore, I don't believe utilizing FocusNode would work.

Issue 2:
Add onTap gesture on a textField

onTap gesture using GestureDetector class is working for every element except for the textField type.

How can i use onTap gesture on textfield element?
Issue 1:
Problem description

Tooltip is displaying under the table rows (on z-axis)

Link to minimally-working code that reproduces the issue

http://www.webpackbin.com/Eyxr9TOLKz

Versions

Material-UI: 0.17.0

React: 15.0.2

Browser: any, checked on the latest versions of firefox and chrome. (Google Chrome Version 56.0.2924.87 (64-bit))

Issue 2:
When trying to view an IconButton's tooltip while contained in a table cell it seems to be hidden by an overflow of some kind.
Issue 1:
Hi. I'm trying to integrate Firebase Auth with Flutter. For that I need to register my Android App with Firebase. For Google Sign-In, I require the SHA-1 Certificate of my Android App.

On a regular app, this used to be possible by going to the Gradle Panel on the right hand side and executing the signingReport Gradle Task. However on the flutter app, there is no such Panel, and I can't find any way to show it.

I've also posted a StackOverflow Question, which has been there for 2 days but has no response. Please allow for a way to get a flutter app's SHA-1 certificate conveniently. If a solution to this already exists, please let me know.

Issue 2:
@UwaisWisitech commented on Fri Jan 04 2019

I need the SHA-1 key of my Flutter App for Google login.

Previously, its possible in Gradle Panel on executing the signingReport Gradle. But there is no Gradle Panel in Flutter.

@zoechi commented on Fri Jan 04 2019

Please check https://stackoverflow.com/questions/51845559/generate-sha-1-for-flutter-app
Issue 1:
With an iterator that returns a borrowed reference to its contents, it’s possible to hold the reference longer than the reference is valid. In particular, if the iterator changes its internal state, the new state can be observed via the saved reference. Check it out:

fn crash_please() {
let mut iter = Newtype(Some(Box::new(0)));
let saved = iter.next().unwrap();
println!("{}", saved);
iter.0 = None;
println!("{}", saved);
}

struct Newtype(Option<Box<usize>>);

impl<'a> Iterator for Newtype {
type Item = &'a Box<usize>;

fn next(&mut self) -> Option<&Box<usize>> {
self.0.as_ref()
}
}

This clearly shouldn’t type check, but it does, and runs, and crashes:

0
zsh: illegal hardware instruction target/collect_bug

Where the type error should be, I’m not sure. It seems like it’s actually a problem with traits. If we change the above code to define next in a non-trait impl, then it no longer passes the borrow checker:

impl<'a> Newtype {
fn next(&mut self) -> Option<&Box<usize>> {
self.0.as_ref()
}
}

I originally observed this bug when testing an iterator that owns a String; at each iteration it modifies the string and then returns a string slice borrowed from it. My non-test code worked fine because it finished with each value from the iterator before calling next() again, but the test code collected the iterator into a vector. This meant that all the slices in the vector continued to point to the same buffer, even after it had been modified. So for example, if the strings written to the buffer were "aaa", "bb", and "c", then in the end the vector would contain "cba", "cb", and "b". Creepy.

Version

I’m using 1.0.0-alpha still, because I’m teaching a class and we don’t want to follow a moving target, but I confirmed that the Feb. 26 nightly has the same bug.

rustc 1.0.0-alpha (44a287e6e 2015-01-08 17:03:40 -0800)
binary: rustc
commit-hash: 44a287e6eb22ec3c2a687fc156813577464017f7
commit-date: 2015-01-08 17:03:40 -0800
host: x86_64-apple-darwin
release: 1.0.0-alpha

Issue 2:
(Sorry for the bad title)

trait Fun {
type Output;
fn call<'x>(&'x self) -> Self::Output;
}

struct Holder { x: String }

impl<'a> Fun for Holder {
type Output = &'a str;
fn call<'b>(&'b self) -> &'b str {
&self.x[]
}
}

This compiles even though the trait's definition should require call's signature in the impl to be fn call<'b>(&'b self) -> &'a str.
Issue 1:
Just found out about this dont know if you consider it as a bug or not

let foo, bar
let bim = boum
[ foo, bar ] = ['foo', 'bar']

compile to

'use strict';

var foo = undefined,
bar = undefined;
var bim = boum[(foo, bar)] = ['foo', 'bar'];

whereas

let foo, bar
let bim = boum;
[ foo, bar ] = ['foo', 'bar']

compile to

'use strict';

var foo = undefined,
bar = undefined;
var bim = boum;
var _ref = ['foo', 'bar'];
foo = _ref[0];
bar = _ref[1];
_ref;

debugger link:

http://babeljs.io/repl/#?experimental=false&evaluate=false&loose=true&spec=false&code=let%20foo%2C%20bar%0Alet%20bim%20%3D%20boum%3B%0A%5B%20foo%2C%20bar%20%5D%20%3D%20%20%5B'foo'%2C%20'bar'%5D%0A%0A

Issue 2:
This code:

const foo = "foo";

function foobar() {
for(let item of [1,2,3]) {
let foo = "bar";
[bar, foo] = 1, 2;
}
}

Generates this one:

// [ some code striped]
var foo = "foo";

function foobar() {
var _arr = [1, 2, 3];

for (var _i = 0; _i < _arr.length; _i++) {
var _temp, _temp2;

var item = _arr[_i];
var _foo = "bar";
(_temp = 1, _temp2 = _slicedToArray(_temp, 2), bar = _temp2[0], foo = _temp2[1], _temp), 2;
}
}

And should generate this:

// [striped code]
var item = _arr[_i];
var _foo = "bar";
(_temp = 1, _temp2 = _slicedToArray(_temp, 2), bar = _temp2[0], _foo = _temp2[1], _temp), 2;
// [striped code

So, the current babel version (5.4.3), in a for loop overwrites the value of the var declared as const.
Issue 1:
I added my own custom protocol, which i create a BrowserWindow from using mist://interface:

protocol.registerHttpProtocol('mist', function(request, callback) {

var call = {
url: (request.url.indexOf('mist://interface') !== -1) ? global.interfaceAppUrl + request.url.replace('mist://interface','') : '',
method: request.method,
referrer: request.referrer
};

console.log(call);

callback(call);

}, function (error) {
if (error)
console.error('Failed to register protocol')
});

It loads the initial page fine, but none of the linked scripts seemed to be loaded later.

I also tried adding a script tag using javascript manually:

var script = document.createElement('script');
script.type = 'text/javascript';
script.src = '/packages/meteor.js?19730f4ff059088b3f7f14c0672d155218a1802d4';

document.getElementsByTagName('body')[0].appendChild(script);

But i can't see this protocoll handler beeing called and the js doesn't load and execute.

Hint: this seems to happen if the url, is relative or absolute and not contains the protocol.

Though by web standards, relative or absolute URLs should get the protocol of the current location.

Issue 2:
some webpage omit the http prefix to minify the page, like http://taobao.com

electron now can not recognize this kind of url, and will log error like this:

[22608:0521/234915:INFO:CONSOLE(0)] "Not allowed to load local resource: file://g.alicdn.com/kg/offline/3.0.1/index-min.js?t=20131121234724.js", source: http://www.taobao.com/ (0)
Issue 1:
As part of #2137 and #456 we have added the crate version to every exported symbol, but not quite in the correct way.

Right now the final part of the path used for the symbol ends with "V" + vers, which gets passed through the mangler. The original design called for @vers but the @ isn't a valid symbol on all platforms (I think?) so gets mangled to _sbox_, which is a bizarre way to indicate the version.

Mangling also makes any dots in the version go away so a version "0.2" symbol will end with "V02".

There is some additional discussion here about how this is supposed to work that I haven't read.

Issue 2:
Status as of 2020-04-18

We intend to stabilize the saturating-float-casts behavior for as, and have stabilized unsafe library functions that handle the previous behavior. See #71269 for the latest discussion on that stabilization process.

Status as of 2018-11-05

A flag has been implemented in the compiler, -Zsaturating-float-casts, which will cause all float to integer casts have "saturating" behavior where if it's out of bounds it's clamped to the nearest bound. A call for benchmarking of this change went out awhile ago. Results, while positive in many projects, are quite negative for some projects and indicates that we're not done here.

The next steps are figuring out how to recover performance for these cases:

One option is to take today's as cast behavior (which is UB in some cases) and add unsafe functions for the relevant types and such.

Another is to wait for LLVM to add a freeze concept which means that we get a garbage bit pattern, but it's at least not UB

Another is to implement casts via inline assembly in LLVM IR, as the current codegen is not heavily optimized.

Old status

UPDATE (by @nikomatsakis): After much discussion, we've got the rudiments of a plan for how to address this problem. But we need some help with actually investigating the performance impact and working out the final details!

ORIGINAL ISSUE FOLLOWS:

If the value cannot fit in ty2, the results are undefined.

1.04E+17 as u8
Issue 1:
Example: I put a ImageView, set scaletype="center" (will not scale), but when I use

Glide.with(getApplicationContext()).load(url).placeholder(R.drawable.ic_default).into(imageV);

seem that the scaletype been changed, because I found that the placeholder icon been filled the whole imageview size.

Issue 2:
Hi

I am displaying images in a recyclerview via Glide. The images are different widths and heights and are being pulled from the server.

The images all display fine until the views begin to be recycled. The image view has android:layout_width="wrap_content" android:layout_height="wrap_content" I have tried to sort this by setting holder.getImageView().setImageDrawable(null); in ` public void onBindViewHolder'. This didn't work. I have found item public void #388 and as that poster had a custom image view you suggested using ViewTarget and delaying size determination. As I'm using a standard ImageView the ImageViewTarget doesn't have a get size method so Im not sure how to apply this to my case

If you could offer any advice..here's my post on SO http://stackoverflow.com/questions/33283493/recyclerview-recycled-viewholder-image-view-wrong-size

Regards,

Gary
Issue 1:
System info

Playwright Version: [v1.1.36.0]

Operating System: [Linux amd64]

Browser: [All, Chromium, Firefox, WebKit]

Other info:

playwright Java and TestNg framework

Hi team,

Playwright failed to find the locator in the Selenium grid docker setup. It works fine till navigation after it throws

com.microsoft.playwright.TimeoutError:

Error {

message='Timeout 60000ms exceeded.

=========================== logs ===========================

waiting for locator("xpath=//input[@id='UserName']")

name='TimeoutError

stack='TimeoutError: Timeout 60000ms exceeded.

=========================== logs ===========================

waiting for locator("xpath=//input[@id='UserName']")

at ProgressController.run (/tmp/playwright-java-11238511618491153829/package/lib/server/progress.js:88:26)
at Frame.fill (/tmp/playwright-java-11238511618491153829/package/lib/server/frames.js:1047:23)
at FrameDispatcher.fill (/tmp/playwright-java-11238511618491153829/package/lib/server/dispatchers/frameDispatcher.js:163:30)
at DispatcherConnection.dispatch (/tmp/playwright-java-11238511618491153829/package/lib/server/dispatchers/dispatcher.js:312:46)

}

It works fine in local and local selenium grid setups.

Page load and waits are used.

Issue 2:
System info

Playwright Version: [v1.32.2]

Operating System: [macOS 13.3]

Browser: [WebKit]

Other info:

Source code

main.js file

const { webkit } = require('playwright');

const test = async () => {
const context = await webkit.launchPersistentContext('path_for_user_dir', {headless: false});
const page = await context.newPage();
await page.goto('https://www.abc.com');
}
test();

package.json

{
"name": "testcafe",
"version": "1.0.0",
"description": "",
"main": "main.js",
"scripts": {
"start": "node main.js"
},
"keywords": [],
"author": "",
"license": "ISC",
"dependencies": {
"testcafe": "^2.0.0"
},
"devDependencies": {
"@playwright/test": "^1.32.2",
"playwright": "^1.32.2"
}
}

Steps

npm start

Expected

It should open webkit browser with latest version (saw in doc and npm package link that it supports 16.4).

Actual

When I use launchPersistentContext method it opens old webkit browser 13.x.x (checked in user agent of browesr and other online sites) and when I use launch method it opens up in new version of webkit which is 16.4.

I don't know if I'm missing something.
Issue 1:
On IRC, @bjz and @Kimundi pointed out some infelicities with how rustpkg handles the test crate.

kimundi writes: "I think there are 3 ways to have the test suite of a rustpkg package work: in-crate by compiling the crate with rustc --test, out-of-crate by having a test.rs file that 'extern mod's the crate, and hybrid where you have a test.rs file that contains all modules of your crate with 'mod ...;' statements, effectively providing an alternate test crate-root."

Currently, rustpkg is designed to give preference to the last option: having a test.rs file that is an alternative crate root for building a test executable.

So one question is whether to support all 3 ways with equally good ergonomics in rustpkg. The other question is whether to choose one way that we prefer, and document that that is the preferred method.

kimundi pointing out that the pros and cons of each approach are:

"in-crate: pro: quick and easy, can test private things. cons: clutters the code, change to tests mean recompile the library itself

out-of-crate: pro: can test the public api extensivly, no cluttering the crate code itself, changes to testsuite do not cause the crate to need recompiling. cons: can't test private items, need to do more work to test the public api

hybrid: pro: can test private api, separate test crate from regular crate, can test public api separately without needing to recompile crate. cons: needs to compile the same amount of code as the crate, needs to duplicate crate root."

Issue 2:
This is a tracking issue for the unstable ref_slice feature in the standard library. These functions seem fairly innocuous but it's also somewhat questionable how useful they are. They're probably ready for either stabilization or deprecation as-is.

cc @nikomatsakis
Issue 1:
A.

All @asserts should be exceptional, and since it's a macro already, it should outline (@noinline) automatically, as was manually done here (to avoid 3x speed regression):

https://github.com/JuliaLang/julia/pull/34237/files

B.

I was looking into optimizing factorial myself, and think in general throws should be outlined too, i.e. all preconditions. For now A. is a low hanging-fruit I think. I'm not sure, possibly after A. is done, throws can be implemented with asserts, getting B for free?

C.

Maybe there are complications when there are two or more asserts and/or throws, still I doubt solving A. and/or B. would be slower then. However possibly in that case something even better could be done?

Issue 2:
We're increasingly seeing this kind of manual optimization in Base code:

function f(...)
check_cond() || throw(SomeError(...))
end

rewritten as

@noinline throw_some_error(...) = throw(SomeError(...))

function f(...)
check_cond() || throw_some_error(...)
end

It would be great if the compiler could figure this out and do the transformation automatically. I don't think it needs to be terribly complicated either: throw should never be a common code path in Julia and throwing each kind of error could be its own outlined function, which would avoid an explosion of these automatically outlined throw functions.
Issue 1:
If I want a terminal for vs code, inputBox is not well for input.

Issue 2:
It would be great if vscode has integrated terminal feature refer vim or atom https://atom.io/packages/term3

I saw this suggestion pending in uservoice(https://visualstudio.uservoice.com/forums/293070-visual-studio-code/suggestions/7752357-integrated-terminal) and repost here since it has specific repo
Issue 1:
Source is very simple.

//

//

static F : Box< Fn(i32) -> i32 > = Box::new(move |x:i32| x);

fn main() {

}

//

//

this code generate fault as follows.

src\main.rs:2:34: 2:58 error: function calls in statics are limited to struct an

d enum constructors [E0015]

src\main.rs:2 static F : Box<Fn(i32) -> i32> = Box::new(move |x:i32| x);

^~~~~~~~~~~~~~~~~~~~~~~~

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/m

aster/CONTRIBUTING.md#bug-reports

note: run with RUST_BACKTRACE=1 for a backtrace

thread 'rustc' panicked at 'assertion failed: self.mode == Mode::Var', C:/bot/sl

ave/beta-dist-rustc-win-64/build/src/librustc\middle\check_const.rs:232

Could not compile hello_world.

To learn more, run the command again with --verbose.

Issue 2:
If I try to create a const &'static Fn(u32), I trigger an ICE:

error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
note: run with `RUST_BACKTRACE=1` for a backtrace
thread 'rustc' panicked at 'assertion failed: self.mode == Mode::Var', /home/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/librustc/middle/check_const.rs:254

error code 101

A small example code snippet is on the playpen (see http://is.gd/U0DmxV):

const x: &'static Fn() = &|| println!("ICE here"); //ICE

fn main() {}