WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Code Sample, a copy-pastable example if possible

import pandas as pd

index = pd.timedelta_range('0', periods=4, freq='s')
series = pd.Series(range(4), index=index)
print series

print series.resample('2s', label='left').sum()

print series.resample('2s', label='right').sum()

print series.resample('2s', label='right', closed='right').sum()

The output

00:00:00 0
00:00:01 1
00:00:02 2
00:00:03 3
Freq: S, dtype: int64
00:00:00 1
00:00:02 5
Freq: 2S, dtype: int64
00:00:00 1
00:00:02 5
Freq: 2S, dtype: int64
00:00:00 1
00:00:02 5
Freq: 2S, dtype: int64

Problem description

When calling the function resample with a DatetimeIndex works as expected. However, if called with a TimedeltaIndex the options label and closed does not work.

Expected Output

00:00:00 0
00:00:01 1
00:00:02 2
00:00:03 3
Freq: S, dtype: int64
00:00:00 1
00:00:02 5
Freq: 2S, dtype: int64
00:00:02 1
00:00:04 5
Freq: 2S, dtype: int64
00:00:00 0
00:00:02 3
00:00:04 3
Freq: 2S, dtype: int64

Output of pd.show_versions()

# Paste the output here pd.show_versions() here

INSTALLED VERSIONS

commit: None

python: 2.7.6.final.0

python-bits: 64

OS: Linux

OS-release: 3.19.0-74-generic

machine: x86_64

processor: x86_64

byteorder: little

LC_ALL: None

LANG: en_GB.UTF-8

LOCALE: None.None

pandas: 0.19.2

nose: 1.3.1

pip: 9.0.1

setuptools: 28.8.0

Cython: 0.24.1

numpy: 1.12.0

scipy: 0.18.1

statsmodels: 0.5.0

xarray: None

IPython: 4.1.2

sphinx: 1.4.6

patsy: 0.4.1

dateutil: 2.6.0

pytz: 2016.10

blosc: None

bottleneck: None

tables: 3.1.1

numexpr: 2.2.2

matplotlib: 1.5.3

openpyxl: 1.7.0

xlrd: 0.9.2

xlwt: 0.7.5

xlsxwriter: None

lxml: None

bs4: 4.2.1

html5lib: 0.999

httplib2: 0.8

apiclient: None

sqlalchemy: None

pymysql: None

psycopg2: 2.4.5 (dt dec mx pq3 ext)

jinja2: 2.8

boto: None

pandas_datareader: None

Issue 2:
brought up in #12925

some examples in #15167

Resampling fence posts are off when upsampling < 1 Day.

In [5]: df = DataFrame(data=[[1, 3], [-5, 10], [0, 0]],index=pd.timedelta_range('00:00:00','00:10:00',freq='5T'))

In [6]: df.resample('1T').asfreq()
Out[6]:
0 1
00:00:00 1.0 3.0
00:01:00 NaN NaN
00:02:00 NaN NaN
00:03:00 NaN NaN
00:04:00 NaN NaN
00:05:00 -5.0 10.0
00:06:00 NaN NaN
00:07:00 NaN NaN
00:08:00 NaN NaN
00:09:00 NaN NaN

In [8]: df.resample('1T').mean()
Out[8]:
0 1
00:00:00 1.0 3.0
00:01:00 NaN NaN
00:02:00 NaN NaN
00:03:00 NaN NaN
00:04:00 NaN NaN
00:05:00 -5.0 10.0
00:06:00 NaN NaN
00:07:00 NaN NaN
00:08:00 NaN NaN
00:09:00 NaN NaN
00:10:00 0.0 0.0
Issue 1:
On this page specifically: https://material-ui-1dab0.firebaseapp.com/customization/themes, not the others apparently.

Versions

Material-UI: alpha 17

Browser: Firefox & chrome

Issue 2:
Given a case: I have 2 types of a Button, first one with rounded corners, second one without. Now in case I want all buttons inside of some subtree use the second type, I would want to use the MuiThemeProvider.

const theme1 = createMuiTheme({
overrides: {
Button: {
root: {
borderRadius: 10
}
}
}
})

const theme2 = createMuiTheme({
overrides: {
Button: {
root: {
borderRadius: 0
}
}
}
})

class Subtree extends Component {
render() {
return (
<ThemeProvider theme={theme2}>
<Button>Click me hard</Button>
</ThemeProvider>
)
}
}

