WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
For example the button .btn, if the gradients was transparent gradient over the then it would be as simple job of changing the color instead of duplicating the all of browser hacks each time.

Code examples: http://stackoverflow.com/a/2293931/560287

From: http://www.colorzilla.com/gradient-editor/

background: -moz-linear-gradient(top, rgba(0,0,0,0.065) 0%, rgba(0,0,0,0) 100%); /* FF3.6+ */
background: -webkit-gradient(linear, left top, left bottom, color-stop(0%,rgba(0,0,0,0.065)), color-stop(100%,rgba(0,0,0,0))); /* Chrome,Safari4+ */
background: -webkit-linear-gradient(top, rgba(0,0,0,0.065) 0%,rgba(0,0,0,0) 100%); /* Chrome10+,Safari5.1+ */
background: -o-linear-gradient(top, rgba(0,0,0,0.065) 0%,rgba(0,0,0,0) 100%); /* Opera 11.10+ */
background: -ms-linear-gradient(top, rgba(0,0,0,0.065) 0%,rgba(0,0,0,0) 100%); /* IE10+ */
background: linear-gradient(to bottom, rgba(0,0,0,0.065) 0%,rgba(0,0,0,0) 100%); /* W3C */
filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#1c000000', endColorstr='#00000000',GradientType=0 ); /* IE6-8 */

Fiddle: http://plnkr.co/edit/A0j1eww3CEbmcKYzC74Z?p=preview

Issue 2:
I have some modal windows in my Rails project. And I have a problem with background.

Generated HTML with duplicated background:

<div class="modal-backdrop fade in"></div>
<div class="modal-backdrop fade in"></div>
</body>

I don't know what's wrong.

My gems

group :assets do
gem 'sass-rails', '3.2.5'
gem 'coffee-rails', '~> 3.2.2'
gem 'uglifier', '>= 1.2.6'

gem 'bootstrap-sass', '~> 2.1.1.0'
end
Issue 1:
deno run --unstable https://deno.land/posts/v1.8/webgpu_discover.ts

error: invalid utf-8 sequence of 1 bytes from index 6

Example from https://deno.land/posts/v1.8

deno 1.8.0 (release, x86_64-pc-windows-msvc)

v8 9.0.257.3

typescript 4.2.2

windows 10

Issue 2:
cloudflare is rate limiting requests for the standard library and also thinks *.ts files are for video streaming

$ curl -I https://deno.land/std@0.85.0/log/logger.ts
HTTP/2 302
date: Wed, 03 Mar 2021 02:04:37 GMT
set-cookie: //
cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
expires: Thu, 01 Jan 1970 00:00:01 GMT
location: https://www.cloudflare-terms-of-service-abuse.com/streaming.ts
cf-request-id: //
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
report-to: //
nel: {"max_age":604800,"report_to":"cf-nel"}
server: cloudflare
cf-ray: //
alt-svc: h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400
Issue 1:
System info

Playwright Version: v1.34.1

Operating System: macOS 13.2.1

Browser: N/A

Other info: Terminal, CLI, Node 18.16.0 LTS

Source code

Config file

// playwright.config.js
const { defineConfig } = require('@playwright/test');

module.exports = defineConfig({
preserveOutput: 'failures-only',
snapshotPathTemplate: '{testDir}/__snapshots__/{testFilePath}/{arg}{ext}',
testDir: './assets',
use: {
viewport: {
width: 1440,
height: 900,
},
},
});

Test file (self-contained)

Simple tests like:

test('builds CSS correctly', () => {
expect(fs.readFileSync(`${PUBLIC_PATH}${MANIFEST['build/app/app.css']}`, 'utf-8')).toMatchSnapshot();
});

test('renders homepage correctly', async ({ page }) => {
await page.goto('<REMOVED_URL>');
await expect(page).toHaveScreenshot({ fullPage: true });
});

// Etc...

