WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
If there is interest, I could provide an FFT library implemented in C99 that is based on fftpack, but falls back to Bluestein's algorithm for near-prime lengths. Accuracy should also be better than the original fftpack.

You can have a look at the code at https://gitlab.mpcdf.mpg.de/mtr/pocketfft

I can contribute this under the 3-clause BSD license, but I haven't added the necessary file headers yet.

Issue 2:
I thought we had an issue open for this but cannot find it now. Occasionally, CI jobs fail like this one with

gcc: build/src.linux-x86_64-3.7/numpy/core/src/multiarray/einsum_sumprod.c
during IPA pass: profile
numpy/core/src/multiarray/einsum_sumprod.c.src: In function ‘longdouble_sum_of_products_contig_three’:
numpy/core/src/multiarray/einsum_sumprod.c.src:1264:1: internal compiler error: in coverage_begin_function, at coverage.c:656
1264 | }
| ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-9/README.Bugs> for instructions.

Note it is in the coverage compilation of the generated code, in the "full" CI run with gcc 9.3.0
Issue 1:
Tooltip container visible all the time, rather than just when necessary, meaning it get in the way of other elements, e.g. buttons.

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

Expected Behavior

The entire tooltip element should not be rendered until I hover over the tooltip activation element.

Current Behavior

The tooltip element is rendered all the time, taking up space with a high z-index. When the element is on top of buttons it makes it so you cannot click that area of the button.

The tooltip itself is not visible until I hover over the correct element, but the empty container is always there.

Steps to Reproduce (for bugs)

Implement tooltip

Add button in area where tooltip is rendered

Try and click on button when tooltip is hidden (it should be unclickable)

Alternatively, just inspect element with tooltip, and you will see the container element on top of the page when you hover over it.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.11

React
15.5.3

browser
Chrome 60

Issue 2:
I know you guys are discussing how to manage theming and CSS going forward. There's React Toolbox which is using CSS Modules, but I went with Material UI because of the more extensive list of components, and I'm not sure about the future of CSS Modules just yet. I tend to watch and see what Facebook officially endorses since, you know, they're the creators of React. ;)

Have you guys looked at Radium though, as a potential stopgap solution? I'm using it in a project of mine, and it's excellent. It can even handle things you can't do with inline styles such as duplicate keys (display: flex; display: -webkit-flex) and pseudo-classes/elements. It even automatically handles vendor prefixes automatically, so with Radium, you can just use an inline style such as {display: 'flex', flex: 1} and it will handle that for you.
Issue 1:
see the issue in docker/docker-py#1325, although I am not sure this is a right place to post.

Issue 2:
I am talking to an app with a custom auth module that I've written. The auth object installs a hook, and if the response fails and indicates that the auth object is expired, I get a new auth object.

I'd like to be able to retry the exact same request with the same settings as the previous request but with a new auth object from my response hook. This means I'd like to be able to make the request as part of the same session (ideally) but to also have access to the initial request parameters such as verify.
Issue 1:
I don't have a tiny screen, but there's still not enough space to see all of the TOC navigation list on the left hand side, and it doesn't scroll, so there's no way for me to access the bottom half of it.

Issue 2:
On the Components page of the Bootstrap docs, the sidebar becomes too tall for the viewport when scrollspy causes the sidebar subheadings to show.

The sidebar cannot be scrolled or manipulated to show content below the viewport.

See here: http://getbootstrap.com/components/#glyphicons
Issue 1:
What problem does this feature solve?

Hello everyone,

Sometimes i want to show different content depending on a variable value and v-if is a bit less legible than this proposed v-switch directive

What does the proposed API look like?

<template v-switch="variable">
<div v-case="1">
... some content A
</div>
<div v-case="2">
... some content B
</div>
<div v-default>
... some content C
</div>
</template>

Note that the <div>s can be <template>s or components as well

Issue 2:
What problem does this feature solve?

Syntax sugar on several v-if, v-else-if, v-else-if etc

An example syntax could be:

<div class="wrapper" v-switch="headingType">
<h1 v-case="big">Headline</h1>
<h2 v-case="small">Headline</h2>
<h3 v-case="smaller">Headline</h3>
</div>

To do this in the current setup would be:

<div class="wrapper">
<h1 v-if="headingType === 'big'">Headline</h1>
<h2 v-else-if="headingType === 'small'">Headline</h2>
<h3 v-else-if="headingType === 'smaller'">Headline</h3>
</div>

