WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Hello, thanks for sharing your great work.

Summary

We need to sign request before they are sent, that is : add a header with an ECDSA signature calculated with full request URL (including parameters) and body, to ensure they are not modified when they reach the server.

In order to verify the signature, server software needs to rebuild data used to calculate the signature, using received request. Hence client (which uses axios and redux-axios-middleware) must sign with actual request data, which leads us in following issue : final url with querystring isn't built before request object construct (here for xhr :

axios/lib/adapters/xhr.js

Line 45
in
0b3db5d

request.open(config.method.toUpperCase(), buildURL(config.url, config.params, config.paramsSerializer), true);

)

As for now, I see two options to achieve this, both unsatisfying :

pass a custom paramSerializer, build the signature in an interceptor using it, and let axios rebuild the actual request url. Problem here is that url is built 2 times, leading to potential differences, not to mention unnecessary runtime overhead.

write a whole custom adapter, which handles the signing stuff, which would involve a lot of code duplication since we cannot easily access to axios' core, helpers & utils from outside the lib.

Ideal situation would be an access to final url at interceptor's level (or in transformers ?).

Do you see a better way to achieve this that I would have missed ?

Context

axios version: v0.18.0

Environment: whatever

Issue 2:
Describe the bug

getting this error from the definitions via yarn2.

➤ YN0000: [@bb/common-framework]: ../../../../../.yarn/cache/axios-npm-0.20.0-535d9e0086-6cf2e96317.zip/node_modules/axios/index.d.ts(63,40): error TS2304: Cannot find name 'ProgressEvent'.

this is from

└─ axios@npm:0.20.0
├─ Version: 0.20.0
│
└─ Dependencies
└─ follow-redirects@npm:^1.10.0 → npm:1.13.0

doesn't happen if I use 0.19.2. I don't have any usage of ProgressEvent myself.

To Reproduce

I suspect putting this in a typescript file, and built with yarn2 is enough, it might actually be a bug in axios-logger

import { AxiosLogger } from '@new10com/axios-logger';

Expected behavior

A clear and concise description of what you expected to happen.

Environment

├─ @bb/common-framework@workspace:ts/lib/common/packages/framework
│ └─ @new10com/axios-logger@npm:0.1.1 (via npm:^0.1.1)
│ └─ axios@npm:0.19.2 (via npm:^0.19)
│

> node --version # services -> feature/RS2-1243-logging $ — » +
v12.18.3
> yarn :g:tsc --version # services -> feature/RS2-1243-logging $ — » + RC=1
Version 4.0.3

Additional context/Screenshots

Add any other context about the problem here. If applicable, add screenshots to help explain.
Issue 1:
I know that mirrors is blocked now because it causes the generated packages to be very large.

However, on the long term, it should remain a goal to find a solution for this. Many libraries use mirrors so not being able to use mirrors for Flutter apps will make the framework a lot less powerful.

The trade-off between large package sizes and using mirrors should be left to the user. A possible solution might be to use an explicit --allow-mirrors flag. But of course the ultimate solution should be to find a way to use mirrors without blowing up package sizes.

Java has reflection and Objective-C has Runtime Reference, so why would Flutter not have a reflection system?

Issue 2:
When using firebase_ml_vision on IOS I receive an error for Firebase Auth.

On android I receive an output that no faces were detected no matter if I use portrait or landscape.

The output is:

W/DynamiteModule(14227): Local module descriptor class for com.google.android.gms.vision.dynamite.face not found.
I/DynamiteModule(14227): Considering local module com.google.android.gms.vision.dynamite.face:0 and remote module com.google.android.gms.vision.dynamite.face:0
D/FaceNativeHandle(14227): Cannot load feature, fall back to load whole module.
W/DynamiteModule(14227): Local module descriptor class for com.google.android.gms.vision.dynamite not found.
I/DynamiteModule(14227): Considering local module com.google.android.gms.vision.dynamite:0 and remote module com.google.android.gms.vision.dynamite:1800
I/DynamiteModule(14227): Selected remote version of com.google.android.gms.vision.dynamite, version >= 1800
V/DynamiteModule(14227): Dynamite loader version >= 2, using loadModule2NoCrashUtils
I/Vision (14227): Loading library libmobile_vision_face.so
I/Vision (14227): libmobile_vision_face.so library load status: true

