WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I tried adding unique keys everywhere but no luck.

Probably this warning is due to an internal bug? Can you check that you assign unique keys in the iterator for table header contents?

Issue 2:
Summary

The title API of Tooltip is clashing with the title of StandardHtmlAttribute.

Expected Behavior

I expect no error will be thrown by TypeScript compiler when I assign a ReactNode to the title property of Tooltip.

Current Behavior

TypeScript compiler will throw an error saying that you cannot assign ReactNode to string.

Steps to Reproduce (for bugs)

Assume you are in a *.ts file and you are using TS compiler.

The following code will cause the TS compiler to throw an error.

const tooltipTitle = () => {
return (
<Typography type="body2" align="center">
{"Hey brother and sister"}
</Typography>
);
};

render () => {
return (
<Tooltip title={tooltipTitle()}> ... </Tooltip>
);
}

The error would look like the following :

message: 'Type '{ title: Element; placement: "bottom"; children: Element; }' is not assignable to type 'IntrinsicAttributes & HTMLAttributes<HTMLDivElement> & { disableTriggerFocus?: boolean; disableTr...'.
Type '{ title: Element; placement: "bottom"; children: Element; }' is not assignable to type 'HTMLAttributes<HTMLDivElement>'.
Types of property 'title' are incompatible.
Type 'Element' is not assignable to type 'string'.'
source: 'ts'

Why does this happen ?

Apparently, this is due to the clashing API for title in StandardHtmlAttribute and TooltipProperty :

// Tooltip.d.ts
export type TooltipProps = React.HTMLAttributes<HTMLDivElement> & {
...
title: React.ReactNode;
...
}

// index.d.ts
interface HTMLAttributes<T> extends DOMAttributes<T> {
....
// Standard HTML Attributes
title?: string;
....

Due to this reason, the TypeScript compiler is confused about the title property.

Proposed solution

Rename title property of Tooltip into tooltipBody .

Context

Typescript

Your Environment

Tech
Version

Material-UI
v1-beta

Tags

TypeScript, v1-beta
Issue 1:
ℹ Computer information

PowerToys version: 0.21.1

PowerToy Utility: n/a

Running PowerToys as Admin: no

Windows build number: 19042.450

📝 Provide detailed reproduction steps (if any)

open powertoys

maximise settings window

✔️ Expected result

titlebar is same size as uwp apps

❌ Actual result

titlebar is not the same size

📷 Screenshots

Are there any useful screenshots? WinKey+Shift+S and then just paste them directly into the form

PowerToys:

Feedback Hub (I tried to find a UWP app that follows the enable coloured title bars setting. lol you can see the bug where here is a massive gap next to the back button. and that missing top 1px border. rip testers.):

PowerToys, maximised:

Feedback Hub, maximised:

This happens to a bunch of win32 apps. The icons of the caption buttons are also positioned slightly differently between UWP apps and apps like Chromium, which doesn't have a pre-windows 10 sized titlebar when maximised. This may be a Project Reunion issue or a duplicate. Oh and I noticed that the navigation pane in powertoys is darker than other apps

Issue 2:
Summary of the new feature/enhancement

The current WPF runner app holds a XAML island with the NavigationView. Ideally the NavigationView would flow into the title bar, like most Windows 10 apps. For this, we'd need to create a custom WPF titlebar.

Proposed technical implementation details (optional)

Create a custom styling control that holds a custom minimize, maximize and close button. Background should be transparent so the NavView can flow to the top.

Left: UWP, right: WPF
Issue 1:
I have updated my app to the latest beta and now the typography of the title in the AppBar has changed. In this demos the title is shown correctly, but if you open them in the code sandbox the title looks like this.

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

Expected Behavior

The title should look like this:

Current Behavior

The title looks like this:

Steps to Reproduce (for bugs)

Codesandbox link here.

Simply insert any AppBar example of the demo site with a title.

Context

It's a bug.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.32

React
16.2.0

browser
64.0.3282.140

Issue 2:
When I build a project in production mode JSS generates non-deterministic class names in components views but styles definition is not changed at all.

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

Expected Behavior

I expect to have it changed in both: HTML in class attribute and inisde <style> tag.

Current Behavior

<div class="jss8 jss12 jss9"> is a result of <Card> component but no styles for those classes are provided.

There are still

<style type="text/css" data-jss="" data-meta="MuiPaper">
.MuiPaperroot-0-3-1 {
background-color: #fff;
}
.MuiPaperrounded-0-3-2 {
border-radius: 2px;
}
...
</style>

injected into the <head> section

Steps to Reproduce (for bugs)

Main component:

ReactDOM.render(
<AppContainer>
<Provider store={store}>
<ConnectedRouter history={history} children={routes} />
</Provider>
</AppContainer>,
document.getElementById('react-app')
);

Build an app with any material-ui component

Build it for production

There is no point to show it in codesandbox.io since it can't build project in production mode.

Context

When I build in production mode, no styles for Material-UI components are applied

Your Environment

Started with https://github.com/aspnet/JavaScriptServices boilerplate - React - Typescript. Introduced Material-UI instead of Bootstrap.

Tech
Version

Material-UI
v1.0.0-beta.33

React
16.2.0

browser
Chrome 63.0.3239.132
Issue 1:
It would be great to be able to specify the API dir location, please refer to https://spectrum.chat/next-js/general/next-9-is-there-a-config-option-to-change-where-the-api-dir-is-located~81da11ce-cd38-4fb5-bcda-9e95ee07db14

Issue 2:
Feature request

Is your feature request related to a problem? Please describe.

Next.js v9.0.0 hard codes the route name of the API path: /api/.

https://github.com/zeit/next.js/blob/71f9288a54c32420a18a07035ea7a73c9c3c50e5/packages/next/lib/constants.ts#L19

In Material-UI, we host pages under the /api/ folder. For instance: https://v3.material-ui.com/api/app-bar/. It forces us to rename this folder. This has an SEO impact.

Describe the solution you'd like

We would be interested in having an option to configure this path. For instance, I could imagine something like:

next.config.js

module.exports = {
apiRoutePath: 'json-api',
};

Additional context

The related thread on our side: mui/material-ui#16752

I had an initial discussion about the problem with @timneutkens on Twitter.

It seems relatively simple to implement as we have access to the config here:

https://github.com/zeit/next.js/blob/71f9288a54c32420a18a07035ea7a73c9c3c50e5/packages/next/build/entries.ts#L51
Issue 1:
Hello, I am using OS X EL Capitan(10.11.3) and vscode : Version 0.10.8 (0.10.8).

Following steps gives me invalid result and code loss:

write few lines of code

select those lines (Shift+arrow key)

3.press tab, and you will indent the code.

4.But if you press cmd+s (for saving file) and again pressed a tab button(while the code is selected already), the code vanishes leaving behind 3-4 last characters of those lines.

My concern is before indenting the selected code with tab button if you pressed cmd+s :+1 it should not affect the indentation or replace it with unwanted code.

Hope you are able to replicate it :)

Thanks in advance..

Issue 2:
when I open 0.10.5, it is crashed.

what I have do:

I have deleted the old config folder ~/.vscode
Issue 1:
Bug report

getInitialProps that with dynamic import, ssr is ok, but have errors in client side

pages/index.js

import React from "react";
import dynamic from "next/dynamic";
class Index extends React.Component {
static async getInitialProps() {
return { Hello: dynamic(import("../components/hello")) };
}
constructor(props) {
super(props);
console.log("props:", props);
}
render() {
const { Hello } = this.props;
console.log(this.props);
return (
<div>
<Hello />
</div>
);
}
}
export default Index;`

components/hello.js

export default class hello extends React.Component{
render ()
{
return (<div>
<p>Hello Next.js</p>
</div>)
}
}

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

just start run the dev npm script

http://localhost:3000

looks fine, but you will get lots of error in the browser console

Expected behavior

i log out the props in the render method on purpose, we can see the content in compiler console, but got nothing in client side console.

Screenshots

System information

OS:Windows10

Browser: chrome

Version of Next.js:7.0.2

Additional context

if we don't use dynamic import but do some simple data api request in getInitialProps, we found that the data recorded inside props would keeped in both server and client side, hope the componens that dynamic import can also shared both server side and client side

Issue 2:
Following directions to clone and run with-dynamic import and run dev yields following error:

Module not found: Error: Can't resolve 'react-dom/lib/ReactReconciler' in '/home/terry/myProjects/next/with-dynamic-import/node_modules/next/dist/client'

@ ./node_modules/next/dist/client/next-dev.js 5:23-63

@ multi ./node_modules/next/dist/client/webpack-hot-middleware-client ./node_modules/next/dist/client/on-demand-entries-client ./node_modules/next/dist/client/next-dev.js

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

Expected Behavior

It should run without errors.

Current Behavior

Steps to Reproduce (for bugs)

Context

Your Environment

Tech
Version

next
downloaded from examples repository

node
8.0.0

OS
ubuntu 16.04

browser
chrome

etc
Issue 1:
I am unable to build clang on OSX with BUILD_LLVM_CLANG in Make.user:

cd /Users/kevin/Source/julia-cxx/deps/scratch/llvm-svn/build_Release+Asserts/projects/compiler-rt/lib/builtins && \
/usr/bin/clang -stdlib=libc++ -mmacosx-version-min=10.8 \
-m64 -D_DEBUG -D__STDC_CONSTANT_MACROS \
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS \
-I/Users/kevin/Source/julia-cxx/deps/scratch/llvm-svn/build_Release+Asserts/projects/compiler-rt/lib/builtins \
-I/Users/kevin/Source/julia-cxx/deps/srccache/llvm-svn/projects/compiler-rt/lib/builtins \
-I/Users/kevin/Source/julia-cxx/deps/scratch/llvm-svn/build_Release+Asserts/include \
-I/Users/kevin/Source/julia-cxx/deps/srccache/llvm-svn/include -O3 -arch i386 -UNDEBUG \
-isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk \
-mmacosx-version-min=10.5 -fPIC -O3 -fvisibility=hidden -DVISIBILITY_HIDDEN -Wall -fomit-frame-pointer -arch i386 \
-o CMakeFiles/clang_rt.builtins_i386_osx.dir/absvsi2.c.o \
-c /Users/kevin/Source/julia-cxx/deps/srccache/llvm-svn/projects/compiler-rt/lib/builtins/absvsi2.c
clang: error: invalid deployment target for -stdlib=libc++ (requires OS X 10.7 or later)

I've tracked it down to a problem with flags: when compiling compiler-rt, an extra -mmacosx-version-min=10.5 is inserted late in the argument list, overriding the -mmacosx-version-min=10.8 on the second line.

Solutions on the web suggest

defining the environment variable MACOSX_DEPLOYMENT_TARGET=10.8

for cmake, adding CMAKE_OSX_DEPLOYMENT_TARGET=10.8

I've tried each of these, and while the second has an effect (I see two instances of -mmacosx-version-min=10.8 in compile commands), it also does not seem to propagate to compiler-rt. (Defining MACOSX_DEPLOYMENT_TARGET=10.8 doesn't seem to do anything.)

Thoughts on this? I was hoping to use Cxx.jl, although I'm wondering if I can get around this issue with a brew installed version...

Cc: @Keno

Issue 2:
This is the standard directory, distributions prefer documentation to go to $(docdir)/julia [1], which defaults to /usr/share/doc/julia. I'll have a look, this is mostly a reminder for myself.

By the way, by default calling make && make install you get the .rst installed directly. Maybe it would make more sense to compile this to HTML? Installing Python and configuration files does not make much sense either.

The man page is also duplicated in $(datarootdir)/julia/doc/man. Not sure why.

1: http://www.gnu.org/software/make/manual/html_node/Directory-Variables.html
Issue 1:
Using latest next.js relase and a simple hello world index page with 0 dependencies fails to run on heroku with the following error:

{ Error: Cannot find module '/tmp/build_xxx/node_modules/babel-runtime/helpers/inherits'
at Function.Module._resolveFilename (module.js:455:15)
at Function.Module._load (module.js:403:25)
at Module.require (module.js:483:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (/app/.next/dist/pages/index.js:7:18)
at Module._compile (module.js:556:32)
at Object.Module._extensions..js (module.js:565:10)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3) code: 'MODULE_NOT_FOUND' }

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

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

Your Environment

Tech
Version

next

node

OS

browser

etc
Issue 1:
This was reported in #16699 but while the error is fixed on the canary when using std/http/server.ts it remains when using Deno.serve. Therefore, I am making this issue to separate concerns.

Repro:

await Deno.serve(() => new Response("Hello World!"));

deno run --allow-net --unstable --watch server.ts

After making file changes to server.ts and saving it shows:

Watcher File change detected! Restarting!
error: Uncaught AddrInUse: Address already in use (os error 98)
Watcher Process finished. Restarting on file change...

Issue 2:
When running this code

Deno.serve(() => {}, { port: x })

with this command

deno run -A --unstable --watch script.ts

I get this error everytime i make a change and have to kill the script (ctrl + c) and run it again.

Watcher File change detected! Restarting!
error: Uncaught (in promise) AddrInUse: Address already in use (os error 98)
Watcher Process finished. Restarting on file change...

deno 1.26.1 (release, x86_64-unknown-linux-gnu)

Linux Fedora 37
Issue 1:
There is a lack of warning for incorrectly parsed configurations. In this case I set invalid values for the following configurations in elasticsearch.yml :

# incorrect values because booleans have to be lowercase
node.master: True
node.data: True
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["localhost"]

But elastic search starts and I am able to see the following cluster nodes:

curl localhost:9200/_nodes/http?pretty=true
{
"cluster_name" : "elasticsearch",
"nodes" : {
...
"attributes" : {
"master" : "True",
"data" : "True"
},
...
},

The only indication when I get that there is a problem is when I try to run other commands to access the data in the cluster. This is the error that I get back when I try to add a mapping to my_index:

curl -X PUT localhost:9200/my_index -d @mapping.json'
{"error":"MasterNotDiscoveredException[waited for [30s]]","status":503}

In this case, it would be useful to fail server start if there is an incorrect parameter or issue some sort of warning or have it logged. I ran this on elasticsearch 1.3.4.

Issue 2:
Currently there is no way of seeing all settings that are enforced. For instance, defaults are not available and settings from the config/elasticsearch.yml are not available.

Any setting which is different from the default should be returned by these APIs:

GET /{index}/_settings
GET /_cluster/settings

Both should also support the include_defaults query string parameter, which would return all settings, including the defaults.

Also, deleting a setting should reset the setting to the default.

Setting an unknown setting, or a setting that can't be changed should throw an error.

Relates to #5018, #3670, #2738, #2730, #3572, #2628, #3671, #5019, #6309
Issue 1:
Describe the bug

SQLAlchemy (on the latest master version) does not place correct parenthesis when using the || operator.

Expected behavior

expr = type_coerce(Author.id + literal(1), types.String)
f = (Author.first_name + expr).label('f')
session.query(f).select_from(Author)

I expect the following query:

SELECT author.first_name || (author.id + ?) AS f
FROM author

Producing:

Name1
Name2
...

Instead SQLAlchemy generate the following query:

SELECT author.first_name || author.id + ? AS f
FROM author

Leading to incorrect results:

1
1
...

Unlike the SQL operator +, the operator || has the highest precedence.

Therefore to interpret this query correctly parenthesis are needed.

For more details see here

Versions.

SQLAlchemy latest master version(commit)

Have a nice day!

Issue 2:
Describe the bug

It seems to me that sqlalchemy does not wrap an SQL expression with brackets when the function type_coerce() is used.

I have the following query

mulExpr = type_coerce((Model.a * Model.b), types.Float).label('mulExpr')
divExpr = (Model.c / mulExpr).label('divExpr')
session.query(divExpr, mulExpr).select_from(Model)

The code generates the following SQL query when I ran it on sqlite.

SELECT Model.c / Model.a * Model.b AS "divExpr", Model.a * Model.b AS "mulExpr"
FROM listing

However, I would expect the following query instead where the sub-expression Model.a * Model.b is wrapped by brackets.

SELECT Model.c / (Model.a * Model.b) AS "divExpr", Model.a * Model.b AS "mulExpr"
FROM listing

Note that this issue only occurs when the function type_coerce() is applied to the sub-expression.

Have a nice day!
Issue 1:
If I add the latest version of rx.TypeScript.DefinitelyTyped to a new TypeScript project, it doesn't build. I get the following errors:

C:\Development\Projects\TypeScriptTestApp\TypeScriptTestApp\Scripts\typings\rx\rx.lite.d.ts(14,15): error TS2000: Build: Duplicate identifier 'Scheduler'. Additional locations:
C:\Development\Projects\TypeScriptTestApp\TypeScriptTestApp\Scripts\typings\rx\rx.lite.d.ts(14,15): error TS2137: Build: Class Scheduler declares interface IScheduler but does not implement it:
C:\Development\Projects\TypeScriptTestApp\TypeScriptTestApp\Scripts\typings\rx\rx.virtualtime.d.ts(10,79): error TS2186: Build: Type name 'Scheduler' in extends clause does not reference constructor function for 'Scheduler'.

@Igorbek / @carldebilly any comments?

Issue 2:
could you please let me know if, there is any existing issues on the below scenario. Else i feel this is something to do with the latest release with @types/express

I tried using the @types/express: 4.17.5 package and had problems.

I tried reverting to @types/express: 4.17.0 package and find no problems.

The latest version problems are as follows

Sometimes i get as Property 'query' does not exist on type 'Request<ParamsDictionary, any, any, any>'[ #40138]

some times i get the issue as

error TS2345: Argument of type 'string | string[] | Query | Query[]' is not assignable to parameter of type 'string'. Type 'string[]' is not assignable to type 'string'. when i use as 'req.query.xxxx'
Issue 1:
Hi, could you update this dependency on the new version?

Moderate Prototype Pollution

Package minimist

Patched in >=1.2.3

Dependency of webpack-dev-server [dev]

Path webpack-dev-server > chokidar > fsevents > node-pre-gyp > tar > mkdirp > minimist

More info https://npmjs.com/advisories/1179

Moderate Prototype Pollution

Package minimist

Patched in >=1.2.3

Dependency of webpack [dev]

Path webpack > watchpack > chokidar > fsevents > node-pre-gyp > rc > minimist

More info https://npmjs.com/advisories/1179

Issue 2:
Bug report

webpack currently depends on the old 0.5.1 version of "mkdirp" which depends on old vulnerable minimist package. The 0.5.x line of mkdirp from the original author is not developed any further and maintenance of this package was taken over by isaacs with the new 1.x versions.

see: https://github.com/substack/node-mkdirp/issues/166

CVE: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7598

Please update "mkdirp" dependency to the latest 1.x version to fix this vulnerability.

.

What is the current behavior?

old "mkdirp" 0.5.1 fetches dependend package "minimist" 0.0.8 which triggers warning in security checkers blocking new builds.

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?

Update dependency "mkdirp" to latest version 1.0.3 which has dropped dependency of "minimist" and does not trigger any security warnings anymore.

Other relevant information:

webpack version: 4.42.0

Node.js version: 10.16

Operating System: linux

Additional tools:
Issue 1:
I am testing out the v1.1.0 tag and built a hyperkube binary. However, running it with no arguments is producing:

_output/local/go/bin/hyperkube
W0930 17:57:47.051620 714 server.go:176] Failed to start in resource-only container "/kube-proxy": mkdir /sys/fs/cgroup/perf_event/kube-proxy: read-only file system
W0930 17:57:47.051962 714 server.go:185] Neither --kubeconfig nor --master was specified. Using default API client. This might not work.
W0930 17:57:47.053839 714 iptables.go:140] Error checking iptables version, assuming version at least 1.4.11: exec: "iptables": executable file not found in $PATH
E0930 17:57:47.054589 714 server.go:331] Not trying iptables proxy: can't get Node "507aa6445e16": Get http://localhost:8080/api/v1/nodes/507aa6445e16: dial tcp 127.0.0.1:8080: connection refused
F0930 17:57:47.055092 714 server.go:246] Unable to create proxier: failed to initialize iptables: error creating chain "KUBE-PORTALS-CONTAINER": exec: "iptables": executable file not found in $PATH:

I would have expected a usage message. None of the servers are working correctly. After doing some more digging I found that when adding the proxy server to hk is causing it to essentially boot up breaking hyperkube.

See 1c25c2c

Issue 2:
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.):

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

Kubernetes version (use kubectl version):

Environment:

Cloud provider or hardware configuration:

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

Kernel (e.g. uname -a):

Install tools:

Others:

What happened:

What you expected to happen:

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

Anything else do we need to know: