WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Describe the bug

Use MSSQL, the password contains @, the error shows Failed to execute migrations to revision 12685bc9edf4. (pyodbc.OperationalError) ('HYT00', '[HYT00] [Microsoft][ODBC Driver 17 for SQL Server]Login timeout expired (0) (SQLDriverConnect)') when using sqlalchemy; while the connection is successful by using sql client.

To Reproduce

Configure password contains @

Error

After checked recent commits, the issue should be introduced by this commit: 2ab6755#diff-f54587482b075b6a76ecbf10620b5183d65f9449639606d8fa88a103d88a95b6L705-R705

# Log output.
Failed to execute migrations to revision 12685bc9edf4. (pyodbc.OperationalError) ('HYT00', '[HYT00] [Microsoft][ODBC Driver 17 for SQL Server]Login timeout expired (0) (SQLDriverConnect)')

Versions.

OS: ubuntu 20.04

Python: 3.7.4

SQLAlchemy: 1.4.18

Database: MSSQL

DBAPI: pyodbc

Additional context

E.g. use password Abcdef1@, the server parameter is @, while password is Abcdef1

Have a nice day!

Issue 2:
Describe the bug

When a password contains a @ character. Sqlalchemy with a string url cannot connect to the database.

I greatly suspect that it was induced by #6482.

Was working fine in 1.4.15.

To Reproduce

url = (
"mssql+pyodbc://"
"SA:P@my_password@127.0.0.1:1433/master"
"?driver=ODBC Driver 17 for SQL Server"
)

Error

``

sqlalchemy.exc.OperationalError: (pyodbc.OperationalError) ('HYT00', '[HYT00] [Microsoft][ODBC Driver 17 for SQL Server]Login timeout expired (0) (SQLDriverConnect)')

``

Versions.

OS:

Python: 3.8

SQLAlchemy: 1.4.17

Database: mssql

DBAPI: pyodbc

Have a nice day!
Issue 1:
This is JS-only API and causes compiler warnings in Dart.

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 compiling the project that has imports from outside of the root directory (shared/components/*), the path in the ngfactory file is targeting the generated ngfactory of the import in the source directory of the import, instead of the directory it's been compiled to.

Expected behavior

The import paths should be adjusted in order to properly target the compiled files.

Minimal reproduction of the problem with instructions

https://github.com/mug3n/bug-report-ngc

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

It's not working as intended, as the files are being compiled, but being looked for in wrong locations.

Please tell us about your environment:

Fedora release 23 (Twenty Three), WebStorm.

The same can be reproduced on OS X

Angular version: 2.0.1

Browser: [all]

Language: [TypeScript X.X]

Node (for AoT issues): v5.10.1
Issue 1:
I can't explain this one. Here's a test case I've been able to whittle down from a bigger class:

'use strict';

const Thing = {

x() {
return <Dingbat uid={'hello'}/>;
},

y() {
for (let row of this.rows) {
let uid = 42;
console.log(uid);
}
}
};

The generated code (unrelated parts elided):

for (var _iterator = this.rows[Symbol.iterator](), _step; !(_iteratorNormalCompletion = (_step = _iterator.next()).done); _iteratorNormalCompletion = true) {
var row = _step.value;
var _uid = 42;
console.log(uid);
}

Note how _uid is assigned, but it's accessed as uid. If I change the JSX line to something else (eg., <Dingbat bing={'hello'}/>;) the problem goes away. Seems to me like the JSX scope is leaking into the parallel function scope, and somehow breaking it. I've not been able to reproduce the effect in any other way; replacing the JSX with plain JS code stops the bug from happening, for example.

However, this bug is oddly similar to this issue. Same underlying cause, perhaps?

Issue 2:
With the code:

function foo() {
let input = ['a', 'b', 'c']
let output = {}

for (let c of input) {
let name = c
output[name] = name
}

return output
}

The output from babel is:

'use strict';

function foo() {
var input = ['a', 'b', 'c'];
var output = {};

var _iteratorNormalCompletion = true;
var _didIteratorError = false;
var _iteratorError = undefined;

try {
for (var _iterator = input[Symbol.iterator](), _step; !(_iteratorNormalCompletion = (_step = _iterator.next()).done); _iteratorNormalCompletion = true) {
var c = _step.value;

var _name = c;
output[name] = name;
}
} catch (err) {
_didIteratorError = true;
_iteratorError = err;
} finally {
try {
if (!_iteratorNormalCompletion && _iterator['return']) {
_iterator['return']();
}
} finally {
if (_didIteratorError) {
throw _iteratorError;
}
}
}

return output;
}

Specifically, the problematic generated code is here:

var _name = c;
output[name] = name;

It should be output[_name] = _name;

This works fine in a regular for loop, and works fine if name is declared with var
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

Putting styles with a /deep/ selector bleeds into sibling components.

When I have a component on one route with a style of the following:

/deep/ app-my-header {
header {
background-color: yellow;
}
}

If I then navigate to another component (not a child component) the styles from the sibling route still persist on the app-my-header.

Expected behavior

Styles should not bleed outside of their component even when using the /deep/ selector.

Minimal reproduction of the problem with instructions

https://github.com/zackarychapple/ng-css-encapsulation

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

We have styles to a header that changes as we navigate through the application, this bleeding causes breaking changes across route events.

Please tell us about your environment:

OSX, IntelliJ, Node

Angular version: 2.0.X

verified in 2.3.1 and 2.4.1

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 ]

tested in Chrome

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

Typescript

Issue 2:
When there are sibling components, one with ViewEncapsulation.Native and the other with ViewEncapsulation.None, the styles that any component stylings are being appended to the shadow root of the one component set to Native.

Plunker: http://plnkr.co/edit/huN8xe0S7xH5CUw4B2P6?p=preview

Updated Stackblitz: https://stackblitz.com/edit/angular-issue-5059?file=src/app/app.component.html

A component set to Native should not adopt the rest of the CSS rules from non-Native components. In the screenshot of the rendered DOM, the last three style elements are appended to the end of the shadow root, but they are actually declared in the other two components which are set to None and Emulated modes.

If all three components are set to Native, then the rules are applied only to the local component, but when they are mixed the rules bleed over into Native (but don't bleed out of Native).
Issue 1:
As discussed here it is possible for Java jar files (zip formatted archives) to include a prefixed bash script that allows them to act like fully executable applications. Many existing tools (java -jar, unzip etc) support zip files with additional prefixed bytes.

Unfortunately go currently doesn't support the reading of such archives which causes problems for the Cloud Foundry cli tool.

Issue 2:
by zheganin@enaza.ru:

runtime package fails to pass test. Actually, this is 100% reprodicible meaning it
fails, but reasons can differ each time (I just hit all.bash every time):
- can just silently "FAIL" without stating a reason, prior to
"GOMAXPROCS=2" phase
- can state "fatal error: unexpected signal during runtime execution" as a
reason on "GOMAXPROCS=2" phase
- can state "panic: runtime error: invalid memory address or nil pointer
dereference" as a reason

OS: Solaris 11.1 amd64
Compiler:

Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/gcc/4.5/lib/gcc/i386-pc-solaris2.11/4.5.2/lto-wrapper
Target: i386-pc-solaris2.11
Configured with:
/builds/hudson/workspace/nightly-update/build/i386/components/gcc45/gcc-4.5.2/configure
CC=/ws/on11update-tools/SUNWspro/sunstudio12.1/bin/cc
CXX=/ws/on11update-tools/SUNWspro/sunstudio12.1/bin/CC --prefix=/usr/gcc/4.5
--mandir=/usr/gcc/4.5/share/man --bindir=/usr/gcc/4.5/bin --libdir=/usr/gcc/4.5/lib
--sbindir=/usr/gcc/4.5/sbin --infodir=/usr/gcc/4.5/share/info
--libexecdir=/usr/gcc/4.5/lib --enable-languages=c,c++,fortran,objc --enable-shared
--with-gmp-include=/usr/include/gmp --with-mpfr-include=/usr/include/mpfr
--without-gnu-ld --with-ld=/usr/bin/ld --with-gnu-as --with-as=/usr/gnu/bin/as
CFLAGS='-g -O2 '
Thread model: posix
gcc version 4.5.2 (GCC)

Session logs attached.

Attachments:

session01.log (16448 bytes)

session02.log (34838 bytes)
Issue 1:
Will be great if we can duplicate/divide terminal screen like tmux or cmdr using some key shortcuts like Ctrl + Alt + H for horizontal division or Ctrl + Alt + V for vertical, and the new terminal need open in the same path of the previous terminal if we are in c:\Users the new terminal need open in the same place, if we are in Linux using /home/ the new need do the same thing and open in same /home directory.

Issue 2:
I'm pretty new to using linux, and don't understand much, but my issue is the following:

Every time I use the linux subsystem in windows 10, I want to work in the same directory, where my repos are located. I want to switch to the new terminal app, but every time I open a new linux terminal, it starts out in my windows system 32 directory, whereas I would like it to start where my repositories are located. Using the terminal that's provided with the ubuntu for windows app, I simply made a new shortcut, that starts in my desired location. Any way to do this with the new app?

tldr: start new linux terminal at a specific directory instead of /mnt/c/WINDOWS/system32

sorry if this is the wrong place to ask this.

The json offers the option to specify a starting directory for both powershell and cmd. If possible, it would be awesome to have that same option for a new bash instance.
Issue 1:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): "static pod orphaned" and "static pod register-node"

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Kubernetes version (use kubectl version): v1.5.0-beta.2

Environment:

Cloud provider or hardware configuration: azure

OS (e.g. from /etc/os-release): CentOS 7

Kernel (e.g. uname -a): Linux master-1 4.8.11-1.el7.elrepo.x86_64 #1 SMP Sat Nov 26 11:13:42 EST 2016 x86_64 x86_64 x86_64 GNU/Linux

Install tools: kargo (+custom changes)

Others:

What happened:

The controller-manager logs repeatedly show that it deleted orphaned pods which belong to the static pods of kubelets which have "--register-node=false" set:

I1206 11:31:14.941598 1 gc_controller.go:184] Found orphaned Pod kube-controller-manager-master-1 assigned to the Node master-1. Deleting.
I1206 11:31:14.941605 1 gc_controller.go:71] PodGC is force deleting Pod: kube-system:kube-controller-manager-master-1
I1206 11:31:15.425141 1 gc_controller.go:188] Forced deletion of orphaned Pod kube-controller-manager-master-1 succeeded

The pods/containers are not really deleted. It looks like only the "mirror" PODs are deleted and later readded. But I'm not sure about this as I did not dig into mirror PODs that deep.

The POD status seems to be jumping from "Running" to "Pending" and back after every few seconds.

What you expected to happen:

I'd expect that the gc_controller would ignore static/mirror PODs in this case. I'm not sure how GC should work here in case the source kubelet dies as we don't have node status here.

How to reproduce it (as minimally and precisely as possible):

Run a kubelet with "--register-node=false" and add some static PODs/manifests. kargo for example does this at the moment.

Anything else do we need to know:

Issue 2:
Forked from #23684 ...

There are debate over that pr on system automatically publishs the fields in NodeStatus.NodeSystemInfo. I don't fully understand the concern, but in my opinion, the advantage of publishing those labels will help debugging and analyzing the issues related to different OSImage, RuntimeVersion, KubeletVersion, etc. especially for a large cluster (> 100 nodes).

cc/ @bgrant0607 @thockin @davidopp @vishh
Issue 1:
Summary of the new feature/enhancement

The ability to be able to search the web using PowerToys Run

Proposed technical implementation details (optional)

It would be nice if there was an option to enable searching the web using PowerToys Run.

Preferably, make the browser selectable and same with search engine.

Issue 2:
Summary of the new feature/enhancement

I want to be able to start a web search from the launcher.

Ideally, I'd type bing power toys and it would navigate to https://www.bing.com/search?q=power+toys in my default browser.

google power toys would go to the equivalent.

The ability to specify the keyword/search engine to use and the domain it goes to would also be necessary. Not only would this enable supporting other search engines, but it would also allow for people to adjust for different TLD versions of search engines.

This would be similar to functionality that used to be available in Enso launcher.

Proposed technical implementation details (optional)

This would presumably require some settings for determining which words are identified as initiating the search and the URL to submit the query to.

This could also be the base for similar functionality where a keyword could launch an app and pass other values as command-line arguments. Without additional arguments, this could also serve as a way to create aliases for apps so they could be launched with a small number of keystrokes.

crutkas: possible solution to this issue in #10619. It defers to default browser + user's search engine. Lets PT Run be generic
Issue 1:
I'd like to be able to host a next.js app on it's own base path (e.g. /some/base/path/ - on a configurable http proxy). This is primarily for use with JupyterHub to run as a separate service (on e.g. /services/nextApp). I've gotten everything to work for the express app (that uses next handlers underneath) as well as the frontend's handling of the paths (the req.params -> query -> page/component are awesome with next.js).

The only issue I'm running into is that _next is assumed to be at the absolute path of /_next when it needs to be able to be served at /some/base/path/_next.

const app = next({ dev, baseURL: '/asdf' });

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

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

Expected Behavior

I'd expect sourcemaps of a basic module to enable breakpoint selection on all lines, except those clearly represented differently through transpilation.

Current Behavior

A basic component is not debuggable with sourcemaps: clicking on a line to set a breakpoint does not set a breakpoint at that line.

Steps to Reproduce (for bugs)

Example: https://github.com/tmcw/next-sourcemap-breakage-example

Single page with the source:

import {Component} from "react";
export default class Button extends Component {
render() {
function foo() {
console.log(1);
}
return <button onClick={foo}>hi</button>
}
};

Setting a breakpoint on the line

console.log(1);

Is not possible:

Context

This makes debugging applications quite difficult.

Your Environment

Tech
Version

next
3.2.2

node
8.4.0

OS
macOS 10.12.6

browser
Google Chrome 61.0.3163.100
Issue 1:
Hi! I am writing some site (taxi with google maps in real time for our city), and I was created modal with form (for selecting taxi filters and your coordinates), and height of this modal was bigger, than height of my smartphone screen. I was tried to scroll modal down, to select other filters, and modal just was not scrollable. I tried to open and scroll modal from Bootstrap docs, and it too was not scrollable. I tried same on Android 4, and it worked normal. Can you fix opened modal scrolling for Android 2?

P.S. Sorry for my bad English.

Issue 2:
This issue might already exist however after a bit of searching I couldn't find anything. I apologize in advance for that.

Problem:

If the content of the modal window is bigger than the screen, you can't scroll and see the bottom of your modal window on certain platforms.

Concerned platforms (what I've tested so far):

Android 2.2 (Nexus - Native Browser), BB7 (Black Berry Bold - Native browser)

Solution:

.modal-open has oveflow: hidden + .modal has position: fixed;

The body can't overflow thus the user can't see the full modal.

I propose to inject a media query (targeting stuff below 780px) that replace overflow: hidden by overflow: auto and position: fixed by position: absolute. Beyond 780px normal behaviour, nothing to be worry about.

May have to remove property such as bottom: 0; to have something that scroll properly.

Thoughts?

Charles
Issue 1:
What steps will reproduce the problem?
1. install sdl (i used macports)
2. install go-sdl (github.com/banthar/Go-SDL). you can't use goinstall, and each
makefile needs to be tweaked to include the following line:
CGO_CFLAGS:=`pkg-config --cflags sdl | sed 's:\(-I[^ ]*\)/SDL:\1:'`)
3. build and run Go-SDL/test/test

this gives the error:
libcgo: could not obtain pthread_keys
wanted 0x108 and 0x109
got 0x10b 0x10c 0x10d 0x10e 0x10f 0x110 0x111 0x112 0x113 0x114 0x115 0x116 0x117
0x118 0x119 0x11a

it looks like libsdl has grabbed too many thread keys already
before libcgo gets a look in. perhaps 0x108 and 0x109 should be
considerably higher numbers.

and indeed, when i change my local repository to use 0x128 and 0x129 (0x4e8)
things get much further (still doesn't work, but that's another issue)

darwin 386 ad738cffc309+ tip

Issue 2:
What steps will reproduce the problem?
1. sudo apt-get install mongodb-server
2. go get -u launchpad.net/juju-core/...
3. go test launchpad.net/juju-core/cmd/jujud

What is the expected output? What do you see instead?

% go test launchpad.net/juju-core/cmd/jujud

panic: runtime error: call of nil func value
[signal 0xb code=0x1 addr=0x0 pc=0x0]

goroutine 16 [running]:
runtime.panic(0x9182e0, 0xdb281c)
/home/dfc/go/src/pkg/runtime/panic.c:279 +0xf5
strconv.init()
/home/dfc/go/src/pkg/strconv/atoi.go:10 +0x43
testing.init()
/home/dfc/go/src/pkg/testing/testing.go:656 +0x43
launchpad.net/juju-core/cmd/jujud.init()
/home/dfc/src/launchpad.net/juju-core/cmd/jujud/upgrade_test.go:138 +0x51
main.init()
/tmp/go-build380384730/launchpad.net/juju-core/cmd/jujud/_test/_testmain.go:50 +0x3b

goroutine 17 [runnable]:
runtime.MHeap_Scavenger()
/home/dfc/go/src/pkg/runtime/mheap.c:507
runtime.goexit()
/home/dfc/go/src/pkg/runtime/proc.c:1430
FAIL launchpad.net/juju-core/cmd/jujud 0.004s

Please use labels and text to provide additional information.

% uname -a
Linux lucky 3.11.0-19-generic #33-Ubuntu SMP Tue Mar 11 18:48:34 UTC 2014 x86_64 x86_64
x86_64 GNU/Linux
% go version
go version devel +94d84d24086b Wed Apr 09 18:23:53 2014 -0700 + linux/amd64
Issue 1:
Bug report

When unit testing a utility function that needs access to the publicRuntimeConfig with jest, it throws error Cannot read property 'publicRuntimeConfig' of undefined

Describe the bug

For example if i am testing a file that has Contentful stuff in it, and the access token those kind of stuff comes from publicRuntimeConfig, then the test won't past and shows above error.

To Reproduce

// next.config.js

module.exports = () => {
return {
publicRuntimeConfig: {
accessToken: '1234565',
}
};
};

// util.js

import getConfig from 'next/config'
const { publicRuntimeConfig } = getConfig()
const client = createClient({
accessToken: publicRuntimeConfig.accessToken
})
function mathCaculation(){
return 1+1
}

util.test.js

expect(mathCaculation()).toBe(2)

Cannot read property 'publicRuntimeConfig' of undefined

System information

"next": "^7.0.2",

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

Expected Behavior

Steps to Reproduce (for bugs)

next.config.js

module.exports = (phase, { defaultConfig }) => {
return {
publicRuntimeConfig: {
defaultEnvironmentSettings: 'test',
},
webpack: (config, { buildId, dev, isServer, defaultLoaders }) => {
// XXX https://github.com/evanw/node-source-map-support/issues/155
config.node = {
fs: 'empty',
module: 'empty',
};
return config;
},
};
};

page

const { publicRuntimeConfig } = getConfig();
const { groupSettings, url } = this.props;
const schoolName = url.query.schoolName;
console.log('publicRuntimeConfig', publicRuntimeConfig) // publicRuntimeConfig undefined
console.log('getConfig()', getConfig()) // getConfig() serverRuntimeConfig:{}, publicRuntimeConfig: undefined

Context

publicRuntimeConfig is undefined

This only happens when I use NODE_ENV staging, it works fine in development mode. (I haven't tested against production env)

Note that my staging environment is hosted on AWS lambda, but it's maybe not related to the issue.