WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I am using Keras to predict multilables, that is, one record might have multiple classes. For ex, if there are 10 target classes, a record can have more than one target class. In this scenario whats the best way to transform target. I am using categorical_crossentropy as my objective. I tried both - 1) having multiple 1s and 0s within 10 output vectors & 2) having only 1 in one of the 10 output vectors & rest 0s. In this way I would duplicate each record with multiple outputs.

I read Keras link https://keras.io/objectives/ where its specifically written -

"Note: when using the categorical_crossentropy objective, your targets should be in categorical format (e.g. if you have 10 classes, the target for each sample should be a 10-dimensional vector that is all-zeros expect for a 1 at the index corresponding to the class of the sample). In order to convert integer targets into categorical targets, you can use the Keras utility to_categorical"

If this is true, still I don't get any error with with 1st approach and even the predictions are better. I want to understand whats happening inside and how does it tackle this kind of situations

Issue 2:
The issue appears because of composing the layers: TimeDistributed(L)

import keras
from keras import backend as K
from keras.models import Model, load_model
from keras.layers import Input, Dense, Concatenate, Flatten
from keras.layers.wrappers import TimeDistributed
a = Input(shape=(784,5))
b = Input(shape=(784,5))

L = Dense(units=10)

u = TimeDistributed(L)(a) # u = L(a) works correctly
v = L(b)

x = Concatenate() ([u, v])

model = Model(inputs=[a, b], outputs=x)

print model.count_params() # 120
model.summary() # 60

model.save('tmp.model')

###################################

loaded_model = load_model('tmp.model')

print loaded_model.count_params() # 120
loaded_model.summary() # 120

Note that count_params() always gives incorrect numbers. Is that another bug?
Issue 1:
We seem to be aggressively autocompleting even in places where we're making a new declaration. This is a regression from 1.5 (incl. with VS 2015):

class Foo {
// type "star(" here modulo quotes
}

Expected behavior: no autocomplete

1.6 behavior: autocompletes to "animationStartTime("

Issue 2:
Edit by @DanielRosenwasser:

Allow new identifiers (i.e. show a builder).

Suggest "appropriate" completions.

Original:

Certainly something like constructor should still be there (maybe methods/properties in parent class or implemented interface), but others should be hidden.
Issue 1:
Migrated issue, originally created by Konsta Vesterinen (@kvesteri)

I've been having problems with CTEs inside function constructs. The CTEs seem to get duplicated in the parent query FROM part. This in turn causes variety of problems. For now I've been using workarounds (in other words not using CTEs at all). However now I have a scenario where this feature desperately needed.

I created a simplistic scenario which illustrates this problem. The generated SQL is also wrong (at least in PostgreSQL) since the select clause in from part does not have an alias.

import sqlalchemy as sa
from sqlalchemy.orm import sessionmaker
from sqlalchemy.ext.declarative import declarative_base

engine = sa.create_engine(
'postgres://postgres@localhost/sqlalchemy_utils_test'
)
Base = declarative_base()
Session = sessionmaker(bind=engine)
session = Session()

class User(Base):
__tablename__ = 'user'
id = sa.Column(sa.Integer, primary_key=True)
name = sa.Column(sa.String)
def __repr__(self):
return 'User(name=%r)' % self.name

Base.metadata.create_all(bind=session.bind)

users = sa.select([User.name]).limit(1).cte('users')

query = sa.select(
[
sa.func.json_build_object('user', sa.select([users.c.name]))
]
)
# query IS:
#
# WITH users AS
# (SELECT "user".name AS name
# FROM "user"
# LIMIT :param_1)
# SELECT json_build_object(:json_build_object_2, (SELECT users.name
# FROM users)) AS json_build_object_1
# FROM (SELECT users.name AS name
# FROM users)
#
# query SHOULD BE:
#
# WITH users AS
# (SELECT "user".name AS name
# FROM "user"
# LIMIT 1)
# SELECT json_build_object('something', (SELECT users.name FROM users))

