WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
WireframeGeometry generates duplicate edges for both indexed and non-indexed buffer geometry.

This is true by inspection, as the code does not test for duplicate xyz-coordinates.

A simple non-indexed example is:

const geometry = new THREE.TetrahedronGeometry( 1, 0 ); // 6 unique edges

const wireframe = new THREE.WireframeGeometry( geometry ); // 12 edges

BoxGeometry( 1, 1, 1 ) is a simple indexed example.

Duplicating an edge is not a problem most of the time, but when using dashed lines, it is a problem.

EDIT: Actually, instead of "duplicate edges", they should be referred to as "coincident edges": A -> B = B -> A.

Issue 2:
Discussion continued from @mrdoob's question in #3657.

It sure would simplify the code. Non-planar quads would no longer shade incorrectly (because quads wouldn't exist). Raycasting against modified quad terrain would work correctly.

The downside is a wireframe cube in CanvasRenderer and WebGLRenderer would no longer have 6 square faces. CanvasRender may be slower. Converters would have to be changed first. We'd lose backward compatibility with existing quad-based models.
Issue 1:
This simple code example ends in an Segmentation fault error.

Mat test(720, 1280, CV_8UC3);
string text = "";
putText(out, text, Point(10, 10), FONT_HERSHEY_SIMPLEX, 1.0, Scalar(0, 0, 0), 2);

The reason is the empty string (""), using any other string, that is not empty, works fine.

This did not happen in OpenCV 2.4.8.

Is this meant to work this way now, that one has to check the string if it is empty before drawing it?

Issue 2:
putText throws a segmentation fault when an empty std::string is passed as the text argument. It doesn't happen with an "empty" char array:

cv::Mat im(640, 480, CV_8UC3);
std::cout << "a" << std::endl;
cv::putText(im, "", cv::Point(10, 30), cv::FONT_HERSHEY_PLAIN,
1., cv::Scalar(255, 255, 255));
std::cout << "b" << std::endl;
cv::putText(im, std::string(""), cv::Point(10, 30), cv::FONT_HERSHEY_PLAIN,
1., cv::Scalar(255, 255, 255));
std::cout << "c" << std::endl;

Output:

a
b
Segmentation fault (core dumped)

OpenCV version 3.0.0. GCC g++ (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4. Linux 3.16.0-50-generic x86_64.
Issue 1:
Make sure these boxes are checked before submitting your issue - thank you!

[ x ] I have checked the superset logs for python stacktraces and included it here as text if any

[ x ] I have reproduced the issue with at least the latest released version of superset

[ x ] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version

0.20.3

Expected results

Upon changing dashboard filtering, icons should indicate new range

Actual results

Since ∞

Until ∞

Steps to reproduce

Add date filter to dashboard

Change range

Issue 2:
Make sure these boxes are checked before submitting your issue - thank you!

I have checked the superset logs for python stacktraces and included it here as text if any

I have reproduced the issue with at least the latest released version of superset

I have checked the issue tracker for the same issue and I haven't found one similar

Superset version

0.20.3

I seems that a combination of #3584 and #3508, although work correctly on their own, has created a new bug in the dashboard filter with the latest version.. ;_;

#3584 fixed a bug where created filter options were not updated, but #3508 replaced the date dropdowns with datepickers, which did not have predetermined options. This causes an index error when updating new options.

Modifying the date filter will cause the filter box UI to freeze up. Will have a hotfix PR soon.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.6.7

Operating System version: windows7

Java version: 1.7.0_79

Steps to reproduce this issue

provider

<dubbo:service version="1.0.0" group="dubbo" protocol="http"

interface="dubbo.api.ApiService" ref="apiService"/>

consumer

<dubbo:reference id="apiService" version="1.0.0" group="dubbo" protocol="http" check="false" interface="dubbo.api.ApiService"/>

3.log

com.alibaba.dubbo.registry.integration.RegistryDirectory: Unsupported protocol http in notified url:

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

What do you expected from the above steps？

Actual Result

What actually happens?

If there is an exception, please attach the exception trace:

Just put your stack trace here!

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

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: xxx

Operating System version: xxx

Java version: xxx

Steps to reproduce this issue

xxx

xxx

xxx

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

What do you expected from the above steps？

Actual Result

What actually happens?

If there is an exception, please attach the exception trace:

Just put your stack trace here!
Issue 1:
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gke-staging-parallel/879/

Run so broken it didn't make JUnit output!

Issue 2:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gke-staging-parallel/561/

Multiple broken tests:

Failed: [k8s.io] Network should set TCP CLOSE_WAIT timeout {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kube_proxy.go:209
Expected error:
<*errors.errorString | 0xc8200e57c0>: {
s: "timed out waiting for the condition",
}
timed out waiting for the condition
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/pods.go:57

Issues about this test specifically: #36288 #36913

Failed: [k8s.io] InitContainer should not start app containers if init containers fail on a RestartAlways pod {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/init_container.go:274
Expected
<*errors.errorString | 0xc8201aa880>: {
s: "timed out waiting for the condition",
}
to be nil
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/init_container.go:263

Issues about this test specifically: #31408

Failed: [k8s.io] ReplicationController should serve a basic image on each replica with a public image [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/rc.go:38
Expected error:
<*errors.errorString | 0xc8201056a0>: {
s: "timed out waiting for the condition",
}
timed out waiting for the condition
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/rc.go:108

Issues about this test specifically: #26870 #36429

Failed: [k8s.io] Kubectl client [k8s.io] Kubectl logs should be able to retrieve and filter logs [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:843
Nov 26 15:38:18.957: Verified 0 of 1 pods , error : timed out waiting for the condition
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:202

Issues about this test specifically: #26139 #28342 #28439 #31574 #36576

Failed: [k8s.io] DNS should provide DNS for pods for Hostname and Subdomain Annotation {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/dns.go:437
Expected error:
<*errors.errorString | 0xc8200db7c0>: {
s: "timed out waiting for the condition",
}
timed out waiting for the condition
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/dns.go:236

Issues about this test specifically: #28337
Issue 1:
Hello Everyone!

I was wondering if it would be possible to implement a method so that users who develop Electron-based apps could bundle their applications with the electron executable as to help obscure their source code further.

As it currently stands, it's rather simple for someone to obtain the source code of your application regardless of whether or not you bundle it into an .asar file.

Although not entirely secure, as it currently stands NW.JS has a method for bundling their .nw files (which is basically a ZIP File renamed) with their executable. I can't quite remember exactly how it was done (because it's been a while since I've used electron or nw.js), but I explain it briefly in this other Github post for Electron-packager.

electron/electron-packager#152

Here is the command line tool for bundling .nw files into an executable with Node-Webkit

copy /B nw.exe+app.nw app.exe

The only issue with this is that even if electron adopted this kind of method it would still not be entirely secure. There are still ways that you could get the source code.

The only way I see this working is if someone built a tool to create a custom version of electron that had a sort of encryption key in it that would decrypt the .asar file and run it's contents that way. Because other than that I see no other way of doing this..

Any suggestions?

If I've missed something, please let me know. I'm just getting back into electron after a long while of doing other things.

Thanks

Issue 2:
It appears to have been a while since the last discussions on source code protection with snapshots. NW.js and enclosejs have found ways to do snapshots without including the source code. I was wondering if this could be looked at again, thank you!
Issue 1:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
3.2.0

Here is our build performance.

After upgrade to Symfony 3.2, automated tests suite take 2x longer to finish.

I tracked it down to this PR #21381

Issue 2:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
3.2.3

Created simple gist to show this https://gist.github.com/tarlepp/be57391ceead9099d66e3500001ae58b also tested with phpunit 5.7.11 and the results are the same.

I tracked this to commit e59f0e0#diff-0e793081ceb720201745c982a568903fL1046

Maybe that $container->setAlias('annotation_reader', 'annotations.cached_reader'); was removed by mistake ?
Issue 1:
When using pd.ExcelWriter, it appears that calling the save method prevents you from subsequently creating new sheets. E.g. see the following test script

import pandas as pd
import numpy as np
import os

if __name__ == "__main__" :
dates = pd.date_range('20130101', periods=6)
df = pd.DataFrame(np.random.randn(6,4), index=dates, columns=list('ABCD'))

currentpath = os.path.realpath(__file__)
outputpath = os.path.join(currentpath, "..\\test.xlsx")

writer = pd.ExcelWriter(outputpath)
df.to_excel(writer, "thing1")

writer.save() #if you remove this line it works as expected

new_sheet = writer.book.add_worksheet("thing2")
new_sheet.write(1,1,"test")

print writer.book.sheetnames

writer.save()
writer.close()

Issue 2:
Hello,

try

import requests
from pandas.io.json import json_normalize
import json
import pandas as pd
response = requests.get("http://api.openweathermap.org/data/2.5/history/station?start=1356220800&end=1356307200&type=hour&id=5530")
df = json_normalize(json.loads(response.text)['list'])
df['dt'] = pd.to_datetime(df['dt'], unit='s')
#df = df.set_index('dt')
df = df[['dt', 'main.temp.ma']]
print(df)

engine = 'openpyxl'
filename = "out_%s.xlsx" % engine
writer = pd.ExcelWriter(filename, engine=engine)
#df.to_excel("out.xls")
df.to_excel(writer)

engine = 'xlsxwriter'
filename = "out_%s.xlsx" % engine
writer = pd.ExcelWriter(filename, engine=engine)
#df.to_excel("out.xls")
df.to_excel(writer)

engine = 'xlwt'
filename = "out_%s.xls" % engine
writer = pd.ExcelWriter(filename, engine=engine)
#df.to_excel("out.xls")
df.to_excel(writer)

Only out_xlsxwriter.xlsx is create

I was expecting out_openpyxl.xlsx and out_xlwt.xls to be created.

See also #9139

Kind regards
Issue 1:
What problem does this feature solve?

for example in render function:

const a = 'Hello world unReactivity'

export default {
render(c){
return c(div,[a])
}
}

here the a is not a reactivity data,but when we use template,it seems that we must make a to be a reactivity data?sometimes is not in need.

What does the proposed API look like?

<template>
<div>
{{ a }}
</div>
</template>
<script>
export default {
unReactivity:{
a: 'Hello world unReactivity'
}
}
</script>

Issue 2:
What problem does this feature solve?

I think it would be nice to be able to have some sort of description or documentation index for the props. This index can than also be displayed in the vue devtools. I think it would help other users using already build components. For example when using a framework like vuetify so they don't have to go back to the documentation of what a prop does.

What does the proposed API look like?

props: {
message: {
type: String,
description: "Represents the the message of the notification"
}
}
Issue 1:
thank you very much

Issue 2:
With 0.20, we now have an excellent Color Picker in PowerToys (thanks to @martinchrzan). There's an opportunity here to create something that goes beyond just picking colors and really speeding up the workflow for (front-end) developers and designers. An editor window could really help to expand the current feature set.

Here's a breakdown of features that might be interesting to add.

Current color picker improvements (Should have)

Support more zoom levels (100% / 500%?)

Theming support (light / dark / high contrast)

(Visual) feedback that the color is copied to clipboard

Support for color-picking :hover states of e.g. a button (this can be done by using the zoom functionality)

Add keyboard shortcuts to zoom (+ - - ) and using arrow keys to control the picker for pixel accuracy.

Making the zoom-in feature more accessible / easy to use / discoverable

Change cursor to a color dropper when in color-picking mode.

Show color name (for accessibility)

Add a way to still support page/window scrolling when in picker mode (e.g. color picker zoom only activated on holding keyboard key (Ctrl?)?) (Can be done by scrolling first?)

Color editor

A color editor could be a view that will show up automatically after picking a color, or can be launched directly. It would provide the following features.

History of colors (Should have)

The ability to see previously picked colors.

Color palette & tweaking (Nice to have)

Automatically generate similar color tones based on the selected color (for e.g. having a nice hover color for a button)

Tweaking the selected color within the editor to do some fine-tuning

More/configurable color code formats (Should have)

It would be great to support more color formats. And for front-end developers, it would be even better to provide code snippets for popular languages (e.g. CSS) to make it even more useful. Clicking on a color code would automatically copy it to clipboard.

Support for more color formats (Must have)

Configurable color formats: let the user create custom color formats so they have the complete freedom to create something custom. It would be nice to re-sort the list or to set a format as the default copy-to-clipboard. The format editor would live in Settings. (Should have)

Proposal: plug-in based?

There's a WinUI 2.4 UWP mock-up available for anyone to check out here: https://github.com/niels9001/ColorPickerUX

Looking forward to see other feature requests.

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Issue 1:
At our company we started to use deno as an alternative to make and bash to provide and run build-scripts for multiple projects. Each project contains an aid.ts file in its root which provides a micro-CLI using docopt. So far this works nicely.

To make the aid.ts files executable from the command line we use this shebang (works on Linux and Mac):

#!/bin/sh
":" //; exec deno run -A --allow-run --unstable --allow-env --allow-write=.local/ --allow-read "$0" "$@"

A user can access the CLI like this: aid.ts arg1 arg2 ...

I would love to remove the .ts file extension so that a user can run the tools via aid arg1 arg2..., but as far as I can tell this doesn't work right now. When I remove the extension, deno will interpret the aid file as JavaScript and complain.

I think it would be nice if deno offered a way to run such executables without extension. I guess a simple --ts flag for deno run would suffice. What do you think? :-)

Issue 2:
I'm trying out deno for scripting (it's been a great experience so far, kudos!).

I'd like to be able to create script files without a .ts extension. If I do this, then the following is interpreted as JS and I get a syntax error on the type annotations:

#!/usr/bin/env -S deno run --allow-run --allow-read --allow-write

// code: language=typescript

function hello(name: string) {
console.log("Hello,", name);
}

hello(Deno.args[0]);

$ ./myscript
error: Uncaught SyntaxError: Unexpected token ':'
function hello(name: string) {
^
at file:///home/joe/tmp/myscript:5:20

I believe the simplest solution would be to add a CLI flag to force script to be interpreted as typescript.

Something like:

--language=[javascript, typescript]

so in the above script the shebang becomes:

#!/usr/bin/env -S deno run --language=typescript --allow-run --allow-read --allow-write
Issue 1:
Numpy 1.8.2 with python 2.7.6 has unconsistent behaviour when doing inplace division of arrays exceeding the buffer size.

import numpy as np
arr = np.random.rand(2, 5000)
arr_copy = arr.copy()
arr_copy = arr_copy / arr_copy[0]
arr /= arr[0]
print np.sum(arr != arr_copy), arr.size - np.sum(np.isclose(arr, arr_copy))

Should print 0 for equal divisions.

This can be circumvented by increasing the buffersize, nevertheless it should be emphasized, that this can happen.

Issue 2:
Original ticket http://projects.scipy.org/numpy/ticket/1085 on 2009-04-15 by trac user tillmann, assigned to @charris.

import numpy as np

x=np.array([[1,2],[3,4]])

print x

[[1 2]

[3 4]]

x+=x.T

print x

[[2 5]

[8 8]]

when writing code on such a high level of abstraction this behavior is not expected and imho wrong. At least a warning should be issued or better the in place operations should fall back to creating copies if the results are not correct otherwise.
Issue 1:
Describe the issue

I've deployed successfully my backend to a serverless cloud service, but, unlike the local version, in the hosted app I'm getting an unreadable response rather than JSON as you can see below.

"��\b��������T�r�8�����r�i�.~�����FH�!�\t��01�C���\\��*Y�T��e�{�=��{��N�gY?_�]��Aӝ�.yQw?k/?��۬=�|���<��#�dd3�)��6�����l2\n�J]X��������e��^�?\r|�H

Example Code

app.get('/api/get-my-books', (req, res) => {

const address = req.query.address;
const chain = "polygon";

const options = {
method: 'GET',
url: `https://api.nftport.xyz/v0/accounts/${address}`,
params: {
chain: chain,
include: 'metadata',
contract_address: process.env.REACT_APP_DROP_CONTRACT
},
headers: {
'Content-Type': 'application/json',
Authorization: process.env.REACT_APP_NFT_PORT
}
};

axios.request(options)
.then((response) => {
res.json(response.data);
})
.catch((error) => {
console.error(error);
});
});

Expected behavior

A readable JSON response is expected.

Axios Version

1.2.0

Adapter Version

No response

Browser

Chrome

Browser Version

No response

Node.js Version

14.19.1

OS

No response

Additional Library Versions

"cors": "^2.8.5",
"dotenv": "^16.0.3",
"express": "^4.18.2"

Additional context/Screenshots

No response

Issue 2:
Describe the bug

`

var axios = require('axios');

var data = JSON.stringify({

"production_status": "",

"package_status": [],

"extra_status_reason": [],

"page": 1,

"limit": 1

});

var config = {

method: 'post',

url: 'https://example.com/',

headers: {

'Authorization': 'Bearer token',

},

data: {

"production_status": "",

"package_status": [],

"extra_status_reason": [],

"page": 1,

"limit": 1

}

};

axios(config)

.then(function (response) {

console.log(response.data);

})

.catch(function (error) {

console.log(error);

});

`

When i send API this response

I want respose must be json like that

To Reproduce

No response

Code snippet

No response

Expected behavior

No response

Axios Version

1.2.0

Adapter Version

No response

Browser

No response

Browser Version

No response

Node.js Version

14.20.1

OS

No response

Additional Library Versions

No response

Additional context/Screenshots

No response
Issue 1:
While using Typescript I've encountered a problem with packaging of an application: it is splitted into separate js files and can't be bundled into one file because of duplication of variables and file-related modules system used by SystemJS. I've tried AMD and CommonJS, both with the same result. For example, there will be an error if we have some main application file and importing another file from a folder "services", just like this:

import {NodeXHRImpl} from 'services/NodeXHRImpl';

I've also tried to wrap my NodeXHRImpl class into a module named "services", and import it with a "require" keyword:

import NodeXHRImpl = require('services/NodeXHRImpl')

after that got an error sounds like "object is not a function" when tried to instantiate an imported class. And another thing: the compiler inserts the Reflect.decorate function that is duplicated among all compiled files and it seem like not a good option for production.

It will be a very handy to have some minimal application demonstrating the modularity and, what is most important, it should be production-ready, i.e. possible to be bundled into a single file(or a bunch of files separated by functionality, for example).

Issue 2:
Currently there is a mix of Console service and getDom().log()

We should unify the log reporting in a Log service.
Issue 1:
Elasticsearch version:

elasticsearch 2.3.4

Describe the feature:

Slow Query log to include information when the query is over an index alias.

Specially if the alis includes a filter this should be visible from slow query log. At the moment these logs don't show any information and look identical when alias is used or not.

Steps to reproduce:

install elasticsearch 2.3.4

index some data. example data, use shakespeare data from docs.

create an alias with a filter, as an example:

POST _aliases/

{

"actions" : [

{

"add" : {

"index" : "shakespeare",

"alias" : "shakespeare_lines",

"filter" : { "type" : {"value":"line"} }

}

}

]

}

4- configure slow log with a very low threshold

index.search.slowlog.threshold.query.trace: 1ms

index.search.slowlog.threshold.fetch.trace: 1ms

5- query the data

{

"query": { "match_all": {} }

}

6- see below log lacking any reference to the alis or the filter.

[2016-08-09 16:10:58,120][INFO ][index.search.slowlog.query] [shakespeare]took[1.1ms], took_millis[1], types[], stats[], search_type[QUERY_THEN_FETCH], total_shards[5], source[{"query":{"match_all":{}}}], extra_source[],

Issue 2:
When using filtered aliases filtered by type, it will be helpful for slowlog to report the types queried. Currently, it returns types[].

POST /_aliases
{
"actions": [
{
"add": {
"index": "index_name",
"alias": "slowlogalias",
"filter": {
"term": {
"_type": "doc_type"
}
}
}
}
]
}
Issue 1:
Would like the ability to have meta data per property in the mapping, and have GET mapping return it.

{
theytype: {
properties: {
field1: {
type: "long",
_meta: {
info:"field1 info"
}
},
field2: {
_meta: {
info:"urls mutli field info"
},
type: "multi_field",
path: "just_name",
omit_norms: true,
fields: {
field2: {type: "string", analyzer: "snowball"},
rawfield2: {type: "string", index: "not_analyzed"}
}
}
}
}
}

It looks like I could use fielddata for this too, however seems like a hack, and I wasn't sure if it would hurt performance. Feature might be useful for folks who want to add comments.

Issue 2:
A mapping can have a _meta element - but it only keeps it if declared on the top level.

When using the _meta to annotate a mapping, or keeping custom configuration on it, or using it for some binding - a lot of times besides the top level you also need more custom data on a field level. So you need the mapping to keep also _meta nodes defined under fields.