You can see how the switch statement would make the html markup so much cleaner

What does the proposed API look like?

<div class="wrapper" v-switch="headingType">
<h1 v-case="big">Headline</h1>
<h2 v-case="small">Headline</h2>
<h3 v-case="smaller">Headline</h3>
</div>
Issue 1:
wonder if console.log on objects, and any non-string types has any standard?

> var data = {"totalTax":7.45,"summary":[{"jurisName":"Utah","taxCalculated":4.85,"jurisType":"State","taxType":"Sales"},{"jurisName":"Salt Lake","taxCalculated":1.35,"jurisType":"County","taxType":"Sales"},{"jurisName":"Murray","taxCalculated":0.2,"jurisType":"City","taxType":"Sales"},{"jurisName":"Salt Lake Co Tr","taxCalculated":1.05,"jurisType":"Special","taxType":"Sales"}]};

> console.log(data);
{
totalTax: 7.45,
summary: [
{ jurisName: "Utah", taxCalculated: 4.85, jurisType: "State", taxType: "Sales" },
{
jurisName: "Salt Lake",
taxCalculated: 1.35,
jurisType: "County",
taxType: "Sales"
},
{ jurisName: "Murray", taxCalculated: 0.2, jurisType: "City", taxType: "Sales" },
{
jurisName: "Salt Lake Co Tr",
taxCalculated: 1.05,
jurisType: "Special",
taxType: "Sales"
}
] // I believe this line not aligning is a bug, it has no leading space, better align with above `summary`
}
undefined

compare with in node:

> console.log(data)
{ totalTax: 7.45,
summary:
[ { jurisName: 'Utah',
taxCalculated: 4.85,
jurisType: 'State',
taxType: 'Sales' },
{ jurisName: 'Salt Lake',
taxCalculated: 1.35,
jurisType: 'County',
taxType: 'Sales' },
{ jurisName: 'Murray',
taxCalculated: 0.2,
jurisType: 'City',
taxType: 'Sales' },
{ jurisName: 'Salt Lake Co Tr',
taxCalculated: 1.05,
jurisType: 'Special',
taxType: 'Sales' } ] }
undefined

also, node's REPL console.log has ansi coloring output for different types on terminals, will this come into Deno anytime soon?

Issue 2:
Match colors and semantics.

node's stringify has been tweaked and optimized over many years, changing anything is likely surprising in a bad way.
Issue 1:
I have created a demo test case of the problem on jsfiddle: http://jsfiddle.net/vjwz7/

You can best see the problem with Chrome.

Reproducing the problem:

double click on the word "adipiscing" (you notice that text selection works well)