session.execute('DROP TABLE "user"')
session.commit()

There might also be a simple workaround for this that I just haven't noticed.

Issue 2:
Migrated issue, originally created by Anonymous

fdb.py supports firebird under python2/3

There are only minor changes to the existing kinterbasdb driver.

A patch is attached.

It works for me using python2 and firebird-2.5.2

Attachments: fdbsupport.diff
Issue 1:
I think it would be good to have a standardised way to access deno.json config data, since 3rd party tools (bundlers for example) need to have read compilerOptions and importMap to prevent a separate config file.

It is possible to do find and parse the file manually (PR in deno/std denoland/deno_std#2356, but @ry is hesitant, since it could get out of sync with the runtime behavior.

So it would be better to include it in the deno namespace.

namespace Deno {
export interface ConfigObject {
tasks: Record<string, string>;
importMap: ImportMap
compilerOptions: CompilerOptions;
…
}
export interface config {
/**
* returns the filePath of the deno.json or deno.jsonc file that was parsed by the runtime
*/
filePath: string | null;
/**
* returns the resolved json or jsonc data that was parsed by the runtime
*/
toObject(): ConfigObject | null;
}
}

What are your thoughts on that?

Issue 2:
I just started playing with Deno,

i made simpler handler which intercepts req and process that

here is my index file

import { serve } from "https://deno.land/std@v0.42.0/http/server.ts";
import handler from './handler.ts'
const s = serve({ port: 8000 });
console.log("http://localhost:8000/");

if(Deno.args.length !== 1){
throw new Error('Handler is not defined')
}

// console.log(finalHandler)
for await (const req of s) {
if(req.url === '/'){
req.respond({ body: handler(req) });
}else{
req.respond({})
}
}

and this is my simple handler file

import { ServerRequest } from "https://deno.land/std@v0.42.0/http/server.ts";
export default (req: ServerRequest) => {
return `test ${req.url} `
}

if i run this command

deno run --allow-net --allow-read index.ts handler.ts

it works fine, and when i try loading handler file from Deno args and try importing them then it give me error

Updated code in index.ts which fails

import { serve } from "https://deno.land/std@v0.42.0/http/server.ts";
// import handler from './handler.ts'
const s = serve({ port: 8000 });
console.log("http://localhost:8000/");

if(Deno.args.length !== 1){
throw new Error('Handler is not defined')
}

let handlerPath = await Deno.realPath(Deno.args[0])
console.log(handlerPath)
let finalHandler = await import(handlerPath)

console.log(finalHandler)
for await (const req of s) {
if(req.url === '/'){
req.respond({ body: finalHandler(req) });
}else{
req.respond({})
}
}

it throws error at time of importing file

let finalHandler = await import(handlerPath)

now when i run this command

deno run --allow-net --allow-read index.ts handler.ts

it gives me this error

thread 'main' panicked at 'internal error: entered unreachable code', cli\state.rs:492:12
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Issue 1:
Bug report

Bug summary

When I specify edgecolor and hatch within pyplot.barh those settings are only applied to the first bar in the plot.

Code for reproduction

import matplotlib.pyplot as plt

values = [13, 2, 1, 1]
y_pos = [0, 1, 2, 3]
fig = plt.figure(figsize=(6.0, 3.3))
ax = fig.add_subplot(111)
ax.barh(y_pos,
values,
align="center",
facecolor="white",
edgecolor="blue",
hatch="/",
)
ax.set_yticks(y_pos)
ax.set_yticklabels([])
plt.show()

Actual outcome

Expected outcome

All bars to show the blue edgecolor and hatch.

This worked in Matplotlib 2.0.1.

Matplotlib version

Operating system: Red Hat Enterprise Linux Workstation release 6.8 (Santiago)

Matplotlib version: 2.1.0

Matplotlib backend: 'Qt5Agg'

Python version: 3.6.2

Jupyter version (if applicable): N/A

Other libraries:

I installed this using the main channel of miniconda.

Issue 2:
I ran some code and realized it is only working on the first bar. I'm using Python 3.6.2, matplotlib 2.1. Just reverted back to 2.0.2.
Issue 1:
on every second row. THis means that in a gable where this happens suddenly half the rows are shown in the default color. Worked perfectly with 3.0.2

In 3.0.2 you would see every line in green. Generating code is unchanged.

The HTML looks like this (heavily cutting out stuff not relevant):

table class="table table-striped table-condensed" id="buckettable"

thead>

tr>

...

/tr>

/thead>

tbody>

tr class="success">

and that TR is for every line in the screenshot. Turns the use of striped and condensed - useless. Removing table-striped leads to the proper coloring.

Issue 2:
This is a feature request for the not-so-distant future, when the upcoming new version of LESS (1.4.0) gets into its final shape.

Also, I understand the new grid system (and the mixin utilities that help to create it) on 3.0.0-wip is still a WIP, and still being overhauled.

The current way the grid system is dynamically created, using mixins (.generate-grid-columns() and .generate-grid-columns()) makes it impossible to :extend the bunch of classes (.col-sm-* and .col-lg-*).

One desirable advantage of :extending (over including mixins) is that the compiled output is far less bloated, as the original selectors are extended (ie. extending selectors are added as comma-separated selectors on the original rule). Compare that to including mixins, where a bunch of code is being duplicated on each include.

This would open the possibility of having another way of wring a cleaner (a.k.a "more semantic") HTML/CSS. I said "another way" because Bootstrap 3.0.0-wip currently provides

a way to work with semantic classes when using the grid system. But, precisely, this current way is the one using mixins as included, generating a more bloated code than the approach that uses ':extend'.

To be realistic, I'm not sure if this will be easily achievable in tandem the way the current Bootstrap grid system names its classes ((.col-*-[1...n]).

The limitation imposed by this way of naming classes is probably the explanation behind why other new (and innovative) grid systems, like csswizardry-grids and Unsemantic took a different approach for naming classes, using fractions and/or percentages, which are far more verbose and less readable (particularly when using them directly in class="" attribute).

In that sense, Bootstrap's class names for grid system are... neat.

Let's see if we can come up with a few ideas on how to take advantage of the upcoming ':extend' (and also silent classes and silent imports) on LESS 1.4.0.

Complementary reads:

less/less.js#1325

http://stackoverflow.com/a/15573240
Issue 1:
Several clients have asked for support of send-to-sync notifications, where a notification is received and the device is expected to sync down the new data in the background in response to the notification (instead of the notification itself carrying the payload).

My understanding from @collinjackson is that this is not currently possible to wire up due to lack of headless-Dart support in our APIs exposed to Flutter plugins.

This issue tracks work in the engine. Providing APIs to access the engine support is tracked in #3671

Issue 2:
When nesting a Slider widget in a Row the thumb shows up, but the text isn't rendered:

Widget _buildLineControls() {
return new Column(
children: <Widget>[
new Row(
children: <Widget>[
const Text('Line width:'),
new Expanded(
child: new Slider(
min: 1.0,
max: 15.0,
divisions: 15,
label: '${lineWidth.round()}',
value: lineWidth,
activeColor: lineColor,
onChanged: onLineWidthChanged,
),
),
],
),
],
);
}

But it works fine without the Row:

Widget _buildLineControls() {
return new Column(
children: <Widget>[
new Slider(
min: 1.0,
max: 15.0,
divisions: 15,
label: '${lineWidth.round()}',
value: lineWidth,
activeColor: lineColor,
onChanged: onLineWidthChanged,
),
],
);
}

This is on the latest master version:

Doctor summary (to see all details, run flutter doctor -v):

[✓] Flutter (Channel master, v0.2.3-pre.41, on Linux, locale en_US.UTF-8)

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)