class App extends Component {
render() {
return (
<ThemeProvider theme={theme1}>
<Subtree />
</ThemeProvider>
)
}
}

In this case, theme2 will overwrite theme1 style sheet.
Issue 1:
Challenge Target the Parent of an Element Using jQuery has an issue.

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:48.0) Gecko/20100101 Firefox/48.0.

Please describe how to reproduce this issue, and include links to screenshots if possible.

My code:

<script>
$(document).ready(function() {
$("#target1").css("color", "red");
$("#target1").prop("disabled", true);
$("#target4").remove();
$("#target2").appendTo("#right-well");
$("#target5").clone().appendTo("#left-well");

});
</script>

<!-- Only change code above this line. -->

<body>
<div class="container-fluid">
<h3 class="text-primary text-center">jQuery Playground</h3>
<div class="row">
<div class="col-xs-6">
<h4>#left-well</h4>
<div class="well" id="left-well">
<button class="btn btn-default target" id="target1">#target1</button>
<button class="btn btn-default target" id="target2">#target2</button>
<button class="btn btn-default target" id="target3">#target3</button>
</div>
</div>
<div class="col-xs-6">
<h4>#right-well</h4>
<div class="well" id="right-well">
<button class="btn btn-default target" id="target4">#target4</button>
<button class="btn btn-default target" id="target5">#target5</button>
<button class="btn btn-default target" id="target6">#target6</button>
</div>
</div>
</div>
</div>
</body>

Issue 2:
Challenge Waypoint: Clone an Element Using jQuery has an issue.

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.73 Safari/537.36.

Please describe how to reproduce this issue, and include links to screenshots if possible.

Issue

I believe I've found bug in the phone simulation in Waypoint: Clone an Element Using jQuery:

I entered the code to clone target5 and append it to left-well, and now I see three target5 buttons in the phone simulator. FCC says my code is correct and advances me to the next challenge. The following challenges also show three target5 buttons:

Waypoint: Target the Parent of an Element Using jQuery

Waypoint: Target the Children of an Element Using jQuery

@qualitymanifest confirms this issue on his Linux box.

My code:

<script>
$(document).ready(function() {
$("#target1").css("color", "red");
$("#target1").prop("disabled", true);
$("#target4").remove();
$("#target2").appendTo("#right-well");
$("#target5").clone().appendTo("#left-well");
});
</script>

<!-- Only change code above this line. -->

<div class="container-fluid">
<h3 class="text-primary text-center">jQuery Playground</h3>
<div class="row">
<div class="col-xs-6">
<h4>#left-well</h4>
<div class="well" id="left-well">
<button class="btn btn-default target" id="target1">#target1</button>
<button class="btn btn-default target" id="target2">#target2</button>
<button class="btn btn-default target" id="target3">#target3</button>
</div>
</div>
<div class="col-xs-6">
<h4>#right-well</h4>
<div class="well" id="right-well">
<button class="btn btn-default target" id="target4">#target4</button>
<button class="btn btn-default target" id="target5">#target5</button>
<button class="btn btn-default target" id="target6">#target6</button>
</div>
</div>
</div>
</div>
Issue 1:
I have followed the instruction to make flutter app. (stop at list of word pairings tutorial). Next I try building release version of iOS following instruction, archives and export from Xcode.

The ipa file is 68.9MB, while release version of apk file is 5.5MB. Is this normal?

If the size in not normal, how could I find and fix the issue in iOS?

Appreciate for any helps.

Issue 2:
With current beta 0.8.2 and latest dev, flutter build ios --release produces app which is 5 times the size of the app built with 0.7.2.

with 0.7.2 the size was around 22mb

with 0.8.2 the size is around 100mb

I've tested with basic flutter app by creating new flutter app and building it. Even basic app size is around 61mb

Steps to Reproduce

Create new flutter app.

Run flutter build ios --release

Check the size of the app

Images for reference

aot and app size

contents of the app

Logs

[✓] Flutter (Channel dev, v0.9.2, on Mac OS X 10.13.2 17C88, locale en-IN)
• Flutter version 0.9.2 at /Users/hari/development/flutter
• Framework revision 85b4670b2a (6 days ago), 2018-09-19 14:59:23 -0700
• Engine revision 2e8e96fad1
• Dart version 2.1.0-dev.4.0.flutter-4eb879133a

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
• Android SDK at /Users/hari/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-27, build-tools 27.0.3
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
• All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 9.4.1, Build version 9F2000
• ios-deploy 1.9.2
• CocoaPods version 1.5.3