Flutter Doctor:

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v0.10.1-pre.25, on Mac OS X 10.13.6 17G65, locale en)
[✓] Android toolchain - develop for Android devices (Android SDK 28.0.0-rc2)
[✓] iOS toolchain - develop for iOS devices (Xcode 10.0)
[✓] Android Studio (version 3.2)
[✓] IntelliJ IDEA Community Edition (version 2018.1.4)
[✓] VS Code (version 1.27.2)
[✓] Connected device (3 available)

• No issues found!
Process finished with exit code 0
Issue 1:
I ran into this error trying to setup a clean installation of the bootstrap source for development:

npm ERR! peerinvalid The package grunt does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer grunt-banner@0.2.2 wants grunt@~0.4.1
npm ERR! peerinvalid Peer grunt-contrib-clean@0.5.0 wants grunt@~0.4.0
npm ERR! peerinvalid Peer grunt-contrib-concat@0.3.0 wants grunt@~0.4.0
npm ERR! peerinvalid Peer grunt-contrib-connect@0.6.0 wants grunt@~0.4.0
npm ERR! peerinvalid Peer grunt-contrib-copy@0.5.0 wants grunt@~0.4.0
npm ERR! peerinvalid Peer grunt-contrib-csslint@0.2.0 wants grunt@~0.4.0
npm ERR! peerinvalid Peer grunt-contrib-cssmin@0.7.0 wants grunt@~0.4.1
npm ERR! peerinvalid Peer grunt-contrib-jade@0.9.1 wants grunt@~0.4.1
npm ERR! peerinvalid Peer grunt-contrib-jshint@0.8.0 wants grunt@~0.4.0
npm ERR! peerinvalid Peer grunt-contrib-less@0.9.0 wants grunt@~0.4.0
npm ERR! peerinvalid Peer grunt-contrib-qunit@0.4.0 wants grunt@~0.4.0
npm ERR! peerinvalid Peer grunt-contrib-uglify@0.3.3 wants grunt@~0.4.0
npm ERR! peerinvalid Peer grunt-contrib-watch@0.5.3 wants grunt@~0.4.0
npm ERR! peerinvalid Peer grunt-csscomb@2.0.1 wants grunt@~0.4.2
npm ERR! peerinvalid Peer grunt-exec@0.4.3 wants grunt@~0.4
npm ERR! peerinvalid Peer grunt-html-validation@0.1.15 wants grunt@~0.4.1
npm ERR! peerinvalid Peer grunt-jekyll@0.4.2 wants grunt@~0.4.1
npm ERR! peerinvalid Peer grunt-jscs-checker@0.3.2 wants grunt@0.4.2
npm ERR! peerinvalid Peer grunt-saucelabs@5.0.1 wants grunt@~0.4.1
npm ERR! peerinvalid Peer grunt-sed@0.1.1 wants grunt@~0.4

npm ERR! System Linux 3.2.0-23-generic-pae
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! cwd /vagrant/bower_components/bootstrap
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! code EPEERINVALID
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /vagrant/bower_components/bootstrap/npm-debug.log
npm ERR! not ok code 0

I'm creating a fresh ubuntu vm with vagrant, using the script here: https://gist.github.com/davethegr8/10935832

Full output from the vagrant up command: https://gist.github.com/davethegr8/10936309

Issue 2:
Hi.

I am switching an old application that uses Prototype to jQuery and Bootstrap, but because of the amount of work it requires, I need to be able to make both coexist during the migration.

Here I have reproduced an issue I have:

http://jsfiddle.net/u6vWL/32/