[✓] Android Studio (version 3.0)

[✓] IntelliJ IDEA Community Edition (version 2017.2)

[✓] VS Code (version 1.21.1)

[✓] Connected devices (1 available)
Issue 1:
Environment

OS: Microsoft Windows [Version 10.0.18362.295]
WT: Version: 0.3.2171.0

Steps to reproduce

Open terminal

Open a second tab

Attempt to select text by clicking and dragging (I'm using a track pad, might be issue around that, don't have mouse available to test difference)

Expected behavior

Text should be highlighted

Actual behavior

Nothing

If I select text in the original tab, then try it in the new, second tab, selection starts working.

Issue 2:
Let me start by saying I did not read the whole source so I might have missed important details.

I was looking at the source code to understand how you're handling the commandline setting and saw that many methods in the Profile class do not move the instance of the std::wstring received and instead create a copy.

Also, why do you mark the methods noexcept when some strings might not be small enough to allow SSO? (e.g. a long command line)

Proposed technical implementation details (optional)

void Profile::SetCommandline(std::wstring cmdline) noexcept
{
_commandline = std::move(cmdline);
}
Issue 1:
React version: v18.0.0

Steps To Reproduce

Run this:

<!DOCTYPE html>
<html>
<body>
<div id="root"></div>
<script src="https://unpkg.com/react@18.0.0/umd/react.development.js"></script>
<script src="https://unpkg.com/react-dom@18.0.0/umd/react-dom.development.js"></script>
<script type="module">
const rootElement = document.getElementById('root')
const element = React.createElement('div', {
className: 'container',
children: 'Hello World',
})
ReactDOM.createRoot(rootElement).render(element)
</script>
</body>
</html>