click on the link icon and click "create link" (don't need to enter a link for this demo)

now try to double click on the text "interdum" or "adipiscing" => impossible.

Explanation:

When you click on the link icon, a popover appears. When you then click on the "Create link" button, I hide the popover (popover("hide")); the popover is hidden BUT I can no longer select the text that is below the hidden popover.

Issue 2:
i searched for an already opened issue but did not found any that was reporting this exact problem.

I'm trying to use the destroy method on tooltip (bootstrap v3) but it does not remove the element from the DOM.

Any idea ?

Fiddle : http://jsfiddle.net/52VtD/59/

click on the button to trigger the tooltip destroy method
Issue 1:
I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

I have a form with a submit button disabled if the form is not valid. This form contains a "username" input and a "password" one. When the page is loaded, these inputs are automatically filled in by Chrome but the button stays disabled (while all input contains valid data).

Expected behavior

The button should become enabled when the form is automatically completed by Chrome with valid data.

Minimal reproduction of the problem with instructions

Run this plunkr

Select the option to open the plunkr in a separate window

If the form is not automatically filled in, fill it in, submit the form, close the window and run the plunkr in a separate window again

Normally, the form should be automatically filled in by the browser but the button will be grayed out

Note that, even though the button is grayed out, I can click on it to send the form but it's not obvious for the user.

What is the motivation / use case for changing the behavior?

A concrete use case would be to prevent a form to be sent if it's empty. However, the user should be able to send the form if this one is completed automatically by the browser.

Please tell us about your environment:

Windows 10

PHPStorm

npm

Webpack

Angular 2.0.2

Chrome 53

TypeScript 2.0.2

node 4.4.7

Issue 2:
I'm submitting a ... (check one with "x")

[x ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

When you make a Component with an attribute with @input() named style, PhantomJS will produce a TypeError: Failed: Attempted to assign to readonly property.

It works properly with any other navigator.

Expected behavior

It shouldn't fail in PhantomJS

Minimal reproduction of the problem with instructions

export class StyleComponent implements OnInit {

@input() style: any;

}

in app.html: <app-style [style]="whatever">

I've detected this bug using primeng, wich uses [style] property to pass style to its components, and then I found in an issolated project this weird behaviour.

What is the motivation / use case for changing the behavior?

With this bug, developers may not use an attribute named style (wich is a name very usual for an input attribute) if they want to test with PhantomJS their code.

Please tell us about your environment:

Windows 7, ng-cli 1.0.0, npm 4.1.2, node 6.9.5

Angular version: 4.1.2

Browser: [ PhantomJS ]

Language: [ ES5]

Node (for AoT issues): node --version = 6.9.5
Issue 1:
Right now you cannot clone a THREE.Line when it's geometry attribute is a type of THREE.Geometry.

This is because the clone method calls the constructor without parameters so that the new line's geometry attribute will be constructed as a THREE.BufferGeometry by default. Then the copy method tries to copy a THREE.Geometry object into a THREE.BufferGeometry, which doesn't work.

So shouldn't the clone method look like the one in THREE.Mesh ? meaning:

`clone: function () {

return new this.constructor(this.geometry, this.material).copy( this );

}`

This fiddle shows the error:

I don't know but maybe this kind of problem could exist at other places too.

Three.js version

Dev

r99

...

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS

Hardware Requirements (graphics card, VR Device, ...)

Issue 2:
ref: #15062

If you are constructing a line, use Geometry

Then line.clone() will cause an error.

let l = new Line(new Geometry());
l.clone();
Issue 1:
No availability apparent for dropdown submenu, and no visible replacement option

Issue 2:
Hi, I try to migrate from bootstrap 2, but this code:

<li class="dropdown"> <a href="#" class="dropdown-toggle" data-toggle="dropdown">Cadastros <b class="caret"></b></a> <ul class="dropdown-menu"> <li class="dropdown-submenu"> <a tabindex="-1" href="#">Clientes</a> <ul class="dropdown-menu"> <li><a href="{% url 'CadPessoa' %}">Novo Cliente</a></li> <li><a href="{% url 'ListaCliente' %}">Listar Clientes</a></li> </ul> </li> </li> </ul> </li>

doesn't work. Don't show me the submenu.. what I miss?
Issue 1:
the brownie points of @alayek (freecodecamp.com/alayek) don't match what he sees on his navbar:

https://files.gitter.im/alayek/oeko/Screenshot-from-2015-10-27-10_54_55.png

Issue 2:
Advanced Algorithm No Repeat Please has an issue.

User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36.

Code editor stuck and screen cannot be accessed after put first code revision in. This code here is a slight modified version to be changed. Please help check the page.

Much thanks!!

function permAlone(str) {

//split string to array

var chars = str.split("");

var noRepeat = [], permArr = [], usedChars = [];

//check if all characters same return 0

var matched = 0;

for (var j = 0; j < chars.length - 1; j++) {

if (chars[j] === chars[j+1]) matched++;

}

if (matched === chars.length - 1) {

return 0;

} else { //if not all matching characters

//create permutaion of strings (factorial) recursive n! into new array

(function permutate() {

for (var i = 0; i < chars.length; i++) {

var ch = chars.splice(i, 1);

usedChars.push(ch);

if (chars.length === 0) permArr[permArr.length] = usedChars.join("");

permutate(chars.join(""));

chars.splice(i, 0, ch);

usedChars.pop();

}

return permArr;

})(chars);

//check for consecutive same characters regexp exclude
noRepeat = permArr.filter(function(value){
var regex = /([a-zA-Z])\1+/;
return (!regex.test(value)); //return value when there is no duplicate
});

}

return noRepeat.length;

}
Issue 1:
This is a feature of sublime text which I really like. When clicking on a file in the sidebar it works like the following.

File a is shown, the tab's title is printed in italics.

When opening file b, a is to be closed.

Let's assume we do this again but we add a particular step in between

File a is shown, the tab's title is printed in italics.

Edit file a, the tab's title changes from italics to regular.

Open file b. File a stays open.

Double click on file a

File a is shown, tab's title in regular.

Open file b. File a stays open.

This is really useful for browsing files as it does not clutter your tabs bar. Maybe you could add an option to disable this feature.

Issue 2:
Support sublime-like preview mode when opening files from the tree view, fuzzy finder, find and replace, etc.

The main issue being tracked is here: atom/tree-view#3
Issue 1:
The range aggregation currently based upon documentation and my testing only supports to and from terminology.

In the theme to avoid ambiguity and prefer lt, lte, gt, and gte it would be nice if the aggregation query DSL support this.

Current

{
"aggs" : {
"price_ranges" : {
"range" : {
"field" : "price",
"ranges" : [
{ "to" : 50 },
{ "from" : 50, "to" : 100 },
{ "from" : 100 }
]
}
}
}
}

Proposed

{
"aggs" : {
"price_ranges" : {
"range" : {
"field" : "price",
"ranges" : [
{ "lte" : 50 },
{ "gte" : 50, "lt" : 100 },
{ "gte" : 100 }
]
}
}
}
}

@dakrone

Issue 2:
Currently, the behaviour appears to be that when specifying a range aggregation, the lower value is included, but the upper value is not.

If I index the following data:

{ "integer" : 0, "float" : 1.0, "date" : "2014-03-10" }
{ "integer" : 1, "float" : 1.1, "date" : "2014-03-11" }
{ "integer" : 2, "float" : 1.2, "date" : "2014-03-12" }
{ "integer" : 3, "float" : 1.3, "date" : "2014-03-13" }
{ "integer" : 4, "float" : 1.4, "date" : "2014-03-14" }
{ "integer" : 5, "float" : 1.5, "date" : "2014-03-15" }
{ "integer" : 6, "float" : 1.6, "date" : "2014-03-16" }
{ "integer" : 7, "float" : 1.7, "date" : "2014-03-17" }
{ "integer" : 8, "float" : 1.8, "date" : "2014-03-18" }
{ "integer" : 9, "float" : 1.9, "date" : "2014-03-19" }
{ "integer" : 10, "float" : 2.0, "date" : "2014-03-20" }

And then (illustrating with dates) do a range aggregation:

"date_range" : {
"date_range" : {
"field" : "date",
"ranges" : [ {
"from" : "2014-03-15",
"to" : "2014-03-17"
} ]
}
}

I get the following results:

"date_range" : {
"buckets" : [ {
"key" : "2014-03-15T00:00:00.000Z-2014-03-17T00:00:00.000Z",
"from" : 1.3948416E12,
"from_as_string" : "2014-03-15T00:00:00.000Z",
"to" : 1.3950144E12,
"to_as_string" : "2014-03-17T00:00:00.000Z",
"doc_count" : 2
} ]
}

Here we can see that its not including both from and to in the aggregation (or otherwise we would expect a doc_count of 3. The same is true if you do a range aggregation on the integer or decimal number.

Doing a different aggregation illustrates that its the upper thats getting omited:

"date_range_upper" : {
"date_range" : {
"field" : "date",
"ranges" : [ {
"from" : "2014-03-01",
"to" : "2014-03-10"
} ]
}
}

Gives results

"date_range_upper" : {
"buckets" : [ {
"key" : "2014-03-01T00:00:00.000Z-2014-03-10T00:00:00.000Z",
"from" : 1.393632E12,
"from_as_string" : "2014-03-01T00:00:00.000Z",
"to" : 1.3944096E12,
"to_as_string" : "2014-03-10T00:00:00.000Z",
"doc_count" : 0
} ]
}

It needs to be possible to include the upper (or omit the lower) value in the aggregation specification.

Here is an example of what I need to do:

I want to do an aggregation as follows:

"aggregations": {
"intentDate": {
"date_range": {
"field": "intentDate",
"ranges": [
{
"key": "Overdue",
"to": "2014-02-17"
},
{
"key": "March",
"from": "2014-02-18",
"to": "2014-03-17"
},
{
"key": "April",
"from": "2014-03-18",
"to": "2014-04-15"
}
]
}
}
}

I want the upper value to be inclusive in the range.

Then I want to take the results to create a filter - without having to do any date/datetime manipulation to translate between them.
Issue 1:
The docs (https://material-ui.com/customization/css-in-js/#css-injection-order) suggest using a HTML Comment Node as a custom jss insertion point to control the order in which CSS is injected.

This does not work if users strip out HTML comments as part of their build process.

create-react-app, which currently strips HTML comments when creating the production build, can only be reconfigured to not strip comments if "ejected", which is undesirable for many users.

A work-around is to reference a node other than a comment node as the jss insertion point.

eg

const insertionPoint = document.getElementById('insertion-point-jss')
jss.setup({ insertionPoint })

<head>
<noscript id="insertion-point-jss"></noscript>
<title>I am the last element</title>
</head>

As create-react-app + material-ui is a pretty common combination I think it could be worth highlighting this problem in the docs, or providing guidance that doesn't rely on html comments.

Thoughts on a less hacky solution?

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

Expected Behavior

If docs are followed CSS injection order should be honoured when using create-react-app

Current Behavior

If HTML Comments are stripped (eg by create-react-app default config) then injection order is broken.

Steps to Reproduce (for bugs)

in a react-scripts app

yarn run build

Context

styled-components/styled-components#860 (comment)

Your Environment

Tech
Version

Material-UI
1.x

React
x.x

browser
x.x

create-react-app
1.x

Issue 2:
Since the docs are mostly out of date, are there any canonical examples for the beta?

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

E.g., https://material-ui.com/demos/app-bar points to the v1.0.0-beta.22 docs (same version I'm using), but the inline examples (expanding "<>") are out of date. E.g.,

import { withStyles } from 'material-ui/styles';

should be:

import withStyles from 'material-ui/styles/withStyles';

OR

import { withStyles } from 'material-ui';

Of course it's beta and I'm fine looking through the source, but having at least one non-broken example would be really useful -- and I would think cut down the bug traffic? (e.g., how are you testing this yourselves other than unit tests?)

Thanks for the package.
Issue 1:
Has anyone considered/tried generating documentation for Zeal/Dash? It would be great to have offline docs. I would be happy to give it a go, just want to make sure I am not duplicating efforts or trying something known to not work (though it looks like it should work using doc2dash).

Issue 2:
Following PR #13511 it appears that there is not reference benchmark for SVMs in scikit-learn or in any side-project (sklearn-contrib).

This seems quite risky on the long run, maybe we should create one - especially to quantify the impact of changes to C code such as in PR #13511 .

I have been working quite a bit on this topic of creating reference benchmarks in the past years, leading to the creation of tools in the pytest ecosystem: pytest-cases and pytest-harvest, with a beginning of tutorial here (outdated I'm afraid). I can therefore certainly try to help with a benchmark framework structure if you find such an idea interesting.

However I do not know a good set of reference datasets to start with (apart from creating challenging ones "by hand").
Issue 1:
I found 2 interesting bugs when we want to create a dataset in SQL Lab:

When we create a dataset and provide some name and then want to do it again with the same name. In second dataset creation we got Untitled Query 7 08/31/2022 17:58:02 name but input has qwe1 name

[FIXED] When we reload page and create a duplicate name of dataset for example name=qwe1 then modal window is disappeared and don't handle error from server.

Expected results

We handle server error response and show "Dataset [qwe1] already exists" on UI side to user.

Actual results

Server error response is not handled.

Screenshots

Screen.Recording.2022-08-31.at.17.57.51.mov

Screen.Recording.2022-08-31.at.18.06.39.mov

Environment

(please complete the following information):

browser type and version:

superset version: superset version

python version: python --version

node.js version: node -v

any feature flags active:

Checklist

Make sure to follow these steps before submitting your issue - thank you!

I have checked the superset logs for python stacktraces and included it here as text if there are 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.

Additional context

Add any other context about the problem here.

@michael-s-molina @kgabryje @villebro @lyndsiWilliams

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 there are 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

Pypi version according to the README label: 0.28.1

Commit hash: 60d5f89faaa6e76fdfb87d3ba8d76766d268a43f

I am running a docker-based host that was created following the steps provided here.

Expected results

The following frontend routes should open with the correct styling and designed forms:

/superset/welcome

/chart/add

/superset/sqllab

Actual results

Note that the CSS files load successfully. There are no errors on the Console tab. No errors on requests either, according to the docker-compose log.

Steps to reproduce

Just open the pages, either through entering the URL on the browser or clicking the menu.