Actually, the clearMenus() function triggers an "hide" event, and then jQuery try to call the corresponding "hide" function of the DOM Element. Because prototype have added an "hide" function, it is called.

See: http://api.jquery.com/trigger/

Note: For both plain objects and DOM objects other than window, if a triggered event

name matches the name of a property on the object, jQuery will attempt to invoke the

property as a method if no event handler calls event.preventDefault(). If this behavior is

not desired, use .triggerHandler() instead.

Fix:

Replace (in : clearMenus())

$parent.trigger(e = $.Event('hide.bs.dropdown', relatedTarget))

by:

$parent.triggerHandler(e = $.Event('hide.bs.dropdown', relatedTarget))
Issue 1:
On Windows, when Electron with Chromium61 is run, the path %HOMEDRIVE%%HOMEPATH%\AppData\Roaming\Electron\logs is created under the current directory.

This can likely be attributed to the following code:

electron/brightray/browser/browser_main_parts.cc

Lines 168 to 179
in
306b627

void OverrideAppLogsPath() {

#if defined(OS_WIN)

std::wstring app_name = base::UTF8ToWide(GetApplicationName());

std::wstring log_path = L"%HOMEDRIVE%%HOMEPATH%\\AppData\\Roaming\\";

std::wstring app_log_path = log_path + app_name + L"\\logs";

#else

std::string app_name = GetApplicationName();

std::string home_path = std::string(getenv("HOME"));

std::string app_log_path = home_path + "/.config/" + app_name + "/logs";

#endif

PathService::Override(DIR_APP_LOGS, base::FilePath(app_log_path));

}

I did not reproduce it with Electron 1.8.1, so I'm deducing that it has something to do with upgrade to Chromium 61 - possibly the function PathService::Override no longer expands environment variables.

Issue 2:
Electron version: 1.8.2-beta 1

Operating system: Windows 7

Expected behavior

Launching electron should not create a subfolder.

Actual behavior

Running electron creates a subfolder in the electron folder. The subfolder is named "%HOMEDRIVE%%HOMEPATH%" and contains subfolders AppData\Roaming\Electron\logs

I've not seen this behaviour in any previous version, and obviously %HOMEDRIVE%%HOMEPATH% are environnement variables names that should be expanded (hence the bug).

How to reproduce

Download electron-v1.8.2-beta.1-win32-x64.zip

Launch electron.exe

See the folder appearing
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

MockConnection isn't consistent with a real connection in its error handling. The real connection checks the response status and if it is okay. If the status is within 200 and 299 then it calls next on the observable, otherwise error. MockRespond always calls next. This means you have to explicitly check the status code in unit tests and call MockError

Expected behavior

MockRespond would fire an error if the response status is not okay. Therefore, I cannot see much need for MockError except if one requires to test the error handling method without creating a mock HTTP method maybe.

Minimal reproduction of the problem with instructions

Not sure this is 100% neccesary, will do if so. See this SO question for more info.

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

Better portrayal of a real HTTP connection in unit tests

Please tell us about your environment:

Ubuntu 15.0, Webstorm, @angular/http version 2.4.1

Angular version: 2.0.X

2.4.1

Browser:

all

Language: [all | TypeScript X.X | ES6/7 | ES5]

Typescript 2.1.4

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

Test Repo - https://github.com/mildfuzz/angular-mockError

I am unable to test predicted HTTP error responses. Mockbackend can either send a response with an error code (which my app treats as a successful response in the test environment, but as an error in real world)

I am unable to send status codes with an error response in my tests, so I can not test any error handling my application might implements.

Expected behavior

at least one of the defined test cases passes

Minimal reproduction of the problem with instructions

Test Repo - https://github.com/mildfuzz/angular-mockError

this is a re-opening of issue #7471, which was closed due to lack of repro steps.

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

To be able to test all responses

Please tell us about your environment:

OsX

Angular version: 2.0.X

Angular 2.1.0

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Chrome 54

Language: TypeScript 2.0.3

Node (for AoT issues): node --version = 6.9.1
Issue 1:
Challenge use-hex-code-to-mix-colors has an issue.

User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36.

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

code is correct but test run is not validating properly.

<style>
.red-text {
color: #FF0000;
}
.green-text {
color: #00FF00;
}
.dodger-blue-text {
color: #1E90FF;
}
.orange-text {
color: #FFA500;
}
</style>

<h1 class="red-text">I am red!</h1>

<h1 class="green-text">I am green!</h1>

<h1 class="dodger-blue-text">I am dodger blue!</h1>

<h1 class="orange-text">I am orange!</h1>

```

Issue 2:
Challenge use-hex-code-to-mix-colors has an issue.

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

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

<style>
.red-text {
color: #ff0000;
}
.green-text {
color: #00ff00;
}
.dodger-blue-text {
color: #1e90ff;
}
.orange-text {
color: #ffa500;
}
</style>

<h1 class="red-text">I am red!</h1>

<h1 class="green-text">I am green!</h1>

<h1 class="dodger-blue-text">I am dodger blue!</h1>

<h1 class="orange-text">I am orange!</h1>

```

Screenshot:
![image](https://cloud.githubusercontent.com/assets/3306170/18378269/47f34348-766c-11e6-8fb7-6e2da365ced7.png)
Issue 1:
References #7888

I have a below snippet:

<Fade in={this.state.scrollVisible}>
<ScrollTopButton />
</Fade>

Initially on load this.state.scrollVisible is false, but ScrollTopButton is visible anyway. After showing/hiding, it starts to work correctly, only initial load with in={false} is broken.

Adding mountOnEnter prop helps, but shouldn't be required.

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

Expected Behavior

Child of Fade should never be visible when in={false} on mount

Current Behavior

Use Fade component with in={false} - child will be rendered and visible while it shouldn't.

Steps to Reproduce (for bugs)

Open https://codesandbox.io/s/9ov57l1pv4

You can see that Shouldnt be visible on Load button is visible on load while it shouldn't

Click SHOW button, Shouldnt be visible on Load will still be there, another button mountOnEnter helps but shouldnt be necessery will show.

From now on, you can toggle hide/show, everything works fine, only point 1 is problematic.

Context

Your Environment

Tech
Version

Material-UI
1.0.0-beta.31

React
16.2.0

browser
any

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

How do i make sure the bottom navigation is always, well, at the bottom?

position: absolute;
bottom: 0;
width: 100%;

This works but when keyboard is open, it will push the view up.

Your Environment

Tech
Version

Material-UI
0.19.2

React
15.6.1

browser
Chrome V60
Issue 1:
Code Example

class Parent {
constructor() {
}
};

class Child extends Parent {
constructor() {
super();
}

scopedFunctionWithThis = () => {
this.name = {};
}
}

Save above snippet as a.js

Run babel --presets stage-0 a.js,

Error Message: SyntaxError: a.js: 'this' is not allowed before super() (This is an error on an internal node. Probably an internal error)

This is fine on babel repl however.

Environment:

node: v4.2.1

npm: 2.14.7

Packages: babel-core, es2015, stage0 are installed

Issue 2:
Issue originally made by @jgrund

Bug information

Babel version: 6.2.1

Node version: 4.2.4

npm version: 3.4.0

Options

--plugins transform-es2015-modules-umd

Input code

import * as foo from '../index.js';

Description

It appears that importing modules is broken with umd when working with node. The above input code generates:

(function (global, factory) {
if (typeof define === "function" && define.amd) {
define(['exports', '../index.js'], factory);
} else if (typeof exports !== "undefined") {
factory(exports, require('../index.js'));
} else {
var mod = {
exports: {}
};
factory(mod.exports, global.index);
global.tests = mod.exports;
}
})(this, function (exports) {
(function (global, factory) {
if (typeof define === "function" && define.amd) {
define(['../index.js'], factory);
} else if (typeof exports !== "undefined") {
factory();
} else {
var mod = {
exports: {}
};
factory(global.index);
global.tests = mod.exports;
}
})(this, function (_index) {
var foo = _interopRequireWildcard(_index);

function _interopRequireWildcard(obj) {
if (obj && obj.__esModule) {
return obj;
} else {
var newObj = {};

if (obj != null) {
for (var key in obj) {
if (Object.prototype.hasOwnProperty.call(obj, key)) newObj[key] = obj[key];
}
}

newObj.default = obj;
return newObj;
}
}
});
});

It seems like the require('../index.js') up top is never passed through to the inner calls. Because of this we end up with an object literal with an undefined default property.
Issue 1:
After updating lodash.TypeScript.DefinitelyTyped from nuget to version 2.3.3

I have two d.ts files in folder typings/lodash: 'lodash-3.10.d.ts' and 'lodash.d.ts'

After build I receive around 80 errors with content: Duplicate Identifier

Issue 2:
I tried using the latest stable version of tsc (typescript@latest = typescript@3.1.1). https://www.npmjs.com/package/typescript

I tried using the @types/react-native@0.57.0 package and had problems.

Mention the authors (see Definitions by: in index.d.ts) so they can respond.

Authors: @alloy, @huhuanming, @iRoachie, @Skn0tt, @timwangdev, @kamal, @nelyousfi, @alexdunne, @swissmanu, @bm-software, @tkrotoff, @a-tarasyuk, @mvdam, @Esemesek

Current typings produce very strange errors being used with typescript 3.1.1

I submit microsoft/TypeScript#27421 to typescript repo, but sure that DT also should track this issue. Main problem, that I can't create minimal example for this. And I can't personally understand why ts since 3.1 behave so strangely. It would be good if anyone can help with this.

Next is mostly duplication of info from microsoft/TypeScript#27421:

import React from 'react'
import { StyleSheet, Text } from 'react-native'

const s = StyleSheet.create({
didNotWork: {
fontSize: 16,
fontWeight: '900', // if we comment this line, errors gone
marginTop: 5, // if this line commented, errors also gone
},
work: {
fontSize: 18,
// fontWeight: '900', // when uncommented also work
},
})

export const sample1 = <Text style={s.work} />
export const sample2 = <Text style={s.didNotWork} />
// ^ this line generate error:
// index.tsx:17:30 - error TS2322: Type 'RegisteredStyle<{ fontSize: number; fontWeight: string; marginTop: number; }>' is not assignable to type 'StyleProp<TextStyle>'.
// Type 'RegisteredStyle<{ fontSize: number; fontWeight: string; marginTop: number; }>' is not assignable to type 'RecursiveArray<false | TextStyle | RegisteredStyle<TextStyle> | null | undefined>'.
// Property 'length' is missing in type 'Number & { __registeredStyleBrand: { fontSize: number; fontWeight: string; marginTop: number; }; }'.
// 17 export const sample2 = <Text style={s.didNotWork} />
// ~~~~~
// node_modules/@types/react-native/index.d.ts:907:5
// 907 style?: StyleProp<TextStyle>;
// ~~~~~
// The expected type comes from property 'style' which is declared here on type 'IntrinsicAttributes & IntrinsicClassAttributes<Text> & Readonly<{ children?: ReactNode; }> & Readonly<TextProps>'
export const sample3 = <Text style={{fontSize: 16, fontWeight: '900', marginTop: 5}} />

This sample shows the error. There is sandbox repo: https://github.com/vovkasm/rn-ts-3.1.1 (to reproduce, clone and npm install && npm test)

If I comment out fontWeight or marginTop style of didNotWork key, error dissapeared

If I add fontWeight to work key, error dissapeared

Why is this?
Issue 1:
These don't seem to be generally useful enough to merit a place in the stdlib (and thus putting the maintenance burden on the core team). Does anyone object to removing them?

Issue 2:
A placeholder text in the search field hints:

…, '?' for more options

so I've entered "?" in the search field and ended up on this page:

https://doc.rust-lang.org/std/?search=%3F

Oops! I've realised that you've meant pressing Shift+/ when text input isn't focused, but text input placeholder text is generally used as an example for the text input itself, so it confused me.

I suggest handling search for ? as a special case and displaying the help text too.

And perhaps even better solution would be to automatically display a search syntax cheatsheet below the search input when the input is focused. Splunk search has something like this (they call it search assistant).
Issue 1:
Code Sample, a copy-pastable example if possible

>>> index = pandas.to_timedelta([15e-7], unit="s")
>>> index[0].nanoseconds
0
>>> index[0].microseconds
2

Problem description

nanoseconds range input for to_timedelta function are rounded to microseconds.

Expected Output

>>> index = pandas.to_timedelta([15e-7], unit="s")
>>> index[0].nanoseconds
500
>>> index[0].microseconds
1

However this works fine:

>>> index = pandas.to_timedelta([1.5], unit="us")
>>> index[0].nanoseconds
500
>>> index[0].microseconds
1

So it seems to be something when se choose unit="s"

Output of pd.show_versions()

INSTALLED VERSIONS

commit: None

python: 3.6.3.final.0

python-bits: 64

OS: Windows

OS-release: 10

machine: AMD64

processor: Intel64 Family 6 Model 158 Stepping 9, GenuineIntel

byteorder: little

LC_ALL: None

LANG: None

LOCALE: None.None

pandas: 0.21.1

pytest: 3.4.0

pip: 9.0.1

setuptools: 38.4.0

Cython: 0.27.3

numpy: 1.13.3

scipy: 1.0.0

pyarrow: None

xarray: None

IPython: 6.2.1

sphinx: 1.6.6

patsy: None

dateutil: 2.6.1

pytz: 2017.2

blosc: None

bottleneck: None

tables: None

numexpr: None

feather: None

matplotlib: 2.1.1

openpyxl: 1.7.0

xlrd: None

xlwt: None

xlsxwriter: None

lxml: None

bs4: None

html5lib: 1.0.1

sqlalchemy: None

pymysql: None

psycopg2: None

jinja2: 2.10

s3fs: None

fastparquet: None

pandas_gbq: None

pandas_datareader: None

Issue 2:
I think this is rounding prematurely, though not entirely sure. Could also just be loss of precision when converting from a float -> int64.

In [12]: pd.to_datetime(1434743731.8770001,unit='s')
Out[12]: Timestamp('2015-06-19 19:55:31.877000')

In [13]: pd.to_datetime(1434743731.8770001,unit='s').value
Out[13]: 1434743731877000000

In [14]: (pd.Timestamp('2015-06-19 19:55:15.877000')+pd.Timedelta('1us')).value
Out[14]: 1434743715877001000
Issue 1:
Environment

Microsoft Windows [Version 10.0.18362.388]
Windows Terminal (Preview) 0.5.2762.0

tmux zsh (bullet-train theme) on Ubuntu WSL 18.04.3 LTS

Steps to reproduce

Install tmux or zsh and install a theme with color blocks (e.g. bullet-train theme) and configure a powerline-font in Windows Terminal.

Expected behavior

Font used for startup does not matter.

Actual behavior

If you start zsh/tmux with a Powerline font, all color blocks are shifted slighty:

If you start with a non-powerline font (e.g. Consolas) the blocks are the correct position:

Applying the powerline font after startup works as it should:

Using WSL without the Terminal App works (excpept lacking Emoji support)

Issue 2:
When using (Get-Host).PrivateData or (Get-Host).UI.RawUI to set Console Colors, they only exist when the console is opened.

Typed text is not bound to them nor do the properties of PrivateData or RawUI indicate that they are properly set. (Clear-Host, effectively removes all changes from the Console.)

Enabling "Use Legacy Console" restores expected function.

Not sure if there is something else I should be doing to make the color changes stick with the "Modern Console" or if this is a legitimate bug in the way console colors are applied to the Console.