Link to code example: https://jsbin.com/hucetewebu/edit?html,js,console,output

The current behavior

Getting a console error:

index.js:1 Warning: You are importing createRoot from "react-dom" which is not supported. You should instead import it from "react-dom/client".

However, there's no UMD version of react-dom/client so the error is not actionable.

I am able to work around this by adding this to the top of the script:

ReactDOM.__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED.usingClientEntryPoint = true

But obviously that's not a great solution, especially for what I'm trying to do 😅

The expected behavior

Disable the warning for UMD or give some other way to use createRoot from the UMD.

Use case

I use the UMD as a way to ease people into React without introducing a bunch of tooling up-front. Getting an error in the console is not a great experience.

Issue 2:
This is a false positive.
Issue 1:
[Enter steps to reproduce below:]

...

...

Atom Version: 0.187.0

System: Microsoft Windows 8.1

Thrown From: Atom Core

Stack Trace

Failed to load the wordpress-api package settings

At unexpected action in C:\Users\Code Local\.atom\packages\wordpress-api\scoped-properties\wordpress.hooks.cson

[stdin]:40:33: error: unexpected action
'admin_action_{$_REQUEST['action']}'
^^^^^^
at C:\Users\Code Local\.atom\packages\wordpress-api\scoped-properties\wordpress.hooks.cson:1:1

Commands

-1:21.6 tree-view:toggle (select.form-control)
-0:54.4 core:confirm (atom-text-editor.editor.mini)

Config

{
"core": {
"themes": [
"one-dark-ui",
"atom-dark-syntax"
]
},
"editor": {
"fontSize": 16
}
}

Installed Packages

# User
wordpress-api, v1.1.0

# Dev
No dev packages

Issue 2:
First of all, thanks for making this package! I'm getting an error on startup using the latest version of Atom. Here's the automated report it generates:

Atom Version: 0.187.0

System: Mac OS X 10.10.2

Thrown From: wordpress-api package, v1.1.0

Stack Trace

Failed to load the wordpress-api package settings

At unexpected action in /Users/robertneu/.atom/packages/wordpress-api/scoped-properties/wordpress.hooks.cson

[stdin]:40:33: error: unexpected action
'admin_action_{$_REQUEST['action']}'
^^^^^^
at /Users/robertneu/.atom/packages/wordpress-api/scoped-properties/wordpress.hooks.cson:1:1

Config

{
"core": {
"followSymlinks": true,
"themes": [
"one-dark-ui",
"base16-eighties-one-dark"
],
"disabledPackages": [
"minimap"
]
}
}