[✓] Android Studio (version 3.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 28.0.1
• Dart plugin version 173.4700
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[✓] VS Code (version 1.27.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 2.18.0

[!] Connected devices
! No devices available

! Doctor found issues in 1 category.
Issue 1:
Hello everyone.

I have an issue to migrate from 0.25 to 0.36 superset

I can run it into a new venv with new installation and without to use my postgresql database, but when i try touse my database, I have some errors (new columns)

For example in the dashboard tab

I can see that this new version use new column for the new features

I tried "superset db upgrade" to update model database but i have some errors (see databaseèupgrade.txt file)

database upgrade.txt

Does I need to create a new database and migrate the data manually ?

Thanks in advance for your answer.

Issue 2:
One of the duplicated color theme 'D3 category 10' show as 'Superset_dafault' in meta data

How to reproduce the bug

Go to Dashboard properties

Click on color theme and select D3 category 10 (duplicated, please select each one)

Scroll down to 'Advance'

4.Observe the color_theme in meta data

See error

Expected results

Color theme name in properties will match the meta data color name

Actual results

One of the duplicated color theme 'D3 category 10' show as 'Superset_dafault' in meta data

Screenshots

If applicable, add screenshots to help explain your problem.

Environment

(please complete the following information):

browser type and version: chrome

superset version: master

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.
Issue 1:
julia/stdlib/LinearAlgebra/src/matmul.jl

Line 536
in
54adf21

# FIXME: This code is completely invalid!!!

julia/stdlib/LinearAlgebra/src/matmul.jl

Line 558
in
54adf21

# FIXME: This code is completely invalid!!!

I stumbled upon these two comments while perusing the base linalg code. Related statement in #23914, where they were introduced:

Also marked a few even more invalid places where managed pointer is passed to unsafe_wrap (the fix for those will be much more involved).

Not terribly reassuring seeing this in production code, so I figured it deserved an open issue.

Issue 2:
At our centre we've just had a talk about Julia, and many of our users are

interested in starting to experiment with using Julia for some of their

work.

I'd love to install Julia system-wide on our cluster to help them get

started (especially since we try to link it with our local fast numerical

libraries), but I'd like to update the package every now and then without

changing it from under them.

We usually do this with modules, creating new installation directories for

each "version", and therein lies a bit of a stumbling block; I'd like to be

able to describe which version they're using in a more consistent way than

the build date, or, worse, something like

27bbad6.

Is there any near term plans to start having tags for release numbers?
Issue 1:
I can see support for users and different roles in superset. But What I need is, Consider, I have a set of dashboards for finance department. Only that department's members can view the dashboards and for any other departments, it should be restricted.

I know we can restrict the dashboard access very easily, But One solution I need is to create a group with all the members I have and to add that group as a single user, while creating Rules and Users in Apache Superset.

One alternate solution is to create a Role as we want and add one or more users easily.

But adding multiple number of users to multiple number of Roles is pretty difficult (Based on which department they belong to). So that the idea is to create a group for each group of Users and sharing dashboard to that group.

Issue 2:
I would like to visual only the raw data WITHOUT the need of apply any kind of aggreation, as the data from the table is already pre-computed aggreated metric values.

Superset version

0.26.3

Expected results

There shouldn't be aggregation enforced for a metric. There should be an option to display the raw metric WITHOUT any aggreation function

Actual results

User must select one of six aggreation available in order to visualize data.

Steps to reproduce

Go to Charts

Create a new Timeseries Line Chart

Under Query section

Configure metric
Issue 1:
Steps to Reproduce

Create a normal Flutter project with the Atom creator project

Remove the internet permission in the manifest

Run the app

Flutter Doctor

[✓] Flutter (on Linux, channel alpha)
• Flutter at /home/kleak/flutter
• Framework revision 9a0a0d9903 (13 days ago), engine revision f8d80c4617

[✓] Android toolchain - develop for Android devices (Android SDK 24.0.1)
• Android SDK at /home/kleak/Android/Sdk
• Platform android-24, build-tools 24.0.1
• Java(TM) SE Runtime Environment (build 1.8.0_101-b13)

[✓] Atom - a lightweight development environment for Flutter
• flutter plugin version 0.2.4
• dartlang plugin version 0.6.38

Logs and Crash Reports

vm-service: Error: Unhandled exception:
SocketException: Failed to create server socket (OS Error: Permission denied, errno = 13), address = 127.0.0.1, port = 0
#0 _NativeSocket.bind.<anonymous closure> (dart:io-patch/socket_patch.dart:511)
#1 _RootZone.runUnary (dart:async/zone.dart:1404)
#2 _FutureListener.handleValue (dart:async/future_impl.dart:131)
#3 _Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:637)
#4 _Future._propagateToListeners (dart:async/future_impl.dart:667)
#5 _Future._completeWithValue (dart:async/future_impl.dart:477)
#6 _Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:528)
#7 _microtaskLoop (dart:async/schedule_microtask.dart:41)
#8 _startMicrotaskLoop (dart:async/schedule_microtask.dart:50)
#9 _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:96)
#10 _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:149)

Issue 2:
If your AndroidManifest.xml is missing this line:

<uses-permission android:name="android.permission.INTERNET"/>

...then when we try to hook up the observatory port we will get an error 13 (permission denied).

We should catch this case and explain what to do about it.
Issue 1:
Issue Type:

Problem with SSL verification

Ansible Version:

ansible 1.5.2

installed via pip

Environment:

Ubuntu 12.04

Summary:

When I try to fetch any URL via https I get SSL verification error

Steps To Reproduce:

ansible -i 127.0.0.1, "*" -m 'get_url' -a'url="https://www.postgresql.org" dest=/tmp/x'

##### Expected Results:

Downloaded file.

##### Actual Results:

127.0.0.1 | FAILED >> {
"failed": true,
"msg": "failed to validate the SSL certificate for www.postgresql.org:443. You can use validate_certs=no, however this is unsafe and not recommended '/usr/share/ca-certificates/cacert.org/cacert.org.crt'"
}

I am on ubuntu 12.04. Script found some certs here /usr/share/ca-certificates/cacert.org/cacert.org.crt and failed to verify postgresql certificate. Any ideas why?

Issue 2:
Issue Type:

Bug Report

Ansible Version:

ansible 1.5.2

Environment:

Ubuntu 12.04

Summary:

SSL verification fails when attempting to use the hipchat module

Steps To Reproduce:

Use the hipchat module and attempt to send a message.

Expected Results:

No errors, message gets sent.

Actual Results:

msg: failed to validate the SSL certificate for api.hipchat.com:443. You can use validate_certs=no, however this is unsafe and not recommended

Ansible v1.5.2 appears to have enabled SSL server certificate verification. If I attempt to use the HipChat module, it fails due to an unclear error message:

msg: failed to validate the SSL certificate for api.hipchat.com:443. You can use validate_certs=no, however this is unsafe and not recommended

It appears that Ansible hard-codes the Certificate Authority bundle based on the current platform and distribution. For Ubuntu, the file is hard-coded to /usr/share/ca-certificates/cacert.org/cacert.org.crt.

Running update-ca-certificates on Ubuntu does not fix the problem because this generates a bundle in /etc/ssl/certs/ca-certificates.crt.

I see a few improvements:

Display the attempted filename in the error message--this would help clarify what went wrong.

Allow configuration of the bundle file in the Ansible configuration (similar to curl's --cacert parameter).

curl also allows a --capath directory to search for certificates within this directory. Support this functionality.
Issue 1:
See https://github.com/elastic/elasticsearch/blob/master/core/src/main/java/org/elasticsearch/cluster/metadata/MetaData.java#L1150. If an element is not recognized in a cluster state, it is simply ignored.

Issue 2:
If a plugin adds custom cluster state parts and the plugin isn't installed on all nodes then it could cause custom metadata to be removed by a node just by reading it.

Brought up while reviewing #21243.
Issue 1:
No matter in which line is dot, code is dislocated after formatting:

My environment:

Microsoft Visual Studio Community 2013 (12.0.31101.00 Update 4)

TypeScript 1.5.40427.1

Issue 2:
Before we would have:

var doSomethingThatReturnsAPromise: any;
this.doSomethingThatReturnsAPromise()
.then(() => {
// more code
})
.then(() => {
// even more code
});

Now we have

var doSomethingThatReturnsAPromise: any;
this.doSomethingThatReturnsAPromise()
.then(() => {
// more code
})
.then(() => {
// even more code
});

Raised from SO
Issue 1:
📝 Performance Stats on Taskbar

This feature is On/Off, with ability to customize what kind of stats are to be displayed in the taskbar.

To have the stats on taskbar, but not on the main screen is to SAVE screen estate, also user can rapidly take a glimpse of the computer's stats without need to move the existing windows or minimize windows (i.e. Issue with RainMeter, Sidebar Diagnostics).

Great examples of this include:

(1) XMeter(https://entropy6.com/xmeters/)

(2) OSS - TrafficMonitor (https://github.com/zhongyang219/TrafficMonitor/blob/master/README_en-us.md)

Similar MacOS product:

(1) iStats

If you'd like to see this feature implemented, add a 👍 reaction to this post.

Issue 2:
Issue 1:
Version

2.3.3

Reproduction link

http://plnkr.co/edit/AiNse4SDOQIiH1RlnKoE?p=preview

Steps to reproduce

Make a Polymer element in a separate file

Import the Polymer element into a main page that makes a new instance of Vue

Run the page in different browsers (particularly, Chrome and one other), notice the number of alert boxes, as well as the Render Order count, in different browsers.

What is expected?

At the end of the page loading, every Polymer element should only have one copy of the template DOM structure within the custom element (same for Shadow DOM or Shady DOM)

What is actually happening?

In Chrome, regardless of which version of Polymer and which DOM structure used, the template structure was rendered twice. This problem is particular visible when using Shady DOM in Polymer v1, which will actually display the element structure twice.

I have traced the Vue code, and identified that the trigger is the call to document.createElement('tag'). For FireFox, IE and Edge, this call (in this example) goes into polyfill, which definitely has different behavior when comparing to the native function inside Chrome.

It looks like, at the point of , Chrome has already created the template structure, and then later on when Vue starts to attach the bindings, it loops through the entire template structure within the Polymer element, and calls document.createElement once every inner element within the template. This may be one of the possible causes making the whole DOM repeated.

This is particularly visible when using Polymer v1 with Shady DOM, which makes users actually see the duplicated elements; for other combinations (either using Shadow DOM or using Polymer v2), the repeated structure would seem to be removed from DOM. Yet, by noticing the alert box I have hooked up in the example, it is clear that the element got created twice each time it is used. In the example I provided, if you add a line saying <script>Polymer={dom:'shadow'}</script>, it will force Polymer v1 to use Shadow DOM. At that moment, the repeating DOM will disappear, but the alert box still comes up 4 times instead of 2, and Render Order # definitely shows the artifact.

The reason I posted the behavior here in the Vue project is that, IMO, looping through the inner template structure within the Polymer element, and calling document.createElement to every single inner element, may not be the optimal way; yet, to be honest, I am merely tracing and describing as much observation I have made as possible. I am not a UI professional, and I am happy to leave this issue to your judgment. Thank you very much for your attention.

Issue 2:
Version

2.5.21

Reproduction link

https://codepen.io/anon/pen/gZGPPL

Steps to reproduce

1.change the components order

2.console.log the $children

What is expected?

should change the $children order corretly

What is actually happening?

$children order not changed
Issue 1:
If client http header contain Expect: 100-continue

client post multipart/form-data Sometimes there will be

"multipart: Part Read: WSARecv tcp ..138.250:80: i/o timeout" ParseMultipartForm(102400) -> /mime/multipart/multipart.go 239

This is immediately returned error.

Did not arrive ReadTimeout

The same service, the same machine, open the IIS running do not have this problem.

Issue 2:
The http Client should probably support Expect: 100-continue. The server does.

It does introduce a new round-trip, though, so we should probably only send it when the
data size exceeds some threshold. Probably the same threshold we use for consuming
request bodies when a handler doesn't (maxPostHandlerReadBytes).

I think we could see if we know the size of the request body (just as NewRequest does,
checking for a few known types), but if the Body is non-nil and the ContentLength is
<=0 (unknown), we instead slurp up the Body into a bytes.Buffer to see if it's >=
someThreshold. If so, we replace the Body with a io.MultiReader(slurped, rest) and
proceed to do a 100-continue. If not, we blast it away HTTP/1.0-style.
Issue 1:
The content of a popover is invisible when the popover is on a .input-append input node.

I think it's because the font-size on .input-append is set to 0.

.input-append, .input-prepend {
font-size: 0;
white-space: nowrap;
}

This issue is similar to this issue with datepicker

Issue 2:
There was a fix made in 2.2.2 to address 0 font size for popovers within a btn group:

#5939

I don't think the fix was comprehensive as it still happens in other situations. Here's an example within an input-append form element:

http://jsfiddle.net/YUS87/