WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

The color which is supplied in palette.text.primary value doesn't seem to do anything.

I was hoping that when I pass that value then that color will be used for every component which has color value set to primary. But it seems that every component decides on the text color on its own by using the getContrastText mixin.

I understand there is a way to override this using "overrides" while creating a theme. But that would require overriding a lot for me as I want this thing to be user controlled through preferences.

May be I am just understanding it wrongly. My main question is that if the value passed under palette.text.primary is used at all ?

Context

I am trying to make a user controlled look and feel where the user will be able to choose from several predefined color schemes I provide in the application

Your Environment

Tech
Version

Material-UI
1.0.0-beta.27

React
16.2.0

browser

etc

Additionally, is there a slack chat available for this kind of questions ?

Issue 2:
Since using v1, I find myself often wanting to quickly navigate to a Component's implementation, to check its implementation details, but especially since material-ui now uses JSS, which requires us to look at the classes in the source code to override them properly.

I think it'd be helpful to either:

Add a link to a component's source code on every page

Add the defaults for each JSS class (much more work I guess)

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

Tech
Version

Material-UI
v1
Issue 1:
I've found two problems of Atom's soft wrapping:

Chinese and Japanese language does not use spaces to separate characters, it causes that Atom treats Chinese sentence as a extremely-long "word" and does not perform correct wrap. According to [http://en.wikipedia.org/wiki/Line_breaking_rules_in_East_Asian_languages], a "CJK Word" is something like (Opening punctuation)*(Han character | Kana)(Trailing punctuation|Traialing Kana)*.

Atom cannot handle non-monospaced fonts correctly. Han characters and Kanas are much wider than Latin characters.

Issue 2:
Reported in Halp:

support/b47caffcaba511e3903bfcd96bef4da2

If I have a paragraph in CJK characters and toggle soft wrap, the wrapping point (should be the right edge of current window) is far away than the current edge and some characters are displayed out of window which is not visible.

I think this may because of the wrong processing of character wide. A latin letter has a width "one character width", but usually a CJK character has a width twice as a latin letter, it's "two character width". Hope this information may help you.

The debug info auto attached should include the test text I open now. It's include (from up to down): Chinese, Japanese, Korean, English. Actully they tell the same thing:)

I can reproduce this in Atom 0.75.0. (notice how CJK characters are not wrapped correctly at the right edge of the app)
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.3

Operating System version: Window10

Java version: 1.8

Steps to reproduce this issue

open AccessLogFilter

dubbo:
scan:
base-packages: ...
protocol:
name: dubbo
port: 12345
registry:
address: N/A
provider:
accesslog: true

org.apache.dubbo.rpc.protocol.ProtocolFilterWrapper#buildInvokerChain return the AccessLogFilter success

org.apache.dubbo.rpc.filter.AccessLogFilter#invoke

String accessLogKey = invoker.getUrl().getParameter(ACCESS_LOG_KEY);
if (ConfigUtils.isNotEmpty(accessLogKey)) {
log......
}

invoker.getUrl() not contain parameter who's named 'ACCESS_LOG_KEY' but accesslog.

private static final String ACCESS_LOG_KEY = "dubbo.accesslog"; (Line 71 in AccessLogFilter)

There is no way to successfully print the log.

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

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.6

Operating System version: xxx

Java version: 1.8

Steps to reproduce this issue

xxx

xxx

xxx

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

What do you expected from the above steps？

Actual Result

What actually happens?

If there is an exception, please attach the exception trace:

Just put your stack trace here!
Issue 1:
These only show up in oldnumeric when 2to3 with the 2to3 renames and nonzero fixers. The replacement for sys.maxint in python3 is sys.maxsize, but the two aren't the same, the latter the size of Py_ssize_t. Likewise the the replacement for __nonzero is __bool__, but anyone using old numeric is likely to have made the change.

Because oldnumeric will go away, I suggest we leave those attributes unchanged and advertize that oldnumeric isn't supported in python 3.

Issue 2:
I've found a very strange bug. Under certain circumstances, a small number of the entries in the dot product of two 2D arrays will be wrong:

import numpy as np
nrow, ncol = 2, 69900
rows = np.random.normal(size=(nrow, 1)).astype(np.float32)
columns = np.random.normal(size=(1, ncol)).astype(np.float32)
np_outer = rows.dot(columns)
ind0, ind1 = 0, 69818
print(np_outer[ind0, ind1], rows[ind0, 0]*columns[0, ind1])

Most entries are fine. In this example, only columns 69818-69899 in the product are wrong.

This issue remains the same using np.matmul(rows,columns) and for different values of nrow. However it doesn't appear for an arbitrary values of ncol. There's a band of values around 69900 where errors appear, but there are none at 60000 or 70000. It's also not always the case that the last columns are the ones affected. For some values of ncol, there will be multiple bands of columns affected.

I have not seen this behavior with float64 arrays. It also disappears if you do the dot product in transposed order:

np_outer_t = columns.T.dot(rows.T).T
print(np_outer_t[ind0, ind1], rows[ind0, 0]*columns[0, ind1])

System info: numpy 1.12.1, python 3.6.1, Macbook Pro, OS 10.6.1
Issue 1:
I've got a small Rust program, trying to implement a binary search tree. With Rust 0.8, the compiler segfaults. WIth GIT revision 8ea2123, I get a nicer error-message, THEN a segfault. Looks like some sort of infinite stack-recursion.

I'm including the program.

extern mod extra ;
use std::rand;
use std::rand::Rng;
use std::vec ;
use std::str ;
use extra::sort ;

struct bstnode<K, V> {
k : K,
v : V,
l : Option< bstnode<K, V> >,
r : Option< bstnode<K, V> >
}

impl<K : Clone + Eq + TotalOrd , V : Clone> bstnode<K, V> {
fn new(k: &K, v: &V) -> bstnode<K,V> {
bstnode { k: (*k).clone(), v: (*v).clone(), l: None, r: None }
}
fn dumbinsert(node: &mut bstnode<K, V>, k : &K, v : &V) {
if (node.k.cmp(k) == Equal) {
node.v = v.clone() ;
}
else if (k.cmp(&(node.k)) == Less) {
match node.l {
None => { node.l = Some(bstnode::new(k, v)) ; }
Some(ref mut l) => bstnode::dumbinsert(l, k, v)
}
}
else {
match node.r {
None => { node.r = Some(bstnode::new(k, v)) ; }
Some(ref mut r) => bstnode::dumbinsert(r, k, v)
}
}
}
}

fn main() {
let k = ~"foo";
let v = ~"bar";
let mut t = bstnode::new(&k, &v) ;
let k2 = ~"foo2" ; let v2 = ~"bar2" ;
bstnode::dumbinsert(&mut t, &k2, &v2) ;
}

Issue 2:
This is a backtrace from compiletest built with -g

#11 0x00007ffff7aee3ff in context::call_shim_on_c_stack (this=0x43d700, args=0x445e80, fn_ptr=0x7ffff7af2f48) at
../src/rt/arch/x86_64/context.h:58
#12 0x00007ffff7af4066 in call_upcall_on_c_stack (args=0x445e80, fn_ptr=0x7ffff7af2f48) at ../src/rt/rust_upcall
.cpp:37
#13 0x00007ffff7af3144 in upcall_shared_malloc (nbytes=52, td=0x0) at ../src/rt/rust_upcall.cpp:200
#14 0x000000000042be44 in glue_take::S::_7fffa7de31d4d8d4 ()
#15 0x000000000042ebf6 in _ZN9glue_take32R_5B_compile_lib_path_3D_Srun_lib_path17_78527795f021202cE ()
#16 0x0000000000426d8e in run_tests::_37dd24d3b9435856 ()
#17 0x000000000042fe28 in __morestack ()
#18 0x000000000041c0d0 in main::_c5e23313747479c7 ()
#19 0x000000000041c162 in _rust_main ()
#20 0x00007ffff7aec619 in task_start_wrapper (a=0x44272c) at ../src/rt/rust_task.cpp:282
#21 0x0000000000000000 in ?? ()

gdb doesn't understand one of the names.
Issue 1:
The latest version of Electron (0.36.0) still has an issue on Yosemite with fullscreen.

Basically when in fullscreen mode the window shows a textured title at the top:

This happens regardless if the window frame option is set to true or false (the only difference being you don't see the traffic lights on hover when set to false). However setting the transparent option to true removes the titlebar completely and solves it.

So in short it needs to hide the titlebar when transparency is set to false and in fullscreen and then ONLY show the title when hovering and the frame is set to true.

Issue 2:
Origintal ticket: sindresorhus/caprine#5

In fullscreen mode, instead of showing the user toolbar, it covers it up with a gray frame.

1. Normal

#### 2. Fullscreen

#### 3. Fullscreen with menubar visible

Ideally it would show the top (covered up) web content in both 2. and 3., so my custom toolbar would be visible there.

OS X 10.10 and Electron 0.32.3.

@jaanus
Issue 1:
I have two pgsql domains: isoweekday that is based on INT and isoweekdays that is an array of the former. Both domains add some checks like no duplicate values, no empty list, only values from <1, 7> range.

CREATE DOMAIN isoweekday AS INT
CHECK(...);

CREATE DOMAIN isoweekdays AS isoweekday[]
CHECK(...);

I've created custom types, like so:

class ISOWeekDayDomain(types.UserDefinedType, types.Integer):
def get_col_spec(self, **kwargs):
return 'isoweekday'

class ISOWeekDaysDomain(types.UserDefinedType, ARRAY):
def __init__(self, **kwargs):
if 'item_type' not in kwargs:
kwargs['item_type'] = ISOWeekDayDomain

super(ISOWeekDaysDomain, self).__init__(**kwargs)

def get_col_spec(self, **kwargs):
return 'isoweekdays'

and then used them to define a column:

Column(
ISOWeekDaysDomain, nullable=False, server_default=text('ARRAY[1,2,3,4,5,6,7]')
)

Creating migrations using Alembic went well, and it created the following statement:

op.add_column(
u'config',
sa.Column(
'dow',
ISOWeekDaysDomain(),
server_default=sa.text(u'ARRAY[1, 2, 3, 4, 5, 6, 7]'),
nullable=False,
),
)

After applying migrations on the database, I'm getting the following warning:

sqlalchemy/dialects/postgresql/base.py:2683: SAWarning: Did not recognize type 'isoweekday[]' of column 'dow'

Running alembic yields a new database migration that alters the previously added column with sqltypes.NULLTYPE.

op.alter_column(u'tent_crawling_config', 'dow',
existing_type=sa.NullType(),
nullable=False,
existing_server_default=sa.text(u'ARRAY[1, 2, 3, 4, 5, 6, 7]'))

The domains dictionary passed to _get_column_info contains both created domains and during execution it enters the dialects/postgresql/base.py#L2677 block.

What am I missing? How to register my custom types that map domains so the reflection API recognises them?

I'm using SQLAlchemy==1.2.14 and PostgreSQL v11

Issue 2:
Migrated issue, originally created by Anonymous

Hello, I've just encountered a very odd behaviour of SA, revision 1190.

Basically, it seems to save dereferenced object as well, even though the object gets deleted from the current namespace. all the object values are actually kept and written to the database!

I don't have enoug SA knowledge to try to understand where the problem occurs; I guess it's got something to do with SA internal object-tracking (maybe it's employing a standard ref instead of a weakref somewhere).

demo attached.

Alan Franzoni <alan.franzoni at gmail dot com>

Attachments: objectstore-problem.py
Issue 1:
I was playing around with the idea of placing a__tests__ folder into my different directory areas.

So

root
|-pages
| `__tests__
| `index.test.js
| `index.js
|-components
| `__tests__
| `Button.js
|-layouts
`__tests__
`TwoColumn.js

But when I do this, I get duplicate issues because of files being copied into .next

.next/dist/pages/__tests__/index.test.js

What is the best way to solve this? I know I can omit the files from jest, but I don't think they should be copied over in general.

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

Expected Behavior

Considering the following snippet:

<Head>
{title ? (
<React.Fragment>
<title>{title} | Cool site</title>
<meta property='og:title' content={title} />
</React.Fragment>
) : (
<title>Cool site</title>
)}

{/* … */}
</Head>

When title is defined, I would expect <title>foo | Cool site</tite> to be rendered.

Current Behavior

An empty <title /> is rendered.

Your Environment

Tech
Version

next
4.1.4

node
8.9.1
Issue 1:
Original ticket http://projects.scipy.org/numpy/ticket/1930 on 2011-08-10 by trac user tlatorre, assigned to unknown.

>>> np.uint64(5) << 1
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: ufunc 'left_shift' not supported for the input types, and the inputs could not be safely coerced to any supported types according to the casting rule 'safe'
>>> np.uint64(5) >> 3
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: ufunc 'right_shift' not supported for the input types, and the inputs could not be safely coerced to any supported types according to the casting rule 'safe'

Issue 2:
Original ticket http://projects.scipy.org/numpy/ticket/1931 on 2011-08-10 by trac user tlatorre, assigned to unknown.

>>> np.uint64(5) << 1
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: ufunc 'left_shift' not supported for the input types, and the inputs could not be safely coerced to any supported types according to the casting rule 'safe'
>>> np.uint64(5) >> 3
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: ufunc 'right_shift' not supported for the input types, and the inputs could not be safely coerced to any supported types according to the casting rule 'safe'
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

DatePipe.transform() produces an incorrect string in IE. Instead of getting the correct, formatted string, you get the correct formatted string followed by the whole date.

Expected behavior

DatePipe.transform() should return the same result as in other browsers.

Minimal reproduction of the problem with instructions

See Plunker example:

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

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

With the current behavior it is impossible to get the correct, formatted string when using DatePipe inside a component.

Please tell us about your environment:

Angular version: 2.0.X

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 ]

IE11

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

typescript@2.0.2

Node (for AoT issues): node --version =

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

[x] bug report
[ ] 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 using the date pipe In IE 11.0.9600.18350 with minutes/seconds it shows the whole date instead of the minutes and/or seconds.

Examples:

Date recieved from service | used binding | result

"2016-06-21T10:47:40Z" | {{mydate | date:'HH'}} | ‎12‎:‎00

"2016-06-21T10:47:40Z" | {{mydate | date:'mm'}} | ‎6‎/‎21‎/‎2016‎ ‎12‎:‎47‎:‎40‎ ‎PM

"2016-06-21T10:47:40Z" | {{mydate | date:'ss'}} | ‎6‎/‎21‎/‎2016‎ ‎12‎:‎47‎:‎40‎ ‎PM

"2016-06-21T10:47:40Z" | {{mydate | date:'HH:mm'}} | ‎12‎:‎00:‎6‎/‎21‎/‎2016‎ ‎12‎:‎47‎:‎40‎ ‎PM

"2016-06-21T10:47:40Z" | {{mydate | date:'mm:ss'}} | ‎6‎/‎21‎/‎2016‎ ‎12‎:‎47‎:‎40‎ ‎PM:‎6‎/‎21‎/‎2016‎ ‎12‎:‎47‎:‎40‎ ‎PM

"2016-06-21T10:47:40Z" | {{mydate | date:'HH:ss'}} | ‎12‎:‎00:‎6‎/‎21‎/‎2016‎ ‎12‎:‎47‎:‎40‎ ‎PM

"2016-06-21T10:47:40Z" | {{mydate | date:'HH:mm:ss'}} | ‎‎12‎:‎00:‎6‎/‎21‎/‎2016‎ ‎12‎:‎47‎:‎40‎ ‎PM:‎6‎/‎21‎/‎2016‎ ‎12‎:‎47‎:‎40‎ ‎PM

It seems that the minutes and seconds produce an entire date instead of the desired minutes/seconds.

Expected/desired behavior

The expected behaviour is that mm only returns the minutes and ss only returns the seconds.

Reproduction of the problem

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

What is the expected behavior?

See above.

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

Please tell us about your environment:

Angular version: 2.0.0-rc.2 && 2.0.0-rc.3

Browser: [ IE 11.0.9600.18350 && Edge ] this does not occur on the latest versions of Chrome and Firefox. Haven't tested other browsers.

Language: [TypeScript 1.8.10]
Issue 1:
str has been asserted it cannot be undefined on all call sites of test() below:

let str: string | undefined;
if (str) {
test();
}

function test() {
str.charAt(1); // error can be undefined
}

Issue 2:
Hi,

Version: 1.8.5

I would like to see an error when duplicate values are found in a string literal declaration:

type alphabet = 'a' | ... | 'x' | 'y' | 'a'; // Error: Duplicate value 'a'

This is most likely an unintentional inclusion.
Issue 1:
Superset version

0.22

Expected results

Was expecting superset to open properly

Actual results

Steps to reproduce

Installed superset 0.22 according to instructions https://github.com/apache/incubator-superset/blob/010a69de83273934cc02c4fcc9e6b3014591193e/CONTRIBUTING.md

npm run dev on superset/assets/

Did anyone face this issue before?

Issue 2:
Expected results

Expected helm chart to work with default/updated values.

Actual results

It throws password authentication failed for both default superset helm

setup as well as updated values.yaml where postgres password is overridden.

ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed:
(psycopg2.OperationalError) FATAL: password authentication failed for user "superset"

How to reproduce the bug

We can reproduce the same by following the official documentation:

https://superset.apache.org/docs/installation/running-on-kubernetes

We can use the default my-values.yaml or the version where postgresPassword is updated.

$ helm repo add superset https://apache.github.io/superset
"superset" has been added to your repositories

// updated postgresPassword from my-values.yaml file
$ helm upgrade --install --values my-values.yaml superset superset/superset
Release "superset" does not exist. Installing it now.
coalesce.go:163: warning: skipped value for extraEnv: Not a table.
NAME: superset
LAST DEPLOYED: Sat Jun 12 10:26:42 2021
NAMESPACE: superset
STATUS: deployed
REVISION: 1
TEST SUITE: None

// list pods
$ helm get pods

// show log from superset pod
$ helm log -t superset-<pod-id>
...
[2021-06-12 10:24:07 +0000] [1092] [INFO] Worker exiting (pid: 1092)
Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
[2021-06-12 10:24:07 +0000] [1094] [INFO] Booting worker with pid: 1094
logging was configured successfully
2021-06-12 10:24:08,970:INFO:superset.utils.logging_configurator:logging was configured successfully
2021-06-12 10:24:08,976:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
2021-06-12 10:24:09,007:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (psycopg2.OperationalError) FATAL: password authentication failed for user "superset"
...

Environment

superset version: superset-helm-chart-0.1.4 (latest docker tag)

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.
Issue 1:
Marcel Stör opened SPR-9722 and commented

With #9462 support for default values was added.

However, I observed that they are applied too early if you have a hierarchy or cascade of property placeholder configurers:

Spring loops through the prioritized list of configurers

if property X is not found in the first configurer the default value is returned

--> the whole list should be processed first before the default value is used

Affects: 3.1.1

Issue Links:

#14292 @Value assigns the default property value (if specified) before all property locations are examined, resulting in assigning a default to a property which is defined in a properties file. ("is duplicated by")

1 votes, 3 watchers

Issue 2:
Lachezar Kozhuharov opened SPR-9474 and commented

I would expect the matching pattern not to partially enforce the query structure. Expected behavior is to fully enforce it or not to enforce it at all. This would be useful when for example building a RESTful service client. A query like "a=b&filter=c==d" is not properly processed and results in URI change.

Affects: 3.1 RC2

Issue Links:

#14465 Erroneous "0" returned where empty string expected in call through the RestTemplate ("duplicates")

Referenced from: commits 2965df6
Issue 1:
I want to make a pattern on a route host requirement using a parameter like this

my_homepage:
path: /
host: {mydomain}
defaults: { _controller: AcmeDemoBundle:Main:myHomepage }
requirements:
mydomain: %mydomain%

and parameter.yml :

mydomain: mydomain.com

Such a config (modified doc example) generate a Yaml parse error

Malformed inline YAML string ({domain}) at line 64 (near "host: {domain}").)

Am i wrong ?

Using quote like this don't solve the problem ,

my_homepage:
path: /
host: "{mydomain}"
defaults: { _controller: AcmeDemoBundle:Main:myHomepage }
requirements:
mydomain: %mydomain%

and generate another error,

An exception has been thrown during the rendering of a template
("Some mandatory parameters are missing ("mydomain") to generate a URL for route...

Tried on different projects without good result....

Issue 2:
Q
A

Bug report?
no

Feature request?
yes

BC Break report?
no

RFC?
no

Symfony version
any

The symfony phpunit bridge does not work with phpunit version 6 which is namespaced. So for example

https://github.com/symfony/symfony/blob/master/src/Symfony/Bridge/PhpUnit/bootstrap.php#L16 will just be skipped.
Issue 1:
Challenge Use HTML5 to Require a Field has an issue.

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

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

My code:

<link href="http://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">
<style>
.red-text {
color: red;
}

h2 {
font-family: Lobster, Monospace;
}

p {
font-size: 16px;
font-family: Monospace;
}

.thick-green-border {
border-color: green;
border-width: 10px;
border-style: solid;
border-radius: 50%;
}

.smaller-image {
width: 100px;
}
</style>

<h2 class="red-text">CatPhotoApp</h2>

<p>Click here for <a href="#">cat photos</a>.</p>

<a href="#"><img class="smaller-image thick-green-border" alt="A cute orange cat lying on its back" src="https://bit.ly/fcc-relaxing-cat"></a>

<p>Things cats love:</p>
<ul>
<li>cat nip</li>
<li>laser pointers</li>
<li>lasagna</li>
</ul>
<p>Top 3 things cats hate:</p>
<ol>
<li>flea treatment</li>
<li>thunder</li>
<li>other cats</li>
</ol>
<form action="/submit-cat-photo">
<input type="text" required placeholder="cat photo URL">
<button type="submit">Submit</button>
</form>

I've tried hard refresh, logging in and logging out, deleting the required fields, and then adding them again, it just doesn't go on.

Issue 2:
I cann't press the button "Submit and go to my next challenge (ctrl + enter)". But if I clicked I only see the infinite loading. How to solve this problem?