Installed Packages

# User
Atom-Syntax-highlighting-for-Sass, v0.5.0
alignment, v1.1.4
atom-bourbon-snippets, v0.9.0
autocomplete-css, v0.4.0
autocomplete-html, v0.3.0
autocomplete-plus, v2.4.1
autocomplete-snippets, v1.0.1
base16-eighties-one-dark, v0.2.1
change-case, v0.5.1
color-picker, v1.4.4
docblockr, v0.6.3
file-icons, v1.5.1
highlight-selected, v0.9.1
linter, v0.12.0
linter-csslint, v0.0.11
linter-jscs, v1.9.0
linter-jshint, v0.1.0
linter-jsonlint, v0.1.2
linter-php, v0.0.11
linter-phpcs, v0.0.12
linter-scss-lint, v0.0.14
project-manager, v1.15.5
sync-settings, v0.2.2
tabs-to-spaces, v0.8.1
trailing-spaces, v0.2.4
wordpress-api, v1.1.0

# Dev
No dev packages
Issue 1:
Similar to other browser globals but recognize this is an ambitious request. If web compatibility is a goal then from my perspective this should be too.

Currently there are only a few options for constructing a DOM on the backend. Some folks are using Chromium/Puppeteer but this is really memory intensive and crummy for places where coldstart performance is important (like AWS Lambda). JSDom has some support for doing this but resolving esmodules mixed with Node require is clunky at best. A first class runtime solution on the backend for Web Components would be extremely useful for those of us that want to render as much of the DOM as possible before sending it to the client.

I think that's a very large audience and a worthwhile goal. Thanks for considering!

Issue 2:
@MarkTiedemann I was wondering if the jsdom port is still happening? I see it was never merged: denoland/deno_std#542

It would be amazing to be able to test code for the browser in Deno 1.0. Thanks!
Issue 1:
This component seems nice to have!

I will standardise it later if you guys don't have time.

https://pasteboard.co/H6O9a3h.png

Ps: Awesome work. keep up the good work

Issue 2:
Scroll down a little here, and you'll see a speed dial pattern. It would be nice if Material UI could support both a vertical and horizontal speed dial on it's Floating Action Buttons.
Issue 1:
There has been people on the forums who have expressed the desire for this feature.

More details of what a proxy icon is and how it works can be found in OS X Human Interface Guidelines: Windows under "The Proxy Icon and Title Bar Menu" (I could not figure out how to link to the subheading).

Here's a gif of how the proxy icon works when cmd+clicking:

Issue 2:
Halp ticket

support/70c780e8ca2711e39d3156f8d64ff878

Cannot operate (e.g drag&drop, right click) on Atom's titlebar text and icon (the latter is missing anyway). Try it on Finder, TextEdit or Terminal.app to get what I mean. Notice the difference in behavior in TextEdit when the file is or isn't saved.

This is one of those little OSX gems that can change your life. Please save mine and implement it.

Also, a similar description from a related issue:

More details of what a proxy icon is and how it works can be found in OS X Human Interface Guidelines: Windows under "The Proxy Icon and Title Bar Menu" (I could not figure out how to link to the subheading).

Here's a gif of how the proxy icon works when cmd+clicking:

I've already seen a couple of similar requests before, so finally made an issue to track these requests.
Issue 1:
Hello, as a nice to have if you could render assetic more flexible it would be nice.

I explain myself, i a usecase we want to store css in database to generate it on the fly but with assetic it is really really hard. in fact we spend couple of days understanding the bundle and trying to add a DataBaseAsset.

We wanted to have an inline editor to stor css in the databse and render it without caching at first time.

We tried to add it to assetic with the Injection Pattern but lots of attributes and methods are private. In fact should be protected to be able to extend it.

Also Assetic use the twig compiler to write in the cache and not in the runtime.

It would be nice to simplify the bundle, i now it's a bit hard to do it but extending it is pretty hard too.