Steps

Run npx playwright test (executed by yarn test)

Expected

To start running tests by executing npx playwright test, like it did in previous versions (1.34.0 and down).

Actual

Getting the following message:

➜ yarn test
Please install @playwright/test package to use Playwright Test.
npm install -D @playwright/test

Already rules out a few things

Reinstalling @playwright/test

Completely removing node_modules and reinstalling with yarn

Works with yarn add @playwright/test@1.34.0 -D

Package playwright is not installed

Issue 2:
System info

Playwright Version: [v1.34.3]

Operating System: [Ubuntu 22.04]

Browser: Chromium

Other info:

So I'm write a function to copy and paste a string for me from one block to another. It worked find in my local machine using Windows, worked on the old playwright docker image too. But After upgraded to the latest (jammy 22.04) the test failed and trace shows that the copy and paste step not work as expected.

Source code

Steps

Highlight and Copy text by key.press("Control+C")

Paste text to other field by key.press("Control+V")

Expected

Pasted successfully

Actual

There's nothing new pasted on the field
Issue 1:
Marieke Vandamme opened SPR-5046 and commented

There seems to be a bug while using hessian in combination with spring framework for remoting.

Outputstream is not closed correctly, and part of the serialized output data gets lost.

This does not occur while doing the same with hessian-only remoting, so this should probably be resolved within spring.

The missing "close" method should be placed in:

org.springframework.remoting.caucho.Hessian2SkeletonInvoker

Close method on output stream needs to be applied after method:

this.skeleton.invoke(in, out);

A test client & server is included for simulation. Batch file launches the client, and war needs to be deployed in servlet engine running on 8080 (both on 1 computer). All source code is located in the "SpringHessianIssue.jar" file

Affects: 2.5.5

Issue Links:

#9722 Hessian Ouput Stream gets cut off when used with spring: ("duplicates")

Issue 2:
Tomasz Pik opened SPR-4012 and commented

jee:jndi-lookup do not provide a way to define a default object (or at least documentation do not show how to setup such a thing, also xsd do not highlight any way to define it) so it cannot be used a as drop-in replacement for org.springframework.jndi.JndiObjectFactoryBean (there's no equivalent of setDefaultObject(Object)

please, provide such a possibility for jee:jndi-lookup

Issue Links:

#8465 Add defaultObject attribute to jee:jndi-lookup tag ("is duplicated by")
Issue 1:
Bug report

Bug summary

The matplotlib set_aspect(aspect='equal') command for 3D plots works perfectly well after the lines 1279:1282 in …\site_packages\matplotlib\axes_base.py (matplotlib 3.1.1) are commented out. With it, the plot maintains the 3D aspect ratio despite window resizing. This is the desired behavior for 3D plots where the axes aspect is important and was the behavior in matplotlib 3.0.3. NB: set_aspect does not establish the axes ratios; that must be done via calls to set_xlim3d(), set_ylim3d(), and set_zlim3d(). Perhaps the documentation for set_aspect should be modified to reflect its usage.

Issue 2:
Bug report

Bug summary

set_aspect does not work for 3D surface plots

Expected outcome

If a sphere is drawn with plot_surface then it should appear as a sphere and not an ellipse that depends on the window sizing. This was achieved in mpl 3.0.3 by calling

set_aspect('equal').

It is now broken in mpl 3.1.1-3.1.3 because the following was inserted in matplotlib/axes/_base.py (lines1279:1282) by the developers

if (not cbook._str_equal(aspect, 'auto')) and self.name == '3d':

raise NotImplementedError(

'It is not currently possible to manually set the aspect '

'on 3D axes')

To get set_aspect to work (correctly, I might add), I have to comment out these lines in my local version of matplotlib. A plotted sphere appears as a sphere independent of the window sizing.
Issue 1:
Please be extremely cautious merging MRs into master as Travis CI has been completely disabled for SciPy and does not show up as a red or green mark in our testing matrix. This timing is a little unfortunate, just days before the planned branching of 1.6.0. We're going to have to migrate the jobs to other services.

Here's what I see in our Travis page:

Issue 2:
Original ticket http://projects.scipy.org/scipy/ticket/1216 on 2010-06-29 by @vincentdavis, assigned to @pv.

As I read in in the ticket below these should be deprecated.

http://projects.scipy.org/scipy/ticket/425

List, (should be verified)

Most of the "Convenience Functions" so maybe we want to keep them?

cbrt -- Cube root.
exp10 -- 10 raised to the x power.
exp2 -- 2 raised to the x power.
radian -- radian angle given degrees, minutes, and seconds.
cosdg -- cosine of the angle given in degrees.
sindg -- sine of the angle given in degrees.
tandg -- tangent of the angle given in degrees.
cotdg -- cotangent of the angle given in degrees.
log1p -- log(1+x)
expm1 -- exp(x)-1
cosm1 -- cos(x)-1
round -- round the argument to the nearest integer. If argument ends in 0.5 exactly, pick the nearest even integer.
Issue 1:
VSCode Version: 1.2.0

OS Version: OSX 10.11.4

Steps to Reproduce:

Enter the following syntax into vscode:

exports.listNames = (request, reply) => {
const family = request.params.family
const status = request.params.status || 'done'
const branch = (status === 'done') ? `master` : `fixes/${family}`

const listNames = github.listNames.bind(github, branch)

listNames(family)
.then((locales) => { reply(locales) })
.catch((err) => {
request.log(['error', 'github'], err)
reply(err)
})
}

Anything following the const branch = (status === 'done') ? master:fixes/${family}` is not highlighted properly

Issue 2:
Under vscode master (0.10.9) with language mode JavaScript.

'amd64' has classes: token block decl expr function meta single string ts var var-single-variable js

'i386' has classes: token annotation block decl expr function meta single string ts type var var-single-variable js

annotation scope is causing the following theme style to be applied:

.monaco-editor.vs-dark.vscode-theme-colorful-defaults-themes-dark_plus-tmTheme .token.var.annotation.type.js {
color: rgba(78, 201, 176, 1);
}
Issue 1:
Issue Type:

Bug Report

Ansible Version:

ansible 2.0.0.2

config file =

configured module search path = Default w/o overrides

Ansible Configuration:

Nothing particular

Environment:

Running from OSX 10.11.2, ansible installed via homebrew

Target OS, up to date debian wheezy

Summary:

It seems that we can't use become (default sudo adapter) without defining a sudo password.

Steps To Reproduce:

Just run

ansible foo -a "whoami" -b

Or

ansible foo -a "whoami" -s

Expected Results:

foo | SUCCESS | rc=0 >>
root

Actual Results:

foo | FAILED | rc=0 >>
ERROR! Missing sudo password

Of course, sudo without password is well configured on the target machine, and everything is ok with ansible 1.9

Issue 2:
Hi in the 2.0.0.1 version.

running ansible-galaxy --help provides the usage instructions and exits with an exit code of 5

This is not an error as you are just looking for help.

Unfortunately this kills vagrants ansible-local provisioner.

LOCAL

$ ansible --version
ansible 1.9.4
configured module search path = None
$ ansible-galaxy --help
Usage: ansible-galaxy [init|info|install|list|remove] [--help] [options] ...
Options:
-h, --help show this help message and exit
See 'ansible-galaxy <command> --help' for more information on a specific command.
$ echo $?
0

2.0.0.1

$ ansible --version
ansible 2.0.0.1
config file = /etc/ansible/ansible.cfg
configured module search path = Default w/o overrides
$ ansible-galaxy --help
Usage: ansible-galaxy [delete|import|info|init|install|list|login|remove|search|setup] [--help] [options] ...

Options:
-h, --help show this help message and exit
-v, --verbose verbose mode (-vvv for more, -vvvv to enable connection
debugging)
--version show program's version number and exit
ERROR! Missing required action
$ echo $?
5

Not your problem but this is how vagrant checks if ansible is installed.

DEBUG ssh: Re-using SSH connection.
INFO ssh: Execute: ansible-galaxy --help && ansible-playbook --help (sudo=false)
DEBUG ssh: stderr: ERROR! Missing required action

DEBUG ssh: stdout: Usage: ansible-galaxy [delete|import|info|init|install|list|login|remove|search|setup] [--help] [options] ...

Options:
-h, --help show this help message and exit
-v, --verbose verbose mode (-vvv for more, -vvvv to enable connection
debugging)
--version show program's version number and exit

DEBUG ssh: Exit status: 5
Issue 1:
Original ticket http://projects.scipy.org/numpy/ticket/1163 on 2009-07-09 by trac user onsi, assigned to unknown.

I'm running version 1.2.1 but this error should also occur in 1.3.0 based on the source currently in the trunk.

I try importing the following ascii data stored in "sample.csv":

9007200000000000,670927001710,0.010190886[[BR]]

9007200000000001,660927001348,0.00976051[[BR]]

9007200000000002,650883003926,0.009154096

using (maximal verbosity for clarity):

import numpy
arr=numpy.loadtxt("sample.csv",dtype=[('id0',numpy.int64),('id1',numpy.int64),('flt',numpy.float32)],delimiter=',',comments='#')

I get:

[(9007200000000000L, 670927001710L, 0.010190886445343494)[[BR]](9007200000000000L, 660927001348L, 0.0097605101764202118)[[BR]](9007200000000002L, 650883003926L, 0.009154096245765686)][[BR]]

After some digging, i found the culprit to be the converter used by loadtxt to convert strings to dtypes. lib.io._getconv (line 352 in trunk) returns:

lambda x: int(float(x))

as the converter for any dtype that is a subclass of int, which int64 is. Unfortunately, float does not faithfully reproduce long integers and so 9007200000000001 gets rounded to 9007200000000000.

This is fairly serious as int64s are often used as IDs in various numerical/simulation contexts. Changing the converter to int() should resolve this problem -- though then some error checking needs to take place to ensure that int is fed an integer string.

Issue 2:
Original ticket http://projects.scipy.org/numpy/ticket/1565 on 2010-07-28 by @fengy-research, assigned to unknown.

Prepare the following file:

-------file /tmp/test -----

9223372043271415339

9223372043271415853

9223372043271415612

9223372043271416107

9223372043271415594

9223372043271415836

9223372043761290139

9223372044088967272

9223372044088967273

9223372043925949039

---------end of file-----

And run the following code:

In [16]: print loadtxt('/tmp/test', dtype='uint64')

-------> print(loadtxt('/tmp/test', dtype='uint64'))

[9223372043271415808 9223372043271415808 9223372043271415808

9223372043271415808 9223372043271415808 9223372043271415808

9223372043761289216 9223372044088967168 9223372044088967168

9223372043925948416]

On the other hand, with fromfile(),

In [2]: print fromfile('/tmp/test', dtype='uint64', sep=' ')

------> print(fromfile('/tmp/test', dtype='uint64', sep=' '))

[9223372043271415339 9223372043271415853 9223372043271415612

9223372043271416107 9223372043271415594 9223372043271415836

9223372043761290139 9223372044088967272 9223372044088967273

9223372043925949039]

Clearly the first few numbers are wrongly converted by loadtxt

The problem was tracked to line 453 in numpy/lib/io.py, _getconv. The conversion for np.integer is int(float(x)), which is inexact for large integers.

I don't know if a priority of normal is appropriate, as this bug will produce hidden errors in programs that use numpy.
Issue 1:
springboot2.4.5, mybatis-plus3.4.1, shardingsphere-jdbc-core-spring-boot-starter5.1.2

单库，20 张表，其中 1 张表分表

11 代 I7， 16G 内存

未分表前启动很快，10s 左右，分表后平均时间 6 分多钟

spring:
shardingsphere:
datasource:
ds:
driver-class-name: com.mysql.cj.jdbc.Driver
jdbc-url: jdbc:mysql://localhost:3306/test?useSSL=false&useUnicode=true&characterEncoding=utf-8&autoReconnect=true&zeroDateTimeBehavior=convertToNull&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=Asia/Shanghai&rewriteBatchedStatements=true&allowPublicKeyRetrieval=true
password: 123456
type: com.zaxxer.hikari.HikariDataSource
username: root
validation-timeout: 5000
connection-timeout: 30000
max-lifetime: 1800000
maximum-pool-size: 20
minimum-idle: 5
idle-timeout: 600000
auto-commit: true
connection-test-query: SELECT 1
pool-name: ${spring.application.name}-ds
names: ds
mode:
type: Memory
rules:
sharding:
key-generators:
snowflake:
type: SNOWFLAKE
sharding-algorithms:
local-date-time-inline:
props:
strategy: standard
algorithmClassName: com.test.sharding.CustomLocalDateTimeStrategyShardingAlgorithm
type: CLASS_BASED
tables:
test_bigdata_his:
actual-data-nodes: ds.test_bigdata_his_202$->{201..912} # 按月分表
key-generate-strategy:
column: id
key-generator-name: snowflake
table-strategy:
standard:
sharding-algorithm-name: local-date-time-inline
sharding-column: data_time
props:
sql-show: true
max:
connections:
size:
per:
query: 50

Issue 2:
sharding-jdbc : 5.1.2

<dependency>
<groupId>org.apache.shardingsphere</groupId>
<artifactId>shardingsphere-jdbc-core-spring-boot-starter</artifactId>
<version>5.1.2</version>
</dependency>

tables : 200+

same config, with version 5.1.0 , application startup very fast

change to version 5.1.2 , application start very slow......
Issue 1:
Hi,

I'm working with histogram aggregation but there is something strange with keys.

For instance (cf : http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-aggregations-bucket-histogram-aggregation.html):

If I use this request :

{

"aggs" : {

"prices" : {

"histogram" : {

"field" : "price",

"interval" : 50

}

}

}

}

I obtain something like this :

{

"aggregations": {

"prices" : {

"buckets": [

{

"key_as_string" : "0",

"key": 0,

"doc_count": 2

},

{

"key_as_string" : "50",

"key": 50,

"doc_count": 4

},

{

"key_as_string" : "150",

"key": 150,

"doc_count": 3

}

]

}

}

}

Instead of :

{

"aggregations": {

"prices" : {

"buckets": [

{

"key": 0,

"doc_count": 2

},

{

"key": 50,

"doc_count": 4

},

{

"key": 150,

"doc_count": 3

}

]

}

}

}

You could say, it's not important but it generates json ~1/3 bigger...

Is there a mean to disable this ???

Moreover, in Elasticsearch Java API, it could be fine to have a method to request the response as a hash instead keyed by the buckets keys (cf :http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-aggregations-bucket-histogram-aggregation.html#_response_format)

Thanks!!!

Issue 2:
Version - 1.3.2

Steps to reproduce

cat a.json
{
"user" : "vm"
}}

curl -XPOST "http://localhost:9200/config/alert" -d @a.json
{
"_index": "config",
"_type": "alert",
"_id": "0_UJFBy3SLOnfwCnS-D_Zg",
"_version": 1,
"created": true
}

Impact: Indexing is happening fine but on return the same wrong formatted JSON is returned and its breaking the application reading it as it expects properly formatted JSON string.
Issue 1:
The NaN debugging feature works with JIT (good), but not with pmap (bad). Please make it work with pmap.

Issue 2:
When I ran the following script:

from functools import partial
import jax
import jax.numpy as jnp

@partial(jax.pmap, axis_name='i')
def nan_with_pmap(x):
return jnp.log(-x)

print(nan_with_pmap(jnp.array([42.])))

using

JAX_DEBUG_NANS=true python script.py

I expected it to crash at the point where the nan was produced, but instead the script prints:

[nan]

Would it be possible to add nan detection to pmap as well?
Issue 1:
I'm trying to use angular2 as a JSPM package.

When I'm doing something like

import {bootstrap, Component, Input} from 'angular2/angular2';

in my code then typescript complains that it can't find the definitions and I don't get any code completions.

The workaround is to install angular2 also as a npm package and set moduleResolution to node. However this seems not optimal, because now I have two dependencies whose versions need to be aligned.

I guess tsc could resolve the modules for jspm/systemjs similar to how it already can do it for node. E.g. look up package.json, config.js and use the pathes from there the locate to type definitions inside the jspm_packages folder.

Not really sure if this is covered by #5039 and #5728.

Issue 2:
I get this error - Build: Cannot compile modules unless the '--module' flag is provided.

even though I have AMD checked in the project settings.

Visual Studio 2015. 14.0.23107.0 D14REL

TypeScript Tools for Microsoft Visual Studio 2015 1.5.4.0
Issue 1:
dropdown-menu is not shifted to the left if it reaches the right edge of the screen.

Demonstration: https://drive.google.com/file/d/0B0nwzlfiB4aQRTRtNVVCZ3JRbjg/edit?usp=sharing

Issue 2:
A picture is worth a thousand words; this is taken directly from the docs with chrome at 515px wide.

I've implemented the following solution in my own project to remedy this, and would like to know if it is worth submitting a pull request for (modified, of course)

$(document).on('shown.bs.dropdown', function () {
OffsetDropdown()

$(window).on('resize.bs.dropdown', function () {
OffsetDropdown()
})
})

$(document).on('hide.bs.dropdown', function() {
$(window).off('resize.bs.dropdown')
})

var OffsetDropdown = function() {
var dropdown = $('.open>.dropdown-menu')

if (dropdown.length == 0)
return

var rightOffset = dropdown.offset().left + dropdown.width()
var browserWidth = $('body').innerWidth()
var neededLeftOffset = dropdown.position().left - (rightOffset - browserWidth)

if (neededLeftOffset < 0) {
dropdown.css({ left: neededLeftOffset - 3 })
} else {
dropdown.css({ left: 0 })
}
}
Issue 1:
Hi, I hope this is an appropriate forum for a feature request. For context - I've just been confused by the lack of configuring semicolons for the deno lint command, when you're able to customize other things such as quotes(double vs single).

Now, I understand not everyone likes ASI in JavaScript, but isn't the whole point of a linting tool to empower users to define their own coding standards?

So to that end, I would like to ask the Deno maintainers if there are any plans to expand the scope of what can be configured with deno lint? Or is the intent of the tool to be opinionated and enforce one standard upon all users of the built in command?

Issue 2:
I am a bit miffed by this error reported by the test runner (notice the async/ops resource sanitizer is not printing (I am the one doing the print). The test completes, reports passed, but a trace at the end.

Any hints, thoughts?

running 1 tests
test clean shutdown ...
{ "0": "stdin", "1": "stdout", "2": "stderr", "3": "webSocketStream" }
ok (11ms)

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out (11ms)

error: Uncaught (in promise) BadResource: Bad resource ID
at handleError (deno:core/core.js:186:12)
at jsonOpParseResult (deno:core/core.js:356:9)
at opSync (deno:core/core.js:259:32)
at jsonOpSync (deno:core/core.js:372:12)
at Object.close (deno:core/core.js:383:12)
at WebSocket.#eventLoop (deno:op_crates/websocket/01_websocket.js:353:18)