Working with general case is nice and assetic is nice because it work but it should be a bit more simple and also it is horrible seeing these private attributes and methods, we need to duplicate code if we want to extend it.

May we will write our custom bundle because it don't match our needs.

I hope i was clear and i help a bit

Issue 2:
The drupal team is back!

In this drupal issue (==> http://drupal.org/node/1599108 ) someone advises to use dependency injection tags like described in this post: http://symfony.com/doc/master/components/dependency_injection/tags.html.

I tried to do that but got a fatal error because the addObjectResource function in The ContainerBuilder class has a hard dependency on the config component. We can not use that component....

Is there a reason why this is so tightly coupled? Is it possible to soften the coupling? Is there a possibility to rewrite this code to prevent this kinda coupling between those two components (Config and DependencyInjection)

Thnx!
Issue 1:
I get the following behaviour on Windows only, using numpy 1.13.1 installed via conda:

>>> import numpy as np
>>> v = np.array('xxx', dtype='U3')[()]
>>> v
'xxx'
>>> a = np.empty(10, dtype='U3')
>>> a[:] = v
>>> a[0] == v
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
UnicodeDecodeError: 'utf-32-le' codec can't decode bytes in position 0-3: code point not in range(0x110000)

I don't understand what's happening here but this seemed surprising to me. Default locale on the Windows machine is cp1252 if that helps to know.

xref https://github.com/alimanfoo/zarr/pull/172

Issue 2:
Follows on from #1123

I'm assigning a numpy.unicode_ to a slice of array of numpy.unicode_ and see the following:

In [85]: l = np.array([u'blah',u'blah',u'blah'])

In [87]: type(l[0])
Out[87]: numpy.unicode_

In [88]: v = np.unicode_('bubu')

In [89]: l[0] = v

In [90]: l
Out[90]:
array([u'bubu', u'blah', u'blah'],
dtype='<U4')

In [91]: l[1:3] = v

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
In [92]: l
Out[92]:
array([u'bubu', u'\uf500\udc62\uf500\udc62\u8d00\udc00',
u'\uf500\udc62\uf500\udc62\u8d00\udc00'],
dtype='<U4')
<<<<<<<<<<<< I consider this a problem

In [93]: {k: v for k, v in sysconfig.get_config_vars().items() if 'unicode' in k.lower()}
Out[93]:
{'PY_UNICODE_TYPE': 'unsigned short',
'Py_UNICODE_SIZE': 2,
'Py_USING_UNICODE': 1,
'UNICODE_OBJS': 'Objects/unicodeobject.o Objects/unicodectype.o'}

In [94]: np.**version**
Out[94]: '1.7.1'

$ uname -a
Linux ... 2.6.32-279.19.1.el6.x86_64 #1 SMP Wed Dec 19 07:05:20 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

On a wide unicode build I can do the same with no problem:

In [81]: l = np.array([u'blah',u'blah',u'blah'])

In [82]: type(l[0])
Out[82]: numpy.unicode_

In [83]: v = np.unicode_('bubu')

In [84]: l[0] = v

In [85]: l
Out[85]:
array([u'bubu', u'blah', u'blah'],
dtype='<U4')

In [86]: l[1:3] = v

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
In [87]: l
Out[87]:
array([u'bubu', u'bubu', u'bubu'],
dtype='<U4')
<<<<<<<<<<<<<<<<<<<<<<<<<<<< this works fine

In [88]: {k: v for k, v in sysconfig.get_config_vars().items() if 'unicode' in k.lower()}
Out[88]:
{'PY_UNICODE_TYPE': 0,
'Py_UNICODE_SIZE': 4,
'Py_USING_UNICODE': 1,
'UNICODE_OBJS': 'Objects/unicodeobject.o Objects/unicodectype.o'}

In [89]: np.**version**
Out[89]: '1.7.1'

(my27py)pavel@pavel-ThinkPad-T520:~$ uname -a
Linux pavel-ThinkPad-T520 3.2.0-40-generic #64-Ubuntu SMP Mon Mar 25 21:22:10 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux